Category PS4 Guides and Tutorials       Thread starter BwE       Start date Mar 10, 2019 at 12:43 AM       13,102       76            
A few months ago I posted a BwE Complete PS4 NOR Removal Guide followed by my BwE PS4 NOR Comparator, and today's Tutorial covers a lesson in corruption repair on PS4 NOR Repairs by Better Way Electronics.

Here in my favourite example we have a dump that does not boot, is ultimately displaying signs of a BLOD but when the dump is validated it shows the following results:

Code:
UNK Dynamic PerConsole Section Filler 2: ✔
UNK Static Section 1: 000000 [DANGER]
UNK Dynamic Section 20 (SKU Byte): 00 [DANGER]
UNK Dynamic Section 21: 0000000000000000000000000000 [DANGER]
UNK Filler 4: ✔
UNK Dynamic Section 22:
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 ✔
UNK Filler 5: ✔
UNK Dynamic Section 23:
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF [WARNING]

Well large blocks of 00 is obviously not good, but what about the UNK Dynamic Section 23? Well I give this area (and the areas below it) WARNING's as it generally has blank spaces sporatically throughout its section. So no big deal! I just can't explain why there are blank spaces!

The real issue is the UNK Static Section 1 and UNK Dynamic Section 20-22. Hence the DANGER output!

If you were to open this dump in a hex editor (I prefer HxD) you would see from 0x1CE000 to 0x1CE1FF (A length of 200) you would see this:

BwE PS4 Dump Repair 1.png

Now this corrupt dump is a CUH-1001A on version 6.20 - If I were to look at a similar dump, with similar specs I would see:

BwE PS4 Dump Repair 2.png

Its quite clear what the solution is! Copy this data from the working dump into the corrupt dump! But Should I?

Well luckily the above static section and dynamic sections that were corrupt are GENERIC. This means they are not tied down to a specific console or even version.

To explain a bit better, here is a quick run down of the possible results for the corrupt area:

The possible outputs for the UNK Static Section 1 are only going to be 0007FF (Unless you are stuck in IDU mode, it will be 0107FF - which I consider a 'DANGER' output). So its quite obvious that there is no other replacement for this corruption!

The next area is the UNK Dynamic Section 20, it is a bit different as it is based on the SKU of the console. The possible outputs are: 07 (Retail) or 06 (Dev/Test). It is again very obvious what to replace it with. Easy!

Now the UNK Dynamic Section 21 is a bit more weird as it is dynamic but can also be static among multiple consoles with very different SKU's and versions. For example, 28 of my dumps have this as the result: 0007FF0700030C04000000040000. This makes it easy to replace! If it didn't work, I would have tried the other results (there are not that many).

The UNK Filler 4 was always going to be blank space, but was it FF space or 00? Well that was easy to figure out.

UNK Dynamic Section 22 is the most complex section. While it is dynamic I was able to prove through my research that it is NOT tied to a specific console. It is highly dynamic, maybe only 2 of 100 consoles will have the same result, but when they do they are totally different SKU's and versions. I ultimately have no idea what this section is, but I do know it's transferable!

Again, the final UNK Filler 5 is a simple fix!

The final result is that logically, I can feel safe in copying the area from 0x1CE000 to 0x1CE1FF verbatim from a similar console! So I did!

So I ran the patched dump in my validator again and ta-da!

Code:
UNK Dynamic PerConsole Section Filler 2: ✔
UNK Static Section 1: 0007FF ✔
UNK Dynamic Section 20 (SKU Byte): 07 (Retail) ✔
UNK Dynamic Section 21: 0007FF0700030C04000000040000 ✔
UNK Filler 4: ✔
UNK Dynamic Section 22:
F9020000F90200009885B400000000003401000034010000A881B700000000006602000065020000AC901C01000000004D000000 ✔
UNK Filler 5: ✔
UNK Dynamic Section 23:
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF [WARNING]

The results come up perfectly! (Ignoring the WARNING). Putting this data on the PS4 resulted in it booting up once again! No more BLOD! Amazing!

This is why my BwE PS4 NOR Comparator tool is so damn useful, this is the best method for understanding what areas of a corrupt console can be patched!

Remember if you want to help my BwE PS4 NOR Validator, send me dumps (but please label them (version, model & issue etc))!

If you like what I do, or just like me for me, buy me a coffeeeee!
BwE Logo.png

BwE PS4 NOR Repair Guide by BetterWayElectronics.jpg
 

Comments

BwE

Developer
Senior Member
Contributor
I just want to make it clear, any area that isn't perconsole or coreos has some chance of repair (unless you're lucky). Just find the area of corruption, use my comparator tool and see what should be there. Now obviously some people don't have the same amount of dumps as I do or even the background knowledge of what the results mean, but this is why I am here. Ask me!

It's not like you can stuff up a corrupt dump any further. Just keep testing patches and so on.

Note my validator has patching capabilities and can even determine the address and length for you for some patches.

Have fun!
 

pearlxcore

Developer
Senior Member
Contributor
Thanks for this. Is it recommended to compare and patch the corrupt area with only dump from same model or or also have to be same firmware version?

It would be nice if you share the ‘uncorrupted’ area of working ps4 slim and pro.

You already have patcher for this?
 

BwE

Developer
Senior Member
Contributor
@pearlxcore same model is more important than version. But then some areas are firmware focused and some aren't... So I try and match 1000 series with 1000 and 1100 etc as there are plenty of bytes that signify what the model is. Then from there worry about firmware.

In the OP, the firmware of the patch data was not the same, and it was from a 1100 series (1000 and 1100 are the same according to my validator) :)

What do you mean share uncorrupt data of a slim and pro?

My validator can patch files into dumps, it has since first release!
 

koosknlo

Senior Member
Contributor
Verified
Is this possible wit a 5.05 dump from different console and change id or stuff like that to downgrade??

Like ps3 patch the nor
 
Recent Articles
Latest PlayStation 4 Game Trailer Videos from Gamescom 2019
Earlier this week we saw a Call of Duty: Modern Warfare 2v2 Alpha PS4 trailer video from Gamescom 2019, and below is some more fresh PlayStation 4 video game footage from this year's Gamescom...
Chiaki: Free and Open Source PS4 Remote Play Client by Thestr4ng3r!
Last month we reported on a PS4 Remote Play open source client in development by thestr4ng3r, and today he released Chiaki... the first free and open source PS4 Remote Play client software for...
Sony Patent Surfaces on Rumored PlayStation 5 / PS5 Development Kit Design
Although Sony's next-generation PlayStation 5 console isn't expected until the 2020 holiday season, today Andrew Marmo tweeted about a rumored Sony Interactive Entertainment patent...
CoD: Modern Warfare 2v2 Alpha Gamescom 2019 PS4 Trailer and Tips
The public Gamescom 2019 event runs from August 21st through the 24th, and during the weekend of August 23rd through the 25th gamers will be able to play the Call of Duty: Modern Warfare 2v2 Alpha...
Top