Print

[Boontis]

The problem I am faced with is I have installed a Duox2 (Cromwell edition), flashed it with an M8 67 bios (my xbox is v1.0). Booted with the original HD and a Slayer’s disc (2.6 if it matters) and backed up the C and E drives.  Then I replaced the original HD with a 200 GB Samsung.  Now I will mention that I did something different then usual at this point.  To save time I formatted and installed the slayer’s apps and such onto the HD with slayer’s on another xbox while I was installing the modchip on this xbox.  Then I installed the 200 GB HD into the xbox being modded and error 13 comes up. So I boot with the slayer’s disc and what is showing for remaining memory is all 0’s (C, E, F, G) .  So I try reformatting and installing the software: reformatting does nothing, 0’s still across the board and when I reinstall the software it says done within seconds of starting, instead of a good 10min of copying.  

Curiously enough, I put the HD into my other modded xbox to see if the HD is to blame.  It boots to Evox no problem and displays that there is plenty of HD space left.  

This leads me to believe that it is the modchip to blame, though I realize that 99% of the time it isn’t the modchip.  So I double check the voltages of the LPC – ok, I know that it is not my D0 or it wouldn’t boot the modchip’s bios.  So I desolder the pinheader and reinstall it to make sure this is not the problem.  The same thing happens, boots, runs fine with the Retail HD, will not work with the 200GB HD.

I noticed that when I boot the Flash Bios in bank 1 of the cromwell it display a message saying that only the first sector could be read when accessing the HD, yet after formatting this message stays.  

So I was thinking of unlocking, formatting on my PC, then reformating on the xbox.  But I don't know how much help this will be.

Any help would be immensely appreciated.

- Boon

[Boontis]

Update -- I flashed the chip with X2 4981.67 FC evox 512k to make sure it wasn't the bios.  This somewhat worsend the problem.  Now whether I try to boot with or without the Slayer's disc in, it gives me error code 6 which I have found on HackDaBox's site to be 6 - kernel - Cannot unlock HDD.  This I don't get, I thought there were only problems with HD's when they couldn't be locked, not unlocked?

I'm starting to think that its a problem with the HD being a samsung, I dunno.

[Boontis]

[HackDaBox]

OK so now you know that a hard drive must be locked so the normal ms bios can boot. but if you want to remove the harddrive and put it in another xbox or a computer you must unlock it first on the xbox that locked it.

Not all harddrives can be locked maybe your samsung has issues with locking and unlocking. You still seem to have more problems than just the locking / unlocking issue though.

Slayer's can Lock and Unlock easily ( supported harddrives only ) from the hard drive managemant menu

www.HackDaBox.com

[Boontis]

Thanks for all the help!