PSXHAX - PSXHACKS: PSX HAX - PSX HACKS - PLAYSTATION HAX - PLAYSTATION HACKS

Recently there has been a few threads that allow people to run the PS4HEN from things like Android or Rasberry PI and it came to mind the same thing can be done with little effort from a wifi usb stick.

So here is a bit of info on that... the wifi stick i used was a 16gb Connect Wireless Stick and you will need PS4-HEN-VTX.

Just plug the usb stick into your pc and copy the exploit folder from the PS4-HEN-VTX (master.zip) archive to the root of the drive.

Unplug the usb stick from the pc as it will not serve files over wifi while it is plugged into the usb port.

The wifi usb stick has its own battery and you can turn it off an on pressing a button on the side of it. turn it on, a light will flash on it to indicate that it is on.

Goto the PS4 wifi network settings and look for the SanDisk Connect XXXXX ssid and setup the connection using the auto settings, there is no need to set dns and stuff.

Once the ps4 is connected to the wifi stick open the WWW broswer and goto http://172.25.63.1/ and you should have the list of files on the stick.

You can then go into the exploit folder and select index.html and it will launch the exploit.

You can also make a bookmark to http://172.25.63.1/myconnect/exploit/index.html and it will launch the exploit straight from the bookmark

There is also some settings you can use to change the ssid and add WPA2 password to the wifi connection and set the power save timer (auto off)

Some pictures...

List of files

Exploit folder

HEN success

Settings

PlayStation Vita developer Princess of Sleeping released via Twitter a PS Vita PUP Extractor utility to extract update files from PUP files alongside the source code today followed by a PKG Installer IDU Spoofer with details below.

Download: PUP-Extractor.vpk / GIT / pkg-installer-idu-spoofer.suprx / GIT

To quote from the README.md: PSV-PUP-Extractor

How to use:

1. vpk install.
2. Launch PUP-Extractor once.
3. Since the PSP2UPDAT folder is created in "ux0:", put the PUP file you want to extract into this folder.(Multiple placement possible)
4. After placing the files, start PUP-Extractor.
5. Wait until the Extract of the PUP file is over.
6. The application closes automatically when extraction of PUP file is completed
7. The extracted file is in "ux0:pSP2UPDAT_Dec/"

Test FW

• retail FW

1.80
1.81
3.60
3.67

• devkit FW

0.945.040
0.996.070
0.996.090
1.000.041
1.000.071
1.030.071
3.600.011

• Testkit FW

3.60 　　

Notes

In theory it is possible to extract all FWs, but if a system error popup appears from the application when extracting FW please let us know on Twitter PoSsvkey.

Changelog:

1.0

• Initial release

1.1

• While extracting, press and hold Start button to abort extraction
• Show number of extracted files

To quote from the README.md: pkg-installer-idu-spoofer

Only NPXS10031 or SKGPKG2CH

*NPXS10031
or *SKGPKG2CH
+ PSP PKG install - ok

Following the 1.76 PS4 API, PSN API, PS4API Open Sourced and recent PS4API 4.05 Port work today PlayStation 4 developer @BISOON made available a PS4API Server for PS4 4.05 Firmware to handle client R/W game memory requests aiding devs in making RTE/RTM tools.

Download: PS4API.bin / PS4 API Server GIT / PS4Lib-master.zip / PS4Lib GIT (Dynamic link library to create RTMs for PS4)

To quote from his post on NGU: Hello everybody after a while being away for a long time

Recently I got my PS4 (4.05) and thanks for everyone who spent his effort to make this happen on 4.5 and also we will not forget who is working on useful things for this community.

I spent the past two days looking for PS4API to control over the app memory using desktop tools/rtms, and unfortunately I got some but seems not worked with me or not stable enough (I am not underestimating their work, I really respect what they are done) also no new commits or updates on their projects for a long time.

So today I just pushed my PS4API server project into github for contribution, or for testing purposes. The client side not finished yet due the lack of time, so I will create the client lib based on the PS3Lib By iMCSx components (if he doesn't mind) to make it easy for people who already has created PS3 rtm tools and to make it simple for updating PS3 tools to PS4 (only changing the addresses will be enough) and the RPC as well if needed.

As I promised you guys I've finished the client side library in c# to make it easy for people who interested in making RTM tools. also demo app included for demonstration.

A Brief...

PlayStation 4 developer oct0xor (aka @Octopus) made available a PS4 Registry Editor and Viewer for other devs to examine the system.nvs, system.dat, system.idx, system.eap and system.rec.

Download: ps4_registry_editor-master.zip / GIT

This comes following the PS4 EAP Kernel Dumps, and to quote from his Blog page on it: PS4 Registry Editor

Recently I reverse-engineered PS4 registry format and made a simple tool to view and edit it.

Sony likes to encrypt and obfuscate everything. Every time it is very fun to figure it out.

PS4 registry is represented by a few different files and file formats:

• /system_data/settings/system.nvs
• /system_data/settings/system.dat
• /system_data/settings/system.idx
• /user/settings/system.eap
• /system_data/settings/system.rec

The most important are system.dat and system.idx. The file format is simple: system.idx contains info about every entry with offset and system.dat contains entries data.


Entries inside system.eap and system.rec are stored in obfuscated format.


First of all, its XOR’ed with 8 bytes, there are a lot of Null bytes, so it’s easy to figure out them without reversing. But thats not all. RegID’s are encrypted, entries and data are hashed. Besides that, RegID’s for system.eap and system.rec are encrypted with different keys.


Why to obfuscate? Dunno.

Folders with those files should be not easily accessible.

My suggestions:

• To prevent fuzzing of file format
• Implement new crypto and hash algorithms is the most fun thing to do at work
• This data is very sensitive

It becomes even more fun when you find a backdoor that grants access to registry for non-system processes. For it to work RegID’s should be encrypted in another fashion.

[ATTACH type="full" alt="PS4...

Following the PS4 Notifications Mod and his GTA V Native Caller, today PlayStation 4 developer @2much4u detailed some PS4 System Notification Types for 4.05 Firmware via Twitter for devs as outlined below.

Download: PS4_405_System_Notification_Types.txt / PS4 GTA V Native Caller

To quote from the Github page: Message types for sceSysUtilSendSystemNotification functions on PS4 version 4.05

0: -Blank-
1: Unknown USB device connected.
2: Too many USB hubs connected.
3: Connect this device using a USB cable, or connect it again.
4: %s battery level low.
5: %s disconnected.
6: Too many USB devices connected.
7: Cannot connect another Bluetooth device.
8: -Blank-
9: Cannot connect another controller.
10: Cannot connect another mouse or keyboard.
11: Cannot use controller feature of keyboard.
12: Device not supported.
13: Cannot use wireless controllers for PS3.
14: %s connected their companion app.
15: %s disconnected their companion app.
16: %s connected using Remote Play.
17: %s disconnected from Remote Play.
18: %s cannot see the screen due to Remote Play blocked scene.
19: %s can see the screen again because Remote Play blocked scene ended.
20: -Blank-
21: -Blank-
22: Less than %s free in system storage.
23: LAN cable not connected.
24: Wi-Fi network connection lost.
25: Cannot connect to network.
26: %s logged in to PS4.
27: -Blank-
28: Your account is banned from PlayStation Network.
29: PlayStation Network access from this PS4 banned or temporarily suspended.
30: Update the system software.
31: PlayStation Network is currently busy.
32: PlayStation Network is currently undergoing maintenance.
33: PlayStation Network is no longer available.
34: -Blank-
35: Sign in to PSN to use network features.
36: Signed out of PSN.
37: Update application to use network features.
38: Update system software to use network features.
39...