Credits / Who We Stand On
Everything we ship is GPL-3.0 and stands on the shoulders of people who shared first. Full credit, always.
Standing On Giants
Orbit (firmware downloader)
- samloader (nlscc) — the original open FUS downloader and the auth-param scheme.
- Bifrost (Zachary Wander) — the modern SmartDownload flow; auth_param.dat is bundled from Bifrost with attribution.
- SamFrew — catalogue and region research.
PolyQon (theming) - Iconify — GPL-3.0 theming engine; a direct porting reference for several tweaks. - Hex Installer — the app that defined One UI theming; we decoded its plugin model for research only — zero Hex code copied. - Repainter — Material You recolour research. - ColorBlendr (Mahmud0808) — the modern dynamic-colour approach.
RootForge (rooting platform) - KernelSU (weishu) + KernelSU-Next — kernel-side root done right. - Magisk (topjohnwu) + APatch (bmax121) — the other two frameworks we ship. - Qualcomm_Loaders (leefshitz2) — EDL loader collection.
Research that pointed the way - The GhostLock research ecosystem (NebuSec / CyberMeowfia, JoinChang, x-spy, YuKongA, BuSung-dev) — kernel exploit work we build on. - tryigit.dev — the SM8850 UEFI/GBL whitepaper: the bootloader-staging playbook. - ZeroPath — CVE analyses for the Qualcomm ABL bypasses. - Kaspersky ICS CERT — BootROM/Sahara research (KLCERT-25-012). - Calif — the OEMpocalypse strategy series. - Christopher Wade — "Breaking Mobile Bootloaders" (QPSS 2022). - Google Project Zero — years of in-the-wild Android chain writeups. - Quarkslab — Samsung boot-chain deep dives.
What Inspired Us
- The Hex Installer era — paid theming that eventually died. We wanted that power back, free and open.
- Iconify — proof that per-device theming can be open source.
- The old XDA glory days — custom ROMs, themes and root for everyone who wanted it.
- KernelSU's elegance — root that lives in the kernel instead of fighting the system.
- The modding community's unlock chains — proof that locked bootloaders aren't absolute.
- samloader + Bifrost — firmware access without vendor tools or accounts.
- Every user who ever bricked a phone on a wrong-file guide — we build so that stops happening.
Our Own Ideas (And Why They Exist)
-
PolyQon recolours via Samsung's official colour slots (
sem_color_primary,tw_color_control_activated,open_theme_*) — survives OTAs; no per-version hex patches. -
One UI 8.5 lockscreen clock via resource replacement — the old
KeyguardClockSwitchclass is gone in Compose, but the resources still load; replace the resource, not the class. -
QS columns via
settings put secure(qs_tile_column,sysui_qqs_count) — settings-level, no fragile runtime hooks. - The Xposed module skips child processes and installs once — kills the flaky double-hook problem.
- Fold-aware theming (folded/unfolded layouts + cover-display colour mapping) — One UI changes palettes per screen mode, so the theme has to follow.
- RootForge's "every method for this exact device" matrix — one wrong file can brick a phone; a ranked matrix can't.
-
Device-matched download ranking (arch + GKI + kernel scoring, best match first) — the wrong
.koor boot image is the #1 brick cause. - Bootloader unlock wizard for every brand — every brand has its own unlock ritual; one wizard, all the routes, with the risks stated.
- Orbit link inside RootForge (the firmware tab opens Orbit for your exact model + region) — firmware and rooting belong in one flow.
- Temp-root persistence (the su daemon survives until reboot) — one exploit run per boot instead of re-running constantly.
-
The unlock research (decoding the OEM-unlock gate stack and proving the bit-4
ablignores the flag entirely) — never trust a toggle; verify what the bootloader actually reads. - This encyclopedia — no central "this device, these methods" map existed. So we're building it, openly.
How We Credit
- Every port is source-verified and attributed in the repo + on the project page.
- We never copy code from closed tools — only facts and resource names, then write our own.
- If we missed you, tell us — it gets fixed the same day.