PS4 PRO CUH72**** UNABLE TO SHUTDOWN AND USE REST MODE. ANY SUGGESTION?

[darthtrader6502]

PS4 PRO CUH72**** ON 11.00. SUCCESSFULLY JAILBREAK LIKE OTHERS BUT UNABLE TO SHUTDOWN AND USE REST MODE. ANY SUGGESTION? THANKS GUYS.

[harsha-0110]

It's because the pppwn is not stable, due to which there will kernel panic during entering restmode or while shutting down even though jb is successful. There is not much could be done untill the exploit gets stable enough and you can try adjusting pppwn settings to improve your success rate.

[darthtrader6502]

It's because the pppwn is not stable, due to which there will kernel panic during entering restmode or while shutting down even though jb is successful. There is not much could be done untill the exploit gets stable enough and you can try adjusting pppwn settings to improve your success rate.

update:- jailbreak using laptop pppwn lite 5.2....works just fine...can shutdown normally and use rest mode....but i need to use the luckfox...i am using luckfox mini b...any ideas guys....something missing here...

[darthtrader6502]

thanks mate...i ll give it a try now...later will update any progress Yahoo Mail: Search, Organize, Conquer On Sun, Aug 11, 2024 at 5:23 AM, ***@***.***> wrote: It's because the pppwn is not stable, due to which there will kernel panic during entering restmode or while shutting down even though jb is successful. There is not much could be done untill the exploit gets stable enough and you can try adjusting pppwn settings to improve your success rate. update:- jailbreak using pppwn lite 5.2....works just fine...can shutdown normally and use rest mode....but i need to use the luckfox...i am using luckfox mini b...any ideas guys....something missing here... You can replace the stage 2 file of luckfox with pppwn lite 5.2 stage 2 file just log in to your luckfox using mobaxterm and replace the stage 2 file... i tried it and it worked perfectly it even pop out pppwned instead of luckfoxed after successfull jailbreak... 😄 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[0x1iii1ii]

did you try the latest v1.2.2 is it fixed? please report back if possible.