Related
Hi guys,
After flashing LP update 5.1 I`m in trouble with my 32GB Nexus 5
I got the error msg " E: can`t mount / cache " ( the same for system e.t.c). (before I did this I was on Custom ROM with Exposed framework installed.)
So I tryed to re-flash LP factory img (LMY47D) using fastboot command (via ADB SDK platform-tools) manually one by one according guides I found on xda.
I did it many times but the result was still the same - appears just green "android man" with rotating cube (10-15 min) and than it reboots itself and starts over again.
So I tryed to flash older factory image the same way (KTU48P) and I succeed to boot my phone but instead of 32 GB (normally available ~26GB) of my storage space there is only 12GB available now.
I thing there iscorupted partition but don`t know what to do next :crying: - how to restore it or format it ???
When I try to do that via Recovery I cant mount those partitions so I can`t format them...
When I did it via SDK - fastboot erase user data it takes veeery long time with no result
Could you pls help me how to format whole storage space ( all partitions ) and return back to stock rom with full 32GB space available ???
Thanks
Have you tried this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
There is a "32 GB phone now shows 16GB?" section.
shoeseat said:
Have you tried this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
There is a "32 GB phone now shows 16GB?" section.
Click to expand...
Click to collapse
Yes, that was one of the first think I tried.
--> I can`t clear cache & factory reset via stock recovery. Error msg -- "E: Unable to mount `/cache` "
--> Unfortunatelly fastboot erase userdata stucked ( it takes aleady 2 hours it started to erase the data and format the partition ) - do you thing it can freeze or it just can`t mount the data so it`s in loop ?
Any othe idea please , please ?
Have u tried to unmount cache partition from recovery?
shoeseat said:
Have u tried to unmount cache partition from recovery?
Click to expand...
Click to collapse
I can`t unmount it because it`s not mounted ...
When I tried to Wipe cache partition these errors appears :
PHP:
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc
(I/O error)
Did you try
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img
joegestes said:
Did you try
fastboot erase cache
fastboot flash cache cache.img
fastboot erase system
fastboot flash system system.img
Click to expand...
Click to collapse
Yes
fastboot erase/flash system was OK, but fastboot erase/flash cache got stucked
So after 2.5 hrs witnout any results I unplug the cord and start over again -- the same results
Maybe this will help
http://forum.xda-developers.com/google-nexus-5/general/howto-repairing-corrupted-data-partition-t2577447
---------- Post added at 09:04 AM ---------- Previous post was at 08:47 AM ----------
basavel said:
Hi guys,
So I tryed to flash older factory image the same way (KTU48P) and I succeed to boot my phone but instead of 32 GB (normally available ~26GB) of my storage space there is only 12GB available now.
Click to expand...
Click to collapse
Did you Wipe data/factory data reset after successful flash?
That will probably fix your 32=16 problem.
I tryed this tutorial :
http://forum.xda-developers.com/showthread.php?t=1284196
Thanks God it`s not "fried".
So I tryed this
Code:
mke2fs /dev/block/mmcblk0p27
(than reboot recovery)
... but still the same result
Than I tried to start over again from stock img flashing so :
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader
fastboot reboot-bootloader
fastboot flash radio
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
... it got stucked on erasing user data so I had to unplug the cord, restart bootloader
When I re-start the device appears "swireling" dodts (the boot animation) but no step forward, still booting....
When I tried to boot in recovery - dead android with red "!" appeared
Any other ideas what to do esle ?
Should I flash CWM or TWRP rec. instead ??
How this can be fixed ??
PLEASE !!!!:crying::crying::crying:
basavel said:
... it got stucked on erasing user data so I had to unplug the cord, restart bootloader
When I re-start the device appears "swireling" dodts (the boot animation) but no step forward, still booting....
When I tried to boot in recovery - dead android with red "!" appeared
Any other ideas what to do esle ?
Should I flash CWM or TWRP rec. instead ??
How this can be fixed ??
PLEASE !!!!:crying::crying::crying:
Click to expand...
Click to collapse
If you are getting an android sign with a red triangle it is normal for stock recovery.
You must tap volume up/down and the power button all together to get to the recovery menu.
Don't hold them in. Just tap all together at the same time and let go. It takes a couple tries but it works.
You'll then get a menu that will let you wipe data/factory reset.
use volume up/down to scroll to "wipe data/factory reset" then power button to select.
looks something like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try it and reply back the result.
joegestes said:
If you are getting an android sign with a red triangle it is normal for stock recovery.
You must tap volume up/down and the power button all together to get to the recovery menu.
Don't hold them in. Just tap all together at the same time and let go. It takes a couple tries but it works.
You'll then get a menu that will let you wipe data/factory reset.
use volume up/down to scroll to "wipe data/factory reset" then power button to select.
looks something like this
try it and reply back the result.
Click to expand...
Click to collapse
Thanks man, I manage to boot under recovery mode.
After wipe data/factory reset system shows msg:
Code:
-- Wiping data...
Formating /data ...
E: failed to mount /cache (invalid argument)
Formating /cache ...
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
Data wipe complete
So I tried to wipe cache as well and it shows up this:
Code:
-- Wiping cache...
Formating /data ...
E: failed to mount /cache (invalid argument)
Formating /cache ...
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/log
E: Can`t open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_log
E: Can`t open /cache/recovery/last_log
E: failed to mount /cache (invalid argument)
E: Can`t mount /cache/recovery/last_install
E: Can`t open /cache/recovery/last_install
E: Failed closing /dev/block/platform/msm_sdcc.1/by-name/mis
(I/O error)
E: failed to mount /cache (invalid argument)
I have no clue how to fix this can you help me pls ??
I would go to fatsboot and try to erase partitions and re flash again. see what happens.
If your data partition fails again we can try adb shell to repair your data partition.
I tried but again got stucked on erasing userdata...
I start research again and search for solution around partitions and I found this ( exactly my problem)
http://androidforums.com/threads/unable-to-mount-cache-while-doing-factory-reset.901188/
and solution for this was posted here on xda
http://forum.xda-developers.com/google-nexus-5/help/lost-cache-partition-fixed-t2949752#post58720690
this link helps me to get back to 32GB storage space (in fact ~ 26GB but doesn`t matter)
[The problem was exactlly the same missing EXT2 partition on cache partition (27)]
But error msg Can`t mount `/cache` still appears So I was not able to flash stock img LP 5.1 but I manage to flash 4.4.4 KTU84Q
It boots us and works like charm, but... ... still can`t mount/erase cache so it`s not fully solved yet but at least I can switch on/off the system now.
Can U pls help me with this mounting / partition problem ???
can it be fixed by stock OTA from KTU84Q to 5.0.1 and than the same to 5.1 ?
I had like 2 years ago similar problem with htc sensation but i fixed it by formating ir with ext2 and the reformated catch with ext4. Try to find something inside sensation forume
basavel said:
I manage to flash 4.4.4 KTU84Q
It boots us and works like charm, but... ... still can`t mount/erase cache so it`s not fully solved yet but at least I can switch on/off the system now.
Click to expand...
Click to collapse
Ok. So you are now successfully running 4.4.4 KTU84Q.
What happens now if you try flashing the stock cache.img of 4.4.4 KTU84Q:
fastboot erase cache
fastboot flash cache cache.img
Also, you could try and see what happens if you flash LP 5.01 lrx22c instead of 5.1 and do factory reset immediately after flash.
Even I manage to boot under KTU84Q the partition is still "lost" - means internal storage is ~26GB thats OK; but the error msg E: Can`t mount /cache bla bla bla still stays.
Actually I have these partitions :
Code:
C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
So after I run this
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
It formats the cache partition (p27) to ext2 but after install of stock KTU84Q it`s back - UNFORMATED with no possibility to mount
What am I doing wrong ? :crying:
basavel said:
Even I manage to boot under KTU84Q the partition is still "lost" - means internal storage is ~26GB thats OK; but the error msg E: Can`t mount /cache bla bla bla still stays.
Actually I have these partitions :
Code:
C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
So after I run this
1.1) adb shell
1.2) mkfs.ext2 /dev/block/mmcblk0p27
1.3) exit
It formats the cache partition (p27) to ext2 but after install of stock KTU84Q it`s back - UNFORMATED with no possibility to mount
What am I doing wrong ? :crying:
Click to expand...
Click to collapse
My guess is it needs to be formatted to ext4 not ext2.
KTU84Q probably can not recognize ext2.
Heres what mine looks like.
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
Again it looks like cache should be formatted ext4
Compare line 22 and line 27.
My line22 fsc is not formatted. Yours is formatted ext2
My line 27 cache is formatted ext4. Yours is not.
That is the problem.
Here is the list of partition locations
[/code]
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 28551146 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ #
[/code]
Finally I got to the stage where the ext2 partition stays ( do not disappear) after next flash.
How I did it - format the partition to ext2 than manually flash KTU84Q
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Than let the system update itself to 5.0.1 LRX22C
Now the erroe msg is gone (E: Can`t mount /cache) but agree those messed up partitions must be fixed.
The question is how ?
- should I install TWRP rec. and let it fix it when the cache partition is mountable now ?
- or should it fix it via ADB SHELL ? (and how ? mkfs.ext4 /dev/block/mmcblk0p27 ? )
- and how to erase line 22 in order to have in unformated ?
--- > or should I try to flash custom ROM over this ? - I don`t think so
Could you pls help with this ?
!!!THANKS!!!
basavel said:
Finally I got to the stage where the ext2 partition stays ( do not disappear) after next flash.
How I did it - format the partition to ext2 than manually flash KTU84Q
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Than let the system update itself to 5.0.1 LRX22C
Now the erroe msg is gone (E: Can`t mount /cache) but agree those messed up partitions must be fixed.
The question is how ?
- should I install TWRP rec. and let it fix it when the cache partition is mountable now ?
- or should it fix it via ADB SHELL ? (and how ? mkfs.ext4 /dev/block/mmcblk0p27 ? )
- and how to erase line 22 in order to have in unformated ?
--- > or should I try to flash custom ROM over this ? - I don`t think so
Could you pls help with this ?
!!!THANKS!!!
Click to expand...
Click to collapse
If it was me, the first thing I would do is flash TWRP. Second, make a full backup using TWRP backup function, then save/transfer a copy of that backup to my PC.
That way, moving forward id' have an easy way to restore the device back to it's presently functioning Lollypop state.
After that I might try the ADB shell command from TWRP you mentioned mkfs.ext4 /dev/block/mmcblk0p27 and see if that manages to re formats cache to ext4.
I've never tried this, and don't have much experience with parted, so I cant say if it will work. So proceed at your own risk.
As far as fsc( I think it means file save clean)partition goes. I honestly don't know but Ill try to find out.
Meanwhile, hopefully someone else with some mad partition skillz will chime in.:laugh:
TWRP coruupted all I did before - it tryed to repair broken partitions with f2fs but they are gone now
So I am 2 steps back
Code:
C:\android-sdk-windows\platform-tools>adb shell parted -s /dev/block/mmcblk0 pri
nt
Model: MMC SEM32G (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB ext2 fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
I can create only ext2 partition thanks to - mkfs.ext2 /dev/block/mmcblk0p27
The same code string with ext4 i.o ext2 is not working
MSG:
~ # mkfs.ext4 /dev/block/mmcblk0p27
mkfs.ext4 /dev/block/mmcblk0p27
/sbin/sh: mkfs.ext4: not found
Nobody helps me ??, This community for lg g flex 2 sucks!!!
Anyways, I have made some progress trying to revive my lg g flex 2 h959 from qualcomm qload 9008 mode,
After extensive research and staying up nights, I have finally compiled a MPGR8994.hex programmer for this device, I have found the prog_emmc_firehose_8994_lite.mbn and I am currently trying to compile the 8994msimage.mbn file. After that I will be able to use the emmcdownload from qpst software pack to restore my phone partition table and set the phone into qualcomm qload 9006 mode.
I have problem compiling the 8994msimage.mbn; This image is basically contains the fastboot bootloader. Now if anyone here lends me the fastboot boot loader of their device it would be nice.
Follow this and make one for me, because I don't have the parts necessary, you can pull those parts using adb commands.
Okey here is the full partition table of All Lg G Flex 2 variants, and they all share this same, it is extracted from the PrimaryGPT.bin and it follows :
Code:
Starting to parse GPT
Size of GPT file is 524288
Parsing GPT
-- GPT STARTs--
name: modem
startLBA: 32768
endLBA: 196607
size: 0x0000000005000000 bytes
attributes: 0x0
name: pmic
startLBA: 196608
endLBA: 197631
size: 0x0000000000080000 bytes
attributes: 0x0
name: sbl1
startLBA: 197632
endLBA: 199679
size: 0x0000000000100000 bytes
attributes: 0x0
name: tz
startLBA: 199680
endLBA: 201727
size: 0x0000000000100000 bytes
attributes: 0x0
name: sdi
startLBA: 201728
endLBA: 202751
size: 0x0000000000080000 bytes
attributes: 0x0
name: hyp
startLBA: 202752
endLBA: 203775
size: 0x0000000000080000 bytes
attributes: 0x0
name: rpm
startLBA: 203776
endLBA: 204799
size: 0x0000000000080000 bytes
attributes: 0x0
name: aboot
startLBA: 204800
endLBA: 208895
size: 0x0000000000200000 bytes
attributes: 0x0
name: sbl1bak
startLBA: 208896
endLBA: 210943
size: 0x0000000000100000 bytes
attributes: 0x0
name: pmicbak
startLBA: 210944
endLBA: 211967
size: 0x0000000000080000 bytes
attributes: 0x0
name: tzbak
startLBA: 211968
endLBA: 214015
size: 0x0000000000100000 bytes
attributes: 0x0
name: hypbak
startLBA: 214016
endLBA: 215039
size: 0x0000000000080000 bytes
attributes: 0x0
name: rpmbak
startLBA: 215040
endLBA: 216063
size: 0x0000000000080000 bytes
attributes: 0x0
name: abootbak
startLBA: 216064
endLBA: 220159
size: 0x0000000000200000 bytes
attributes: 0x0
name: sdibak
startLBA: 220160
endLBA: 221183
size: 0x0000000000080000 bytes
attributes: 0x0
name: limits
startLBA: 221184
endLBA: 222207
size: 0x0000000000080000 bytes
attributes: 0x0
name: devinfo
startLBA: 222208
endLBA: 223231
size: 0x0000000000080000 bytes
attributes: 0x0
name: apdp
startLBA: 223232
endLBA: 224255
size: 0x0000000000080000 bytes
attributes: 0x0
name: msadp
startLBA: 224256
endLBA: 225279
size: 0x0000000000080000 bytes
attributes: 0x0
name: dpo
startLBA: 225280
endLBA: 226303
size: 0x0000000000080000 bytes
attributes: 0x0
name: misc
startLBA: 229376
endLBA: 262143
size: 0x0000000001000000 bytes
attributes: 0x0
name: persist
startLBA: 262144
endLBA: 327679
size: 0x0000000002000000 bytes
attributes: 0x0
name: modemst1
startLBA: 327680
endLBA: 330751
size: 0x0000000000180000 bytes
attributes: 0x0
name: modemst2
startLBA: 330752
endLBA: 333823
size: 0x0000000000180000 bytes
attributes: 0x0
name: fsg
startLBA: 333824
endLBA: 336895
size: 0x0000000000180000 bytes
attributes: 0x0
name: fsc
startLBA: 336896
endLBA: 337919
size: 0x0000000000080000 bytes
attributes: 0x0
name: ssd
startLBA: 337920
endLBA: 338943
size: 0x0000000000080000 bytes
attributes: 0x0
name: keystore
startLBA: 338944
endLBA: 339967
size: 0x0000000000080000 bytes
attributes: 0x0
name: DDR
startLBA: 339968
endLBA: 344063
size: 0x0000000000200000 bytes
attributes: 0x0
name: sec
startLBA: 344064
endLBA: 345087
size: 0x0000000000080000 bytes
attributes: 0x0
name: encrypt
startLBA: 345088
endLBA: 346111
size: 0x0000000000080000 bytes
attributes: 0x0
name: eksst
startLBA: 346112
endLBA: 347135
size: 0x0000000000080000 bytes
attributes: 0x0
name: rct
startLBA: 347136
endLBA: 347151
size: 0x0000000000002000 bytes
attributes: 0x0
name: persistent
startLBA: 347152
endLBA: 355343
size: 0x0000000000400000 bytes
attributes: 0x0
name: laf
startLBA: 360448
endLBA: 458751
size: 0x0000000003000000 bytes
attributes: 0x0
name: boot
startLBA: 458752
endLBA: 540671
size: 0x0000000002800000 bytes
attributes: 0x0
name: recovery
startLBA: 540672
endLBA: 622591
size: 0x0000000002800000 bytes
attributes: 0x0
name: drm
startLBA: 622592
endLBA: 638975
size: 0x0000000000800000 bytes
attributes: 0x0
name: sns
startLBA: 638976
endLBA: 655359
size: 0x0000000000800000 bytes
attributes: 0x0
name: mpt
startLBA: 655360
endLBA: 720895
size: 0x0000000002000000 bytes
attributes: 0x0
name: factory
startLBA: 720896
endLBA: 815103
size: 0x0000000002e00000 bytes
attributes: 0x0
name: fota
startLBA: 815104
endLBA: 835583
size: 0x0000000000a00000 bytes
attributes: 0x0
name: raw_resources
startLBA: 835584
endLBA: 843775
size: 0x0000000000400000 bytes
attributes: 0x0
name: raw_resourcesbak
startLBA: 843776
endLBA: 851967
size: 0x0000000000400000 bytes
attributes: 0x0
name: system
startLBA: 851968
endLBA: 8191999
size: 0x00000000e0000000 bytes
attributes: 0x0
name: cust
startLBA: 8192000
endLBA: 8716287
size: 0x0000000010000000 bytes
attributes: 0x0
name: cache
startLBA: 8716288
endLBA: 11239423
size: 0x000000004d000000 bytes
attributes: 0x0
name: userdata
startLBA: 11239424
endLBA: 60981247
size: 0x00000005ee000000 bytes
attributes: 0x0
name: grow
startLBA: 60981248
endLBA: 61071326
size: 0x0000000002bfbe00 bytes
attributes: 0x0
-- GPT ENDs --
Exited with success
Now Please someone who know, tell me which is the fastboot partition and someone exract it for me using adb and the dd command, It doesn't matter which variant for now.
This guide below is only general and I need the appropriate parts for 8994msimage.mbn
HTML:
How to generate the 8660_msimage.mbn
8660_msimage.mbn is released in SW by default, actually, it includes the all the boot images and partition table there. MPRG8660.hex will download this image and reset to mass-storage mode. If customers have different HW settings, such as GPIO/DDR, the default 8660_msimage.mbn may not work for them, so customers need build their own 8660_msimage.mbn by themselves with following ways.
1. Have the QPST 2.7.366 or higher version installed.
2. Make a local folder, copy sbl1/sbl2/sbl3/rpm/tz images to this folder.
3. copy the emmcswdownload.exe from C:\Program Files\Qualcomm\QPST\bin to this folder.
4. Prepare the partition_boot.xml as below and copy the partition_boot.xml to the same folder as above.
<?xml version="1.0"?>
<image>
<physical_partition number="0">
<primary order="1" type="4d" bootable="true" label="SBL1" size="1000" readonly="false">
<file name="sbl1.mbn" offset="0"/>
</primary>
<primary order="2" type="51" bootable="false" label="SBL2" size="3000" readonly="false">
<file name="sbl2.mbn" offset="0"/>
</primary>
<primary order="3" type="45" bootable="false" label="SBL3" size="1500" readonly="false">
<file name="sbl3.mbn" offset="0"/>
</primary>
<primary order="4" type="5" bootable="false" label="EXT" size="1000000">
<extended order="1" type="47" label="RPM" size="1000" readonly="false">
<file name="rpm.mbn" offset="0"/>
</extended>
<extended order="2" type="46" label="TZ" size="1000" readonly="false">
<file name="tz.mbn" offset="0"/>
</extended>
</primary>
</physical_partition>
</image>
5. Run the emmcswdownload.exe tool to create OEM boot image with a command below.
emmcswdownload.exe -f 8660_msimage.mbn -x partition_boot.xml -s 1G -g 4M
6. The 8660_msimage.mbn will be generated in the folder.
1. In this mode, you can't flash, you can't to do anything, only the LG Service can repair your phone
2. Currently no hex programmer for msm8994 to repair with QPST at home.
3. One more method is JTAG, (require soldering knowledge, soldering station, flux, wire etc...) need to find, the right emmc pinouts on the pcb, but if the pinouts not in the pcb, need to desolder emmc and flash directly...
stars2 said:
1. In this mode, you can't flash, you can't to do anything, only the LG Service can repair your phone
2. Currently no hex programmer for msm8994 to repair with QPST at home.
3. One more method is JTAG, (require soldering knowledge, soldering station, flux, wire etc...) need to find, the right emmc pinouts on the pcb, but if the pinouts not in the pcb, need to desolder emmc and flash directly...
Click to expand...
Click to collapse
Hey mate, Thanks for the reply. My phone is model H959 and that is a Hongkong version, But I live in UK and bought the phone from a UK ebay seller, and UK LG service is not liable for my phone model, and I cant get a service from HongKong either. I'm screwed.
I've been trying to use the Lg flash tool 2015 which has board dl mode, I tried it and it does see my phone in qualcomm 9008 mode and establishes connection but when it wants to download the stuff it gets failed. I extracted some bin files from the kdz rom.
I am also able to see the phone from QPST tools but the software download fails to initiate the downloader. If you have the same model, using qpst you can build the mbn files nessesary for me to restore mine. I know you've got the knowledge, may be please try.
Well l have the sprint version the ls996 and mine shows qsusb_bulk is the issues the same? Sorry lm a noon
Akihiromeep said:
... the issues the same? ...
Click to expand...
Click to collapse
Yes, same problem
If you install the driver, you get QHS-USB QDLoader 9008 mode, but currently no fix, only LG Service can help...
32 bit
https://www.androidfilehost.com/?fid=24269982087002410
64 bit
https://www.androidfilehost.com/?fid=24269982087002409
if you can flash any rom, phone boots with no problem, I flashed a lot of kdz from diferent versions over my h950.
you may lost your imei, so after all, make a backup from qpst. so when you boots your phone, you can restore.
which partitions do you need?
In which format?
I can try to extract from mine. is an h950 with h955ar firmware, mixed with h950pr... H959 kdz boots with no signal in my phone... so I think h950pr partitions must work in your phone...
pelelademadera said:
if you can flash any rom, phone boots with no problem, I flashed a lot of kdz from diferent versions over my h950.
you may lost your imei, so after all, make a backup from qpst. so when you boots your phone, you can restore.
which partitions do you need?
In which format?
I can try to extract from mine. is an h950 with h955ar firmware, mixed with h950pr... H959 kdz boots with no signal in my phone... so I think h950pr partitions must work in your phone...
Click to expand...
Click to collapse
I think I have already lost my IMEI as my phone is in qualcomm 9008 mode, that is to say there is no partition table on the phone and emmc is blank. That happened when I was flashing the stock rom and the flash tool on my pc crashed. That said if you read the first thread I have said I need the part which is necessary enough to make the phone boot into download mode, lg logo, fastboot, laf(I already have this one). I 'm not a expert and dont know what are they called in terms as in the full partition table I have provided. So I need help if you know them. SO that I can compile the 8994msimage.mbn
Masteryates said:
How does that work? Does it allow you to have the best of both worlds? :angel:
Click to expand...
Click to collapse
So so, problem is imei and baseband, the rest, all roms works in h950, so all roms works in all flex2, you have to keep imei!!!!
Afshin44 said:
I think I have already lost my IMEI as my phone is in qualcomm 9008 mode, that is to say there is no partition table on the phone and emmc is blank. That happened when I was flashing the stock rom and the flash tool on my pc crashed. That said if you read the first thread I have said I need the part which is necessary enough to make the phone boot into download mode, lg logo, fastboot, laf(I already have this one). I 'm not a expert and dont know what are they called in terms as in the full partition table I have provided. So I need help if you know them. SO that I can compile the 8994msimage.mbn
Click to expand...
Click to collapse
You probably not, cause no kdz have modemst1 and modemst2 partitions. If you dobt flash another kdz that overwright that partitions, imei are safe.
Modem are the baseband.
So which partitions you need?
Qpst see the phone as a phone?
Laf is download mode, if you dont have that, you have fastboot that dont work in flex 2, all commands are invalid
Enviado desde mi LG-H955 mediante Tapatalk
anyone managed to.fixed???
moonmoon8 said:
anyone managed to.fixed???
Click to expand...
Click to collapse
I don't think any of my work is going to work unless we have the proper files and the proper software. I have tried many different ways but phone does not respond to any. Phone is obviously seen by qpst by none of its apps work with this chip. The qpst is old and we need new version. I have given up. Only way is JtagBox like Octopus Box which does support lg g flex 2.
I'm trying to fix one that I have kept in the closet, this qualcomm 9008, I did everything I could, even with BoarDiag but does not support it, I went to a page that is android1brick called and told me that it can be done only with direct EMMC but no boxes, and I do not guarantee unfortunately, I'm just hoping to take out a hope , we have to create a new BoarDiag o another program for fix this dificult mobile
Adriantech said:
I'm trying to fix one that I have kept in the closet, this qualcomm 9008, I did everything I could, even with BoarDiag but does not support it, I went to a page that is android1brick called and told me that it can be done only with direct EMMC but no boxes, and I do not guarantee unfortunately, I'm just hoping to take out a hope , we have to create a new BoarDiag o another program for fix this dificult mobile
Click to expand...
Click to collapse
I feel you , but I don't know how the softwares work and to flash directly we need the pin outs and we have no idea of where the pin outs of the emmc is either.
Exactly , we have to do a program or a way to fix this phone , maybe easyjtag can fixed or riff box
LG G Flex2 Sprint in Volcano Red (LS996) no enciende después de flash.
Such friends, I am new to this great forum.
I have a Sprint LG G Flex2 in Volcano Red (LS996) which wanted to change the firmware. Enter a support page and found this firm:
ARGENTINA
1 TFS / TELEFONICA (ARGENTINA) V15A LGH955AR 13
You install the "LG Flash Tool 2014", and the process is 100% complete smoothly. But when I went to see the phone does not turn on.
He did not catch more or disconnecting the battery.
When I connect it to the PC it detects it as QHSUSB_BULK me and nothing else. No Dowland nothing enters mode.
Please help!!!! Hopefully we can find a solution.
And probe using interfaces because not assign me any port when I connect it to use the TOT or DDL
I have been recently been looking for a way to unbrick my G Flex 2. I made a mistake and flashed Zv5. I keep seeing there might be a way to recover the phone if we had a zv6 or above tot. i have found what seems to be vv8 tot on chinese website. would this be any help?
http://www.xuexiaowuwo.com/forum.php?mod=viewthread&tid=653
@astaccz is no solution for now
Adriantech said:
@astaccz is no solution for now
Click to expand...
Click to collapse
aww. i literally bought a new g flex 2 from the sprint store for 250 and bricked it in 2 days. smh. i had to order a logic board online from ifixit. i updated it to zv9 and rooted. now i know not to go back to zv5.
the logic board i ordered was revision 2 and the one coming from the sprint store was revision 4. both were lag free when updated to 5.1.1 but the revision 2 board is noticeably just a pinch slower.
gonna send board for boot repair to a guy states away
astaccz said:
aww. i literally bought a new g flex 2 from the sprint store for 250 and bricked it in 2 days. smh. i had to order a logic board online from ifixit. i updated it to zv9 and rooted. now i know not to go back to zv5.
the logic board i ordered was revision 2 and the one coming from the sprint store was revision 4. both were lag free when updated to 5.1.1 but the revision 2 board is noticeably just a pinch slower.
gonna send board for boot repair to a guy states away
Click to expand...
Click to collapse
Do have to wait bro :crying:
I successfully can fix soft brick (bootloop) only for LS996 for now. I spent hours fiddling making a custom tot that flashes ZV8. Already rooted after tot flash.
If interested message me on [email protected] Carln2ubb
astaccz said:
I successfully can fix soft brick (bootloop) only for LS996 for now. I spent hours fiddling making a custom tot that flashes ZV8. Already rooted after tot flash.
If interested message me on [email protected] Carln2ubb
Click to expand...
Click to collapse
That's great! You should make a tutorial and post it. A lot of people would be grateful for that.
Hello guys!
Recently I've acted like an idiot and now I am asking for help.
I have a new smartphone - Gionee gn8001 (Marathon M5 Plus). It is a new model, I've bought it in China. I rooted it via Kingroot. But, as every phone in China this one does not have gapps integrated into it's ROM. That's why I wanted to install any custom recovery into it. I have not found a firmware or recovery scecifically for this phone so I decided to try and flash recovery from another model using the same CPU (MTK6753). I've downloaded recovery from Elephone P8000, which is very close to mine. Then I've flashed it into my phone using MTK MobileUncle Tool. After that I cannot enter into the recovery at all. The phone is still working but recovery just reboots and that's all.
I have several questions...
1)How SPFlash tool should work when I cannot extract a battery from the phone? The phone starts then I connect it to USB, SPFlash tool cannot work. This is why i have not extracted my own recovery from it. To avoid this in future, I want to know how this should be done?
2)Any suggestions except "wait till someone will make a recovery for this phone model"?
3)After I rooted the phone, it's OTA upgrade program recommended a full restore. I've downloaded the file, it's 1.5Gb of data, I think it is a full OS image. And it looks like one. BUT it's scatter file is not a full one, it's very brief:
preloader 0x0
pgpt 0x0
proinfo 0x80000
nvram 0x380000
protect1 0x880000
protect2 0x1280000
lk 0x1c80000
para 0x1d00000
boot 0x1d80000
recovery 0x2d80000
logo 0x3d80000
expdb 0x4580000
seccfg 0x4f80000
oemkeystore 0x5000000
secro 0x5200000
keystore 0x5800000
tee1 0x6000000
tee2 0x6500000
frp 0x6a00000
nvdata 0x6b00000
metadata 0x8b00000
system 0xb000000
cache 0xcb000000
userdata 0xe4000000
flashinfo 0xFFFF0084
sgpt 0xFFFF0004
I understand that this is an image to be installed from stock recovery. The question is - can I somehow tell is there a stock recovery itself in this image? And if it is there - can I somehow extract it and flash it into my phone to return at least stock recovery back?
Thanks for answers!
Hello to all
I am fighting since 2 weeks with a GT-P5100 that seems to be in read only and in boot loop (it shows the CM9 boot animation and then reboot ...). This after a simple update of some apps that seems to have corrupted the sdcard inside ...
I have tried to clear the cache and the user data via the recovery mode, but nothing happen ... (boot in recovery, choose to wipe data/factory reset and wipe cache partition)
To make a long story short:
I am able to boot in recovery and enter as root via adb. Whatever change I do in the filesystem it seems to be done, but when I unmount/mount the fs or reboot I find the same initial situation !
So for example:
a) enter as root, mount /data, delete data content via rm -rf /data/* ... then if I do ls -la /data I see the device empty ... if I unount /data and then mount /data .. all the files are there !!!! :-O
b) enter as root and activate parted ... remove the data partition (for me n. 10) and quit. Run parted again and the partition is still there :-O
c) enter as root and touch a file in any filesystem ... when I ls after I can see the file ... as soon as I reboot, not such file is there
I have tried with ODIN and HEIMDAL (booting in download mode or fastboot mode) also to flash new system.img from stock roms and different recovery.img (currently I have CWM-based recovery v6.0.1.0)... no way. system.img flash does not work, while recovery.img flash say ok, but when I reboot in recovery mode still find always the same partition :-O
It seems somehow that the overall internal disk is in read only and - I do not understand why - when I do changes they are recorded locally, but when I reboot the fs really does not store anything.
BTW, this is my partition table
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 15.2GB 12.9GB ext4 DATAFS
11 15.2GB 15.8GB 537MB ext4 HIDDEN
Any idea ?
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.