HFW 4.89.1 (Hybrid Firmware) Official Release -

[Coro]

modified version of PS3Xploit's "flash dumper v 2.0.2"

that is for older firmware so useless right now. an update for it is being tested so maybe soon you can just go to cfw.

 

[STLcardsWS]

This HFW is not working for me on CECHG model. .

If the PUP installed / running and its an official HFW release, then it worked.
It would be your PS3HEN setup not working
HFW is nothing special (in terms of features), its 99% the same as OFW,
until you start making additions, after PS3HEN is running.

What is different about HFW is that it takes the patched webkit in 4.89 and replaces it with the unpatched one from 4.82.
Since this is such a small modification, the scene were lucky it could be repacked and installed on OFW like a regular firmware on a unmodded system,
This just brings back a patched exploit (patched in frmware) to be used again.

That was Sony's last attempt to curb exploits on the PS3 and worked for a small time until joonie discovered this clever trick for creating HFW that brought back a patched exploit.

Then bguerville ps3 toolset (for cfw models) relies on a completely different exploit, separate from all other PS3Xploit tools of the past and present as those rely on the bug in the webkit from 4.82, then the porting of it in HFW where as toolset is using a different exploit all together. .

HFW by itself is just OFW with a 4.82 webkit, so if things do not work on it, its the things being installed on it. So first thing would be the PS3HEN setup to look into and make sure its operating as it should be. .

 

[Lasaif]

that is for older firmware so useless right now. an update for it is being tested so maybe soon you can just go to cfw.

Well, I know it is for firmware 4.00 to 4.85 and by looking at the source code of enablehen :

if (fwv == "4.85") {
        (toc_addr = 7296344),
          (gadget1_addr = 620036),
          (gadget8_addr = 131072),
          (gadget_mod1_addr = 6352856),
          (gadget_mod2_addr = 80756),
          (gadget_mod3_addr = 757248),
          (gadget_mod4a_addr = 890500),
          (gadget_mod4b_addr = 4376440),
          (gadget_mod4c_addr = 346864),
          (gadget_mod7_addr = 108204),
          (gadget_mod8_addr = 2862264),
          (gadget_mod9_addr = 68384),
          (gadget_mod12_addr = 6500860),
          (gadget_mod15_addr = 3788856);
      }

      if ((fwv==="4.86") || (fwv==="4.87") || (fwv==="4.88") || (fwv==="4.89")) {
        (toc_addr = 7296344),
          (gadget1_addr = 620036),
          (gadget8_addr = 131072),
          (gadget_mod1_addr = 6352856),
          (gadget_mod2_addr = 80756),
          (gadget_mod3_addr = 757248),
          (gadget_mod4a_addr = 890500),
          (gadget_mod4b_addr = 4376440),
          (gadget_mod4c_addr = 346864),
          (gadget_mod7_addr = 108204),
          (gadget_mod8_addr = 2862264),
          (gadget_mod9_addr = 68384),
          (gadget_mod12_addr = 6500860),
          (gadget_mod15_addr = 3788856);
      }

These values are apparently exactly the same for for FW 4.85 to 4.89. If that is true, then the only thing needed is including these values in the flash dumper which what I did and I got a good NAND dump with only one warning:

******* Checks completed *******

Total number of checks = 113
Number of dangers = 0
Number of warnings = 1

Following check(s) returned a
WARNING!
  011.03   cell_ext_os_area Break Section

I have read on another thread that this warning can be safely ignored. Still, I wouldn't risk bricking my console without a hardware flasher in my toolbox.

 

[Lasaif]

If the PUP installed / running and its an official HFW release, then it worked.
It would be your PS3HEN setup not working
HFW is nothing special (in terms of features), its 99% the same as OFW,
until you start making additions, after PS3HEN is running.
.

That might be the case, HEN itself installs and runs without any apparent issue but lunching any homebrew will result in a black screen afterword. I tried the explorer plugin fix and it did not work either.

Then bguerville ps3 toolset (for cfw models) relies on a completely different exploit, separate from all other PS3Xploit tools of the past and present as those rely on the bug in the webkit from 4.82, then the porting of it in HFW where as toolset is using a different exploit all together. .

Since bguerville ps3 toolset is a PHP web application, my initial guess is that it is a combination of a flash dumper, checker and writer. All relies on exploiting the buggy ps3 web browser. The source code of these three elements are available and can be combined using PHP or Node.js into a single application with a nice HTML interface. But since you mentioned this, I guess this estimate of mine is wrong..

 

[kostirez1]

These values are apparently exactly the same for for FW 4.85 to 4.89. If that is true, then the only thing needed is including these values in the flash dumper which what I did and I got a good NOR dump with only one warning

Your approach isn't wrong, good job!
There were however some problems with the memory search function that made it unstable when modifying contents of the HTML (+ javascript). It was so unstable that you could change a single character anywhere on the page, and it wouldn't work anymore. Fortunately for all of us, bguerville has fixed this issue and posted about it when working on his PS3 Toolset. It wasn't hard then to port the fix to HFW flash dumper and flash writer.

my initial guess is that it is a combination of a flash dumper, checker and writer.

If you oversimplify it and only consider the core functionality, then yes, it's basically that.

The source code of these three elements are available and can be combined using PHP or Node.js into a single application with a nice HTML interface.

For a single purpose page (single firmware version, dump, write), you don't really need a backend code. There is already a port of the PS3Xploit project to 4.89 that combines the dumper and writer. Hopefully there are no other issues, and it can come out soon after being tested.

 

[Coro]

If that is true, then the only thing needed is including these values in the flash dumper

my bad, i thought you were talking about the flash writer.