Jump to content
OGXbox.com

Search the Community

Showing results for tags 'xeniumos'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Rules
    • Why Can't I Download?
  • Subscribed Members Only
    • Subscribed Members Only
  • Off Topic
    • New Member Introductions
    • Rumble Pit
    • Suggestion Box.
  • General Xbox Discussion
    • General Xbox Discussion
  • Original Xbox Modding Forum
    • Hardware Mods
    • Modchips
    • TSOP Flashing
    • Softmods
    • Repair
  • Xbox Case Modding
    • Case Mods
    • Lighting & Electrical Mods
  • Tutorials
    • Official Tutorials
    • Tutorial Submission
  • Software
    • Bios
    • Dashboards
    • Installation Disks
    • Applications
    • Games
    • Emulators
    • Homebrew
  • Xbox Collecting
    • Xbox Collection Showcase
  • Rare and Uncommon
    • Rare and Uncommon Xbox Hardware
    • Rare and Uncommon Xbox Software
  • Vendors
    • N64 Freak's Products
    • Barnito's Products
  • Development
    • Rocky5's Projects
  • Online Play
    • Game Night
  • Classifieds
    • Wanted
    • For Sale
  • Moderator Section
    • Moderator Back Room

Calendars

  • Community Calendar

Product Groups

  • Vendor Forum
  • Membership Subscriptions
  • Forum Ads

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 3 results

  1. I'm bringing up my console collection to the modern ages... Or at least trying to keep them from wasting away in a pile of leaky capacitor fluid. I have a 1.4 OG that was modded with a Xenium Blue chip. Original HD, DVD, etc. Just modded to turn it into a media box back in the day. Prior to the restoration, I would get an initial green light, then flashing red light constantly. I've recapped the entire system, reflowed the LPC to the Xenium, and verified continuity. There was slight corrosion under the clock cap and a few of the CPU caps had bulged. Post-rehab, I can boot initially to the XeniumOS 1.0 menu. I have two old BIOS images available along with "Original BIOS", however when any of the options are selected the eject button LED goes from solid green immediately to a flashing red light. Two spin-ups of what I believe is the DVD drive, no video, no audio. Flashing red continues until a single press of the power button shuts down the system. Eject button works during this time. Component A/V cables will not work display the XeniumOS menu, but RCA cables will. I've seen another post on reddit discuss an EEPROM failure as the potential cause, and I'm starting to think that's most likely it. In the EEPROM tools section, the Game Region is "INVALID!" and cannot be flashed to another region. Before I go down the rabbit hole of procuring another EEROM, flashing, and reinstallation I wanted to see if anyone here had any other thoughts on the issue. I appreciate any insight you folks may have. Thanks!
  2. I've tried to boot with a newly formatted 2TB SATA HDD, and have been having issues... Cerbios Hybrid 2.3.1 UDMA5: Stays on the Boot Animation. M8Plus Titan & Stock (TSOP): Error 21. XBlastOS: Black screen, jumps back into XeniumOS The chip has XeniumOS 2.3.5. The drive has been formatted with FatXplorer using the Cerbios preset, and is unlocked. The only data on the HDD is the default C:\ contents from the XBOXHDM build of Rocky5's installer along with cerbios.ini and the BootAnims folder. I used CerbiosTool to generate the ini and have set "DashPath1" to "C:\xboxdash.xbe" and "DriveSetup" to 1 (No HDD, Legacy), with everything else being "stock". Does anyone know what could be the problem? UPDATE: Turns out it was an issue with using Rocky5's softmod files on a hardmod. I fixed this by just copying Rocky5's UnleashX build from xbins onto the C:\ partition.
  3. Hey everyone! Not new to the OG Xbox scene, but am new to using OpenXenium chips. I’ve just done an install on my Crystal 1.6 - rebuilt LPC with a Chimeric Systems QSB - and everything is working fine. However, I’m trying to update to the “unofficial” MakeMHz XeniumOS to address the “lines” issue when using component out on a 1.6. When I attempt to use the MakeMHz updater tool, it throws back the error: ”Unknown XeniumOS Detected” The supplier that I got my chip from seems to have loaded the XeniumGold OS 2.3.1 - as when I boot into XeniumOS I have a “Xenium 24k Gold” skin. How would I go about reinstalling XeniumOS 2.3.1 (as per the recommendation on the MakeMHz GitHub) so that I can update to 2.3.5? I’m sure this is a stupid/noob question - but just wanted to be sure so I don’t brick/soft brick the chip. Thanks for the help!

Board Life Status


Board startup date: April 23, 2017 12:45:48
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.