Because I was struggling to find them, I create a thread to offer the information I gathered.
So, here is a small list of the builds number and their equivalent OS version:
10.0.10586.0 -> 10.0.13052.0
10.0.10586.11 -> 10.0.13058.11
10.0.10586.29 -> 10.0.13065.29
10.0.10586.36 -> 10.0.13067.36
10.0.10586.63 -> 10.0.13070.63
10.0.10586.71 -> 10.0.13073.71
10.0.10586.107 -> 10.0.13080.107
10.0.10586.122 -> 10.0.13086.122
10.0.10586.164 -> 10.0.13090.164
10.0.10586.218 -> 10.0.13111.218
10.0.10586.242 -> 10.0.13125.242
10.0.10586.318 -> 10.0.13169.318
Hello i tought it share my findings here
Huawei P20 Partitions
Code:
HWEML:/dev/block/platform/ff3c0000.ufs/by-name $ ls -la
total 0
drwxr-xr-x 2 root root 1300 2018-03-28 14:54 .
drwxr-xr-x 4 root root 1420 2018-03-28 14:54 ..
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 bootfail_info -> /dev/block/sdd18
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 cache -> /dev/block/sdd58
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 certification -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 cust_a -> /dev/block/sdd56
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 ddr_para -> /dev/block/sdd15
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dfx -> /dev/block/sdd20
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dto_a -> /dev/block/sdd43
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 dts_a -> /dev/block/sdd42
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_kernel_a -> /dev/block/sdd35
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_ramdisk_a -> /dev/block/sdd36
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_vbmeta_a -> /dev/block/sdd48
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 erecovery_vendor_a -> /dev/block/sdd37
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fastboot_a -> /dev/block/sdd28
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 frp -> /dev/block/sdc1
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fw_hifi_a -> /dev/block/sdd32
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 fw_lpm3_a -> /dev/block/sdd22
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hdcp_a -> /dev/block/sdd24
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hhee_a -> /dev/block/sdd26
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_encos -> /dev/block/sdd13
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_fs_a -> /dev/block/sdd27
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 hisee_img_a -> /dev/block/sdd25
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 isp_boot_a -> /dev/block/sdd30
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 isp_firmware_a -> /dev/block/sdd31
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 kernel_a -> /dev/block/sdd38
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 misc -> /dev/block/sdd19
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modem_fw_a -> /dev/block/sdd45
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modem_om -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modem_secure -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_backup -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_cust_a -> /dev/block/sdd51
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 modemnvm_factory -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_img -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_system -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 modemnvm_update_a -> /dev/block/sdd50
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 nvme -> /dev/block/sdd4
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 odm_a -> /dev/block/sdd57
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 oeminfo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 patch_a -> /dev/block/sdd52
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 persist -> /dev/block/sdc2
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 product_a -> /dev/block/sdd55
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 ramdisk_a -> /dev/block/sdd39
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_ramdisk_a -> /dev/block/sdd40
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_vbmeta_a -> /dev/block/sdd47
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 recovery_vendor_a -> /dev/block/sdd41
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 reserved1 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved2 -> /dev/block/sdd16
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved3_a -> /dev/block/sdd23
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 reserved4_a -> /dev/block/sdd46
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 rrecord -> /dev/block/sdd21
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 secure_storage -> /dev/block/sdd7
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 sensorhub_a -> /dev/block/sdd34
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 splash2 -> /dev/block/sdd17
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 system_a -> /dev/block/sdd59
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 teeos_a -> /dev/block/sdd33
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 trustfirmware_a -> /dev/block/sdd44
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 userdata -> /dev/block/sdd60
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vbmeta_a -> /dev/block/sdd49
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vector_a -> /dev/block/sdd29
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 vendor_a -> /dev/block/sdd54
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 veritykey -> /dev/block/sdd14
lrwxrwxrwx 1 root root 16 2018-03-28 14:54 version_a -> /dev/block/sdd53
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 vrl -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 2018-03-28 14:54 vrl_backup -> /dev/block/sdd2
Code:
HWEML:/system $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.4G 12M 1.4G 1% /
tmpfs 1.7G 684K 1.7G 1% /dev
/dev/block/dm-0 4.3G 3.2G 1.1G 75% /system
/dev/block/dm-1 747M 688M 44M 94% /vendor
/dev/block/dm-2 120M 110M 7.2M 94% /odm
/dev/block/dm-3 27M 516K 26M 2% /version
/dev/block/dm-4 182M 114M 64M 65% /product
/dev/block/dm-5 182M 44M 134M 25% /cust
tmpfs 1.7G 0 1.7G 0% /mnt
none 1.7G 0 1.7G 0% /sys/fs/cgroup
/dev/block/sdd60 111G 3.6G 106G 4% /data
/dev/block/sdd58 122M 60K 119M 1% /cache
/data/media 111G 4.9G 106G 5% /storage/emulated
Hope it helps some one
Can you check for this? https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
Here we go
Cant get the unlock code from the huawei site then i would try phh AOSP
Yes the P20 Lite ANE-LX1 is also Treble enabled but is A only
crucky said:
Here we go
Cant get the unlock code from the huawei site then i would try phh AOSP
Click to expand...
Click to collapse
Hey please tell me what you did?
I just remote helped a guy to bootloader unlock his demo unit
Sent from my DUK-L09 using Tapatalk
IMEI SN Missmatch always the same on the P20 Lite Demo Unit it worked
EDIT:I Saw you posted a tutorial for unlock will try it now with my demo unit
LastStandingDroid said:
Hey please tell me what you did?
I just remote helped a guy to bootloader unlock his demo unit
Click to expand...
Click to collapse
How did you unlock the Demo Unit? Mine has OEM lock and I can't unlock it in the developer options.
Nogorka said:
How did you unlock the Demo Unit? Mine has OEM lock and I can't unlock it in the developer options.
Click to expand...
Click to collapse
Simply by enable developer options and tick oem unlock? You'd have to ask the guy who owns it
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Simply by enable developer options and tick oem unlock? You'd have to ask the guy who owns it
Click to expand...
Click to collapse
The owner is a Provider because it's a Demo unit from "my" shop. And i can't enable the OEM unlock option, it's grayed out. I thought you could help me with unlocking it, sorry!
Nogorka said:
The owner is a Provider because it's a Demo unit from "my" shop. And i can't enable the OEM unlock option, it's grayed out. I thought you could help me with unlocking it, sorry!
Click to expand...
Click to collapse
Greyed out? Sounds like they disabled it.
Is it the demo version which has the demo app? Because on the p20 pro it was possible to unlock. And it was demo store unit
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Greyed out? Sounds like they disabled it.
Is it the demo version which has the demo app? Because on the p20 pro it was possible to unlock. And it was demo store unit
Click to expand...
Click to collapse
Yeah, there ist the retail Demo on it, and a "explore P20" app too. Okay.. than ill have to wait till somebody know how to enable the OEM unlock. Thanks a lot!
Nogorka said:
Yeah, there ist the retail Demo on it, and a "explore P20" app too. Okay.. than ill have to wait till somebody know how to enable the OEM unlock. Thanks a lot!
Click to expand...
Click to collapse
Hello i own a Demo phone to EML-L29 non-pro you can enable oem unlock by factory reseting and connecting wifi also turn on developer options then and connect and disconnect the type c usb.After a while i could enable it and unlocked the bootloader of the demo unit running phh treble aosp rom
crucky said:
Hello i own a Demo phone to EML-L29 non-pro you can enable oem unlock by factory reseting and connecting wifi also turn on developer options then and connect and disconnect the type c usb.After a while i could enable it and unlocked the bootloader of the demo unit running phh treble aosp rom
Click to expand...
Click to collapse
Could you try
https://mega.nz/#!xGYSiSCS!cgkEfytbI_D8BUl2HjQB1qtGuTPc7Rw2630HIHXxGKE
Eml patched
Sent from my DUK-L09 using Tapatalk
LastStandingDroid said:
Could you try
https://mega.nz/#!xGYSiSCS!cgkEfytbI_D8BUl2HjQB1qtGuTPc7Rw2630HIHXxGKE
Eml patched
Sent from my DUK-L09 using Tapatalk
Click to expand...
Click to collapse
Yes will try it tomorrow because today i need my phone and iam currently running phh AOSP not Demo Stock
crucky said:
Yes will try it tomorrow because today i need my phone and iam currently running phh AOSP not Demo Stock
Click to expand...
Click to collapse
That shouldn't matter should work on both stock and phh
Sent from my DUK-L09 using Tapatalk
Can confirm works great Deinstalled the Demo APK
crucky said:
Can confirm works great Deinstalled the Demo APK
Click to expand...
Click to collapse
Do you mean that you're running AOSP with magisk patched boot image on Huawei P20 (EML)?
No switched back to stock. but will try it now again with phh AOSP somone here with a C432 P20 EML-L29 ? maybe you can give me a dump of CUST ? then i would try to rebrand from my demo C652. @LastStandingDroid maybe we can find a solution for rebrand ? because i modded CUST partition the only problem i have now i cant set fingerprint or faceunlock because of that its very annoying. @ectroplasma22 do you have it ? Maybe you could grab the full package firmware ? Still isnt avaible @ FF only funkyhuawei
Great news guys.
There a working twrp for you guys
Bad news I can't share since user who created it is banned.
Also decryption won't work. So it's basically useless for mate P20 pro users.
Good thing lite/regular should be good to go. If having a external Sd!
Edit it did not
Picture tells u what to Google for. Please do not ask for link!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my DUK-L09 using Tapatalk
Ok the patched ramdisk isnt working with RROS
Hi, I'm trying to build lineage 16 for my oxygen device. But after repo sync I'm getting this error:
/root/build.sh: line 141: [: $(PLATFORM_VERSION
$(TARGET_PLATFORM_VERSION): integer expression expected
>> [Sun Apr 7 06:12:21 UTC 2019] Missing "vendor/cm", abort
I can't find /root/build.sh and why is "vendor/cm" missing ??
why do I need this "cm" folder ?
I have the same problem as you.
Set cache size limit to 50.0 GB
>> [Fri Apr 12 18:47:02 UTC 2019] Branch: lineage-16.0
>> [Fri Apr 12 18:47:02 UTC 2019] Devices: herolte,hero2lte,
>> [Fri Apr 12 18:47:05 UTC 2019] (Re)initializing branch repository
>> [Fri Apr 12 18:47:07 UTC 2019] Copying '/srv/local_manifests/*.xml' to '.repo/local_manifests/'
>> [Fri Apr 12 18:47:07 UTC 2019] Syncing branch repository
/root/build.sh: line 141: [: $(PLATFORM_VERSION
$(TARGET_PLATFORM_VERSION): integer expression expected
>> [Fri Apr 12 18:49:54 UTC 2019] Missing "vendor/cm", aborting
~/LineageOS/16.0_microG $
xiaomi A3 laurel_sprout partitions table
Code:
18:29 ALIGN_TO_128K_1 -> /dev/block/sdd1
18:29 ALIGN_TO_128K_2 -> /dev/block/sdf1
18:29 abl_a -> /dev/block/sde8
18:29 abl_b -> /dev/block/sde29
18:29 apdp -> /dev/block/sde45
18:29 bk03 -> /dev/block/sde54
18:29 bluetooth_a -> /dev/block/sde5
18:29 bluetooth_b -> /dev/block/sde26
18:29 boot_a -> /dev/block/sde11
18:29 boot_b -> /dev/block/sde32
18:29 catecontentfv -> /dev/block/sde61
18:29 catefv -> /dev/block/sde60
18:29 cateloader -> /dev/block/sde51
18:29 cdt -> /dev/block/sdd2
18:29 cmnlib64_a -> /dev/block/sde13
18:29 cmnlib64_b -> /dev/block/sde34
18:29 cmnlib_a -> /dev/block/sde12
18:29 cmnlib_b -> /dev/block/sde33
18:29 ddr -> /dev/block/sdd3
18:29 devcfg_a -> /dev/block/sde14
18:29 devcfg_b -> /dev/block/sde35
18:29 devinfo -> /dev/block/sde43
18:29 dip -> /dev/block/sde44
18:29 dsp_a -> /dev/block/sde9
18:29 dsp_b -> /dev/block/sde30
18:29 dtbo_a -> /dev/block/sde18
18:29 dtbo_b -> /dev/block/sde39
18:29 frp -> /dev/block/sda5
18:29 fsc -> /dev/block/sdf5
18:29 fsg -> /dev/block/sdf4
18:29 gsort -> /dev/block/sde62
18:29 hyp_a -> /dev/block/sde3
18:29 hyp_b -> /dev/block/sde24
18:29 imagefv_a -> /dev/block/sde19
18:29 imagefv_b -> /dev/block/sde40
18:29 keymaster_a -> /dev/block/sde10
18:29 keymaster_b -> /dev/block/sde31
18:29 keystore -> /dev/block/sda4
18:29 limits -> /dev/block/sde48
18:29 logdump -> /dev/block/sde53
18:29 logfs -> /dev/block/sde50
18:29 mdtp_a -> /dev/block/sde7
18:29 mdtp_b -> /dev/block/sde28
18:29 mdtpsecapp_a -> /dev/block/sde6
18:29 mdtpsecapp_b -> /dev/block/sde27
18:29 metadata -> /dev/block/sda14
18:29 minidump -> /dev/block/sda11
18:29 misc -> /dev/block/sda3
18:29 modem_a -> /dev/block/sde4
18:29 modem_b -> /dev/block/sde25
18:29 modemst1 -> /dev/block/sdf2
18:29 modemst2 -> /dev/block/sdf3
18:29 multiimgoem -> /dev/block/sde56
18:29 multiimgqti -> /dev/block/sde57
18:29 odm_a -> /dev/block/sda8
18:29 odm_b -> /dev/block/sda9
18:29 oem -> /dev/block/sda10
18:29 persist -> /dev/block/sda2
18:29 product_a -> /dev/block/sda6
18:29 product_b -> /dev/block/sda7
18:29 qupfw_a -> /dev/block/sde15
18:29 qupfw_b -> /dev/block/sde36
18:29 rawdump -> /dev/block/sde52
18:29 rpm_a -> /dev/block/sde1
18:29 rpm_b -> /dev/block/sde22
18:29 secdata -> /dev/block/sde59
18:29 splash -> /dev/block/sde47
18:29 spunvm -> /dev/block/sde46
18:29 ssd -> /dev/block/sda1
18:29 storsec -> /dev/block/sde55
18:29 storsec_a -> /dev/block/sde21
18:29 storsec_b -> /dev/block/sde42
18:29 system_a -> /dev/block/sda12
18:29 system_b -> /dev/block/sda13
18:29 toolsfv -> /dev/block/sde49
18:29 tz_a -> /dev/block/sde2
18:29 tz_b -> /dev/block/sde23
18:29 uefisecapp_a -> /dev/block/sde20
18:29 uefisecapp_b -> /dev/block/sde41
18:29 uefivarstore -> /dev/block/sde58
18:29 userdata -> /dev/block/sda15
18:29 vbmeta_a -> /dev/block/sde17
18:29 vbmeta_b -> /dev/block/sde38
18:29 vendor_a -> /dev/block/sde16
18:29 vendor_b -> /dev/block/sde37
18:29 xbl_a -> /dev/block/sdb1
18:29 xbl_b -> /dev/block/sdc1
18:29 xbl_config_a -> /dev/block/sdb2
18:29 xbl_config_b -> /dev/block/sdc2
Version 2​Works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Build Date:
2020/05/13
Android Version:
QP1A.190711.020
Display ID:
AL2522-Merlin-V039-Q-0513
Build Fingerprint:
Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
Security Patch:
2019/12/05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V94.3
Kernel Version:
4.14.141-gf3c3c7a
Wed May 13 12:49:46 CST 2020
Download:
https://www.mediafire.com/file/02xo...V039-Q-0513_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use any scatter file specific for MERLIN.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6768_MOLY_LR12A_R3_MP_V94_3_2019_12_31_16_23.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19.xz
md1_mddbmeta=MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3.EDB
Prop.default:
Code:
ro.build.version.incremental=258
ro.odm.build.version.incremental=258
ro.vendor.build.version.incremental=258
ro.build.version.security_patch=2019-12-05
ro.vendor.build.security_patch=2019-12-05
ro.build.display.id=AL2522-Merlin-V039-Q-0513
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp2-V1.4_huaqin.q0mp1.k69v1.64_P1
ro.build.product=merlin
ro.product.board=merlin
ro.product.odm.device=merlin
ro.product.odm.model=merlin
ro.product.odm.name=merlin
ro.product.product.device=merlin
ro.product.product.model=merlin
ro.product.product.name=merlin
ro.product.system.device=merlin
ro.product.system.model=merlin
ro.product.system.name=merlin
ro.product.vendor.device=merlin
ro.product.vendor.model=merlin
ro.product.vendor.name=merlin
ro.build.flavor=merlin-userdebug
ro.build.description=merlin-userdebug 10 QP1A.190711.020 258 test-keys
ro.board.platform=mt6768
ro.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.bootimage.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.product.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.system.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/merlin/merlin:10/QP1A.190711.020/258:userdebug/test-keys
ro.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.type=userdebug
ro.vendor.build.type=userdebug
ro.bootimage.build.date=Wed May 13 12:41:51 CST 2020
ro.build.date=Wed May 13 12:41:51 CST 2020
ro.odm.build.date=Wed May 13 12:41:51 CST 2020
ro.product.build.date=Wed May 13 12:41:51 CST 2020
ro.system.build.date=Wed May 13 12:41:51 CST 2020
ro.vendor.build.date=Wed May 13 12:41:51 CST 2020
MD5 hashes:
Code:
APDB_MT6768_S01__W1953 -> 3adfe0c4e41828cd51ed783da774bd08
boot-debug.img -> e9dfb7dde67795157a871bc14b490054
boot.img -> d6e19a30d85a27379d91072665ad43c9
cache.img -> c40c137a18a26980d406d4ef0ccd7e61
cust.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
DbgInfo_LR12A.R3.MP_HUAQIN_Q0MP1_MT6769_SP_MOLY_LR12A_R3_MP_V94_3_2020_03_26_19_19_1_ulwctg_n -> b5bf654ddaacfd61e78c131f721974af
dtb.img -> ec4b37b164f1bd9ce6f2b1b911ac0872
dtbo-verified.img -> 9b0fa19089a0310325b88eebc8e41ae7
dtbo.img -> 9b0fa19089a0310325b88eebc8e41ae7
efuse.img -> 421f2cead0fbea555680b96136555941
exaid.img -> e8c4e9f4ee0fe5052cf0dc356aedd8de
lk-verified.img -> 0ba475d8c216b2613815b59e3db8da2b
lk.img -> 0ba475d8c216b2613815b59e3db8da2b
logo.bin -> 257508aa9cdeb690e4a4ed038c91ff76
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> 27cd78644df092ade4ca03799dc3c2a3
md1img.img -> 27cd78644df092ade4ca03799dc3c2a3
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB.META.ODB_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.XML.GZ -> 4e040508c1878706a428c54ef0844e0f
MDDB.META_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> 7c1ecfd4e3d626957b6655f107824649
MDDB_InfoCustomAppSrcP_MT6768_S00_MOLY_LR12A_R3_MP_V94_3_1_ulwctg_n.EDB -> b24757bd125ad435bd2d26575b5c1d75
MT6768_Android_scatter.txt -> 0a8f16b2276ee9c37337a3937f71a7c8
preloader.img -> dbc21da31860042674fab69d07444e95
preloader_emmc.img -> dbc21da31860042674fab69d07444e95
preloader_merlin.bin -> bc7ebc0c2ca06b0d99856d595949e215
preloader_ufs.img -> 29ef0e631a45bf14555fd6b7adb7a7bf
product.img -> 7ec4f1ffd2b49d7c5b4f1bb5d3ba0dc6
ramdisk-debug.img -> b6048055b240d3c9f6933544b86416b5
ramdisk-recovery.img -> 77de275ef543e46bbedfd53b7e36f945
ramdisk.img -> 545ec84cf25662d1e4f4cf7e496fa56e
recovery.img -> 6362f1beb617572680f3fc91640d3767
scp-verified.img -> 2cac6177dc7eec82421cb3f4a2776aff
scp.img -> 2cac6177dc7eec82421cb3f4a2776aff
secro.img -> 096587b863e1252d67b1b8307291db09
spmfw-verified.img -> 40345cc1edec88bcd510fa62eac01739
spmfw.img -> 40345cc1edec88bcd510fa62eac01739
sspm-verified.img -> 0ceaf392e89bf70c9a52a5c91cc75865
sspm.img -> 0ceaf392e89bf70c9a52a5c91cc75865
super.img -> d3a61d5292e4584bb3932abb7d6984bf
super_empty.img -> a6d56d7a12d989bf31511d866449291d
system.img -> 1a191b461d47c0a7bf8ce08d3c09001e
tee-verified.img -> 4f2fdf78d5be3a5de0154c46af69d476
tee.img -> 4f2fdf78d5be3a5de0154c46af69d476
userdata.img -> 802561cd4739f2f0aae7a51890a5866f
vbmeta.img -> 31da88d4a00b99b36081f859f17f808a
vbmeta_system.img -> a6b560b53a42c98fba204f2b69e70fd7
vbmeta_vendor.img -> 86fae46d211bdedcb49bd08e901d4d3f
vendor.img -> e609cb6a9d7ae103a64d9fe856d4edae
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
What's different in V2 and the one which was posted earlier?
Communos said:
What's different in V2 and the one which was posted earlier?
Click to expand...
Click to collapse
Its funny how VD171 never mention about the difference of this v2 to the old one
What is engineering firmware?
Bharath kota said:
What is engineering firmware?
Click to expand...
Click to collapse
A ROM with few or minor security patches.
Essentialy for doing things not allowed in released firmwares.
Sorry, what is the password?, I can't find
eric_new_master said:
Sorry, what is the password?, I can't find
Click to expand...
Click to collapse
On the attachment "PASSWORD_by_VD171.txt".
VD171 said:
On the attachment "PASSWORD_by_VD171.txt".
Click to expand...
Click to collapse
the thing is that now winrar doesnt let us open files inside an archive without a password so we cant access it now. i just guessed it and it
worked. lol
Kaustubh Mishra said:
the thing is that now winrar doesnt let us open files inside an archive without a password so we cant access it now. i just guessed it and it
worked. lol
Click to expand...
Click to collapse
and i didnt see the attachment too. lol im a fool
Kaustubh Mishra said:
and i didnt see the attachment too. lol im a fool
Click to expand...
Click to collapse
The file is attached on the thread:
https://forum.xda-developers.com/attachments/password_by_vd171-txt.5249247/
Volte not working for Merlin Redmi note 9 ( Indian user).
Volte option is available in setting menu. But volte not working.