PS4 Registry Editor Now Released

  • Hello Guest! Welcome to ConsoleCrunch, to help support our site check out the premium upgrades HERE! to get exclusive access to our hidden content.
  • Unable to load portions of the website...
    If you use an ad blocker addon, you should disable it because it interferes with several elements of the site and blocks more than just adverts.
  • Read Rules Before Posting Post Virus Scans with every program.

Luke

God Tier
Retired Staff
Active Member
Oct 6, 2015
232
193
103
UK
Blue-Bytes.jpg

With the ever growing community of PS4 Modding, oct0xor brings us the first PS4 Registry Editor which allows us to view the files using a simple tool that he made by reverse-engineering the Registry itself. In its current state you can view the following files;
  • /system_data/settings/system.nvs
  • /system_data/settings/system.dat
  • /system_data/settings/system.idx
  • /user/settings/system.eap
  • /system_data/settings/system.rec
However system.nvs isn't supported due to the fact its stored in a kernel like view so parsing it would be entirely dependant on they system version but it has the exact same entries as system.rec. Due to the 5.01 update system.rec implemented a new layer of encryption so the tool currently doesn't feature the ability to add new entries or rebuild the registry as of yet.

Within the registry the most important files are system.dat and system.idx with system.dat containing information on entries data and system.dat containing information on every entry and its offset. The files system.eap and system.rec are stored in a obfuscated format which requires you to guess the XOR pattern itself however due to it being XOR'd with 8 bytes there are a lot of null bytes which this makes it a lot easier to guess.

iaQ4A7L.png

E8HbL5b.png


Within the system.eap the RegID's are encrypted along with the data and entries hashed but the RegID's in system.eap and system.rec are encrypted with different keys. It makes you ask the question; Why are these files are obfuscated in the way they are? Well oct0xor believes that the files shouldn't be easily accessible and the files themselves are very sensitive which does make sense after all.

UfAJRdy.png


Another thing with the tool is when you are able to find a backdoor which can give you access to other registry's for any non-system processes but for this to work the RegID's should be encrypted in another way. The link for oct0xor's GitHub will be down below which include the source for his Registry tool. Let me know your thoughts down below in the comments and t
thanks for taking the time to read my article, thanks!! :)

Credits: oct0xor

GitHub

Other Images:
OuacHga.png

RQtP3k3.png
 

lxlKingzOFAllModzlxl

Community Veteran
Retired Staff
Community Veteran
Determined Poster
Active Member
Console ID Poster
May 1, 2016
1,386
1,161
398
inside your mind
Blue-Bytes.jpg

With the ever growing community of PS4 Modding, oct0xor brings us the first PS4 Registry Editor which allows us to view the files using a simple tool that he made by reverse-engineering the Registry itself. In its current state you can view the following files;

  • /system_data/settings/system.nvs

    /system_data/settings/system.dat

    /system_data/settings/system.idx

    /user/settings/system.eap

    /system_data/settings/system.rec
However system.nvs isn't supported due to the fact its stored in a kernel like view so parsing it would be entirely dependant on they system version but it has the exact same entries as system.rec. Due to the 5.01 update system.rec implemented a new layer of encryption so the tool currently doesn't feature the ability to add new entries or rebuild the registry as of yet.

Within the registry the most important files are system.dat and system.idx with system.dat containing information on entries data and system.dat containing information on every entry and its offset. The files system.eap and system.rec are stored in a obfuscated format which requires you to guess the XOR pattern itself however due to it being XOR'd with 8 bytes there are a lot of null bytes which this makes it a lot easier to guess.

iaQ4A7L.png

E8HbL5b.png


Within the system.eap the RegID's are encrypted along with the data and entries hashed but the RegID's in system.eap and system.rec are encrypted with different keys. It makes you ask the question; Why are these files are obfuscated in the way they are? Well oct0xor believes that the files shouldn't be easily accessible and the files themselves are very sensitive which does make sense after all.

UfAJRdy.png


Another thing with the tool is when you are able to find a backdoor which can give you access to other registry's for any non-system processes but for this to work the RegID's should be encrypted in another way. The link for oct0xor's GitHub will be down below which include the source for his Registry tool. Let me know your thoughts down below in the comments and t
thanks for taking the time to read my article, thanks!! :)

Credits: oct0xor

GitHub

Other Images:
OuacHga.png

RQtP3k3.png
nice i like all i see :) indeed
 
  • Like
Reactions: Luke
General chit-chat
Help Users
    Chat Bot: apple21 is our newest member. Welcome!