Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
PS4 CFW and Hacks       Thread starter PSXHAX       Start date Mar 19, 2019 at 12:04 AM       20      
Status
Not open for further replies.
Recently we saw the release of GhidraPS4Loader for PlayStation 4 developers to utilize in their reverse-engineering work, and following the PS4 Debugger Oni Framework scene dev @KIWIDOGGIE (aka diwidog on Twitter) updated his Github repository with GhidraOrbisTools which include loaders, scripts and other files for use with OpenOrbis ported from the costly IDA Interactive Disassembler to the free Ghidra SRE Suite of tools. :D

Download: GhidraOrbisTools-master.zip / GIT / Ghidra Allegrex (Ghidra processor module adding support for the Allegrex CPU) / ghidra91_extensions.zip (1.13 MB) / ghidra_9.1_DEV_20190714_win64.zip (215.82 MB) / ghidra_9.1_DEV_20190714_linux64.zip (215.55 MB) / ghidra_9.1_DEV_20190720_win64.zip (216.89 MB) / ghidra_9.0.4_PUBLIC_20190720_ghidra_psx_ldr.zip (Loader for PSX games and PsyQ libraries and objects) / ghidra_9.1_DEV_20190921_win64.zip (221.05 MB) / ghidra_9.2_DEV_20191221_win64.zip (224.57 MB)

Those interested in his other projects can drop by the blog located at KiwiDog.me (previously AllenThinks.com), and according to @g991 on Twitter himself and diwidog (aka kiwidog) will be combining both PS4 Ghidra Loaders as goldfitzgerald is working on userland while the kernel work is being done by diwidog. :lovewins:


Hackjob (day1) PS4 kernel loader, will clean then PR to golden's loader via Github.com:
Code:
For the love of anything, don't use this as a Ghidra example

HACK JOB PLUGIN MANG

This was a dirty filthy direct port of IDA scripts and their shortcomings (Although ghidra provides many thing that will fix the hackyness of this script port)

Ghidra's still slow, and unusable for many things I do, but doesn't mean it's still not powerful enough to overtake IDA.

Lower your prices Hex-Rays, extend support, I have unlimited time, not money.

<?xml version='1.0' encoding='ISO-8859-1' ?>
<!--

   This is an XML file intended to be parsed by the Ghidra help system.  It is loosely based
   upon the JavaHelp table of contents document format.  The Ghidra help system uses a
   TOC_Source.xml file to allow a module with help to define how its contents appear in the
   Ghidra help viewer's table of contents.  The main document (in the Base module)
   defines a basic structure for the
   Ghidra table of contents system.  Other TOC_Source.xml files may use this structure to insert
   their files directly into this structure (and optionally define a substructure).

   In this document, a tag can be either a <tocdef> or a <tocref>.  The former is a definition
   of an XML item that may have a link and may contain other <tocdef> and <tocref> children.
   <tocdef> items may be referred to in other documents by using a <tocref> tag with the
   appropriate id attribute value.  Using these two tags allows any module to define a place
   in the table of contents system (<tocdef>), which also provides a place for
   other TOC_Source.xml files to insert content (<tocref>).

   During the help build time, all TOC_Source.xml files will be parsed and    validated to ensure
   that all <tocref> tags point to valid <tocdef> tags.  From these files will be generated
   <module name>_TOC.xml files, which are table of contents files written in the format
   desired by the JavaHelp system.   Additionally, the genated files will be merged together
   as they are loaded by the JavaHelp system.  In the end, when displaying help in the Ghidra
   help GUI, there will be on table of contents that has been created from the definitions in
   all of the modules' TOC_Source.xml files.


   Tags and Attributes

   <tocdef>
   -id          - the name of the definition (this must be unique across all TOC_Source.xml files)
   -text        - the display text of the node, as seen in the help GUI
   -target**    - the file to display when the node is clicked in the GUI
   -sortgroup   - this is a string that defines where a given node should appear under a given
                  parent.  The string values will be sorted by the JavaHelp system using
                  a javax.text.RulesBasedCollator.  If this attribute is not specified, then
                  the text of attribute will be used.

   <tocref>
   -id             - The id of the <tocdef> that this reference points to

   **The URL for the target is relative and should start with 'help/topics'.  This text is
   used by the Ghidra help system to provide a universal starting point for all links so that
   they can be resolved at runtime, across modules.


-->


<tocroot>
   <!-- Uncomment and adjust fields to add help topic to help system's Table of Contents
   <tocref id="Ghidra Functionality">
       <tocdef id="HelpAnchor" text="My Feature" target="help/topics/my_topic/help.html" />
   </tocref>
   -->
</tocroot>
:arrow: For those still using the Interactive Disassembler, here's a collection of scripts and tools for PS4 IDA analysis from zecoxao as well:

Download: ps4ida-master.zip / GIT

And from the README.md: PS4IDA

Collection of scripts and tools for PS4 IDA analysis

Credits
  • SocraticBliss: for most of the scripts
  • flatz: for the 27000(!) symbols
  • idc: for ps4libdoc
  • zer0xff: for some symbols
Download: ghidradec13.zip (2.51 MB - Password: exetools)
GhidraOrbisTools PS4 Loader and IDA Script Ports by Kiwidoggie.jpg
 

Comments

it does nothing as usual

it's funny how they always advertise for the "development" when they basically do nothing for the regular user
the regular user just needs playable titles >5.05 ATM
nothing else
no one cares about the rest
99% of the people following these posts want to play, because it's a console after all

just release the damn beast through an anonymous twitter and leave us alone
 
Status
Not open for further replies.
Back
Top