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 revision Previous revision
Next revision
Previous revision
doc:appunti:hardware:xiaomi_mi_a1 [2019/04/12 11:43]
niccolo [Install the TWRP Recovery]
doc:appunti:hardware:xiaomi_mi_a1 [2019/05/19 19:46] (current)
niccolo [Install Magisk, the SuperUser Tool]
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  | ^ RAM              | 3.8 Gb  |
Line 8: Line 13:
 ^ Connector ​       | USB Type C  | ^ Connector ​       | USB Type C  |
 ^ Audio jack       | 3.5 mm  | ^ Audio jack       | 3.5 mm  |
 +^ A/B (Seamless) System Updates ​ | Yes  |
 ===== How to Gain root Privileges ===== ===== How to Gain root Privileges =====
  
Line 129: Line 134:
 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 **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 254: Line 259:
  
 FIXME Write how to complete the upgrade! FIXME Write how to complete the upgrade!
 +
 +  * Backup **boot_a** and **boot_b**
 +  * Allow the system to **update**. FIXME Does it complete or will fail? May be it detects that the system was rooted and it will refuse.
 +  * Eventually re-install **TWRP** and **Magisk**. FIXME Does the upgrade switch from boot_b to boot_a partition? If such case, we should to reinstall TWRP and eventually Magisk.
 ===== Web References ===== ===== Web References =====
  
doc/appunti/hardware/xiaomi_mi_a1.1555062189.txt.gz ยท Last modified: 2019/04/12 11:43 by niccolo