Manual: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
yeoldegrove (talk | contribs) m (correct image naming) |
||
Line 10: | Line 10: | ||
* Images with "install" in the name will automatically flash the system to emmc, erasing anything that was on it previously in the process. | * Images with "install" in the name will automatically flash the system to emmc, erasing anything that was on it previously in the process. | ||
* Images that have "install" in the file name can run directly from the SD card that you write them to, leaving emmc untouched. | * Images that do not have "install" in the file name can run directly from the SD card that you write them to, leaving emmc untouched. | ||
=== Reflashing a Pyra === | === Reflashing a Pyra === |
Revision as of 07:06, 11 October 2021
Info assembled from inclusions from other pages so that its always updated. Mostly Hw and Sw categories. For example assembly/disassembly from repairs. Screenshots of every installed app.
Software
Pyra images
https://packages.pyra-handheld.com/images/buster/
- Images with "install" in the name will automatically flash the system to emmc, erasing anything that was on it previously in the process.
- Images that do not have "install" in the file name can run directly from the SD card that you write them to, leaving emmc untouched.
Reflashing a Pyra
Sometimes you've played with your pyra so much that you need to start again. With a spare SD card, we have you covered.[1]
- Grab the latest image with install in its name from https://packages.pyra-handheld.com/images/buster/
- Extract that 7z file to get an .img file
- Write that image file to an SD card with something like etcher. This will erase everything on the SD card
- Insert SD card into Pyra left SD card slot
- Power on, and it should start flashing. This will erase everything on the internal drive of the Pyra
From there, power off when it tells you, eject the SD card, power back on, and you should get to the first-run setup stuff.
Testing keyboard/buttons/nubs
The input tester accesses the hardware directly and therefore conflicts with funkey monkey. To use it, you must stop funkey monkey temporarily (systemctl stop pyra-input afair)
- ↑ https://pyra-handheld.com/boards/threads/first-information-for-new-pyra-owners-faq.99302/post-1686480 Based on forum information