I don't know if anyone need it but here it is
Code:
Model: MMC DF4032 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 786kB 262kB vrl
2 786kB 1049kB 262kB vrl_backup
3 1049kB 1311kB 262kB fw_lpm3
4 1311kB 2097kB 786kB frp
5 2097kB 6291kB 4194kB fastboot
6 6291kB 10.5MB 4194kB modemnvm_factory
7 10.5MB 16.8MB 6291kB nvme
8 16.8MB 83.9MB 67.1MB oeminfo
9 83.9MB 88.1MB 4194kB reserved3
10 88.1MB 92.3MB 4194kB modemnvm_backup
11 92.3MB 101MB 8389kB ext4 modemnvm_img
12 101MB 105MB 4194kB modemnvm_system
13 105MB 138MB 33.6MB ext4 secure_storage
14 138MB 141MB 2097kB reserved4
15 141MB 143MB 2097kB reserved5
16 143MB 145MB 2097kB persist
17 145MB 159MB 14.7MB ext4 modem_secure
18 159MB 193MB 33.6MB ext4 modem_om
19 193MB 260MB 67.1MB ext4 splash2
20 260MB 262MB 2097kB misc
21 262MB 287MB 25.2MB modemnvm_update
22 287MB 354MB 67.1MB recovery2
23 354MB 417MB 62.9MB reserved2
24 417MB 422MB 4194kB teeos
25 422MB 424MB 2097kB trustfirmware
26 424MB 440MB 16.8MB sensorhub
27 440MB 453MB 12.6MB fw_hifi
28 453MB 487MB 33.6MB boot
29 487MB 554MB 67.1MB recovery
30 554MB 587MB 33.6MB dts
31 587MB 688MB 101MB ext4 modem_fw
32 688MB 690MB 2097kB reserved7
33 690MB 692MB 2097kB reserved8
34 692MB 709MB 16.8MB dfx
35 709MB 713MB 4194kB vbmeta
36 713MB 981MB 268MB ext4 cache
37 981MB 984MB 2097kB hisitest0
38 984MB 986MB 2097kB hisitest1
39 986MB 990MB 4194kB hisitest2
40 990MB 1023MB 33.6MB patch
41 1023MB 1026MB 2097kB bootfail_info
42 1026MB 1042MB 16.8MB rrecord
43 1042MB 1074MB 31.5MB reserved9
44 1074MB 5989MB 4916MB ext4 system
45 5989MB 6191MB 201MB ext4 cust
46 6191MB 6224MB 33.6MB ext4 version
47 6224MB 7046MB 822MB ext4 vendor
48 7046MB 7248MB 201MB ext4 product
49 7248MB 31.3GB 24.0GB userdata
Code:
lrwxrwxrwx 1 root root 21 Dec 24 10:46 boot -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Dec 24 10:46 bootfail_info -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Dec 24 10:46 cache -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Dec 24 10:46 cust -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Dec 24 10:46 dfx -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Dec 24 10:46 dts -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 20 Dec 24 10:46 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Dec 24 10:46 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Dec 24 10:46 fw_hifi -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Dec 24 10:46 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Dec 24 10:46 hisitest0 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Dec 24 10:46 hisitest1 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Dec 24 10:46 hisitest2 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Dec 24 10:46 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modem_fw -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modem_secure -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Dec 24 10:46 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Dec 24 10:46 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Dec 24 10:46 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Dec 24 10:46 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Dec 24 10:46 patch -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Dec 24 10:46 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Dec 24 10:46 product -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Dec 24 10:46 recovery -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Dec 24 10:46 recovery2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Dec 24 10:46 reserved2 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Dec 24 10:46 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 24 10:46 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Dec 24 10:46 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 24 10:46 reserved7 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Dec 24 10:46 reserved8 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Dec 24 10:46 reserved9 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Dec 24 10:46 rrecord -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Dec 24 10:46 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Dec 24 10:46 sensorhub -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Dec 24 10:46 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Dec 24 10:46 system -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Dec 24 10:46 teeos -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Dec 24 10:46 trustfirmware -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Dec 24 10:46 userdata -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vbmeta -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Dec 24 10:46 vendor -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Dec 24 10:46 version -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 20 Dec 24 10:46 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Dec 24 10:46 vrl_backup -> /dev/block/mmcblk0p2
Join Telegram group if you are willing to test latest stuff.
reserved
i m not pro but does it means project treble supported since it has separate vendor partition
Mohan0004 said:
i m not pro but does it means project treble supported since it has separate vendor partition
Click to expand...
Click to collapse
Yes it should support treble on oreo launch
Sent from my BND-AL10 using Tapatalk
Related
Hi everyone, any developer who wants to help, and you have the sources to compile a custom recovery like CWM or TWRP recovery for Alcate Scribe Easy ...
these are the specs build. prop of the device:
ro.build.id=JZO54K
ro.build.display.id=JZO54K
ro.build.version.incremental=v196-0
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Fri Jan 10 12:04:30 CST 2014
ro.build.date.utc=1389326670
ro.build.type=user
ro.build.user=sl_nb_zpxiang
ro.build.host=50721-1
ro.build.tags=release-keys
ro.product.model=ALCATEL ONE TOUCH 8000A
ro.product.brand=TCT
ro.product.name=Scribe5
ro.product.device=Scribe5_gsm
ro.product.board=7x27
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=TCT
ro.tct.device=scribe5
ro.tct.operator=
ro.wifi.channels=
ro.board.platform=msm7627a
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Scribe5_gsm
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Scribe5-user 4.1.2 JZO54K v196-0 release-keys
ro.build.fingerprint=TCT/Scribe5/Scribe5_gsm:4.1.2/JZO54K/v196-0:user/release-keys
ro.build.characteristics=default
My partitions:
[email protected]:~# adb shell
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 3776512 mmcblk0
179 1 204800 mmcblk0p1
179 2 20 mmcblk0p2
179 3 300 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1000 mmcblk0p5
179 6 1000 mmcblk0p6
179 7 2000 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 307200 mmcblk0p14
179 15 409600 mmcblk0p15
179 16 20480 mmcblk0p16
179 17 122880 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 1000 mmcblk0p19
179 20 1000 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 2610320 mmcblk0p22
179 32 7639040 mmcblk1
179 33 7634944 mmcblk1p1
[email protected]:/ #
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.3/by-name
lrwxrwxrwx root root 2014-07-25 09:02 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-07-25 09:02 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-07-25 09:02 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-07-25 09:02 cfgdata -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-07-25 09:02 custpack -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-07-25 09:02 fota -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-07-25 09:02 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-07-25 09:02 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-07-25 09:02 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-07-25 09:02 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-07-25 09:02 oemsbl -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-07-25 09:02 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-07-25 09:02 qcsbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-07-25 09:02 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-07-25 09:02 ssd -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-07-25 09:02 studypara -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-07-25 09:02 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-07-25 09:02 traceability -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-07-25 09:02 tunning -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-07-25 09:02 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-07-25 09:02 watchdog -> /dev/block/mmcblk0p21
[email protected]:/ #
Stock kernel Sources
someone who wants to help.
any file you want, I can give is for the creation of recovery for this device
I don't know if anyone need it but here it is
Code:
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 bootfail_info -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 cache -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 cust -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 dfx -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 dto -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 dts -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 erecovery_kernel -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 erecovery_ramdisk -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 erecovery_vbmeta -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 erecovery_vendor -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 fastboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 frp -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 fw_hifi -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 fw_lpm3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 hisitest0 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 hisitest1 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 hisitest2 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 kernel -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 misc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modem_fw -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modem_om -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modem_secure -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modemnvm_backup -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 modemnvm_factory -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modemnvm_img -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modemnvm_system -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 modemnvm_update -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 nvme -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 odm -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 oeminfo -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 patch -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 product -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 ramdisk -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 recovery_ramdisk -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 recovery_vbmeta -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 recovery_vendor -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 reserved2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 reserved3 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 reserved4 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 reserved5 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 reserved8 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 reserved9 -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 rrecord -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 secure_storage -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 sensorhub -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 splash2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 system -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 teeos -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 trustfirmware -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 userdata -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 vbmeta -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 vendor -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-03-16 17:19 version -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 vrl -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2018-03-16 17:19 vrl_backup -> /dev/block/mmcblk0p2
Join Telegram group if you are willing to test latest stuff.
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
Greetings everyone. I'm trying to figure out the size of my userdata partition in my new Cubot Nova running Android 8.1 Oreo.
On older devices I managed to do this by running the following commands:
adb shell ls -al /dev/block/platform/bootdevice/by-name --------------> To list my partitions by name and find the actual userdata partition name. In my case, it's /dev/block/mmcblk0p33
Code:
Z:\Android\devices\Cubot Nova\adb platform-tools>adb shell ls -al /dev/block/platform/bootdevice/by-name
total 0
drwxr-xr-x 2 root root 780 2019-11-28 19:47 .
drwxr-xr-x 4 root root 860 2019-11-28 19:47 ..
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 boot_para -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 cache -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 expdb -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 flashinfo -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 frp -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 gz1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 gz2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 lk -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 lk2 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 loader_ext1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 loader_ext2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 logo -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 mcupmfw -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 md1dsp -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 md1img -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 metadata -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 nvcfg -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 nvdata -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 nvram -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 odmdtbo -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 para -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 23 2019-11-28 19:47 preloader_a -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2019-11-28 19:47 preloader_b -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 proinfo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 protect1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 protect2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 2019-11-28 19:47 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 sdrpmb -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 sec1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 seccfg -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 spmfw -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 system -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 tee1 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 tee2 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2019-11-28 19:47 vendor -> /dev/block/mmcblk0p30
Then I would run tune2fs -l /dev/block/mmcblk0p33 in the shell to get the partition info (block count and block size) to calculate, but it's not working. I get the following error message:
Code:
tune2fs 1.43.3 (04-Sep-2016)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p33
I googled the error message, but I couldn't find anything specific to Android, just Linux. Can someone please help me figure out what I'm doing wrong?.
Is there's another way to get the partition size?
I need it to perform backups with SP Flash Tools. TWRP is unable to decrypt my phone or mount it's internal storage, so that's not an option
Thanks in advance
EDIT: I should have mentioned that the phone is rooted via Magisk, and I run the tune2fs command with superuser access.
Nevermind, I'm dumb. This worked just fine:
blockdev --getsize64 /dev/block/mmcblk0p33
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?