Update README with autoloader troubleshooting steps #10
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-itsPLK/ps5-y2jb-autoloader!10
Loading…
Reference in a new issue
No description provided.
Delete branch "patch-1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Added instructions for fixing console crashes caused by incorrect .elf files in the autoloader.
Sorry for the late response, I just noticed this after a month lol.
I'll pass on this PR though. By default, the autoloader starts Payload Manager anyway, which doesn't require manual config. If a user decides to go the manual autoload.txt route, they should be expected to figure out how to use the USB override (which is already documented under manual config priorities) to fix their setup.
I want to keep the README simple and focused on core features rather than troubleshooting manual configuration errors. Thanks anyway!
I created this account just to tell you. Your insistence on defaulting to payload manager is as dumb as the idea that my PS5 will be bricked in a targeted attack. your v0.9 update broke payload manager on 12.70 and it took me a lot of wasted time to find your blink and ya miss it mention of not allowing remote payloads by default. I've had to restore a backup to undo the update. Lost nearly 1tb restoring from backup. You're reinventing the wheel and you've created a square. If I could have simply push an elf to the console I could have been well on my way to fixing things. screw you. your not Snowden and neither am I, I'll take my chances on a determined attacker infiltrating my network and bricking my PS5, gosh do you know how stupid that sounds? Surely they'd use the access provided by a comped machine to do literally anything more valuable then damaging a games console. Let me worry about open socks on my network, thanks for a wasted night genius.
oh And before you tell me to just manually config to allow it. I would have had I known. I spent so long thinking I messed up some config or network setting, never even thought some wise guy would just disable remote payloads because of some (and I really cant stress this enough) dumb, overblown fear of remote infiltrators targeting peoples playstation. again, from the bottom of my heart, screw you.
@screw-your-proprietary
You had plenty of ways to fix this before doing a backup restore.
First off, read the README. Everything is in there. If reading is too hard, you could've just pasted the repo link into ChatGPT and it would've given you the answer.
Payload manager isn't forced on anyone, it's literally just the default fallback if it doesn't find your config (which is also mentioned in the README). Nobody else is having issues with payload manager on 12.70 either.
Next time just read for 2 minutes before wasting your own night.
@screw-your-proprietary
You are just so stupid and dumb that you had plenty of ways to fix your shitty console but your single cell brain couldn't think more than just creating a stupid account to insult this man who has been doing a great job .. screw you too
Pull request closed