Search the Community

Requirements.Working Xbox with a Pinheader Install and a Working Modchip with a Hacked BiosHackDaBox Re-Flash DiscWith the working Xbox turned off Remove the lid , the screws from the hard drive bay and DVD-ROM drive. Remove the hard drive (still connected ), lift it up and over slightly, now lift the DVD-ROM drive up ( still connected) and spin it around to face the opposite way. So now the DVD-ROM is facing the wrong way round but still connected . Support the DVD with something underneath, so it sits level. Now put the hard drive bay back where it used to be ( covering up the power supply ).WARNING NEVER TOUCH THE POWER SUPPLY AREA AS IT CAN KILL YOU !This procedure is safe the way I have described above because you have access to the Modchip area . The chip should be plugged onto a pinheader ? If not you can not re-flash this way.Now remove the wire that goes to the D0 pad on the Modchip itself. Unscrew the screw near the LPC area and put the D0 wire under the screw and carefully tighten it up. You can solder the wire to the circle around the screw if you wish. remove any wire you have connecting the chip to the Xbox motherboard but leave the chip plugged into the pinheader.Now depending on your chip type you need to make the chip enabled all the time.On DuoX 2 solder a wire between the BT pad on the chip and pin 9 on the chip (This is point G on the official Duo diagram) see the picture below coutesy of cubistproject.On Aladdin solder a wire between BT pad on the chip and Pin 2 on the chipOn Spiderchip simply leave off the switch.Note : You need to do this to the good chip in the Xbox and the ones you intend to Flash.Turn on the Xbox with the good chip in and let it boot up and then load HackDaBox Re-flash Disc Choose Re-flash Spiderchip ( it works fine on DuoX 2 and Aladdin ). Choose the Xbox version you wish to use the flashed chip on. E.g. 1.0 - 1.5 or V. 1.6 but don't hit A to flash yet.Note Evoxdash or Slayers or your preffered Flash utility can be used with this method.Now carefully pull the Modchip off the pin header with the power still on ( note only 3.3 volts goes into the Modchip so it will not electrocute you.Now carefully line up the chip you are going to flash and then push it on the pinheader. Never try and force it on , double check it's lined up properly and it should slide onto the pinheader easily.Now go ahead and flash the chip now. The Xbox should turn off after the successful flash. Once it turns off ,turn it back on and the previously bad flashed chip should now boot the new flashed bios that you just put on it.If you picked Xbox V.1.6 and your Modchip is not in a V.1.6 it may not boot reliably so try it in the V.1.6 box.Remember to put all the original wires back to the chip, and remove any links you have made. In other words put the install back to the manufacturers recommendation.

I'm trying to softmod an old OG Xbox by doing a hotswap (since the DVD drive can't read games) on the original 8GB WD harddrive. I'm using "Amazon's Choice" usb adapter for whatever that's worth. Inateck USB 3.0 to IDE/SATA External Hard Drive Reader Applicable to 2.5"/3.5" HDD/SSD, with 12V/2A Power Supply, SA03001 https://www.amazon.com/Inateck-External-Reader-Applicable-SA03001/dp/B08BNPXSJ9 I can't tell if a) this adapter isn't supported or b) I'm not getting lucky (timing wise) with the hotswap keeping the drive unlocked. Any help is appreciated! If I use USB View it shows the device as: Loc[124] DeviceConnected: USB Mass Storage Device Device Descriptor: bcdUSB: 0x0300 bDeviceClass: 0x00 bDeviceSubClass: 0x00 bDeviceProtocol: 0x00 bMaxPacketSize0: 0x09 (9) idVendor: 0x1F75 idProduct: 0x0611 bcdDevice: 0x0006 iManufacturer: 0x04 0x0409: " When I try to see the device in FATXPlorer I get the following log: =====FATXplorer v3.0.0.24789 64-bit (x64) Log File START===== Runtime: .NET 7.0.3 OS Fingerprint: 3047bb3539608b94e41b5d78e5d1bc137edd101800e5ae889a3164cec688de07 [3/11/2023 4:19:13 PM] [Startup] FATXplorer is starting... [3/11/2023 4:19:13 PM] [Startup] MainForm initializing... [3/11/2023 4:19:13 PM] [Driver] Driver v22.0.8464.0 is installed and available. [3/11/2023 4:19:13 PM] [Startup] MainForm initialized. [3/11/2023 4:19:14 PM] [Startup] Startup complete, searching for devices... [3/11/2023 4:19:14 PM] [Device Detection] Search for devices starting [3/11/2023 4:19:14 PM] [Startup] FATXplorer is up to date. [3/11/2023 4:19:19 PM] [Device Detection] Found SCSI device "NVMe KXG70ZNV1T02 NVMe KIOXIA 1024GB" @ "\\.\PHYSICALDRIVE0" [3/11/2023 4:20:27 PM] [Device Detection] -OS disk, skipping [3/11/2023 4:20:27 PM] [Device Detection] Found USB device "WDC WD80 EB-28CGH1 USB Device" @ "\\.\PHYSICALDRIVE1" [3/11/2023 4:21:21 PM] [Device Detection] --Device doesn't support SMART [3/11/2023 4:21:21 PM] [Device Detection] -Checking security status... [3/11/2023 4:21:29 PM] [Device Detection] --Failed to check this device's security status, details: pd1: Unable to read USB device ID [3/11/2023 4:21:29 PM] [Device Detection] -Checking this device for HDD and MU storage... [3/11/2023 4:21:44 PM] [Device Detection] Device detection read failed at position 0x0000000000000000: The request failed due to a fatal device hardware error. : '\\.\PHYSICALDRIVE1' [3/11/2023 4:21:48 PM] [Device Detection] Device detection read failed at position 0x00000000007FF000: The request failed due to a fatal device hardware error. : '\\.\PHYSICALDRIVE1' [3/11/2023 4:21:52 PM] [Device Detection] Device detection read failed at position 0x0000000020E30000: The request failed due to a fatal device hardware error. : '\\.\PHYSICALDRIVE1' [3/11/2023 4:21:56 PM] [Device Detection] Device detection read failed at position 0x0000000130EB0000: The request failed due to a fatal device hardware error. : '\\.\PHYSICALDRIVE1' [3/11/2023 4:22:00 PM] [Device Detection] Device detection read failed at position 0x00000000ABE80000: The request failed due to a fatal device hardware error. : '\\.\PHYSICALDRIVE1' [3/11/2023 4:22:00 PM] [Device Detection] --Sector Format: N/A [3/11/2023 4:22:00 PM] [Device Detection] --Health: Healthy [3/11/2023 4:22:00 PM] [Device Detection] --Couldn't find any HDD or MU storage on this device [3/11/2023 4:22:00 PM] [Device Detection] -Finished checking this device for HDD and MU storage [3/11/2023 4:22:00 PM] [Device Detection] -Checking this device for Xbox 360 USB storage... [3/11/2023 4:22:41 PM] [Device Detection] --This device doesn't have any partitions [3/11/2023 4:22:41 PM] [Device Detection] -Finished checking this device for Xbox 360 USB storage [3/11/2023 4:22:41 PM] [Device Detection] -Finished with this device [3/11/2023 4:22:41 PM] [Device Detection] Search finished in 206.7 seconds

I did a dumb thing and tried to hotswap softmod a second console I have, with a guide from consolemods.org everything was going great but Xplorer360 seemed to have deleted my Partition 4. I saved all the files I could (this is pre softmod so i wasn’t able to backup EEPROM) and now when I boot the Xbox it just goes straight to an error screen, no dashboard. I’m unsure how to unlock the HDD again and what to do from here. It’s a v. 1.0 console with 3944 kernel. Any help is appreciated! I realize what I did was dumb and my only other hope might just be to chip the console, but I have no idea to solder so it might just be out of my scope of knowledge and I’ll have to sell the console as parts or something.

Jargon Buster TSOP - IS THE ONBOARD CHIP THAT BOOTS THE MS BIOS , YOU WILL WANT TO BOOT FROM THIS FOR XBOX LIVE. LPC - THE HOLES WHERE THE MODCHIP CONNECT TO THE MOBO USING WIRES OR PINHEADER OR QUICKSOLDER METHODS. FRAG - FLASHES RED AND GREEN. THE XBOX IS TELLING YOU SOMETHING IS WRONG AND IT CANNOT BOOT POSSIBLY DUE TO POOR SOLDERING. BOOT - WHEN THE XBOX LOADS A BIOS AND STARTS UP THIS PROCESS IS CALLED BOOTING. BIOS - THE PROGRAM THAT IS STORED ON THE MODCHIP OR TSOP. IT'S EITHER MS OR HACKED (EVOX OR X2). PIN HEADER - 2 ROWS OF PINS THAT YOU SOLDER INTO THE LPC HOLES AND THEN SIMPLY PLUG YOUR CHIP ONTO IT. MOBO - SIMPLY MEANS THE XBOX MOTHERBOARD. D0 - THIS IS A LITTLE VIA ON THE TOP OF THE MOBO OR A SMALL PAD ON THE BOTTOMSIDE OF THE MOBO THAT WHEN GROUNDED PREVENTS THE TSOP BOOTING. VIA - A VERY SMALL LITTLE CIRCLE. YOU WILL NEED PRACTICE BEFORE YOU CAN SOLDER TO THESE. YOU CAN AVOID THESE ON EARLIER MODELS BUT NOT ON A V1.6 EVOX DASHBOARD - AN ALTERNATE DASHBOARD FOR THE XBOX THAT HAS A MENU TO LOAD GAMES , FLASH YOUR BIOS ETC. NOT TO BE CONFUSED WITH EVOX BIOS WHICH IS DIFFERENT AGAIN. EVOX DASHBOARD IS MADE UP OF A NUMBER OF FILES THAT YOU TRANSFER ONTO YOUR HARD DRIVE OR A CDRW. THE LATEST VERSION IS 3935. EVOX BIOS - A HACKED BIOS FOR THE XBOX , IT ALLOWS YOU TO PLAY BACKUP GAMES AND RUN COOL APPS LIKE EVOX DASHBOARD. THE LASTEST BIOS IS M8 PLUS. X2 BIOS - A HACKED BIOS FOR THE XBOX , IT ALLOWS YOU TO PLAY BACKUP GAMES AND RUN COOL APPS LIKE EVOX DASHBOARD. THE LASTEST BIOS IS 4983. HOT SWAP - THE NAME GIVEN TO THE TECHNIQUE OF BOOTING THE XBOX WITH ONE MODCHIP (WITH THE LID OFF AND THE DVDROM TURNED AROUND THE WRONG WAY) AND THEN UNPLUGGING THE MODCHIP FROM THE HEADERPIN AND REPLACING IT WITH A BLANK ONE OR ONE THAT HAS HAD A BAD FLASH AND THEN FLASHING THIS CHIP. FLASHING - PROGRAMMING A BLANK CHIP OR REPROGRAMMING A CHIP WITH A BIOS FILE. SPIDERCHIP AND ALADDINS NEED A 256K BIOS. DUOX2 NEED A 512K BIOS. ALSO V1.6 XBOX'S REQUIRE THE EVOX M8 PLUS V1.6 BIOS. OTHER MODELS CAN USE THE X2 4981 OR X2 4983 BIOS. FLASHBIOS - A SPECIAL BIOS THAT ONLY LETS YOU DO A FEW FUNCTIONS. (WONT PLAY BACKUP GAMES). ITS MAIN PURPOSE IS TO FLASH YOUR MODCHIP WITH A HACKED BIOS. LOCK - LOCKS A HARD DRIVE SO THE MICROSOFT BIOS AND DASHBOARD WILL BOOT. THIS IS NEEDED FOR XBOX LIVE. UNLOCK - UNLOCKS A HARD DRIVE FOR USE IN A PC. YOU MUST UNLOCK A XBOX HARD DRIVE BEFORE IT CAN BE USED IN A COMPUTER.