[pre-release] v0.9-dev-ae5f2d0

This is a thread for discussion about v0.9-dev-ae5f2d0.

[adamj871]

Hi, thanks for new version autoloader. Out of 3 attempts to run it, I got the exploit failed message twice (the first time the console restarted - along with subsequent data reconstruction, and the second time the autoloader closed itself and I restarted the console). The third time the loader launched successfully.

[YatoHMK]

can u add the search for autoload.txt from inside youtube's download0.dat and bd disc

Unfortunately not. Payloads are now loaded after YT app is closed, so we can't easily access download0 content to load elfs from there.

[adamj871]

I replaced the download.dat file and updated y2jb.update. I don't have a BD drive. I have PS5 Pro FW 10.01

On internal drive additionally i have folder /data/ps5_autoloader (it contains autoload.txt, etahen.elf and shadowmountplus.elf)

Greetings,
Adam
y2jb_update.zip

P.S. czy jesteś z Polski?

[YatoHMK]

ty, its understandable. is there an alternative path that can survive the backup restore

@YatoHMK , technically the autoloader ELF could be modified to load your payloads instead of Payload Manager when autoload.txt isn't found on /data or USB, but that's not something I'd recommend doing. Compiling/packaging payloads directly into the ELF is not a user-friendly process, and the idea is to avoid setting up default payloads that can quickly become outdated and can't be easily modified.
Plus, the old way of loading from autoload.txt wasn't very reliable anyway. Losing the option to put the autoload config in YT's cache directory is a small trade-off for having a fully stable way to load ELFs from /data or USB.

@adamj871 ,

P.S. czy jesteś z Polski?

Tak

[kratelos-fr]

Hi,

Thanks for the update and all the work on this project.

On my side, when the autoloader execution finishes, I'm unable to use Netcat to send payloads from my PC. None of the payload tools seem to work afterward. I had the same issue with v0.8 as well.

The only method that works reliably for me is using PLMR.

Has anyone else experienced this behavior, or is there a specific setup required to make Netcat/payload loaders work after the autoloader finishes?

Thanks.

That's intended behavior - by default elfldr isn't exposed anymore to other devices on the network.
You can load "normal" elfldr though - readme describes how to do this: https://github.com/itsPLK/ps5-y2jb-autoloader#additional-info

[kratelos-fr]

Thanks for the explanation.
I already placed a custom elfldr.elf in the ps5_autoloader folder and configured my autoload.txt to load only that file. However, I still cannot send payloads from my PC using Netcat once the autoloader has finished.
I also tried adding a delay after loading elfldr.elf, but the result is the same. Netcat and other payload sender tools cannot connect, while PLMR continues to work normally.
Is there a specific version of elfldr.elf that should be used, or is there another requirement to make remote payload loading work correctly?
Thanks.

Just tested using the original elfldr in autoload.txt and it definitely works, can send payloads over the network to it.
It doesn't matter what version of elfldr you'll use there - it will always stop the previously running elfldr and start the one you are loading.

[kratelos-fr]

I tried adding the original elfldr.elf file to the autoloader, and that was indeed the solution. Everything is now working perfectly: the jailbreak loads automatically at boot, remote payload loading works again, and all the payloads I manually added are loading correctly as well.

Thank you for all the work and development effort put into this project.

Just as an additional note, I'm using a PS5 Fat running firmware 12.40.

[boydreamxx-cyber]

I have an update 7.00 is it good for me? Or what is the best thing