Print

[kevlar69]

Guys, it has to be possible to save this HD, this is the situation I'm in now;

I'm booting shagged xbox with eeprom embedded bios, and the unlocked HD out of my xbox. I haven't reflashed the damaged eeprom yet though. I have just done an evox bios backup and have the HD key text as follows;

Disk Serial Number : "000000000000        "
Disk Model Number  : "Nikimi NIK-XD600A                       ****PARTINFO****                                XBOX MUSIC      "
HDD Key            : 6e:eb:69:95:bd:73:09:b0
                    94:a6:5d:b3:d0:54:13:4d
                    64:d4:90:5a:00:00:00:00
                    00:00:00:00:00:00:00:00

HDDLockDisablePassword 6e eb 69 95 bd 73 09 b0 94 a6 5d b3 d0 54 13 4d 64 d4 90 5a 00 00 00 00 00 00 00 00 00 00 00 00

XboxHDKey 94 1d 6b 7b 71 51 38 27 32 be 75 72 bf c5 7c 86


The disc model number ' Nikimi NIK-XD600A ' refers to my unlocked drive, but the HDD key is the key to the locked drive ( I think anyway, it is completely different to the HD key my xbox produces with this drive fitted, so must be the key to the locked Samsung 120g )

Now how do I get this key into an eeprom image so I can flash the eeprom and get this drive working again?

How about if I use config magic on my other m8's v1.5 xbox with unlocked HD, alter the HD key in that eeprom, back it up and then embed it in a bios, flash modchip with this eeprom embedded bios and then fit the modchip to shagged xbox?

I can't see why this shouldn't work, anyone?

Kevlar

[triggernum5]

QUOTE

The disc model number ' Nikimi NIK-XD600A ' refers to my unlocked drive, but the HDD key is the key to the locked drive ( I think anyway, it is completely different to the HD key my xbox produces with this drive fitted, so must be the key to the locked Samsung 120g ) Now how do I get this key into an eeprom image so I can flash the eeprom and get this drive working again? How about if I use config magic on my other m8's v1.5 xbox with unlocked HD, alter the HD key in that eeprom, back it up and then embed it in a bios, flash modchip with this eeprom embedded bios and then fit the modchip to shagged xbox?

I don't think you actually need to supply the model/serial as it is reported via ata cmds even on a locked drive and assuming that the versions are correct, I think it should work.  Just out of curiousity, have you stumbled accross any details on the problem eeprommer 0.45 has locking 1.1+ HDDs.  Sounds like you've spent some time searching info out.

[triggernum5]

QUOTE

yep, I've spent hours trying to figure this out, alas I don't know much more than has been mentioned here. Seems I'm still stuck trying to unlock this drive though, it looks like there are 2 keys for each drive, xbox HD key and HD lock key. Config magic will let me alter the former but not the latter. I'm still stumped and it looks like I'll be sending this drive off tomorrow, although I don't think the company I bought it off are going to fall for it, but I'm hopefull!

The reason you can't edit the HDD unlock code is because it is calculated.  The unique HDD key is a code on your eeprom.  This code, along with the drive model/serial(returned by drive),  undergo some algorythms and produce the unlock code.   Rather than bugging with eeprom stuff, have you tried hdunlock.exe/hddisabl.exe with:
HDDLockDisablePassword 6e eb 69 95 bd 73 09 b0 94 a6 5d b3 d0 54 13 4d 64 d4 90 5a
Or atapwd with User Password:
XboxHDKey 94 1d 6b 7b 71 51 38 27 32 be 75 72 bf c5 7c 86

[triggernum5]

Well, they will replace it or send it back anyways correct?

[kevlar69]

cheers Guys

Kevlar

[Evil Ryu]

Glad to hear that everything worked out in the end kevlar69. Excellent learning experience...

[opjose]

QUOTE (kevlar69 @ May 20 2004, 08:15 PM)

My feeling is most online retailers would probably fall for this ( passing off a locked drive as faulty ) as what is their technician going to do? probably connect the drive to his test pc and give up in about 5 minutes trying to figure out whats wrong with it, then send it back to the manufacturer and a replacement to you.

The manufacturer in turn will throw it on the bench just to see why it failed.

They will see that it's locked (and relatively new), unlock & reformat it with their hardware jig and re-sell it.

So no, don't feel guilty. This DOES happen by accident too.

[kevlar69]

You create an eeprom embedded bios and flash it to a modchip. Fit the modchip to shagged box. fit an unlocked HD to shagged box, maybe even a HD that already has evox and config magic on it. if HD is blank boot up xbox with an evox disc, like slayers etc. If HD already has evox on it and is unlocked it will boot anyway. Slayers disc has config magic on it. For the record I didn't use config magic in the end to flash the eeprom, I used eeprom magic which I installed on the HD in my xbox before fitting it to shagged box.

Kevlar

[mackjack]

awesome thanks!!!  It worked... but now i have 1 last question...  I ran another program... and it corrupted my eeprom again!  Is there anyway to write-protect the EEPROM?  and will this interfere w/ any xbox functionality?

[kevlar69]

QUOTE

still dont know what did it, so i took it fixed it with the backup eeprom. and i just lifted pin 7 on the eeprom and shorted it to pin 8 to make it write protected, and its been fine ever since.

Haven't tried this or read this anywhere else so would confirm this with Lugnut or other Xperts  before doing this.

Kevlar

[mackjack]

Hmm.... OK... Which chip is the EEPROM and how do I determine what pins are 7 and 8?

[mackjack]

lugnut answered my questions in another post.... here's the link he gave.  Thanks again lugnut!

http://lugnut.150m.com/eepromlock/

[anu|b|iss]

had the same scenario. only I flashed the EEPROM and it still flashes RED with the modchip off.

weird thing, configmagic always said invalid version specified.
so I used EEPROMER
that flashed it, I didn't reboot but then tried configmagic and it picked it up.

I shut the xbox down. startup without the chip. still bad/corrupt EEPROM.

I am guessing (but would like confirmation) that the EEPROM chip is faulty and will need to be replaced?

[Evil Ryu]

Hey mackjack,... just wondering if you ever got that eeprom write-protected? I was just wondering if you have to lift pin 7 and send it to GND or 3.3v to have it write-protected? According to kevlar69's post, you lift pin 7 and short it to pin 8 (3.3v), but I just wanted to find out if this actually worked...

Thanks