He means saves OE, not XeX's Well most saves are either saved on the profile itself or on the hdd save partitions like where halo 3 saves its films etc. Currently if you wanted to transfer a film to dev all you do is resign the file with a CON resigner using a dev key vault and the machine and profile ID of the dev. For profiles I believe some people do know how to transfer them but currently it int public, I think you need a special key that only like 2 people have it for dev.
Use the hyperviser exploit and get a nand dump and just compile it with any old con resighner, then resign it all you need is the kv and your key-pairs, at least im pretty sure... (maybe)
well the kv is the keyvault ( witch contains your keys ) but it can resign them to different id's when i said keypairs i meant your console id/ device id so u need the kv.bin dumped from an xdk and you need your id's from witch can be extracted from any user created content container file (gamesaves)
lol. Also, kiwi, hypervisor is still intact on devkits. So I don't believe so, as the exploitable kernel let us around the hypervisor. Even more lol. No. It isn't. A keyvault is a section which contains multiple keypairs, and certificate info. If you are aware that cryptological methods use TWO keys, and you know what a pair is, then you'll understand. And a vault meaning a safe place to hide something. You don't neccessarily need to to make it work. Also machine ID has nothing to do with most gamesaves, that's only Halo Related LEo. The only IDs that you're looking at that should matter are the ConsoleID, ProfileID, DeviceID, and if you edit those accordingly, you can make a container file work on any xbox/profile. EDIT: Hah I beat you in post time gamerfreak! ;P
