RGH Two xbox's dead after flashing glitch image

M

mamaki

Junior Member
Jun 9, 2004
17
0
Portugal
so many thanks to everyone, i have successfully rewrite the nands with the 44-47 pin shunt recovery solution.

what i have done:

1 - unplug power connector from xbox

2 - shunt pin 44-47 with a flat head screwdriver

3 - plug the power connector to xbox

4 - get the screwdriver out of nand pins

5 - try to write your nand backup

the nandpro will recognise and write to nand.

if you dont have success on the first time, repeat always from the 1st step.

i have to repeat +/- 5 times to get success
 
M

mamaki

Junior Member
Jun 9, 2004
17
0
Portugal
yes it worked for slim and phat.

I will not build again a glitched image with XnandHealer0.72, seems that the program generate a corrupt 14699 glith image.

If someone have the same experience with XnandHealer0.72 please post.
 
T

tingedace

VIP Member
Feb 23, 2011
387
0
Scotland
I've never seen this problem but would also be interested to hear if it's happened to anyone else.

I did a trinity tonight, and 3 Jaspers (1 x 16SB, 1x 256BB and 1x512BB) in the last few days and no problems at all. All with Xnandhealer using the multibuilder 0.7 folder structure.

Not had the opportunity to test a Falcon yet as I don't have one.

Could the multibuilder folder have been corrupted or changed/rearranged in any way? XNH has only been tested using a fresh unpack of Multibuilder so I'm wondering if anything could have changed.

Have you used Multibuilder itself standalone previously before using Xnandhealer? Any bad blocks?

EDIT:
Do you still have a copy of the glitch_image.bin.log file? It will be in the same folder as your nand dumps.
 
Last edited:
T

tingedace

VIP Member
Feb 23, 2011
387
0
Scotland
OK I have a theory as to what's going on...

Xnandhealer 0.72 was tested with Multibuilder 0.6 quite extensively before being released. Literally minutes after releasing it (and cracking open a cold one) I discovered that Multibuilder 0.7 had been released - D'oh!

So I grabbed it and did some testing and found quite quickly that there was a stray smc.bin file in the \my360 folder that was causing problems with retail images. However it appeared that Multibuilder removed this when it was first run so I noted it in the Xnandhealer release thread and thought it wouldn't be a big deal.

Now if it's possible that running multibuilder 0.7 or something else can leave an smc.bin file in that \my360 folder then xeBuild will pick it up by default when it's invoked. And of course having a wrong smc ties up with the symptoms of dead xbox / can't detect nand.

This is just speculation but does seem plausible. Still if someone who's had the problem can send me their glitch_image.bin.log file it should confirm it.

Either way I will release an update of xnandhealer tomorrow to ensure any smc.bin file is removed prior invoking xeBuild. In the meantime it should be removed manually if it exists prior to running xnandhealer 0.72.

---------- Post added at 18:30 ---------- Previous post was at 18:27 ----------
xboxhack11 said:
What is your CB version on that falcon? I often see posts with problems flashing Falcons and Jaspers but generally people dont post cb number. Some falcons and some jaspers are not glitchable apparently.

http://img802.imageshack.us/img802/8560/identifypowerjtglitchv1.png

Could this be one of them?
Click to expand...
True some CBs aren't but I think if it was an un-glitchable CB it would still power up but just not boot successfully.

Worth checking though :smile:
 
You must log in or register to reply here.