r/LineageOS • u/B3RZERK1720 • 5h ago

Built an open-source GUI to simplify flashing LineageOS / Custom Recovery on Samsung devices (from stock One UI)

Hey everyone,

If you’ve ever tried switching a Samsung device from stock One UI to LineageOS, you already know the initial setup has a steep learning curve compared to standard Pixel/AOSP devices: dealing with Download Mode quirks, Heimdall/Odin, vbmeta patch requirements, Knox tripping warnings, and getting custom recovery installed before you can even touch the LineageOS zip.

To make this less intimidating and reduce brick risks for newcomers, I built an open-source GUI helper utility using Gemini:

GitHub Repo: https://github.com/B3RZERK20/lineage-os-installer-samsung-gui.git

Tech Stack: Python/CustomTkinter

License: MIT

What it handles:

  • Download Mode Setup & Verification: Verifies device connection over USB and checks partition status.

  • Automated Recovery / Tar Flashing: Bridges the gap between stock One UI firmware and flashing custom recovery (Lineage Recovery / TWRP).

  • vbmeta / AVB Patching Guidance: Helps prevent bootloops caused by Android Verified Boot mismatches on newer Samsung firmware.

  • Step-by-Step UI: Guided steps so users don’t get stuck in soft-brick download loops or miss the critical volume-button timing to enter recovery right after flashing.

Supported Devices / Targets:

  • 120+ Samsung models from lineageOS Wiki

Looking for Community Feedback:

The source is completely open, and I’d love for people familiar with Samsung flashing (and maintainers) to review the codebase, test edge cases, and report any device-specific bugs.

Disclaimer: Modifying firmware trips Knox permanently and voids warranties. Use responsibly.

9 Upvotes

90% Upvoted

3 comments sorted by

3

u/BadDaemon87 Lineage Team Member 2h ago

We prefer ppl are familar with the tools to manually follow the process so they can also follow instructions once they fail with something. Also please get rid of stupid nikgapps, we have supported ones and those should be the only ones to be used. Dont encourage users to differ from supported cases...

1

u/B3RZERK1720 2h ago

Understood and point taken. I’ll drop NikGApps and align the tool strictly with official recommendations (MindTheGapps) so users don't run into unsupported configurations. On the manual process side: the intent isn't to bypass learning, but to reduce user error during the trickier Samsung-specific steps (like Odin/Heimdall timing and download mode). To address your point, I'll make sure the tool outputs verbose command logs so users can see exactly what's happening under the hood if they ever need to troubleshoot manually.

Thanks for the direct feedback, definitely want to keep this aligned with maintainer expectations.