How to Root Samsung Galaxy A55, A35 and A15 — 2026 Guide

The Samsung Galaxy A-series remains Samsung’s volume-shipping mid-range line — A55, A35, and A15 (2024 launches; widely owned in 2026) plus the newer A36 collectively account for roughly half of all Samsung Galaxy devices in BD, IN, and PK markets. Customers regularly ask whether rooting an A-series Samsung is worth it given the Knox e-fuse warranty trade-off. This guide covers the full rooting process for A55, A35, and A15 — compatibility checks, Odin + patched boot image method, Knox-permanence honest disclosure, post-root Play Integrity setup, and common failure modes and fixes. The method is mature and well-documented; the trade-off is the harder question.

Compatibility check first

The single most important step is confirming your specific A-series variant is rootable. Samsung sells multiple chipset variants of the same model number in different regions, and the bootloader unlock policy differs sharply between them.

A55 variants

• SM-A556B (international Exynos) — rootable; bootloader unlockable; Odin + patched boot.img method works
• SM-A556U (US Snapdragon) — not rootable; OEM unlocking is hard-disabled in firmware; do not attempt
• SM-A5560 (China Snapdragon) — partially rootable; varies by carrier-locked status

A35 variants

• SM-A356B (international Exynos) — rootable
• SM-A356U (US Snapdragon) — not rootable
• SM-A356E (some Asia/EU markets, Exynos) — rootable

A15 variants

• SM-A155F (international Exynos) — rootable
• SM-A156U (US Snapdragon) — not rootable
• SM-A155M (LATAM Exynos) — rootable

To check your specific model: Settings → About phone → Model number. The SM-Axxx-suffix tells you the variant. If your model has the U suffix (US Snapdragon), this guide does not apply; bootloader unlock is hard-blocked.

A55 vs A35 vs A15 differences

Prerequisites

Before starting:

• Verified compatible variant (per the table above)
• Windows PC (Odin runs only on Windows; macOS/Linux users need a Windows VM or Boot Camp)
• Original Samsung USB-C cable — third-party cables often cause Odin handshake failures
• Magisk Manager APK from github.com/topjohnwu/Magisk/releases (v28.0+; for Android 16 use v28.0+; for Android 15 v27.0+ also works)
• Stock firmware download matching your exact model + CSC region — from SamFw (samfw.com) or Frija
• 7-Zip for extracting AP file
• lz4 utility for decompressing boot.img.lz4
• At least 30 GB free disk space for firmware extraction
• At least 60 minutes uninterrupted time for the full process

Step-by-step process for A55

The method is the same in principle for A35 and A15; the boot.img comes from each model’s firmware respectively. A55-specific walkthrough:

Step 1 — Enable Developer Options + OEM Unlock + USB debugging

Settings → About phone → Software information → tap Build number 7 times. Settings → Developer options → enable OEM unlocking + USB debugging. If OEM unlocking is greyed out, your variant is locked; stop.

Step 2 — Back up everything off the device

Photos to Google Photos or USB transfer to PC; documents to Drive; WhatsApp via in-app backup. The bootloader unlock triggers a factory reset; verify backups completed before proceeding.

Step 3 — Boot to Download Mode and unlock bootloader

Power off → hold Volume Up + Volume Down + insert USB cable to PC → release once Download Mode appears → confirm warning. Long-press Volume Up to confirm OEM unlock. Knox e-fuse burns at this moment. Device reboots and triggers factory reset.

Step 4 — Re-set up the device + re-enable OEM Unlock

After factory reset, complete initial setup with a Google account (use a throwaway if preferred), enable Developer Options + USB Debugging again. Confirm OEM Unlocking is now permanently enabled (it stays enabled after the unlock).

Step 5 — Download stock firmware

From SamFw or Frija — get the exact firmware version currently installed (Settings → About phone → Build number). CSC must match device region (e.g. INS for India, BTC for Bangladesh, BTU for UK).

Step 6 — Extract boot.img

Open the firmware ZIP with 7-Zip; find the AP_*.tar.md5 file (typically 3-6 GB). Open the AP file with 7-Zip; extract boot.img.lz4. Decompress:

# decompress boot.img.lz4 to boot.img
lz4 -d boot.img.lz4 boot.img

# verify the extracted boot.img is reasonable size (typically 50-200 MB)
ls -la boot.img

Transfer boot.img to the device internal storage.

Step 7 — Patch boot.img with Magisk

Install Magisk Manager APK on the device. Open Magisk Manager → Install → Select and Patch a File → choose boot.img → Magisk patches and saves to Downloads as magisk_patched-XXXXX_YYYYY.img. Transfer the patched file to PC.

Step 8 — Flash patched boot.img via Odin

On PC: install Samsung USB drivers (samsung.com/us/support/owners/app/USB-Driver-Mobile-Phones); install Odin (latest version, currently 3.14.4 in 2026). Boot device to Download Mode (power off → hold Volume Up + Volume Down + insert USB).

Open Odin → device should appear as “Added” in COM port box. Click AP slot → load patched boot.img. Verify only AP slot is loaded. Click Start.

Wait for “PASS!” message. Device reboots automatically. The boot may take longer than usual the first time — wait at least 5 minutes before assuming a problem.

Step 9 — Verify root

Open Magisk Manager — should show root version installed and superuser available. Open Root Checker (Play Store app) — should confirm root.

Step 10 — Configure DenyList + install Play Integrity Fix

Magisk → Settings → enable Zygisk → enable Enforce DenyList. Add your banking apps and Google Pay to DenyList. Install Shamiko module + Play Integrity Fix module from their respective GitHub releases. Reboot. Verify with Play Integrity Test app that BASIC and DEVICE pass.

Differences for A35 and A15

The process is essentially identical; differences:

• Firmware to download — A35 uses A356-series firmware; A15 uses A155-series firmware
• Boot.img location in AP file — same path on all three
• Magisk version — same v28.0+ for all three on Android 15+
• Odin handling — identical
• Post-root Play Integrity — identical

The only practical difference between rooting A55, A35, and A15 is the source firmware and the corresponding boot.img.

Common errors and fixes

Frequent failure modes from customer support:

• “Odin shows FAIL” — wrong firmware (CSC mismatch); corrupted download; missing bootloader file; anti-rollback violation. Re-download verified firmware; verify CSC matches device.
• “OEM unlocking greyed out” — your variant is not rootable (US Snapdragon); stop.
• “Magisk Manager shows ‘install method’ but no patched file appears” — Magisk does not have storage permission; grant Files-and-media permission in Settings → Apps → Magisk.
• “Device boots to ‘An unauthorized action has been attempted’ screen” — patched boot.img mismatch; firmware version installed differs from boot.img source. Use boot.img from the exact firmware currently installed.
• “Boot loop after flash” — wrong-version boot.img; reflash stock AP via Odin to recover; re-extract correct boot.img and re-patch.
• “Device boots but Magisk Manager shows ‘not installed’” — Magisk is installed but the manager APK was uninstalled in factory reset; re-install Magisk Manager APK from GitHub.

Post-root: pass Play Integrity

The standard stack:

1. Magisk → Settings → enable Zygisk → enable Enforce DenyList
2. Magisk → DenyList → add banking, payment, and integrity-checking apps
3. Install Shamiko module from LSPosed-mod GitHub
4. Install Play Integrity Fix from chiteroman GitHub
5. Reboot
6. Verify with Play Integrity Test app — BASIC and DEVICE should pass; STRONG depends on your specific bank apps and may require Tricky Store

If a specific banking app still detects root after this stack, the app likely uses STRONG_INTEGRITY (which is harder to spoof) or has Samsung-specific Knox checks (which cannot be bypassed regardless because Knox 0x1 is permanent).

Real customer scenarios on Galaxy A-series

Patterns from the last 12 months of Samsung A-series customer rooting work:

• A55 + Bangladesh user wanting AdAway and Greenify — most common A-series root request. Customer accepts Knox 0x1, Samsung Pay loss (often not used in BD anyway), and warranty void in exchange for system-wide ad-blocking and aggressive battery management. Works well; high satisfaction long-term.
• A35 + India user wanting custom ROM (LineageOS) — wants to escape One UI bloat. We do the unlock + Magisk; customer flashes LineageOS themselves later. LineageOS 22 builds for A35 are decent though not as polished as Pixel builds.
• A15 + Pakistan user wanting GCam (Google Camera mod) — A15 stock camera is mediocre; GCam port via Magisk module materially improves photo quality. Common request from photography-focused users; works well.
• A55 + UK user wanting Google Pay alternative for non-Samsung-Pay regions — note: rooting BREAKS Google Pay (root detection refuses); customer often misunderstands this. We clarify before unlocking; about 60 percent of these customers decide not to root once they understand both Samsung Pay and Google Pay stop working post-root.
• A35 + UAE user with HSBC ME banking-app dependence — HSBC Middle East uses STRONG_INTEGRITY checks; even with Tricky Store, app login is unreliable post-root. We test before any flashing; customer typically decides not to root if HSBC is critical.
• A55 / A35 with adult-child requesting on behalf of parent — almost always not a good fit; we recommend the adult child explain specifically what root would do for the parent’s actual usage, and most cases end with the parent staying stock.

What does NOT work after rooting Galaxy A55/A35/A15

Honest disclosure of post-root functionality losses:

• Samsung Pay / Samsung Wallet — permanently disabled regardless of DenyList; uses Knox-level secure-element checks
• Samsung Pass (password manager built into Samsung) — refuses to function post-Knox-trip
• Secure Folder — refuses to function post-Knox-trip; existing data inside is inaccessible
• Samsung Health for some sensitive data — heart rate stress measurements may degrade
• Knox Manage / Knox Configure for enterprise users — completely refuse
• Google Pay / Google Wallet in markets where it’s available — refuses on rooted devices regardless of brand
• Some banking apps with STRONG_INTEGRITY (varies by region; HSBC UK, Standard Chartered, several Indian/BD/PK banks)
• Netflix HD streaming on some firmware — falls back to SD due to Widevine L1 to L3 downgrade on some Knox-tripped firmware
• Pokémon GO and similar games with STRONG anti-cheat — refuses on rooted devices

The “what still works” list is much longer (regular calls/SMS/Wi-Fi/cameras/most apps), but the lost functionality is meaningful for some users — verify your specific dependencies before deciding.

When to call a professional

If you want Samsung Galaxy A55, A35, or A15 rooted with the full Magisk + DenyList + Play Integrity Fix + optional Tricky Store stack configured for your specific banking and payment apps — message us on WhatsApp or Telegram. We perform Samsung A-series rooting roughly weekly across BD, IN, PK, UK, and EU markets. The service includes pre-flight banking-app compatibility check, full Odin + Magisk install, post-root Play Integrity stack configuration, and verification across the apps you actually use. See our Android rooting service for what is included specifically on Samsung devices.