Search the Community

Hi Guys. Welcome to the PS4 Hacking/Modding scene and welcome to 2018. Today i will be showing you guys, how to run the PS4 4.05 exploit on any PS4 (brand new out of the box, or which was once activated and used) which is on firmware ,<= 4.05, and how to open the Advanced ★Debug Settings on the ps4 You will need a PC, a PS4 on firmware equal to 4.05 or lower, and a network connection. Now i have a video here showing how to achieve this below, but if you would rather read on how to do this, please scroll down further and i will write the instructions below. Please make sure to follow every step carefully. DISCLAIMER! Please be careful with debug settings as there are options in there which can brick your PS4 if you do not know what you are doing. Please steer clear of IDU mode as that will turn your PS4 into a kiosk. I highly recommend using an Ethernet cable to connect the PS4 to a Router and another Ethernet cable to connect the PC to the same router. I WILL NOT BE RESPONSIBLE IF YOU BRICK OR DAMAGE ANY OF YOUR HARDWARE. So please use care and if you don't know what something is, don't touch it Happy Modding. Video: WRITTEN Tutorial: Ok guys so first off you will want to download these files below as you will need every single one of them to fully follow this tutorial. Downloads ---➣ ps4-exploit-host - https://github.com/Al-Azif/ps4-exploit-host/releases ---➣ Advanced ★DEBUG Settings Payload - https://mega.nz/#!O5hiHRzK!jh6nKnFe_w5jXUnOz_fMwYueZkW1u7tfxZMfX86Q-YE ---➣ Python 3 - https://www.python.org/downloads/ If you need to update to 4.05, please select a link from below and download the 4.05 firmware. ---➣ Firmware Files (GBATemp) - https://gbatemp.net/threads/ps4-firmw... ---➣ Firmware Files (sce.party) - https://sce.party/?page=firmwares Right you have everything now? Good. Make sure you extract all the zip files into their own respected folders, inside a folder with all your ps4 hack files Next you will have to install python. Please follow on screen prompts and install it. Ok so now we have set up the environment we need to run the server on the PC. IF YOU NEED TO UPDATE YOU PS4 AND HAVE DOWNLOADED THE UPDATE FILES, THIS WILL BE THE TIME TO UPDATE. - to update you might need to go into recovery mode if your ps4 has already downloaded a later version of the firmware. - Make a folder on the root of your usb called 'PS4' and inside that make a new folder called 'UPDATE' if you have done so then you can past your 'PS4UPDATE.pup' into the update folder. - from here you will need to figure out how you are going to update, weather it will be from the home menu or recovery. make sure you check what version is showing up on the home menu prior to updating if you will be going that way. Now that you are on firmware 4.05 we can commence Jailbreaking and setting up the exploit. Start up the server - Please take the 'fullDebugSettings405' file you downloaded (or modified) and place it into the payloads folder in the 'ps4-exploit-host' folder - Open a CMD window as admin - cd into the directory where your 'ps4-exploit-host' folder is located - Once you are there you will need to type 'Start.py' and it will start the server - (if you get any errors you might need to make sure ports 80 and 53 are not in use by other applications - Then press 1 and hit enter - (if you get any errors you might need to make sure ports 80 and 53 are not in use by other applications - You should see a message telling you that the server is running and you might get a check box that comes up asking to allow python to access the network, tick both boxes and press 'Allow' - if all is still well and you have no errors, then we are ready to move to the PS4. (NOTE: you sould see your DNS ip displayed on the console) First, you will need to go to network settings on the PS4. You will need to make your settings as such: - IP - 192.168.1.6 (or you can leave it as whatever you want if you will be changing the IP in the payload file) - Subnet mask - 255.255.255.0 - Default gateway - (you need to find out what your routers ip is and put it in) - DNS (This will be displayed on the CMD prompt console when we run the server) - leave DNS 2 as - 0.0.0.0 Make sure to save the settings and do a network test - As long as the PS4 obtains an IP and has internet access then this is fine. PSN will fail. Now that is all set up, we will now launch the exploit. Please head over to the user manuals at the top of settings, open it and observe the CMD console. It should start displaying more information, and ask if you would like to inject the FTP payload (fullDebugSettings405.bin). - Press 1 and hit enter. to inject the payload. Once an Error Pops up on the screen, simply back out with Button, and go back to settings. Scroll down to the bottom and there should be ★Debug Settings. Profit? Hope this helped you guys. Please make sure to ask any questions you may have below and i will do my best to help you. Sooooooo..... If you're still reading this you might have got yourself stuck in IDU mode.... I told you not to do it, Anyways. Thanks to Al Azif for the Method to get out of IDU mode, and thanks to @dev-ps3 for the tip.

xai_plugin by mysis - Release 0.1 Happy New Year Everyone! Features: * XMB Icons for nice cfw tasks, nicely listed in network column * XMB-Actions without the need for webbrowser for each step * Simply select and its executed! * No Thread waiting for controller input! * No additional CPU time stolen! * BD Remarry without downgrading! * Enter Factory Service Mode up to latest Firmware without Dongle! =CFW-Settings= Clean Log File - Gives you the option to delete the Log-File Dump Disc Hash Key - This Option will write retrieve disc hash key from an ORIGINAL game disc and save it to log file This works without running the actual game! Log Klicense usage - Games that use klicense for accessing edat-files this option will save filename and klicensee to log file. Log Secure File ID usage - This will log save data name and file id key Enable In-Game Screenshot - This will only Enable for current system runtime. Override Disc SFO - Will apply SFO Attribute (0xA5) Remoteplay and SystemBGM to Disc Games. It will prolly not work with its Updates. Display applicable version - Tells you the minimum downgrade version of your system Dump IDPS - Prints your IDPS in cfw-settings.log Set dev_flash from USB - Jailcrab code for writing Lv2Kernel redirecting /dev_flash/ access to a mounted /dev_usb/ Remarry Bluray Drive - Remarries the bd drive to the System Re-Initialize VTRM-Region - Aka RSOD-Fix if VTRM not a hw problem Toggle DLNA - Turns DLNA Media Server On/Off, usefull for DEX Rebulid Database - Reboots with Database rebuilding flag set Check Filesystem - Reboots and allows you to check and repair filesystem Toggle Recovery Mode - Reboots into Recovery Mode Toggle Factory Service Mode - Reboots into Factory Service Mode without Dongle =REBUG-Settings= Toggle Cobra Mode - Enables or if active disables Cobra Mode Toggle Rebug Mode - Enables or if active disables Rebug Mode Toggle Debug Settings Menu - Switches between "CEX QA" and "DEX" Debug Settings Download latest Rebug Toolbox Install downloaded Rebug Toolbox =Note= * should not be fw dependant, tested on 4.46 and 4.7x and does not use hardcoded offset patches * requires peek+poke (sc6+7+8+9) for few options * Log File path: /dev_hdd0/tmp/cfw-settings.log (Note: in FSM its /dev_usb/cfw-settings.log + hidden + system file flagged) * if you are using another xai_plugin for ex. rebooting, it can lead to incompatibility to prevent that, change the actual module action in (probably) category_user.xml (?) to: "<Pair key="module_name"><String>xai_plugin</String></Pair>" "<Pair key="module_action"><String>soft_reboot_action</String></Pair>" // soft reboot or "<Pair key="module_name"><String>xai_plugin</String></Pair>" "<Pair key="module_action"><String>hard_reboot_action</String></Pair>" // hard reboot =Installation= copy "xai_plugin.sprx" AND "videorec.sprx" to "/dev_blind/vsh/module/" copy "xai_plugin.rco" to "/dev_blind/vsh/resource/" copy "category_network.xml", (cfw-settings added for CEX xmb) "category_network_tool2.xml" and (cfw-settings added for DEX xmb) "cfw_settings_en.xml" (contains cfw-settings and rebug-settings xmb-folders) to -> "/dev_blind/vsh/resource/explore/xmb/" =BD Remarry= 1) Toggle Factory Service Mode (should be easy now) 2) Put "eid_root_key" that belongs to the console to /dev_usb/ 3) Select Remarry Bluray Drive in Network->cfw-settings->Remarry Bluray Drive 4) If everything went fine it should have notified: "CEX_drive_init() succeeded" 5) Dont forget to repair CRL/DRL if you need to fix it Successfully remarried /dev_usb/cfw-settings.log should look like: 2011-12-31 19:00:24 [xai_plugin] : : _xai_plugin_prx_entry() 2011-12-31 19:00:24 [xai_plugin] : 1 : xai_plugin_init() 2011-12-31 19:00:24 [xai_plugin] : 1 : xai_plugin_start() 2011-12-31 19:00:24 [xai_plugin] : ACT0 : xai_plugin_action(remarry_bd) Looking for lv1 offset Found lv1 code @0xac574 EID2 P-Block decrypted EID2 S-Block decrypted sys_storage_open(bdvd) = 0 stg BDVD Auto Request Sense OFF success = 0 Identified Drive = SONY PS-SYSTEM 302R4154 ps3rom_lv2_mode_select(2) = 0 ps3rom_lv2_write_buffer(2,60) = 0 ps3rom_lv2_mode_select(3) = 0 ps3rom_lv2_write_buffer(3,670) = 0 ps3rom_lv2_mode_select(4) = 0 ps3rom_lv2_write_buffer(4,8000) = 0 CEX_drive_init() succeeded 2011-12-31 19:01:20 [xai_plugin] : ACT0 : xai_plugin_action(service_mode) Product Mode Disabled = Thanks = Sandungas - for the xml adding and rco Joonie Pics: Download: cfw-settings 0.1 rar