Help unlocking hard drive
in [Hardware]
|
Prev: RAID 5 reading performance
Next: DVR-K17A firmware?
From: Grinder on 31 Jan 2008 20:21 nmorson(a)googlemail.com wrote: > On Jan 30, 9:51 am, Grinder <grin...(a)no.spam.maam.com> wrote: >> I still think that unlockhd from your xboxhdm disc can be used to unlock >> your drive, but I've found this site that might provide a plan B (or C): >> >> http://www.seagateunlock.com/ >> >> I see now where updating the firmware, for some Seagate models, will >> unlock the drive. > > Many thanks for all your help. I have tried: > xboxscene in lower/upper case - no joy with xboxhdm > atapwd in pure DOS mode - with xboxscene password (uppper/lower case) > and also by typing in key from eeprom.bin - no joy > writing zeros (using a program which I forget the name of) to the > drive - although this was in the Windows environment - I could try > this in DOS mode The key in eeprom.bin is encrypted. I'm not sure how you extracted it, but that would be something good to know. xboxhdm's unlockhd cannot unlock the drive with the provided eeprom.bin, I would think that it's not locked with that key, or that the hd might actually be failing.
From: nmorson on 1 Feb 2008 02:43 > The key in eeprom.bin is encrypted. I'm not sure how you extracted it, > but that would be something good to know. xboxhdm's unlockhd cannot > unlock the drive with the provided eeprom.bin, I would think that it's > not locked with that key, or that the hd might actually be failing.- Hide quoted text - I didn't extract the key from the eeprom.bin - I guessed that xboxhdm had reset the password to xboxscene. Upon first build it used the eeprom.bin file to lock the drive and then set the master password to xboxscene (I obviously missed this screen when setting it up). What doesn't make sense is how the same eeprom.bin file managed to unlock it later so that I could rebuild the drive when the master password had been set to xboxscene. This would not have been stored in the eeprom.bin as I was using the original file. As for the drive failing, it's a one week old Seagate 1/2Tb model so think it unlikely
From: Grinder on 1 Feb 2008 03:53 nmorson(a)googlemail.com wrote: >> The key in eeprom.bin is encrypted. I'm not sure how you extracted it, >> but that would be something good to know. xboxhdm's unlockhd cannot >> unlock the drive with the provided eeprom.bin, I would think that it's >> not locked with that key, or that the hd might actually be failing.- Hide quoted text - > > I didn't extract the key from the eeprom.bin - I guessed that xboxhdm > had reset the password to xboxscene. Upon first build it used the > eeprom.bin file to lock the drive and then set the master password to > xboxscene (I obviously missed this screen when setting it up). What > doesn't make sense is how the same eeprom.bin file managed to unlock > it later so that I could rebuild the drive when the master password > had been set to xboxscene. There is a hard drive key, derived from eeprom.bin *and* a master password that gets set by xboxhdm. Knowing either one can unlock the hard drive. > This would not have been stored in the > eeprom.bin as I was using the original file. Ok, I don't understand that at all. Xboxhdm, nor lockhd/unlockhd make any modifications to eeprom.bin. The reason eeprom.bin is used is so that the drive can be locked with the same key that the xbox will attempt to unlock it with. *In addition* to that, a master password is set on the drive so that you can unlock the drive without having to know the xbox-specific key.
From: nmorson on 1 Feb 2008 18:43
On Jan 31, 8:53 am, Grinder <grin...(a)no.spam.maam.com> wrote: > nmor...(a)googlemail.com wrote: > >> The key in eeprom.bin is encrypted. I'm not sure how you extracted it, > >> but that would be something good to know. xboxhdm's unlockhd cannot > >> unlock the drive with the provided eeprom.bin, I would think that it's > >> not locked with that key, or that the hd might actually be failing.- Hide quoted text - > > > I didn't extract the key from the eeprom.bin - I guessed that xboxhdm > > had reset the password to xboxscene. Upon first build it used the > > eeprom.bin file to lock the drive and then set the master password to > > xboxscene (I obviously missed this screen when setting it up). What > > doesn't make sense is how the same eeprom.bin file managed to unlock > > it later so that I could rebuild the drive when the master password > > had been set to xboxscene. > > There is a hard drive key, derived from eeprom.bin *and* a master > password that gets set by xboxhdm. Knowing either one can unlock the > hard drive. > > > This would not have been stored in the > > eeprom.bin as I was using the original file. > > Ok, I don't understand that at all. Xboxhdm, nor lockhd/unlockhd make > any modifications to eeprom.bin. The reason eeprom.bin is used is so > that the drive can be locked with the same key that the xbox will > attempt to unlock it with. *In addition* to that, a master password is > set on the drive so that you can unlock the drive without having to know > the xbox-specific key. That's useful to know and explains why I can lock the hard drive with the eeprom.bin file (although once the master password is set to XBOXSCENE this file will not unlock the drive). Thanks again for all your help :-) |