QUOTE(baltazor @ Jul 19 2007, 10:08 PM)

ALSO.....
U sure about that,.....?
Yes. I've been observing the entire development of this on xboxhacker and I'm a professional embedded developer who spends half the day futzing with the contents of NAND flash on odd devices

QUOTE
So, if it indeed is stored in the kernel then it awfully look like the kernel shall be modified too at least to change that!!
The NAND flash contains several things:
* The cpu/southbridge init code and second stage boot loader.
* The original hypervisor and kernel
* Patches to the hypervisor and kernel
* The keyvault
* A filesystem, containing the dashboard binaries and resources
The keyvault is a separate part of the flash from the kernel, hypervisor and dash. It can be changed independently of the kernel, all that is required is a known CPU key to decrypt and encrypt it with. It includes the DVD key, the game region, and various other settings (some with known purposes, some currently unknown).
This is why it's possible to upgrade the kernel after dumping your CPU key, and still modify the region afterwards - the keyvault is not kernel-dependant as far as anyone knows, currently this kind of modification appears to work just fine. It is fairly analogous to the EEPROM on the xbox1, though it only seems to store 'permanent' settings like the DVD key and region - the normal dash settings are probably somewhere else. Unlike the EEPROM on the xbox1, however, it's encrypted, so you can't modify it without knowing the key.
Also, it doesn't store the CPU key (equivalent of the xbox1 serial) so it's not possible to get unbanned by modifying the keyvault (unlike xbox1 where you can replace the serial with another box's and thus get back on live)

I hope that makes it clearer.