#attention We are plan to move obsoleted device firmware

We are going to move the official firmware of the following obsolete models to _obsoleted_ .
The latest retention date is 2022-01-01, after these firmware will not be kept on the main website (https://mirrors.lolinet.com).
Please go to the obs-2 server to download it in the future, website URL: https://mirrors-obs-2.lolinet.com

cedric Moto G5 XT167x
potter Moto G5 Plus XT168x
watson Moto C 3G XT175x
namath Moto C 4G XT175x
panell Moto C Plus XT1725
albus Moto Z2 Play XT1710-x
nash Moto Z2 Force XT1789-x
montana Moto G5s XT179x
sanders Moto G5s Plus XT180x
payton Moto X4 XT1900-x

#note Tiny Fastboot Script update to 1.7.6

Change Log:

1. NEW: Custom custom.cmd have a new fully_customizable parameter, which no longer executes any flash commands when it is enabled, easy to fully customize.
2. UPDATE: adb version update to 1.0.41(31.0.3-7562133).
3. UPDATE: fastboot version update to 31.0.3-7562133。
4. BUGFIX: On newer MTK models preloader image could not be flashed.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note Tiny Fastboot Script update to 1.9.0

Change Log:

v1.9.0 2022-07-08
- New: Toolbox menu.
- New: Flashfile XML covert BAT (in "Toolbox" Menu).
This function will convert the flashfile.xml to a bat batch file in the firmware, suitable for users who "do not trust" Tiny Fastboot Script.

v1.8.0 2022-07-02
- Optimization: No longer rename the sparse format image, to avoid errors with other similar tools after using this tool (Note: It is no longer compatible with earlier Droid 2013 models, please use the old version of TFS if you use these models).

v1.7.8 2022-07-01
- Fix: Directory identified issues when running as administrator.

v1.7.7 2022-05-30
- Update: adb version updated to 1.0.41 (33.0.2-8557947).
- Update: Fastboot version updated to 33.0.2-8557947.
- Fix: (For Chinese) Remove exclamation on the signal icon link change to hicloud.com.
- Fix: Edge 20 fusion misses flashing md1img2 and audio_dsp partitions.
- Fixed: If cache partition no exists no process this operation.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note About Motorola blankflash and EDL mode

How to use blankflash:

1. Connect your bricked phone to your computer.
2. Press and hold the power button for 8 seconds to restart the 9008 port. When it restarts successfully you will hear the computer disconnecting and reconnecting sound.
3. Unzip blankflash zip and run blank-flash.bat.
4. Normally your phone will boot into fastboot mode, using the Tiny fastboot script to flash your phone carrier's official firmware. And your phone will be rescued.

The Sahara driver will only turn on the first time. When you need to retry different versions of blankflash, you have to do Step 2 to restart 9008 port.

The function of blankflash:

Blankflash for use in EDL mode only, its ability is simply to help you bring your phone back to fastboot mode. If your phone can boot into fastboot mode normally, you don't need it at all.

If your phone can boot fastboot normally, your search for a way to use EDL mode is useless.

Because only Motorola signed programmer.elf files can be loaded into your phone. Motorola restricts that only GPT and bootloader partitions can be flashed normally, while other partitions are not accessible (not being able to read and write).

You can't use it to flash official firmware or even third-party ROM, can't even use it to root your phone.

Please don't ask nonsense things like what EDL does and why.

About test points:

Some models reserve EDL Test Points (on the schematic called FORCED_USB_BOOT) on the motherboard, you can force the phone into EDL mode by shorting the two contacts.
Please be careful not to randomly try the test points on the motherboard, some contacts are not protected and a short circuit could completely burn the phone.
Entering EDL via test point is not privileged, you can't get around the restrictions through it.
Phones that can be damaged by improper disassembly. Not all models have reserved EDL Test Points.

Reporting a problem:

If you don't find blankflash for your phone, you can ask us in the group. If there is any possible error, please send the full screenshot to the group.

#note About flashing_locked

Please contact the nearest Motorola Service Center, this is the only way to save your phone.

You cannot flash any firmware in this state, and EDL mode won't help.

You have no way to re-unlock it if you don't enable OEM unlock option in developer options.

Don't ask flashing_locked questions anymore, no one can help you at the moment.

#note About CID 0x0000 and can't get unlock data

Some merchants use certain server unlock tools(E.g. MWorker-Tool) to unlock the carrier network (SIM lock, IMEI Blacklist etc.), during the unlock process, the CID certificate has been tampered with.

When you use fastboot getvar all command to get the information, you will see that the cid becomes 0x0000, and may lose the fastboot oem get_unlock_data functions. You will not be able to get the bootloader unlock data.

In this case, if you don't have the original CID backup, your device has permanently lost the ability to unlock. We can't help you with this problem. Please give up completely on the idea of unlocking the Bootloader.

#note Only the last 2 Android versions will be kept

Since the server disk is completely insufficient, we will only guarantee the last two current Android releases, for previous Android releases, only the last version will be kept. There's no point in keeping old firmware around, they just waste disk space.

Please note that our website is free and we do not guarantee timely updates of any firmware.

Welcome to donate large hard disk servers to us, we would appreciate it! :)

#note About the "RETAIL" folder

RETAIL folder does not represent any carrier. Many of motorola's retail carriers use the same firmware. In order to save disk space, we will place these firmwares in the retail folder, then use symbolic links to link these firmwares to multiple carrier folders.

#note How to backup your CID

Motorola uses the CID (Customer ID) to limit the carrier firmware that the device can be used to flash, and the ability to turn on certain factory features, and bootloader unlock features.

If your device supports unlocking bootloader, please backup this original CID partition at the first time after unlocking your device.

How to Backup CID Partition

1. Use Magisk to patch boot.img with your current device version number, then flash it (This step is to get ROOT permssions, use Google search then you will be get more detailed steps, please search by yourself!).
2. Enable USB debugging.
3. Use the following adb command to back up the cid partition.

adb shell
su
dd if=/dev/block/bootdevice/by-name/cid of=/sdcard/cid.img

4. Backup the cid partition image to the folder where adb is located on your computer.

adb pull /sdcard/cid.img

I would also recommend that you also back up the persist partition, which holds a lot of the plant's initial configuration, calibration data, and IMEI.

Use the following adb command to back up:

adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
adb pull /sdcard/persist.img

Finally, keep your partition backups in a safe place and don't lose them!

#note Tiny Fastboot Script update to 1.9.3

Change Log:

v1.9.3 2023-07-24
- Update: adb version updated to 1.0.41 (34.0.4-10411341).
- Update: fastboot version updated to 34.0.4-10411341.
- Update: mfastboot version updated to 33.0.1-eng.leizhe.20221012.102014.
- Added: Customized CMD script (End) for easy execution of commands at the end of customized flash.
- Added: Added support for MTK models like Motorola Moto G73 / G Power 2023.
- Tweak: Split the flashing steps for Qualcomm, MediaTek, SLSI models.
- Tweak: Move adb and fastboot to bin.
- Fixed: Some bugs on MTK models' flashing.
- Optimize: Adjust some codes.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note Tiny Fastboot Script update to 1.9.4

Change Log:

v1.9.4 2023-07-31
- Update: mfastboot version rolled back to 31.0.2-eng.a21550.20211025.113450.
- New: Support drag-and-drop flashing magisk patched boot image.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note Hardware way to full repair flashing_locked couldn't boot

Note:

You must have phone disassembly skills.
You must have BGA level soldering skills.
You need to have a UFS programmer, such as MiPi TESTER, UFI Box with UFS-Prog.
You must have Soldering Tools & Consumables, E.g. Soldering Gun, Soldering Station, Tweezers Set, UFS steel mesh, Solder paste...

1. Disassemble the phone, place the motherboard on the soldering vise, locate the UFS chip, then use soldering gun to heat and remove the UFS shield, then heat and desolder the UFS chip, finally re-ball the UFS chip (The temperature must not be higher than 350°C/660°F).
2. Place the UFS chip on the UFS adapter, use UFS programmer read the CID partition.
3. Resolder the UFS chip.
4. Find a Motorola remote unlock merchants (E.g. MWorker-Tool, you can also find better prices in our group), let them help you rewrite the CID to 0x0000. Simply writing 0x0000 you will not be able to unlock it again, see details: https://t.me/lolinetnews/8 .
5. Desolder UFS chip again, and re-ball the UFS chip.
6. use UFS Programmer restore original CID partition backup. At this step you will regain the ability to re-unlock the bootloader.
7. Resolder the UFS chip and shield.
In the end, you'll fix your phone completely.

Other things you need to know:

1. Some may think of restoring a CID backup in EDL mode, this is not possible under normal circumstances, Motorola's programmer bin restricts the ability to read and write CID partition, you couldn't possibly do that. do that. Only some models have exceptions, such as the Moto X30 (Edge 30 Pro).
2. This option is not feasible for the normal user, you may need to get a repair technical man to help you with this.
3. If you directly ask Motorola remote unlock merchants to help you, you will permanently lose the original CID partition, and you will no longer be able to unlock the bootloader again, I think this is very heart-wrenching and not recommended.

#note Tiny Fastboot Script update to 1.9.5

Change Log:

v1.9.5 2023-08-02
- - Added: Added a new Global Configuration, which can configure whether to reboot the bootloader when flashing the full firmware process, and whether to reboot after flashing.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note Tiny Fastboot Script update to 1.9.6

Change Log:

v1.9.6 2023-08-10
- Tweak: MTK models will be flashed into both A/B slots to avoid bricking when flashing BL Part.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note Tiny Fastboot Script update to 1.9.7

Change Log:

v1.9.7 2023-09-16
- Tweak: Adjust some codes.
- Added: Add fastboot flashing unlock option in unlock menu.
- New: Clean factory parameters option (only for engineering models).
- Fixes: Old non-super partition model AP part recognized issue.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note No longer able to get latest firmware

Due to permission restrictions, we will not be able to obtain firmware updates without IMEI/Serial Number.

If you need to get the latest firmware link, please contact our maintainer @yexu21 @alphacat @electimon @ShaikhMushahiD with your IMEI and model number. Usually share the full output of the fastboot getvar all command is the best way.

#note About phone Baseband version shows Unknown

For Motorola Moto Edge, Razr, One, X, G series:

This means that the Baseband Part of your phone is not starting up as expected. There are only two possibilities for this situation when the baseband is unknown.

Situation one:

Hardware problem.

Usually many people don’t believe that their phone is broken. If the baseband version suddenly becomes unknown without you doing anything, it must be a hardware problem.

If you are a phone repair man, you should focus on checking the RF power amplifier and power supply parts. Check whether water has entered the motherboard, causing corrosion or short circuit.

Situation two:

Software problem.

1. Check if the BP part is downgraded.

Motorola restricts that if the Baseband Part is downgraded, the Bootloader will refuse to load it at booting stage.

2. Check if the wrong baseband image is flashed.

The wrong baseband is naturally not recognized properly.

For causes caused by software problems, troubleshooting is naturally very simple. Just flash the latest firmware for the current model to troubleshoot the problem.

No need to think about other possibilities, no need to think about QCN backups or anything else.

Others you need to know how it works:

Motorola is not like Xiaomi, Samsung, Oppo, etc... Their implementation principles are completely different, Motorola's baseband definition does not exist in partitions such as fsc/efs.

The persist partition is responsible for storing the device's IMEI and SIM lock (dhob.bin), RF configuration (shob.bin), factory default calibration parameters, etc. Do not try to use a hex editor to modify any of the bytes, they are signed by the Motorola PKI Certificate. Whenever files are modified, they will not load correctly. If they don't pass signature verification correctly, your phone will lose signal. Although modifying them will not cause the baseband to be unknown.

Fsg image (Modern models will incorporate this into the radio image) stores the baseband configurations that each carrier should use.

The utags/hw partition is responsible for defining which specific baseband configuration in fsg should be used. And then motorola will put that baseband configuration into the baseband cache partition (modemst1/2, mdm1m9kefs). If the bootloader detects that the baseband cache is empty or the partition format is incorrect during the booting phase, it will reinitialize this process.

Whether the phone has a signal or not has nothing to do with the IMEI. When the BP part of your phone cannot start normally, the IMEI will naturally become 0. And rewriting the IMEI will be useless. Only when the BP part is working properly, then the IMEI will be loaded, not the other way around. Even when the IMEI is 0, as long as the Baseband Part boot normally and the Baseband configuration is correct, there will be get signal (as long as it is not a country where IMEI is a required option, such as the United States, etc).

QCN backup is just equivalent to backing up the modemst baseband cache. Motorola’s baseband cache can be cleared at will, so, it is completely useless for Motorola. On Samsung models, modemst also known as efs partition (However, due to different implementation principles, Samsung cannot clear these partitions at will).

#note Tiny Fastboot Script update to 1.9.8

Change Log:

v1.9.8 2023-12-30
- Adjustment: Moved MTK spmfw, scp, vcp, gpueb image flashing to BL Part.
- Adjustment: When the "Reboot after flashing the full firmware" function is enabled for MTK models, the bootloader will be reboot after flashing full firmware is completed to avoid reboot failure.
- Adjustment: When the GPT partition table is damaged, you can try to flash full firmware or flash the BL part only to rescue your phone.
- Fixed: The problem of unlocking Motorola bootloader successfully but still reporting an error.
- New: The Get Device Information menu has been added to read Primary screen model, Baseband version, Warranty fuse, and Dual SIM card information.
- Update: adb version updated to 1.0.41(34.0.5-10900879).
- Update: fastboot version updated to 34.0.5-10900879.

Download Link:

https://mirrors.lolinet.com/software/windows/TinyFastbootScript