Database Develop

[DEV] NEXUS 4 MOUNT POINTS

/dev/block/platform/msm_sdcc.1/by-name:
lrwxrwxrwx root root 2012-11-13 19:02 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2012-11-13 19:02 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-11-13 19:02 abootb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-11-13 19:02 boot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-13 19:02 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2012-11-13 19:02 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-11-13 19:02 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2012-11-13 19:02 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2012-11-13 19:02 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-13 19:02 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2012-11-13 19:02 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-13 19:02 rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-11-13 19:02 rpmb -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-11-13 19:02 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-13 19:02 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-13 19:02 sbl2b -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-11-13 19:02 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-13 19:02 sbl3b -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-11-13 19:02 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2012-11-13 19:02 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-13 19:02 tzb -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2012-11-13 19:02 userdata -> /dev/block/mmcblk0p23
Also provided by c900712 is the Voodoo Report file for the Nexus 4 it may be interesting reading for some people.
EDIT:
Originally posted by Houstonn in post#28
Code:
LG Nexus 4 Mako - LGE960 JVP15Q
Number Start (sector) End (sector) Size Code Name
1 1024 132095 64.0 MiB 0700 modem
2 132096 133119 512.0 KiB FFFF sbl1
3 133120 134143 512.0 KiB FFFF sbl2
4 134144 138239 2.0 MiB FFFF sbl3
5 138240 139263 512.0 KiB FFFF tz
6 139264 184319 22.0 MiB FFFF boot
7 184320 229375 22.0 MiB FFFF recovery
8 229376 230935 780.0 KiB FFFF m9kefs1
9 230936 232495 780.0 KiB FFFF m9kefs2
10 232496 234055 780.0 KiB FFFF m9kefs3
11 234496 235519 512.0 KiB FFFF rpm
12 235520 236543 512.0 KiB FFFF aboot
13 236544 237567 512.0 KiB FFFF sbl2b
14 237568 241663 2.0 MiB FFFF sbl3b
15 241664 242687 512.0 KiB FFFF abootb
16 242688 243711 512.0 KiB FFFF rpmb
17 243712 244735 512.0 KiB FFFF tzb
18 244736 245759 512.0 KiB 8301 metadata
19 245760 278527 16.0 MiB FFFF misc
20 278528 311295 16.0 MiB 8300 persist
21 311296 2031615 840.0 MiB 8300 system
22 2031616 3178495 560.0 MiB 8300 cache
23 3178496 15267839 5.8 GiB 8300 userdata
24 15267840 15268863 512.0 KiB FFFF DDR
25 15268864 15269854 495.5 KiB 8300 grow
Mark.

check ur email
Sent from my Nexus 4 using xda premium

c900712 said:
check ur email
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you thats everything I needed.
Mark.

That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
Sent from my DROID2 GLOBAL using xda app-developers app

Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4

EddyOS said:
Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4
Click to expand...
Click to collapse
Just extract system img and then you must make a file for mako to make kitchen work (maybe)
Sent from my HTC Explorer A310e using xda app-developers app

All that's the easy part, it's getting the right mount points so it'll flash correctly. Comparing the OP to existing device files doesn't mean a lot to me unfortunately! Here's the edify_defs file for the Galaxy Nexus if someone wants to help out?
# Samsung Galaxy Nexus (GSM/HSPA+)
change_mnt=yes
param1=ext4
param2=HSMMC
sys_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/system
cache_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/cache
boot_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/boot
data_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/userdata
sdcard_mnt=???
fix_boot3=yes

zyy757 said:
That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
Sent from my DROID2 GLOBAL using xda app-developers app
Click to expand...
Click to collapse
Just download Voodoo Report from the Market and save the output to your usb storage. It will save a zip file to your Internal Storage that has all the info you need.
Mark.

Also got the issue of not being able to deodex the ROM using the kitchen as it's not supporting SDK17 yet...d'oh!

Any ETA for your tool kit please?

vinnyutd6899 said:
Any ETA for your tool kit please?
Click to expand...
Click to collapse
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.

mskip said:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
Click to expand...
Click to collapse
I can test if you want. Just send me an email when you would like to.

mskip said:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
Click to expand...
Click to collapse
i will test it

Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.
Mark.

mskip said:
Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.
Mark.
Click to expand...
Click to collapse
Yeah thats worked for me

[vertigo] said:
Yeah thats worked for me
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 4 mit Tapatalk 2

[vertigo] said:
Yeah thats worked for me
Click to expand...
Click to collapse
P0MM3S said:
+1
Gesendet von meinem Nexus 4 mit Tapatalk 2
Click to expand...
Click to collapse
Thank you very much I can finish building the toolkit now. I will post when its ready for testing and see who is available. The initial version will have custom recovery operations blocked as it isnt available yet but it shouldnt be long before a working recovery is built.
Mark.

I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
Sent from my Nexus 4 using Tapatalk 2

Kstarz said:
I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.
The one I made and posted a few posts back has been reported to work fine.
Mark.

mskip said:
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.
The one I made and posted a few posts back has been reported to work fine.
Mark.
Click to expand...
Click to collapse
Yes booting it works fine but flashing it doesn't and I am unsure why it doesn't.
Sent from my Nexus 4 using Tapatalk 2

[Q] Creating partition images on 870A

Does anyone know the relation of which block devices in /dev/mmcblk0pXX belong to which partition? (ex: system, modem, boot, etc)
I'm looking to create a custom Odin AIO package for my install of lollipop, which has been rooted and such; going back to NE4 is a PITA and would like a faster route for when a full wipe is required.
Thanks in advance :good:

After scrounging the internet for awhile, I was able to answer my own question. I've posted the partition scheme below for others who might need it someday:
aboot -> /dev/block/mmcblk0p6
apnhlos -> /dev/block/mmcblk0p1
backup -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p15
cache -> /dev/block/mmcblk0p24
dbi -> /dev/block/mmcblk0p4
ddr -> /dev/block/mmcblk0p5
efs -> /dev/block/mmcblk0p12
fota -> /dev/block/mmcblk0p17
fsc -> /dev/block/mmcblk0p19
fsg -> /dev/block/mmcblk0p9
modem -> /dev/block/mmcblk0p2
modemst1 -> /dev/block/mmcblk0p13
modemst2 -> /dev/block/mmcblk0p14
pad -> /dev/block/mmcblk0p10
param -> /dev/block/mmcblk0p11
persdata -> /dev/block/mmcblk0p22
persist -> /dev/block/mmcblk0p21
recovery -> /dev/block/mmcblk0p16
rpm -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p25

ZD551KL/ZE550KL/ZE551KL/ZE600KL/ZE601KL official bootloader unlock

Released on asus website 14/12/2015:
Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551KL/UnlockTool_ASUS_AndroidM20160928_Singed.zip
Lollipop:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/ZE600KL_UnlockApp.zip
The APKs for each are binary identical, so it is not really important which unlock utility you download.
Frequently asked questions:
Q: will this work on ZE500KG / ZE500KL / ASUS_Z00RD / ASUS_Z00RD_5 / ASUS_Z00RD_7 / ASUS_Z00ED / ASUS_Z00EDB / ASUS_Z00E_1 / ASUS_Z00E_2 / ASUS_Z00E_3
A: we do not think so, but we do not know if anyone has tried it.
Q: can I relock bootloader?
A: we do not have a way of re-locking bootloader right now. Hopefully it will be possible using a backup of some partition to restore original bootloader, but we have not found it yet.
Q: can I restore my warranty by re-locking the bootloader?
A: we believe that ASUS records the serial number of the device through the unlock utility, so it will not be possible to make a warranty claim even if you do manage to re-lock the bootloader.
Q: can I still receive OTA updates?
A: we do not know, because no updates have been released since the unlock utility was released.
Q: can I still update firmware manually?
A: yes, definitely. fetch the new firmware zip from ASUS website and flash in stock recovery or transfer to root of sd-card and boot the phone normally (it will find the update zip file and prompt you).
Download notes from the site:
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V1.15.40.771 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
Click to expand...
Click to collapse

Do you think this would work on the US 551KL? If so thatd be great

* edit *
firmware v1.15.40.771 now released for ZE600KL, so I will try to flash now on ZE550KL and then unlock
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip

Please note, I have ZE550KL-1A025TW version, Snapdragon 615, 2GB RAM (ASUS_Z00LD / ASUS_Z00L_93)
I updated my ZE550KL to firmware v1.15.40.771:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip
then ran the ZE600KL unlock utility.
Unlock utility runs without errors, phone reboots, no errors, everything still working fine.
Confirmed unlock successful
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s

Let me get this straight, you flashed ZE600KL firmware on your ZE550KL and it worked? Not something I would recommend.

Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk

You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"

Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery

wickedpygmy said:
Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?

capeorigins said:
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery
Click to expand...
Click to collapse
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...

destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
Code:
C:\adb>adb devices
List of devices attached
F8AZCY01P722 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
C:\adb>

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.

destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
heywheelie said:
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?
Click to expand...
Click to collapse
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.

Titokhan said:
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
Click to expand...
Click to collapse
@Titokhan must be too late for me to do this, since I already unlocked and have no way to get back?
attached is aboot and abootbak after unlocking, maybe @heywheelie can upload the before?

destilant said:
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...
Click to expand...
Click to collapse
the ZE550KL has a snapdragon 615 not 610

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
doesnt look like folder exists.
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/
drwxr-xr-x root root 1970-05-15 01:49 7824900.sdhci
[email protected]_Z00L_93:/ #

heywheelie said:
the ZE550KL has a snapdragon 615 not 610
Click to expand...
Click to collapse
init! i wish people would stop polluting the version/hardware topic, especially since its so confusing already

wickedpygmy said:
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.
Click to expand...
Click to collapse
might be same firmware but specs do differ slightly
https://www.asus.com/Phone/ZenFone-2-Laser-ZE550KL/specifications/
https://www.asus.com/Phone/ZenFone-2-Laser-ZE600KL/specifications/
WLAN bands differ, bluetooth is 4.0 on 550 and 4.1 on 6.0. Nothing dramatic but different

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
This any use?
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-05-15 01:49 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-15 01:49 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-15 01:49 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-15 01:49 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-15 01:49 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-15 01:49 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-15 01:49 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-15 01:49 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-15 01:49 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-15 01:49 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-15 01:49 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-15 01:49 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-15 01:49 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-15 01:49 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-15 01:49 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-15 01:49 config -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-15 01:49 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-15 01:49 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-15 01:49 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-15 01:49 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-15 01:49 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-15 01:49 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-15 01:49 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-15 01:49 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-15 01:49 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-15 01:49 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-15 01:49 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-15 01:49 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-15 01:49 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-15 01:49 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-15 01:49 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-15 01:49 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-15 01:49 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-15 01:49 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-15 01:49 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-15 01:49 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-15 01:49 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-15 01:49 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-15 01:49 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-15 01:49 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-15 01:49 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-15 01:49 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-15 01:49 userdata -> /dev/block/mmcblk0p46
[email protected]_Z00L_93:/ #

[CLOSED] T-Mobile OnePlus 7T Pro 5G McLaren DEV Starts here...

*Request: Can anyone post the super.img of a OnePlus 7T Pro/McLaren (Global Edition)? If you don't know how and still want to help, please let me know. Thank You!
Under construction > > > Temp DEV and Research area...
Before messing with your phone, please check post #4 on how to backup your partitions.
This is the first step towards DEV (You first compare... then make changes/modify and ultimately create a ROM) In the meantime, we will have to work with Magisk Modules.
Special thanks to @jhofseth for providing the TMO 5G images & @ntzrmtthihu777 (also @DanDroidOS) for messing up the phone and requesting the images.
I basically extracted the 5G images and added the Global Images (also extracted)
Okay, here is the deal... The file below is a RAR with 2 folders inside: (ALL files extracted & ready - NO IMG)
Folder > mclaren_global_TEKHD (based on OnePlus 7T Pro McLaren Global Firmware with Security Patch 2019-11-01 [hotdog])
with Sub Folders:
odm
product
system
vendor
Folder > mclaren_TMO_5G_TEKHD (based on TMO OnePlus 7T Pro 5G McLaren Firmware 10.0.13.HD61CB with Security Patch 2019-10-01 [hotdogg]
with Sub Folders:
odm
product
system
vendor
The idea is to encourage development by providing a direct comparison between the 2 Firmwares (Global vs TMO 5G). You can use a software like "Beyond Compare" (or any other) in order to compare files. (Left Side Global vs Right Side TMO 5G)
OnePlus7TPro_Global_vs_TMO_5G_Partitions_DEV_KIT_TEKHD.rar

Dual SIM on OnePlus 7T Pro 5G McLaren > Can anyone test this:
\vendor\build.prop
Search:
Code:
persist.radio.multisim.config=ssss
...replace with:
Code:
persist.radio.multisim.config=dsds
...see screenshot below

Activate 5G Radio on OnePlus 7T Pro Global McLaren (When using Global Firmware on TMO 5G Variant) > Can anyone test this:
\vendor\build.prop
Search:
Code:
persist.vendor.radio.5g_mode_pref=0
...replace with:
Code:
persist.vendor.radio.5g_mode_pref=1
...see screenshot below

How to backup your own partitions before messing with the phone:
Partition Structure on OnePlus 7T Pro 5G McLaren Edition:
Code:
ls -al /dev/block/platform/soc/1d84000.ufshc/by-name
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 5gdump -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 LOGO_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 LOGO_b -> /dev/block/sde47
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 abl_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 aging -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 aging_mod -> /dev/block/sde55
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 aop_b -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 apdp -> /dev/block/sde59
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 bluetooth_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 boot_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 carrier -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 catecontentfv -> /dev/block/sde72
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 catefv -> /dev/block/sde71
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cateloader -> /dev/block/sde66
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib64_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 cmnlib_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 config -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 core_nhlos -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 devcfg_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 devinfo -> /dev/block/sde57
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dip -> /dev/block/sde58
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dsp_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dtbo_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 dtbo_b -> /dev/block/sde44
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs1_a -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs1_b -> /dev/block/sde48
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs2_a -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs2_b -> /dev/block/sde49
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs3_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs3_b -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs4_a -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs4_b -> /dev/block/sde51
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs5_a -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 fw_ufs5_b -> /dev/block/sde52
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 hyp_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 imagefv_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 imagefv_b -> /dev/block/sde46
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 keymaster_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 limits -> /dev/block/sde63
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 logdump -> /dev/block/sde67
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 logfs -> /dev/block/sde65
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefs1 -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefs2 -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefs3 -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdm1m9kefsc -> /dev/block/sdf9
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdm1oemnvbktmp -> /dev/block/sde77
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdm_oem_dycnvbk -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdm_oem_stanvbk -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdmddr -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdtp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 mdtpsecapp_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 metadata -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 modem_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 msadp -> /dev/block/sde60
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 multiimgoem_a -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 multiimgoem_b -> /dev/block/sde53
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 op1 -> /dev/block/sde56
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 param -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 qupfw_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 rawdump -> /dev/block/sda20
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 recovery_a -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 recovery_b -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve1 -> /dev/block/sde73
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve2 -> /dev/block/sde74
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve3 -> /dev/block/sde75
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 reserve4 -> /dev/block/sde76
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 secdata -> /dev/block/sde70
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 splash -> /dev/block/sde62
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 spunvm -> /dev/block/sde61
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 storsec_a -> /dev/block/sde68
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 storsec_b -> /dev/block/sde78
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 super -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 toolsfv -> /dev/block/sde64
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 tz_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 uefisecapp_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 uefisecapp_b -> /dev/block/sde45
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 uefivarstore -> /dev/block/sde69
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 userdata -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_system_a -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 1970-01-29 11:39 vbmeta_system_b -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1970-01-29 11:39 xbl_config_b -> /dev/block/sdc2
Boot into Fastboot ->
Code:
adb reboot fastboot
Run TWRP -> (You need to have twrp.img on your ADB folder)
Code:
fastboot boot ./twrp.img
For example, if you want to backup LOGO_a ->
Code:
adb pull /dev/block/sde21 LOGO_a.img
After you are done, simply exit/reboot from TWRP (with no modifications, read only)
or
Code:
adb reboot
Done
Automatic Extraction Tool for TMO 5G McLaren available here.

Announcement:
I have created a series of Highly Experimental ROMs. Files are based on Global Firmware. I also have restore/revert files for each Experimental ROM. We can FLASH ZIP -> TEST -> RESTORE. It's LITERALLY a trial & error WIP and THERE IS ALWAYS THE POSSIBILITY OF THINGS GOING WRONG!
-> ROM ZIPS are designed from BASIC TO COMPLEX - English please? -> I will try to flash the less amount of partitions required in order to make Global firmware boot & work on our device. I will start with a few partitions (partitions that I know are 100% required) and then move to a more complex set of partitions if required.
-> We will try to boot with our Kernel as well as the Global Kernel. Again, Trial & Error.
Requirements:
- ADB/Fastboot/Linux Knowledge (at least the basic commands and some common sense)
- Ability to follow instructions
- Patience (each file is 2GB+ in size... and the process is a bit time consuming)
- Balls of steel
- Dual SIM Tray (optional)
If you want to test, you are welcome to join my new Telegram Channel -> HERE - My 2 favorite bots are already there waiting for you!
-> I will prepare and upload everything tomorrow, (and during the the next few days) while people start joining the channel.
Thank You,
TEKHD

@TEKHD Is there any way you could post these partitions? I think I'm gonna need all of them because I flashed the Int version. The system, product, and vendor that we have now just gets me a Qualcomm error
aop.img
bluetooth.img
boot.img
dsp.img
dtbo.img
LOGO.img
modem.img
oem_stanvbk.img
qupfw.img
storsec.img
multiimgoem.img
uefisecapp.img
recovery.img
vbmeta.img
vbmeta_system.img
opproduct.img

DanDroidOS said:
@TEKHD Is there any way you could post these partitions?
aop.img
bluetooth.img
boot.img
dsp.img
dtbo.img
LOGO.img
modem.img
oem_stanvbk.img
qupfw.img
storsec.img
multiimgoem.img
uefisecapp.img
recovery.img
vbmeta.img
vbmeta_system.img
opproduct.img
Click to expand...
Click to collapse
How to restore your OnePlus 7T Pro 5G McLaren: (with easy flash-all.bat script for Windows and flash-all.sh script for Linux)
https://forum.xda-developers.com/showpost.php?p=81374031&postcount=67
Thanks @jhofseth
________________________________________________________
@Some_Random_Username Please, can you pull all partitions from latest OnePlus 7T Pro Global McLaren?
Like @jhofseth did above? See Link
Those global images can help a lot here. We might end up using Magisk Modules for modifications but I would like to see a few things.

Ideally it would be good to get dumps from multiple people with multiple versions
and compare hashes of the files to be certain that these dumps are identical across
all the phones.

Tell me what you need I'll do my best. I'm still awaiting my unlock bin from OnePlus but I'm definitely interested in converting to global.

TEKHD said:
@Some_Random_Username Please, can you pull all partitions from latest OnePlus 7T Pro Global McLaren?
Like @jhofseth did above? See Link
Those global images can help a lot here. We might end up using Magisk Modules for modifications but I would like to see a few things.
Click to expand...
Click to collapse
Not sure if this is relevant but I managed to extract OnePlus7TOxygen_14.O.08_OTA_008_all_1911061912_3b6d7f83eb174cbc.zip
from oneplus's firmware download into individual images; could be helpful?
Nvm. Just realized that was the 7t, not 7t pro. Afaict there is no stock image for that up anywhere yet?

ntzrmtthihu777 said:
Not sure if this is relevant but I managed to extract OnePlus7TOxygen_14.O.08_OTA_008_all_1911061912_3b6d7f83eb174cbc.zip
from oneplus's firmware download into individual images; could be helpful?
Nvm. Just realized that was the 7t, not 7t pro. Afaict there is no stock image for that up anywhere yet?
Click to expand...
Click to collapse
I am using ro.system.build.fingerprint=OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys on my OP kit. I would like a clean pull from the device itself if possible as a failsafe. (device running whatever latest global firmware; basically something that compares to our current version) Remember, we can't risk ourselves too much. Restoring partitions via fastboot is still risky business.
by the way... @ntzrmtthihu777 > Is your fingerprint working fine? @DanDroidOS seems to be having fingerprint issues after restoring.

TEKHD said:
I am using ro.system.build.fingerprint=OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys on my OP kit. I would like a clean pull from the device itself if possible as a failsafe. (device running whatever latest global firmware; basically something that compares to our current version) Remember, we can't risk ourselves too much. Restoring partitions via fastboot is still risky business.
by the way... @ntzrmtthihu777 > Is your fingerprint working fine? @DanDroidOS seems to be having fingerprint issues after restoring.
Click to expand...
Click to collapse
I have a logcat if you can make sense of it

TEKHD said:
I am using ro.system.build.fingerprint=OnePlus/OnePlus7TPro/OnePlus7TPro:10/QKQ1.190716.003/1912060020:user/release-keys on my OP kit. I would like a clean pull from the device itself if possible as a failsafe. (device running whatever latest global firmware; basically something that compares to our current version) Remember, we can't risk ourselves too much. Restoring partitions via fastboot is still risky business.
by the way... @ntzrmtthihu777 > Is your fingerprint working fine? @DanDroidOS seems to be having fingerprint issues after restoring.
DanDroidOS said:
I have a logcat if you can make sense of it
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hadn't tried it (not putting too much work into customizing the phone as I don't intend
to stay on stock any longer than needed) but just set up a thumb print and it seems to be fine.
What exactly are you having issues with, setting it up or using it? Not to be a **** but the
sensor seems quite anal about dirty print area and dirty fingers, perhaps a good scrub down
of both could help? Also are you using any sort of screen protector or just bare screen?
And sure, gimme da logcat.

ntzrmtthihu777 said:
Hadn't tried it (not putting too much work into customizing the phone as I don't intend
to stay on stock any longer than needed) but just set up a thumb print and it seems to be fine.
What exactly are you having issues with, setting it up or using it? Not to be a **** but the
sensor seems quite anal about dirty print area and dirty fingers, perhaps a good scrub down
of both could help? Also are you using any sort of screen protector or just bare screen?
And sure, gimme da logcat.
Click to expand...
Click to collapse
It's not the sensor, it won't even let me register a fingerprint.

DanDroidOS said:
I have a logcat if you can make sense of it
Click to expand...
Click to collapse
Possibly, if you're rooted, have Android terminal and download the attached on phone:
su
cp -f /sdcard/Download/settings_fingerprint.xml /data/system/users/0/settings_fingerprint.xml
chmod 600 /data/system/users/0/settings_fingerprint.xml
reboot
(or modified via adb)

DanDroidOS said:
It's not the sensor, it won't even let me register a fingerprint.
Click to expand...
Click to collapse
Huh, not getting that here. And where is the logcat?

Here is the logcat:

DanDroidOS said:
Here is the logcat:
Click to expand...
Click to collapse
I know it would probably be long and drawn out, but can you
say exactly what you've done to the phone up to this point?
flashing, bricking, unbricking. what and how you've done it.

@DanDroidOS maybe you could do a Titanium backup, copy to external storage before factory resetting? IMHO, at this point, just going nuclear with factory reset would be what I'd do.

ntzrmtthihu777 said:
I know it would probably be long and drawn out, but can you
say exactly what you've done to the phone up to this point?
flashing, bricking, unbricking. what and how you've done it.
Click to expand...
Click to collapse
unllocked sim & bootloader ==> flashed Omni on slot b: ended up with no calls or text ==> flashed 10.0.4 Europe fastboot rom on slot b: wouldn't boot ==> flashed Omni on slot b: to wait for an update to fix calls ==> Set active back to ' slot a' to see if I could recover ==> flashed dump & super.img: now I'm on 10.0.16 with no working fingerprint

General [ENGINEERING][ROM][OFFICIAL] OFFICIAL Engineering Firmware for LIME (Redmi 9 Power / Redmi 9T)

Works with:
- Xiaomi Redmi 9 Power
- Xiaomi Redmi 9T
Build Date:
2021/06/13
Android Version:
QKQ1.200730.002
Display ID:
QL2880-lime-V065-Q-0613
Build Fingerprint:
Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
Security Patch:
2020-10-01
Radio/Modem/Baseband Version:
A.1.0-00505.1-KAMORTA_GEN_PACK-3
Download:
https://www.mediafire.com/file/y25b...ing_QL2880-lime-V065-Q-0613_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
Prop.default:
Code:
ro.build.version.incremental=1648
ro.odm.build.version.incremental=1648
ro.vendor.build.version.incremental=1648
ro.product.board=lime
ro.product.odm.device=lime
ro.product.odm.model=lime
ro.product.odm.name=lime
ro.product.system.device=lime
ro.product.system.model=lime
ro.product.system.name=lime
ro.product.vendor.device=lime
ro.product.vendor.model=lime
ro.product.vendor.name=lime
ro.build.flavor=lime-userdebug
ro.build.display.id=QL2880-lime-V065-Q-0613
ro.board.platform=bengal
ro.build.id=QKQ1.200730.002
ro.odm.build.id=QKQ1.200730.002
ro.system.build.id=QKQ1.200730.002
ro.vendor.build.id=QKQ1.200730.002
ro.bootimage.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.system.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648: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.build.version.security_patch=2020-10-01
ro.vendor.build.security_patch=2020-10-01
ro.bootimage.build.date=Sun Jun 13 11:26:22 CST 2021
ro.build.date=Sun Jun 13 11:26:22 CST 2021
ro.odm.build.date=Sun Jun 13 11:26:22 CST 2021
ro.system.build.date=Sun Jun 13 11:26:22 CST 2021
ro.vendor.build.date=Sun Jun 13 11:26:22 CST 2021
MD5 hashes:
Code:
abl.elf -> 307b569127da67ebdeb370565583de1a
adsp.mbn -> ffa7d3bc5ef6f891ab5125d48234b89b
Android.mk -> 9974f4247eb0ae79e4b255bc9f00fcbb
AndroidBoard.mk -> a6b120e6be701425f0173dd692da4251
AndroidProducts.mk -> 02ceda404d626107e7120c75b69f78e0
apdp.mbn -> f07702b513692fcc0527f7b110352349
BoardConfig.mk -> 9faf9a77e686cdf7c376b597187f9ac3
boot-debug.img -> 6a4e7d179387eb2e2bf34289c7b0c5a8
boot.img -> 1657f03a47b851e8a4bb8c17c8ccb86a
BTFM.bin -> 60bafd6a584fb0a7400cf2165ca88e43
cache.img -> b8153431cc4d6ea191b645e0a128bdc0
cdsp.mbn -> 011980a2a26de149c948c1231d53cf22
cmnlib.mbn -> 77fa0376beb60fb0bd012a6494df9a6a
cmnlib64.mbn -> f355ecc5aa729b2d2b1c368b78251538
crclist.txt -> e02e29f4e54bd8296d21e58e631e9d2d
devcfg.mbn -> f1a7eeb49175d09288c17617f518646f
dspso.bin -> 05ac90f5b8ed3081953bfc6fa6892723
dtb.img -> 39e42397b1a22d76cd719541c5352098
dtbo.img -> ee0390d2139b9ee762e78284856c4621
featenabler.mbn -> 72cee21b29be1d40fc1c67ba7f77b2b3
ffu_list.txt -> de14db3496000a21b5dfab4aebbdd65b
fpctzappfingerprint.mbn -> 74fa2cff302eba319ceab45fe6800584
framework_manifest.xml -> 27356acf4cc0f74dcc57a6d15feacf4d
fsgall.img -> f41be81fc7bc6399253ff709f7505b6f
fstab_AB_dynamic_partition.qti -> 7c3d314e66a594d3eb4e33595ffc38be
fstab_AB_variant.qti -> 119a06c449fd04b505197683f0efcd09
fstab_non_AB_dynamic_partition.qti -> 6f4d0e4bae0bae60b6d71fac323dc472
fstab_non_AB_variant.qti -> 6dec0d19154c8281a42442fcb86bbb83
goodixfp.mbn -> c2ef5ece85b46b8da46e22e7a5c76524
gpio-keys.kl -> fab01e275a873c98eb02d028914d106e
gpt_backup0.bin -> a36dcedb727673b91a2e7b8b22a1aa75
gpt_backup1.bin -> f0de661557245fd66019c67609c947da
gpt_backup2.bin -> c06bcb8b4e61886020a05a285acd741c
gpt_backup3.bin -> befa5fc7e32238c271d301809de66e02
gpt_backup4.bin -> 2b488b4ca19529696da66503c31fec99
gpt_backup5.bin -> 5297cf70c8bea38c889f4a7f7cb34aed
gpt_both0.bin -> 5cad138c5ee02829f9c93b05b204f95e
gpt_both1.bin -> bd2495d9ab349f50b79b1ff725dbe685
gpt_both2.bin -> 70eb31cdc704c1069733716a954c4f56
gpt_both3.bin -> 4089e123aa5efeef27e243ff672971f4
gpt_both4.bin -> 6e7eeea89b88461b4ab002c01be3ea5a
gpt_both5.bin -> 9f4fea4d36ccd14d4e2520d5dc63374d
gpt_empty0.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty1.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty2.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty3.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty4.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty5.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_main0.bin -> 02a364a649d8ceacfb1d4ef999c69a32
gpt_main1.bin -> 89cd12e778b682e1bbef3c39d4c04b47
gpt_main2.bin -> 0126324ac62639234b97c15b24a3fb6a
gpt_main3.bin -> 79d7af8800e97a51b6a3777275f4c8dc
gpt_main4.bin -> f81792b8fce6267a71cb2f1ef1ce3666
gpt_main5.bin -> 41043df5c47c07d3204f8ccecb4e7978
gptest.mbn -> c566897e78ab5c509715fa45dcf4a5f0
haventkn.mbn -> f2aebab2e886c94644eeda2f27d5addf
hyp.mbn -> 42208206997cfade7c3e48b356eab71a
imagefv.elf -> 6aa23453aa999dc35eba9923f1441609
init.target.rc -> aeb427a1c3333b6d9dc77f3f776eb506
km4.mbn -> 9a438dc22df7c80178cacfd62ef60184
lime.mk -> 1dfbe34c27e319b90441c9a89af1d39d
logfs_ufs_8mb.bin -> c040a889d66a4f120f502f89b551f42b
manifest.xml -> caf0e96e0c0bf30f991f165030fa3cc4
manifest_ab.xml -> b623b992da295acd8310f43e8f4ebe85
metadata.img -> ac7abb42ba4dd0f75335153549f41f84
MICRON_LYRA2_64GB_0605.bin -> e35b487e8c63d492aac16db97cbd77ef
multi_image.mbn -> 434a8847eb2848e3ed6f25713aadad53
NON-HLOS.bin -> 875cb19f6013dfe44f1d15fc7b5159e2
NOTICE -> 98017cf03a7e1b612bcf232f9b44aa2e
odm_manifest_lemon.xml -> 9b290f8f379c3e8a6f8f79822acac677
odm_manifest_lime.xml -> 2384e886ad7573acb92604d4103c1c87
odm_manifest_pomelo.xml -> 2384e886ad7573acb92604d4103c1c87
partition.xml -> e3b3e37247680b45408fd3d1982eca09
patch0.xml -> 15694a6e6716908db07b048d915ab37f
patch1.xml -> 0780990ee59934bdcaffc918cac99aed
patch2.xml -> 81036277fd056a16c0e418a756a5a835
patch3.xml -> f1e955eeee449ed57767ac0b87552cf1
patch4.xml -> 82a65c3c86ad47ffa1aaa21417598c32
patch5.xml -> 90ed396b2667209688b315f4dcc37104
persist.img -> 9c8f964fb03faa6a79d6e4ab2dd1957d
prebuilt_dtbo.img -> 5a310187621d72f82d672daf91231463
product.img -> 3edbde6439c089e66368cd370c6cd903
prog_firehose_ddr.elf -> 13dd339bd2db3a8c9bdfa6357d41ca12
ProjectConfig.mk -> 8f9e31321f8452a1e690f2e426ad8a22
provision_hynix.xml -> c7fecbec91b6aa5449bbe7ff5c2ca51d
PT_3Dv5_TLC_Voyager_UFS2.2_A251_USER.bin -> ca3088a07474377f54429f7cb1d9d7a2
public.libraries-qti.txt -> d599da22e6c4b8467ce28e1e562250eb
qupv3fw.elf -> dde60357158c8f7275aa153d8e221bba
ramdisk-debug.img -> e931fe2a009dbaab4f60775f83f0e772
ramdisk-recovery.img -> 8e579f57d0695d925b08a63b57c809f1
ramdisk.img -> 19e3f68d17f4d8f5a8b47d24a4d3e72b
rawprogram0.xml -> 98c3a8110edccdf01c57bfa5f0dd97a3
rawprogram0_BLANK_GPT.xml -> b3200cadf9be377d4f950cc03f4490a6
rawprogram0_WIPE_PARTITIONS.xml -> a08020b62484e1bfa7dbc6a7a76ac8fb
rawprogram1.xml -> 1df8d77508440b40cce09e94d5904af9
rawprogram1_BLANK_GPT.xml -> 30c9b7228531bbc0a0bfc5421105c196
rawprogram1_WIPE_PARTITIONS.xml -> 2c9dd8708195e23f910c0728873662c6
rawprogram2.xml -> 5b75a6083172cce4147d4a8769d81a55
rawprogram2_BLANK_GPT.xml -> 3198bf3e352b48600e63b90979e71a08
rawprogram2_WIPE_PARTITIONS.xml -> db15a8c1ac994e50be924e32ed9f03f4
rawprogram3.xml -> e03411d04b290ffe1ea9b993d1f23074
rawprogram3_BLANK_GPT.xml -> 439d4e875584101690085e1c95833e24
rawprogram3_WIPE_PARTITIONS.xml -> 3322789cb2c9e42bebd04f364e7a7aed
rawprogram4.xml -> fbaa3ea21bca23aa413bb9167773c7c7
rawprogram4_BLANK_GPT.xml -> 4d34e3bb4a83abdbe5f1fbf972d31918
rawprogram4_WIPE_PARTITIONS.xml -> 1dae44f86205d39ac83a6f83ee8911ad
rawprogram5.xml -> ebc54f7ab9d20e97b7601fb71bab4d6f
rawprogram5_BLANK_GPT.xml -> 93e0a3b178a136cda2cbab8de547f645
rawprogram5_WIPE_PARTITIONS.xml -> 9abf9d0a5859d4394a159ea29b499d9a
recovery-two-step.img -> a5a6f212c93886ff8515c2479ef4bfb2
recovery.img -> 251497aba4fed6188919606dda5cd715
recovery_AB_dynamic_partition.fstab -> a1734c76b6cf3c7cceb6384f2b167bf9
recovery_AB_variant.fstab -> 131037786ef6b9a8c56a1e34cb03ecc5
recovery_non-AB_dynamic_partition.fstab -> e4e761473a7a0e190c3e0ed5d5438600
recovery_non-AB_variant.fstab -> 379263def26dcaf344aa027980f4b731
rpm.mbn -> 05c3096461be56f1d94200be9124c547
S101_64G_430bda1ae4_MICRON.bin -> 2644fac2ba2516c40aee7cc543544a29
S201_64G_dd6e035122_MICRON.bin -> ea229b469d8e39e2d411cdac0fc467fa
SANTOS_UFS_2_2_V5_TLC_256Gb_128GB_P17.bin -> 1238740ee9d31d3f5b560c61f94f7845
Santos_V5_TLC_128GB_P15_General.bin -> f02b19fc3bcb8f2a9f1c8bdb919a86ac
sec.dat -> 21775907582b06389a656ab56011c160
sec.elf -> db0ff694b116843bef34a1b8fc1fbd5b
smplap64.mbn -> 6ef1323ee8a74727359ca510719fea36
soter64.mbn -> 9ecc10629adb114076489cd12540d94c
sparsecrclist.txt -> a6b02a3d5d0819ae7a994decbb456db9
storsec.mbn -> cbcaa3cd55ef02eb318066eaa800cf90
super.img -> ec54cd76fc3d8300a37222bc9ad9b31a
super_empty.img -> 1f8c5307a34885c9577d875d5c366d93
system.img -> 2e1cd737578b8c94dd0ead1c9ddeb97f
system.prop -> dcf0fa9fc04edeaed8ef6a9d0d224276
tz.mbn -> 21c38fd53a3c46e1ebdb2efc59bacba7
uefi_sec.mbn -> 4a28fa0f72ecc18a173d8035098e36c5
userdata.img -> e952e2c175d99f35d20acdd31d90e8f2
vbmeta.img -> 1cbd4a76cf8bc05d1dc3f84fb2dacf02
vbmeta_system.img -> 74a918bbd11203de6d001c2ebade8f08
vendor.img -> 3dd4303c5c516e33f374a6419e0656b6
vold.fstab -> a1e06a3daf0404cb89944e95dfdd8fec
widevine.mbn -> f07842bfedbf439111d9be6a6a35eb81
xbl.elf -> 14cda50cabdaaae74a0a204a39b68b32
xbl_config.elf -> 7975e2560048f7c4a543045d399091ee
Xiaomi_Columbus_S76_PRV_0005_Official_FW_bitflip_count.bin -> fc9018659527ad3add419eff38a75753
Xiaomi_Columbus_S76_T005_Test _FW_bitflip_count.bin -> 7f6647928bb0eb78b2c583603fffd460
zeros_1sector.bin -> 620f0b67a91f7f74151bc5be745b7110
zeros_5sectors.bin -> daa100df6e6711906b61c9ab5aa16032

Woah, nice!

Done.
Uploaded.
Enjoy !

Hey,
I noticed that the EDL Loader included in the Engineering Firmware does not require an authentication, meaning that the Redmi 9T can now be unbricked without having to contact a Service Center, etc.
Thank you

TheRedHugo said:
Hey,
I noticed that the EDL Loader included in the Engineering Firmware does not require an authentication, meaning that the Redmi 9T can now be unbricked without having to contact a Service Center, etc.
Thank you
Click to expand...
Click to collapse
Very good work, my friend.
You are welcome

Hello, phone come with problem:
Not power on, when connect to PC - hs-usb qdloader 9008
Try flash it. Flash Ok, but problem same
Not power on, when connect to PC - hs-usb qdloader 9008
What may be? Memory die?

Abzal said:
Hello, phone come with problem:
Not power on, when connect to PC - hs-usb qdloader 9008
Try flash it. Flash Ok, but problem same
Not power on, when connect to PC - hs-usb qdloader 9008
What may be? Memory die?
Click to expand...
Click to collapse
If you can flash to the device, it is not dead.

So what problem may be?

VD171 said:
Works withass
- Xiaomi Redmi 9 Power
- Xiaomi Redmi 9T
Build Date:
2021/06/13
Android Version:
QKQ1.200730.002
Display ID:
QL2880-lime-V065-Q-0613
Build Fingerprint:
Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
Security Patch:
2020-10-01
Radio/Modem/Baseband Version:
A.1.0-00505.1-KAMORTA_GEN_PACK-3
Download:
https://www.mediafire.com/file/y25b...ing_QL2880-lime-V065-Q-0613_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
Prop.default:
Code:
ro.build.version.incremental=1648
ro.odm.build.version.incremental=1648
ro.vendor.build.version.incremental=1648
ro.product.board=lime
ro.product.odm.device=lime
ro.product.odm.model=lime
ro.product.odm.name=lime
ro.product.system.device=lime
ro.product.system.model=lime
ro.product.system.name=lime
ro.product.vendor.device=lime
ro.product.vendor.model=lime
ro.product.vendor.name=lime
ro.build.flavor=lime-userdebug
ro.build.display.id=QL2880-lime-V065-Q-0613
ro.board.platform=bengal
ro.build.id=QKQ1.200730.002
ro.odm.build.id=QKQ1.200730.002
ro.system.build.id=QKQ1.200730.002
ro.vendor.build.id=QKQ1.200730.002
ro.bootimage.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.system.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/lime/lime:10/QKQ1.200730.002/1648: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.build.version.security_patch=2020-10-01
ro.vendor.build.security_patch=2020-10-01
ro.bootimage.build.date=Sun Jun 13 11:26:22 CST 2021
ro.build.date=Sun Jun 13 11:26:22 CST 2021
ro.odm.build.date=Sun Jun 13 11:26:22 CST 2021
ro.system.build.date=Sun Jun 13 11:26:22 CST 2021
ro.vendor.build.date=Sun Jun 13 11:26:22 CST 2021
MD5 hashes:
Code:
abl.elf -> 307b569127da67ebdeb370565583de1a
adsp.mbn -> ffa7d3bc5ef6f891ab5125d48234b89b
Android.mk -> 9974f4247eb0ae79e4b255bc9f00fcbb
AndroidBoard.mk -> a6b120e6be701425f0173dd692da4251
AndroidProducts.mk -> 02ceda404d626107e7120c75b69f78e0
apdp.mbn -> f07702b513692fcc0527f7b110352349
BoardConfig.mk -> 9faf9a77e686cdf7c376b597187f9ac3
boot-debug.img -> 6a4e7d179387eb2e2bf34289c7b0c5a8
boot.img -> 1657f03a47b851e8a4bb8c17c8ccb86a
BTFM.bin -> 60bafd6a584fb0a7400cf2165ca88e43
cache.img -> b8153431cc4d6ea191b645e0a128bdc0
cdsp.mbn -> 011980a2a26de149c948c1231d53cf22
cmnlib.mbn -> 77fa0376beb60fb0bd012a6494df9a6a
cmnlib64.mbn -> f355ecc5aa729b2d2b1c368b78251538
crclist.txt -> e02e29f4e54bd8296d21e58e631e9d2d
devcfg.mbn -> f1a7eeb49175d09288c17617f518646f
dspso.bin -> 05ac90f5b8ed3081953bfc6fa6892723
dtb.img -> 39e42397b1a22d76cd719541c5352098
dtbo.img -> ee0390d2139b9ee762e78284856c4621
featenabler.mbn -> 72cee21b29be1d40fc1c67ba7f77b2b3
ffu_list.txt -> de14db3496000a21b5dfab4aebbdd65b
fpctzappfingerprint.mbn -> 74fa2cff302eba319ceab45fe6800584
framework_manifest.xml -> 27356acf4cc0f74dcc57a6d15feacf4d
fsgall.img -> f41be81fc7bc6399253ff709f7505b6f
fstab_AB_dynamic_partition.qti -> 7c3d314e66a594d3eb4e33595ffc38be
fstab_AB_variant.qti -> 119a06c449fd04b505197683f0efcd09
fstab_non_AB_dynamic_partition.qti -> 6f4d0e4bae0bae60b6d71fac323dc472
fstab_non_AB_variant.qti -> 6dec0d19154c8281a42442fcb86bbb83
goodixfp.mbn -> c2ef5ece85b46b8da46e22e7a5c76524
gpio-keys.kl -> fab01e275a873c98eb02d028914d106e
gpt_backup0.bin -> a36dcedb727673b91a2e7b8b22a1aa75
gpt_backup1.bin -> f0de661557245fd66019c67609c947da
gpt_backup2.bin -> c06bcb8b4e61886020a05a285acd741c
gpt_backup3.bin -> befa5fc7e32238c271d301809de66e02
gpt_backup4.bin -> 2b488b4ca19529696da66503c31fec99
gpt_backup5.bin -> 5297cf70c8bea38c889f4a7f7cb34aed
gpt_both0.bin -> 5cad138c5ee02829f9c93b05b204f95e
gpt_both1.bin -> bd2495d9ab349f50b79b1ff725dbe685
gpt_both2.bin -> 70eb31cdc704c1069733716a954c4f56
gpt_both3.bin -> 4089e123aa5efeef27e243ff672971f4
gpt_both4.bin -> 6e7eeea89b88461b4ab002c01be3ea5a
gpt_both5.bin -> 9f4fea4d36ccd14d4e2520d5dc63374d
gpt_empty0.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty1.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty2.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty3.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty4.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_empty5.bin -> 7b062e4b9562bb74ea8fe445676b3a92
gpt_main0.bin -> 02a364a649d8ceacfb1d4ef999c69a32
gpt_main1.bin -> 89cd12e778b682e1bbef3c39d4c04b47
gpt_main2.bin -> 0126324ac62639234b97c15b24a3fb6a
gpt_main3.bin -> 79d7af8800e97a51b6a3777275f4c8dc
gpt_main4.bin -> f81792b8fce6267a71cb2f1ef1ce3666
gpt_main5.bin -> 41043df5c47c07d3204f8ccecb4e7978
gptest.mbn -> c566897e78ab5c509715fa45dcf4a5f0
haventkn.mbn -> f2aebab2e886c94644eeda2f27d5addf
hyp.mbn -> 42208206997cfade7c3e48b356eab71a
imagefv.elf -> 6aa23453aa999dc35eba9923f1441609
init.target.rc -> aeb427a1c3333b6d9dc77f3f776eb506
km4.mbn -> 9a438dc22df7c80178cacfd62ef60184
lime.mk -> 1dfbe34c27e319b90441c9a89af1d39d
logfs_ufs_8mb.bin -> c040a889d66a4f120f502f89b551f42b
manifest.xml -> caf0e96e0c0bf30f991f165030fa3cc4
manifest_ab.xml -> b623b992da295acd8310f43e8f4ebe85
metadata.img -> ac7abb42ba4dd0f75335153549f41f84
MICRON_LYRA2_64GB_0605.bin -> e35b487e8c63d492aac16db97cbd77ef
multi_image.mbn -> 434a8847eb2848e3ed6f25713aadad53
NON-HLOS.bin -> 875cb19f6013dfe44f1d15fc7b5159e2
NOTICE -> 98017cf03a7e1b612bcf232f9b44aa2e
odm_manifest_lemon.xml -> 9b290f8f379c3e8a6f8f79822acac677
odm_manifest_lime.xml -> 2384e886ad7573acb92604d4103c1c87
odm_manifest_pomelo.xml -> 2384e886ad7573acb92604d4103c1c87
partition.xml -> e3b3e37247680b45408fd3d1982eca09
patch0.xml -> 15694a6e6716908db07b048d915ab37f
patch1.xml -> 0780990ee59934bdcaffc918cac99aed
patch2.xml -> 81036277fd056a16c0e418a756a5a835
patch3.xml -> f1e955eeee449ed57767ac0b87552cf1
patch4.xml -> 82a65c3c86ad47ffa1aaa21417598c32
patch5.xml -> 90ed396b2667209688b315f4dcc37104
persist.img -> 9c8f964fb03faa6a79d6e4ab2dd1957d
prebuilt_dtbo.img -> 5a310187621d72f82d672daf91231463
product.img -> 3edbde6439c089e66368cd370c6cd903
prog_firehose_ddr.elf -> 13dd339bd2db3a8c9bdfa6357d41ca12
ProjectConfig.mk -> 8f9e31321f8452a1e690f2e426ad8a22
provision_hynix.xml -> c7fecbec91b6aa5449bbe7ff5c2ca51d
PT_3Dv5_TLC_Voyager_UFS2.2_A251_USER.bin -> ca3088a07474377f54429f7cb1d9d7a2
public.libraries-qti.txt -> d599da22e6c4b8467ce28e1e562250eb
qupv3fw.elf -> dde60357158c8f7275aa153d8e221bba
ramdisk-debug.img -> e931fe2a009dbaab4f60775f83f0e772
ramdisk-recovery.img -> 8e579f57d0695d925b08a63b57c809f1
ramdisk.img -> 19e3f68d17f4d8f5a8b47d24a4d3e72b
rawprogram0.xml -> 98c3a8110edccdf01c57bfa5f0dd97a3
rawprogram0_BLANK_GPT.xml -> b3200cadf9be377d4f950cc03f4490a6
rawprogram0_WIPE_PARTITIONS.xml -> a08020b62484e1bfa7dbc6a7a76ac8fb
rawprogram1.xml -> 1df8d77508440b40cce09e94d5904af9
rawprogram1_BLANK_GPT.xml -> 30c9b7228531bbc0a0bfc5421105c196
rawprogram1_WIPE_PARTITIONS.xml -> 2c9dd8708195e23f910c0728873662c6
rawprogram2.xml -> 5b75a6083172cce4147d4a8769d81a55
rawprogram2_BLANK_GPT.xml -> 3198bf3e352b48600e63b90979e71a08
rawprogram2_WIPE_PARTITIONS.xml -> db15a8c1ac994e50be924e32ed9f03f4
rawprogram3.xml -> e03411d04b290ffe1ea9b993d1f23074
rawprogram3_BLANK_GPT.xml -> 439d4e875584101690085e1c95833e24
rawprogram3_WIPE_PARTITIONS.xml -> 3322789cb2c9e42bebd04f364e7a7aed
rawprogram4.xml -> fbaa3ea21bca23aa413bb9167773c7c7
rawprogram4_BLANK_GPT.xml -> 4d34e3bb4a83abdbe5f1fbf972d31918
rawprogram4_WIPE_PARTITIONS.xml -> 1dae44f86205d39ac83a6f83ee8911ad
rawprogram5.xml -> ebc54f7ab9d20e97b7601fb71bab4d6f
rawprogram5_BLANK_GPT.xml -> 93e0a3b178a136cda2cbab8de547f645
rawprogram5_WIPE_PARTITIONS.xml -> 9abf9d0a5859d4394a159ea29b499d9a
recovery-two-step.img -> a5a6f212c93886ff8515c2479ef4bfb2
recovery.img -> 251497aba4fed6188919606dda5cd715
recovery_AB_dynamic_partition.fstab -> a1734c76b6cf3c7cceb6384f2b167bf9
recovery_AB_variant.fstab -> 131037786ef6b9a8c56a1e34cb03ecc5
recovery_non-AB_dynamic_partition.fstab -> e4e761473a7a0e190c3e0ed5d5438600
recovery_non-AB_variant.fstab -> 379263def26dcaf344aa027980f4b731
rpm.mbn -> 05c3096461be56f1d94200be9124c547
S101_64G_430bda1ae4_MICRON.bin -> 2644fac2ba2516c40aee7cc543544a29
S201_64G_dd6e035122_MICRON.bin -> ea229b469d8e39e2d411cdac0fc467fa
SANTOS_UFS_2_2_V5_TLC_256Gb_128GB_P17.bin -> 1238740ee9d31d3f5b560c61f94f7845
Santos_V5_TLC_128GB_P15_General.bin -> f02b19fc3bcb8f2a9f1c8bdb919a86ac
sec.dat -> 21775907582b06389a656ab56011c160
sec.elf -> db0ff694b116843bef34a1b8fc1fbd5b
smplap64.mbn -> 6ef1323ee8a74727359ca510719fea36
soter64.mbn -> 9ecc10629adb114076489cd12540d94c
sparsecrclist.txt -> a6b02a3d5d0819ae7a994decbb456db9
storsec.mbn -> cbcaa3cd55ef02eb318066eaa800cf90
super.img -> ec54cd76fc3d8300a37222bc9ad9b31a
super_empty.img -> 1f8c5307a34885c9577d875d5c366d93
system.img -> 2e1cd737578b8c94dd0ead1c9ddeb97f
system.prop -> dcf0fa9fc04edeaed8ef6a9d0d224276
tz.mbn -> 21c38fd53a3c46e1ebdb2efc59bacba7
uefi_sec.mbn -> 4a28fa0f72ecc18a173d8035098e36c5
userdata.img -> e952e2c175d99f35d20acdd31d90e8f2
vbmeta.img -> 1cbd4a76cf8bc05d1dc3f84fb2dacf02
vbmeta_system.img -> 74a918bbd11203de6d001c2ebade8f08
vendor.img -> 3dd4303c5c516e33f374a6419e0656b6
vold.fstab -> a1e06a3daf0404cb89944e95dfdd8fec
widevine.mbn -> f07842bfedbf439111d9be6a6a35eb81
xbl.elf -> 14cda50cabdaaae74a0a204a39b68b32
xbl_config.elf -> 7975e2560048f7c4a543045d399091ee
Xiaomi_Columbus_S76_PRV_0005_Official_FW_bitflip_count.bin -> fc9018659527ad3add419eff38a75753
Xiaomi_Columbus_S76_T005_Test _FW_bitflip_count.bin -> 7f6647928bb0eb78b2c583603fffd460
zeros_1sector.bin -> 620f0b67a91f7f74151bc5be745b7110
zeros_5sectors.bin -> daa100df6e6711906b61c9ab5aa16032
Click to expand...
Click to collapse

Abzal said:
So what problem may be?
Click to expand...
Click to collapse
Allright, sorry. My mistake.

VD171 said:
Qdloader is for QUALCOMM devices.
LIME is mediatek.
Apparentely you doing something wrong.
Click to expand...
Click to collapse
Lime has Qualcomm Snapdragon 662 processor.

Show me Redmi 9T on mediatek, this phone go on Snapdragon 662

Allright, sorry. My mistake.
I'm not so familiarized with qualcomm devices.

How to flash normal firmware if bootloader locked. cant find unlock bootloader option

almat_moto said:
How to flash normal firmware if bootloader locked. cant find unlock bootloader option
Click to expand...
Click to collapse
Apply for unlocking Mi devices
en.miui.com

Thanks for providing this. Managed to unbrick my Redmi 9T that has been sitting in a drawer for months.

SZander93 said:
Thanks for providing this. Managed to unbrick my Redmi 9T that has been sitting in a drawer for months.
Click to expand...
Click to collapse
Good work, my friend.
You are welcome

Abzal said:
Hello, phone come with problem:
Not power on, when connect to PC - hs-usb qdloader 9008
Try flash it. Flash Ok, but problem same
Not power on, when connect to PC - hs-usb qdloader 9008
What may be? Memory die?
Click to expand...
Click to collapse
Hello, it is working way, maybe it can help you:

password not work

wil232 said:
password not work
Click to expand...
Click to collapse
Password is inside the attached file PASSWORD_by_VD171.txt.
Enjoy