Xiaomi Redmi Note 7 (xiaomi-lavender)
Kept this block as code, to prevent device auto-listing
{{Infobox device
| manufacturer = Xiaomi
| name = Redmi Note 7
| codename = xiaomi-lavender
| image = File:xiaomi-lavender.jpg
| imagecaption = Redmi Note 7
| releaseyear = 2019
| originalsoftware = Android 9, MIUI 10
| chipset = Qualcomm SDM660 Snapdragon 660 (14 nm)
| cpu = 8-core (4x2.2 GHz Kryo 260 & 4x1.8 GHz Kryo 260)
| gpu = Adreno 512
| storage = 32 (64) Gb
| display = 1080 x 2340
| memory = 3 (4) Gb
| architecture = aarch64
| status_usbnet =
| status_flashing = Y
| status_touch =
| status_screen =
| status_wifi =
| status_xwayland =
| status_fde =
| status_mainline =
| status_battery =
| status_3d =
| status_accel =
| status_audio =
| status_bluetooth =
| status_camera =
| status_gps =
| status_mobiledata =
| status_sms =
| status_calls =
| status = "Work not started yet"
| booting = no
| pmoskernel = 4.4.153
| whet_dhry = 0.0
| status_otg = -
}}
Contributors
Maintainer(s)
Users owning this device
Kept this block as code, to prevent device auto-listing
{{Device owners}}
How to enter flash mode
Bootloader Unlocking
Like other Xiaomi devices, the user will have to acquire the bootloader unlock key: https://en.miui.com/unlock
The device will not unlock if the device isn't 7 days old (from the time when your device connects to internet and powered on, and linked with Mi Account)
Recovery mode
- Turn the device off (or restart also works)
- Hold both volume buttons (+ and -) and power button
- Keep holding until you got to recovery.
Flashing (Download, Fastboot) mode
- Same as recovery, but this time hold the volume down key instead of both keys.
Installation
Should be as usual for fastboot devices
Additional info
Partition list
TODO: full layout with sizes
abl -> /dev/block/mmcblk0p25 ablbak -> /dev/block/mmcblk0p26 apdp -> /dev/block/mmcblk0p11 bk1 -> /dev/block/mmcblk0p49 bk2 -> /dev/block/mmcblk0p51 bluetooth -> /dev/block/mmcblk0p38 boot -> /dev/block/mmcblk0p60 cache -> /dev/block/mmcblk0p62 cmnlib -> /dev/block/mmcblk0p21 cmnlib64 -> /dev/block/mmcblk0p23 cmnlib64bak -> /dev/block/mmcblk0p24 cmnlibbak -> /dev/block/mmcblk0p22 cust -> /dev/block/mmcblk0p65 ddr -> /dev/block/mmcblk0p28 devcfg -> /dev/block/mmcblk0p31 devcfgbak -> /dev/block/mmcblk0p30 devinfo -> /dev/block/mmcblk0p43 dip -> /dev/block/mmcblk0p27 dpo -> /dev/block/mmcblk0p2 dsp -> /dev/block/mmcblk0p48 dtbo -> /dev/block/mmcblk0p52 dtbobak -> /dev/block/mmcblk0p53 frp -> /dev/block/mmcblk0p14 fsc -> /dev/block/mmcblk0p3 fsg -> /dev/block/mmcblk0p45 hyp -> /dev/block/mmcblk0p17 hypbak -> /dev/block/mmcblk0p18 keymaster -> /dev/block/mmcblk0p36 keymasterbak -> /dev/block/mmcblk0p37 keystore -> /dev/block/mmcblk0p13 limits -> /dev/block/mmcblk0p4 logdump -> /dev/block/mmcblk0p57 logfs -> /dev/block/mmcblk0p44 mdtp -> /dev/block/mmcblk0p50 mdtpsecapp -> /dev/block/mmcblk0p34 mdtpsecappbak -> /dev/block/mmcblk0p35 misc -> /dev/block/mmcblk0p42 modem -> /dev/block/mmcblk0p58 modemst1 -> /dev/block/mmcblk0p46 modemst2 -> /dev/block/mmcblk0p47 msadp -> /dev/block/mmcblk0p12 persist -> /dev/block/mmcblk0p55 persistbak -> /dev/block/mmcblk0p56 pmic -> /dev/block/mmcblk0p19 pmicbak -> /dev/block/mmcblk0p20 rawdump -> /dev/block/mmcblk0p59 recovery -> /dev/block/mmcblk0p61 rpm -> /dev/block/mmcblk0p15 rpmbak -> /dev/block/mmcblk0p16 sec -> /dev/block/mmcblk0p6 splash -> /dev/block/mmcblk0p54 ssd -> /dev/block/mmcblk0p5 lsti -> /dev/block/mmcblk0p39 storsec -> /dev/block/mmcblk0p9 storsecbak -> /dev/block/mmcblk0p10 switch -> /dev/block/mmcblk0p1 system -> /dev/block/mmcblk0p63 toolsfv -> /dev/block/mmcblk0p29 tz -> /dev/block/mmcblk0p32 tzbak -> /dev/block/mmcblk0p33 userdata -> /dev/block/mmcblk0p66 vbmeta -> /dev/block/mmcblk0p7 vbmetabak -> /dev/block/mmcblk0p8 vendor -> /dev/block/mmcblk0p64 xbl -> /dev/block/mmcblk0p40 xblbak -> /dev/block/mmcblk0p41
Android Verified Boot (vbmeta)
This device is using Android Verified Boot ( https://android.googlesource.com/platform/external/avb/+/refs/tags/android-vts-8.0_r11/README.md ) so you may need to flash vbmeta
partition with vbmeta.img
from LineageOS zip or downloaded separately (from https://androidfilehost.com/?fid=1395089523397954291 for example); or we need to find a way to generate it with avbtool
and flash it during installation somehow. (add pmbootstrap flasher flash_vbmeta
?)
DTBO partition
This device is using a dedicated partition to store the Device Tree Blob Overlay. Read more at https://source.android.com/devices/architecture/dto/partitions . We need to find a way to flash generated dt.img
to dtbo
partition during installation process. (add pmbootstrap flasher flash_dtbo
?)
See also
Nothing yet