Getting "Slice Bounds out of Range"

[gspb2]

Hi! First of all, thanks for this great software! I'm trying Jailbreak with many applications and this is the one that is going faster than the others for me. So, I have a PS4 model CUH-1004A running on FW 11.00. And after a few Kernel Panics (i guess becouse PPPwn is somewhat instable with some consoles), i'm getting this error message "panic: runtime error: Slice Bounds out of Range [:9] with capacity 6". I dunno if this is an error on my part, of the instability of PPPwn or the PPPwn_go, but i'm reporting just in case. Thanks a lot!

[wetor]

I've noticed this before, and I think it's one of the things that triggered the power outage (or did you not?). I'll fix him, and then I want you to run the test again

[gspb2]

Yes, i think so. I'm having many power outages. Many thanks!

[wetor]

This is the new version: https://github.com/wetor/PPPwn_go/releases/tag/v0.1.2

You can try using this version and use --debug and --log="log.log" If there is an error or it stops at a certain stage, you can send the log file and I will try to analyze it when I have time

Please try to execute it multiple times

[gspb2]

Hi! Unfortunately I had no success yet, but i tried a lot and I have many logs to share to, who knows, help with the solution. For context, I have access to 2 Laptops, 1 running win10 (labeled PC1) and another running win11 (labeled PC2). Also in both I tried running the exploit in PS4 Startup and on Network Menu > Test Internet Connection. And in some tests I'm having Power outages, on others is stucking just after "Defeating KASLR". All these scenarios are labeled in the log files. I noted that I'm having less power outages when I run the exploit on startup.

PC1 - Network Menu - Power Outage.log PC1 - Network Menu - Stuck Defeating KASLR.log PC1 - On Startup - Stuck Defeating KASLR.log PC2 - Network Menu - Power Outage.log PC2 - Network Menu - Stuck Defeating KASLR.log PC2 - On Startup - Power Outage.log

If more info are nedded, i'm pleased to help. Many thanks!

[wetor]

Sorry, I may not be able to help you

This issue may be related to the machine itself, and I have also noticed that many people encounter similar situations when using other tools. May need to wait for some professionals to repair it

If possible, I hope you can try modifying the code of pppwn and make multiple attempts, although it may not be useful https://github.com/TheOfficialFloW/PPPwn/blob/master/pppwn.py#L714 edit

        for i in reversed(range(self.SPRAY_NUM)):

to

        for i in reversed(range(self.SPRAY_NUM - 0x100)):

[gspb2]

I tried and doesn't work, but thanks for your time and patience. I will wait for the original devs to check it out.