|
watk
|
 |
« Reply #20 on: November 01, 2011, 07:18:19 PM » |
|
Well I suppose there is the possibility that you broke something. Have you tried reconnecting the glitch clip?
Also have you totally disconnected all the glitch wires, rather then just remove the chip?
The only thing thats still connected on board is the nand x wires, the problem is... if I put the hacked and back the red light desappers and I get the green light flashing like the glitch one...
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
|
Vampirtc
|
 |
« Reply #23 on: November 02, 2011, 06:13:15 PM » |
|
I have the same problem. Was trying different cable lenghts and I somehow pulled part of FTR42 trace. After that the fan is reseting like every 0,5 seconds. I have made two nand dumps, both match. I also have the correct CPU key. Tried writting original nand back, I get red light and 0032 secondary error. But the problem was cause sometime during my testing, I think it must have been just after I pulled the wire and killed some of the trace on FTR42. I have tried soldering to alt point, doesn't work either. Have tryed with ggbuild nand as well.
|
|
|
|
|
Logged
|
|
|
|
|
fullban
|
 |
« Reply #24 on: November 02, 2011, 06:36:59 PM » |
|
|
|
|
|
|
Logged
|
|
|
|
|
watk
|
 |
« Reply #25 on: November 02, 2011, 08:31:45 PM » |
|
I have the same problem. Was trying different cable lenghts and I somehow pulled part of FTR42 trace. After that the fan is reseting like every 0,5 seconds. I have made two nand dumps, both match. I also have the correct CPU key. Tried writting original nand back, I get red light and 0032 secondary error. But the problem was cause sometime during my testing, I think it must have been just after I pulled the wire and killed some of the trace on FTR42. I have tried soldering to alt point, doesn't work either. Have tryed with ggbuild nand as well.
Just a sad thing, a lot of ppl with the same problem and no one knows yet what's going on O.o
|
|
|
|
|
Logged
|
|
|
|
bownsir
Newbie

Posts: 2
|
 |
« Reply #26 on: November 02, 2011, 09:36:38 PM » |
|
I thought I was the only one with this problem. I pulled the FTR42 pad while trying to rewire. I wrote original nand back and get red dot with secondary code 0032. I removed my glitcher and flashed stock nand back, dumped for comparison, now there are differences from my original dumps that worked compared to the dump after i got 0032. When I flash the ggbuild updflash and matrix wired up, I can here the fans resetting so the matrix is trying to glitch but wont. I scraped the trace of FTR42 so I know it should work.Will continue to look for a fix.
|
|
|
|
« Last Edit: November 02, 2011, 11:21:53 PM by bownsir »
|
Logged
|
|
|
|
|
edsondario
|
 |
« Reply #27 on: November 02, 2011, 10:34:04 PM » |
|
Here I finished the whole process and the red light remained the same in the original dash. Not synchronizing the controls. Disconnect the matrix glitche, there were only taken before the VCC, and slim worked normal. The GND was connected with the CPU_RESET (A). In your case, Watk, it may happen that one of the glitch points have been connected in GND.
|
|
|
|
« Last Edit: November 02, 2011, 10:38:22 PM by edsondario »
|
Logged
|
|
|
|
|
Vampirtc
|
 |
« Reply #28 on: November 03, 2011, 12:49:00 PM » |
|
I used a magnifying glass and noticed that the FT4R2 pad has a connection going from it. By lifting the pad I think that you kill that connection as well. Could someone with more experience check and suggest a solution for this?
|
|
|
|
|
Logged
|
|
|
|
|
watk
|
 |
« Reply #29 on: November 03, 2011, 09:14:08 PM » |
|
I used a magnifying glass and noticed that the FT4R2 pad has a connection going from it. By lifting the pad I think that you kill that connection as well. Could someone with more experience check and suggest a solution for this?
Dude I just checked, and I think I did the same here O.o, theres any alternative point to this ?
|
|
|
|
|
Logged
|
|
|
|
|
maximilian0017
|
 |
« Reply #30 on: November 04, 2011, 05:46:08 AM » |
|
if you damage something just make a picture of it and it will be a lot easyer to help.
|
|
|
|
|
Logged
|
|
|
|
|
watk
|
 |
« Reply #31 on: November 04, 2011, 10:20:00 AM » |
|
if you damage something just make a picture of it and it will be a lot easyer to help.
I will when I get back from work, later~ Thanks for the help~
|
|
|
|
|
Logged
|
|
|
|
|
maximilian0017
|
 |
« Reply #32 on: November 04, 2011, 11:27:47 AM » |
|
You can post the images here if the pictures they have in the thread don't seem to describe your problem.
|
|
|
|
|
Logged
|
|
|
|
Orka
Newbie

Posts: 4
|
 |
« Reply #33 on: November 06, 2011, 01:42:02 PM » |
|
|
|
|
|
|
Logged
|
|
|
|
Hucklebuck
Newbie

Posts: 1
|
 |
« Reply #34 on: July 03, 2012, 09:02:14 AM » |
|
I am having the same problem. I had my console glitching. Then I decided to change to thicker wire to improve my glitch time, I pulled the FT4R2 pad off. I tried some of the alternate points to no avail. Console would give green light but glitch chip wouldn't flash. So I removed the glitch chip and flashed stock nand, that's when I got a red light and no a/v. I got error code 0032.
Anyone have a solution for this yet? Any recommended repairman for this in the Chicago area? Or anywhere?
|
|
|
|
|
Logged
|
|
|
|
|