Yeah, I'm in the middle of re-writing and testing them right now.
Thats a quick and easy one to do. /files/img/BG.jpg
wait, so db backup and restore does not work on v9b? and only on v10?
Okay, I can confirm that it does not work on v9b. I lost all my games.
I used backup on v9b and restore just crashes my PS4 and rebuilds DB again.
I try to restore from v10 but the backup files from my v9b is not compatible and can't find the backup files.
restore_db from python dosen't work for some reason and gives no response when i type in command after FTP. Could you help me Leeful. Or make a v9b with restore working again
Okay, I can confirm that it does not work on v9b. I lost all my games.
I used backup on v9b and restore just crashes my PS4 and rebuilds DB again.
I try to restore from v10 but the backup files from my v9b is not compatible and can't find the backup files.
restore_db from python dosen't work for some reason and gives no response when i type in command after FTP. Could you help me Leeful. Or make a v9b with restore working again
Last edited by HommyB,
^^ while we dont have the HDD Upgrade payload made by Leeful, you have to use the own ps4 backup tool and restore savegames by the same way. But if you kept the data, you can perform the operation by hand on ftp. I did it some times and worked. But of course you have to control the user ID activate it, and blablabla...
Wow, great news !! - don't be hurry and take it easy, I know is a hard work to test itYeah, I'm in the middle of re-writing and testing them right now.
Last edited by mameluko,
Do not use the python script. It does restore most of your games to the home screen but it also messes up a lot of things as well.
Do this to make the v9b backup files work with the Database Restore in v10:
On your USB drive rename the DB_Backup folder to Database_Backup and then run the Database Restore payload in v10.
The problem with the restore payload in v9b (and everyone else exploit menus out there) is that it is from the 6.72 port that Al Azif did when 6.72 first came out and it does not work correctly.
The problem with it is that in the code, after it has restored the db's it tells the PS4 to reboot and doing this makes the PS4 rebuild the database again when it reboots.
I fixed it by telling the PS4 to shutdown insted, this solves the problem.
In my next menu I will rewrite the payload to be compatable with the older backups as well so that people do not have problems anymore.
I didn't realize the python script had issues aside from not remembering folders, which is understandable why it can't do that. I just backup mine manually or with the db+sg payload. I don't know what's changed with a firmware update, but I do remember my app.db on the vita changing size (somehow came out smaller) when updating to 3.65 enso. downgrading may have affected the size as well, but it's no longer the size it originally was regardless.
yeah, there are a few problems with it:
It does not restore some homebrew titles.
After you have played one of the games you cannot delete it anymore. (without manually editing 'can_remove' in the app.db)
If you try and backup your profile the filesize is all wrong even when you uncheck all the games.
for example if you had 1TB of games installed the profile backup would be 1TB even when you deselect the apps from the profile backup, when it should only be about 150MB in size.
opps I already used the python script... Could you tell me more specifically what that script messes up?Do not use the python script. It does restore most of your games to the home screen but it also messes up a lot of things as well.
Do this to make the v9b backup files work with the Database Restore in v10:
On your USB drive rename the DB_Backup folder to Database_Backup and then run the Database Restore payload in v10.
The problem with the restore payload in v9b (and everyone else exploit menus out there) is that it is from the 6.72 port that Al Azif did when 6.72 first came out and it does not work correctly.
The problem with it is that in the code, after it has restored the db's it tells the PS4 to reboot and doing this makes the PS4 rebuild the database again when it reboots.
I fixed it by telling the PS4 to shutdown insted, this solves the problem.
In my next menu I will rewrite the payload to be compatable with the older backups as well so that people do not have problems anymore.
Thanks a lot @Leeful for your hard work.., being using V10 for a few days with AutoLoad HEN 2.1.3b, on ps4 pro CUH-7216B (Fw 6.72, Acitvated profile offline), did a lot of « stuff », and so far, everything works very well , No KP ( I did have with V9b and V6mod ).
And being very new to PS4 hacking...I found it very easy with your Menus... Keep going this way
And being very new to PS4 hacking...I found it very easy with your Menus... Keep going this way
Hi leeful I'm the guy that's been converting your exploits to bin files over at darksoftware I joined psxhacks was and trying to ask you a couple of questions but for some reason the mod over there ban my account any chance of dropping me a dm when its convenient thanksThis is not a fault.
The version that the PS4 is spoofed to is calculated and displayed at the bottom of the menu.
The FW version it shows in system settings only changes when the system is initially booted or resumed from rest mode so it will not change when you just run the payload. It was also like this on 5.05.
Similar threads
