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

Vincentted

Member
Contributor
OMG, thank u so much @egycnq then if I replace nor chip and syscon along with new cell, it will work? If yes, that would be great! I will get a new board asap. Thanks for the information
 

Chaos Kid

Developer
Senior Member
Contributor
Thanks to the dev who made this for others one main problem for guys like us using ryzen7 have issues with the software it don't let it load on windows 7 it just hangs

Just so you know
 
  • Like
Reactions: BwE

thiagomaxxx

Member
Contributor
Great job, I have a problem reading the SPI of a slim ps4 that I believe is having a problem with nand, I believe Way-launcher does not yet have support for this model of spi winbond 25q256jveq. the ps4 problem: he start's with blue light without spin the cooler, after 20 seconds he power off alone, i had tried everything, change's the PSU, reball on APU, CXD change and nothing.

@BwE any suggestion to read a winbond 25q256jveq with way launcher
 
  • Like
Reactions: BwE

BwE

Developer
Senior Member
Contributor
@pearlxcore absolutely, the more dumps I get the easier it becomes

@zecoxao hahaha I see it, but I may have to restructure my program to accommodate. I will just add a separate validation for it later. My program validates every single bit of the NOR regardless.

@egycnq at that stage you just buy a new ps3. Or save some time and buy a working ps3 and put your flash and syscon in it, saving the cell reballing. I've never done this for customers, too expensive.

@Chaos Kid you can't get my program running on ryzen? Owch. Well I did convert my programs to 32bit...

@thiagomaxxx the 25xx ps4 NOR can definitely be read. Something else is wrong. You could have fried the chip or soldered it wrong.


 

Chaos Kid

Developer
Senior Member
Contributor
Yes that's correct bwe seems the mobo is the problem and won't load I tried everything but figured I'd let you know the issue exist for people who use X370/X470 mobo where seems old programs don't work
 
Recent Articles
Nintendo (NES) PS2 on PS4 Emulator FCEUX Port PKG by Irfanansarionl9
Proceeding the PS4NES Emulator, PS4 v5.05 Port, PS4NES v1.01 Update and RetroArch QuickNES Port comes a Nintendo Entertainment System (NES) PS2 on PS4 Emulator FCEUX Port PKG from irfanansarionl9...
Blood & Truth Hits PS VR Next Week Among New PS4 Releases
Next week three heavy hitters land on PlayStation VR amongst the new PS4 game releases, namely The London Heist follow-up Blood & Truth, Five Nights at Freddy's VR: Help Wanted and also Trover...
Crash Team Racing: Nitro-Fueled Adventure Mode PS4 Gameplay, Details
Last month we saw a demo of rival Team Sonic Racing, and today Beenox Co-Studio Head Thomas Wilson shared a look at the CTR Adventure Mode in their upcoming kart racer Crash Team Racing...
Shoot Test PS4 Homebrew PKG by Lapy05575948
Following his Overcome: Save the Girl Edition PS4 PKG, today PlayStation 4 developer @Lapy is back with a Shoot Test PS4 PKG on Twitter stating the following: This is not the game that I have...
Top