Bowlsnapper

Friggin' fascists. What CPU model, specifically?

I received the parts for the kernel debugger today. I will build it tonight.

I do have the SVF file for the openxenium if you are interested. @Hellraiser988

Yes. PM'd.

It's doing the SAME THING?... Something is up with that console that the games don't like...

I have the newer one, It just looks so GOD awful... Lol. Is there any advantage to it?

Damn, Now I have no boot anims folder. lol. Yes, it still locks up, just at the Xbox/Mircosoft logo. Somebody suggested that I need to use 2.3.1. I guess I'll try it... Edit: Yes, 2.3.1 will work as BFM from the XDK dash. I will use this for now, but I assume it is a bug. Edit 2: With the reintroduction of boot animations, the lockups are returning with 2.3.1 being loaded as BFM from the XDK dash. It was booting fine without them. NOW I'm getting pissed. @KaosEngineer

Sorry for bumping, but attempting to load Cerb retail as a BFM from the XDK launcher (So hardbooting with a debug = true flag in the ini) is causing a lockup during the boot animation XBE. Does anybody know why this might be? I had somebody else test and it is doing the same thing for them. The BFM is set to retail and to ignore the INI.

So I got the XDK dash installed, and PBL is listed, but when my retail Cerbios bios boots, it freezes at the boot animation. Anybody have ANY idea why? Edit: I think the HDD is gonzo. It got moved in the HDD bay while copying the XDK dash files over and unmounted. It has been unstable since. Guess I'll fuckin trash that and image another drive. Start over.

The soldering is indeed better. If you can, try to uncross the wires. Try to avoid them going across each other either above or underneath. Apparently the signals going through them are sensitive enough for this to be an issue. I have seen @KaosEngineer state this, however, if I am wrong, please correct me.

Your posts are limited to 10 posts a day as a new member, so use them sparingly. Unless you are a paid member (which isn't much) I think you can only edit your post within 10 minutes. You can be a committed member for 5 bucks. I recommend it.

I think the CPLD is toast and is basically shorting and dying. I never knew that much power was going through the LPC, honestly.

Yeah, the XBE, perhaps, but you would have to build the bios on the PC every time, as long as you were okay with that.

AH I see. Not that I've found, no. But if it doesn't exist, I'm sure it will soon, with all the Halo 2 stuff going on.

Yes, looking at the kernel debugger page on github, I did see that I could basically just have Cerbios in debug mode on the TSOP and just hook up the ribbon straight to the LPC. Thank GOD I had no issues flashing the TSOP on this guy or putting in the RAM. I'm comfortable doing them, but sometimes those procedures go bad for seemingly no reason. The hardware modification is finished, at least with the mobo. I will work on modifying the case to get USB-C out on the back. I was watching this video and went "oh SHIT" because I needed to sort out what to do and what NOT to do on the software side, but I think it'll be easy to figure out. Forget everything involving PBL and transfer the rest of the XDK files. No big deal. You said as much above. Edit: @Dempsey_86 I read your post more carefully and I see that using the PBL will enable me to use the rest of the HDD normally, dash and all. I will have to think on that! Right now I have the standard 2TB with my image on it, so that may be overkill and I may be able to use a more regular drive.

Heh, it's on XBlast aladdins (swapped 1MB flash chip and reflashed CPLD). Open Xeniums have their own OS called XeniumOS. It has basically all the features of XBLast, minus the 128MB test tool. There may a be a few minor differences otherwise, but the main purpose is tat you can FTP, do basic HDD operations and, most importantly, flash a bios to the main banks with it.

Right... Those don't count. lol. Those things are cursed and are a pain. Case in point. I meant a chip that has at least Xblast on it, like an XBlast aladdin (which is modified with multiple banks and has XBlastOS on it) or an OpenXenium with XeniumOS on it (or even PrometheOS)

Interesting. I had this happen once with a OpenXenium in Xenium Tools. I tried again and swapped without issue. If this is repeatedly happening... Maybe just get a modchip with an OS present.

I think what is happening (and @KaosEngineer mentioned this) is that since you are still booting a softmod setup, you are booting with a "Shadow" C partition. Even though you are hardmodded, I think your chip's bios is still booting the exploited/shortcut xboxdash.xbe (because no other dash files are present on E, so it defaults to the stock dashboard) on your REAL C partition. The softmod runs the exploit and boots your modded dash with a fake C partition. You are creating the directory on what is not ACTUALLY your C partition and that is why you are not seeing it when XBlast looks to your REAL C partition. What bios is currently on your modchip? if you are able to boot a disc, I would use the FTP feature, and backup anything you need on that HDD, then format it and install a modded dash (such as XBMC or UnleashX) as well as "set up C" which you should see as part of the main installer options. You will then boot from the E partition. However, to run the TSOP flash, you need to boot with the mod disabled and boot the official MS bios and dash. After that, you can either use the savegame exploit or the endgame exploit to TSOP flash Cerbios to your onboard TSOP flash. Remember, if you're not booting from your TSOP, you will not have access to it in XBlast. Make sure that after your HDD is set up with an installer (including C), you are able to disable the SmartXX chip and boot your stock TSOP MS Bios with your new, un-softmodded MS dash files on C. I cannot find instructions on how to boot with the mod disabled, so you may have to pull the chip off the pin header when you want to boot from your TSOP and run the TSOP flashing exploit(s). Edit: Looks like you resolved this on reddit. Glad you sorted it out. For anybody wondering, this was solved using option 6 on the aforementioned Cerbios Disc "Option 6: Flash Cerbios (Softmod Users)" after choosing the option to boot with BFM. I recommend using netflash to ensure that you can easily flash the newest version of Cerbios.

Now that is weird. Okay. So run an installation disc with the 60GB, use a common dash and try playing the games in a typical structure: F:/Games/(Whatever Game Folder)/. Use NOTHING from the problem setup. Unless you have done that here. In which case... I'm at a loss.

I'm probably gonna borrow from a few tutorials, one of them being the MVG video. I will use the kernel debugger, since I have Cerbios installed on the TSOP and the LPC is free to attach the ribbon to. I will detail it here as much as possible. I will use a USB-C breakout and internalize the serial debugger, with USB-C out at the rear of the console. There is a case modification STL I have that will enable this. The 128MB RAM upgrade is something you will want to do one chip at a time, carefully and methodically. That way if you have a FRAG, you will know it's the chip you just worked on, probably a bridge or lifted pin. Do NOT get solder into the vias around it. This has ALWAYS killed my motherboards and I do NOT know why. You can run XBlast at every chip installation. If XBlast does not boot from your chip and you FRAG, inspect your work. This happened a couple times on this board and there was a bridge on one and a lifted pin on another. Stay tuned!

I figured, "Why not"? Maybe I can learn to code at least a little. I have a spare Halo Edition. Need to build the serial debugger after I finish with the software side of this. https://github.com/XboxDev/serial-usb-adapter

It's worth a shot. I forgot to focus on the fact that this is only with a few actual games. Back to the HDD thing, what happens if you mirror your dash configuration on the other HDD and load a problem game in folder format?

However, XBlast will have a hard time being used because it has to boot with the intended flash area fully exposed. This would have to be a one time TSOP flash. There will only ever be one chance to do it.... Unless a programmer is involved. Or, perhaps XBLAST will see the TSOP and detect it properly regardless of how much is exposed and the proper switch configuration can be engaged after XBlast has booted from its 256K bank.

Yeah, try the other HDD. At this point, it looks like just trying to run ANYTHING from it would be a sufficient test as new files do not seem to wanna run on the current HDD.