User Tools

Site Tools


doc:appunti:hardware:xiaomi_mi_a1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
doc:appunti:hardware:xiaomi_mi_a1 [2018/11/19 17:47] – [Control and Privacy Settings] niccolodoc:appunti:hardware:xiaomi_mi_a1 [2019/11/09 14:48] – [Upgrading the Operating System] niccolo
Line 1: Line 1:
 ====== Xiaomi Mi A1 Android Phone ====== ====== Xiaomi Mi A1 Android Phone ======
  
 +{{:img:star_full.png?nolink&28|}}
 +{{:img:star_full.png?nolink&28|}}
 +{{:img:star_full.png?nolink&28|}}
 +{{:img:star_full.png?nolink&28|}}
 +{{:img:star_full.png?nolink&28|}}
 +
 +^ RAM              | 3.8 Gb  |
 +^ Internal Memory  | 32 Gb   |
 +^ CPU              | Qualcomm Snapdragon 625 2.0GHz 8-core  |
 +^ Screen           | 5.5 Inches, 1920 x 1080  |
 +^ Connector        | USB Type C  |
 +^ Audio jack       | 3.5 mm  |
 +^ A/B (Seamless) System Updates  | Yes  |
 ===== How to Gain root Privileges ===== ===== How to Gain root Privileges =====
  
Line 8: Line 21:
  
   - Install on your PC the **adb** and **fastboot** command line tools.   - Install on your PC the **adb** and **fastboot** command line tools.
-  - **Unlock** the Bootloader. 
   - **Backup**.   - **Backup**.
 +  - **Unlock** the Bootloader.
   - Install a **custom Recovery** program (we used [[https://twrp.me/|TWRP]]).   - Install a **custom Recovery** program (we used [[https://twrp.me/|TWRP]]).
   - Install the **su** binary and an app to manage **superuser privileges** (we used [[https://www.xda-developers.com/what-is-magisk/|Magisk]]).   - Install the **su** binary and an app to manage **superuser privileges** (we used [[https://www.xda-developers.com/what-is-magisk/|Magisk]]).
Line 55: Line 68:
 <code> <code>
 adb shell adb shell
-tissot_sprout:/ find /dev -name 'by-name' 2> /dev/null +tissot_sprout:/ $ ls -/dev/block/bootdevice/
-/dev/block/platform/soc/7824900.sdhci/by-name +
-cd /dev/block/platform/soc/7824900.sdhci/by-name +
-ls -l+
 ... ...
 lrwxrwxrwx 1 root root 21 1970-07-10 05:23 boot_a -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 1970-07-10 05:23 boot_a -> /dev/block/mmcblk0p22
Line 65: Line 75:
 </code> </code>
  
-The meaning is: search into **/dev/** for a directory named "**by-name**", look for the names **boot_a** and **boot_b** and take note of the actual partition names. You can see also that the **recovery** name does not exists.+The meaning is: search into **/dev/block/bootdevice/** for symbolic links **boot_a** and **boot_b** and take note of the actual partition names. You can see also that the **recovery** name does not exists.
  
 Now we need to **boot** into an environment where we have **root privileges**, otherwise we cannot read the entire partitions. This means booting into the **Fastboot Mode** bootloader and load and run the TWRP Recovery program. Now we need to **boot** into an environment where we have **root privileges**, otherwise we cannot read the entire partitions. This means booting into the **Fastboot Mode** bootloader and load and run the TWRP Recovery program.
  
 <code> <code>
-adb reboot-bootloader+adb reboot bootloader
 </code> </code>
  
Line 101: Line 111:
  
 <code> <code>
-adb reboot-bootloader+adb reboot bootloader
 fastboot boot recovery-3.2.1-2-oreo.img fastboot boot recovery-3.2.1-2-oreo.img
 </code> </code>
Line 107: Line 117:
 Once that TWRP is started on the phone, swipe to allow writing to the partitions, then choose **Install** and browse to the **Twrp-recoveryInstaller-3.2.1-2-oreo.zip** archive. Once that TWRP is started on the phone, swipe to allow writing to the partitions, then choose **Install** and browse to the **Twrp-recoveryInstaller-3.2.1-2-oreo.zip** archive.
  
-After the installation, the procedure will ask us if we want to **install the TWRP App**. You can answer yes, but it is not strictly required, the TWRP Recovery is a stand-alone program, it runs when requested without an underlying Android system and it does not require any App. The TWRP App may be used to install or upgrade the TWRP Recovery and to backup the existing Recovery, but it seems that the current version (1.19) is not able to handle the **A/B system updates** mechanism, it searches for the **recovery partition**, which **does not exist** in Xiaomi Mi A1 Oreo 8.1.0. So it's best not to use it.+After the installation, the procedure will ask us if we want to **install the TWRP App**, we answered **no**.You can answer yes, but it is not strictly required, the TWRP Recovery is a stand-alone program, it runs when requested without an underlying Android system and it does not require any App. The TWRP App may be used to install or upgrade the TWRP Recovery and to backup the existing Recovery, but it seems that the current version (1.19) is not able to handle the **A/B system updates** mechanism, it searches for the **recovery partition**, which **does not exist** in Xiaomi Mi A1 Oreo 8.1.0. So it's best not to use it.
  
 Beware of this: Beware of this:
  
 {{ .:android:xiaomi-mi-a1-android-system-corrupt.jpg?direct&240|System Corruption, Factory Reset Needed}} {{ .:android:xiaomi-mi-a1-android-system-corrupt.jpg?direct&240|System Corruption, Factory Reset Needed}}
-  * **Do not swap Slot A and Slot B**. Some recipes found on the internet say to do that in TWRP (it is from the Reboot menu). I tried it and it was a nightmare! The Reboot menu was stating that the Slot B were active, so I switched to Slot A and installed TWRP. At the next reboot I got a non-working environment: plenty of pop-up with **Android Phone force close**, pop-up for **Factory reset**, boot loop, etc. May be the Slot A contained the boot code for Android 8.0.0, whereas my phone already had received 8.1.0. Fortunately enough I was able to ''adb reboot-bootloader'' and switch again to Slot B.+  * **Do not swap Slot A and Slot B**. Some recipes found on the internet say to do that in TWRP (it is from the Reboot menu). I tried it and it was a nightmare! The Reboot menu was stating that the Slot B were active, so I switched to Slot A and installed TWRP. At the next reboot I got a non-working environment: plenty of pop-up with **Android Phone force close**, pop-up for **Factory reset**, boot loop, etc. May be the Slot A contained the boot code for Android 8.0.0, whereas my phone already had received 8.1.0. Fortunately enough I was able to ''adb reboot bootloader'' and switch again to Slot B.
   * **Do not veryfy the ZIP archive**. The archive does not have the required info to check.   * **Do not veryfy the ZIP archive**. The archive does not have the required info to check.
-  * **Do not wipe the Dalvik cache after the install**. Don't know if it was the culprit, but after installing TWRP, I clicked the button to wipe Dalvik cache, at the next reboot I had a damaged system. The **home button did not work**, the Developer options were no longer availables (//**Developer options are not available for this user**//), the top **status bar did not swipe** down, etc. I had to **Factory reset** the phone!+  * **Do not wipe the Dalvik cache after the install**. Don't know if it was the culprit, but after installing TWRP, I clicked the button to wipe Dalvik cache, at the next reboot I had a damaged system. The **home button did not work**, the Developer options were no longer availables (//**Developer options are not available for this user**//), the top **status bar did not swipe** down, etc. I had to **Factory reset** the phone (see a possible fix for this problem here: [[xiaomi_mi_a1_home_key_problem]]).
  
 ==== Install Magisk, the SuperUser Tool ==== ==== Install Magisk, the SuperUser Tool ====
  
 {{ .:android:xiaomi-mi-a1-magisk-su-install.jpg?direct&200|Magisk Install from TWRP Recovery}} {{ .:android:xiaomi-mi-a1-magisk-su-install.jpg?direct&200|Magisk Install from TWRP Recovery}}
-When rooting an Android device we generally need the **su** binary program (the actual Unix tool used to switch from normal user to root), plus an **app to manage superuser permissions** granted (or denied) to other applications. Historically the most known app for this purpose was **SuperSU** by Chainfire, but something changed. Chainfire [[https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ|retired from SuperSU development]] in October 2017 and new protecting schemas were introduced by Google into Android, mainly **[[https://developer.android.com/training/safetynet/|SafetyNet]]** and **[[https://source.android.com/security/verifiedboot/dm-verity|dm-verity]]**. The new leading-edge app for su management appears to be **Magisk**.+When rooting an Android device we generally need the **su** binary program (the actual Unix tool used to switch from normal user to root), plus an **app to manage superuser permissions** granted (or denied) to other applications. Historically the most known app for this purpose was **SuperSU** by Chainfire, but something changed. Chainfire [[https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ|retired from SuperSU development]] in October 2017 and new protecting schemas were introduced by Google into Android, mainly **[[https://developer.android.com/training/safetynet/|SafetyNet]]** and **[[https://source.android.com/security/verifiedboot/dm-verity|dm-verity]]**. The new leading-edge app for su management appears to be **[[https://github.com/topjohnwu/Magisk/|Magisk]]**.
  
-The first step is to install the ZIP archive which provides the **su** binary, we already copied the **Magisk-v17.3.zip** file to the phone storag. Let's reboot into TWRP Recovery executing from the connected PC the following command:+The first step is to install the ZIP archive which provides the **su** binary, we already copied the **Magisk-v17.3.zip** file to the phone storage. Let's reboot into TWRP Recovery executing from the connected PC the following command:
  
 <code> <code>
Line 151: Line 161:
 ===== Fastboot Mode ===== ===== Fastboot Mode =====
  
-Once in Recovery Menu, you can boot into the **Fastboot Mode** using the menu entry //Reboot to bootloader//Otherwise you can execute the **adb** command on PC when the phone is booted normally and connected via the USB cable (it is required to enable //USB debugging// on the phone and to authorize the PC on the phone pop-up, once connected):+In Android**fastboot** is a special diagnostic protocol that you can boot your Android device into. While in fastboot, you can modify the file system images from a computer over a USB connection.
  
-<code> +You can start fastboot mode in severl ways: 
-adb reboot bootloader + 
-</code>+  * Power off the phone, then press **VolumeDown + Power** buttons together, untill vibration. 
 +  * Executing the **adb reboot bootloader** command on a PC when the phone is booted normally and connected via the USB cable. It is required to enable //USB debugging// on the phone and to authorize the PC on the phone pop-up, once connected. 
 +  * From the **stock Recovery** menu, choosing the entry **Reboot to bootloader**. 
 +  * From the **TWRP Recovery**, choosing **Reboot** menu, then **Bootloader**. 
 + 
 +The Xiaomi Mi A1 will show the following image when in fastboot mode:
  
 {{.:android:mi-a1-fastboot-log.jpg?direct&200|Mi-A1 Fastboot Logo}} {{.:android:mi-a1-fastboot-log.jpg?direct&200|Mi-A1 Fastboot Logo}}
 +
 +To control the fastboot mode of the phone, you have to install the **fastboot** command on your PC. On a Debian GNU/Linux install the **fastboot 8.1.0** package. **NOTICE**: Version 7.0.0 is not reccomended, e.g. the command ''fastboot set_active b'' does not work on the Mi A1.
 +
 +Here are some commands that can be used in fastboot mode:
  
 <code> <code>
-adb devices +fastboot help 
-List of devices attached +fastboot devices 
-574524d99913    device+fastboot boot recovery-3.2.1-2-oreo.img 
 +fastboot flash boot_b boot_b.img 
 +fastboot oem unlock 
 +fastboot set_active b 
 +fastboot reboot
 </code> </code>
  
Line 199: Line 222:
     * Gmail     * Gmail
     * Google Play Film, ...     * Google Play Film, ...
-  * Settings => **Mi Services** 
-    * **User Experience Program** (Programma Esperienza Utente) 
-    * **Send diagnostic data automatically** (Invia i dati diagnostici automaticamente) 
-  * Google Play => Settings => **Auto-update apps** 
-  * Google Play => Settings => Notification settings => **Updates** 
-  * Contacts => Settings => **Default account for new contacts** 
  
   * Impostazioni => **Sicurezza e posizione**   * Impostazioni => **Sicurezza e posizione**
Line 214: Line 231:
     * Sicurezza => **Trova il mio dispositivo**     * Sicurezza => **Trova il mio dispositivo**
     * Posizione => **Modalità** (Alta precisione, Basso consumo, Solo dispositivo)     * Posizione => **Modalità** (Alta precisione, Basso consumo, Solo dispositivo)
 +    * Posizione => **Cronologia delle posizioni Google** 
     * Smart Lock per password => **Smart Lock per password** (salvare le password nel tuo Account Google)     * Smart Lock per password => **Smart Lock per password** (salvare le password nel tuo Account Google)
 +    * Altro (menu in alto a destra) => **Utilizzo e diagnostica** (off)
  
-  * FIXME Dove sono queste voci? +  * Settings => **Mi Services*
-    Aiuta le app a rilevare la posizione +    * **User Experience Program** (Programma Esperienza Utente) 
-    * Migliora la precisione +    * **Send diagnostic data automatically** (Invia dati diagnostici automaticamente) 
-    * Invia dati diagnostici e sull'utilizzo + 
-    Installa aggiornamenti e app (non disattivabile?)+  * Google Play => Settings => **Auto-update apps** 
 +  * Google Play => Settings => Notification settings => **Updates** 
 +  * Contacts => Settings => **Default account for new contacts**
  
 ===== Battery Otimization and Background Sync ===== ===== Battery Otimization and Background Sync =====
Line 227: Line 248:
  
   * Settings => Apps & notifications => Advanced => Special app access => **Battery optimization**   * Settings => Apps & notifications => Advanced => Special app access => **Battery optimization**
 +
 +===== Upgrading Android maintaining root privileges =====
 +
 +In November 2019 my phone still was running the following:
 +
 +  * **Android 8.1.0** - Patch 2018-10-05
 +  * **Magisk v17.3** (the **su** binary, etc.)
 +  * **MagiskManager v6.0.1** (the superuser rights management app)
 +  * **TWRP 3.2.1-2**
 +
 +MagiskManager warns about the availability of **Magisk v20.1**, the operating system too warns about the availability of **Nov 2018 Android System Update**. Also **MagiskManager** can be upgraded to **v7.4.0** (but **don't upgrade it before upgrading Magisk**, the app must follow exactly the **su** binary package contained in Magisk).
 +
 +==== Upgrade Magisk and MagiskManager ====
 +
 +  - Copy the **[[https://github.com/topjohnwu/Magisk/releases/download/v20.1/Magisk-v20.1.zip|Magisk-v20.1.zip]]** archive to the smartphone. TWRP will search by default into the internal storage, so I copied it into **/data/media/0/Download/**, but you can use the microSD storage.
 +  - Copy the **[[https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk|MagiskManager-v7.4.0.apk]]** app into the same **/data/media/0/Download/** directory, or into the microSD.
 +  - Reboot into TWRP recovery. I used the **adb reboot recovery** command from the PC, but you can use the **VolumeUp + Power** trick.
 +  - From the TWRP menu, choose **Install** and search for the Magisk-v20.1.zip archive.
 +  - I choosed not to verify the zip archive and not to reboot the phone, so I had time to read the output of the command. Everything seemed OK, so I finally **rebooted**.
 +  - Once rebooted in normal system, install **MagiskManager-v7.4.0.apk** from the file manager of your choice (it will require the permission //System// => //App// => <File manager> => //Unknown sources//).
 +
 +==== Upgrading the Operating System ====
 +
 +The phone automatically warns about the availability of an **OTA (On The Air) Upgrade**. You can also check for upgrades availability by tapping //Settings// => //System// => //**System Updates**//.
 +
 +If you allow downloading and installing the upgrade, a check will be performed about the **integrity** of the **boot image** and the **system image**, before the actual install. The check will fail and the upgrade will be aborted if one or both of these two conditions is true:
 +
 +  - You have installed **Magisk SU** or **TWRP Recovery**. These software are installed into the boot partition, either **boot_a** or **boot_b** partition. The installation of Magisk patches only the active boot partition, whereas TWRP will patches (install itself) both boot partitions.
 +  - You have used **su** to modify the **/system** partition. If you have **re-mounted** /system in **read/write** mode and you have altered it, the upgrade process will detect this and will refuse to proceed.
 +
 +The upgrade process will fail with a warning message **Couldn’t update - Installation problem** (in Italian: //Impossibile aggiornare - Problema di installazione//).
 +
 +To escape from the first condition, it is sufficient to **restore the boot partition** from the original backup. You will loose root and TWRP Recovery, but you can reinstall them after the upgrade. If you have just installed Magisk, uninstalling it should be sufficient and rather simple. Start the Magisk Manager app, disable and uninstall all the modules (if any) and reboot. Then run Magisk Manager again and choose to uninstall it completely. But if you have installed also TWRP you have to recover from a backup image. This is the recipe to run from a PC command line (supposing that **active partition is B** and that you have the original **boot_b.img** dump):
 +
 +<code>
 +adb reboot bootloader
 +fastboot flash boot_b boot_b.img
 +fastboot reboot
 +</code>
 +
 +Allowing automatic OTA upgrade after **tampering the /system partition** is more painful: you have to **restore system partition** by flashing it in fastboot mode. Obviously you need the original **system.img** file, either from your own backup or from factory ROM archive. Fortunately enough Xiaomi provides full stock ROM archives of the various versions. Look at this **[[https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929|forum post]]** and search for your version.
 +
 +Once you extracted the system.img file from the archive, boot in fastboot mode and execute the following from an attached PC (once again your **active partition is B**):
 +
 +<code>
 +fastboot flash system_b system.img
 +fastboot reboot
 +</code>
 +==== The OTA Update ====
 +
 +When the phone downloads an OTA upgrade, it will save it into the **/data/ota_package/update.zip** file, but it will be removed after the installation and even if the installation fails.
 +
 +The file is actualy a Jar archive. The jar executable is provided by the Debian package **openjdk-8-jdk-headless** (or whatever version of Java you have), and you can use it in this way:
 +
 +<code>
 +mkdir update
 +cd update
 +jar -xf ../update.zip
 +</code>
 +
 +The main content is a **payload.bin**, in our case it was an incremental update (November 2018 Security patches), with size of about 66 Mb. It seems that there is a tool able to extract the content of that payload files, see **[[https://forum.xda-developers.com/android/development/extract-files-ota-payload-bin-diff-t3959161|Extract files from OTA payload.bin full and incremental]]**.
  
 ===== Web References ===== ===== Web References =====
Line 233: Line 315:
   * [[https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472|Xiaomi Mi A1 tissot TWRP 3.2.1-2 (Oreo) Recovery]]   * [[https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472|Xiaomi Mi A1 tissot TWRP 3.2.1-2 (Oreo) Recovery]]
   * [[https://forum.xda-developers.com/mi-a1|Xiaomi Mi A1 Forum]]   * [[https://forum.xda-developers.com/mi-a1|Xiaomi Mi A1 Forum]]
 +  * [[https://forum.xda-developers.com/showpost.php?p=75545902&postcount=5|Help understanding A/B partitions]]
   * [[https://source.android.com/devices/tech/ota/ab/|A/B (Seamless) System Updates]]   * [[https://source.android.com/devices/tech/ota/ab/|A/B (Seamless) System Updates]]
   * [[https://forum.xda-developers.com/mi-a1/help/flash-twrp-partition-table-doesnt-exist-t3785354|Can't flash twrp.(partition table doesn't exist)]]   * [[https://forum.xda-developers.com/mi-a1/help/flash-twrp-partition-table-doesnt-exist-t3785354|Can't flash twrp.(partition table doesn't exist)]]
doc/appunti/hardware/xiaomi_mi_a1.txt · Last modified: 2020/09/23 17:06 by niccolo