PS3 CFW Flash Writer - Unofficial 4.91 update

Developer @aldostools has released an unofficial update for the CFW Flash Writer to support HFW 4.91 on the PS3. This can be a secondary candidate for allowing Custom Firmware installations when bguerville's PS3Toolset (https://www.ps3toolset.com/bgtoolset/) isn't accessible or a self hosting offline option. However, The Ps3toolset is still the preferred and safest method when available for hacking your capable ps3 model so its ready for PS3 Custom Firmware installations.

​

Unofficial 4.91 Update Notice Tutorials

• 
  

  The PS3Xploit Flashwriter 4.91 finally was tested on NOR and NAND. It's now released.
  https://github.com/aldostools/flashwriter/releases

  
  PS3Xploit FlashWriter 4.91 (Unofficial)
  
  URL: aldostools.github.io/flashwriter / 491 or 490
  Offline Site: ZIP / tar.gz
  
  Thanks to @Joonie86, @Evilnat , @littlebalup, @lmn7, @kostirez1 and Team @PS3Xploit.
  
  • Auto-detect PS3 firmware redirects to folder 490 or 491.
  • Ported HTML & javascript from PS3Xplot Flashwriter 4.90 to 4.91 by @aldostools (Thanks @lmn7)
  • Ported offsets for gadgets from PS3Xplot Flashwriter 4.89 to 4.91 by @aldostools (Thanks @lmn7)
  • New custom flash491.P3T created and ported to HFW 4.91 by @Joonie86
  • Thanks to @littlebalup & @Evilnat for NOFSM PATCH & CFW 4.91
  • Thanks to @lmn7 for the offsets & improvements to flash writer 4.89 & 4.91
  • Thanks to @bguerville and @PS3Xploit Team for the PS3Xploit that let this execute
  • Thanks to @littlebalup & @Joonie86 for HFW 4.91
  
  
  NOTE: The official HFW 4.91 by Joonie & Littlebalup is required. mirror
  MD5: C2717C377EB4F0FF458B8819B1E53D50
  PS3HEN is not necessary to be installed. Only HFW 4.90 or 4.91 is enough.
  
  
  DISCLAIMER: This tool haven't been tested in all scenarios. Use it at your own risk. The official BGToolset is more robust and safer.
  
  
  Special thanks to @Joonie86 for flash491.P3T and beta test it on NAND. @SczVideogames for beta test it on NOR.
  
• 
  
  Notice​
  Background: The CFW Flash Writer was originally created by PS3Xploit Team, the project was later replaced by bguerville's PS3 Toolset. Some of the reasoning behind that decision is explained in the quote below from @bguerville ..

  ---

  .
  via bguerville https://www.psx-place.com/threads/ps3xploit-flash-writer-4-90-hfw.39744/page-11#post-386454
  
  The Flash Writer was never deemed dangerous per se otherwise we would never have released it but it's a bad design, my own bad design!! That's why I moved on, even though the code can still be useful for certain things obviously..
  
  The thing is, it's like hen, it's the same core code, nobody understands why it's a dodgy implementation which will unavoidably result in issues you could actually calculate statistics for.
  
  The entire thing relies on using unreserved memory, memory which could be used at any time by the browser for one reason or another. That memory is where the entire exploit code and the patches, payload are stored, so basically all that crucial stuff is at the mercy of fate. It turns out because the system is quite deterministic that it works without glitch because often that memory portion is not used, but Murphy's law, what can happen eventually happens and some folks will get fucked..
  
  Another weakness is that the flashing procedure takes place directly on the browser main thread which means that closing, crashing the browser (maybe even changing tabs or loading a new page closes the process, so if you have multi-stack frames in play and exit the browser accidentally or not, it means half the stuff will never be executed.
  And of course there's the non standard 3Mb patch thingie too..
  That and other issues I won't bother to describe..
  
  These issues would be easy to fix really if you knew what you were doing but few do and none of them bother, I am too busy to go back to this, but I fixed them all in the Toolset already long ago.​
  
  
  
  @NiQ Workaround Guide to access ps3tool set:
  https://www.psx-place.com/threads/bgtoolset-access-workaround-guide.44181/​
  
  
• 
  
  English: 4.91
  
  

  Spanish - 4.91​
  
  

https://github.com/aldostools/flashwriter/releases
https://www.psx-place.com/threads/ps3xploit-flash-writer-4-90-hfw.39744/page-11#post-394422
​

​

 

Nice!

 

All went well for the patching process on CECHL01 NOR flash I hope you eventually update the webMAN MOD flasher too one of these days @aldostools

 

All went well for the patching process on CECHL01 NOR flash I hope you eventually update the webMAN MOD flasher too one of these days @aldostools

The code is available for developers that want to improve the current code.
I stopped due I bricked by mistake one of my consoles during the development. I only have one left and I don't want to brick that one.

kostirez1 started to improve the code in webMAN MOD, then he changed his approach to a HENFlasher application. But both tools ended unfinished. He focused on help with PS3Xploit flashwriter.

 

Thanks for this work, used it for CECH-E model and it worked
To be honest I was afraid of a brick but I feel like this model will die soon so whatever

 

The code is available for developers that want to improve the current code.
I stopped due I bricked by mistake one of my consoles during the development. I only have one left and I don't want to brick that one.

kostirez1 started to improve the code in webMAN MOD, then he changed his approach to a HENFlasher application. But both tools ended unfinished. He focused on help with PS3Xploit flashwriter.

Do you think it might be possible to test on RPCS3 before risking a real console? Or is the environment too different?

 

Do you think it might be possible to test on RPCS3 before risking a real console? Or is the environment too different?

too different. emulators are never accurate enough. in fact, some things only work in emulators rather than hardware. hardware is usually more restrictive.

 

too different. emulators are never accurate enough. in fact, some things only work in emulators rather than hardware. hardware is usually more restrictive.

Sorry, I wasn't clear enough. What I meant is that maybe it could be used to verify that it doesn't brick the console on installation.

 

Well, I think the problem here is that you wouldn't want to rely on an emulator for something this risky. Since aldo must not own an e3 flasher and according to RIP Felix, most nowadays are fake, it's probably too much of a pita to develop something this dangerous that you can't really test yourself.

 

Well, I think the problem here is that you wouldn't want to rely on an emulator for something this risky. Since aldo must not own an e3 flasher and according to RIP Felix, most nowadays are fake, it's probably too much of a pita to develop something this dangerous that you can't really test yourself.

I never said you can test on just RPCS3 and then released, but I do think that you could (if possible) test it on RPCS3 first and only proceed to test on real PS3 if you didn't break the emulator. Just another safety layer.

 

I never said you can test on just RPCS3 and then released, but I do think that you could (if possible) test it on RPCS3 first and only proceed to test on real PS3 if you didn't break the emulator. Just another safety layer.

Most likely their patching it because they only support *OFW*
Plus I am staying out of their Discord on my second account, because Ani pissed me off
That time out was absolutely uncalled for. back in June

 

I never said you can test on just RPCS3 and then released, but I do think that you could (if possible) test it on RPCS3 first and only proceed to test on real PS3 if you didn't break the emulator. Just another safety layer.

RPCS3 can be a good test tool for development for some things like test XML MODs.
Unfortunately I couldn't get webMAN MOD working. xai_plugin also crashes the emulator.

 

So now I changed my hdd hard drive to ssd as soon as I turn on my PS3, it tells me to plug in a controller, then after to do the update 4.91 or +.
As soon as I do "start" + "select" it tells me "Verification in progress please wait ..." and it lasts, it lasts but nothing!
If anyone has a solution please

 

Just patched a client's 2001 console and the process was flawless.

 

So now I changed my hdd hard drive to ssd as soon as I turn on my PS3, it tells me to plug in a controller, then after to do the update 4.91 or +.
As soon as I do "start" + "select" it tells me "Verification in progress please wait ..." and it lasts, it lasts but nothing!
If anyone has a solution please

It's probably that ssd. The PS3 is picky with them. Check @Berion 's SSD guide.

 

will this work on CECH-3003A model ? i want to do a full Jailbreak because the multiman freezes a lot in HEN

 

will this work on CECH-3003A model ? i want to do a full Jailbreak because the multiman freezes a lot in HEN

No. CFW is not possible on consoles manufactured after April 2011 (some 25xx, all 30xx, all super-slims) due to changes in the bootloader. There are no exceptions. Any attempt to bypass the safeties and force Flash Writer to write CFW to a 30xx's flash will result in a brick.

 

Guess ill stick with HEN... but i whanna ask if i some how backup the NAND flash and i brick the console can i restore the nand backup back ?

It's possible that my PS3 has SSD installed , to be the reason that Multiman freezez 3/1 times i try entering on it ?
SSD is brand new.

Are there any CW that i can try , full CW i mean.

 

Guess ill stick with HEN... but i whanna ask if i some how backup the NAND flash and i brick the console can i restore the nand backup back ?

It's possible that my PS3 has SSD installed , to be the reason that Multiman freezez 3/1 times i try entering on it ?
SSD is brand new.

Are there any CW that i can try , full CW i mean.

yes, I think that's what this thread is for (doesn't work with emmc, only nor on metldr2): https://www.psx-place.com/threads/guide-unbrick-a-ps3-after-an-unfortunate-ps3xploit-flash.21750/

edit: note, that I believe the only legit e3 flashers now come from Germany, and you have to pay a premium price for them afaik.

 

Thanks so much, is there any chance that dumping nor on usb to cause brick ? or idps ?