Related
Hi
I'm using darktremor's a2sd. I've configured it to move apps and data to sd, but not dalvik cache.
Now i have installed around 90 apps, the ext4 partition of sd has 795mb free space and internal memory has 15mb of space. This my /data:
Code:
drwxrwxr-x 1 system system 2048 Apr 3 12:01 anr
lrwxrwxrwx 1 root root 11 Apr 3 20:25 app -> /sd-ext/app
lrwxrwxrwx 1 root root 19 Apr 3 20:25 app-private -> /sd-ext/app-private
drwx------ 1 system system 2048 Apr 3 20:31 backup
drwxrwx--x 1 system system 2048 Apr 3 06:21 dalvik-cache
lrwxrwxrwx 1 root root 12 Mar 29 21:17 data -> /sd-ext/data
drwxr-x--- 1 root log 2048 Mar 29 20:20 dontpanic
-rw-rw-rw- 1 root root 83017 Apr 3 20:31 dta2sd.log
drwxrwx--x 1 shell shell 2048 Mar 29 20:20 local
drwxrwx--- 1 root root 2048 Mar 29 20:20 lost+found
drwxrwx--t 1 system misc 2048 Apr 3 21:10 misc
drwx------ 1 root root 2048 Apr 3 20:25 property
drwxrwxrwx 1 system system 2048 Mar 29 20:24 sdcard
drwx------ 1 system system 2048 Mar 29 20:21 secure
drwxrwxr-x 1 system system 2048 Apr 3 21:28 system
drwxr-xr-x 1 system system 2048 Apr 2 20:40 tombstones
As the output of ls shows, i have /data/data linked to sd. So what has used my internal memory?
I'm using MIUI 2.3.23 on htc desire.
Sent from my HTC Desire using XDA
I think this thread is obsolete now, please go to
[DEV][REF] El Grande Partition Table Reference
instead, which contains more facts
Hi,
I want to create a list of Android partitions, to collect information for different purposes.
My current cause of investigation is about repartitioning emmc bricked Samsung phones, but the guide could collect all kinds of information (in short form, eventually with links to deeper investigations).
I want to format this as a living post, with new information added where appropriate (I assume the wiki would fit better, but I don't see a section to put this, also I don't know if fitting to Samsung only or Android in general until enough information is collected).
So let's start:
So let's visit partitions one by one:
GANG
* has zero size in PIT, seems to be hidden in the following unused area
* no real partition, but included in PITs
BOOT
* has zero size in PIT, seems to be hidden in the following unused area
EFS
* mounted on /efs
* contains many personalized information
* IMEI
* bluetooth MAC etc.
* restoration only possible with JTAG
* should be backuped!!!
SBL1, SBL2
* BL = boot loader
* S = Secondary?
* why do we have SBL1 *and* SBL2?
PARAM
* currently I don't know anything about this
KERNEL
* contains kernel (obviously)
* also contains recovery on some/many Samsung Galaxy phones (e.g. N7000)
* read only
RECOVERY
* seems to be unused on Samsung Galaxy N7000, KERNEL comes with recovery integrated
* read only
CACHE
* mounted on /cache
* temporary data
* can be cleared without loosing any important data
MODEM
* modem software for cell phone
* can be flashed from stock file
* read only?
FACTORYFS, system
* mounted on /system
* main OS code
* system apps
* read only
DATAFS, data
* mounted on /data
* user apps
* read/write
UMS, userdata
* mounted on /sdcard, sometimes /emmc
* sometimes called internal sd
HIDDEN, PRELOAD
* mounted on /preload
* purpose?
FOTA
* F = Factory?
* OTA = Over The Air
* may be used for Updates by stock ROM
Here are also some general thoughts about repartitioning these partitions to be mixed into the list later if it fits (just as a reminder):
* if you have a brick in a partition you cannot create a backup to restore afterwards
* partitions which have stock contents (not personalized) will be easy
* EFS cannot be restored without having a backup,
it contains nearly all really personalized information, with the most important data being the IMEI, which is unique to your phone. You find it printed on a sticker on your phone, but currently no one seems to be able to patch it into a generic copy of the EFS.
* some partitions will be needed to boot into recovery and/or download mode
I would assume BOOT, SBL1 and/or SBL2 are involved.
Some may be needed to boot into both recovery *and* download mode.
Some may be needed only for one of them.
If a PIT would move these, you cannot enter download and/or recovery again, thus your phone is nearly dead and only recoverable by JTAG.
* what about PARAM?
First of all, great initiative!
I have a SE Xperia Arc and the file structure differs a lot from your Samsung device.
Here is a list of the partitions, their current mount point(s) and filetype. I have put some useful references to the list. This will probably provide more accurate descriptions, rather than giving a brief explanation on each file system.
rootfs / rootfs [1]
tmpfs /dev tmpfs [2]
tmpfs /mnt/asec tmpfs
tmpfs /mnt/obb tmpfs
tmpfs /mnt/sdcard/.android_secure tmpfs
devpts /dev/pts devpts [3]
proc /proc proc [4]
sysfs /sys sysfs [5]
/dev/block/mtdblock0 /system yaffs2 [6][8]
/dev/block/mtdblock1 /cache yaffs2
/dev/block/mtdblock2 /system/vendor yaffs2
/dev/block/mtdblock3 /data yaffs2
/dev/block/vold/179:1 /mnt/sdcard vfat [7][9]
/dev/block/vold/179:1 /mnt/secure/asec vfat
References:
[1] rootfs
[2] tmpfs
[3] devpts
[4] proc
[5] sysfs
[6] yaffs2
[7] vfat Virtual FAT
[8] mtd
[9] vold
I also found two more links that could be useful in this thread.
Atrix HD Partition Research, How to use QUALCOMM eMMC MBR/EBR Partitioning plugin
hg42 said:
FOTA
* F = Factory?
* OTA = Over The Air
* may be used for Updates by stock ROM
Click to expand...
Click to collapse
F = firmware, http://en.wikipedia.org/wiki/FOTA_%28technology%29
Thanks, nice contribution.
Can you provide a dump of 'parted print' for your device?
Unfortunately, the parted partition command is not included among the Xperia Arc's stock binaries, nor in BusyBox 1.20.2 (but hopefully in the future).
Do you have a pre-compiled binary to share?
Here is what I can contribute to your collection for now:
Code:
[email protected]:/ # busybox fdisk -l
Linux localhost 2.6.32.9-perf #1 PREEMPT Wed Jul 4 12:32:24 2012 armv7l GNU/Linux
[email protected]:/ # busybox fdisk -l
Note: sector size is 4096 (not 512)
Disk [URL="http://shmilyxbq-compcache.googlecode.com/hg/README"]/dev/zram0[/URL]: 62 MB, 62914560 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 4096 = 65802240 bytes
Disk /dev/zram0 doesn't contain a valid partition table
k02a said:
Unfortunately, the parted partition command is not included among the Xperia Arc's stock binaries, nor in BusyBox 1.20.2 (but hopefully in the future).
Do you have a pre-compiled binary to share?
Click to expand...
Click to collapse
you can try the attachment to this post
but I'm not sure if an exynos processor (Samsung Galaxy Note N7000) has the same executable format than your phone, at least both have armv7l.
hg42 said:
but I'm not sure if an exynos processor (Samsung Galaxy Note N7000) has the same executable format than your phone, at least both have armv7l.
Click to expand...
Click to collapse
The parted binary worked fine, but the file system on the LT15i needs to be explored some day.
Code:
[email protected]:/ # parted
parted
GNU Parted 1.8.8.1.179-aef3
Using /dev/zram0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/zram0: unrecognised disk label
(parted)
k02a said:
The parted binary worked fine, but the file system on the LT15i needs to be explored some day.
Error: /dev/zram0: unrecognised disk label
Click to expand...
Click to collapse
can you post the output of " adb shell ls /dev/block/ "?
Sure.
Code:
[email protected]:/ $ ls -la /dev/block
ls -la /dev/block
brw------- root root 254, 0 1980-01-06 02:02 dm-0
brw------- root root 254, 8 1980-01-06 02:02 dm-8
brw------- root root 7, 0 1980-01-06 02:01 loop0
brw------- root root 7, 1 1980-01-06 02:01 loop1
brw-rw---- root root 7, 10 1980-01-06 02:02 loop10
brw-rw---- root root 7, 11 1980-01-06 02:02 loop11
brw-rw---- root root 7, 12 1980-01-06 02:02 loop12
brw------- root root 7, 2 1980-01-06 02:01 loop2
brw------- root root 7, 3 1980-01-06 02:01 loop3
brw------- root root 7, 4 1980-01-06 02:01 loop4
brw------- root root 7, 5 1980-01-06 02:01 loop5
brw------- root root 7, 6 1980-01-06 02:01 loop6
brw------- root root 7, 7 1980-01-06 02:01 loop7
brw-rw---- root root 7, 8 1980-01-06 02:02 loop8
brw-rw---- root root 7, 9 1980-01-06 02:02 loop9
brw------- root root 179, 0 1980-01-06 02:01 mmcblk0
brw------- root root 179, 1 1980-01-06 02:01 mmcblk0p1
brw------- root root 31, 0 1980-01-06 02:01 mtdblock0
brw------- root root 31, 1 1980-01-06 02:01 mtdblock1
brw------- root root 31, 2 1980-01-06 02:01 mtdblock2
brw------- root root 31, 3 1980-01-06 02:01 mtdblock3
drwxr-xr-x root root 1980-01-06 02:01 platform
brw------- root root 1, 0 1980-01-06 02:01 ram0
brw------- root root 1, 1 1980-01-06 02:01 ram1
brw------- root root 1, 2 1980-01-06 02:01 ram2
brw------- root root 1, 3 1980-01-06 02:01 ram3
brw------- root root 1, 4 1980-01-06 02:01 ram4
brw------- root root 1, 5 1980-01-06 02:01 ram5
brw------- root root 1, 6 1980-01-06 02:01 ram6
brw------- root root 1, 7 1980-01-06 02:01 ram7
drwxr-xr-x root root 1980-01-06 02:01 vold
brw------- root root 253, 0 1980-01-06 02:01 zram0
The listing you were asking for is not as interesting as the following:
Code:
[email protected]:/ # ls -la /sys/devices/virtual/block/zram0
ls -la /sys/devices/virtual/block/zram0
-r--r--r-- root root 4096 2012-09-06 00:18 alignment_offset
lrwxrwxrwx root root 2012-09-06 00:18 bdi -> ../../bdi/253:0
-r--r--r-- root root 4096 2012-09-06 00:18 capability
-r--r--r-- root root 4096 2012-09-06 00:18 compr_data_size
-r--r--r-- root root 4096 2012-09-06 00:18 dev
-rw-r--r-- root root 4096 1980-01-06 02:01 disksize
-r--r--r-- root root 4096 2012-09-06 00:18 ext_range
drwxr-xr-x root root 2012-09-06 00:18 holders
-r--r--r-- root root 4096 2012-09-06 00:18 inflight
-r--r--r-- root root 4096 2012-09-06 00:18 initstate
-r--r--r-- root root 4096 2012-09-06 00:18 invalid_io
-r--r--r-- root root 4096 2012-09-06 00:18 mem_used_total
-r--r--r-- root root 4096 2012-09-06 00:18 notify_free
-r--r--r-- root root 4096 2012-09-06 00:18 num_reads
-r--r--r-- root root 4096 2012-09-06 00:18 num_writes
-r--r--r-- root root 4096 2012-09-06 00:18 orig_data_size
drwxr-xr-x root root 2012-09-06 00:18 power
drwxr-xr-x root root 2012-09-06 00:18 queue
-r--r--r-- root root 4096 2012-09-06 00:18 range
-r--r--r-- root root 4096 2012-09-06 00:18 removable
--w------- root root 4096 2012-09-06 00:18 reset
-r--r--r-- root root 4096 2012-09-06 00:18 ro
-r--r--r-- root root 4096 2012-09-06 00:18 size
drwxr-xr-x root root 2012-09-06 00:18 slaves
-r--r--r-- root root 4096 2012-09-06 00:18 stat
lrwxrwxrwx root root 2012-09-06 00:18 subsystem -> ../../../../
class/block
-rw-r--r-- root root 4096 2012-09-06 00:18 uevent
-r--r--r-- root root 4096 2012-09-06 00:18 zero_pages
Time to get some sleep.
k02a said:
Sure.
Code:
[email protected]:/ $ ls -la /dev/block
ls -la /dev/block
...
brw------- root root 179, 0 1980-01-06 02:01 mmcblk0
brw------- root root 179, 1 1980-01-06 02:01 mmcblk0p1
brw------- root root 31, 0 1980-01-06 02:01 mtdblock0
brw------- root root 31, 1 1980-01-06 02:01 mtdblock1
brw------- root root 31, 2 1980-01-06 02:01 mtdblock2
brw------- root root 31, 3 1980-01-06 02:01 mtdblock3
...
The listing you were asking for is not as interesting as the following:
Code:
[email protected]:/ # ls -la /sys/devices/virtual/block/zram0
ls -la /sys/devices/virtual/block/zram0
...
[/QUOTE]
why? Do you mean mtdblock0-3 are really located on zram0?
Or what else?
mtdblock0-3 don't seem to be partitions of a block device, like mmcblk0p1 is a partition on mmcblk0
Click to expand...
Click to collapse
hg42 said:
why? Do you mean mtdblock0-3 are really located on zram0?
Or what else?
mtdblock0-3 don't seem to be partitions of a block device, like mmcblk0p1 is a partition on mmcblk0
Click to expand...
Click to collapse
Sorry for my ambiguousness...
After having a bad nights' sleep, I made some re-thinking.
I dd'ed the /dev/zram0 (62 914 560 bytes). This value also corresponds to the content found in /sys/block/zram0/disksize and I find it unlikely that the OS keeps the entire amount of mtdblocks within this memory constraint, even if they are compressed. I have not tried to mount the zram-image on a Linux system, so I cannot tell anything about its content. My belief is that this image carries some RAM contents and perhaps some cache information.
Did you find anything similar in your Samsung device?
The mmcblk:s seem to represent the MicroSD-card device and I assume the mmcblk0p1 is the (only) partition.
k02a said:
Sorry for my ambiguousness...
After having a bad nights' sleep, I made some re-thinking.
I dd'ed the /dev/zram0 (62 914 560 bytes). This value also corresponds to the content found in /sys/block/zram0/disksize and I find it unlikely that the OS keeps the entire amount of mtdblocks within this memory constraint, even if they are compressed. I have not tried to mount the zram-image on a Linux system, so I cannot tell anything about its content. My belief is that this image carries some RAM contents and perhaps some cache information.
Did you find anything similar in your Samsung device?
The mmcblk:s seem to represent the MicroSD-card device and I assume the mmcblk0p1 is the (only) partition.
Click to expand...
Click to collapse
we have these block devices:
Code:
[email protected]:/ $ ls -lF /dev/block/
brw------- 1 root root 7, 0 Sep 6 08:28 loop0
brw------- 1 root root 7, 1 Sep 6 08:28 loop1
brw------- 1 root root 7, 2 Sep 6 08:28 loop2
brw------- 1 root root 7, 3 Sep 6 08:28 loop3
brw------- 1 root root 7, 4 Sep 6 08:28 loop4
brw------- 1 root root 7, 5 Sep 6 08:28 loop5
brw------- 1 root root 7, 6 Sep 6 08:28 loop6
brw------- 1 root root 7, 7 Sep 6 08:28 loop7
brw------- 1 root root 179, 0 Sep 6 08:28 mmcblk0
brw------- 1 root root 179, 1 Sep 6 08:28 mmcblk0p1
brw------- 1 root root 259, 2 Sep 6 08:28 mmcblk0p10
brw------- 1 root root 259, 3 Sep 6 08:28 mmcblk0p11
brw------- 1 root root 259, 4 Sep 6 08:28 mmcblk0p12
brw------- 1 root root 179, 2 Sep 6 08:28 mmcblk0p2
brw------- 1 root root 179, 3 Sep 6 08:28 mmcblk0p3
brw------- 1 root root 179, 4 Sep 6 08:28 mmcblk0p4
brw------- 1 root root 179, 5 Sep 6 08:28 mmcblk0p5
brw------- 1 root root 179, 6 Sep 6 08:28 mmcblk0p6
brw------- 1 root root 179, 7 Sep 6 08:28 mmcblk0p7
brw-rw---- 1 system radio 259, 0 Sep 6 08:28 mmcblk0p8
brw------- 1 root root 259, 1 Sep 6 08:28 mmcblk0p9
brw------- 1 root root 179, 8 Sep 6 08:28 mmcblk1
brw------- 1 root root 179, 9 Sep 6 08:28 mmcblk1p1
drwxr-xr-x 4 root root 0 Sep 6 08:28 platform/
brw------- 1 root root 1, 0 Sep 6 08:28 ram0
brw------- 1 root root 1, 1 Sep 6 08:28 ram1
brw------- 1 root root 1, 10 Sep 6 08:28 ram10
brw------- 1 root root 1, 11 Sep 6 08:28 ram11
brw------- 1 root root 1, 12 Sep 6 08:28 ram12
brw------- 1 root root 1, 13 Sep 6 08:28 ram13
brw------- 1 root root 1, 14 Sep 6 08:28 ram14
brw------- 1 root root 1, 15 Sep 6 08:28 ram15
brw------- 1 root root 1, 2 Sep 6 08:28 ram2
brw------- 1 root root 1, 3 Sep 6 08:28 ram3
brw------- 1 root root 1, 4 Sep 6 08:28 ram4
brw------- 1 root root 1, 5 Sep 6 08:28 ram5
brw------- 1 root root 1, 6 Sep 6 08:28 ram6
brw------- 1 root root 1, 7 Sep 6 08:28 ram7
brw------- 1 root root 1, 8 Sep 6 08:28 ram8
brw------- 1 root root 1, 9 Sep 6 08:28 ram9
drwxr-xr-x 2 root root 0 Sep 6 08:28 vold/
The ram* may be what is zram in your device.
The 'z' may indeed mean compression.
There are several tmpfs in our device (e.g. /tmp and /dev, perhaps they use these ram disks).
Also the root file system where everything is mounted runs in ram.
The zram0 seems to act like some kind of swap RAM and was obviously added to the latest SE 2011 firmware version [1].
My guess is that Sony Ericsson decided to pick the compressed alternative, due to the smaller flash memory in their Xperia 2011 devices. This solution probably costs some clock cycles, but I assume it gains in overall internal storage capacity.
I found an interesting thread where sirkay showed how to initiate/alter the zram size.
[1] questions/problems with 4.1.B.0.587 firmware
You guys are confusing.
The Xperia NAND disk device is translated to an MTD block device in the Linux world. The partition boundaries are hardcoded in the bootloader passed to the kernel via the ATAGs parameters. You can see those partitions via /proc/mtd
Code:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00040000 "system"
mtd1: 00600000 00040000 "appslog"
mtd2: 06580000 00040000 "cache"
mtd3: 1a400000 00040000 "userdata"
Still those are only the partitions the bootlooader chooses to expose to the kernel. In reality, there are more, unknown to the kernel.
kuisma said:
You guys are confusing.
The Xperia NAND disk device is translated to an MTD block device in the Linux world. The partition boundaries are hardcoded in the bootloader passed to the kernel via the ATAGs parameters. You can see those partitions via /proc/mtd
Code:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00040000 "system"
mtd1: 00600000 00040000 "appslog"
mtd2: 06580000 00040000 "cache"
mtd3: 1a400000 00040000 "userdata"
Still those are only the partitions the bootlooader chooses to expose to the kernel. In reality, there are more, unknown to the kernel.
Click to expand...
Click to collapse
Thanks for clearing up, this fits my conclusions.
Never saw such fixed devices before.
hg42 said:
Thanks for clearing up, this fits my conclusions.
Never saw such fixed devices before.
Click to expand...
Click to collapse
I'd say this is the way it's most commonly done in Android devices, using a raw NAND device with the MTD translation layer. It's far more uncommon using block devices, such as MMC devices as the primary internal memory.
kuisma said:
You guys are confusing.
The Xperia NAND disk device is translated to an MTD block device in the Linux world. The partition boundaries are hardcoded in the bootloader passed to the kernel via the ATAGs parameters. You can see those partitions via /proc/mtd
Code:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00040000 "system"
mtd1: 00600000 00040000 "appslog"
mtd2: 06580000 00040000 "cache"
mtd3: 1a400000 00040000 "userdata"
Still those are only the partitions the bootlooader chooses to expose to the kernel. In reality, there are more, unknown to the kernel.
Click to expand...
Click to collapse
Thanks for this. :good:
I am still curious about the possibility to gain boot or root partition access in Xperia?
Many other devices come with this feature, e.g. HTC Incredible S, HTC Vision, Acer Liquid Metal and on the widely spread article HOWTO: Unpack, Edit, and Re-Pack Boot Images).
Oh, by the way...
I found a collection with recovery images on OnlineNandroid.
k02a said:
Thanks for this. :good:
I am still curious about the possibility to gain boot or root partition access in Xperia?
Many other devices come with this feature, e.g. HTC Incredible S, HTC Vision, Acer Liquid Metal and on the widely spread article HOWTO: Unpack, Edit, and Re-Pack Boot Images).
Click to expand...
Click to collapse
In Xperia, the boot partition is not visible to the Linux kernel, so you can't simply dd it to an image file. The easiest way is running Sony Update Service reflashing your phone with the current firmware, and then copy the temporary files it downloaded, recreating the FTF file using Flashtool. Unzip the FTF and you've got the boot.img. Now split it, do whatever you want to change and flash it using fastboot. There's a YouTube video showing this in detail. Search for it. Or download the firmware FTF directly from a trusted source.
I looked in fota0.sin and found a few more partition names on the Xperia (Active):
Code:
amss
amss_fs
fota0
fota1
dsp1
boot
system
userdata
cache
image_backup
amss_log
vendor
ramdump
Thanks a lot for this, a really valuable post!
I know I wont find the help I need to do what I want here, but ill provide the stuff from my Galaxy Note tomorrow (partition layout/vold)...
My Galaxy Note is nice, but 2GB is a joke for apps, and damnit I want my sdcard to actually be mounted as /sdcard! (PITA for apps that utilize /sdcard for game data and backups, not to mention having a 32GB or 64GB makes the joke 10GB internal... a JOKE!)
hg42 said:
we have these block devices:
Code:
[email protected]:/ $ ls -lF /dev/block/
brw------- 1 root root 7, 0 Sep 6 08:28 loop0
brw------- 1 root root 7, 1 Sep 6 08:28 loop1
brw------- 1 root root 7, 2 Sep 6 08:28 loop2
brw------- 1 root root 7, 3 Sep 6 08:28 loop3
brw------- 1 root root 7, 4 Sep 6 08:28 loop4
brw------- 1 root root 7, 5 Sep 6 08:28 loop5
brw------- 1 root root 7, 6 Sep 6 08:28 loop6
brw------- 1 root root 7, 7 Sep 6 08:28 loop7
brw------- 1 root root 179, 0 Sep 6 08:28 mmcblk0
brw------- 1 root root 179, 1 Sep 6 08:28 mmcblk0p1
brw------- 1 root root 259, 2 Sep 6 08:28 mmcblk0p10
brw------- 1 root root 259, 3 Sep 6 08:28 mmcblk0p11
brw------- 1 root root 259, 4 Sep 6 08:28 mmcblk0p12
brw------- 1 root root 179, 2 Sep 6 08:28 mmcblk0p2
brw------- 1 root root 179, 3 Sep 6 08:28 mmcblk0p3
brw------- 1 root root 179, 4 Sep 6 08:28 mmcblk0p4
brw------- 1 root root 179, 5 Sep 6 08:28 mmcblk0p5
brw------- 1 root root 179, 6 Sep 6 08:28 mmcblk0p6
brw------- 1 root root 179, 7 Sep 6 08:28 mmcblk0p7
brw-rw---- 1 system radio 259, 0 Sep 6 08:28 mmcblk0p8
brw------- 1 root root 259, 1 Sep 6 08:28 mmcblk0p9
brw------- 1 root root 179, 8 Sep 6 08:28 mmcblk1
brw------- 1 root root 179, 9 Sep 6 08:28 mmcblk1p1
drwxr-xr-x 4 root root 0 Sep 6 08:28 platform/
brw------- 1 root root 1, 0 Sep 6 08:28 ram0
brw------- 1 root root 1, 1 Sep 6 08:28 ram1
brw------- 1 root root 1, 10 Sep 6 08:28 ram10
brw------- 1 root root 1, 11 Sep 6 08:28 ram11
brw------- 1 root root 1, 12 Sep 6 08:28 ram12
brw------- 1 root root 1, 13 Sep 6 08:28 ram13
brw------- 1 root root 1, 14 Sep 6 08:28 ram14
brw------- 1 root root 1, 15 Sep 6 08:28 ram15
brw------- 1 root root 1, 2 Sep 6 08:28 ram2
brw------- 1 root root 1, 3 Sep 6 08:28 ram3
brw------- 1 root root 1, 4 Sep 6 08:28 ram4
brw------- 1 root root 1, 5 Sep 6 08:28 ram5
brw------- 1 root root 1, 6 Sep 6 08:28 ram6
brw------- 1 root root 1, 7 Sep 6 08:28 ram7
brw------- 1 root root 1, 8 Sep 6 08:28 ram8
brw------- 1 root root 1, 9 Sep 6 08:28 ram9
drwxr-xr-x 2 root root 0 Sep 6 08:28 vold/
Click to expand...
Click to collapse
From the above list is it possible to know the boot paritions.
on S2_lte_I9210 /proc/partitions list the system partition as /dev/block/mmcblk0p24 /system but not the boot partition.
I'm eagerly waiting to do boot.img backup using via dd command
---------- Post added at 04:20 PM ---------- Previous post was at 04:16 PM ----------
# cat /proc/partitions
major minor #blocks name
179 0 15387648 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 500 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 2500 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 500 mmcblk0p9
179 10 500 mmcblk0p10
179 11 500 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 100352 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 100352 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 10240 mmcblk0p23
179 24 677888 mmcblk0p24
179 25 2099200 mmcblk0p25
179 26 309248 mmcblk0p26
179 27 132096 mmcblk0p27
179 28 11738112 mmcblk0p28
179 32 15558144 mmcblk1
179 33 15557120 mmcblk1p1
Click to expand...
Click to collapse
partition list on samsung galaxy S2_lte I9210
I am newbie on android , and I just though of few question after reading some of the partition. http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
But what I do not understand is , are those partition a folder or real partition ?
As for commonly known , Windows partition consist of either 4 Primary partition or 3 primary 1 extended partition.
-Master boot record partition
-Primary (max 4 , min 0)
-Extended partition ( multiple logical partition )
What about android ? Let me know whether I am wrong
-/boot ( equal to MBR )
-/system /recovery /data /cache /misc (1 parimary partition with different path like /system32 , /Programs files /My Document and etc)
-/SDcard0 (Extended partition )
External SDcard = something like external hard disk.
Overall any android Device have 2 partition ,1 Primary (/system /recovery /data /cache /misc) and 1 Extended logical ( SDcard0)
Please correct me if I'm getting the idea wrong.
Any expert here able to clear out or confirm them ?
Kindly let me know the correct answer.
I am just a starter
It's a hard question ?
Even for a dev too ?
xdadfm said:
I am newbie on android , and I just though of few question after reading some of the partition. http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
But what I do not understand is , are those partition a folder or real partition ?
As for commonly known , Windows partition consist of either 4 Primary partition or 3 primary 1 extended partition.
-Master boot record partition
-Primary (max 4 , min 0)
-Extended partition ( multiple logical partition )
What about android ? Let me know whether I am wrong
-/boot ( equal to MBR )
-/system /recovery /data /cache /misc (1 parimary partition with different path like /system32 , /Programs files /My Document and etc)
-/SDcard0 (Extended partition )
External SDcard = something like external hard disk.
Overall any android Device have 2 partition ,1 Primary (/system /recovery /data /cache /misc) and 1 Extended logical ( SDcard0)
Please correct me if I'm getting the idea wrong.
Click to expand...
Click to collapse
I'm not an expert but as far as I know :
android has 5 partitions ..
/boot
/system
/recovery
/data
/cache
and there Is the SD card partition
/sdcard
Boot: Contains Kernal and Ramdisk ,, Without This Partition The Device Simply Won't Boot
System: Contains The Entire Android System,Android User Interface and System Apps
Recovery: Another Booting Option For Performing Advanced Recovery And maintenance Operations
Data: Contains The User Data Such As Contacts,Messages ... etc
Cache: Where Android Stores Applications Components and Cache
Hope It Helps
falf123 said:
I'm not an expert but as far as I know :
android has 5 partitions ..
/boot
/system
/recovery
/data
/cache
and there Is the SD card partition
/sdcard
Boot: Contains Kernal and Ramdisk ,, Without This Partition The Device Simply Won't Boot
System: Contains The Entire Android System,Android User Interface and System Apps
Recovery: Another Booting Option For Performing Advanced Recovery And maintenance Operations
Data: Contains The User Data Such As Contacts,Messages ... etc
Cache: Where Android Stores Applications Components and Cache
Hope It Helps
Click to expand...
Click to collapse
The partition is actually real partition like what we did to a hardisk ?
Possible to have 5 partition on a Flash drive ? as for window , maximum is 4 primary partition .
The question you are asking requires a bit of an explanation, but I will do my best (forgive me if I gloss over some things).
When a windows PC boots up, it initializes CMOS which searches for the hard drive or other boot device based on the order set up in BIOS/CMOS. Once it finds a storage device it attempts to boot that device (i.e. hdd=hard disk drive, eMMC=electronic MultiMedia Card). There is a bit set somewhere that determines what type of filing system is on the drive. In linux, you can see the partition table by using fdisk (devices are located in the /dev folder and look like /dev/sda or /dev/mmcblk0, depending on the type and how many there are). Therefore the command would be 'fdisk /dev/sda' and let's take a look at that...
Welcome to fdisk (util-linux 2.32.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: xxxxxxxxxx (omitted)
Device Start End Sectors Size Type
/dev/sda1 2048 2050047 2048000 1000M Windows recovery environment
/dev/sda2 2050048 2582527 532480 260M EFI System
/dev/sda3 2582528 4630527 2048000 1000M Windows recovery environment
/dev/sda4 4630528 4892671 262144 128M Microsoft reserved
/dev/sda5 4892672 1619314687 1614422016 769.8G Microsoft basic data
/dev/sda6 1619314688 1845840078 226525391 108G Microsoft basic data
/dev/sda7 1845840094 1853995007 8154914 3.9G Microsoft basic data
/dev/sda8 1853995008 1858228223 4233216 2G Windows recovery environment
/dev/sda9 1858228224 1859151871 923648 451M Windows recovery environment
/dev/sda10 1859151872 1911580671 52428800 25G Microsoft basic data
/dev/sda11 1911580672 1953523711 41943040 20G Windows recovery environment
As you can see, my device "sda" has 11 partitions. 1,3,8,9,11 are all recovery partitions, 2 is an EFI partition, etc. A short list of possibilities...
1 EFI System C12A7328-F81F-11D2-BA4B-00A0C93EC93B
2 MBR partition scheme 024DEE41-33E7-11D3-9D69-0008C781F39F
3 Intel Fast Flash D3BFE2DE-3DAF-11DF-BA40-E3A556D89593
4 BIOS boot 21686148-6449-6E6F-744E-656564454649
5 Sony boot partition F4019732-066E-4E12-8273-346C5641494F
6 Lenovo boot partition BFBFAFE7-A34F-448A-9A5B-6213EB736C22
7 PowerPC PReP boot 9E1A2D38-C612-4316-AA26-8B49521E5A8B
8 ONIE boot 7412F7D5-A156-4B13-81DC-867174929325
9 ONIE config D4E6E2CD-4469-46F3-B5CB-1BFF57AFC149
10 Microsoft reserved E3C9E316-0B5C-4DB8-817D-F92DF00215AE
11 Microsoft basic data EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
12 Microsoft LDM metadata 5808C8AA-7E8F-42E0-85D2-E1E90434CFB3
13 Microsoft LDM data AF9B60A0-1431-4F62-BC68-3311714A69AD
14 Windows recovery environment DE94BBA4-06D1-4D40-A16A-BFD50179D6AC
15 IBM General Parallel Fs 37AFFC90-EF7D-4E96-91C3-2D7AE055B174
16 Microsoft Storage Spaces E75CAF8F-F680-4CEE-AFA3-B001E56EFC2D
17 HP-UX data 75894C1E-3AEB-11D3-B7C1-7B03A0000000
18 HP-UX service E2A1E728-32E3-11D6-A682-7B03A0000000
19 Linux swap 0657FD6D-A4AB-43C4-84E5-0933C84B4F4F
20 Linux filesystem 0FC63DAF-8483-4772-8E79-3D69D8477DE4
21 Linux server data 3B8F8425-20E0-4F3B-907F-1A25A76F98E8
22 Linux root (x86) 44479540-F297-41B2-9AF7-D131D5F0458A
23 Linux root (ARM) 69DAD710-2CE4-4E3C-B16C-21A1D49ABED3
24 Linux root (x86-64) 4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
Each partition stores data differently. Windows 95 all the way through Windows ME uses FAT (File Allocation Table) and doesn't use user permissions on files. NTFS (Windows NT File System) is the updated version of FAT which had its evolution and caveats. NTFS is the Windows standard now because it 1) can handle file systems larger than 2GB and 2) has the ability to set user file permissions so only the owner can read/write/execute certain files. Android uses ext4, which is a linux file system. The difference is that linux doesn't have drive letters. In windows, C:\ is your normal hard drive, A:\ is a floppy drive, and all disk devices (Thumb drive, CD ROM drive, tape backup, etc) have a letter and are almost always "mounted". In linux... the "root" is / and every device is either mounted as a subfolder or listed in /dev. So if I do a ls /dev I get this as a result (ls is the same command as dir for windows/dos):
ls -l
total 0
crw-r--r-- 1 root root 10, 235 Aug 27 05:17 autofs
drwxr-xr-x 2 root root 340 Aug 27 05:34 block
drwxr-xr-x 2 root root 60 Aug 27 05:34 bsg
crw------- 1 root root 10, 234 Aug 27 05:17 btrfs-control
drwxr-xr-x 3 root root 60 Aug 26 22:17 bus
drwxr-xr-x 2 root root 3580 Aug 27 14:00 char
crw------- 1 root root 5, 1 Aug 27 05:17 console
lrwxrwxrwx 1 root root 11 Aug 26 22:17 core -> /proc/kcore
drwxr-xr-x 2 root root 60 Aug 26 22:17 cpu
crw------- 1 root root 10, 62 Aug 27 05:17 cpu_dma_latency
crw------- 1 root root 10, 203 Aug 27 05:17 cuse
drwxr-xr-x 8 root root 160 Aug 26 22:17 disk
drwxr-xr-x 3 root root 100 Aug 27 05:17 dri
crw------- 1 root root 245, 0 Aug 27 05:17 drm_dp_aux0
crw-rw---- 1 root video 29, 0 Aug 27 05:17 fb0
lrwxrwxrwx 1 root root 13 Aug 26 22:17 fd -> /proc/self/fd
crw-rw-rw- 1 root root 1, 7 Aug 27 05:17 full
crw-rw-rw- 1 root root 10, 229 Aug 27 05:17 fuse
crw------- 1 root root 247, 0 Aug 27 05:17 hidraw0
crw------- 1 root root 247, 1 Aug 27 05:17 hidraw1
crw------- 1 root root 10, 228 Aug 27 05:17 hpet
drwxr-xr-x 2 root root 0 Aug 27 05:17 hugepages
lrwxrwxrwx 1 root root 12 Aug 27 05:17 initctl -> /run/initctl
drwxr-xr-x 4 root root 580 Aug 27 05:44 input
crw-r--r-- 1 root root 1, 11 Aug 27 05:17 kmsg
crw-rw----+ 1 root kvm 10, 232 Aug 27 05:17 kvm
lrwxrwxrwx 1 root root 28 Aug 27 05:17 log -> /run/systemd/journal/dev-log
crw-rw---- 1 root disk 10, 237 Aug 27 05:17 loop-control
drwxr-xr-x 2 root root 60 Aug 27 05:17 mapper
crw-rw---- 1 root video 243, 0 Aug 27 05:17 media0
crw-rw---- 1 root video 243, 1 Aug 27 05:42 media1
crw-rw---- 1 root video 243, 2 Aug 27 05:43 media2
crw-rw---- 1 root video 243, 3 Aug 27 05:44 media3
crw-rw---- 1 root video 243, 4 Aug 27 05:44 media4
crw-rw---- 1 root video 243, 5 Aug 27 05:44 media5
crw-rw---- 1 root video 243, 6 Aug 27 05:44 media6
crw-rw---- 1 root video 243, 7 Aug 27 05:44 media7
crw------- 1 root root 244, 0 Aug 27 05:17 mei0
crw-r----- 1 root kmem 1, 1 Aug 27 05:17 mem
crw------- 1 root root 10, 59 Aug 27 05:17 memory_bandwidth
brw-rw---- 1 root disk 179, 0 Aug 27 05:17 mmcblk0
brw-rw---- 1 root disk 179, 1 Aug 27 05:17 mmcblk0p1
brw-rw---- 1 root disk 179, 2 Aug 27 05:17 mmcblk0p2
drwxrwxrwt 2 root root 40 Aug 26 22:17 mqueue
drwxr-xr-x 2 root root 60 Aug 27 05:17 net
crw------- 1 root root 10, 61 Aug 27 05:17 network_latency
crw------- 1 root root 10, 60 Aug 27 05:17 network_throughput
crw-rw-rw- 1 root root 1, 3 Aug 27 05:17 null
crw-r----- 1 root kmem 1, 4 Aug 27 05:17 port
crw------- 1 root root 108, 0 Aug 27 05:17 ppp
crw------- 1 root root 10, 1 Aug 27 05:17 psaux
crw-rw-rw- 1 root tty 5, 2 Aug 27 14:05 ptmx
drwxr-xr-x 2 root root 0 Aug 26 22:17 pts
crw-rw-rw- 1 root root 1, 8 Aug 27 05:17 random
crw-rw-r--+ 1 root netdev 10, 58 Aug 27 05:17 rfkill
lrwxrwxrwx 1 root root 4 Aug 27 05:17 rtc -> rtc0
crw------- 1 root root 252, 0 Aug 27 05:17 rtc0
brw-rw---- 1 root disk 8, 0 Aug 27 05:17 sda
brw-rw---- 1 root disk 8, 1 Aug 27 05:17 sda1
brw-rw---- 1 root disk 8, 10 Aug 27 05:17 sda10
brw-rw---- 1 root disk 8, 11 Aug 27 05:17 sda11
brw-rw---- 1 root disk 8, 2 Aug 27 05:17 sda2
brw-rw---- 1 root disk 8, 3 Aug 27 05:17 sda3
brw-rw---- 1 root disk 8, 4 Aug 27 05:17 sda4
brw-rw---- 1 root disk 8, 5 Aug 27 05:17 sda5
brw-rw---- 1 root disk 8, 6 Aug 27 05:17 sda6
brw-rw---- 1 root disk 8, 7 Aug 27 05:17 sda7
brw-rw---- 1 root disk 8, 8 Aug 27 05:17 sda8
brw-rw---- 1 root disk 8, 9 Aug 27 05:17 sda9
crw-rw---- 1 root disk 21, 0 Aug 27 05:17 sg0
drwxrwxrwt 2 root root 40 Aug 27 14:05 shm
crw------- 1 root root 10, 231 Aug 27 05:17 snapshot
drwxr-xr-x 3 root root 220 Aug 27 06:31 snd
lrwxrwxrwx 1 root root 15 Aug 26 22:17 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root 15 Aug 26 22:17 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root 15 Aug 26 22:17 stdout -> /proc/self/fd/1
crw-rw-rw- 1 root tty 5, 0 Aug 27 13:16 tty
crw--w---- 1 root tty 4, 0 Aug 27 05:17 tty0
crw--w---- 1 root tty 4, 1 Aug 27 05:18 tty1
crw--w---- 1 root tty 4, 10 Aug 27 05:17 tty10
crw--w---- 1 root tty 4, 11 Aug 27 05:17 tty11
crw--w---- 1 root tty 4, 12 Aug 27 05:17 tty12
crw--w---- 1 root tty 4, 13 Aug 27 05:17 tty13
crw--w---- 1 root tty 4, 14 Aug 27 05:17 tty14
crw--w---- 1 root tty 4, 15 Aug 27 05:17 tty15
crw--w---- 1 root tty 4, 16 Aug 27 05:17 tty16
crw--w---- 1 root tty 4, 17 Aug 27 05:17 tty17
crw--w---- 1 root tty 4, 18 Aug 27 05:17 tty18
crw--w---- 1 root tty 4, 19 Aug 27 05:17 tty19
crw--w---- 1 root tty 4, 2 Aug 27 05:17 tty2
crw--w---- 1 root tty 4, 20 Aug 27 05:17 tty20
crw--w---- 1 root tty 4, 21 Aug 27 05:17 tty21
crw--w---- 1 root tty 4, 22 Aug 27 05:17 tty22
crw--w---- 1 root tty 4, 23 Aug 27 05:17 tty23
crw--w---- 1 root tty 4, 24 Aug 27 05:17 tty24
crw--w---- 1 root tty 4, 25 Aug 27 05:17 tty25
crw--w---- 1 root tty 4, 26 Aug 27 05:17 tty26
crw--w---- 1 root tty 4, 27 Aug 27 05:17 tty27
crw--w---- 1 root tty 4, 28 Aug 27 05:17 tty28
crw--w---- 1 root tty 4, 29 Aug 27 05:17 tty29
crw--w---- 1 root tty 4, 3 Aug 27 05:17 tty3
crw--w---- 1 root tty 4, 30 Aug 27 05:17 tty30
crw--w---- 1 root tty 4, 31 Aug 27 05:17 tty31
crw--w---- 1 root tty 4, 32 Aug 27 05:17 tty32
crw--w---- 1 root tty 4, 33 Aug 27 05:17 tty33
crw--w---- 1 root tty 4, 34 Aug 27 05:17 tty34
crw--w---- 1 root tty 4, 35 Aug 27 05:17 tty35
crw--w---- 1 root tty 4, 36 Aug 27 05:17 tty36
crw--w---- 1 root tty 4, 37 Aug 27 05:17 tty37
crw--w---- 1 root tty 4, 38 Aug 27 05:17 tty38
crw--w---- 1 root tty 4, 39 Aug 27 05:17 tty39
crw--w---- 1 root tty 4, 4 Aug 27 05:17 tty4
crw--w---- 1 root tty 4, 40 Aug 27 05:17 tty40
crw--w---- 1 root tty 4, 41 Aug 27 05:17 tty41
crw--w---- 1 root tty 4, 42 Aug 27 05:17 tty42
crw--w---- 1 root tty 4, 43 Aug 27 05:17 tty43
crw--w---- 1 root tty 4, 44 Aug 27 05:17 tty44
crw--w---- 1 root tty 4, 45 Aug 27 05:17 tty45
crw--w---- 1 root tty 4, 46 Aug 27 05:17 tty46
crw--w---- 1 root tty 4, 47 Aug 27 05:17 tty47
crw--w---- 1 root tty 4, 48 Aug 27 05:17 tty48
crw--w---- 1 root tty 4, 49 Aug 27 05:17 tty49
crw--w---- 1 root tty 4, 5 Aug 27 05:17 tty5
crw--w---- 1 root tty 4, 50 Aug 27 05:17 tty50
crw--w---- 1 root tty 4, 51 Aug 27 05:17 tty51
crw--w---- 1 root tty 4, 52 Aug 27 05:17 tty52
crw--w---- 1 root tty 4, 53 Aug 27 05:17 tty53
crw--w---- 1 root tty 4, 54 Aug 27 05:17 tty54
crw--w---- 1 root tty 4, 55 Aug 27 05:17 tty55
crw--w---- 1 root tty 4, 56 Aug 27 05:17 tty56
crw--w---- 1 root tty 4, 57 Aug 27 05:17 tty57
crw--w---- 1 root tty 4, 58 Aug 27 05:17 tty58
crw--w---- 1 root tty 4, 59 Aug 27 05:17 tty59
crw--w---- 1 root tty 4, 6 Aug 27 05:17 tty6
crw--w---- 1 root tty 4, 60 Aug 27 05:17 tty60
crw--w---- 1 root tty 4, 61 Aug 27 05:17 tty61
crw--w---- 1 root tty 4, 62 Aug 27 05:17 tty62
crw--w---- 1 root tty 4, 63 Aug 27 05:17 tty63
crw--w---- 1 root tty 4, 7 Aug 27 05:18 tty7
crw--w---- 1 root tty 4, 8 Aug 27 05:17 tty8
crw--w---- 1 root tty 4, 9 Aug 27 05:17 tty9
crw-rw---- 1 root dialout 4, 64 Aug 27 05:17 ttyS0
crw-rw---- 1 root dialout 4, 65 Aug 27 05:17 ttyS1
crw-rw---- 1 root dialout 4, 66 Aug 27 05:17 ttyS2
crw-rw---- 1 root dialout 4, 67 Aug 27 05:17 ttyS3
crw------- 1 root root 10, 239 Aug 27 05:17 uhid
crw------- 1 root root 10, 223 Aug 27 05:17 uinput
crw-rw-rw- 1 root root 1, 9 Aug 27 05:17 urandom
drwxr-xr-x 2 root root 80 Aug 27 09:50 usb
drwxr-xr-x 4 root root 80 Aug 27 05:17 v4l
crw------- 1 root root 10, 57 Aug 27 05:18 vboxdrv
crw------- 1 root root 10, 56 Aug 27 05:18 vboxdrvu
crw------- 1 root root 10, 55 Aug 27 05:18 vboxnetctl
drwxr-x--- 4 root vboxusers 80 Aug 27 05:17 vboxusb
crw-rw---- 1 root tty 7, 0 Aug 27 05:17 vcs
crw-rw---- 1 root tty 7, 1 Aug 27 05:17 vcs1
crw-rw---- 1 root tty 7, 2 Aug 27 05:17 vcs2
crw-rw---- 1 root tty 7, 3 Aug 27 05:17 vcs3
crw-rw---- 1 root tty 7, 4 Aug 27 05:17 vcs4
crw-rw---- 1 root tty 7, 5 Aug 27 05:17 vcs5
crw-rw---- 1 root tty 7, 6 Aug 27 05:17 vcs6
crw-rw---- 1 root tty 7, 7 Aug 27 05:18 vcs7
crw-rw---- 1 root tty 7, 128 Aug 27 05:17 vcsa
crw-rw---- 1 root tty 7, 129 Aug 27 05:17 vcsa1
crw-rw---- 1 root tty 7, 130 Aug 27 05:17 vcsa2
crw-rw---- 1 root tty 7, 131 Aug 27 05:17 vcsa3
crw-rw---- 1 root tty 7, 132 Aug 27 05:17 vcsa4
crw-rw---- 1 root tty 7, 133 Aug 27 05:17 vcsa5
crw-rw---- 1 root tty 7, 134 Aug 27 05:17 vcsa6
crw-rw---- 1 root tty 7, 135 Aug 27 05:18 vcsa7
drwxr-xr-x 2 root root 60 Aug 27 05:17 vfio
crw------- 1 root root 10, 63 Aug 27 05:17 vga_arbiter
crw------- 1 root root 10, 137 Aug 27 05:17 vhci
crw------- 1 root root 10, 238 Aug 27 05:17 vhost-net
crw------- 1 root root 10, 241 Aug 27 05:17 vhost-vsock
crw-rw----+ 1 root video 81, 0 Aug 27 05:17 video0
crw-rw----+ 1 root video 81, 1 Aug 27 05:17 video1
crw------- 1 root root 10, 130 Aug 27 05:17 watchdog
crw------- 1 root root 249, 0 Aug 27 05:17 watchdog0
crw-rw-rw- 1 root root 1, 5 Aug 27 05:17 zero
As you can see there are a lot of devices, and some of those are pipes/other linux things. To get a list of BLOCK devices, we can either use the lsblk command or we can go into the /dev/block folder and type ls...
/dev/block$ ls -l
total 0
lrwxrwxrwx 1 root root 10 Aug 27 05:17 179:0 -> ../mmcblk0
lrwxrwxrwx 1 root root 12 Aug 27 05:17 179:1 -> ../mmcblk0p1
lrwxrwxrwx 1 root root 12 Aug 27 05:17 179:2 -> ../mmcblk0p2
lrwxrwxrwx 1 root root 6 Aug 27 05:17 8:0 -> ../sda
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:1 -> ../sda1
lrwxrwxrwx 1 root root 8 Aug 27 05:17 8:10 -> ../sda10
lrwxrwxrwx 1 root root 8 Aug 27 05:17 8:11 -> ../sda11
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:2 -> ../sda2
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:3 -> ../sda3
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:4 -> ../sda4
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:5 -> ../sda5
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:6 -> ../sda6
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:7 -> ../sda7
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:8 -> ../sda8
lrwxrwxrwx 1 root root 7 Aug 27 05:17 8:9 -> ../sda9
Here you can see my sdcard (mmcblk0) and my primary hard drive (sda). The number at the end represents the partition number. As you cans see, I have 11 partitions on my hard drive on my laptop and my sdcard has 2 partitions (in liunx the first of almost everything is 0 instead of 1).
Those ARE real partitions... but the storage isn't exactly like a hard disk drive. All of the information is saved on memory chips in the phone, whereas a hard disk drive (HDD) uses magnetic dust to signify bits (if more dust is on the top of the sector it's a 1, and if more dust is down it's a zero). Also, there are MANY more Android partitions than the partitions that you listed.... using the "cat" command you can print a text file to the screen in linux (including Android) and the /proc/ folder has a bunch of text files with information about your device. Typing the command "cat /proc/partitions" on my ZTE prints this out...
$ cat /proc/partitions
major minor #blocks name
253 0 196608 zram0
179 0 7634944 mmcblk0
179 1 8192 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 8192 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 90112 mmcblk0p11
179 12 49152 mmcblk0p12
179 13 49152 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 8192 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 540672 mmcblk0p28
179 29 2621440 mmcblk0p29
179 30 4030447 mmcblk0p30
179 64 4096 mmcblk0rpmb
179 128 31260672 mmcblk1
179 129 31256576 mmcblk1p1
254 0 4030431 dm-0
Each of those partitions stores different information in them. One is the cache partition, which is where all app data is stored. One is for the baseband (cellular radio chip), zram0 is RAM, system contains the Android system file (like c:\windows). Nowadays, there is an frp partition to lock the device if someone attempts to factory reset the device, the account information is still maintained (as the data and cache partitions are formatted but frp isn't, and therefore Android won't let you in unless you supply the username and password). The laf partition has to do with Fastboot (a PC command line program to change the partitions) and there are also vendor, firmware, carrier, and several others that I don't know the purpose of.
I hope this helped you and maybe some other people.
Greetings All,
I have a confusion about root usage with Magisk that maybe someone can help me with.
I would like to change some files on the /system directory in the Moto E6.
Using TWRP would make this change trivial.
Alas, there does not appear to be a functional TWRP available for this device.
So I am using the next best thing, Magisk rooted.
Booting up with the Magisk patched recovery, I can adb shell from a Linux terminal,
and execute 'su' for root privileges.
Attempting to remount /system rw results in '/system not in /proc/mounts' message (which is true).
If I attempt to mount /dev/block/by-name/system, I get a 'device or resource busy' message.
I CAN remount '/', and the /system directory can then be modified.
However, when the system is booted normally, those changes do not show in the 'normal' /system directory.
I suspect that Magisk is creating it's own /system directory for the recovery boot.
Is there any way to access/update the REAL /system image on this phone?
Thanx
Richard Rosa
Here is another mystery:
Boot with Magisk recovery.
adb shell
su
mount -o rw,remount /oem
cd oem
touch junk_file
ls -a
(file created is there)
(wait 10 seconds)
ls -a
(the file has disappeared).
Can someone enlighten me as to why?
Thanx.
Richard Rosa
It happens on my XT2005-5, as well.
Once the file is gone, I could not make any other file, either.
Right after mounting:
surfna:/ # ls -altr /oem
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 9 root root 4096 2021-01-27 16:16 .
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
Creating a file (TTT):
surfna:/ # touch /oem/TTT
surfna:/ # ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
-rw-r--r-- 1 root root 0 2021-05-30 03:58 TTT
drwxr-xr-x 9 root root 4096 2021-05-30 03:58 .
And it disappered:
surfna:/ # ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 03:58 .
I did touch and then chmod 700, without error.
But no TTT. The time stamp of oem stayed unchanged.
surfna:/ # touch /oem/TTT
surfna:/ # chmod 700 /oem/TTT
surfna:/ # ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 03:58 .
Same thing, but without delay. No effect.
surfna:/ # touch /oem/TTT; chmod 700 /oem/TTT
surfna:/ # ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 03:58 .
Trying to create more files ==> I/O error.
surfna:/ # touch /oem/TTT2
touch: '/oem/TTT2': I/O error
1|surfna:/ # touch /oem/123
touch: '/oem/123': I/O error
Repeating same thing. This time, time stamp of oem changed!
surfna:/ # touch /oem/TTT23
touch: '/oem/TTT23': I/O error
1|surfna:/ # touch /oem/TTT23
surfna:/ # touch /oem/T12
touch: '/oem/T12': I/O error
1|surfna:/ # touch /oem/TDD
touch: '/oem/TDD': I/O error
1|surfna:/ # ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 04:03 .
Using echo instead of touch to create a file.
Error for TDD, but no error for TTT, the original file, somehow.
But it doesn't show up is ls.
surfna:/ # echo 123 > /oem/TDD
/system/bin/sh: can't create /oem/TDD: I/O error
1|surfna:/ # echo 123 > /oem/TTT
surfna:/ # ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 04:03 .
But it shows up with full path.
surfna:/ # ls -altr /oem/TTT
-rwx------ 1 root root 4 2021-05-30 04:03 /oem/TTT
I rebooted (recoverly) and checked original mount parameters.
surfna:/ # mount |grep oem
/dev/block/dm-1 on /oem type ext4 (ro,context=ubject_remfs:s0,nosuid,nodev,relatime,block_validity,delalloc,barrier,user_xattr)
Remounting as "rw" doesn't change other parameters.
surfna:/ # mount -o rw,remount /oem
surfna:/ # mount |grep oem
/dev/block/dm-1 on /oem type ext4 (rw,context=ubject_remfs:s0,nosuid,nodev,relatime,block_validity,delalloc,barrier,user_xattr)
This time, the file didn't stay.
surfna:/ # touch /oem/TTT;chmod 700 /oem/TTT;ls -altr /oem/;mount |grep oem
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 04:40 .
/dev/block/dm-1 on /oem type ext4 (rw,context=ubject_remfs:s0,nosuid,nodev,relatime,block_validity,delalloc,barrier,user_xattr)
But it's there when I used full path, again.
surfna:/ # touch /oem/TTT;chmod 700 /oem/TTT;ls -altr /oem/TTT ;mount |grep oem
-rwx------ 1 root root 0 2021-05-30 04:41 /oem/TTT
Writing to the file did not change the time stamp of oem, but touching it changed.
surfna:/ # touch /oem; ls -altr /oem/
total 52
drwxr-xr-x 21 root root 4096 2009-01-01 01:00 ..
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 usc
-rw-r--r-- 1 root root 272 2021-01-27 16:15 oem.prop
drwxr-xr-x 3 root root 4096 2021-01-27 16:15 comcast
drwxr-xr-x 6 root root 4096 2021-01-27 16:16 app
drwxr-xr-x 7 root root 4096 2021-01-27 16:16 overlay
drwxr-xr-x 12 root root 4096 2021-01-27 16:16 priv-app
drwxr-xr-x 7 root root 4096 2021-01-27 16:17 etc
drwx------ 2 root root 16384 2021-01-27 16:17 lost+found
drwxr-xr-x 9 root root 4096 2021-05-30 04:53 .
It's a block device (rw) and special block.
It's small. Too small to contain all directories.
surfna:/ # ls -al /dev/block/dm-1
brw------- 1 root root 252, 1 1970-01-27 08:20 /dev/block/dm-1
surfna:/ # file /dev/block/dm-1
/dev/block/dm-1: block special
Recently I noticed that Windows 11 Arm64 version is possible to run on Z2 Force which has the same processor (Snapdragon 835) with my Z3 retcn version, so I feel very like to give it a try on my Z3. (Project Renegade)
Unfortunately I am stuck at the first step which is repartitioning the internal storage.
According to the guidelines, I will need to:
1. Repartition device;
2. Format new partitions;
3. Mount PE partition as /mnt;
4. (And other following steps);
The example given by the project's guidelines is OnePlus 6T 128GB, which apparently has its /userdata on /dev/block/sda, and its /dev/block/sda seems has only 17 partitions in place originally.
I see on my Z3 its /userdata is on /dev/block/sdb, which has already 21 partitions existing, and also it has so many disks existing as in below:
messi:/ # ls -l /dev/block/ | grep sd
brw------- 1 root root 8, 0 1970-01-01 00:17 sda
brw------- 1 root root 8, 1 1970-01-01 00:17 sda1
brw------- 1 root root 8, 2 1970-01-01 00:17 sda2
brw------- 1 root root 8, 16 2022-03-07 06:56 sdb
brw------- 1 root root 8, 17 1970-01-01 00:17 sdb1
brw------- 1 root root 8, 18 1970-01-01 00:17 sdb2
brw------- 1 root root 8, 19 2022-03-07 06:35 sdb3
brw------- 1 system system 8, 20 1970-01-01 00:17 sdb4
brw------- 1 root root 8, 21 1970-01-01 00:17 sdb5
brw------- 1 root root 8, 22 1970-01-01 00:17 sdb6
brw------- 1 root root 8, 23 1970-01-01 00:17 sdb7
brw------- 1 root root 8, 24 1970-01-01 00:17 sdb8
brw------- 1 root root 8, 25 1970-01-01 00:17 sdb9
brw------- 1 root root 8, 26 1970-01-01 00:17 sdb10
brw------- 1 root root 8, 27 1970-01-01 00:17 sdb11
brw------- 1 root root 8, 28 1970-01-01 00:17 sdb12
brw------- 1 root root 8, 29 1970-01-01 00:17 sdb13
brw------- 1 root root 8, 30 1970-01-01 00:17 sdb14
brw------- 1 root root 8, 31 1970-01-01 00:17 sdb15
brw------- 1 root root 259, 0 1970-01-01 00:17 sdb16
brw------- 1 root root 259, 1 1970-01-01 00:17 sdb17
brw------- 1 root root 259, 2 1970-01-01 00:17 sdb18
brw------- 1 root root 259, 3 1970-01-01 00:17 sdb19
brw------- 1 root root 259, 4 1970-01-01 00:17 sdb20
brw------- 1 root root 259, 5 2022-03-07 06:56 sdb21
brw------- 1 root root 8, 32 1970-01-01 00:17 sdc
brw------- 1 root root 8, 33 1970-01-01 00:17 sdc1
brw------- 1 root root 8, 48 1970-01-01 00:17 sdd
brw------- 1 root root 8, 49 1970-01-01 00:17 sdd1
brw------- 1 root root 8, 64 1970-01-01 00:17 sde
brw------- 1 root root 8, 65 1970-01-01 00:17 sde1
brw------- 1 root root 8, 66 1970-01-01 00:17 sde2
brw------- 1 root root 8, 67 1970-01-01 00:17 sde3
brw------- 1 root root 8, 68 1970-01-01 00:17 sde4
brw------- 1 root root 8, 69 1970-01-01 00:17 sde5
brw------- 1 root root 8, 70 1970-01-01 00:17 sde6
brw------- 1 root root 8, 71 1970-01-01 00:17 sde7
brw------- 1 root root 8, 72 1970-01-01 00:17 sde8
brw------- 1 root root 8, 73 1970-01-01 00:17 sde9
brw------- 1 root root 8, 74 1970-01-01 00:17 sde10
brw------- 1 root root 8, 75 1970-01-01 00:17 sde11
brw------- 1 root root 8, 76 1970-01-01 00:17 sde12
brw------- 1 root root 8, 77 1970-01-01 00:17 sde13
brw------- 1 root root 8, 78 1970-01-01 00:17 sde14
brw------- 1 root root 8, 79 1970-01-01 00:17 sde15
brw------- 1 root root 259, 6 1970-01-01 00:17 sde16
brw------- 1 root root 259, 7 1970-01-01 00:17 sde17
brw------- 1 root root 259, 8 1970-01-01 00:17 sde18
brw------- 1 root root 259, 9 1970-01-01 00:17 sde19
brw------- 1 root root 259, 10 1970-01-01 00:17 sde20
brw------- 1 root root 259, 11 1970-01-01 00:17 sde21
brw------- 1 root root 8, 80 1970-01-01 00:17 sdf
brw------- 1 root root 8, 81 1970-01-01 00:17 sdf1
brw------- 1 root root 8, 82 1970-01-01 00:17 sdf2
brw------- 1 root root 8, 83 1970-01-01 00:17 sdf3
brw------- 1 root root 8, 84 1970-01-01 00:17 sdf4
brw------- 1 root root 8, 85 1970-01-01 00:17 sdf5
brw------- 1 root root 8, 86 1970-01-01 00:17 sdf6
brw------- 1 root root 8, 87 1970-01-01 00:17 sdf7
brw------- 1 root root 8, 88 1970-01-01 00:17 sdf8
brw------- 1 root root 8, 89 1970-01-01 00:17 sdf9
brw------- 1 root root 8, 90 1970-01-01 00:17 sdf10
brw------- 1 root root 8, 91 1970-01-01 00:17 sdf11
brw------- 1 root root 8, 92 1970-01-01 00:17 sdf12
brw------- 1 root root 8, 93 1970-01-01 00:17 sdf13
brw------- 1 root root 8, 94 1970-01-01 00:17 sdf14
brw------- 1 root root 8, 95 1970-01-01 00:17 sdf15
brw------- 1 root root 259, 12 1970-01-01 00:17 sdf16
brw------- 1 root root 259, 13 1970-01-01 00:17 sdf17
brw------- 1 root root 259, 14 1970-01-01 00:17 sdf18
brw------- 1 root root 259, 15 1970-01-01 00:17 sdf19
brw------- 1 root root 259, 16 1970-01-01 00:17 sdf20
brw------- 1 root root 259, 17 1970-01-01 00:17 sdf21
The /userdata is on /dev/block/sdb which is like this (by parted):
messi:/ # parted /dev/block/sdb
GNU Parted 3.2
Using /dev/block/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: SAMSUNG KLUDG8V1EE-B0C1 (scsi)
Disk /dev/block/sdb: 116GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 131kB 139kB 8192B ssd
2 262kB 33.8MB 33.6MB ext4 persist
3 33.8MB 34.9MB 1049kB misc
4 34.9MB 35.4MB 524kB frp
5 35.4MB 35.9MB 524kB utags
6 35.9MB 36.4MB 524kB utagsBackup
7 36.4MB 36.6MB 131kB cid
8 36.6MB 37.1MB 524kB metadata
9 37.1MB 45.5MB 8389kB kpan
10 45.5MB 53.9MB 8389kB sp
11 53.9MB 70.6MB 16.8MB carrier
12 70.6MB 72.7MB 2097kB modemst1
13 72.7MB 74.8MB 2097kB modemst2
14 74.8MB 74.8MB 4096B fsc
15 75.0MB 75.0MB 4096B devinfo
16 75.1MB 83.5MB 8389kB logfs
17 83.5MB 83.5MB 16.4kB sec
18 83.6MB 83.9MB 262kB apdp
19 83.9MB 84.1MB 262kB msadp
20 84.1MB 84.2MB 4096B dpo
21 84.2MB 116GB 116GB ext4 userdata
The disk /dev/block/sdb1 has only 8192B and no partition created as shown below (Model: Unknown):
(parted) select /dev/block/sdb1
Using /dev/block/sdb1
(parted) print
Error: /dev/block/sdb1: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/block/sdb1: 8192B
Sector size (logical/physical): 4096B/4096B
Partition Table: unknown
Disk Flags:
However, the disk /dev/block/sdb2 has 1 partition (33.6MB) on it as shown below (Model: Unknown):
(parted) select /dev/block/sdb2
Using /dev/block/sdb2
(parted) print
Model: Unknown (unknown)
Disk /dev/block/sdb2: 33.6MB
Sector size (logical/physical): 4096B/4096B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 33.6MB 33.6MB ext4
What I wanted was:
rm 21
mkpart esp fat32 85MB(84.2MB) 500MB #415MB
mkpart pe fat32 500MB 3000MB #2500MB
mkpart win ntfs 3000MB 100GB #97GB
mkpart userdata ext4 100GB 116GB #16GB
The problem is after I removed partition 21 on /dev/block/sdb (115.9158GB) and created the esp partition without problem, then I needed to create the pe partition but I got an error as:
(parted) mkpart pe fat32 500MB 3000MB
Error: Too many primary partitions.
I understand the number of primary partitions can not exceed 21, but in this case how can I continue to create the partitions needed for the Windows 11?
I think I may need to shrink the size of /dev/block/sdb, keeping the /userdata partition still on this disk but taking size only 16GB and then utilize the free space to create a new disk /dev/block/sdg to hold esp, pe, win partitions but I don't know how to do it. The Z3 currently is not my daily use, so that I have no problem losing all data on it.
Could you please help and see how can I progress on this problem?
Grateful to your help!