Posted: Tue Apr 17, 2012 2:15 pm Post subject: random booting issues with a 1.0 flashed TSOP
when i boot up my softmodded xbox, it either boots normally into the executer rocks my xbox splash screen and i can go about my business, or what seems to happening more and more, is either
1. error 13
2. error 21
3. original factory M$ dash
4. it will boot to unleashx, but text is jumbled/missing/F&G drives not detectable
i don't know if there are some "ghost" files from the HDD upgrade still left hanging around, but hoping there is a fix besides reformatting all the drives. I'm running a 2 TB HDD and am hoping i can just install a clean set of C/E files, but not 100% sure what i have on my hands. Can anyone help point me in the right direction? Thanks in advance,
Prehistoricman Moderator
Xbox Version: 1.6 crystal Modded: Xecuter 3
Joined: Oct 09, 2011 Posts: 406
Posted: Wed Apr 18, 2012 7:12 pm Post subject:
Are you sure this is softmodded with the Xecuter rox my box?
It sounds like you have got the wrong cluster sizes for your drive and when you get past a certain threshold, it corrupts. Either that or you have a slow spinning up drive. How long does it take to boot successfully? _________________
alexis524 Xbox-HQ Newbie
Xbox Version: 1.6 crystal Modded: Xecuter 3
Joined: Apr 17, 2012 Posts: 2
Posted: Thu Apr 19, 2012 12:31 pm Post subject:
I did some tinkering last night/this morning with the SATA>IDE adapter, and it seems that i have a clearance issue. When the top half of the console shell is tightened up, it leaves next to no breathing room, what looks to be happening is the plastic "ribs' underneath the shell is putting enough pressure on the IDE cable that comes off of the HDD and also on the way the adapter sits that it causes the error 13. I must have tested my theory at least 30-40 times. With the top half off, it booted up normally each and every time, no errors, no funny text, drives showed up with remaining space. Then rebooted, but put slight pressure on the area in question as if the top half of the shell is on, and errors every single time. I tried to shave off some of the protruding plastic rib (for lack of a better term) with a utility knife to gain some space, but at 2am, i was still getting errors, so i'll have to get a dremmel to take more off to give as much breathing room as possible under the hood.
It wasn't all a loss though. Not only did i isolate the root of my errors, but i also got crafty with the four rubber feet on the bottom of the case. They have been off ever since i started this project for easy access in and out. I wanted to use double-sided tape to reattach, but couldn't find any in the house, so i grabbed some super-glue and a hole puncher. I cleaned off the feet and contact area of adhesive residue, punched a hole in the rubber right where the bolt would sit underneath, and oila! feet back on permanently with access to the four corner bolts with no need to take off the rubber feet!
dartht33bagger Moderator
Joined: Apr 17, 2007 Posts: 5408 Location: Oregon, USA
Posted: Fri Apr 20, 2012 7:09 am Post subject:
This may not be related to your issue, but if you have a an "Xecuter rox my box" logo on your startup screen, then you either have a mod chip or TSOP (it seems to be TSOP from your title). If you do in fact have a TSOP, then you need to uninstall your softmod and use AID to install a mod chip version of unleashX.
If you leave a softmod on with a modded bios some weird things can happen. This happened to me on my first mod chip install. My 1.6 had SID 5.0 still running on it when I installed the chip and it would randomly boot to the MS dash or it would randomly freeze. Once I removed the softmod and installed the mod chip version of unleashX, these errors went away. _________________
|
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