> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



Xiaomi Mi A2 Lite - Official firmware



Rep: (89)
Xiaomi Mi A2 Lite - Official firmware
PictureModel: M1805D1SG | Codenames: daisy, daisy_sprout
Description | Discussion пїЅ | Unofficial firmware | Purchase пїЅ | Accessories пїЅ | Camera talk пїЅ | power usage пїЅ | Modification and decorations пїЅ | Configure Notifications пїЅ | Mi Account пїЅ | Bootloader unlocking пїЅ | Project treble пїЅ | Official firmware пїЅ

Important information!
You can not block the bootloader if availableanydevice modifications!
All about official Android Pie 9.0
On the smartphone (Xiaomi Mi A2 Lite) there is Android One and Miui firmware is not and will not be.
About installing updates
About "A / B" partition structure and "seamless" updates

If you have any problems, you need advice.

Drivers and Utilities
Firmware
Instructions
Kernels
miscellanea


There is no curator in the subject. If there is a user in the subject who wants to become a Curator and the correspondingRequirements for candidates, he can apply in the sectionI want to be curator(after having studied the topic header and all materials for curators).
Prior to the appointment of the curator, on filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.


Post has been editeddraiv88 - 14.07.19, 15:26
Reason for editing: full phone backup



Rep: (5205)
Installing ADB / Fastboot drivers


The most complete and correct instruction.
Disclaimer
1. This manual describes the steps to manually install / update / adjust drivers in case of their absence / damage / incorrect installation or inoperability.
2. These actions do not need to be performed if the drivers are already installed (automatically or manually earlier) and work correctly, even if they are not from your device model.

Normal way
1. Download from the header Necessary software for firmware - Windows ".
2. Unzip the folder " Tools "from the archive to the root of the disk" WITH: "(for convenience). You will have a way:" C: \\ Tools ". You can unpack to any other place convenient to you, it does not matter.
3. Turn off the device.
4. Load the device into bootloader mode (Bootloader / Fastboot):
From the off device : Press and hold simultaneously power button + volume down key .
Note: Installation is also possible with USB debugging or in mode Adb sideload .
5. Connect your smartphone to PC.
6. Go to the device manager.
7. You will see the detected device " Android " or " Xiaomi Mi A2 Lite "with a yellow exclamation mark.
8. Click on the device with the right mouse button, select - " Update drivers ... ".
9. Select - " Search for drivers on this computer ".
10. Be sure to tick the " Including subfolders ". Click" Overview "and specify the path to the folder" usb_drivers "in, unpacked earlier folder" Tools ".
11. Click " Further ". Wait for the installation to complete. All drivers installed.

I'm sorry, what? Nothing succeeded? Everything is lost? Drivers are not installed? Well then ... -Change to Linux.- We go to suffer in the way below.
!Alternative way!
1. Download from the header Necessary software for firmware - Windows ".
2. Unzip the folder " Tools "from the archive to the root of the disk" WITH: ". You get the way:" C: \\ Tools ".
3. Turn off the device.
4. Load the device into bootloader mode (Bootloader / Fastboot):
From the off device : Press and hold simultaneously power button + volume down key .
Note: Installation is also possible with USB debugging or Adb sideload .
5. Connect your smartphone to PC.
6. Go to the device manager.
7. You will see the detected device " Android " or " Xiaomi Mi A2 Lite "with a yellow exclamation mark.
8. Click on the device with the right mouse button, select - " Update drivers ... ".
9. Select - " Search for drivers on this computer ".
10. Select - " Select a driver from the list of already installed drivers. ".
11. Select - " Show all devices ".
12. Select - " Install from disk ".
13. Click " Overview ".
14. In the opened explorer go to the folder " Tools ", unpacked from the archive in step 2 . Go to the folder " usb_drivers ", choose File " android_winusb.inf "and click" Open ". You will be returned to the previous window, click on it." OK ".

15. Now the fun part. You returned to the window " Select a driver for this device. ".
Uncheck "Only compatible devices "and you will see three options available to choose from:
1. Android ADB Interface and Android Composite ADB Interface - for debug mode from the included device and mode Adb sideload .
2. Android Bootloader Interface - for bootloader mode (Bootloader / Fastboot) .
Attention: Choose and install what you are right now!

16. Click " Further ". Wait for the installation to complete. Everything, the correct driver is installed and ready to go.

Note: For Linux and MacOS no need to install drivers. They are included by default in these operating systems.



Rep: (5205)
Unlocking and locking the bootloader


1. First of all, is necessarynecessarilyallow bootloader unlock on your device.
To do this, activate the menu "For developers ": Go to" Settings " -> " About phone " -> 7 times click on the item "Build Number" .
In the appeared tab "For developers "in the main settings menu, activate the item:" Factory Unlock " - " (Enable OEM Unlock) ".
2. Download from the header Necessary software for firmware ".
3. Unzip the folder " Tools "from the archive to the root of the disk" WITH: ". You get the way:" C: \\ Tools ".
4. Load the device into bootloader mode (Bootloader / Fastboot) one of the following ways:
From the off device : Press and hold simultaneously power button + volume down key .
From the included device : With USB debug activated follow up Adb team :
adb reboot bootloader

5. Connect the device to the PC and install drivers (if you did not do it earlier or they were not installed automatically).
6. Go to the, previously unpacked, folder " Tools ". In it, in the address bar of the folder above, write -" cmd "(without quotes).
7. Check device availability and driver installation. Run the fastboot command:
fastboot devices

If everything is good, the drivers are successfully installed and the phone is properly connected - you will see the following answer:
<device serial number>fastboot

8. At the command prompt, run the following command to unlock the bootloader:
Attention:When unlocking the bootloader, all data will be deleted !!!
fastboot oem unlock


P.S. To lock the bootloader, run the following command:
Attention:Make sure that you have a fully installed stock system without a single modification !!!
Attention:When locking the bootloader, all data will be deleted !!!
fastboot oem lock



Rep: (5205)
Instructions for flashing the original Fastboot image
(return to stock firmware)


Important information!
1. Make sure that the battery charge of the device is at a sufficient level - (>50%).
2. To connect the device do not use hubs and extension cords. Connect the device to the USB 2.0 port, directly to the PC motherboard (back of the system unit). The use of non-original (complete) cables and USB Type-C adapters for connecting and flashing the device is not recommended and is carried out at your own peril and risk.

Instructions on firmware
Please note that the firmware process is described.as detailed as possible. If you are an advanced user, feel free to skip the points you’ve already known and completed earlier.
1. Training
1.1 Download from spoiler " Drivers and Utilities "in the cap" Necessary software for firmware " in accordance with OS of your PC .
1.2 Unzip the folder " Tools "from the archive downloaded above to the root of the disk" WITH: ". It will turn out the way:" C: \\ Tools ".
Yes, you can unzip the folder "Tools "anywhere, on your own, but avoid spaces and Cyrillic characters in the path to it.
And yes, you can create a global variable in "PATH", for convenience, if you need it and you know how to do it.

1.3 Download the link from the header you need Fastboot image official firmware.
1.4 Unpack folder contents at * .tgz the image (archive) of the firmware in, previously unpacked, the folder " Tools ".
Attention: For correct unpacking * .tgz images (archives) highly recommend use Winrar . Using 7-zip archive must be unpacked twice .
Attention: Opening / Unpacking * .tgz images (archives) can take a long time. Be patient.

1.5 You should be able to exactly the same set and structure of files, as in the screenshot below. We verify .
Screenshot
Attached Image

1.6 Load the device into bootloader mode (Bootloader / Fastboot) one of the following ways:
From the off device : Press and hold simultaneously power button + volume down key .
From the included device : With USB debug activated follow up Adb team :
adb reboot bootloader

1.7 Install drivers (if necessary) and unlock bootloader (if not done this early).
2. Flashing process
2.1 Select and run one of automatic firmware scripts according to OS used and desired firmware mode :

Windows:
"flash_all.bat" - for automatic firmware with removalall data on the device and subsequent maintaining statusopen bootloader .
"flash_all_except_storage.bat" - for automatic firmware with preservationall data on the device and subsequent maintaining statusopen bootloader .
"flash_all_lock.bat" - for automatic firmware with removalall data on the device and follow blockingloader .
"flash_all_lock_crc.bat" - for automatic firmware with removalall data on the device follow blockingloader and encryptionof memory . It makes no sense to use, the data is encrypted by default.
"flash_factory.bat" пїЅ Do NOT use this script !!! It erases the / modemst1, / modemst2 (EFS) and / persist partitions. Your IMEI will be lost!

Linux / MacOS:
"flash_all.sh" - for automatic firmware with removalall data on the device and subsequent maintaining statusopen bootloader .
"flash_all_except_storage.sh" - for automatic firmware with preservationall data on the device and subsequent maintaining statusopen bootloader .
"flash_all_lock.sh" - for automatic firmware with removalall data on the device and follow blockingloader .
"flash_all_lock_crc.sh" - for automatic firmware with removalall data on the device follow blockingloader and encryptionof memory . It makes no sense to use, the data is encrypted by default.
"flash_factory.sh" пїЅ Do NOT use this script !!! It erases the / modemst1, / modemst2 (EFS) and / persist partitions. Your IMEI will be lost!

2.2 Wait for the end of the firmware process. Depending on the performance of your PC, this process can be quite long. After completion, the device will reboot itself.

P.S. Yes, you can use MiFlash for firmware if you prefer it. But it uses the same fastboot, so there is no difference.


Post has been editedDisplax - 11.09.18, 16:02



Rep: (5205)
Getting ROOT rights


1. Download (find in the subject) or self-extract from necessary ( installed by you ) Stock firmware core (boot.img) and copy it into the memory of the smartphone.
Important: For each of the firmware assemblies its core!
2. Download and install Magisk Manager. ( Download )
3. Open Magisk Manager. Go to: " Settings " -> " Update source " -> " Beta Channel ".
4. Go to Magisk Manager: " Installation " -> " Installation " -> " Select and patch file " -> Select boot.img from device memory .
5. The download of the Magisk archive begins, followed by the kernel modification process. Wait.
6. Download from the header Necessary software for firmware ".
7. Unzip the folder " Tools "from the archive to the root of the disk" WITH: ". You get the way:" C: \\ Tools ".
8. Copy the modified kernel to the unpacked folder with the working adb / fastboot utilities (C: \\ Tools) located in: / sdcard /, Download / patched_boot.img .
If the kernel is not displayed in the explorer on the PC - just move it to the root of the user memory (/ sdcard).
9. Put the device into fastboot mode, install drivers (if nessesary), unlock bootloader (if you have not done this earlier) and load the modified kernel:
  • Temporarily load the modified kernel:
    fastboot boot patched_boot.img
The device will reboot automatically after entering the command, just wait for the download.

Attention: At this stage you have already received temporary root-rights (valid until reboot)! If you don't need constant root (for example, for the Camera2 API) and the safety of the OTA update feature is important - do not perform further actions!

Attention: The following steps will lead to the installation of Root-rights on a permanent basis.
10. Go to Magisk Manager: " Installation " -> " Installation " -> " Direct installation (Recommended) ". Wait for the process to complete and reboot the device.
11. Everything, the root is received.

Post has been editedDisplax - 18.06.19, 12:28
Reason for editing: Update



Rep: (5205)
About installing updates


So. You received (or just left) a new update of the official firmware. And youhighly want to update.
However, you are plagued by doubts, questions spawn, and uncertainty scares.Will the update be installed? If not - How to install the update?

There are two options here: "There is no third"
пїЅ Option 1: I am a regular user
"I have a completely stock, clean device. Ruth did not set, did not change anything in the system. I did not climb anywhere."

Verdict: The update is installed without any problems. Install it in the normal mode.
пїЅ Option 2: I'm Satan
"TWRP set. Ruth set. Xposed set. I deleted half of the applications. And in general, I picked the system in every way."

Verdict: The update will not install, or after installation will lead to a bootlap.


Solution options:

You have changed / modified only the kernel. The system partitions / system and / vendor are in pristine-clean state and all other partitions in both slots correspond to the installed firmware.
I mean, you are 100% sure that neither you nor any application that works with root-rights made changes to the system partitions, and you did not confuse the components of the firmware.
1. Restore the stock kernel, the backup copy (backup) of which makes Magisk.
Go to Magisk Manager: "Deletion " -> " Restore partitions ". Restart the device.
2. Install flown update.
3. Re-get root-rights.
If this method did not work, it means that you were mistaken and the system partitions were compromised and / or the other partitions in both slots do not match the installed firmware.


The system partitions / system and / vendor are compromised and / or the remaining partitions in both slots do not match the installed firmware.
That is, any changes are made to system sections.
1. Flash the latest available fastboot firmware image according to the instructions .
If at the moment there is already a fastboot image of the update you need - stop there, you have successfully updated.
If at the moment there is only a fastboot image of the last update - flash it, and then smoothly update it via OTA.
2. Re-install all of your "Shaitan good" (modifications). Or do not install, thereby going from the discharge " Shaitan "to discharge" Regular user ".


Current bootloader status (locked/unlocked) installation of OTA updates is not affected.

Post has been editedDisplax - 26.08.18, 18:47



Rep: (332)
* Displax ,
Add to the instructions how to unlock and lock without deleting data.



Rep: (0)
Good day friends do not tell me if there is an opportunity to put twrp on this body.

Posted 08/16/2018 10:14:

And if so, the principle is not the same as on Xiaomi Redmi 6 Pro.



Rep: (5)
Good day friends do not tell me if there is an opportunity to put twrp on this body

Judging by the topic on xda, while there is no twrp for this body
https: //forum.xda-deve…e-daisy-t3827236/page2
developed a couple of days promised to do, we are waiting



Rep: (5205)
* _luki4_ ,
This joke can be corrected at any time, so it makes no sense to describe and rely on it.

Posted 08/16/2018 12:13 pm:

Lexxx_mac @ 08/16/18, 10:11*
Is it possible to put twrp on this body.
There is. But the current TWRP is so crooked and improperly assembled that this is of little use.



Rep: (20)
Priv! From the post Installing the ADB / Fastboot drivers installed the driver in alternative ways - the MiFlash prog does not see the device, I am already fighting for the third day (reinstalling different versions of the program, reinstalling, rolling back divers) there are no results. How can I envy this program?



Rep: (95)
How can I envy this program?

Did you try to disable the verification of the digital signature of firewood?



Rep: (8)
Remind me, please, how long will the Android One program work on this device? Is there a promising swim on it to 10ki?

By the way, when to wait for 9k? Unless under this program we should not receive updates simultaneously with pixels?

Post has been editedvuglusker - 18.08.18, 15:59



Rep: (5205)
* vuglusker
Guaranteed period of support for 18 months.

By the way, when to wait for 9k?
As soon as possible. This is not known to anyone.

Unless under this program we should not receive updates simultaneously with pixels?
No, they should not.



Rep: (26)
[RECOVERY] [UNOFFICIAL] TWRP for Xiaomi Mi A2 Lite

XDA
download

Attached images
Attached Image
Attached Image


Post has been editedYSH ALSAGER - 18.08.18, 16:39



Rep: (8)
As soon as possible. This is not known to anyone.

I apologize for the dissolution of this topic, but is this question on the shoulders of the device manufacturer, or do they have obligations for Google to update the firmware within a reasonable time? I just ordered it today (on a nostalgic wave after a nexus), and now I’m worried that Shaomi could upset with updates.



Rep: (5)
YSH ALSAGER @ 08/18/18, 20:38*
[RECOVERY] [UNOFFICIAL] TWRP for Xiaomi Mi A2 Lite


Those. You want to say that twrp itself was originally normal, we just hand-held users and were not satisfied with the “About A / B” partition structure ”, see the header? ;)

as far as I understand it is necessary to sew with a slightly different command than was originally written in the instructions,
namely

fastboot flash boot_b twrp.img
fastboot set_active b


enlighten, and then reluctant to get a brick?

Post has been editedVrazhina - 18.08.18, 18:37



Rep: (0)
I also have A2 Lite.
Unlock did. But, TWRP can not be installed yet.
Download this file "TWRP-3.2.3-TwrpBuilder-daisy-20180809.img"
Unsubscribe if someone succeeds.



Rep: (5)
It turned out to flash twrp

first look at your active boot

fastboot getvar all
or
fastboot getvar current-slot


then write twrp to it
fastboot flash boot_b twrp.img


ps
I had an active A slot, but as it was sykatno I wrote in it
therefore, first made active b, by command
fastboot set_active b

I recorded it and am happy :)

Post has been editedVrazhina - 18.08.18, 19:29



Rep: (402)
Vrazhina @ 08/18/2018, 18:17*
It turned out to flash twrp
I had an active A slot, but as it was a bit sykatno to write to it

And what is the difference in which section to write? Is it possible to both?



Rep: (5205)
PAraBelllum @ 08/18/18, 19:27*
Is it possible to both?
You can, but not at all. This TWRP cannot be temporarily downloaded as it should be. Therefore, they sew it instead of a core, enter it, do what is needed, and then return the core back.
In this form, TWRP is useless and even harmful.


Full version    

Help     rules

Now: 07/20/19, 22:33