I wanted to extract boot.img from an existing rom, following this wiki:
http://android-dls.com/wiki/index.p..._Images#Structure_of_boot_and_recovery_images
But it seems that on Stock Rom (actually I'm using Zeus rom, based on stock) there is no /proc/mtd that would tell me where to find the "boot" partition. I think it should be one of these:
179 0 1912832 mmcblk0
179 1 128 mmcblk0p1
179 2 512 mmcblk0p2
179 3 6144 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 660480 mmcblk0p8
179 9 1161088 mmcblk0p9
179 10 65536 mmcblk0p10
179 11 128 mmcblk0p11
179 12 128 mmcblk0p12
179 16 15637504 mmcblk1
179 17 15633408 mmcblk1p1
Do anyone know where the boot partition is hiding? Or have an idea on how to find where it is?
Here are some of the partitions:
Code:
loop0 =
/dev/block/mmcblk0 =
/dev/block/mmcblk0p1 =
/dev/block/mmcblk0p2 =
/dev/block/mmcblk0p3 = /boot
/dev/block/mmcblk0p4 = /recovery
/dev/block/mmcblk0p5 = /lgdrm
/dev/block/mmcblk0p6 = /dvp/userdata
/dev/block/mmcblk0p7 =
/dev/block/mmcblk0p8 = /system
/dev/block/mmcblk0p9 = /data
/dev/block/mmcblk0p10 = /cache
/dev/block/mmcblk0p11 =
/dev/block/mmcblk0p12 =
/dev/block/mmcblk1 =
/dev/block/mmcblk1p1 = /sdcard
dm-0 =
I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m
Velrix said:
I have extracted the Gear 2 firmware to a zip so people can look at the structure and possibly start modding the device. Its extracted from the newest rom available on Sammobile. If you have any questions let me know.
htt p://bit.ly/1m4mj5m
Click to expand...
Click to collapse
Updates..
I am trying to backup the current partitions to see the kernel/recovery and not getting far. Has anyone else been working on this?
sh-3.2$ cat /proc/partitions
major minor #blocks name
7 0 19732 loop0
179 0 3817472 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 65536 mmcblk0p12
259 5 131072 mmcblk0p13
259 6 2996224 mmcblk0p14
259 7 524288 mmcblk0p15
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
179:0 179:3 179:7 1:10 1:14 1:4 1:8 259:2 259:6 7:2 7:6
179:1 179:4 179:8 1:11 1:15 1:5 1:9 259:3 259:7 7:3 7:7
179:16 179:5 1:0 1:12 1:2 1:6 259:0 259:4 7:0 7:4
179:2 179:6 1:1 1:13 1:3 1:7 259:1 259:5 7:1 7:5
Current information I can receive from the watch.
If I try to make a backup obviously it fails with the following message..
D:\tizen-wearable-sdk\tools>sdb shell
sh-3.2$ chmod 755 /tmp/rkdump
sh-3.2$ /tmp/rkdump /dev/mmcblk0boot0 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0boot0: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p1 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p1: Permission denied
sh-3.2$ /tmp/rkdump /dev/mmcblk0p2 /tmp/update.img
/tmp/rkdump: /dev/mmcblk0p2: Permission denied
Hi all,
I bought a moto g 2nd gen in USA. I live in Ireland. The phone works fine but mobile data is extremely slow. I get E but no 3G whatsoever. I was wondering if I was able to change baseband to an EMEA one would it solve the problem. I am attaching a screenshot of my settings.
Many thanks..
You got dual sim or single sim? If dual put your card sim in first slot (on the left)
wiemar said:
You got dual sim or single sim? If dual put your card sim in first slot (on the left)
Click to expand...
Click to collapse
Hi, Its a single sim.
Settings>sim>settings connection>mobile networks
wiemar said:
Settings>sim>settings connection>mobile networks
Click to expand...
Click to collapse
Hi, did that. See attached.
Go to the dialer and enter:
*#*#4636#*#*
Click on Phone Information, then look for Set preferred network type, then select ‘WCDMA only’
The problem is that the US uses different frequencies from the rest of the world, so your US phone may not be able to use it on a hardware level. If after selecting WCDMA only you can't connect at all, there is nothing you can do to fix it as it is a physical issue with the radio.
SeanWatson said:
Go to the dialer and enter:
*#*#4636#*#*
Click on Phone Information, then look for Set preferred network type, then select ‘WCDMA only’
The problem is that the US uses different frequencies from the rest of the world, so your US phone may not be able to use it on a hardware level. If after selecting WCDMA only you can't connect at all, there is nothing you can do to fix it as it is a physical issue with the radio.
Click to expand...
Click to collapse
Thanks Sean, I tried that but the code just disappears after pressing the last *.
It seems I have the US version of the phone and not the Global version therefore I am screwed. - according to Motorola support.
gdublin said:
Thanks Sean, I tried that but the code just disappears after pressing the last *.
It seems I have the US version of the phone and not the Global version therefore I am screwed. - according to Motorola support.
Click to expand...
Click to collapse
Do I need to root my phone first?
After you enter the last * the dialer will disappear and a new activity will appear with Phone Information, Battery Information, etc. Touch the Phone Information and then preferred network to WCDMA only.
It doesn't need root. There is an app that does the same thing, but this forum won'tlet me post direct links. Search for Philipp Mangelow in Google Play, and install Network
gdublin said:
Hi all,
I bought a moto g 2nd gen in USA. I live in Ireland. The phone works fine but mobile data is extremely slow. I get E but no 3G whatsoever. I was wondering if I was able to change baseband to an EMEA one would it solve the problem. I am attaching a screenshot of my settings.
Many thanks..
Click to expand...
Click to collapse
Yeah, it sounds like the 2100MHz band is disabled in firmware. Others have been said they've lost 'mobile data' when flashing OTA packages willy-nilly from the XT1063/64 onto the XT1068. You need an EMEA (Europe, Middle East and Asia) firmware package... Do they exist? Flashing an XT1068 baseband firmware might work as the phone still has a single radio, I dunno, but I wouldn't bank on it. IF the partition sizes match between the XT1063/64 and XT1068, you could always try it and flash the old firmware back if it screws things up...
My XT1068 is running firmware with same version number, but with the EMEA_DSDS_CUST suffix. I believe DSDS denotes dual sim dual standby.
CDMA support is the difference between the MSM8226 and the MSM8626 chipsets and they both use the same WTR2605 multi-mode radio, AFAIK. Motorola's support response is typically inaccurate. I'm pretty sure the issue is the firmware, not the hardware, but good luck getting an EMEA firmware out of Motorola -- they'd obviously much rather you buy another handset!
rufflove said:
Yeah, it sounds like the 2100MHz band is disabled in firmware. Others have been said they've lost 'mobile data' when flashing OTA packages willy-nilly from the XT1063/64 onto the XT1068. You need an EMEA (Europe, Middle East and Asia) firmware package... Do they exist? Flashing an XT1068 baseband firmware might work as the phone still has a single radio, I dunno, but I wouldn't bank on it. IF the partition sizes match between the XT1063/64 and XT1068, you could always try it and flash the old firmware back if it screws things up...
My XT1068 is running firmware with same version number, but with the EMEA_DSDS_CUST suffix. I believe DSDS denotes dual sim dual standby.
CDMA support is the difference between the MSM8226 and the MSM8626 chipsets and they both use the same WTR2605 multi-mode radio, AFAIK. Motorola's support response is typically inaccurate. I'm pretty sure the issue is the firmware, not the hardware, but good luck getting an EMEA firmware out of Motorola -- they'd obviously much rather you buy another handset!
Click to expand...
Click to collapse
Thanks for the reply. My phone is a single sim. IS it still XT1068? If I find suitable firmware but its for dual sim do you think that would matter?
SeanWatson said:
After you enter the last * the dialer will disappear and a new activity will appear with Phone Information, Battery Information, etc. Touch the Phone Information and then preferred network to WCDMA only.
It doesn't need root. There is an app that does the same thing, but this forum won'tlet me post direct links. Search for Philipp Mangelow in Google Play, and install Network
Click to expand...
Click to collapse
Thanks Sean, That app worked. Unfortunately WCDMA only did not work. I'll have to go with rufflove's suggestion and try and find EMEA firmware that will activate the radio frequency I need.
gdublin said:
Thanks for the reply. My phone is a single sim. IS it still XT1068? If I find suitable firmware but its for dual sim do you think that would matter?
Click to expand...
Click to collapse
I believe your phone is the XT1064 version. That version is for US only.
Sent from my XT1068 using XDA Free mobile app
gdublin said:
Thanks for the reply. My phone is a single sim. IS it still XT1068? If I find suitable firmware but its for dual sim do you think that would matter?
Click to expand...
Click to collapse
The XT1068 has a white sticker under the backpiece that includes the model code. It definitely sounds like you have the XT1064, but you can confirm by checking the sticker. I honestly do not know what effect(s) shoehorning an XT1068 baseband firmware onto an XT1064 would have. For starters, it depends whether the XT1064 and XT1068 share the exact same partition map. It is highly likely that they do. Could you post the output of the following command? You'll need the adb tools installed.
Code:
adb shell cat /proc/partitions
Alternatively, install a terminal emulator app on the phone and issue 'cat /proc/partitions'. If I remember correctly, the first partition (mmcblk0p1 ) holds the baseband firmware. It should have a block size of 65536. You'd also need to overwrite the fsg partition, but I can't remember which partition it maps to right now! I'd check mine, but I'm in Windows whilst gaming and my Android tools are installed on my usual linux desktop instead.
rufflove said:
The XT1068 has a white sticker under the backpiece that includes the model code. It definitely sounds like you have the XT1064, but you can confirm by checking the sticker. I honestly do not know what effect(s) shoehorning an XT1068 baseband firmware onto an XT1064 would have. For starters, it depends whether the XT1064 and XT1068 share the exact same partition map. It is highly likely that they do. Could you post the output of the following command? You'll need the adb tools installed.
Code:
adb shell cat /proc/partitions
Alternatively, install a terminal emulator app on the phone and issue 'cat /proc/partitions'. If I remember correctly, the first partition (mmcblk0p1 ) holds the baseband firmware. It should have a block size of 65536. You'd also need to overwrite the fsg partition, but I can't remember which partition it maps to right now! I'd check mine, but I'm in Windows whilst gaming and my Android tools are installed on my usual linux desktop instead.
Click to expand...
Click to collapse
Thank . Its a XT1064 . Im not very technical but i will have a go at what you suggested and will get back to you.
gdublin said:
Thank . Its a XT106 . Im not very technical but i will have a go at what you suggested and will get back to you.
Click to expand...
Click to collapse
The full model number has 4 digits. You should definitely get hold of a copy of the 4.4.4 OTA, or root your device and backup everything, before attempting anything adventurous.
rufflove said:
The XT1068 has a white sticker under the backpiece that includes the model code. It definitely sounds like you have the XT1064, but you can confirm by checking the sticker. I honestly do not know what effect(s) shoehorning an XT1068 baseband firmware onto an XT1064 would have. For starters, it depends whether the XT1064 and XT1068 share the exact same partition map. It is highly likely that they do. Could you post the output of the following command? You'll need the adb tools installed.
Code:
adb shell cat /proc/partitions
Click to expand...
Click to collapse
hi, all,
im in same shi*, i have *64 version of device, bought in US, now in EU only EDGE is working...
here is list of partitions:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 1012 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 1012 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 546944 mmcblk0p35
259 4 1130496 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 5774208 mmcblk0p38
179 32 2048 mmcblk0rpm
179 64 15440896 mmcblk1
179 65 15436800 mmcblk1p1
can you share list from *68...
if flashing only baseband, is this part enough from flashing Stock with fastboot:
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
if this will work, i will make flashable zip for those basebands...
oh yeah, happy new year!!!
I'm short on time right now, but here's the partition table:
Code:
179 0 7634944 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 1012 mmcblk0p4
179 5 200 mmcblk0p5
179 6 400 mmcblk0p6
179 7 32 mmcblk0p7
179 8 512 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 2332 mmcblk0p10
179 11 1012 mmcblk0p11
179 12 200 mmcblk0p12
179 13 400 mmcblk0p13
179 14 32 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1052 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 488 mmcblk0p19
179 20 32 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 1 mmcblk0p22
179 23 8 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 128 mmcblk0p25
179 26 3072 mmcblk0p26
179 27 4096 mmcblk0p27
179 28 4096 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 512 mmcblk0p30
179 31 10200 mmcblk0p31
259 0 10280 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 546944 mmcblk0p35
259 4 1130496 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 5774208 mmcblk0p38
179 32 2048 mmcblk0rpmb
179 64 15449088 mmcblk1
179 65 15448064 mmcblk1p1
Here's the mappings (obtained via 'ls -l /dev/block/platform/msm_sdcc.1/by-name'):
Code:
lrwxrwxrwx root root 1970-01-25 22:05 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-25 22:05 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-25 22:05 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-25 22:05 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-25 22:05 cache -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-25 22:05 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-25 22:05 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-25 22:05 deviceinfo -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-25 22:05 dhob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-25 22:05 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-25 22:05 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-25 22:05 ftmlog -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-25 22:05 hob -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-25 22:05 kpan -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-25 22:05 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-25 22:05 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-25 22:05 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-25 22:05 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-25 22:05 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-25 22:05 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-25 22:05 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-25 22:05 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-25 22:05 pds -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-25 22:05 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-25 22:05 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-25 22:05 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-25 22:05 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-25 22:05 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-25 22:05 sdi -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-25 22:05 sdiBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-25 22:05 sp -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-25 22:05 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-25 22:05 system -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-25 22:05 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-25 22:05 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-25 22:05 userdata -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-25 22:05 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-25 22:05 utagsBackup -> /dev/block/mmcblk0p15
IIRC, Motorola's OTA system also writes to the fsg partition, which appears to include service definitions for various carriers. My retgb device has files for European carriers. I'd read up on that, too.
Any update here? I bought a moto g 2014 in the US and it was supposed to be an international version but 3g doesn't work in Europe.... Anyone kept trying this baseband change solution?
del.
DISCLAIMER
All, what you do with your Phone : doing at your own RISK !
the only chance, that i see : https://forum.xda-developers.com/9-lite/development/honor-9-lite-update-zip-lld-l31-8-0-0-t3767781
extract the *.img , that you need and flash it
Attention : this is for C432 ( Country europ )
PLEASE : if you flash (or use dd) is your Risk ! Never flash other Partitions as "recovery_ramdisk" and "system" ! Here is the Risk little for kill phone .
most error : bootloop . you have huawei-images - than you can self-repair
NEVER flash images from other Phone-Model ! only you 100% secure that is 100% same hardware inside .
you flash other partition-images : you can kill your phone ! now only repair is - send to huawei-service and pay !
huawei-repair is change MotherBoard : cost over 100 €
i hope this help you
Partition-List from H9L
HWLLD-H:/ # cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
254 0 1572864 zram0
179 0 30535680 mmcblk0
179 1 256 mmcblk0p1
179 2 256 mmcblk0p2
179 3 256 mmcblk0p3
179 4 768 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 6144 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 32768 mmcblk0p13
179 14 2048 mmcblk0p14
179 15 2048 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 14336 mmcblk0p17
179 18 32768 mmcblk0p18
179 19 65536 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 24576 mmcblk0p21
179 22 61440 mmcblk0p22
179 23 4096 mmcblk0p23
179 24 2048 mmcblk0p24
179 25 16384 mmcblk0p25
179 26 12288 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 32768 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 24576 mmcblk0p30
179 31 16384 mmcblk0p31
179 32 32768 mmcblk0p32
179 33 16384 mmcblk0p33
179 34 28672 mmcblk0p34
179 35 4096 mmcblk0p35
179 36 98304 mmcblk0p36
179 37 1024 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 2048 mmcblk0p39
179 40 16384 mmcblk0p40
179 41 4096 mmcblk0p41
179 42 131072 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 2048 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 4096 mmcblk0p46
179 47 32768 mmcblk0p47
259 0 2048 mmcblk0p48
259 1 16384 mmcblk0p49
259 2 30720 mmcblk0p50
259 3 3620864 mmcblk0p51
259 4 196608 mmcblk0p52
259 5 32768 mmcblk0p53
259 6 802816 mmcblk0p54
259 7 196608 mmcblk0p55
259 8 24637440 mmcblk0p56
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
179 192 125041664 mmcblk1
179 193 125040640 mmcblk1p1
HWLLD-H:/ #
HWLLD-H:/ # ls -al /dev/block/platform/hi_mci.0/by-name
total 0
drwxr-xr-x 2 root root 1160 2018-03-21 08:52 .
drwxr-xr-x 4 root root 1280 2018-03-21 08:52 ..
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 bootfail_info -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 cust -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 dfx -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 dto -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 dts -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_kernel -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_ramdisk -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 erecovery_vendor -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 fw_hifi -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 hisitest0 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 hisitest1 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 hisitest2 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 kernel -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modem_fw -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modem_secure -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 odm -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 patch -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 product -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 ramdisk -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 recovery_ramdisk -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 recovery_vbmeta -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 recovery_vendor -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved8 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 reserved9 -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 rrecord -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 sensorhub -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 system -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 teeos -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 trustfirmware -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 userdata -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 vbmeta -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 vendor -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-03-21 08:52 version -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2018-03-21 08:52 vrl_backup -> /dev/block/mmcblk0p2
HWLLD-H:/ #
He asked the question yesterday in telegram group and got answer.
He damaged his persist partition and need to restore it step by step.