FORUMS

[Guide] Root your Elephone U Pro Manual

10,488 posts
Thanks Meter: 14,795
 
By skeleton1911, Senior Member on 6th April 2018, 12:10 AM
Post Reply Email Thread
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 :P
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:
#/Disclaimer

* I am not responsible for anything/bricked devices, dead SD cards,
* thermonuclear war, or exploding cars.
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
The Following 3 Users Say Thank You to skeleton1911 For This Useful Post: [ View ] Gift skeleton1911 Ad-Free
6th April 2018, 12:29 AM |#2  
skeleton1911's Avatar
OP Senior Member
Flag münster
Thanks Meter: 14,795
 
Donate to Me
More
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:
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
The Following 4 Users Say Thank You to skeleton1911 For This Useful Post: [ View ] Gift skeleton1911 Ad-Free
6th April 2018, 12:37 AM |#3  
Maherabed1986's Avatar
Senior Member
Flag Jeddah
Thanks Meter: 189
 
Donate to Me
More
Great job buddy very clear explaining
Wish you the best as always
The Following 3 Users Say Thank You to Maherabed1986 For This Useful Post: [ View ] Gift Maherabed1986 Ad-Free
6th April 2018, 09:27 AM |#4  
Senior Member
Thanks Meter: 207
 
Donate to Me
More
Quote:
Originally Posted by skeleton1911

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 :P
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:
#/Disclaimer

* I am not responsible for anything/bricked devices, dead SD cards,
* thermonuclear war, or exploding cars.
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.



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 ?
6th April 2018, 09:29 AM |#5  
skeleton1911's Avatar
OP Senior Member
Flag münster
Thanks Meter: 14,795
 
Donate to Me
More
Quote:
Originally Posted by Laptapper

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 ?

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
6th April 2018, 09:36 AM |#6  
Senior Member
Thanks Meter: 207
 
Donate to Me
More
No I didn't see direct install

---------- Post added at 10:36 AM ---------- Previous post was at 10:32 AM ----------

Quote:
Originally Posted by skeleton1911

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.
6th April 2018, 09:42 AM |#7  
skeleton1911's Avatar
OP Senior Member
Flag münster
Thanks Meter: 14,795
 
Donate to Me
More
Quote:
Originally Posted by Laptapper

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.

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
6th April 2018, 09:49 AM |#8  
mzsquared's Avatar
Senior Member
Flag CT
Thanks Meter: 184
 
More
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/1RYP...ew?usp=sharing
The Following User Says Thank You to mzsquared For This Useful Post: [ View ] Gift mzsquared Ad-Free
6th April 2018, 09:55 AM |#9  
skeleton1911's Avatar
OP Senior Member
Flag münster
Thanks Meter: 14,795
 
Donate to Me
More
Quote:
Originally Posted by mzsquared

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/1RYP...ew?usp=sharing

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....
6th April 2018, 09:58 AM |#10  
mzsquared's Avatar
Senior Member
Flag CT
Thanks Meter: 184
 
More
Quote:
Originally Posted by skeleton1911

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

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.
6th April 2018, 10:01 AM |#11  
skeleton1911's Avatar
OP Senior Member
Flag münster
Thanks Meter: 14,795
 
Donate to Me
More
Quote:
Originally Posted by mzsquared

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.

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
Post Reply Subscribe to Thread

Tags
elephone-u-pro

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes