Xbox freezes after Original Nand Flash

[legitmod]

You nand dose not appear to have any faults in it your dashboard is 12625 which is the very first dashboard i be leave for slims what command are you using to write the nand

---------- Post added at 22:17 ---------- Previous post was at 22:12 ----------

NAND Looks fine. It's actually the first Slim nand, 12625 and LDV is 1. Unless OP ran a update there is no need to change the LDV value.

The nand is fine so it should work without an issue, E79 on a Slim is more than likely related to the nand, my first RGH was a Slim and I had some major E79 issues. You cannot create a retail image without CPU key so that option is not available. This is what I think happened, so try and remember exactly what you did as it is crucial if fixing this.

Did you.....
Dump nand
Possibly update the system?
RGH Install (CoolRunner)
Bad CoolRunner/Soldering
Flashed stock NAND back (without dumping the new updated NAND)?

This would allow the system to boot 1 ROL cycle but while loading 2nd ROL cycle would post E79 and or freeze. If this is what happened then the only thing to do that I can think of off the top of my head would be to RGH it, create ECC from 12625 nand, boot Xell, get CPU Key, dump kv from 12625 and inject into a donor nand.

If this is the case with a update, you need to figure out which one as if it was 14717+ the CB's are updated so that creates a whole new mess to deal with. This could be very time consuming.

Probably best if Martin C chimes in on this thread as he knows more about this type of thing than I do.

I agree with this sorta same thing i said but he went in deep lol but i would do as wnyconsoles said

 

[WNYConsoles]

Good point legit, how are you writing the original nand back?

Try nandpro using the command "nandpro usb: -w16 nanddump1.bin" (No quotes)

 

[dil_king]

NAND Looks fine. It's actually the first Slim nand, 12625 and LDV is 1. Unless OP ran a update there is no need to change the LDV value.

The nand is fine so it should work without an issue, E79 on a Slim is more than likely related to the nand, my first RGH was a Slim and I had some major E79 issues. You cannot create a retail image without CPU key so that option is not available. This is what I think happened, so try and remember exactly what you did as it is crucial if fixing this.

Did you.....
Dump nand
Possibly update the system?
RGH Install (CoolRunner)
Bad CoolRunner/Soldering
Flashed stock NAND back (without dumping the new updated NAND)?

This would allow the system to boot 1 ROL cycle but while loading 2nd ROL cycle would post E79 and or freeze. If this is what happened then the only thing to do that I can think of off the top of my head would be to RGH it, create ECC from 12625 nand, boot Xell, get CPU Key, dump kv from 12625 and inject into a donor nand.

If this is the case with a update, you need to figure out which one as if it was 14717+ the CB's are updated so that creates a whole new mess to deal with. This could be very time consuming.

Probably best if Martin C chimes in on this thread as he knows more about this type of thing than I do.

well first of all thank you for taking a look at my nand this is what I did

1. open slim did not even turn it on and Dumped nand 4 times

2. flashed ecc

3. programmed cool runner

4. install coolrunner and soldered it and it stopped working

5.remove all cool runner wires

6. flash back the original nand I got with Jrunner and then after I did it again with jtag tool

what tool did you use to determine the dash and the LDV?
and I flashed xbox with nandpro and still same thing.

Im guessing I should have dumped the nand again after I wrote the ecc ?

 

[legitmod]

well first of all thank you for taking a look at my nand this is what I did

1. open slim did not even turn it on and Dumped nand 4 times

2. flashed ecc

3. programmed cool runner

4. install coolrunner and soldered it and it stopped working

5.remove all cool runner wires

6. flash back the original nand I got with Jrunner and then after I did it again with jtag tool

what tool did you use to determine the dash and the LDV?
and I flashed xbox with nandpro and still same thing.

Im guessing I should have dumped the nand again after I wrote the ecc ?

no you did not want to dump your nand after flashing your ecc because its just the ecc file an its over written. look around for 360flashtool ill send you an pm. post some pics of the solider points of where your nand wires go

 

[dil_king]

here is the install pics I made sure the wires dont touch and im not the best at soldering

So I flashed my stock nand then turned on xbox and it froze turned it off and did a nand dump agian

and the compare reported the following


"2 non-matching block(s) found
37D
37E"


update 2

I got e71 error and dumped nand and got this


3 non-matching block(s) found
37F
380
3DE

 

[dil_king]

So the only way to fix is RGH it ?

 

[legitmod]

here is the install pics I made sure the wires dont touch and im not the best at soldering

So I flashed my stock nand then turned on xbox and it froze turned it off and did a nand dump agian

and the compare reported the following


"2 non-matching block(s) found
37D
37E"


update 2

I got e71 error and dumped nand and got this


3 non-matching block(s) found
37F
380
3DE

So the only way to fix is RGH it ?

the problem is your soildering on the nand points your wicks are long which could cause problems in touching bridging an other conflicting stuff so you might want to fix that

 

[dil_king]

ok here is the soldering on the wires to the nand and still same problem.

also where the red wire is the solder came off could that be the issue? the picture is below

Click Here

 

[dil_king]

so what would my ldv count be ?

 

[Martin C]

As per my sticky, count the number of FF's on lines 7 and 8.

I see 1.

Does your console freeze with the retail NAND flashed to it?

 

[dil_king]

As per my sticky, count the number of FF's on lines 7 and 8.

I see 1.

Does your console freeze with the retail NAND flashed to it?

yes it does even if it has retail nand flashed to it