Jump to content
  • Similar Content

    • By Oldnice
      Hi everyone,
      I recently did a 128MB mod on an Xbox 1.1, which was successful. Console booted nice, and ran for hours while gaming, even with a small NV & FSB overclock. I decided I didn't hate myself enough, and decided to go even further and replace all the K4D263238M-QC50 on the board, with the Samsung K4D263238F-QC50-variant, which is said to be tad bit more efficient. Thought this might allow for even more OC (never enough, right?), but now I've run into issues after replacing all the memory chips on the board: The console boots, but only runs for 5-30 seconds, before the screen starts to glitch heavily, with the system freezing as well. If rebooted after a glitch, without a small pause, the system will not boot, and will flash a green light.
      I've tried to do the following:
      - Reflow all 8 memory chips 4 times in total. No improvement.
      - Removed the extra 64MB memory, retaining only the original 64MB, just with the new F-variant memory chips. No improvement.
      - Replace the remaining 4 memory chips with another, fresh, F-variant memory chips. No improvement.
      Each time I complete a step, the end result is exactly the same: XBlast runs for the same 5-30 seconds, before glitching and freezing. I can run the memory test for the extra 64MB (when I had it installed), which always completes successfully, if I manage to run it completely before the system starts to glitch. If I connect a HDD, I can even boot iND bios with UnleashX, and everything works and shows correctly, before the system glitches and freezes. Always the same screen glitch effect, before freezing.
      The Xbox is modded with an Aladdin XT+, with the XBlast enchanced 49LF080A-chip.
      I can solder, remove or reflow the chips with confidence, with clear and clean solder jobs. I can share pictures, if required, but I'm pretty sure at this point that the solder job is not to blame. Have I nicked some important component somewhere with my solder iron? Are the F-variant memory chips simply incompatible with the 1.1 board? Anyone got any leads?
    • By Icarium
      Greetings again!
      Running XeniumOS 2.3.1, but it turns out no bios are present. I've done some research, but the information is scattered from over 15 years and there are a lot of different opinions on the matter. 
      What are the present day recommended bios for open xenium running xenium 2.3.1? Are there any bios/dashboard packages or bundles available? Thanks!
    • By Icarium
      Greetings!
      I am very new to the OG XBOX (both the console and the forums).
      I have a 1.4v xbox that I have dusted off recently to install Open Xenium chip. The console was a bit dirty, so I gave it a good cleaning, removed the clock capacitor (which had just started to leak), replaced the fan with a Nexus, and installed the new open Xenium chip. 
      The system seems to be running great and immediately boots into the Xenium OS screen when powered on. The problem: no controller inputs are recognized in any of the controller ports (I've tried with four different working controllers). So basically I boot to Xenium OS, but cannot select any of the menu options. (I should also mention that before the Xenium install, everything had been working fine).
      Now, when this first happened, naturally my thought was that I had not properly reconnected the ports back to the motherboard, but upon checking they seemed to be well connected (I cleaned the ports and reconnected for good measure). I have looked at the traces on the motherboard and they seem fine. I imagine the chip install went okay since I can boot into Xenium OS(?) Port have been cleaned thoroughly. The only thing I have not tried is swapping the 1&2 ports with the 3&4 ports (in case there is a problem with port #1, and Xenium OS will only recognize input from Port #1???)
      Does anyone have any idea what the problem may be? It seems odd that none of the 4 controller ports are working, and all I am left with is an idle Xenium OS screen on my system. Could it be a single bad solder joint on the Xenium chip?Could it be that Port #1 is busted?
      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.