KeyVault Editor 0.1b

This application allows you to encrypt and decrypt your KV image (will require your unique CPU-key - which as reminder you can't get if you upgraded to kernel 849x or higher)). You can spoof ur DVD drive on KV-side (rather than spoofing the actual drive), change your game-region and read-out/change the DVD-key and change your serial number, Console ID, Convert Type 1 to Type 2.



New version 0.1b

New features:
1. Fix Decrypt Data
2. Fix Set MFR Date
3. Fix Set Console ID
4. Fix Set Serial Number

Download:
http://www.megaupload.com/?d=01GNU0QQ

Thanks for the app!

Here is a Demo: http://www.youtube.com/watch?v=gzFcrCwlHA4

Nice work, but after editing the controller does not connect to the console, and this editor is can not open falcon and jasper keyvaults, only xenons for me.

Can you tell me more about it? And i have open Falcon KV just fine

With this tool, then it is possible to unban a console?

With OSIG set to Unspoofed does that mean any brand DVD drive would work as long as the Keys matched?

Your console shouldn't be banned in the first place...

Spoof the DVD-ROM console-side - that's awesome, and seems like it could save a lot of time (and DVD-ROMs)!

Error: Failed to decrypt data.

Jasper KV with correct CPU key.

I can't figure out how you go about changing the kv type.

Type 1 = Unspoofed
Type 2 = With OSIG String

not working with jasper, work with xenon.

Problem Fix Try my new 0.1b

Ok, now 0.1b is working with Falcon keyvault. But If I change anything, i get christmas lights on Falcon.

I think (but I'm not sure), you'll need to use this with freeboot .03, which had a patch to disable KV checks.

So what happens if we change our console ID's and serial numbers, then go online?

can i use it with my 16mb nand jasper or i will get cristmas light from hash checking?
thanks.

I know on XBR3 (not sure on freeboot .03), you could not change the serial number/mfr date etc because the KV is hashed in certain sections (serial number, mfr date, console id, console certs). Freeboot .03 did say it "disabled kv checks", but I'm not sure if they meant they disabled this hash check. I know that on XBR3, whenever you tried to do this (which is incredibly easy to hex edit), if it was an xenon, the xbox controller wouldn't connect. All other boards would get christmas lights. On the xenon, i plugged in a usb keyboard to navigate around the dash and it did show edited serial number in the dash, but i couldn't connect to xbox live.

I know you can use different keyvaults on a falcon in Freeboot 0.3, but using any other version of freeboot will give you christmas lights.

LOL

Since you can read the KV, make the DVD drive comply with it instead of making the KV comply with the drive.
Also, because the KV is signed and hashed with the CPU key, you can't modify a single bit in it.

Every time the console power up with a modified keyvault it will log a "keyvault policy violation" event on the security data and you don't want to go online with that flag set on your console ...

I wouldn't bother putting that console online. I'd rather JTAG it.

Isn't part of the KV (the "ticket") signed with an external private key only known by MS? They just need to pass it to the auth servers like steam does to verify legitimation since its unique and unchangeable. That would be virtually uncrackable and safe because the private key is completely unknown.

did editing region using this utility also result christmas light ?

Exactly. This is why everyone who is changing anything other than the DVD Key and OSIG is getting christmas lights. The only way you could edit the serial number on a kv is if the check was removed completely from the dash or we knew the MS private key.

use it with FreeBoot or XBR = NO christmas light

Falcon with freeboot 0.32, and xbr got christmas lights.

hey thanks for the progie one question i tried to build a freeboot image with a KV i modded with this and freeboot is now telling me that the modded kv is not the right size ERROR: File "kv.bin" has a size of 16384 bytes. Expected size is 16368 bytes. i was just wondering if there was a way to fix this

I think you just have to cut the first 16 bytes (checksum).

I'm trying to enter my unbanned consoles console ID number, but the field isn't long enough to get all of the digits, so it wont let me type in 2 of them. Anyone else have this problem?

...Never mind. I didn't read everything in this post lol

Apparently there's a patch getting around for 0.32 that allows KV change, If anyone can pass it on I would be most grateful. otherwise I/we would donate heaps to anyone who can help us making our own. I've tried a couple of different ways of going about it but so far no good.

Brgds/Dan

A complete noob question here..
I have been reading a lot lately about KV.bin and what it does, how to change it etc. i have found a bit about hex editing the sec_data.bin to re-allow writing to hdd.

I have two old xboxes in working order, one banned in 2008 dash 67XX with a bricked dvd drive, the second is dash 6717 - (I'm told) not banned and I know dvd is working. I worry that connecting the second one to xbl will reveal it is banned really and so lose functionality (plus it would seem an advantage not to update that xbox).
Neither of these boxes will be used to connect to xblive

What I would like to know is.. If you change the KV.bin key... do you still need to hex edit the sec_data.bin?
How are they related/dependent?

Thanks works great

I tried this with ggbuild 0.33 (that works with the reset glitch hack) and as soon as I change anything to a keyvault I get 2 red and 2 green lights aka christmas tree.

Is there any solution for ggbuild users?

because you'll have type2 keyvault it is hashed, any alterations to the kv will result in xmas lights.
only option is to change the whole kv.

Ted