green key is the production crypto key, it's what they use to encrypt the XVDs for production. there's also the red key which they use for development that all devs have

https://github.com/emoose/xvdtool
is the tool to use supposedly :shrug:

So this is for Xbox One, not Xbox

https://github.com/emoose/xvdtool
is the tool to use supposedly :shrug:

user7 wrote:

Any chance you would consider open sourcing this?

sure, here it is: https://github.com/LedZeppelin68/dvd-shrinker

all credits for the algorithms goes to JayFoxRox

The "green key" has been leaked, whatever that is. Would it be of any help in obtaining the second type seed?

Also, I noticed that the wiki was updated since our last posts, so maybe there are new insights: https://xboxdevwiki.net/XDVDFS#Random_blocks

Any chance you would consider open sourcing this?

sure, here it is: https://github.com/LedZeppelin68/dvd-shrinker

all credits for the algorithms goes to JayFoxRox

Thanks for your work.

Did you make any new research on this, Led?

I would continue to research type 2 algo, maybe some statistical analysis will help

for now, all i can offer to save space
1) for a little amount of isos with type 1 seed (maybe few hundreds) - xbox shrinker
2) for big games with regional clones, which data occupies most of the iso - use merger

Sorry, this is all i can offer

Did you make any new research on this, Led?

So, the tool is useless for most discs.

I remade xbox_rnd tool, now it doesn't remove the junk from ISO, but only brutes the seed of first type
saves it to log, and it works much faster

P.S. drag all ISOS on the EXE and wait

Ok but my questions about the timestamp? Is there no way to predict the seed?

i can say - no

the seed value for second type is 128 bit, which consists of two 64 values:
1: system time and date (we can reduce this value to year, or maybe a month) +
2: and time from last reset (2^64 combos)

it is a very huge number to bruteforce

second type seed is 128bit, 256^16 combinations, impossible to bruteforce, forever