Related
Root Elephone U Pro
Foreword:
It was a long way to get root on the U Pro and dangerous , i could brick my phone , but finally its done!
It wasn't my own work at all. We all shared ideas and thoughts . We that are
Mr. Fünke (not an xda member) @Maherabed1986 @lKinder_Bueno @dypak and me @skeleton1911 .
so thanks goes also to them.
In the last days we spent hours and hours to get not only root . ( but this is another chapter, soon more )
Took the last OTA 20180227 Build and extracted the payload.bin (in it are all images etc.) Surprise
the System has a second partition table of all images . called _a and _b ( example: boot_a.img , boot_b.img)
thats a good thing, because if one gets damaged the Bootloader will boot the other Partition.
i could write many more but lets come to the Topic.
Code:
[SIZE="3"][COLOR="Red"]#/Disclaimer[/COLOR]
* I am not responsible for anything/bricked devices, dead SD cards,
* thermonuclear war, or exploding cars.
[/SIZE]
What do we need for Root our U Pro
1. QPST flashtools (qualcomm)
2. Qualcomm Drivers for the Device
3. a firehose file for SDM660
4. rawprogram_unsparse and patch0.xml
6. patched_boot.img
7.ADB
8.unlocked bootloader
Uploaded all here: https://1drv.ms/u/s!Am93l3qEx-D_hJZQQpXbjL45aKcUiQ only for 20180227
TOOL FILES https://1drv.ms/u/s!Am93l3qEx-D_hOcLmv0inQJ-vrVdLg
IF YOU USE QFIL FLASHTOOLS YOU DONT NEED TO UNLOCK THE BOOTLOADER:
THIS IS ONLY NECCESARY IF YOU WANT TO USE FASTBOOT COMMANDS: SINCE 20180423 BASE
(files are at the bottom of this post)
Also enable USB Debugging in settings/system/developer settings
(tap 7 times on the build number in settings/system/phone info if you dont have developer settings)
we need an unlocked bootloader
Enable OEM unlock in developer settings..
If you unlocked the bootloader , that will wipe your userdata and
you have the google protection password screen.
Notice: if your password dont work , no panic! just enter 30 times a wrong password with minimal 5 letters and the phone will make a factory reset.
for unlock bootloader do:
Code:
adb shell
Code:
reboot bootloader
and
Code:
fastboot flashing unlock
that will wipe userdata!
after that you can enter recovery via bootloader or it reboots itself to it . when you see the red android icon . hold power and vol- 5 seconds and then slide to vol+ and back to vol- or try : press power and then click on vol+
that will enter recovery, then reboot , you will have to enter the google password 30times (look above)
After the phone is back on Homescreen , enable usb debugging again and use adb
Code:
adb shell
Code:
reboot edl
1. install ADB . (newest ADB files are in the zip) . copy the "adb" folder to C:/
2. install the QPST/QFIL Flashtool
3. install Qualcomm Drivers
-----------------------------------------------------------------
Connect your phone to pc
when all is installed open a command (cmd) and go to your adb folder
Code:
C:\>cd adb
we need to reboot the phone to the EDL mode (emergency download mode) to use the Flashtool :
Code:
adb shell
reboot edl
phone will reboot to edl mode ( black screen, no led)
Now check your device manager . the COM & LTP port should show "Qualcomm HS-USB QDLoader 9008"
if not then update the driver and choose it from your internal list. or google for it
if the driver is fine, open the QPST/QFIL FLashtool in
Code:
C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe
prepare the Flashtool:
in Select Build Type:
choose: Flat Build
in Select Programmer:
browse and choose the "prog_emmc_ufs_firehose_Sdm660_ddr.elf" file
( you cant see it change to "all files" )
Load XML:
now choose the rawprogram_unsparse.xml and right after the patch0.xml
you can press the "download button"
wait a bit , at the end of the flashing procedure it will make an error, thats normal because i left the patch0.xml empty.
after all disconnect the cable and hold Power button a few seconds. phone will reboot and you have root.
install magisk manager.apk from magisk thread .
enjoy
This is the boot.img of the boot_b partition and will root the system_b.
the system_a is untouched , also the boot_a.img . so if an OTA will come you can install it with no problem.
BTW after you installed magisk manager.apk , choose install again and direct download to get magisk files into system.
IF YOU USE QFIL FLASHTOOLS YOU DONT NEED TO UNLOCK THE BOOTLOADER:
THIS IS ONLY NECCESARY IF YOU WANT TO USE FASTBOOT COMMANDS: SINCE 20180423 BASE
20180227 Root Boot.img
Flashable via QFIL Flashtools only!
you dont need to be unlock. just install qfil and its drivers...
Go here: https://1drv.ms/u/s!Am93l3qEx-D_hJZPwPoJzH4zTrkLqQ
20180423 Root Boot.img
use QFil flashtools when you dont want to unlock your bootloader- (unlocking bootloader will wipe your data)
if you want fastboot commands unlock the bootloader and flash the boot.img via fastboot . ( you have to be in bootloader mode )
for this place only the boot.img to your adb folder and do this commands
GO here: https://1drv.ms/u/s!Am93l3qEx-D_hJZODc_2yG3Kl-VTow
20180511 Root Boot.img
Rooted Boot.img .- https://1drv.ms/u/s!Am93l3qEx-D_hJZv4OOlKoGa6BFxdA
you can use this with the files above ( raw.xml etc for QFIL , or flash it via fastboot if you are unlocked
go to bootloader mode with
Code:
adb shell
reboot bootloader
then
Code:
fastboot flash boot_a boot.img
and
Code:
fastboot flash boot_b boot.img
thats all.
easy to do
after install magisk manager to activate root
maybe some of you are interested in the partitions and sectors of the U pro to take out a dump or make a rawprogram_unparse.xml for a fullrom
i took them out with adb for you :
Code:
Number Start End Size File system Name Flags
1 131072s 138239s 7168s xbl_a
2 138240s 145407s 7168s xbl_b
3 145408s 153599s 8192s tz_a
4 153600s 161791s 8192s tz_b
5 161792s 162815s 1024s rpm_a
6 162816s 163839s 1024s rpm_b
7 163840s 164863s 1024s hyp_a
8 164864s 165887s 1024s hyp_b
9 165888s 166911s 1024s pmic_a
10 166912s 167935s 1024s pmic_b
11 167936s 172031s 4096s fsg
12 262144s 393215s 131072s boot_a
13 393216s 524287s 131072s boot_b
14 524288s 6815743s 6291456s ext4 system_a
15 6815744s 13107199s 6291456s ext4 system_b
16 13107200s 14745599s 1638400s ext4 vendor_a
17 14745600s 16383999s 1638400s ext4 vendor_b
18 16384000s 16386047s 2048s keymaster_a
19 16386048s 16388095s 2048s keymaster_b
20 16388096s 16390143s 2048s cmnlib_a
21 16390144s 16392191s 2048s cmnlib64_a
22 16392192s 16394239s 2048s cmnlib_b
23 16394240s 16396287s 2048s cmnlib64_b
24 16396288s 16404479s 8192s mdtpsecapp_a
25 16404480s 16412671s 8192s mdtpsecapp_b
26 16412672s 16478207s 65536s mdtp_a
27 16478208s 16543743s 65536s mdtp_b
28 16543744s 16769023s 225280s fat16 modem_a
29 16769024s 16994303s 225280s fat16 modem_b
30 16994304s 17027071s 32768s ext4 dsp_a
31 17027072s 17059839s 32768s ext4 dsp_b
32 17059840s 17061887s 2048s abl_a
33 17061888s 17063935s 2048s abl_b
34 17063936s 17065983s 2048s dip
35 17065984s 17065991s 8s devinfo
36 17065992s 17066503s 512s apdp
37 17066504s 17067015s 512s msadp
38 17067016s 17067017s 2s dpo
39 17067024s 17133871s 66848s splash
40 17133872s 17133879s 8s limits
41 17133880s 17135927s 2048s toolsfv
42 17170432s 17186815s 16384s logfs
43 17301504s 17303551s 2048s ddr
44 17303552s 17303583s 32s sec
45 17303584s 17305631s 2048s bluetooth_a
46 17305632s 17307679s 2048s bluetooth_b
47 17432576s 17436671s 4096s prodinfo
48 17436672s 17457151s 20480s ext4 factory
49 17457152s 17477631s 20480s ext4 factorybak
50 17477632s 17477633s 2s fsc
51 17477640s 17477655s 16s ssd
52 17477656s 17481751s 4096s modemst1
53 17481752s 17485847s 4096s modemst2
54 17485848s 17551383s 65536s ext4 persist
55 17551384s 17553431s 2048s misc
56 17553432s 17554455s 1024s keystore
57 17554456s 17556503s 2048s devcfg_a
58 17556504s 17558551s 2048s devcfg_b
59 17558552s 17559575s 1024s frp
60 17559576s 17690647s 131072s logdump
61 17690648s 17694743s 4096s sti
6
2 17825792s 17826047s 256s storsec
63 17956864s 18219007s 262144s rawdump
64 18219008s 18219135s 128s vbmeta_a
65 18219136s 18219263s 128s vbmeta_b
66 18350080s 244277214s 225927135s userdata
Code:
[SIZE="3"]1|U_Pro:/ # ls -l /dev/block/platform/soc/c0c4000.sdhci/by-name
total 0
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 abl_a -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 abl_b -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 apdp -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 bluetooth_a -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 bluetooth_b -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 boot_a -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 boot_b -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib64_a -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib64_b -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib_a -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 cmnlib_b -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 ddr -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devcfg_a -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devcfg_b -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 devinfo -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dip -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dpo -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dsp_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 dsp_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 factory -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 factorybak -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 frp -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 fsc -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 fsg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 hyp_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 hyp_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keymaster_a -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keymaster_b -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 keystore -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 limits -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 logdump -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 logfs -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtp_a -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtp_b -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtpsecapp_a -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 mdtpsecapp_b -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 misc -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modem_a -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modem_b -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modemst1 -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 modemst2 -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 msadp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 pmic_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 pmic_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 prodinfo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 rawdump -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 rpm_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 rpm_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 sec -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 splash -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 ssd -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 sti -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 21 19
70-01-08 10:22 storsec -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 system_a -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 system_b -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 toolsfv -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 tz_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 tz_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 userdata -> /dev/block/mmcblk0p66
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vbmeta_a -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vbmeta_b -> /dev/block/mmcblk0p65
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vendor_a -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-08 10:22 vendor_b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 xbl_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-08 10:22 xbl_b -> /dev/block/mmcblk0p2[/SIZE]
Great job buddy very clear explaining
Wish you the best as always
skeleton1911 said:
Root Elephone U Pro
Foreword:
It was a long way to get root on the U Pro and dangerous , i could brick my phone , but finally its done!
It wasn't my own work at all. We all shared ideas and thoughts . We that are
Mr. Fünke (not an xda member) @Maherabed1986 @lKinder_Bueno @dypak and me @skeleton1911 .
so thanks goes also to them.
In the last days we spent hours and hours to get not only root . ( but this is another chapter, soon more )
Took the last OTA 20180227 Build and extracted the payload.bin (in it are all images etc.) Surprise
the System has a second partition table of all images . called _a and _b ( example: boot_a.img , boot_b.img)
thats a good thing, because if one gets damaged the Bootloader will boot the other Partition.
i could write many more but lets come to the Topic.
Code:
[SIZE="3"][COLOR="Red"]#/Disclaimer[/COLOR]
* I am not responsible for anything/bricked devices, dead SD cards,
* thermonuclear war, or exploding cars.
[/SIZE]
What do we need for Root our U Pro
1. QPST flashtools (qualcomm)
2. Qualcomm Drivers for the Device
3. a firehose file for SDM660
4. rawprogram_unsparse and patch0.xml
5. python-2.7.13.amd64
6. patched_boot.img
7.ADB
Uploaded all here: https://androidfilehost.com/?fid=673956719939832819
Also enable USB Debugging in settings/system/developer settings
(tap 7 times on the build number in settings/system/phone info if you dont have developer settings)
we dont need an unlocked bootloader.
If you unlocked the bootloader already and dont locked it again the flashtool will do it , that could wipe all userdata and
you have the google protection password screen.
Notice: if your password dont work , no panic! just enter 30 times a wrong password with minimal 5 letters and the phone will make a factory reset.
1. install ADB . (newest ADB files are in the zip) . copy the "adb" folder to C:/
2. install the QPST/QFIL Flashtool
3. install python 2.7.13
4. install Qualcomm Drivers
-----------------------------------------------------------------
Connect your phone to pc
when all is installed open a command (cmd) and go to your adb folder
Code:
C:\>cd adb
we need to reboot the phone to the EDL mode (emergency download mode) to use the Flashtool :
Code:
adb shell
reboot edl
phone will reboot to edl mode ( black screen, no led)
Now check your device manager . the COM & LTP port should show "Qualcomm HS-USB QDLoader 9008"
if not then update the driver and choose it from your internal list. or google for it
if the driver is fine, open the QPST/QFIL FLashtool in
Code:
C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe
prepare the Flashtool:
in Select Build Type:
choose: Flat Build
in Select Programmer:
browse and choose the "prog_emmc_ufs_firehose_Sdm660_ddr.elf" file
( you cant see it change to "all files" )
Load XML:
now choose the rawprogram_unsparse.xml and right after the patch0.xml
you can press the "download button"
wait a bit , at the end of the flashing procedure it will make an error, thats normal because i left the patch0.xml empty.
after all disconnect the cable and hold Power button a few seconds. phone will reboot and you have root.
install magisk manager.apk from magisk thread .
enjoy
This is the boot.img of the boot_b partition and will root the system_b.
the system_a is untouched , also the boot_a.img . so if an OTA will come you can install it with no problem.
BTW after you installed magisk manager.apk , choose install again and direct download to get magisk files into system.
Click to expand...
Click to collapse
Hello skeleton
Thanks for the perfect job!
May you can help me, I've done all steps and all went fine except after magisk manager installation I've to choose download zip only or patch boot.img. I tried both but only download is for twrp and patching boot.img I can only patch it on as card ?
What's the next step ?
Laptapper said:
Hello skeleton
Thanks for the perfect job!
May you can help me, I've done all steps and all went fine except after magisk manager installation I've to choose download zip only or patch boot.img. I tried both but only download is for twrp and patching boot.img I can only patch it on as card ?
What's the next step ?
Click to expand...
Click to collapse
In magisk manager tap on install , a new window pops up. Choose directly install.
That's all. After it downloaded and flashed the file you can reboot.
Wait.
Do you see direct install?
Gesendet von meinem U_Pro mit Tapatalk
No I didn't see direct install
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
skeleton1911 said:
In magisk manager tap on install , a new window pops up. Choose directly install.
That's all. After it downloaded and flashed the file you can reboot.
Wait.
Do you see direct install?
Gesendet von meinem U_Pro mit Tapatalk
Click to expand...
Click to collapse
No I didn't see direct install.
Laptapper said:
No I didn't see direct install
---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------
No I didn't see direct install.
Click to expand...
Click to collapse
What build number you are on?
You are on 20180227 build?
If so. Flash the boot.img again. And reboot.
Gesendet von meinem U_Pro mit Tapatalk
Success! I have gotten my UPro rooted! Thanks so much Skeleton! I'm new to it, I did something wrong at my first attempt, the flushing stopped, wrong path
on my pc or something, but it gave me a scare when I had to enter like, x10 a pin and at some point there was some warnings that the phone will be locked out after 9 more trials. I've managed to shut it off and go manually to recovery and do factory reset. The second time was the charm, the end of the flushing hangs on some error(as you predicted) and then this big relief, the phone comes to life!
https://drive.google.com/file/d/1RYP40jVhYsQXAu8ZBxz_zrByGxEIXtzw/view?usp=sharing
mzsquared said:
Success! I have gotten my UPro rooted! Thanks so much Skeleton! I'm new to it, I did something wrong at my first attempt, the flushing stopped, wrong path
on my pc or something, but it gave me a scare when I had to enter like, x10 a pin and at some point there was some warnings that the phone will be locked out after 9 more trials. I've managed to shut it off and go manually to recovery and do factory reset. The second time was the charm, the end of the flushing hangs on some error(as you predicted) and then this big relief, the phone comes to life!
https://drive.google.com/file/d/1RYP40jVhYsQXAu8ZBxz_zrByGxEIXtzw/view?usp=sharing
Click to expand...
Click to collapse
yep . that it hangs at the end of the flashtool is normal. because i left the patch0.xml empty...
also you didnt reboot to recovery. just enter the password . 10 times and phone display. please reboot info. after that another 10 times. phone displays a reboot info. after that it shows that it will reboot itself and delete userdata after another 10 times .... that is not part of my mistaken. its because of googles protection laws....
skeleton1911 said:
In magisk manager tap on install , a new window pops up. Choose directly install.
That's all. After it downloaded and flashed the file you can reboot.
Wait.
Do you see direct install?
Gesendet von meinem U_Pro mit Tapatalk
Click to expand...
Click to collapse
I used Total Commander from Google Play, had MagiskAPK on mu sd card, Total Commander asks for permission to install "other sources app" and it's done.
mzsquared said:
I used Total Commander from Google Play, had MagiskAPK on mu sd card, Total Commander asks for permission to install "other sources app" and it's done.
Click to expand...
Click to collapse
thanks. but thats not the problem of @Laptapper.
i think he is not on the latest build. because we have _a and _b system.
the latest build is on _b . also the root is only in _b
he could use cmd and adb in bootlader mode
fastboot set_active b
Setting current slot to 'b'...
but that will not work . the bootloader in the u pro is a bit strange. tested many things
Did u finally get root?
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
skeleton1911 said:
thanks. but thats not the problem of @Laptapper.
i think he is not on the latest build. because we have _a and _b system.
the latest build is on _b . also the root is only in _b
he could use cmd and adb in bootlader mode
fastboot set_active b
Setting current slot to 'b'...
but that will not work . the bootloader in the u pro is a bit strange. tested many things
Click to expand...
Click to collapse
Same boat. I could not get root.
abbas said:
Did u finally get root?
---------- Post added at 09:40 PM ---------- Previous post was at 09:37 PM ----------
Same boat. I could not get root.
Click to expand...
Click to collapse
Strange . For many users it works. For some not.
One user told me that he installed the ota with the fota app.
And then he flashed the ota.zip again. So he did installed it twice.
For him the root also don't work.
So maybe _a and _b partitions are the same now.
And the system is running in _a partition now.
The root only goes to _b partition.
That could be an explaining for it..
Also can you send me the Qfil log ?
skeleton1911 said:
Strange . For many users it works. For some not.
One user told me that he installed the ota with the fota app.
And then he flashed the ota.zip again. So he did installed it twice.
For him the root also don't work.
So maybe _a and _b partitions are the same now.
And the system is running in _a partition now.
The root only goes to _b partition.
That could be an explaining for it..
Also can you send me the Qfil log ?
Click to expand...
Click to collapse
Thanks for your help. This is my log
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM:
rawprogram_unsparse.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Programmer Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
Process Index:0
Image Search Path: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Start Download
Program Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
22:52:17: Requested ID 13, file: "C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
22:52:18: 629284 bytes transferred in 0.313000 seconds (1.9174MBps)
22:52:18: File transferred successfully
22:52:18: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
22:52:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=rawprogram_unsparse.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:22: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:22: INFO: Showing network mappings to allow debugging
22:52:22: INFO:
22:52:22: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
22:52:22: INFO: Looking for file 'rawprogram_unsparse.xml'
22:52:22: INFO: User wants to talk to port '\\.\COM10'
22:52:22: INFO: Took 0.00000000 seconds to open port
22:52:22: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:52:22: INFO: If you don't want this, use --dontsorttags
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO:
Total to be tansferd with <program> or <read> is 47.79 MB
22:52:22: INFO: Sending <configure>
22:52:22: INFO: TARGET SAID: 'UFS DEVICE RESET'
22:52:22: INFO: TARGET SAID: 'Binary build date: Dec 8 2017 @ 13:33:11'
22:52:22: INFO: TARGET SAID: 'Chip serial num: 0 (0x0)'
22:52:22: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
22:52:22: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
22:52:22: INFO: In handleProgram('boot.img')
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO: =======================================================
22:52:22: INFO: {<program> FILE: 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'}
22:52:22: INFO: {<program> (47.79 MB) 97883 sectors needed at location 393216 on LUN 0}
22:52:22: INFO: =======================================================
22:52:23: INFO: TARGET SAID: 'start 393216, num 97883'
22:52:24: INFO: Overall to target 1.391 seconds (34.36 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: TARGET SAID: 'Finished programming start_sector 491099 and TotalSectorsToProgram 97883'
22:52:24: INFO:
22:52:24: INFO: =======================================================
22:52:24: INFO: ==================== {SUCCESS} ========================
22:52:24: INFO: =======================================================
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: ==============================================================
22:52:24: INFO: Files used and their paths
22:52:24: INFO: 1 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
22:52:24: INFO: 2 'C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml'
22:52:24: INFO: 3 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'
22:52:24: INFO: _ (done)
22:52:24: INFO: | |
22:52:24: INFO: __| | ___ _ __ ___
22:52:24: INFO: / _` |/ _ \| '_ \ / _ \
22:52:24: INFO: | (_| | (_) | | | | __/
22:52:24: INFO: \__,_|\___/|_| |_|\___|
22:52:24: INFO: {All Finished Successfully}
22:52:24: INFO: Overall to target 1.657 seconds (28.84 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
22:52:27: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=patch0.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:27: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:27: INFO: Showing network mappings to allow debugging
22:52:28: INFO:
22:52:28: INFO: Trying to store 'patch0.xml' in string table
22:52:28: INFO: Looking for file 'patch0.xml'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML packet not formed correctly. Ran out of room looking for TAG}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML is not formatted correctly. Could not find closing />
}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
skeleton1911 said:
thanks. but thats not the problem of @Laptapper.
i think he is not on the latest build. because we have _a and _b system.
the latest build is on _b . also the root is only in _b
he could use cmd and adb in bootlader mode
fastboot set_active b
Setting current slot to 'b'...
but that will not work . the bootloader in the u pro is a bit strange. tested many things
Click to expand...
Click to collapse
Hello skeleton
Many thanks for your private chat support! I've tried a lot of things alone but only in case of your know-how to get a bricked phone working again.
I've got root now :highfive:
For me it's clear now that the problem was in my manually update of the full it's file. The phone has booted alone after the update and so I think it changed from image a to b.
I've done the update again and it has booted again.
Then I've removed all flashing software from Windows 10 and deleted old drivers. Complete clean up with registry clean with temp clean........
Then I've installed all of your tools again except python , here I took python 3 (by the way: we've talked about my short flashing time.....it was exactly short as before).
So may be also python could be the problem before but I guess it was the full ota.
Anyway ....for those who had problems like me try to flash the ota again (if before was done) or because better AND clean up all and then try again.
Many thanks again to the elephone u pro conqueror skeleton
Hopefully he will go further on with a full rom with twrp. And for this I've send him some dollars and I'll hope the other users will do it like me.
Laptapper said:
Hello skeleton
Many thanks for your private chat support! I've tried a lot of things alone but only in case of your know-how to get a bricked phone working again.
I've got root now :highfive:
For me it's clear now that the problem was in my manually update of the full it's file. The phone has booted alone after the update and so I think it changed from image a to b.
I've done the update again and it has booted again.
Then I've removed all flashing software from Windows 10 and deleted old drivers. Complete clean up with registry clean with temp clean........
Then I've installed all of your tools again except python , here I took python 3 (by the way: we've talked about my short flashing time.....it was exactly short as before).
So may be also python could be the problem before but I guess it was the full ota.
Anyway ....for those who had problems like me try to flash the ota again (if before was done) or because better AND clean up all and then try again.
Many thanks again to the elephone u pro conqueror skeleton
Hopefully he will go further on with a full rom with twrp. And for this I've send him some dollars and I'll hope the other users will do it like me.
Click to expand...
Click to collapse
Thank you very much i appreciate it
abbas said:
Thanks for your help. This is my log
Validating Application Configuration
Load APP Configuration
COM:-1
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM:
rawprogram_unsparse.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Programmer Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
Process Index:0
Image Search Path: C:\Users\abbas\Desktop\boot_b_root__QPST
RAWPROGRAM file path: C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml
PATCH file path:C:\Users\abbas\Desktop\boot_b_root__QPST\patch0.xml
Start Download
Program Path:C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf
22:52:17: Requested ID 13, file: "C:\Users\abbas\Desktop\boot_b_root__QPST\prog_emmc_ufs_firehose_Sdm660_ddr.elf"
22:52:18: 629284 bytes transferred in 0.313000 seconds (1.9174MBps)
22:52:18: File transferred successfully
22:52:18: Sahara protocol completed
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
22:52:22: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=rawprogram_unsparse.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:22: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:22: INFO: Showing network mappings to allow debugging
22:52:22: INFO:
22:52:22: INFO: Trying to store 'rawprogram_unsparse.xml' in string table
22:52:22: INFO: Looking for file 'rawprogram_unsparse.xml'
22:52:22: INFO: User wants to talk to port '\\.\COM10'
22:52:22: INFO: Took 0.00000000 seconds to open port
22:52:22: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
22:52:22: INFO: If you don't want this, use --dontsorttags
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO:
Total to be tansferd with <program> or <read> is 47.79 MB
22:52:22: INFO: Sending <configure>
22:52:22: INFO: TARGET SAID: 'UFS DEVICE RESET'
22:52:22: INFO: TARGET SAID: 'Binary build date: Dec 8 2017 @ 13:33:11'
22:52:22: INFO: TARGET SAID: 'Chip serial num: 0 (0x0)'
22:52:22: INFO: TARGET SAID: 'Supported Functions: program configure nop firmwarewrite patch setbootablestoragedrive ufs emmc power benchmark read getstorageinfo getsha256digest erase peek poke '
22:52:22: INFO: TARGET SAID: 'Calling usb_al_bulk_set_zlp_mode(TRUE) since ZlpAwareHost='1''
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 1048576
22:52:22: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
22:52:22: INFO: In handleProgram('boot.img')
22:52:22: INFO: Looking for file 'boot.img'
22:52:22: INFO: =======================================================
22:52:22: INFO: {<program> FILE: 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'}
22:52:22: INFO: {<program> (47.79 MB) 97883 sectors needed at location 393216 on LUN 0}
22:52:22: INFO: =======================================================
22:52:23: INFO: TARGET SAID: 'start 393216, num 97883'
22:52:24: INFO: Overall to target 1.391 seconds (34.36 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: TARGET SAID: 'Finished programming start_sector 491099 and TotalSectorsToProgram 97883'
22:52:24: INFO:
22:52:24: INFO: =======================================================
22:52:24: INFO: ==================== {SUCCESS} ========================
22:52:24: INFO: =======================================================
22:52:24: INFO: {percent files transferred 100.00%}
22:52:24: INFO: ==============================================================
22:52:24: INFO: Files used and their paths
22:52:24: INFO: 1 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
22:52:24: INFO: 2 'C:\Users\abbas\Desktop\boot_b_root__QPST\rawprogram_unsparse.xml'
22:52:24: INFO: 3 'C:\Users\abbas\Desktop\boot_b_root__QPST\boot.img'
22:52:24: INFO: _ (done)
22:52:24: INFO: | |
22:52:24: INFO: __| | ___ _ __ ___
22:52:24: INFO: / _` |/ _ \| '_ \ / _ \
22:52:24: INFO: | (_| | (_) | | | | __/
22:52:24: INFO: \__,_|\___/|_| |_|\___|
22:52:24: INFO: {All Finished Successfully}
22:52:24: INFO: Overall to target 1.657 seconds (28.84 MBps)
22:52:24: INFO: {percent files transferred 100.00%}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
***** Working Folder:C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10
Base Version: 16.10.28.15.28
Binary build date: Oct 31 2016 @ 22:51:02
Incremental Build version: 16.10.31.22.51.02
22:52:27: INFO: FH_LOADER WAS CALLED EXACTLY LIKE THIS
************************************************
C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe --port=\\.\COM10 --sendxml=patch0.xml --search_path=C:\Users\abbas\Desktop\boot_b_root__QPST --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
************************************************
22:52:27: INFO: Current working dir (cwd): C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\
22:52:27: INFO: Showing network mappings to allow debugging
22:52:28: INFO:
22:52:28: INFO: Trying to store 'patch0.xml' in string table
22:52:28: INFO: Looking for file 'patch0.xml'
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML packet not formed correctly. Ran out of room looking for TAG}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
22:52:28: {ERROR: XML is not formatted correctly. Could not find closing />
}
Writing log to 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt', might take a minute
Log is 'C:\Users\abbas\AppData\Roaming\Qualcomm\QFIL\COMPORT_10\port_trace.txt'
Download Fail:FireHose Fail:FHLoader Failrocess fail
Finish Download
Click to expand...
Click to collapse
Flash was fine.
look a post above . maybe thats also the solution for you
The root is good on my Upro, carved some space out on my Fat32 microSD to make Ext4 partition and it mounts with LinkSD Plus better then in Nougat where it was always little tricky. My next thing with Upro will be finding ways to extend the LTE bands, lots of threads on XDA about it to dig in.
https://drive.google.com/file/d/1MDw0itjMOznzbHDpRuHbOIFMPn0CVrXj/view?usp=sharing
skeleton1911 said:
Flash was fine.
look a post above . maybe thats also the solution for you
Click to expand...
Click to collapse
Finally done. I just reinstalled the OTA, installed Phyton 3.0.1 and voila, it is done. Thanks to everyone.
https://drive.google.com/file/d/1MDw0itjMOznzbHDpRuHbOIFMPn0CVrXj/view?usp=sharing[/QUOTE]
No Cache partition in Oreo? The storage shows the entire internal used for Cache.
Variant: XT1900-2 (commonly known as the Indian variant)
Channel: retapac
Storage/RAM: 64GB/4GB
Use the Download links, not the Source. The Source URLs can only be accessed when the Motorola Update Service is downloading the same version (different version might be OK, I didn't test). When the Motorola Update Service is downloading, the OTA server temporarily authorizes your (Internet) IP, so you can download it from your desktop or other devices (that shares the same IP). Otherwise, you would get HTTP ERROR 403. The links were accessible previously when my phone is updating, which was how I download the OTA zips (using my desktop browser).
Instruction: See https://forum.xda-developers.com/moto-x4/how-to/rom-upgrade-directly-to-pie-8-0-locked-t3876127
ADB sideload or unlocked bootloader probably won't work. Other variants/channels/storage/RAM might work (not tested). As always, flash at your own risk.
All OTAs: https://mega.nz/#F!XAFClSKC!IVPI6iLH74CQ89wBAA5PFg
Filename: Blur_Version.27.266.19.payton.retail.en.US.zip
Download: https://mega.nz/#!Dc1QiaII!DMHto5E1eXrZWz0R_CBzZwXpAAETlf-FnBVDSY5QZNQ
Blur: 27.266.19 -> 27.271.23
Build: OPWS27.2.2 -> OPWS27.2.3
Motorola: OPWS27.57-40-14 -> OPWS27.57-40-17
Security: 1 April 2018 -> 1 June 2018
Baseband: M660_7036.16.01.69R PAYTON_APACDSDS_CUST (Same)
OS: 8.0 (Same)
SHA256SUM: cea37f81fb026f32ee53c7ffa8db59624670137c199f24bbf029da148e69a357
Source:
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/VXo2J%2Fo8AOtIdtJlYDQ88nb98SYvcz3La8G7Q%2FzZfF%2Fx2%2B050WFYMNrGLsDB14%2BSIjX2%2BffVYrcksDn8LfDD7fuDEjZZbOLQ2IYRZH0OBs%2FO82Axl7OzAbj34PDYELnHqtLL7ZxTEAdvqmKGTkyR07ovJ%2BXFW5cghnAqwiaS9o%2FkXMdBya5LuOZkJ3paCk2GcJ%2B%2BRi50EkdLaabMq%2BX%2FxyWTcYwPw4nfhg%2BAP4ZU%2BoxpGnZmBWY%2FSZ8QqMDAFmJ8s9Ig9QkrFEM7JtPEfQBBD4sQey9pKnT9RUKzonuTJW2TbVC2xtGrALG4QSo2WUqCd4z9i2BF6GcYedCwbyJhrUZE9TenLqdTHrk6VKmBK0aUjOdB2fMTKZ8etBkvaBhfJD9oBQdzY7tfy1Og%2Fte%2BU2NroZ%2B1Y6Q27gyo66AAyxfbFKqjEQIaKP8SWhO2LhzW%2BrH7UFSyXkuXlWLjvBu92SPTlWaEOZx37E1ubWEi5DbHaxOX%2F5hKg9WIHIzXGNORODJOhKVkn8%2FVL7S0ik%2Biet6xPd%2BIXlimez7mbl6qBVCjwu86Kh2FJiD%2FMx6Mn1IFFgC2uk1IPhb2K5eRNiqP%2F8vP1J%2FyyctNv9KMqZ8Vxu31vcQgzyrueiHWMZbJ7lRGDbJd3C982LCxaKPwxNonCg%3D%3D
Filename: Blur_Version.27.271.23.payton.retail.en.US.zip
Download: https://mega.nz/#!ydlVESLS!lvEiCF12MlMTW_lWNzC0XHgVq0aGyAho1hYIW7QvjRM
Blur: 27.271.23 -> 27.281.28
Build: OPWS27.2.3 -> OPWS27.2.4
Motorola: OPWS27.57-40-17 -> OPWS27.57-40-22
Security: 1 June 2018 -> 1 August 2018
Baseband: M660_7036.16.01.69R PAYTON_APACDSDS_CUST -> M660_7036.16.01.69.01R PAYTON_APACDSDS_CUST
OS: 8.0 (Same)
SHA256SUM: 5ba197aee41333db2ac81a103234007a0a9221855788c811ab8a72e0e27c4b97
Source:
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/7LT4ZbgXuhG3B9SID6igK3b98SYvcz3La8G7Q%2FzZfF%2Fx2%2B050WFYMNrGLsDB14%2BSIjX2%2BffVYrcksDn8LfDD7fuDEjZZbOLQ2IYRZH0OBs%2FO82Axl7OzAbj34PDYELnHJVX7VHw6Oc4dPictfH5P9mDLVMxBseQP8R%2BK%2FezK7%2FXkXMdBya5LuOZkJ3paCk2GfedQ5Db2Uv2Qk8xSG76CQNHpc3SP%2FnPcmZB%2FvklroOH3e7djz6jwWwxbmK8S1SWbs9Ig9QkrFEM7JtPEfQBBD4sQey9pKnT9RUKzonuTJW2TbVC2xtGrALG4QSo2WUqCd4z9i2BF6GcYedCwbyJhrUZE9TenLqdTHrk6VKmBK0aUjOdB2fMTKZ8etBkvaBhfbN2dppRey8p%2BodbAzQPdoEYF0j5BmZe2wBEr%2BR2FfjQPEVbu3Krxpga9F9tQwuOkyH16GQRihqvTP2xfKDWv%2FY0s2duq2QPhbMapypVnP%2B2ten%2BtHD6aOXaV%2FjY62Tcm%2BQw%2FxusQVxPtrxCtpEIzyGgYOHyckBQ4UYZP41rVkXmBfeVBr9MMyYzNlkWu1kqV3bYRNuQyCx7MtjcAT31meNc8ilhvxNQjMeEVff3BhVLS9AlR6I17z2uzVNTD57fkm5uwooO5%2FT4LCWoyjdwy5g%3D%3D
Filename: Blur_Version.27.281.28.payton.retail.en.US.zip
Download: https://mega.nz/#!WRtj2IbJ!QlkQlDwdZDVo2LfIxfXnEc_tnXcVO7R_9noBlR686-c
Blur: 27.281.28 -> 27.301.32
Build: OPWS27.2.4 -> OPWS27.2.5
Motorola: OPWS27.57-40-22 -> OPWS27.57-40-25
Security: 1 August 2018 -> 1 October 2018
Baseband: M660_7036.16.01.69.01R PAYTON_APACDSDS_CUST -> M660_7036.16.01.69.02R PAYTON_APACDSDS_CUST
OS: 8.0 (Same)
SHA256SUM: b87600e72887e0fa9a21ed4452f4a033c21ba7e449a4d40ddda83fa763b2ad2e
Source:
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/WO7QB36R4539RFCOw5dx0Ynkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfUaEpYDTcFpv70Mtjlaua8WPEiMhigZVS7CEtx5RP%2FTzUsNSMV0YC5m8TngRy2Y9M5sBFDp3OA5JJqDMAMDtLAFTyfoZt2HWXrgjVHTJUS8CcAuW5QjPv5%2FJMwAdm36sfQ%3D%3D
Filename: Blur_Version.27.301.32.payton.retail.en.US.zip
Download: https://mega.nz/#!7FMFRK5B!nIWRvw2nvBEnHdnAguuRAqGNQ3uSwFu0BI6CRn1txHY
Blur: 27.301.32 -> 29.11.36
Build: OPWS27.2.5 -> PPW29.69-26
Motorola: OPWS27.57-40-25 -> ? (not shown in Pie?)
Security: 1 October 2018 -> 1 November 2018
Baseband: M660_7036.16.01.69.02R PAYTON_APACDSDS_CUST -> M660_7042.27.01.89R PAYTON_APACDSDS_CUST
SHA256SUM: f90b1fc256d8d5e3790f3dcc0f641edf5853d40beecd80407f921fa9efa2792a
OS: 8.0 -> 9.0
Note: This is similar update as the other thread, but the hash is different due to different variant.
Source:
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/qu6kSfSkWKOOAXN3FEAgjonkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfcpnX60qZKLQzKlcebP%2FdhcNsNn9Cb9QEEvcjBuGsnOe8iEJiyLtWqnD4JNRgzgQ7%2FYmue0L0b6uZLl8KB7Q6iD9c2h8CXFi9ClB5tv0ihvsOcTQjLUHJm1jGxmqUAatFw%3D%3D
Filename: Blur_Version.29.11.36.payton.retail.en.US.zip
Download: https://mega.nz/#!bQdhGCDZ!cIw3Z6qLp7-dOW5X74VX604lgFxK7451hbDMNRhR8-g
Blur: 29.11.36 -> 29.211.11
Build: PPW29.69-26 -> PPWS29.69-26-4
Motorola: ? -> ? (not shown in Pie?)
Security: 1 November 2018 -> 1 January 2019
Baseband: M660_7042.27.01.89R PAYTON_APACDSDS_CUST-> ? (unknown because I don't install it. I've switched to custom ROM by then)
OS: 9.0 (Same)
SHA256SUM: d9119765a028262e4e9ddec871702300133aaf177ae8a98c0827df244a8255d1
Source:
Code:
https://dlmgr.gtm.svcmot.com/dl/dlws/1/download/iAw8NkhECSbfjmHMvZw9Qonkj9%2FmlRBFuisKgbOUteZFGF0LVIr3fZGsyTBNleklN%2BvGu2j4xooz5Ky%2Fve7SfZM05zAizxusyjY9I1yc2nZ%2FnVByLo%2BzXaVBNT9O2CZR%2F%2FKUaFUpFD9Wl7rEizYklz9eem3182RDZAvW6aO86%2Fzewdke2HpS%2FmesDDU%2FHvFpOcTQjLUHJm1jGxmqUAatFw%3D%3D
When in doubt, check the metadata.json inside the zip. Earlier ZIPs are not available, I forgot to capture them.
Will it work on relocked bootloader?
Works with:
- Xiaomi Redmi 9A
- Xiaomi Redmi 9AT
Does NOT work with:
- Xiaomi Redmi 10A
Build Date:
2020/07/03
Android Version:
QP1A.190711.020
Display ID:
dandelion-userdebug 10 QP1A.190711.020 246 test-keys
Build Fingerprint:
Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
Security Patch:
2020/03/05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V107.5.P4
Download:
https://www.mediafire.com/file/7kaa...neering_246_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use the attached scatter file.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6765_MOLY_LR12A_R3_MP_V107_5_P4_2020_05_08_15_56.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_LCSH_Q0MP1_MT6762_SP_MOLY_LR12A_R3_MP_V107_5_P4_2020_07_01_16_05.xz
md1_mddbmeta=MDDB.META_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
Prop.default:
Code:
ro.build.version.incremental=246
ro.vendor.build.version.incremental=246
ro.odm.build.version.incremental=246
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp3-V1.4_lcsh.q0mp1.k62v1.64.bsp_P4
ro.product.system.device=dandelion
ro.product.system.model=dandelion
ro.product.system.name=dandelion
ro.build.product=dandelion
ro.product.board=dandelion
ro.product.vendor.device=dandelion
ro.product.vendor.model=dandelion
ro.product.vendor.name=dandelion
ro.product.odm.device=dandelion
ro.product.odm.model=dandelion
ro.product.odm.name=dandelion
ro.product.product.device=dandelion
ro.product.product.model=dandelion
ro.product.product.name=dandelion
ro.build.flavor=dandelion-userdebug
ro.build.display.id=dandelion-userdebug 10 QP1A.190711.020 246 test-keys
ro.build.description=dandelion-userdebug 10 QP1A.190711.020 246 test-keys
ro.board.platform=mt6765
ro.system.build.id=QP1A.190711.020
ro.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.bootimage.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.product.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.system.build.tags=test-keys
ro.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.type=userdebug
ro.build.type=userdebug
ro.vendor.build.type=userdebug
ro.odm.build.type=userdebug
ro.build.version.security_patch=2020-03-05
ro.vendor.build.security_patch=2020-03-05
ro.system.build.date=Fri Jul 3 07:47:24 CST 2020
ro.build.date=Fri Jul 3 07:47:24 CST 2020
ro.vendor.build.date=Fri Jul 3 07:47:24 CST 2020
ro.odm.build.date=Fri Jul 3 07:47:24 CST 2020
ro.product.build.date=Fri Jul 3 07:47:24 CST 2020
ro.bootimage.build.date=Fri Jul 3 07:47:24 CST 2020
MD5 hashes:
Code:
android-info.txt -> 32dbb7967eee2053e0317f87a93fb6b9
APDB_MT6765_S01__W2015 -> 5358ccefe1fda7f456f3a568ec4b04d5
APDB_MT6765_S01__W2015_ENUM -> fbe5f23b8bc20d1bce7be6200a0731a1
apex -> d41d8cd98f00b204e9800998ecf8427e
arm11_path.txt -> e40c703ef2deffd68827450517984a77
boot-debug.img -> c1d38992863d18176047b02429b11c59
boot.img -> a32268ea83ff1d5d51f47eca241a87a3
build.prop -> 3ae4db3db38ca854dd72df6a457aa703
build_fingerprint.txt -> 07d4c4773385f28d5f0b4659f6777d3b
build_thumbprint.txt -> 9cd94d3bb077ca0d08d72c4bf3131ec3
cache.img -> 9515cdaf0a9558de94f0502ed3664da4
Checksum.ini -> 7a098cb0b8710975489f70478283ab30
clean_steps.mk -> 30f988afe6140fd1afb0a19ed9b53da4
content_cert_sig.bin_hash.tmp -> b0b9c0585e65fab3fa827d4aac0edf26
cust.img -> 09e9b617296df53b0716255c86d01c53
dexpreopt.config -> 3bd2bfa98738f4798fcc97be5ba41e74
dtb.img -> 8cae5478f4627f3dd5f27f7d970db7e5
dtbo-verified.img -> 6c55f4ca20af2d45b1635103df4f68a1
dtbo.img -> 24a92cc62b438970407ff16536fcb4bb
dummy.bin -> 6811c482ead27c0b1165ecfbe996c2b4
efuse.img -> 22e70283687ccca929e3f6d117c5fc34
flash_all.bat -> 024c2db0556931d2d7fc6e92e6ed54b6
fs_image.tar.gz.mbn.img -> 633b9aac7f2d2e81c0dc595d2a644d80
init -> 0c3c9ae3511888e757583690d46e8068
installed-files-product.json -> 8f6fce4756c9e83ccedd0299939e7bdd
installed-files-product.txt -> a9198d055f20793c95bbb5eb12a163ca
installed-files-ramdisk-debug.json -> 0ef92222c9c2cd818c9c6dcd7b727007
installed-files-ramdisk-debug.txt -> 3d2578d523ca82acb1e878fcf5718261
installed-files-ramdisk.json -> 398a83700d0da10043200dd81f5b7397
installed-files-ramdisk.txt -> 194df0e3bdef259bd0d69c036a6af870
installed-files-recovery.json -> e5a3877f1341d5b950e91193ab78a746
installed-files-recovery.txt -> 7e9701a5f6c42c9cd27a0125e3b99888
installed-files-root.json -> e2017cd6f1befb266cb137f306b0a6eb
installed-files-root.txt -> 40d211d2878ac2e27d1d93878dff8a41
installed-files-vendor.json -> 4d53b60ae91e57b5a6a79e760759c72f
installed-files-vendor.txt -> 179c7cb9aa22d7134c5c26b731022e24
installed-files.json -> 0790dbb6a5ecd887b7ff26db3a7ba8b6
installed-files.txt -> f2f4e07ee2f870fc4f90dcae2c87280a
kernel -> f8e1e485a3a62a4394e9519e9ca4fc83
LCSH_Q0MP1_MT6762_SP_PCB01_MT6765_S00_1_lwg_n.elf -> 6787d83c0163564471394381f4f8d29a
lk-verified.img -> 0b178c7801d794020c2a451af00ffedc
lk.img -> 5449098089f99f6665621a0c86beaddb
logo-verified.bin -> b8e0d8450e3d4d99cf0b3bd871152a7a
logo.bin -> 535bfd42ca7ef019d44c6ae64104633e
md1arm7-verified.img -> 1b32f1ebac264d195c7f555b9fd8f042
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> dd3497f816cf00c9925d8115cc77a474
md1img.img -> 0d4d8c18261e8a697c5e933ac482f352
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4_1_ulwctg_n.EDB -> 449ece5c1a6ab8ffa6b4efc92891be72
module-info.json -> 5d00ba03fa5af1e00c75ffac1f7903b0
MT6765_Android_scatter.txt -> bf253edfc605418fd862337cdcb488ff
PGPT -> 20bedc49348b16cdc20be09c4f32245c
preloader.bin -> d63fc47140c0d7c1bc6ea86ec6ce9043
preloader.img -> 59f7f68c99f30b5471e166a82c1bda57
preloader_dandelion.bin -> d63fc47140c0d7c1bc6ea86ec6ce9043
preloader_dandelion_signed.bin -> ba020d4e46ff99bcc91ccb2da887bc20
preloader_emmc.img -> 59f7f68c99f30b5471e166a82c1bda57
preloader_k62v1_64_bsp.bin -> ba020d4e46ff99bcc91ccb2da887bc20
preloader_ufs.img -> 1883960018454eaae59555c48dc7285b
previous_build_config.mk -> 673bf9a01f6afa6b55a5554ed1a09176
product -> d41d8cd98f00b204e9800998ecf8427e
product.img -> 41a7589079435e9f84b93feedbbbcf1e
ramdisk-debug.img -> 24a5f19c3eb41e553f8e035e4125b383
ramdisk-recovery.img -> a6b50d8cb84d722d405200f35c961e08
ramdisk.img -> 2392bea220016ec89cd9b7df0c6ce173
recovery -> d41d8cd98f00b204e9800998ecf8427e
recovery.id -> b86a1ea13fe21eea9a521b2e1da13146
recovery.img -> a9cd39f28ee3063afd9639ee151fef38
scp-verified.img -> 2f168c310b4f23d403548a766ee71bc5
scp.img -> 1e0a976e554975c7d5625910436916ae
secro.img -> 096587b863e1252d67b1b8307291db09
sig_size.txt -> 7a600b6f266737e2830a101876dd3561
sparsecrclist.img -> 9a027470a494d216f144b6a2ac86c440
spmfw-verified.img -> d6b568c6f86146aed476b91bbdf61341
spmfw.img -> 66cf26550d6650dd65f5f3865948bdf2
sspm-verified.img -> d014b44c00a39b78c4c08384996282ae
sspm.img -> b281a508c22190047eed1af202bd5520
super.img -> eba65ecb1ec79c259c59a27c45b9d70a
super_empty.img -> f911a1089119bd6f6a56919deb7bb9e8
system -> d41d8cd98f00b204e9800998ecf8427e
system.img -> 4a340e79e83e90d6c70360b6503cfa20
TARGET.txt -> 748150f0c3bbf2fa4dcc3346e73099f5
tee-verified.img -> 452aa3410f1be5f80d5c52aa1751a6c3
tee.img -> c17a4cd1a2c8265954ce3238fad9f3b3
userdata.img -> 0af062847d5f163ed835686f4a196743
vbmeta.img -> 8f10a8eabccb78a5ef5526ba8a0b17a4
vbmeta_system.img -> c3fa65e967f5b63c200b6493df9b5034
vbmeta_vendor.img -> b8faac2a2e1a60aa6cf6030ac7e3827d
vendor -> d41d8cd98f00b204e9800998ecf8427e
vendor.img -> 160818f19e7460b7a4d266eab93b4768
Is this miui or aosp ?
m.arham said:
Is this miui or aosp ?
Click to expand...
Click to collapse
That is a leaked OFFICIAL rom.
So, obviously that is MIUI.
Does not turn on after engineering firmware. On MIUI, it is enabled, but there is no imei and no radio module. Tell me what's wrong. Lk and lk2 flashed separately from MIUI, still not included.
stels.ol said:
Does not turn on after engineering firmware. On MIUI, it is enabled, but there is no imei and no radio module. Tell me what's wrong. Lk and lk2 flashed separately from MIUI, still not included.
Click to expand...
Click to collapse
If you lost radio/baseband, you need to format nvdata and then flash the whole miui again.
After the first reboot, the device will rewrite the baseband.
VD171 said:
If you lost radio/baseband, you need to format nvdata and then flash the whole miui again.
After the first reboot, the device will rewrite the baseband.
Click to expand...
Click to collapse
Thank you!
stels.ol said:
Thank you!
Click to expand...
Click to collapse
You are welcome, my friend.
Enjoy
Any way to install gapps?
kalonjee said:
Any way to install gapps?
Click to expand...
Click to collapse
I suggest you to make daily usage on another ROM.
This engineering rom is for certain purpoises and not for daily usage.
the device dont start after flashing this (tried without preload of course)
ernestico911 said:
the device dont start after flashing this (tried without preload of course)
Click to expand...
Click to collapse
Try to bypass the EDL auth.
is MIUI 12.0.10?
Al3xFreitex said:
is MIUI 12.0.10?
Click to expand...
Click to collapse
No. This is Engineering ROM build 246.
a question, from this ROM I can change to another ROM like NUSANTARA ROM and that the wifi works
Al3xFreitex said:
a question, from this ROM I can change to another ROM like NUSANTARA ROM and that the wifi works
Click to expand...
Click to collapse
I have no ideia, I'm sorry.
VD171 said:
Works with:
- Xiaomi Redmi 9A
- Xiaomi Redmi 9AT
Does NOT work with:
- Xiaomi Redmi 10A
Build Date:
2020/07/03
Android Version:
QP1A.190711.020
Display ID:
dandelion-userdebug 10 QP1A.190711.020 246 test-keys
Build Fingerprint:
Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
Security Patch:
2020/03/05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V107.5.P4
Download:
https://www.mediafire.com/file/7kaa...neering_246_QP1A.190711.020_by-VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use the attached scatter file.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6765_MOLY_LR12A_R3_MP_V107_5_P4_2020_05_08_15_56.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_LCSH_Q0MP1_MT6762_SP_MOLY_LR12A_R3_MP_V107_5_P4_2020_07_01_16_05.xz
md1_mddbmeta=MDDB.META_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
Prop.default:
Code:
ro.build.version.incremental=246
ro.vendor.build.version.incremental=246
ro.odm.build.version.incremental=246
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp3-V1.4_lcsh.q0mp1.k62v1.64.bsp_P4
ro.product.system.device=dandelion
ro.product.system.model=dandelion
ro.product.system.name=dandelion
ro.build.product=dandelion
ro.product.board=dandelion
ro.product.vendor.device=dandelion
ro.product.vendor.model=dandelion
ro.product.vendor.name=dandelion
ro.product.odm.device=dandelion
ro.product.odm.model=dandelion
ro.product.odm.name=dandelion
ro.product.product.device=dandelion
ro.product.product.model=dandelion
ro.product.product.name=dandelion
ro.build.flavor=dandelion-userdebug
ro.build.display.id=dandelion-userdebug 10 QP1A.190711.020 246 test-keys
ro.build.description=dandelion-userdebug 10 QP1A.190711.020 246 test-keys
ro.board.platform=mt6765
ro.system.build.id=QP1A.190711.020
ro.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.bootimage.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.product.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/246:userdebug/test-keys
ro.system.build.tags=test-keys
ro.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.type=userdebug
ro.build.type=userdebug
ro.vendor.build.type=userdebug
ro.odm.build.type=userdebug
ro.build.version.security_patch=2020-03-05
ro.vendor.build.security_patch=2020-03-05
ro.system.build.date=Fri Jul 3 07:47:24 CST 2020
ro.build.date=Fri Jul 3 07:47:24 CST 2020
ro.vendor.build.date=Fri Jul 3 07:47:24 CST 2020
ro.odm.build.date=Fri Jul 3 07:47:24 CST 2020
ro.product.build.date=Fri Jul 3 07:47:24 CST 2020
ro.bootimage.build.date=Fri Jul 3 07:47:24 CST 2020
MD5 hashes:
Code:
android-info.txt -> 32dbb7967eee2053e0317f87a93fb6b9
APDB_MT6765_S01__W2015 -> 5358ccefe1fda7f456f3a568ec4b04d5
APDB_MT6765_S01__W2015_ENUM -> fbe5f23b8bc20d1bce7be6200a0731a1
apex -> d41d8cd98f00b204e9800998ecf8427e
arm11_path.txt -> e40c703ef2deffd68827450517984a77
boot-debug.img -> c1d38992863d18176047b02429b11c59
boot.img -> a32268ea83ff1d5d51f47eca241a87a3
build.prop -> 3ae4db3db38ca854dd72df6a457aa703
build_fingerprint.txt -> 07d4c4773385f28d5f0b4659f6777d3b
build_thumbprint.txt -> 9cd94d3bb077ca0d08d72c4bf3131ec3
cache.img -> 9515cdaf0a9558de94f0502ed3664da4
Checksum.ini -> 7a098cb0b8710975489f70478283ab30
clean_steps.mk -> 30f988afe6140fd1afb0a19ed9b53da4
content_cert_sig.bin_hash.tmp -> b0b9c0585e65fab3fa827d4aac0edf26
cust.img -> 09e9b617296df53b0716255c86d01c53
dexpreopt.config -> 3bd2bfa98738f4798fcc97be5ba41e74
dtb.img -> 8cae5478f4627f3dd5f27f7d970db7e5
dtbo-verified.img -> 6c55f4ca20af2d45b1635103df4f68a1
dtbo.img -> 24a92cc62b438970407ff16536fcb4bb
dummy.bin -> 6811c482ead27c0b1165ecfbe996c2b4
efuse.img -> 22e70283687ccca929e3f6d117c5fc34
flash_all.bat -> 024c2db0556931d2d7fc6e92e6ed54b6
fs_image.tar.gz.mbn.img -> 633b9aac7f2d2e81c0dc595d2a644d80
init -> 0c3c9ae3511888e757583690d46e8068
installed-files-product.json -> 8f6fce4756c9e83ccedd0299939e7bdd
installed-files-product.txt -> a9198d055f20793c95bbb5eb12a163ca
installed-files-ramdisk-debug.json -> 0ef92222c9c2cd818c9c6dcd7b727007
installed-files-ramdisk-debug.txt -> 3d2578d523ca82acb1e878fcf5718261
installed-files-ramdisk.json -> 398a83700d0da10043200dd81f5b7397
installed-files-ramdisk.txt -> 194df0e3bdef259bd0d69c036a6af870
installed-files-recovery.json -> e5a3877f1341d5b950e91193ab78a746
installed-files-recovery.txt -> 7e9701a5f6c42c9cd27a0125e3b99888
installed-files-root.json -> e2017cd6f1befb266cb137f306b0a6eb
installed-files-root.txt -> 40d211d2878ac2e27d1d93878dff8a41
installed-files-vendor.json -> 4d53b60ae91e57b5a6a79e760759c72f
installed-files-vendor.txt -> 179c7cb9aa22d7134c5c26b731022e24
installed-files.json -> 0790dbb6a5ecd887b7ff26db3a7ba8b6
installed-files.txt -> f2f4e07ee2f870fc4f90dcae2c87280a
kernel -> f8e1e485a3a62a4394e9519e9ca4fc83
LCSH_Q0MP1_MT6762_SP_PCB01_MT6765_S00_1_lwg_n.elf -> 6787d83c0163564471394381f4f8d29a
lk-verified.img -> 0b178c7801d794020c2a451af00ffedc
lk.img -> 5449098089f99f6665621a0c86beaddb
logo-verified.bin -> b8e0d8450e3d4d99cf0b3bd871152a7a
logo.bin -> 535bfd42ca7ef019d44c6ae64104633e
md1arm7-verified.img -> 1b32f1ebac264d195c7f555b9fd8f042
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> dd3497f816cf00c9925d8115cc77a474
md1img.img -> 0d4d8c18261e8a697c5e933ac482f352
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4_1_ulwctg_n.EDB -> 449ece5c1a6ab8ffa6b4efc92891be72
module-info.json -> 5d00ba03fa5af1e00c75ffac1f7903b0
MT6765_Android_scatter.txt -> bf253edfc605418fd862337cdcb488ff
PGPT -> 20bedc49348b16cdc20be09c4f32245c
preloader.bin -> d63fc47140c0d7c1bc6ea86ec6ce9043
preloader.img -> 59f7f68c99f30b5471e166a82c1bda57
preloader_dandelion.bin -> d63fc47140c0d7c1bc6ea86ec6ce9043
preloader_dandelion_signed.bin -> ba020d4e46ff99bcc91ccb2da887bc20
preloader_emmc.img -> 59f7f68c99f30b5471e166a82c1bda57
preloader_k62v1_64_bsp.bin -> ba020d4e46ff99bcc91ccb2da887bc20
preloader_ufs.img -> 1883960018454eaae59555c48dc7285b
previous_build_config.mk -> 673bf9a01f6afa6b55a5554ed1a09176
product -> d41d8cd98f00b204e9800998ecf8427e
product.img -> 41a7589079435e9f84b93feedbbbcf1e
ramdisk-debug.img -> 24a5f19c3eb41e553f8e035e4125b383
ramdisk-recovery.img -> a6b50d8cb84d722d405200f35c961e08
ramdisk.img -> 2392bea220016ec89cd9b7df0c6ce173
recovery -> d41d8cd98f00b204e9800998ecf8427e
recovery.id -> b86a1ea13fe21eea9a521b2e1da13146
recovery.img -> a9cd39f28ee3063afd9639ee151fef38
scp-verified.img -> 2f168c310b4f23d403548a766ee71bc5
scp.img -> 1e0a976e554975c7d5625910436916ae
secro.img -> 096587b863e1252d67b1b8307291db09
sig_size.txt -> 7a600b6f266737e2830a101876dd3561
sparsecrclist.img -> 9a027470a494d216f144b6a2ac86c440
spmfw-verified.img -> d6b568c6f86146aed476b91bbdf61341
spmfw.img -> 66cf26550d6650dd65f5f3865948bdf2
sspm-verified.img -> d014b44c00a39b78c4c08384996282ae
sspm.img -> b281a508c22190047eed1af202bd5520
super.img -> eba65ecb1ec79c259c59a27c45b9d70a
super_empty.img -> f911a1089119bd6f6a56919deb7bb9e8
system -> d41d8cd98f00b204e9800998ecf8427e
system.img -> 4a340e79e83e90d6c70360b6503cfa20
TARGET.txt -> 748150f0c3bbf2fa4dcc3346e73099f5
tee-verified.img -> 452aa3410f1be5f80d5c52aa1751a6c3
tee.img -> c17a4cd1a2c8265954ce3238fad9f3b3
userdata.img -> 0af062847d5f163ed835686f4a196743
vbmeta.img -> 8f10a8eabccb78a5ef5526ba8a0b17a4
vbmeta_system.img -> c3fa65e967f5b63c200b6493df9b5034
vbmeta_vendor.img -> b8faac2a2e1a60aa6cf6030ac7e3827d
vendor -> d41d8cd98f00b204e9800998ecf8427e
vendor.img -> 160818f19e7460b7a4d266eab93b4768
Click to expand...
Click to collapse
Hello. I recently flashed the firmware v12.0.10 global from PitchBlack Recovery. I was on v12.5.12 China before flashing. What I did was boot into the recovery, flash the firmware, flash the new recovery who Works with firmware v12.0.10 and then the installer of that recovery rebooted my device automatically. The result is that my Redmi 9A is dead. It doesnt show the initial screen after power on, nor boot, nor nothing. I can not enter it in META mode either. The Maui Meta software is not able to put it into META mode because it fails when checking Serial Link Authentication with error 6004, after checking the baseband chip, send AUTH. Do you know any tricks, software or whatever that help me to bring to life this device?
leiniercs said:
Hello. I recently flashed the firmware v12.0.10 global from PitchBlack Recovery. I was on v12.5.12 China before flashing. What I did was boot into the recovery, flash the firmware, flash the new recovery who Works with firmware v12.0.10 and then the installer of that recovery rebooted my device automatically. The result is that my Redmi 9A is dead. It doesnt show the initial screen after power on, nor boot, nor nothing. I can not enter it in META mode either. The Maui Meta software is not able to put it into META mode because it fails when checking Serial Link Authentication with error 6004, after checking the baseband chip, send AUTH. Do you know any tricks, software or whatever that help me to bring to life this device?
Click to expand...
Click to collapse
use EDL mode to revive your phone, and use SP Flash Tool to revive it on Global Firmware
Al3xFreitex said:
use EDL mode to revive your phone, and use SP Flash Tool to revive it on Global Firmware
Click to expand...
Click to collapse
Hello. I was able to flash the stock ROM once again using the software MTKClient. It has modern techniques. Now I'm using crDroid with firmware 12.5.12 R-vendor. I relieve that I must to flash the full stock ROM v12.0.10 if I want to avoid that bar experience once again, and then flash other custom ROMs. Thank you all for your tips.
leiniercs said:
Hello. I was able to flash the stock ROM once again using the software MTKClient. It has modern techniques. Now I'm using crDroid with firmware 12.5.12 R-vendor. I relieve that I must to flash the full stock ROM v12.0.10 if I want to avoid that bar experience once again, and then flash other custom ROMs. Thank you all for your tips.
Click to expand...
Click to collapse
I do not recommend it, if it is bricked in v12.0.10 it is because you have the ARB (AntiRollBack) that prevents you from downgrading to other versions
leiniercs said:
Hola. Pude flashear la ROM stock una vez más usando el software MTKClient. Tiene técnicas modernas. Ahora estoy usando crDroid con firmware 12.5.12 R-vendor. Considero que debo flashear la ROM de stock completa v12.0.10 si quiero evitar esa experiencia de barra una vez más, y luego flashear otras ROM personalizadas. Gracias a todos por sus consejos.
Click to expand...
Click to collapse
Could you tell me how you flashed the CrDroid ROM? because I've done a lot of research and if I don't downgrade to MIUI 12.0.10 I get a Wi-Fi bug
Hello,
i trying to edit inside boot.img with Android-Kitchen-0.224
Commands:
Code:
1. Set up working folder from ROM
2. Ensure there is at least one ROM under the 'original_update' folder! (Enter)
3. (1) system.img and boot.img (Enter)
4. Creating a folder named (WORKING_040621_174933)
5. Delete everying inside (WORKING_040621_174933)
6. ./menu -> ADVANCED OPTIONS (0) -> 12 -> a -> Place boot.img/recovery.img into the folder mentioned above (bootimg_040621_175411) -> copy boot.img and recovery.img into (bootimg_040621_175411)
7. ./menu -> ADVANCED OPTIONS (0) -> 12 -> w
8. copy all "bootimg_040621_175411" into "BOOT-EXTRACTED"
9. ./menu -> ADVANCED OPTIONS (0) -> 12 -> b
Why does reduce MB Size from 32MB -> 17MB
Code:
Old: -rwxrwxrwx 1 fredy fredy 32M Apr 6 17:49 boot.img
New: -rw-r--r-- 1 fredy fredy 17M Apr 6 17:57 boot.img
But then i unpack the files and repack it i can't boot up any more.
can you help me out?
@007fred62
If you compare the file permissions of old & new boot.img then you will know why device no longer boots up.
jwoegerbauer said:
@007fred62
If you compare the file permissions of old & new boot.img then you will know why device no longer boots up.
Click to expand...
Click to collapse
Hello,
commands "ls -ll"
-rwxrwxrwx 1 fredy fredy 17436672 Apr 6 17:22 boot_fixBootLoop.img
chmod 777 the file.
i use SP_Flash_Tool-5.1916_Linux to flash the new boot file
And it will not start up.
I use the other script to recreate the boot.img (CarlivImageKitchen64)
Works with:
- Xiaomi Redmi 9A
- Xiaomi Redmi 9AT
Does NOT work with:
- Xiaomi Redmi 10A
Build Date:
2020/09/20
Android Version:
QP1A.190711.020
Display ID:
AL2615-lancelot-V016-Q-0918
Build Fingerprint:
Redmi/lancelot/lancelot:10/QP1A.190711.020/20:userdebug/test-keys
Security Patch:
2019-12-05
Radio/Modem/Baseband Version:
MOLY.LR12A.R3.MP.V107.5.P4
Download:
https://www.mediafire.com/file/l28w...neering-440-QP1A.190711.020-by_VD171.zip/file
Password:
Pass is in the attached file: PASSWORD_by_VD171.txt
How to flash it?
Use the attached scatter file.
Radio/Modem/Baseband properties:
Code:
md1_dbginfodsp=DbgInfo_DSP_MT6765_MOLY_LR12A_R3_MP_V107_5_P4_2020_05_08_15_56.xz
md1_dbginfo=DbgInfo_LR12A.R3.MP_LCSH_Q0MP1_MT6762_SP_MOLY_LR12A_R3_MP_V107_5_P4_2020_10_30_17_04.xz
md1_mddbmeta=MDDB.META_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
md1_mddbmetaodb=MDDB.META.ODB_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.XML.GZ
md1_mddb=MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4.EDB
Prop.default:
Code:
ro.build.version.incremental=440
ro.vendor.build.version.incremental=440
ro.odm.build.version.incremental=440
ro.build.version.security_patch=2020-03-05
ro.vendor.build.security_patch=2020-03-05
ro.build.display.id=dandelion-userdebug 10 QP1A.190711.020 440 test-keys
ro.vendor.mediatek.version.release=alps-mp-q0.mp1.tc8sp3-V1.4_lcsh.q0mp1.k62v1.64.bsp_P4
ro.product.system.device=dandelion
ro.product.system.model=dandelion
ro.product.system.name=dandelion
ro.build.product=dandelion
ro.product.board=dandelion
ro.product.vendor.device=dandelion
ro.product.vendor.model=dandelion
ro.product.vendor.name=dandelion
ro.product.odm.device=dandelion
ro.product.odm.model=dandelion
ro.product.odm.name=dandelion
ro.product.product.device=dandelion
ro.product.product.model=dandelion
ro.product.product.name=dandelion
ro.build.flavor=dandelion-userdebug
ro.build.description=dandelion-userdebug 10 QP1A.190711.020 440 test-keys
ro.board.platform=mt6765
ro.system.build.id=QP1A.190711.020
ro.build.id=QP1A.190711.020
ro.vendor.build.id=QP1A.190711.020
ro.odm.build.id=QP1A.190711.020
ro.product.build.id=QP1A.190711.020
ro.system.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/440:userdebug/test-keys
ro.vendor.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/440:userdebug/test-keys
ro.bootimage.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/440:userdebug/test-keys
ro.odm.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/440:userdebug/test-keys
ro.product.build.fingerprint=Redmi/dandelion/dandelion:10/QP1A.190711.020/440:userdebug/test-keys
ro.system.build.tags=test-keys
ro.build.tags=test-keys
ro.vendor.build.tags=test-keys
ro.odm.build.tags=test-keys
ro.system.build.type=userdebug
ro.build.type=userdebug
ro.vendor.build.type=userdebug
ro.odm.build.type=userdebug
ro.system.build.date=Fri Nov 13 07:08:25 CST 2020
ro.build.date=Fri Nov 13 07:08:25 CST 2020
ro.vendor.build.date=Fri Nov 13 07:08:25 CST 2020
ro.bootimage.build.date=Fri Nov 13 07:08:25 CST 2020
ro.odm.build.date=Fri Nov 13 07:08:25 CST 2020
ro.product.build.date=Fri Nov 13 07:08:25 CST 2020
MD5 hashes:
Code:
ADPT_20201113-083150_0.log -> 480ee59a3ed686ca2458cd7243ea4b2d
android-info.txt -> 32dbb7967eee2053e0317f87a93fb6b9
APDB_MT6765_S01__W2015 -> 5358ccefe1fda7f456f3a568ec4b04d5
APDB_MT6765_S01__W2015_ENUM -> fbe5f23b8bc20d1bce7be6200a0731a1
apex -> d41d8cd98f00b204e9800998ecf8427e
arm11_path.txt -> 08876b2f90811c34cab13c7ff5e0e9dd
boot-debug.img -> a138170982bbbc79dc5969f7654f3485
boot.img -> 8538775edb84c5e6c8eeb5f534049c44
build.prop -> 7ff8a14f1f284545e75d1d8767ed38f8
build_fingerprint.txt -> e9e053d16e8c9b057bdf02c8ec13ed65
build_thumbprint.txt -> 0e32dcd8f7ea37aea27c1b04541c80dc
cache.img -> 012fcfb3a30f86d210bb9038138636e3
Checksum.ini -> f5a9b0de9d91b32b39f527918aa4962c
clean_steps.mk -> 30f988afe6140fd1afb0a19ed9b53da4
content_cert_sig.bin_hash.tmp -> 2d274d38535bf4fae2a80a8a6c28e6e3
CT865_factory_1_0.zip -> 1a8d2920eee999ef3b014c46adb61137
cust.img -> 09e9b617296df53b0716255c86d01c53
dexpreopt.config -> 3bd2bfa98738f4798fcc97be5ba41e74
dtb.img -> 8cae5478f4627f3dd5f27f7d970db7e5
dtbo-verified.img -> dddbf145fba03a12ba060a8a79dc6d9b
dtbo.img -> 49d56a5ce0f6c14c025a030e90cfd1ef
dummy.bin -> 6811c482ead27c0b1165ecfbe996c2b4
efuse.img -> 22e70283687ccca929e3f6d117c5fc34
flash_all.bat -> 3a15f1b192e819d29502100f6f93427a
fs_image.tar.gz.mbn.img -> c696a342b6de28e36a776ba85972c1a0
init -> 0c3c9ae3511888e757583690d46e8068
installed-files-product.json -> 449a46ce04df11754714762c202e92cf
installed-files-product.txt -> a9198d055f20793c95bbb5eb12a163ca
installed-files-ramdisk-debug.json -> 541357cd9df88b12a964b2ee1d14d3fa
installed-files-ramdisk-debug.txt -> ab32416ccaf4cc2972733fe5f3dfee19
installed-files-ramdisk.json -> bc58c28abb95fd7f61845248370e9a00
installed-files-ramdisk.txt -> f8baf00b2f269e8f9ead5fc31b365878
installed-files-recovery.json -> 40066ea794509825c4928f89bc847abe
installed-files-recovery.txt -> 6e472833a5b1a32b3b459338e2c5fda8
installed-files-root.json -> 180b39f8042272c46ef6cf3339a5eaa9
installed-files-root.txt -> cae4505da086ba6466b178cdcf670398
installed-files-vendor.json -> abf9fff24dea8f2f2a97afcd3f82fb3a
installed-files-vendor.txt -> a73b112d46d8fa325a83544939059cac
installed-files.json -> 1989a226988e7fb041b55cd838bb3a59
installed-files.txt -> 9b9aab253cd9051b2840bb983551abc5
kernel -> 177bca792e0dba738898cc5b0a44fc79
LCSH_Q0MP1_MT6762_SP_PCB01_MT6765_S00_1_lwg_n.elf -> 39b3477d0b7a8105bd8b4e8df39575f6
lk-verified.img -> 2638aba2ba72c427d84f6a372a6d42e6
lk.img -> ee642501342981b7cc18b65b7d493cf6
logo-verified.bin -> 66c4fcf02bd2d89bc996fa76bf651874
logo.bin -> 535bfd42ca7ef019d44c6ae64104633e
md1arm7-verified.img -> 5fa8d04a23b005d178a44537ff35a452
md1arm7.img -> a0453e723dc84255940d7791740d06db
md1img-verified.img -> de4a4a371c03995e2cd265179afd278f
md1img.img -> 924564348694dd8a714be10081bbce20
md3img.img -> 9a9c185e3f6234103e5949716b9962d2
MDDB_InfoCustomAppSrcP_MT6765_S00_MOLY_LR12A_R3_MP_V107_5_P4_1_ulwctg_n.EDB -> 2a22d79b2945f0f2b0d033aa21292e8e
module-info.json -> 4dc70d2f4c56de99935177ffb98c4379
MT6765_Android_scatter.txt -> bf253edfc605418fd862337cdcb488ff
PGPT -> 20bedc49348b16cdc20be09c4f32245c
preloader.bin -> 11e7416e4eb82096e11fbc5b8c794bb8
preloader.img -> 123f2104ed0579104b5b92a6592de662
preloader_dandelion.bin -> 11e7416e4eb82096e11fbc5b8c794bb8
preloader_dandelion_signed.bin -> e9a83554256f4bf7b637e949203e281c
preloader_emmc.img -> 123f2104ed0579104b5b92a6592de662
preloader_k62v1_64_bsp.bin -> e9a83554256f4bf7b637e949203e281c
preloader_ufs.img -> fa69a06727d8bec3c4ac3dfd9e764837
previous_build_config.mk -> 673bf9a01f6afa6b55a5554ed1a09176
product -> d41d8cd98f00b204e9800998ecf8427e
product.img -> d2631a5ec9fe2ef3da67acd5d4aafda3
ramdisk-debug.img -> 89dd1860aaa0623ecc3f536564721c8d
ramdisk-recovery.img -> 29709a0b5284853012428e007f5891e4
ramdisk.img -> 8af851440a4c40b1079760014ea38179
recovery -> d41d8cd98f00b204e9800998ecf8427e
recovery.id -> 865203b580b2fa74c599e8194dc3c528
recovery.img -> b18a5b61f5848adc5d52597f33b4889b
scp-verified.img -> 3338f81cc7888434d48c08ef57439b04
scp.img -> 89450a3d7cd74fa3b568a9b2cbb15035
secro.img -> 096587b863e1252d67b1b8307291db09
sig_size.txt -> 7a600b6f266737e2830a101876dd3561
spmfw-verified.img -> d8c73c204d67af9903720a5448d839bb
spmfw.img -> 66cf26550d6650dd65f5f3865948bdf2
sspm-verified.img -> 7da617202fc03a073625fa935430d921
sspm.img -> b281a508c22190047eed1af202bd5520
super.img -> 82a5b448855743dfe64de8c657cc6df2
super_empty.img -> f911a1089119bd6f6a56919deb7bb9e8
system -> d41d8cd98f00b204e9800998ecf8427e
system.img -> 3457feb31092ccc0a4d3820e82d3d5e5
TARGET.txt -> 748150f0c3bbf2fa4dcc3346e73099f5
tee-verified.img -> 6914c261e7e157c3b3408d0e1b703ed3
tee.img -> 3618d84b155dfc4ada6a7a89efefbe83
userdata.img -> 65e91188ad66358162a55b9c35627a22
vbmeta.img -> 54e5bb41ccbe9ff1d4413d1a38507c47
vbmeta_system.img -> 649fe3da8988b8192dbdbdab882509d0
vbmeta_vendor.img -> d768b480ae5ce08e2b421fc1d3bede86
vendor -> d41d8cd98f00b204e9800998ecf8427e
vendor.img -> 873d29a091ead9812e3679be24cd0744
Hi, thank you for these files. I'm experiencing something very weird and wish to know if you could help me here, I'm willing to pay for your time if needed.
I've seen dozens of tutorials and articles on how to fix NVRAM, and the first thing to do is to flash the Engineering ROM, which I have successfully done with the firmware provided, either by yourself or by other mediums.
The thing here is, using the v246 ROM I get a bootloop state, but with reversed colors (the background is white and the letters are black), and the graphics seem to be reversed as well (instead of saying Redmi, it says imdeR). I tried to ignore this and go ahead to try and get into META mode from Modem Meta program, but just as it enters META mode, it starts to reboot.
Then I tried the other version provided in this post, now the graphics are normal, but I'm still getting a bootloop and can't get the meta mode properly (it just reboots over and over).
My procedure:
1. Flash Dandelion Fasboot ROM global v12.0.18
2. Unlock bootloader
3. Bypass Auth using Mediatek Bypass Tool
4. Flash Engineering ROM in Download Only Mode though SP Flash Tool
5. Power on the device, and fall into bootloop.
I've tried every single combination that I could think of, like downgrading way back to 12.0.2 (TR), and also using the latest firmware available (12.5.x), but I'm always experiencing this issue. I don't know what else to try, thank you in advance and thank you again for your contribution here, cheers.
system32uwu said:
Hi, thank you for these files. I'm experiencing something very weird and wish to know if you could help me here, I'm willing to pay for your time if needed.
I've seen dozens of tutorials and articles on how to fix NVRAM, and the first thing to do is to flash the Engineering ROM, which I have successfully done with the firmware provided, either by yourself or by other mediums.
The thing here is, using the v246 ROM I get a bootloop state, but with reversed colors (the background is white and the letters are black), and the graphics seem to be reversed as well (instead of saying Redmi, it says imdeR). I tried to ignore this and go ahead to try and get into META mode from Modem Meta program, but just as it enters META mode, it starts to reboot.
Then I tried the other version provided in this post, now the graphics are normal, but I'm still getting a bootloop and can't get the meta mode properly (it just reboots over and over).
My procedure:
1. Flash Dandelion Fasboot ROM global v12.0.18
2. Unlock bootloader
3. Bypass Auth using Mediatek Bypass Tool
4. Flash Engineering ROM in Download Only Mode though SP Flash Tool
5. Power on the device, and fall into bootloop.
I've tried every single combination that I could think of, like downgrading way back to 12.0.2 (TR), and also using the latest firmware available (12.5.x), but I'm always experiencing this issue. I don't know what else to try, thank you in advance and thank you again for your contribution here, cheers.
Click to expand...
Click to collapse
Did you formatting data?
total n00b here, whats an engineering ROM?
Ivan.Adriazola said:
total n00b here, whats an engineering ROM?
Click to expand...
Click to collapse
A rom with less security, very useful for developers.