XboxHDM 2.2 (USB Edition) Options

[spliff721]

ok. i have now upgraded to an 80g hdd. had a little trouble locking it whith xboxhdm2.2, but after searching for a bit through the posts here i found a link saying to plug the ide into the xbox after POST. i wasnt fully sure what this ment so through trial and error i found that after choosing xboxhdm2.2 on the usb, wait till the screen pauses for the first time for 3 seconds or so and i pluged in at that time and i stoped getting the "drive is frozen" error. the drive locked and booted to M$ dash after i pluged it back into the xbox. i then proceeded to mod it through the same splintercell exploit i found on the SID disk. thanx again to everybody for all your help. marry christmas!!!!

This post has been edited by spliff721: Dec 15 2010, 08:08 AM

[robot3]

I was using the 2.2 version and I keep running into a bug. If this was mentioned already than I did miss it.

this bug showed up on both 2.1 and 2.2. I had a virgin 500 gig WD hdd. The xboxhd program worked fine and it formatted the drive (used my existing xbox eeprom). The issue I was having is that whenever it got to the step to copy files off the usb, it gave me an error message saying it could find any files on the -c or -e and to reinsert the cd. I found this odd since i am using the usb version. It then ask you to hit enter, so I did and it gave the same error again. At this point though the xboxhd app at the end of the message listed this

"possible bug?"

Has anyone encountered this before or know how to get around it? In my case I ended up going to the Xbrowser and the files it said it could not find where obviously there and I just did some copy/pasting, but it would save tons of time if this USB version copied the files over itself. Any ideas on what might have caused the odd bug?

This post has been edited by robot3: Dec 16 2010, 07:23 AM

[scullc]

ok. i have now upgraded to an 80g hdd. had a little trouble locking it whith xboxhdm2.2, but after searching for a bit through the posts here i found a link saying to plug the ide into the xbox after POST. i wasnt fully sure what this ment so through trial and error i found that after choosing xboxhdm2.2 on the usb, wait till the screen pauses for the first time for 3 seconds or so and i pluged in at that time and i stoped getting the "drive is frozen" error. the drive locked and booted to M$ dash after i pluged it back into the xbox. i then proceeded to mod it through the same splintercell exploit i found on the SID disk. thanx again to everybody for all your help. marry christmas!!!!

i am a bit behind here but glad to hear you got a result and am glad that you the 'usual suspects' helped you solve this one (thanks guys!)

for the record - and this relates to the Ndure3.1 exploit - here is my failed attempt at trying to get this work. I gave up and I highly suspect the fuwi boot method of being the factor in this failed attempt. I don't think i have heard/read anyone successfully performing this hack.
Well if anyone fancies ago here is my write up on how i tried.

Now that the scene is quiet we may wait a long while for reports on that.
I too have stopped testing (quite a while ago).

I was using the 2.2 version and I keep running into a bug. If this was mentioned already than I did miss it.

this bug showed up on both 2.1 and 2.2. I had a virgin 500 gig WD hdd. The xboxhd program worked fine and it formatted the drive (used my existing xbox eeprom). The issue I was having is that whenever it got to the step to copy files off the usb, it gave me an error message saying it could find any files on the -c or -e and to reinsert the cd. I found this odd since i am using the usb version. It then ask you to hit enter, so I did and it gave the same error again. At this point though the xboxhd app at the end of the message listed this

"possible bug?"

Has anyone encountered this before or know how to get around it? In my case I ended up going to the Xbrowser and the files it said it could not find where obviously there and I just did some copy/pasting, but it would save tons of time if this USB version copied the files over itself. Any ideas on what might have caused the odd bug?

I have never seen any of those errors during my testing time with xboxhdm2.1/2.2
You sure the USB is built correctly?
I have seen that error saying 'it could not find any files on the -c or -e and to reinsert the cd' before with failed writes to CD using xboxhd - not xboxhdm. We moved away from the iso version a long while ago.

Read above post on Xbrowser (limited testing)/Ndure 3.1

[robot3]

i am a bit behind here but glad to hear you got a result and am glad that you the 'usual suspects' helped you solve this one (thanks guys!)

for the record - and this relates to the Ndure3.1 exploit - here is my failed attempt at trying to get this work. I gave up and I highly suspect the fuwi boot method of being the factor in this failed attempt. I don't think i have heard/read anyone successfully performing this hack.
Well if anyone fancies ago here is my write up on how i tried.

Now that the scene is quiet we may wait a long while for reports on that.
I too have stopped testing (quite a while ago).
I have never seen any of those errors during my testing time with xboxhdm2.1/2.2
You sure the USB is built correctly?
I have seen that error saying 'it could not find any files on the -c or -e and to reinsert the cd' before with failed writes to CD using xboxhd - not xboxhdm. We moved away from the iso version a long while ago.

Read above post on Xbrowser (limited testing)/Ndure 3.1

thanks for the reply. The 2.2 version, I used all of the files you had listed on the first page of this post and I got that error. Originally I found directions for the 2.1 usb on another site, then someone mentioned the huge update with 2.2 and gave the link back here. I started from fresh

On my old pc I had no problems with the 1.9 cd version (used to plug in my drive after auto detect). Since i am on a new pc with only one ide slot, I had the hard drive on that (plugging it in after auto detect ) and used the 2.2 usb. Again with the files and directions you provided but I still got the odd "reinsert cd error-- possible bug". The lock/unlock has never been a problem and with the 2.2 build it did see the eeprom in the folder but seems to have an issue with trying to see the files in the C or E folders. Again using the Xbrowser part of this setup the files were there and I did at least get the dash and such on the new drive so all was not lost. I wanted to report the error here that I received or as a way around it should anyone else encounter the same problem that I did

This post has been edited by robot3: Dec 23 2010, 07:13 AM

[spliff721]

thanks for the reply. The 2.2 version, I used all of the files you had listed on the first page of this post and I got that error. Originally I found directions for the 2.1 usb on another site, then someone mentioned the huge update with 2.2 and gave the link back here. I started from fresh

On my old pc I had no problems with the 1.9 cd version (used to plug in my drive after auto detect). Since i am on a new pc with only one ide slot, I had the hard drive on that (plugging it in after auto detect ) and used the 2.2 usb. Again with the files and directions you provided but I still got the odd "reinsert cd error-- possible bug". The lock/unlock has never been a problem and with the 2.2 build it did see the eeprom in the folder but seems to have an issue with trying to see the files in the C or E folders. Again using the Xbrowser part of this setup the files were there and I did at least get the dash and such on the new drive so all was not lost. I wanted to report the error here that I received or as a way around it should anyone else encounter the same problem that I did

if i recall i ran into an error of similar wording when trying to run the old NDURE script till i found out that there was a new script made just for this USB edition. but i never ran into this problem when simply using the stock options of rebuilding the hdd. i wonder if you had the c and e folder in the HDM directory populated with the files or did you put them somewhere else?
there was actually a point when i had the C and E folder in the HDM folder populated with stock files from slayers disk, then i had an NDURE directory with its own C and E folders that were populated with moded dash and files and such, and even when i was not trying to run NDURE and only use the stock HDM option of rebuilding the hdd it seemed to only want to find the C and E folders located inside the NDURE folder.

[robot3]

if i recall i ran into an error of similar wording when trying to run the old NDURE script till i found out that there was a new script made just for this USB edition. but i never ran into this problem when simply using the stock options of rebuilding the hdd. i wonder if you had the c and e folder in the HDM directory populated with the files or did you put them somewhere else?
there was actually a point when i had the C and E folder in the HDM folder populated with stock files from slayers disk, then i had an NDURE directory with its own C and E folders that were populated with moded dash and files and such, and even when i was not trying to run NDURE and only use the stock HDM option of rebuilding the hdd it seemed to only want to find the C and E folders located inside the NDURE folder.

I should have mentioned this earlier. My old xbox was with the sids softmod exploit. However my new xbox is the Trusty modified board. That setup was tsop flashed (no mod chip present). I was also told to keep the HDD unlocked on it. The Hdd I bought at bestbuy and that is the drive used for the 2.2 usb. The program DID format it properly and it would unlock and lock the drive if needed (used eeprom from my soft mod xbox just in case). So in my setup for the 2.2 I had no ndure folder as it was not needed. Yes you are correct I had the C and E folders in the HDM directory with the retail dash files from the slayers evox disc and I was getting that error. I was able to verify I had it setup right since browsing to those directories with theXbrowser found me the files I needed to at least get a dash on it. Again no idea why it had the hang up but at least the program gives an alternate way to get things done

This post has been edited by robot3: Jan 3 2011, 12:36 AM

[doctorhifi]

So whats the current consensus regarding use of SATA drives in original xbox? I've got 5 boxes modded (3 soft and 2 hard) and want to replace the HDD in one of the softmodded boxes with a 160gb Western Digital WD1600AAJS SATA drive I've got laying around (haven't checked yet to see if it is lockable).
I've got a SATA to IDE adapter in hand, purchased from goharddrive.com (for the bargain price of $3.95)

I'm using xboxhdm v 1.9 with 2 older PCS (one with AMD motherboard so I can lock the drive).

So what can I expect if I throw the SATA to IDE adapter on this drive and use xboxhdm 1.9 like I'm used to?

This post has been edited by doctorhifi: Jan 11 2011, 02:13 AM

[spliff721]

perfectly doable. they say that the converters are hit and miss though. so if you run into any problems, i expect that will be the first place to troubleshoot. people are going as far a 2TB sata these days. check back and let us know how it goes and give us model and serial numbers on the converter and HDD so we can add it to a compatability list.

good luck

i also believe that there has been issues using XBOXHDM with sata drives, or at least that its pretty well untested. if you run into problems, do a search for HeXEn. its a boot CD and has an option for HDD upgrades. all it requires is that the box already be modded and that you have an external power source for the new hdd. just an extra option if XBOXHDM fails.

This post has been edited by spliff721: Jan 11 2011, 09:53 AM

[scullc]

perfectly doable. they say that the converters are hit and miss though. so if you run into any problems, i expect that will be the first place to troubleshoot. people are going as far a 2TB sata these days. check back and let us know how it goes and give us model and serial numbers on the converter and HDD so we can add it to a compatability list.

good luck

i also believe that there has been issues using XBOXHDM with sata drives, or at least that its pretty well untested. if you run into problems, do a search for HeXEn. its a boot CD and has an option for HDD upgrades. all it requires is that the box already be modded and that you have an external power source for the new hdd. just an extra option if XBOXHDM fails.

this thread covers a lot of the issues regrading SATA convertors and indeed my own success with one.

regarding xboxhdm2.2 & the use of SATA drives - on the 1st page of this thread there is a NOTE: SATA HDD drives are largely untested but some users have suggested that forcing IDE legacy mode in the BIOS, may yield success.

Personally like spliff721 I used my hard modded XBOX to build a HDD SATA drive (256gb). But I need to upgrade myself now

[spliff721]

been using 2.2 for weeks. ive done 7 boxes in as many weeks. today i hit a problem. i was simply using it to unlock a pair of HDDs and swap them between boxes. (one box has a custom paint job but im waiting on the guy to get the cash. the other is for a customer that want it this weekend. so i took the HDD out of the custom one and swapped it into the other since the HDD was already upgraded, moded and loaded with games and apps and movies.) now i had no problem unlocking the upgraded HDD and then relocking it with the eeprom of the other box. swapped it into the other box and it boots just fine. then i took the stock seagate out of the box and went to put it in the painted box cuz ill go but a new HDD later in the week to upgrade it, but for some reason im getting the "there is no HDD in hda/1 hook up HD and power back on" or whatever it said(something really simillar to that.) i have tried about 5 times now and it keeps saying the same thing.
the thing is, i can see that it detects it right after post like it is supposed to. right after the script stops scrolling upon bootup for the first time for 2 or 3 sec. i can see that it is detected, but it wont read it later when i try to lock or unlock it. or even when i try to go to 2nd stage.
anyone got any ideas? ive tried plugging the HDD in at the afor mentioned pause during boot. thats usualy when i have to plug it in to not get "the drive is frozen" error. i have tried 2 different IDE cords. and i tend not to think its that or my IDE slot because i can see it being detected during boot.
all my boxes are modded with krayzies1.1 ndure. not that that matters. this is either a hardware problem or something wrong with the software like maybe my usb got corrupt or something.
im going to hit the sac for tonight, but ill do some more testing with it tomarrow.

[scullc]

so the stock HDD is working/unlocked?

there are many ways to lock/unlock the HDD - most of which are contained in xboxhdm2.2 - you could try an alternative
see my post here

here is a possible workaround for the frozen drive

if all that fails try xboxhdm2.1 as xboxhdm2.2 is possibly bugged (development has stopped on that i'm afraid)

This post has been edited by scullc: Jan 29 2011, 03:24 PM

[spliff721]

ok. i got it sorted. my conclusion is that there is something insufficient with the V1.1 xbox power source, and here is why.

i have done like 7 mods in the past few weeks. all have been v1.6. the one i got yesterday was a v1.1. XBOXNDM2.2 would detect the drive during and after post, but once i get to the options for locking or unlocking, it would not detect.
so it crossed my mind to power it up with one of my 1.6 boxes and it worked. had no problem changing the eeprom and when i plugged it back into the 1.1 it booted to XBMC as it should have.
here are a couple of my observations:
1. i always wait now to plug the IDE into the xbox HDD untill i boot slax and i get to the first pause in the scrolling script. then i plug in and can see that the drive serial number is there. then when it gets to the point where it says "wait a minute" if the drive is locked it takes a minute.
now when powering this HDD with the 1.1 it was locked, but it didnt wait a minute like im used to, but when i powered the same HD(still locked) with the 1.6 it did wait a minute.
2. everyone knows that there are differences between the motherboards and power supplies from version to version. i notice the power supply in my 1.6 is greatly different from my 1.1. the least of which is simply the color of the wires leading to the molex plug.
3. i also tried a few different stock HDDs i have lying around with the 1.1 power supply and they to would not be detected when trying to lock,unlock or enter step 2 of XBOXHDM. they do however work when powered by my 1.6.
(just for testing perpouses i tried 2 different Western Digital HDDs, and 2 different Seagates. one of them was a sleeved one and one was not)
just thought id post my experience and my solution. im curious what you guys think?

[scullc]

well done - glad you got a result & you are finding the tool useful. i personally was unaware that such a tactic (changing power via different xbox's - I only have a 1.0 & 1.1) would make a difference - so worth knowing. thanks.

heres a trick i learned during my testing on how to get a locked drive to boot quickly - would be good to reprint again

..basically I turned off IDE detection in the BIOS.

it may help you shorten your sequence of steps

[spliff721]

Glad you find my information usefull. And your tool is invaluable. Thanx for the tip also, but my bios has no option for turning on or off the IDE detection, and I like that it hangs there cuz it lets me know that things are working as they should. It was one of the first sign that I knew something was wrong when I came accross this problem.
I am curious though if anyone else has had this problem. You youself said you hav a 1.1 have you run into this? Or is it spacific to my box? If its not, what is the difference in the power supp,y that is causing it? Obviously the power supply is sufficient to boot the xbox and keep it running, how could it be a problem for XBOXHDM or is it my computer?

[xXDestroyerGRXx]

Hello, im on ubuntu linux 10.10 32 bit and i wonder how im going setup xboxhdm2.2

my xbox doens't have any modchip or softmod

Thanks.