1. bbqtool

    OP bbqtool Advanced Member

    Aug 21, 2018
    If you are new to PS4 jailbreaking, it is very confusing as to what works and what doesn't. 6.72 is extremely stable for me right now. I have seen a lot of people claim otherwise and I would recommend they try this before updating to 7.xx if they want to try to improve on things and they don't mind spending some money. I've posted about this a few times in advice threads already, but I thought it warranted a tutorial just so it is documented for new users. (If you've been doing this for a while, you might see this as reinventing the wheel a bit.) The bottom line is I don't get kernel panics anymore on 6.72 after I found a method which works for me and never had it crash after successfully enabling the JB. The worst that can happen is "the jailbreak has failed" error (I've had it happen twice and I use my PS4 a LOT) and I just reset the PS4 after that and try again.

    This is what I am using:

    - A wifi powerboard: https://www.amazon.com/Kasa-Smart-Power-Strip-TP-Link/dp/B07G95FFN3

    - An ESP8266 4MB

    - A self host bin file:
    *PS-Phive: https://gbatemp.net/threads/release-ps-phive-forps4-6-72-exploit-host-menu.579557/
    Darkmodder: https://gbatemp.net/threads/darkmodders-6-72-jailbreak-esp8266.585563/#post-9416173/
    Leeful's 6.72 Exploit Menu: https://gbatemp.net/threads/esp8266-bins-for-fw-6-72.578045/#post-9285149


    - Google Home/Alexa

    - My phone

    This is what I'm doing:

    1. USB port 1, empty. USB port 2 has a 5 port USB hub with a USB stick that has Linux connected to it with another USB drive which has pkg files and roms on it (I don't run PS4 games from a USB drive, I just install them straight to the PS4) and a wireless dongle which I use for a keyboard sometimes.

    2. I have my PS4 connected to a wifi powerboard which I use with Google Home and has a few other things plugged into it which I power on/off with voice activation. This is optional but it saves me from going behind the TV and unplugging my PS4 and plugging it back in again when it was KPing all the time.

    3. I don't use the browser at all and my cache/cookies are clear from the get go. Reducing unnecessary use of the PS4's memory reduces KPs. I installed my JB menu to my user guide with an ESP8266 so I don't need to recache the browser after x amount of uses til the browser cache makes things unstable. You can get them on aliexpress for less than $10 shipped (I checked on there today and there were people selling them for $1US without shipping) and you may only need to use it once, but you can reflash new menus when new, improved ones come out. I 3D printed a case for mine. This is why I would recommend self-hosting via the user guide with a newer menu. It is a cheap, easy and effective way to install whichever exploit menu you want to the user guide. There are .bin files on this board and Modded_Warfare has a guide to set it up this way:

    I currently use darkmodder's menu for 6.72 because the Linux payload works everytime but you can use PS-Phive just the same. I'm also using Al-Azif's DNS and update blocker so I can use it for online stuff.

    To use the JB:

    1. Open the user guide and run it as per usual. (I run the exploit first then enable HEN seperately)

    2. Always shut the PS4 down properly through the menu.

    3. With Google Home, I tell my wifi powerboard to unplug the PS4 and plug it back in after every time I do a full shut down (The powerboard has an app as well to do this from your phone if you don't want to use any voice recognition stuff) from either Orbis or Linux. This is important. For Linux users, to avoid the KP after booting back into Orbis you need to shutdown Linux via the menu, then power off the console completely. It needs to be unplugged. You can then power the PS4 back on and boot into Orbis.

    Here's a demonstration:

    Since using this method, I have not had a KP once and I use my PS4 almost every day. When I first started, they would happen all the time. Until a better method is created, I am very happy with this setup. If I make changes to my setup that refines it, I will edit this post but right now it works exactly how I want it to.

    Shout out to Prb for making the bin files for these exploit menus.
    Last edited by bbqtool, Jun 7, 2021 at 6:45 PM
    pcwizard7, ca032769, Alsusee and 2 others like this.
  2. bbqtool

    OP bbqtool Advanced Member

    Aug 21, 2018
    As an added extra, I recorded myself booting into Linux 5 times in a row, back to back unedited to test for errors/issues I would get just booting into Linux. 5 out of 5 successful attempts. It also shows you my method of booting into Linux the best way I can with minimal problems.

    Some things to remember:

    - The PS4, Linux and the jailbreak all share the same memory. That means if you aren't shutting Linux down through shutdown in Fedora, eventually the JB will start failing and it will even KP if you get the jailbreak to work when you try to run the Linux payload. You can remedy this when the PS4 has to rebuild the database and just following the method that works for you. (Hopefully this one) The process is more important than the hardware. I don't have any issues when I follow the process I have written up here.

    - The combination of the PS4's video card, your TV and the drivers that come with Linux aren't a perfect combination. Not by a long shot. An example of this is if you have your PS4 Pro set at a resolution higher than 1080p when you boot into Linux, it doesn't like that. Another thing which breaks Fedora is if you turn the television off with Linux open. You lose the display completely and you need to unplug/plug in the PS4 and reboot to return to Orbis. Do this enough times and you'll have issues.

    - A PS4 Linux setup is limited by the console hardware. It sounds obvious, but just remember that the PS4 is not a PC. There are certain functions of Linux that will not work with the PS4. Testing and refining your setup, even running the jailbreak itself will change when there are new options available. Between now and then, when you refine things make an .img file of your USB storage. If you make something work better, make a new .img file as a restore point. Reinstalling and reconfiguring Linux is an absolute pain and it is why I don't encourage users to use it from the PS4's internal HDD. If you do break things, just reflash the drive and there is no real loss.

    - This is how I have set up my PS4 to work how I want it to. Any tutorial I post are just ideas which can lead you closer to having your setup suit you as best as possible. I wrote these up for people who, like me, had a lot of questions and needed to find the answers myself as the things I write about aren't documented. (At least in English) It was fun but would be pretty difficult for people who might be intimidated by it all. I feel like my setup right now is pretty extreme compared to when I first started. (Which was just a PS4 on 6.72 plugged into my TV with a jailbreak menu cached in the browser) I also think any huge changes will be fairly superficial. I've spent a lot of time thinking and configuring things in Linux and in Orbis and money on other hardware for it to work. Maybe a CFW and a firmware downgrader will be released tomorrow? Who knows. This will do me well before then.

    - Linux is free to use, but costly of time. Setting it up is so tedious. Now that mine works, hey no problem. It's great. I enjoy playing with stuff like this to a point. I believe the tediousness and most people using PCs are why Linux is so underutilised on PS4. I think I have spent more time getting my setup to where it is than playing PS4 games! At the end of the day, it really is an OK computer running Linux. Still, for what it is I think it serves a purpose for me and I would encourage other users to dig deeper with it.

    Again, shoutout to ITmania for all the time invested in PS4 Linux.
    Last edited by bbqtool, Jun 7, 2021 at 6:52 PM
    phonemonkey and ca032769 like this.
  3. spotanjo3

    spotanjo3 GBAtemp Legend

    Nov 6, 2002
    Great for ESP8266 users and useless guide for us who don't have an ESP8266. Therefore, I am staying with 5.05 for now with backports anyway. :)
    bbqtool likes this.
Draft saved Draft deleted

Hide similar threads Similar threads with keywords - [GUIDE], Kernel, Panic