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

Ghengis · « **Reply #30 on:** July 22, 2004, 03:37:00 PM »

::sigh::

I hate looking like such a newb. Of course, it had not been signed, and I stupidly thought it just came that way (or something). Fixed it after a brief irc chat at #xbins-help, and CM gave me the correct HD key, so hopefully the eeprom dump is right (e.g. different) as well. Will give it a shot momentarily.

SargeZT · « **Reply #31 on:** July 22, 2004, 03:48:00 PM »

Rice: Exactly what would you be trying to accomplish using HPA?

big_pimping25 · « **Reply #32 on:** July 22, 2004, 04:40:00 PM »

any luck Ghengis?

RiceCake · « **Reply #33 on:** July 22, 2004, 04:47:00 PM »

SargeZT, just to have a secured area for backing up my PC and storing critical data.

My PC not my Xbox - lol...

Ghengis · « **Reply #34 on:** July 22, 2004, 07:17:00 PM »

OK, so the wierdness continues.

A.) ldots, if you're still reading this, I have a bug report/incompatibility to alert you to -- it might be out of your hands, but hey, doesn't hurt to try. I have an Asus P4P800 Deluxe, which means the usual 2 IDE channels plus two SATA hookups. To get them all running, you use "Enhanced Mode". Windows XP speaks this just fine, but apparently iso-linux not so much. When I had it on, it kept getting confused and trying to disable a certain IRQ -- at first it was 11; I disabled that and it started on IRQ 5. Rather than play fingers-in-the-dam, I thought it might be all those ide devices. I was right. I turned it back to "Compatibility Mode" (no SATA) and it was fine. So, might at least be worth a 2-line note at the end of the readme.

B.) I've got a pretty good picture of the problem. ConfigMagic dumps the same BIOS file (AFAIK -- don't have a binary version of diff handy to test for sure but it prints identical in wordpad) as Evox, and when I load either eeprom file in liveinfo, it makes the right key. That is, the liveinfo-generated key matches the hddinfo.txt and eeprombackup.txt files. The linux tools (xinfo, etc) appear to read the eeprom.bin file incorrectly. The listed Unique HDD Key (which, as I understand, is from the EEPROM, not the hard drive, and thus a bit of a misnomer) matches the text files in windows, but is completely different in Linux. No idea where it's getting the values from.

I am unsure how to proceed -- I'm considering locking by hand, generating the new key here in Windows then locking in DOS, but I'm a bit scared because I don't own a working floppy drive to save logs with. If only the DOS utils had FTP support... I'll try to figure something out...

Ghengis · « **Reply #35 on:** July 22, 2004, 08:49:00 PM »

OK, had I thought it through a bit more clearly, I might have tried the lock tools from linux, but WWWWOOOOOOOTTTTT!!!!! I got it working with the DOS tools. Hair-raising, sure, but it's done.

BUT.... there's always a fucking but. There's an F drive, and I think maybe even a G drive, in the FTP listing. But they're both empty, I can't create directories in them or send files, and they show some unreasonably large capacity (787 gig or so). Tried formatting both with formatdrive (harddrive0\partition6) and evox (format f:).

Is there any way I can fix the partition table here without hotswapping or redoing the lock-with-my-fingers-crossed thing? I mean, I *should* be able to use the whole 80 gigs without changing my bios, right? Did I miss something important?

Ghengis · « **Reply #36 on:** July 22, 2004, 09:02:00 PM »

I can script the command to use the password from a file instead of hand-typed from the console. You live, you learn. If there's a next time -- and, if you read the above message, there may well be -- I'll do it from linux.

dabbage · « **Reply #37 on:** July 22, 2004, 11:11:00 PM »

just to make sure noone else has the same impression as you, genghis:

hdtool in linux offers several big advantages over the dos tools

- master password (can recover drive if you enter the wrong password)

- ftp access (you can even directly connect to your xbox and get the eeprom.bin)
- hd access (mount your ntfs/fat partition)
- cdrom support
- open source and current, ldots already extended it quite a bit

etc.

chimpanzee · « **Reply #38 on:** July 22, 2004, 11:13:00 PM »

I still don't get it, what is the cause of this "broken" concern ? Have it been found ?

RiceCake · « **Reply #39 on:** July 22, 2004, 11:40:00 PM »

Yeah its believed to be a bad EEPROM dump through EvoX.

Ghengis · « **Reply #40 on:** July 22, 2004, 11:54:00 PM »

Rice, I'm not so sure. LiveInfo pulls the info out just fine. I used it to generate a key for a new HD (80 gig upgrade) and it works fine. So, Evox had a fine eeprom, or else it messed it up, and liveinfo messed up reading it just so that the error was cancelled out. I'm going to call the latter case "unlikely", which means the linux tools are fuxored.

ldots · « **Reply #41 on:** July 23, 2004, 04:18:00 AM »

Thanks for reporting this "unlikely" incompatebility Ghengis.
Hmmm - that sucks! The bug is probably not in the locking tool but in the eeprom decryption or HDD password generation.

Could you do one more test that would help out. Ftp my memcard UDE installer to your xbox and run the backup option. Then ftp the E:\backup_linux folder to your PC and compare the hdd_info.txt output with the output from ConfigMagic/Liveinfo.
Doing it this way the eeprom would be read by the linux tool right from the mobo and not from a file.

Also send you a PM.

chimpanzee · « **Reply #42 on:** July 23, 2004, 04:26:00 AM »

ldots · « **Reply #43 on:** July 23, 2004, 04:37:00 AM »

Yup, and xbox_tool has been working fine for a long time producing correct passwords. But that doesn't mean there is a small bug that only shows itself in rare cases. It would really surprise me though!

Maybe Ghengis' HDD is reporting a wrong model and serial number (which the password generator needs). That could also be a PC/Bios issue. Actually that's more likely since unlockhd didn't work on the stock HDD either.

Ghengis, would it be possible for you to try out xboxhdm on another PC ?

Edit : To anyone reading this. This doesn't mean you could give the linux locking tools a try if you are upgrading your HDD. Even though a wrong password should be generated you should still be able to unlock the drive again with unlockhd, or in the worst case scenario using the master password with atapwd.

YoshiKool · « **Reply #44 on:** July 23, 2004, 07:09:00 AM »

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