Your Guide To Updating/Modding Your Innioasis/Timmkoo Without Innioasis Updater

Recently, there's been a quite concerning trend. A program made entirely by AI has been officially adopted by Innioasis - it's called Innioasis Updater. It's a complete mess that the creator even admits was meant pretty much only to force Innioasis to use it, expressing extreme paranoia that they would choose to use something else and even threatening to use C2 against them. Here's the funny part, it's becoming much less "open source" in spirit, as he's now even been hired by Innioasis and even before then had a clear conflict of interest, with free device gifts that had nothing to do with his software. He even said that on Discord, we should curb negative talk specifically to please Innioasis, but I don't care about their opinion, nor their AIPAC-like donations. Unlike AIPAC, though, they're incredibly broke and can't even bother to pay $2500 of the $2500 they offered in a firmware, let alone the thousands in runner-up prises, they somehow cheaped out and paid $2000 on that too. Innioasis is nowhere near "open-source friendly" in the first place, so you can only imagine what the "dev" of the Updater did to get an in with them, they don't even correctly host firmware files for other devices than the Y1 and refuse to comply with GPL. You have to imagine even more, considering this: https://imgur.com/a/20llGKL. That being said, while a human, debloated rewrite is being made (Just on Windows, the original Updater is 1GB+ and comes bundled with site backups and even had non-consensual screenshot features at one point! Imagine!), I wanted to write this complete guide to help you install firmware on your device. Some users may think it's overly complicated, and some may ask why this is even happening. Here's why:

• Don't rely on GitHub API keys, as Innioasis Updater is notorious for rate limits that you just have to wait out. It's not exactly your fault you wanted to see what firmware there was.

• Maybe free up some space on your computer (especially on macOS, where users report it can be 6GB+!) 

• I've been C&D'd (on r/teenagers, after all) over this, but make what you will of the site's title. Do you really want that kind of software?

So, with that being said, let's first identify your device:

Note that some devices currently can't be modded, due to a lack of resources, a lack of knowledge of security measures, or unavailable kernel sources. For more info, join us at our Discord server .

Let's go ahead:

Setting up MTKClient

This will be the prerequisite to modding all of your devices. You never know if you have a new revision or if something will go wrong during the update! Let's go ahead and set it up for your OS:

Windows

1. Git clone https://github.com/bkerler/mtkclient, or click on Code > Download ZIP.

2. Extract the .zip to a directory where you can easily find it.

3. Download https://github.com/daynix/UsbDk/releases/download/v1.00-22/UsbDk_1.0.22_x64.msi. Install this and reboot.

4. Download https://www.python.org/ftp/python/3.14.3/python-3.14.3-amd64.exe.

5. Run python-3.14.3-amd64.exe.

6. Press Win+R. Type CMD and press enter. Run  pip install pyside6 pycryptodomex colorama pyusb pyserial

7. Shift + right click in the folder you extracted MTKClient to.

8. Select "Open PowerShell Window Here"

9. Run  python mtk_gui.py

10. Congrats! MTKClient works.

Linux (Debian used for guide)

1. Run sudo apt install python3 python3-pip build-essential adb git libusb-1.0-0 libfuse2.

2. Run python3 -m venv ~/.venv

3. git clone https://github.com/bkerler/mtkclient

4. cd mtkclient

5. ~/.venv/bin/activate

6. pip install -r requirements.txt

7. python3 ./mtk_gui.py

8. Congrats! MTKClient works.

macOS

1. Run /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

2. Run brew install python3 python3-pip build-essential adb git libusb-1.0-0 libfuse2.

3. Run python3 -m venv ~/.venv

4. git clone https://github.com/bkerler/mtkclient

5. cd mtkclient

6. ~/.venv/bin/activate

7. pip install -r requirements.txt

8. python3 ./mtk_gui.py

9. Congrats! MTKClient works.

Note: Steps may require tweaking, steps are based off of public instructions and could not be tested on a real Apple device.

Backing up firmware using MTKClient

This should be relatively simple to do, but there ARE some things to be aware of. For example:

• If you've truly rebooted after fully installing UsbDK, and the device is still failing to handshake, ensure that you're using the correct cable and that the device is off before you connect it over USB.

• Note: On some Dell machines, potentially other brands as well, you will need to use a small pin, bent paperclip, or bent staple (sim eject tool, etc.) to press your device's reset button multiple times while plugged in for it to connect. The reason for this is currently not known. You can find your reset pin location in your manual, usually.

• Depending on your hardware, this process can take upwards of an hour and does not back up your SD card. This is normal.

Follow the instructions on the MTKClient UI, aside from the volume button press or test point instructions, as these are not needed. Once connected, you should be able to go to the read tab, and from here, select all detected partitions, and output them to a folder. DO NOT unplug your device during this process! It can get stuck in preloader/BROM mode and may cause issues with battery calibration, and you will have to start the process over again. 

Once it fully backs up the files, you may notice they are named .bin. If you've worked with SP Flash Tool before, you may be very confused, but do not worry. .bin and .img files in this case, are entirely identical. .bin just stands for "binary", which is the raw partition itself. If you wish to use a scatter.txt provided by Innioasis alongside these files, you can rename all of them to have the extension .img, except for:

• logo.bin (this is .bin normally)

• lk.bin (this is also .bin normally)

• preloader_(your device platform).bin (this is, yet again, also .bin normally).

Ensure that your files are saved somewhere you won't easily delete or overwrite them. You might need them! 

Do I even need firmware?

Before we answer that question, it's important to address: What is firmware?

Normally, when people say "firmware", they mean the software that sits between the apps and the OS that you see and run and your hardware that handles basic functionality. And for some very simple devices,  or devices like desktop computers where updating your firmware can allow you to add certain new CPUs, updating your firmware can in fact add functionality. However, in this case, specifically for Innioasis/Timmkoo devices and similar, it's important to note that they use "firmware" quite loosely. Here, firmware (or sometimes "Software", as stated in our favorite AI slop tool Innioasis Updater) also includes the main Android OS and the apps in it, but in reality, most official updates don't actually update the security patch version or Android version. In fact, we're yet to see an official update from the company for the same revision of device that actually updates either the Android version or security patch version. Usually, it will just change things such as if Wi-Fi is enabled in the OS, certain icons, or in some cases, actual firmware updates that break compatibility with your device. 

For many, installing a firmware update might seem like it will solve all of your problems. In reality, unless you need specific features, or you recently installed firmware on your device that broke some sort of functionality on it, installing official firmware updates for the device is often more risky than good. Because of the fact that the OS is often over a decade old anyways, with unpatched vulnerabilities like Stagefright, normal update tips you may have heard elsewhere often don't apply here. 

In the case of custom firmware, which exists for a few devices, new features can be added, but before installing it, you should always fully read the documentation to see if you'd be okay with the known bugs, if it's compatible with your device or not, and most importantly, back up your firmware and any songs/media you have saved on the internal storage. This process doesn't touch your SD card, so you should not worry about losing files from your SD card... well, unless you have a Y1, but that can happen on stock firmware too. Of course, it's important to also note that installing custom firmware (or any mods in general) can void your warranty. I don't condone lying to Innioasis, but of course, it's a DADT policy, essentially.  If you've bought the device, and you're within the 30 day window, they won't replace it if you have modded it... and tell them about it. That's all I will say.

A short disclaimer about using mods

In any normal situation, mods shouldn't be (and aren't actually currently fully) supported by Innioasis. Despite linking to Rockbox, this is a side effect of our Carl Pei clout-chasing friend in Innioasis, in his own words, "shoehorning" it into the website and Innioasis Updater. Hell, they go as far as saying that using their theme system, that they set up to have user-accessible .zips, is actually an offense that warrants taking away your warranty! If you're thinking about buying these devices to mod them - don't. There are much, much better options on the market, and we have to mod these for a reason. Some examples are Fiio's Snowsky series, which is more open to modding, for those who want a more traditional "touch" experience for a cheap price, the HiBY R1, and for those willing to live on the edge and want streaming support, an LG V30 from eBay. They will all get significantly longer battery life, last longer, and most likely, even on eBay ironically, be better supported than Innioasis devices. If you're actually looking for an Innioasis/Timmkoo device, which... I highly doubt you are, then please keep your expectations realistic. Even with mods, their most powerful devices struggle with modern apps, and you most certainly won't get streaming support or normal applications on devices like the Timmkoo R1 or Q3. 

User-created mods are also subject to change. People have personal lives, people also have budgets that don't allow constant purchases of new Innioasis or Timmkoo device revisions in order to program custom firmware for them and maintain it all professionally.  So far, the Y1 is the only device in this family that has shown consistent moddability, even then, it has one scrollwheel-breaking hardware update you have to account for. If you have a "type B" or older Innioasis Y1, newer firmware that isn't explicitly marked as "Type B" will make it so that you cannot use your touch wheel. You are  doing this entirely at your own risk, hence the firmware backups.

That being said, let's get into it.

Innioasis Y1

If you're using this guide, you're almost certainly using the Y1, and why not after all? It's the most popular AND moddable of the bunch, got that "wannabe iPod that also smells vaguely of new Chinese sandals but also doesn't have an SD card slot"  feel as well. 

What do you get with mods for this device?

Currently, the two available software mods are Kidz-Y1 and Rockbox. If you don't know what Rockbox is, you probably shouldn't be messing with it, but (in theory), it's a highly themeable, audio-focused "OS". I say "OS", because your Y1 will still be running Android under it when you install it.  Kidz-Y1 is, well, a firmware that, in theory, is "for kids", but honestly, I think the fact that it allows you to organize your music in folders is pretty neat for all ages. It's also built on Android. There's one hardware mod, which involves switching out the SD card (they're notorious for crapping out, you'll likely need to do this at some point). There's a guide on Patreon that's free, and I'm not naming any names, but the person who made it seems to think that signing up for it just to get the guide so they can get your email in return is a fair deal. I might "pirate" the guide at some point for your privacy if you really want to look at it, but there's an iFixit guide as well, that's completely free to anyone: https://www.ifixit.com/Guide/Innioasis+Y1+SD+Card+Replacement/169710. 

Aside from "mods", there are stock OS themes for the Y1. Someone in our Discord server made a site where you can view these themes and play with them before you download them, and then go download them. You can check it out at https://y1-themes.vercel.app. If you want to check directly to a creator, you can check out willysjeepman's themes (https://willysjeepman.neocities.org/y1).

I want themes on the stock OS!

Okay, okay! Just go and download some, extract the zip, and copy the theme's extracted folder to Themes on your Y1! Note: When you enter the folder, there should not be another folder inside titled as the theme. Copy the folder directly containing the config.json and images to Themes. Not the content inside it by themselves, the folder. Boom.

Downloading firmware

The one, and possibly only, good thing to come from the Big Developer Sellout of 2025, was the standardization of ROM files. 

1. For Rockbox, download Rockbox from https://github.com/rockbox-y1/rockbox/releases/latest. Choose rom_240p.zip for better legacy Rockbox theme support, or rom_360p.zip in other cases. Choose the "type B" version if at first your Y1 doesn't control right with the regular (type A) firmware. 

2. For Kidz-Y1, download rom.zip from https://github.com/pcorbel/kidz-y1/releases/latest. Apparently there's no Type B support here?

3. If you're a boring normie that wants to update their stock firmware, download https://github.com/y1-community/y1-stock-rom/releases. Choose the "type B" version if at first your Y1 doesn't control right with the regular (type A) firmware.
   Note: In this case, the "updater" in Innioasis Updater is a bit of a misnomer. Yes, it does in fact update your Y1 "launcher" version, but to my knowledge, all of these releases are just Android 4.2.2. Don't expect magic like Android Auto or something like that.

Once you have this, extract the files, open MTKClient again if it isn't open already (Windows step 9, Linux steps 4-7) and reconnect the device according to the instructions shared in "Backing up firmware using MTKClient". Go to the write/flash tab, depending on the MTKClient version,  and select a folder to flash images from. Choose where you extracted the firmware to earlier. Wait until the flash is complete, and then unplug your Y1. Hold the center button until it turns on. Voila.

Innioasis G1

This is a device I see slightly more discorse of today than I see of many other devices. There's currently no custom firmware for it to my knowledge, but there is one mod, which allows you to gain temporary root access and install APKs. There's even a whole site for it: https://seph29.github.io/Lumos-G1/.  You can also install regular firmware on the G1, so if you just wanted stock firmware or you're not compatible with Lumos G1, you can check out:

1. https://drive.google.com/file/d/1A52h9tUZdrPUA9qo-hWRkJMAfWP2XkCS/view?usp=drive_link - German language firmware

2. https://drive.google.com/file/d/1cIhiE8XLntf5A_Y-nYKMbjV524lXB5Cu/view?usp=drive_link - English language firmware

3. https://drive.google.com/file/d/1_7za04kenfVeeSlPBxheAca1p87R__A0/view?usp=drive_link - French language firmware

Once you have this, extract the files, open MTKClient again if it isn't open already (Windows step 9, Linux steps 4-7) and reconnect the device according to the instructions shared in "Backing up firmware using MTKClient". Go to the write/flash tab, depending on the MTKClient version,  and select a folder to flash images from. Choose where you extracted the firmware to earlier. Wait until the flash is complete, and then unplug your G1. Hold the power button until it turns on. Voila.

Innioasis G3

Because the G3 is a lot more "open" than other devices, surprisingly, you can just install APKs after enabling "app installs" in Parental Controls in the Settings app. That being said, as long as your APK of choice is built for Android 8.1+ or under, and is ARMv8a, ARMv7a, or noarch, you can simply install it at this point. There are no Google services, however. This means apps like Google Play, Firefox, and Spotify (god knows how you get it on there) will be somewhat broken.  Some app stores like F-Droid and Aptoide are known to work on the device. There are no known custom firmwares for the device. However, you can install stock firmware to it.

1. https://drive.google.com/file/d/1ALhWrHxIHoCxwDxpRaWy572b1kY8KfsU/view?usp=drive_link - German language firmware

2. https://drive.google.com/file/d/15q1QuuBrbJcgXY5fmEyFDLFDKMTBXx-G/view?usp=drive_link - English language firmware

3. https://drive.google.com/file/d/1rlyN5oIiJK11DdO4qJ9xbv1vyK-JiFD2/view?usp=drive_link - French language firmware

Once you have this, extract the files, open MTKClient again if it isn't open already (Windows step 9, Linux steps 4-7) and reconnect the device according to the instructions shared in "Backing up firmware using MTKClient". Go to the write/flash tab, depending on the MTKClient version,  and select a folder to flash images from. Choose where you extracted the firmware to earlier. Wait until the flash is complete, and then unplug your G3. Hold the power button until it turns on. Voila.

Innioasis/Timmkoo Q5/Q3

The good news is that, in each generation, both are hardware-identical, meaning, in theory, you can cross-flash between Q5 and Q3 of the same generation. And that's where the good news ends, succinctly. Because there are so many random revisions of this hardware, which, in the latest run, has even seemingly introduced a front camera, it is imperative that you follow "Backing up firmware using MTKClient" as detailed above before continuing. Although, for a device that I've measured reaches over 170*F (76*C) on the back while charging and watching YouTube, I suppose one new revision could get lucky and maybe not burn your hand off, so... there's that. If you want to report what your device is or see if there's more custom firmware for it, you can go to https://timmkoo.de/, a fan-made project. If you're looking for more goodies from the guy who made that site, he's also made T-ROM for Y1s, although this isn't released yet. As for the firmware itself, this is where it gets very, very messy:

Modded

1. https://manufactory.carrd.co/ - 4th gen compatible mod, also 6th gen compatible (if you swap the screen from 4th gen) and has experimental 7th gen support. No Gapps, Android 5.0 (Note: Gapps are extremely slow and may not work fully)
   This custom firmware enables ADB by default (which you can turn off for security reasons), which you can use with SCRCPY. On top of that, you can install APKs, watch videos, etc.

2.  https://timmkoo.de/ - 4th/5th gen compatible mods available, may be down. 5th gen mods may need to be specially requested. Gapps or no Gapps, Android 5.0 (Note: Gapps are extremely slow and may not work fully)
   This custom firmware enables various things you might be used to in a polished Android device, like setup wizards, Settings rewrites, and Google Play Services support in some versions, with the tradeoff of it being slower. On top of that, you can install APKs, watch videos, etc.

3.  https://www.mediafire.com/folder/3r7zx6ssngrav/Beta - Lithium 4, Android 4 based, 3rd-gen compatible (and 4th gen, from what I've heard)
   Note: Lithium 5 does not work.
   This custom firmware is focused heavily on aesthetics, and while compatibility with older models is the main reason to install it, it features various theming tweaks and changed fonts. It is based on an older Android version than the other two, and you'll need to have a backup of your stock firmware or working Android 4.x firmware for your device installed before attempting to install it, as it only includes boot.img and system.img (no userdata, lk, logo.bin, cache.img, etc.)

Note: You cannot reliably tell what hardware revision you have and what mods are compatible with your device based on the kernel/build version shown in Settings. Some builds are used both on hardware and software navigation key-compatible firmware, but they are not compatible with each other. Please use physical characteristics instead. Sometimes, identifying what your device is can also be somewhat difficult, as Timmkoo supposedly discontinued the Q3, but it is still available for sale today, and it is not listed as a Q3 on Amazon, but it is on Innioasis' website. Yeah, it's screwed right now, I'm aware.

Stock

1. https://drive.google.com/file/d/1zKRbbNSqBTyBxraXYnFQH6D4MNdntV94/view - 3rd gen compatible stock firmware

2. https://drive.google.com/file/d/1D9KRQiKAC0XKGecnV0lhJRj0GV90Pcxa/view?usp=drive_link  - 4th gen compatible firmware

3. https://drive.google.com/file/d/1bZl_pC-ocwLaeZFziIiatOI28Ti7RMAp/view?usp=drive_link - 5th gen/MT6735 compatible firmware

4. https://drive.google.com/file/d/15pMSg8ZBoxin5Vp_EC1wC3KYf222RamI/view?usp=drive_link - More 4th gen compatible firmware

5. https://drive.google.com/file/d/16afQL1mLyDt8rXyQGmh4ygSAUN8Uj7ne/view?usp=drive_link - Q3 4th gen compatible firmware, English

6. https://drive.google.com/file/d/1HhGXigNdirkc9nc56W9_VwD_v6Mhrxjo/view?usp=drive_link - Q3 4th gen compatible firmware, English

7. https://drive.google.com/file/d/1HbLl3tmUSVeTf-nYcPQcN5bWGaTEOBdD/view?usp=drive_link - Q5 4th gen compatible firmware, German

8. https://drive.google.com/file/d/1qgTEiRcTQqoMkg6AgQ--Y1a_K5zjATfo/view?usp=drive_link - Q5 4th gen compatible firmware, German
   Note: Soon, firmware will be available via another method. Various links have been disabled by the owner and another method is being created to download firmware.

9. For more firmwares and mods, join https://discord.gg/3udBgrKgac. Links can be updated and added here more reliably.

Once you have this, extract the files, open MTKClient again if it isn't open already (Windows step 9, Linux steps 4-7) and reconnect the device according to the instructions shared in "Backing up firmware using MTKClient". Go to the write/flash tab, depending on the MTKClient version,  and select a folder to flash images from. Choose where you extracted the firmware to earlier. Wait until the flash is complete, and then unplug your Q3/Q5. Hold the power button until it turns on. Voila.

Android 7

Lithium 7 does... well, work, but you'll have to sweat for it. First, download https://github.com/NoahDomingues/Lithium/releases/download/v7.1.06.13.25/Lithium.Beta.v7.1.06.13.25.zip. You will also need to install T-ROM before doing anything. First, boot your device fully one time. Then shut it off. Connect your device to MTKClient as installed above in Setting up MTKClient, and flash the system.img, boot.img, and logo.bin from the extracted Lithium .zip file. Then hold Power and Volume Up until you enter TWRP, and in TWRP, tap on Wipe > Advanced Wipe. Tap on the cache partition and slide to confirm the wipe. Now go back home, and then go back to Wipe, then to Format Data, write "yes" and slide to confirm the wipe again. Now, go back home AGAIN and go to Wipe, and then factory reset. Then boot by pressing "Reboot to System", and wait anywhere from 6-15 minutes as it is booting for the first time as this will take longer than all subsequent boots. Voila. 

Timmkoo Q8

The Q8 is an interesting device. It's like a Galaxy Note 7, but instead of recalls, it just got a subtle rebrand. In its firmware architecture, it is also quite unique, seemingly lacking a settings apk despite Settings being present. It has not been modded, to my knowledge, yet. Still, stock firmware exists for it. Please, PLEASE back up your firmware using MTKClient before flashing firmware to the Q8, because we have very little info on its actual specifications. 

Stock

1. https://drive.google.com/file/d/1HdjASUlE9gMbuHR-93ZLVF4vTFve6BFc/view?usp=drive_link - Stock firmware, 1st gen compatible (?)

Once you have this, extract the files, open MTKClient again if it isn't open already (Windows step 9, Linux steps 4-7) and reconnect the device according to the instructions shared in "Backing up firmware using MTKClient". Go to the write/flash tab, depending on the MTKClient version,  and select a folder to flash images from. Choose where you extracted the firmware to earlier. Wait until the flash is complete, and then unplug your Q8. Hold the power button until it turns on. Voila.

Other devices

If you have other devices that were not listed here, such as the B6, S1, S6, etc. but were in the hardware table, this is because the device is currently completely unknown! Innioasis does not always provide firmware for devices, and in some cases, they are extremely unpopular. The B6 and Smart Player, for example, only exist in archive.org backups of Innioasis's website, which was never designed particularly well, but now we have some British joker in charge of it, so the nostalgia is granted. We are deeply sorry that there are no known mods at this time.

We also understand that sometimes it can be hard to tell what revision of device you have. That is why we always recommend you use MTKClient to back up your firmware to restore later if something goes wrong. 

Something went wrong / I want to go back

No worries. You did take a backup in MTKClient, right...? Right? Well, anyways, if you did, go back to "Backing up firmware using MTKClient" and repeat Windows step 9, Linux steps 4-7. Then, ensure your device is fully off. If you can't tell, refer to your manual (or one on https://device.report/ if you lost yours or got your device secondhand) for where the reset hole is, and insert a long, thin object into it, like a SIM eject tool, bent paperclip, or staple until you hear a click. Go to the write/flash tab, depending on the MTKClient version,  and select a folder to flash images from. Choose where you saved the firmware to earlier. Wait until the flash is complete, and then unplug your device. Hold the power button until it turns on. Voila.

If this doesn't work, try using the reset pin again. If it still doesn't work, try talking to customer support. (Note, we are a third party enthusiast group, not customer support). 

How do I install apps then?

Trust me, if you think you want Google Play, you absolutely don't, because the fastest device they offer uses a low-end chip from 2018, and let me remind you, that's their flagship device that costs nearly twice as much as the others. It supposedly has worse specs than the Galaxy A15, and the device is even lying about that. For all devices except the G3 and possibly G5, it actually won't support APK installs by default so you'll need to use a mod. Refer to the supported devices above. For the Q3, Q8, and Q5, your device will be ARMv7, and for the G1, G3, and G5, your device will be ARMv8. The G1 and G3 come with Android 8.1, while the G5 has Android 12.0, and the Q3 and Q5 have technically, theoretically worked with Android 7.1.2 before but the latest actually working custom firmware for it is Android 5.0 based, while they come with 4.4.2 by default. The Y1, on Rockbox firmware, can have APKs installed, but in reality, you know the issues with that, right? Either way, it has Android 4.2.2. The way this works is that if an app supports your android version or below it, and it works on your ABI (ARMv7 or noarch for ARMv7, ARMv7, ARMv8 or noarch for ARMv8), it will work in theory. Most sites will show that an app will support Android version (X)+, which does not mean you need a higher android version to run it. Based on this info, you can download an appropriate APK for the app you want from APKMirror,  at  https://www.apkmirror.com/. Once you have it on your device for all devices except the Y1, you can simply tap to install it and it should lead you through the settings you need to change to install the APK. In the case of some apps (.xapk, .apks, .sapk format) you will need SAI, or Split APKs installer, as they include extra data that a normal APK doesn't and cannot be installed normally. You can get this here at APKMirror. However, for the Y1, you need one extra step. For Windows, use this tool on GitHub to install ADB. On Linux, install android-tools-adb  (e.g. sudo apt install android-tools-adb ).  For Mac, use /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"  and then brew install android-tools-adb. So now, open your terminal of choice, plug in your Y1 while it's on, rename your APK to something simple without spaces you can remember, navigate using CD to the directory where you have the APK stored (usually downloads or the desktop) and type "adb install (name of your APK).apk". Boom! If it works, it should say so, and you now have an app on your Y1. This works on the other devices if you tap the build number in about device on modded firmware 7 times (not on stock firmware, they disabled developer options) and enable "USB Debugging" and authorize the debugging. Enjoy!

Credits

• Palutenfan123 for developing T-ROM, hosting certain firmware files, helping with guide info, and keeping timmkoo.de up to date

• Multiwirth for developing Rockbox-Y1

• Sarah G. Lato for developing Manufactory

• Noah Domingues for making Lithium and owning the Timmkoo Modders server

• pcorbel for developing Kidz-Y1

• Innioasis for (making? dropshipping?) these devices

• willysjeepman for Y1 themes, Y1 guides on Reddit

• Ryan Specter: Visit this site to see his accolades, truly a number that can't be used more than once, a legend

• Carlos Hernández Gómez for creating Y1 themes vercel app

• Dan, Kris Rodriguez, Abdullah Juwale, Jelly Bean Man (Y1 SD card replacement tutorial)

• Seph29 for developing Lumos G1, reverse-engineering Innioasis recovery cryptography

• Alrxñßë for archiving firmware for Q3/Q5 devices

This site is under construction! Tell us how to improve!