VMGate Rooting Guide

Version: 1.0
Date: November 29, 2025
Last Updated: November 29, 2025
Based on: Rooting Guide V4
For: Samsung Galaxy A15, A16, A53, A54 (Android 13+)

---

WHAT IS ROOTING?

Rooting gives your Android device administrator-level access, allowing apps like VMGate to:

• Access system-level permissions
• Modify system files
• Control telephony functions
• Bridge audio between VoIP and GSM calls

Why VMGate Requires Root:

• VMGate must be installed as a system/priv-app to access hidden Android APIs
• System-level permissions are required for call routing and audio bridging
• Regular app installation does not provide sufficient privileges

---

PREREQUISITES

Required Hardware:

• ✅ Samsung Galaxy A15, A16, A53, or A54
• ✅ USB cable (original Samsung cable recommended)
• ✅ Windows computer (Windows 10/11)
• ✅ Stable internet connection (for firmware download: 2-4 GB)

Required Software:

• ✅ Magisk v27.0 - Download Magisk Manager → Download app-release.apk from the releases page
• ✅ ODIN (for flashing) - Download
• ✅ ADB Platform Tools - Download
• ✅ Samsung USB Drivers - Download

Device Requirements:

• ✅ Android 13 or higher
• ✅ At least 50% battery charge
• ✅ USB Debugging enabled
• ✅ Developer Options enabled
• ✅ OEM Unlock enabled (if available on your device)

Before You Start:

• ✅ Backup all data - Photos, contacts, messages, apps
• ✅ Remove screen lock - PIN, pattern, or password (temporarily)
• ✅ Disable Find My Device - Settings → Security → Find My Device → OFF
• ✅ Charge device to 50%+ - Prevent power loss during process

---

UNDERSTANDING THE ROOTING PROCESS

What Happens During Rooting:

1. Enable Developer Options - Unlock developer settings
2. Unlock Bootloader - Remove manufacturer restrictions
3. Enter Download Mode - Special mode for firmware flashing
4. Flash Patched Boot Image - Install Magisk-patched boot image via ODIN
5. Recovery Mode Navigation - Navigate recovery menu if needed
6. Verify Root - Confirm root access is working
7. Install Magisk Manager - Root management app
8. Install Systemizer - Required for VMGate systemization

Time Estimate:

• First-time (with download): 30-60 minutes (depends on internet speed)
• Already rooted (re-root): 10-15 minutes

---

STEP-BY-STEP ROOTING PROCEDURE

Step 1: Enable Developer Options

1. Open Settings on your device
2. Scroll to "About phone" (or "About device")
3. Tap "Software information"
4. Find "Build number"
5. Tap "Build number" 8 times rapidly
6. You'll see: "Developer mode has been turned on" message
7. Developer Options now appears in Settings

---

Step 2: Configure Developer Options

1. Go back to Settings
2. Scroll to bottom → Tap "Developer option"
3. Disable "Auto update system" - Toggle OFF
4. Enable "OEM unlocking" - Toggle ON
   • Note: If you can't find "OEM unlocking", connect device to Wi-Fi and try again
   • ⚠️ CRITICAL WARNING: If "OEM unlocking" option is completely missing or permanently greyed out (even after connecting to Wi-Fi), your device may have operator restrictions that prevent bootloader unlocking. If the bootloader cannot be unlocked, the device cannot be rooted, and VMGate will NOT work on this device. You may need to contact your carrier or consider using a different device.
5. Enable "USB debugging" - Toggle ON
   • Confirm warning dialog: "Allow USB debugging?" → Tap "OK"

---

Step 3: Install Samsung USB Drivers

1. Download Samsung USB Drivers:
   • Link: Samsung Android USB Driver
   • Or search: "Samsung USB Driver for Mobile Phones"
2. Install drivers on your Windows computer
3. Restart computer (recommended)
4. Connect device to computer via USB
5. Verify connection:
   • Device should show: "USB debugging connected" notification
   • Computer should recognize device

---

---

Step 5: Re-enable Developer Options (After Bootloader Unlock)

After bootloader unlock, Developer Options are reset. Re-enable them:

1. Open Settings → About phone → Software information
2. Tap "Build number" 8 times rapidly
3. You'll see: "Developer mode has been turned on" message
4. Go back to Settings → Developer option
5. Disable "Auto update system" - Toggle OFF
6. Enable "USB debugging" - Toggle ON
7. Verify Bootloader Unlock:
   • Check "OEM unlocking" option
   • It should now be greyed out and say: "Bootloader already unlocked"
   • ✅ If you see this, bootloader unlock was successful!

---

Step 6: Install Magisk Manager

1. Download Magisk Manager v27.0:
   • GitHub Release
   • Download: app-release.apk
2. Install on device:
   • Transfer APK to device (via USB or download directly to device)
   • Tap APK file → "Install"
   • Grant "Install from unknown sources" if prompted
3. Verify installation:
   • Open Magisk Manager app
   • App should launch (may show "Magisk not installed" - this is normal, we'll patch boot image next)

Note: We will configure Magisk Manager and verify root access after flashing the patched boot image (Step 12).

---

1. Find your device information on the phone:
   1. Open Settings on your Samsung phone
   2. Scroll down and tap "About phone" (or "About device")
   3. Find and write down these 3 values:
      • Model number: Look for "Model number" (e.g., SM-A156B)
      • Build number: Scroll down to find "Build number" (e.g., A156BXXU4CXH1)
        • ⚠️ IMPORTANT: Write down the EXACT build number - it's case-sensitive and must match exactly
        • The build number looks like: A156BXXU4CXH1 or similar
      • CSC/Region code: Look for "Service provider" or "CSC" (e.g., ITV, EUX, XAA)
        • This is usually 3 letters (e.g., ITV = Italy, EUX = Europe, XAA = USA unlocked)
2. Download firmware from SamFW.com:
   1. Open SamFW website on your PC:
      • Go to: https://samfw.com
   2. Search for your firmware:
      • Method 1 (Recommended - Direct URL):
        • Use this URL format: https://samfw.com/firmware/{MODEL}/{CSC}/{BUILD}
        • Replace {MODEL} with your Model number (e.g., SM-A156B)
        • Replace {CSC} with your CSC code (e.g., ITV)
        • Replace {BUILD} with your Build number (e.g., A156BXXU4CXH1)
        • Example: If your Model is SM-A156B, CSC is ITV, and Build is A156BXXU4CXH1, the URL is:
          https://samfw.com/firmware/SM-A156B/ITV/A156BXXU4CXH1
        • Copy this URL and paste it in your browser
      • Method 2 (Manual Search):
        • On SamFW.com homepage, use the search box
        • Type your Model number (e.g., SM-A156B)
        • Click on your device from search results
        • Find your CSC code (e.g., ITV) in the list
        • Click on your CSC code
        • Find your Build number (e.g., A156BXXU4CXH1) in the list
        • Click on your Build number to see download page
   3. Download the firmware:
      • On the firmware download page, click "Download" button
      • Firmware file is large (2-4 GB) - download will take 10-30 minutes depending on internet speed
      • ⚠️ DO NOT close browser or interrupt download - if download fails, you must start over
   4. Verify firmware ZIP contains all 4 files:
      • After download completes, extract the ZIP file
      • You should see these 4 files inside:
        • AP_*.tar.md5 (System partition - contains boot.img)
        • BL_*.tar.md5 (Bootloader)
        • CP_*.tar.md5 (Modem/Baseband)
        • HOME_CSC_*.tar.md5 (Preserves user data - MUST use HOME_CSC, NOT CSC)
      • ⚠️ CRITICAL: If you see CSC_*.tar.md5 instead of HOME_CSC_*.tar.md5, DO NOT use it - it will wipe all your data! You need HOME_CSC file.
3. Extract firmware files:
   • Extract firmware ZIP to a working directory
   • You should see all 4 files: AP_*.tar.md5, BL_*.tar.md5, CP_*.tar.md5, HOME_CSC_*.tar.md5
   • ⚠️ CRITICAL: Verify HOME_CSC_*.tar.md5 exists (NOT CSC_*.tar.md5). Using CSC_*.tar.md5 will wipe all data!
4. Extract boot.img from AP:
   • Extract AP_*.tar.md5 (it's a TAR archive, use 7-Zip or WinRAR)
   • Find boot.img inside extracted AP folder
   • Copy boot.img to a separate working directory
5. Patch boot.img with Magisk:
   • Note: Magisk Manager should already be installed (Step 6)
   • Transfer boot.img to device storage
   • Open Magisk Manager → Tap "Install" → "Select and Patch a File"
   • Select boot.img
   • Wait for patching to complete
   • Patched file: magisk_patched_[random].img
   • Transfer patched image back to computer
   • Rename to boot_patched.img
6. Rebuild AP archive with patched boot.img:
   • Extract the original AP_*.tar.md5 completely to a temporary folder
   • Replace boot.img in the extracted AP folder with boot_patched.img
   • Rebuild the TAR archive with the patched boot.img:
     • Use 7-Zip or WinRAR to create a new TAR archive
     • Name it: AP_patched.tar (same name as original, but with "_patched")
   • Create MD5 checksum file:
     • Use a tool like md5sum or online MD5 generator
     • Generate MD5 for AP_patched.tar
     • Save as AP_patched.tar.md5
   • Final result: You should have:
     • AP_patched.tar.md5 (with patched boot.img)
     • BL_*.tar.md5 (original, unchanged)
     • CP_*.tar.md5 (original, unchanged)
     • HOME_CSC_*.tar.md5 (original, unchanged)

---

---

---

Step 10: Navigate Recovery Mode (If Required)

Note: This step may or may not be required, depending on your device and firmware.

After flashing, if device enters Recovery Mode instead of booting normally:

1. Device may require to press power button (up to 3 times) - Press it
2. Recovery Mode Menu:
   • You will see a page with 3 options:
     • "Try again"
     • "Factory data reset"
     • "View recovery logs"
3. Navigate Recovery Menu:
   • Press Volume Down button 1 time (move to next option)
   • Press Power button 1 time (select option)
   • Press Volume Down button 1 time (move to next option)
   • Press Power button 1 time (select option)
4. Device may require to press power button again (up to 3 times) - Press it
5. After Recovery Navigation:
   • Device should boot normally
   • Skip all setup pages
   • Connect to Wi-Fi and enable auto-connection
   • If asked to copy data → Choose "Don't Copy"
   • If asked to install apps → Press "Later" (top-right corner)

If device boots normally without Recovery Mode, skip this step.

---

Step 11: Verify Root Access

After device reboots:

1. Wait for device to fully boot (2-3 minutes)
2. Re-enable Developer Options (if needed):
   • Settings → About phone → Software information → Tap "Build number" 8 times
   • Settings → Developer option → Enable "USB debugging"
3. Reconnect device to computer via USB
4. Allow USB Debugging:
   • Device shows: "Allow USB debugging?" dialog
   • Check "Always allow from this computer" (optional but recommended)
   • Tap "OK"
   • You may need to press "Allow" 2 times
5. Verify root:
   • Open Command Prompt or PowerShell on computer
   • Type: adb shell su -c id
   • Expected output: uid=0(root) gid=0(root) groups=0(root),...
   • If you see uid=0 → Root is working! ✅

If root verification fails:

• Boot image patching may have failed
• Flashing may have been incomplete
• Try re-rooting process (Step 6-9)

---

Step 12: Configure Magisk Manager

After successful root verification (Step 11), configure Magisk Manager:

1. Open Magisk Manager:
   • App should now show: "Magisk v27.0" installed
   • Root status: "Installed"
   • Superuser: "Granted" (when apps request root)
2. Configure Magisk:
   • Settings → "Superuser" → Enable "Automatic response" (optional)
   • Settings → "Allow background execution" (required for VMGate)

---

Step 13: Install Systemizer Module (Required for VMGate)

1. Open Magisk Manager
2. Tap "Modules" tab (bottom navigation)
3. Tap "Browse" button (or search icon)
4. Search for "Systemizer"
5. Find "Systemizer" by Veez21
6. Verify version is v17.3.1 before downloading
7. Tap "Download"
8. After download: Tap "Install"
9. Wait for installation to complete
10. Reboot device when prompted

After reboot:

• Open Magisk Manager → Modules tab
• Verify "Systemizer v17.3.1" shows as installed and enabled

Direct Download (if not found in Magisk Manager):

• Direct Download (recommended)
• GitHub Release → Download Systemizer-v17.3.1.zip (alternative)
• Magisk Manager → Modules → Install from storage → Select ZIP

---

TROUBLESHOOTING

Issue: Device Not Detected in Download Mode

Symptoms:

• Device shows "Downloading..." screen
• Computer doesn't recognize device
• ODIN can't find device (ID:COM box is red or empty)

Solutions:

1. Check USB cable - Try different cable (original Samsung recommended)
2. Check USB port - Try different USB port on computer
3. Reinstall Samsung USB drivers - Download latest drivers, reinstall, restart computer
4. Check USB mode - Some devices need specific USB mode (try different modes)
5. Try different computer - Rule out computer-specific issues
6. Restart ODIN - Close and reopen ODIN
7. Restart device - Exit Download Mode, restart device, re-enter Download Mode

---

Issue: ODIN Shows "FAIL!" Message

Symptoms:

• ODIN shows red "FAIL!" message
• Flashing doesn't complete
• Device may be stuck in Download Mode

Solutions:

1. Do NOT panic - Device is likely recoverable
2. Check USB connection - Ensure cable is connected securely
3. Do NOT exit Download Mode - Keep device in Download Mode
4. Check ODIN log - Read error message in ODIN log window
5. Common errors:
   • "File analysis..." → Boot image may be corrupted, re-download/patch
   • "SetupConnection..." → USB connection issue, try different port/cable
   • "Complete(Write) operation failed" → Try flashing again with same patched boot image
6. Retry flashing - Try flashing again with same patched boot image
7. Use original firmware - If flashing fails repeatedly, flash original firmware to recover

---

Issue: Firmware Download Fails

Symptoms:

• Download starts but fails
• "Network error" or "Connection timeout"
• Download incomplete

Solutions:

1. Check internet connection - Ensure stable connection
2. Retry download - Firmware files are large (2-4 GB), may need multiple attempts
3. Use different network - Try mobile hotspot or different WiFi
4. Check disk space - Ensure 5+ GB free space for download and extraction

---

Issue: Boot Image Patching Fails

Symptoms:

• Patching process errors
• "Invalid boot image" error
• Patching hangs or crashes

Solutions:

1. Verify boot.img - Ensure boot.img is correct for your device model and build
2. Check file integrity - Boot.img may be corrupted, re-download firmware
3. Use correct Magisk version - Ensure using Magisk v27.0 (tested version)
4. Try manual patching - Use Magisk Manager on device instead of PC patching
5. Check device storage - Ensure sufficient storage space on device

---

Issue: Root Verification Fails After Flashing

Symptoms:

• Device boots normally
• adb shell su -c id shows "permission denied" or "not found"
• Magisk Manager shows "Magisk not installed"

Solutions:

1. Re-check boot image - Ensure patched boot image is correct
2. Re-flash patched boot image - Try flashing again
3. Check Magisk version - Ensure using Magisk v27.0
4. Try different patching method - Use Magisk Manager on device instead
5. Check device security - Some devices have additional security that blocks root
6. Reinstall Magisk Manager - Uninstall and reinstall Magisk Manager

---

Issue: Device Boot Loop After Flashing

Symptoms:

• Device reboots repeatedly
• Stuck on boot animation
• Never reaches home screen

Solutions:

1. Enter Download Mode - Hold Power + Volume Down during boot
2. Flash original firmware - Download original firmware, flash all 4 files (AP, BL, CP, HOME_CSC) using ODIN
3. Device should recover - Original firmware restores normal boot
4. Re-attempt rooting - After recovery, try rooting process again with different approach

---

SAFEGUARDS AND BEST PRACTICES

Before Rooting:

• ✅ Full device backup - Photos, contacts, messages, apps
• ✅ Remove screen lock - Prevents lock screen issues
• ✅ Charge to 50%+ - Prevents power loss
• ✅ Stable USB connection - Use original cable, good USB port
• ✅ Stable internet - For firmware download (2-4 GB)
• ✅ Read all instructions - Understand each step before proceeding

During Rooting:

• ✅ Do NOT disconnect USB - Keep cable connected throughout
• ✅ Do NOT exit Download Mode - Wait for automatic reboot
• ✅ Do NOT interrupt flashing - Let process complete
• ✅ Monitor ODIN progress - Watch for errors or warnings
• ✅ Follow instructions exactly - Do not skip steps

After Rooting:

• ✅ Verify root access - Test with adb shell su -c id
• ✅ Install Magisk Manager - Required for root management
• ✅ Install Systemizer - Required for VMGate systemization
• ✅ Test device functionality - Make test call, check apps
• ✅ Keep Magisk updated - Use v27.0 (tested version)

---

FREQUENTLY ASKED QUESTIONS

Q: Will rooting delete my data?

A: Yes, unlocking the bootloader (Step 4) will wipe all data. However, after bootloader is unlocked, subsequent flashing using HOME_CSC (not CSC) preserves user data. Always backup before rooting.

Q: Can I unroot my device?

A: Yes. Flash original firmware (not patched) to remove root. However, warranty remains void even after unrooting.

Q: Will rooting work on all Samsung devices?

A: No. This guide is for Samsung A15, A16, A53, A54 only. Other models may have different procedures or may not be rootable.

Q: What if my device is already rooted?

A: If device is already rooted, you can skip Steps 4-9 (bootloader unlock and flashing). Proceed directly to Step 10 (Verify Root), Step 11 (Install Magisk Manager), and Step 12 (Install Systemizer).

Q: Can I use Heimdall instead of ODIN?

A: This guide uses ODIN for manual rooting (Windows). Heimdall is an alternative for Linux/Mac users, but ODIN is recommended for Windows.

Q: How long does rooting take?

A:

• First device (with download): 30-60 minutes
• Already rooted (re-root): 10-15 minutes

Q: What if firmware is not found on SamFW?

A:

• Try different CSC/region code
• Check if build number is correct
• Download firmware manually from SamFW.com
• Contact Startel support for assistance

Q: Can I root without a computer?

A: No. Rooting requires:

• Computer for firmware download and boot image patching
• USB connection for flashing
• ODIN/ADB tools

---

SUPPORT

For Rooting Issues:

• Startel does not provide support for rooting procedures
• Rooting is at your own risk
• Startel is not responsible for bricked devices

For VMGate Installation (After Rooting):

• See VMGate Installation Guide
• Contact: info@startelinternational.com

For General Android Rooting Help:

• XDA Developers Forums: https://forum.xda-developers.com/
• Magisk GitHub: https://github.com/topjohnwu/Magisk

---

APPENDIX: ODIN REFERENCE

ODIN Interface:

What You Should See:

• ID:COM box (top-left) - Shows COM port when device connected (blue/yellow = good, red = error)
• AP, BL, CP, CSC buttons - Load firmware files
• Options checkboxes - Auto Reboot, F. Reset Time, etc.
• Log window - Shows flashing progress
• Start button - Begin flashing process

ODIN Status Messages:

• "PASS!" (green) - Flashing successful ✅
• "FAIL!" (red) - Flashing failed ❌
• "ID:COM" (blue/yellow) - Device detected ✅
• "ID:COM" (red) - Device not detected ❌

ODIN Settings:

• ✅ Auto Reboot - Device reboots after flash (recommended)
• ✅ F. Reset Time - Resets timer (recommended)
• ❌ Re-Partition - DO NOT check (can brick device)
• ❌ NAND Erase All - DO NOT check (wipes all data)

---

APPENDIX: DOWNLOAD MODE REFERENCE

Download Mode Screen:

What You Should See:

• Blue background with "Downloading..." text
• Android robot icon (may appear)
• "Do not turn off target!!" warning text
• Blue progress bar (during flashing)

What You Should NOT See:

• ❌ Normal boot animation
• ❌ Home screen
• ❌ Lock screen
• ❌ Any app interface

If you see anything other than Download Mode screen:

• Device is NOT in Download Mode
• Re-enter Download Mode (Step 8)

---

APPENDIX: COMMAND REFERENCE (ADVANCED)

For users comfortable with command-line:

Check Device Connection:

adb devices

Check Root Status:

adb shell su -c id

Expected: uid=0(root) gid=0(root) groups=0(root),...

Reboot to Download Mode:

adb reboot download

Check Device Properties:

adb shell getprop ro.product.model        # Device model
adb shell getprop ro.build.display.id    # Build number
adb shell getprop ro.csc.sales_code      # CSC code

---

END OF ROOTING GUIDE

Next Steps: After successful rooting, proceed to VMGate Installation Guide