-
-
Notifications
You must be signed in to change notification settings - Fork 600
Factory Defaults
Sometimes with an update some settings management is changed and render the actual settings set in various place not working correctly or clearly killing some apps.
To resolve this you can try to reset these settings. For that, you'll have to clear the persistent settings and clean some directories on your SDCARD.
The best way to achieve the reset is to take out the SDCARD and do the cleanings on it on computer.
Boot the unit without the SDCARD (you may need to press your boot key), get into the 'Settings' / 'P.Memory Mgmt' menu and clean the persistent memory using the button.
Shutdown.
While you're at it update the SDCARD content to latest if not done.
Put back the SDCARD.
Boot (may need boot key).
You can now use your device like if it was installed first.
Delete all the files under 'SETTINGS' to reset "App Load and Save" settings as well as the configuration of the "P.Mem" menu. (note: this does not reset the persistent memory itself).
NOTE FIRST: this reset the saved boot config key. In case you think it's not booting because of a bad saved detection, delete the file under that directory.
Get into 'Settings' , 'P.Memory Mgmt' and click on the '! reset p.mem, load defaults !'. This resets all configuration settings that are stored in persistent memory. Note that persistent memory settings are sometimes reset automatically following a firmware upgrade or downgrade, specifically if there is a firmware change that affects the persistent memory data format, or if the coin cell battery is discharged. For a complete list of settings stored in persistent memory, the "Debug Dump" app can be used to create a file listing all persistent memory settings.
In case the p.mem contents somehow block the startup (the screen stays black and the RX led blinks rapidly that typically happen after flashing a different build) the p.mem can be ignored during startup by holding down the left and right buttons while starting up the device.
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.
How to collaborate
How to ask questions correctly
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- 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
- H2+ speaker modifications
- 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
- Applications
-
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)
- 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