I have read that the KF has 8GB of storage. I see two partitions.... one of them is 1GB in size and the other is 5GB
Can someone explain to me how the 8GB is divided up on the KF?
Thanks
If I understand it correctly, it has two partitions. The 1GB and a 7GB that hosts the system software and where the SD-Card section is. The 5GB you see is what's free after the system software and your stored files.
Sent from my Kindle Fire using Tapatalk
If you look at Setup -> Device you will see what the memory allocation is and what is is basically for...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The top section is Application storage and is aprox 1GB. This is where your applications are loaded along with some other data.
The top section is Internal Storage and is what you see when you plug in the device as a USB drive as the SDcard. It is less than 6GB.
It is possible to move applications in a round about way from the Application Memory to the Internal Storage segment.
Dekan54 said:
I have read that the KF has 8GB of storage. I see two partitions.... one of them is 1GB in size and the other is 5GB
Can someone explain to me how the 8GB is divided up on the KF?
Thanks
Click to expand...
Click to collapse
The 1 gb partition is for your apps, etc....the rest is for reading material. It's my understanding there are utilities to repartition. Not sure if you have to root to do that however. This is where the nook tablet and KF differ the most IMO.
Also remember, there is a difference between actual memory and usable memory. Yes, it's 8 gig but that is not a full 8 gig of usable memory (which is why you only see about 6 gig.
For example, my 8 gig flash drive only has a little over 7 gig of usable memory.
Xandralia said:
Also remember, there is a difference between actual memory and usable memory. Yes, it's 8 gig but that is not a full 8 gig of usable memory (which is why you only see about 6 gig.
For example, my 8 gig flash drive only has a little over 7 gig of usable memory.
Click to expand...
Click to collapse
It's not because of "actual memory" and "usable memory" It's because manufactures represent hard drive space using a different reference.
Here's an example for a 1 TB hard drive:
Manufacturers describe the size of their drive in multiples of 1000
1,000 GB = 1,000 * 1,000,000,000 bytes = 1,000,000,000,000 bytes.
Now let's see how many KiB that is. 1 KiB = 1,024 bytes,
so 1,0000,000,000,000 bytes = 976,562 KiB.
So how many MiB is that? 1 MiB = 1,024 KiB.
So 976,562 KiB = 953 GiB.
Operating systems measure hard drive space in GiB, even though they call it "GB".
Thank you to all that answered....
Are some Fires different?
My fire shows 2.13 GB of 5.37 GB available. No matter how I calcluate that, it is still well under 7GB for content storage. Can someone explain? Thanks.
crackedshel said:
My fire shows 2.13 GB of 5.37 GB available. No matter how I calcluate that, it is still well under 7GB for content storage. Can someone explain? Thanks.
Click to expand...
Click to collapse
C:\Programme\Android\Kindle Fire Utility\tools>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
Code:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Calculating size using GB still falls short of 8GB. It actually has 7376MiB of storage. And of those 7376MiB, 1134MiB is for apps/data in the data partition, and 5131MiB is for other media in the sdcard partition. Android sits on a 512MiB partition leaving 599MiB for recovery, diagnostics, bootloader, etc.
Would be nice if there was a small drive we could plug into the port to add a little more.
lmntone said:
Code:
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734296576B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Calculating size using GB still falls short of 8GB. It actually has 7376MiB of storage. And of those 7376MiB, 1134MiB is for apps/data in the data partition, and 5131MiB is for other media in the sdcard partition. Android sits on a 512MiB partition leaving 599MiB for recovery, diagnostics, bootloader, etc.
Click to expand...
Click to collapse
+ any drive and any operating system uses some of the storage space for the filesystem format info, the partition tables, the file tables and so on. So it doesn't matter if the it's 8GB or 8GiB you will never have the full 8 of it unless you leave it an unformated unusable drive. The bigger the drive the bigger the amount of it that has to reserved for the format info by the system.
I've always been confused by the partitioning since I got it as well
Granite Gargoyle said:
Would be nice if there was a small drive we could plug into the port to add a little more.
Click to expand...
Click to collapse
It's been said that the Kingston Wi-Drive will have android support soon, so that would give ya a portable hard drive you could hook up to with wifi to carry around with ya.
Starfire70 said:
It's been said that the Kingston Wi-Drive will have android support soon, so that would give ya a portable hard drive you could hook up to with wifi to carry around with ya.
Click to expand...
Click to collapse
From what I've read on other Fire forums, it already does. It sends out its own wifi signal. Cost $49 for 16gb; around $90 for 32gb.
Partition sizes given in decimal kB and MB are inaccurate.
Sizes and offsets given by parted are not exact because they are given in decimal kB and MB, rather than in binary KiB and MiB, while partitioning is done in the binary units. You can see the exact numbers from the following:
Code:
# cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
I have no idea what '179' means, but the sizes are all in 1-KiB (i.e., 1024-byte) blocks, and all the numbers are integral multiples or integral fractions of 1024, so that the partition sizes are, except for those too small, all in integral numbers of MiB.
as the title said, here i will post partition table of our ancora
Code:
Number Start (sector) End (sector) Size Code Name
1 1 212991 104.0 MiB 0700 Microsoft basic data
2 212992 213991 500.0 KiB 8300 Linux filesystem
3 213992 221183 3.5 MiB 8300 Linux filesystem
5 229376 239615 5.0 MiB 8300 Linux filesystem
6 245760 285759 19.5 MiB 8300 Linux filesystem
7 286720 292863 3.0 MiB 8300 Linux filesystem
8 294912 306175 5.5 MiB 8300 Linux filesystem
9 311296 324271 6.3 MiB 8300 Linux filesystem
10 327680 333823 3.0 MiB 8300 Linux filesystem
11 335872 342015 3.0 MiB 8300 Linux filesystem
12 344064 360447 8.0 MiB 8300 Linux filesystem
13 360448 375807 7.5 MiB 8300 Linux filesystem
14 376832 387071 5.0 MiB 8300 Linux filesystem
15 393216 1488895 535.0 MiB 8300 Linux filesystem
16 1490944 1613823 60.0 MiB 8300 Linux filesystem
17 1613824 3887103 1.1 GiB 8300 Linux filesystem
18 3891200 3993599 50.0 MiB 8300 Linux filesystem
19 3997696 3998695 500.0 KiB 8300 Linux filesystem
20 4005888 4013079 3.5 MiB 8300 Linux filesystem
21 4014080 4024319 5.0 MiB 8300 Linux filesystem
22 4030464 4070463 19.5 MiB 8300 Linux filesystem
23 4071424 4081663 5.0 MiB 8300 Linux filesystem
24 4087808 4101807 6.8 MiB 8300 Linux filesystem
25 4104192 4114431 5.0 MiB 8300 Linux filesystem
26 4120576 4130815 5.0 MiB 8300 Linux filesystem
27 4136960 4147199 5.0 MiB 8300 Linux filesystem
28 4153344 7733247 1.7 GiB 8300 Linux filesystem
well, my question regarding this data are
1. why i don't get the name of each partition ?
2. as we know, kernel block memory is mmcblk0p13, the block size is 7.5MB, is this available size only for the kernel or this size included kernel+ramdisk?
3. we got so many partition, any idea of having a hidden partition that is vacant or useable to mount other things?
thanks
i hope pep would see this post and help me
Sent from my GT-I8150
hadidjapri said:
i hope pep would see this post and help me
Sent from my GT-I8150
Click to expand...
Click to collapse
You're making me ashamed
I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified:
* bootloader partition
* 2 (two) baseband partitions
* ROM partition
* recovery partition
As to the others... they *are* still mysterious...
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
pepoluan said:
You're making me ashamed
I'll look for my notes tomorrow. Of those partitions, IIRC we (that is, me & friends in this forum) successfully identified:
* bootloader partition
* 2 (two) baseband partitions
* ROM partition
* recovery partition
As to the others... they *are* still mysterious...
-- xda app / Pristine NoMod CM9b4 / CastagnaIT kernel / GT-I8150 --
Click to expand...
Click to collapse
i got efs from arco
another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk?
Sent from my GT-I8150
hadidjapri said:
another question, kernel got 7.5mb space,.is this only for the kernel or kernel+ramdisk?
Click to expand...
Click to collapse
kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb.
This is the information I've gathered about the partitions.
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
arco68 said:
kernel+ramdisk, and boot is 5.5mb actually. Recovery is 7.5mb.
This is the information I've gathered about the partitions.
Code:
# cat /proc/partitions
major minor #blocks name
179 0 3864576 mmcblk0
179 1 106495 mmcblk0p1 //secboot2 partition map
179 2 500 mmcblk0p2 //dbl (boot loader)
179 3 3596 mmcblk0p3 //osbl (boot loader)
179 4 1 mmcblk0p4 //mbr extended partition table
179 5 5120 mmcblk0p5 //emmcboot (boot loader, download mode)
179 6 20000 mmcblk0p6 //amss
179 7 3072 mmcblk0p7 //emmcparam
179 8 5632 mmcblk0p8 //boot
179 9 6488 mmcblk0p9 //adsp
179 10 3072 mmcblk0p10 //rmt
179 11 3072 mmcblk0p11 //rmt
179 12 8192 mmcblk0p12 //persist
179 13 7680 mmcblk0p13 //recovery
179 14 5120 mmcblk0p14 //param
179 15 547840 mmcblk0p15 //system
179 16 61440 mmcblk0p16 //cache
179 17 1136640 mmcblk0p17 //data
179 18 51200 mmcblk0p18 //preload
179 19 500 mmcblk0p19
179 20 3596 mmcblk0p20
179 21 5120 mmcblk0p21
179 22 20000 mmcblk0p22
179 23 5120 mmcblk0p23
179 24 7000 mmcblk0p24
179 25 5120 mmcblk0p25
179 26 5120 mmcblk0p26
179 27 5120 mmcblk0p27 //efs
179 28 1787904 mmcblk0p28 //internal sdcard
Click to expand...
Click to collapse
hmm what does mmcblk10-26 store sir?
Sent from my GT-I8150
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
arco68 said:
You mean 19-26? No idea. Probably not used for anything. You can dd them and see if they contain something, or is just filled with zeros.
Click to expand...
Click to collapse
I once dd-ed p22, it has similar strings to p6.
A kind of backup baseband?
-- CM9b4 / CastagnaIT 7.3 BFS+ExtUV / DXKL1 / GT-I8150 --
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
sigprof said:
My notes from analyzing dumps and tables inside loaders (apparently the partition type IDs are listed in many of these tables):
Code:
N Size (s) Size (MiB) Size (MB) B T
1 212991 104.000 MiB 106.496 MB 0c ? (hashes)
2 1000 0.488 MiB 0.500 MB *4d DBL [/boot/qcsbl_cfg] {dbl.mbn}
3 7192 3.512 MiB 3.596 MB 46 OSBL [/boot/oemsbl, /boot/osbl] {osbl.mbn}
4 2 0.001 MiB 0.001 MB 05 (extended)
5 10240 5.000 MiB 5.120 MB 47 HBOOT [/boot/appsbl] {EMMCBOOT.MBN}
6 40000 19.531 MiB 20.000 MB 49 AMSS [/boot/modem] {amss.mbn}
7 6144 3.000 MiB 3.072 MB 58 ? (empty - 00)
8 11264 5.500 MiB 5.632 MB 48 Android boot [/boot/apps]
9 12976 6.336 MiB 6.488 MB 50 ADSP [/boot/adsp] {adsp.mbn}
10 6144 3.000 MiB 3.072 MB 4a ? (random) [/boot/modem_fs1]
11 6144 3.000 MiB 3.072 MB 4b ? (random) [/boot/modem_fs2]
12 16384 8.000 MiB 8.192 MB 90 Android /persist (ext4)
13 15360 7.500 MiB 7.680 MB 91 Android recovery
14 10240 5.000 MiB 5.120 MB 92 ? (region ID) {emmcparam.bin}
15 1095680 535.000 MiB 547.840 MB 93 Android /system (ext4)
16 122880 60.000 MiB 61.440 MB 94 Android /cache (ext4)
17 2273280 1110.000 MiB 1136.640 MB 95 Android /data (ext4)
18 102400 50.000 MiB 51.200 MB 96 Android /preload (ext4)
19 1000 0.488 MiB 0.500 MB 97 ? (empty - 00)
20 7192 3.512 MiB 3.596 MB 98 ? (empty - 00) [/boot/osbl_bkp?]
21 10240 5.000 MiB 5.120 MB 99 HBOOT backup [/boot/appsbl_bkp]
22 40000 19.531 MiB 20.000 MB 9a AMSS backup [/boot/modem_bkp]
23 10240 5.000 MiB 5.120 MB 9b ? (empty - 00) [/boot/apps_bkp]
24 14000 6.836 MiB 7.000 MB 9c Android (boot image?) [/boot/adsp_bkp?]
25 10240 5.000 MiB 5.120 MB 9d ? (empty - 00)
26 10240 5.000 MiB 5.120 MB 9e ? (empty - 00)
27 10240 5.000 MiB 5.120 MB 9f Android /efs (ext2)
28 3575808 1746.000 MiB 1787.904 MB a0 Android /sdcard (FAT16)
Partitions: 7639521 3730.235 MiB 3819.760 MB
Holes: 89631 43.765 MiB 44.816 MB
Total sectors: 7729152 3774.000 MiB 3864.576 MB
Apparently some partitions were intended to store backup copies of bootloaders, AMSS, ADSP and the Android boot image; however, there are some mismatches between tables in OSBL and APPSBL, as well as apparently wrong partition sizes — e.g., the OSBL table lists the partition type 0x9b as /boot/apps_bkp, but this partition (mmcblk0p23) is too small to contain the actual boot.img, and the boot image backup is actually stored in mmcblk0p24, which was intended for ADSP backup.
Click to expand...
Click to collapse
is it possible partition number 19-26 are intended to be backup partition?
Sent from my GT-I8150
Could phone operator lock code be stored in one of the (normally unmounted) partitions?
Sent from my GT-I8150 using xda app-developers app
i use dd if command on this amazing topic and always use this toturial
but not worked on g920p 6.0.1
when i type below command :
HTML:
adb shell
su
dd if=/dev/block/sda18 of=/sdcard/system.img
HTML:
cat /proc/partitions
major minor #blocks name
7 0 32768 loop0
253 0 2097152 vnswap0
8 0 31240192 sda
8 1 4096 sda1
8 2 4096 sda2
8 3 20480 sda3
8 4 4096 sda4
8 5 4096 sda5
8 6 4096 sda6
8 7 8192 sda7
8 8 28672 sda8
8 9 34816 sda9
8 10 8192 sda10
8 11 77824 sda11
8 12 1024 sda12
8 13 1024 sda13
8 14 768 sda14
8 15 256 sda15
259 0 9216 sda16
259 1 15360 sda17
259 2 3829760 sda18
259 3 307200 sda19
259 4 46080 sda20
259 5 26820608 sda21
8 16 4096 sdb
8 32 4096 sdc
system.img created on my sdcard and i copy to my pc and convert to tar file but when i flash the odin just say fail
how to dump system.img correctly on android marshmalow ?
pls help
Hello!
I managed to flash the CM 12.1 rom but I noticed that the /system partition is barely large enough (585Mb). It is so small that
I can't install the gapps package I need.
I also note that my /userdata partition is 1200Mb.
I would like to decrease the size of the userdata partition and increase the size of the system partition.
I am able to do this fine through adb shell after booting into TWRP recovery - but
the changes don't stick.
In some cases (not sure if it's when I mess up the partition table) - the partition table is simply reset
upon reboot.
In other cases - the partition table is reset - but contains duplicate partitions (as shown below)
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2332 MB, 2332033024 bytes
1 heads, 16 sectors/track, 284672 cylinders, total 4554752 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 4554750 2272311 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 137216 3072 4a Unknown
/dev/block/mmcblk0p14 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p15 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p16 145412 163326 8957+ 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 1343486 571391+ 83 Linux
/dev/block/mmcblk0p26 1343488 3749886 1203199+ 83 Linux
/dev/block/mmcblk0p27 3749888 4046846 148479+ 83 Linux
/dev/block/mmcblk0p28 4046848 4358143 155648 83 Linux
/dev/block/mmcblk0p29 4358145 4364286 3071 33 Unknown
/dev/block/mmcblk0p30 4364288 4406782 21247+ 19 Unknown
/dev/block/mmcblk0p31 4406784 4407295 256 23 Unknown
/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 137216 3072 4a Unknown
/dev/block/mmcblk0p41 137218 143361 3072 4b Unknown
/dev/block/mmcblk0p42 143363 145410 1024 74 Unknown
/dev/block/mmcblk0p43 145412 163326 8957+ 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 1343486 571391+ 83 Linux
/dev/block/mmcblk0p53 1343488 3749886 1203199+ 83 Linux
/dev/block/mmcblk0p54 3749888 4046846 148479+ 83 Linux
/dev/block/mmcblk0p55 4046848 4358143 155648 83 Linux
/dev/block/mmcblk0p56 4358145 4364286 3071 33 Unknown
/dev/block/mmcblk0p57 4364288 4406782 21247+ 19 Unknown
/dev/block/mmcblk0p58 4406784 4407295 256 23 Unknown
/dev/block/mmcblk0p59 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p60 70131 95130 12500 50 Unknown
(Note how partition 32 and onwards are just copies of the earlier ones)
My question is, is there some part of the system that actually tries to repair/reset the partition table after I have changed it - or does TWRP simply not save the changes I do for some reason?
What part of my system might reset the partition table & why?
Thanks!
Hi,
I own a OP3 with broken screen and am not able to retrieve some photos from the device.
As I already bought a new phone, I'd like to avoid having to repair the display.
Phone facts:
-Rooted Stock Rom, Bootloader unlocked
-Screen totally black, not sure if touch works, at least home key LED lights up when touched
- MTP not working (was recognized by PC, but no files displayed)
What works:
- Boot into stock recovery and fastboot
- adb and fastboot both work (I'm using android-tools-adb with Ubuntu 18.04)
- adb root shell
However, when browsing through the system, both /data and /storage are empty.
mount -a or mount /storage does not work.
When I do a
Code:
cat /proc/partitions
I get something similar to this:
Code:
major minor #blocks name
7 0 98304 loop0
8 16 4096 sdb
8 17 4052 sdb1
8 0 56582144 sda
8 1 8 sda1
8 2 32768 sda2
8 3 262144 sda3
8 4 1024 sda4
8 5 512 sda5
8 6 128 sda6
8 7 128 sda7
8 8 512 sda8
8 9 10240 sda9
8 10 10240 sda10
8 11 1024 sda11
8 12 8096 sda12
8 13 16192 sda13
8 14 512 sda14
8 15 56238572 sda15
8 48 131072 sdd
8 49 32 sdd1
8 50 4 sdd2
8 51 1024 sdd3
8 64 4194304 sde
8 65 512 sde1
8 66 512 sde2
8 67 2048 sde3
8 68 2048 sde4
8 69 512 sde5
8 70 512 sde6
8 71 2048 sde7
8 72 16 sde8
8 73 512 sde9
8 74 512 sde10
8 75 97280 sde11
8 76 16384 sde12
8 77 1024 sde13
8 78 32768 sde14
8 79 8192 sde15
259 0 8192 sde16
259 1 16384 sde17
259 2 65536 sde18
259 3 65536 sde19
259 4 3080192 sde20
259 5 65536 sde21
259 6 4 sde22
259 7 1024 sde23
259 8 512 sde24
259 9 512 sde25
259 10 256 sde26
259 11 256 sde27
259 12 256 sde28
259 13 256 sde29
259 14 256 sde30
259 15 256 sde31
259 16 4 sde32
259 17 33424 sde33
259 18 2048 sde34
8 32 4096 sdc
8 33 4052 sdc1
8 80 1572864 sdf
8 81 2048 sdf1
8 82 2048 sdf2
8 83 4 sdf3
8 84 512 sdf4
Is there any way I can mount the correct partitions to /storage and /data to get access to the the photos using adb / fastboot?
or any other way, maybe like flashing new Stock Rom (without wiping) using adb sideload and then let it boot and access the files via MTP?
@HansiT4 Maybe this tool: https://github.com/Genymobile/scrcpy
Never used it myself as I've never had the need though.