Help rebuilding corrupt Nand (if possible)

[Disperat]

Hello. I will try to keep it short, keeping important facts, as I presume wall blocks bore people.

TX Product(s) used: TX Nand-X, CoolRunner Rev B
Console Type: Jasper
NAND size: 16GB

Description of problem:

Jasper 16MB Xbox. The original dashboard of the console was 2.0.14699, so it was glitched with success using RGH (1).

Last week, the console was returned to stock dashboard, then updated using Xbox Live to 2.0.16547 (1 update).

Following the update, the nand was written with the dump from 2.0.14699 dashboard (no backup first).

Obviously, not the Xbox dosen't run anymore. The console gives 0022 after 30 seconds.

What I have:

- original dump of retail when it was 14699
- CPU Key

I've tried to make a new nand without nand following Martin's instruction from here, increased LDV with one (from 8 to 9), but I am not really sure if it applies in my case.

My question is that if I can do something about it or dump the motherboard in the history's recycle bin.

Thank you.

 

[xzanox]

Fill out the complete template please with pictures and logs.

And give a little more info about who put back the original NAND and why? You do know that your Xbox can't be written and wired for rgh1 anymore since you've updated it via Xbox live.

If I do understand it correct, you didn't do a new NAND read after the update correct?

You could have updated your dashboard thru jrunner update function if you just wanted to update the dash and still could have had the nice instaboots of rgh1, but I guess that is to late now...

 

[Disperat]

Thanks for the reply, mate.

Pictures I don't think are needed, as it is a software problem, and not a hardware one, especially that I want to build a retail nand. I can post them, of course, altough I don't see any help you will get from them.

To clarify more, even if it is irrelevant now: my friend wanted to return to RGH after some Live (bored after a few days) and tought that is a good ideea to write the RGH nand back. I know how the update should have been done (through J-Runner / update then RGH2 it etc), by my friend didn't know so he thought that he can return to RGH by writing the old nand back.

If I would have a nand dump with the latest official dash updated, things would be simple and I woudn't post here. Now I try to focus on the problem at hand, not on how things should be done before the problem.

Thank you again for your reply.

 

[PetrozPL]

You've updated to 2.0.16547 (above 2.0.14699) so burned your e-fuses, and RGH1 is blocked. You need RGH2 now.

EDIT : Try to build clean retail image with kv from old nand. Then from it generate RGH2 image. It should do the trick.

 

[Disperat]

Thanks for the answer, but I think I didn't made myself clear in my original post.

Additional information:

- I haven't said I want reverse to RGH1. Funny ideea, as I am trying to make it work with retail nand actually.

- I have tried, PetrozPL, what you already stated: trying to build in J-Runner a 16547 retail image based on 14699 nand and increasing LDV with one, but it still gives 0022 after 30 seconds.

I tried also to build using kv, smc and smc config from the orignal 14699 nand, like in the tutorial offered by Martin in the link in the first post (thank you Martin, for it, by the way).

 

[PetrozPL]

write rgh2 image and run xell - check LDV value on e-fuses

 

[gavin_darkglide]

This is an easy fix. Load up the original 14699 dump and use it to create a retail 16747 nand image. After 15572 the cb has changed to 6754, so you can build any dash that uses that cb, might as well be the latest. If you have only done 1 update up the ldv value by 1. Flash nand to console and enjoy. You might want to remove the coolrunner, as it will no longer work with the RGH1 wiring. Enjoy your stock console. If you want RGH back, you will need to remove the A(CPU_PLL_BYPASS) Wire, and Hook up E and F wires, and change some settings(Remove resistors/Bridge some points) on coolrunner, and also reflash coolrunner with a new timing file and build a RGH2 image. If you want almost instant boots get R-Jtag, or the new CR4-XL that is to be released any day now.

 

[xzanox]

Thanks for the reply, mate.

Pictures I don't think are needed, as it is a software problem, and not a hardware one, especially that I want to build a retail nand. I can post them, of course, altough I don't see any help you will get from them.

To clarify more, even if it is irrelevant now: my friend wanted to return to RGH after some Live (bored after a few days) and tought that is a good ideea to write the RGH nand back. I know how the update should have been done (through J-Runner / update then RGH2 it etc), by my friend didn't know so he thought that he can return to RGH by writing the old nand back.

If I would have a nand dump with the latest official dash updated, things would be simple and I woudn't post here. Now I try to focus on the problem at hand, not on how things should be done before the problem.

Thank you again for your reply.

Pictures could help to see how you've wired your coolrunner at the moment (besides when asking for help is necessary to post pictures etc per the template, also to see if we are talking about original coolrunner and so on) and your jrunner logs could enlighten a lot on how about your actions got you where you're at the moment. You could post your efuses and everything needed to help you.

If you don't want that, then it's up to you.

 

[gavin_darkglide]

Pictures could help to see how you've wired your coolrunner at the moment (besides when asking for help is necessary to post pictures etc per the template, also to see if we are talking about original coolrunner and so on) and your jrunner logs could enlighten a lot on how about your actions got you where you're at the moment. You could post your efuses and everything needed to help you.

If you don't want that, then it's up to you.

For what the op is trying to do, all the required information has been given. 1 update means plus 1 on the ldv, and dash 16547 on jasper means cb 6754. With this information and 14699 nand image/CPU_Key it is an easy fix. The coolrunner images arent needed, as this is going to be a stock console, and the issue is more of a not understanding how the security works on the xbox to prevent downgrades.

to the op

As I said in my last post... Make latest retail dash 16747 from your 14699 image with j-runner, with the ldv + 1. flash image and enjoy. If you want RGH in the future, you will need to change coolrunner wiring, if not remove coolrunner. it is as simple as that. If you are afraid to solder in the console, switch the switch on the coolrunner to prg and call it a day.

Also read this, it might help with understanding what the issue is here. http://team-xecuter.com/forums/showthread.php?t=77634

 

[Disperat]

OK. I remembered that I read somewhere in one of Martin posts or guide that 30 seconds 0022 is LDV problem, and after reading PetrozPL's post about checking LDV and I knew what I should do next.

I basically did out gavin_darkglide method about hour ago, but didn't have Internet connection to return with results. It appears that it was indeed a LDV problem, as the original had LDV 8 and booting Xell gave me an LDV of 11. Of course after changing accordingly the LDV, the console booted up on retail, and by now it is already RGH-ed (2) and closed up.

Thank you all, guys (xzanox, gavin_darkglide and PetrozPL). Doubt I could by myself answer to this problem in such quick and effective time.

Thank you again!

 

[PetrozPL]

Great you've managed to get it up and working again!

 

[xzanox]

For what the op is trying to do, all the required information has been given. 1 update means plus 1 on the ldv, and dash 16547 on jasper means cb 6754. With this information and 14699 nand image/CPU_Key it is an easy fix. The coolrunner images arent needed, as this is going to be a stock console, and the issue is more of a not understanding how the security works on the xbox to prevent downgrades.

I first understood he wanted to keep it rgh...\


good thing there are more observative members (gavin ) and nice you've found a solution OP.

 

[nofeloniesyet]

we also require pictures of products to make sure thier using xecuter products,so we arent helping with others crap products here.

 

[gavin_darkglide]

I first understood he wanted to keep it rgh...\


good thing there are more observative members (gavin ) and nice you've found a solution OP.

I didnt get the impression that the op wanted to keep it RGH from what I was reading, so u must have seen something I missed.

we also require pictures of products to make sure thier using xecuter products,so we arent helping with others crap products here.

While I dont disagree, what I was reading said the op wanted help with creating a new stock nand, which has more to do with console repair, and less to do with glitch hardware. If it were a case of the console not glitching, I would have requested pictures as well.

To the OP: Congrats on fixing your console. Lets try not to forget to make a backups when u update to the latest dash.