Can you FTP to your debug? If you put the retail XBE patch on it, you should be able to read the key from UnleashX.
Debug is dead and needs repairs (well, actually finding out the fault is the major thing). So no, the key is not obtainable that way. I have the eeprom dump and the hdd is in a 1.0 retail xbox, but evox is giving me a hdd unlock error.
No....? The debug console is dead, the hard drive from it is in a 1.0 retail console. I need to get the key from the debug eeprom so I can unlock the hdd and read it via a retail console.
Sorry didn't read the last line. Uh, even with a modchip isn't not ignoring the lock/unlock? Have you tried redumping the EEPROM? Sometime LiveInfo won't read it straight away, what I did on the retail one. Not sure if this will help, but it might show the key. http://xbox-scene.com/tools/tools.php?page=harddrive#newsitemEpFuAlFEpFNMArtNKu
Modchips cant bypass the ATA lock, you need to know the key. The eeprom is dumped correctly, it was removed and read in my programmer. I believe its something to do with debugs using a different encryption key - but I do not know a great deal about debug hardware, which is why I am posting here.
Would XBOXHDM show you the key? I just remember when trying to unlock/lock via EEPROM it shows you the information.
Debug kits are not locked, so Im not sure why you would need the key? Not to say it hasn't been locked, but usually its not. http://www.assemblergames.com/forums/showthread.php?25294-Xbox-Debug An old thread had Diddy trying out the software from here : http://www.hdd-tools.com/products/rrs/ With some success http://www.assemblergames.com/forums/showthread.php?17224-Need-some-advise-on-unlocking-xbox-HDD-s
Evox says "unlock error" for the hdd, so I assume its locked. If not, I wouldnt be asking I would rather not mess with software to brute force or mess around with the drive. I would much rather get the key from the eeprom. Worst case, I will get another debug and swap the eeproms to get the data and/or key.
You can see the key in XBOXHDM... I doubt it matters about the different security. Worth a try I guess...
It very much matters about the security, if what I read about using a different key is correct - its encrypted, without correct key you cant read it. I have never used xbox HDM though, will look into it.
I mean like not sure if XBOXHDM will care about it. It will show the key when you attempt to unlock the drive, regardless if it's successful or not.
Yes, which it reads from the eeprom - which is encrypted. Xbox HDM will have to care about the encryption, else it wont be able to read the key from the eeprom. You cant read the key directly from the HDD, it comes from the eeprom.bin you drop in the xbox hdm folder.
I know you can't... didn't say you read it from the HDD lol. As long as XBOXHDM can find the EEPROM it may or may not be able to read it - only one way to find out.
Debug EEPROMs are encrypted with a different key, hence the error. If this is a true debug, the hard drive key is all zeros, as my memory serves. However, that was only debugs that haven't been seriously mucked with. =) By the above, I meant that debug drives are locked by default, but a) the key is all 00 bytes by default, and b) the debug kernel will accept entirely-unlocked drives.
Its locked, its a true debug, I know its different encryption - which is what I said above. I will try all zeros, thanks
