Since the initial PS4 HEN Russian WIP called MiraHEN by The Sugarleaf followed by their open source PS4 homebrew initiative known as OpenOrbis, today PlayStation 4 developers from the OpenOrbis Team have officially launched The Mira Project which will include full expansion PS4 Custom Firmware (PS4 CFW) for 5.05 Jailbroken Consoles (currently targets 5.01 and is being ported per Mathieulh) and lots more as outlined below! 
Before we dive into all the juicy details, as @Wultra reminds everyone on Twitter the aim of this project will NOT be a full PS4 CFW PUP similar to those familiar with the PS3 scene, however, the Mira Homebrew Platform will consist of the following numerous components from the README.md:
The users guide is found at USERS.md yamsayin' check it out if you want instructions on how to build, install, and use the firmware once it has been installed on the console with any of the methods described within.
To quote from USERS.md: Mira Users Guide
Shwaoop dere it is
How to install
There are many ways that you can install the firmware, you will have to choose an option that suites your use case. The typical install will be done via a WebKit exploit via the web browser.
WebKit (Web Browser Install) Non-Permanent
This will involve using a WebKit userland exploit, and then elevating to kernel to install the MiraCFW. The changes will be lost upon reboot, but should survive sleep mode.
Permanent Install
There is not permanent install options at this time, nor will one be offered in the near future.
Preparing
TODO: Instructions on how to prepare
Installing
TODO: Instructions on how to install
Using MiraCFW
TODO: Instructions on using the features and configuring options
Using MiraLib
TODO: Instructions on how to use MiraLib
Developer Guide
To quote from DEVELOPERS.md: Developers developers developers
Here is the developers page
Environment variables that must be set
BSD_INC - FreeBSD based include headers, a compatible copy can be found at freebsd-headers
You can set this on windows using SET BSD_INC="path" or on linux using export BSD_INC="path"
ONI_FRAMEWORK - Absolute path, or relative path (to current building project) to the OniFramework directory
To get started, from the Mira root directory run Scripts/init_development_environment.cmd if you are on windows or Scripts/init_development_environment.sh if you are on linux.
This will parse the configuration file and set the environment variables accordingly.
REMOTE_BUILD_DIR ~/projects MIRA_DIR same jawn
Special Thanks To
We want to give a special shout out to these people in no paticular order.
Thanks to everyone who passed along this news on the PSXHAX Forums today!
Before we dive into all the juicy details, as @Wultra reminds everyone on Twitter the aim of this project will NOT be a full PS4 CFW PUP similar to those familiar with the PS3 scene, however, the Mira Homebrew Platform will consist of the following numerous components from the README.md:
- Firmware - Previously known as MiraHEN, this has been expanded into a full expansion custom firmware
- Tools - There are many tools included in the Mira project and they are listed out below
- newlib-ps4 - This is the libc implementation ported for PS4. It's a pain in the ass to compile, just take the pre-built binaries seriously.
- ld-ps4 - This is the linker to be used with newlib-ps4 to create Orbis compatible ELF files, or you could use CrazyVoid's elfFixupTool
- MiraLib - This is the communications library that will be specialized for operation with the Mira firmware.
The users guide is found at USERS.md yamsayin' check it out if you want instructions on how to build, install, and use the firmware once it has been installed on the console with any of the methods described within.
To quote from USERS.md: Mira Users Guide
Shwaoop dere it is
How to install
There are many ways that you can install the firmware, you will have to choose an option that suites your use case. The typical install will be done via a WebKit exploit via the web browser.
WebKit (Web Browser Install) Non-Permanent
This will involve using a WebKit userland exploit, and then elevating to kernel to install the MiraCFW. The changes will be lost upon reboot, but should survive sleep mode.
Permanent Install
There is not permanent install options at this time, nor will one be offered in the near future.
Preparing
TODO: Instructions on how to prepare
Installing
TODO: Instructions on how to install
Using MiraCFW
TODO: Instructions on using the features and configuring options
Using MiraLib
TODO: Instructions on how to use MiraLib
Developer Guide
To quote from DEVELOPERS.md: Developers developers developers
Here is the developers page
Environment variables that must be set
BSD_INC - FreeBSD based include headers, a compatible copy can be found at freebsd-headers
You can set this on windows using SET BSD_INC="path" or on linux using export BSD_INC="path"
ONI_FRAMEWORK - Absolute path, or relative path (to current building project) to the OniFramework directory
To get started, from the Mira root directory run Scripts/init_development_environment.cmd if you are on windows or Scripts/init_development_environment.sh if you are on linux.
This will parse the configuration file and set the environment variables accordingly.
REMOTE_BUILD_DIR ~/projects MIRA_DIR same jawn
Special Thanks To
We want to give a special shout out to these people in no paticular order.
- flatz
- SpecterDev
- EvilSperm
- Rogero
- Joonie
- AlexAltea
- Mistawes
- Abkarino
- qwertyoruiop
- CTurT
- Mathieulh
- Senaxx
- m0rph3us1987
- CrazyVoid
- xvortex
- bigboss
- ZeraTron
- xorloser
- AlAzif
- masterzorag
- fail0verflow
- idc
- Anonymous Contributors (You know who you are)
