User Tools

Site Tools


doc:appunti:hardware:xiaomi_redmi_6

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
Last revision Both sides next revision
doc:appunti:hardware:xiaomi_redmi_6 [2019/05/20 10:34]
niccolo [2nd method: success]
doc:appunti:hardware:xiaomi_redmi_6 [2019/08/02 18:34]
niccolo [Misc]
Line 6: Line 6:
 {{:​img:​star_empty.png?​nolink&​28|}} {{:​img:​star_empty.png?​nolink&​28|}}
 {{:​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**. ​ |
  
 ^ Model            | Redmi 6  | ^ Model            | Redmi 6  |
Line 135: Line 140:
   - Start **TWRP** as seen above.   - Start **TWRP** as seen above.
   - Mount **system** and **vendor** partitions. From TWRP //Main menu//, //Mount//, tap //System// and //Vendor//. Then tap back.   - Mount **system** and **vendor** partitions. From TWRP //Main menu//, //Mount//, tap //System// and //Vendor//. Then tap back.
-  - FIXME: Should run **Install Root**, ​from //​Advanced// ​menu?+  - 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.   - 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**.   - **Reboot to System**.
  
-**NOTICE**: The LR.Team TWRP 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. May be, for this reason, installing Magisk 19.1 is not strictly required.+**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**: 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**. **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**.
Line 292: Line 297:
 {{.:​redmi:​redmi-6a_14-mi-unlock-couldnt-unlock.jpg?​direct&​128|Mi Unlock: Delay}} {{.:​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 ===== ===== Web References =====
  
doc/appunti/hardware/xiaomi_redmi_6.txt ยท Last modified: 2019/08/02 18:36 by niccolo