User talk:Zecoxao: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
Line 128: Line 128:
|-
|-
|}
|}
= request_idps generated files binary xor =
* [[https://mega.co.nz/#!J1M1zKDK!MNBmfqyoqp2hJR3kj8urcKZ-b_pCVnMBrY2zcb-gTBs 2 generated cex files]]
* [[https://mega.co.nz/#!N1dmQA5C!gbmqekcbUorH-2zXlakfxJNd1QMC8fSMoNl0pvdfFjs 2 generated decr files]]
* [[https://mega.co.nz/#!VlUmgJBJ!gWk0Y4aXSOu7VoxiwfpnkFpOm7pNaWJqgl39coZ93L4 2 generated dex files]]

Revision as of 08:07, 9 July 2015

The Last Piece of the Puzzle

How

  • By enabling diagnostic mode on the ps3, we can enable the use of JTAG again (it's temporarily disabled when diag mode isn't set)
  • It is possible to dump the syscon firmware using this method (in unencrypted state)
  • The JTAG registers/TAP-controllers need to be bruteforced / reverse engineered
  • The leaked service manuals present information about the pins connected to the JigPin
  • The ObjectiveSuite contains an object (DIAGSERVICE) used to diagnose the ps3 using JTAG
  • Using a DIY JigPin would facilitate the task, but we still need more info about the hardware and software interface used by ObjectiveSuite to handle this.
  • This would probably work on ps4 too (provided that the diag pin and the JTAG pins still exist)

To wikify

request_idps generated files binary xor