Repository navigation
WebUI and FTP
While the payload runs it starts two services on the PS5's network address:
| Service | Address | Purpose |
|---|---|---|
| WebUI | http://$PS5IP:8080 |
Inspect/label boot files, pick image + target, upload/delete files |
| FTP | ftp://$PS5IP:21 |
Anonymous; rooted at the upload dir for very large *.img files |
The page auto-boots with the detected defaults after about 2 minutes if you do nothing. From it you can:
- see the auto-detected
bzImage,initrd.img,cmdline.txtacross the search paths; - choose the OS image and the boot / install target;
- set the install size (GB,
0= full); - list / upload / delete files in the boot directory;
- edit search paths and filename overrides (one
key=valueper line).
FTP is handy for pushing a multi-GB .img without the WebUI's HTTP upload size limits:
# anonymous login, empty password
ftp $PS5IP
# or
curl -T ps5-arch.img ftp://$PS5IP/Files land in the same upload directory the WebUI lists.
The WebUI shows a Hardware / driver support table listing the PS5's components
(GPU, CPU, WiFi, Bluetooth, Ethernet, audio, NVMe, USB) with their chipset name,
kernel driver, and support status. It also reports whether the PS5 WiFi firmware
(lib/nxp/pcieuartiw620_combo_v1.bin) has been dumped onto the boot directory.
The payload reads the ext4 volume label from the selected .img and rewrites
root=LABEL=... in the cmdline automatically, so the loop-mount matches the
image even if cmdline.txt is stale. The initramfs also re-scans the NVMe
GPT (BLKRRPART) so the hidden PS5 partitions appear before mounting.