doc:appunti:hardware:xiaomi_mi_a1
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
doc:appunti:hardware:xiaomi_mi_a1 [2019/04/12 11:52] – [Upgrade Magisk and MagiskManager] niccolo | doc:appunti:hardware:xiaomi_mi_a1 [2019/11/06 18:27] – [Upgrade Magisk and MagiskManager] niccolo | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Xiaomi Mi A1 Android Phone ====== | ====== Xiaomi Mi A1 Android Phone ====== | ||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
^ RAM | 3.8 Gb | | ^ RAM | 3.8 Gb | | ||
Line 8: | Line 13: | ||
^ Connector | ^ Connector | ||
^ Audio jack | 3.5 mm | | ^ Audio jack | 3.5 mm | | ||
+ | ^ A/B (Seamless) System Updates | ||
===== 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:// | 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:// | ||
- | 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: |
< | < | ||
Line 257: | Line 262: | ||
* Backup **boot_a** and **boot_b** | * 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. | * 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 **Magisk**. FIXME Does the upgrade switch from boot_b to boot_a partition? If such case, we should to reinstall | + | * Eventually re-install |
+ | * Reading various posts it seems that on devices with the **Boot A/B** schema, there is not a recovery partition. Recovery is instead installed into either partition A or partition B, and it will overwritten when upgrading the operating system. | ||
===== Web References ===== | ===== Web References ===== | ||
doc/appunti/hardware/xiaomi_mi_a1.txt · Last modified: 2020/09/23 17:06 by niccolo