All Activity

Since you are now fragging, I think we can assume that your LPC rework got the chip to be able to trigger D0 through the wire. That's why your TSOP boots when the chip is unsocketed and your dashboard boots with the locking error. You are still unable to boot your modded dash and bios which would bypass a locking error entirely. You are triggering an LPC boot, but your chip is not giving the bios over successfully, so the chip may be defective in some way. The D0 point is not a ground itself. It is a lead to the MCPX for triggering a chip (LPC) boot. IT is grounded in order to force a chip boot. That's why it's going to the Xenium. The chip is grounding the D0 point (pointing to the MCPX) at boot in order to tell the console to boot from it and load a bios through the LPC instead of the onboard flash (TSOP). That's how it works. All chips require this. Shitty chips like the Aladdin do not have a working D0 pad on them which requires you to take that wire and run it from that point on the bottom of the board to aground point anywhere on the console. I use a screwhole ground on the top of the board, but that's just me. If the chip is dead, then you should be able to throw another one on the header, yes. Are you able to boot/power-on with the eject button? That should load XeniumOS. I would assume that a bios was already configured to load based on the fact that the HDD is unlocked and it already had the chip in it, but it's worth a shot.

Regardless of popular belief, I have seen many thrown errors on hard modded consoles. Especially if the hdd is locked to another console, has improper files installed, or simply dying. I find it's always best to start with the simple tests just to rule them out. Instead of immediately jumping to resoldering stuff. We're steering back to a few months ago it seems, by overlooking simple solutions and instantly diving in deep. Im just saying

I can find ZERO trace of this anywhere online by part number. I did find the raptor PCI card, but not this.

ok, after reflowing the header, I power it up and now all I get is green and red ring and no boot. mod is lit red. If I remove the mod I get Factory boot with 05 error. It will not boot at all with mod plugged in. Also, I checked the D0 wire point of solder on bottom of motherboard and it is not a ground. I've attached a pic of bottom D0 solder point. I don't know anything about this mod, but it must have worked at one time as it is. If mod is bad can I just install another?

On the DVD emulator card (inside the dev kit), the part number is 700-15326 rev 00. Middle number on the part number is hard to read. Looks like a 3 to me. Here's more photos: https://imgur.com/a/YRb11os

Your D0 is wired to the chip. You can see the D0 attached to the pad on one of the corners of the Xenium. If the chip is not functioning right, it will not perform the momentary grounding required to spur an LPC boot and the TSOP will boot, like it is now. I was just curious to see if it would actually push a chip boot if provoked by manually grounding the mobo D0wire to a ground point while booting, but if you're already done with the LPC touch up, then just try booting with D0 as it is. Let us know how it goes.

I didn't mod it, but I'm assuming the D0 wire is already grounded. I just got done reflowing the header pins but havn't tried it yet

If your bios is loading properly, locking will not be a problem. You are getting the HDD locking error because of the underlying issue, which is that your chip is not functioning properly and not booting your hacked bios. Once you start booting from it again, the HDD locking issue will become a non-issue. Don' future trip yet. For one, I am almost positive that this is your problem. Secondly, if it isn't the problem, then we will help you through the most logical diagnostic steps we can to help you pin it down. Thankfully we have a lot of pretty knowledgeable guys around here. As long as you're not dealing with a FRAG issue, most things can be solved, thankfully. Actually, before you do anything, if you would be willing, ground the D0 wire and power on to go ahead and force an LPC boot. I'm would want to make sure it happens. With your LPC in the condition it's in at the moment, I would expect a FRAG and wouldn't be alarmed, but at least you would know that your mobo's D0 is gonna force an LPC boot and you can expect it to work properly from here on out as long as the chip is utilizing it appropriately.

Going to reflow the header pins today. If that's not the problem, what is next?

How do I lock the HDD? It's been many years since I've worked on an Xbox. Trying to get this one working for a friend.

Sorry for reviving yet another dead thread, but I am on an XDK kick recently. Just wanted to say that I am using the SuperIO Kernel debugger and built it using the github page. Also have a BOM available. https://mega.nz/file/JqdiFTqb#Ca4eF9tDnwTdIUDDyewTpFyj7p-Jqa73LLHCZmvV5jU Come back to the forum @DobaMuffin!

I'm bumping this thread simply to bring attention to it. I think it is interesting reading and would like to share it. I am fascinated currently by the original ODE and would love to reverse engineer it as a project, even if it is no longer practical to do so. It would be a crazy learning experience... Maybe one day @GoTeamScotch, what is the part number on the Xbox-side card? I can't read it in that photo. Glare or something...

Awesome and problem dude! Glad you’re enjoying it. That game was always one I really enjoyed but I was always surprised that more people didn’t know about it. Especially given that it was a LoTR title game.

Agreed. Regardless of if that ends up being the issue it definitely needs to be reflowed and the mobo cleaned up afterwards.

I've successfully tsop'd two v1.0's, a Hynix and ST, both with Destiny's OGXbox Cerbios Disc. Both were softmodded running Rocky's latest, and then flashed using the Cerbios Disc. Is this picture still relevant? I'm working on a v1.4 now, and it's a Winbond. According to the pic, it's a different method? Or is the Cerbios disc compatible with all 6 versions of tsop?

Welcome to the forums and we hope you stick around.

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!

Reading how you went through all the steps to get everything taken care of, step-by-step, I was impressed. You know ho to diagnose and treat issues. I honestly would not have an Aladdin that had to be programmed externally. If you're getting a programmer, you may as well get the rest of the programming gear necessary to change it into an XBlast. SST and flashcatUSB to JTAG the CPLD. Or just get an XBlast Aladdin, really. The cheapest chip there is that's worth a damn.

This is a wonderful post. Thank you for moving it here for others to find more easily. Edit: I didn’t get down to where you said you solved it on the other thread. This fits even better here now as a single thread. Nobody has to sift through comments. Again, great post

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

Have you tried simply locking your HDD?

Cop and paste this all into a new thread post. You’ll have this fixed pretty soon. I just don’t want to clutter old posts and a new title could help others find answer in the future.

Ok, I'll resolder and clean up. thanks

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?