(adsbygoogle = window.adsbygoogle || []).push({}); Hi,

Got a question regarding KV's. Now i know that with the CPU key and 360 flash tool you can extract the KV_dec and KV_enc from the nand. But what i'm wondering is when you are jtagging and reading from the nand you extract the KV (KV.bin) directly from the nand via the lpt or usb flasher, whatever it is you are using. You do this to inject KV into XBR etc. Why is this KV different from the one generated by 360 flash tool (KV_dec & KV_enc)?

any answers would be appreciated, aslong as they help that is

The one through flash tool is decrypted, if you read it directly it is encrypted.

No need to extract it via flash360 unless you are putting freeboot on. And even then ibuild does it for ya.

Is there anyway of decrypting it? I put XBR on first and then make the freeboot image from the piggy toolbox with the CPU key, but i have only just started putting freeboot onto the consoles i work with as about up until a few weeks ago i was only doing the XBR. And when i backed up the nands i never made a copy of the CPU keys, so i have a load of nand backups without CPU keys but instead they have the KV.bin which was read directly from the nand...

You use the KV's you took straight from NAND, inject them into XBR, or use the entire Nand dumps to build Freeboot.

The KV enc/dec are for using with KV editor etc. Your NAND KV's are used to inject over XBR as you say.

There's a very slight difference in size too, the KV's straight from NAND won't open in KV editor.

I noticed yesterday that if you don't use the KV straight from the NAND when injecting XBR, it might not work, I was trying after extracting by "Nanddump1.bin: -r16 KV.bin" for example as opposed to "LPT: -r16 KV.bin" and it just wouldn't boot, power it up and it just green lighted in the centre, nothing else happened. Once I tested stock dashboard again and it worked, I just read KV from there (onboard) and injected that one for XBR3. I think it might be like the diff between the enc/dec versions.

Just my opinion on it!

You're missing my point. I know the KV's you extract directly from the NAND during the jtagging process are the very same 1's you use for injecting etc.
Yeah theres .5 of a kb size difference. I just want to know if there's a way of using teh KV extracted fromt he nand via the flasher during the JTAG process to obtain the actual KV file, like for unbanning....

I have a load of nand backups without CPU keys but they do have the KV.bin i dumped directly from the nand during the jtagging process.

Is there a way of obtaining the KV without the CPU key but with a KV.bin dumped directly from the nand. Am i making any sense?

The only way to get a usable KV needed for unbanning is extracting it with the valid CPU key.

Flash Xell/Xellous, or if you have XBR on there xell is already installed. Boot up the console from the eject button.

Yeah i know all of this, point being i don't have the consoles anymore. I jtagged them with XBR for customers and then shipped them out. I just have the raw backups of the nands, untapped KV potential!!!! All this before i started using freeBOOT so had no need to backup the cpu key

Then sorry to say you are SOL.

You should always grab the CPU key!