Hi All.
First up, thanks Krayzie for putting the time into this project. It really was a pleasure to use, and very easy.
Some background:
I just bought a second hand XBox wih the intention of running XBMC on it for streaming media to my TV. After heaps of reading and pages and pages of printing I got all the necessary items together to attempt Krayzie's mod.
I first updated the 1.1 pack to 1.1.1 on the PC.
Next I transferred the Game Saves (Splinter Cell PAL version) to a USB stick using XPLorer360
I connected the USB stick to the XBox with an adapter cable, transferred the Saves across, fired up Splinter Cell and ran the Exploit.
After the EEPROM backup step, the first thing I did was FTP into the XBox and back up C and E drive to my PC.
The rest of the install was fine, up until the "Press OK to re-boot and activate the Shadow C: drive" part.
When I did this, the XBox re-booted to the XBox splash screen (I think I've seen it referred to as "Flubber"??), but the hard drive started making a horrible "Clack -Click" noise until eventually I got an error screen with 07 in the corner.
I had only turned the box on 2 or 3 times before instaling the mod, and it seemed to be fine.
After the error, I powered off and waited a few minutes before trying again. This time it powered up fine with the UnleashX dashboard, and all seemed to work well, so I put it down to a minor glitch.
Later I power up again to install XBMC and the same thing happened. The first attempt failed, but a wait then retry got it working and I installed XBMC.
Now, however, it seems to have failed completely, and won't boot at all no matter how many times I try or how long I wait. I just get the "Clack - Click" and the error 07.
I'm 90% sure it's a hardware fault and I just got unlucky and got a drive that was on it's way out. Fortunately the store I bought the machine from gives a 12 month warranty on second hand units, so I'm not worried about that. I just wanted to make sure it wasn't something I had done that had caused the fault, before I try again on the replacement unit.
Is there anyway at all the installer (or more correctly, the mug using the installer) can cause a hard drive failure as I described? I'm pretty certain the answer is no, but I thought I should check anyway.