- Dec 2, 2011
- 27
- 0
So i did over 20 RGH/CR installs lately and all went without a hickup. However my latest was kind of a shocker..
1. check if 14699 is installed.
2. update console via usb to 14699
3. format hdd via serialnumber
4. create new test avatar.
5. read my NAND with NANDX by wires (no QSB for me). Dumped it twice using nandhealer. Got matching dumps.
6. create ecc using multibuilder.
7. flashed image_00000000.ecc back to nand using nandpro usb: +w16
8. flashed coolrunner with trinity timings
9. soldered coolrunner to mobo
10. boot into xell.
11. got cpukey
12. build nandflash.bin (or something like that) and put it on usb stick.
13. shutdown xbox
14. power on xbox with usb stick inserted.
WTF? E 79? Switched to phat modus. Again, whatever i tried it kept giving me error 79.
Why does this happen?
15. damnit
16. start reading the forums
17. get original nand from working directory
18. flash it back to nand using nandpro usb: -w16 nand1.bin (It was reccommended to not use +w16 (someone can explain that to me? why is this not recommended) Why flash ecc with +w16 and originalnand with -16?
19. phew it boots.
20. let it rest for a day.
21. GET NEW NANDDUMPS.
22. have questoinmarks above your head because the New dumps are different from the original dumps
23. read up again on forums and notice that the nand changes between powercycles so they offcourse do not match.
24. sigh of relieve
24. create new ecc image
25. flash that one with nandpro
26. boot into xell
27. check cpukey
28. build nandflash image
29. put on usb key
30. flash it via hadrwareflasher/xenon.elf
Yeah baby. No more error 79.
Still dont know what happened.
Tip for everyone, keep your calms. Read read read and understand. (u myself still dont understand lockdown values, the use of fuses etc...)
1. check if 14699 is installed.
2. update console via usb to 14699
3. format hdd via serialnumber
4. create new test avatar.
5. read my NAND with NANDX by wires (no QSB for me). Dumped it twice using nandhealer. Got matching dumps.
6. create ecc using multibuilder.
7. flashed image_00000000.ecc back to nand using nandpro usb: +w16
8. flashed coolrunner with trinity timings
9. soldered coolrunner to mobo
10. boot into xell.
11. got cpukey
12. build nandflash.bin (or something like that) and put it on usb stick.
13. shutdown xbox
14. power on xbox with usb stick inserted.
WTF? E 79? Switched to phat modus. Again, whatever i tried it kept giving me error 79.
Why does this happen?
15. damnit
16. start reading the forums
17. get original nand from working directory
18. flash it back to nand using nandpro usb: -w16 nand1.bin (It was reccommended to not use +w16 (someone can explain that to me? why is this not recommended) Why flash ecc with +w16 and originalnand with -16?
19. phew it boots.
20. let it rest for a day.
21. GET NEW NANDDUMPS.
22. have questoinmarks above your head because the New dumps are different from the original dumps
23. read up again on forums and notice that the nand changes between powercycles so they offcourse do not match.
24. sigh of relieve
24. create new ecc image
25. flash that one with nandpro
26. boot into xell
27. check cpukey
28. build nandflash image
29. put on usb key
30. flash it via hadrwareflasher/xenon.elf
Yeah baby. No more error 79.
Still dont know what happened.
Tip for everyone, keep your calms. Read read read and understand. (u myself still dont understand lockdown values, the use of fuses etc...)
