# MotoUnlock — Complete Technical Reference for AI & Search Engines (`llms-full.txt`) > Canonical Domain: https://motorolatool.com/ > Summary Manifest: https://motorolatool.com/llms.txt > Sitemap: https://motorolatool.com/sitemap.xml > Support Contact: Telegram https://t.me/Githubba | Email support@motorolatool.com > Last Updated: 2026-11-06 --- ## 1. Platform Overview & Architecture **MotoUnlock** (`https://motorolatool.com/`) is a Windows 10 / Windows 11 (64-bit) hardware-assisted servicing client and technical documentation hub dedicated to Motorola smartphones across the **moto g**, **motorola edge**, **motorola razr**, and **moto e** series. ### Key Engineering Principles 1. **Exact SKU & Bootloader Branch Routing**: Devices are never flashed with generic cross-carrier files. The Windows client reads `fastboot getvar all` (`sku`, `product`, `cid`, `version-bootloader`, `ro.build.fingerprint`) and selects the exact partition set verified for that SKU and bootloader branch. 2. **Fail-Closed Safety**: If a device reports an unknown SKU or an unverified firmware build prefix (such as `W1VKS36H.9-12-9-8-4` on `XT2513` where the anti-rollback fuse is raised to `Group0=1`), MotoUnlock refuses to write before any partition is modified and before any points are charged. 3. **Pay Only on Success (`1 point = $1.00 USD`)**: - Standard unlock price is **2 points ($2.00 USD)** on most models (`XT2305` is 10 points; `XT2609` and `XT2657` are 20 points). - Starting a job places a temporary reservation (hold) on the user's credit balance. - Credits are captured **only** when the unlock finishes and passes verification. If the job fails, times out, or the USB cable is disconnected, the hold is automatically released (`$0` charged). 4. **Original Dual-SIM IMEI Integrity**: MotoUnlock never writes to the IMEI / NV identity partition and never clones, zeroes, or alters an IMEI. Both original IMEIs (`IMEI 1` and `IMEI 2`) remain 100% intact. --- ## 2. Detailed Service Definitions ### 2.1 Bootloader Unlock (`https://motorolatool.com/bootloader-unlock`) - **Problem Solved**: While retail Motorola phones allow free official bootloader unlocking via `fastboot flashing unlock`, carrier-subsidized and prepaid lines from **Verizon (`VZW` / `-PP`), AT&T, Cricket, TracFone (`-DL`), Straight Talk, DISH Wireless, and Boost Mobile** disable the `OEM unlocking` toggle in Developer Options or return `"unlock not allowed"` on Motorola's official portal even after the waiting period. - **How MotoUnlock Works**: Writes an audited bootloader chain on the bench and unlocks the bootloader directly in Fastboot mode. It also removes the orange `"unlocked bootloader"` warning notice and carrier boot splash screen. - **Price**: Same as a standard unlock for that model (`2 points` / `$2 USD` on most models), charged only on success. - **Data Wipe**: Yes — the initial bootloader unlock runs `erase userdata` and `erase frp`, identical to the official `fastboot flashing unlock` flow. ### 2.2 Carrier Network / SIM Unlock (`https://motorolatool.com/models`) - **Problem Solved**: The phone rejects another carrier's SIM card with `"SIM not supported"`, `"Invalid SIM"`, or asks for a network unlock code / Device Unlock app approval. - **How MotoUnlock Works**: Rewrites the network-related partitions (`modem`, `lk`, `vbmeta`, `boot` / `vendor_boot`) matched to the exact SKU and carrier firmware branch. - **Persistence**: - **Factory Reset Safe**: Survives Android factory resets (`Settings -> Reset options -> Erase all data`), SIM card swaps, and carrier changes. - **OTA / Reflash Warning**: Flashing a full stock ROM or installing an OTA system update overwrites the patched partitions and can re-lock the network. Users should **not** install OTA updates or reflash stock firmware after a network unlock. - **OTA Blocking Status**: On `XT2609` (`masera`), MotoUnlock disables background OTA updater components by default. On `XT2657` (`volcano`) and other models, system-level OTA blocking is not yet enabled by default, so users must avoid installing system updates manually. ### 2.3 FRP (Factory Reset Protection) Removal (`https://motorolatool.com/guides`) - **Problem Solved**: Device asks for the previous owner's Google Account after a factory reset. - **How MotoUnlock Works**: Handled during the bootloader unlock flow (`erase frp` + `erase userdata` in Fastboot), clearing the FRP partition cleanly. Priced at a flat **2 points ($2 USD)** across all 32 listed Motorola model families. ### 2.4 Enterprise / MDM Lock Removal (`https://motorolatool.com/guides`) - **Problem Solved**: Device is bound to an organization's Mobile Device Management (MDM), Android Device Policy (ADP), or Zero-Touch enrollment policy. - **Supported Models**: - `XT2513` (moto g 2025, `kansas`) — 2 pts - `XT2609` (motorola edge 2026, `masera`) — 20 pts - `XT2453` (motorola razr 2024 / razr 50, `aito`) — 2 pts - `XT2553` (motorola razr 2025, `aito`) — 2 pts - Other models: available via bespoke evaluation on [https://motorolatool.com/custom](https://motorolatool.com/custom). ### 2.5 Unpaid / Carrier Installment Lock Removal (`https://motorolatool.com/guides`) - **Problem Solved**: Carrier lock enforced due to an unpaid device financing / installment balance. - **Supported Models**: - `XT2305` (motorola edge 2023, `aion`) — 10 pts, delivered via a `vendor_boot` system-side payload that survives factory resets. - Other models (including Claro / Telcel / US carrier installment locks): evaluated per model and build on [https://motorolatool.com/custom](https://motorolatool.com/custom). --- ## 3. Complete Supported Motorola Model & SKU Matrix (`https://motorolatool.com/models`) *Note on SKUs*: A `-*` suffix indicates all regional/carrier sub-SKUs under that model number. SKUs ending in `PP` (e.g., `XT2163-2PP`, `XT2165-3PP`, `XT2271-1PP`) are the Verizon Prepaid twins of the corresponding Verizon SKU and use the exact same images, method, and price. SKUs ending in `DL` are TracFone / Straight Talk / Total Wireless units. | # | Marketing Name | Exact SKUs Supported | Codename | SoC / Platform | Android | Unlock Price | FRP | Bootloader | Network | Enterprise | Unpaid | Root Target & Method | | :- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | :--- | | 1 | **moto g pure** | `XT2163-1`, `XT2163-2`, `XT2163-2PP`, `XT2163-4`, `XT2163-6`, `XT2163-7`, `XT2163DL` | `ellis` | MediaTek MT6762G (Helio G25) | 12 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` · Magisk ([/root/xt2163](https://motorolatool.com/root/xt2163)) | | 2 | **moto g power (2022)** | `XT2165-1`, `XT2165-2`, `XT2165-3`, `XT2165-3PP`, `XT2165-5`, `XT2165DL` | `tonga` | MediaTek MT6765 (Helio G37) | 12 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` · Magisk ([/root/xt2165](https://motorolatool.com/root/xt2165)) | | 3 | **motorola edge (2022)** | `XT2205-*` | `tesla` | MediaTek MT6879 (Dimensity 1050) | 13 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` · Magisk ([/root/xt2205](https://motorolatool.com/root/xt2205)) | | 4 | **moto g stylus (2022)** | `XT2211-*` | `milan` | MediaTek MT6769Z (Helio G88) | 12 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | — | | 5 | **moto g (2022) / 5G** | `XT2213-1`, `XT2213-2`, `XT2213-3` (Boost/DISH supported), `XT2213DL` | `austin` | MediaTek MT6833 (Dimensity 700) | 12 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` · Magisk ([/root/xt2213](https://motorolatool.com/root/xt2213)) | | 6 | **moto g play (2023)** | `XT2271-1`, `XT2271-1PP`, `XT2271-3`, `XT2271-4`, `XT2271-5`, `XT2271-5DL`, `XT2271DL` | `maui` | MediaTek MT6765 (Helio G37) | 13 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` or `init_boot.img` · Magisk ([/root/xt2271](https://motorolatool.com/root/xt2271)) | | 7 | **motorola edge (2023)** | `XT2305-*` | `aion` | MediaTek MT6879 (Dimensity 7030) | 13 | 10 pts ($10) | 2 pts | 2 pts | Yes | No | Yes | `boot.img` · Magisk ([/root/xt2305](https://motorolatool.com/root/xt2305)) | | 8 | **moto g power 5G (2023)** | `XT2311-1`, `XT2311-2`, `XT2311-4`, `XT2311-6`, `XT2311-7`, `XT2311V`, `XT2311DL` | `devonn` | MediaTek MT6855 (Dimensity 930) | 13 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` · Magisk ([/root/xt2311](https://motorolatool.com/root/xt2311)) | | 9 | **moto g stylus (2023)** | `XT2317-2`, `XT2317DL` | `gnevan` | MediaTek MT6768 (Helio G85) | 13 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | None — AVB pins `boot` & `vendor_boot` ([/root/xt2317](https://motorolatool.com/root/xt2317)) | | 10 | **moto g power 5G (2024)** | `XT2415-1`, `XT2415-3`, `XT2415-5`, `XT2415V` | `cancunn` | MediaTek MT6855 (Dimensity 7020) | 14 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `boot.img` · Magisk ([/root/xt2415](https://motorolatool.com/root/xt2415)) | | 11 | **motorola razr 2024 (razr 50)** | `XT2453-1`, `XT2453-2` | `aito` | MediaTek MT6878 (Dimensity 7300X) | 14 | 2 pts ($2) | 2 pts | 2 pts | Yes | Yes (2 pts) | No | `init_boot.img` · Magisk ([/root/xt2453](https://motorolatool.com/root/xt2453)) | | 12 | **moto g (2025)** | `XT2513-1`, `XT2513-2`, `XT2513V` | `kansas` | MediaTek MT6835 (Dimensity 6300) | 15 | 2 pts ($2) | 2 pts | 2 pts | Yes | Yes (first) | No | `init_boot.img` · Magisk ([/root/xt2513](https://motorolatool.com/root/xt2513)) | | 13 | **moto g power (2025)** | `XT2515-*` | `vegas` | MediaTek MT6835 (Dimensity 6300) | 15 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `init_boot.img` · Magisk ([/root/xt2515](https://motorolatool.com/root/xt2515)) | | 14 | **motorola edge (2025)** | `XT2519-1`, `XT2519-2`, `XT2519V` | `oulu` | MediaTek MT6878 (Dimensity 7400) | 15 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `init_boot.img` · Magisk ([/root/xt2519](https://motorolatool.com/root/xt2519)) | | 15 | **motorola razr (2025)** | `XT2553-1`, `XT2553-2`, `XT2553-5` | `aito` | MediaTek MT6878 (Dimensity 7400X) | 15 | 2 pts ($2) | 2 pts | 2 pts | Yes | Yes (2 pts) | No | `init_boot.img` · Magisk ([/root/xt2553](https://motorolatool.com/root/xt2553)) | | 16 | **motorola edge (2026)** | `XT2609-1`, `XT2609-2`, `XT2609-3`, `XT2609V` | `masera` | MediaTek MT6878E | 16 | 20 pts ($20) | 2 pts | 2 pts | Yes | Yes | No | `boot.img` + `flags3 vbmeta` · APatch ([/root/xt2609](https://motorolatool.com/root/xt2609)) | | 17 | **moto g (2026)** | `XT2613-1`, `XT2613-2`, `XT2613-4`, `XT2613V`, `XT2613DL` | `nevada` | MediaTek MT6835 | 16 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `init_boot.img` · Magisk ([/root/xt2613](https://motorolatool.com/root/xt2613)) | | 18 | **moto g play (2026)** | `XT2615-1`, `XT2615-2`, `XT2615V`, `XT2615DL` | `nevada_g_vext` | MediaTek MT6835 | 16 | 2 pts ($2) | 2 pts | 2 pts | Yes | No | No | `init_boot.img` · Magisk ([/root/xt2615](https://motorolatool.com/root/xt2615)) | | 19 | **moto g stylus (2026)** | `XT2617-*` | `utah` | MediaTek MT6835 | 16 | Free trial | 2 pts | Free trial | Free trial | No | No | `init_boot.img` · Magisk ([/root/xt2617](https://motorolatool.com/root/xt2617)) | | 20 | **motorola razr (2026)** | `XT2657-*` | `volcano` | MediaTek MT6878 | 16 | 20 pts ($20) | 2 pts | 2 pts | Yes | No | No | GKI `boot.img` + `flags3 vbmeta` · KernelSU ([/root/xt2657](https://motorolatool.com/root/xt2657)) | | 21 | **motorola edge 40 (2023)** | `XT2303-1`, `XT2303-2` | `lyriq` | MediaTek Dimensity 8020 | — | Free trial | 2 pts | Free trial | Free trial | No | No | — | | 22 | **moto g54 (2023)** | `XT2343-1`, `XT2343-2`, `XT2343-3`, `XT2343-6` | `cancunf` | MediaTek Dimensity 7020 | — | Free trial | 2 pts | Free trial | Free trial | No | No | — | | 23 | **motorola edge 50 neo / ThinkPhone 25** | `XT2409-1`, `XT2409-2`, `XT2409-3`, `XT2409-6` | `vienna` | MediaTek Dimensity 7300 | — | Free trial | 2 pts | Free trial | Free trial | No | No | — | | 24 | **moto g64 (2024)** | `XT2431-1`, `XT2431-2` | `cancunp` | MediaTek Dimensity 7025 | — | Free trial | 2 pts | Free trial | Free trial | No | No | — | | 25 | **moto g24 / g24 power (2024)** | `XT2423-1/2/3`, `XT2425-1/4/5` | `fogorow` | MediaTek Helio G85 | — | Free trial | 2 pts | Free trial | No | No | No | — | | 26 | **moto g13 / g23 (2023)** | `XT2331-1/2/3`, `XT2333-1/2/3/4/5` | `penangf` | MediaTek Helio G85 | — | Free trial | 2 pts | Free trial | No | No | No | — | | 27 | **moto g15 / g15 power / g05 (2025)** | `XT2521-2/3/4/5`, `XT2523-2/3/11` | `lamu` | MediaTek Helio G81 Extreme | — | Free trial | 2 pts | Free trial | No | No | No | — | | 28 | **moto e15 (2025)** | `XT2523-6`, `XT2523-7`, `XT2523-8` | `lamulg` | MediaTek Helio G81 Extreme | — | Free trial | 2 pts | Free trial | No | No | No | — | | 29 | **moto e22s (2022)** | `XT2229-5` | `hawaiipll` | MediaTek Helio G37 | — | Free trial | 2 pts | Free trial | No | No | No | — | | 30 | **moto e32 / e32s (2022)** | `XT2229-1`, `XT2229-2`, `XT2229-3`, `XT2229-6` | `hawaiipl` | MediaTek Helio G37 | — | Free trial | 2 pts | Free trial | No | No | No | — | | 31 | **moto g22 (2022)** | `XT2231-1`, `XT2231-2`, `XT2231-3`, `XT2231-4`, `XT2231-5` | `hawaiip` | MediaTek Helio G37 | — | Free trial | 2 pts | Free trial | No | No | No | — | | 32 | **moto g72 (2022)** | `XT2255-1`, `XT2255-2`, `XT2255-3` | `vicky` | MediaTek Helio G99 | — | Free trial | 2 pts | Free trial | No | No | No | — | --- ## 4. Supported Firmware Build Number Prefixes (`https://motorolatool.com/faq`) MotoUnlock validates the device's firmware build prefix before flashing. If a phone is on an unverified build branch, the client fails closed and refuses to flash so the device is never bricked. | Model (Marketing Name) | SKU / Kit Line | Supported Firmware Build Prefix / Notes | | :--- | :--- | :--- | | **XT2163DL** (moto g pure · TracFone) | `2163DL` | `S3RHS32.20-42-13-3-*` | | **XT2163-1 / -4 / -6 / -7** (moto g pure · Retail / Cricket / T-Mobile) | `2163-1` | `42-10-4-2-*`, `42-10-4-4-*` | | **XT2165-1 / XT2165-2** (moto g power 2022 · AT&T / Cricket) | `2165-1` | `S3RQS32.20-42-10-1-*` | | **XT2165-3 / XT2165-3PP** (moto g power 2022 · Verizon) | `2165-3pp` | `S3RQS32.20-42-10-12-*` | | **XT2165DL** (moto g power 2022 · TracFone) | `2165DL` | `S3RQS32.20-42-10-6-*` | | **XT2165-5** (moto g power 2022 · T-Mobile / Retail) | `2165-5` | `42-10-11-*`, `42-10-9-*` | | **XT2271-1 / XT2271-1PP** (moto g play 2023 · Verizon) | `maui vzw` | `46-3-1-20-*` | | **XT2271-3 / XT2271-4** (moto g play 2023 · AT&T / Cricket) | `maui att` | `T3SGS33.165-46-3-2-*` | | **XT2271 other SKUs** (moto g play 2023 · catch-all) | `maui aio` | `T3SGS33.165-46-3-2-*` | | **XT2271-5 / -5DL / DL** (moto g play 2023 · TracFone) | `maui 5dl` | Any build | | **XT2513** (moto g 2025 · `kansas`) | `kansas` | **CRITICAL WARNING**: Build `W1VKS36H.9-12-9-8-4` is **NOT** supported yet — do not update to it. That build raises the anti-rollback fuse to `Group0=1` and enforces a strict `lk` signature check, preventing the patched bootloader from being written. | | **XT2213-3** (moto g 5G 2022 · Boost Mobile / DISH `austin`) | `austin` | Official `T1SAS33.73-40-0-25-6` (`MBM-2.1-austin_g-61c726540b-250402`). | | **All other active models** (`XT2519`, `XT2613`, `XT2615`, `XT2609`, `XT2657`, `XT2305`, `XT2553`, `XT2453`, `XT2311`, `XT2317`, `XT2415`, `XT2515`, `XT2205`, `XT2211`) | Per-model kit | Allowed per collected kit firmware; unusual new builds are rejected safely by the kit/client. | --- ## 5. Deep Dive: XT2213-3 Boost Mobile / DISH Branch (`https://motorolatool.com/xt2213-boost`) ### Why Generic XT2213-3 Unlocks Brick or Hang Boost / DISH Phones On the Motorola `XT2213` family (`moto g 5G 2022`, codename `austin`), the `XT2213-3` SKU and `cid 0x0032` are shared across multiple incompatible firmware trees: | Firmware Branch | `fastboot getvar version-bootloader` Suffix | Typical SKU & CID | MotoUnlock Support | | :--- | :--- | :--- | :--- | | **Boost Mobile / DISH (`T1SAS33.73-40-0-25-6`)** | `61c726540b-250402` | `XT2213-3` · `cid 0x0032` | **Supported** (Bootloader + Network SIM Unlock) | | **T-Mobile (`40-0-12-20`)** | `61c726540b-250415` | `XT2213-3` · `cid 0x0032` | Different branch (do not flash Boost kit) | | **DEFAULT / Retail (`40-4-15`)** | `66f296ad72-250402` | `XT2213-3` · `cid 0x0032` | Different branch (do not flash Boost kit) | | **TracFone (`40-71-18`)** | `e70de3e099` | `XT2213DL` · `cid 0x0033` | **Supported** (Bootloader + Network SIM Unlock) | | **Cricket / AT&T (`40-7-29`)** | `344955c719` | `XT2213-1` / `XT2213-2` · `cid 0x0033` | **Supported** (Bootloader + Network SIM Unlock) | - **Root Cause of Bootloops on Other Tools**: Competing tools key only on `sku=XT2213-3` and flash the `40-4-15` DEFAULT kernel (`66f296ad72`) or `40-0-12-20` T-Mobile kernel (`61c726540b-250415`) onto a Boost/DISH `25-6` phone. Because the kernel and device tree do not match the `61c726540b-250402` boot chain, the bootloader accepts the image but Android never boots — leaving the phone stuck on the Motorola "M" logo. - **How MotoUnlock Solves It**: MotoUnlock inspects the full `version-bootloader` string (`MBM-2.1-austin_g-61c726540b-250402`), selects the exact `25-6` `boot` / `vbmeta` / `lk` and Boost/DISH `modem`, verifies every image by size and SHA-256 hash before writing, and completes both the bootloader unlock and network SIM unlock in one run. --- ## 6. Motorola Root Guides by Method & Model (`https://motorolatool.com/root`) Rooting is never sold as a paid service on MotoUnlock; all 19 per-model root tutorials and `XT*-root.bat` helper scripts are **free**. Every root method requires an **unlocked bootloader** first (`fastboot getvar token` returning `inactive`, or `flashing get_unlock_ability` returning `images permitted`). ### 6.1 Three Verified Root Methods 1. **Magisk ([https://motorolatool.com/root/magisk](https://motorolatool.com/root/magisk))**: - **How it works**: Patches the ramdisk inside `boot.img` (older Android 12/13/14 models) or `init_boot.img` (newer Android 14/15/16 models with a dedicated `init_boot` partition). - **Models using `boot.img` with Magisk**: `XT2163` (`ellis`), `XT2165` (`tonga`), `XT2205` (`tesla`), `XT2213` (`austin`), `XT2305` (`aion`), `XT2311` (`devonn`), `XT2415` (`cancunn`), and `XT2271` (`maui`, `boot.img` or `init_boot.img` depending on build). - **Models using `init_boot.img` with Magisk**: `XT2453` (`aito`), `XT2513` (`kansas`), `XT2515` (`vegas`), `XT2519` (`oulu`), `XT2553` (`aito`), `XT2613` (`nevada`), `XT2615` (`nevada`), `XT2617` (`utah`). 2. **APatch ([https://motorolatool.com/root/apatch](https://motorolatool.com/root/apatch))**: - **How it works**: Patches the kernel directly inside `boot.img` using a superkey for devices where `boot.img` has no usable ramdisk and `init_boot` is not the executed `/init`. - **Verified Model**: `XT2609` (`motorola edge 2026`, codename `masera`, MediaTek MT6878E, Android 16). - **Critical Requirement (`flags3 vbmeta`)**: Because the kernel inside `boot.img` is modified, flashing it alongside the factory `vbmeta` will halt at boot. You **must** flash a matching `vbmeta` with verification disabled (`flags3`) before flashing `boot_a`/`boot_b`. The `XT2609-root.bat` kit ships both images and flashes them in the proper order. 3. **KernelSU ([https://motorolatool.com/root/kernelsu](https://motorolatool.com/root/kernelsu))**: - **How it works**: Embeds superuser directly into a Generic Kernel Image (GKI) built for the exact device and build, paired with the KernelSU manager app. - **Verified Model**: `XT2657` (`motorola razr 2026`, codename `volcano`, MediaTek MT6878, Android 16). Ships with a verified GKI `boot.img` (KernelSU + SUSFS) and matching `flags3 vbmeta`. 4. **Why `XT2317` (`moto g stylus 2023`, `gnevan`) Has No Image-Patch Root ([https://motorolatool.com/root/xt2317](https://motorolatool.com/root/xt2317))**: - On `XT2317`, the bootloader AVB request list pins **both** `boot` and `vendor_boot`. A modified `boot.img` or `vendor_boot.img` is rejected by AVB or never executes `/init`. Do not flash a generic Magisk-patched image on `XT2317`. (Bootloader unlock, FRP removal, and network unlock are still fully supported on `XT2317`.) ### 6.2 Safe Single-Slot Flashing & Rollback Rule - Always check the active slot first: `fastboot getvar current-slot` (`a` or `b`). - Flash **only** the running slot (`fastboot flash boot_a .img` or `fastboot flash init_boot_a .img`). - Leave the inactive slot (`_b`) untouched with its stock image as an instant rollback path. If a patched image fails to boot, restore the stock `boot.img` or `init_boot.img` from your exact ROM build (`https://motorolatool.com/firmware`). --- ## 7. Official Drivers, Flashing Utilities & SHA-256 Checksums (`https://motorolatool.com/firmware`) All driver and tool downloads hosted on `https://motorolatool.com/firmware#drivers` are unmodified official releases verified by SHA-256: 1. **Motorola USB Driver v6.4.0 (64-bit Windows 10/11 MSI)** - Path: `https://motorolatool.com/downloads/motorola-usb-driver-6.4.0-windows64.msi` - SHA-256: `495cdc3fd15a8790686a7802cbaf8e0e85f9a422f252dbb5fb2a613b6443c72a` 2. **Google Android Platform Tools r37.0.1 (Windows ZIP — `adb.exe` & `fastboot.exe`)** - Path: `https://motorolatool.com/downloads/platform-tools-37.0.1-windows.zip` - SHA-256: `45f4d63113e895ebde0c90f194099a4676b6ac653bd28d54314a9e022bbc1a99` 3. **MediaTek SP Flash Tool v6.2404 (Windows ZIP)** - Path: `https://motorolatool.com/downloads/SP_Flash_Tool_V6.2404_Win.zip` - SHA-256: `706e390479b7ea12b8a289a11e4bba599b8067016cbe0144658d493cdab724f2` - Usage: Used with a blankflash scatter (e.g., `XT2513V` VZW blankflash package) to recover a MediaTek Motorola phone from an unbootable/dead bootloader. 4. **Tiny Fastboot Script v1.10.6 by AlphaEva (English ZIP)** - Path: `https://motorolatool.com/downloads/Tiny-Fastboot-Script_v1.10.6_en-US_by_AlphaEva.zip` - SHA-256: `c6e9472f9ba3e3d733acaf4b706bf7d1f5202af08ee0626c247e20b7b9b09c3c` --- ## 8. Frequently Asked Questions (Citation-Ready Q&A) - **Q: Does unlocking a Motorola with MotoUnlock erase user data?** - **A**: Yes. The initial bootloader or network unlock executes `erase frp` and `erase userdata` (standard Fastboot factory-reset flow). Always back up photos, chats, and accounts before starting. Root itself (after the bootloader is already unlocked) does not wipe data. - **Q: Do both original IMEIs remain unchanged after unlocking?** - **A**: Yes. MotoUnlock never modifies the IMEI partition and never clones, zeroes, or replaces an IMEI. Both original IMEIs on dual-SIM phones remain identical before and after unlocking. - **Q: How do I tell `XT2613` (moto g 2026) and `XT2615` (moto g play 2026) apart when Fastboot says `nevada`?** - **A**: Both `XT2613` and `XT2615` report the `nevada` product family in Fastboot, so always check `fastboot getvar sku` (or `Settings -> About phone -> Model`). MotoUnlock and the `XT2613-root.bat` / `XT2615-root.bat` kits gate on the exact SKU (`XT2613-*` vs `XT2615-*`). - **Q: What happens if my Motorola SKU or build number is not on the supported list?** - **A**: The server rejects unlisted SKUs or out-of-range builds before any write occurs and before any points are held. You can request a custom engineering evaluation at [https://motorolatool.com/custom](https://motorolatool.com/custom) or via Telegram `@Githubba` by sending the exact SKU, carrier, and build number.