Root My Galaxy: a KernelSU installer for a fixed list of Samsung firmware
KSU installer for supported Samsung Galaxy firmware with CVE-2026-43499
At a glance
- What is it?
- Root My Galaxy is a Kotlin Android app that installs KernelSU on Samsung models whose firmware and kernel version appear in a maintained payload catalog. It is a one-click tool with a deliberately narrow device list, and the README does not document rollback.
- Who is it for?
- Root My Galaxy fits owners of an explicitly supported Samsung model whose three-part kernel version matches a cataloged payload, and who accept that the README documents no unroot or rollback path. It is the wrong tool for anyone outside the catalog, for devices whose kernel version does not match, and for users who want to inspect the exploit before it runs, since the README states the app is kept separate from device offsets and native exploit payloads.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 15 days ago.
- What is it written in?
- Mainly Kotlin, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 18, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Root My Galaxy actually does
Root My Galaxy is a one-click installer for KernelSU on explicitly supported Samsung model and kernel combinations. That sentence from the README is the whole scope. The project is not a general rooting toolkit. It is a matching front end: you run it on a phone, it looks up a payload that fits, and it installs it.
The audience is narrow by design. You need a Samsung device whose model appears in the payload catalog and whose kernel version matches one of the entries. The README gives the matching rule directly: a kernel string such as 6.6.98-android15-8-... matches 6.6.98, meaning the comparison uses the three-part version, not the full build string. If your firmware was updated past the cataloged kernel, the app has nothing to offer you.
There is also a legal and ethical line in the README: use only on devices you own or are explicitly authorized to test. That is not boilerplate. The app installs KernelSU, which changes the trust model of the phone, and the payloads come from a separate repository.
How the payload catalog and matching work
The repository is split in two. This project holds the Kotlin application. Device offsets, native exploit payloads and KernelSU build artifacts live in a separate repository, Root-My-Galaxy-Payloads, which the README calls the device feed. That separation is the most interesting design decision here. It means the app can be updated without shipping new exploit code, and the payload repository can be updated without rebuilding the APK.
The runtime flow is a lookup. The app reads the phone's model and kernel version, filters the catalog by both values, and selects a matching payload. Advanced mode exposes the same catalog for manual selection, but the README notes it attaches model and kernel-version warnings, which is a fair hint that picking the wrong entry is a real failure mode rather than a theoretical one.
What the app does not do is visible in the same separation. The README says the application is kept separate from device offsets and native exploit payloads, so the APK you install is a selector and an installer, not the exploit itself. If you want to read the code that touches the kernel, the README points you to the payload repository, not this one.
Installing Root My Galaxy and running it once
The README documents building the app from source, not downloading a prebuilt binary. It points to the releases page for the latest release, and the build path below is copied from the README's Build section. Requirements as listed: Android Studio JBR 21, Android SDK 37, Android NDK 28 or newer, and CMake 3.22.1.
The README shows the Windows invocation. It sets JAVA_HOME to the Android Studio bundled JDK and calls the Gradle wrapper for the debug variant:
$env:JAVA_HOME='C:\Program Files\Android\Android Studio\jbr'
.\gradlew.bat :app:assembleDebugThe output path is given in the README:
app/build/outputs/apk/debug/app-debug.apkAfter installing that APK on a supported phone, the first real use is the matching step. Open the app, let it read the model and kernel version, and confirm the payload it selects. If you use advanced mode instead, the README says the catalog can be filtered by both model and kernel version and that manual selection carries warnings. The README does not describe what the screen shows after a successful install, so treat the absence of an error as the only signal it documents.
Where Root My Galaxy stops being the right tool
The supported-device list is the boundary, and it is enforced by the catalog rather than by a compatibility layer. A model that is not in the catalog gets nothing. A model that is in the catalog but running a newer kernel than any entry also gets nothing, because the three-part kernel version has to match. That is the most common way this tool fails for a real user: the phone is supported on paper, the firmware moved on, and the match is gone.
The second limitation is documentation. The README covers what the app is, how payload selection works, and how to build it. It does not document rollback, unrooting, or recovery from a payload that does not boot. For a tool that modifies the kernel of a phone, that is a significant gap, and it is a gap in the documentation rather than a claim about the code.
The third is trust. The README states the app is kept separate from device offsets and native exploit payloads, so reviewing the application does not mean reviewing the code that runs against the kernel. If your reason for rooting is control over what executes on your device, this split works against you.
How it differs from Magisk and manual KernelSU setup
Magisk patches the boot image and is distributed as a general tool with a module ecosystem; it does not ship a per-model payload catalog, and it does not match your phone against a list before doing anything. Root My Galaxy inverts that. It refuses to act unless model and kernel version both match a cataloged payload, which is why it can be one click and why it covers so few devices.
A manual KernelSU setup sits between the two. You obtain the KernelSU build for your device yourself, and you are responsible for knowing whether it fits your kernel. The difference is where the knowledge lives. With Root My Galaxy it lives in the payload repository and is consumed by the app. With a manual setup it lives with you. That makes the manual path more flexible and considerably more error-prone, and it is the path to take if your model is not in the catalog but you still want KernelSU.
Maintenance, licence and what a fork costs you
The repository is not archived, and the last push was on 2026-09-03. The most recent release listed is v0.2.65 from 2026-08-24, preceded by v0.2.6 on 2026-08-06 and v0.2.55 on 2026-08-03. Release numbering is irregular, so do not read the version string as a signal about how much changed; read the release notes instead.
The upgrade cost is structural. Because payloads live in a separate repository, keeping the tool useful means keeping the catalog current as Samsung ships new firmware. A fork inherits the app but not that maintenance. You would be maintaining device offsets and KernelSU build artifacts yourself, in a second repository, for every model you want to keep working.
The licence is Apache-2.0, which is permissive and includes an explicit patent grant. That covers the application code in this repository. It does not tell you anything about the payloads in the other repository, and the README does not state their licence. If you plan to redistribute a build, that is the question to resolve first, and it is not a question this repository answers.
Editorial conclusion
Root My Galaxy fits owners of an explicitly supported Samsung model whose three-part kernel version matches a cataloged payload, and who accept that the README documents no unroot or rollback path. It is the wrong tool for anyone outside the catalog, for devices whose kernel version does not match, and for users who want to inspect the exploit before it runs, since the README states the app is kept separate from device offsets and native exploit payloads. Before installing, verify that your exact model and kernel version appear in the payload catalog and check the repository's latest release notes.
Frequently asked questions
What is Root My Galaxy?
It is a one-click installer for KernelSU on explicitly supported Samsung model and kernel combinations. The app selects a payload whose model list and three-part kernel version match the phone, while device offsets and native payloads are kept in a separate repository.
Is Root My Galaxy safe?
The README states the app is kept separate from device offsets, native exploit payloads and KernelSU build artifacts, so the APK is not the code that runs against the kernel. It also says to use the tool only on devices you own or are explicitly authorized to test, and it documents no rollback path.
How do I root my Samsung Galaxy with Root My Galaxy?
Install the app on a phone whose model and three-part kernel version match a cataloged payload, then let it select and install that payload. Advanced mode filters the catalog by model and kernel version and allows manual selection, with warnings attached.
Can a rooted Samsung phone be unrooted?
The README does not document rollback or unrooting, so Root My Galaxy gives no procedure for it. The project's documented scope ends at selecting and installing a matching payload.
Is rooting my phone a good idea?
The README does not argue for or against rooting. It limits use to devices you own or are explicitly authorized to test, and it documents no way to reverse the install.
Is rooted device means hacked?
The README does not use that framing. It describes Root My Galaxy as an installer that selects a payload matching the phone's model and kernel version, and it does not discuss whether a rooted device counts as compromised.
Community notes