- Status
What a nice work @mrdude , so much customizing, going to play with this dongle, (being on classic esp32 dongle before), using your PSFree autoload (with latest Goldhen), now time for me to customize screen and more, again thanks a lot , very well done 
Post automatically merged:
PSFree or Ps-Phive! V3 ?
Last edited by Maupiti,
Dude, stop spamming this thread with unrelated stuff. This isn't a helpline for your board, it's only for the Lilygo-T-dongle and that's it. If you don't know what you're doing start your own thread. The reason it doesn't work properly for you is that you need to flash a partitions bin file with fat support and that has been set to use 32MB. You can do that by modding your boards partitions file and then compiling from source. I don't want to report your posts, but if you keep spamming the thread with unrelated thread stuff I'll contact the mods/admin to either remove your posts or I'll close the thread and you won't get anymore updates.
Last edited by mrdude,
, just sometimes a "bit overwhelming",
Because I put these lines of code in the software before I compiled it:
Code:
if (TIME2SLEEP < 5) {
TIME2SLEEP = 5;
} //min sleep time
bootTime = millis();This is so that the PS4 has time to boot fully after suppling the the dongle with power. It really shouldn't be less than this. Although the dongle can instantly go to deep sleep as soon as the usb image is mounted and then unmounted so it doesn't stay on - this option is in the config page. The 5 in the code above is for minutes.
Hum, dunno what I messed 
, PSFree with autogoldHen worked the first time flawlessly, (with the right splash screen), now whenever I use the dongle I get a red screen on PS4 with a bunch of offset, some errors , even if at the end I can launch (manually) GoldHen.
Already tried wiping everything from the dongle, flashing again, deleting cache, cookies on the PS4, only thing I did from the first setup was to change sleeping Time and add a Scroll text (a very short one,
redirect index2.html is checked),
Any idea ?
I should have done a dump as you suggest when it worked the first time
I'm not at home right now, will take some screenshots if it can help to identify the issue.
Looks like it's not using index2.html from PsFree
Used on AP mode,haven't tried over wifi network, but I don't see why it would change somethng.
, PSFree with autogoldHen worked the first time flawlessly, (with the right splash screen), now whenever I use the dongle I get a red screen on PS4 with a bunch of offset, some errors , even if at the end I can launch (manually) GoldHen.Already tried wiping everything from the dongle, flashing again, deleting cache, cookies on the PS4, only thing I did from the first setup was to change sleeping Time and add a Scroll text (a very short one,
redirect index2.html is checked),
Any idea ?
I should have done a dump as you suggest when it worked the first time
I'm not at home right now, will take some screenshots if it can help to identify the issue.
Looks like it's not using index2.html from PsFree
Used on AP mode,haven't tried over wifi network, but I don't see why it would change somethng.
Last edited by Maupiti,
Just wait, I'm doing an update just now to add PSfree into the program. I'm almost done - just a few tweaks to the loader as I always seem to get an out of memory error on the first run, then it works ok after that. I should be done in a day or two when I get around to fixing that.Hum, dunno what I messed
Already tried wiping everything from the dongle, flashing again, deleting cache, cookies on the PS4, only thing I did from the first setup was to change sleeping Time and add a Scroll text (a very short one,
redirect index2.html is checked),
Any idea ?
I should have done a dump as you suggest when it worked the first time
I'm not at home right now, will take some screenshots if it can help to identify the issue.
Looks like it's not using index2.html from PsFree
Used on AP mode,haven't tried over wifi network, but I don't see why it would change somethng.
In the meantime just format your dongle from the config page and leave the default settings as they are and clean your cookies and website data on your ps4 browser and you should be fine.
GreatJust wait, I'm doing an update just now to add PSfree into the program. I'm almost done - just a few tweaks to the loader as I always seem to get an out of memory error on the first run, then it works ok after that. I should be done in a day or two when I get around to fixing that.
In the meantime just format your dongle from the config page and leave the default settings as they are and clean your cookies and website data on your ps4 browser and you should be fine.
, thanks a lot 
.No worries, take your Time, I've got a spare Esp32-S2 dongle with a working PSFree, so no problem for me for the exploit, but true that I really like your work .
Mandatory to format via the config or erasing via your flash gui is ok with size box Set to 1000000 ?
Oh, I think I understood, just format the partition so no need to reflash
Last edited by Maupiti,
Whenever you flash a bin file on your lilygo-t-dongle you should flash all 3 files provided. However I just told you to use the config page to format - it's kind of obvious to me that I mean from the dongle and not from any where else. Although you can easily erase your entire dongle via the software I provided for flashing and start from scratch if you need to. Also I fixed that memory error now so you should probably wait to do anything as an update is inniment. I just have some more testing to do then I'll release.Great
No worries, take your Time, I've got a spare Esp32-S2 dongle with a working PSFree, so no problem for me for the exploit, but true that I really like your work .
Mandatory to format via the config or erasing via your flash gui is ok with size box Set to 1000000 ?
Oh, I think I understood, just format the partition so no need to reflash
OP updated with new firmware (PSFree).
NOTE: Please make sure you clear your PS4 cached data files and cookies as your old loader files will be present and break stuff. Let's start clean!
After flashing I advice you head to the admin page on the dongle and format the fatfs partition storage. After that the dongle will reboot. If you wish to use the PSFree exploit, head to the config page and enable PSFree. This will reboot the dongle and you'll have some new files in stoage called loader.html and a file called exploitunpacked.js. These are the PSFree exploit files, as the exploit is still currently advancing these can be modded by those that know how, just do your mods and over write them. Don't worry about messing up as you can just disable PSFree and Re-enable it again to get the default files back.
I added some extra stuff to the dongle code to unpack gz files, so even though these files are stored as gzip in memory, once the PSFree is activated they get unpacked, this is to save space and also to prevent the PS4 browser from giving an out of memory error as it doesn't need to download and unpack them. Also note that in PSfree you now need to press a button when the usb image is mounted, this was giving me issues with timing and the best way to stop the PS4 from crashing was to force the user to see when the usb drive image was successfully mounted. Once the hack reaches the point of mounting the usb drive image the dongle will flash red and blue, once the payload is ready to be sent the dongle will stay on a green light so show that it managed to reach that stage. If it crashes the PS4 after this you should try using different versions of goldhen. I tried some older versions and they seemed more stable and less likely to cause memory crashing. The dongle will not shut down into deep sleep straight away, it will just use the time set in the config and shutdown when the timer expires after the exploit has been run.
The old hack is still present on the dongle as well, if you have issues with PSfree just disable it again and clear your browser cached files and you'll be back on the older hack.
Also attached in the OP is the new source code files for those that want to mess about with that stuff, that way you can see there's nothing dodgy going on :-)
That's all folks :-)
NOTE: Please make sure you clear your PS4 cached data files and cookies as your old loader files will be present and break stuff. Let's start clean!
After flashing I advice you head to the admin page on the dongle and format the fatfs partition storage. After that the dongle will reboot. If you wish to use the PSFree exploit, head to the config page and enable PSFree. This will reboot the dongle and you'll have some new files in stoage called loader.html and a file called exploitunpacked.js. These are the PSFree exploit files, as the exploit is still currently advancing these can be modded by those that know how, just do your mods and over write them. Don't worry about messing up as you can just disable PSFree and Re-enable it again to get the default files back.
I added some extra stuff to the dongle code to unpack gz files, so even though these files are stored as gzip in memory, once the PSFree is activated they get unpacked, this is to save space and also to prevent the PS4 browser from giving an out of memory error as it doesn't need to download and unpack them. Also note that in PSfree you now need to press a button when the usb image is mounted, this was giving me issues with timing and the best way to stop the PS4 from crashing was to force the user to see when the usb drive image was successfully mounted. Once the hack reaches the point of mounting the usb drive image the dongle will flash red and blue, once the payload is ready to be sent the dongle will stay on a green light so show that it managed to reach that stage. If it crashes the PS4 after this you should try using different versions of goldhen. I tried some older versions and they seemed more stable and less likely to cause memory crashing. The dongle will not shut down into deep sleep straight away, it will just use the time set in the config and shutdown when the timer expires after the exploit has been run.
The old hack is still present on the dongle as well, if you have issues with PSfree just disable it again and clear your browser cached files and you'll be back on the older hack.
Also attached in the OP is the new source code files for those that want to mess about with that stuff, that way you can see there's nothing dodgy going on :-)
That's all folks :-)
Last edited by mrdude,
There's an entire thread with over 121K views right here:
https://gbatemp.net/threads/release...xploit-host-menu.621028/page-29#post-10346604
And yet you somehow missed that after all the time you spend in here?
@laz305 And yet once again this has nothing do do with the lilygo-t-dongle or any of the files I have posted. I've already told you this thread isn't your personal helpline. It's a thread about the lilygo-t-dongle. That stuff you are showing in your screenshot has nothing to do with this thread or any of the files posted in here so you should start you own thread.
OP Firmware updated: Lot's of fixes.
For those that want to use this you should see big speed increases in booting with PSFree and the normal loader. This is because I no longer use a function to disable the mounted usb which was in previous and all other dongles firmware which reboots the dongle to disable the usb, this causes the PS4 to lose it's wifi connection and then the dongle also needs to reboot and re-run it's software. This has been fixed by unmounting the usb image and just mounting a good blank image instead. This fixes a lot of the timing issues with usb, so no need to wait for the dongle to reboot which makes the glitch faster and more stable. Also there's a few bug fixes so you are advised to update your dongle. Also replaced is goldhen back to a stable version(2.3), if you want to use a newer version (which I don't recommend for now), just rename your latest goldhen to goldhen.bin and use the web interface to upload it to the dongle.
I also recommend you format your dongle after flashing via the config page and clear your website data on your PS4 so that your cached files are not being used.
For those with issues, plug the dongle directly into the PS4 usb port and don't use a usb hub as these sometimes cause speed issues if they are not usb3 hubs and make the glitch slower for mounting the usb image from the dongle and can cause crashes. If you really need to use a usb hub go to the config page and change the default usb speed from 3000 to 4000 (or higher if you still have issues).
This will be my last release for a while as now all bugs seem to be fixed that are fixable. The next update when I get around to it will probably be to add microsd card support so that you can install small pkg files from the dongle. I should be able to mount a micorsd drive (probably fat32 or exfat) to show up on the ps4 when the cfw hack has finished so you can store some pkgs on a small microsd, bear in mind that the dongle microsd driver is slow and only supports usb1.1 transfer speeds, even though the dongle is usb3.0, so take that into account when trying to install to ps4. More info on this will be posted when I do the code. Anyway that's my next plan for this dongle as we may as well make use of that microsd feature this dongle provides.
For those that want to use this you should see big speed increases in booting with PSFree and the normal loader. This is because I no longer use a function to disable the mounted usb which was in previous and all other dongles firmware which reboots the dongle to disable the usb, this causes the PS4 to lose it's wifi connection and then the dongle also needs to reboot and re-run it's software. This has been fixed by unmounting the usb image and just mounting a good blank image instead. This fixes a lot of the timing issues with usb, so no need to wait for the dongle to reboot which makes the glitch faster and more stable. Also there's a few bug fixes so you are advised to update your dongle. Also replaced is goldhen back to a stable version(2.3), if you want to use a newer version (which I don't recommend for now), just rename your latest goldhen to goldhen.bin and use the web interface to upload it to the dongle.
I also recommend you format your dongle after flashing via the config page and clear your website data on your PS4 so that your cached files are not being used.
For those with issues, plug the dongle directly into the PS4 usb port and don't use a usb hub as these sometimes cause speed issues if they are not usb3 hubs and make the glitch slower for mounting the usb image from the dongle and can cause crashes. If you really need to use a usb hub go to the config page and change the default usb speed from 3000 to 4000 (or higher if you still have issues).
This will be my last release for a while as now all bugs seem to be fixed that are fixable. The next update when I get around to it will probably be to add microsd card support so that you can install small pkg files from the dongle. I should be able to mount a micorsd drive (probably fat32 or exfat) to show up on the ps4 when the cfw hack has finished so you can store some pkgs on a small microsd, bear in mind that the dongle microsd driver is slow and only supports usb1.1 transfer speeds, even though the dongle is usb3.0, so take that into account when trying to install to ps4. More info on this will be posted when I do the code. Anyway that's my next plan for this dongle as we may as well make use of that microsd feature this dongle provides.
Last edited by mrdude,
Great, with this latest release, it finally works well for me, using PSFree and latest release of GoldHen , so far, no issues, speed is there and stability ,(using defaults settings, and didn't need to increase usb time). Thanks @mrdude
- Status
Similar threads
- No one is chatting at the moment.
