does it???it does need to be an old phat console with hdmi ..or a new slim with a certain mb though ...just to add to martins answer...in case you were wondering
some zyphers with a certain cb are also not rghable. i dumped one but i think it has been back to ms for repair.
You are right, the hack should work since it doesnt use the hana chip, but they need to make new files specifically for corona consolesCoronas are not glitchable period. A new hack needs to be developed for it since it doesn't have a Hana chip
Hey Sdeens, thank you for the heads up.Also the Falcons with CB "above" 5771 will NEVER glitch due to secondary bootlader, but even the older 5771 CBs motherboards are still designed around the newer v3 schematic from (circa August 2008 and newer) and are also not easily glitcheable. They seem just as finicky as the early Zephyrs IMHO. I think you need v1 or v2 Falcon if you want to reliably RGH. A rare v3 Falcon is 50/50 chance.
But despite all that, you can probably get the CPU key via Xell after an ECC write session, but the nandflash.bin that v0.7 "360 multi builder: creates has problems making working TSOP images for the 5771 CB in these newest rare V3 Falcons. It helps to first erase these Falcon TSOPs before flashing them and ground the low at startup wil trigger a bootrecovery and force a reload of the kernel.
btw: these 360 firmware chips are called TSOPs and not NANDs.
Some have suggested flashing an Opus timing file or making an OPUS .ecc file or sliding the coolrunner toggle to SLIM, but that wont help a CB: 5771 Falcon v3 console. these are not the easiest of the Falcons to RGH.
The Falcon/Opus timing files may still need tweaking.