shauno5

I had a closer look, no points have been bridged, so I guess its stock then. Since I can't softmod/TSOP flash, I guess a modchip is my only option. I was my last resort option as I don't want to stuff my working xbox, but Ill try and move the modchip from my working xbox over to this one. Not confident with this as I haven't done it before, but it will give me something to learn. Theres no way to TSOP flash via the LPC header pins is there?

No text at all. It just hangs for 5 - 10 seconds at that point and then goes to E16. All the files are there as well on C, 167MB.

I rebuilt the HDD with FATXplorer, using clean C and E folders which include xboxdash.xbe, but still getting Error 16. I tried all the different partition options as well to no effect. I'm not even sure what kind of modified BIOS could be on this machine, theres no EvoX logo on the flubber screen, so not sure which dashboard it could be looking for. I just presumed it is running something other than stock BIOS as it's not complaining about an unlocked HDD.

So, finally able to give this another look. Thanks for all the advice so far, checked with smartctl.exe and can unlock and lock with the eeprom.bin that i've written to the xbox. Thanks, yeah, performed this to unlock the HDD and remove password so I then was able to mount it with FATXplorer. This led me to by accident put in an unlocked HDD into the troublesome Xbox and actually got something I didn't expect -- Error 16, and I expected Error 05. Could this mean that the xbox may actually already be TSOP flashed, and expecting an unlocked HDD?

My guess is something to do with the HDD(s) as I've verified the EEPROM now has all 1s and should be ready to go with an all 1s HDD. Even though I checked my HDD and it unlocked with 1's, I guess there's a lot of variables and things that can to wrong with USB adapters, old drives etc.. I'm going to try a build again with a brand new SATA drive as soon as I get a SATA adapter and cable. If that fails then I guess I'll try and move the modchip over from my other board and see how that goes.

Yeah I should clarify that. The target Xbox i'm trying to build a HDD for never had a matching HDD in it to begin with when I acquired it.

So the Xbox i'm trying to put the drive into has no mod, just a re-written EEPROM with all 1's. The Xbox I used to build the drive was actually a hardmod (so I could boot the tools disk to build the drive), and then use the Null EEPROM tool to lock the drive to all 1's. It also set the password to "TEAMASSEMBLY" I believe. Then I verified it booted into a softmodded xbox which had a nulled 1's key and it loaded into the dashboard. Also unlocked successfully on FATXplorer so I knew it accepted an all 1's key, and relocked. Then when I put the drive back in the EEPROM edited xbox from step 1 ... E06. I might just look into the TSOP process instead though. A couple of questions: 1. Can a hardmod or TSOP flashed xbox boot into a locked drive? 2. Whats the relationship between the HDD key and the password? Im a bit confused about this. Does a stock xbox need a password as well as a HDD key?

Tried the drive on PC with a USB IDE adapter (startech brand). Security tools found and unlocked fine using all 1's. However when I went into build tools I get "Media not loaded. Might be locked", and I can't mount it either to view files. Maybe i've got a bad IDE adapter (i've heard they are hit and miss). Thats why I preferred to build with my existing modded xbox using utils disc. I'm going to try and find a larger drive anyway to do a fresh build and see how that goes.

Ah my mistake it wasn't XboxHDM exactly, it was Heimdall's Xbox Engineering Disk on TruHexen 2021, using the 3.5.4 New Disk > PAL Xbox option, after which the drive was nulled with 1's and locked, which I thought would be sufficient.

Double checked that and 32 1's. I wrote them myself in the LiveInfo utility.

Hi all, Hoping to get some help on this one as i'm really stumped. Problem: I'm restoring an Xbox and trying to get a fresh built HDD paired with a motherboard using nulled (1's) key, but still getting E06. Steps I've taken: 1. Built a fresh drive using XBHDM, locked the HDD with all 1's, and verified it boots correctly into a working soft modded xbox with nulled HDD key in the EEPROM (all 1's). 2. Read the EEPROM of the target motherboard using PiPROM, edited the eeprom.bin file to null the HDD key with 1's and written this back to the EEPROM. 3. Read the EEPROM again and verified its indeed now all 1's in the HDD Key. 4. Installed the newly created and locked HDD from step 1 into the target motherboard. 5. Error 06 Other info that may or may not be relevant? * HDD i'm building is an original 8/10?GB Seagate drive, but i've also tried two original WD drives in step #1 and the same issue arises. * Target motherboard revision is a v1.1 Any ideas whats going on here?