Booting is CONFIRMED! Flashing not possible due to recovery partition non-existant.
https://androidfilehost.com/?fid=11410963190603864372
To flash this you need an unlocked bootloader and adb files
Do the following command; fastboot boot twrp-deen-0.img
I'm NOT responsible if you brick your device. Warranty is COMPLETELY void! You have been warned.
Every single peice of credit goes to the one, the only; @Alberto97 he got TWRP to boot on our device, l personly don't own the device yet, but people tested and booting is confirmed.
This is how to remove data encryption; https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595 if you can help out our device, please attempt to follow this guide to remove data encryption and make a backup of our device.
Deleted
The recovery at the Motorola Ona runs over the boot.img so you have to use the command:
fastboot boot <imagename.img>
I'll test it later, but I suspect it's not working.
Deleted
bb2k22 said:
The recovery at the Motorola Ona runs over the boot.img so you have to use the command:
fastboot boot <imagename.img>
I'll test it later, but I suspect it's not working.
Click to expand...
Click to collapse
Progress?
There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed.
Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal
Alberto97 said:
There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed.
Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal
Click to expand...
Click to collapse
Wow! Your a legend! Tysm!
Alberto97 said:
There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed.
Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal
Click to expand...
Click to collapse
Hi. I haven't tried the TWRP recovery you provided yet. Just wanted to share some partitions. First one is different command but I guess output is pretty much the same.
Code:
deen_sprout:/ $ ls -al dev/block/platform/soc/7824900.sdhci/by-name
total 0
drwxr-xr-x 2 root root 1280 1970-02-02 13:53 .
drwxr-xr-x 4 root root 1360 1970-02-02 13:53 ..
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 aboot_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 aboot_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 apdp -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 boot_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 boot_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cid -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib64_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib64_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib_a -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib_b -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 devcfg_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 devcfg_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dpo -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dsp_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dsp_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dto_a -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dto_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 frp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 fsg_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 fsg_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 hw -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 keymaster_a -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 keymaster_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 kpan -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 logo_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 logo_b -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 logs -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 metadata -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 misc -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modemst1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modemst2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 mota -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 msadp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 oem_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 oem_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 padA -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 prov_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 prov_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 rpm_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 rpm_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 sbl1_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 sbl1_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 sp -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 syscfg -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 system_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 system_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 tz_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-02-02 13:53 tz_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 userdata -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 utags -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 utagsBackup -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vbmeta_a -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vbmeta_b -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vendor_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vendor_b -> /dev/block/mmcblk0p59
deen_sprout:/ $
deen_sprout:/ $ cat /proc/partitions
major minor #blocks name
253 0 524288 zram0
179 0 61071360 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 1792 mmcblk0p5
179 6 1792 mmcblk0p6
179 7 64 mmcblk0p7
179 8 64 mmcblk0p8
179 9 1536 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 192 mmcblk0p17
179 18 192 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 102400 mmcblk0p20
179 21 4 mmcblk0p21
179 22 8 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 2048 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 12288 mmcblk0p30
179 31 12288 mmcblk0p31
259 0 32768 mmcblk0p32
259 1 512 mmcblk0p33
259 2 128 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 16384 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 512 mmcblk0p38
259 7 8192 mmcblk0p39
259 8 65536 mmcblk0p40
259 9 65536 mmcblk0p41
259 10 16384 mmcblk0p42
259 11 16384 mmcblk0p43
259 12 1024 mmcblk0p44
259 13 512 mmcblk0p45
259 14 512 mmcblk0p46
259 15 2048 mmcblk0p47
259 16 256 mmcblk0p48
259 17 256 mmcblk0p49
259 18 8 mmcblk0p50
259 19 64 mmcblk0p51
259 20 64 mmcblk0p52
259 21 13056 mmcblk0p53
259 22 8192 mmcblk0p54
259 23 8192 mmcblk0p55
259 24 196608 mmcblk0p56
259 25 196608 mmcblk0p57
259 26 524288 mmcblk0p58
259 27 524288 mmcblk0p59
259 28 2621440 mmcblk0p60
259 29 2621440 mmcblk0p61
259 30 53813231 mmcblk0p62
179 32 4096 mmcblk0rpmb
252 0 2580508 dm-0
252 1 516068 dm-1
252 2 193500 dm-2
252 3 53813231 dm-3
tys0n said:
Hi. I haven't tried the TWRP recovery you provided yet. Just wanted to share some partitions. First one is different command but I guess output is pretty much the same.
Click to expand...
Click to collapse
Okay! Tell me if it boots ???
borksek said:
Okay! Tell me if it boots
Click to expand...
Click to collapse
I probably won't have time to tamper with it for a few days so I don't think I'll be the first one to try.
Trevligt med en till svensk i denna del av forumet
Nice to see another swede in this part of the forum
tys0n said:
I probably won't have time to tamper with it for a few days so I don't think I'll be the first one to try.
Trevligt med en till svensk i denna del av forumet
Nice to see another swede in this part of the forum
Click to expand...
Click to collapse
Japp haha
Yep haha
Alberto97 said:
There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed.
Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal
Click to expand...
Click to collapse
The output of ls -l dev/block/bootdevice/by-name is following:
Code:
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 DDR -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 aboot_a -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 aboot_b -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 apdp -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 boot_a -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 boot_b -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 carrier -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cid -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib64_a -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib64_b -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib_a -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib_b -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 devcfg_a -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 devcfg_b -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dpo -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dsp_a -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dsp_b -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dto_a -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dto_b -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 frp -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 fsc -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 fsg_a -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 fsg_b -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 hw -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 keymaster_a -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 keymaster_b -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 kpan -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 logo_a -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 logo_b -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 logs -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 metadata -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 misc -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modem_a -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modem_b -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modemst1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modemst2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 mota -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 msadp -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 oem_a -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 oem_b -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 padA -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 persist -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 prov_a -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 prov_b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 rpm_a -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 rpm_b -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 sbl1_a -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 sbl1_b -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 sp -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 syscfg -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 system_a -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 system_b -> /dev/block/mmcblk0p61
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 tz_a -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 1970-01-01 03:56 tz_b -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 userdata -> /dev/block/mmcblk0p62
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 utags -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 utagsBackup -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vbmeta_a -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vbmeta_b -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vendor_a -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vendor_b -> /dev/block/mmcblk0p59
Unfortunately I don't have root so I can't execute the second one.
But TWRP booted up!
Polyparadox said:
Unfortunately I don't have root so I can't execute the second one.
But TWRP booted up!
Click to expand...
Click to collapse
That's good news! Did you try to perform any actions, or check if MTP etc was working?
tys0n said:
That's good news! Did you try to perform any actions, or check if MTP etc was working?
Click to expand...
Click to collapse
I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption.
Mounting seemed to work fine (not for internal- external- and USB OTG storage).
I forgot to check MTP but I don't think that it'll work because of the encryption.
I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt.
Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here.
Edit: Here's what /proc/partitions looks like:
Code:
179 0 61071360 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 1792 mmcblk0p5
179 6 1792 mmcblk0p6
179 7 64 mmcblk0p7
179 8 64 mmcblk0p8
179 9 1536 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 192 mmcblk0p17
179 18 192 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 102400 mmcblk0p20
179 21 4 mmcblk0p21
179 22 8 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 2048 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 12288 mmcblk0p30
179 31 12288 mmcblk0p31
259 0 32768 mmcblk0p32
259 1 512 mmcblk0p33
259 2 128 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 16384 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 512 mmcblk0p38
259 7 8192 mmcblk0p39
259 8 65536 mmcblk0p40
259 9 65536 mmcblk0p41
259 10 16384 mmcblk0p42
259 11 16384 mmcblk0p43
259 12 1024 mmcblk0p44
259 13 512 mmcblk0p45
259 14 512 mmcblk0p46
259 15 2048 mmcblk0p47
259 16 256 mmcblk0p48
259 17 256 mmcblk0p49
259 18 8 mmcblk0p50
259 19 64 mmcblk0p51
259 20 64 mmcblk0p52
259 21 13056 mmcblk0p53
259 22 8192 mmcblk0p54
259 23 8192 mmcblk0p55
259 24 196608 mmcblk0p56
259 25 196608 mmcblk0p57
259 26 524288 mmcblk0p58
259 27 524288 mmcblk0p59
259 28 2621440 mmcblk0p60
259 29 2621440 mmcblk0p61
259 30 53813231 mmcblk0p62
179 32 4096 mmcblk0rpmb
Polyparadox said:
I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption.
Mounting seemed to work fine (not for internal- external- and USB OTG storage).
I forgot to check MTP but I don't think that it'll work because of the encryption.
I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt.
Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here.
Click to expand...
Click to collapse
We need to have a way to skip it aka no-verity or force-decrypt. We don't have a developer who can do this. @Alberto97 helped us getting twrp and I don't think he has any more intentions of helping. But he gave us a super head up! What a legend ❤
borksek said:
We need to have a way to skip it aka no-verity or force-decrypt. We don't have a developer who can do this. @Alberto97 helped us getting twrp and I don't think he has any more intentions of helping. But he gave us a super head up! What a legend
Click to expand...
Click to collapse
Man, I wish I had the skills to port TWRP. But yeah that's true, a huge thank you to @Alberto97!
Also look at my last post in this thread, I've got the partitions.
Does anyone have the guts to flash the twrp image?? The command is "fastboot flash recovery twrp-dean-0.img
Polyparadox said:
I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption.
Mounting seemed to work fine (not for internal- external- and USB OTG storage).
I forgot to check MTP but I don't think that it'll work because of the encryption.
I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt.
Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here.
Edit: Here's what /proc/partitions looks like:
Code:
179 0 61071360 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 1792 mmcblk0p5
179 6 1792 mmcblk0p6
179 7 64 mmcblk0p7
179 8 64 mmcblk0p8
179 9 1536 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 192 mmcblk0p17
179 18 192 mmcblk0p18
179 19 102400 mmcblk0p19
179 20 102400 mmcblk0p20
179 21 4 mmcblk0p21
179 22 8 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 32 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 2048 mmcblk0p28
179 29 2048 mmcblk0p29
179 30 12288 mmcblk0p30
179 31 12288 mmcblk0p31
259 0 32768 mmcblk0p32
259 1 512 mmcblk0p33
259 2 128 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 16384 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 512 mmcblk0p38
259 7 8192 mmcblk0p39
259 8 65536 mmcblk0p40
259 9 65536 mmcblk0p41
259 10 16384 mmcblk0p42
259 11 16384 mmcblk0p43
259 12 1024 mmcblk0p44
259 13 512 mmcblk0p45
259 14 512 mmcblk0p46
259 15 2048 mmcblk0p47
259 16 256 mmcblk0p48
259 17 256 mmcblk0p49
259 18 8 mmcblk0p50
259 19 64 mmcblk0p51
259 20 64 mmcblk0p52
259 21 13056 mmcblk0p53
259 22 8192 mmcblk0p54
259 23 8192 mmcblk0p55
259 24 196608 mmcblk0p56
259 25 196608 mmcblk0p57
259 26 524288 mmcblk0p58
259 27 524288 mmcblk0p59
259 28 2621440 mmcblk0p60
259 29 2621440 mmcblk0p61
259 30 53813231 mmcblk0p62
179 32 4096 mmcblk0rpmb
Click to expand...
Click to collapse
Yeah, We need to format data and then patch boot and fstab so that forced encryption gets disabled so that we can mount data in TWRP.
This should probably work Universal DM-Verity, ForceEncrypt, Disk Quota Disablers
tys0n said:
I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption.
Mounting seemed to work fine (not for internal- external- and USB OTG storage).
I forgot to check MTP but I don't think that it'll work because of the encryption.
I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt.
Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here.
Edit: Here's what /proc/partitions looks like:
Yeah, We need to format data and then patch boot and fstab so that forced encryption gets disabled so that we can mount data in TWRP.
This should probably work Universal DM-Verity, ForceEncrypt, Disk Quota Disablers
Click to expand...
Click to collapse
Try it and post results! Mildly interested
borksek said:
Does anyone have the guts to flash the twrp image?? The command is "flashboot flash recovery twrp-dean-0.img
Click to expand...
Click to collapse
Recovery is not a valid partition. I always use "fastboot boot twrp-dean-0.img" to boot up twrp.
tys0n said:
Yeah, We need to format data and then patch boot and fstab so that forced encryption gets disabled so that we can mount data in TWRP.
This should probably work Universal DM-Verity, ForceEncrypt, Disk Quota Disablers
Click to expand...
Click to collapse
I'll back up my phone and try it out right now
Related
I've pulled a few and have been decompiled them. Anybody have a little link to all pulled partitions so I can do some reverse engineering? I see our parameters partition has very few values in it. Also interested in any of the stock Knox files as well.....
Sent from my SM-G900T using XDA Free mobile app
omgbossis21 said:
Anybody have a little link to all pulled partitions
Click to expand...
Click to collapse
You could have easily found this by searching the forum.
Google search: partition dump sm-g900t xda
[email protected]:/ # cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 64 mmcblk0p4
179 5 32 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 7136 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 14336 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 13312 mmcblk0p15
179 16 15360 mmcblk0p16
179 17 13312 mmcblk0p17
179 18 7159 mmcblk0p18
179 19 1 mmcblk0p19
179 20 8 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 9216 mmcblk0p22
179 23 2536448 mmcblk0p23
179 24 512000 mmcblk0p24
179 25 12150767 mmcblk0p25
179 32 512 mmcblk0rpmb
179 64 7761920 mmcblk1
179 65 7760896 mmcblk1p1
[email protected]:/ #
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2014-03-03 14:11 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-03-03 14:11 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-03-03 14:11 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-03-03 14:11 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-03-03 14:11 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-03-03 14:11 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-03-03 14:11 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-03-03 14:11 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-03-03 14:11 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-03-03 14:11 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-03-03 14:11 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-03-03 14:11 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-03-03 14:11 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-03-03 14:11 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-03-03 14:11 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-03-03 14:11 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-03-03 14:11 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-03-03 14:11 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-03-03 14:11 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-03-03 14:11 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-03-03 14:11 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-03-03 14:11 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-03-03 14:11 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-03-03 14:11 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-03-03 14:11 userdata -> /dev/block/mmcblk0p25
[email protected]:/ #
.
Sorry about that I meant hosted lol If I recall their were a few apps that involved knox that was the stock rom, I would like to disassemble those too. I have a few of the partitions and other files that caught my eye, suppose I can use this thread and start hosting some and others can jump in and help too.
Param Partition : https://www.dropbox.com/s/ejscttfivnke0ad/mmcblk0p11
My pc is currently a fresh setup so I have to reinstall apk multi-tool and set it up and all. In the meantime here are the knox associated apks if anybody wants to dissect them for my while I got through some of these partitions. I pulled them all if anyone is interested in them let me know I will host them.
https://www.dropbox.com/s/2uc9mqprd6mn84x/knoxstuff.rar
Closing thread until More comes along
This is for Development purposes only so we can get a working recovery
Code:
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
ls -al /dev/block/platform/msm_sdcc.1/by-namels -al /dev/block/platform/msm_sdcc
.1/by-name
lrwxrwxrwx root root 1969-12-31 21:13 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:13 abootf -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:13 boot -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:13 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1969-12-31 21:13 carrier -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1969-12-31 21:13 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:13 dbibak -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:13 drm -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1969-12-31 21:13 eksst -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1969-12-31 21:13 encrypt -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1969-12-31 21:13 factory -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1969-12-31 21:13 fota -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1969-12-31 21:13 fsc -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:13 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:13 grow -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1969-12-31 21:13 laf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1969-12-31 21:13 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1969-12-31 21:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:13 modemst1 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:13 modemst2 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:13 mpt -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1969-12-31 21:13 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:13 pad1 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:13 pad2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:13 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:13 rct -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1969-12-31 21:13 recovery -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:13 rpmbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:13 rpmf -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:13 sbl1b -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:13 sdif -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:13 sns -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1969-12-31 21:13 spare1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:13 spare2 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1969-12-31 21:13 spare3 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1969-12-31 21:13 ssd -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:13 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1969-12-31 21:13 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:13 tzbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:13 tzf -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:13 userdata -> /dev/block/mmcblk0p43
[email protected]:/ #
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 4 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 512 mmcblk0p10
179 11 1024 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 512 mmcblk0p15
179 16 2048 mmcblk0p16
179 17 2044 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 32768 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 3072 mmcblk0p22
179 23 4 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 4 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 8 mmcblk0p30
179 31 5104 mmcblk0p31
259 0 16384 mmcblk0p32
259 1 32768 mmcblk0p33
259 2 32768 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 24576 mmcblk0p40
259 9 2949120 mmcblk0p41
259 10 868352 mmcblk0p42
259 11 26324474 mmcblk0p43
259 12 501 mmcblk0p44
179 32 4096 mmcblk0rpmb
179 64 15558144 mmcblk1
179 65 15557120 mmcblk1p1
Benny3 is here.. that's a real good sign for recovery!
budeone said:
Benny3 is here.. that's a real good sign for recovery!
Click to expand...
Click to collapse
I have never compiled a recovery before, Not sure if i want to try...lol
I got some guys that are familiar in this area...I just linked the thread to them...so maybe they can work some magic.
still gotta wait on unlocked boot loader
Sent from my LGLS990 using Tapatalk
matthew0776 said:
I got some guys that are familiar in this area...I just linked the thread to them...so maybe they can work some magic.
still gotta wait on unlocked boot loader
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Yeah it didnt dawn on me it had a locked bootloader, Seems odd that sprint has it locked
benny3 said:
Yeah it didnt dawn on me it had a locked bootloader, Seems odd that sprint has it locked
Click to expand...
Click to collapse
Right on..I know tmo comes unlocked. But I think Unlocked Boot loader is close. And I have some guys willing to try and build TWRP for ls990
Sent from my LGLS990 using Tapatalk
I have never had to mess around with Loki. Doesn't Philz recovery address loki?
benny3 said:
I have never had to mess around with Loki. Doesn't Philz recovery address loki?
Click to expand...
Click to collapse
tbh...not sure...I just passed the info to some guys I know that have some exp With recoveries. I'm more of a theme and Rom (AOSP) guy..lol This is my first LG so most these unlock and root processes are new to me.
But looking forward to getting some CANDY on this G3 !!
Sent from my LGLS990 using Tapatalk
Guy's just to let you know that root for the LG G3 for Sprint is out and no computer needed just installed an app, got mine rooted now and installed viper4android sound mod and is working perfect
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
http://forum.xda-developers.com/showthread.php?t=2850906
DR0IDMANIAC said:
Guy's just to let you know that root for the LG G3 for Sprint is out and no computer needed just installed an app, got mine rooted now and installed viper4android sound mod and is working perfect
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
Viper dont increase volume
Sent from my LGLS990 using XDA Premium HD app
DR0IDMANIAC said:
Guy's just to let you know that root for the LG G3 for Sprint is out and no computer needed just installed an app, got mine rooted now and installed viper4android sound mod and is working perfect
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
http://forum.xda-developers.com/showthread.php?t=2850906
Click to expand...
Click to collapse
We know that. This is for once the bootloader is unlocked
Sent from my LGLS990 using XDA Free mobile app
matthew0776 said:
Right on..I know tmo comes unlocked. But I think Unlocked Boot loader is close. And I have some guys willing to try and build TWRP for ls990
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
If only tdhite were here. His TWRP for the M7 was and is first rate.
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
pbedard said:
Viper dont increase volume
Sent from my LGLS990 using XDA Premium HD app
Click to expand...
Click to collapse
There's a thread around that tells how to increase volume using the build.prop, but I'm way too nervous to mess with my phone until I can Nandroid it.
slyest12 said:
If only tdhite were here. His TWRP for the M7 was and is first rate.
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
There's a thread around that tells how to increase volume using the build.prop, but I'm way too nervous to mess with my phone until I can Nandroid it.
Click to expand...
Click to collapse
I woulnt i messed up one n returned it
Sent from my LGLS990 using XDA Premium rHD app
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
deadman96385 said:
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Click to expand...
Click to collapse
Do you still need this done..?.. I have the Verizon Version of the Galaxy View.
justjayhere said:
Do you still need this done..?.. I have the Verizon Version of the Galaxy View.
Click to expand...
Click to collapse
I have gotten the sizes still working on getting twrp to boot.
deadman96385 said:
I have gotten the sizes still working on getting twrp to boot.
Click to expand...
Click to collapse
I am looking forward to getting root for Galaxy View.
justjayhere said:
I am looking forward to getting root for Galaxy View.
Click to expand...
Click to collapse
@ashyx and I have gotten the wifi variant to boot twrp can you grab the partition sizes for your tablet just run these commands and paste there output here or in a pastebin
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
cat /proc/partitions
deadman96385 said:
@ashyx and I have gotten the wifi variant to boot twrp can you grab the partition sizes for your tablet just run these commands and paste there output here or in a pastebin
Click to expand...
Click to collapse
I will do so later today...currently out of town.
Verizon 4G 64GB version Partition Info
deadman96385 said:
I am getting a Galaxy View on Monday but in the mean time i have made a basic twrp tree can someone run these commands on there device so i can get the partition sizes .
Code:
adb shell
ls -al /dev/block/platform/13540000.dwmmc0/by-name
Click to expand...
Click to collapse
Verizon 4G 64GB version...
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ ls -al /dev/block/platform/13540000.dwmmc0/by-name
ls -al /dev/block/platform/13540000.dwmmc0/by-name
lrwxrwxrwx root root 2016-10-06 15:51 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-10-06 15:51 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-10-06 15:51 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-10-06 15:51 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-10-06 15:51 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-10-06 15:51 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-10-06 15:51 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-10-06 15:51 DNT -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-10-06 15:51 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-10-06 15:51 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-10-06 15:51 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-10-06 15:51 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-10-06 15:51 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-10-06 15:51 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-10-06 15:51 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-10-06 15:51 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-10-06 15:51 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-10-06 15:51 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-10-06 15:51 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs3 -> /dev/block/mmcblk0p7
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 15360 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 32768 mmcblk0p10
259 3 38912 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 4096 mmcblk0p13
259 6 90112 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 512 mmcblk0p17
259 10 12288 mmcblk0p18
259 11 2560 mmcblk0p19
259 12 3072000 mmcblk0p20
259 13 1048576 mmcblk0p21
259 14 56676352 mmcblk0p22
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1048576 vnswap0
[email protected]:/ $
justjayhere said:
Verizon 4G 64GB version...
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ $ ls -al /dev/block/platform/13540000.dwmmc0/by-name
ls -al /dev/block/platform/13540000.dwmmc0/by-name
lrwxrwxrwx root root 2016-10-06 15:51 BOOT -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-10-06 15:51 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-10-06 15:51 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-10-06 15:51 CACHE -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2016-10-06 15:51 CARRIER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-10-06 15:51 CDMA-RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-10-06 15:51 CPEFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-10-06 15:51 DNT -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-10-06 15:51 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-10-06 15:51 OTA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-10-06 15:51 PARAM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-10-06 15:51 PERSDATA -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2016-10-06 15:51 PERSISTENT -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-10-06 15:51 RADIO -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-10-06 15:51 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-10-06 15:51 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-10-06 15:51 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-10-06 15:51 TOMBSTONES -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-10-06 15:51 USERDATA -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-10-06 15:51 m9kefs3 -> /dev/block/mmcblk0p7
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 4096 mmcblk0p7
259 0 15360 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 32768 mmcblk0p10
259 3 38912 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 4096 mmcblk0p13
259 6 90112 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 512 mmcblk0p17
259 10 12288 mmcblk0p18
259 11 2560 mmcblk0p19
259 12 3072000 mmcblk0p20
259 13 1048576 mmcblk0p21
259 14 56676352 mmcblk0p22
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 1048576 vnswap0
[email protected]:/ $
Click to expand...
Click to collapse
I would say try the wifi build but i can't recommend it due to there not being any firmware builds for the Verizon variant so i can't get a stock recovery image from it in case it doesn't work.
What happened is, I've been using cm13 for sm-a300h for a couple of weeks now. I have a 16gb external sd card, and as I needed more memory, I've bought a new 64gb one. As soon as I placed it in the slot, the phone recognized it, and I selected, by mistake, to use it as an internal storage unit. The process got bugged somewhere in the middle, and it crashed.
Assuming there was nothing else to do, I re-inserted the same memory card, and it wasn't recognized. After a few attempts, I tried the old one (16gb one which was working fine before), which wasn't recognized as well. Thinking it was a system's fault, I even flashed the rom, erasing all the data, but to no avail. Even trwp doesn't recognize the sd card. As I'm not really experienced with this, and I don't have any idea what to do next, any help is appreciated. If anyone needs any further info, I'll gladly provide it.
@AbominableSnowman check mmc in other devices and check the status. If it works in other device try to put back in and check
It works on other devices, tried that.
Side note: I've found a thread where a guy had a problem similar to mine. Seems that I've deleted my partition layout, or at least did something to it. I've mad a mistake trying to format my external memory, and deleted things I wasn't supposed to. After I saw the thread, I've tried flashing pit, as well as the rest of the stock rom, but still no luck...
Here's what I got from adb:
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 16 mmcblk0p10
179 11 10768 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 15360 mmcblk0p17
179 18 5121 mmcblk0p18
179 19 7159 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 9216 mmcblk0p23
179 24 1781760 mmcblk0p24
179 25 512000 mmcblk0p25
179 26 71680 mmcblk0p26
179 27 12834796 mmcblk0p27
179 32 4096 mmcblk0rpmb
253 0 524288 vnswap0
Click to expand...
Click to collapse
As far as I know, this seems to be in order. I was thinking of getting a new pit file, but this seems to be fine.
Edit:
lrwxrwxrwx root root 2014-06-12 02:36 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-06-12 02:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-06-12 02:36 backup -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-06-12 02:36 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-06-12 02:36 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-06-12 02:36 ddr -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-06-12 02:36 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-06-12 02:36 fota -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-06-12 02:36 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-06-12 02:36 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-06-12 02:36 hidden -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-06-12 02:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-06-12 02:36 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-06-12 02:36 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-06-12 02:36 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-06-12 02:36 param -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-06-12 02:36 persdata -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-06-12 02:36 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-06-12 02:36 qhee -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-06-12 02:36 qsee -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-06-12 02:36 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-06-12 02:36 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-06-12 02:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-06-12 02:36 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-06-12 02:36 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-06-12 02:36 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-06-12 02:36 userdata -> /dev/block/mmcblk0p27
Click to expand...
Click to collapse
I've come across this thread: http://forum.xda-developers.com/showthread.php?t=1949372
When i try to echo the partition, i get the following error:
/system/bin/sh: /data: can't execute: Is a directory
Click to expand...
Click to collapse
Edit: It seems that /usb_mass_storage doesn't exist at all. Is there a way to manually add it? It seems that there is no longer a reference point to external memory at all...
Hi, i am trying to dump the boot.img from a Huawei P Smart to flash it in another phone of the same model whose boot.img has been corrupted.
So most of the tutorials i have found on internet suggest to use this command:
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
The problem is that there isn't any device named boot in the by-name directory, so i get a no such file or directory error.
I have also seen some tutorials checking the /proc/mtd file, but it is empty.
Help
You're probably A/B. Did you check for boot_a and boot_b?
Are you rooted? You need that for dd.
Renate said:
You're probably A/B. Did you check for boot_a and boot_b?
Are you rooted? You need that for dd.
Click to expand...
Click to collapse
What means being A/B? Is boot_a or b in the same directory of the normal boot image? I am not rooted because when i flashed the Magisk zip the boot.img got corrupted, so i want to make a backup boot.img first.
I don't know if this can help but I used the PotatoNV method to unlock the bootloader and when I selected the Kirin version i selected 65x (B).
This is the error i am getting in my phone: https://forum.xda-developers.com/t/...mode-after-flashing-magisk-from-twrp.4535311/
Edit: I have checked the by-name directory but there isn't neither boot_a nor boot_b, the only device which starts with boot is bootfail_info.
Renate said:
You're probably A/B. Did you check for boot_a and boot_b?
Are you rooted? You need that for dd.
Click to expand...
Click to collapse
I have made a list of all the files in the /dev/block/bootdevice/by-name/ directory: https://pastebin.com/6VXpNWeM
read Huawei section (deleted)
https://web.archive.org/web/20200922111028/https://topjohnwu.github.io/Magisk/install.html
aIecxs said:
read Huawei section
Installation
A Magic Mask to Alter Android System Systemless-ly
web.archive.org
Click to expand...
Click to collapse
Yes so I should find an update for the FIG-LX1 and extract a boot image from it.
The problem is that i have downloaded the update from Huawei Firmware, but inside i have found another phone model. (FIG-L31 if i remember well, are them the same thing?)
aIecxs said:
read Huawei section
Installation
A Magic Mask to Alter Android System Systemless-ly
web.archive.org
Click to expand...
Click to collapse
I have downloaded the Huawei Update Extractor to extract the .app file.
I am assuming that FIG-LX1 and LA1 are the same thing.
So what should i extract from that file?
In the update i have downloaded, in the dload directory there are FIG-L31_hw_eu and a file named update_sd.zip
aIecxs said:
read Huawei section (deleted)
https://web.archive.org/web/20200922111028/https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
So i have found the UPDATE.APP file in update_sd.zip, i have extracted it and now i am trying to open it in the update extractor.
I have got this error (Profile set to Unknown (worstenbrood)):
RECOVERY_RAMDIS.img: invalid header crc - Expected: 21611 Got: 49278
aIecxs said:
read Huawei section (deleted)
https://web.archive.org/web/20200922111028/https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Ok, solved it by disabling verifications in the Huawei Update Extractor settings.
LOL skipping checksum won't solve the issue. why don't you dump ramdisk.img off device with IDT Flash Tool?
if you post output of /proc/partitions we may able to help identify ramdisk partition.
Code:
# cat /proc/partitions
aIecxs said:
LOL skipping checksum won't solve the issue. why don't you dump ramdisk.img off device with IDT Flash Tool?
Click to expand...
Click to collapse
Now the Update Extractor works. And why should i extract ramdisk?
aIecxs said:
LOL skipping checksum won't solve the issue. why don't you dump ramdisk.img off device with IDT Flash Tool?
if you post output of /proc/partitions we may able to help identify ramdisk partition.
Code:
# cat /proc/partitions
Click to expand...
Click to collapse
Is it possible to use adb from TWRP? Because I cant paste it here if i run the command from the TWRP terminal.
yes official TWRP has adb root enabled by default. on terminal you can redirect output > to file
Code:
# cat /proc/partitions > /external_sd/partitions.txt
aIecxs said:
yes official TWRP has adb root enabled by default. on terminal you can redirect output > to file
Click to expand...
Click to collapse
This is the output:
Code:
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
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 47104 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 12288 mmcblk0p27
179 28 24576 mmcblk0p28
179 29 32768 mmcblk0p29
179 30 16384 mmcblk0p30
179 31 24576 mmcblk0p31
179 32 12288 mmcblk0p32
179 33 32768 mmcblk0p33
179 34 16384 mmcblk0p34
179 35 28672 mmcblk0p35
179 36 4096 mmcblk0p36
179 37 98304 mmcblk0p37
179 38 1024 mmcblk0p38
179 39 1024 mmcblk0p39
179 40 12288 mmcblk0p40
179 41 16384 mmcblk0p41
179 42 4096 mmcblk0p42
179 43 131072 mmcblk0p43
179 44 131072 mmcblk0p44
179 45 2048 mmcblk0p45
179 46 2048 mmcblk0p46
179 47 4096 mmcblk0p47
259 0 32768 mmcblk0p48
259 1 2048 mmcblk0p49
259 2 16384 mmcblk0p50
259 3 30720 mmcblk0p51
259 4 2367488 mmcblk0p52
259 5 1130496 mmcblk0p53
259 6 32768 mmcblk0p54
259 7 139264 mmcblk0p55
259 8 32768 mmcblk0p56
259 9 598016 mmcblk0p57
259 10 548864 mmcblk0p58
259 11 24637440 mmcblk0p59
179 144 4096 mmcblk0rpmb
179 96 4096 mmcblk0boot1
179 48 4096 mmcblk0boot0
aIecxs said:
yes official TWRP has adb root enabled by default. on terminal you can redirect output > to file
Code:
# cat /proc/partitions > /external_sd/partitions.txt
Click to expand...
Click to collapse
But will I be able to fix the other phone by flashing the ramdisk?
I attach the magisk that bricked it.
slx23 said:
I have made a list of all the files in the /dev/block/bootdevice/by-name/ directory: https://pastebin.com/6VXpNWeM
Click to expand...
Click to collapse
Code:
# ls -l /dev/block/bootdevice/by-name/* > /external_sd/names.txt
aIecxs said:
Code:
# ls -l /dev/block/bootdevice/by-name/* > /external_sd/names.txt
Click to expand...
Click to collapse
Output:
Code:
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/bootfail_info -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/cache -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/cust -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/dfx -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/dto -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/dts -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/eng_system -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/eng_vendor -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_kernel -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_ramdisk -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_vbmeta -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/erecovery_vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/hisitest0 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/hisitest1 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/hisitest2 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/kernel -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modem_fw -> /dev/block/mmcblk0p37lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modem_om -> /dev/block/mmcblk0p18lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modem_secure -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/odm -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/patch -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/preas -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/preavs -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/preload -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/product -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/recovery_ramdisk -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/recovery_vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/recovery_vendor -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved3 -> /dev/block/mmcblk0p9lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/reserved9 -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/rrecord -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/system -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/userdata -> /dev/block/mmcblk0p59lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/vbmeta -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/vendor -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 21 Jul 6 11:05 /dev/block/bootdevice/by-name/version -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jul 6 11:05 /dev/block/bootdevice/by-name/vrl_backup -> /dev/block/mmcblk0p2
aIecxs said:
Code:
# ls -l /dev/block/bootdevice/by-name/* > /external_sd/names.txt
Click to expand...
Click to collapse
And how should i flash magisk if there isnt a boot image?
"boot" = kernel + ramdisk
I would expect there exist any 32768 KB mmcblk0p? partition for ramdisk, but seems that device doesn't have ramdisk in "boot" and therefore no separate ramdisk partition at all.
so what you're looking for is kernel.img (without ramdisk)
for rooting with Magisk you need to patch twrp.img, flash to recovery_ramdisk (mmcblk0p33) and boot into recovery all the time.
aIecxs said:
"boot" = kernel + ramdisk
I would expect there exist any 32768 KB mmcblk0p? partition for ramdisk, but seems that device doesn't have ramdisk in "boot" and therefore no separate ramdisk partition at all.
so what you're looking for is kernel.img (without ramdisk)
for rooting with Magisk you need to patch twrp.img, flash to recovery_ramdisk (mmcblk0p33) and boot into recovery all the time.
Click to expand...
Click to collapse
So wait, to unbrick that phone i have to flash the kernel.img?
And what do you mean with booting to recovery every time?
Also what that magisk zip patched if there isn't a boot image?