lolinet channel

#note Don't Private Message us to ask blankflash If you can't find it on the website, then we don't have it either. Please don't send us a private message asking for it. Thank you.

#note We need you to share unspecific IMEI/SN We need you to provide us with the first 13 digits of IMEI to confirm the phone model and download the firmware. We don't need to know the specific imei of your device, and you don't need to worry about information leakage. If you find that your software channel has not been updated since 2025-06-28, please contact @alphacat / @ExcellentCompress in @lolinet

#note It's time to say goodbye We have lost all access to download Motorola/Lenovo's firmware, It's time to say goodbye. Thank you all. Existing firmware will continue to be stored until the end of the year. If someone could help download and upload the firmware I could put it on the website.

#note About Moto Google Factory Reset Protection (FRP) Please search for related vulnerabilities and tutorials from Google or YouTube or related groups. Do not ask any FRP question in the lolinet group. There is no answer here. In addition, Blankflash is not compatible with Google FRP. Blankflash is just a moto official tool used to restore EDL/PreLoader mode to fastboot mode. Since the built-in firehose programmer / Download Agent of blankflash has very low permissions, you cannot use it to read and write any partition except the Bootloader partition. Motorola is not Xiaomi. If your device SoC is Unisoc, performing FRP with Pandora or UnlockTool or Other Hacking Tools may cause baseband NV data (IMEI) permanent loss. Please only erase the FRP partition if you know how to do it. Lolinet won't seriously explain how to implement this process.

#note Lenomola Device Product Code list in 2024 The Lenomola models released in 2024 has been clearly listed, please visit the following URL for details: https://mirrors.lolinet.com/firmware/lenomola/2024/README.html Other older Lenomola models: https://mirrors.lolinet.com/firmware/lenomola/_obsoleted_/README.html

Happy New Year 2025!

#note Tiny Fastboot Script update to 1.10.0 Change Log: v1.10.6 2024-12-30 - New: Added support for flashing mvpu_algo partition. Download Link: https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note What you need to know about 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. The CID certificate is stored in the cid partition, which is generated by the Moto PKI server and is bound to the SoC(CPU) ID and UFS (or EMMC) ID and RPMB content. If the content of this partition is tampered with, it will not pass the certificate verification. the specific encryption method is not included in, this is not the focus of this post. When the device starts loading the bootloader, the bootloader will verify the status of CID. If CID is empty or the data in its partition cannot match the CPU/UFS chip ID, it will become 0xDEAD. When the SoC fuse (QFUSE is for Qualcomm and EFUSE is for MTK) is blown to the Secure state (secure boot), and the Bootloader is not unlocked, the Bootloader will verify the validity of the CID. If the CID is 0xDEAD, your device will not be able to boot normally. In the 0xDEAD state, you cannot flash any image in AP Fastboot Mode, including but not limited to official retail firmware, engineering firmware, factory firmware etc. The CID will not be verified only if the device is in Not Secure(engineering) state or the Bootloader is unlocked (newer devices). The solution provided by Moto after-sales service is to upload the key generated by the Bootloader to the PKI server through fastboot oem cid_prov_req. Then the server responds and writes the new CID. When the CID is in normal state, you have the permission to write normal firmware. If the device's storage chip is damaged or your CID is broken, without the intervention of moto after-sales, you will need to change the brand new SoC + storage chip at the same time to save the phone. When the CID is normal, if the device has not unlocked the Bootloader, the carrier's firmware that can be flashed to the device is determined by the CID code. For example, CID 0x0032, this is an unlockable retail device. 0x000B, this is a device sold in mainland China. There are two special CID codes, 0x00FF and 0x0000. When the device bootloader is not unlocked, 0x00FF will only allow factory firmware to be flashed, 0x0000 can be flashed into all latest official firmware except the factory firmware (Same model, and the firmware's fuse version is not lower than the device's fuse version). For specific CID code sales areas, you can refer to: https://bbs.ixmoe.com/t/topic/25104 How to backup your CID: https://t.me/lolinetnews/11

#note How to update the bootloader image in blankflash of MTK Let’s take manaus (edge ​​40 neo) as an example. 1. Find the old version of blankflash for your device You can find old versions of blankflash on lolinet, for example it is blankflash_manaus_U1TM34.107-34-4-3_rebuild.zip. 2. Download and unzip the new version of the firmware Find the full firmware of the latest version, download and unzip it, for example, new version is: MANAUS_RETAIL_14_U1TM34.107-34-9-3_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml.zip 3. Unzip the old blankflash Unzip old blankflash to your favorite folder 4. Replace Bootloader images Replace the bootloader image file with the same file name in the new firmware into the old version blankflash folder. For example, the list of all bootloader image files is: dtbo.img gz.img lk.img logo.img mcupm.img pi_img.img spmfw.img sspm.img tee.img 5. Remove preloader.img 4096 bytes header Open preloader.img (in your latest full firmware) with your favorite hex editor, remove 4096 bytes(0-0FFFh) header, and save the file as preoloader.bin. The modified file will start with 4D 4D 4D 01 38 00 00 00 46 49 4C 45 5F 49 4E 46 (MMM 8 FILE_INF). 6. Replace modified preloader.bin into old blankflash Replace the modified preloader.bin to the same file name in the old blankflash. After all steps are completed, you can test whether it is available. Other Notes: 1. Please note that different MTK chips or models have different bootloader image files, this bootloader image list cannot be used universally. 2. This update method is only applicable to MTK blankflash. 3. Different models of blankflash are completely incompatible. 4. This method has limitations and can only be used when the download agent and authentication files are not updated.

#note Please don't Private Message to our Group Admin Unless approved by the goup admin himself, please only ask questions in the lolinet group. Not all of our group admin could answer your questions. Thank you.

#note Why is there no latest firmware on the website? We are very busy at work, not have free time every day. All firmware is uploaded manually by us, not a bot or programs, keeping the firmware up-to-date is not our obligation. We are not profiting from this hobby. If you find that your device has a OTA update, and we didn't update, please ask us again in next month, and provide your IMEI and phone P/N (Print on the phone box), usually the reason is that the vendor has not released full firmware yet. OTA update packages and full firmware are released at different times. The release time of stable firmware will be later, and it may even take 1-3 months to be released.

#note Tiny Fastboot Script update to 1.10.0 Change Log: v1.10.0 2024-07-26 - New: Added support for flashing efuse partitions (Moto Stylus 2023). - New: Added support for flashing connsys_bt, connsys_gnss, and connsys_wifi partitions (Motorola RAZR 50).…

Old model backup site, thanks @zinstack625 https://lolinet-replica.zinstack.ru

Unfortunately we lost all the firmware for 2020 due to disk broken. If anyone has a backup of these models, please contact us.

#note Tiny Fastboot Script update to 1.10.0 Change Log: v1.10.0 2024-07-26 - New: Added support for flashing efuse partitions (Moto Stylus 2023). - New: Added support for flashing connsys_bt, connsys_gnss, and connsys_wifi partitions (Motorola RAZR 50). - Optimization: Refactor code. Download Link: https://mirrors.lolinet.com/software/windows/TinyFastbootScript

#note Device Product Name will be distinguished by year In order to facilitate classification and deletion, we have adjusted the directory structure. Now the device code will be distinguished by year. E.g. : hiphi => 2022/hiphi rtwo => 2023/rtwo arcfox => 2024/arcfox

Messages in this channel will no longer be automatically deleted

#note We use symbolic link to save disk space Maybe when you are looking for the firmware of your phone model, you find that the software channels in the folder are inconsistent. E.g. RETBR -> OPENLA, AMXMX -> OPENMX, TELEU -> RETEU, TIMIT -> RETEU etc. Don't worry, this is normal. There is nothing wrong with our website. Motorola uses the same firmware across several retail carriers. We use symbolic links to significantly reduce the disk usage of these same firmware. Our firmware files are verified, You don't have to worry about downloading the wrong firmware.

#note We do not publicly upload any firmware in early testing Please note that if the device is not officially released, you cannot get any images from our website. We will not provide early testing firmware to anyone. Maybe you got some engineering or leaked models before the device is officially released, please be patient and wait for the device to be officially released. These early versions generally have many problems and are not suitable for general use.

#note Tiny Fastboot Script update to 1.9.9 Change Log: v1.9.9 2024-04-18 - Adjustment: MTK dtbo image flashing moved to BL Part. - Update: adb version updated to 1.0.41(35.0.1-11580240). - Update: fastboot version updated to 35.0.1-11580240. - Update: mfastboot version updated to 34.0.4-eng.gongsc.20230918.193125. - New: Add pvmfw.img flash support. Download Link: https://mirrors.lolinet.com/software/windows/TinyFastbootScript