Bowlsnapper

I just discovered ship of Harkinian. I'm about to try out the OOT PC port. I REALLY wish I could program so I could port it over...

I would love to finally replace a temp sensor, too. Well damn!

This happens when you swap the chip before you reach the point where you flash. Make sure that the last XBE has loaded before swapping chips and then hit the button combo or "Write" function to flash. Don't swap the chip and THEN load whatever executable is meant to flash. The bios is called upon every time an executable is launched. You will crash if a blank chip is mounted and you try to launch a piece of software, flashing software included.

For the hell of it, could you try ripping the game from an ISO (Mulleter) and running it on a different HDD? Clean files. Same dash setup. Nothing from the current drive. If it works, THEN copy the game files from the old/main HDD for a problem game and run that file set on teh new HDD, sourced from the old.../main. You know what I mean. lol. Wanna see if it's corruption. That's my idea, anyway.

Sceptre... at least it wasn't expensive. However, I am interested to see why these sets would have an issue with this signal...

Okay, if it is at a cold boot EVER (like the console is cold and things can't be hot yet), then yes, the temp sensor probably needs to be replaced. That is my assessment, but maybe Kaos can add his input as well. It's worth a shot if wanna try. Do you have any confidence to try to replace the sensor yourself, or are you not a very soldery guy?

The fix for a failure of this component is to desolder it and solder in a new one. Cleaning the contacts is not going to fix the component. The bios is not responsible and it is handled at a lower level than bios software. Although, @KaosEngineer is most experienced with all that Edit @fox That could be! @lightwish Is the issue ever at boot from a cold start or is it in the middle of operation?

Kay, so OpenXenium. Download from this link and flash Cerbios 2.3.2. I don't know what HDD is in your console, so just flash UDMA 2 for now, which is the file that does not have any UDMA 4,5 or 6 naming. We'll figure out the HDD part later, but this will at least diagnose the issue. Be sure to leave evox in the boot menu in case you have an issue with Cerbios for any reason and you can switch back. It should theoretically work fine, though. There is ElpisHD available to configure the HD+. This console mods link tells you how and how to boot it as default. https://consolemods.org/wiki/Xbox:XeniumOS Here is the manual: https://www.mediafire.com/file/8pp4o8b0m3yzrcp/Xenium-OS_V2.0_User_Guide.pdf/file

Okay. You running an OpenXenium, or do you not know? I assume an installation service did this for you, correct?

This is the newest version of the installer and is the one I would use. I would select "DHCP and no BFM" at the beginning as long as you are running Cerbios already.

He's basically asking if you're using the Evox bios that was compatible or Cerbios 2.3.2. Do you see a purple "Evo-X" logo in the corner at boot, or 3 blue dogs?

Edit: My apologies @p3t3rpopp3r. I failed to check the OP. I remember this issue now. Have you tried swapping the DVD-ROM drive in case the drive board is crapped out and holding up the boot? I read through a little bit and didn't see it, so I thought I'd ask.

Okay then I won't panic. lol. Find a parts console with a bad DVD drive for cheap. Good way to acquire a working console!

With AND without it?

The FRAG is occurring without the Xenium, correct?

Are you sure the eject button is functioning? Is the status LED turning purple when both buttons are pressed?

Beat me to it by 38 seconds. @Warlord_Zsinj

I'm talking about booting into it as a main dashboard. It's what I boot into at startup and I boot games directly from it. It keeps me from having to deal with my settings being reset after I configure them in the MS dash. I set the XBMC network settings to "Default" which is intended to use MS dash settings and keeps them from being both overridden and overwritten. I set up settings in the MS Dash, then IGR back into XBMC and launch the game. Or if there is nothing to fix or modify, I just boot up into XBMC immediately at boot, and launch Halo 2. No issues. I'm in Live/Insignia from power up within 90 seconds. That's why I'm suggesting to use it as your main dash. Unleash seems to cause lots of issues for people, even when they put some serious time into trial and error editing their settings. I know the topic suggests you would like to do so with UnleashX since that seems to be the dash that you're accustomed to, so I should state that it is merely a suggestion. It MAY be worth looking into if you would like to try it.

I agree that Unleash is probably resetting your settings. FWIW, I use XBMC4XBOX and just set it to "default" which is looking to the MS dashboard for network settings and never changes them. If you are able and willing, look into it. It's a old dash, but it's awesome and does everything you really need a dash to do.

I look at this post now and I realize how far I have come in such a short time... Thank you @sweetdarkdestiny for being supportive at a time when I needed it. You were a great help Sorry for deviating from the topic.

I admire your skills GREATLY, dude.

I like that Jewel! Nice work here on everything!

What is the dash? Is it similar to origins? If I had that problem I would probably just wipe out te dash and start over with something I know works and the just re-link all the shortcuts and what not. It may be more trouble than it's worth though in this case. I wish I knew. I've yet to try this build...

@antonic901

It smells like plastic and some Styrofoam. Awesome.