I bought a 360 off of ebay with the intent to do some hacky stuff with it (last year actually). Unfortunately, the seller didn't mention anything regarding the history of this box. Turns out that ... It was a Xenon console (the kind you wouldn't want to RGH unless you don't mind waiting up to 24 hours for it to boot). It had been previously opened. Doesn't play 360 game discs (will play Xbox1 games though); just assumes it's a DVD movie. And when you try to update the dashboard, you get the E66 (1002). I know what the E66 means in general, but since I don't know if the DVD drive was replaced or wasn't spoofed properly, I don't know exactly where to begin fixing it. It wasn't a total loss since I got loads of peripherals I needed. The reason I didn't find all this out until recently was because I didn't have any 360 games and all I cared about was playing arcade games and stuff. I never could get Xbox live before because I was homeless (not "sleeping under a bridge" homeless), so that's why I'm just now finding all this out. Maybe I'm just better getting another console. I hate 360 with a passion, but I still have some use for it. Any ideas? Thanks.
Unfortunately, E66 usually indicates a dvd drive key mismatch. That means someone tried to flash the dvd drive and didnt spoof the key, or most likely the original drive is missing and different one was put in which has a different dvdkey meaning that you will have to either JTAG it if the dash is 7371 , Time attack it if the dash is 8498 or lower, or if the dash is is higher than 8498 then have to rgh it. Any of those options can be used to retrieve the original dvdkey to spoof to the drive properly.
Could you explain exactly what the "Time Attack" is. I've been trying to find out about it but I can't find anything.
A time attack is the method that the RGH uses. You can read all about how it works here: http://www.free60.org/Reset_Glitch_Hack
I've installed lots of Coolrunners for people's 360s, and that page about how it works still completely throws me off xP
The dashboard version is too high to JTAG, so I can only RGH it then. Since it's a Xenon, it's probably not worth even trying.
E66 happens when the DVD drive key is correct but the device ID query on the keyvault mismatches what the drive is reporting. It get logged as a security fault on secdata.bin so I would not put that console online with a important account even if it got fixed... You could try flashing a few different drives with that key then try each one with the console. If the key is wrong it doesn't even bother checking the drive inquiry against the keyvault. Knowing it's a xenon, it can be any drive from Hitachi-LG up to Benq/Phillips. If it has a service date of 2009 or later it can also be a Lite-on. But the "key" information here is it won't give you E66 unless the DVD key is correct. Edit: Another thing I forgot to mention, you will need to fix it to be able to update it to a recent dash or use some of the dirty tricks people use to let it update (an XBOX360 DVD drive with mismatched key could work). Newer dashboards/kernels don't enforce ID query match on "fat" consoles because the ID of the drive was changed due to the drive firmware update for XGD3 discs. Because they cannot locally modify the keyvaults, they choose to just disable the query checks so an updated "fat" console (XGD3 capable) won't give you E66 in any way. I can't vouch about serviced consoles as servicing them personally they're able to securely sign anything on the unit, meaning they could re-jig all the protections throughly. Field updated consoles are a different story.
No it's not. It was an obsolete hack that exploited the memcmp function in the HV that allowed the downgrading to 1888 base kernel then to a King Kong hack exploitable dash. It works up to 8498, but the hardware to do the timing attack is difficult to find because infectus who made downgrading hardware went out of business a looooooong time ago
