Custom Firmware: Difference between revisions
From Handhelds Wiki
Jump to navigationJump to search
| Line 10: | Line 10: | ||
{{SectionStyleEnd}} | {{SectionStyleEnd}} | ||
{{SectionStyleStart}} | {{SectionStyleStart}} | ||
== Other or older Firmwares == | == Other or older Firmwares == | ||
Revision as of 05:23, 25 July 2026
Introduction
Custom Firmware (CFW) refers to a modified or alternative operating system installed on a device. It adds features like improved emulator support, performance tweaks, and custom themes. Most CFWs are based on Linux, offering flexibility and open-source support. Installing CFW usually involves flashing a microSD card and booting from it.
Other or older Firmwares
| Name | Link | Notes |
|---|---|---|
| Adam image | GitHub | CFW for Anbernic RG350, RG350P, RG350M, RG280M, RG280V, RG300X, PlayGo, PocketGo 2, PowKiddy Q80, GCW-Zero |
| Allium | GitHub | Custom launcher for the Miyoo Mini, Miyoo Mini Plus, and Miyoo Mini Flip |
| Anbernic StockOS Modifikation | GitHub | Anbernic RG35xx, RGG35xx 2024, RG35xx H, RG35xxSP, RG28xx, RG40xx H, RG40xx V, RGcube XX, RG34xx, RG34xx, SP RG35xx PRO |
| Carl OS | GitHub | StockMod of Miyoo Flip OS |
| cHAos | GitHub | AmberELEC fork for gameMT E6 / Game Console R50S |
| DesktopOS | GitHub | Desktop Environment for H700 devices |
| FunKey OS | GitHub | DrUm78's custom build of FunKey OS for FunKey S, Anbernic RG Nano, PowKiddy Q36 Mini, GBA Mini |
| GammaOS | GitHub | LineageOS based firmware for Anbernic RG405M / RG405V / RG505 |
| GammaOS Next | GitHub | LineageOS based firmware for Anbernic RG556 / RG-CUBE / RG406V / RG406H, AYANEO Pocket Micro, Retroid Pocket 4 PRO, Retroid Pocket Classic, KT Pocket KT-R1, ZPG Unicorn A1, GameMT E6 MAX |
| GarlicOS | Website | CFW for the Anbernic RG35XX (original version) that is similar to OnionOS |
| JelOS | GitHub | JELOS development has ended |
| KOLOS | GitHub | JELOS fork for RK3566 devices (Anbernic RG353P/M/V/VS, RG503, Powkiddy RK2023, RGB30, RGB10 and Max 3) |
| Koriki | GitHub | SimpleMenu frontend for the Miyoo Mini and Miyoo Mini Plus |
| Lakka | Website | Lightweight Linux distribution that uses RetroArch as front-end |
| MiyooCFW | GitHub | CFW for BittBoy, PocketGo, PowKiddy V90-Q90-Q20 |
| NextUI | GitHub | CFW for Trimui Brickand Trimui Smart Pro based of MinUI |
| PakUI | GitHub | This is like an addon for MinUI which adds lots of features and enhancements (for TrimUI Brick and TrimUI Smart Pro) |
| Powkiddy X39Pro / X45 / X51 / X70 Custom Firmware | GitHub | Powkiddy X39Pro/X45/X51/X70 Custom Firmware |
| Quark | Website | CFW for the Trimui Smart (not Pro) |
| R36S-Xorg | GitHub | Xorg on the R36S ArkOs |
| Recalbox | Website | CFW for Anbernic RG353M/V/P, RG351M/V/P, GPiCase 2W, Raspberry Pi, ODROID Go Advance, ODROID Go Super, PIBOY DMG |
| RetroFW | GitHub | CFW for devices with the JZ4760 SoC (system on a chip) |
| RetroOZ | GitHub | Custom firmware for OGS, OGA, RGB10Max and RGB10Max2 |
| StarkOS | Website | Preconfigured ArkOS fork for Anbernic RG353M/P/PS with simplified interface (DIY guide) |
| Surwish OS | Website | CFW for the Miyoo Flip |
| XFCE for H700 devices | GitHub | Desktop Environment for H700 devices |
Installing Custom Firmware
The process of installing the firmware to the SD card is often called "flashing". It creates a bootable drive.
ℹ️
Info
The "flashing" process is basically the same for all firmwares, but there may be some additional steps to get it working for your specific device.
Choosing the right micro SD card
Lots of devices come with cheap quality micro SD cards. If you don't want to risk loosing your 50 hour Pokemon save due to file corruption, it's recommended to get a card of a known brand.
Recommended SD card sizes
The firmwares usually take around 5GB-12GB of space. The card size(s) depend on your game list. This is only a reference point for smaller curated game lists up to PS1.
1 card Setup: 128GB
2 card Setup:
- TF1: 16-32GB
- TF2: 64-128GB
DTBVault
DTBVault is a community-driven archive for .dtb files, which are needed to boot. This archive is useful if you need to obtain a .dtb file that was corrupted in your handheld.
Warning
ℹ️
Info
If you can, please upload .dtb files that have not yet been uploaded.
