Print

[mars0124]

So I can't make head or tales of this situation.  I know it must be something simple that I am missing, but for the life of me I can't figure out what.

I have a v1.0 XBox with retail 10GB HDD (softmodded) which boots just fine.  I have copied my EEPROM backup  + C + E to my desktop via FTP and have them burnt to a xboxhdm 1.9 CD.  I have two supported drives (one SG and one WD, both 500GB) which when I create an HDD from scratch (or clone unlocked retail drive) and lock (with either EEPROM or manually typing the password) give of error 07 when trying to boot in the xbox.

I tried flashing the BIOS via TSOP except considering my soldering skills and the burn mark on my mobo, it is a miracle the machine even runs.

Aside from a modchip (trying not tot put more money into this), what are my options?  Any genius' out there that might point out the flaws in my attemps and get me up and running?

Also, I have a second xbox (unknown version) that I will be doing the same too with the second drive afterwards.

Thank you all in advance for your help.

George

[Bomb Bloke]

Error 07 means the system simply can't access the drive. Usually it means the drive is actually dead, but since your PC seems happy enough with it, I'd guess you're either somehow connecting the IDE cable incorrectly, or you've got the cable jumpers in the wrong position (Cable Select should do it).

Another vague possibility is that your console's PSU isn't up to the job. To test that, have your PC power the drive while the X-Box's IDE cable is attached.

[Heimdall]

It sounds as though error 6 is your real problem, and the disk has been locked with the wrong eeprom. Just to confirm, open the eeprom with LiveInfo and check that the serial number matches the one on the bottom of your Xbox.

To get a good copy of the eeprom, bypass your softmod virtual eeprom (Krayzie extras, Kingroach E:\ndts\default.xbe, for other softmods cold boot with Frosty's Rescue disc) then take a fresh eeprom backup with Config Magic or Evox.

Unlock the disk with your current (wrong) eeprom, and relock it with the good one.

[Bomb Bloke]

Indeed, the drive should be set to pretty much anything but slave.

[Heimdall]

QUOTE(mars0124 @ Sep 7 2009, 03:26 PM)

The idea that it could be a bad eeprom seems odd to me though.  I tried backing it up with EVOX and with Forrrest Tools, and one other that I can no longer recall.  And, as mentioned, I tried locking it manually (unlockhd -p) using the password as told by eeprom backup/system info from one of my dashboards.

Backing up the eeprom if you have virtual eeprom enabled only backs up the virtual eeprom, which is read from a file on the disk, not from the actual eeprom. If you took your softmod files from another Xbox with an existing eeprom.bin backup then all you are doing is taking another copy of the eeprom from the other Xbox.

Manual locking with the password from the stock disk won't work either, because the password is specific to the disk you are locking - it is a mathematical combination of the disk serial number, the disk model number, and the HDD key from the eeprom.

[Heimdall]

QUOTE(Heimdall @ Sep 7 2009, 01:11 PM)

To get a good copy of the eeprom, bypass your softmod virtual eeprom (Krayzie extras, Kingroach E:\ndts\default.xbe, for other softmods cold boot with Frosty's Rescue disc) then take a fresh eeprom backup with Config Magic or Evox.

But check the serial number on your copy of eeprom.bin with LiveInfo. If it unlocks and locks your retail hard drive then it must be the right eeprom, so it is more likely that your problem is finger trouble.....

[mars0124]

Should I bring my XBOX back to a completely retail/unmodded state and build from the ground up, do you think?

I was just looking at the prices of a modchip and realized that I am willing to put the hours into this - but not the money (that is already invested in the HDD).

Thanks again.

[mars0124]

So I went ahead and wiped the drive clean, reinstalled MS-DASH, and then soft modded with NDURE...  Checked the eeprom again: I am using the proper one after all.

In the event that I am an idiot, I will write the process I went through to lock the drive:

• Copy C + E content to PC via FTP from AutoInstaller Deluxe after disable virtual C. (If I put virtual C on xboxhdm, would I get an error after rebuild? What would it be?)

• Copy eeprom from E:\backups from NDURE process.

• Build xboxhdm disc - burn to DVD.

• Boot disc and build drive from scratch.

• Reboot again to lockhdd from eeprom (sucess verified via repeating steps after reboot).

• Place drive in XBOX.

• Receive error 06 (or 05 if I left unlocked for troubleshooting purposes).

I hope I missed something simple - please call me out and then call me an idiot if I did.

George

[obcd]

No, you shouldn't start over again.
Error 6 simply means that the harddisk was locked with an incorrect password.
It has nothing to do with the contents of the harddisk.

So, you can lock / unlock the stock disk fine. What tool are you using to do it?

Have you checked the eeprom.bin file with the liveinfo beta 3 program in windows?
You can verify the serial number and it can even give you the harddisk password if the harddisk is connected to the pc.

As was mentionned before, the harddisk password is calculated from the eeprom hddkey and the harddisk model and serial number. So, every xbox uses a different password and every harddisk gets a different one.

What softmod did you use on your stock harddisk? What dashboard are you using?
Any chanche you have a ndts folder on your E partition with a default.xbe in it?

I remember somthing like an EEPROM_off.bin file in the root of the E partition or the NKP11 folder. The contents of the file aren't important, and you need to reboot the xbox after you created (ftped) the file.

regards.

[obcd]

Looks like my previous message came to late.

So,

You can unlock the stock xbox drive with your pc and the xboxhdm lock / unlock option? and,

If you lock the other drive with that same xboxhdm cd, the xbox greets you with an error 6 error screen?

What are you using to backup the xbox eeprom?

You can do it with the evox dashboard.
You can do it with a special tool xman954 created.
You can do it with the configmagic program.

In all cases, the virtual eeprom needs to be disabled.
You can do that with the default.xbe in the ndts folder or by creating an EEPROM_off.bin file.

regards.

[mars0124]

That's right - I can unlock/lock the stock drive with xboxhdm, but I get error 06 if I use the same disc on the other HDD.  Same results if I use ConfigMagic and hotswapping drives.

In some of my earlier posts I list what I try to backup the eeprom with - most recently the NDURE SplinterCell save.

Can you tell me more about eeprom_off.bin?

I've seen a number of mentions of the ndts folder.  What tool is that, and how can I get it?

[mars0124]

Ah - OK its for NDURE 3.0 +.  I was using... 2.1 I think, from some SplinterCell saves.

I'll post a little later on my results when I try the eeprom_off.bin

As for how I am locking the HDD, I have tried two ways that have worked.
ConfigMagic Way:
Boot XBOX, select ConfigMagic from apps, once booted hotswap HDD (have external power for 2nd HDD) and once detected try to lock.
XBOXHDM Way:
Insert unlocked drive in PC, boot xboxhdm, lock HDD with 'lockhd -a' (eeprom on disc).

I realize that neither of those methods mean a thing if I am dealing with a virtual C/eeprom through.  Will post again soon.

[mars0124]

OK... sorry that I have dropped the thread.  My issue was not resolved, but I had to prepare for a move: thus my disappearance.  Well - move never happened, and I am able to get back to it again.

I've been making assumptions along the way, exchanging tools for others that have a similar function, etc... Obviously I don't know what I am doing, otherwise those assumptions would have ended in my not needing help.

Soooo....

Can someone point me to a good softmod HDD upgrade tutorial?  I can google then I want and assume that I am getting the right one, but I would rather ask what you guys think.

This XBOX was originally intended as an early b-day gift: Deadline - November.  If anyone can save my rump in this case you will have my eternal gratitude in a written form (rather than the usual disappearance without thanks after satisfaction).

Thanks

[Bomb Bloke]

My personal method is:

1) Flash the system TSOP, hence granting most of the perks of a modchip.
2) Delete all traces of any softmods.
3) Throw in the new drive, and proceed without ever worrying about drive locking again...

With a 1.0 system, a valid BIOS for flashing is the X2 5035.

Though now that I think about it, that's odd... 1.0 systems shouldn't provide error codes on the "contact customer service" screen...

Alternatively...

[mars0124]

So...

Here I am again.  I tried NDURE 3.1, which got me further then before but I was still having problems.

I decided to opt for the simplest method which I had not considered before, which was doing a bit by bit ghost transfer from drive to drive.  Short version: it worked great.

Thanks for your help everyone, you've all been great.