@Leeful and @Prb , thanks a lot for this great menu ( that i was using on 6.72) and was waiting this port for 9.00.
Using esp32-S2 V2, no issues so far, was using @kameleon_ esp32-S2 host before, (a great esp32-s2 host).
Speed of webkit is amazing 2 sec for me, the kernel exploit is more or less as fast as @kameleon_ , but kameleon is auto-host, and full automated, so different concept.
Guess everybody have to choose what fit their needs.
Your choice of having the menu cached is great I think, but probably the most important feature is to be able to choose which GH version to load .
Using esp32-S2 V2, no issues so far, was using @kameleon_ esp32-S2 host before, (a great esp32-s2 host).
Speed of webkit is amazing 2 sec for me, the kernel exploit is more or less as fast as @kameleon_ , but kameleon is auto-host, and full automated, so different concept.
Guess everybody have to choose what fit their needs.
Your choice of having the menu cached is great I think, but probably the most important feature is to be able to choose which GH version to load .
It is incredible how fast the hack is working with this PS-Phive menu...
So @Leeful is now working with the v3 so the people wouldn't have to click on the usb message for the people with ESP32-S2...
If you have an ESP32-S2 board you can configure the timing after USB is mounted and before the hack is applied with the below Auto USB wait option:
My question is, are you going to use this option to force to wait before to apply the kernal hack and let us to configure the correct timing value for the different ps4 models?
Because right now I think that your menu is ignoring this value..
So @Leeful is now working with the v3 so the people wouldn't have to click on the usb message for the people with ESP32-S2...
If you have an ESP32-S2 board you can configure the timing after USB is mounted and before the hack is applied with the below Auto USB wait option:
My question is, are you going to use this option to force to wait before to apply the kernal hack and let us to configure the correct timing value for the different ps4 models?
Because right now I think that your menu is ignoring this value..
USB auto wait does not work in this version as it was based on a very early version of the sketch has nothing to do with the menu itself I do know for a fact that it will be included in the v3
Just be patient and let leeful do his stuff and good things will come
Ok, I'm just was curious..
Of course, there isn't any hurry here....
My opinion is always take all the time that need it before release it so have a great product with the less side effects possible...
Yes, in v3 you will be able to set an exact USB wait time to allow you to increase or decrease the wait time so that you can dial in the best time that works for your own PS4+ESP setup.
I havent seen one of those before so I cant say.
You could try altering the timing of when you click OK when the notification appears. You can try pressing it as soon as you see the notication or wait 2-3 seconds instead of waiting for it to dissapear.
I noticed a count of 3 works best but must be a count of seconds.
Post automatically merged:
So I would if I had an ESP32 probably around 5 to 6 second because it takes 2 to 3 for notice to show then another 3 for exploit.
Please help.. I tried to using the esp32 s2 and it always give me an error.. my ps4 can connect to esp32 s2 also tried with my phone and it can connect too.. but it always said the kernel exploit failed, reboot.. tried so many times and not a single one is succeed.. tried to re-flash the esp32 s2 using v1 / v2, tried to re chahe with v1 / v2, still got the same..
silly question sorry, but I have to ask, are you on 9.00?
Does it say [ESP MODE] in the title at the top of the screen when it is loading?
Do you get the "This USB storage device's filesystem is unsupported." popup notification?
Yes, I'm on 9.00, and yes it does say [ESP MODE] in the title at the top..
But I never get the notification "This USB storage device's filesystem is unsupported" tried to wait about 30s until 1 minute and still no pop up..
Attachments
It is normal, it happens to me sometimes too..
Sometimes the hack is almost instant and other times happen like @OnyXxX has described....
What I did when it happen to me, I click ok to close the message box, and then, the web hack start automatically again, and the result is the same (it fails again), then I close the browser and open again and the hack start again...
After repeat this previous sequence 4-5 times, the hack happen and the menu is showed correctly and I can run GH without issues.
Note: In the middle of this previous sequence sometimes the message "This USB storage device's filesystem is unsupported" show up but sometimes it not show up but the hack works too...
I guess that the reason is the way that the @Leeful made menu/code for some PS4 models it works without issues and for others ps4 model no, and sometimes happen this issue...
That is why I'm confidence that with the next version v3 when it will have incorporate the option "USB wait time", we will put a wait time to dial with the best time for our PS4 model + ESP-S2...
The "USB wait time" has nothing to to do with anything in v2.
USB wait time is only used in fully automated exploits.
v2 uses alert screens so you do the wait time yourself. You do the waiting and decide yourself when to continue the exploit after you see the USB unsopported popup.
If anyone is having problems it is probably either because thier ESP has crashed and is no longer connected to the network or that the ESP device itself is not being recognozed as a plugged in USB device on their PS4.
I have created a page for people who are having problems so that they can test if theis ESP is working as it should.
Step 1: Clear cache and cookies in your PS4 browser and install the test page using prb123.ir/ps-phive/esptest or if you dont use an online connection use the selfhost attached below.
Step 2: After you have installed the test page go to your network settings and connect to the PS-Phive! access point.
Step 3: After you have connected to the ESP access point, go back to the browser and run the tests.
Test 1 tests the network connection to your PS4 and Test 2 test the USB functionality of your ESP.
Full instructions are on the test page.
Sorry that the test page looks a mess but it does what it should which is all that matters. LOL.
**Important note that I forgot to add to the test page:
When you are doing the USB tests make sure to wait at least 20 seconds between clicking the Test USB buttons.
This gives the ESP enough time do disable the USB between tests.
USB wait time is only used in fully automated exploits.
v2 uses alert screens so you do the wait time yourself. You do the waiting and decide yourself when to continue the exploit after you see the USB unsopported popup.
If anyone is having problems it is probably either because thier ESP has crashed and is no longer connected to the network or that the ESP device itself is not being recognozed as a plugged in USB device on their PS4.
I have created a page for people who are having problems so that they can test if theis ESP is working as it should.
Step 1: Clear cache and cookies in your PS4 browser and install the test page using prb123.ir/ps-phive/esptest or if you dont use an online connection use the selfhost attached below.
Step 2: After you have installed the test page go to your network settings and connect to the PS-Phive! access point.
Step 3: After you have connected to the ESP access point, go back to the browser and run the tests.
Test 1 tests the network connection to your PS4 and Test 2 test the USB functionality of your ESP.
Full instructions are on the test page.
Sorry that the test page looks a mess but it does what it should which is all that matters. LOL.
**Important note that I forgot to add to the test page:
When you are doing the USB tests make sure to wait at least 20 seconds between clicking the Test USB buttons.
This gives the ESP enough time do disable the USB between tests.
Great stuff dudeThe "USB wait time" has nothing to to do with anything in v2.
USB wait time is only used in fully automated exploits.
v2 uses alert screens so you do the wait time yourself. You do the waiting and decide yourself when to continue the exploit after you see the USB unsopported popup.
If anyone is having problems it is probably either because thier ESP has crashed and is no longer connected to the network or that the ESP device itself is not being recognozed as a plugged in USB device on their PS4.
I have created a page for people who are having problems so that they can test if theis ESP is working as it should.
Step 1: Clear cache and cookies in your PS4 browser and install the test page using prb123.ir/ps-phive/esptest or if you dont use an online connection use the selfhost attached below.
Step 2: After you have installed the test page go to your network settings and connect to the PS-Phive! access point.
Step 3: After you have connected to the ESP access point, go back to the browser and run the tests.
Test 1 tests the network connection to your PS4 and Test 2 test the USB functionality of your ESP.
Full instructions are on the test page.
Sorry that the test page looks a mess but it does what it should which is all that matters. LOL.
**Important note that I forgot to add to the test page:
When you are doing the USB tests make sure to wait at least 20 seconds between clicking the Test USB buttons.
This gives the ESP enough time do disable the USB between tests.
The one thing I'd recommend is people make sure they are selecting erase flash when flashing the esp and not just over writing as this can cause problems also
Great idea to create this. I will do this tests next week and I will let know the results of my test.The "USB wait time" has nothing to to do with anything in v2.
USB wait time is only used in fully automated exploits.
v2 uses alert screens so you do the wait time yourself. You do the waiting and decide yourself when to continue the exploit after you see the USB unsopported popup.
If anyone is having problems it is probably either because thier ESP has crashed and is no longer connected to the network or that the ESP device itself is not being recognozed as a plugged in USB device on their PS4.
I have created a page for people who are having problems so that they can test if theis ESP is working as it should.
Step 1: Clear cache and cookies in your PS4 browser and install the test page using prb123.ir/ps-phive/esptest or if you dont use an online connection use the selfhost attached below.
Step 2: After you have installed the test page go to your network settings and connect to the PS-Phive! access point.
Step 3: After you have connected to the ESP access point, go back to the browser and run the tests.
Test 1 tests the network connection to your PS4 and Test 2 test the USB functionality of your ESP.
Full instructions are on the test page.
Sorry that the test page looks a mess but it does what it should which is all that matters. LOL.
**Important note that I forgot to add to the test page:
When you are doing the USB tests make sure to wait at least 20 seconds between clicking the Test USB buttons.
This gives the ESP enough time do disable the USB between tests.
If you have loaded GoldHEN there is no need for a disable ASLR payload because it will already be disabled.
You always know if ASLR has been disabled because you wil see that the webkit always loads a lot quicker and it usually loads in the same amount of time, every time.
The best way to test this is to use a more simplified menu like my 9v5 menu.
After a clean boot you wil know that the webkit exploit time can vary a lot. Sometimes if can load quickly but usually its around 20 seconds. After GoldHEN has been loaded you will see that the webkit loads in 4-5 seconds every time.
This is because ASLR has been disabled.
You can test this out with the PS-Phive! menu also but because it is more complex than a simple menu it causes the webkit to take a little longer to load but it will always load in under 10 seconds after GoldHEN has loaded because ASLR has been disabled.
No problem mate. You have my permission to make a userguide version if you want. Thanks for asking first.
Similar threads
-
Maximumbeans
-
DinohScene
That cat suit twink -
Veho
-
-
-
-
-
-
-
-
-
-
-
@
SylverReZ:
I haven't been gaming for such a long time. Been mostly busy with sleep, hardware tinkering and checking GBAtemp frequently. -
-
@
Maximumbeans:
It's going alright thanks+1 I know what you mean with gaming time. It's precious where I can get it these days.
-
@
Maximumbeans:
I think that's why I focus on just enjoying single player experiences that aren't too competitive
-
-
-
-
-
@
SylverReZ:
@Maximumbeans, Indeed. I've been working on getting this Infecutus chip to work on my PS2. But after soldering, I realised that a plastic piece was missing from the power ribbon cable to the power and eject buttons.
-
@
SylverReZ:
Now I could go with soldering the contacts from the cable to the connector on the mobo, but doesn't sound like a good permanent solution.
-
@
Maximumbeans:
Man, that's beyond my brain I'm no good with hardware for now. I'd like to get into hardmods in future though
-
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1
-
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.
gm