JTAG Problem when creating freeboot.bin

[Hiryuu]

Hey everyone,

So I installed NAND-X JTAG the other day, dumped nands no problems, created FB and booted up fine etc. No issues. Then I replaced the HDD in my 360, and redid jtag tool process, again no issues w/ nand, xell installed fine but when I go to create FB, I get this message. I cannot seem to find any good info about what to do! Here is a screenshot:

 

[hodgie]

why did you redo your freeboot after a hdd install? just curious

 

[Hiryuu]

Right, In hindsight I feel that was pretty foolish. I was coming from the mindset that a total reinstall would just be an OK thing to do. I had installed FSD and had it configured to boot at startup on the old HDD so I just wanted to start fresh again.

 

[ianflann]

make sure your putting the right cpu key in

 

[Martin C]

open your original NAND with 360 Flash Dump Tool and ensure your CPU key can decrypt it.

Then once this is a certainty, use these details to make your freeboot image.

If you've not even attempted to write back to the NAND, you don't need to to worry about it.

 

[Hiryuu]

Ok, I will try that. I did try to write back to NAND.. So I also just checked my nand dump against the CPU key that I have triple checked and written out on paper and it is now saying 'wrong key' in all boxes in the KV info pane....

 

[marshamods]

I had this happen once when I mistakenly put a wrong digit as the cpu key. Check that your cpu key is correct. Remember their are no o's for cpu key, they are zeros. One of my buddies did that.

 

[Hiryuu]

Well guys thanks for all the input so far. I feel like quite a fool I have check over my CP key repeatedly, no issues there. But when I ran the nand in 360 flash dump tool I see 'Bad Key/KV!!! I have a screenshots of the xell cpu key screen and I have written it out. I am sure that my key is typed in correctly at this point. Im quite the noob here with the flash dump tool, so I can't quite see what my next step is....

 

[Martin C]

Well guys thanks for all the input so far. I feel like quite a fool I have check over my CP key repeatedly, no issues there. But when I ran the nand in 360 flash dump tool I see 'Bad Key/KV!!! I have a screenshots of the xell cpu key screen and I have written it out. I am sure that my key is typed in correctly at this point. Im quite the noob here with the flash dump tool, so I can't quite see what my next step is....

Do you have a copy of the NAND when you first did this and if not, did you dump a working NAND before you started?

Make 100% sure you have the CPU key - connect the console to your home network and boot into Xellous. Go to the http link at the bottom of the xellous screen and copy/paste the CPU key.

If you don't have a good NAND before you started, you'll need a decrpyted kv and config to build a new one.

 

[Hiryuu]

Do you have a copy of the NAND when you first did this and if not, did you dump a working NAND before you started?

Make 100% sure you have the CPU key - connect the console to your home network and boot into Xellous. Go to the http link at the bottom of the xellous screen and copy/paste the CPU key.

If you don't have a good NAND before you started, you'll need a decrypted kv and config to build a new one.

OK, now the CPU key that I have seems to always have a bad key/KV is that the one I will use anyways? Working NAND meaning one that is 100%? I don't have the original pre jtag nand...just the dumps i've made since this all started...

How do I go about procuring or making decrpyted kv and config to build a new one?

 

[beastyX]

Hey everyone,

So I installed NAND-X JTAG the other day, dumped nands no problems, created FB and booted up fine etc. No issues. Then I replaced the HDD in my 360, and redid jtag tool process, again no issues w/ nand, xell installed fine but when I go to create FB, I get this message. I cannot seem to find any good info about what to do! Here is a screenshot:

This sometimes happens when i update a console for someone that doesn't have the original NAND dump, only a dump that i'm forced to create using flash360.

Of course i'm not saying this is definitely what it is in your case but i always see the error in Jtag tool and the KV error on flash360 but it always works just fine after the flash.

 

[Hiryuu]

Alright here is the latest, I redumped the nand, multiple times, no errors, compares with 0 errors as well. When I go to install xellous, this started happening, I might add it DID NOT happen previous to this afternoon's efforts! So I still go ahead and I connected to the network w/ Xellous boot, and I see this info, my CPU key (same as always) BUT DVD key is '0000000000000000'??? WTF?
Also get this message when booting xellous. Ive included 3 screens of all this as well. I also went ahead and downloaded my 'flashdmp.bin' and 'config_raw.bin' However it would only give me a 505 error when trying to DL the KV encrypted or decrypted!! What now?? Thanks for all your patience and help so far btw!

I apologize for the quality of that last one...no capture card for my PC!

 

[hodgie]

i have never actually been connected to the interwebz when doing this, so i haven't been to thier website to download everything, but i have gotten your message in the last pic. after writing, everything was fine. i got my dvd key from Jtag tool.
i couldn't even begin to tell you why this is though. i know of 2 different consoles reading the same on Xellous.

 

[Hiryuu]

Well I dont have a dvd key in jtag tool... Im very much stuck right now...

 

[hodgie]

im confused i guess. you never saved it anyware, from your previous FreeBoot, or dumps? didnt you keep your orig, and keys? i mean, it hasnt changed from before, so if you had it still, you would be good, right?

 

[Hiryuu]

im confused i guess. you never saved it anyware, from your previous FreeBoot, or dumps? didnt you keep your orig, and keys? i mean, it hasnt changed from before, so if you had it still, you would be good, right?

Right, I know thats what I said when I started this thread. I only have the cpu key... No original nand stupid on my part. But Im trying to get this fixed now as you can see

 

[hodgie]

do you need the dvd key? isnt it already flashed to your Drive from before you changed anything this time around?

BTW, i do far dumber things on a daily basis, LOL im sure this will be no biggie soon

 

[Hiryuu]

well you saw in the pics its shows as '0000000000000' and in the xellous boot it says there is an error with the kv

 

[hodgie]

right, but i have had the same thing on 2 different occasions. i asked about it as well, but noone but me was concerned, so i went ahead anyway.
did you have a disc drive before all this?
im prolly not helping you at all, and i appologize if i am wasting your time!

 

[Hiryuu]

yup i still do