Topic: KeyVault Modder v1D (Read 227 times)

saso · « **Reply #15 on:** November 27, 2009, 09:36:00 AM »

it worked only with xenon MB can't change region with zypher or falcon the same as FT

damonnomad · « **Reply #16 on:** November 27, 2009, 09:55:00 AM »

QUOTE(saso @ Nov 28 2009, 12:36 AM)

it worked only with xenon MB can't change region with zypher or falcon the same as FT

Don't you mean type 1 key vault and not type 2.

Granted type 1 never made it to zephyr/falcon+, but xenon can also have type 2.

saso · « **Reply #17 on:** November 27, 2009, 10:36:00 AM »

QUOTE(damonnomad @ Nov 27 2009, 05:55 PM)

Don't you mean type 1 key vault and not type 2.

Granted type 1 never made it to zephyr/falcon+, but xenon can also have type 2.

even if u have xenon kv type 2 it will work with it but not zephyr/falcon

pricemeista33 · « **Reply #18 on:** November 27, 2009, 11:02:00 AM »

QUOTE(biscoito @ Nov 27 2009, 07:29 AM)

what would happen if you changed the DVD key to all zeros ?

I was thinking the exact same thing as you may still need to have the "zeros" reflect the drive though. So if you do manage to change the key to all zeros then you will need to change the drive itself to "zeros". The KV side and the components themselves must still be married as the Kernel governs this.

modslave · « **Reply #19 on:** November 27, 2009, 12:19:00 PM »

QUOTE(ToBbErT @ Nov 27 2009, 09:48 AM)

The cygnos is used for exploiting the system and reading/writing ect. It can be used but its to expansive imo if you only wanna read/write the nand.

Yes it is expensive but as soon as it supports the Jaspers with larger sized NAND's I think im gonna get one as its an easier option to reading/writing using USB than making your own convertor.

Im too impatient to wait for it to dump using printer port but also to impatient for another hardware revision

I had orriginally hoped it would just be a firmware update to the cygnos v2 but according to their site forum apparently not

effective · « **Reply #20 on:** November 27, 2009, 01:09:00 PM »

They do hashing and signing of the keyvault to prevent you from changing this information on nxe or higher consoles. This info is stored at 0x1DF8 into the kv.bin if extracted with bincrypt.

shummyr · « **Reply #21 on:** November 27, 2009, 02:24:00 PM »

will this work on console with a jasper 512mb and Kernel 8507 with the Cygnos v2.0

zouzzz · « **Reply #22 on:** November 27, 2009, 02:55:00 PM »

QUOTE(caster420 @ Nov 27 2009, 01:26 PM)

Nice release zouzzz.
Caster.

Thanks.

Morning Call · « **Reply #23 on:** November 27, 2009, 03:30:00 PM »

this is good progress. but i do not see the real world application.

if you have your CPU key, you can recover your DVDkey. so lost key due to a dead drive isnt the reason.

if its so you can use a legitimate fw on a drive other then your stock, well that can be done on the drive side.

if its to spoof your drive for xbox live use, well modifying your KV can be detected.

i just dont see where this app is real world useful. seems more like a testing app

braza · « **Reply #24 on:** November 27, 2009, 04:45:00 PM »

HHUMMM

I try to change the region from NTSC-J to NTSC-U and.... fucked!

I get 2 red lights and 2 green lights !

Why ??

Falcon boards and same KeyVAULT !

Hex says 00FF changed to 0101 only!

nilezon · « **Reply #25 on:** November 28, 2009, 05:46:00 AM »

QUOTE(damonnomad @ Nov 28 2009, 07:34 AM)

It hasn't been directly mentioned in this thread, but the key vault is hashed.

Changing anything within the hashed area obviously breaks the hash.

This causes the Christmas lights, or as it was called in the xbox 1 days cause it to frag.

Changing it back to the original region should fix it.

Is there any chance this hashing/signing will be reverse engineered, bypassed or brute forced any time soon?

Mr.RedRing · « **Reply #26 on:** November 28, 2009, 10:08:00 AM »

I have an Xbox 360 I got from someone because they screwed up the flash. Can I use this to read the dvd drive key from the Key Vault in the Nand? If so, I can get a working system again can't I...

effective · « **Reply #27 on:** November 28, 2009, 10:14:00 AM »

QUOTE(effective @ Nov 27 2009, 09:09 PM)

They do hashing and signing of the keyvault to prevent you from changing this information on nxe or higher consoles. This info is stored at 0x1DF8 into the kv.bin if extracted with bincrypt.

It was mentioned, and I told you where the information is stored, read next time. They hash certain parts of the keyvault leaving out areas that are dynamic, they then do byteswapping and rsa. The result is stored to 0x1DF8 in the keyvault and is 0x100 long. You could try clearing this area and see if the console will still boot after a change and redo the hash, but I suspect they added this function to the updates so you can't just clear it.

Author Topic: KeyVault Modder v1D (Read 227 times)