Post by: chimpanzee on July 24, 2004, 11:55:00 PM
The reason is that ConfigMagic no longer runs on 1.6 and there is a chance that the eeprom layout etc. has been changed so the HD key generation may no longer work as well.
Post by: EthanHunt_IMF on July 25, 2004, 12:24:00 AM
Post by: chimpanzee on July 25, 2004, 12:31:00 AM
Post by: chimpanzee on July 25, 2004, 12:40:00 AM
| QUOTE (scrupul0us @ Jul 25 2004, 08:40 AM) |
| Whats your kernel version? |
mine is an old one 5101, so it is not a problem for me. But I would like to know how crippled 1.6 is so if I buy a new one, I have to watch out.
The 5713+ kernel issue is more or less solved but 1.6 box is iffy based on what I have read so far.
Post by: chimpanzee on July 25, 2004, 12:47:00 AM
| QUOTE (scrupul0us @ Jul 25 2004, 08:44 AM) |
| Far as I know, UDE2 supports 1.6 Kernels... |
I am not talking about the kernel, I know UDE2 supports the kernel 1.6 use in US/Canada. The whole thread is about if the key grabbing procedure still works on 1.6 as that is needed for HD upgrade. Without HD upgrade, the box is heavily crippled even after modding. There is only about 5G space on E which can't even store one backup game and at most 3-4 DivX movies.
Post by: ldots on July 25, 2004, 10:09:00 AM
First of all you need a tool that can read and dump the eeprom on a v1.6 xbox. This has new hardware (new mobo), so this probably needs some changes in the software that is suppose to access the eeprom. In the xbox_tool case the i2c-bus drivers probably need updating. I'm sure the xbox-linux team will do this in a future release of the xbox-kernel. I think Gentoox was recently run on a 1.6 for the first time.
Second, the eeprom could be encrypted differently. I doubt it. So I would think xbox_tool (in my updated version) would be able to decrypt the eeprom. If it doesn't it might only be minor changes that would be needed. And EthanHunt_IMF, this linux tool doesn't use the eeprom key. It's able to decrypt the eeprom without any keys using the "Friday 13th attack" hack.
Thirdly, the eeprom layout could be changed. Also that should mean minor changes in present tools. And it's not only the HD key that needs extraction, it's also the "Confounder" entry that goes into the HDD password generation (along with the HDD model and serial number).
So, can any tool presently even dump the eeprom to a file? If so, does it look reasonable
Post by: EthanHunt_IMF on July 25, 2004, 12:19:00 PM
Note to Ldots... Are you sure about the confounder key being needed? When I use liveinfo, it generates the same password whether i used the confounder or not, and this password matches the orginal password i used to unlock the drive (it's my stock seagate 10 gig HD)
Post by: ldots on July 25, 2004, 01:22:00 PM
| QUOTE (EthanHunt_IMF @ Jul 25 2004, 08:22 PM) |
| Note to Ldots... Are you sure about the confounder key being needed? When I use liveinfo, it generates the same password whether i used the confounder or not, and this password matches the orginal password i used to unlock the drive (it's my stock seagate 10 gig HD) |
Sorry, not being too specific. The Confounder entry is not needed in the actual HDD password generation, but it's used in the "Friday 13th" hack for decrypting the eeprom. Both the linux tools, Liveinfo and ConfigMagic use this.
Well, if the evox eeproms seem OK you can try them out with the updated xboxhdm when I finish that. Should be soon.
Did you try generating a HDD password with LiveInfo using these eeproms and see if if lets you unlock the HDD?
Post by: EthanHunt_IMF on July 25, 2004, 08:31:00 PM
Post by: chimpanzee on July 25, 2004, 08:40:00 PM
| QUOTE (batman00 @ Jul 26 2004, 04:40 AM) |
| i think ldots xboxhdm isnt locking drives right,so you might wanna check hdddriver! |
no. ldots' program get the hddkey wrong only. The locking/unlocking works so long the hddkey or the password is right.
Post by: chimpanzee on July 25, 2004, 08:52:00 PM
| QUOTE (batman00 @ Jul 26 2004, 04:46 AM) |
| chimp what u mean hdd key wrong,dont u lock new drive with hdd key? |
I was confused as well and there is a chance that some of the faile lock/unlock scenario is caused by this confusion.
The HD is locked/unlocked by a PASSWORD. This password is generated from HDkey+HDserial+HDModel. The HDkey is stored in eeprom, the serial and model stored in the HD.
ldots' program(or should be the existing xbox-linux team version) get the wrong Hdkey for 1.2+ box so the password generated is wrong. If the password is given manually, it still works.
Post by: ldots on July 25, 2004, 09:28:00 PM
Post by: chimpanzee on July 25, 2004, 09:38:00 PM
BTW, it may be a good idea to change hdtool to take hdkey(from a file may be) in addition to eeprom and manual password. This way, if there is some tools that get updated faster than hdtool(in getting new hdkey), it would still work.
I would assume that this change still does not work for 1.6 box because of your points outlined previously.
Post by: ImagineMicro on July 25, 2004, 11:00:00 PM
I used evox backup to get an hddinfo.txt file, but using the XboxHDKey to generate a password in liveinfo did not work. Has anyone had success with this?
Will XBOXHDM 1.7 provide a correct password if I input the XboxHDKey?
Post by: YoshiKool on July 26, 2004, 03:19:00 AM
Post by: EthanHunt_IMF on July 26, 2004, 08:49:00 PM
Post by: chimpanzee on July 26, 2004, 08:52:00 PM
| QUOTE (EthanHunt_IMF @ Jul 27 2004, 04:52 AM) |
| Thanks for the info, we know ude 2 work on 1.6's i've done 2 myself... but the issue in this thread is whether we'll be able to upgrade the hd as the old tools no longer work on the 1.6. ConfigMagic doesn't work, liveinfo doesn't read the eeprom.bin. |
Have you tried ldots' new xinfo and see what kind of info coming out of it ? At least it would give us some idea if the location and ways to retrieve those eeprom info is right(most likely this has changed).
Post by: EthanHunt_IMF on July 26, 2004, 09:46:00 PM
Post by: ImagineMicro on July 27, 2004, 04:54:00 PM
| QUOTE |
| Disk Serial Number : "5JRFC1QC " Disk Model Number : "ST310014A " HDD Key : db:34:16:0b:af:a5:7b:c9 72:d5:70:b7:6f:5b:5e:ee 15:8f:50:61:00:00:00:00 00:00:00:00:00:00:00:00 HDDLockDisablePassword db 34 16 0b af a5 7b c9 72 d5 70 b7 6f 5b 5e ee 15 8f 50 61 00 00 00 00 00 00 00 00 00 00 00 00 XboxHDKey 98 6f 19 39 8a a8 20 1c da a7 65 3b 5c c0 42 c3 |
Open up liveinfo and enter the XboxHDKey into the Unique HDD Key field. If you're gonna copy and paste make sure that you take the spaces out in between each set of 2 characters before you paste it inside liveinfo. So what you would paste is this
| QUOTE |
| 986f19398aa8201cdaa7653b5cc042c3 |