![\"A](\"https:\/\/www.newsbeep.com\/au\/wp-content\/uploads\/2026\/08\/Galaxy-S24-Ultra-S25-bench-scaled.jpg\"\/ "\\"Galaxy")
<\/p>\n<\/p>\n
Zac Kew-Denniss \/ Android Authority<\/p>\n
TL;DR<\/p>\n
A new open-source tool called \u201cRoot My Galaxy\u201d uses a software exploit to grant temporary root access on select Samsung Galaxy flagships.
\nThe tool works without wiping data, unlocking the bootloader, or tripping Knox, preserving features like Secure Folder, Samsung Wallet, and Play Integrity.
\nRoot access is temporary and must be reapplied on every reboot, and devices running newer security patches or Exynos chipsets are currently excluded.<\/p>\n
Modding modern flagship phones has become an increasingly uphill battle. Samsung hasn\u2019t been a stalwart in this space for a while, thanks to Knox, but the company went further and effectively killed bootloader unlocking on One UI 8<\/a> in several major regions. However, a developer has now released a new open-source tool called \u201cRoot My Galaxy\u201d that promises a simple, one-click rooting procedure without wiping data, unlocking the bootloader (!) or tripping Knox (!!).<\/p>\n Detailed by developer busung on XDA Forums<\/a> and hosted on GitHub<\/a>, the Root My Galaxy app functions as a KernelSU installer. Because it leaves the bootloader locked and doesn\u2019t blow the Knox e-fuse, features like Secure Folder, Samsung Wallet, and banking apps continue to work normally. Even Play Integrity remains intact, though some security-focused apps might detect the root-related apps that you may subsequently install.<\/p>\n The Root My Galaxy app\/tool works by exploiting CVE-2026-43499<\/a> (dubbed \u201cGhostLock\u201d), a recently discovered high-severity bug in how the Linux kernel manages system memory locks. When a lock operation fails and rolls back, the system cleans up after the wrong process. This leaves behind a \u201cghost\u201d pointer referencing memory that has already been freed, usually referred to as a \u201cUse-After-Free\u201d flaw. The exploit hijacking this leftover memory space allows the Root My Galaxy tool to take control of kernel memory and directly inject KernelSU privileges.<\/p>\n This is a software-level kernel exploit and acts as a \u201csoft\u201d root, meaning root privileges are temporary and must be reapplied manually after every phone reboot. That\u2019s great for not tripping Knox at the hardware level, but it does introduce some repetitive labor to keep root active (but the few steps are a small price to pay)<\/p>\n Developer busung mentions the tool runs on June 2026 security patches and older, but community members like thatjoshguy69 on X<\/a> have had luck with the exploit running on July 2026 patches, too. There\u2019s a very high chance that Samsung will patch the exploit with the August 2026 security patches, so advanced users should make hay while the sun shines. With root access, you can explore system-level adblockers, remove pre-installed bloatware, try out advanced automation tools like Tasker, and go even deeper into customization with ZygiskNext and LSPosed.<\/p>\n What devices does Root My Galaxy support?<\/p>\n Because kernel memory addresses vary across hardware and builds, the exploit relies on specific memory offsets maintained in the Root My Galaxy Payloads repository<\/a>.<\/p>\n Supported hardware currently includes mainly Snapdragon-based Samsung flagships:<\/p>\n Fully Working: Galaxy S25 Ultra Galaxy S25 You may notice the Galaxy Z Flip 7 is not mentioned in the list, as it uses an Exynos processor. Exynos variants of the above-mentioned devices are also not currently supported by Root My Galaxy, as the developer\u2019s current work targets Snapdragon devices due to architectural differences. This doesn\u2019t rule out future support, but currently, nothing is in the pipeline for Exynos.<\/p>\n The Galaxy S26 series is also missing from the list, as these phones launched with a newer kernel build that does not leave room open for the exploit. As a result, these devices are inherently immune to this specific memory injection payload and will likely never support Root My Galaxy.<\/p>\n How to use Root My Galaxy to temporarily root your recent Samsung flagship?<\/p>\n Using the app is fairly straightforward, though success can take a few attempts:<\/p>\n Ensure your Samsung Galaxy phone is running the June 2026 security patch or an earlier version, preferably on the stable One UI 8.5 build. Your luck may vary with the July 2026 patch. Note that some memory injection processes use brute-force methods, so you may encounter failures even on supported devices. Retrying has yielded results for some users.<\/p>\n That being said, should you rush to root your Galaxy phone? No, not really.<\/p>\n While having root access is great, you don\u2019t have an unlocked bootloader (!!!). This is good for preventing security-focused apps on your phone from breaking, but it\u2019s horrible if you ever break a key software component and brick your phone. Without an unlocked bootloader, you have practically zero chance of reviving your phone without lucking out on a future exploit. Rooting with the current exploit also doesn\u2019t open up custom ROMs on its own, either, as you\u2019d still need an unlocked bootloader to flash any custom ROMs or kernels. You will also have to forego future software updates, which isn\u2019t a good idea in the long run.<\/p>\n Given the relatively narrow firmware window, the need to re-run the app on every boot, and other drawbacks, Root My Galaxy isn\u2019t a complete replacement for a permanently unlocked bootloader. However, for Galaxy owners stranded on locked firmware who miss root access, it\u2019s currently the only way out.<\/p>\n
\nPorting\/Testing in progress:<\/p>\n
\nGalaxy S25 Plus
\nGalaxy S25 Edge
\nGalaxy S24
\nGalaxy S24 Plus
\nGalaxy S24 Ultra
\nGalaxy S24 FE
\nGalaxy Z Fold 7<\/p>\n
\nDownload and install the latest version of the app from the official GitHub repository<\/a>.
\nOpen the app. It will automatically match you to the right build for your device and firmware. If the exact build and firmware for your device are not auto-detected, there\u2019s an Advanced Mode that lets you manually select matching kernel profiles.
\nFollow the in-app instructions to initiate the exploit process. The app will run the payload in memory to elevate privileges and inject the KernelSU manager.<\/p>\n