Topic: Xboxhdm's New Mode 3 Broken? (Read 376 times)

ldots · « **Reply #45 on:** July 23, 2004, 01:21:00 PM »

Dont think so. And I still feel they are safe to use. Remember Ghengis had no problems unlocking the drive again.
More testing is needed to find out whether it's was caused be the eeprom, the PC bios, the PC itself, the harddrive, the locking tools.

total_ass · « **Reply #46 on:** July 23, 2004, 02:50:00 PM »

how many people have had success with the automatic locking tools?

Ghengis · « **Reply #47 on:** July 23, 2004, 08:21:00 PM »

OK, just to set things straight:

One: there is no apparent danger from the malfunctions I'm describing. As Ldots indicated, the tools always generate the same password for a given drive, so no problem. If I accidentally lock with the wrong one, I can always run the unlock command to use the same (wrong) password.

Two: I would like to emphasize that I can see the plain-text, presumed correct (since LiveInfo generated the correct PW for both of my hard drives using it) HD key in the hd text files generated by both CM and Evox, and that when I run the linux tools to examine the eeprom.bin file created by either of those apps, they display the HD Key (supposedly from the eeprom.bin file) and it does not match. So, the generation algorithms are probably fine, and I think it's reading the serial numbers correctly in all cases as well (so not an issue with my PC BIOS).

The heart of the issue is that LiveInfo can read the eeprom.bin files correctly, and xinfo (for instance) cannot. I'm pretty sure that if I had a linux tool that I could pass a hand-typed HD key to and have it spit out a password, that would work fine. It is only the part where the HD key is extracted from the eeprom.bin file that seems to be broken. The one thing I have not checked is whether every time I try to read the eeprom.bin under linux, it gives the same (wrong) value.

I have tried it on two completely different computers and have the same problem for each. I'd be interested to know if anybody else with the exact same xbox as mine (see my sig) has gotten this to work.

I will try downloading the UDE installer later tonight, or tomorrow. If I get any different results, I'll let you know. This thing has been driving me crazy, and I'd hate to put anybody else through what I've had to deal with.

chimpanzee · « **Reply #48 on:** July 23, 2004, 08:38:00 PM »

RiceCake · « **Reply #49 on:** July 23, 2004, 09:57:00 PM »

Bottom line is we dunno. Something went wrong, might've been a bad EEPROM dump or some glitch...

ldots · « **Reply #50 on:** July 25, 2004, 09:03:00 AM »

As I expected the problem was the decryption of the eeprom. The linux guys came up with a brilliant way of decrypting he eeprom without using the copyrighted eeprom key (friday 13th attack), but in the xbox_tool and the hdd locking tool this part of the code was a bit outdated (it worked perfectly for v1.0 and v1.1 xbox's).

I assumed that the xbox-linux kernel (cromwell) would be working on v1.0-1.5 xbox's and therefore re-did the eeprom decryption of the hdd locking and info tools with this kernel as a reference. That seems to have solved it.

Hopefull Ghengis will test out the updated tools, and if all is well I will update xboxhdm.

So, if you have a v1.1+ xbox dont trust the hdd password produced by xboxhdm until version 1.8 is released.

chimpanzee · « **Reply #51 on:** July 25, 2004, 09:49:00 AM »

ldots · « **Reply #52 on:** July 25, 2004, 09:57:00 AM »

I'm gonna post my view on this in that thread in a moment, Might not nessecarely be xbox_tool (in my updated version) that is the problem.

ldots · « **Reply #53 on:** July 25, 2004, 11:13:00 AM »

Expect the xboxhdm update soon.

ldots · « **Reply #54 on:** July 25, 2004, 11:39:00 AM »

Just wondered why you posted that question after I announced that the tools had been fixed?

total_ass · « **Reply #55 on:** July 25, 2004, 12:52:00 PM »

cool man, do you have an idea of when version 1.8 is gonna be done, or in the words of bungie

'it will be done when it is done'

lol.

ldots · « **Reply #56 on:** July 25, 2004, 01:33:00 PM »

Yes. If a wrong HDD password should be generated you should still be able to unlock it again with the linux tools.
But 1.8 should be ready soon. Just waiting for Ghengis to test them with his "problematic" eeprom.

batman00 · « **Reply #57 on:** July 25, 2004, 03:42:00 PM »

ill test it for you ldot?

Author Topic: Xboxhdm's New Mode 3 Broken? (Read 376 times)