Hey everyone,
Got a modchip that is driving me nuts over here, modded it about a year ago and was fine for a while but I don't think it was powered off or rebooted very much. The battery died and when we turned it back on no response from the chip AT ALL. Zip zilch nothing, so I assumed DAT0 and tore the console down, resoldered DAT0 in place and tested again, was getting straight red flashing and looking around i see that possibly means fpga issue (I'm guessing the modchip itself right).
Interesting thing however is every once in a while it will turn on and glitch, also every time I try to do a diagnostic with putty it glitches quickly. However if it's. It connected then the chip will do a few different things.
1. No power to switch, no lights on modchip. (Chip has 3.3v and reset (b) has just under 1.8v)
2. No lights on modchip but boots straight to OFW (almost like it doesn't have power)
3. Chip will flash red 7-9 times, short pause and repeat. This seems to happen until I pull the battery or maybe it will stop on its own but for testing I've been d/c battery to move on.
4. Glitch on its own and get No SD Card rocket image (don't have the SD card yet that was a whole other deal)
5. Connect to PC to diagnose and it basically glitches almost instantly Everytime.
Also to note if I try to test a few times and getting results #2 multiple times I hook up the USB I get the pulsing blue light and the next glitch attempt almost always succeeds
Every once in a while when trying to diagnose I get an error "Glitcher fatal : no MMC CLK observed" Diagnose status: BAD00108 (ERR_GLITCH_NO_EMMC_COMM) and led is flashing white continuously and boots OFW. (D point?)
Now for diode values checked with black on USB port and red on pins for ribbon cable on the chip.
3.3v - .87
D - .61 (this one changes somehow, sometimes if I push a certain way on the D point on the ribbon test pad then I get .72 or so) wondering now if the ribbon has an issue or just my meter/leads. Can you leave the ribbon soldered on and run a jumper wire or should I remove the ribbon first?
A - .73
C - .75
B - 2.94
Diode with red probe on USB
3.3 - .44
D - .55
A - .56
C - .53
B - .7
D point may be a little low but I don't think that would cause the other issues of flashing red as well as just nothing at all. Hoping someone has seen similar. I know everyone is probably going to say DAT0 but that doesn't really explain why it almost always glitches in diag mode and the diode values are spot on. Yesterday I touched up every solder joint besides B point since my original install was without a scope and while they were solid they weren't the best looking and trying to figure out what is going on
TIA
Got a modchip that is driving me nuts over here, modded it about a year ago and was fine for a while but I don't think it was powered off or rebooted very much. The battery died and when we turned it back on no response from the chip AT ALL. Zip zilch nothing, so I assumed DAT0 and tore the console down, resoldered DAT0 in place and tested again, was getting straight red flashing and looking around i see that possibly means fpga issue (I'm guessing the modchip itself right).
Interesting thing however is every once in a while it will turn on and glitch, also every time I try to do a diagnostic with putty it glitches quickly. However if it's. It connected then the chip will do a few different things.
1. No power to switch, no lights on modchip. (Chip has 3.3v and reset (b) has just under 1.8v)
2. No lights on modchip but boots straight to OFW (almost like it doesn't have power)
3. Chip will flash red 7-9 times, short pause and repeat. This seems to happen until I pull the battery or maybe it will stop on its own but for testing I've been d/c battery to move on.
4. Glitch on its own and get No SD Card rocket image (don't have the SD card yet that was a whole other deal)
5. Connect to PC to diagnose and it basically glitches almost instantly Everytime.
Also to note if I try to test a few times and getting results #2 multiple times I hook up the USB I get the pulsing blue light and the next glitch attempt almost always succeeds
Every once in a while when trying to diagnose I get an error "Glitcher fatal : no MMC CLK observed" Diagnose status: BAD00108 (ERR_GLITCH_NO_EMMC_COMM) and led is flashing white continuously and boots OFW. (D point?)
Now for diode values checked with black on USB port and red on pins for ribbon cable on the chip.
3.3v - .87
D - .61 (this one changes somehow, sometimes if I push a certain way on the D point on the ribbon test pad then I get .72 or so) wondering now if the ribbon has an issue or just my meter/leads. Can you leave the ribbon soldered on and run a jumper wire or should I remove the ribbon first?
A - .73
C - .75
B - 2.94
Diode with red probe on USB
3.3 - .44
D - .55
A - .56
C - .53
B - .7
D point may be a little low but I don't think that would cause the other issues of flashing red as well as just nothing at all. Hoping someone has seen similar. I know everyone is probably going to say DAT0 but that doesn't really explain why it almost always glitches in diag mode and the diode values are spot on. Yesterday I touched up every solder joint besides B point since my original install was without a scope and while they were solid they weren't the best looking and trying to figure out what is going on
TIA
Last edited by T4nk3d,






