Hello all, I am having an interesting issue. I dumped my zephyr's NAND and attempted the RGH but forgot to update to 13604, so I reflashed my xbox with the original NAND and THEN updated to 13604. The thing is... I totally forgot to dump the NAND again after the update (Idiotic I know, believe me I'm still hitting myself on the head over that) and went ahead and flashed the NAND with the GGBuild Bin. Thing is Now, the motherboard won't recognize any NAND dump. I tried fabricating my own using both Bincrypt and 360 Multi Builder, but unfortunately nothing seems to work. I have tried different tutorials and still cannot get my motherboard to boot a NAND image. Fortunately I got it to run Xell using an image created with 360 multi builder. If anyone can perhaps guide me in the right direction to solving this problem I would be forever grateful. Thank you very much everyone for the great tutorials and help on this forums, you guys have saved me more than once.
Xbox 360 won't run original NAND.
- Thread starter ruishang
- Start date
Yes sir. I tried using a donor NAND using multi builder. I do have my CPU key thankfully, and xell boots without fault. Only when I flash a my NAND I get the black screen and blinking green light.
if it boots xell now then everything is correct with wiring so let me ask u this have u tried anything else but ggbuild and multi
I tried injecting my kv and cpu key to a donor nand using Bincrypt and it didn't work. I was thinking about trying flash360 but I'm yet to figure it out.
---------- Post added at 21:53 ---------- Previous post was at 21:52 ----------
I was wondering if perhaps updating the dashboard made the old NAND dump incompatible because of the fuses the update burns.
---------- Post added at 21:53 ---------- Previous post was at 21:52 ----------
I was wondering if perhaps updating the dashboard made the old NAND dump incompatible because of the fuses the update burns.
Use the image u use to boot xell, and the cmd line of ggbuild to make a correct image, gui's arnt always your friend
daretogo
VIP Member
What about taking something like this guide http://digiex.net/guides-reviews/console-guides/xbox-360-guides/9574-easily-update-your-jtagged-xbox-360-kernel-dashboard-13604-fbbuild-0-33-a.html and using it to update your original nand to 13604 and then flashing that back to the Xbox?
I tried it. Unfortunately it wont work. I did manage to update the NAND dump to dashboard to 13604. But every time I flash my console with it, I get the green blinking light and black screen. Here are some screen captures from flash tool of both the retail NAND updated to 13604 with fbbuild, and the gg image using the fbbuild updated NAND.
Last edited:
So, can anybody guess what could be wrong? hell I even tried making my own clean NAND and NOTHING. I have injected my KV into a donor times so many times it has become almost automatic in nature. The thing that bothers me is that Xell Reloaded boots up like a charm in 5 seconds or less, but no matter what NAND I write it always gives me the blinking green light, black screen and three red lights. It can't be RROD if xell boots and stays on for minutes. I compared my original NAND and it has no bad blocks. The big mistake I made on this one is that I updated the xbox to dash 13604 and didn't dump the updated NAND, then flashed the glitched NAND, premade with the older original NAND. I don't know if it was the burned E-Fuse that screwed me on this one, but no matter how many donors and kv's I flash, wether glitched or nonglitched, I always get blinking green light and 3 red lights. This think keeps clawing at the back of my brain, and any professional help from you guys would be EXTREMELY appreciated. I'm willing to transfer my original nand dumps if closer inspection is required.
-Also, I don't know if having a donor nanddump with dash 13604 will help this issue, but if anyone is willing to donate I would really see how I could return the favor, thanks everyone!
-Also, I don't know if having a donor nanddump with dash 13604 will help this issue, but if anyone is willing to donate I would really see how I could return the favor, thanks everyone!
BWAHAHAHAHA I FIXED IT ON MY OWN!!!!!!!!! Anyways... As I almost completely gave up on this and was about to consider smashing this motherboard with a hammer, I read somewhere that Xell gives you the most accurate reading on your fuseset. So I launched Xell and noted down my fusesets. Counting the number of F's on row 7 gave me a reading of 14 (ldv=14). Which turns out to be higher than 12 as 360 flash tool was showing from my original dump. So I entered 14 on the ldv value in the options.ini for ggbuild and made a glitched image with the original outdated nanddump and.... BOO YAH! booted into glitched kernel =D. So to put it short, the answer layed in front of my very eyes the whole time and it just took me one and a half weeks to figure out... So for anyone having trouble with an outdated dash on your original nanddump because you forgot to dump your nand after updating to dash 13604, just create a Xell image with 360 multi builder, do not include your cpukey.txt on mydata folder and it will create an ecc image that will definitely boot with your console. then add the ammount of f's on your fuseset 7 on Xell, and put the total ammount as your cfldv number on ggbuild's or 360 multi builder's options.ini. That should work without flaw on creating a fully working glitched image. It might be a simple couple of steps, but nowhere did i really find an answer to this problem. I hope this helps some of you folks and thanks to everyone for the help!
Last edited:
Thanks a bunch. I did the same thing today, and beat myself up for it haha. Never would have thought 360flashtool would give the wrong ldv value