Transferning Eeprom Keys Options

[AucardThe3rd]

ok first let me say its been a long time since i have done xbox modding so if i seem rusty please excuse me. with that out of the way on to the topic. i recently had a softmodded xbox (hardware 1.0) die on me. the hard drive is fine the issue is with the motherboard. i have a perfectly working xbox (hardware 1.6) just no hard drive. now i want to transfer the hard drive from the old to the new. now i know that i have to unlock the old drive, but i want to know. is it possible to just change the eeprom key on the drive (which is for the 1.0) to the current one? i just don't want to go through the process of rebuilding the drive from scratch and reload all programs, games, etc.

note: the xbox (hardware 1.6) was at one point softmodded and i have a backup files of that drive so i have access to the bios, eeprom, etc.

[ldotsfan]

Check my sig - you can adapt the key zeroizing concept to your situation. Change target xbox key to match source hdd. The softmod needs to use generic - kernel version neutral fonts too.

I gave similar advice in this post: http://forums.xbox-scene.com/index.php?s=&...t&p=4735214

[AucardThe3rd]

thanks for the info, i took a look at it, and i'm nor sure if this will work for me. right now i don't have access to the drive from the xbox that died, i was thinking i need to unlock it first then see if there was a program that i can use on my pc to access the drive then replace the contents of the folder that contains the eeprom, bios, hdd key, then lock it after with a new hdd key (that was from the 1.6 box that was softmodded at one point) but config magic is only usable from the xbox dashboard. i was thinking that i could use xplorer360 to view the contents of the drive and copy over the the bios, epprom, hhd key of the 1.6 box on to the drive, then lock it after and in theory should be good to go. (this post may sound noobish)

This post has been edited by AucardThe3rd: Sep 14 2010, 02:34 PM

[Passerby]

I've also got a 1.0 Xbox with a janky motherboard, and was going to post a thread asking how to make xboxhdm's floppy boot disk unlock my current hard drive and lock it to the hdd key of a second Xbox I haven't bought yet. Using ConfigMagic to change the second Xbox's eeprom to accept the original hard drive sounds a lot more convenient, but I'd just like to clarify the procedure:

1) Softmod the second Xbox and backup the second eeprom and hdkey info just in case.
2) Disable the virtual eeprom.
3) Copy ConfigMagic to the hard drive of the second Xbox.
4) Unlock the second Xbox's hard drive using ConfigMagic.
5) Change the hdd key of the second Xbox to the key of the first Xbox (the 32-byte string contained in hddkey.bin in my original backup), selecting "UPDATE XBOX EEPROM" to finalize the change.
6) Lock the second Xbox's hard drive to the changed key (might as well).
7) Shut off the second Xbox, then insert the first hdd into the second Xbox.

If I follow the above steps, will the second Xbox work normally with the first Xbox's hdd?

[xboxmods2977]

AucardThe3rd

So, you have a dead 1.0 with a good HD, and a good 1.6 with no HD? and you want to combine what you have to make a working xbox? This is not going to be easy no matter what route you take.

If you change the eeprom stored on your hard drive in the "backup" folder, this will not magically lock your HD to a new eeprom. It is there for backup purposes only.

When an xbox hard drive is locked or unlocked by the xbox, the key used is taken from the xbox motherboard. This is why you need to take the eeprom (or at least the HD key) from the 1.0 xbox and write it to the new xbox motherboard (making the 2 xbox boards "clones"), so that when your HD is installed in the 1.6 xbox, the bios will read the correct key from the 1.6 board (because you put it there) and use it to attempt to unlock the HD, which will be successful.

Also, the eeprom contents of the 1.6 are useless in this situation because your 1.0 is already dead and the xbox HD is locked, however, it could be useful if you have spare HD laying around to temporarily use to resurrect your 1.6 just long enough to softmod it and change it's HD unlock key (eeprom) to match that of the 1.0's, and then you could put the 1.0's HD into the 1.6.

To save yourself from a lot of headache, build or buy an eeprom reader. This will make what you are trying to do much easier.

[ldotsfan]

1) Softmod the second Xbox and backup the second eeprom and hdkey info just in case.
2) Disable the virtual eeprom.
3) Copy ConfigMagic to the hard drive of the second Xbox.
4) Unlock the second Xbox's hard drive using ConfigMagic.
5) Change the hdd key of the second Xbox to the key of the first Xbox (the 32-byte string contained in hddkey.bin in my original backup), selecting "UPDATE XBOX EEPROM" to finalize the change.
6) Lock the second Xbox's hard drive to the changed key (might as well).
7) Shut off the second Xbox, then insert the first hdd into the second Xbox.

If I follow the above steps, will the second Xbox work normally with the first Xbox's hdd?

a. At the point of backup for step 1, virtual eeprom should be disabled so that the backup is a good copy of the eeprom. Backups should be stored offsite - meaning off the console and on your PC and before any changes via ConfigMagic.
b. Step 6 is not a "might as well". It is mandatory. Otherwise the softmod will not be able to boot off the second xbox's hdd and console will boot to a rude error 5.
c. Softmod fonts should be kernel version generic - meaning even if second xbox isn't a version 1.0, it shouldn't matter. You have to check this yourself since you didn't mention which softmod is being used.

[Passerby]

Backups should be stored offsite - meaning off the console and on your PC and before any changes via ConfigMagic.

That's what I meant when I said backup the second Xbox's eeprom: copy it to my computer alongside the eeprom of my first 'box.

Step 6 is not a "might as well". It is mandatory. Otherwise the softmod will not be able to boot off the second xbox's hdd and console will boot to a rude error 5.

The point of all this is to take the 320 GB hdd that I installed in my original Xbox, who's motherboard is now wonky, and plug it into a second, working Xbox. I guess it'll be nice to have a stock hdd to use if the big one dies or something.

Softmod fonts should be kernel version generic - meaning even if second xbox isn't a version 1.0, it shouldn't matter. You have to check this yourself since you didn't mention which softmod is being used.

I'm using Krayzie_MA_Ndure_Installer_v1.0. As for the second Xbox (which I bought today), I haven't been started the softmod process yet, but the manufacturing date sticker on it says July 24, 2002. It's probably somewhere between 1.0 and 1.2.

I left some details out in my other post, and I apologize for any confusion. Your consideration is greatly appreciated, and it looks like I won't have any problems, but I'll be knocking on wood with all my fingers crossed anyway. Thank you very much.

This post has been edited by Passerby: Sep 27 2010, 03:04 AM

[Heimdall]

Use Krayzie 1.1.1. It's newer, with a couple of minor bugfixes and improvements.

[Passerby]

If I've already run 1.0, if I copy 1.1.1 onto my softmodded system and run that normally, will it install properly over its older version? Never mind that, I see Krayzie 1.1 has an "Update from 1.0" option.

There were two problems with the whole procedure:

First, the virtual eeprom was not disabled when I thought it was. I put an empty file called EEPROM_off.bin (that exact capitalization) in E:\ and E:\NPK11 as described here, however when I used ConfigMagic to change the eeprom the change only went to the virtual one. I locked the hdd to the changed eeprom and rebooted to an error 06. I've since re-locked the new hdd to the eeprom I saved when I first modded it, and it works properly, so I know the actual eeprom never got changed.

Second, the larger hdd, a Seagate ST3320620A, would not unlock. I checked the password several times and I know I had it written down correctly. Of the programs on the XboxHDM 1.9 boot floppy, unlockx said "drive will not unlock" and hdunlock and hddisab both said "device not ready" when attempting to unlock the drive. Hdlock said it successfully locked the drive to the new eeprom when it really shouldn't have been able to, and I still got an error 06 when using the drive in the Xbox afterwards. I can only guess that it's still locked to the first console's eeprom.

Basically, I've got a working modded Xbox with a stock hdd and all my old data inaccessible. If I can be certain that the virtual eeprom is disabled, I can change the eeprom to work with the big drive, but I'm better off now than I was before.

This post has been edited by Passerby: Sep 28 2010, 02:58 AM

[Heimdall]

Lower case eeprom_off.bin goes in E:\ for Krayzie 1.x softmods. Alternatively you can run Krayzie extras (E:\Apps\Extras\default.xbe), then select Launch Extras - Professional Mode, and run Config Magic from there.

[ldotsfan]

Assuming big hdd was formatted with xboxhdm, boot option 4 - ATAPWD and password XBOXSCENE will unlock it.

[AucardThe3rd]

well just a fyi i got it working!!! ok heres what i did, i made 2 bootup disk

1. disk made with xboxhdm v1.9 (made for my xbox that was 1.0 hardware, but is now dead)
1. disk made with xboxhdm v1.9 (made for my xbox that is 1.6 hardware)

Note both xbox were softmodded at one point so i already had backups of there drives on my pc

i then unlocked the hard drive from the 1.0 box, shutdown the pc, then switched cds and booted up my computer with the 1.6 disk locked my drive, put in my box and started it up. and it worked perfectly can play my games do everything i can do normally i was never able to get the evox dashboard to display at 720p properly but oh well lol.

[xboxmods2977]

Cool.