How to get root access to Samsung: 3 proven methods with a guarantee of security

Obtaining root-rights on smartphones Samsung opens access to hidden Android functions, but requires caution: incorrect actions can turn your Galaxy S23 or Galaxy A54 into a “brick”. This article contains current methods for modern devices (including models with One UI 6.0), analysis of risks and step-by-step guide taking into account the features of firmware Samsung.

We analyzed forums XDA Developers, user reviews and official warnings from the manufacturer in order to collect only working solutions. Important: the procedure will void the warranty and may block Samsung Pay/Knox. If you are ready for this, read on.

What root access give on Samsung and when they are needed

Root (or “superuser”) allows you to:

• 🔧 Delete built-in applications Samsung (Bixby, Samsung Free etc.) without disconnecting through ADB
• 📱 Install custom firmware (LineageOS, Pixel Experience) and kernels to improve performance
• 🔋 Optimize battery performance using Greenify or Battery Charge Limit
• 🛡️ Systematically block ads via AdAway or Blokada
• 📡 Overclock the processor/GPU (at your own risk!) for games like Genshin Impact

When you should NOT get root:

• ⚠️ If you use Samsung Knox (working with corporate data, Secure Folder)
• 💳 With active use Samsung Pay (stops working)
• 🔄 If you plan to sell the phone, reset the counter Knox impossible

⚠️ Attention: On devices with Exynos 990 (for example, Galaxy S20 Ultra) and newer, some methods may not work correctly due to hardware protection RMM. Before starting, check the processor model in Settings → Phone information → Hardware information.

Preparation of the phone: 5 mandatory steps before rooting

Unpleasant surprise: up to 30% of unsuccessful attempts to get root are associated with improper preparation. Follow the checklist to avoid the “brick”:

Data backup (photos, contacts, SMS)

Battery charge ≥ 70%

Installing the original USB cable (not wireless charging!)

Disabling OEM locking in the developer settings

Checking the model and firmware version (for example, SM-S901B/DS, One UI 5.1)

-->

The most critical point - OEM unlocking. Without this, no method will work. How to enable:

1. Go to Settings → About phone → Software information
2. Tap 7 times Build numberto activate Developer mode
3. Return to the main settings menu, open Developer options
4. Find option OEM Unlock and enable it (if there is no item - see spoiler below)

adb shell settings put global oem_unlock_supported 1

Critical detail: on devices with Android 12+ and One UI 4.0+, OEM unlocking is reset after a reboot. You will have to enable it again before each attempt to root.

Method 1: Root via Magisk (without PC) - for firmware with patch

This method is suitable for devices with One UI 3.1–6.0, where the kernel is not locked by hardware (for example, Galaxy A52, Galaxy S21 FE). The main advantage is that a computer is not required.

Algorithm:

1. Download the latest version Magisk.apk with official GitHub (check the file hash!)
2. Install APK as a regular application
3. Download patched boot.img for your model (look on XDA or in telegram channels like @SamsungFirmware)
4. B Magisk select Install → Select and patch the file and specify downloaded boot.img
5. After patching, move the file magisk_patched.img to the root of the internal memory
6. Reboot into Download Mode (turn off the phone, hold Volume up + Volume down, connect the USB cable)
7. Flash the patched file through Odin (see Method 2, steps 4–6)

⚠️ Attention: If after rebooting the phone is stuck on the logo Samsung, then boot.img is not suitable for your firmware. Do not try to reflash again - use Combination Firmware to restore (instructions in the next section).

adb shell getprop ro.bootloader

Compare the output with the name of the boot.img file (for example, s906bxxu2awg1 should match with boot-s906bxxu2awg1.img).-->

Method 2: Classic root via Odin + TWRP (for experienced)

This method is universal for most models Samsung, but requires a PC with Windows and knowledge of the command line. Suitable for Galaxy S10–S23, Note 10–Note 20, Galaxy Tab S.

You will need:

• 🖥️ A computer with installed drivers Samsung USB Drivers (download from official site)
• 📁 app Odin3 v3.14.4 (only this version works stably with new devices)
• 📄 Files:
  • TWRP-3.7.0_9-0-yourmodel.tar (for example, TWRP-3.7.0_9-0-d2xq for Galaxy S22+)
  • Magisk-v26.4.zip (not APK!)
  • multidisabler-samsung-3.1.zip (to disable forced encryption)

Step-by-step guide:

1. Turn off the phone and hold down Volume up + Volume down + Powerto enter Download Mode. Confirm by pressing Volume up.
2. Connect the phone to the PC Odin a message should appear Added!! v. log.
3. In Odin click AP and select the file TWRP. Leave the remaining fields (BL, CP, CSC) empty!
4. Uncheck the Auto Reboot and press Start. Wait for the message PASS!.
5. Without disconnecting the cable, press Volume down + Power for 10 seconds to exit Download Modeimmediately press Volume up + Power. to enter TWRP.
6. V TWRP select Wipe → Format Data, enter yes and confirm. This will remove the encryption!
7. Go to Install and flash first multidisabler-samsung-3.1.zipthen Magisk-v26.4.zip.
8. Reboot. The first launch may take up to 15 minutes.

Method 3: Root via patched firmware (for new ones) models)

For devices with Exynos 2200/Snapdragon 8 Gen 2 (for example, Galaxy S23, Galaxy Z Fold 5) classical methods often do not work due to protection RMM and KnoxGuard. The solution is to use patched firmware from the community.

Instructions:

1. Download full firmware for your model from the site SamFW or SamMobile (select region XAA or XXV for minimal bloat).
2. Unzip the firmware and find file AP_[model]...tar.lz4.
3. Download LZ4 Tool and unpack the APfile with the command:

   lz4 -d AP_S918BXXU1AWG5.tar.lz4 AP_S918BXXU1AWG5.tar

4. Extract from the archive boot.img.lz4 and unpack it in the same way.
5. Patch boot.img via Magisk (as in Method 1).
6. Pack it back into tararchive with the original structure.
7. Flash via Odin (in the field AP) together with the original BL, CP i CSC (not HOME_CSC!).

⚠️ Attention: On devices with Snapdragon (for example, Galaxy S23 Ultra SM-S918U for the USA) this method may not work due to a blocked bootloader. For such models, the only option is exploits like DirtyPipe, but they are temporary and require re-use after a reboot.

How to check the success of rooting and fix it errors

After reboot, check the root status:

1. Open Magisk - if you see a green checkmark and version, root has been received.
2. Install Root Checker from Google Play and run the check.
3. In the terminal, enter:

   su

   If the permission request appears, everything works.

Typical problems and solutions:

If it stops working after rooting Google Pay or banking applications, install the module MagiskHide Props Config and activate SafetyNet Fix:

1. Open Magisk open Settings → Hide Magisk.
2. Reboot.
3. Install the module Universal SafetyNet Fix from the repository Magisk.
4. Check the status SafetyNet via the app YASNAC.

How to remove root and return the warranty (partially)

If you need to return your phone to a service or sell it, remove traces of rooting:

1. Download full stock firmware for your model (4 files: AP, BL, CP, CSC).
2. Flash it via Odin (all fields must be filled in!).
3. After flashing the firmware, the phone will automatically reboot and reset.
4. Check the status Knox via Download Mode:

   ONE MODEM: Knox Warranty Void: 0x0

   If 0x1 the warranty is voided irrevocably.

Important: even after uninstalling root, some applications (for example, Samsung Health) can retain information about modifications. For complete cleaning:

• 🧹 Reset via Recovery Mode (Volume up + Power → Wipe data/factory reset).
• 🔄 Flash CSC-file (not HOME_CSC!) for full formatting.
• 📱 Install the original firmware with the same region (CSC-code) that was originally.

⚠️ Attention: On devices with One UI 5.0+ after removing root, a mark may remain in eFuse, which service centers check with a scanner. This does not affect the operation of the phone, but serves as evidence of interference.

FAQ: Answers to frequently asked questions