PS3 PS3 4.83 OFW Now Live - Beware changes impacting HAN users - stay tuned for more info

BEWARE (Exploited PS3's) PlayStation firmware update 4.83 has just went Live, developer's from the PS3Xploit team have not had time to take a look at it yet since this has just been released (see update, devs are looking into it now and will update us here in this thread), This update could potentially be a patch for the PS3Xploit hacks (but they have not in a year which has been odd) or it could be a simple routine update for things such as the BluRay player. Developer's will look into this newly released update and we will keep us posted here in this thread. Its advised to stay on 4.82 until Ps3Xploit developer's verify the newly released Official firmware. Users and Ps3 Firmware Bot has confirmed the update is live.
-STLcardsWS​


Update:
(See "Ps3Xploit Status" TAB below for latest reports on PS3Xploit Status)


ps3-system-software-update-two-column-01-ps3-eu-23mar15.png


  • WARNING 4.83 PS3 Firmware is NOW LIVE
    PS4_4.83.png

    Official Changelog via Sony:

    New for 4.83
    • This system software update improves system performance.

  • ps3xploit-logo.png
    Current Status for 4.83
    • PS3Xploit (for CFW enabled Console) - Do not update to 4.83 OFW (From 4.82 CFW you can update to a 4.83 CFW when available)
    • PS3Xploit HAN (for non CFW Compatible Consoles) - Do not update to 4.83, or you will lose various abilities of HAN

    .Official Ps3Xploit Response via @bguerville
    .
    RECOMMENDATION FROM PS3XPLOIT TEAM:
    FOR THE MOMENT, DO NOT UPDATE TO 4.83 UNLESS YOU HAVE DECIDED TO GIVE UP USING HAN PERMANENTLY ON THE CONSOLE.

    After a look at the update files & preliminary tests, I am afraid I am bearing some bad news for HAN users playing online.

    1. It would appear that s@ny patched one of the 2 webkit exploits we currently use to trigger ROP chains.
    It means that we need to replace this exploit in order to get any ps3xploit tool working on 4.83. Work is already under way, obviously no ETA at this stage. Please don't ask.

    2.
    The kernel is completely untouched. No changes to either lv1 or lv2 which means CFWs will be easier to make. That's also good news for devs with any promising kernel vulnerability under investigation.

    3. Changes were made to vsh as usual & they seem extensive enough to suspect that they may have patched the HAN vulnerability as well. We have not yet had time to look into the matter at all but if they did, HAN might be gone for good past 4.82, leaving only CFW2OFW conversions installable & runnable on 4.83 whenever the patched webkit exploit gets replaced.


    In conclusion, the changes brought by the 4.83 update mean that anyone updating will lose usage of HAN, and possibly permanently until a kernel exploit comes out. Cfw2ofw conversions will be the only installed games that will still be working after updating.


    The nature of this update is upsetting our 4.0 release plans somewhat. It's still very early stages in our investigations & there are still many unanswered questions for the moment. I will keep you all posted whenever I have additional information to share.

  • PS3_4.83_CFW.jpg
    As 4.83 releases (CFW / Homebrew / Tools) are made , we will keep this linked thread below updated:

Do not update to 4.83 or you could lose the ability to exploit your PS3

Source: playstation.com / twitter.com/PS3FWBot
(Thanks to montcer for the Alert in the forum :) )​
 
Last edited by a moderator:
Soooo... (sorry I'm not a pro). I can buy a new HDD and install the 4.81 or lower version vía USB? (when I turn the console on and ask me to install some firmware). Because I know how to do that. Re-install Xploit/Han (on the new HDD) and get over that problem. Again...sorry
A new HDD won't help you. If you updated your console to 4.83, there is no way back, you will remain on 4.83 no matter what you try.
 
I tried to build a 4.83 DB but something went wrong and one of mine ps3s is in 4.83 now.No problem,is a 2101.
I dont remember the exact settings for MFWbuilder.
Anyone could share the data? Ill build it and test it.
please, thanks.
 
Last edited:
Hello, a question, will the Flash Dumper with ferrox charge for 4.83?, I'm worried, I do not want to send my ps3 free, since they would have to downgrade it with e3 flasher, and that's hard to get in my country, sorry for English, I am using a translator​
 
No, there is not a "real" browser, rather a series of sprx that render web pages for different tasks using webkit and silk.

Replacing the whole "browser" basically requires replacing many sprx. There is no way to do this on 4.83 OFW as of yet.

Technically, from testing, only the silk_webkit.sprx would need replaced, but again...no way to replace it on newest firmware yet.
 
No, there is not a "real" browser, rather a series of sprx that render web pages for different tasks using webkit and silk.

Replacing the whole "browser" basically requires replacing many sprx. There is no way to do this on 4.83 OFW as of yet.

Technically, from testing, only the silk_webkit.sprx would need replaced, but again...no way to replace it on newest firmware yet.
This means that there will be no way to exploit the PS3 to hack it? that is to say the Dump FLASH (NOR AND NAND) :nonchalance:
 
No, there is not a "real" browser, rather a series of sprx that render web pages for different tasks using webkit and silk.

Replacing the whole "browser" basically requires replacing many sprx. There is no way to do this on 4.83 OFW as of yet.

Technically, from testing, only the silk_webkit.sprx would need replaced, but again...no way to replace it on newest firmware yet.
There is still hope. Backup injection should still work. This means that we can access dev_flash2
To do that we need IDPS, this means that either they already have it or they can bruteforce with @habib tool(and we now know what one extra byte represents)
We can extract xRegistry.sys, enable browser debug mode and reinjecting the backup.
We then use the Silk engine. Most likely they only patched webkit and rather ignored silk, with some tweaking we might get it to work, silk does support js but it reports different useragent and version.
Furthermore backup injection allows us to write to dev_flash2, and we can use this later on. Plus, the browser can load sprx as a plugin. This can also come in handy.
 
hola, yo la actualice a 4.83, la tenencia pirateada, quería saber ... si abra un nuevo método para flashearla por web con xploit

Hello, I update it to 4.83, tapeworm pirated, I wanted to saber...si will come back the method to flash by web with Xploit
 
hola, yo la actualice a 4.83, la tenencia pirateada, quería saber ... si abra un nuevo método para flashearla por web con xploit

Hello, I update it to 4.83, tapeworm pirated, I wanted to saber...si will come back the method to flash by web with Xploit
Eso mismo me paso a mi,la actualice pensando que todavia estaria el Xploit normal,y ahora me toca esperar,nos toca esperar,que triste.

That happened to me, update it thinking that the Xploit would still be normal, and now I have to wait, we have to wait, how sad
 
hola, yo la actualice a 4.83, la tenencia pirateada, quería saber ... si abra un nuevo método para flashearla por web con xploit

Hello, I update it to 4.83, tapeworm pirated, I wanted to saber...si will come back the method to flash by web with Xploit

Sorry if it sounds rude, we just have to leave the devs, be patient
 
There is still hope. Backup injection should still work. This means that we can access dev_flash2
To do that we need IDPS, this means that either they already have it or they can bruteforce with @habib tool(and we now know what one extra byte represents)
We can extract xRegistry.sys, enable browser debug mode and reinjecting the backup.
We then use the Silk engine. Most likely they only patched webkit and rather ignored silk, with some tweaking we might get it to work, silk does support js but it reports different useragent and version.
Furthermore backup injection allows us to write to dev_flash2, and we can use this later on. Plus, the browser can load sprx as a plugin. This can also come in handy.

You don't need your IDPS to inject xRegistry.sys IIRC, you can just create a backup with xReg in the unprotected archives and it should work.

This is a good idea, but I don't think Silk supports JS enough to run the exploit. Correct me if I'm wrong.
 

Featured content

Trending content

Back
Top