Can your phone be rooted? Magisk guides by brand
Whether a phone can be rooted comes down to one thing: can its bootloader be unlocked? In 2026 the answer depends heavily on the brand. Pick yours for an up-to-date status, a model finder and step-by-step instructions.
Last updated 3 sourcesHow we check pages
Samsung no longer allows rooting on current software
Samsung removed bootloader unlocking in One UI 8, so the Galaxy S26, Z Fold7, Z Fold8 and any Galaxy updated to One UI 8 cannot be rooted. See the Samsung page for what still works.
The short version
Every phone is rooted the same basic way: unlock the bootloader, get the stock firmware for the exact build installed, patch the right image with the Magisk app, and flash it. What differs between brands is whether and how you can unlock, where the firmware comes from, and which image to patch.
Pick your brand
Google Pixel
UnlockableOne fastboot command, no waiting period. Patch init_boot.img on Pixel 7 and newer.
Samsung Galaxy
Blocked on One UI 8+Samsung removed bootloader unlocking in One UI 8. Only Galaxy phones still on One UI 7, outside the US and Canada, can be rooted.
Galaxy guide →OnePlus
UnlockableFastboot unlock, no wait on global units. Extract init_boot.img from payload.bin. Do not downgrade the 13 or 15.
Nothing and CMF
UnlockableFastboot unlock, no wait, no regional locks found. init_boot.img on everything newer than Phone (2).
Xiaomi, Redmi and POCO
Approval neededCommunity app application, a 30-day-old account and a 72-hour or longer wait. China-region phones cannot be unlocked.
Xiaomi guide →Motorola
Code requiredUnlock code from Motorola, warranty void, no carrier models. The image to patch varies by model.
Motorola guide →How the brands compare
Status as of October 2026. Each brand page cites its sources.
Rooting by brand at a glance
| Feature | Pixel | Samsung | OnePlus | Nothing | Xiaomi | Motorola |
|---|---|---|---|---|---|---|
| Bootloader can be unlocked | PartlyNot Verizon | PartlyOne UI 7 or older, not US or Canada | Yes | Yes | PartlyAfter approval; not China models | PartlyNot carrier models |
| No waiting period | Yes | NoUp to 168 h | PartlyT-Mobile: 1 to 2 weeks | Yes | No72 h to 30 days | PartlyCode by email |
| Official firmware download page | YesFactory images | PartlySamsung servers, via the samloader-rs tool | PartlyNo public page; Oxygen Updater (unofficial app) | PartlyNo public page; community archive | YesFastboot ROMs | YesRescue and Smart Assistant |
| Keeps root through updates | Yes | No | PartlyA/B method | PartlyA/B method | PartlyUnreliable | PartlyNot advised |
| Unlocking leaves no permanent mark | Yes | NoKnox warranty bit trips for good | Yes | Yes | Yes | NoWarranty void for good once the code is issued |
| Brand | Unlock | Wait | Firmware | Patch | Updates with root |
|---|---|---|---|---|---|
| Google Pixel | fastboot flashing unlock | None | Google factory images | init_boot (7+) / boot | Yes, Install to Inactive Slot |
| Samsung Galaxy | Download mode, only on One UI 7 or older | Up to 168 h (KnoxGuard) | samloader-rs (Samsung servers) | Whole AP file | No, manual firmware flash |
| OnePlus | fastboot flashing unlock | None (T-Mobile: 1–2 weeks) | Full OTA zip, payload.bin | init_boot (11+) / boot | Yes, Install to Inactive Slot |
| Nothing and CMF | fastboot flashing unlock | None | OTA payload.bin or community archive | init_boot / boot on (1), (2) | Yes, Install to Inactive Slot |
| Xiaomi, Redmi and POCO | Community app application + Mi Unlock | 72 h to 30 days | Fastboot ROM (.tgz) | init_boot (check) / boot | Unreliable; reflash ROM |
| Motorola | Code from Motorola's website | Email (toggle: up to a week) | Rescue and Smart Assistant | Varies: check firmware | Possible, not advised |
Which image do I patch?
- YesPatch the whole
AP_*.tar.md5file. See the Samsung guide. - NoMagisk app shows Ramdisk: Yes?
- NoPatch
recovery.imgwith Recovery Mode ticked. See the installation guide. - YesDoes the firmware contain
init_boot.img?- YesPatch
init_boot.img - NoPatch
boot.img
- Yes
- No
init_boot; phones updated to 13 keep their old layout.Not sure what your firmware contains? The root method checker walks you through these questions and gives you the flash command for your answers.
Launch Android version is only a rule of thumb. We read the partition lists of 79 official updates (Pixel, Xiaomi, Redmi and POCO, Nothing) and found phones that launched with Android 13 or 14 but have no init_boot, such as the POCO F5 and several Redmi Note models. Each brand guide lists the image per model.
Phones that cannot be rooted
If a phone's bootloader cannot be unlocked, Magisk cannot be installed on it. No patched image, app or website gets around this. In 2026 that includes Samsung phones on One UI 8 or later, US and Canada Samsung models, China-region Xiaomi phones, Verizon Pixels, and carrier Motorola models from Verizon, AT&T and Tracfone. If you only need some root-like features, Shizuku works without unlocking.
Sources
This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.
- Magisk installation guide (topjohnwu)
- Generic boot partition and init_boot (Android Open Source Project)
- Bootloader unlocking by manufacturer (Wikipedia)
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