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

 

can you be more active on discord

Sorry i have a private life. and why hijack this thread? (Don't answer have respect for the topic at hand). Cuss detection is fine, NO one is having an issue but you. The issue can't be replicated so i would assume its on your end or you are using language your not suppose to. Either way this discussion is done in this thread. not the place for it

 

4.82 OFW - Never previously exploited
CECH-A1 Trying Exploit 2.0 (Nand Dump and Write)

*The Nand_hdd option fails to save the link.*
"An error occurred (80711008)"

are you using the webpage and TRIANGLE to save, as stated? the jpg is in same directory and will save. That jpg is just a placeholder for writing to

- Flasher instantly shows "success" and am asked to dump again to verify only to basically get the same check result. Reboot and no ability to CFW update

are you actually pressing the write button after init? Then checking dump after again?

well, anyways, thanks for the input on the situation

.

 

4.82 OFW - Never previously exploited
CECH-A1 Trying Exploit 2.0 (Nand Dump and Write)

*The Nand_hdd option fails to save the link.*
"An error occurred (80711008)"

I've scoured this thread and I can't seem to find any help with my particular model. I have only gotten "successful" dumps using Nand, Nand hdd doesn't even let me save the link for the photo and I can't find info on moving the pic another way or if just copying it over from usb is an option. I also don't get any system reboots like I see in so many Nor videos.

The 239 mb dump.hex it writes to the usb fails check every time using PS3DumpChecker. Python just closes the window right away and doesn't write a log.

"Error on 1 of 105 Checks" with R0S0 showing the error.
12:04:03 PM : Hash check Started!
12:04:03 PM : Hash check for 009.02 ROS0 Hash Started... Result: FAILED!
Actual data: MD5 Hash: 8ED20C654ACF584A71FBD8BB7038710D

I presume this means something went wrong and should not continue, but I have because why not brick a collectors item? xD

All the faq's and tutorials are focused at Nor and usually lead me into dead ends because they seemingly act differently. But if I'm wrong about the hex check and continue to write the flash using Nand, I have varying results:

- Flasher instantly shows "success" and am asked to dump again to verify only to basically get the same check result. Reboot and no ability to CFW update

- Flasher shows loading bar for about 40% before success and hex check shows the same result after another dump and reboot

- Flasher loads to 100% then fails asking to refresh. I now clear cache and reboot and get one of these 3 results.

If someone could point me in the right direction I would appreciate it.

For starters you are using the wrong tool to check your dumps. You will never get a correct result by using ps3dumpchecker which has never been updated to work with ps3xploit tools. You said you scoured all faqs & tutorials but obviously you must have missed that crucial part, mentioned both in the OP & on **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new). The only tool that has been updated is pyPS3checker, available on github/littlebalup/PyPS3tools

You don't explain either whether you are using locally hosted files or **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new).
If files are locally hosted you cannot rely on miniweb server, there is a flaw in it that will not let you download the picture file placeholder necessary for dumping on hdd. That's also mentioned in various places.

 

I really wish someone talks more about metldr 2 as we have little info about it

Metldr.2 and bootldr.2 have new keysets which are as of yet unattainable. If we even get them ecdsa won't let us sign the new metadata(lv0.2 and ldrs.2).
As for what is in the metldr.2 and lv0.2. Well the metadata Sony uses is such that both decrypt the same loaders and lv0 so really metldr.2 will only offer root key of ps3 and it doesn't have any new code which is worth investigating

Also there can be exploits like ps3xploit also kernel and hv exploits which will make up cfw by running browser. One doesn't need keys to do everything. Keys is just fun to take control at boot and that's about it

I'm trying to find kernel vulnerabilities and we should be able to find some soon. If we don't find one we might be able to just downgrade superslims etc to minver and use the known exploits. Once we get kernel exploit, we will be able to run payload in kernel and then once we get hv exploit we will be able to dump .2 keys, lv2, lv1 poke and npdrm ecdsa check bypassed

 

I figured out what the problem is with and checker.py and it appears my dump is OK as far as I can tell. I assume that I am to patch the original dump somehow to continue. Can't seem to find those details.

I can't respond to the previous quotes for some reason but here's what I got:
Figured out how to make checker.py validate my dump. Appears OK. I have been using the hosted server for this but have had little to no success just dumping from Nand_hdd. Was able to save the link from the hosted server but it fails to initialize step 2 every time. I got my dump using Nand through the hosted server.

So now I have a dump with no idea how to patch it to continue. Is that even a step I need to take or is just copying the flash_482 to the usb and writing the flash the only other step I need?

 

I figured out what the problem is with and checker.py and it appears my dump is OK as far as I can tell. I assume that I am to patch the original dump somehow to continue. Can't seem to find those details.

I can't respond to the previous quotes for some reason but here's what I got:
Figured out how to make checker.py validate my dump. Appears OK. I have been using the hosted server for this but have had little to no success just dumping from Nand_hdd. Was able to save the link from the hosted server but it fails to initialize step 2 every time. I got my dump using Nand through the hosted server.

So now I have a dump with no idea how to patch it to continue. Is that even a step I need to take or is just copying the flash_482 to the usb and writing the flash the only other step I need?

You never need to patch the dump or flash anything else than the provided hex file otherwise you will brick. That's explained in the OP & on **ps3xploit.com >Domain no Longer owned by team** (ps3xploit.me =new).

The instructions are summarised here:
1. Use the flash writer to patch the flash memory using flash_482.hex. .
2. After flash writer final success message, load the flash dumper, dump the nor/nand & validate that the patching was satisfactory in the python checker tool. If everything worked well, in your dump validation results, one ros will be corrupted, the other will be valid & detected as ps3xploit patched.
3. If validation was successful as just described above, reboot & install cfw.
If not, don't reboot. You made a mistake & need to use the flash writer again, properly this time, to repair it.

 

I keep getting the same results from the checker before and after the flash the 1 in 15 times it works. The same ROS0 Warning exists both times. I don't think it is taking the flash because it happens instantly and I see no indicator on my usb that it was being accessed.

 

Metldr.2 and bootldr.2 have new keysets which are as of yet unattainable. If we even get them ecdsa won't let us sign the new metadata(lv0.2 and ldrs.2).
As for what is in the metldr.2 and lv0.2. Well the metadata Sony uses is such that both decrypt the same loaders and lv0 so really metldr.2 will only offer root key of ps3 and it doesn't have any new code which is worth investigating

Also there can be exploits like ps3xploit also kernel and hv exploits which will make up cfw by running browser. One doesn't need keys to do everything. Keys is just fun to take control at boot and that's about it

I'm trying to find kernel vulnerabilities and we should be able to find some soon. If we don't find one we might be able to just downgrade superslims etc to minver and use the known exploits. Once we get kernel exploit, we will be able to run payload in kernel and then once we get hv exploit we will be able to dump .2 keys, lv2, lv1 poke and npdrm ecdsa check bypassed

after one jailbroken their playstation SS is it possible that it can be dumped an used for researching metldr 2.

 

after one jailbroken their playstation SS is it possible that it can be dumped an used for researching metldr 2.

Yes.
But there is nothing to be researched. It's a revision update just for metadata and ecdsa fail fix. All the ps3s out there including hackable and unhackable loaf the same lv0 and loaders. When we modify them the 3k/4K metadata becomes invalid(sha1 and ecdsa of sections) and causes ps3 to shutdown

 

Yes.
But there is nothing to be researched. It's a revision update just for metadata and ecdsa fail fix. All the ps3s out there including hackable and unhackable loaf the same lv0 and loaders. When we modify them the 3k/4K metadata becomes invalid(sha1 and ecdsa of sections) and causes ps3 to shutdown

so even when you got an jailbroken SS its still almost impossible to look at metlrd2

 

so even when you got an jailbroken SS its still almost impossible to look at metlrd2

It should be hard even if possible.
Also what will we achieve by getting those keys? Nothing.

 

@habib would the ecdsa keys allow running full cfw on 3k and 4k?? but there is no way to dump those keys even with exploits right??

 

@habib would the ecdsa keys allow running full cfw on 3k and 4k?? but there is no way to dump those keys even with exploits right??

Yeah it would allow full cfw and they are impossible to get because they are not in the system itself. It's a complicated maths which generate you 2 keys in which one you keep private and keep one public which is used to verify file integrity

 

my browser won't let me go to page.
goes to google then wont open. any ideas? thank you

 

my browser won't let me go to page.
goes to google then wont open. any ideas? thank you

either your entering the address wrong or your using the search option on the ps3

 

I was using browser. but found another option.
@bitsbubba I thank you for taking time to help.
great work by the way.

 

I was using browser. but found another option.
@bitsbubba I thank you for taking time to help.
great work by the way.

it helps if you make the exploit page your homepage

 

Yeah it would allow full cfw and they are impossible to get because they are not in the system itself. It's a complicated maths which generate you 2 keys in which one you keep private and keep one public which is used to verify file integrity

are they hardware based or software based?

 

are they hardware based or software based?

Let's break into Sony's headquarters

 

Let's break into Sony's headquarters

heheheh u sirious or not becuase im not sure when an dev says something