QUOTE(spliff721 @ Dec 15 2010, 09:06 AM)
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).
QUOTE(robot3 @ Dec 16 2010, 08:22 AM)
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
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