This page lacks the following devices: TCL Flip 3, JioPhone Prima 2, HCmobi 4G Flip, B-Felix BF401, B-Felix BF402, HMD Barbie Phone, and Energizer E288s.
All of these devices are considered untested.
This device table is taken from tbrrss's blog, some information taken from bmndc's device table.
This list was possible thanks to the feedbacks of our users, all people like you, and serves to guide developers in choosing a KaiOS device on which they can test applications, study bugs and improve the operating system as freely as possible using ADB and development tools.
Its thanks to the research of the community that it was possible to "free" these phones by bringing together the experiences of each of us.
| Emoji | Description |
|---|---|
| ✅ | Debug enabled by default, enable debugging via *#*#33284#*#* code or *#*#0574#*#* code |
| ⛔ | engmode-extension permission is disabled |
| ❓ | Device is untested |
| 🔒 | Debugging is not possible |
| 👾 | Requires w2d |
| 👹 | Requires root or boot patching |
To turn on debugging mode with W2D, open your phone's built-in Browser and go to w2d.bananahackers.net. Navigate your mouse and click on the big Launch developer menu button; you'll be redirected to a hidden Developer menu in the Settings app. From there, select ADB and DevTools under Debugger, and a bug icon will appear in the status bar.
To turn off, do the same steps but select Off under Debugger.
| Manufacturer | Model Name | Debug | KaiOS Version | Notes | Market | Form Factor |
|---|---|---|---|---|---|---|
| GreatCall | Jitterbug Flip | ✅ | Firefox OS 2.2 | Originally runs FirefoxOS but was later updated to use KaiOS | US | Flip |
| Alcatel | Alcatel GO FLIP 2 | ✅ | 1.0 | dial ##3424# after enabling debug mode |
US | Flip |
| Alcatel | Alcatel GO FLIP 3 | 👹 | 2.5 | US | Flip | |
| Alcatel | Alcatel GO FLIP 4 | 🔒 | 3.0 | ADB unauthorized, u/tbrrss | US | Flip |
| Alcatel | Alcatel SMARTFLIP | 👹 | 2.5 | US | Flip | |
| TCL | TCL Flip Pro | 🔒 | 3.0 | ADB does not detect device | US | Flip |
| Jio | JioPhone | 👹 | 2.5 | India | Candybar | |
| Jio | JioPhone 2 | 👹 | 2.5 | India | QWERTY | |
| Jio | JioPhone Prima 4G | ❓ | 2.5 | India | Candybar | |
| CAT | CAT B35 | 👹👾 | 2.5.1 | Requires extracting using EDL and using w2d to enable debugging. | Global | Candybar |
| Doro | Doro 7050/60/70 | 👾 | 2.5 | FFBM must first be enabled via Power + Vol-, run the command adb shell start b2g, and make the dev menu permanent via Wallace Toolbox |
Global | Flip |
| Maxcom | Maxcom MK241 | 👹 | 2.5.1 | Europe | Candybar | |
| Maxcom | Maxcom MK281 | 👾 | 2.5.1.1 | Europe | Candybar | |
| Maxcom | Comfort MK399 | ❓ | 2.5 | Europe | Flip | |
| Multilaser | Multilaser ZAPP | ✅ | 2.5 | Brazil | Candybar | |
| Multilaser | Multilaser ZAPP II 3G | 👾 | 2.5 | Brazil | Candybar | |
| myPhone | Up Smart 3G | ❓ | 2.5 | Europe | Candybar | |
| myPhone | Up Smart LTE | 🔒 | 2.5 | Europe | Candybar | |
| Positivo | Positivo P70S | ✅ | 2.5 | Brazil | Candybar | |
| Hammer | Hammer 5 Smart | ❓ | 2.5 | Europe | Candybar | |
| Nokia | Nokia 8110 4G | ✅ | 2.5.1 | Global | Candybar | |
| Nokia | Nokia 2720 V Flip | 🔒 | 2.5.4 | US | Flip | |
| Nokia | Nokia 2720 Flip | ✅ | 2.5.2 | Global | Flip | |
| Nokia | Nokia 2720 Flip (latest firmware, 40.00.17.02) | 👹 | 2.5.2.2 | Global | Flip | |
| Nokia | Nokia 8000 4G | ✅⛔ | 2.5 | Global | Candybar | |
| Nokia | [Nokia 6300 4G] | ✅⛔ | 2.5 | Global | Candybar | |
| Nokia | [Nokia 2780 Flip] | 👹 | 3.1 | ADB unauthorized | US | Flip |
| Nokia | Nokia 2760 Flip | 🔒 | 3.0 | ADB unauthorized | US | Flip |
| Nokia | Nokia 800 Tough | ✅ | 2.5.2 | Global | Candybar | |
| Nokia | Nokia 800 Tough (latest firmware, 40.00.17.01) | 👹 | 2.5.2.2 | Global | Candybar | |
| TracFone | My Flip 2 4G | ✅⛔ | 2.5 | US | Flip | |
| Cingular | Cingular Flex 4G | ✅⛔ | 2.5 | No rooting | US | Flip |
| Cingular | Cingular Flex 2 (Debut Flex) | 🔒 | 3.1 | Debugging mode can be turned on with W2D, but phone shows up in ADB as unauthorized (thanks u/canyouswim73!) |
US | |
| Cingular | Cingular Flip 2 | ✅ | 1.0 | US | Flip | |
| Cingular | Cingular Flip 3 (Q28A) | 👹 | 2.5 | US | Flip | |
| Consumer Cellular | IRIS Flip | 🔒 | 3.1 | Enable ADB via *#*#9527#*#* |
US | Flip |
| Orbic | Journey V 4G | ❓ | 2.5 | US | Flip | |
| Orbic | JOURNEY Pro 4G | ❓ | 3.1 | Japan | Flip | |
| Blu | Zoey Smart 3G | 👾 | 2.5 | Global | Candybar | |
| Blu | Tank Mega | ❓ | 2.5 | Global | Candybar | |
| Blu | Flex B300V | ❓ | 3.1 | Global | Flip | |
| Cricket | Debut Flip | 🔒 | 3.1 | US | Flip | |
| SPC | Jasper | ❓ | 2.5 | Europe | Flip | |
| SPC | Jasper 2 4G | ❓ | 2.5 | Europe | Flip | |
| TIM | TIM Social 4G | ❓ | 2.5 | Europe | Candybar | |
| Aspera | Aspera R40 | ❓ | 2.5 | Australia | Candybar | |
| Aspera | Aspera F30 4G | ❓ | 2.5 | Australia | Candybar | |
| R3Di | FR150 Bright Flip | ❓ | 2.5 | US | Flip | |
| Mobicel | S1 Smart 4G | ❓ | 2.5 | South Africa | Candybar | |
| MTN | MTN Smart | ✅ | 2.5 | Africa | Candybar | |
| Jazz | Digit 4G | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Music | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Elite | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Power | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Power Max | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Bold | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Star | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Defender | ❓ | 2.5 | Pakistan | Candybar | |
| Jazz | Digit 4G Shine | ❓ | 2.5 | Pakistan | Candybar | |
| Orange | Sanza | ✅ | 2.5 | Africa | Candybar | |
| Orange | Sanza XL 4G (it9301) | ✅ | 2.5 | Africa | Candybar | |
| Orange | Neva Link | ❓ | 2.5 | Global | Flip | |
| Orange | Neva Mini | ❓ | 2.5 | Global | Candybar | |
| Orange | Orange K2 | ❓ | 2.5 | Africa | Candybar | |
| Alcatel | Alcatel 3078 | ❓ | 2.5 | LATAM | Candybar | |
| Alcatel | Alcatel 3088 | ❓ | 2.5 | Global | Candybar | |
| Alcatel | Alcatel 3088X | ❓ | 2.5 | LATAM | Candybar | |
| Altan | Altan K26 | ❓ | 2.5 | Mexico | Candybar | |
| Energizer | Energizer H280S | ✅ | 2.5 | Global | Candybar | |
| Energizer | Energizer E241S | ✅ | 2.5 | Global | Candybar | |
| Energizer | Energizer E280S | ✅ | 2.5 | u/gogolplex-pt | Global | Candybar |
| Energizer | Energizer E282SC | 🔒 | 2.5 | u/nicalejo | Global | Flip |
| Energizer | Energizer E242S | 🔒 | 2.5 | u/CaramelSpoonful | Global | Candybar |
| TECNO | TECNO T901 | ❓ | 2.5 | Africa | Candybar | |
| TECNO | TECNO T920d 4G | ❓ | 2.5 | Africa | Candybar | |
| Tigo | Tigo T-Smart | ✅ | 2.5 | Africa | Candybar | |
| VMK | Elikia Moke 2 | ❓ | 2.5 | Africa | Candybar | |
| Muni | Muni Smart 4G | ❓ | 2.5 | Africa | Candybar | |
| Lemok | Lehumo Smart 4G | ❓ | 2.5 | Africa | Candybar | |
| QMobile | QMobile 4G Plus | ✅ | 2.5 | Pakistan | Candybar | |
| Vodacom | Smart Kitochi (Azumi) | ❓ | 2.5 | Tanzania | Candybar | |
| Vodacom | Smart Kitochi (Vida) | ❓ | 2.5 | Tanzania | Candybar | |
| Vodacom | Vibe 4G | ❓ | 2.5 | Lesotho | Candybar | |
| Qubo | Qubo Rainbow P280 | ❓ | 2.5 | Europe | Candybar | |
| GeoPhone | GeoPhone T15 | ❓ | 2.5 | Bangladesh | Candybar | |
| GeoPhone | GeoPhone T19 | ❓ | 2.5 | Bangladesh | Candybar | |
| GeoPhone | GeoPhone T19i | ❓ | 2.5 | Bangladesh | Candybar | |
| CellAllure | Smart Temp | ❓ | 2.5 | LATAM | Candybar | |
| DIXON | DIXON XK1 | ❓ | 2.5 | South Africa | Candybar | |
| RAM9 | RAM9 Plum 4G | ❓ | 2.5 | Global | Candybar | |
| Xandos | Xandos X5 3G | ❓ | 2.5 | Mexico | QWERTY | |
| GHIA | GHIA GQWERTY | ❓ | 2.5 | Mexico | QWERTY | |
| GHIA | GHIA KoX1 | ❓ | 2.5 | Mexico | Candybar | |
| GHIA | GHIA GK3G | ❓ | 2.5 | Mexico | Candybar | |
| Logicom | Kay 283 | ✅ | 2.5.1 | Europe | Candybar | |
| Logicom | Kay 284 4G | ✅⛔ | 2.5 | @xy_cy on r/KaiOS Discord Server | Europe | Candybar |
| Hyundai | Hyundai L365 | ❓ | 2.5 | Global | Flip | |
| VIETTEL | VIETTEL V6504 | ❓ | 2.5 | Press and hold 2 on boot to enter Recovery mode | Vietnam | Candybar |
| VIETTEL | VIETTEL V1207 | ❓ | 2.5 | Vietnam | Candybar | |
| VIETTEL | VIETTEL BKAV C85 | ❓ | 2.5 | Vietnam | Candybar | |
| Corn | Smart K 3G | ❓ | 2.5 | Global | Candybar | |
| Telma | Wi-kif 3G | ❓ | 2.5 | Africa | Candybar | |
| Telma | Wi-kif 4G+ | ❓ | 2.5 | Africa | Candybar | |
| Telma | Wi-kif Max 4G | ❓ | 2.5 | Africa | Candybar | |
| Crosscall | Core-S4 | ✅⛔ | 2.5.3.2 | Europe | Candybar | |
| i-PLUS | i-PLUS i4G | ❓ | 2.5 | Africa | Candybar | |
| iPRO | iPRO Geniphone A22 | ❓ | 2.5 | Global | Candybar | |
| iPRO | iPRO Smart 2.4S | ❓ | 2.5 | Global | Candybar | |
| WINTEK | W209 3G | ❓ | 2.5 | Ethopia | Candybar | |
| Symphony | Symphony PD1 4G | ❓ | 2.5 | Bangladesh | Candybar | |
| VGO TEL | VGO TEL Smart HiFi | ❓ | 2.5 | Pakistan | Candybar | |
| Unitel | Unitel Wifone (M42445) | ❓ | 2.5 | Africa | Candybar | |
| Safaricom | Kimem Kerefa | ❓ | 2.5 | Africa | Candybar | |
| Gigaset | Gigaset GL7 | ❓ | 2.5 | Europe | Flip | |
| Smart | Smart Nano II | ❓ | 2.5 | Global | Candybar | |
| Logan | Panita | ❓ | 2.5 | LATAM | Candybar | |
| Unonu | Unonu K8 | ❓ | 2.5 | LATAM | Candybar | |
| Sveon | Sveon SMB300 | ❓ | 2.5 | LATAM | Candybar | |
| Logicom | Logic B8K Dual | ❓ | 2.5 | Global | Candybar | |
| IKU | IKU V400 | ✅ | 2.5 | UAE | Candybar | |
| Nobby | Nobby 231 | ✅ | 2.5 | Russia | Candybar | |
| Nobby | Nobby 240 LTE | ❓ | 2.5 | Russia | Candybar | |
| IDC | IDC Voice 20 4G | ❓ | 2.5 | Russia | Candybar | |
| Wonder | Wonder L2407 4G | ✅ | 2.5 | Kenya | Candybar | |
| Africell | Afriphone Smart 3G | ❓ | 2.5 | Africa | Candybar | |
| Zantel | Zantel Smarta | ❓ | 2.5 | Tanzania | Candybar | |
| Smart | Smart TZ1 | ❓ | 2.5 | Tanzania | Candybar | |
| Advan | Hape Online 4G | ❓ | 2.5 | Indonesia | Candybar | |
| WizPhone | WizPhone WP006 | ❓ | 2.5 | Indonesia | Candybar | |
| Sigma | X-Style S3500 sKai | ❓ | 2.5 | Ukraine | Candybar | |
| Blackview | Blackview N1000 | 👹 | 2.5.3.2 | timofei.agafonov on r/KaiOS Discord Server, use https://github.com/bkerler/mtkclient to boot patch | Ukraine | Candybar |
| Lanix | Lanix U340 | ❓ | 2.5 | Mexico | Candybar | |
| Accent | Accent Nubia 50K | ✅ | 2.5 | Morocco | Candybar | |
| Accent | Accent Nubia 60K | ❓ | 2.5 | Morocco | Candybar | |
| Flow | Alpha B10 Flow | ❓ | 2.5 | Caribbean | Candybar | |
| Econet | Econet Atom 3G | ❓ | 2.5 | Zimbabwe | Candybar | |
| TTfone | TTfone TT240 | ✅ | 2.5.1.1 | .yarnamamite on r/KaiOS Discord Server | UK | Candybar |
| ZTE | ZTE Z2316 4G | ❓ | 2.5 | Global | Candybar | |
| ZTE | ZTE Z2317 4G | ❓ | 2.5 | Global | Candybar | |
| Mango | AKEZA 4G | ❓ | 2.5 | Rowanda | Candybar | |
| Mango | AKABUTO 4G | ❓ | 2.5 | Rowanda | Candybar | |
| Itel | Itel it9200 4G | 👾 | 2.5.1.2 | imchocomint on r/KaiOS Discord Server | Global | Candybar |
| Itel | Itel it9300 | ❓ | 2.5 | Global | Candybar | |
| Lava | Lava Captain 11 3G | ❓ | 2.5 | Global | Candybar | |
| Condor | Condor FP216L | ❓ | 2.5 | Global | Candybar | |
| Aligator | Aligator K50 eXtremo | ❓ | 2.5 | Czechia | Candybar | |
| Fise | Fise M32421 | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M32424 | ❓ | 2.5 | Global | QWERTY | |
| Fise | Fise M32428 | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M42421 | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M42421A | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M42428 | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M32433 3G | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M42433 | ❓ | 2.5 | Global | Candybar | |
| Fise | Fise M42842 | ❓ | 2.5 | Global | Flip | |
| Kammunica | La Mano | ❓ | 2.5 | Europe | Candybar | |
| G-Plus | G-Plus F5 | ❓ | 2.5 | Taiwan | Candybar | |
| Red-X | Red X Revolver | ❓ | 2.5 | Papua New Guinea | Candybar | |
| BMobile | BMobile W125K | ❓ | 2.5 | Europe | Candybar |
The sideload of applications and the ability to access the debug tools belongs to the nature of Firefox OS, which is the heart that moves KaiOS, and should be so for all.
The devices supported by the Development Tools (WebIDE, kaiosrt, ADB, etc...) require access to the USB debugging, normally accessible using codes, however, there are many devices whose access requires specific tools to manipulate the partitions, safely (userdata or cache) or in a risky way (boot). It all depends on the OEMs and their decision to hide or not the natural properties of the software once installed on their devices.
After two years of research, since summer 2018, we have finally come to a precise pattern on how jailbreak works on different KaiOS devices.
The approach is based on the type of processor used on the device, Qualcomm, Spreadtrum or Mediatek (learn more here):
Qualcomm devices are the most prone to OEM blocking (CAT, Doro, Alcatel...), but for some of them debugging is the easier (Nokia), using just one code.
Spreadtrum devices use codes, just like Qualcomm phones, but statistically they are the most numerous among debug-enabled devices.
Mediatek devices do not have codes, but are much more versatile for Fastboot connections.
The devices in this list are broken down according to five search situations in which the researcher attempted to enable USB debugging and the Developer menu. We can further subdivide them on the basis of effectiveness and utility:
From the first to the fourth situation all the devices enabled for debugging are listed.
The fifth concerns devices that are still locked (for now).
We start by listing the debug-enabled devices, and then move on to locked phones up, ending with the devices unknown. If you want to let us know about any KaiOS phone, please edit the wiki. It will be of great help to other people like you. Because alone we are nothing, but all together we are so much!
Let's see them together. Just click on the devices with the name underlined for more details.
Start by reading the device class features listed below to understand what you can do with your device. Detect the chipset model, so you know where to start.
This solution is not based on any particular situation, as it is a natural capability of KaiOS, discovered on September 22, 2020 by Tbrrss (on Discord) and implemented in a web page by Luxferre. It consists to connect the browser of your phone to https://w2d.bananahackers.net/ to open the hidden Developer Menu, then select "Debugger" and enable "ADB and DevTools", a bug icon should appear in the system tray above. Try it now from your KaiOS phone:
Listed below are all devices on which Development Tools have been proven to work properly and without adding patches to the boot partition:
This solution has proven effective not only for debug-enabled devices (situation 1 and 2), but also for many models that have been classified as "Debug-locked", for example, Blu Zoey Smart, various Qualcomm-based Jio phones and CAT B35 (see situation 4). NOTE that only Doro-branded KaiOS phones require to be started in FFBM mode in order to use ADB and WebIDE.
On any other device, if using the "adb devices" command you get "unauthorized" as output message, you probably need to patch the boot partition. Use Fastboot (see MEDIATEK-BASED devices) or jump to the situation 4.
This situation is typical of Qualcomm-based devices. If the code *#*#33284#*#* needed for debugging works, we must verify if we have access to ADB and WebIDE.
Listed below are all Qualcomm-based devices where this rule is confirmed:
Although this situation is the easiest to move into, many other Qualcomm-based devices (for example Doro, CAT and Maxcom) are more likely to be "debug-locked" by their manufacturers, so by knowing this rule, we can be more aware of the problems we might encounter if we wanted to develop applications on a KaiOS device (skip to the points 4 and 5 for more information about debug-locked Qualcomm phones).
This situation is typical of Spreadtrum-based devices. If the code *#*#33284#*#* needed for debugging works, we must verify if we have access to ADB and WebIDE. If the result is negative, enable debugging using the code *#*#0574#*#* and retry the access to ADB and WebIDE. If all goes well we can use Wallace-toolbox to perform a "privileged factory reset" and make the jailbreak permanent. Like before, all Spreadtrum-based phones where this rule is confirmed are listed here:
Listed below are some unknown Spreadtrum-based phones that should work the same way as the ones just listed above, but we don't have any researchers on them to confirm or deny this rule:
Edit this list and add to it as needed.
This situation is typical of Mediatek-based devices. The debug code does not work, let's check if Fastboot is available and if it is possible to flash the "cache" partition. If all goes well, use the "cache injection" method, and we will get the Developer menu. This rule was tested and confirmed on:
Listed below are some unknown Mediatek-based phones that should work the same way as the ones just listed above, but we don't have any researchers on them to confirm or deny this rule:
Please, edit this page if you have any further information. It will help many other people in their choice.
If all of the situations seen so far have not been successful, your device is Debug-locked (situations 4 and 5).
This situation is typical for devices that are no longer locked (see "situation 5"). The debug code does not work and Fastboot is not available even to flash the partitions. Check if we have other tools to flash the partitions. If yes, we can use the "cache injection" method, or the "manual jailbreak", and we will get the "developer" menu.
The situation 5 includes all the devices in which the debug code does not work, Fastboot is not available and we do not even have the tools to perform the partition flash. Those interested in developing applications for KaiOS are advised to do not buy one of these phones:
All of the known locked phones are Qualcomm-based and sold exclusively in Europe (CAT, Doro and Maxcom) and the United States (Alcatel and Doro), however, with the right tools we would be able to bring them back to situation 4, (see above), unlocking them, as has already happened for CAT B35, Alcatel A405DL and Maxcom MK241. Although debugging is not possible, you can use a non-root "adb shell" on them. Find out how to do on their common page
Listed here are some devices whose chipset is not specified anywhere:
To receive more support and report useful news and information about your device, please contact us. As always, your feedback will help many other people in their choice.
Some KaiOS phones are not sold as KaiOS phones, and or/feature modified versions of KaiOS. One example are the phones made by Alcatel for Greatcall/Lively, which feature custom versions of KaiOS. In this case these phones were targeted towards elderly Americans with large buttons and a custom OS.
Sometimes the official website of the manufacturer provides an idea and these phones really exist, but only in the form of prototypes to be presented on the stands of the main technology fairs, without the belief of being able to produce others in the future, perhaps for something better.
Sometimes to inflate the product portfolio on a site or fill blog pages with articles... as with many topics outside of technology, we easily come across fake news.
We know the shape of these devices and some articles, but they are not available. Learn more on the page of KaiOS devices that you will never find on the market