Rooting a Samsung Galaxy with Magisk: what still works in 2026
Short answer: most current Galaxy phones cannot be rooted. Since One UI 8, Samsung no longer lets you unlock the bootloader in any region, and installing One UI 8 relocks phones that were already unlocked. A Galaxy that is still on One UI 7 or older, and was not sold in the US or Canada, can still be rooted. This page shows how to tell which one you have, and the full method if yours qualifies.
Last updated 10 sourcesHow we check pages
One UI 8 and later: bootloader unlocking is gone
Samsung removed the OEM unlocking option from One UI 8 in all regions. That covers phones that shipped with it (Galaxy S26 series, S25 FE, Z Fold7, Z Flip7, Z Fold8, Z Flip8, Tab S11) and every older Galaxy once it installs One UI 8 or later. A Magisk contributor confirmed that Magisk cannot be installed on a One UI 8 bootloader, even if the phone was unlocked before the update. Samsung has not commented. If your phone is still on One UI 7 and you want root, do not update.
- Bootloader unlockOnly on One UI 7 or olderRemoved in One UI 8, 8.5 and 9
- US and Canada modelsNever unlockable
- Waiting periodUp to 168 hoursOnly if KnoxGuard shows Prenormal
- Data wipeYes, twiceWhen unlocking and on first install
- Knox warranty bitTrips permanently
- Updates with rootManual firmware flash only
Rooting a Galaxy: the whole job
- Step 1 · 5 minutesCheck that your Galaxy can still be unlocked
- Step 2 · 10 minutesUnlock the bootloader
- Step 3 · 20 to 40 minutesDownload the firmware for your exact model and build
- Step 4 · 5 minutesPatch the AP file in the Magisk app
- Step 5 · 10 minutesFlash in Download mode
- Step 6 · 5 minutesFinish setup and check root
Find your model
On Samsung the model matters less than the software it runs. Find yours to see whether it can be unlocked at all, then check the One UI version on your own phone in step 1.
-
Galaxy S26, S26+, S26 UltraLaunched withOne UI 8 or laterPatch / unlockAP file Not unlockable
-
Galaxy Z Fold8, Z Flip8Launched withOne UI 9Patch / unlockAP file Not unlockable
-
Galaxy Z Fold7, Z Flip7, Z Flip7 FELaunched withOne UI 8Patch / unlockAP file Not unlockable
-
Galaxy S25 FELaunched withOne UI 8Patch / unlockAP file Not unlockable
-
Galaxy Tab S11, S11 UltraLaunched withOne UI 8Patch / unlockAP file Not unlockable
-
Galaxy S25, S25+, S25 Ultra, S25 EdgeLaunched withOne UI 7Patch / unlockAP file Only on One UI 7
-
Galaxy S24, S23, S22, S21 (all models, including FE)Launched withOne UI 6.1 or olderPatch / unlockAP file Only on One UI 7 or older
-
Galaxy Z Fold6, Flip6 and older Fold and FlipLaunched withOne UI 6.1 or olderPatch / unlockAP file Only on One UI 7 or older
-
Galaxy A series: A56, A55, A36, A35, A26, A17, A16, A15 and olderThe A56, A36 and A17 5G received One UI 8 from September 2025. On MediaTek A models (such as A15 5G and A16 5G), users report losing 5G after unlocking.Launched withOne UI 7 or olderPatch / unlockAP file Only on One UI 7 or older
-
Galaxy Tab S10, S9 and older tabletsLaunched withOne UI 6 or olderPatch / unlockAP file Only on One UI 7 or older
-
Any Galaxy sold in the US or CanadaLaunched withModel codes ending in U, U1 or WPatch / unlockAP file Not unlockable
No match. The rule for every Galaxy: it can be unlocked only if it runs One UI 7 or older and is not a US or Canada model.
“Shipped with” is the One UI version the phone launched with. Phones that shipped with One UI 7 or older can be rooted only while they stay on One UI 7 or older. Status is from Magisk issue #9447, reporting by Android Authority, GSMArena and 9to5Google, and the community bootloader-unlock tracker.
Before you start
You will need
- A Galaxy on One UI 7 or older that was not sold in the US or Canada. Check this in step 1 before anything else.
- A computer with samloader-rs, the Samsung download and flash tool Magisk's guide now uses, plus adb from Google's Platform-Tools.
- A full backup. Unlocking wipes the phone, and the first Magisk install wipes it again.
- The Magisk app from the official GitHub release.
What you give up
- Knox, forever. Installing Magisk trips Knox's one-time-programmable warranty fuse. Samsung's Knox documentation says it cannot be reverted; only a mainboard replacement resets it.
- Samsung Wallet, Secure Folder and Knox features stop working permanently, even if you unroot and relock.
- Samsung Health. Samsung says it stops working when it finds root or unauthorised changes.
- Warranty and OTA updates. Samsung's warranty terms exclude rooted phones, and a rooted Galaxy cannot install updates over the air.
- One UI 8 and later. Updating relocks the bootloader and removes root, so a rooted phone stays on One UI 7.
Root your Galaxy step by step
Do step 1 first. If your phone fails it, stop: no tool, app or patched file gets around a locked Samsung bootloader.
-
Check that your Galaxy can still be unlocked
5 minutes- One UI version: open Settings → About phone → Software information. If One UI is 8.0 or higher, the bootloader cannot be unlocked. Stop here.
- Model code: in About phone, a model number ending in
U,U1orW(for exampleSM-S938U) is a US or Canada model, which cannot be unlocked. - Download mode check: Magisk's guide says to enable Settings → Device care → Maintenance mode, then boot into Download mode and read two lines:
- OEM Lock:
ON (L)is locked,ON (U)means OEM unlocking is enabled,OFF (U)is unlocked. No OEM Lock line at all usually means a US or Canada model. - KnoxGuard:
ActiveorLockedmeans a carrier or insurer has locked the phone remotely, and Magisk will not work.Prenormalclears after 168 hours of uptime.Checking,CompletedorBrokenare fine.
- OEM Lock:
-
Unlock the bootloader
10 minutes- Enable Developer options (tap Build number seven times) and turn on OEM unlocking. If the option is missing, your phone cannot be unlocked.
- Power off, boot into Download mode with your model's key combination, and long-press Volume Up to unlock. This erases all data.
- Set the phone up while connected to the internet, enable Developer options again, and check that OEM unlocking is present and greyed out. That confirms KnoxGuard did not lock it.
-
Download the firmware for your exact model and build
20 to 40 minutesDownload the firmware matching your model, region (CSC) and current build with samloader-rs, which fetches it directly from Samsung's servers. It must be the build you are running now, or a One UI 7 build with the same bootloader binary; Samsung blocks flashing firmware with a lower binary. Unzip it. You get five files:
BL,AP,CP,CSCandHOME_CSC. -
Patch the AP file in the Magisk app
5 minutesCopy
AP_*.tar.md5to the phone. In the Magisk app tap Install, choose Select and Patch a File and select the AP file. On a phone whose Magisk app shows Ramdisk: No, tick Recovery Mode first. Magisk patchesinit_bootorbootandvbmetainside the tar for you. Copy the result back with adb: Magisk's guide warns that MTP is known to corrupt large files.Copy the patched AP to the computer$adb pull /sdcard/Download/magisk_patched-XXXXX_YYYYY.tar -
Flash in Download mode
10 minutesBoot into Download mode and flash these four files together with samloader-rs, or with Odin if you already use it:
Slot File AP magisk_patched-XXXXX_YYYYY.tarBL BL_...from the same firmwareCP CP_...from the same firmwareCSC CSC_..., notHOME_CSC: the first install must wipe dataAgree to the factory reset if the phone asks for one.
-
Finish setup and check root
5 minutesSet the phone up, install the Magisk app and open it. Let it complete the additional setup and reboot. The Magisk card on the home screen should show a version number, for example
31.1 (31100); the App card's Installed line is the app's own version and doesn't prove root. If you ticked Recovery Mode, Magisk only loads when you boot through recovery's key combination.
Keeping root after updates
Updating within One UI 7
- 1Download the new firmwareSame model, One UI 7 only
- 2Patch the new APIn the Magisk app
- 3Flash in Download modeAP + BL + CP +
HOME_CSC - 4Boot and checkData kept, still rooted
A rooted Galaxy cannot take over-the-air updates. To update within One UI 7, download the new firmware, patch its AP again, and flash it with BL, CP and HOME_CSC, which keeps your data. Never flash a stock, unpatched AP on a rooted phone.
Flashing any One UI 8, 8.5 or 9 firmware relocks the bootloader and removes root. Users in Magisk's issue tracker report that going back to One UI 7 afterwards only works if the old firmware has the same bootloader binary, and that Samsung raised it on several models in 2026.
If the phone does not boot
Magisk's documentation is explicit: on Samsung, never restore only the boot, init_boot, recovery or vbmeta partitions to stock, as that can brick the phone. Recover by flashing the complete stock firmware (BL, AP, CP and CSC together) for your model, which wipes data. If a Magisk module caused the bootloop, try Safe Mode or removing modules first.
Errors and fixes
The messages people most often hit on this brand, and what they mean.
“Only official released binaries are allowed to be flashed”
The bootloader refused unsigned files. Either the bootloader is still locked, or KnoxGuard is Prenormal. Magisk's guide says Prenormal should clear after 168 hours of uptime. On One UI 8 or later there is no fix.
“Secure Check Fail: (VBMETA)”, (boot) or (init_boot)
You flashed a patched file onto a One UI 8 bootloader. In Magisk issue #9447, a Magisk contributor explains that Magisk cannot be installed on One UI 8 and that the only option is going back to One UI 7, which is possible only with matching bootloader binaries. Flash the complete stock firmware to boot again.
There is no OEM unlocking option in Developer options
Your phone runs One UI 8 or later, or it is a US or Canada model. Neither can be unlocked.
Download mode shows KG: Active or Locked
A carrier, retailer or insurer has locked the phone through Knox Guard. Magisk will not work until that lock is released by whoever set it.
The phone asks for a factory reset after flashing
Expected on the first install. Magisk's guide says to agree.
The bootloader relocked itself after an update
Installing One UI 8 or later relocks it, even if Settings still shows the phone as unlocked. Root cannot be restored on that firmware.
Questions people ask
Can you root the Galaxy S26 Ultra?
No. The S26 series shipped with One UI 8 or later, which has no bootloader unlock option in any region, so Magisk cannot be installed. The same applies to the Z Fold7, Z Flip7, Z Fold8, Z Flip8, S25 FE and Tab S11.
Can I root my S25 Ultra?
Only if it still runs One UI 7 and is not a US or Canada model. Once it installs One UI 8, the bootloader is relocked and root is no longer possible.
I unlocked before updating to One UI 8. Am I still unlocked?
No. Users and a Magisk contributor report that the One UI 8 update relocks the bootloader, even when Settings still says it is unlocked.
Can I downgrade to One UI 7 to unlock?
Only to a One UI 7 build with the same bootloader binary as your current firmware. Samsung blocks lower binaries, and users report that newer binaries now ship on many models, which closes this route.
Is there an unlock token or developer program?
No official one. Paid “unlock” services for US models only ever worked on firmware from before March 2021, and claims that unlocking returned in One UI 8.5 or 9 are unconfirmed.
Does unrooting bring back Samsung Wallet and Secure Folder?
No. The Knox fuse is a hardware e-fuse; Samsung's Knox documentation says it cannot be reverted.
Do I still need Odin?
Not for Magisk. Its guide now uses samloader-rs for both downloading and flashing on Windows, macOS and Linux. Odin still works for the same four-file flash if you already use it.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- Magisk installation guide: Samsung devices (topjohnwu)
- Magisk issue #9447: Magisk on One UI 8 bootloaders
- samloader-rs: Samsung firmware download and flash tool (topjohnwu)
- Samsung disables bootloader unlocking in One UI 8 (Android Authority)
- Samsung restricts bootloader unlocking on One UI 8 devices (GSMArena)
- One UI 8 removes the OEM unlock option (9to5Google)
- Samsung Knox: warranty bit cannot be reverted (Samsung Knox documentation)
- How Samsung Health protects your data (Samsung)
- Bootloader unlock status by brand: Samsung (community tracker)
- Galaxy A36 and A56 receive One UI 8 (GSMArena)
Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.
Report a problem with this page