Background Information
My phone is stuck in a boot loop. Fortunately my phone is rooted and I have TWRP installed.
Original Plan
So my original plan was to just restore the data with TWRP.
However when trying to access the data I found out that the "data" partition can't be mounted in TWRP.
It apparently has to do something with it being encrypted. However I don't understand why I can't just decrypt it since I know my password! ??
New Plan
So my new plan was:
1. Create a disk clone with dd
2. Save it on my pc
3. Flash my phone and use it again
4. Wait (Maybe one day in the future I'll be able to decrypt my data and access it again)
So I listed all partitions in order to find the appropriate "hard drive" or in this case the appropriate flash drive (UFS)
p3s:/ # 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 264 loop0
7 8 888 loop1
7 16 98312 loop2
7 24 18604 loop3
8 0 499814400 sda
8 1 20480 sda1
8 2 20480 sda2
8 3 4096 sda3
8 4 8192 sda4
8 5 8192 sda5
8 6 512 sda6
8 7 40960 sda7
8 8 3072 sda8
8 9 2048 sda9
8 10 4096 sda10
8 11 8192 sda11
8 12 64 sda12
8 13 65536 sda13
8 14 65536 sda14
8 15 65536 sda15
259 0 71680 sda16
259 1 7680 sda17
259 2 1024 sda18
259 3 512 sda19
259 4 1024 sda20
259 5 53248 sda21
259 6 16384 sda22
259 7 64 sda23
259 8 64 sda24
259 9 32768 sda25
259 10 4 sda26
259 11 316 sda27
259 12 11468800 sda28
259 13 1433600 sda29
259 14 30720 sda30
259 15 614400 sda31
259 16 51200 sda32
259 17 51200 sda33
259 18 485654528 sda34
8 16 4096 sdb
8 32 4096 sdc
8 48 8192 sdd
8 49 6144 sdd1
8 64 20480 sde
253 0 6601340 dm-0
253 1 1764892 dm-1
253 2 845048 dm-2
253 3 4248 dm-3
Click to expand...
Click to collapse
So sda seems to be the main storage as it's the biggest one. I then wanted to know what's the path of sda . Like in normal linux on normal pcs it's always /dev/sda and one can just do dd if=/dev/sda .... .
I tried listing it via:
ls -l /sys/class/block/sda
Click to expand...
Click to collapse
/sys/devices/platform/13100000.ufs/host0/target0:0:0/0:0:0:0/block/sda
p3s:/sys/dev/block # dd if=/sys/devices/platform/13100000.ufs/host0/target0\:0\:0/0\:0\:0\:0/block/sda bs=512 count=1
dd: /sys/devices/platform/13100000.ufs/host0/target0:0:0/0:0:0:0/block/sda: read error: Is a directory
Click to expand...
Click to collapse
However when i try this, dd complains, that sda is a directory
Does anyone know the correct path ? Or how I can find out what the correct path is ?
Oh I think i found it :
I think it's
/dev/block/sda
Click to expand...
Click to collapse
when i now try to execute dd it works
p3s:/ # dd if=/dev/block/sda bs=512 count=1
☺�☺��rU�1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.004320 s, 116 K/s
Click to expand...
Click to collapse
Related
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
I have some difficulties understanding partitions' layout of my phone. (Huawei G6-U10 ***NOT*** rooted yet)
As spec:
4 GB Internal Memory
|__ 2 GB reserved
|__ 2 GB Internal Storage
|__ Memory android option menu shows ~2 GB total (1,91 GB) but only ~1 GB (1,03 GB) available.If I connect my phone through MTP it shows as internal memory just a partition of ~ 1 GB (994 MB)
32 GB external SD
Code:
major minor #blocks name
7 1 9387 loop1
7 2 16664 loop2
7 3 10427 loop3
7 4 15624 loop4
253 0 196608 zram0
179 0 3866624 mmcblk0
179 1 512 mmcblk0p1
179 2 32 mmcblk0p2
179 3 32 mmcblk0p3
179 4 500 mmcblk0p4
179 5 500 mmcblk0p5
179 6 5592 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 65536 mmcblk0p8
179 9 4096 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 98304 mmcblk0p11
179 12 4096 mmcblk0p12
179 13 1 mmcblk0p13
179 14 8 mmcblk0p14
179 15 32768 mmcblk0p15
179 16 65536 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 12288 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 262144 mmcblk0p20
179 21 196608 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 1048576 mmcblk0p23
179 24 1048576 mmcblk0p24
179 25 974831 mmcblk0p25
179 32 2048 mmcblk0rpmb
179 64 30748672 mmcblk1
179 65 30744576 mmcblk1p1
254 1 9387 dm-1
254 4 15624 dm-4
254 2 16663 dm-2
254 3 10426 dm-3
Then I listed partition symlink by name
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
DDR -> /dev/block/mmcblk0p3
aboot -> /dev/block/mmcblk0p6
bkbootup -> /dev/block/mmcblk0p16
boot -> /dev/block/mmcblk0p18
cache -> /dev/block/mmcblk0p21
cust -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p13
fsg -> /dev/block/mmcblk0p12
grow -> /dev/block/mmcblk0p25
log -> /dev/block/mmcblk0p15
misc -> /dev/block/mmcblk0p22
modem -> /dev/block/mmcblk0p11
modemst1 -> /dev/block/mmcblk0p9
modemst2 -> /dev/block/mmcblk0p10
oeminfo -> /dev/block/mmcblk0p8
pad -> /dev/block/mmcblk0p7
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p19
rpm -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p1
sdi -> /dev/block/mmcblk0p2
ssd -> /dev/block/mmcblk0p14
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p5
userdata -> /dev/block/mmcblk0p24
Assuming a blocksize of 1024, I can see that sizes of mmcblk0p23 (/system) and mmcblk0p24 (/userdata) are 1 GB each.
1) The space unavailable from internal storage, is the /userdata partition?
2) Of the 2 GB Android doesn't show at all, 1 is obviously occupied by /system, but if the sum of all the other partitions on the first block device (except /userdata and /system) is equal to ~1,67 GB, how can it resides on the 1 GB remaining space?
3)What's the /grow mountpoint?
1 Day, 30 views, 7th page and no reply.
Have I made any mistake? Wrong category? Questions are unclear?
Bump.
Another bump.
I fear people stop reading this thread after the title, because they think it's the same old "I don't know what partitions and mountpoints are and don't want to document about it".
Please read the questions.
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?
I'm using a Xiaomi Redmi Note 9S with MIUI 11.0.10 which is Android 10. There seems to be some bug with root that can soft-brick your phone. When you boot into TWRP, it can no longer mount the System partition - pressing it, will do nothing.
So I connect via adb to the phone. It's root adb and I am root according to "whoami".
cat /proc/partitions output:
Code:
~ # 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 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 0 8192 sda16
259 1 8388608 sda17
259 2 109786956 sda18
8 16 8192 sdb
8 17 7168 sdb1
8 18 128 sdb2
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 3 2048 sde16
259 4 512 sde17
259 5 4096 sde18
259 6 512 sde19
259 7 262144 sde20
259 8 1024 sde21
259 9 4096 sde22
259 10 32768 sde23
259 11 8192 sde24
259 12 32768 sde25
259 13 512 sde26
259 14 512 sde27
259 15 512 sde28
259 16 128 sde29
259 17 64 sde30
259 18 2048 sde31
259 19 2048 sde32
259 20 4 sde33
259 21 1024 sde34
259 22 256 sde35
259 23 8192 sde36
259 24 33424 sde37
259 25 4 sde38
259 26 1024 sde39
259 27 8192 sde40
259 28 2048 sde41
259 29 65536 sde42
259 30 128 sde43
259 31 32 sde44
259 32 32 sde45
259 33 512 sde46
259 34 28 sde47
259 35 512 sde48
259 36 1024 sde49
259 37 64 sde50
259 38 131072 sde51
259 39 24576 sde52
259 40 64 sde53
259 41 24576 sde54
259 42 131072 sde55
8 32 8192 sdc
8 33 7168 sdc1
8 34 128 sdc2
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 10240 sdf4
8 85 128 sdf5
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 1024 sdd3
253 0 934804 dm-0
253 1 1403780 dm-1
253 2 2356452 dm-2
df -h output after flashing new .EU ROM - this is how it should look like:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 2.7G 752.0K 2.7G 0% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
tmpfs 2.7G 6.4M 2.7G 0% /tmp
/dev/block/sda18 104.7G 14.5G 90.2G 14% /data
/dev/block/sda18 104.7G 14.5G 90.2G 14% /sdcard
/dev/block/dm-1 1.3G 1.2G 33.4M 97% /vendor
/dev/block/sda13 356.0M 428.0K 328.7M 0% /cache
/dev/block/dm-2 2.2G 2.1G 109.5M 95% /system_root
/dev/block/dm-2 2.2G 2.1G 109.5M 95% /system
df -h output - what it actually looks like after soft-brick:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 2.7G 752.0K 2.7G 0% /dev
tmpfs 2.7G 0 2.7G 0% /mnt
tmpfs 2.7G 0 2.7G 0% /apex
tmpfs 2.7G 2.6M 2.7G 0% /tmp
/dev/block/sda13 356.0M 1.1M 328.0M 0% /cache
/dev/block/sda18 104.7G 15.3G 89.4G 15% /data
/dev/block/sda18 104.7G 15.3G 89.4G 15% /sdcard
Trying to mount the "dm" devices, you can mount dm-0 and dm-1, but dm-2 (which should be system) fails:
Code:
~ # mount -r /dev/block/dm-2 /fufu/ -v -t ext4
mount: mounting /dev/block/dm-2 on /fufu/ failed: Read-only file system
DM-verity is disabled:
Code:
adb enable-verity
verity not enabled - ENG build
e2fsck fails because it claims to have no write access:
Code:
~ # e2fsck /dev/block/dm-2
e2fsck 1.44.4 (18-Aug-2018)
e2fsck: Operation not permitted while trying to open /dev/block/dm-2
You must have r/w access to the filesystem or be root
~ # whoami
root
File system is still intact. You can "dd" the dm-2 partition to some other place and access it via Linux or an ext4 viewer on Windows (https://www.diskinternals.com/linux-reader/ for example). You can also do it via adb: "adb pull /dev/block/dm-2"
When mounting (see above) and then looking in the log (dmesg):
Code:
<6>[ 1057.614782] EXT4-fs (dm-2): INFO: recovery required on readonly filesystem
<3>[ 1057.614797] EXT4-fs (dm-2): write access unavailable, cannot proceed
tune2fs for dm-1 and dm-2:
Code:
~ # tune2fs -l /dev/block/dm-1
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name: vendor
Last mounted on: <not available>
Filesystem UUID: 6d16bab1-58d9-3c5d-8f14-f608f924affd
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 87824
Block count: 350944
Reserved block count: 0
Free blocks: 12643
Free inodes: 84860
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 87
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 7984
Inode blocks per group: 499
Last mount time: n/a
Last write time: Thu Jan 1 08:00:00 1970
Mount count: 0
Maximum mount count: -1
Last checked: Thu Jan 1 08:00:00 1970
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
~ # tune2fs -l /dev/block/dm-2
tune2fs 1.44.4 (18-Aug-2018)
Filesystem volume name: /
Last mounted on: /
Filesystem UUID: bbcb9ad2-245d-035f-a549-7d500312efe1
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode filetype needs_recovery extent sparse_super large_file uninit_bg
Filesystem flags: unsigned_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 147456
Block count: 589113
Reserved block count: 0
Free blocks: 32124
Free inodes: 142168
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 143
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Last mount time: Sun Aug 2 03:07:27 2020
Last write time: Thu Jan 1 08:00:00 1970
Mount count: 4
Maximum mount count: -1
Last checked: Thu Jan 1 08:00:00 1970
Check interval: 0 (<none>)
Lifetime writes: 692 kB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: tea
Journal backup: inode blocks
-> dm-2 has a flag called "needs_recovery" set.
- I can run e2fsck on the dd exported image of dm-2 which recovers it fine, but I cannot dd it back to dm-2 - again no write access:
Code:
~ # dd if=/sdcard/systemfile.img of=/dev/block/dm-2
dd: writing '/dev/block/dm-2': Operation not permitted
1+0 records in
0+0 records out
0 bytes (0B) copied, 0.000131 seconds, 0B/s
Ideas how I can write anything to /dev/block/dm-2 (I also cannot change anything via tune2fs to the other dm devices).
Thank you
@herlgl You should take a look at this or this. Good luck!
have you solved? how?
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 ):