Hi, I have a Xbox 1.6. I don't know if it's 1.6b, not sure how to tell or if it is an issue... Ok, so here is the deal. I have a 160 GB Maxtor hdd. Yes, it is lockable, not frozen, or anything else. I ran through xboxhdm 1.9, trying multiple C and E file configurations, and getting the eeprom from multiple sources (configmagic, evox, etc.), and it always runs without a hitch. However, when I change my hard drives out and then turn on my xbox, I get the error that it can't unlock. Yes, drive is locked, I have checked this, checked that. Any suggestions? I have heard of using chimp, but my network is DHCP (don't know if that changes anything) and I don't know anything about telnet, so if you want to help me there, thanks a lot.
Well ive never had alot of good luck with softmods . But here is my findings . With a softmod i dont believe that you can unlock your harddrive then turn it off then be safe . I have personally done this with a 1.6 and it gave me error code 5 . Same as what you are most likely seeing . I used a modchip to fix the problem . i think the reason that the 1.6 and 1.6b's are like that is because there isnt a tsop that you can reflash with hacked bios that allow you to upgrade your harddrive safely . If i am wrong then moderators please tell me so . Im up for new info . But with xboxhdm i generally do the lock feature 2 times just to see that its locked . Lock it once then reboot your pc then relock it again and make sure that it says its locked then try the hd in your xbox . And if that doesnt work then i believe you need a modchip . I hope this helps if not then please post a reply .
chimp doesn't use a network, only 1 xbox. you connect both harddrives to the xbox and run the chimp program from your xbox. haven't used it ever, but what i heard it is easy to use. you can give it a try mmmmm. i now see i replied to a somewhat ancient message (7th july).... a well, maybe someone else finds the information usefull
S10 bringing threads back from the dead... Anyway from my experience you just have to unlock the drive, build or modify the contents, lock it and throw it back in. I always read the confirmation code and i always check the eeprom with live info if i have any issues. Just make sure to check your eeprom with live info and you'll see if it will be successful or not before you attempt to lock it. By the way, you can easily get a fake eeprom by using splinter cell to mod with, i really don't know why but i encountered it a few times already. I used to mod with a old school BOND AUF exploit. Now i use sid5 and still haven't had any issues with drives not locking or fake eeproms.
That's interesting.. because in the development of the eeprom reader I sent 20 or so eeprom files gained from the splinter cell/ndure exploit from 1.0 to 1.6 boxes to the hardware man and every one was good. No problems at all flashing the eeprom with the new data and locking the drive to it. I think the version of live info may be critical.. could the offsets be wrong in other versions or the program basically report garbage? I have hex edited eeprom files before now with the key input from the keyboard again with no real problems other than my incompetence with all things typing related .. I'm suspicious of windoze interfering with the files in some way.. signing them possibly, or region coding them. That would explain the problem of unlocking the drive with the file it has been locked with.. it was locked to that.. If it didn't match the xbox eeprom it would still match the lock data in the file.. what could be the problem??. If this had come up 4 or 5 years ago I might have had the motivation to look into it.
It's an odd problem, and first i suspected the dual boot. Further down the road it turned up that it was almost everyone who modded using splinter cell and a softmod installer of some sort. It must be a certain version out there somewhere or something to do with the code to capture the eeprom. If you click that link you'll see even my old school exploit couldn't pull the real eeprom and they had to unmod the xbox and remod it. It's a really odd problem.
