If you try:

nandpro.exe lpt: -e16 0x000000

What happens ?

Also i found that EPP and SPP settings worked on my computer, however had occasional errors. ECP works flawlessly

You will need:

- your original corrupt nand (nand.bin)
- your CPU key (you can get this by loading Xell xenon_hacked.bin on your 360)
- Degraded v1.1 (Degraded_v1.1.rar) *
- 1888 File System (1888.FS.rar) *
- 360 Flash Tool v0.88b *

* tool is available from "the usual places"


Firstly we will build a new nand image.

- Open Degraded 1.1
- Click "..."
- Find your corrupt nand.bin file
- Click Open
- Click Settings
- For the 1BL Key enter: DD88AD0C9ED669E7B56794FB68563EFA
- Tick the Valid box next to the entry
- Enter your CPU key
- Tick the valid box next to the entry
- In the 1888 File System section click "..."
- Specify where your extracted 1888 File System is and click OK
- Set File System Start to 39
- Click OK
- Click Build v1888 image
- Specify a save name: temporary.bin and click Save
- Close Degraded

- Open 360 Flash Tool
- Click "..."
- Find your corrupt nand.bin file
- Take note of the following values:
   - Pairing
   - CB LDV
   - CD LDV
   - CE LDV
- Close 360 Flash Tool

- Determine your maximum LDV value. From the previous step you noted three LDV values. For example they could be: 0, 1, 2. Therefore your maximum LDV value is 2. If your values are 0, 7, 3. Your maximum LDV value is 7.

Now patch your new image with the right Pairing and LDV values

- Open 360 Flash Tool
- Click "..."
- Find your temporary.bin file
- Make sure your Pairing value is correct to what you noted in the previous step
- Now for the important step. You will notice your CD and CE LDV values are greyed out, this is because you're downgrading to a base dashboard therefore there aren't any patches applicable and no Lockdown Values (LDV's) applicable.
- Now click Patch
- Put a tick in the Patch Headers checkbox
- In the LDV text box for CB type in your maximum LDV value
- In the Pairing data text box for CB type in your Pairing Data value.
(Both these values are crucial. If you dont get them right, your xbox will turn on, but you'll get no image and a RRoD after 20 seconds)
- Click OK
- 360 Flash Tool will now automatically ask you to save
- Provide a name for your new nand image: e.g. myclean1888.bin

- Make sure your Key Vault values are correct. If they're not and you have your valid kv.bin file you can inject it now using the Patch button. To do this:
- Click Patch
- Check the Patch KeyVault checkbox
- Put a tick in the Patch KeyVault checkbox
- Select Import KV and click "..."
- Find your KV.bin file and click Open
- click OK
- Provide a name for your new nand image: e.g. myclean1888.bin (you can overwrite your previously saved file at this point in time)

Change the Region of your console (THIS IS OPTIONAL):

You can change the region of your console from PAL->NTSC or vice versa. To do this:
 - Click Patch
- Check the Patch KeyVault checkbox
- Select the Patch KV option
- Change the Region from the drop down box to the desired region.
- Click OK
- Provide a name for your new nand image: e.g. myclean1888.bin (you can overwrite your previously saved file at this point in time)

You can now flash the image to your xbox.
I would suggest running the following command before hand, it will erase your entire nand of any possible garbage.

nandpro.exe lpt: -e16 0x000000

(Thanks to Gee99x for this command)

then flash your xbox with:

nandpro.exe lpt: -w16 myclean1888.bin

Gents I did it !!!!! Its working. The missing component was LVD values !!!

I'll write it up tomorrow, now its bed time, gotta go to work tomorrow and its 4:50 am :/

I do have the CPU key from my original dump.

Ok i've been doing a bit of reading and i think that my pairing data is corrupt.

One of the best pieces of evidence of this is that the xbox turns on, and then about 20 seconds later it goes to RRoD (which is what is described in the infectus manual as the state the xbox needs to be in to begin pairing)

So i think the reason its not working when i try a 1888 dump is because my pairing key has been incremented.

The dump that got corrupt is:

CB: 1903   Pairing: 0xA202CF
CD: 1888   Patch 0: 4552
CE: 1888   Patch 1: 4548

Whilst the 1888 image i was trying to patch was:

CB: 1888   Pairing: 0x9E8CE4
CD: 1888   Patch 0: 7371
CE: 1888   Patch 1: 7363

If anyone out there has a nand image with patch 0: 4552 and patch 1: 4548,  would you please pm me a link to it ?
I think this is what is stopping me from getting my console to boot.
My understanding is that i must use my pairing code as its tied to my CPU. And my pairing code is limited to a certain CB and Patch level. So therefore any attempts to patch an older image are futile as the pairing code won't calculate.

Is there any way of getting other than running IDGtool and and infectus chip ? Is there a tool that works with the parallel cable ?

Hitec,

I'm experiencing the total opposite. I can get xenon_hacked.bin working but not my original nand.bin file.  One difference I'll point out is that i don't have not removed the  R6T3. Maybe this is a key component ? Hmmm maybe i should go to bed (its 3:16 am here in Australia)

I've injected my kv into the 1888 dump. I used an older version of Flash Tool for this. Version 0.88 won't allow me to do it, but 0.81 did

However it didnt work

I have access to a friend's dump. It is 1888. How do i inject my KV into it ?

FlashTool won't let me do it, neither will the Degrader tool

Solution to the problem: http://www.xboxhacker.net/index.php?topic=12265.msg81244#msg81244

Hi everyone,

I thought I'd start a new thread as i've been writing a lot in the "method for extracting dvd key" thread, however, this is no longer applicable and got that post off topic.

So, here's a breakdown of what I've managed to do and what I cant seem to do.

I dumped my nand flash image (lets call it nand_orig.bin)
I then flashed my nand with xenon_hacked.bin
I got my CPU key, 1BL key
I then flashed my nand_orig.bin file back to my nand, and I've got no video output and after about 30 seconds i get a RRoD.

The backed up nand_orig.bin seems fine as FlashTool displays a DVD Key, my serial number and region correctly.

I've tried creating a downgraded 1888 image using my nand_orig.bin file as the basis, however when i flash it to my 360, i get the same exact error. BLack screen, no picture, and you know how the 4 lights on the console usually light up 1 after the other, this doesn't happen

I can flash my console with xenon_hacked.bin anytime and it works just fine.

Any ideas on how i can get my console back to a usable dash ?

Hi guys,

I used NAND Checker 1.1 on my nand and got 0 bad pages, however when i flash my xbox with the nand i get no picture. The console starts up, but no video. Also i got no read errors when dumping the nand, neither did i get any errors writing it. Any ideas why it doesnt work ?

xenon_hacked.bin works perfectly btw

Hey tmbinc,

The emulator runs i've just tested it with SUper Mario All-Start ...... but i can t play it coz i dont have wired controllers ?

Maybe some keyboard support ?

Sorry it wont. It will break the signature on the hddss.bin file and the xbox won't detect the hdd at all.

B1N4RY ... that's what I'm going to try and do, if you guys wanna muck around I'm willing to test a complied nand on my xbox ?

Ok, so i  buggered up my nand dump. It dumped wrong Anyone care to help me make a new one ?

I think my nand image i dumped is corrupt

Although i did retrieve the dvd-key from it. Although i'm not sure its correct ? How can i check ? It seems that when i flash my original nand back to the 360 i cant get it to display anything

Any chance someone can hook me up with their original confirmed working nand ?

Also another question i have ... is it necessary to desolder the 330 ohm resistors when you want to flash the original nand back ?

Well I have managed to flash mine with the xenon_hacked.bin again and its loading.

I'm not too really sure what i did to fix the problem to be honest. I tried plugging the 360 into my t43 laptop with a built in parallel port and that kept coming up with the incorrect config value 1200000 ... something or other. And then i tried my other desktop computer and it seemed to have the same exact problem. The config value wouldn't budge from 120000 ... I checked all different port settings: SPP, EPP, ECP, EPP+ECP and different IRQ/DMA combinations and nothing. So i got pi$$ed off and just said flash with 120000 setting. And then i got write errors. So i pressed CTRL+break after the first error message and then replugged the console into my previously working desktop. I then turned on the xbox360 and it started up, but the fans wouldnt turn and i couldnt turn the xbox off, i had to unplug the power supply (my guess, corrupt nand) and then ... i flashed it with my previously working desktop and what do you know ? It works.

Im not sure how a nand works, but it seems corrupting the first block worked like a charm and was what i needed to get this baby back up and running. Seems like a very flakey solution though. Im keen at looking at a USB solution, because knowing my luck, when a software solution comes out from the free60 group, ill play around with it, budge something up and need a hardware method of flashing the nand

Anyone tried the USB solution with the Olmix controller ?

http://www.olimex.com/dev/lpc-h2148.html

Sorry i should explain. After i got the RRoD i took the damn thing apart and performed the x-clamp fix. Cooked the gpu a little and now i dont get RRoD.

I just started the flashing process again. I pulled out the power plug, put it back in and now am trying to flash it with xenon_hacked.bin. If this doesnt working, im gonna flash it with my laptop (IBM T43) it has a built in parallel port

Also, does it matter when i connect up the 360 to the pc ?

Should the pc be off before connecting the cable ? Or should i plug the parallel cable in and then plug the xbox into power and then power up the pc ? Does it matter ?

Ok, so i managed to get rid of the RRoD issue. I think it was a legit RRoD issue. I have still no picture Both on VGA and Component
Furthermore i resoldered the connectors to the motherboard and got some new 330 ohm resistors and flashed the motherboard with 378 and EPP LTP port settings. Im going to read back from the nand and compare the files now.

Last time, when i compared the files, what happened was there were 2 offsets that the flashes differed, however this was on 378 and ECP settings. Hmmmmmm.... any further ideas on how to get this going ?

Im using a vga monitor and im using the nand available from xbins

Ok i managed to get it talking to the pc again, however, when i flash it with the xenon_hacked.bin or my original nand.bin i made an image of, the xbox doesnt show any output to the screen. It just sits there, the dvd drive is disconnected, so the middle light is flashing green, however i dont get the "initiation" green lights and then it sits there for a while and after about 20 seconds, the RRoD comes on :/ hmmmmmmm