Stock NAND 0020 Error

[Scrufdog]

I installed an R-Jtag and Demon to my Falcon last night. This is not the same Falcon that gets a 0010 in the thread thats in the RJtag section.

I get RRoD 0020 when trying to boot the Stock NAND on the Xbox360. All LDVs match, however the various BL's are all different. I'll post pics.

Here's what I've tried.

Demon and Rjtag connected normally. Demon - Glitch NAND, Xbox360 - Stock NAND. Glitch boots fine, Stock instant 0020.

Rjtag to Demon ribbon cable disconnect, so Rjtag runs on both NANDs. Demon - Glitch NAND, Xbox360 - Glitch NAND. Both boot just fine.

Rjtag 5v wire removed, demon to rjtag ribbon cable disconnected. Demon - Stock NAND, Xbox360 - Stock NAND. Both boot fine.

Rjtag 5v wire removed, demon to rjtag ribbon cable disconnected. Demon - Glitch NAND, Xbox360 - Stock NAND. Glitch side just sits there with the green center light, waited 2 minutes, nothing happened. Stock side instant 0020

Gone through all my soldering, looks pretty good, at least the important stuff.

To make sure the NANDs are actually switching, I flashed the Demon side with the Glitch NAND, then flashed the Xbox360 side with the Stock NAND. I then read the Xbox360 and compared and both NANDs were the same. So it's definitely flashing to both NANDs, from what I can tell.

Xbox was on dash 16302 when I started, and ran just fine.

The glitch NAND was built with the stock NAND, so I'm not sure why the BL's are different, must be a needed thing for glitching, I dunno.

Any thoughts on this one?

 

[Scrufdog]

I flashed the stock NAND with Jrunner 289 and now it's an instant 0010. Could this have anything to do with the 14 bad blocks in there?

 

[Scrufdog]

Here's a Rater Log on the stock side when it errors out.

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 01 
Post 03 
Post 01 
Post 10 - Payload/1BL started 
Post B7 - Panic - UPDATE_MISSING 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 34 - HMACSHA_COMPUTE_4BL_CD 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 34 - HMACSHA_COMPUTE_4BL_CD 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 34 - HMACSHA_COMPUTE_4BL_CD 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 94 - Panic - VERIFY_OFFSET 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 01 
Post 01 
Post FD 
Post 01 
Post 01 
Post 03 
Shutdown
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 94 - Panic - VERIFY_OFFSET 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 94 - Panic - VERIFY_OFFSET 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 01 
Shutdown
Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 94 - Panic - VERIFY_OFFSET 
Post 34 - HMACSHA_COMPUTE_4BL_CD 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 94 - Panic - VERIFY_OFFSET 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 94 - Panic - VERIFY_OFFSET 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post B4 - Panic - LZX_EXPAND 
Post 14 - FSB_CONFIG_TX_CREDITS 
Post 01 
Shutdown

Also, glitch side runs within 1-2 cycles, with the occasional -

Post 01 
Post 01 
Post 01 
Post 03 
Post 33 - FETCH_CONTENTS_4BL_CD 
Post 03 
TIMEOUT or SMC CORRUPTED - Shutting Down
Most Fails(cumulative): 0x22
Shutdown

Probably fix that with some DIP tweaking, but the problem is still getting the stock side to boot.

 

[Martin C]

Remove everything (if you've not already done so) and write the stock NAND back.

If you're still getting 0020 then it's probably a genuine RRoD.

 

[Scrufdog]

Took the Jtag QSB off the bottom first. Still 0020. Desolder the wires from the JR QSB v3, left the QSB on, and works no problem, flashed stock to Demon as well as Xbox360, both boot just fine. So it seems like there may a problem with the Rjtag board conflicting with something on the stock side. I think someone mentioned once in a post that the voltage and DIP settings could conflict with the stock NAND. I'm currently running at 1.2v DIPs 1,7 ON. I'm going to solder the wires back to the rjtag QSB and see where it errors out.

 

[Scrufdog]

Jtag QSB removed. Rjtag unwired from JR QSB V3, QSB in place. Flashed both Demon and Xbox360 with retail NAND, both boot fine. Flash Demon with Glitch NAND, switch to Xbox360 side that still has the stock NAND, boots into 0020. So I'm guessing at this point its a Demon thing. Gonna check my points on it. Is there a resistance check list for each point I can use to help? Before I reflow the joints.

 

[Scrufdog]

I'm getting 0 ohms resistance from test pads on the Demon to the Alt points on top of the board at the NAND chip (thanks XMods). Whats next to check on the Demon?

Could this be a Demon firmware thing? I updated it from 1.0 to what Jrunner lists as 1.4 before I installed it. Should I try a reflash?

 

[Scrufdog]

Put Demon into bootloader mode, reflashed with 1.04, still RRoD 0020 if a glitch NAND is on the Demon. This will only boot stock is a Stock NAND is on the Demon AND the Xbox360. Jrunner is reading a flashing to 2 different NAND chips for sure, as I checked by reading and writing different NANDs, so it seems that is not actually switching with the Demon I guess. Seems like it will only boot from the Demon NAND, and not from the Stock Chip. What else can I check on the Demon while its installed?

 

[Scrufdog]

Before I swap the Demon for another one, is there anything else I can check with my multimeter or oscilliscope, on the Demon itself?

 

[Martin C]

SBR controls the switch between the two. I would definitely tidy up RB soldering as that's too long a wire.

For the DemoN, erase the NAND and write a 'noremp' image with the Advanced option (Demon/Fusion write).

 

[Scrufdog]

ok.

I'll clean up RB, shortening the wire itself and the exposed copper right at the point.

What type of signal is supposed to be on the SBR? Something measurable?

I'll check those things tonight or tomorrow. If that doesnt work, I have another Demon I can try. I'll remove the current Demon, check for stock operation, and then install a new Demon, if needed.

Thanks

 

[Martin C]

Can you also take a better pic of the DemoN, just so we can see where all your wires are going?

I'd also tidy SBR to the console, while you're there.

 

[Scrufdog]

yes sir. I'll shoot for tonight or tomorrow with cleanup and pics. I wont remove the Demon until all else fails.

 

[Martin C]

Cool - FTR, I don't think the DemoN is at fault here.

 

[Scrufdog]

ok... touched up solder, cleaned up wires.

As flashed and results....

Demon - Stock (erased, then Flash with Advanced - Demon Write (remaps bad blocks) option...... Xbox360 - Stock ==== Both boot fine.
Demon - Glitch (erased, created new NAND with noremap option on 16203 NAND)...... Xbox360 - Stock ==== Stock side - 0020 error, Glitch side(without rjtag installed) just sits there.

Also, just in case it comes up, I unplug the xbox for 30 seconds in between each flash.

 

[gavin_darkglide]

try booting the glitch image, and then switch nands with xbox on, and then hit the power button again. I bet it boots stock and works properly until you unplug the power again. Had this problem on a falcon board, and never did find a solution other then this...... I chalked it up to a freaky smc reset error.

 

[Martin C]

Can you do me a favour and just write the ECC file to the DemoN and let me know what happens?

 

[Scrufdog]

No rjtag installed...

Demon - ECC(Xell-Reloaded), Xbox360 - Stock ==== Demon - RRoD diagonal 2,3 no secondary... Xbox360 - 0020

.....

Same as above, booted to Demon (error), switched NAND to Xbox360 and immediately hit power button, booted stock fine. Weird. I believe I've read this before, with no fix. Ideas?

 

[Martin C]

You should be using AUD_CLAMP TBH - using R2P12 or any other RoL soldering causes glitches with the RoL board.

I meant using the xell.bin, apologies.

Can you replicate the switch from DemoN to XBOX and boot stock every time?

eg - plug in PSU, so DemoN LEDs should be on.

Then:
Try to boot. Power off.
Press button so LEDs are off. Try to boot again. Power off.
Press button so LEDs are on. Try to boot again. Power off.
etc - do this 5 times and without pulling the PSU, do you get the same result each time?

 

[Scrufdog]

I'll let ya know.

My Falcon Jtag glitches out the ROL, so thats something I'm used to at this point. Once the current issue is fixed or settled I may switch over to AUD_CLAMP.