Retail.  I know I need the coolrunner for a hacked dash.  If I build a retail image, can I not boot that?

Nothing is set in stone.  I just built another glitched image instead of retail.  I'll play around with it for awhile, set up a hard drive with some things I want.  Then revert to retail dash, uninstall the coolrunner, sell it, and run a dual NAND setup on the slim:)

Thanks again to everyone for the assistance.

The job is done.  I'm back to 13604, hacked 13604 no less.  Thanks MS for forcing me to glitch my Xbox by updating it without telling me, well done

For anyone who's interested or in the same situation, this problem was difficult for me to find a solution for and not well documented, so I'll post a mini-tutorial.  I found my answer here in post #15: http://www.team-xecuter.com/forums/showthread.php?t=74685&page=2.

In a nutshell, here's what you do:

-Flash good "old" NAND (YOU ALREADY DID THAT!)
-Perform RGH
-Count F's in fuse set 7 shown in Xell
-Insert value under cfldv line in options.ini within Multi Builder's "my360" directory.
-Recreate the image with MB and flash again.

Enjoy having a better machine than you did before you messed it up.

So I created a ggbuild image via multi builder .3, using the old dump, and get a black screen.  Do I need to be using an image with dashboard 13604?  Is there any way I can build a working image using this old dump, or do I need a donor?

Ok, seems I can't read instructions.  I was writing the ecc with -w instead of +w.  After writing with +w, it booted Xell in about 6 seconds.

Thanks again for all the help

CB is 6750, so from what I understand it is valid.  But system does not power up when creating ECC from the same dump.  It does power up before I flash the ECC however..  I don't see how I could be creating the image incorrectly, just load dump in multi builder .3, select mobo and it spits it out..  Is a proper .ecc all that needs to be on the nand in order to boot Xell?  It's japser 256 though, so I'm not sure if one for a 512 would work.

Thanks for the replies.  I bought a cool runner locally today, seller programmed it for my mobo.  Last night I flashed my "bad" dump just to see what would happen and got the same results, black screen.  Anyway, created my ecc from one of my "good" old dumps, flashed it, installed the cool runner in very clean manner, and the xbox will not power on although the coolrunner did have the red light on.  I'm hoping this is simply because I flashed the bad dump and/or the ecc created out of my old good dump.  We'll see when I wake up.


So a couple questions.  Will this old dump even work with the RGH?  All seemed well creating the ecc with 360 Multi builder.  Do I need latest dash that every tutorial says to update to followed by NAND dump?


If not, how do I go about building a correct image to flash with a donor?

Update: Powers up after writing first 64 MB of the "good" dump from old dash, will not power up after writing the .ecc file created from the same dump.  Again, dump is from debut of AP2.5 dash, around this same time last year.


Thanks again:)

I couldn't care less about signing into live.  Especially after this.  All this is because I signed onto XBL FREE.

I am using lpt which is the reason I didn't back up prior to flashing, simple impatience.  It would have taken over 24 hours and I guess I was subconsciously thinking the efuses was a one shot deal to stop jtags.

I don't mind glitching as I was planning on doing it anyway.  But I've reflashed twice, with two identical dumps and get nothing but black screen, no video initialization period.  Where I start with the RGH if I don't have a proper dump?

I didn't make the dump today.  Haven't even taken a dump today..

As stated, I made the backup in March.  Pretty sure it was the dash where AP2.5 was released.  I have updated a few times since, including the latest dash, got the DAE.bin update yesterday, a day after making XGD3 backups, wanted to remove the flag and play them again, so I wrote the NAND image I made in March, with the intention of updating back to the current dash and reflashing drive again so I would be where I was before the silent update.  Got black screen, 3 red lights.  I do not have a dump any later than the original ap2.5 dump I am working with.

In typical impatient fashion, knowing that I should have backed up current NAND, I went ahead and flashed an earlier dump I made after applying the original AP2.5 dash. Of course I was at the current dashboard prior to writing the flash considering I recieved the silent update. So now, upon booting I'm greeted with a black screen and RROD. This is a Jasper board.

I suppose some efuses have been tripped since I made the backup. Do I have any options? Donor NAND? Simulate/apply current dash update to my earlier NAND backup? All I want to do is regain the current dash version, I don't care if I'm flagged and I don't care if XGD3 backups don't boot. I'm reflashing right now with an alternate dump, I'm hoping it was a bad write (wishful thinking)..  At the very least, can I use this older nand to glitch the box?

Please help.