PS3 4.89 Update is Live! - Discussions / Details about the firmware update

Please understand that a custom FW release is not the same than a homebrew release.
It can cause permanent damage to several users that trust on the forum.
I can make a bricker homebrew for a 5 minutes. No one can make a bricker FW that can be installed on non-CFW models because it can't be properly signed with current public tools.

But we have a working HFW 4.89.1 since many days
May you tell me how you got 4.89.1 HFW many days ago if 4.89 OFW was published less then week ago?

The current HFW 4.89.1 in private testing has no issues so far
So, there is an updated version of fwpkg that can properly sign tar and/or hdr?
 
I can make a bricker homebrew for a 5 minutes. No one can make a bricker FW that can be installed on non-CFW models because it can't be properly signed with current public tools.


May you tell me how you got 4.89.1 HFW many days ago if 4.89 OFW was published less then week ago?


So, there is an updated version of fwpkg that can properly sign tar and/or hdr?
The HFW @littlebalup is referring to was done shortly after @Louay posted his link, so it was after 4.89 OFW was released, obviously :)

I do not know anything about a newer version of fwpkg. Others may have the answer to that.
 
"Many" is relative. For me more than 3 can be considerer as many. I'm maybe wrong. English is not my native language. Note that I didn't said "week(s)".

In french I whould have said "depuis plusieurs jours".
I suppose "plusieurs" would have been better translated as "several" rather than "many" in this context.
But anyway, picking on a non native speaker's choice of words is cheap and low, you don't need to explain yourself, everyone had understood except maybe those who didn't want to.
 
I suppose "plusieurs" would have been better translated as "several" rather than "many" in this context.
But anyway, picking on a non native speaker's choice of words is cheap and low, you don't need to explain yourself, everyone had understood except maybe those who didn't want to.

cheap, low and embarrassing.....
 
There's so much talk about this new HFW that everyone (except people that is dedicating his precious time on this) is asking so many question that already were responded, developers/admins/mods are also having to dedicate their time to respond them. That's crazy. starting with bguerville (as all the great people we all know) which is a true example of a dedicated person of the Scene. Moderating the forum, responding stupid questions and also developing the fu&%ng firmware. What else do you need, all of you?

All the staff, including escort, aldos, littlebalup, etc, etc are working at it and you only need to wait with your ass stick to your chair. NOTHING ELSE.

If it's not ready, IS NOT. WAIT.

It's not that complicated. If you can't play online with your hacks, go and play something else, or study, read, watch videos or get a job. It's stupid that it's may 2022 and people still have ZERO sense about something so simple.
 
I can make a bricker homebrew for a 5 minutes. No one can make a bricker FW that can be installed on non-CFW models because it can't be properly signed with current public tools.


May you tell me how you got 4.89.1 HFW many days ago if 4.89 OFW was published less then week ago?


So, there is an updated version of fwpkg that can properly sign tar and/or hdr?
I can make a bricker homebrew for a 5 minutes. No one can make a bricker FW that can be installed on non-CFW models because it can't be properly signed with current public tools.


May you tell me how you got 4.89.1 HFW many days ago if 4.89 OFW was published less then week ago?


So, there is an updated version of fwpkg that can properly sign tar and/or hdr?
I can make a bricker homebrew for a 5 minutes. No one can make a bricker FW that can be installed on non-CFW models because it can't be properly signed with current public tools.


May you tell me how you got 4.89.1 HFW many days ago if 4.89 OFW was published less then week ago?


So, there is an updated version of fwpkg that can properly sign tar and/or hdr?
please friend respect the developers, they know what they are doing and at no time have they treated you badly you are on the defensive... just calm down and thank you very much for your support.
 
4.89.1 didn't work on non-CFW models, mine 4.89.2 works. The tools used to craft 4.89.2 can build any of the previous HFWs (except "broken" 4.89.1) with same MD5. 4.89.2 was done in exactly same way as "official" ones.

PS3 scene has lost a lot of developers lately. And instead of welcoming new people, you make things to turn
them around and walk away upset.

I think @esc0rtd3w kind of summed it up, so won't repeat what he said about the HFW

The PS3 Scene IMO has not lost many developer's there are various developer who go in active and re-appear and we see some leave and not come back much. Also we have seen new developer come into the fold. I think this is the same for any community or platform, Some developer work behind the scenes more as well and do not post here or this and that.. There is development all the time, its always been in waves but now its a legacy console so it will be less attention but also more attention by other's who are just getting into the platform.
 
The PS3 Toolset 1.2 update is ready and under testing as I write this post (thanks to esc0's devotion, for dedicating his hardware and some of his time to this task), Nat kindly provided us with a standard CEX release for 4.89 and a CoreOS, that helped test the new code in situ especially that behind the curtain, a lot of code has changed in preparation of the file manager tool addition which won't be rolled out just yet as it's not completely ready. Same thing for the xRegistry editor.
Both tools work fine already, the code looks strong so far but I haven't had time to finish some necessary Toolset GUI changes and theming for those tools yet, sorry about that. I don't control s#ny's timing and I have had other pressing matters to attend these past weeks.
Anyway I prefer to update now with less features than I had hoped rather than make people wait for 4.89 flashing capabilities.
Users will still be able to use a few new features with this 1.2 release like extended system information, syscon errors extraction, memory patching capabilities including HAN, debug PKG and custom patches as well as memory dumps to file and in theory the page load freezes on certain consoles should be gone.
At this point I am essentially waiting for littlebalup to update his pyps3patcher project, the Toolset update roll out should come just after, in line with the same patch file.
 
Last edited:
Well, this is not going to stop to release new versions of HFW/HEN/CFW for 4.89... is mostly a problem for the custom .rco files released before

I dont want to trigger the alarms yet (because im not sure if there is some easy way to solve it) but is a big problem, in plain words...
Half of the .rco files from 4.89 are incompatibles with the custom rco files that was compatibles with 4.88
And the percentage of "broken" rco's probably is way higher than half of them, because a single rco file could store tenths of values inside the layout.txt files... if only one of them is broken we should consider the whole .rco file is broken

As example... the only rco mods i know for sure that are not broken are the ones for custom_render_plugin.rco there is a changelog where it can be seen at which line inside the layout.txt files is storing his values:
https://www.psdevwiki.com/ps3/Custom_render_plugin
It stores 6 values, located consecutivelly at lines:
664+1
665+1
666+1
667+1
668+1
669+1

The displacement in the 4.89 layout.txt files happened at line 2580, this is why custom_render_plugin.rco has not been updated (it stores his values before the displacement)

Actually... the best way to know how many rco files are incompatibles with the layout.txt from 4.88 is to extract the contents of 4.88 and 4.89 and compare the MD5 of all the rco files
If the MD5 matches it means the rco mods released for 4.88 of that specific rco file are compatibles with 4.89

Otherway (if the MD5 is different) there is a huge probability that the rco mods published before (compatibles with 4.88) are going to be broken in 4.89

Even moving all rcos and layout files from 4.88 to 4.89 will still have bugs

- Impose_plugin: The battery icon is in the right corner of the screen (Edit fixed by basic_plugins.sprx)
- system_plugin: The notification is wider than it should. (Edit fixed by basic_plugins.sprx)
- wboard_plugin: The rss text is blinking. (Edit fixed by basic_plugins.sprx)
- explorer_plugin_full : Throphies are upsidedown (Edit fixed by explore_plugin.sprx)
- osk_plugin: Completely broken. (Edit fixed by osk sprxs)
- webbrowser : The shadow takes up all the screen (Even replacing all rcos + sprxs + layout files, this bug is still there)

Lots of sprx have been modified, video player. save data sprxs, osk (keyboard), all category sprxs, etc. (All of them are smaller) I wonder why.

It seems that for rco mods we will have to port them to 4.89, it's a pity that we don't have new dex firmwares, because I use the rebug 4.84.3 more than any other,

Remaning bug: probably tied to vsh.self
E3bTqb9.png


Interresting
Using regcam_plugin.sprx from 4.88 on 4.89 ENABLES BACK THE CREATION OF PSN ACCOUNTS THROUGH THE CONSOLE.

(Edit: Just like the 4.88 after the 4.89 release, the PSN refuses the account creation in the 3rd step)
 
Last edited:
Using regcam_plugin.sprx from 4.88 on 4.89 ENABLES BACK THE CREATION OF PSN ACCOUNTS THROUGH THE CONSOLE.
That's what happens when you don't revoke old binaries...

But when you mean"enables back", you mean you see the XMB GUI functions or you are speaking of the entire creation process? Or in other words did you create a PSN account on 4.89?
 
Even moving all rcos and layout files from 4.88 to 4.89 will still have bugs

- Impose_plugin: The battery icon is in the right corner of the screen (Edit fixed by basic_plugins.sprx)
- system_plugin: The notification is wider than it should. (Edit fixed by basic_plugins.sprx)
- wboard_plugin: The rss text is blinking. (Edit fixed by basic_plugins.sprx)
- explorer_plugin_full : Throphies is upsidedown (Edit fixed by explore_plugin.sprx)
- webbrowser : The shadow takes up all the screen (Even replacing all rcos + sprxs + layout files, this bug is still there)

Lots of sprx have been modified, video player. save data sprxs, osk (keyboard), all category sprxs, etc. I wonder why.

Remaning bug:
E3bTqb9.png



Interresting
Using regcam_plugin.sprx from 4.88 on 4.89 ENABLES BACK THE CREATION OF PSN ACCOUNTS THROUGH THE CONSOLE.

The web browser bug aint a big deal is it? Can't we install a 3rd party web browser and just use that?

And Other than the shadow we could still install hen on it if its still functional that's all that really matters
 
Last edited:
Even moving all rcos and layout files from 4.88 to 4.89 will still have bugs

- Impose_plugin: The battery icon is in the right corner of the screen (Edit fixed by basic_plugins.sprx)
- system_plugin: The notification is wider than it should. (Edit fixed by basic_plugins.sprx)
- wboard_plugin: The rss text is blinking. (Edit fixed by basic_plugins.sprx)
- explorer_plugin_full : Throphies is upsidedown (Edit fixed by explore_plugin.sprx)
- webbrowser : The shadow takes up all the screen (Even replacing all rcos + sprxs + layout files, this bug is still there)

Lots of sprx have been modified, video player. save data sprxs, osk (keyboard), all category sprxs, etc. I wonder why.

Remaning bug:
E3bTqb9.png
Is this from your MOD or represents the ps3xploit team?
 
The web browser bug aint a big deal is it? Can't we install a 3rd party web browser and just use that?
There are no 3rd party independent browsers afaik.
Modern web browsers are resource hungry beasts, open just one tab of Firefox on your PC and browse with it then look at how much memory it uses...
You are unlikely to see such things ported to PS3 tbph, maybe a stripped down version but then comes the next obstacle, you will have to find a dev willing to take on such a big project.
 
You can't, it will hang when in the postal code column
That's what happens when you don't revoke old binaries...

But when you mean"enables back", you mean you see the XMB GUI functions or you are speaking of the entire creation process? Or in other words did you create a PSN account on 4.89?


Seems a false alert :P

I thought it worked when the EULA agreement appeared, my bad

yw71SLn.png
 
Back
Top