[re-partition]Hard-Bricked FRD-L09 ! i need backup of gpt.img - Honor 8 Questions & Answers

Hello everyone
ive bricked my phone while trying to update to emui 8
first of all its was stuck at 99% ercovery update for hours, so ive shutdown it , so its stuck at honor logo with no erecovery no recovery , only fastboot was accessible(but mine was having a locked bootloader and locked frp so fastboot not going to help me at all)
so ive google for solutions and i've managed to get the phone enter to EDL mode by shorting the two pins on the MB (after opening the phone case)
when connecting the phone on my linux machine using usb it got reconeized as a serial usb,
then after googling again i found that i can flash the board software while the phone is on EDL mode without unlocking the bootloader
so i ve tried to search for the software board for my phone but unlucky all i got is password protected firmwares (i cant afford to buy something online or pay for dc-unlocker )
after lot of searching on the internet i found a similiar board firmware that belong to the huawei MATE 8 that got the same chipset and cpu (kirin 950) so i tried to flash it using EDL mode (load fastboot.img to ram then flash every image one by one using fastboot flash partiton)
everything on the flashing process worked flashed all the partition on the phone with success
but after rebooting the phone its no longer powering on
when connecting to compter its reconeized as a adb device and it is detected as a fastboot device when taping command fastboot devices.
so i ve tried to flash partitions from the official update package but unlucky the update package doesnt contain the GPT.img file. it is the necessary file for repartition the emmc ( because i ve flashed the gpt.img from the mate 8 and its no longer accepting images from honor 8 package. only mate 8 images that are successfully flashing through fastboot)
so please if someone can provide me with the software board of the honor 8 FRD-l09 or the file gpt.img of the honor 8 frd-l09 or do a backup of it . i will be appreciated
asking for help if there is another methode for unbricking the phone (obviously my only option is paying for dc-unlocker but i cant afford that ) and thank you all

hello, i can send you the gpt.img, but please explain how can i get it for you

kinkat1995 said:
hello, i can send you the gpt.img, but please explain how can i get it for you
Click to expand...
Click to collapse
thanks for reply.
i dont know exactly the name of partitions but there is a guide provided by member @majdinj https://forum.xda-developers.com/showthread.php?t=2450045
Pr-requirement:
-root
-adb
-sd card where backup will be saved
-es file explorer or any root explorer
first explore this directory using a root explorer /dev/block/platform/
then search every folder in the "/dev/block/platform" directory that contain a folder named "by-name"
lets assume that your find the folder xxx that contain the "by-name" folder
-run the following commands using adb terminal
=> adb shell
=> su
=> ls -al /dev/block/platform/xxx/by-name
it will give you info about the dev block names and their familiar names
search for the name gpt and check its dev block name it must be something like this
gpt -> /dev/block/mcmcblkxxx
then final part make a backup of it using this command
=> dd if=/dev/block/mmcblkxxx of=/sdcard/gpt.img
(replace mmcblkxxx with the dev block name that matched the gpt partiton)

ay.amouch said:
thanks for reply.
i dont know exactly the name of partitions but there is a guide provided by member @majdinj https://forum.xda-developers.com/showthread.php?t=2450045
Pr-requirement:
-root
-adb
-sd card where backup will be saved
-es file explorer or any root explorer
first explore this directory using a root explorer /dev/block/platform/
then search every folder in the "/dev/block/platform" directory that contain a folder named "by-name"
lets assume that your find the folder xxx that contain the "by-name" folder
-run the following commands using adb terminal
=> adb shell
=> su
=> ls -al /dev/block/platform/xxx/by-name
it will give you info about the dev block names and their familiar names
search for the name gpt and check its dev block name it must be something like this
gpt -> /dev/block/mcmcblkxxx
then final part make a backup of it using this command
=> dd if=/dev/block/mmcblkxxx of=/sdcard/gpt.img
(replace mmcblkxxx with the dev block name that matched the gpt partiton)
Click to expand...
Click to collapse
i listed the partitions but there are no with gpt name, see the output:
Code:
HWFRD:/ # ls -al /dev/block/platform/hi_mci.0/by-name
total 0
drwxr-xr-x 2 root root 1200 2020-05-21 19:36 .
drwxr-xr-x 4 root root 1320 2020-05-21 19:36 ..
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodem -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvm -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvmbkp -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 bootfail_info -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cust -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dfx -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dto -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dts -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_kernel -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_ramdisk -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vbmeta -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vendor -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 fw_hifi -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest0 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest1 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest2 -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 kernel -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dsp -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dtb -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 odm -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 patch -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 product -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 ramdisk -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_ramdisk -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vbmeta -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vendor -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved3 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 rrecord -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 sensorhub -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 splash -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 system -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 teeos -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 trustfirmware -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 userdata -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vendor -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 version -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl_backup -> /dev/block/mmcblk0p2

kinkat1995 said:
i listed the partitions but there are no with gpt name, see the output:
Code:
HWFRD:/ # ls -al /dev/block/platform/hi_mci.0/by-name
total 0
drwxr-xr-x 2 root root 1200 2020-05-21 19:36 .
drwxr-xr-x 4 root root 1320 2020-05-21 19:36 ..
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodem -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvm -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 3rdmodemnvmbkp -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 bootfail_info -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 cust -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dfx -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dto -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 dts -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_kernel -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_ramdisk -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vbmeta -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 erecovery_vendor -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 fw_hifi -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest0 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest1 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 hisitest2 -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 kernel -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dsp -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_dtb -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 odm -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 patch -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 product -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 ramdisk -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_ramdisk -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vbmeta -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 recovery_vendor -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved1 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved2 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 reserved3 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 rrecord -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 sensorhub -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 splash -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 system -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 teeos -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 trustfirmware -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 userdata -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 vendor -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2020-05-21 19:36 version -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2020-05-21 19:36 vrl_backup -> /dev/block/mmcblk0p2
Click to expand...
Click to collapse
thanks for help.
i ve just checked your reply on my post with the partitions info, as you said there is no gpt partition on it.
i believe that partition is special and it is only provided with a full paid repair firmware because it is not a real partition, it is just a file named gpt.img contain info about every partition name and size and their infos , it is also called ptable.img on some other huawei honor devices
i will try one more time to fix before dump it
her is my email [email protected]
send me these partitions : vrl - vrl_backup - fw_lpm3
you can backup them using following commands and make sure you have inserted an sd card on your device:
dd if=/dev/block/mmcblk0p3 of=/sdcard/fw_lpm3.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/vrl_backup.img
dd if=/dev/block/mmcblk0p1 of=/sdcard/vrl.img

Here are the files

kinkat1995 said:
Here are the files
Click to expand...
Click to collapse
thanks

ay.amouch said:
thanks
Click to expand...
Click to collapse
Hi my friend, I have the same issue, did u find any solution to this problem. My phone got bootloop, no erecovery no recovery and no dload, just fastboot working. Tried to flash boot and recovery stock images from fastboot but got error this command is not allowed. pls help me with this.

Related

[Q] N915F mounting points

Does anyone has by any chance the mount points table for the N915F?
Thank you.
Instruction
starbucks2010 said:
Does anyone has by any chance the mount points table for the N915F?
Thank you.
Click to expand...
Click to collapse
If you can instruct me - I'll do it.
I tried with (adb shell) cat /proc/partitions and cat /proc/mounts but I don't know which partition is which mmcblk.
I checked also in fstab file but the mount point information is missing from it.
PS. Finaly I found out. If anyone need it:
lrwxrwxrwx root root 2014-01-10 11:07 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-10 11:07 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-10 11:07 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-10 11:07 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-01-10 11:07 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-10 11:07 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-10 11:07 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-10 11:07 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-10 11:07 hidden -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-10 11:07 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-10 11:07 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-10 11:07 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-10 11:07 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-10 11:07 param -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-10 11:07 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-10 11:07 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-10 11:07 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-10 11:07 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-10 11:07 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-10 11:07 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-10 11:07 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-10 11:07 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-10 11:07 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-10 11:07 userdata -> /dev/block/mmcblk0p27
Good luck.
does anyone knows which mount point is for "data": mmcblk0p26 (hidden) or mmcblk0p27 (userdata)?
thank you
Here's some info from the N915T
Code:
lrwxrwxrwx 1 root root 20 Jan 3 2014 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 3 2014 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 3 2014 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 3 2014 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 Jan 3 2014 dbi -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 3 2014 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jan 3 2014 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 3 2014 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 3 2014 mdm1m9kefsc -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 3 2014 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 3 2014 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 3 2014 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 3 2014 param -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 3 2014 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jan 3 2014 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 3 2014 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Jan 3 2014 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Jan 3 2014 sbl1bak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 3 2014 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 3 2014 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 3 2014 tz -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 3 2014 userdata -> /dev/block/mmcblk0p26

[PE-UL00] Honor 6 PLUS - Urgent partition layout question

Hello,
I messed up my Honor 6 PLUS (PE-UL00) SENSORHUB partition - possibly overwriting it with an image other than the SENSORHUB.img (extracted from UPDATE.APP). Can someone with a stock Lollipop or MM please post their partition layout which can be obtained using the following command in ADB SHELL:
ls -l /dev/block/platform/hi_mci.0/by-name
My current layout (with corrupted SENSORHUB partition - phone does not boot) is as follows:
lrwxrwxrwx 1 root root 21 Nov 17 10:19 3rdmodem -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Nov 17 10:19 3rdmodemnvm -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Nov 17 10:19 3rdmodemnvmbkp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Nov 17 10:19 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Nov 17 10:19 cache -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Nov 17 10:19 cust -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Nov 17 10:19 dfx -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Nov 17 10:19 dts -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Nov 17 10:19 fastboot -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Nov 17 10:19 fw_hifi -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Nov 17 10:19 fw_lpm3 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Nov 17 10:19 hibench -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Nov 17 10:19 hisitest0 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Nov 17 10:19 hisitest1 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Nov 17 10:19 misc -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modem -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modem_dsp -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modem_om -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_backup -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Nov 17 10:19 modemnvm_factory -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_img -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Nov 17 10:19 modemnvm_update -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 Nov 17 10:19 nvme -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Nov 17 10:19 oeminfo -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Nov 17 10:19 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Nov 17 10:19 recovery2 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Nov 17 10:19 recovery3 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 20 Nov 17 10:19 reserved1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Nov 17 10:19 reserved2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Nov 17 10:19 secure_storage -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Nov 17 10:19 sensorhub -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Nov 17 10:19 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Nov 17 10:19 splash2 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Nov 17 10:19 splash3 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Nov 17 10:19 system -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Nov 17 10:19 teeos -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Nov 17 10:19 userdata -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 20 Nov 17 10:19 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Nov 17 10:19 vrl_backup -> /dev/block/mmcblk0p2
I suppose the SENSORHUB partition should be on another mmcblk - that's why I get the following error when booting the phone:
Error!
Func NO: 12 (FUNC_LOAD_IOM3)
Error NO: 1
I suppose the partition layout can also be from similar models, such as the PE-TL10.
Thanks in advance for a fast help
Allright.. the layout seems OK - and thanks to Split74 I managed to resurrect the sensorhub partition :good:
However I found an interesting thing - the Huawei update extractor tool extracts images from UPDATE.APP - however these contain additional data in the header and cannot be directly cloned using the dd command in TWRP/ADB SHELL.
Thus I and Split74 need someone to dump their Honor 6 PLUS (PE-UL00 or PE-TL10 should also be OK) boot, recovery, system and cust partitions using dd - they contain only stock data and no personal files AFAIK.
Anyone is willing to help two desperate Honor 6 Plus owners? (I am stuck on MM (camera not focusing, sensors not working) and cannot downgrade do LL and Split74 cannot boot at all, only TWRP) Please kindly PM me or Split74, I will also post the necessary instructions in this post..
we are in deep s mate! =) no1 have Honor 6 plus! such a shame it's a fantastic device! (when you dont mess with android haha)
EDIT: Booting again DC-Phoenix tool did It!

Lg v20 Rent-a-center unlock

I Bought a LG V20 us996 through ebay it had a rent a center lock on it, i tried to uninstall it but it install itself again from somewhere, then i found out from samsung forum that it is in persist partition
to unlock it we need
1.unlocked bootloader
2.latest twrp
3.adb access
4 wipe the persdata partion ( dd if=/dev/zero of=/dev/block/sda15) and install [US996][ROM + Kernel] NRD90M Modded NotSoStock ROM v5.5 1/5/2017 by Tilde88
and it worked sec.abt did not install itself again.
78us996:/ # ls -al /dev/block/platform/soc/624000.ufshc/by-name
total 0
drwxr-xr-x 2 root root 1480 2016-01-02 14:10 .
drwxr-xr-x 4 root root 1660 2016-01-02 14:10 ..
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 aboot -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 abootbak -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 apdp -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 boot -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cache -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 carrier -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 cdt -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib64 -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib64bak -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlibbak -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 ddr -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 devcfg -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 devcfgbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 devinfo -> /dev/block/sdb6
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 dip -> /dev/block/sdb5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 dpo -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 drm -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 eksst -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 encrypt -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 eri -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 factory -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fota -> /dev/block/sdb3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fsg -> /dev/block/sdb4
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 grow -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow2 -> /dev/block/sdb7
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow3 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow4 -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 grow5 -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow6 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow7 -> /dev/block/sdg2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 hyp -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 hypbak -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keymaster -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keymasterbak -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keystore -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 laf -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 lafbak -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 misc -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 modem -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 mpt -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 msadp -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 operatorlogging -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 persdata -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 persist -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 persistent -> /dev/block/sdg1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 pmic -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 pmicbak -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 raw_resources -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 raw_resourcesbak -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rct -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 recovery -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 recoverybak -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 reserve -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rpm -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rpmbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 sec -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 sns -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 spare1 -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 spare2 -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 ssd -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 system -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 tz -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 tzbak -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 userdata -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl2 -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl2bak -> /dev/block/sdc2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xblbak -> /dev/block/sdb2
us996:/ # dd if=/dev/zero of=/dev/block/sda15
dd: /dev/block/sda15: No space left on device
131073+0 records in
131072+0 records out
67108864 bytes transferred in 8.561 secs (7838904 bytes/sec)
1|us996:/ # dd if=/dev/zero of=/dev/block/sda15
Can you explain a little bit how to install TWRP for the v20? It doesnt look like its supported according to their support page.
Edit. NM i was able to figure out how to install TWRP. Now i have to wait until i can sign in with google with phone.
i have a lg v20 but i cannot access anything even just go to the setting it wont do it. because of rent a center lock. any help? I try using lgup to flash stock rom old and new but after finishing the update REnt a center lock pop up cannot access anything.
i have lock bootloader
no twrp
cannot access adb because phone is lock cannot access setting to unlock oem and usb debugging.
any help will be much appreciated.
cjnoob said:
i have a lg v20 but i cannot access anything even just go to the setting it wont do it. because of rent a center lock. any help? I try using lgup to flash stock rom old and new but after finishing the update REnt a center lock pop up cannot access anything.
i have lock bootloader
no twrp
cannot access adb because phone is lock cannot access setting to unlock oem and usb debugging.
any help will be much appreciated.
Click to expand...
Click to collapse
for us996 you can unlock the bootloader using official lg website then install twrp.
So in a few words this means, rooting the phone and installing that ROM will erase the problem? What happens is you try to go back to stock after that ? Thanks !
shajubinglish said:
I Bought a LG V20 us996 through ebay it had a rent a center lock on it, i tried to uninstall it but it install itself again from somewhere, then i found out from samsung forum that it is in persist partition
to unlock it we need
1.unlocked bootloader
2.latest twrp
3.adb access
4 wipe the persdata partion ( dd if=/dev/zero of=/dev/block/sda15) and install [US996][ROM + Kernel] NRD90M Modded NotSoStock ROM v5.5 1/5/2017 by Tilde88
and it worked sec.abt did not install itself again.
78us996:/ # ls -al /dev/block/platform/soc/624000.ufshc/by-name
total 0
drwxr-xr-x 2 root root 1480 2016-01-02 14:10 .
drwxr-xr-x 4 root root 1660 2016-01-02 14:10 ..
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 aboot -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 abootbak -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 apdp -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 boot -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cache -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 carrier -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 cdt -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib64 -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib64bak -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlibbak -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 ddr -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 devcfg -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 devcfgbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 devinfo -> /dev/block/sdb6
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 dip -> /dev/block/sdb5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 dpo -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 drm -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 eksst -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 encrypt -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 eri -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 factory -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fota -> /dev/block/sdb3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fsg -> /dev/block/sdb4
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 grow -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow2 -> /dev/block/sdb7
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow3 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow4 -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 grow5 -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow6 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow7 -> /dev/block/sdg2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 hyp -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 hypbak -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keymaster -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keymasterbak -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keystore -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 laf -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 lafbak -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 misc -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 modem -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 mpt -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 msadp -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 operatorlogging -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 persdata -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 persist -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 persistent -> /dev/block/sdg1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 pmic -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 pmicbak -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 raw_resources -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 raw_resourcesbak -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rct -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 recovery -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 recoverybak -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 reserve -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rpm -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rpmbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 sec -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 sns -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 spare1 -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 spare2 -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 ssd -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 system -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 tz -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 tzbak -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 userdata -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl2 -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl2bak -> /dev/block/sdc2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xblbak -> /dev/block/sdb2
us996:/ # dd if=/dev/zero of=/dev/block/sda15
dd: /dev/block/sda15: No space left on device
131073+0 records in
131072+0 records out
67108864 bytes transferred in 8.561 secs (7838904 bytes/sec)
1|us996:/ # dd if=/dev/zero of=/dev/block/sda15
Click to expand...
Click to collapse
HEY BRO, Well the thing is I got scammed on eBay buying and unlocked lg v20 us996, I already opened a dispute in PayPal but in the meantime I'm trying to fix this...
I've read these explanation but I still dont understand. My bootloader is locked and I don't have enabled OEM unlock nor USB debugging . So my question is, is there any way to activate these two other than in the phone itself ? so I can unlock the bootloader then root and remove RAC,, (I can't do it the normal way since the RAC message blocks absolutely everything on the phone)
Could you please walk me through this? I would extremely appreciate it!!!
Thanks in advance people.
Kevinrdz91 said:
HEY BRO, Well the thing is I got scammed on eBay buying and unlocked lg v20 us996, I already opened a dispute in PayPal but in the meantime I'm trying to fix this...
I've read these explanation but I still dont understand. My bootloader is locked and I don't have enabled OEM unlock nor USB debugging . So my question is, is there any way to activate these two other than in the phone itself ? so I can unlock the bootloader then root and remove RAC,, (I can't do it the normal way since the RAC message blocks absolutely everything on the phone)
Could you please walk me through this? I would extremely appreciate it!!!
Thanks in advance people.
Click to expand...
Click to collapse
I use this metod
1. Factory reset
2. After reboot log in to a google account and wait home screen start loading and VERY fast pull off battery.
3. Boot in a safe mode (in safemode you can use youre phone normaly but you cant use non system applications)
Antoni0_ said:
I use this metod
1. Factory reset
2. After reboot log in to a google account and wait home screen start loading and VERY fast pull off battery.
3. Boot in a safe mode (in safemode you can use youre phone normaly but you cant use non system applications)
Click to expand...
Click to collapse
Thank you man! I will try that as soon as I get home.
By "home screen start loading" you mean the moment when you finished setting up the phone (Google account , sync , lockscreen) ? In that exact moment I pull off the battery and then boot into safemode in order to activate USB debugging - OEM unlock. Am I correct? Thanks again!
Kevinrdz91 said:
Thank you man! I will try that as soon as I get home.
By "home screen start loading" you mean the moment when you finished setting up the phone (Google account , sync , lockscreen) ? In that exact moment I pull off the battery and then boot into safemode in order to activate USB debugging - OEM unlock. Am I correct? Thanks again!
Click to expand...
Click to collapse
Antoni0_ said:
I use this metod
1. Factory reset
2. After reboot log in to a google account and wait home screen start loading and VERY fast pull off battery.
3. Boot in a safe mode (in safemode you can use youre phone normaly but you cant use non system applications)
Click to expand...
Click to collapse
Hey Bro, it didn't work. Even in safe mode is asking for a code. Any other suggestions on how to access the phone and enable USB debugging and OEM unlock ?
Kevinrdz91 said:
Thank you man! I will try that as soon as I get home.
By "home screen start loading" you mean the moment when you finished setting up the phone (Google account , sync , lockscreen) ? In that exact moment I pull off the battery and then boot into safemode in order to activate USB debugging - OEM unlock. Am I correct? Thanks again!
Click to expand...
Click to collapse
Yes. I mean this moment.
---------- Post added at 10:23 AM ---------- Previous post was at 10:22 AM ----------
Kevinrdz91 said:
Hey Bro, it didn't work. Even in safe mode is asking for a code. Any other suggestions on how to access the phone and enable USB debugging and OEM unlock ?
Click to expand...
Click to collapse
Do you Factory reset youre phone?
Antoni0_ said:
I use this metod
1. Factory reset
2. After reboot log in to a google account and wait home screen start loading and VERY fast pull off battery.
3. Boot in a safe mode (in safemode you can use youre phone normaly but you cant use non system applications)
Click to expand...
Click to collapse
It works to my us996
but I have question do i have to use safe mode only?
please help me
Thank you
Backup of Partition
shajubinglish said:
I Bought a LG V20 us996 through ebay it had a rent a center lock on it, i tried to uninstall it but it install itself again from somewhere, then i found out from samsung forum that it is in persist partition
to unlock it we need
1.unlocked bootloader
2.latest twrp
3.adb access
4 wipe the persdata partion ( dd if=/dev/zero of=/dev/block/sda15) and install [US996][ROM + Kernel] NRD90M Modded NotSoStock ROM v5.5 1/5/2017 by Tilde88
and it worked sec.abt did not install itself again.
78us996:/ # ls -al /dev/block/platform/soc/624000.ufshc/by-name
total 0
drwxr-xr-x 2 root root 1480 2016-01-02 14:10 .
drwxr-xr-x 4 root root 1660 2016-01-02 14:10 ..
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 aboot -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 abootbak -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 apdp -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 boot -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cache -> /dev/block/sda19
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 carrier -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 cdt -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib64 -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlib64bak -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 cmnlibbak -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 ddr -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 devcfg -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 devcfgbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 devinfo -> /dev/block/sdb6
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 dip -> /dev/block/sdb5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 dpo -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 drm -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 eksst -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 encrypt -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 eri -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 factory -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fota -> /dev/block/sdb3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 fsg -> /dev/block/sdb4
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 grow -> /dev/block/sda21
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow2 -> /dev/block/sdb7
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow3 -> /dev/block/sdc3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow4 -> /dev/block/sdd5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 grow5 -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow6 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 grow7 -> /dev/block/sdg2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 hyp -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 hypbak -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keymaster -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keymasterbak -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 keystore -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 laf -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 lafbak -> /dev/block/sda17
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 misc -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 modem -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 mpt -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 msadp -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 operatorlogging -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 persdata -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 persist -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 persistent -> /dev/block/sdg1
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 pmic -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 pmicbak -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 raw_resources -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 raw_resourcesbak -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rct -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 recovery -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 recoverybak -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 reserve -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rpm -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 rpmbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 sec -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 sns -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 spare1 -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 spare2 -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 ssd -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 system -> /dev/block/sda18
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 tz -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 tzbak -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 2016-01-02 14:10 userdata -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl2 -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xbl2bak -> /dev/block/sdc2
lrwxrwxrwx 1 root root 15 2016-01-02 14:10 xblbak -> /dev/block/sdb2
us996:/ # dd if=/dev/zero of=/dev/block/sda15
dd: /dev/block/sda15: No space left on device
131073+0 records in
131072+0 records out
67108864 bytes transferred in 8.561 secs (7838904 bytes/sec)
1|us996:/ # dd if=/dev/zero of=/dev/block/sda15
Click to expand...
Click to collapse
shajubinglish , do you happen to have a backup of this persdata partition that you can send me? If you have them please send me the stock partitions and how to flash them manually.
After using my phone for a long time US996 UNLOCKED bootloader and using NRD90M Modded NotSoStock ROM v5.5 1/5/2017 by Tilde88 for a long time without having needed to delete this partition. I decided to use WETA and I wanted to go ahead and delete this because it was a RAC locked phone but I didn't need this because of the Unlocked US996 just unlocked bootloader and flashed TWRP and rom. Rooted... NOW AFTER DELETING THIS PARTITION (without a backup, like a dummy) and flashing WETA Rom I got a horrible bootloop. Not to recovery but after Android OS loads first time and keeps booting to setup and restarts over and over very quickly after booting up. About 5-30 seconds at most the first time longest then mayve 5 secs each afterward. Tried restoring my TWRP backup, flashing back to the NRD90M Modded NotSoStock ROM. Flashing stock 10f firmware through TWRP, and also flashing stock 10f KDZ to phone completely stock with LGUP. (AS I UNDERSTAND.) I dont know what to do. I have completely redone and repeated above processes about 5 times over all of them! PLEASE HELP!

xt1962-1/river_amz stock resources (16_7) & tools

I will be sharing my stock resources with the community here.
Individual Stock Files
Stock boot.img
https://drive.google.com/open?id=1TVKhFx1HAGRXds5U9BTxaEnLfGQuw7sD
Format: .img
Size: 32Mbytes
This is from "RIVER_AMZ_PPO29.114_16_7_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
I was successfully able to patch this image using magisk manager. Screenshots of the magisk app and root checker available in attachments.
Full Stock Files
https://drive.google.com/open?id=1U7asJXX1_lJkbateTl0R2adYwVsCg0Fo
Format: .7z
Size: 1.8Gbytes
"RIVER_AMZ_PPO29.114_16_7_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC"
Extract and use with RSD or XML>BAT
Tools
Lenovo MOTO Smart Assistant: https://download.lenovo.com/consumer/mobiles/lmsa_v4.1.0.8_setup.exe
Non-verizon solution for returning to stock (idk if it works for verizon as well, it should)
Moto Software Repair Assistant: https://www.verizonwireless.com/support/knowledge-base-209211/
Verizon solution for returning to stock
Portable Android Tools (adb+fastboot): https://drive.google.com/open?id=13ppb_xveLtP9BBMdz6zYW-R_p4BDO_oW
Partition Info
Code:
drwxr-xr-x 2 root root 1320 1970-01-23 13:12 .
drwxr-xr-x 3 root root 1380 1970-01-23 13:12 ..
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 aboot_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 aboot_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 apdp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 boot_a -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 boot_b -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 carrier -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cid -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib64_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib64_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib_a -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 cmnlib_b -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 devcfg_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 devcfg_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 devinfo -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dpo -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dsp_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dsp_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dtbo_a -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 dtbo_b -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 frp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 fsg_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 fsg_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 hw -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 keymaster_a -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 keymaster_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 kpan -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 logo_a -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 logo_b -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 logs -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 metadata -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 misc -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modemst1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 modemst2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 mota -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 msadp -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 oem_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 oem_b -> /dev/block/mmcblk0p59
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 padA -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 persist2 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 prov_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 prov_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 rpm_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 rpm_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 sbl1_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 sbl1_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 sp -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 syscfg -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 system_a -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 system_b -> /dev/block/mmcblk0p63
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 tz_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-23 13:12 tz_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 userdata -> /dev/block/mmcblk0p64
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 utags -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 utagsBackup -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vbmeta_a -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vbmeta_b -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vendor_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-01-23 13:12 vendor_b -> /dev/block/mmcblk0p61
Will be providing more resources soon.
-reserved for flashable scripts-
Thanks for this--question regarding returning to stock
Hi,
Thanks for posting these resources--very useful. Question for you: do you happen to know what the process would be to "undo" root (via Magisk) and TWRP installation to be able to get back to stock 16_7 version? I've currently got a rooted 16_5 version with TWRP, and I think it might be good to get up to the 16_7 version. Thanks in advance.

managed to repair imei on Sawshark (LEO-DLXX)

Hi,
Just wanted to share that I was able to repair the imei on a Huawei Watch 2 (Sawshark,LEO-DLXX).
It goes on just as any other snapdragon imei repair. There are many tutorials out there.
The step I was stuck at was opening a diag port on the watch after issuing this command as root.
Code:
setprop sys.usb.config diag,adb
The usb device does change, but not recognized even though Qualcomm drivers are installed.
The solution? Manually load this driver named:
Qualcomm HS-USB Diagnostics 9404
Some tutorials say some partitions need to be cleared for imei repair to work. Not sure if this is necessary, but these are the partitions that need clearing.
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name/ <
total 0
drwxr-xr-x 2 root root 740 1970-01-29 07:08 .
drwxr-xr-x 4 root root 820 1970-01-29 07:08 ..
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 DDR -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 abootbak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 boot -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 cache -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 cmnlib -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 cmnlibbak -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 config -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 fsc -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 fsg -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 keymaster -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 keymasterbak -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 keystore -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 modem -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 nfc -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 nvbin -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 nvdata -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 oem -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 recovery -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 reserved -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 sec -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 splash -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 ssd -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 system -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-29 07:08 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-29 07:08 userdata -> /dev/block/mmcblk0p35
sawshark:/ #
sawshark:/ # dd if=/dev/zero of=/dev/block/mmcblk0p11
dd: /dev/block/mmcblk0p11: No space left on device
8193+0 records in
8192+0 records out
4194304 bytes transferred in 1.069 secs (3923577 bytes/sec)
1|sawshark:/ # dd if=/dev/zero of=/dev/block/mmcblk0p12
dd: /dev/block/mmcblk0p12: No space left on device
8193+0 records in
8192+0 records out
4194304 bytes transferred in 0.854 secs (4911362 bytes/sec)
1|sawshark:/ # dd if=/dev/zero of=/dev/block/mmcblk0p22
dd: /dev/block/mmcblk0p22: No space left on device
8193+0 records in
8192+0 records out
4194304 bytes transferred in 0.951 secs (4410414 bytes/sec)
1|sawshark:/ #
The rest is same as any other snapdragon imei repair.
Hope this helps some of you out there.

Categories

Resources