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/​

 

Before applying the ps3xploit patch, did you install ofw 4.82 twice as per the instructions?

i did not. i only installed it once. is there a way to fix this?

 

i did not. i only installed it once. is there a way to fix this?

When flashing firmware, every single step in the instructions is of the utmost importance. Don't omit any step or you will experience problems.

2 possible options to solve your problem:

1. Restart the whole jailbreak process ie reinstall ofw 4.82 twice & then apply the ps3xploit patch with the Flash Writer 2.0. When you get the Flash Writer success message, don't restart/shut down the console, first make a ps3xploit dump & validate it with pyps3checker only (no other validation tool has been updated to validate the ps3xploit patch). If pyps3checker validation of the dump succeeds, restart the console & install the 4.82 cfw of your choosing.

2. Extract the internal hdd & reformat the whole hdd on PC, ntfs or any other partition type should do just fine. When we done, put the hdd back in the console, boot the console which will go directly into recovery mode. Place a 4.82 cfw PUP file on a FAT32 USB key & insert it into the USB port closest to the BD drive. The fw file path on USB should be x:\PS3\UPDATE\PS3UPDAT.PUP. Follow the on screen instructions to install the 4.82 cfw.

 

When flashing firmware, every single step in the instructions is of the utmost importance. Don't omit any step or you will experience problems.

2 possible options to solve your problem:

1. Restart the whole jailbreak process ie reinstall ofw 4.82 twice & then apply the ps3xploit patch with the Flash Writer 2.0. When you get the Flash Writer success message, don't restart/shut down the console, first make a ps3xploit dump & validate it with pyps3checker only (no other validation tool has been updated to validate the ps3xploit patch). If pyps3checker validation of the dump succeeds, restart the console & install the 4.82 cfw of your choosing.

2. Extract the internal hdd & reformat the whole hdd on PC, ntfs or any other partition type should do just fine. When we done, put the hdd back in the console, boot the console which will go directly into recovery mode. Place a 4.82 cfw PUP file on a FAT32 USB key & insert it into the USB port closest to the BD drive. The fw file path on USB should be x:\PS3\UPDATE\PS3UPDAT.PUP. Follow the on screen instructions to install the 4.82 cfw.

okay. thank you for your time man, greatly appreciated!!

 

okay. thank you for your time man, greatly appreciated!!

Np.

 

Hello.
One quick question.
Can I create a new online account after cfw installation, or better do it while still on 4.82 ofw? (on one console I'm already on cfw without an account, the second ps3 I'm just about to jailbreak)
Thanks.

 

Hi.
Need some help.
My PS3 is on 4.78 ofw, so I started the 4.78 dumper.
It displayed SUCCESS, and the USB flashdrive LED is flashing for more than 10 minutes.
What should I do? I know this is way too long, done already on other console.
Can I switch off the console?
Thank you.

 

Hi.
Need some help.
My PS3 is on 4.78 ofw, so I started the 4.78 dumper.
It displayed SUCCESS, and the USB flashdrive LED is flashing for more than 10 minutes.
What should I do? I know this is way too long, done already on other console.
Can I switch off the console?
Thank you.

No.
If the usb led is active, the dump is not finished. Be patient.
Note that if the console is an early phat model the nand dump takes longer than nor.
Also this 4.78 dumper might be based on an earlier dumper version using libc functions to write to usb. It takes much longer to dump the flash memory with that version compared to the latest version using cellFs syscalls. The performance of the libc io functions is abysmal, a 239Mb nand dump can take over 25 minutes, a 16Mb nor dump can easily take 7 or 8mn.

 

Thank god you answered in time.I was about to give up. Just beeped, and shut off. It took like 20+ minutes, don't know why so long. It's a 2504A with minver 3.5
Thank you.

 

Thank god you answered in time.I was about to give up. Just beeped, and shut off. It took like 20+ minutes, don't know why so long. It's a 2504A with minver 3.5
Thank you.

I just explained why.
The 4.78 dumper is based on older code using super slow libc io functions instead of the sys_fs syscalls used in the 2.0 release.

 

Ah yes, that makes sense. I will update to 4.82, just made a dump to be safe. Even I know it's not necessary, since the exploits never touch any per console stuff.

 

Ah yes, that makes sense. I will update to 4.82, just made a dump to be safe. Even I know it's not necessary, since the exploits never touch any per console stuff.

Rightly so. It costs you nothing & it's always a good idea to have a proper dump safely backed up.

 

I need help. Im trying to exploit my friend PS3. i use the jailbreak checker and it say 3.40. So when im trying gto exploit it i tried everything like delete cache and shit. but its still said it failed on 95%

 

I need help. Im trying to exploit my friend PS3. i use the jailbreak checker and it say 3.40. So when im trying gto exploit it i tried everything like delete cache and shit. but its still said it failed on 95%

Have you read the OP? All the information you needed was there, including how to ensure initialization success.
Btw "deleting cache & shit" is basically useless.

Anyway, just follow the exact steps I already detailed here. Don't omit anything.
http://www.psx-place.com/index.php?posts/108103

 

hi dear i brick my ps3 phat CECHHxx do you have a nor dump from this ps3

 

hi dear i brick my ps3 phat CECHHxx do you have a nor dump from this ps3

1. Please do no post the same thing in multiple threads. See the forum rules, in particular #7. http://www.psx-place.com/threads/site-forum-rules-guidelines.79/
2. You do not require a nor dump from anybody. If you didn't follow our instructions & ended up bricking your console by flashing a wrong file, you now need to dump your NOR with a hardware flasher then apply a no-fsm patch to the dump using pyPS3patcher. When it's done, validate the result using pyps3checker & if the fixed dump is valid, flash it back with the hardware flasher, then boot the console & install a 4.82 cfw of your choice.

 

hi thank you for your help i accidentally delete my dump from pc and have no dump do all nor dumps are same if someone can take a dump from this CECHHxx or CECHJxx and another nor consoles iam very appreciated

 

No. Every console is unique.
Anyway, your only option is a hardware flasher like the E3 or teensy.
With that you can dump your NOR memory, make the necessary corrections and flash it back.

 

hi thank you for your help i accidentally delete my dump from pc and have no dump do all nor dumps are same if someone can take a dump from this CECHHxx or CECHJxx and another nor consoles iam very appreciated

I already explained to you in my previous post that you did not need a prior dump!
All you need is a hardware flasher like E3 or Teensy installed on your console.

1. use the hardware flasher to dump the contents of your console's NOR chip to a dump file.
2. patch the dump file with the no-fsm option using pyPS3patcher.
3. validate the patched dump file with pyps3checker
4. use the hardware flasher to write the successfully validated patched dump file to the console's NOR chip.
5. start the console & in the Settings column of the XMB, use the System Software Update via USB feature to install the 4.82 CFW of your choice.

 

I already explained to you in my previous post that you did not need a prior dump!
All you need is a hardware flasher like E3 or Teensy installed on your console.

1. use the hardware flasher to dump the contents of your console's NOR chip to a dump file.
2. patch the dump file with the no-fsm option using pyPS3patcher.
3. validate the patched dump file with pyps3checker
4. use the hardware flasher to write the successfully validated patched dump file to the console's NOR chip.
5. start the console & in the Settings column of the XMB, use the System Software Update via USB feature to install the 4.82 CFW of your choice.

Kernel exploit is done?.. Are still in development

 

Kernel exploit is done?.. Are still in development

As far as i know there is no known kernel exploit above 4.40 fw.