Love this forum and got a lot of great info from here. Recently I dusted of my good old softmod and gave this all a go again after many years. I was able to tsop the xbox and install a larger harddisk. My friends picked up on the idea of having a xbox with emustation and asked me to build one for them as well. So I ended up buying and working on 6 xboxes and harddrives that all went trough their own struggle to get the job done but hey, I made it.
Thing is though, at some point I used chimp to format a 500gb WD and it locked it by the end of the session in one of the xboxes. this drive ended up not being used and now I want to use it again but I do not know what xbox it's from.
Being all wel prepped I did read all the eeproms from al the xboxes trough simple serial eeprom reader. Extracted them straight of the board with no issues but the sidenote is I never did with this 500gb WD hdd installed.
And this is where my confusion is, because what I understand is the eeprom is xbox specific. And the harddrive password is generated trough the hdd serial number and model based on the eeprom. (Please correct me if I'm wrong). So all the eeproms I have when I read them in live info beta 3 show me other harddrives.
So I connected the harddrive to my ide port refreshed the disk managment, it pops up under disk# and I try to select it in live info without any luck. I tried running chimp in order to unlock the hdd in the slave disk options with all the available eeproms but had no luck.
Basically, and I'm sorry this is a long read, I'm trying to find a way to backwards engineer my hdd locking code with the 6 eeproms I have available that all state a different make/brand/sn hdd.
Thank you in advance
I accidentally wiped my EEPROM with an Arduino when trying to read it, and have no backup. Now even with Config Magic's valid blank EEPROM, there's no video out. Only a green blink code (34? It's 3 fast and 4 slow blinks)
Now I'm wondering if there's any way to fix it.
This rarely happens, so there's not much info on the net about it. I'm thinking even if I got a modchip such as openXenium, the motherboard might be useless.
Should I give up on this yet and just get another box, or get the modchip (already prepped the v1.6 board with headers and LPC rebuild)?
Can the modchip make it boot with bad EEPROM data?
Eventually, I got the Arduino code reliably reading and writing data, but even with the 'valid blank' EEPROM data, that hasn't helped so far.
Board Life Status
Board startup date: April 23, 2017 12:45:48