After few days later, USB exploits alway failed. No matter how many restart it took.
Original PS4 FW 9.00.
That's why I won't upgrade from my 6.72, software is always better
After few days later, USB exploits alway failed. No matter how many restart it took.
Original PS4 FW 9.00.
Wat a joke.. most stable one is now so far is 9.00.. plus no backport bla bla...That's why I won't upgrade from my 6.72, software is always better
Wat a joke.. most stable one is now so far is 9.00.. plus no backport bla bla...
Thanks for the answer , I probably forgot to clear the cache browserI just re-cached to test and its fine. Trainers Updated 12-Jan-2022
View attachment 293592
New sleirsgoevy exploit released yesterday for 6.72 makes the the ps4 in my opinion as stable as 5.05, for me is cherry of the cake, I and another user kindly requested sleirsgoevy for a possible update, since his last exploit had absolutely no exploit failure, but had some instability issues after the exploit, and he was so kind into look into the exploit and update it, now the issues after the kernel exploit are gone, and 6.72 is perfect now.Wat a joke.. most stable one is now so far is 9.00.. plus no backport bla bla...
I haven't had the chance to try it out yet I'll have a look later and speak to leeful to see what he thinks about it also
Same here, I was testing it a lot last nght and did not find any problems.I have no problems with new exploit, works wonders, for 6.72 which all payloads load on the fly you don't need golden2b2, also golden 1.1 fixed the cmos issue.
Sleirsgoevy did it, 6.72 is the new 5.05 in what concerns stability, it is my belief this exploit would had come sooner for 6.72, if Sleirsgoevy had more free time and willingness back then when he was developing for 7.xx exploits, ofc new exploits takes a lot of efforts and thinking of strategies to make the exploit run flawlessly, after his long experience on 7.xx exploits, he gained so much knowledge on the ps4 architecture to make 6.72 what is now, he doesn't even have a 6.72 console to try this new code, if memory serves me well 5.05 also took two years to become and it is now, 13th January is the milestone for 6.72, a perfect exploit .Same here, I was testing it a lot last nght and did not find any problems.
Just curious about the pull request for the dlsym patch in the krop.
I totally agree but that doesnt answer the question about the pull request for the dlsym patch.Sleirsgoevy did it, 6.72 is the new 5.05 in what concerns stability, it is my belief this exploit would had come sooner for 6.72, if Sleirsgoevy had more free time and willingness back then when he was developing for 7.xx exploits, ofc new exploits takes a lot of efforts and thinking of strategies to make the exploit run flawlessly, after his long experience on 7.xx exploits, he gained so much knowledge on the ps4 architecture to make 6.72 what is now, he doesn't even have a 6.72 console to try this new code, if memory serves me well 5.05 also took two years to become and it is now, 13th January is the milestone for 6.72, a perfect exploit .
Being using it on 6.72 pro since it’s release and won’t use another one.. amazingly stable for meI've been using this host for over a week now and more than 20 jailbreaks and 40 rest modes and not a single kernel panic
I'm getting worried,what kind of dark magic is this?!
Sleirsgoevy did it, 6.72 is the new 5.05 in what concerns stability, it is my belief this exploit would had come sooner for 6.72, if Sleirsgoevy had more free time and willingness back then when he was developing for 7.xx exploits, ofc new exploits takes a lot of efforts and thinking of strategies to make the exploit run flawlessly, after his long experience on 7.xx exploits, he gained so much knowledge on the ps4 architecture to make 6.72 what is now, he doesn't even have a 6.72 console to try this new code, if memory serves me well 5.05 also took two years to become and it is now, 13th January is the milestone for 6.72, a perfect exploit .
Hey man could you please make an esp file of this host as well please?I totally agree but that doesnt answer the question about the pull request for the dlsym patch.
Is the current patch correct in sleirsgoevy's code or does it need updating as zerofo suggests in this pull request.