PS3 Ps3Xploit Tools v2.0 - Improved Flash Writers & Dumpers (Even easier to install CFW on 4.82 OFW )

UPDATE 04-02-2020
These tools have been superseded by the BG Toolset
** 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/










UPDATE (OCT. 11 2018) - With the release of OFW 4.83 portions of PS3Xploit have been patched, The team is looking at workarounds, STAY ON 4.82, DO NOT UPDATE TO 4.83 AT THIS TIME:
IMPORTANT UPDATE (MARCH-2019) v3.0.1 was released providing support for 4.84 HFW (a new hybrid firmware that restores PS3Xploit for 4.84 OFW user's (See Link to HFW)

---

dI will start this off with NO you can not jailbreak your PS3 SuperSlim Console's (seems to be a popular question), however that does not mean the Ps3Xploit Team, (bguerville, esc0rtd3w, habib & W), has not been hard at work, with this new release of Ps3Xploit v2.0.. In this release all the tools (IDPS Dumper, Flash Dumper & Flash Writer) have seen significant improvements and now performing the task such as installing a Custom Firmware on your 4.82 OFW PS3 (with flash writer) has been made even easier and very stable thanks to the team's new checks implemented and progression of the exploit. The Flash and IDPS dumper are also much improved. All the details are provided below please read all the spoiler and tabs before asking any questions.
​

-STLcardsWS​

PS3Xploit 2.0 Tools Now LIVE!!​

Ps3Xploit 2.0 Release >> IMPORTANT DETAILS << FLASH DUMPER TOOL FLASH WRITER IDPS DUMPER

• 
  
  Included Tools​
  • 4.XX IDPS DUMPER
  • 4.XX FLASH DUMPER (USB Edition)
  • 4.XX FLASH DUMPER (HDD Edition)
  • 4.82 NOR/NAND WRITER (USB Edition)
  • 4.82 NOR/NAND WRITER (HDD Edition)
  Ps3Xploit Tools Changelogs​
  v2.0
  
  • Freeze issues - Fixed
  • Occasional bad dumps - Fixed
  • No beeps & shutdown. Replaced by a graceful ROP chain exit & return to browser. This gives the opportunity to the user to dump after patching & validate the dump with littlebalup's py checker. As long as the user does not shutdown/restart, it's still possible to recover from bad patching.
  • Support for usb port 0,1,6 + sd/cf/ms cards.
  • Multi firmware support on all dumpers (4.10+) & DEX support on 4.81.
  • HDD editions for all dumpers & flash writer where a picture file placeholder is used for read/write operations.
  • Javascript refactoring for performance & efficiency.
  • **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) will host the 2.0 update, no need for 3rd party sites.
  
  v1.0 (Thanksgiving 2017 Release)
  
  • Supports Direct OFW to CFW patching for All Phat and 2xxx Slim (minver 3.56 Dec 2010 and lower)
  • the NOR/NAND writer will just copy 3Mb of CoreOS data to both ros0 & ros1 in the flash memory.
  • There is only one version released for 4.82. The same hex patch file can be used on nor & nand.
  • It's as safe as possible, with a check for usb device & patch file making the exploit hang instead of corrupting flash if file is not found.
  • In case of corruption (extremely rare but could always happen), it's only a partial brick because no per console info ever gets erased so a hardware flasher could still be used if ever a recovery reboot was impossible
  
  
• 
  
  
  Frequency Asked Questions​
  
  Will this jailbreak my SuperSlim?
  
  • NO,The Flasher Writer Tool is not Supported on the SuperSlim and a some very late Slim models, Howeever, PS3Xploit has a strong possiablity to eventually evolve into a HEN style exploit (that aspect will take some additional development.)
  
  Which PS3Xploits Tools are Compatible with my PS3 Console?
  
  Spoiler: CLICK TO VIEW COMPATIBILITY

  FAT SLIM SuperSlim

  • 
    
    
    
    Check this sticker on the back of your PS3 to view your PS3 Model.
    ​
    Flash Writer Model Compatibility (PHAT):
    
    • CECH-A01 (NAND)
    • B (NAND)
    • C (NAND)
    • E (NAND)
    • G (NAND)
    • H (NOR)
    • J (NOR)
    • K (NOR)
    • L (NOR)
    • M (NOR)
    • P (NOR)
    • Q (NOR)
    
    
    All DUMPER (FLASH/IDPS) & FLASH WRITER TOOLS are Supported for this model. ​
    
    
  • 
    
    
    Check this sticker on the back of your PS3 to view your PS3 Model.
    
    ***IMPORTANT***
    You must pay very close attention to your PS3 SLIM Models depending on when the PS3 SLIM was manufactured will determine if your console can install CFW (Flasher Writer Compatibility).
    
    For the 25XX series or even if your unsure about any of the models it is reccomnded you run the minverchk PUP >> (DOWNLOAD) & (How to use Minverchk) its a simply utility that show the factory installed firmware on your ps3 and for the CECH-25XX model if the utility shows 3.56 or lower you are compatible but if it shows 3.60 and higher that means your are NOT compatible to use the Flash Writer (CFW enabler for 4.82 CFW)​
    
    
    • Flash Writer Model Compatibility (SLIM):
      • 20XX NOR
      • 21XX NOR
      • 25XX NOR (3.56 minver. and Lower)
    • NOT COMPATIBLE (SLIM):
      • 25XX NOR (3.60 and Higher)
      • 3XXX NOR
    
    
    
    All DUMPER (FLASH/IDPS) TOOLS are Supported for this model. ​
    
    
    
  • 
    
    
    Check this sticker on the back of your PS3 to view your PS3 Model.
    ​
    • FLASH WRITER NOT COMPATIBLE (SUPERSLIM):
      • 4XXXA EMMC
      • 4XXXB NOR
      • 4XXXC NOR
      ​
    All DUMPER (FLASH/IDPS) TOOLS are Supported for this model. ​
    
    
  
  Where can i find official info and details?
  
  • Official Website (Exploit Hosting / Info) @ ** http://www.**ps3xploit.com >Doma...no Longer owned by team** (ps3xploit.me =new)
  • Official Ps3Xploit Forum (Support/News/Info): @ http://www.psx-place.com/forums/PS3Xploit/
  Warning: Known Limitation
  
  • Due to the lack of proper checks after exiting the ROP chain, it is possible in some cases to obtain a success message despite an operation failure. For instance, if you choose a path where no device is plugged in, a dumper page will still display a success message despite the fact the dump save could not work. This limitation has already been addressed, the added operation checks will be part of an update to these PS3Xploit tools which will be released in the coming weeks, that update will be final, no more will come after it
  
  
• 
  
  FLASH Dumper's Help​
  
  
  Spoiler: CLICK HERE >>>>> FLASH DUMPER <<<<< CLICK HERE

  USB EDITION HDD EDITION

  • 
    
    PS3 4.xx NAND/NOR/EMMC FLASH DUMPER v2.0
    ​
    All PS3 models supported
    All 4.10+ CEX CFW/OFW supported
    4.81 DEX CFW/OFW supported
    
    IMPORTANT NOTES:
    
    • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically....
    • So in short, never use the browser or use a homepage you cancel before running the exploit!
    • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
    Steps:
    
    1. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
    2. Open the browser. The exploit page will load automatically. Choose your dump path option.
    3. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
    4. Trigger the exploit by pressing the dump button.
    5. On success, validate your dump with the py checker tool.
  • 
    
    PS3 4.xx NAND/NOR/EMMC FLASH DUMPER - HDD EDITION v2.0​
    
    All PS3 models supported
    All 4.10+ CEX CFW/OFW supported
    4.81 DEX CFW/OFW supported
    
    IMPORTANT NOTES:
    
    • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically....
    • So in short, never use the browser or use a homepage you cancel before running the exploit!
    • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
    Steps:
    
    1. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
    2. Open the browser. The exploit page will load automatically. Download the dump.jpg placeholder file to your PS3 System Storage using the provided link as instructed on screen.
    3. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
    4. Trigger the exploit by pressing the dump button.
    5. On success, retrieve the dump file from the PS3 XMB Photo section, rename it appropriately to dump.hex or whatever & validate your dump with the py checker tool.
  
  
  Usage Tips:
  
  • Try using a LAN connection or a solid WiFi connection during exploitation. A weak signal can cause problems.
  • If the exploit takes more than 5 minutes to work, reload page, browser, or restart console and try again.
  • ]If you are using a LAN connection and experience network issues, make sure all cables to router are in working order.
  
  
• 
  
  
  Spoiler: CLICK HERE >>>> FLASH WRITER <<<< CLICK HERE

  USB EDITION HDD EDITION

  • 
    
    PS3 OFW 4.82 NAND/NOR FLASH WRITER v2.0
    ***** IMPORTANT DETAILS BELOW -- AVOIDING A BRICK *****
    ​
    WARNING: USE ONLY THE PROVIDED flash_482.hex AS IS. DON'T PATCH IT OR MODIFY IT OR YOU WILL BRICK *****
    
    • Verify flash_482.hex file on a flash drive and in the selected USB slot!
      • flash_482.hex MD5: d05be52f8d21700052fbd1fc0174acae
    • DO NOT USE ON CFW (Custom Firmware) (Only Supports OFW)
    • DO NOT USE ON PS3 Models 3xxx/4xxx (aka late Slim or Superslim models), you would brick those consoles.
    • ON SLIM 2xxx Consoles, always use MinVerChck PUP to ensure that the minimum installable firmware version is < 3.60, if ever the minimum version is >3.56, using the flash writer would partially brick your console!
    • USE ONLY ON 4.82 OFW
    
    IMPORTANT NOTES:
    
    • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to ps3 javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded due to previous browsing then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically..
    • So in short, never use the browser or use a homepage you cancel before running the exploit!
    • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
    
    Steps:
    
    For best results with flash writer, here are the recommended steps.
    

    1. Install OFW 4.82 twice on the console you wish to flash to avoid the potential corruption error during CFW installation.
    2. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
    3. Open the browser. The exploit page will load automatically. Choose your path option.
    4. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
    5. Trigger the exploit by pressing the patch button.
    6. On success, load the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) flash dumper, dump the flash memory & validate it with py checker tool. Do NOT restart the console if ever the validation tool gives you errors/warnings on both ros0 & ros1 or you risk to partially brick your console. Report your problem instead.
    7. When you are satisfied with the dump validation, restart your console & install a 4.82 CFW.
  • 
    
    
    PS3 OFW 4.82 NAND/NOR FLASH WRITER - HDD EDITION v2.0
    ***** IMPORTANT DETAILS BELOW -- AVOIDING A BRICK *****
    ​
    WARNING: USE ONLY THE PROVIDED flash_482.jpg AS IS. DON'T PATCH IT OR MODIFY IT OR WILL BRICK *****
    
    • YOU
    • Download flash_482.jpg file to PS3 System Storage!
      • flash_482.jpg MD5: d05be52f8d21700052fbd1fc0174acae
    • DO NOT USE ON CFW (Custom Firmware) (Only Supports OFW)
    • DO NOT USE ON PS3 Models 3xxx/4xxx (aka SuperSlims / Late Slim models), you would brick those consoles.
    • ON SLIM 2xxx Consoles, always use MinVerChck PUP to ensure that the minimum installable firmware version is < 3.60, if ever the minimum version is >3.56, using the flash writer would partially brick your console!
    • USE ONLY ON 4.82 OFW
    
    IMPORTANT NOTES:
    
    • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to ps3 javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded due to previous browsing then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically..
    • So in short, never use the browser or use a homepage you cancel before running the exploit!
    • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
    Steps:
    
    For best results with flash writer, here are the recommended steps.
    

    1. Install OFW 4.82 twice on the console you wish to flash to avoid the potential corruption error during CFW installation.
    2. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
    3. Open the browser. The exploit page will load automatically. Download the patch file flash_482.jpg to your PS3 System Storage using the provided link on screen.
    4. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
    5. Trigger the exploit by pressing the patch button.
    6. On success, load the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) flash dumper, dump the flash memory & validate it with py checker tool. Do NOT restart the console if ever the validation tool gives you errors/warnings on both ros0 & ros1 or you risk to partially brick your console. Report your problem instead.
    7. When you are satisfied with the dump validation, restart your console & install a 4.82 CFW.
  
  Usage Tips:
  
  • Try using a LAN connection or a solid WiFi connection during exploitation. A weak signal can cause problems.
  • If the exploit takes more than 5 minutes to work, reload page, browser, or restart console and try again.
  • ]If you are using a LAN connection and experience network issues, make sure all cables to router are in working order.
• 
  
  PS3 4.xx IDPS DUMPER v2.0​
  
  
  All PS3 models supported
  All 4.10+ CEX CFW/OFW supported
  4.81 DEX CFW/OFW supported​
  
  IMPORTANT NOTES:
  
  • It's essential not to flood the browser memory with junk before running the exploit. The reason for this is that due to javascript core memory usage limitations we are scanning several times a small range of browser memory (a few Mb) to find some essential data in RAM, if the memory is flooded then the range to scan becomes much larger & the probabilities that our data is found in the smaller range decrease dramatically....
  • So in short, never use the browser or use a homepage you cancel before running the exploit!
  • It is recommended to set your homepage temporarily to the exploit page you wish to use to ensure there is no memory flooding messing with the exploit initialization stage.
  Steps:
  
  1. Open the browser & browse to the **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new) website, go to the page of the exploit you need. Set the current page as browser homepage. Don't launch the exploit initialization. Close the browser.
  2. Open the browser. The exploit page will load automatically. Choose your dump path option.
  3. Press the exploit initialization button & wait until initialization succeeds. If it fails, follow the refresh/reload instructions on screen.
  4. Trigger the exploit by pressing the dump button.
  5. On success, check your idps dump with an hex editor.

Source Code & Downloads:
NOR/NAND/EMMC/IDPS 4.xx Dumpers v2.0 Update
NOR/NAND 4.82 Flash Writer v2.0 Update
flash_482.hex (already included in the Flash Writer 2.0 archive) MD5: d05be52f8d21700052fbd1fc0174acae
MinVerChck PUP

IMPORTANT UPDATE (MARCH-2019) v3.0.1 was released providing support for 4.84 HFW (a new hybrid firmware that restores PS3Xploit for 4.84 OFW user's (See Link to HFW)

Exploits now hosted @ **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new)
Official Support Forum: psx-place.com/forums/PS3Xploit/​

 

If, and only if, both ros0 & ros1 are corrupted then you have a problem.

If this happens, what is the right thing to do? One should reapply the patch? (reinstalling OFW might require the console to reboot in safe mode, so I guess that is not advisable)

Why these corruptions occur during flash write? (you can be technical)

One last question, flash memory isn't CRC checked by bootrom or something?

Thank you.

 

If this happens, what is the right thing to do? One should reapply the patch? (reinstalling OFW might require the console to reboot in safe mode, so I guess that is not advisable)

Why these corruptions occur during flash write? (you can be technical)

One last question, flash memory isn't CRC checked by bootrom or something?

Thank you.

If both ros0 & ros1 are corrupted it means user error in play!
Either the hex patch file was wrong or corrupted or the patch was applied on incompatible fw.
In such cases, reapplying ofw by system update is impossible. The flash memory needs patched again with an appropriate hex file to solve the problem. Users should keep their console turned on & seek guidance as to building an hex file if required.

Of course, there is also the case of cfw incompatible consoles. That's different though because even if the patch is well applied, you still have a brick on reboot.
That's why a minVerChk is absolutely necessary before users consider patching a slim 2xxx console.

 

Hi. How is it safe to move from OFW to CFW with this method, and then back to OFW and again to CFW? Could I brick it?

 

Hi. How is it safe to move from OFW to CFW with this method, and then back to OFW and again to CFW? Could I brick it?

If you follow the recommendations & requirements, it's perfectly safe although bothersome & quite frankly pointless if you intend to switch regularly because if you really need ofw that often then you should opt for a DB fw setup. That's beyond the scope of this thread though, create your own if you need info/help with that.

 

There is a rumor that soon could be written in the flash of the super slim, is this true or is it just that people talk without knowing anything. Forgive my ignorance but this is for me the official forum where we should be informed of any news about this. Regards everyone

 

There is a rumor that soon could be written in the flash of the super slim, is this true or is it just that people talk without knowing anything. Forgive my ignorance but this is for me the official forum where we should be informed of any news about this. Regards everyone

No, we 3.55+ users are waiting for Homebrew Enabler, maybe this year.

 

There is a rumor that soon could be written in the flash of the super slim, is this true or is it just that people talk without knowing anything.

It's the latter.
Although technically we can already write to the superslim flash memory, that's not the issue. Writing to the flash memory is not sufficient to enable cfw for post 3.56 consoles.

 

Hi Guys, when I click on the download links that you have provided it take me to the PS3Xploit site however it says account suspended.
Any ideas as I need to download the file or are they hosted somewhere else now?

 

Hi Guys, when I click on the download links that you have provided it take me to the PS3Xploit site however it says account suspended.
Any ideas as I need to download the file or are they hosted somewhere else now?

Site (**ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new)) was down for a bit but is back up. not sure if that was the message that was being displayed when down or not..

 

Is v 2.0 necessary? I jailbroke two other PS3's with 1.0 and thought it was really easy. I don't know what I'm doing at all but I followed the tutorials EXACTLY and wrote my own instructions for myself, and now I'm confused with 2.0 since there are no tutorials. Also 1.0 was pretty easy b/c I didn't need to host the mini web server or whatever it was since i used the one for v1.0 hosted on someone's site (redthetrainer)

 

Is v 2.0 necessary? I jailbroke two other PS3's with 1.0 and thought it was really easy. I don't know what I'm doing at all but I followed the tutorials EXACTLY and wrote my own instructions for myself, and now I'm confused with 2.0 since there are no tutorials. Also 1.0 was pretty easy b/c I didn't need to host the mini web server or whatever it was since i used the one for v1.0 hosted on someone's site (redthetrainer)

Have you been to redthetrainer.com lately, he's changed things, how would the official host site be any different for you it's pretty much the same but a different layout

 

Muchas gracias mi Slim se pudo flashear sin problema,pero un amigo hizo el mismo método con una super slim y ahora ya no prende creo se bloqueó,no se sé si allá alguna forma de reparar o revertir esto sería de mucha ayuda cualquier intento se los agradezco,espero alguien nos ayude gracias.

 

Is v 2.0 necessary? I jailbroke two other PS3's with 1.0 and thought it was really easy. I don't know what I'm doing at all but I followed the tutorials EXACTLY and wrote my own instructions for myself, and now I'm confused with 2.0 since there are no tutorials. Also 1.0 was pretty easy b/c I didn't need to host the mini web server or whatever it was since i used the one for v1.0 hosted on someone's site (redthetrainer)

If it was not necessary, why would we bother spending days/weeks working on an update? On top of providing fixes for a number of issues, v2.0 lowers the brick risks in case of user error as you can now check the patching validity before it is too late. Also keep in mind that help & support for 1.0 ended when 2.0 was released!

And I don't understand what you mean about hosting locally. Although local Web servers are usually a better setup, v2.0 is also hosted officially on **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new), how could it be any easier than that? I really don't get why people would actually still use an unsupported 3rd party website, it doesn't make much sense, but it's all up to you at the end of the day.

 

Muchas gracias mi Slim se pudo flashear sin problema,pero un amigo hizo el mismo método con una super slim y ahora ya no prende creo se bloqueó,no se sé si allá alguna forma de reparar o revertir esto sería de mucha ayuda cualquier intento se los agradezco,espero alguien nos ayude gracias.

English please...

If your friend bricked a superslim with a NOR chip then he should be able to use a hardware flasher (E3/Teensy) to restore the NOR.
But if the superslim uses emmc (12Gb consoles - CECH4xxx-A revisions), then the console is fully bricked as there is currently no hardware flasher available to restore emmc.

 

bro you should make this more simple like v1 theres too much pissin about do you know what I mean so I'm waiting for v3 for my other console (ps3) because I get confused with this I don't even know what files I need so if you read this message reply if your going to work on making it more simple and less files needed thanks .

 

bro you should make this more simple like v1 theres too much pissin about do you know what I mean so I'm waiting for v3 for my other console (ps3) because I get confused with this I don't even know what files I need so if you read this message reply if your going to work on making it more simple and less files needed thanks .

Bro?
Too much pissing about? An extra step to check that you haven't made a mistake & bricked your console before it's too late?
That's confusing?
lol I don't see anything confusing whatsoever & maybe taking time to read & understand might be a good start.
Moreover if you don't want to check for mistakes, don't do the extra step. Patch & reboot, then hope you didn't make a mistake.
And if you prefer to experience freezes & other issues on top of the extra risk, use v1.0 by all means, it's still available in the 1.0 thread. Support is ended but you are free to use it.
V3 will be the same as v2 in concept, with extra checks & some other stuff, so you are waiting for nothing.

 

is it possible to check md5 with rop chain ? the reason I ask this is flash_482.jpg. How to check md5 if flash_482.jpg is downloaded directly to ps3 hdd ?
You could also download flash_482.jpg to usb instead of flash_482.hex (usb000/picture)
Maybe a new feature to identify ps3 model and minver ? (for ps3 with bad stickers)

 

is it possible to check md5 with rop chain ? the reason I ask this is flash_482.jpg. How to check if it's good if it's downloaded directly to ps3 hdd ?
You could also download flash_482.jpg to usb instead of flash_482.hex (usb000/picture)
Maybe a new feature to identify ps3 model and minver ? (for ps3 with bad stickers)

Not easily done in ROP! Md5 support comes as a library in the sdk for executables to link to on compiling, not as syscalls or exports in the OS.
Javascript cannot do it either, not directly anyway due to file access permission, so...
If it were possible in a reasonable amount of work I would already have implemented it.
MinVerChk however is feasible. It's actually one of the 2 last missing checks I plan to add.

 

any idea how to check the file then ?

edit: @bguerville I googled javascript md5 function and I found this https://github.com/emn178/js-md5 and this https://github.com/blueimp/JavaScript-MD5 and many other pages maybe usefull

 

any idea how to check the file then ?

I am adding all the checks I can in v3. You will get the details when it's out.
But a complete foolproof solution that checks absolutely everything in its own, from file integrity to patch integrity will not happen, or at least I won't be making it.
V3 will be final, it will be as good as I can reasonably make it then I am moving on to another project full time. If people want to take the tools project over from there, they are welcome to, the source is always avalable .