Search the Community

Bit of a necro post but having had error 16 and figuring it out the hard way...I came to the same result and,I think, at least in my case, I have found something that appears to be an explanation and fits my issues. Googling further to find more on various Xbox error codes I found myself at this post. Being inexperienced in more than softmodding my own box and upgrading it's drive, I've never tried to just repair a random box, but I intend to do more this place seems perfect! Bit of a tale to this one... I bought a faulty xbox. Turned out it was chipped (super aladdin live) and the box was throwing all sorts of errors. Removing the chip completely got to a new error. The drive (upgraded) was not locked. Being once hardmodded that made sense. I needed to lock it.. but how? Found I could get the eeprom from the Xbox by soldering a few wires to the Xbox and dumping it using my raspberry pi. Great success. Finally got fat Xplorer to detect my drive, formatted it as standard Xbox drive and locked it. Booted up, all looked good. Then, error 16! This was a very new code! I found with some googling that this is is due to the system clock being unset. (could be wrong but leads to correct results and seems dashboard related) The box tried to boot the Microsoft dash to set this Even trying to boot a game failed. (On my other softmod box I could always boot discs regardless of the HDD state as long as it was there and partitions correct. That's how I would use a burned dvd to rebuild it..) Retracing my steps I realised my error. My drive was blank!! I placed all the stock files on the drive and tried again. All sorted Xbox booted and asked me to set the date and time. I'm waiting on a programmer for the aladdin flash chip. My hunch is Someone tried to update their chip and broke it? Unlocked HDD leading to soft brick as no way of using default bios? Edited 8 minutes ago by flip_flop Further info and typos. OCD, ADHD edit. Last one. Sorry if this is all common knowledge now but I was pleased to bring this box back from the dead. Getting the eeprom dump.. whoever found that i2c connection. Genius

I've tried to boot with a newly formatted 2TB SATA HDD, and have been having issues... Cerbios Hybrid 2.3.1 UDMA5: Stays on the Boot Animation. M8Plus Titan & Stock (TSOP): Error 21. XBlastOS: Black screen, jumps back into XeniumOS The chip has XeniumOS 2.3.5. The drive has been formatted with FatXplorer using the Cerbios preset, and is unlocked. The only data on the HDD is the default C:\ contents from the XBOXHDM build of Rocky5's installer along with cerbios.ini and the BootAnims folder. I used CerbiosTool to generate the ini and have set "DashPath1" to "C:\xboxdash.xbe" and "DriveSetup" to 1 (No HDD, Legacy), with everything else being "stock". Does anyone know what could be the problem? UPDATE: Turns out it was an issue with using Rocky5's softmod files on a hardmod. I fixed this by just copying Rocky5's UnleashX build from xbins onto the C:\ partition.

I got a free Xbox v1.0 that had Error 21. I cleaned the board, replaced the clock cap with one I bought online (no leakage), installed an Aladdin XT Plus 2 modchip, and used TrueHeXen 2021 to erase the hard drive and install UnleashX. Now, the console turns on without giving an error, but this is where the real pickle is: 1. Trying to boot MS DASH from the menu brings up Error 21 2. Trying to load Burnout 3 (an Xbox Live game) freezes as it loads. 3. Trying to change dashboards (I.e. UnleashX to XBMC4Gamers) ALWAYS fails with an error and no description. This is both with the TrueHeXeN disk or from within UnleashX. As some additional background, it’s a 1.0 and I cannot flash a 512kb BIOS, and it actually says “BIOS: Unknown” in the TrueHeXen disk. I’ve also tried clearing the cache to see if that’s preventing the game from running and it’s not that.