Error 0022 after flashing back to stock.

[Menethoran]

Hey guys... did a console (Zephyr - RGH1) for a kid that is local but moved to Colorado... Everything was good on my end when i shipped it out (USPS)... but when the customer got the console he couldnt get it to glitch. I thought at first it was the PRG/NOR switch got tripped (ive had it happen once before shipping USPS...NO freaking clue how...). So, I had the kid take the cover off and check the PRG/NOR switch as well as take a look at the DBG light (DBG wasnt lighting up) so, I had him send it back to me.

Anyway, long story short, I got it back today and redid all the wiring figuring it was a broken solder joint or something. Still no debug light). So, figured...lets check stock NAND... lo and behold, im getting RRoD (0022)... is rthere any chance this is a lifted trace i just cant see? or is 0022 always needing to be reflow/reball?

Photos of PLL_BYPASS (As it's the only thing ive seen so far that MIGHT cause 0022)
There doesnt seem to be any damage, and pad is not lifted...

http://i1326.photobucket.com/albums/u645/Menethoran/IMG_9285_zps34e7df7f.jpg

http://i1326.photobucket.com/albums/u645/Menethoran/IMG_9284_zpsbbb81acf.jpg

ALSO, now that i compare nands (i read the nand before flashing back to retail...)
here are screen shot comparing the nand i took from the machine after i got it back and one of the nand when i load it from retail...

 

[BL4K3Y]

When you power on the console with the stock NAND written and the CR disabled (switch set to PRG), how many seconds does it take to red ring?

 

[Menethoran]

5 to 7 seconds.

Ignore the previous pics... screenshot issues...

anyway, comparison of the nand i read as retail before sending it out, and a read of the nand today before flashing the retail nand back onto the machine...

FYI, the pic on the right is the RETAIL original nand... The pic on the left is the read i took when i got the machine today BEFORE flashing the retail nand back to the machine.

 

[BL4K3Y]

5 to 7 seconds.

That sounds like an issue with CPU_PLL_BYPASS.

Has it been shorted to ground?

The R7R17 resistor should measure 10K Ohm, but you need to remove it before you can get an accurate reading from it.

 

[Menethoran]

replaced R7R17 from a donor board... same issue (cant test at the moment, multimeter needs a 9v battery, which is apparently no where in this house)

 

[Menethoran]

strike that.. RE-replaced the R7R17 (but tested it before changing it (dug up a 9v from my scale)...)

ANYWAY, now ive got a 0022 at 30-ish seconds (somewhere between 30 and 33 seconds)

 

[BL4K3Y]

now ive got a 0022 at 30-ish seconds (somewhere between 30 and 33 seconds)

I am pretty sure that means the CPU is dead (I had a similar problem with a Jasper motherboard a few months ago).

The CPU heatsink on a Zephyr board will get hot in a short time, so with the console powered on, see if the CPU heatsink starts to get warm.

If it doesn't, you have two choices - replace the CPU or buy a new motherboard (recommended).

 

[Menethoran]

odd, hit the resistor again with the iron, and just for good measure, touched up some surrounding points with flux and the iron, now i get 0102 at around 5 seconds...

grrrr....

and yes, the cpu gets VERY warm, VERY quick... not hot, but definately way up on the warm end of things in under 5 seconds.

 

[nofeloniesyet]

odd, hit the resistor again with the iron, and just for good measure, touched up some surrounding points with flux and the iron, now i get 0102 at around 5 seconds...

grrrr....

and yes, the cpu gets VERY warm, VERY quick... not hot, but definately way up on the warm end of things in under 5 seconds.

0102 is actually one of the more common error codes,which points toward gpu reflow/reball.any chance you have the right equipment to try it out? also how long does it take to rrod and throw 0102?

 

[Menethoran]

a reflow, yes... but not here at home, at my shop, yes. will give it a shot tomorrow.

 

[nofeloniesyet]

a reflow, yes... but not here at home, at my shop, yes. will give it a shot tomorrow.

how long is it taking to rrod? and i would boot it quite a few times and make sureeeee this isnt one of those consoles where its throwing diff error codes all the time,those can have you hunting issues for days,and simply arent worth the time and aggrivation imho.

 

[Menethoran]

first 0102 seemed to be 15 seconds, since that one though, 5 seconds...

 

[Menethoran]

will a RRoD (specifically with a cold solder/bridged joint under CPU) attempt to glitch? ie, could this machine have been dead and thats what was causing the no DBG light to show... or was this more likely a grounded PLL (assuming thats what cause 0022) that just cascaded?

 

[gavin_darkglide]

I had an issue similar to this with a falcon r-jtag/demon, installed everything, and it worked for about 2 hours, before it got the RROD. Never did figure out what was wrong with it, as the error code seemed to change every time i booted it. I decided to scrap the board, if a reflow on the GPU doesnt fix it, I would scrap it. This is why I try to avoid anything below a Jasper.

 

[moco]

Dont know if this will help you. I just did a Jasper, whenever I had pll bypass connected, even with a raw wire disconnected at the opposite end, I got the same error, no debug and no booting of stock nand. When removed the wire, stock nand booted fine. I then tried topside pll bypass by the via, got debug led, very fast, then it stopped.

The only way I was able to rgh the console was by updating it and doing an rgh2.0. That worked fine. I suggest it may work for you as a last resort.

It seems from what I've read that some consoles act up when anything at all is connected to pll bypass.

 

[Menethoran]

I am awaiting material for a reball.. reflow didnt work, just led to a 0020 (bridged solder joint under cpu)...
so, ill pull the chip, reball it and pray... if that doesnt work, it'll go into my spare parts bin...