In most cases, yes. Some manufacturers preserve settings across minor revisions, but v60 is a major version. Assume all custom settings will be reset to factory defaults.
We have tracked three verified sources for the p75358v60 file as of this writing: p75358v60 firmware download exclusive
Avoid: Filesending sites, unverified Telegram channels, or eBay listings selling "firmware on USB." These are 99% scams. In most cases, yes
Even with exclusive firmware, issues can arise. Below are solutions based on field reports: We have tracked three verified sources for the
| Symptom | Likely Cause | Resolution |
|---------|--------------|-------------|
| “Firmware signature invalid” | Bootloader key mismatch or file corruption | Re-download from the exclusive source; check checksum. |
| Device stuck in boot loop after flash | Incomplete write or memory misconfiguration | Use serial console to interrupt boot and reflash v60 or roll back to v58. |
| Ethernet ports not responding | Configuration residue from previous version | Perform a hardware reset (hold reset button for 15 seconds). |
| Web GUI inaccessible | Default IP changed or HTTP service disabled | Use serial or SSH to check network config and reset to defaults. |
If the device becomes completely unresponsive (bricked), you may need a JTAG programmer or an SPI flash programmer to directly write the bootloader and firmware—a last resort for advanced users.
In most cases, yes. Some manufacturers preserve settings across minor revisions, but v60 is a major version. Assume all custom settings will be reset to factory defaults.
We have tracked three verified sources for the p75358v60 file as of this writing:
Avoid: Filesending sites, unverified Telegram channels, or eBay listings selling "firmware on USB." These are 99% scams.
Even with exclusive firmware, issues can arise. Below are solutions based on field reports:
| Symptom | Likely Cause | Resolution |
|---------|--------------|-------------|
| “Firmware signature invalid” | Bootloader key mismatch or file corruption | Re-download from the exclusive source; check checksum. |
| Device stuck in boot loop after flash | Incomplete write or memory misconfiguration | Use serial console to interrupt boot and reflash v60 or roll back to v58. |
| Ethernet ports not responding | Configuration residue from previous version | Perform a hardware reset (hold reset button for 15 seconds). |
| Web GUI inaccessible | Default IP changed or HTTP service disabled | Use serial or SSH to check network config and reset to defaults. |
If the device becomes completely unresponsive (bricked), you may need a JTAG programmer or an SPI flash programmer to directly write the bootloader and firmware—a last resort for advanced users.