Long time listener, first time caller here. I have never modded an XBOX before, but looks like a fun project and I wanted to run my plan by the gurus on this forum to avoid any potential pitfalls (i.e. destroying the data on the original HDD doing something stupid being a newbie) after watching a ton of YouTube videos on the subject.
I have an OG XBOX v1.6 that was modded and setup around 6-7 years ago. The motherboard died and I am looking to swap that drive into a new system and upgrade it to an unlocked SATA HDD (I don't want to have to deal with locked HDDs anymore). I have no knowledge of how it was built originally aside from the HDD password, but I love how it is laid out and boots up directly in to the emulator menu, etc and want to keep that.
There is no evidence of any hard modding on the motherboard (no chip, no bridged soldering, etc), so I am assuming some version of soft mod.
I have two working units (v1.2 & v1.4) and both are currently soft modded with the latest Rocky5 build with stock HDDs. I did install XMBC-Emustation on one of them, but aside from that, they have nothing special going on with them and I don't need anything off those drives.
30K foot view of my plan is as follows:
1. TSOP mod one of the working units and flash the BIOS with Evox M8 with F & G (HeXen 2020).
2. Take the currently modded HDD (400GB) out of the dead unit and using Victoria, remove the user password.
3. Install that HDD in the new TSOP modded unit and test (I assume that since the password is removed from the drive and the BIOS is flashed, it will simply boot even though I have no idea how the HDD was originally prepared).
4. Assuming steps 1 - 3 go as planned, convert the TSOP unit to an 80-pin cable and IDE/SATA adapter and clone the HDD to a WD Blue 500GB SATA using Chimp.
-Am I correct in that I should pick the TSOP hard mod option in Chimp even though the HDD itself is soft modded?
-Since my new SATA is bigger than the drive I am cloning, pick option 2 for select partitions and pick option 4 so partition G takes up all the remaining space on the larger drive
5. Shut it all down and remove the stock hard drive and install the SATA in the unit and hopefully it all boots up correctly.
6. Assuming everything up to this point went well, clone the new SATA drive with Chimp to another WD Blue 500GB (this time I can just pick the full disk clone option)
7. TSOP the second working unit and install the cloned drive and have 2 working, upgraded units.
Let me know your thoughts and if you have any suggestions. I appreciate the feedback!
So I was given an Xbox 1.0 from a friend that is chipped and has a 120gb HDD. Unfotunately the chip does not have support for HDD larger than 120gb and I am unable to flash the chip's BIOS (evox says it is not flash writeable).
I'm basically in a bind to find a guide on how to softmod this box and tsop it from a modchip because I don't know what type of chip it is and how to disable it. Pictures below:
Apologies for the very dusty MB, lol! As always any guidance will be highly appreciated.
I've got a 1.0 with a Hynix with DVD drive that won't eject that came previously TSOP'd. It had an older version of EVOX flashed and then the two TSOP junctions were removed. It unfortunately didn't have the LBA48 configured so thus I wanted to reflash. When I used the BIOS checker I would get Unknown. When I tried to use Flash tools (blastos and evox) I wouldn't get anywhere with flashing as it was unwritable (makes sense)
Today I reapplied the TSOP junctions and when I ran the BIOS Checker I was getting something back - identfying the correct chip and flash. I grabbed the 1mb size version of ind-bios, added a fresh config file to my c drive, started up blastos, and flashed it which seemed to be successful... until the restart. Now the xbox will start, power off, start, power off and then start again with a red/green alternating LED.
Have I ruined my TSOP? Should I have done the 256K? I've got a couple Alladiin's on the way, is this recoverable? I'd appreciate your thoughts and guidance.
Board Life Status
Board startup date: April 23, 2017 12:45:48