Jump to content

zecoxao

Super Admin
  • Content Count

    883
  • Donations

    $6.00 
  • Joined

  • Last visited

  • Days Won

    84

Reputation Activity

  1. Like
    zecoxao reacted to 3absiso in PlayStationHaX Wishes You Ramadan Kareem   
    Ramadan Kareem to u all,
    Thanx Greg
  2. Upvote
    zecoxao reacted to 3absiso in [Tutorial] Convert PS4 4Pins to 5Pins PSU   
    Hi;
    Here we have a lot of PS4 that can be imported from USA and some from Europe, and for who does not know some comes with a 5Pins PSU and some with 4Pins PSU.
     
    In this tutorial we will convert a 4Pin PS4 to use a 5Pin PSU, there may other methods to do that but i found this is the easiest:
     
    - You Will need One 4 Pins Power Cable and One 5 Pins Power Cable and follow the images and Diagram:
     

     
     

     
     
    Thanx
     
  3. Like
    zecoxao got a reaction from GregoryRasputin in Phat PS3, siren beep. downgrade   
    you probably converted it from CEX to DEX (i had the siren beep only when that happened and it checked hashes) but from your description that doesn't seem to be the case :/
  4. Like
    zecoxao got a reaction from GregoryRasputin in How to setup 3.65 Local DNS for easy upgrade   
    Tools required:

    1. PSVita with wifi working
    2.Al Azif's dns tool found in his repo: https://github.com/Al-Azif/ps4-exploit-host/releases
    3. 3.65 update found in darthsternie.net (or any other one you want to really)
    4. 3.65 psp2-updatelist.xml (see 3)
    5. A brain to know which region the vita belongs to
     
    Steps:
    1. Download and extract 3.65 OFW and psp2-updatelist.xml from darthsternie.net
    2. Download al azif's dns host tool and extract it
    3. Place both the pup and the updatelist.xml on your updates folder of dns host.
    4. Once you figurre out which region your vita is from (us,eu,uk,etc) replace ALL instances of the given region in psp2-updatelist.xml with the one from your vita.
    5. Start the dns host. If everything goes well you should see your PC's ip for main IP and DNS.
    6. Set up the wifi of your console, taking into consideration that the dns must be the same one displayed on the host terminal window!
    7. Attempt to update. You should see a notification of update version 3.65. if not, recheck region, and that the xml and updare files are ok!
    8. Update
  5. Thanks
    zecoxao got a reaction from OldBrain in How to setup 3.65 Local DNS for easy upgrade   
    Tools required:

    1. PSVita with wifi working
    2.Al Azif's dns tool found in his repo: https://github.com/Al-Azif/ps4-exploit-host/releases
    3. 3.65 update found in darthsternie.net (or any other one you want to really)
    4. 3.65 psp2-updatelist.xml (see 3)
    5. A brain to know which region the vita belongs to
     
    Steps:
    1. Download and extract 3.65 OFW and psp2-updatelist.xml from darthsternie.net
    2. Download al azif's dns host tool and extract it
    3. Place both the pup and the updatelist.xml on your updates folder of dns host.
    4. Once you figurre out which region your vita is from (us,eu,uk,etc) replace ALL instances of the given region in psp2-updatelist.xml with the one from your vita.
    5. Start the dns host. If everything goes well you should see your PC's ip for main IP and DNS.
    6. Set up the wifi of your console, taking into consideration that the dns must be the same one displayed on the host terminal window!
    7. Attempt to update. You should see a notification of update version 3.65. if not, recheck region, and that the xml and updare files are ok!
    8. Update
  6. Like
    zecoxao reacted to GregoryRasputin in [Update][Released] Gameboy Advance Emulator For PS4 By @HackHackStopSop   
    7heD4RKH4CK has ported belek666's version of TempGBA,  a Gameboy Advance Emulator to the PS4, it does not run native on the PS4, but rather runs on top of the PS2 Emulator on the PS4, it runs the same way as last weeks MegaDrive Emulator release.

     
     
     
     
    The developer had help from Markus95 and PlayStationHaX Admin @zecoxao , unfortunately i cannot link the download as it contains files that would be considered a CopyRight Violation.
     
     
    UPDATE
    Markus95 released a version of the emulator without the roms:
    Source
  7. Like
    zecoxao reacted to mr_lou in The real meaning of the word "homebrew"   
    It has come to my attention that a large group of people are walking around with a wrong idea about what the word "homebrew" means. There seems to be a wide misconception that the word is exclusively related to hacking activities, and that it only applies to platforms that doesn't normally "allow" you to create your own software. This perception is completely wrong.
     
    Let me start out small and simple:
     
    When a company makes a game, it is called "a commercial game".
     
    When a consumer makes a game (thus in his sparetime as a hobby), then it is called "a homebrew game".
     
    The platform doesn't matter.
    The technique doesn't matter.
    The language doesn't matter.
     
    The only thing that determines that it is "homebrew", is the fact that it is made by an individual (or a small group of hobbyists) rather than a company, and that it was done at home in his sparetime.
     
    And that's it. Plain'n'simple. That's how you define a homebrew game. Nothing illegal about it whatsoever.
     
     
     
    I'm an old geezer. I grew up with the Amstrad CPC 8-bit computer in the 80s. This computer too had a lot of commercial titles that you could buy. And it also had a lot of homebrew games. People were encouraged to make these homebrew games back then - so a lot of people did!
    It was easy back in those days, because most of the 8-bit computers came with a built-in programming language called BASIC. As soon as you turned on the computer, it was ready to receive your BASIC instructions.
    We didn't have the Internet back then, so a lot of these homebrew games were instead spread via magazines. Pages full of BASIC lines that you would then sit and type in yourself. Ah yes, those were the days.
     
    The next generation of computers, such as the Amiga, didn't come with a built-in programming language. On these computers you had to load a programming language yourself if you wanted to code anything. But the result was still called a homebrew game.
     
    And then we have all the game consoles that doesn't give you any immediate way of loading a programming language onto the machine itself. So you naturally can't develop anything on those consoles. But that simply means you develop it on another platform. It's called cross platform development, and it's done on a lot of platforms. That's all. It is still a homebrew game - and there's still nothing illegal about it.
     
     
    But I understand where the confusion comes from here in the PSX communities.
     
    One of the reasons people are confused is probably because you need to jailbreak your PlayStation in order to run (native) homebrew on it. Jailbreaking your console isn't illegal though. But you probably think it is because the majority of people who jailbreaks their console, does it not to run homebrew games, but rather to run pirated software - and THAT is indeed illegal yes.
     
    Another cause of the confusion is probably emulators. If you code (or port) an emulator, then it also qualifies as homebrew. It is still you sitting at home coding some software - and it still isn't illegal. The illegal part in relation to developing an emulator, only comes if you include pirated copies of games and/or ROM files with it. THAT is what makes it illegal. But you're absolutely allowed to code and distribute the emulator itself, as long as your users have to supply the ROM files and games for themselves. (Supplying the ROM files and games themselves is also normally perfectly legal - as long as they own the original game(s) as well).
     
    It's easy to see how all of this may have confused you and lead you to believe that homebrew is all about (illegal) hacking. But now you at least know better. 😉
     
    To summarize: Homebrew is no more illegal than a car: You can use a car to break the law if you absolutely want to - but no one will ever blame any aspect of the car for that.
  8. Like
    zecoxao reacted to GregoryRasputin in [Released] LibOrbisPKG   
    maxton has released an application for reading and writing PS4 PKG's and PFS archives, here is a quote from the source:
     

     
     
     
    Source
  9. Thanks
    zecoxao got a reaction from ConsoleHax in How to test your own sdk homebrew   
    Tools:
    HEN 1.8
    https://cdn.discordapp.com/attachments/159066660962041856/498138504656715776/ps4-hen-vtx.bin
    https://cdn.discordapp.com/attachments/159066660962041856/498138541570654209/index.html
     
    payload_ldr
    https://cdn.discordapp.com/attachments/159066660962041856/498062138686963712/payload_ldr_verbose.pkg
     
    FTP payload/OrbisMAN

    (Optional But Recommended) Mira for usermode logs / UART

    Step0:If needed for your homebrew, put ALL resources inside /data/ (specify the path in your homebrew as well)
    Step1: Create a folder called self inside data folder (You can use ftp or orbisman for this)
    Step2: Launch HEN 1.8
    Step3: If needed, launch mira aswell(for logging your homebrew/game while it's being tested)
    Step4: Install payload_ldr pkg
    Step5: Launch payload ldr (the screen should hang at start)
    Step6: Send the main eboot (it MUST be a self file)
     
    sender.py --endpoint 192.168.1.4 eboot.bin Other options are available but for now i'll only use this one
    Step7: Your homebrew should now run and (if you have it) logs should be displayed on putty/some other Telnet/Serial logger
  10. Thanks
    zecoxao got a reaction from OldBrain in How to test your own sdk homebrew   
    Tools:
    HEN 1.8
    https://cdn.discordapp.com/attachments/159066660962041856/498138504656715776/ps4-hen-vtx.bin
    https://cdn.discordapp.com/attachments/159066660962041856/498138541570654209/index.html
     
    payload_ldr
    https://cdn.discordapp.com/attachments/159066660962041856/498062138686963712/payload_ldr_verbose.pkg
     
    FTP payload/OrbisMAN

    (Optional But Recommended) Mira for usermode logs / UART

    Step0:If needed for your homebrew, put ALL resources inside /data/ (specify the path in your homebrew as well)
    Step1: Create a folder called self inside data folder (You can use ftp or orbisman for this)
    Step2: Launch HEN 1.8
    Step3: If needed, launch mira aswell(for logging your homebrew/game while it's being tested)
    Step4: Install payload_ldr pkg
    Step5: Launch payload ldr (the screen should hang at start)
    Step6: Send the main eboot (it MUST be a self file)
     
    sender.py --endpoint 192.168.1.4 eboot.bin Other options are available but for now i'll only use this one
    Step7: Your homebrew should now run and (if you have it) logs should be displayed on putty/some other Telnet/Serial logger
  11. Thanks
    zecoxao got a reaction from DEFAULTDNB in How to test your own sdk homebrew   
    it's a mod
    i'd like it if you could add it to your nodemcu payload
  12. Thanks
    zecoxao got a reaction from DEFAULTDNB in How to test your own sdk homebrew   
    Tools:
    HEN 1.8
    https://cdn.discordapp.com/attachments/159066660962041856/498138504656715776/ps4-hen-vtx.bin
    https://cdn.discordapp.com/attachments/159066660962041856/498138541570654209/index.html
     
    payload_ldr
    https://cdn.discordapp.com/attachments/159066660962041856/498062138686963712/payload_ldr_verbose.pkg
     
    FTP payload/OrbisMAN

    (Optional But Recommended) Mira for usermode logs / UART

    Step0:If needed for your homebrew, put ALL resources inside /data/ (specify the path in your homebrew as well)
    Step1: Create a folder called self inside data folder (You can use ftp or orbisman for this)
    Step2: Launch HEN 1.8
    Step3: If needed, launch mira aswell(for logging your homebrew/game while it's being tested)
    Step4: Install payload_ldr pkg
    Step5: Launch payload ldr (the screen should hang at start)
    Step6: Send the main eboot (it MUST be a self file)
     
    sender.py --endpoint 192.168.1.4 eboot.bin Other options are available but for now i'll only use this one
    Step7: Your homebrew should now run and (if you have it) logs should be displayed on putty/some other Telnet/Serial logger
  13. Like
    zecoxao got a reaction from ocam in How to test your own sdk homebrew   
    Tools:
    HEN 1.8
    https://cdn.discordapp.com/attachments/159066660962041856/498138504656715776/ps4-hen-vtx.bin
    https://cdn.discordapp.com/attachments/159066660962041856/498138541570654209/index.html
     
    payload_ldr
    https://cdn.discordapp.com/attachments/159066660962041856/498062138686963712/payload_ldr_verbose.pkg
     
    FTP payload/OrbisMAN

    (Optional But Recommended) Mira for usermode logs / UART

    Step0:If needed for your homebrew, put ALL resources inside /data/ (specify the path in your homebrew as well)
    Step1: Create a folder called self inside data folder (You can use ftp or orbisman for this)
    Step2: Launch HEN 1.8
    Step3: If needed, launch mira aswell(for logging your homebrew/game while it's being tested)
    Step4: Install payload_ldr pkg
    Step5: Launch payload ldr (the screen should hang at start)
    Step6: Send the main eboot (it MUST be a self file)
     
    sender.py --endpoint 192.168.1.4 eboot.bin Other options are available but for now i'll only use this one
    Step7: Your homebrew should now run and (if you have it) logs should be displayed on putty/some other Telnet/Serial logger
  14. Like
    zecoxao got a reaction from GregoryRasputin in How to test your own sdk homebrew   
    Tools:
    HEN 1.8
    https://cdn.discordapp.com/attachments/159066660962041856/498138504656715776/ps4-hen-vtx.bin
    https://cdn.discordapp.com/attachments/159066660962041856/498138541570654209/index.html
     
    payload_ldr
    https://cdn.discordapp.com/attachments/159066660962041856/498062138686963712/payload_ldr_verbose.pkg
     
    FTP payload/OrbisMAN

    (Optional But Recommended) Mira for usermode logs / UART

    Step0:If needed for your homebrew, put ALL resources inside /data/ (specify the path in your homebrew as well)
    Step1: Create a folder called self inside data folder (You can use ftp or orbisman for this)
    Step2: Launch HEN 1.8
    Step3: If needed, launch mira aswell(for logging your homebrew/game while it's being tested)
    Step4: Install payload_ldr pkg
    Step5: Launch payload ldr (the screen should hang at start)
    Step6: Send the main eboot (it MUST be a self file)
     
    sender.py --endpoint 192.168.1.4 eboot.bin Other options are available but for now i'll only use this one
    Step7: Your homebrew should now run and (if you have it) logs should be displayed on putty/some other Telnet/Serial logger
  15. Thanks
    zecoxao got a reaction from OldBrain in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  16. Like
    zecoxao got a reaction from ocam in [Release] LV1 and LV2 IDA databases by picard (4.46 rebug)   
    Since @3141card has  agreed to let these databases be released to the general public.
    Link: https://www.sendspace.com/file/5b9jw4
     
    Contains LV1 and LV2 memory dump databases with several comments, constructors, destructors, documented syscalls, etc.
    Extremely useful for emulation research and/or exploit research
  17. Like
    zecoxao got a reaction from ocam in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  18. Like
    zecoxao got a reaction from Milad in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  19. Like
    zecoxao got a reaction from DEFAULTDNB in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  20. Like
    zecoxao got a reaction from Bereuza in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  21. Like
    zecoxao got a reaction from Lightra1n in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  22. Like
    zecoxao got a reaction from Shiro in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  23. Like
    zecoxao got a reaction from ImMrNiato in How to Port games From a Newer version to an older one   
    First of all, credits to @Joonie, without him none of this would have been possible.
     
    Things required:
     
    2 PS4s (one in 5.05 preferably, another in the version you wish to port stuff to, like 4.55)
    SDK of the older version (don't ask for it, just search a bit)
    Hexeditor (such as HxD)
    Fpkg tools (specifically https://www.sendspace.com/file/bqsin5 )
    Game to port (Something like God of War or the likes)
    FTP Payload on 5.05
    Filezilla Client

    First thing we'll do is find how many modules our game has and which they are.
    So we start our game minimized, go to the ftp payload and start filezilla, then navigate to the pfsmnt folder and to the title id for patch.
    In the case of God of War, they're libc and libSceFios2.
    So we'll grab both of these from our SDK (in this case, 4.50 sdk) and place them in the sce_module folder, replacing the ones existing there (from 5.00 SDK).
    Last but not least we grab the eboot from the ftp and we replace the version binary string (search for ORBI, caps, it should be around this location)

    Example:
    https://imgur.com/a/4rZofbG
     
    https://imgur.com/a/isZaGw9
     
    And finally, after replacing those strings you can replace the eboot as well and place it under the fpkg creator.

    This has been tested by @Joonie and works for some games (cases like 5.05 on 4.55 work for the majority of it but cases like 5.05 on 4.05 don't for the majority so you're on your own to test these)
  24. Like
    zecoxao reacted to GregoryRasputin in [Released] Belf For PS4 v0.1   
    Would you stop trolling, you are posting off topic and asking stupid questions as well.
    There will never be a 5.50 Jailbreak, it isn't even the latest firmware, so stop asking, 5.05 has just been released and there is no way we will see another KExploit any time this year.
    The only person to blame for this problem is you, nobody forced you to keep updating and you had plenty of warnings to stay on 5.05.
  25. Like
    zecoxao reacted to GregoryRasputin in [Released] Belf For PS4 v0.1   
    Balika011 has released a PS4 ELF Loader for IDA Pro:

     
    Source/Download
    Thanks @zecoxao
×
×
  • Create New...