Category PS4 Guides and Tutorials       Thread starter BwE       Start date Mar 10, 2019 at 12:43 AM       12,032       73            
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

jd200

Senior Member
Contributor
Verified
Well I soldered wires at first attempt to the chip. still attached to the mb and lifted the vcc pin and it showed the chip name ect but when tried to read the chip it said cant read the chip is locked so I just desoldered it all
 

XfactorX

Senior Member
Contributor
Verified
@BwE
Yes, it's messy :rolleyes:
but the intention was to do something on the fly so I didn't worry about the aesthetic part, the important thing is that I could read Nor correctly the first time, I made 4 dumps one after the other.

PS: With the 1xxx series chips I also prefer to remove it from the motherboard
 

XfactorX

Senior Member
Contributor
Verified
For those who need to dump the Nor chip from ps4 equipped with 8-WSON chip packages, and that do not have the equipment or the ability to unsolder the chip from the motherboard, they can wire the Teensy 2 ++ board using the diagram illustrated in the three images below.

Note that contrary to what I wrote on post #50, following further tests, there is no need to remove the 4.7K resistor on the CS # point and the diode on the VCC point, of course, it is always necessary to use shortest possible wires.




 

BwE

Developer
Senior Member
Contributor
@XfactorX Very nice! So no need to ground VCC or anything special like that? Im surprised!

Note my validator is in dire need of an update given that this thread has made more people send me dumps. Its mostly within the CID and UNK areas on slims and pros. Im surprised I was spot on with every other area. Looks like most of the firmware updates don't touch much else.
 
Recent Articles
Deadpool 60 FPS Mod PS4 Package (PKG) by Wastelander121
Last week he made available a Dishonored: Definitive Edition 60 FPS Mod PS4 PKG, and today @Wastelander121 returns bringing a Deadpool 60 FPS Mod PS4 PKG (CUSA-03528) via Twitter with a...
Wolfenstein: Cyberpilot & Wolfenstein: Youngblood Join Latest PS4 Games
PlayStation VR fans can expect to see Wolfenstein: Cyberpilot arrive on PS VR while Wolfenstein: Youngblood hits PS4... both on July 26th: :) Wolfenstein: Cyberpilot puts you in the action on...
IG Tools: Insomniac Games Reversing and Modding PS4 Tools
Following recent Spiderman PS4 Decryption and PS4 Remote Play Protocol Reverse-Engineering development comes IG Tools this weekend by doesthisusername, which are a collection of Kaitai Struct /...
FFVII Dreamake: Final Fantasy 7 Remake in Dreams by Sosetsuken5360
Last month we saw a Metal Gear Solid HD Remake playable in Dreams on PS4, and this weekend another noteworthy creation dubbed FFVII Dreamake (a fan-made Final Fantasy 7 Remake) by Sosetsuken5360...
Top