Print

[vipergts619]

I've been using the Itools v1.7.5 since it came out and have had no problems until recently.  I was just working on a box the other night and I do my usual routine..

for references here's my routine:

This was done to a 1.0 Xbox too
1)hook up my xenium ice solderless modchip
2)setup new hard drive (hook up new hd in place of dvd as slave and it copies the orginal's hd files to it)
3)set aside old hd and boot up with new HD and lock it, then boot up to make sure it boots to dash
4)copy over run linux game save hack for mech assualt from memory card (which boots to a evox dashboard for ftp access)
5)ftp in and copy the Itools 1.7.5 contents
6)boot up and run linux, hit Install UDE/UDE2

Usually from here I walk away (eat something, switch vga over to pc and listen to music, etc.) and come back to a blinking light.

However, I took the mech assualt out and booted up but it booted to dashboad.. so i was like... what the fudge... booted back up with mech assualt and ran linux.. hit install ude/ude2 and this time watched it.

It says there's an error, and list a bunch of files as "read only."  This is happening when creating the backup process.  Now I could just copy my xbox's c and e drive files that are needed and ftp them in, but the backup from Itools is very nice and critical for recovery options as I burn the backup folder on E to a cd and give the old HD and cd to the owner and say "DONT LOOSE IT!"

Anyways, I also want to mention I tried going back a version and 1.6.1 and it does the same thing.  Any info on this is appreciated.

ps.  Just wanted some info on something else, I remember using the Itools 3 times on a 1.0 and two 1.6's and when it went to backup, the screen gave that scrambled look like the old focus chip detecting the pbl, anyways I left it sit cause the xbox led was yellow, and sure enough, after about 5-10minutes, i cam back and it was blinking and everything was ok... just wandering what causes that.. again.. any help is appreciated, thx in advace!!!

[vipergts619]

Ok, rather than sit for an answer like a sac, I did some more troubleshooting myself.  First thing, took out the new HD, and put back in the old.  Gonna try this again but on the original drive.  Copied over game save hack and then ran linux, booted into evox, ftp'd in and copied itools 1.7.5 and re-ran the install ude/ude2.

Well it's still beyond me right now, but it worked.  I also remember the two 1.6 boxes i mentioned in my previous post were done on original hd's since they didn't have new hd's at the time.  But I remember doing it to the 1.0 box, or do i??? oh well.... Is there something with trying to run itools on a new hard drive... i mean my modchip replicated the old one to the new 200gb so I don't see why not.  ohhh well... just thought i'd post back, in case anybody runs into this prob and somebody happens to read this and have an answer.. the more you know the better right!  haha ok
<-- total noob out!