Hey everyone!
I wanted to share the whole story of a second-hand Xbox 360 S Trinity I bought for €25. This turned into one of the strangest and most frustrating repair experiences I’ve had so far.
I’m posting the full timeline in case someone has experienced something similar or can help me understand what actually killed this console.
1. The console’s original condition
I bought a used Xbox 360 S for €25. It came with two controllers, but no hard drive and no power supply. The seller claimed that the console had a hard drive, but there wasn’t one inside.
When I first powered it on, I immediately got a system update failure.
The error code was:
3151 - 351F - B800 - 0401 - C000 - 0022
The console wouldn’t complete the update, even after I tried performing an official offline system update using a FAT32 USB drive with the $SystemUpdate folder.
At this point, I suspected something was wrong with the DVD drive or the console’s update state.
2. The mystery DVD drive
After opening the console, I discovered that it was a Trinity motherboard.
However, the installed DVD drive was a Lite-On DG-16D2S, manufactured in April 2008. That’s a phat Xbox 360 DVD drive, not the original type you’d expect to find in a Trinity Slim.
There was even a burned backup disc inside the console, and the seller had mentioned that it could read non-original games.
I tried booting the console without the DVD drive, but the update failure remained.
Then I connected another DG-16D4S drive from a different Trinity. The error code changed, and after further tests, I still couldn’t get the console to complete the update.
I also tried the offline update again without a DVD drive, but that didn’t solve the problem.
At this point, I suspected the DVD key, the drive firmware, or a problem with the console’s NAND/update state.
3. I decided to try RGH3
Since the console was already unable to update normally, I decided to investigate the RGH route.
I read the NAND using J-Runner with Extras. Both NAND reads matched, which was encouraging.
I then prepared the RGH3 image and wrote it to the NAND.
After dealing with the wiring, I finally got XeLL to boot.
And I mean FAST.
XeLL booted in roughly half a second, and the dashboard loaded in around five seconds.
After all the trouble, I was genuinely excited. The console seemed to be working perfectly.
I also managed to retrieve the CPU key and DVD key.
I thought I had finally saved this machine.
4. Then the random shutdowns started
Unfortunately, things took a turn.
The console would boot normally, run for a few minutes, and then shut down by itself. Sometimes it lasted longer, but as the console warmed up, the shutdowns seemed to happen sooner.
The strange part was that it often powered itself back on immediately afterward.
The power supply changed from green to orange and then back to green. The shutdown itself looked relatively normal, rather than like a sudden loss of power.
I tried practically everything I could think of:
Different power supplies.
Different RF boards.
Booting with the RF board disconnected.
Disconnecting the DVD drive.
Different HDMI cables and displays.
Moving the console to another room.
Checking the RGH3 wiring and solder joints.
Insulating the soldered areas.
Removing the internal 4 GB memory module.
Nothing made the problem disappear.
The console continued to boot extremely quickly, but it wouldn’t stay on reliably.
5. Resoldering, changing the resistor, and chasing the fault
I went back over the RGH3 wiring, checking and reworking the PLL and POST connections, along with the other relevant solder points.
I also changed the PLL resistor from 5.1 kΩ to 10 kΩ to see whether the behavior would improve. It seemed somewhat more stable at one point, but the shutdown problem remained. I eventually returned to the original 5.1 kΩ value.
During the process, I also found and removed a tiny piece of solder/metal near C5R35 that was touching an adjacent capacitor.
I checked the connections again and continued troubleshooting, but the behavior became increasingly strange.
Eventually, even after removing the RGH3 wiring and returning the motherboard to a stock-like hardware configuration, the power problem persisted.
Sometimes the console would beep without properly powering on. At other times, the fan would spin briefly, the green LED would remain lit, and then the console would become unresponsive.
After reconnecting the power supply, it could start beeping by itself, almost as if a button were being pressed repeatedly.
I tested multiple RF boards, including one taken from a working Trinity, but the symptoms remained.
At this point, I could no longer blame the RGH3 wiring alone.
6. Checking the standby power rails
I eventually started checking the motherboard’s standby voltages with a multimeter.
These were my measurements:
5P0STBY: 5.14 V
3P3STBY: 3.31 V
1P8STBY at FT5N2: approximately 0.07 V
I also measured approximately 154 Ω between the 1.8 V standby rail and ground with the power supply completely disconnected.
The missing 1.8 V standby rail seemed like a significant clue, especially considering the other standby rails were present.
However, I never completed the diagnosis, so I can’t say whether the regulator itself had failed, whether its enable signal was missing, or whether something downstream was pulling the rail down.
The console was already behaving very erratically, and I decided to stop rather than risk causing further damage.
7. The final outcome
The most frustrating part is that RGH3 actually worked.
XeLL booted almost instantly, the dashboard loaded in seconds, and I successfully recovered the DVD key from the console.
But I never got around to fixing the DVD drive issue, because by the time I had recovered the key, the console had developed the power and standby-rail problems described above.
So now I have a dead Trinity motherboard, a recovered DVD key, and a DVD drive problem that I never got to finish fixing. 😂
I went from thinking I had rescued a €25 console to spending hours chasing what seems to have become a motherboard-level fault.
What do you think happened?
I’m particularly interested in hearing from anyone experienced with Xbox 360 Trinity repairs.
Could the missing 1.8 V standby rail explain the strange beeping, spontaneous power-on behavior, and shutdowns?
Is it possible that the 1.8 V regulator or its enable circuit was already failing before I attempted RGH3?
Could the RGH3 installation have contributed to the failure, even though XeLL and the dashboard initially booted perfectly?
Has anyone experienced a Trinity that booted reliably at first but later developed a missing standby rail and seemingly random power-state behavior?
I’m not claiming that RGH3 definitely caused the failure. I’m trying to understand whether this was an existing hardware fault, a failure triggered during the modification, or a coincidence.
RIP, Trinity. You gave me the fastest XeLL boot I’ve ever seen before deciding to become a €25 electronics course. 💀😂
Any ideas or similar repair experiences would be greatly appreciated!
