-
-
Notifications
You must be signed in to change notification settings - Fork 914
Factory Defaults
After a firmware update, some settings may be stored in an incompatible format, causing apps to malfunction or the device to behave unexpectedly. Resetting to factory defaults clears these settings and returns the device to a known-good state.
There are two separate stores that may need to be reset:
- Persistent memory (P.Mem): Stores device-wide settings such as frequency, corrections, UI options, and radio configuration. Held in battery-backed RAM (requires a working coin cell battery).
- SETTINGS directory on SD card: Stores per-app settings saved by the "App Load and Save" feature.
Navigate to Settings → P.Memory Mgmt. The following options are available:
| Button / Control | Function |
|---|---|
| Use SD card for P.Mem | Store P.Mem on SD card instead of coin-cell-backed RAM (useful if coin cell is dead or missing) |
| Save P.Mem to SD card | Back up current P.Mem contents to SD card |
| Load P.Mem from SD Card | Restore P.Mem from a previously saved SD card backup |
| Reset P.Mem to defaults | Reset all persistent memory settings to factory defaults |
Pressing Reset P.Mem to defaults opens a confirmation dialog:
"This will reset the P.Mem to default settings."
Confirm with Yes to apply the reset. The status bar refreshes immediately.
If the device is in a state where it cannot be navigated normally, persistent memory can be bypassed at startup. Hold the Left and Right buttons simultaneously while powering on or pressing reset. The device will boot as if P.Mem is empty, loading factory defaults without modifying the stored contents.
Note
This bypass is temporary — P.Mem is not permanently cleared by this method. To permanently reset, use the Settings menu as described above.
P.Mem is reset to defaults automatically in two cases:
- After a firmware upgrade or downgrade that changes the P.Mem data structure version
- When the coin cell battery is discharged (P.Mem loses power and becomes invalid)
Delete all files under the SETTINGS/ directory on the SD card. This resets all per-app settings saved via "App Load and Save", as well as the P.Memory Mgmt configuration (e.g. the SD pmem flag file). It does not reset the persistent memory itself.
Note
Updating the SD card content to the latest release is a good opportunity to do this cleanup. The firmware does not automatically remove old or incompatible settings files.
For a complete reset (both P.Mem and SD card settings):
- Remove the SD card and connect it to a computer.
- Delete all files under
SETTINGS/. - Optionally update the SD card content to the latest release.
- Reinsert the SD card.
- Boot the device without the SD card first (hold the boot key if required), go to Settings → P.Memory Mgmt, and press Reset P.Mem to defaults.
- Shut down, reinsert the SD card, and boot normally.
The device will now behave as if freshly set up.
Note
The "Debug Dump" app (under Settings → Debug → Debug Dump) can generate a file listing all current persistent memory settings — useful for diagnosing issues before resetting.
How to collaborate
Contributing Guidelines
Trusted contributors
How to ask questions correctly
- PortaPack Versions (which one to buy)
- Features
- HackRF Versions
-
Description of the hardware
- Enclosure/cases
- Repairs
- Mods
- Usage cautions
- First steps
- Firmware update procedure
- User interface
- Powering the PortaPack
-
Troubleshooting
- Won't boot
- Config Menu
- Firmware upgrade
- Diagnose firmware update in Windows
- Receive Quality Issues
- No TX/RX
- TX Carrier Only
- Dead Coin Cell Battery
- Factory Defaults
- SD card not recognized by PC with the SD-card over USB selected
- DFU overlay
- Full reset
- SolveBoard
- How to Format SDCard
- What if I don't like some of the apps
- 📥 Receivers
- 2-Tone-RX
- ACARS
- ADS-B
- AFSK
- AIS Boats
- Analog TV
- APRS RX
- Audio
- BLE RX
- Detector
- EPIRB RX
- ERT Meter
- Flex RX
- Radio
- Fox-Hunt
- FPV-Detect
- gfxEQ
- Level
- Meteor
- Morse RX
- NOAA
- NRF
- POCSAG
- ProtoView
- Radiosonde
- RTTY RX
- Scanner
- Search
- Signal Hunter
- SSTV RX
- SubCar
- SubGhzD
- Tetra RX
- Time Sink
- TPMS RX
- Weather
- WeFax
- VOR RX
- 📤 Transmitters
- 2-Tone-TX
- ADS-B(S) TX
- Adult Toys
- APRS TX
- BHT Xy/EP
- BLE TX
- BLESpam
- Burger Pager
- CVS Spam
- EPIRB TX
- Flex TX
- FlipperTX
- GPS Sim
- Hopper
- Jammer
- KeeLoq TX
- Key fob TX
- LGE Tool
- MDC-1200 TX
- Morse TX
- OOK
- OOK Brute
- OOK Editor
- P25 TX
- POCSAG TX
- RDS
- RTTY TX
- SAME TX
- Security+ TX
- Signal gen
- Soundboard
- Spectrum Painter
- SSTV
- TEDI/LCR
- TouchTunes
- TPMS TX
- VOR TX
- 🔄 Transceivers
- 🟡 Recon
- 🔴 Capture
▶️ Replay- 🖲️ Remote
- 🔍 Looking Glass
- 🛠️ Utilities
- 🎮 Games
- ⚙️ Settings
- 💻 HackRF Mode
-
Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi), or other weird distros
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
-
Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes