viking24 Xbox-HQ Member Xbox Version: 1.1 Modded: Xecutor 2.6
Joined: Jul 08, 2004 Posts: 58 Location: NH, USA
Posted: Mon Dec 13, 2004 12:02 am Post subject: X2.6 & HD Install prob...this makes totally no #@!$$# se
Modded a buddies V 1.0 xbox yesterday w/ an X 2.6 4983.67 bios and a 200 G seagate. Everything went well. installed chip< flashed bios< installed evox< and appps dumped about 20 games everything runnin great.
So whats the problem right?. I also bought the same model hd to upgrade my xbox (also V1.0) so I follow the tutorial to copy the drive using ghost. I image the drive w/ ghost plug it into my xbox (V1.0, X2.3b lite 4983.67) and it runs perfect w/ the new drive.
Now, here's the messed up part..I put the drive back in the 2.6 box and I get a frag w/ error code 6 (unable to lock Hdd). I figure maybe I didn't put the drive that was originally in the 2.6 and swap it w/ the other drive .. Still frags.
So now I try both drives in the 2.3 and both work fine. Neither work in the 2.6 now after imaging. I pull everything aprt and check my chip install, cables ect. I lock and unlock both drives in the 2.3 w/ no probelm.
Both drive sstill frag on the 2.6. I then take a virgin hd and plug it into the 2.6 and no fragging. I wipe one the 200 drive and sure enough works fine now (though I had to install everything again I used AI 1.3 for everything) Can any one explain why making an image from one drive to another messed up both of them? And why did both drives work fine in the 2.3 and not the 2.6? I have everything working so this is just for curiosity. I've become the defacto mod guy at work and will probably have to do several in th future. I'd like to be able to clone drives instead of the hassle of manually loading everything. Xenium chip maybe??? _________________ XBOX v1.1
Xecutor 2.6 Modchip
200GB Seagate HDD
X2 4983.67 Bios
EvoX 3935 Dashboard
80mm Blue LED Cooling Fan
Mad Catz Lynx Wireless Controller
TheModGod Xbox-Hq Legendary Xbox Version: 1.1 Modded: Xecutor 2.6
Joined: Apr 18, 2004 Posts: 5303 Location: Greensburg PA
Posted: Mon Dec 13, 2004 2:58 am Post subject:
Next time try unlocking the HD that you are cloning from. Maybe you copied the data that is stored on the HD for security features and since the 2.6 machine eeprom obviously had different info you eneded up getting the frag.
I know that you said you unlocked it and then tried again.....but something still must've been on that puppy. Anyway, my best guess right off the bat. I never cloned a drive so not sure.
After you used the 1.3AI do you get error code 13 when launching MS Bis/MS Dash (chip disabled). Just curious.
You should get the torrent for the new AI that they have out here...it's friggin awesome!
TheModGod
------------------------------
http://www.xbox-hq.com http://www.themodgod.com _________________ Good Deals: Death@Hand, funkydopenloven, StaticMind, Slamscaper, PorscheXboxter
Bad Deals: None Yet
Pending Deals: Vanguard
viking24 Xbox-HQ Member Xbox Version: 1.1 Modded: Xecutor 2.6
Joined: Jul 08, 2004 Posts: 58 Location: NH, USA
Posted: Mon Dec 13, 2004 3:41 am Post subject:
Nope no code 13....but I didn't realize that installing the MS dash was seperate step. Kept getting the MS "your xbox needs service" error. Can't blame the AI for that I'm gonna dl the deluxe at work tommorow...I live in modemville.
Both drives were unlocked prior to cloning...I dont think the PC will recognize a locked drive. The weird thing is I used the 2.6 to install the drive originally and everything worked. The drive when into my pc w/ a blank drive then right back to the 2.6 and the former blank drive to the 2.3. Something must have happened during cloning to the "source" drive.....I dont know. Hopefully someone else can be saved a bunch of frustration after readung this _________________ XBOX v1.1
Xecutor 2.6 Modchip
200GB Seagate HDD
X2 4983.67 Bios
EvoX 3935 Dashboard
80mm Blue LED Cooling Fan
Mad Catz Lynx Wireless Controller
TheModGod Xbox-Hq Legendary Xbox Version: 1.1 Modded: Xecutor 2.6
Joined: Apr 18, 2004 Posts: 5303 Location: Greensburg PA
Posted: Mon Dec 13, 2004 3:57 am Post subject:
Oh, my bad. I thought you were using the Xbox to clone the HD.... _________________ Good Deals: Death@Hand, funkydopenloven, StaticMind, Slamscaper, PorscheXboxter
Bad Deals: None Yet
Pending Deals: Vanguard
custom-xmodz Xbox-HQ Freak
Joined: Aug 28, 2004 Posts: 796 Location: Wales, UK
Posted: Mon Dec 13, 2004 4:06 am Post subject:
Hmm that is real wierd, i would say that the cloning somehow edited the lock password but is unlikley, and the fact it worked in the 2.3 makes it even easier.
I always just copy from one xbox to another with a crossover cable, less handling the hard drives and copies at over 9000k/s with avalaunch so is not amazingly slow but takes a few hours.
at least it don't cause wierd probs anyway. i gotta admit you got me stumped as the ghost should not have written anything to the first HD at all unless it was cache.
DJH
viking24 Xbox-HQ Member Xbox Version: 1.1 Modded: Xecutor 2.6
Joined: Jul 08, 2004 Posts: 58 Location: NH, USA
Posted: Mon Dec 13, 2004 2:13 pm Post subject:
Xbox to xbox huh? DO you ftp from one to the other or is there a transfer feature in avalaunch? _________________ XBOX v1.1
Xecutor 2.6 Modchip
200GB Seagate HDD
X2 4983.67 Bios
EvoX 3935 Dashboard
80mm Blue LED Cooling Fan
Mad Catz Lynx Wireless Controller
|
All times are GMT |Page 1 of 1
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
HQ Network: 19,088 | 
Guests: 8420 | 
Members: 1 
Forums 
