Need Help with NOR issue on PS4

  • Thread starter Thread starter Giants
  • Start date Start date
  • Views Views 998
  • Replies Replies 3

Giants

New Member
Newbie
Joined
Aug 17, 2025
Messages
4
Reaction score
4
Trophies
0
Age
53
XP
19
Country
France
Hi every body !

I got a PS4 slim SAD-001 & BT J20H091.
I completely reset the console and now I'm stuck on “press the PS button.”

The button is NOT detected by the console.
Of course, this has nothing to do with the controller (which works fine and is detected in safe mode).
Searching the internet, I came across a problem with corruption during a failed update. (NOR corrupt)

OK, goint to desolder the mx25L25635FZ2I chip and ran it through my CH341A to dump everything.
I launch PS4 weetools pro 1.0.8 and sure enough, I get a nice FW Fail when checking the S0_eap_Kbl partition.

We extract the partitions, check sflash0s0x33, and sure enough, there is data, but not all of it... which explains everything.

Well, I'm having fun trying everything (with the help of chapGpt because this tool is a factory) to try to rebuild this partition.
Note: I don't care about recovering anything, I just want a functional console.

Nothing works, it stuck with the same CRC and the same error (even after reconstruction).

It seems that it can't recreate this partition because my personal console data in S0_eap_kbl of my dump
no longer contains all the necessary information... (nice...)

It seems that I need to find a ‘healthy’ dump from the same console revision.
This seems impossible to me... I haven't found anything on the internet that fits the bill.

The GitHub pair C0020001 (which does not contain my version of BT)
or the pairs of files fws/eap.. emc..syscon... torus (found on GitHub)
do not seem to be sufficient to rebuild the partition.

If anyone has any information that could help me move forward or correct me if I've made a mistake,
or simply help me with this issue,

I'm all ears.
The goal is to save this console.
 
Other console, exactly same model (but this console work)
And same 'issue' with ps4-wee-tools-pro-v1.0.8
s0_eap_kbl : [.....] Fail FW Fail

Nobody have idea ?
 
Nop !
He use another tool to extract each 'partition' of the dump (like ps4-wee-tools-pro do)
He use a 'template' of wifi module to re-write the selection of his dump.
We don't have a 'template' as I know for J20H091 chip on Sad-001
and it's not sure this is my issue.

The question is, Why I have exactly a Fail FW Fail on sflash0s0x33
2 dumps of exactly same model of console/chip/...
Ps4_#01 is working week
Ps4_#02 don't recognising the PS button (but PS button working well on 'safe mode')
I don't understand this 'Fail FW Fail' on ps4-wee-tools-pro-v1.0.8...
present on Working ps4 and present on non-working ps4

It's...not logic.
 
  • Like
Reactions: bonkmaykr

Site & Scene News

Popular threads in this forum