Xiaomi Mi A2 - Official firmware
Xiaomi Mi A2 - Official firmware
Model: M1804D2SG | Codenames: jasmine, jasmine_sprout
Description | Discussion пїЅ | Purchase пїЅ | Accessories пїЅ | Camera talk пїЅ | Unofficial firmware | Official firmware | Power consumption and autonomy пїЅ
For questions of filling and updating the topic header, the Curator is always ready to help you. FranticKernel at QMS
Post has been editedFranticKernel - 19.06.19, 15:56
Model: M1804D2SG | Codenames: jasmine, jasmine_sproutDescription | Discussion пїЅ | Purchase пїЅ | Accessories пїЅ | Camera talk пїЅ | Unofficial firmware | Official firmware | Power consumption and autonomy пїЅ
Important information!
About installing updates
About "A / B" partition structure and "seamless" updates
You can not block the bootloader if availableanydevice modifications!
About "A / B" partition structure and "seamless" updates
You can not block the bootloader if availableanydevice modifications!
Drivers and Utilities
Firmware
Android9
- Android 9 PKQ1.V10.0.10.0.PDIMIXM
- Android 9 PKQ1.V10.0.9.0.PDIMIXM
- Android 9 PKQ1.V10.0.8.0.PDIMIXM
- Android 9 PKQ1.V10.0.7.0.PDIMIXM
- Android 9 PKQ1.V10.0.5.0.PDIMIXM
- Android 9 PKQ1.V10.0.4.0.PDIMIXM
- Android 9 PKQ1.V10.0.3.0.PDIMIXM
- Android 9 PKQ1.V10.0.2.0.PDIMIFJ
- Android 9 PKQ1.V10.0.1.0.PDIMIFJ
- Android 9 PKQ1.V10.0.1.0.PDIMIFJ BETA
Android8
- Android 8.1.0 OPM1.V9.6.17.0.ODIMIFE
- Android 8.1.0 OPM1.V9.6.17.0.ODIMIFE BETA
- Android 8.1.0 OPM1.V9.6.16.2.ODIMIFE BETA
- Android 8.1.0 OPM1.V9.6.16.0.ODIMIFE
- Android 8.1.0 OPM1.V9.6.16.0.ODIMIFE BETA
- Android 8.1.0 OPM1.V9.6.15.0.ODIMIFE
- Android 8.1.0 OPM1.V9.6.14.0.ODIMIFE BETA
- Android 8.1.0 OPM1.V8.9.20.ODIMIFE BETA
- Android 8.1.0 OPM1.V9.6.13.0.ODIMIFE
- Android 8.1.0 OPM1.V9.6.10.0.ODIMIFE
- Android 8.1.0 OPM1.V9.6.9.0.ODIMIFE
- Android 8.1.0 OPM1.V9.6.5.0.ODIMIFE
Kernel and Recovery
Instructions and fixes
Instructions:
Fixes:
- Instructions for solving the problem of "sensors and camera do not work", "erased IMEI"
- Instructions for installing a custom Hex kernel on the stock firmware.
- Instructions for unlocking and locking the bootloader for Windows
- Unlock and Lock Uploader for MacOS instructions
- Instructions for restoring your phone using Test Point
- Instructions for receiving gestures on the official firmware
- Installation instructions for permanent root with OTA support
- Installation instructions for Xposed for V9.6.15.0.ODIMIFE
- Instructions for returning from MIUI to Stock firmware
- Installation instructions for ADB / Fastboot drivers
- Instructions for firmware Fastboot image
- Smart Lock Instruction Manual
- Instructions for obtaining ROOT
Fixes:
miscellanea
- Removing embedded applications without root on a locked bootloader
- Dark animation and screen saver when enabled
- Activation app for Camera 2API
- bootanimation from stock firmware
- Magisk module for stereo sound
- Xiaomi Mi A2 navigation bar
- splash from stock firmware
- Dolby Atmos for Android 9
- Dolby Atmos for Android 8
- Unpacking payload.bin
- Viper fx
For questions of filling and updating the topic header, the Curator is always ready to help you. FranticKernel at QMS
Post has been editedFranticKernel - 19.06.19, 15:56
Reason for editing: Android 9 PKQ1.V10.0.10.0.PDIMIXM
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.
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 "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.
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 "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 ... -
!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 "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.
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 "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.
Post has been editedFranticKernel - 25.10.18, 14:00
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
Attention:When unlocking the bootloader, all data will be deleted !!!
8. Command line consistently Run the following commands to unlock the bootloader:
- fastboot flashing unlock
After you have entered the command, you will receive an unlock confirmation on your phone, confirm and after the phone restarts, go back to fastboot and enter the second command: - fastboot flashing unlock_critical
And confirm the second time.
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 flashing lock
Post has been editedFranticKernel - 08.05.19, 15:19
Reason for editing: Simplifying instructions
Instructions for flashing the original Fastboot image
(return to stock firmware)
(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.
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 .
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 :
1.7 Install drivers (if necessary) and unlock bootloader (if not done this early).
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
 |
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_data.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_data.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.
Windows:
"flash_all.bat" - for automatic firmware with removalall data on the device and subsequent maintaining statusopen bootloader .
"flash_all_except_data.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_data.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 editedFranticKernel - 25.10.18, 14:01
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
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:27
Reason for editing: Update
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.
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.
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 ".
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 editedFranticKernel - 25.10.18, 14:00
Official firmwareMi A2 V9.6.10.0.ODIMIFE (Android O) 1577MB
Post has been editedVYUEV - 08.08.18, 13:27
Post has been editedVYUEV - 08.08.18, 13:27
I suggest everyone to perform two simple commands.
Logs to copy into a text document and show in the case of bricks. Then you just can not do it.
Someone one, show in the message now.
fastboot getvar all
fastboot oem device-info
fastboot oem device-info
Logs to copy into a text document and show in the case of bricks. Then you just can not do it.
Someone one, show in the message now.
8. Copy the modified kernel in the /sdcard/MagiskManager/patched_boot.img to the unpacked folder with the adb / fastboot working utilities (C: \\ Tools).
If the kernel is not displayed in the explorer on the PC - just move it to the root of the user memory (/ sdcard).
I do not have a patched kernel in this folder.
If the kernel is not displayed in the explorer on the PC - just move it to the root of the user memory (/ sdcard).
I do not have a patched kernel in this folder.
uussttaass , go to this folder through the file manager of the phone and move the patched image to the root of the system. If there is no image, then you probably missed a step somewhere.
All of the instructions, the kernel coincides with the firmware 9.6.10, at the stage "fastboot boot patched_boot.img" on the screen of the phone "Your device is corrupted", in the console
Downloading 'boot.img' OKAY [0.614s]
booting FAILED (status read failed (Too many links))
fastboot flashing unlock_critical - does not pass, writes that it is already unlocked.
What could be the problem? I tried to roll the core twice already.
Downloading 'boot.img' OKAY [0.614s]
booting FAILED (status read failed (Too many links))
fastboot flashing unlock_critical - does not pass, writes that it is already unlocked.
What could be the problem? I tried to roll the core twice already.
Displax @ 08/10/18, 22:15
Reboot the bootloader, it hangs. If the error persists, change the USB connection port.
Thank. It helped to additionally make just fastboot flashing unlock. (I wanted to transfer - but it was impossible not to lock, not to unlock)
Good day)
When the boot loader is unlocked, when the smart is turned on, a dumb warning flies that the boot loader is unlocked. Very unaesthetic)
Really somehow remove it?)
When the boot loader is unlocked, when the smart is turned on, a dumb warning flies that the boot loader is unlocked. Very unaesthetic)
Really somehow remove it?)
[email protected], 03:24
Good day)
When the boot loader is unlocked, when the smart is turned on, a dumb warning flies that the boot loader is unlocked. Very unaesthetic)
Really somehow remove it?)
When the boot loader is unlocked, when the smart is turned on, a dumb warning flies that the boot loader is unlocked. Very unaesthetic)
Really somehow remove it?)
Xiaomi Mi A1 - Modification and decorations (Post Alexey_KF # 72182485)
iSmolin, The inscription Unlocked was removed from the boot screen of the android, but I was more confused by this:
 |
Post has been editedhonmiv - 13.08.18, 13:07
Gentlemen, who is not difficult to help? I can not block back the bootloader, I’m doing everything according to the instructions.
Good evening!
I'm trying to make root, but I get an error. Maybe someone knows what's the matter?
The issue was resolved, following the instructions again and changing the computer.
I'm trying to make root, but I get an error. Maybe someone knows what's the matter?
 |
 |
The issue was resolved, following the instructions again and changing the computer.
Displax @ 08/02/18, 18:56
P.S. To lock the bootloader, execute one of the following commands:
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 !!!
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 !!!
Those. If I temporarily receive a root to restore a backup from Titanium, everything will be in vain?
And the second question:
Which camera application would you recommend?
msasoft If you are ready not to block the bootloader back, then it is not in vain. With the unlocked loader only one inconvenience - dumb notice when you turn on the phone
[email protected], 16:20
Those. If I temporarily receive a root to restore a backup from Titanium, everything will be in vain?
©savagemessiahzine.com2005-2019. All rights reserved.
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement
savagemessiahzine.com®- registered trademark.
Terms of Use | Denial of responsibility | Advertising placement