The fight against the 360 ban is heating up as hackers start to pull out there big guns. k0mpresd
from X-S has posted a tutorial (confirmed working), which unbans any Xbox 360 console (8955). The method is old and known (more info below), and is quite complicated so its not "newb friendly".
Post from k0mpresd :
what you need:
your 8955 live console + cpu key a 2nd unbanned console nandpro b + flash cable xell loader degraded 1888 fs robinsod's flashtool
use nandpro and dump nand from unbanned console. flash xell and use jtag hack to obtain cpu key. use flashtool to extract file system.
dump nand from 8955 console. use flashtool to patch nand dump with kv.bin from unbanned console. save patched file (patched_kv.bin).
open degraded + 1888 fs. create 1888 downgrader image (downgrader.bin) from your patched_kv.bin file.
flash downgrader.bin to 8955 console. attach hdd + ethernet cable and boot console.
connect to live and update to 8955 dashboard.
console is now fully working and unbanned!
More info on this method:
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 there's a (really) big 'IF' (besides the required tech knowledge) ... you need the (unique) CPU key of your banned console - without it you can't correctly write (or encrypt if you want) 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 that's even more outdated) ... and if you got banned the last few weeks it means you updated to the latest dashboard/kernel (else you can't get on LIVE). And that's 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 there's also added KV protection (hashing) on newer motherboards (Falcon+ ? and kernel 1888 won't boot on those), but if you can't even get your CPU-key it doesn't 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 I'm not telling you anything new Downgrading kernel is not an option either, older kernels won't boot as both kernel and CB fuses were burned during the various updates MS performed, and you can't bypass that without ... your CPU-key.
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). Side-note2: in case it wasn't obvious yet those "unban isos" are fake and iXtreme LT won't unban you (it will instead try to avoid new bans).
In other news, C4eva has announced he is working on a new firmware for the 360 which is not bannable, more info:
C4Eva announced he's working on a new firmware on IRC: "[c4eva] new fw in dev/test - ixtreme LT (Lite Touch) - more efficient , minimal patching , all aspects of fw indistinguisable from orig, no more bans, No ETA!"
We do not have more details atm. As far as we know the 3 'test boxes' C4Eva has running (see here) are still fine (not banned).
and Team Executer