Get bootlogo not found - Android Q&A, Help & Troubleshooting

Hello guys,
i have an allview viva C701 tablet and tried to change the bootlogo image but i didn't manage to extract it.
Using adb and the following command dd if=/dev/logo of=/sdcard/logo.bin bs=3145728 count=1 i get the following error "no such file or directory". examining forward i saw that if i try "#cat /proc/mtd" is returning the same error, after some researching i managed to get the partition table with "cat /proc/partitions" and the result is like this :
major minor #blocks name
253 0 131072 zram0
93 0 32768 nanda
93 8 16384 nandb
93 16 16384 nandc
93 24 2097152 nandd
93 32 16384 nande
93 40 32768 nandf
93 48 786432 nandg
93 56 16384 nandh
93 64 16384 nandi
93 72 81920 nandj
93 80 4358144 nandk
Now i am stuck. can someone help me find the boot logo image? or an original rom ?
any ideas ?
Best regards.

nobody ?

Related

Anyone help me with this: partion table

a dev from Google Play contacted me asking for the "partion layout" for my Galaxy player 5. He replied to my usage data my device sent to him via my email. Can anyone help me help this guy? Much Appreciated
What my device apparently sent to him
This email doesn't contain any personal information.
It only contains technical information needed to improve the quality of the backup on your device.
Your help is very appreciated!
-- TECHNICAL INFORMATION --
Device detected as:
Commercial name: YP-G70
Technical name: YP-G70
Searched patch filename: partlayout4nandroid.YP-G70
Information from Android system
Device brand: samsung
Device technical name: YP-G70
Device commercial name: YP-G70
Device board name: YP-G70
Device hardware name: smdkc110
Firmware version: UEKI8
Android SDK: 10
Partition Table:
major minor #blocks name
7 0 9387 loop0
7 1 3150 loop1
179 0 7757824 mmcblk0
179 1 1 mmcblk0p1
179 5 256 mmcblk0p5
179 6 256 mmcblk0p6
179 7 1280 mmcblk0p7
259 0 1280 mmcblk0p8
259 1 5120 mmcblk0p9
259 2 10240 mmcblk0p10
259 3 7680 mmcblk0p11
259 4 7680 mmcblk0p12
259 5 296960 mmcblk0p13
259 6 137216 mmcblk0p14
259 7 65536 mmcblk0p15
259 8 1970176 mmcblk0p16
259 9 5252096 mmcblk0p17
179 8 31166976 mmcblk1
179 9 31162880 mmcblk1p1
254 0 9387 dm-0
254 1 3150 dm-1
THE MESSAGE HE SENT AS A REPLY
to me
Information about your device is rare on the internet. Would you be able to direct me to a place where I can obtain information about partition layout for that device?
Thanks,
(His name)
Sent from my Xperia Pro
any devs see this let me know if you have any info =)
Sent from my YP-G70 using Tapatalk 2
You could always do a mount command in an adb shell, and send the output but I think he wants all the partitions right?
Sent from my Nexus 7 using Tapatalk HD
zaclimon said:
You could always do a mount command in an adb shell, and send the output but I think he wants all the partitions right?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
no idea lol
LordZilo said:
no idea lol
Click to expand...
Click to collapse
As root (adb or emulator)
Code:
fdisk -l /dev/block/mmcblk0
mount
That's about all the information there is.
Meticulus said:
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 5 969728 7757792 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p5 9 40 256 83 Linux
/dev/block/mmcblk0p6 45 76 256 83 Linux
/dev/block/mmcblk0p7 81 240 1280 83 Linux
/dev/block/mmcblk0p8 245 404 1280 83 Linux
/dev/block/mmcblk0p9 409 1048 5120 83 Linux
/dev/block/mmcblk0p10 1053 2332 10240 83 Linux
/dev/block/mmcblk0p11 2337 3296 7680 83 Linux
/dev/block/mmcblk0p12 3301 4260 7680 83 Linux
/dev/block/mmcblk0p13 4265 41384 296960 83 Linux
/dev/block/mmcblk0p14 41389 58540 137216 83 Linux
/dev/block/mmcblk0p15 58545 66736 65536 83 Linux
/dev/block/mmcblk0p16 66741 313012 1970176 83 Linux
/dev/block/mmcblk0p17 313017 969528 5252096 83 Linux
Click to expand...
Click to collapse
This is the one (from another thread) that I used to repartition mine
thanks

Internal SD info from fdisk - I need it!

Hi,
can somebody post me internal SD info via fdisk in ADB shell for HTC Desire X? I need partition sizes list.
Only for Desire X with ICS for HBOOT 1.24.
I need output from following commands in adb shell:
Code:
~ # fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 473088.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: deleting partitions after 60
Command (m for help):
then type 'u'
Code:
Command (m for help): u
u
Changing display/entry units to sectors
then type 'p'
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 3875 MB, 3875536896 bytes
1 heads, 16 sectors/track, 473088 cylinders, total 7569408 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 41 1128 544 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 7569406 3779639 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 2162686 980991+ 83 Linux
/dev/block/mmcblk0p26 2162688 4685822 1261567+ 83 Linux
/dev/block/mmcblk0p27 4685824 5210110 262143+ 83 Linux
/dev/block/mmcblk0p28 5210112 5258606 24247+ 19 Unknown
/dev/block/mmcblk0p29 5258608 5258749 71 90 Unknown
/dev/block/mmcblk0p30 5258751 5259262 256 23 Unknown
/dev/block/mmcblk0p31 5259264 7569407 1155072 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p32 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p33 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p34 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p35 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p36 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p37 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p38 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p39 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p40 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p41 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p42 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p43 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p44 163328 163839 256 76 Unknown
/dev/block/mmcblk0p45 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p46 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p47 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p48 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p49 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p50 196096 196607 256 73 Unknown
/dev/block/mmcblk0p51 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p52 200704 2162686 980991+ 83 Linux
/dev/block/mmcblk0p53 2162688 4685822 1261567+ 83 Linux
/dev/block/mmcblk0p54 4685824 5210110 262143+ 83 Linux
/dev/block/mmcblk0p55 5210112 5258606 24247+ 19 Unknown
/dev/block/mmcblk0p56 5258608 5258749 71 90 Unknown
/dev/block/mmcblk0p57 5258751 5259262 256 23 Unknown
/dev/block/mmcblk0p58 5259264 7569407 1155072 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p59 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p60 70131 95130 12500 50 Unknown
Partition table entries are not in disk order
Thats all, just close command with CTRL+C
Please I need that output from working android.

[Q] Why are there so many partitions?

When I look inside /dev/block, I see a lot of partitions on mmcblk0 (and I have confirmed, just to be certain, the combined size of all partitions almost exactly equals the size of mmcblk0 on its own):
Code:
~ # ls mmcblk0*
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
What is even more bizarre is I get even more partitions listed when I use fdisk:
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2432 MB, 2432696320 bytes
1 heads, 16 sectors/track, 296960 cylinders, total 4751360 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4751358 2370615 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p26 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p27 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p28 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p29 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p30 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p31 4504944 4505085 71 90 Unknown
/dev/block/mmcblk0p32 4505087 4505598 256 23 Unknown
/dev/block/mmcblk0p33 4505600 4702191 98296 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p34 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p35 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p36 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p37 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p38 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p39 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p40 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p41 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p42 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p43 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p44 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p45 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p46 163328 163839 256 76 Unknown
/dev/block/mmcblk0p47 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p48 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p49 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p50 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p51 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p52 196096 196607 256 73 Unknown
/dev/block/mmcblk0p53 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p54 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p55 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p56 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p57 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p58 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p59 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p60 4504944 4505085 71 90 Unknown
Partition table entries are not in disk order
The thing is, those extra partitions don't seem to be in use. Running mount only lists the following partitions as mounted somewhere (irrelevant mounts excluded from the output)
Code:
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
What are all these extra partitions for?
Is this specific to my particular device (HTC One V, with firmware for Cricket Wireless), or do all Android devices have this sheer number partitions?

A little help

Can someone with rooted device run this command and let me known if mmcblk0 partition exists in note 9 pro
Here is the procedure to check:-
Code:
1) Open a terminal in your linux.
2) adb devices (This step assumes that adb and fastboot are in linux system path)
3) adb shell
4) su -
5) You are in root shell now.
6) cat /proc/partitions.
7) check if mmcblk0 partition available
Please let me know if this partitions exists, since it could help others to unbrick they device. Thanks in advance ?.
Anyone? please help me to know if the partitions exists, it could help us to recover the bricked device. Maybe in future you will use the unbrick method to unbrick your device.
On Evolution X ROM, that partition refers to the external SD card on my phone. The main phone partitions are showing on sda.
Apple Pi said:
On Evolution X ROM, that partition refers to the external SD card on my phone. The main phone partitions are showing on sda.
Click to expand...
Click to collapse
Thanks for reply, it will be appear like this, you can try termux to see the partition.
Code:
su
Cat /proc/partitions
It will list out all partitions, there the mmcblk0 partition should exist. And can you help me creat a image of it for recovering device?
Like this
riyan65 said:
Like this
Click to expand...
Click to collapse
Code:
curtana:/ # cat /proc/partitions
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
7 0 97048 loop0
7 8 880 loop1
7 16 1660 loop2
7 24 264 loop3
7 32 22540 loop4
7 40 97048 loop5
7 48 880 loop6
7 56 5664 loop7
7 64 5164 loop8
254 0 3145728 zram0
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
8 64 4194304 sde
8 65 512 sde1
8 66 4096 sde2
8 67 512 sde3
8 68 262144 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 32768 sde9
8 74 512 sde10
8 75 512 sde11
8 76 512 sde12
8 77 128 sde13
8 78 64 sde14
8 79 2048 sde15
259 0 2048 sde16
259 1 512 sde17
259 2 4096 sde18
259 3 512 sde19
259 4 262144 sde20
259 5 1024 sde21
259 6 4096 sde22
259 7 32768 sde23
259 8 8192 sde24
259 9 32768 sde25
259 10 512 sde26
259 11 512 sde27
259 12 512 sde28
259 13 128 sde29
259 14 64 sde30
259 15 2048 sde31
259 16 2048 sde32
259 17 4 sde33
259 18 1024 sde34
259 19 256 sde35
259 20 8192 sde36
259 21 33424 sde37
259 22 4 sde38
259 23 1024 sde39
259 24 8192 sde40
259 25 2048 sde41
259 26 65536 sde42
259 27 128 sde43
259 28 32 sde44
259 29 32 sde45
259 30 512 sde46
259 31 28 sde47
259 32 512 sde48
259 33 1024 sde49
259 34 64 sde50
259 35 131072 sde51
259 36 24576 sde52
259 37 64 sde53
259 38 24576 sde54
259 39 131072 sde55
8 16 8192 sdb
8 17 7168 sdb1
8 18 128 sdb2
8 32 8192 sdc
8 33 7168 sdc1
8 34 128 sdc2
8 0 120479744 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 512 sda4
8 5 512 sda5
8 6 131072 sda6
8 7 1048576 sda7
8 8 131072 sda8
8 9 131072 sda9
8 10 64 sda10
8 11 64 sda11
8 12 16384 sda12
8 13 393216 sda13
8 14 393216 sda14
8 15 16384 sda15
259 40 8192 sda16
259 41 8388608 sda17
259 42 109786956 sda18
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 10240 sdf4
8 85 128 sdf5
179 0 125042688 mmcblk0
179 1 125041647 mmcblk0p1
253 0 1518988 dm-0
253 1 1398808 dm-1
253 2 2097152 dm-2
Yes, the partition exists, now there are high chance of recovery of hard brick device. Will you help me to create one. Please PM me if you are interested
That partition only exists due to external storage being mounted to the system via the microSD card slot.
Apple Pi said:
That partition only exists due to external storage being mounted to the system via the microSD card slot.
Click to expand...
Click to collapse
No, it a system partition which contains you firmware, fastboot, and gpt table and much more. It will be the size of your device memory but get compress to 2-3gb.
riyan65 said:
No, it a system partition which contains you firmware, fastboot, and gpt table and much more. It will be the size of your device memory but get compress to 2-3gb.
Click to expand...
Click to collapse
The Partition is 125,042,688 KBytes which is the size of my 128GB MicroSD Card.
Apple Pi said:
The Partition is 125,042,688 KBytes which is the size of my 128GB MicroSD Card.
Click to expand...
Click to collapse
Could you try the same with remove sd card?

Help! plz Data 0mb after phone updated, TWRP is working, data recovery with Dm-0?

Hi
My Poco F2 pro, rooted and encrypted (sadly) decided to auto update, when it flashed in twrp, after reboot I couldnt even mount Data, so I tried to change the file system, but still 0mb, tried try decryp with no luck
I reseach about it, and found that I could dump the dev/block/dm-xx (I trhink so, or to at least recover my data anywhere else but the phone
Please help, any ideas what could or should I do?
~ # cat /proc/partitions
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
8 16 16384 sdb
8 17 7168 sdb1
8 18 7168 sdb2
8 19 512 sdb3
8 20 1492 sdb4
8 0 248700928 sda
8 1 8 sda1
8 2 32 sda2
8 3 32 sda3
8 4 32 sda4
8 5 128 sda5
8 6 256 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 2048 sda10
8 11 4096 sda11
8 12 8192 sda12
8 13 8192 sda13
8 14 8192 sda14
8 15 16384 sda15
259 0 16384 sda16
259 1 1024 sda17
259 2 16384 sda18
259 3 15360 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 65536 sda22
259 7 65536 sda23
259 8 65536 sda24
259 9 131072 sda25
259 10 98304 sda26
259 11 32768 sda27
259 12 131072 sda28
259 13 393216 sda29
259 14 393216 sda30
259 15 1048576 sda31
259 16 8912896 sda32
259 17 32768 sda33
259 18 237166572 sda34
8 32 16384 sdc
8 33 7168 sdc1
8 34 7168 sdc2
8 35 512 sdc3
8 36 1492 sdc4
8 48 32768 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
8 52 2048 sdd4
8 53 2048 sdd5
8 54 1024 sdd6
8 64 1048576 sde
8 65 104 sde1
8 66 32 sde2
8 67 32 sde3
8 68 32 sde4
8 69 32 sde5
8 70 128 sde6
8 71 128 sde7
8 72 256 sde8
8 73 256 sde9
8 74 32 sde10
8 75 32 sde11
8 76 32 sde12
8 77 32 sde13
8 78 128 sde14
8 79 128 sde15
259 19 128 sde16
259 20 128 sde17
259 21 128 sde18
259 22 256 sde19
259 23 256 sde20
259 24 256 sde21
259 25 512 sde22
259 26 512 sde23
259 27 512 sde24
259 28 128 sde25
259 29 128 sde26
259 30 128 sde27
259 31 3712 sde28
259 32 1024 sde29
259 33 1024 sde30
259 34 1024 sde31
259 35 1024 sde32
259 36 1024 sde33
259 37 1024 sde34
259 38 1024 sde35
259 39 1024 sde36
259 40 2048 sde37
259 41 2048 sde38
259 42 2048 sde39
259 43 2048 sde40
259 44 4096 sde41
259 45 4096 sde42
259 46 32768 sde43
259 47 8192 sde44
259 48 8192 sde45
259 49 16384 sde46
259 50 32768 sde47
259 51 65536 sde48
259 52 65536 sde49
259 53 131072 sde50
259 54 458752 sde51
259 55 32768 sde52
259 56 32768 sde53
259 57 53248 sde54
259 58 4096 sde55
259 59 4096 sde56
259 60 2048 sde57
259 61 2048 sde58
8 80 65536 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 2048 sdf4
8 85 128 sdf5
8 86 768 sdf6
8 87 8192 sdf7
8 88 8192 sdf8
8 89 8192 sdf9
8 90 1024 sdf10
252 0 2842372 dm-0
252 1 1655520 dm-1
252 2 1147096 dm-2
252 3 131072 dm-3
252 4 404196 dm-4
~ #
------------------------------
Tried
~ # pull /dev/block/dm-0 /data.img
-/sbin/sh: pull: not found
~ # twrp decrypt 1238
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
Tried flashing disableVerity
PD: Lost vendor partition
Any way I can copy the dm-0 (I understood that I could somehow manage to regain my data if I get those files)
Or is it anyway to mount them or any ideas
===================
Would mean the world to me if anyone could help
Kevincorella said:
Hi
My Poco F2 pro, rooted and encrypted (sadly) decided to auto update, when it flashed in twrp, after reboot I couldnt even mount Data, so I tried to change the file system, but still 0mb, tried try decryp with no luck
I reseach about it, and found that I could dump the dev/block/dm-xx (I trhink so, or to at least recover my data anywhere else but the phone
Please help, any ideas what could or should I do?
~ # cat /proc/partitions
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
8 16 16384 sdb
8 17 7168 sdb1
8 18 7168 sdb2
8 19 512 sdb3
8 20 1492 sdb4
8 0 248700928 sda
8 1 8 sda1
8 2 32 sda2
8 3 32 sda3
8 4 32 sda4
8 5 128 sda5
8 6 256 sda6
8 7 512 sda7
8 8 512 sda8
8 9 512 sda9
8 10 2048 sda10
8 11 4096 sda11
8 12 8192 sda12
8 13 8192 sda13
8 14 8192 sda14
8 15 16384 sda15
259 0 16384 sda16
259 1 1024 sda17
259 2 16384 sda18
259 3 15360 sda19
259 4 32768 sda20
259 5 32768 sda21
259 6 65536 sda22
259 7 65536 sda23
259 8 65536 sda24
259 9 131072 sda25
259 10 98304 sda26
259 11 32768 sda27
259 12 131072 sda28
259 13 393216 sda29
259 14 393216 sda30
259 15 1048576 sda31
259 16 8912896 sda32
259 17 32768 sda33
259 18 237166572 sda34
8 32 16384 sdc
8 33 7168 sdc1
8 34 7168 sdc2
8 35 512 sdc3
8 36 1492 sdc4
8 48 32768 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
8 52 2048 sdd4
8 53 2048 sdd5
8 54 1024 sdd6
8 64 1048576 sde
8 65 104 sde1
8 66 32 sde2
8 67 32 sde3
8 68 32 sde4
8 69 32 sde5
8 70 128 sde6
8 71 128 sde7
8 72 256 sde8
8 73 256 sde9
8 74 32 sde10
8 75 32 sde11
8 76 32 sde12
8 77 32 sde13
8 78 128 sde14
8 79 128 sde15
259 19 128 sde16
259 20 128 sde17
259 21 128 sde18
259 22 256 sde19
259 23 256 sde20
259 24 256 sde21
259 25 512 sde22
259 26 512 sde23
259 27 512 sde24
259 28 128 sde25
259 29 128 sde26
259 30 128 sde27
259 31 3712 sde28
259 32 1024 sde29
259 33 1024 sde30
259 34 1024 sde31
259 35 1024 sde32
259 36 1024 sde33
259 37 1024 sde34
259 38 1024 sde35
259 39 1024 sde36
259 40 2048 sde37
259 41 2048 sde38
259 42 2048 sde39
259 43 2048 sde40
259 44 4096 sde41
259 45 4096 sde42
259 46 32768 sde43
259 47 8192 sde44
259 48 8192 sde45
259 49 16384 sde46
259 50 32768 sde47
259 51 65536 sde48
259 52 65536 sde49
259 53 131072 sde50
259 54 458752 sde51
259 55 32768 sde52
259 56 32768 sde53
259 57 53248 sde54
259 58 4096 sde55
259 59 4096 sde56
259 60 2048 sde57
259 61 2048 sde58
8 80 65536 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 2048 sdf4
8 85 128 sdf5
8 86 768 sdf6
8 87 8192 sdf7
8 88 8192 sdf8
8 89 8192 sdf9
8 90 1024 sdf10
252 0 2842372 dm-0
252 1 1655520 dm-1
252 2 1147096 dm-2
252 3 131072 dm-3
252 4 404196 dm-4
~ #
------------------------------
Tried
~ # pull /dev/block/dm-0 /data.img
-/sbin/sh: pull: not found
~ # twrp decrypt 1238
Attempting to decrypt data partition or user data via command line.
Failed to decrypt data.
Tried flashing disableVerity
PD: Lost vendor partition
Any way I can copy the dm-0 (I understood that I could somehow manage to regain my data if I get those files)
Or is it anyway to mount them or any ideas
===================
Would mean the world to me if anyone could help
Click to expand...
Click to collapse
I don't know Bro. Seems like your data has gone read only. I don't know if I am right though. Anyways what I want to ask you is if you can manage to completely wipe your data and install a custom rom. I don't think I am much helpful but please let me know if you can do it.
Arc android said:
I don't know Bro. Seems like your data has gone read only. I don't know if I am right though. Anyways what I want to ask you is if you can manage to completely wipe your data and install a custom rom. I don't think I am much helpful but please let me know if you can do it.
Click to expand...
Click to collapse
I could install the rom via Fastboot, but I want to see if there is any hope for the data before wiping everything ):

Categories

Resources