FW Revert Not changing regardless of slot swap & UART not reporting.

  • Thread starter Thread starter Rasa39
  • Start date Start date
  • Views Views 1,210
  • Replies Replies 6

Rasa39

Pervert Deluxe
Member
Joined
Aug 16, 2015
Messages
783
Reaction score
812
Trophies
2
XP
3,971
Country
United Kingdom
So I've attempted a revert of my ps4 pro.

For the Nor, I have made several files for the swap, all with UART enabled. However when I run the console, PUTTY gives me a blank readout on UART, the cursor moves but nothing displays, like what happens in moddedwarfare's old video about UART before he runs the ps4debug payload.

PS4 wee tools told me to patch my syscon with method B. I flashed this method after my Nor, but I get a long blod. Flashing the original files back boots the console to the original fw.
When I patch the syscon with method A or C, it boots even with the patched Nor I have tried so far, the problem is both slot switch 3 and 4 (for pro model) don't seem to have an affect, it still boots into the old firmware. Does this mean the syscon patch with A or C isn't registering the Nor slot swap at all?

Does anybody know what I'm doing wrong to get UART to not display the logs, I followed the guide and checked all my wiring, it is seeing something it's just acting like it's still decrypted from the look of it.
I'm hoping I just need to keep trying different Nor slot swaps, but if the console keeps booting into the same firmware, even when I'm swapping through the slots, does that mean it's the syscon that's the issue? Again syscon method B causes a blod and a small blank readout on putty, but without UART actually showing me the logs, I can't tell what firmware it's trying to boot into with that version of the syscon patch.

My syscon has debug enabled now with the glitch pin put back down as instructed, and ps4 wee tools states it is "probably patcheable".

Any help would be greatly appreciated.
 
Edit: Nvm I found the answer, my previous slot has been overwritten with the current firmware after a factory reset or when I reinstalled the firmware on the hdd, apparently that wipes the lower firmware in the backup slot.

Time to update and grab a lua demo I guess, then see if I can revert back to my current fw and inject the license.
 
Last edited by Rasa39,
  • Like
Reactions: KiiWii
If you are now on 12.02, you can update and get the demo and after that revert back to 12.02. That's what I did with my son's ps4 slim.
 
Edit: Nvm I found the answer, my previous slot has been overwritten with the current firmware after a factory reset or when I reinstalled the firmware on the hdd, apparently that wipes the lower firmware in the backup slot.

Time to update and grab a lua demo I guess, then see if I can revert back to my current fw and inject the license.
Does a factory reset always overwrite the backup slot?
 
Does a factory reset always overwrite the backup slot?
If done through the ps4 system, I'm not sure, but according to what I found, it stated that a factory reset through safe mode always overwrites the backup slot.

I confirmed this by using the "legit CoreOS swap" method in PS Wee Tools which asks you to reinstall the same system firmware after you make an initial Nor and syscon dump from safe mode, as it causes the slot to switch to the backup and can therefore be used to compare the two dumps and find the real swap file, rather than guessing with the traditional method.

This is apparently the same as a reinitialisation/factory reset from safe mode.
 
I did the same thing and now I have the same problem, but I have nor and syscon dumps that are before factory reset but they are also latest firmware dumps, can I use them to downgrade anyway?
 
So I've attempted a revert of my ps4 pro.

For the Nor, I have made several files for the swap, all with UART enabled. However when I run the console, PUTTY gives me a blank readout on UART, the cursor moves but nothing displays, like what happens in moddedwarfare's old video about UART before he runs the ps4debug payload.

PS4 wee tools told me to patch my syscon with method B. I flashed this method after my Nor, but I get a long blod. Flashing the original files back boots the console to the original fw.
When I patch the syscon with method A or C, it boots even with the patched Nor I have tried so far, the problem is both slot switch 3 and 4 (for pro model) don't seem to have an affect, it still boots into the old firmware. Does this mean the syscon patch with A or C isn't registering the Nor slot swap at all?

Does anybody know what I'm doing wrong to get UART to not display the logs, I followed the guide and checked all my wiring, it is seeing something it's just acting like it's still decrypted from the look of it.
I'm hoping I just need to keep trying different Nor slot swaps, but if the console keeps booting into the same firmware, even when I'm swapping through the slots, does that mean it's the syscon that's the issue? Again syscon method B causes a blod and a small blank readout on putty, but without UART actually showing me the logs, I can't tell what firmware it's trying to boot into with that version of the syscon patch.

My syscon has debug enabled now with the glitch pin put back down as instructed, and ps4 wee tools states it is "probably patcheable".

Any help would be greatly appreciated.
I want to attempt this as well. Do you have a guide on how to accomplish this on a PS4 PRO specific. Do you know what type of motherboard you have?
 

Site & Scene News

Popular threads in this forum