PS3 4.87.1 PS3 HFW (Hybrid Firmware) - HFW is helpful for installing PS3HEN on 4.84/4.85/4.86/4.87 FW

UPDATE (May, 2022) 4.89 HFW Released see here.

---

. Original Article (4.84 HFW - March 2019): Huge News as the PS3 exploit ladder has taken a step up into 4.84 rung, with a new approach to bring back PS3Xploit functionality on 4.84. With a Hybrid Firmware (NOT A CFW) that can be installed on ANY MODEL PS3 over any Official Firmware (OFW) version. .The only thing this modified firmware essentially does is bring back the patched webkit from OFW 4.82 that was an entry point for PS3Xploit, if you recall when 4.84 was released developers @bguerville and @esc0rtd3w stated the exploit was not actually patched but rather only the webkit entry used was removed in 4.83+ which rendered the actual exploit unreachable (not patched and could be restored). Now the webkit is back for 4.84 OFW thanks to this new clever magic that has allowed OFW user's to use and install this slightly modified Firmware.​

So, what does all this mean? Now it will be just like it was back in 4.82 before PS3Xploit was "patched"(some ps3xploit tools need updated still) you will be able to install a CFW (on a CFW compatible model) and for those unfortunate user's that does not have a CFW Compatible model (i.e. SuperSlim/late slims) you have will have access to the HAN exploit . So for new user's or ones that updated, here is your second chances thanks to the efforts of the members of PS3Xploit Team and to @Joonie (waved magic wand on files) and prepared this magically release, @habib (for valuable input on this project) and @esc0rtd3w (work in porting ps3xploit tools to 4.84) ​

It has been an exciting month here at psx-place with so much progress on all fronts of the PS3 . the fuel of this project actually comes from a user simply igniting a spark with an idea as @Doge_Rules did with this thread truly making it a community effort. Updated - to version 4.84.2 (see details below)​

-STLcardsWS​

​

4.91 HFW 4.90 HFW 4.89 HFW 4.88 HFW 4.87.1 HFW 4.86.1 HFW 4.85.1 HFW Original 4.84.2 Release (via Joonie) SPECIAL INSTRUCTIONS

• 
  Joonie is back again with 4.91 HFW
  
  • (March 2024) > HFW 4.91 (Hybrid Firmware)
  
  
• 
  Joonie is back with an update to 4.90 with 4.90 HFW.
  
  • (March 2023) > HFW 4.90.1 (Hybrid Firmware)
• 
  4.89 HFW
  
  • https://www.psx-place.com/threads/hfw-4-89-1-hybrid-firmware-official-release.37319/
• 
  4.88 HFW:
  
  • https://www.psx-place.com/resources/4-88-1-hfw-hybrid-firmware.1249/
• 
  
  UPDATE 4.87.1 RELEASED:​
  via @Joonie:
  It's been a while, saw a new FW dropped today. So here's yet another one for everyone.
  
  https://mega.nz/file/fAJFwSqL#PeQfhVjbGAi69S4Jr369Tly4trG4Y9ALqdlUIBzW8qk
  
  Since there's no change in the kernel, you may see a PS3HEN update anytime soon.
  
  Have fun and stay safe at home.
  
  
  >> Release Post <<​
• 
  Release Post via Joonie

  ---

  .
  4.86.1 (HFW) Hybrid Firmware​
  It's been a while, saw a new FW dropped today. So here's yet another one for everyone.
  
  https://mega.nz/#!zIpFnDjB!PwJVSc15POf0jzFDQuUllxJahdzpnb48TW74hJOgjyc
  
  Since there's no change in the kernel, you should see a PS3HEN update anytime soon.
  
  Have fun and stay safe at home.​
  
  
• 
  Release Post via Joonie

  ---

  .Here's a little gift for everyone who has working PS3 (excluding RSOD or broken BD/BT units)
  
  Here's what we have found.
  

  1. no changes in Kernel
  2. no changes in VSH
  3. no changes in isolated loaders
  4. Stability improved

  
  Enjoy your latest HFW 4.85.1 and stay tuned for more updates coming from various developers.
  
  Download link : https://mega.nz/#!SAYhnYYB!6CmxOz0H_pSuVRb4YZ7-lYvY66hP0LlohgVMWfFut4Q
  
  FYI @STLcardsWS @esc0rtd3w @habib @Zar @aldostools
  
  To devs - PS3HEN can literally be ported in 5 mins. or you could just use PS3HEN 2.3.1 and it should work right out of the box.
  
  To everyone else - Don't rush your update until all the tools get fully ported & released.
  
• 
  
  4.84.2 HFW (Hybrid Firmware)
  Restores PS3Xploit Flasher/Tools & PS3Xploit HAN for 4.84 OFW user's​
  
  
  Today, we proudly present the very first modified OFW that can be installed on all PS3 models. (NOTE: THIS IS NOT A FULL BLOWN CFW, HOWEVER IT Allows you to run the patched webkit exploit that's ported to 4.84)​
  
  Yes, you didn't hear wrong, it can be installed over
  
  • ALL OFW versions on ALL PS3 models
    • ex) OFW 4.83, 4.84 , CECH-3XXX, CECH-4XXX and etc..
  
  We wanted this to be called "HHHFW" since it was Hybrid, Hack-able, HAN ready also inspired by @habib but let's call it HFW since this is Hybrid FW (Well you can call this MFW).
  
  The idea was reminded by some guy who didn't want to be annoying but actually ended up being helpful: @ psx-place.com
  
  Habib had this idea long time ago but the previous attempt was not successful due to lack of interest and preparation.
  
  As you all know, I recently started messing with my PS3 again and this idea was brought back.
  
  So then I went ahead and tried his magical idea.... after a few hours later... Boom!!, now we have HFW that works on all PS3 models (including 3K and 4K) that allows the previously patched exploit by using old webkit from 4.50 that's been used until 4.83. This method is rather hacky than technical, so I would like to leave this method under the radar for now until it gets patched out (this can easily be patched).
  
  What can you do with this HFW 4.84.1/2?
  
  1. You can use PSN since the FW is the latest.
  2. You can downgrade/Install CFW on your PS3 if your model is downgrade-able/hack-able (excluding CECH-3K and 4K)
  (The same capability as what you had for 4.82 OFW)
  3. You can use HAN and all the tools that worked up to 4.82 with this FW.
  4. You can always go back to the real OFW 4.84 if you wish.​
  
  To all scener's and developers
  
  • Please update the HAN toolbox or any xml that can support 4.84 if anyone's available.
  
  
  
  
  ​
  
  
  Special thanks @habib @bguerville @esc0rtd3w @Doge_Rules @DeViL303 @littlebalup​
  
  

  ---

  .UPDATE 3-22-2019 - 4.84.2 Released

  ---

  .​
  HFW 4.84.2_PS3UPDAT.PUP
  
  • Bugfix : Fixed the installation issue with regions that use following languages
    English (UK), Turkish (Turkey), and Portugal (Brazil) , Thanks to @citra mulia to report the bug
  • 
  

  ---

  ,​
  System Update displaying 4.84.1 HFW
  
  
  
  
  PS3Xploit Tools running on 4.84 HFW
  
  
  
  
  
  
  
• 
  
  DO NOT UPDATE WHEN A NEW OFW FIRMWARE UPDATE IS RELEASED!!!​
  
  -STLcardsWS​
  Here is a video tutorial by @MrMario2011
  
  
  
  
  

Release Thread & Download: HFW 4.87.1

---

.Update May 2022 https://www.psx-place.com/threads/p...-the-ps3-exploit-for-noncfw-ps3-models.37273/

UPDATE JAN. 2023
Mirror's HFW Downlaod's :
LINK

​

 

Try my latest resigner
If it errors out still simply don't resign pkg just resign the rap file and you should be done!

Oh sweet. Okay I'll give that a try then! Thanx

 

Try my latest resigner
If it errors out still simply don't resign pkg just resign the rap file and you should be done!

I forgot to mention this but there was a bug in your resigner tool that caused EBOOT files to be resigned randomly, it only happens with certain games and I'm not sure why.

I don't know if you fixed this in the latest version because I'm still using the older one, but wanted to let you know just in case.

 

Sorry if I'm being a noob here, but I'm kinda struggling to get the PUP file installed. My Ps3 recognizes both the usb drives I'm trying this with and I've even downloaded the file twice to make sure it's not a problem on my end. It's throwing me a no applicable update data was found error. I'm on OFW 4.84 on a SS CECH-4001B. Maybe I'm just not meant to install it yet? sorry for the trouble and massive congrats for this breaktrough.

If the usb is Fat32 , put the PUP file on this path and create folder if needed,

PS3/UPDATE

Renamae the PUP file to "PS3UPDAT" without "E"

So the final path to the PUP is

PS3/UPDATE/PS3UPDAT.pup

If it is not recognize use SAFE MODE to install it ,select System Update

 

I forgot to mention this but there was a bug in your resigner tool that caused EBOOT files to be resigned randomly, it only happens with certain games and I'm not sure why.

I don't know if you fixed this in the latest version because I'm still using the older one, but wanted to let you know just in case.

EBOOT???
You meant edat probably?
It resigns *edat, EDAT, CONFIG, ISO.BIN.ENC if found in a package

 

EBOOT???
You meant edat probably?
It resigns *edat, EDAT, CONFIG, ISO.BIN.ENC if found in a package

Nah I meant EBOOT, it's the reason why so many people had issues when resigning their games, but then they installed the pkg as is without resigning and it worked. I can verify this myself as I compared the original EBOOT with the one in the pkg, they were signed differently (or at least the header was changed).

BTW, signing the EDAT files in the pkg is not always a good thing, since some games have checks (I guess klicensee checks) which causes the game to reject the license and the content. I don't think it should be changed, but maybe an option could be provided to disable resigning of those files? Just a thought.

 

Nah I meant EBOOT, it's the reason why so many people had issues when resigning their games, but then they installed the pkg as is without resigning and it worked. I can verify this myself as I compared the original EBOOT with the one in the pkg, they were signed differently (or at least the header was changed).

BTW, signing the EDAT files in the pkg is not always a good thing, since some games have checks (I guess klicensee checks) which causes the game to reject the license and the content. I don't think it should be changed, but maybe an option could be provided to disable resigning of those files? Just a thought.

Edats klic is not changed, only ecdsa sig check is renewed of the existing header so no that's no problem and actually is nice.

Regarding eboot.....if you can send me two examples of eboot or alternatively pm me a pkg which would do this I can definitely check. Eboot resigning is not done so I would say eboot is corrupted.

 

Edats klic is not changed, only ecdsa sig check is renewed of the existing header so no that's no problem and actually is nice.

Regarding eboot.....if you can send me two examples of eboot or alternatively pm me a pkg which would do this I can definitely check. Eboot resigning is not done so I would say eboot is corrupted.

Yeah I wasn't sure how the EDAT files were modified I never really checked, regardless it causes issues with certain games and the content no longer works. That's why I no longer resign pkgs, there's a risk of the EBOOT becoming corrupted and the EDAT file issue.

I can try to pkg a few games and see which ones are affected, and I'll let you know after that.

 

Yeah I wasn't sure how the EDAT files were modified I never really checked, regardless it causes issues with certain games and the content no longer works. That's why I no longer resign pkgs, there's a risk of the EBOOT becoming corrupted and the EDAT file issue.

I can try to pkg a few games and see which ones are affected, and I'll let you know after that.

There is no edat issue. The signature is checked by vsh so it actually fixes something which vsh I'd checked would report as invalid.

Eboot one...definitely... in my tests they were fine and if you can extract eboot that means enc/dec is fine. The corruption is highly unlikely. I would need the specific pkgs which exhibit such behavior. Me and Joonie tested and everything went perfectly

 

There is no edat issue. The signature is checked by vsh so it actually fixes something which vsh I'd checked would report as invalid.

Eboot one...definitely... in my tests they were fine and if you can extract eboot that means enc/dec is fine. The corruption is highly unlikely. I would need the specific pkgs which exhibit such behavior. Me and Joonie tested and everything went perfectly

I verified it myself, I tested DLC content resigned with your tool and the content no longer worked (the game froze when checking the EDAT). Then I restored the original edat and the content worked.

If you don't believe me it doesn't really matter, it doesn't affect me, I just thought you'd want to know since a lot of users have had these kind of issues and don't know why.

 

I forgot to mention this but there was a bug in your resigner tool that caused EBOOT files to be resigned randomly, it only happens with certain games and I'm not sure why.

I don't know if you fixed this in the latest version because I'm still using the older one, but wanted to let you know just in case.

EBOOT shouldn't be resigned as the tool was designed to resign EDAT files for PSX and PSP, PKG type to HAN or DEBUG. and RIF finally.

From my previous test, resigning RIF was enough to run PS3 contents. not sure why this issue was reported. His tool shouldn't be resigning any EBOOT as it makes it impossible to run on OFW/HFW system due to missing ECDSA signature.

 

EBOOT shouldn't be resigned as the tool was designed to resign EDAT files for PSX and PSP, PKG type to HAN or DEBUG. and RIF finally.

From my previous test, resigning RIF was enough to run PS3 contents. not sure why this issue was reported. His tool shouldn't be resigning any EBOOT as it makes it impossible to run on OFW/HFW system due to missing ECDSA signature.

It was reported because it's an issue that other forum users have had and they don't know why. There are many posts on the forum talking about the bug but they don't actually realize why it happens. They say they resign the pkg, the game doesn't start (I forget the exact error), so they install the original debug pkg and the game suddenly works.

From memory one of the games was NFS Most Wanted 2012, maybe you can find the thread.

I agree it doesn't make sense that the eboot is being resigned, it makes less sense that it only happens with some games. I don't understand it either, but it's a legit thing and it happened to multiple people, not just me.

Anyway I'm currently testing a few games right now, so I'll get back to you when I get some results.

 

thank you but for my part does not work on my ps3 ultra slim 4204b EMMC the HFW 4.84.2 is not recognized on my USB mode without fail yet all and well put as it should

CECH-4004C tested and working, maybe its your USB, try install it through recovery.

Update Path: USB/PS3/UPDATE/UPDAT. PUP

Sent from my G8341 using Tapatalk

 

Okay, after some research the error is 80010007, generic EBOOT error. Check this thread here https://www.psx-place.com/threads/han-error-80010007-when-booting-up-mirrors-edge.21294/ - this guy had this issue and all he did was resign the game, yet he says he got the error indicating the EBOOT was modified.

I got the exact same error with the exact same game a couple months ago, but I fixed it by installing the original pkg. I obtained the game from Sony's servers, so there is no possible way that the EBOOT could have been modified.

I still had Mirrors Edge on my HDD, so I just re-packaged the game and resigned it, and the EBOOT was modified. I can send you the modified EBOOT and the original too if you like, let me know.

It is only a portion of the header that is modified, which makes me think it's somehow mistaking the EBOOT for an EDAT file. Incidentally, there is an EDAT file in the USRIDR, this may have something to do with it.

 

Okay, after some research the error is 80010007, generic EBOOT error. Check this thread here https://www.psx-place.com/threads/han-error-80010007-when-booting-up-mirrors-edge.21294/ - this guy had this issue and all he did was resign the game, yet he says he got the error indicating the EBOOT was modified.

I got the exact same error with the exact same game a couple months ago, but I fixed it by installing the original pkg. I obtained the game from Sony's servers, so there is no possible way that the EBOOT could have been modified.

OK, I understand that the EBOOT may have been corrupted/resigned by the tool, but is there any reason why one would resign the whole PS3 pkg when it's not needed?

PKG resigning was only required for PS2 to begin with. And some custom PS1/PSP packages that are RIF-less.

 

OK, I understand that the EBOOT may have been corrupted/resigned by the tool, but is there any reason why one would resign the whole PS3 pkg when it's not needed?

PKG resigning was only required for PS2 to begin with. And some custom PS1/PSP packages that are RIF-less.

Many users initially resigned every pkg simply because they thought it was required, I can't remember if this was mentioned in the release thread when HAN initially came out, but it was something that pretty much everyone did at first. It was mentioned in all of the tutorials (that I recall) at the time.

I agree that there's no reason to resign whole pkgs, it's a waste of time, it's just that in HAN's infancy, nobody knew any better.

The problem is easily solved, I just wanted to make you aware that it exists.

 

Many users initially resigned every pkg simply because they thought it was required, I can't remember if this was mentioned in the release thread when HAN initially came out, but it was something that pretty much everyone did at first. It was mentioned in all of the tutorials (that I recall) at the time.

I agree that there's no reason to resign whole pkgs, it's a waste of time, it's just that in HAN's infancy, nobody knew any better.

The problem is easily solved, I just wanted to make you aware that it exists.

@habib I guess we will need a solution to prevent unnecessary PS3 pkg conversion (which appears to be corrupting EBOOT) since it's not needed to activate the PS3 NPDRM content.

Not really surprising after all these years and people started to think updating CFW requires OFW installation and the NAND/NOR Flasher to install CFW again. A lot of people lost interest in PS3 and things get misinformed over time.

 

Not really surprising after all these years and people started to think updating CFW requires OFW installation and the NAND/NOR Flasher to install CFW again. A lot of people lost interest in PS3 and things get misinformed over time.

It didn't help that many users stated that resigning pkgs was required, people still believe that now. As soon as I read about the debug pkg enabler, I knew that resigning every pkg was absolutely pointless, unless you were installing a PS2 game.

 

It didn't help that many users stated that resigning pkgs was required, people still believe that now. As soon as I read about the debug pkg enabler, I knew that resigning every pkg was absolutely pointless, unless you were installing a PS2 game.

Yeah the reason why PKG conversion was introduced was to allow custom packed PKGs including PS1,PS2 and PSP. There's no reason for original PKGs to be resigned when they have no problem being installed as they are packed properly by $ONY.

Apparently people have been resigning everything because they think that's safer/better I suppose.

 

Guys when i install HFW 4.84.2 update through safe mode it stops at 50% and doesn't complete the install.. Please help -_-

 

Yeah the reason why PKG conversion was introduced was to allow custom packed PKGs including PS1,PS2 and PSP. There's no reason for original PKGs to be resigned when they have no problem being installed as they are packed properly by $ONY.

Apparently people have been resigning everything because they think that's safer/better I suppose.

Well, somehow there was a miscommunication somewhere, as most HAN users believe that resigning all pkgs is necessary.

I don't blame noobs for thinking that, when you have no insight into how HAN actually works and why it works, you kind of just accept what other people say without thinking about it. In their eyes, they have more knowledge, so they must be right about it.