RGH Partial update to 14719, but not quite..

[dogeatdog]

Ok, I need the help of the experts on this one.

A customer dropped off an XBOX tonight, turning it on revealed a nice 351F-397F-xxxx error.

So this means an interrupted update to 2.0.14719.

The drive is flashed back to stock and is the correct drive (first thing I did and checked).

But here's the catch, the XBOX needs to be glitched.

Of course I prefer RGH1 over RGH2 and I know that I can fix the 351F-397F by letting the XBOX update from USB to 2.0.14719... but that would mean RGH2..

So, can I dump the nand as is and use that as a basis for an RGH1 or will this 'limbo'-state prevent that in some way. Also.. is the damage already done ?

I tried teajunkie's reset cache method (hold synch while powering the xbox), but that didn't help..

Any help is welcome

 

[webnomix]

My guess would be that the damage has been done. I would dump the nand and have a look at the CB, but to be honest I would be preparing for a RGH2.

 

[dogeatdog]

Dumping right now.. I'll get back to you

 

[dogeatdog]

Crap : 5773, Falcon, 14719.

Ah well, happy hunting for another sweet spot it is..

Not so shabby after all : same config as another Falcon RGH2 last week (cpu_rst kynar wire, top board, Martin C's method (470pF/2kOhm) and glitches consistently around 30-40 secs.

 

[webnomix]

Not too shabby at all, well done.