• Official PS3 Toolset is now supporting 4.92 Firmware

    View Official Release Post for additional information HERE

PS3 [Update: SSL issue Resolved} BG Toolset SSL Issues (80710A06 Error) (July 2024)

How exactly do you do this? I got my PS3 today and just my luck the site is down lol. My PS3 is currently running a fresh install of HEN+HFW, but I want to put CFW on it. It is compatible.
If your system isn't patched and you're on 4.90 HFW, run the PS3Xploit flash writer, select your flash type (NAND or NOR), and follow the onscreen instructions. Once done, power cycle your PS3 and install CFW the same way you used to do when bgtoolset was up.

I forgot mentioning, you don't need to do AutoHEN if your end goal is CFW. The only reason I mentioned it just in case anyone's end goal happens to be HEN.
 
Last edited:
Yes seems some resellers have it as compatable with ps3 then you get it and find out it ain't. Hope you find some that the resellers let you test some way to be sure it works so you ain't paying for a cert that ends up not working as that would add up quickly.
 
I saw an alternative to host your own server/website incase the ps3 tools website was down, the tutorial came around the time when the actual website was not operational.

I keep encountering the same error when trying to load the CFW through like the proxy server.
FYI I'm on like a hybrid 4.90 I installed from a tutorial and am using a XAAMP Apache module or smth.

I host the page from my PC with all the files (its what I should be seeing on my ps3)
view

I go on the browser and put: "http:// (IPv4 address) : (port number ) " and encounter the same issue as I would visit the ps3 toolkit site

I feel like there could e an error on my part for the proxy part, ut cant figure it out
 
If you turn bgtoolset into a homebrew, how are official firmware users supposed to run it? I mean the purpose of bgtoolset is to run even on OFW

But if your running some sort of hybrid exploit firmware that I loaded through my FAT32 USb, shouldn't it still work
Im just theorizing
 
Hopefully this doesn't sound stupid or rude. Why do we have to rely on you hosting the website? Why can't you release an executable or the code so that we can run the site locally and have the console hit the local server?
 
turning the toolset into a homebrew program would mean installing and running hen to install and run it. But that would cause rewriting pretty much the whole toolset again to turn it into that. Plus not sure how well that would work for flashing the patch. Finding the updated ps3 cert that is future proof as was discussed in the browser problem thread would be less work and alot better then trying that. Better for the cert to be found and installed so it can be accessed by the ps3 again as it's already stable and safe. Just hope it is discovered soon.
 
Following cikocet guide on mitmproxy in the other thread, the SSL error is skipped but results in another 80710028 (CELL_HTTP_ERROR_CANNOT_AUTHENTICATE) error 401 with Acces denied when requesting the file log.php.

Following HWNJ comment in this thread, I would say, the error happens cause ps3toolset.com uses Cloudflare. Cloudflare supports HTTP/3 which is using UDP with default port 443 for the sites they serve. Since we don't redirect UDP port 443 and since mitmproxy would be unable to deal with this traffic anyway it bypasses the interception.

I didn't have the time yet to test, but following mitmproxy docs using-a-custom-server-certificate we should be able to generate a custom cert with openssl and disable http3 which is enabled by default. Then start mitmproxy with options:


mitmproxy --set http3=false --certs *.ps3toolset.com=cert.pem


This should let the ps3 browser fall back to HTTP/2, which mitmproxy should be able to catch.

(Sorry I can't post any links, because this is my first reply)

Error 80710028 could also be related to flash player, since mitmproxy does not send application/x-shockwave-flash header.
 
Last edited:
Why not make public the website files so we can run it locally instead of paying for a certificate?

Hopefully this doesn't sound stupid or rude. Why do we have to rely on you hosting the website? Why can't you release an executable or the code so that we can run the site locally and have the console hit the local server?

Bguersville has already said many, many times, that his project is his and his own, and that he wants to keep it closed sourced until he deems to release it to the public. It's even stated in the official bgtoolset topic: https://www.psx-place.com/threads/u...ion-of-tools-fueled-by-new-ps3-exploit.28658/

Also, we have had a glance on what an incomplete, untested toolset can do to a console, a.k.a. the stolen toolset bricking consoles because hackers didn't know crap about the exploit, the code sequence and how the payload must be delivered.

So please, DO NOT ASK HIM TO RELEASE HIS SOURCE CODE!. Respect his will as he already had done more for the scene than most people here.

If you really, really want to use homebrew on your console, you can always use HEN until the toolset is operational again.
 
That is completely up to bguerville if and when he wants to do that. Its his project and code.
Hi, I gotta ask something. There is a tool allowing to create overclocked firmwares and I want to know. Is it possible to create a hybrid firmware that is also overclocked? I'd like a HFW with 650/750 clocks for my new PS3 fat acquired 2 days ago. Thanks

When I try to create my own CFW or HFW it always end up in error, I think my rig is too old (A10-7800)
 
Hi, I gotta ask something. There is a tool allowing to create overclocked firmwares and I want to know. Is it possible to create a hybrid firmware that is also overclocked? I'd like a HFW with 650/750 clocks for my new PS3 fat acquired 2 days ago. Thanks

When I try to create my own CFW or HFW it always end up in error, I think my rig is too old (A10-7800)
HFW is just using OFW signed files with edit to unsigned tar file. The headers and sprx/self, etc cannot be edited and used on OFW to install over top of OFW.

So basically HFW, for all intents and purposes is just OFW.

CFW/MFW can be modified and installed over CFW or patched OFW (ie bgtoolset nofsm patch)
 
HFW is just using OFW signed files with edit to unsigned tar file. The headers and sprx/self, etc cannot be edited and used on OFW to install over top of OFW.

So basically HFW, for all intents and purposes is just OFW.

CFW/MFW can be modified and installed over CFW or patched OFW (ie bgtoolset nofsm patch)
Apparently LV1 is exploitable however no one tried it I've heard for OFW? it's about the chain of trust 3.60+
Edit: I saw on Discord in the server
 
Back
Top