PS3 SYSCON Firmware key is now public (release by zecoxao) - What does it mean?

Discussion in 'THE FEED (Submit/View News)' started by STLcardsWS, Sep 2, 2019.

By STLcardsWS on Sep 2, 2019 at 5:37 PM
  1. 8,991

    STLcardsWS Administrator

    Sep 18, 2014
    Likes Received:
    Trophy Points:
    Developer @zecoxao has recently released something that the dev has been working on obtaining for 10 years now and that obstacle that has now been cleared is the SYSCON Firmware Key and zecoxao has now released it to the public. First off we must erase some misconceptions as this is not going to directly lead us to a CFW on nonCFW PS3's anytime soon. As the dev stated on twitter "needless and pointless to say that the confusion being created around these keys that they will be useful for cfw on ps3 3k and superslim is a very farfetched idea. unless we have access to the TSOP 78K0R models, we will not be able to obtain anything else" and then when @kozarovv provided a follow-up question about 3k models here the developer responded with "don't expect miracles, is all i'm saying ". Now the question (which was asked by @DeViL303) "So what can we do with this as of now, what is possible with just this key alone and current knowledge? Then @zecoxao provides an explanation seen in this post (and also seen below). So this is a great feat that has been made, but its still being investigated and something that will need to be explored in the weeks to come to fully understand what we can be uncovered,. .


    • i got the syscon firmware key, a dream i've been pursuing for the past 10 years. now that i have it i feel like i've acomplished my goal. the rest will follow naturally.

      What can developer's do with this key?

      via @zecoxao : With this key the following has happened:

      14 syscon firmwares for the BGA models (CXR) were decrypted.
      from them, keys for PATCHES and FULL FW signing and encryption, as well as decryption and validation were found. we can now sign our own patches and fws for the following models:

      • TMU-510
      • COK-001
      • COK-002
      • SEM-001
      • DIA-001
      • DIA-002 or DEB-001 (same soft id)

      Additionally we found the initialization key for eid1 as well as the process of initializing it from factory
      We also found 7 extra keys (we still don't know what they do)
      Finally, we found out there is a secret keyslot function that generates keys for
      • SNVS
      • AUTH1/AUTH2
      • Regions of EEPROM
      • PATCH keys xoring (to generate the final keys)
      • Relationship with the other 7 Keys

      What still has to be done:
      • Hack the 78K0R chips (the TSOP ones found in later models)
      • Dump the firmware of those chips
      • Get the DYN-001 patch keys
      • Find an exploit on arm firmware that works in 78k0r firmware

      Edit: and yes, you can do all that fun kinky shit of fan boosting at max speeds, led disco panic attack, and star wars theme ON A DECR-1000! THIS is a devkit, so THIS is the ONLY device that supports FULL FUCKING FIRMWARES! DO NOT CONFUSE IT with a DECR-1400, that is a HALF devkit!

    Release Source:

    Thanks to @NathanHale for the news alert
    Last edited: Sep 10, 2019
    Louis Garry, esc0rtd3w, afrv and 14 others like this.


Discussion in 'THE FEED (Submit/View News)' started by STLcardsWS, Sep 2, 2019.

    1. afrv
      CECH-Pxx support? Does this simply support all models?
    2. Naked_Snake1995
      Persona 4 - Arena says hi!

      Sent from my G8141 using Tapatalk
      TheMadPolarBear likes this.
    3. Naked_Snake1995
      CEHC-P already has the Syscon decrypted, this its for the newer models that are implemented with MetLdr2, or in other words Firmware 3.60 or higher, also known as Non-CFW Models.

      The Firmware 3.56 isn't a actual Exploit Entry-Point, but actually a reference to distinguish the consoles that are Exploitable with Custom Firmware and the don't have the newer Syscon with MetLdr2 implemented, and the ones that do,so when you hear next time Factory Firmware 3.56 or below it means that MetLdr2 isn't implemented and its an older Syscon Chip, meaning Custom Code can be flashed to the Syscon without any risks of bricking, at the moment if you try to install any CFW on a newer Syscon/Model after 3.56, there will be a brick, this is because the Syscon has not been decrypted yet, so the operation procedure is unknown, so with the newer keys you can understand how the newer Syscon works, and how to work with the MetLdr2 so you can flash any custom code, so the Syscon can recognise it as an OFW Code, without entering into Panic-Mode.

      Sent from my G8141 using Tapatalk
      Last edited: Oct 16, 2019
      esc0rtd3w, Algol, iesus gamer and 2 others like this.
    4. afrv
      Likely zecoxao quit because he wanted to quit a long time ago, but now finally finished what he started - it was probably more of a burden than anything for him to follow the scene for this long
    5. zecoxao
      here is latest idb from my friend @3141card
      currently some fun stuff found, like the infamous number of on and off times and shutdowns :)

      Attached Files:

    6. zecoxao
      Again another new database by @3141card with more resolved function names and symbols :)

      Attached Files:

    7. zecoxao
      New database by picard, documenting some RRAC registers (already on the wiki) and also some POWERSEQ funcs

      Attached Files:

Share This Page