MSZ-MGS
commented
3 years ago Further notes:
When we utilized Alert to pause the code, below test results revealed for first 10 consecutive tests:
1- KP 2- KP 3- S 4- S 5- S 6- S 7- S 8- S 9- KP 10- KP
S: Success KP: Kernel Panic
If you notice, that the end results always Kernel Panic or Success, no freeze happened. JB failed message happened but rearly.
When we tried to automate the pause with setTimeout function, we started getting system freeze frequently as shown below:
1- JF 2- FR 3- S 4- FR 5- S 6- S 7- S 8- FR 9- S 10- KP
FR: Freeze S: Success JF: Jailbreak Failed Message
But still the success rate is better than without the 2m pause
This is for your kind consideration
Thank you for making PS4 scene great!
I have introduced (alert) function to the JB file to test specific things. The test involved recording things manually from the screen to my note, so the JB execution was paused every time I conduct a test. However, I have noticed that all JB executions went successfully! I redid the test for 11 times on my Pro with pausing from 1 - 2 minutes each and found 9 of them went successfully compared by 20 – 30% success rates with the same JB release but without the pause.
I posted this info to the followers to verify if that is a placebo. According to at least 10 reports received from followers, below pause introduced to the JB code has improved the success rate of the JB 7.5X up to 75% across all variants.
Alert function added to pause the execution of the JB, the pause shall be 2 minutes (I tested one and jumped to 2 minutes, I didn’t test in between)
Please verify this finding.
Below is your JB coding in addition to the added alert function (you may replace the alert with a timer for convenient).
var ropchain_array = new Uint32Array(498282); var ropchain = read_ptr_at(addrof(ropchain_array)+0x10);
alert ("Please Wait 2m ... @MSZ_MGS");
var ropchain_offset = 2; function set_gadget(val) { ropchain_array[ropchain_offset++] = val | 0; ropchain_array[ropchain_offset++] = (val / 4294967296) | 0; }