PS3 [UPDATE 4] PS3 Toolset by bguerville: A powerful collection of tools fueled by new PS3 exploit

UPDATE FEB 2023 (The domain's of ** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com and .com are no longer in poccession of the team, A new address will be posted in future release coverage.
Update (4) Now supporting 4.86 Fully & Issue fixed with NAND console's in rare situations

---

.You may recall a recent article revealing a few exclusive screenshots of bguerville's latest project, now the time has come to introduce the next evolution in PS3 Jailbreaking solutions. The PlayStation 3 Toolset by @bguerville is a new suite of tools, built upon a new PS3 exploitation framework & fueled by a new exploit discovered on the PS3 by the developer. The new exploit (and the toolset project as a whole) is compatible with all PS3 models running 4.82 - 4.86 OFW/HFW/CFW

While ps3xploit team member's @habib continued research and development of PS3HEN for nonCFW models with assistance from @esc0rtd3w, @bguerville meanwhile was working on his own research and developing other tools and exploits as you will see with this new PlayStation 3 Toolset, which thorough testing was conducted by @esc0rtd3w (whom we recently interviewed). All the team of talented devs have done some amazing work in the scene in recent years with all the PS3Xploit projects and that trend continues with this release.

The PS3 toolset is a project that @bguerville has been working on for some time,
the developer gave us a brief timeline of events since the Ps3Xploit Tools 2.0 framework (flash writer and dumper(s)) that led to this new release (see the timeline section).

Some tools in this project may offer limited features on non-CFW compatible consoles. For instance, the Flash Memory Manager includes the most functionality for CFW-compatible consoles, certain of its features are available on non-CFW models, others aren't. Features such as the dumping of flash memory (for backup purposes) and displaying of various console specific information in real-time such as the IDPS, Factory Installed Firmware version and automatic detection of your console's Custom Firmware (cfw) compatibility status are available on both CFW compatibles & non CFW compatibles console's.

Note that the PS3 Toolset does not feature PS3HEN, bguerville declared having his own plans for a HEN style solution.

The validation and safety checks have advanced greatly in this latest framework of bguerville's tools (since the release of the flashing tools in PS3Xploit v1.0 and v2.0), the toolset detects your console type and only allows the features that are compatible with your console to be used on your system, making it noob proof while also being very user friendly thanks to new automation and detection built in.

Let us now discover this release and how to use various functions of the toolset.

About Requirements & Features Userland Tools Included Toolset Functionality Donations & Acknowledgements

• 
  
  PS3 Toolset by bguerville
  ​
  
  
  "The PS3 Toolset is a repository project for tools built upon a new ps3 exploitation framework I have been working on for a while. More tools should be added to this repository with time.
  I hope you enjoy using them as much as I enjoy making them ;-)"​
  - @bguerville​
  
  Project Timeline:
  
  • End 2018, Sony patches one of the bugs the ps3xploit tools exploited to gain ROP execution. (4.83 OFW release)
    
  • Beginning 2019, I begin to look for a replacement exploit & the release of ps3xploit tools 3.0 is postponed.
  • Spring 2019, I rewrite most of the 3.0 framework to leverage the new capabilities gained with the new exploits.
  • Summer 2019, realizing the potential of the newly written 4.0 framework to create flexible & powerful tools, I decide to cancel the 3.0 release altogether & scrap the 3.0 framework.
  • Beginning 2020, I am releasing this "Toolset" project, as a repository for the tools created around my 4.0 framework that I deem release worthy, each tool being accessible in a toolset tab. This project is the fruit of many sleepless hours during many months, it showcases only part of the 4.0 framework capabilities though, there is still room for more surprises later... ;-)
  
  The initial release, contains a couple userland tools, a fully featured Flash Memory Manager & a Memory Editor (mostly for development & research purposes). A file explorer tool should be added to the repository soon, it will be the last userland tool I write for the foreseeable future
  ​
  General Information about the PS3 Toolset
  
  • Toolset supports all ps3 models & official firmware versions from 4.82 to 4.86 (cex & dex) *some ps3 models have exclusive features/tools (note: toolset tools will also work from CFW)
    
  • PS3 Toolset is executed from the PS3's Web-Browser by visiting the following URL (SSL): ** www.** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com)/bgtoolset
    
  • PS3 Browser Requirements
    • JavaScript (Enabled from browser settings)
    • Cookies (Enabled from browser settings)
    • Flash Plugin (Enabled, but this one has a few caveats that may need explaining, the good news being that the toolset will detect the issue and let you know how to proceed (if there is an issue), see further explanations below)
      • If ever in the past, you agreed to load the Flash Player plugin when prompted and checked the checkbox "Do not show again", you should have no issue & will never even see the plugin popup.
        
      • If you never before checked the "Do not show again" checkbox, you will be greeted with a popup asking you to allow the Flash player plugin. If you agree to load the plugin, the PS3 toolset should continue to load. Note that if you take more than 15s to agree when prompted by the popup, you will get a PS3 Toolset warning about the plugin being disabled even if you finally agreed to load the plugin, just refresh the page when prompted.
        
      • If ever you got the Flash Player plugin popup in the past & selected NO and checked the checkbox "Do not show again", the Flash Player plugin will be permanently disabled, consequently the PS3 Toolset will not be able to load. Unfortunately there seems to be no official way to reset this setting in the browser. The PS3 toolset does have automatic detection of this issue and some instructions are given. Currently the easiest workaround is to create a new user profile on the XMB, when launching the toolset on the new profile, you will be greeted with the browser pop-up asking to allow the flash plugin. However it has been found that in some cases, a new user profile is not sufficient to reset the Flash Player plugin status. I hope that other devs & advanced users will look into this situation while I continue working on new tools, if nobody does, I might end up looking into the problem after the next tool release.
  • You are free to use the tools in this project at your own risk. Keep in mind that no official support is provided, if you experience any kind of problem & find yourself in need of help, I strongly recommend that you turn to the PS3Xploit sub-forum on psx-place.com for support & guidance..
    
  • It is highly recommended that you adjust the console's System Time settings properly to avoid any time related issues with the browser and/or the Flash Player plugin.
  • To avoid potential crashes, you should never attempt to close the browser while toolset operations are in progress, especially when the browser exit confirmation setting is turned off.
    
  • PS3 Toolset only loads tools & features compatible for your console, this means no accidental use of a feature not compatible with your system.
    
  • No local/offline version is planned & the source code will remain closed for the time being.
• 
  Requirements
  
  • PS3 Console (Any Model) running 4.82 - 4.86 (CEX/DEX) Firmware
    
  • Internet Connection to access Toolset from PS3's Internet Browser.
    
  • PS3 Browser Flash Player 9 Plugin enabled (View General Information section for additional info)
    
  • PS3 Browser Javascript enabled
    
  • PS3 Browser Cookies enabled
  
  Quick Overview of Toolset (v1.0.19) Capabilities:
  All Models
  
  • Display console's IDPS
  • Detects Console's CFW Compatibility + Factory Installed Firmware
  • Detects Internal Flash Type of console: NOR / NAND / eMMc ect...
  • Detects console & firmware information
  • Take's a Full dump (backup purposes) of Internal Flash
  • Memory Editor tool (R&D tool)
  Custom Firmware (CFW) compatible Models Only
  
  • Patching of OFW Flash (Flash Memory Patch) for Custom Firmware Installations.
  
  
• 
  Included Userland Tools (v1.x)
  1. The Memory Editor tool v1.1
  
  
  
  
  • The tool maps up all the currently loaded sprx modules segments (text & data) & allows you to browse them as well as the 2 vsh segments and the browser memory container. Users can also edit the memory as they see fit in all writable memory segments. This is mostly a R&D tool.
  • - Notice - issues caused by RAM synchronisation. The memory editor is not a live debugger, it cannot pause lv2 or userland threads execution. Consequently, the RAM can be modified by the various threads executing in userland between the moment the memory editor tool takes a snapshot of a ram range to create the hex table to display on screen & the moment the table is actually displayed on screen.This means that on rare occasions the values displayed on screen might be different from those actually in RAM. This is especially true for specific memory areas such as the browser container memory.
    • There is no easy way to solve this issue, even the debugging deci3 syscalls available only in DEX would not help us much because while it would enable us to take properly synchronised snapshots of the RAM, displaying the data on screen would still require running js code in the browser, which would modify the RAM & lead to the same synchronisation problem we currently face without using the deci3 syscalls.
    • I implemented code to color out the detected table cells found to be unsynced with RAM so there is as little ambiguity as possible. The text of such detected table cells is set to 'undefined'.
  
  2. Flash Memory Manager v1.2 tool
  
  
  
  
  • Compatible with all PS3 models (patching flash options exclusive to CFW compatible models)
    
  • FMM displays basic Flash Memory data in a tree.
  • Clicking on appropriate tree nodes reveals context menu entries to launch the tool's features.
  • Among other things, the manager can dump the Flash memory to file on any natively writable partition mounted on the console.
  • To patch (for cfw installation) a console using the no-fsm method, users must first load a patch file in memory. That file will be checked first & if found valid, the context menu entry to apply the patch will be enabled.
  There are 2 ways to acquire the correct patch file to flash.
  

  1. it can be downloaded to disk first then loaded into memory from file & finally applied to the system
  

  - or -​

  2. it can be loaded via https directly to memory without using disk storage, the data is checked in RAM then if found valid, users can decide to apply it (from the unlocked menu, once file is validated by the toolset automatically).​

  • After applying a patch, the FMM automatically dumps the 2 ROS regions it just overwrote to double check that patching was properly done.
  • Progress dialogs keep the user informed of current operations & outcomes. User logs are provided in the various progress dialogs.
  
  3. Logs v1.0 Tool
  
  
  
  Technically the log section is also a tool of this Toolset. Its tab contains all the logs, warnings, errors & debug output of the toolset & its different tools.
  
  • Whenever something goes wrong, it's the first place to look & screenshots can be used to identify problems.
  • I also included a UDP broadcast similar to Cobra's. Users can use socat to listen on UDP to the Toolset broadcast. However for the moment, only some data gets broadcasted but not the entire contents of the log tab because of the performance impact. With the file explorer release, I plan implement a few changes to this feature as well, the UDP broadcast will be done in a separate thread & all logged data should be broadcasted to UDP.
• 
  
  
  Legend:
  
  • Displays firmware information
    • PS3 Firmware: (version)
    • VSH Mode: (Retail (CEX) or Debug (DEX))
    • Kernel Mode: (Retail (CEX) or Debug (DEX))
    • Custom Syscalls:
      • 1. detects 'Mamba' (if syscall 1022 exists)
      • 2. detects 'Cobra' (if 1022 does not exist but syscall 8 works)
      • 3. detects CFW (if 1022 & 8 are unavailable but syscall 6 works)
      • 4. Displays 'No' (if neither sc 1022, 8 & 6 are unavailable)
  • Flash Memory
    • the tree contains alot of information about any PS3 console and also provide option for taking a backup (dump) of internal flash
  • Quickly determines if your console is a NOR/NAND/eMMc type
    • Displaying of console info, also note previous tools user's had to select NOR/ NAND/ eMMc Tools (depending on model), now the toolset automatically checks and detects tools needed.
  • Displays your IDPS (option to hide onscreen)
    • Will display any Ps3 models IDPS
  • Displays Factory Installed Firmware
    • If your console < 3.60 that means you can install CFW
  • Displays Custom Firmware Installation Compatibility,
    • No longer have to check the sticker of your console and run minverpup and check min factory installed firmware, the toolset displays the compatibility of a Custom Firmware (CFW) Installation for your console.
  • ROS Bank 0/1
    • Display's hash checks of ROS 0 /1 (technically the hashes are not calculated from the entire ros ranges but from the range corresponding to a noFSM patch so that ROS hashes & patch file hashes can be compared.
  • Flash Memory Patch (CFW Compatible Console Only)
    • Patch Flash for CFW installations

  ---

  .Flash Dumper:
  - Notice - dumps should always be validated with PyPS3Checker to ensure a proper dump took place before using it for future backup purposes)
  
  Purpose of dumping the Flash?
  
  • Having a Clean backup of your system internal flash memory is a vital piece of information to have stored, its something that may never be used but can be extremely important in some instances where a brick occurs, having a clean backup can help restore your system along with a hardware flasher
  
  
  Patch Flash (aka Flash Writer Tool) - CFW compatible console's only
  Purpose of patching flash?
  
  • Patching the Flash (ROS 0/1) allows for Custom Firmware Installations on applicable models
  Userland Memory Editor
  Purpose of using Userland Memory Editor?
  
  • The memory editor is a R&D tool. It's useful mostly for devs & hackers who can use it to peek/poke the RAM, either to verify certain results or to search for flaws.
  Toolset detecting various PS3 models
  
  Toolset Themes Options
  The toolset contains 4 Themes as shown below
  
• 
  
  Acknowledgements
  My warmest thanks to Jason, for his friendship & support of course, but in the context of this project, also for testing my work on a daily basis, not just before this release but all year round.
  
  
  The PS3 Toolset & its GUI were built in native js upon various open source js libraries including jQuery, jQueryUI, bigInteger, jstree, mCustomScrollbar, js-cookie, sjcl, switchButton & toastmessage as well as the Fork Awesome CSS icon library .
  Thanks to all the coders involved in the various projects.
  
  
  Thanks to all the psdevwiki contributors, scene hackers & developers who have brought us to this point.
  ​
  - @bguerville

  ---

  .​
  Help and Donations
  You can show your appreciation for my (@bguerville) work & help fund future projects with a donation in BTC at either of the addresses below​
  ​
  Thank you for your support.
  
  

  ** www.** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com)/bgtoolset/assets/images/qr-legacy-P2PKH.png​	** www.** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com)/bgtoolset/assets/images/qr-native-segwit-BECH32.png​	** www.** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com)/bgtoolset/assets/images/qr-PayNyms.png​
  Legacy P2PKH​	Segwit BECH32​	PayNyms​

  ​
  ​
  
  The PS3Xploit team also needs your continued help to cover its growing web hosting costs.
  Please consider a donation to PS3Xploit via Paypal at https://www.paypal.me/ps3xploit​

From the PS3 web browser you can access the toolset @: (SSL only)
** www.** ** www.ps3xploit.net > D... (NEW URL = http://ps3toolset.com)/bgtoolset​

Spoiler: Previous Updates

UPDATE (2) - Regarding 4.86 Support via @bguerville ​

PS3 Toolset is fully supporting 4.86

UPDATE (3) -A limited number of user's have been complaining of errors, the information often provided by user's is incomplete, which means tracking the issue is not easy based on the information provided, Developer bguerville is asking those user's who are experiencing issue to provide a dump of the flash to diagnose a possible issue and fix for the problem, here is a thread by fellow developer @esc0rtd3w setup here to acquire those dumps from affected user's:​

https://www.psx-place.com/threads/bg-toolset-user-issues-and-dump-submissions.28868/ ​

Update (4) - Issues has been resolved and FMM has been updated to
v1.0.22. A fix for the handful of ppl with NAND consoles who are stuck unable to install another firmware at
** www.** ** www.ps3xploit.net > D...http://ps3toolset.com)/bgtoolset/fix_nand.php

Instructions here for NAND ISSUE:
https://www.psx-place.com/threads/bg-toolset-user-issues-and-dump-submissions.28868/​

 

Could you please provide a short vid of your screen while opening browser and loading page? Also set toolset url to home page

Will do. Im rebuilding the database right now. This is taking a bit of time.
I can see in the first post, it is possible, that the flash popup will not Pop up, even if a new user is created. Maybe thats the problem? hm...
Edit: Now it works! Flash popup doesnt came Up (again), but works now. Rebuilding database was the right thing to do. Thank you!

 

Now i understood it better, so the rule is... to dont mess around with the cookies and the cache in between toolset sessions

If someone wants to clear them (for paranoid reasons) it needs to be made before using the toolset for first time, or after using the toolset for last time, but never in between

You got it exactly right..
Except that this rule applies to cookies only!
Cache is different, you can clear it whenever you wish, it makes no difference because all important stored data is in cookies (I really wish there was an alternative to cookies to be honest but no other storage means in ps3 browser). Having said that, keeping the cache clearly speeds up the Toolset loading process as it saves a few hundred kb of file download.
If you clear the cache, the next Toolset load will take longer.

Also in case of slow or unreliable connections, even a busy server, it is possible to get a Toolset loading failure with the Flash Player 9 must be enabled message. It can happen after clearing the cache & may be caused by a simple file request timing out. If this happens, a simple page refresh (no clearing anything) should solve it.

The PS3 Toolset is a large project using many js libraries. Its total size is over 800kb. The minified jquery, jqueryui, css & jstree library files alone are over 500kb!
You can understand why the cache speeds up the loading process..


Another thing that I really need to stress out.
The importance of always using a browser exploit in a clean browser, either as homepage or as favourite using a blank homepage.

Let me explain the reasons behind this reasoning.
During an exploitation process, we must look for data in RAM & we cannot afford to scan the entire RAM because that would take 10mn or more for each signature we look for... So we must use statistics & probabilities, helped by the particularities of the system ie make educated guesses.
So for instance, we know that when we open the webkit browser, the browser memory container is in the range 0x80000000 to 0x90000000, we also know that the webkit stack starts at 0x8FD00000. We know roughly where the js & as objects get located, for example webkit js strings data get stored between 0x80160000 & 0x81000000 & a lot of other things like objects, backing objects, vtables.
So certain parts of an exploit must rely on those best guesses & when an exploit is reliable those best guesses turn out to hold 100% true, when the exploit is always run in the same conditions.
However if you begin charging the condition in which the exploit runs, the best guesses reliability may or may not be reduced... They could stay 100% true, become 80% or even 0% in extreme situations.

Of course, a good exploit should be able to work around these different issues but it's not always easy & the ps3xploits are a specific kind of exploits, that are not just trying to get control of a system at all cost, whether it takes 7s or 7 days to do it, here the exploits must work instantly, with as little latency as possible because a user is watching the screen expecting results right away.
So while new measures have been put in place in the Toolset to keep the user informed whenever long memory scanning features are being needed, overall the ps3xploits in general are designed to run optimally in a perfectly clean browser, the exploit page being the first page the browser should open.

So if, instead, you open the browser, already on another homepage, then browse the Internet, follow links & along the way, load xhtml, html, xml, images, svg, css, flash movies along with tons of javascript being run, you can easily imagine that by the time you run the exploit, there has already been so much memory usage that the same webkit js strings created as we talked earlier are no longer found in range 0x80160000 & 0x81000000 but much higher, all objects will be found in different memory ranges, some lower some higher, everything changes, the best guesses become all wrong & the exploit reliability collapses because of it.

All this was especially true for exploits used in v2/v3 tools including HEN.

The Toolset currently uses exploits that are much more advanced & a lot more resilient than those used in v2/v3/HEN, those new exploits are only temporary & I have much better ones to use in the future that no longer require clean browser session for reliability.

Yet, even if not perfect, with the exploits used currently, you can refresh the Toolset 10 times & it will reload 10 times, you can browse other sites first & still the Toolset will load ok..
BUT the rules that applied to the previous ps3xploit exploits still apply to the current Toolset exploits to a degree, even if Toolset loading problems are rare overall, it could happen.

So to ensure 100% reliability, I still recommend to Toolset users to use a blank page as PS3 browser homepage & set the Toolset as a favourite that they can open directly after opening the browser when needed.

 

Will do. Im rebuilding the database right now. This is taking a bit of time.
I can see in the first post, it is possible, that the flash popup will not Pop up, even if a new user is created. Maybe thats the problem? hm...
Edit: Now it works! Flash popup doesnt came Up (again), but works now. Rebuilding database was the right thing to do. Thank you!

You must have had flash enabled always. If you check your setting.xml under webrowser home path, when on cfw, it should reflect a 1 for auto.

It's good that restoring db got you going again.

 

Thanks for the explaination @bguerville it made me think in an idea, but probably you thought in it before

As you said, in the correct PS3 setup there are some memory areas that should be empty (because the user was not loading any other web before starting the toolset)
I mean... im thinking in memory as a water tank, under that circunstances the tank should be almost empty, right ?

The idea is to scan the empty areas to verify that doesnt contains anything... and based on that check you can display a info message with several posible results before scanning the real data:
-The exploit have a probability of 100% success in your current PS3 setup
-The exploit have a probability of 80% success in your current PS3 setup
-The exploit have a probability of 40% success in your current PS3 setup

----------------
This % numbers are rought approximations, doesnt really represents the success ratio accuratelly (or instead of that you can use only 3 posible results "low", "medium", "high" to simplify it)
Is not intended to prevent users continuing with further steps, but mostly as something handy to know

 

It is possible to raw dump eMMC to dev_usb000 by some "magic user tool" in toolset?

 

It is possible to raw dump eMMC to dev_usb000 by some "magic user tool" in toolset?

You can dump emmc like all the other ones using Flash Memory Manager.

 

But isn't whole eMMC is 16GiB and CellOS doesn't support anything else on USB than FAT32? I don't have CECH-4xxx so it is only question to cure my curiosity.

 

But isn't whole eMMC is 16GiB and CellOS doesn't support anything else on USB than FAT32? I don't have CECH-4xxx so it is only question to cure my curiosity.

As far i know the contents of the eMMC chip are pretty much the same than if you take the contents of the NAND chips of the first PS3 models and you add a couple more regions (not sure how many) for dev_hdd0 and dev_hdd1
I dont know the details, but my guess is the full eMMC dumps are going to have a VHDD region inside flash, in the same way some PS3 models have a VFLASH region inside hdd, in other words:
-The PS3 models with NOR flash chip have a VFLASH region (virtual flash partition) inside the real hdd
-The PS3 models with eMMC flash chip have a VHDD region (virtual hdd partition) inside the real flash chip

Is the same stuff... is just it works in the other way around

If you access them with the standard syscalls everything works pretty much in the same way... this "tricks" of virtualization are made by the hypervisor at lv0
Im mentioning this because i guess you are curious about dev_hdd0, i guess things like making a copy of some sectors to take a look at the partition tables of VHDD and dev_hdd0 regions should work fine

 

To bad that we don't know how to get ERK on new models, but from with HEN, from GameOS we still have access to decrypted partitions (I don't know if LV0 will not defend raw access to the eMMC/HDD) but I'm not sure if this could lead to anything if it is closed in "VHDD partition". Funny that I got the same idea as You.

 

But isn't whole eMMC is 16GiB and CellOS doesn't support anything else on USB than FAT32? I don't have CECH-4xxx so it is only question to cure my curiosity.

ahh yes, i misunderstood you

We actually did talk about this a while ago, but never pursued it further. You have me curious again now though lol

 

Hello,
First of all I want to say big thank you to bguerville and everyone involved for incredible work! I wish to be smart as you!
Now, I hope my post will help.
Like many I have/had a problem with bgtoolset page freeze. Tried everything and the only way i made it works was to reset ps3 to factory settings, create new user, clear cookies(everything as the instructions) then access to tools website trough google link. Page didn't open normally when I typed address. When tools load you have to stay on the page, if you leave you won't load again. Also what happened I had to prepare usb with cfw and when I finished I plugged usb drive to ps3 and tried to flash memory patch but seems like page wasn't responding. I only refresh toolset, not a page and I can confirm I patched memory to usb and loaded from there.
After I applied cfw successfully.

I hope that help.
Sorry for my English

 

Hello,
First of all I want to say big thank you to bguerville and everyone involved for incredible work! I wish to be smart as you!
Now, I hope my post will help.
Like many I have/had a problem with bgtoolset page freeze. Tried everything and the only way i made it works was to reset ps3 to factory settings, create new user, clear cookies(everything as the instructions) then access to tools website trough google link. Page didn't open normally when I typed address. When tools load you have to stay on the page, if you leave you won't load again. Also what happened I had to prepare usb with cfw and when I finished I plugged usb drive to ps3 and tried to flash memory patch but seems like page wasn't responding. I only refresh toolset, not a page and I can confirm I patched memory to usb and loaded from there.
After I applied cfw successfully.

I hope that help.
Sorry for my English

Your post is quite confusing. I don't understand why you are clearing cookies, and also do not understand how it's freezing.

It freezes when? On a fresh browser load? You type address exactly and what don't work?

Your post makes no sense and isn't very helpful to be honest. We would love to fix this "freezing" issue but we cannot seem to actually have someone tell us how to reproduce it.

I think it's user error, and most are just unaware of what to check or do, despite instructions.

 

Hello,
First of all I want to say big thank you to bguerville and everyone involved for incredible work! I wish to be smart as you!
Now, I hope my post will help.
Like many I have/had a problem with bgtoolset page freeze. Tried everything and the only way i made it works was to reset ps3 to factory settings, create new user, clear cookies(everything as the instructions) then access to tools website trough google link. Page didn't open normally when I typed address. When tools load you have to stay on the page, if you leave you won't load again. Also what happened I had to prepare usb with cfw and when I finished I plugged usb drive to ps3 and tried to flash memory patch but seems like page wasn't responding. I only refresh toolset, not a page and I can confirm I patched memory to usb and loaded from there.
After I applied cfw successfully.

I hope that help.
Sorry for my English

Like I explained before, that freeze issue is caused by certain user profile settings & we only partly understand which ones for the moment. @esc0rtd3w just rightly said that nobody having reported this freeze error has ever provided any data to help identifying the culprit setting.

The workaround is to create another user profile & possibly rebuild the database in some cases (TBC). You can always delete the new user profile once you are done with using the Toolset.

Regarding your failing attempts to load the Toolset I think you should refer to my earlier post explaining the most reliable ways to use a Web browser exploit because the steps you are currently using easily explain the problems you have had.
Read https://www.psx-place.com/index.php?posts/239971

1. Browsing other Web pages before using the Toolset or any earlier ps3xploit release for that matter is ALWAYS a bad idea. That includes having a homepage that loads automatically before using the Toolset.

2. Whatever error you may have had when typing the URL was a user error, maybe a typo or the omission of the www. part of the URL.
Think about it, the same URL cannot error out when typed in but load the page when launched from a Google link.
Always use the full URL below & don't omit a single character:
** www.** ** www.ps3xploit.net > D... (NEW URL = http://ps3toolset.com)/bgtoolset

In any case, my recommendation to you is to leave cache & cookies alone, set the browser homepage setting to blank page & create a favourite entry for the Toolset. When you wish to use the Toolset, you start a fresh browser session (which will open on a blank page) then open the favourites menu & launch the Toolset from there, you will find that loading will succeed every single time, at least as long as your Internet connection is good.

Refreshing the Toolset page should always work fine as well, it never fails at my end, but you should avoid browsing to other pages then coming back to the Toolset.

 

Apologies for confusing post. It wasn't my intention.
I cleared cookies and cache before starting with clean/fresh browser.
In my case I carefully followed all your step by step directions and trust me, I tried many times and toolset didn't loaded. In top right corner all I seen was "Please wait".After long time waiting I had to reboot console every time because it was not responding.
I installed cfw in the past on PSP and Vita.
Anyway, I got cfw on my ps3 now thanks to you guys!
Best wishes and stay safe!

 

Apologies for confusing post. It wasn't my intention.
I cleared cookies and cache before starting with clean/fresh browser.
In my case I carefully followed all your step by step directions and trust me, I tried many times and toolset didn't loaded. In top right corner all I seen was "Please wait".After long time waiting I had to reboot console every time because it was not responding.
I installed cfw in the past on PSP and Vita.
Anyway, I got cfw on my ps3 now thanks to you guys!
Best wishes and stay safe!

no beep? no flash dialog? You are not specifying these things in responses

flash is not loading, if so, which is solved by new user account.

if you made a new user account, then you WILL get the prompt. If not then we need a dump of some files from you or we have no idea what the problem is. That would require running HEN to get these files, but there is no reason i can think of that its not loading

 

You are really awesome guys thanks a lot, finally jailbreak my ps3 nand without the need of hardware flashers and soldering

 

Hello, I am getting error 8002F957 while trying to install cfw, I don't know why my PS3 updated itself to a 3.55 ofw? I still have hombrews and so on... I had 4.86 Rebug LE CFW installed and switched to 4.86 CEX Ferrox but something weird happened and now I am on 3.55 ofw ... when I try to install cfw l get that error. They told me to use bguerville's toolset but l have no clue what to do and l dont want to destroy my console lol. Someone can guide me?

 

Hello, I am getting error 8002F957 while trying to install cfw, I don't know why my PS3 updated itself to a 3.55 ofw? I still have hombrews and so on... I had 4.86 Rebug LE CFW installed and switched to 4.86 CEX Ferrox but something weird happened and now I am on 3.55 ofw ... when I try to install cfw l get that error. They told me to use bguerville's toolset but l have no clue what to do and l dont want to destroy my console lol. Someone can guide me?

Hmmm..
The console didn't install 3.55 ofw on its own. Someone downgraded to the 3.55 firmware manually & purposefully!

Anyway on 3.55 ofw, you should be able to install a 4.xx CFW directly without patches so the error you are getting doesn't make much sense.

Update error - 0x8002F957:
Error with installing Firmware update. The data is corrupted (firmware in flash does not allow the MFW installation as it does not contain the needed patches)

I would first try reinstalling 3.55 OFW first then install Rebug Lite 4.86.

If that does not work, you can always use the PS3 Toolset method to jailbreak.
Install OFW 4.86 then load the PS3 Toolset in a clean browser (homepage set to blank): ** www.** ** www.ps3xploit.net > D... (NEW URL = http://ps3toolset.com)/bgtoolset

Go to the Flash Memory Manager.
Always keep "strict mode" on.
Heed all the warnings, if ever the Flash Memory Manager returns an error message after any of the steps 1 - 3 below, seek guidance immediately, don't proceed to the next step, don't reboot, don't switch off.

To jailbreak using FMM with CFW compatible consoles:
1. Use the "load no-fsm patch file via https" context menu entry.
2. When the patch is loaded, use the "apply patch" context menu entry.
3. When the patching is complete & if successfully validated, you will get a message on screen telling you to reboot. You can safely do so.
4. After reboot, the console is jailbroken, now you can either enter safe mode or XMB to install Rebug Lite 4.86.

 

Hmmm..
The console didn't install 3.55 ofw on its own. Someone downgraded to the 3.55 firmware manually & purposefully!

Anyway on 3.55 ofw, you should be able to install a 4.xx CFW directly without patches so the error you are getting doesn't make much sense.

Update error - 0x8002F957:
Error with installing Firmware update. The data is corrupted (firmware in flash does not allow the MFW installation as it does not contain the needed patches)

I would first try reinstalling 3.55 OFW first then install Rebug Lite 4.86.

If that does not work, you can always use the PS3 Toolset method to jailbreak.
Install OFW 4.86 then load the PS3 Toolset in a clean browser (homepage set to blank): ** www.** ** www.ps3xploit.net > D... (NEW URL = http://ps3toolset.com)/bgtoolset

Go to the Flash Memory Manager.
Always keep "strict mode" on.
Heed all the warnings, if ever the Flash Memory Manager returns an error message after any of the steps 1 - 3 below, seek guidance immediately, don't proceed to the next step, don't reboot, don't switch off.

To jailbreak using FMM with CFW compatible consoles:
1. Use the "load no-fsm patch file via https" context menu entry.
2. When the patch is loaded, use the "apply patch" context menu entry.
3. When the patching is complete & if successfully validated, you will get a message on screen telling you to reboot. You can safely do so.
4. After reboot, the console is jailbroken, now you can either enter safe mode or XMB to install Rebug Lite 4.86.

I am trying it right now, but should l better install 4.85 HFW then follow the steps to make my ps3 jailbreak again?

UPDATE: okey, I choosed the second method and worked flawlessly <3 thanks for the help you are insane

Btw, as I installed 4.86 OFW and then jailbreaked with your method, should l keep this or now install 4.86 Rebug LE?

 

I am trying it right now, but should l better install 4.85 HFW then follow the steps to make my ps3 jailbreak again?

Hfw is basically ofw for HEN usage.
It's totally useless in your case.