JTAG Help! I think I killed my JTAG's KV/NAND?

[hot_wired13]

Hey guys,

I apologize for my terminology if its wrong, I'm a real noob to this.

I bought a JTAG Falcon and it was working fine. Seller gave me 2 copies of a 16MB nand.bin, and a 16MB Sam_CFW.bin inside a CD.

My dash was 2.0.12611.0.

My friend told me the very first thing I needed to do was to update to dash_launcher_2.21, so I downloaded the zip, put it into a usb drive, and ran the installer. Readme file said it works fine with 12611, so i thought, yea.

Went through the defaults and they asked if i wanted to patch some stuff - looked safe so i went ahead with it.

Poof. My xbox360 started showing the Keyvault error. I googled and tried going into xellous - and it said: kv_get_dvd_key Failure: kv_read

After removing the power cable physically and putting it back, it started showing E52 error. I read some more and saw many people saying they fixed it by flashing their original nand file, so i went ahead and renamed the nand.bin the seller provided to updflash.bin and put it on a USB and let xellous flash it.

Boom. I think it got things even worst. Now I got 3 RROD and I can't even go to xellous anymore.

Anyone? Please help me? I don't want to be stuck with a giant paper weight!

 

[Martin C]

Use the JTAG Tool and flash Xellous to your console. Remember to choose the Falcon board.

Do you know what wiring was used to JTAG? i.e TRAY_OPEN, AUD_CLAMP etc? If so, you need to specify custom options.

once you've got XeLL working, note the CPU key and try to open the supplied images with 360 Flash Tool. This will make sure you've been supplied the right files.

 

[hot_wired13]

Use the JTAG Tool and flash Xellous to your console. Remember to choose the Falcon board.

Ok, so to use this tool, I will need NAND-X or the LPT port thingy, right?

Do you know what wiring was used to JTAG? i.e TRAY_OPEN, AUD_CLAMP etc? If so, you need to specify custom options.

Nope. But will it help if i disassemble the set and take pictures of it?

once you've got XeLL working, note the CPU key and try to open the supplied images with 360 Flash Tool. This will make sure you've been supplied the right files.

I happened to snap a photo from xellous of the CPU key *after* i installed attempted the dash_install_2.21. Tried opening the nand.bin file with 360_Flash_Tool_v0.97 and i entered the CPU key as the one i got, it said "Failed to open file"

Edit: Ok, my bad, the nand.bin was in a path which had non-english characters, hence the error. Moved it to c:\ and it showed this:

So what's the deal here?

 

[seanr28]

you either did'nt save the cpukey in 360 flash tool, else you typed it in wrong, otherwise you would not be seeing BAD KEY/KV

 

[hot_wired13]

you either did'nt save the cpukey in 360 flash tool, else you typed it in wrong, otherwise you would not be seeing BAD KEY/KV

I actually copied and pasted the key from XeLLous before my second time flashing (the updflash.bin part) - so it can't really be possible that I typed it wrong.

The nand.bin I was testing on was also the one supplied by the seller - I have no physical tools to dump/read/write stuff.

Something about this just don't add up:
- Why would updating dash_launcher_2.21 (or rather, having it patch stuff) put the christmas lights (2 red 2 green) on?
- Why is it that when I flashed my original seller-supplied nand.bin file back via xellous, the set ruses to boot? (3 rrod)

 

[Fisticuffs]

you either did'nt save the cpukey in 360 flash tool, else you typed it in wrong, otherwise you would not be seeing BAD KEY/KV

With 360 Flash tool click settings and add your Cpu key then open the orig nand and see what is says and click the little box next to cpu key

 

[hot_wired13]

With 360 Flash tool click settings and add your Cpu key then open the orig nand and see what is says and click the little box next to cpu key

Says Bad Key/KV. Note that the seller didn't provide me the cpu key - i only managed to capture the cpu key after the time the kv_error occurred..

 

[Fisticuffs]

Ask the seller to send you the orig nand.bin and kv.bin, And you could try to add what it says for the cpu key in the settings tab/Keys with the little box ticked For cpu key and delete what is states as xex 1 and 2, Then open your nand.bin in the main window and see what it still says

 

[manwithoutname]

That's assuming the nand.bin he sent you is the right one for your console and not another one.

 

[Fisticuffs]

I actually copied and pasted the key from XeLLous before my second time flashing (the updflash.bin part) - so it can't really be possible that I typed it wrong.

The nand.bin I was testing on was also the one supplied by the seller - I have no physical tools to dump/read/write stuff.

Something about this just don't add up:
- Why would updating dash_launcher_2.21 (or rather, having it patch stuff) put the christmas lights (2 red 2 green) on?
- Why is it that when I flashed my original seller-supplied nand.bin file back via xellous, the set ruses to boot? (3 rrod)

Says Bad Key/KV. Note that the seller didn't provide me the cpu key - i only managed to capture the cpu key after the time the kv_error occurred..

I copied and pasted the key from XeLLous before my second time flashing??,

 

[hot_wired13]

I copied and pasted the key from XeLLous before my second time flashing??,

I would assume that the "first time flashing" is when that dash_launcher_2.21 patched/flashed something? Hence screwing stuff up?

"second time flashing" = when i put the seller-provided nand.bin into a USB and flashed from xellous.

..or am i mistaken?

 

[manwithoutname]

You shouldn't have even considered flashing the nand.bin as this in normal cases will restore the console to normal. The nand.bin should be only used to re-flash the console as a last resort when everything else has failed or re-create freeboot images.

What should have happened is that the seller should have supplied you a copy of the freeboot image which you should have flashed the console with after installing dash launch has caused the problems.

 

[hot_wired13]

You shouldn't have even considered flashing the nand.bin as this in normal cases will restore the console to normal. The nand.bin should be only used to re-flash the console as a last resort when everything else has failed or re-create freeboot images.

What should have happened is that the seller should have supplied you a copy of the freeboot image which you should have flashed the console with after installing dash launch has caused the problems.

Seller just finally came online and sent me a freeboot-image updflash.bin, compared it against the original one i flashed over, and well... its different!

Yes, I guess so. I just opened the set, and I don't see any leftover wires and stuff from the top of it. So... what do I do now?

Do I buy a NAND-x and flash again?

 

[manwithoutname]

Obviously yeah, as you now don't have xell/xellous on there anymore to use to flash the updflash.bin image.

You will need to physically connect the NAND-X to your console and flash the freeboot image back to it again.

 

[hot_wired13]

Ok so here's the set - I don't see any leftover wires and all - so I suppose the seller removed the extra wires used while flashing?



..and here's the screen after i tried to update dash_launch_2.21. KV error but still displaying key!


What now?

 

[manwithoutname]

This is bit confusing .. What do you get now if you boot the console with the eject button and leave the tray out?

 

[hot_wired13]

This is bit confusing .. What do you get now if you boot the console with the eject button and leave the tray out?

Now, I get no video output (via normal AV cables), and the 3 RROD...

 

[manwithoutname]

Then like stated previously, buy a NAND-X and solder the QSB's or wires directly to the motherboard in order to flash your freeboot image.

You can of course make your own LPT cable if you do have an LPT port on your computer but be prepared to wait for like 2 hours to write to the NAND.

 

[hot_wired13]

Hey guys,

Okay, I got a NAND-X and flashed the seller-provided updflash.bin and my console is alive again.

However, I'm unable to read any backups - homebrew works fine though.

Looking at XeLLous, it looks like I still get:
kv_get_dvd_key Failure: kv_read

What's the deal this time? Could it be that the seller has prepared the wrong keyvault?

 

[Teajunkie]

Then you could change the key in Jtag tool and the drive type.