FAQ

A free web app that indexes custom ROMs, recoveries, root tools, and guides for 946+ Android devices. Data is pulled live from 20+ public sources. No account needed, no ads, no paywalls.

Completely free. No subscription, no paywall, no ads. MIT licensed and open source on GitHub.

An independent developer who was frustrated by having to check 6 different sites to find what was available for a device. Source code is on GitHub. No company, no team, no funding.

No. Independent project. We read their public APIs the same way a browser would. No partnership, no endorsement from any of them.

No. Completely separate projects that happen to share a name. The F-Droid Droidify is an Android app store client. This Droidify is a web-based ROM and recovery indexer. Different product, different function, different team, no affiliation.

Cold start after a deploy. The server fetches live data from 20+ sources simultaneously. Usually takes 1–2 minutes. After that everything is cached and fast. Refreshing fixes it.

Most sources every 2 hours. Stock firmware every 24 hours. Android versions refresh every hour.

Links go directly to the original project’s servers — LineageOS mirrors, OrangeFox CDN, TWRP’s own servers, GitHub Releases, SourceForge. Droidify is never in the path between you and the file.

Yes. github.com/eliekh05/Droidify. MIT license.

Open a GitHub issue at github.com/eliekh05/Droidify/issues. Templates are provided for bugs, missing data, new ROM sources, and takedowns.

That comes from the ROM developers, not Droidify. The version shown is pulled directly from whatever metadata the developer included when they uploaded the build. Some put the target SDK level instead of the Android version number. Some leave it blank. Some put placeholder values. Droidify shows the raw value honestly rather than guessing.

Yes. Docker setup is included. Clone the repo, set your environment variables, and run. The README has the full setup. You’ll need to provide your own GitHub OAuth credentials.

Open the site in Chrome or Edge — tap the install prompt that appears automatically. Or download the APK from GitHub Releases and sideload it.

Samsung devices on One UI 6.1.1 or later have Auto Blocker on by default. Fix:

1. Settings → Security and Privacy → Auto Blocker → Off
2. Settings → Apps → Install unknown apps → allow your browser
3. Open the APK and install
4. You can turn Auto Blocker back on after — it won’t affect apps already installed.

Or skip the APK entirely and install from Chrome or Edge — no Auto Blocker issue.

Open in Safari → tap Share → tap “Add to Home Screen”. Has to be Safari — Chrome and Firefox on iOS cannot install PWAs.

Open in Chrome or Edge and use the install icon in the address bar. Or download Droidify.msix from Releases.

Yes. The warning appears because the package is not signed through the Microsoft Store. Click “More info” then “Run anyway”. Source code is public. For no warnings at all, use Chrome or Edge to install from the browser instead.

Open in Chrome or Edge and use the install icon in the address bar for a clean chrome-free window. In Safari, File → Add to Dock — but Safari always shows a toolbar inside the app, Chrome and Edge don’t.

A TWA (Trusted Web Activity) — a thin native shell that opens the website full screen with no browser address bar. The APK contains almost no code. When the site updates, the app updates automatically. No new APK needed for any content or feature change.

No. Everything works without signing in. Signing in with GitHub only adds the watchlist and ROM alerts.

Unlocks the watchlist (save up to 20 devices) and ROM alerts (badge when new builds drop for your saved devices). We read your public GitHub username and avatar. No email, no private data, no posting on your behalf.

Use the “Delete account” button in the navbar when signed in. It removes your profile, watchlist, and all alerts immediately. To also revoke GitHub’s access token: github.com → Settings → Applications → Authorized OAuth Apps → Droidify → Revoke.

Possible reasons: the ROM only exists as a forum post or Google Drive link which can’t be indexed automatically, the cold start cache hasn’t populated yet (try refreshing), the device has no custom ROM support from any indexed source, or you searched a marketing name instead of the codename. Open an issue with the codename and download URL if something should be there.

Some sources don’t include which Android version a build targets. We show “unknown” rather than guess.

An internal name manufacturers use during development, like beryllium (Poco F1), bluejay (Pixel 6a), or j7elte (Galaxy J7 2015). ROM projects use codenames because marketing names vary by region but the hardware is the same. Search by codename for the most accurate results.

Search your device model number on the Devices page. Or search “[device name] codename” on XDA Developers — it’s usually in the forum thread title.

Manufacturers release the same device with different hardware for different regions or carriers. The Snapdragon and Exynos variants of a Galaxy S are different codenames even though they look identical. ROM support differs between variants.

LineageOS API, LineageOS Wiki, OrangeFox CDN, TWRP search.json, Wikipedia, crDroid, SourceForge, GrapheneOS, postmarketOS, DivestOS, CalyxOS, /e/OS, Ubuntu Touch, NetHunter, customrombay.org, SamFW, and GitHub Releases.

Devices are indexed from the sources above automatically. If a device is missing it means none of the sources have data for it. If a specific ROM exists for your device but isn’t showing, open a GitHub issue with the codename and the direct download URL.

A version of Android built by community developers instead of your manufacturer. Examples: LineageOS (clean Android, wide device support), GrapheneOS (privacy and security, Pixels only), crDroid (feature rich), /e/OS (Google-free), CalyxOS (privacy with microG).

Replaces the stock recovery partition. Lets you flash ZIP files, make full backups, and wipe partitions. Usually the first thing you flash after unlocking the bootloader. Common ones: TWRP, OrangeFox, PBRP, SHRP.

Getting superuser access — like administrator on Windows. Lets you modify system files, remove bloatware, and run apps that need deep access. Main tools: Magisk (most compatible), KernelSU (kernel-level), APatch.

The bootloader runs first when you power on the device. By default it only allows manufacturer-signed software. Unlocking it lets you flash anything. Unlocking completely wipes your device. On some devices and carriers it cannot be unlocked at all.

On most devices yes. Google Pixels allow re-locking to restore the security state. Samsung Knox trips permanently the moment you unlock — no way back.

Knox is Samsung’s security platform. The moment you unlock the bootloader on a Samsung device, Knox trips to 0x1 permanently. Samsung Pay, Secure Folder, Knox Workspace, and Samsung Pass stop working forever. If any of those matter to you, do not unlock the bootloader.

Depends on the ROM and root setup. Stock-based ROMs often pass Play Integrity. Magisk with Shamiko can hide root from some apps. GrapheneOS has sandboxed Google Play. Check the ROM’s XDA thread for reports specific to your device.

Google’s system for verifying a device is unmodified and running certified software. Apps like banking, streaming, and games use it to refuse running on rooted or modified devices. Some ROMs and root setups can pass it, others cannot.

A full image backup of your device’s partitions taken from custom recovery. Lets you restore the exact state of your device if something goes wrong. Always make one before flashing anything. It is the only way to fully undo a flash.

ADB (Android Debug Bridge) communicates with Android over USB. Fastboot flashes images at the bootloader level before Android boots. Both are part of Android SDK Platform Tools available free from Google.

Emergency Download Mode — a Qualcomm-specific low-level mode for flashing firmware directly to the device even when it won’t boot. Used to recover hard-bricked Qualcomm devices.

Making a device unable to boot. A soft brick can often be recovered from recovery or fastboot. A hard brick means the device won’t respond at all. Flashing the wrong file for the wrong variant is the most common cause.

Google Apps — Play Store, Gmail, Maps, etc. Most AOSP ROMs don’t include them for licensing reasons. Flash a GApps package (MindTheGapps or NikGapps) separately if you want Google services. GrapheneOS and /e/OS have their own approaches.

All AOSP-based. LineageOS is the foundation — minimal, stable, widely supported. crDroid adds many customization options. EvolutionX is feature-rich with a Pixel-like aesthetic. Stability varies by device and maintainer.

A privacy and security hardened Android OS. Supports only Google Pixel devices. The most secure Android ROM available. Ships without Google Play — requires manual setup for apps.

A Linux-based OS for Android devices, not Android itself. Designed to give old phones a second life. Support is partial on most devices — calling and mobile data often don’t work. Aimed at developers and tinkerers.

A fork of LineageOS with enhanced privacy and security hardening. Supports many older devices that LineageOS has dropped. Good middle ground between LineageOS and GrapheneOS for non-Pixel devices.

A privacy-focused Android OS that includes microG as a Google Play Services replacement, allowing most Google Play apps to work without a full Google account. Supports Pixels and a small number of other devices.

A Google-free Android OS based on LineageOS with its own app store and cloud services. Aims to be a complete de-Googled daily driver. Supports a wider range of devices than GrapheneOS or CalyxOS.

Magisk patches the boot image to gain root without modifying the system partition. KernelSU implements root at the kernel level. Magisk is more compatible with older devices and more apps. KernelSU is harder to detect and better for newer Pixel/flagship devices.

A newer root solution similar to KernelSU but with broader device support. Patches the Android kernel directly. Growing in popularity as an alternative to both Magisk and KernelSU on devices where those don’t work well.

A number Google assigns to each Android release to identify its SDK version. Developers target a specific API level when building apps. API 35 = Android 15, API 36 = Android 16, API 37 = Android 17. The API level is more precise than the version name because it doesn’t change with minor updates.

Google dropped public dessert codenames after Android 9 Pie and switched to plain numbers starting with Android 10. Internal codenames still exist (Baklava, Cinnamon Bun) but aren’t marketed publicly anymore.

A release between Android 12 and 13 focused on tablets and foldables. API level 32. Most people never heard of it because it shipped on very few consumer devices. It is listed on the Android versions page.

As of 2026: Android 14, 15, 16, and 17 receive Google security patches. Android 13 reached end of life on March 2, 2026. Everything below is unsupported by Google — some manufacturers and custom ROMs still patch older versions independently.

Android 17, codenamed Cinnamon Bun, API level 37. Released June 16, 2026. Currently the latest stable Android release.

If you never sign in: nothing. No cookies, no analytics, no tracking, no fingerprinting. If you sign in: your GitHub username, avatar URL, and numeric ID. Your watchlist of up to 20 codenames. One session cookie. That is the complete list.

No. No advertising networks, no analytics platforms, no social media pixels. The only external service involved is GitHub OAuth when you sign in and jsDelivr CDN for the stylesheet.

Use the “Delete account” button in the navbar when signed in. Removes everything instantly. To also revoke GitHub’s OAuth access: github.com → Settings → Applications → Authorized OAuth Apps → Droidify → Revoke.

Yes. Open a GitHub issue with the device codename and the ROM’s public download URL or API endpoint. Single-file Google Drive links and forum posts cannot be indexed automatically.

Open an issue before writing any code. Unsolicited pull requests are closed without review. Describe what you want to fix or add and why first.

Yes. Open a takedown request with the project name and the URL on Droidify. Removed within 48 hours, no questions asked.

If your project is publicly accessible via one of the sources Droidify already indexes (LineageOS, OrangeFox, TWRP, SourceForge, GitHub Releases, etc.) it should appear automatically. If it doesn’t, open a GitHub issue with the API endpoint or structured download URL.