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.
Related
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
Hello!
I have a moto g xt1033 dual sim BR. It goes into fastboot mode but accepts no recording. I believe he is not with usb mode debbugin enabled, as in recovery mode (stock recovery) adb does not recognize ..
when I do a wipe, message me:
blkdiscard on partition failed /dev/block/platform/msm_sdcc.1/by-name/userdata
I can do the adb recognize him as recovery with the following command:
fastboot boot openrecovery-TWRP-2.8.1.0-xt1032.img
he gets the M on the screen and can enter the shell mode.
the adb shell, can not see the partitions:
/dev/block/platform/msm_sdcc.1/by-name # ls -la
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 1970-01-01 06:08 DDR -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:08 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:08 abootBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 06:08 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 06:08 cache -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 06:08 cid -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 06:08 clogo -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 06:08 dhob -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 06:08 fsc -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 06:08 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 06:08 hob -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 06:08 kpan -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 06:08 logo -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 06:08 logs -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 06:08 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 06:08 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:08 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 06:08 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 06:08 padA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 06:08 padB -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 06:08 pds -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 06:08 persist -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 06:08 recovery -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 06:08 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:08 rpmBackup -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 06:08 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:08 sdi -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 06:08 sdiBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 06:08 sp -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 06:08 ssd -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 06:08 system -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 06:08 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:08 tzBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 06:08 userdata -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 06:08 utags -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:08 utagsBackup -> /dev/block/mmcblk0p15
I am not presenting solution because I decided not to. but it can help someone with more knowledge in the area ...
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.
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.
I want to root my phone using magisk.
I am using Arch Linux. I installed the adb packages using -
Code:
sudo pacman -S android-tools && yay -S adbfs-rootless-git
# for mounting adb devices see https://aur.archlinux.org/packages/adbfs-rootless-git
# and https://github.com/spion/adbfs-rootless
# I didn't use MTP (media transfer protocol as it is known to corrupt over larger files.)
I ran the following commands but it didn't work -
Code:
[[email protected] 13:33 ~]$ adbfs ~/mnt
--*-- exec_command: adb shell "ls"
[[email protected] 13:33 ~]$ ls ~/mnt
acct cache debug_ramdisk lost+found proc storage vendor
apex config default.prop mnt product sys vgc
bin d dev odm res system
bugreports data etc oem sdcard system_ext
[[email protected] 13:33 ~]$
[[email protected] 13:15 mnt]$ adb shell ls -la /dev/block/bootdevice/by-name/
total 0
drwxr-xr-x 2 root root 920 2023-02-18 03:20 .
drwxr-xr-x 3 root root 960 2023-02-18 03:20 ..
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 backup -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 cache -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 cust -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 dtbo -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 efuse -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 expdb -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 flashinfo -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 frp -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 gz1 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 gz2 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 lk -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 lk2 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 logo -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 md1img -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 metadata -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 nvcfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 nvdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 nvram -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 otp -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 para -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 23 2023-02-18 03:20 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2023-02-18 03:20 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 proinfo -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 protect1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 protect2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 scp1 -> /dev/block/mmcblk0p22
[[email protected] 13:20 Desktop]$ adb pull /dev/block/mmcblk0p31/by-name/boot boot.img
adb: error: failed to stat remote object '/dev/block/mmcblk0p31/by-name/boot': Not a directory
[[email protected] 13:20 Desktop]$ ls /dev/block/mmcblk0p31/
ls: cannot access '/dev/block/mmcblk0p31/': No such file or directory
[[email protected] 13:21 Desktop]$ adb pull /dev/block/mmcblk0p31/HYNRI7QKC6TCORLN/boot boot.img
adb: error: failed to stat remote object '/dev/block/mmcblk0p31/HYNRI7QKC6TCORLN/boot': Not a directory
I know it is a long code. But I still I am not able to extract my boot.img
Another way is to download the boot.img from vivos official website.
It says the funtouch os version is -
PD1901BF_EX_A_6.72.23but the version I have is -
PD1901BF_EX_A_6.72.24 here is the ss - https://ibb.co/HzFPFgy
It is ok for me to download the file and flash it to my phone ? This is my first time rooting a device. I need some help :'(
prorounak said:
I want to root my phone using magisk.
I am using Arch Linux. I installed the adb packages using -
Code:
sudo pacman -S android-tools && yay -S adbfs-rootless-git
# for mounting adb devices see https://aur.archlinux.org/packages/adbfs-rootless-git
# and https://github.com/spion/adbfs-rootless
# I didn't use MTP (media transfer protocol as it is known to corrupt over larger files.)
I ran the following commands but it didn't work -
Code:
[[email protected] 13:33 ~]$ adbfs ~/mnt
--*-- exec_command: adb shell "ls"
[[email protected] 13:33 ~]$ ls ~/mnt
acct cache debug_ramdisk lost+found proc storage vendor
apex config default.prop mnt product sys vgc
bin d dev odm res system
bugreports data etc oem sdcard system_ext
[[email protected] 13:33 ~]$
[[email protected] 13:15 mnt]$ adb shell ls -la /dev/block/bootdevice/by-name/
total 0
drwxr-xr-x 2 root root 920 2023-02-18 03:20 .
drwxr-xr-x 3 root root 960 2023-02-18 03:20 ..
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 backup -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 boot -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 cache -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 cust -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 dtbo -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 efuse -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 expdb -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 flashinfo -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 frp -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 gz1 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 gz2 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 lk -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 lk2 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 logo -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 md1img -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 metadata -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 nvcfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 nvdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 nvram -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 otp -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 para -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 23 2023-02-18 03:20 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2023-02-18 03:20 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 proinfo -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 protect1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 protect2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2023-02-18 03:20 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2023-02-18 03:20 scp1 -> /dev/block/mmcblk0p22
[[email protected] 13:20 Desktop]$ adb pull /dev/block/mmcblk0p31/by-name/boot boot.img
adb: error: failed to stat remote object '/dev/block/mmcblk0p31/by-name/boot': Not a directory
[[email protected] 13:20 Desktop]$ ls /dev/block/mmcblk0p31/
ls: cannot access '/dev/block/mmcblk0p31/': No such file or directory
[[email protected] 13:21 Desktop]$ adb pull /dev/block/mmcblk0p31/HYNRI7QKC6TCORLN/boot boot.img
adb: error: failed to stat remote object '/dev/block/mmcblk0p31/HYNRI7QKC6TCORLN/boot': Not a directory
I know it is a long code. But I still I am not able to extract my boot.img
Another way is to download the boot.img from vivos official website.
It says the funtouch os version is -
PD1901BF_EX_A_6.72.23but the version I have is -
PD1901BF_EX_A_6.72.24 here is the ss - https://ibb.co/HzFPFgy
It is ok for me to download the file and flash it to my phone ? This is my first time rooting a device. I need some help :'(
Click to expand...
Click to collapse
Hi.
You command is a little off.
adb pull /dev/block/mmcblk0p31/by-name/boot boot.img
The by-name directory shows the symlink to the actual partition.
boot -> /dev/block/mmcblk0p31
You need to make an image file from the actual partition.
Using adb to pull the partition into an image file, the command would be.
adb pull /dev/block/mmcblk0p31 boot.img
Cheers.
ipdev said:
Hi.
You command is a little off.
adb pull /dev/block/mmcblk0p31/by-name/boot boot.img
The by-name directory shows the symlink to the actual partition.
boot -> /dev/block/mmcblk0p31
You need to make an image file from the actual partition.
Using adb to pull the partition into an image file, the command would be.
adb pull /dev/block/mmcblk0p31 boot.img
Cheers.
Click to expand...
Click to collapse
Thanks for helping me but I am still getting errors
Code:
[[email protected] 16:10 Downloads]$ adb pull /dev/block/mmcblk0p31 boot.img
adb: error: failed to stat remote object '/dev/block/mmcblk0p31': Permission denied
[[email protected] 16:10 Downloads]$
You'd need a rooted adb to be able to pull a partition.
Try simply with a adb shell.
You probably can't do that either.
Code:
archissexy$ adb shell
$ dd if=/dev/block/mmcblk0p31 of=/sdcard/boot.img
(probably says Permission denied)
$ su
(probably says Not found)
Renate said:
You'd need a rooted adb to be able to pull a partition.
Try simply with a adb shell.
You probably can't do that either.
Code:
archissexy$ adb shell
$ dd if=/dev/block/mmcblk0p31 of=/sdcard/boot.img
(probably says Permission denied)
$ su
(probably says Not found)
Click to expand...
Click to collapse
Then can i install boot.img of my vivo device as mentioned in my main post ? I am not sure if it is compatible with my device.
prorounak said:
I am not sure if it is compatible with my device.
Click to expand...
Click to collapse
You can try to Magisk convert the older image.
Don't flash it, just fastboot boot magisk-12345678.img