Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
Status
Not open for further replies.
While there is no ETA on future PS4 jailbreak exploits yet and current jailbroken PS4 5.05 consoles can run homebrew and play hundreds of PS4 Fake PKG games, those stuck on PS4 4.74 OFW due to a missing or broken Blu-ray drive (aka PS4 NoBD) can now directly update to PS4 5.05 OFW to enjoy all the fun of a 5.05 PS4 jailbroken console following the previously released PS4Brew 4.74 Kernel Exploit! 💽 📀

:idea: Those stuck on 4.55 / 5.03 / 5.05+ (including 5.5x) / 6.xx (including 6.20 and 6.72) and 7.xx (including 7.0x and 7.5x) are also now supported via @LightningMods with the PS4 NoBD Updater PKG, PS4 NoBD Payloads and PS4 NoBD Toolkit in the update below.

:alert: As a precaution, PS4 scene developers strongly advise those who attempt this PS4 BD Driveless Updating 4.74 (No BD) to 5.05 Patch Updater method to backup your HDD as soon as you're on 5.05 Firmware. :alert:

From Logic-Sunrise.com, to quote roughly translated: [PS4] A solution to update from 4.74 to 5.05 with the HS reader!

The developer @zecoxao informs us that a solution has just come out for those who were stuck in firmware 4.74 following a bluray drive out of order.

A direct update solution to version 5.05 is now available.

To update the console on the firmware 5.05, just run the HEN on the firmware 4.74, inject the payload jkpatchsyscall9.bin, install the package 505.pkg, then install the firmware 5.05 from a USB device connected to the console.

For the moment, no brick is raised, but hey you take the risk of experiencing this kind of problem.

To sum up:
  • Remove any PUP from the / update / directory of your USB key
  • Download the magic_update.7z (11.52 MB) payload jkpatchsyscall9.bin and the 505.pkg or here (Mirror)
  • Put the PS4UPDATE.PUP on the usb0 (the PUP of 5.05)
  • Install the PKG and restart
  • Install syscall9 with payload
  • Launch the HEN after sending it (zecoxao.github.io)
  • Launch the upgrade from firmware 4.74 to 5.05
Before you start, make sure you have all the elements, and understand the approach!

All this has been tested on PlayStation 4 1000/1100 series consoles, but it should work on PlayStation 4 Pro, in fact the payload allows to launch on a console at HS bluray the update.

Zecoaxo recognizes that the most unstable part is the HEN that can crash when launching an application.

Everything is there: discordapp.com

Thanks to the devs who helped in this advance!
Spoiler: Related Tweets

PS4 No BD 4.74 to 5.05 Update via tiago92ba

PS4 NoBD Updater for 6.20 FW

:alert: Warning: Based on Twitter replies and YouTube comments the NoBD 6.20 PS4 Updater is currently in a TEST phase only, as always what you do with your PS4 is your responsibility so proceed with the spoiler AT YOUR OWN RISK! :alert:

Spoiler: Related Tweets, Demo Video & Files

:arrow: Update: PS4 NoBD Updater PKG & Payloads released via @LightningMods for those with no Blu-ray drive, currently supporting the following PlayStation 4 Firmware versions:
  • 4.55
  • 5.03
  • 5.05+ (including 5.5x)
  • 6.xx (including 6.20 and 6.72)
  • 7.xx (including 7.0x and 7.5x)
Spoiler: Related Tweets & Payloads / PKG Files

PS4 Blu-ray Optical Drive Chip Swap Re-marry by NorthRidgeFix.com

If you have a PS4 console with dead drive and you stuck in lower firmware and want to update, here you go:

1 - Find a working drive daughterboard from any phat 1000, 1100 or pro dead console for example, and with FW lower than your current one.

Continue...
2 - Desolder Renesas chip from it and keep it.

3 - Desolder your dead drive Renesas chip from drive’s daughter board.

4 - Solder the working Renesas chip on place of your original one.

Continue...
5 - Install drive daughter board and install the drive to your console and update it either from dashboard or recovery.

6 - console should be updated now without any issue.

7 - if you want to re-update it again you should repeat this steps.
This is the complete method and will do another one for slim and new models when we finish it 😉
A small correction here is donor chip should comes from SAC-001 board, and it is better if you could find one with Renesas chip that made in Japan.
Because this chip have a special bootloader that help in this trick.
PS4 BD Driveless Updating 4.74 (No BD) to 5.05 Patch Updater Method.jpg
 

Comments

my friends now, for example my harddisk format or damage after update 4.74 to 5.05 no bd ok the system will remain at 5.05

How will the system be loaded 5.05 without bd after damge or format hard drive??
 
Hopefully the no Bd payload for 4.74 will be ported for 5.05 for us without working drives. Would be nice to know I could install 5.05 recovery firmware again if something happens.

Anyone tried reinstalling 5.05 again on a 4.74-5.05 console?
 
I don't know what went wrong but i think i bricked it. The case says it's a CUH-1114 but i don't know what board is inside , might as well be CUH-1214. Now that i read the tutorial again, only thing i did different was first enabling HEN, then injecting the payload.

It started to do the update directly , without asking now or later. A popup appeared that the firmware is patched for NO-BD , like in the video. Finished the update , restarted but the light bar on the console remained white.

I turned it off and on again and now the light is flashing blue. The controller seems to sync but it will not output image or enter recovery mode. RIP ?
 
Hey ... i'm following this tutorial and after running Update to 5.05 from the dashboard like i run my games i'm just looking at a HB blue screen and thats it ... wont do anything else.

My drive board is fried so i got no cables running anywhere ... USB and PUP files are all correct and with correct names ...
 
The instructions are a bit unclear. I think you need to put PS4UPDATE.PUP straight to the root of the stick but unfortunately I bricked mine. Maybe some day there will be a way to remarry or an no-bd cfw.

I suggest you stick to 4.74. You can enable Hen from zecoxao.github.io (the first try will show an INSUFFICENT MEMORY error , launch again , it will hang at loading and will not confirm in the upper left corner , but if you exit with the PS button Hen will be activated)
 
First ever posting here. But i have to say thanks so much to all who were involved with this GREAT project. Worked like a charm. Thanks again so much.
 
@saski @tusk99, unfortunately if you use this method to update from 4.74 to 5.05 and your harddrive goes bad, you won't be able to install 5.05 to a new harddrive until your fix the BluRay issue you have. This is one huge flaw or risk when performing the update to 5.05.

Better off staying on 4.74 if you don't repair the BluRay problem. At least that way, you can always reinstall the firmware if something goes wrong.
 
@xanadu247
I know the risks its worth getting off 4.74
The payloads for 4.74 are so unstable
That's half the issue with the update to 5.05
I have done 2 updates 4.74-5.05 no problems
I have multiple 5.05 ps4 that are not bad bd drive fix so im not worried
 
@arcadekidflo
I think my update has gone the same way as yours, may well be bricked too :(

Followed the video and steps provided, with the exception of using Al Azif's local host instead for HEN and payload injector cause they've been a bit more stable for me. I also injected on PC with Netcat GUI instead of android.

I didn't get the "update later" prompt when I launched 505.pkg from the home menu, it installed and went to reboot but no image displayed and solid white light on top. Left it for a few minutes, it restarted by itself and now has flashing blue like yours.

Disc drive spins up as in normal boot by still no image. My BR drive's data cable was disconnected previously so I could update from 4.07->4.74, but power is still connected. I wonder if that disconnected data cable had anything to do with it?

@tusk99
For the PS4's you successfully updated, were the BR Drives still attached? or removed completely? Not sure if there's anything can be done, but I'm curious whats causing it.

Edit: On that note, I just plugged the BR drive's data cable back in and it booted up fine! Currently running 5.05 on a mismatched board!

Thanks all for the hard work, top stuff.
 
Status
Not open for further replies.
Back
Top