the orig.bin it says ‘DVD key@ 0×4f00 0×33681CB6′.
nandpro
i dumped my nand 3 times to be safe luckily i did as when i flashed my nand back
just for testing , it wouldnt power on then tried my second dump and it came straight back to life
i havnt had time yet to compare the 2 files properly but they look the same
so it could of just been a bad flash the first time
Dump nand using nandpro attached via jtag.
Write xenon_hacked using jtag.
Note fusebits 3 and 5 displayed through xell.
Use fusebits 3 and 5(cpukey) to decrypt keyvault using robinsods flash tool.
Note dvdkey.
Reflash original nand dump via jtag.
you may have to keep a camera at hand cause the cpu key scrolls by somewhat
fast, but yeah, that’s all you gotta do.
just about any 15-25W pen tip iron. the solder spots are quite large.
you just need to backup your original nand image, and then flash a hack image
to the nand, and turn on the 360 with a LPT cable. You
will be able to see the cpu key on the screen. with that, you can decrypt your
original nand and get your dvd key.
MOTHERBOARD IS A XENON BOARD
U can read here too!

http://www.free60.org/Reading_out_NAND

Xenon on this pic no hdmi console and u can read here

http://forums.xbox-scene.com/index.php?showtopic=690493h

xell gives you your cpu key when it boots, so all thats needed for dvdkey recovery
is your original nand, xell booting on the motherboard and 360 flash tool to read out your dvdkey.

http://360.xbox-hq.com/xbox-tutorials-107.html
http://www.xbox360-hacks.com/forums/about3547.html how to do it

http://dwl.xbox-scene.com/tutorial/Xbox_360-HandC-V1_4.pdf
http://www.free60.org/Reading_out_NAND
http://www.console24.com/product_info.php/products_id/357

I see lots of sites posting today about a way to unban Xbox 360 from LIVE often linking to a thread made on our forums here.

This method has been known for a long time (since the King Kong Exploit days) and does indeed work. Basically you swap the Keyvault (or KV in short, it stores stuff like console certificates, per-box private keys, DVD key, etc) inside the NAND with the KV from an unbanned console. While technically very different you could somewhat compare it to swapping eeprom data during the Xbox1 days.

However theres a (really) big IF (besides the required tech knowledge) you need the (unique) CPU key of your banned console without it you cant correctly write the new KV data in the NAND bin of your banned console.
Now you wonder how to get the CPU-key well by running XeLL of course!
To run XeLL u need to perform the JTAG hack (or the King Kong exploit, but thats even more outdated) and if you got banned the last few weeks it means you updated to the latest dashboard/kernel (else you cant get on LIVE).
And thats the problem Microsoft patched the JTAG hack since kernel 849x (July 2009) so no way to boot up XeLL (= no realistic way for you to get the CPU-key atm) and thus no way to swap the KV data in your NAND image.
And then theres also added KV protection (hashing) on newer motherboards (Falcon+ ?), but if you cant even get your CPU-key it doesnt matter much to do deeper into this problem.
The only way it would work is if you retrieved the CPU-key of your old banned 360 before you updated to anything over 849x. If you did that you probably know about all of this and Im not telling you anything new
Downgrading kernel is not an option either, older kernels wont boot as both kernel and CB fuses were burned during the various updates MS performed.

Hope that explains the situation a bit (tried to make it not too technical)
On a side-note, it would probably be pretty easy for MS to detect KV-swaps (like HW-mismatches etc).

Duration : 0:10:1