flip_flop

I crudely re-invented the wheel lol

I'm probably releasing something i could have found if i looked hard enough, but anyway.. I was manually inputting the folder names and iso file for every bloody game i have. it was driving me insane. copy pasting only helps so much. I decided to stop being lazy as it's costing me more time so, I made a python script that checks the current folder it lives in. looks at all folders within that folder and makes a list of them. It then runs extract-xiso with the correct name and parameter to create the iso. one after another IT's quick and dirty and has literally no error handling at all. but it works for what i need. hope it helps someone. in the end it took all of 2 minutes to write. curse you procrastination! all that time wasted extract-iso-all.py

Interesting. This is a 1.4 box as well. Thanks for the pointer, will go look into that

It's rising! Now at 1078 lol. Assuming it's about 1030 off from real value

Softmodded the box I repaired recently ( I'll keep that aladdin chip for my box once it's sorted. ) Booted a few times now to confirm.. this is what's being reported? Anyone have a suggestion? Sensor(s) failure or software issue?

Wow, thank you for the kind words and advice. I'm glad it was appreciated! As soon as I started reading the thread I knew I wanted to join! Here's to more fixed xboxs!

I have done as you suggested. I have fixed the issue, I came across this post after the fact and was hoping to add my findings, info and advice for someone in a similar situation to mine. (hopefully correct and of use) Where I started and how I resolved it.

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

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. 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.. 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. 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?