Differences

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

--- doc:appunti:hardware:xiaomi_redmi_6 [2019/05/19 09:53] – [First attempt: failed] niccolo
+++ doc:appunti:hardware:xiaomi_redmi_6 [2019/08/02 18:36] (current) – [Xiaomi Redmi 6 Android Phone] niccolo
@@ Line 6: / Line 6: @@
 {{:img:star_empty.png?nolink&28|}}
 {{:img:star_empty.png?nolink&28|}}
+A brief review focused on **obtaining root privileges** and software de-bloating.
+| {{:img:pros_icon.png?nolink&36|}}  | Good **quality/price** ratio.\\ 3 Gb **RAM**.\\ Android **Oreo 8.1.**  |
+| {{:img:cons_icon.png?nolink&36|}}  | Unfriendly **rooting** procedure with some unsolved issues.\\ Bootloader **unlock requires MS-Windows** software.\\ MIUI O.S. filled with **bloatware**.\\ Double **privacy leak**: Google and Xiaomi apps.\\ Non replaceable **battery**.\\ **Proximity sensor problem**: fails when **closer than one centimeter**.  |
 ^ Model            | Redmi 6  |
@@ Line 101: / Line 106: @@
 When you run the TWRP Recovery for the first time, you can install **Magisk**. It provides the **su** program, the actual super-user command, and the **Magisk Manager**, the app which manages root permissions. We downloaded the **Magisk-v19.1.zip** file from the **[[https://github.com/topjohnwu/Magisk/releases|GitHub releases page]]** (4.7 Mb, md5sum 1205486d9302e2e8ea03d67bd1f67aa3). We copied the file to the **/sdcard** directory of the phone.
+**NOTICE**: Does not know if it matters: **I don't have cryptography enabled on the phone**. I think that this will easy any action performed from recovery. From phone settings: **Impostazioni** => //Impostazioni aggiuntive// => //Privacy// => //Crittografia e credenziali// => **Crittografa il dispositivo usando la password della schermata di blocco** (disabled).
 ==== 1st method: failed ====
@@ Line 112: / Line 118: @@
 Unfortunately the phone boots into normal system, not into Recovery. If you start Recovery (power down, **VolumeUp** + **Power** until the Mi logo is shown), you enter the stock **Mi-Recovery 3.0**. It is very likely that flashing went OK, but during the bootstrap **the recovery is automatically restored** to the stock one.
-==== Second attempt: success ====
+==== 2nd method: success ====
 **NOTICE**: The key difference of this recipe seems to be **flashing two partitions**: the one name **recovery** with the actual TWRP image and the one named **para**, with dummy data.
@@ Line 134: / Line 140: @@
   - Start **TWRP** as seen above.
   - Mount **system** and **vendor** partitions. From TWRP //Main menu//, //Mount//, tap //System// and //Vendor//. Then tap back.
+  - Execute **Install Root**. From TWRP //Main Menu//, //Advanced//. This option installs Magisk 19.0.
   - Execute **Sign Boot**. From TWRP //Main Menu//, //Advanced//, //Sign Boot//, //Swipe to Confirm//. Then tap back.
-  - Install **Magisk**. From TWRP //Main Menu//, //Install//, tap on //Magisk-v19.1.zip// file, (do not verify signature, do not reboot) //Swipe to confirm Flash//. After flashing tap the **Wipe Cache/Dalvik** button.
+  - Optional: install **Magisk 19.1**. From TWRP //Main Menu//, //Install//, tap on //Magisk-v19.1.zip// file, (do not verify signature, do not reboot) //Swipe to confirm Flash//. After flashing tap the **Wipe Cache/Dalvik** button.
   - **Reboot to System**.
+**NOTICE**: The LR.Team TWRP 3.3.0-0423 image **contains Magisk 19.0** (unpack the img file and extract the ramdisk content, you will find a ''/supersu/SuperSU_installer.zip'' file, which actually is Magisk). This is the **default root method**, and it is executed inside TWRP with the **Install Root** title.
+**NOTICE**: Some recipes on the net say to flash also **LazyFlash** or some other **DM Verity Disabler** tool. It seems that it is not longer require with Magisk 19. Infact, during Magisk installation, we read a log line stating **Removing dm(avb)-verity in dtb** (see ''/common/boot_patch.sh'' of the SuperSU_installer.zip file). By the way, the LR.Team TWRP image contains also the ''/supersu/no-verity-opt-encrypt.zip'' file into the ramdisk image, which actually is the LazyFlasher installer.
+**NOTICE**: It seems that flashing the **para** partition is a non-permanent action. If you want to boot into another recovery from the fastboot mode, you have to flash it again witht the dummy **misc.bin**.
 FIXME Sometimes the **/sbin/su** command **disappears**. It happened after a **system crash** (trying to remove one system app via //Titanium Backup//) or after a simple **system reboot**, or doing a **reboot from TWRP menu**. Fortunately enough, it was sufficient to reboot into TWRP Recovery and reinstall **Magisk-v19.1.zip**.
+==== 3rd method: failed ====
+Wishing to have the official TWRP image instead of an unofficial one, I used the previous method **substituting the LR.Team image** with the **official one** from TWRP (twrp-3.3.0-0-cereus.img). The TWRP official image were flashed, but the result was un **unbootable system!** Even booting in **fastboot** or **recovery** were problematic, because I got a black screen after the "Mi" logo regardless the key combination pressed at boot time.
+After several blind tries, **the TWRP screen eventually appeared**! Perhaps the right keys sequence was: power off, VolumeUp + Power, wait one minute, then VolumeDown + Power). Fromt the TWRP menu I fortunately booted in fastboot mode and re-flashed LR.Team image.
 ==== "Internal problem" warning message ====
@@ Line 278: / Line 297: @@
 {{.:redmi:redmi-6a_14-mi-unlock-couldnt-unlock.jpg?direct&128|Mi Unlock: Delay}}
+===== Hardware Tests  =====
+To enter the **hardware test mode** go to dialling screen and dial **%%*#*#64663#*#*%%**
+Here you can check if you are affected by the **proximity sensor problem**: move your hand toward the top of the phone, you should see that the proximity sensor //sense// your hand at a distance of about 3-5 cm. It should keep sensing it even if you touch the phone, but my model is defective: when you put your hand **closer than one centimeter**, the proximity **fail**.
 ===== Web References =====
@@ Line 289: / Line 313: @@
     * **[[https://en.gizchina.it/2018/09/xiaomi-redmi-6-bootloader-twrp-root-magisk/|Xiaomi Redmi 6: unlock bootloader, TWRP installation and root permissions with Magisk]]** - Another full recipe, based on recovery by TWRPBuilder, does not work for me.
     * **[[https://www.techdroidtips.com/xiaomi-redmi-6-install-twrp-recovery/|Download & Install TWRP Recovery on Xiaomi Redmi 6]]** - Using the official TWRP image, does not work for me.
-    * **[[https://miui.blog/redmi-6/flash-twrp-redmi-6-root/|How to Flash TWRP on Redmi 6 (and Root)]]** - Using the official TWRP image, Magisk or DM Veridy Disabler, does not work for me.
+    * **[[https://miui.blog/redmi-6/flash-twrp-redmi-6-root/|How to Flash TWRP on Redmi 6 (and Root)]]** - Using the official TWRP image, Magisk or DM Verity Disabler, does not work for me.
     * **[[https://forum.xda-developers.com/redmi-6-pro/how-to/boot-loader-unlock-twrp-installation-t3859220|Boot Loader Unlock/TWRP Installation – Redmi 6 Pro]]** - For the 6 Pro (TWRP for //sakura// build, not //cereus//).
   * **Install root permissions**