- May 26, 2014
- 174
- 23
View attachment 32216I wrote my 16 mb retail nand to the new chip before I installed it to my mobo, just like recommended in the tutorial: http://team-xecuter.com/forums/show...-corona-V2-to-V1-(for-DemoN-use-or-for-repair).
Then I followed the tutorial. Once I completed installation of the new components, I read the newly installed nand twice. I got two matching nands and my cpu key automatically popped up in J Runner. I then turned on the console and it booted perfectly fine.
The problem started when I tried to write a hacked nand. Ever since I tried this, the Xbox beeps but won't turn on; no lights turn on even for a second. Now, when I try reading the nand back, I get "header is wrong" and J Runner crashes after the second read when the nand compare starts.
Antalpromille mentioned in the tutorial that if there was trouble writing to the new nand, some bad flash recovery method may be necessary. Now, I've already erased the nand with J Runner via Advanced>Custom NAND/CR Functions and used Demon/fusion write. This didn't make any difference. So my question is whether there is something else in J Runner, or any other program, that I could try. I've looked all over for a guide but I couldn't find anything that applies to my situation.
View attachment 32214View attachment 32215View attachment 32213View attachment 32212View attachment 32211
Then I followed the tutorial. Once I completed installation of the new components, I read the newly installed nand twice. I got two matching nands and my cpu key automatically popped up in J Runner. I then turned on the console and it booted perfectly fine.
The problem started when I tried to write a hacked nand. Ever since I tried this, the Xbox beeps but won't turn on; no lights turn on even for a second. Now, when I try reading the nand back, I get "header is wrong" and J Runner crashes after the second read when the nand compare starts.
Antalpromille mentioned in the tutorial that if there was trouble writing to the new nand, some bad flash recovery method may be necessary. Now, I've already erased the nand with J Runner via Advanced>Custom NAND/CR Functions and used Demon/fusion write. This didn't make any difference. So my question is whether there is something else in J Runner, or any other program, that I could try. I've looked all over for a guide but I couldn't find anything that applies to my situation.
View attachment 32214View attachment 32215View attachment 32213View attachment 32212View attachment 32211