PS5 UART commands

  • Thread starter Thread starter stetofix
  • Start date Start date
  • Views Views 128,608
  • Replies Replies 213
  • Likes Likes 2
Feel free to contact .dony. on TheCod3r's World discord and talk with him about the UART error codes he found out while decrypting a southbridge dump.
 
Last edited by stetofix,
  • Like
Reactions: White_Raven_X
Failed to read data 01 9/23/2025 12:58:15 AM C0020303 Low APU Not Responding - Trying Init or Reboot -3- (User Submitted: System wont start Blue Light Flashes), Check Fuses F3501, F7501 |-(OK 00000000 C0020303 19D246C5 FFFF0005 00000100 2157 003E 3791 2093:3E) .... 3E 2/21/2025 2:43:23 PM80C00140 Low MainSOC_FORCEOFF (TitaniaGPIO) - APU Halt (No Response) - Forced Power Off Via Power Button |-(OK 00000000 80000140 18B8E729 FFFF0005 00000100 2157 003E 236C 179A:69)

Checked all fuses all good
What is next?
 
Привет,

У меня проблема с PS5.
Я не могу прочитать код ошибки. Не знаю почему.

Я использую PS5 wee tools и у меня установлены Python и PySerial.

программа прочитала код один раз и выдала мне следующее:

€ÞÞ @ ûøÀЃ Ð €ü`?ÀðÿüÞŸÜÂÿþ OK 00000000:3A
$$ [MANU] UART CMD ГОТОВ:36
üþ


Я использую FT232L для подключения к компьютеру.



Я пробовал с PS5 Code Reader и ничего.

Я подключил кабель, как на видео и скриншоте.
Поменяй местами Tx и Rx
 
@stetofix

80800000 Fatal shutdown by OS request. Kernel panic shutdown (case: single GDDR6 RAM ic failure. replaced -> fine) [CE-108262-9]

how did you found out which ram ic causing the issue?
 
Hi guys did any one encounter error code 80800024 and did any one fix this isue before?

The uart code shows to check any joint or die cracks,but the die and the solder balls look Great.
 
Hello friends. I have a PS5 slim CFI-2016 A01Y console on an EDM-044 board. There's a problem with it, when you turn it on, the blue light turns on for 2 seconds and turns off, you turn it on again, and the same problem. I disassembled the console, connected the UART, and read the errors. There is only 1 error in the system. 80800014 TPM 2.0 chip or Power Failure. The south bridge was soldered and the processor was rebalanced, but the problem remained. Perhaps the problem is in the chip itself, but how can I take information from it and overwrite it on another chip? I would be grateful for your help.
 
80801f12 error after clearing all errors resolved after using thin flux and gentle massage during reflow on RAM IC 1 and 2. I did not need to do anything else. I was getting a blue light for a second and off. Thermal showed power up on VRMs and RAM ICs etc before off.
EDIT: It was loading and trying to update. I was able to get it reset and even loaded up to the user selection but soon after the screen and audio starting breaking up and then failure again.
 
Last edited by Gawsh,
report back 80060000 uart code is fixed by replacing all 6phase SOC_VGFX mosfets, though IMO its likely the first 3 phase is the root cause but I just do all 6 together since I see last two has less heat during game run before crush shutoff. They were only 4 mosfet running 80C-ish. After replacing all 6 mosfet, none of them goes above 70C and all 6 has even temp under thermal camera.
Details of the UART code is as followed

2026/5/7 16:03:41 80060000 Severe Main SoC GFX Power Fail - SoC VRM Power Fail (GFX) - VRM Power Fail (GFX): Couldn't get the error factor.
|-(OK 00000000 80060000 1AFD5833 150000F5 00080000 217B 0036 51B1 1C09:1B)
Click for TSB Information
 
Last edited by jkyoho,
Hi everyone, I have an EDM-030 motherboard with the same BLOD codes: two C0020303s followed by 80810001.

I measured the standby voltage and found that the TLV62090 on the back of the motherboard had no output voltage. Replacing it didn't solve the problem. I then discovered that pin 13 had no input voltage, and although this pin leads to the front of the motherboard, I haven't been able to find where it leads.

Can anyone help?

1779257836565.png

1779257852171.png

1779257875912.png

1779257883473.png
 
Good morning, here we go again with this cursed 80810001 error. Could someone help me out? I can’t find any obvious short circuit. The board powers on for a second, the fan starts spinning, and then everything shuts down.


The power sequence stops at 196 mA, while on a working board I measure around 220 mA, so I assume that something is failing to initialize already during the preboot phase.


If it helps, this is the full error string:


80810001 FFFFFFFF FFFF0023 10000100 216D 0036 FFFF 19A0:F4


Going from memory, that “216D” should be related to something involving the SoC/SSD section, but after checking the entire area around the controller I can’t see or find any anomalies.
 

Site & Scene News

Popular threads in this forum