> 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 A1 - Official firmware



Rep: (582)
Xiaomi Mi A1 - Official firmware
PictureModels: MDG2, MDI2 | Codenames: tissot, tissot_sprout
Description | Discussion пїЅ | Purchase пїЅ | Accessories пїЅ | Owners Club пїЅ | Camera talk пїЅ | Modification and decorations пїЅ | Power consumption (autonomy) пїЅ | Unofficial firmware пїЅ | Official firmware пїЅ

Questions that arise after the update

FAQ

Important information!

You can not reset the settings from stock recovery when you get root-rights through SuperSU!

It is impossibleBlock the bootloader, if you have root or modifications - this will lead to Bootloop (perpetual download). To block the bootloader, you can only on a clean system (without any changes in the system)
Drivers and Utilities
Firmware
Instructions
Recovery
Useful


For filling caps, please contact QMS

Post has been editedSSRPI - 25.06.19, 09:38
Reason for editing: Added OTA image 10.0.10.0 for Fastboot / TWRP, Added in instructions: Prevent downloading and installing updates without user permission



Rep: (5173)
This machine does not get it?
Why is it possible? Patch the kernel with Magisk, flash the kernel, install Magisk.
With SuperSU will be more difficult. Until TWRP appears (and even when it appears - it will be very buggy because of A / B), it will not be installed.
You can try through FlashFire, but it’s also full of glitches.

Post has been editedDisplax - 19.09.17, 16:24



Rep: (354)
Patch core Magisk

And what, for this unlocked boot and TWRP are not needed?



Rep: (5173)
* bbv62,
An unlocked boot is needed, TWRP is not necessary.
1. Razlachivaet bout.
2. Flash the patched kernel.
3. Install apk magisk and sew it into the system. Everything.



Rep: (354)
1. Razlachivaet bout.

This item is of interest.
It is assumed that there will also be syaomist "subscription unlock"?



Rep: (5173)
* bbv62,
Will not be. Elementary "fastboot oem unlock" here.



Rep: (9)
https://www.youtube.com/watch?v=cOOk217uJNcvideo unlocking bootloader



Rep: (5173)
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 A1 "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: "(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 up 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 A1 "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. Press the button Further . Wait for the installation to complete. Everything, the correct driver is installed and ready to work.

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

Post has been editedDisplax - 30.06.18, 13:31



Rep: (5173)
Instructions for the firmware of the original image
(return to stock firmware)
(fastboot)


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.

Provisions
With this manual you can:

1. Restore the device with a "bootlup" - "(bootloop)", due to unsuccessful: updates, getting root-rights, installing TWRP, applying modifications, installing custom kernels / firmwares, etc.
2. Restore the original state of the device (stock, clean firmware) and remove all traces of interference in the system.
3. Upgrade or, conversely, downgrade the firmware version of your choice.
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 .
Picture 1.1
Attached Image

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 ".
Picture 1.2.1
Attached Image

Image 1.2.2
Attached Image

1.3 Download the link from the header you need Fastboot image official firmware.
Picture 1.3
Attached Image

1.4 Unpack folder contents at * .tgz the image (archive) of the firmware in, previously unpacked, the folder " Tools ".
Note: For correct unpacking * .tgz images (archives) highly recommend use Winrar . Using 7-zip archive must be unpacked twice .
Note: Opening / Unpacking * .tgz images (archives) can take a long time. Be patient.
Picture 1.4
Attached Image

1.5 You should have the same set and file structure as on " Image 1.5 "below. We verify .
Picture 1.5
Attached Image

1.6 Install drivers for Fastboot mode . Driver installation details described in this post .
Note: For Linux and MacOS no need to install drivers. They are included by default in these operating systems.
Note: If the installation of the drivers was done earlier - skip this item .
2. Bootloader unlocking
Note: If the boot loader was unlocked earlier - skip this item .

2.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) ".

пїЅ The process of manually unlocking the bootloader
Note: The manual unlocking of the bootloader can be omitted, since the bootloader automatically unlocks when the image is flashed and locks back after the end of the firmware process.

2.2 Load the device into bootloader mode (Bootloader / Fastboot) :
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

2.3 Connect the device to the PC (if you have not done this earlier).

2.4 Go to the, previously unpacked, folder " Tools ". In it, from scratch, hold down the keys Shift + RMB (Right Mouse Key) .
In the menu that appears, select "Open command window ".
Note: If you have Windows 10 - run the command line directly from the address bar of the utility folder by typing " cmd ".
Picture 2.4
Attached Image


2.5 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

2.6 At the command prompt, run one of the following commands :

When unlocking and locking the bootloader, starting with the firmware from May 2018 (OPR1.170623.026.V9.5.11.0.ODHMIFA), all data will be deleted !!!

fastboot oem unlock
or
fastboot flashing unlock

Commands are equal, choose any.
3. Flashing process
3.1 Go back to the, early unpacked, folder " Tools ".
3.2 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 preservation *all data on the device and follow blocking* loader.
"flash_all_except_storage.bat" - for automatic firmware with saving **all data on the device and subsequent maintaining status **open 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!
* Saving data only if you install firmware released before May 2018 (before assembling OPR1.170623.026.V9.5.11.0.ODHMIFA)!
** Use (replace the batch file in the working folder) to install firmware released after May 2018 (after assembling OPR1.170623.026.V9.5.11.0.ODHMIFA (and including it))!

Problem solving:
Problem: After running the script, the command prompt window closes immediately.
Decision: This happens due to the lack of executable programs ("fastboot.exe, etc.") in the working directory ("Tools" folder). Check the consistency of your working folder with the reference screenshot in the instructions above - "Image 1.5". Also, other errors are possible, to display them, run the firmware script directly from the running command line.

Problem: After running the script, I get the error: "" findstr "is not an internal or external command, an executable program, or a batch file."
Decision: This problem occurs because of damage to the paths of variable environments in your Windows.
Either correct the paths of the variable environments, or replace and use the scripts from this archive:Attached filebatch.zip(2.42 KB)

Problem: The process starts normally, but when I flash the system image (system.img), I get the errors: "error: cannot load load" * ~ \ system.img "or" FAILED (remote: data too large) ".
Decision: You are using (very) old versions of working utilities, "fastboot.exe" in particular. Please update them to the latest version. Links to fresh utility packages you will find in the header.

Problem: After running the script, I get the error: "Warning: Device A / B support is outdated. Bootloader update required." and "FAILED (remote: partition table doesn't exist)".
Decision: You have Xiaomi Mi 5X with firmware and a stripped down bootloader from Xiaomi Mi A1. Sew it in the way of Xiomi Mi A1 will not work. Please visit the topic. Xiaomi Mi 5X - MIUI firmware to return the original firmware of your Xiaomi Mi 5X.


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 preservation *all data on the device and follow blocking *loader .
"flash_all_except_storage.sh" - for automatic firmware with saving **all data on the device and subsequent maintaining status **open 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!
* Saving data only if you install firmware released before May 2018 (before assembling OPR1.170623.026.V9.5.11.0.ODHMIFA)!
** Use (replace the scripts in the working folder) to install the firmware released after May 2018 (after building OPR1.170623.026.V9.5.11.0.ODHMIFA (and including it))!

Problem solving:
Problem: After running the script, I get the error: "error: Missmatching image and device", "error: unlock error", "error: Flash modem_a error", etc.
Decision: These errors occur because the script does not manage to find the "fastboot" binary in global variable environments, and the script "does not look" in the current directory. Either install adb / fastboot "globally", via "sudo", according to this instruction , or replace and use scripts from this archive for local use: Attached fileshell.zip (2.73 KB)

Problem: The process starts normally, but when I flash the system image (system.img), I get the errors: "error: cannot load load" * ~ \ system.img "or" FAILED (remote: data too large) ".
Decision: You are using (very) old versions of working utilities, "fastboot.exe" in particular. Please update them to the latest version. Links to fresh utility packages you will find in the header.

Problem: After running the script, I get the error: "Warning: Device A / B support is outdated. Bootloader update required." and "FAILED (remote: partition table doesn't exist)".
Decision: You have Xiaomi Mi 5X with firmware and a stripped down bootloader from Xiaomi Mi A1. Sew it in the way of Xiomi Mi A1 will not work. Please visit the topic. Xiaomi Mi 5X - MIUI firmware to return the original firmware of your Xiaomi Mi 5X.


3.3 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.

Please note that the first download after applying any update can be quite long.



Post has been editedDisplax - 04.06.18, 23:19



Rep: (20)
For some reason, quoting does not work (.
In general, the instruction is verified, it works, the root has been received.
Only it is necessary to add that before the start of manipulations adb-debugging must be enabled in the menu "For Developers".
Well, you can clarify that after running root.bat in fastboot mode, you need to wait until the deviceselfwill reboot (will occur in approximately one minute).
SuperSU apk can be installed in advance or after.



Rep: (5173)
__m1x__ @ 09/26/17, 23:05*
Only it is necessary to add that before the start of manipulations adb-debugging must be enabled in the menu "For Developers".
Do not need it there.



Rep: (5173)
How to get a link to the OTA update


The manufacturer sends OTA incremental and full OTA updates.
It would be nice to know their links to create homemade stock firmware.


We get a direct link to OTA:
1. We catch the update and start downloading it.
2. Go to the menu item "For Developers".
3. We request the creation of an error report by clicking on the item "Error Report".
4. The collection and generation of the report will begin, with a duration of about one minute.
5. After the process is completed, a notification about the successful creation of a report appears in the blind. Click on it.
6. The log should weigh about 10-12 MB. We will be offered various options for saving / transferring a file. We save the finished report in the device's memory (we need Solid Explorer). Or, you can save it as a gmail draft and download the finished file from there.
7. We attach the finished report file in this topic, or independently find the link in the log by mask: "xiaomi_tissotsprout_tissot" (without quotes).

Post has been editedDisplax - 01.07.18, 21:36



Rep: (20)
The ruled phone after OTA went into a cyclic reboot. Am I the only one?)
If anyone encounters:
1. Nakatka through the fastboot official firmware via "flash_all_except_storage.bat" so that the data will remain (the root flies);
2. Install OTA update;
3. Again we get the root according to the instructions.

Post has been editedDisplax - 12.10.17, 15:16



Rep: (593)
Magisk version 14.1 has the correct support for the A / B update system.Proof.
This made it possible to install OTA updates while keeping the installed Magisk.
Instruction.
Short translation:
1. Restore the stock boot in Magisk Manager, but do not reboot the device.
2. Start installing the update using the usual method, i.e. as it would have been without Magisk.
3. As soon as the update goes through the first stage, go to the Magisk Manager and install the Magiskin the second slot. After that, wait until the update is complete and reboot. Everything should be in place.

Owners, check;)



Rep: (5173)
OTA image:N2G47H.7.9.21
https: //android.google…cd8956ef1ac7f87aa3.zip
https://android.googleapis.com/packages/ota-api/xiaomi_tissotsprout_tissot/1708f685882654506222b8cd8956ef1ac7f87aa3.zip


Post has been editedDisplax - 02.10.17, 01:20



Rep: (793)
M
We move to subsectionXiaomi .



Rep: (2415)
Displax @ 09/29/17, 19:08*
For a long time in a hat.

Add for September patch
https: //forum.xda-deve…tember-update-t3681024

Or just flash the kernel and install the SuperSU application.
https: //forum.xda-deve...=73977357&postcount=15



Rep: (5173)
* kep2008,
It does not matter. CFAR for each assembly do not need to rivet, and the current one works fine.



Rep: (2415)
* kep2008,
It does not matter. CFAR for each assembly do not need to rivet, and the current one works fine.

OK...

But it is important to me, I want, after the upgrade, to have an updated kernel, and not from the previous build, even if it works ...: D



Rep: (5173)
* kep2008,
It does not work that way.
In the CF-Auto-Root command is used:
fastboot boot boot.img

That is temporary, one-time loading of the modified kernel. It is not stitched.
Upon subsequent loading, this kernel is loaded, the necessary scripts are executed in it (by analogy with the zip installation in TWRP) and the device is rebooted with its own native kernel (patched to work with SuperSU).

Post has been editedDisplax - 29.09.17, 19:54



Rep: (5173)
* kep2008,
By the way. Since you have root rights, as I understand it, I will ask you to execute the command in ADB and attach its output.
Or maybe someone else wants ...
adb shell
su
ls -la / dev / block / bootdevice / by-name /

This is our partition table.
I will be grateful.

Post has been editedDisplax - 29.09.17, 20:03


Full version    

Help     rules

Now: 29.06.19, 20:18