Related
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
Ok i played a little with GAB's SU760 and one way to root v29C ICS is this
Download Root_with_Restore_by_Bin4ry_v10.7z
execute runme.bat from Root_with_Restore_by_Bin4ry_v10.7z
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.09.2012) v10 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
It will show some info etc and ask you to restore go ahead and restore..
after that your SU760 won't be ROOTED BUT run the script again and now choose option 1
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.09.2012) v10 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Wait for it to reboot and after that you have ROOT access. :good:
You will lose Google Playstore.
Download it and install it (first remove the old one from /system/app dont forget the odex file).
Some more info from Gabs SU760 V29C
Code:
[email protected]:/ # ls -l /dev/block
brw------- root root 254, 0 2012-09-25 22:43 dm-0
brw------- root root 7, 0 2012-09-25 22:43 loop0
brw------- root root 7, 1 2012-09-25 22:43 loop1
brw------- root root 7, 2 2012-09-25 22:43 loop2
brw------- root root 7, 3 2012-09-25 22:43 loop3
brw------- root root 7, 4 2012-09-25 22:43 loop4
brw------- root root 7, 5 2012-09-25 22:43 loop5
brw------- root root 7, 6 2012-09-25 22:43 loop6
brw------- root root 7, 7 2012-09-25 22:43 loop7
brwxrwx--- root lg_fota 179, 0 2012-09-25 22:43 mmcblk0
brw------- root root 179, 25 2012-09-25 22:43 mmcblk0boot0
brw------- root root 179, 50 2012-09-25 22:43 mmcblk0boot1
brw------- root root 179, 1 2012-09-25 22:43 mmcblk0p1
brw------- root root 179, 10 2012-09-25 22:43 mmcblk0p10
brw------- root root 179, 11 2012-09-25 22:43 mmcblk0p11
brw------- root root 179, 12 2012-09-25 22:43 mmcblk0p12
brw------- root root 179, 13 2012-09-25 22:43 mmcblk0p13
brw-rw---- system media_rw 179, 14 2012-09-25 22:43 mmcblk0p14
brw------- root root 179, 15 2012-09-25 22:43 mmcblk0p15
brw------- root root 179, 16 2012-09-25 22:43 mmcblk0p16
brw------- root root 179, 17 2012-09-25 22:43 mmcblk0p17
brw-rw---- system media_rw 179, 2 2012-09-25 22:43 mmcblk0p2
brw-rw---- system media_rw 179, 3 2012-09-25 22:43 mmcblk0p3
brw------- root root 179, 4 2012-09-25 22:43 mmcblk0p4
brw------- root root 179, 5 2012-09-25 22:43 mmcblk0p5
brw------- root root 179, 6 2012-09-25 22:43 mmcblk0p6
brw------- root root 179, 7 2012-09-25 22:43 mmcblk0p7
brw------- root root 179, 8 2012-09-25 22:43 mmcblk0p8
brw------- root root 179, 9 2012-09-25 22:43 mmcblk0p9
brw------- root root 179, 75 2012-09-25 22:43 mmcblk1
brw------- root root 179, 76 2012-09-25 22:43 mmcblk1p1
drwxr-xr-x root root 2012-09-25 22:43 platform
brw------- root root 1, 0 2012-09-25 22:43 ram0
brw------- root root 1, 1 2012-09-25 22:43 ram1
brw------- root root 1, 10 2012-09-25 22:43 ram10
brw------- root root 1, 11 2012-09-25 22:43 ram11
brw------- root root 1, 12 2012-09-25 22:43 ram12
brw------- root root 1, 13 2012-09-25 22:43 ram13
brw------- root root 1, 14 2012-09-25 22:43 ram14
brw------- root root 1, 15 2012-09-25 22:43 ram15
brw------- root root 1, 2 2012-09-25 22:43 ram2
brw------- root root 1, 3 2012-09-25 22:43 ram3
brw------- root root 1, 4 2012-09-25 22:43 ram4
brw------- root root 1, 5 2012-09-25 22:43 ram5
brw------- root root 1, 6 2012-09-25 22:43 ram6
brw------- root root 1, 7 2012-09-25 22:43 ram7
brw------- root root 1, 8 2012-09-25 22:43 ram8
brw------- root root 1, 9 2012-09-25 22:43 ram9
drwxr-xr-x root root 2012-09-25 22:43 vold
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 205.00M 48.00K 204.95M 4096
/mnt/asec 205.00M 0.00K 205.00M 4096
/mnt/obb 205.00M 0.00K 205.00M 4096
/mnt/extasec 205.00M 0.00K 205.00M 4096
/mnt/extobb 205.00M 0.00K 205.00M 4096
/system 688.98M 654.49M 34.48M 4096
/data 1.97G 163.95M 1.81G 4096
/cache 123.98M 16.07M 107.92M 4096
/dvp 1.96M 1.02M 962.00K 1024
/log 9.68M 1.18M 8.50M 1024
/data/ve 9.67M 4.02M 5.65M 4096
/mnt/sdcard 11.81G 3.88M 11.80G 32768
/mnt/secure/asec 11.81G 3.88M 11.80G 32768
/mnt/sdcard/_ExternalSD 1.84G 273.53M 1.57G 32768
/mnt/extsecure/extasec 1.84G 273.53M 1.57G 32768
/mnt/asec/jackpal.androidterm-1 2.04M 368.00K 1.68M 8192
Special Thanx to Bin4ry for his script.
Good job maybe now we can port?
Sent from my LG-P925 using xda app-developers app
Porting questions in ICS Thread..
Lets keep this thread clean for SU760 users.
Sent from my P920 using xda-developers app
I did that a week ago but i dont know how can i can i put cmw...
Sent from my LG-SU760 using xda premium
CWM is not available for SU760 ICS ROMS for now.
Hope CWM will be available soon.
worked fine su760 29d. thank you!! u r legend
Nice to hear it works in V29D too.
Send from my Xperia Neo V using xda-developers app.
hey xbsall, can this work with the port, also for the 1st run, do we go all the way till the script says root, or do we close the script after the phone restores??
whats the name of google play in the system/app folder?
i dont know how i can open the folder cuz i dont have a file manager and cant use google play to download anyone
i ve tried with root explorer to delete apk files from the system/app folder but it tells me failed delete..
phonesky.apk and phonesky.odex
got root access from ported rom using this method
What's the secret? Yesterday I managed to root the ported v30b, but now I get loads of Access Denied on script, ends ok but I have no root and I lost play store
vitorcruzbr said:
What's the secret? Yesterday I managed to root the ported v30b, but now I get loads of Access Denied on script, ends ok but I have no root and I lost play store
Click to expand...
Click to collapse
After rooting you need to update the superuser app and download latest binaries.
Sent from my phone.
Only su binary is missing, cant update it. But I have access to system folder - only read though
i make root(thanks to xbsall) and i find SuperSU 0.96 but i can't find where i can tap to update binary...maybe don't need.
i check on google play(v. 3.9.16) and it's ok.
I went to play store after root and installed superuser then switched and uninstalled supersu and throught super user you can update binary
Sent from my LG-SU760 using xda app-developers app
play store was uninstalled after I rooted ICS how do I install it back?
sketch2k278 said:
play store was uninstalled after I rooted ICS how do I install it back?
Click to expand...
Click to collapse
Place it in system/app
defcomg said:
Place it in system/app
Click to expand...
Click to collapse
ok thanks for this but how to install it if there's no file explorer type app installed?
First of all if there is any way for those like me with less than perfect eyesight and experienced with the structure of these most complicated I've seen to date, I would like to respectively ask that the captchas be reduced in difficulty.
My issue is that I seem to have hit an impasse in that I can't post a question here to a How-to guide published for non-experts unless I am an expert, qualified by posting 10 helpful comments in an area I am just beginning to learn. If I think back to other operating systems I have learned over the years other than Linux, there were sometime years that passed before I felt qualified to help someone with understanding the OS.
So I am in a catch 22.
All I want to do is make a backup with a possibility of restore of my full OS on a Blu Studio 5.5s that I have factory reset for just that purpose, to have a customized OS that I could restore. It would also be nice to be able to learn how to someone share this image online, assuming that others can use it where none are available otherwise, but that is my second objective and not the first.
Now understanding my first objective is just a backup and restore capability and also understanding that the two bootloader recovery packagers out now don't (yet?) support my phone, I at last found this article and was excited that it would accomplish what I needed. I went through the hoops of days of research, getting hardcodes out of Windows device manger, altering Google driver INF files with dummied up hardware codes with a new device, overriding windows and getting the drivers installed and to work, installing the 64 bit version of SDK, and careful with the 32bit Java, relocating, renaming the SDK, modified the PATH to find my variables, installing Cgwin64, researching and comparing old package to new info and testing it all to see that it worked.
So in short, I am stuck in the middle of this how-to guide with my phone stripped to the bone for a backup but I can't ask a question here until after I have learned the answer to the question I am asking.
THE QUESTION:
reference: http://forum.xda-developers.com/showthread.php?t=1818321
My phone directory structure is not documented online and does not match the examples in the backup guide, plus it appears I may also have some permission restrictions? How do I continue? Thanks
My results thus far:
===================NOTE: PHONE IS BLU STUDIO 5.5S================
[email protected] /blustudio
$ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
0 B 0:00:00 [ 0 B/s] [<=>
===================
[email protected] ~
$ adb forward tcp:5555 tcp:5555
[email protected] ~
$ adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ /system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if =/dev/block/mmcblk0
555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0 <
dd: can't open '/dev/block/mmcblk0': Permission denied
1|[email protected]:/ $ ls -lR /dev/block
============================
ls -lR /dev/block
/dev/block:
brw------- root root 7, 0 2014-06-27 21:34 loop0
brw------- root root 7, 1 2014-06-27 21:34 loop1
brw------- root root 7, 2 2014-06-27 21:34 loop2
brw------- root root 7, 3 2014-06-27 21:34 loop3
brw------- root root 7, 4 2014-06-27 21:34 loop4
brw------- root root 7, 5 2014-06-27 21:34 loop5
brw------- root root 7, 6 2014-06-27 21:34 loop6
brw------- root root 7, 7 2014-06-27 21:34 loop7
brw-rw---- root system 179, 0 2014-06-27 21:34 mmcblk0
brw-rw---- root system 179, 32 2014-06-27 21:34 mmcblk0boot0
brw------- root root 179, 64 2014-06-27 21:34 mmcblk0boot1
brw------- root root 179, 1 2014-06-27 21:34 mmcblk0p1
brw------- root root 179, 2 2014-06-27 21:34 mmcblk0p2
brw------- root root 179, 3 2014-06-27 21:34 mmcblk0p3
brw------- root root 179, 4 2014-06-27 21:34 mmcblk0p4
brw------- root root 179, 5 2014-06-27 21:34 mmcblk0p5
brw------- root root 179, 6 2014-06-27 21:34 mmcblk0p6
brw------- root root 179, 7 2014-06-27 21:34 mmcblk0p7
drwxr-xr-x root root 2014-06-27 21:34 platform
drwxr-xr-x root root 2014-06-27 21:34 vold
brw------- root root 253, 0 2014-06-27 21:34 zram0
/dev/block/platform:
drwxr-xr-x root root 2014-06-27 21:34 mtk-msdc.0
/dev/block/platform/mtk-msdc.0:
drwxr-xr-x root root 2014-06-27 21:34 by-num
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0 -> /dev/block/mmc blk0
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0boot0 -> /dev/bloc k/mmcblk0boot0
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0boot1 -> /dev/bloc k/mmcblk0boot1
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p1 -> /dev/block/m mcblk0p1
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p2 -> /dev/block/m mcblk0p2
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p3 -> /dev/block/m mcblk0p3
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p4 -> /dev/block/m mcblk0p4
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p5 -> /dev/block/m mcblk0p5
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p6 -> /dev/block/m mcblk0p6
lrwxrwxrwx root root 2014-06-27 21:34 mmcblk0p7 -> /dev/block/m mcblk0p7
/dev/block/platform/mtk-msdc.0/by-num:
lrwxrwxrwx root root 2014-06-27 21:34 p1 -> /dev/block/mmcblk0p 1
lrwxrwxrwx root root 2014-06-27 21:34 p2 -> /dev/block/mmcblk0p 2
lrwxrwxrwx root root 2014-06-27 21:34 p3 -> /dev/block/mmcblk0p 3
lrwxrwxrwx root root 2014-06-27 21:34 p4 -> /dev/block/mmcblk0p 4
lrwxrwxrwx root root 2014-06-27 21:34 p5 -> /dev/block/mmcblk0p 5
lrwxrwxrwx root root 2014-06-27 21:34 p6 -> /dev/block/mmcblk0p 6
lrwxrwxrwx root root 2014-06-27 21:34 p7 -> /dev/block/mmcblk0p 7
/dev/block/vold:
brw-rw---- root root 179, 0 2014-06-27 21:34 179:0
brw-rw---- root root 179, 1 2014-06-27 21:34 179:1
brw-rw---- root root 179, 2 2014-06-27 21:34 179:2
brw-rw---- root root 179, 3 2014-06-27 21:34 179:3
brw-rw---- root root 179, 4 2014-06-27 21:34 179:4
brw-rw---- root root 179, 5 2014-06-27 21:34 179:5
brw-rw---- root root 179, 6 2014-06-27 21:34 179:6
brw-rw---- root root 179, 7 2014-06-27 21:34 179:7
[email protected]:/ $
Thanks in advance for any advise.
The device is OnePlus 8 Pro, it is completely functional, booted for root ADB from LineageOS Recovery via fastboot -s XXXXXXXX boot lineage-recovery.img.
Bash:
$ adb --version
Android Debug Bridge version 1.0.41
Version 31.0.2-7242960
Installed as /opt/android-sdk/platform-tools/adb
Click to expand...
Click to collapse
Trying to follow some 4-6 years old online guides & QnAs (mostly written by Irfan Latif) on how to backup stock ROM & partitions using adb pull or adb exec-out.
All of these materials always reference an mmcblk0 partition. But in my case it is missing.
What I have instead are these:
Bash:
$ adb -s XXXXXXXX shell 'ls -al /dev/block' | grep -e '^[^d]'
total 0
lrwxrwxrwx 1 root root 37 1970-04-15 15:06 bootdevice -> /dev/block/platform/soc/XXXXXXX.ufshc
brw------- 1 root root 7, 0 1970-04-15 15:06 loop0
brw------- 1 root root 7, 8 1970-04-15 15:06 loop1
brw------- 1 root root 7, 80 1970-04-15 15:06 loop10
brw------- 1 root root 7, 88 1970-04-15 15:06 loop11
brw------- 1 root root 7, 96 1970-04-15 15:06 loop12
brw------- 1 root root 7, 104 1970-04-15 15:06 loop13
brw------- 1 root root 7, 112 1970-04-15 15:06 loop14
brw------- 1 root root 7, 120 1970-04-15 15:06 loop15
brw------- 1 root root 7, 16 1970-04-15 15:06 loop2
brw------- 1 root root 7, 24 1970-04-15 15:06 loop3
brw------- 1 root root 7, 32 1970-04-15 15:06 loop4
brw------- 1 root root 7, 40 1970-04-15 15:06 loop5
brw------- 1 root root 7, 48 1970-04-15 15:06 loop6
brw------- 1 root root 7, 56 1970-04-15 15:06 loop7
brw------- 1 root root 7, 64 1970-04-15 15:06 loop8
brw------- 1 root root 7, 72 1970-04-15 15:06 loop9
brw------- 1 root root 1, 0 1970-04-15 15:06 ram0
brw------- 1 root root 1, 1 1970-04-15 15:06 ram1
brw------- 1 root root 1, 10 1970-04-15 15:06 ram10
brw------- 1 root root 1, 11 1970-04-15 15:06 ram11
brw------- 1 root root 1, 12 1970-04-15 15:06 ram12
brw------- 1 root root 1, 13 1970-04-15 15:06 ram13
brw------- 1 root root 1, 14 1970-04-15 15:06 ram14
brw------- 1 root root 1, 15 1970-04-15 15:06 ram15
brw------- 1 root root 1, 2 1970-04-15 15:06 ram2
brw------- 1 root root 1, 3 1970-04-15 15:06 ram3
brw------- 1 root root 1, 4 1970-04-15 15:06 ram4
brw------- 1 root root 1, 5 1970-04-15 15:06 ram5
brw------- 1 root root 1, 6 1970-04-15 15:06 ram6
brw------- 1 root root 1, 7 1970-04-15 15:06 ram7
brw------- 1 root root 1, 8 1970-04-15 15:06 ram8
brw------- 1 root root 1, 9 1970-04-15 15:06 ram9
brw------- 1 root root 8, 0 1970-04-15 15:06 sda
brw------- 1 root root 8, 1 1970-04-15 15:06 sda1
brw------- 1 root root 8, 10 1970-04-15 15:06 sda10
brw------- 1 root root 8, 11 1970-04-15 15:06 sda11
brw------- 1 root root 8, 12 1970-04-15 15:06 sda12
brw------- 1 root root 8, 13 1970-04-15 15:06 sda13
brw------- 1 root root 8, 14 1970-04-15 15:06 sda14
brw------- 1 root root 8, 15 1970-04-15 15:06 sda15
brw------- 1 root root 259, 0 1970-04-15 15:06 sda16
brw------- 1 root root 259, 1 1970-04-15 15:06 sda17
brw------- 1 root root 259, 2 1970-04-15 15:06 sda18
brw------- 1 root root 259, 3 1970-04-15 15:06 sda19
brw------- 1 root root 8, 2 1970-04-15 15:06 sda2
brw------- 1 root root 259, 4 1970-04-15 15:06 sda20
brw------- 1 root root 259, 5 1970-04-15 15:06 sda21
brw------- 1 root root 259, 6 1970-04-15 15:06 sda22
brw------- 1 root root 259, 7 1970-04-15 15:06 sda23
brw------- 1 root root 8, 3 1970-04-15 15:09 sda3
brw------- 1 root root 8, 4 1970-04-15 15:06 sda4
brw------- 1 root root 8, 5 1970-04-15 15:06 sda5
brw------- 1 root root 8, 6 1970-04-15 15:06 sda6
brw------- 1 root root 8, 7 1970-04-15 15:06 sda7
brw------- 1 root root 8, 8 1970-04-15 15:06 sda8
brw------- 1 root root 8, 9 1970-04-15 15:06 sda9
brw------- 1 root root 8, 16 1970-04-15 15:06 sdb
brw------- 1 root root 8, 17 1970-04-15 15:06 sdb1
brw------- 1 root root 8, 18 1970-04-15 15:06 sdb2
brw------- 1 root root 8, 32 1970-04-15 15:06 sdc
brw------- 1 root root 8, 33 1970-04-15 15:06 sdc1
brw------- 1 root root 8, 34 1970-04-15 15:06 sdc2
brw------- 1 root root 8, 48 1970-04-15 15:06 sdd
brw------- 1 root root 8, 49 1970-04-15 15:06 sdd1
brw------- 1 root root 8, 50 1970-04-15 15:06 sdd2
brw------- 1 root root 8, 51 1970-04-15 15:06 sdd3
brw------- 1 root root 8, 52 1970-04-15 15:06 sdd4
brw------- 1 root root 8, 64 1970-04-15 15:06 sde
brw------- 1 root root 8, 65 1970-04-15 15:06 sde1
brw------- 1 root root 8, 74 1970-04-15 15:06 sde10
brw------- 1 root root 8, 75 1970-04-15 15:06 sde11
brw------- 1 root root 8, 76 1970-04-15 15:06 sde12
brw------- 1 root root 8, 77 1970-04-15 15:06 sde13
brw------- 1 root root 8, 78 1970-04-15 15:06 sde14
brw------- 1 root root 8, 79 1970-04-15 15:06 sde15
brw------- 1 root root 259, 8 1970-04-15 15:06 sde16
brw------- 1 root root 259, 9 1970-04-15 15:06 sde17
brw------- 1 root root 259, 10 1970-04-15 15:06 sde18
brw------- 1 root root 259, 11 1970-04-15 15:06 sde19
brw------- 1 root root 8, 66 1970-04-15 15:06 sde2
brw------- 1 root root 259, 12 1970-04-15 15:06 sde20
brw------- 1 root root 259, 13 1970-04-15 15:06 sde21
brw------- 1 root root 259, 14 1970-04-15 15:06 sde22
brw------- 1 root root 259, 15 1970-04-15 15:06 sde23
brw------- 1 root root 259, 16 1970-04-15 15:06 sde24
brw------- 1 root root 259, 17 1970-04-15 15:06 sde25
brw------- 1 root root 259, 18 1970-04-15 15:06 sde26
brw------- 1 root root 259, 19 1970-04-15 15:06 sde27
brw------- 1 root root 259, 20 1970-04-15 15:06 sde28
brw------- 1 root root 259, 21 1970-04-15 15:06 sde29
brw------- 1 root root 8, 67 1970-04-15 15:06 sde3
brw------- 1 root root 259, 22 1970-04-15 15:06 sde30
brw------- 1 root root 259, 23 1970-04-15 15:06 sde31
brw------- 1 root root 259, 24 1970-04-15 15:06 sde32
brw------- 1 root root 259, 25 1970-04-15 15:06 sde33
brw------- 1 root root 259, 26 1970-04-15 15:06 sde34
brw------- 1 root root 259, 27 1970-04-15 15:06 sde35
brw------- 1 root root 259, 28 1970-04-15 15:06 sde36
brw------- 1 root root 259, 29 1970-04-15 15:06 sde37
brw------- 1 root root 259, 30 1970-04-15 15:06 sde38
brw------- 1 root root 259, 31 1970-04-15 15:06 sde39
brw------- 1 root root 8, 68 1970-04-15 15:06 sde4
brw------- 1 root root 259, 32 1970-04-15 15:06 sde40
brw------- 1 root root 259, 33 1970-04-15 15:06 sde41
brw------- 1 root root 259, 34 1970-04-15 15:06 sde42
brw------- 1 root root 259, 35 1970-04-15 15:06 sde43
brw------- 1 root root 259, 36 1970-04-15 15:06 sde44
brw------- 1 root root 259, 37 1970-04-15 15:06 sde45
brw------- 1 root root 259, 38 1970-04-15 15:06 sde46
brw------- 1 root root 259, 39 1970-04-15 15:06 sde47
brw------- 1 root root 259, 40 1970-04-15 15:06 sde48
brw------- 1 root root 259, 41 1970-04-15 15:06 sde49
brw------- 1 root root 8, 69 1970-04-15 15:06 sde5
brw------- 1 root root 259, 42 1970-04-15 15:06 sde50
brw------- 1 root root 259, 43 1970-04-15 15:06 sde51
brw------- 1 root root 259, 44 1970-04-15 15:06 sde52
brw------- 1 root root 259, 45 1970-04-15 15:06 sde53
brw------- 1 root root 259, 46 1970-04-15 15:06 sde54
brw------- 1 root root 259, 47 1970-04-15 15:06 sde55
brw------- 1 root root 259, 48 1970-04-15 15:06 sde56
brw------- 1 root root 259, 49 1970-04-15 15:06 sde57
brw------- 1 root root 259, 50 1970-04-15 15:06 sde58
brw------- 1 root root 259, 51 1970-04-15 15:06 sde59
brw------- 1 root root 8, 70 1970-04-15 15:06 sde6
brw------- 1 root root 259, 52 1970-04-15 15:06 sde60
brw------- 1 root root 259, 53 1970-04-15 15:06 sde61
brw------- 1 root root 259, 54 1970-04-15 15:06 sde62
brw------- 1 root root 259, 55 1970-04-15 15:06 sde63
brw------- 1 root root 259, 56 1970-04-15 15:06 sde64
brw------- 1 root root 259, 57 1970-04-15 15:06 sde65
brw------- 1 root root 259, 58 1970-04-15 15:06 sde66
brw------- 1 root root 259, 59 1970-04-15 15:06 sde67
brw------- 1 root root 259, 60 1970-04-15 15:06 sde68
brw------- 1 root root 259, 61 1970-04-15 15:06 sde69
brw------- 1 root root 8, 71 1970-04-15 15:06 sde7
brw------- 1 root root 259, 62 1970-04-15 15:06 sde70
brw------- 1 root root 259, 63 1970-04-15 15:06 sde71
brw------- 1 root root 259, 64 1970-04-15 15:06 sde72
brw------- 1 root root 259, 65 1970-04-15 15:06 sde73
brw------- 1 root root 259, 66 1970-04-15 15:06 sde74
brw------- 1 root root 259, 67 1970-04-15 15:06 sde75
brw------- 1 root root 259, 68 1970-04-15 15:06 sde76
brw------- 1 root root 8, 72 1970-04-15 15:06 sde8
brw------- 1 root root 8, 73 1970-04-15 15:06 sde9
brw------- 1 root root 8, 80 1970-04-15 15:06 sdf
brw------- 1 root root 8, 81 1970-04-15 15:06 sdf1
brw------- 1 root root 8, 82 1970-04-15 15:06 sdf2
brw------- 1 root root 8, 83 1970-04-15 15:06 sdf3
brw------- 1 root root 8, 84 1970-04-15 15:06 sdf4
brw------- 1 root root 8, 85 1970-04-15 15:06 sdf5
brw------- 1 root root 8, 86 1970-04-15 15:06 sdf6
brw------- 1 root root 8, 87 1970-04-15 15:06 sdf7
brw------- 1 root root 8, 88 1970-04-15 15:06 sdf8
brw------- 1 root root 8, 89 1970-04-15 15:06 sdf9
brw------- 1 root root 254, 0 1970-04-15 15:06 zram0
Which one of those is the new mmcblk0? Which one should I pull to have a full backup of my device stock firmware as an .img file?
mmcblk0 is the internal NAND which contains the n partitions ( mmcblk0p1 ... mmcblk0pn ). Whereas mmcblk1 is the external SD-card.
Try this to backup NAND
Code:
adb exec-out "cat /dev/block/mmcblk0 | gzip" > C:\emmc_copy.zip
Take note that this operation can take very long ( a few hours ).
jwoegerbauer said:
mmcblk0 is the internal NAND which contains the n partitions ( mmcblk0p1 ... mmcblk0pn ). Whereas mmcblk1 is the external SD-card.
Try this to backup NAND
Code:
adb exec-out "cat /dev/block/mmcblk0 | gzip" > C:\emmc_copy.zip
Take note that this operation can take very long ( a few hours ).
Click to expand...
Click to collapse
The problem is that there is no mmcblk0 nor mmcblk1 on my device. Or maybe they were made invisible or somehow unlisted for ls.
Bash:
$ adb -s XXXXXXXX shell 'ls -shlap /dev/block'
total 0
0 drwxr-xr-x 5 root root 3.1K 1970-04-15 15:06 ./
0 drwxr-xr-x 11 root root 5.9K 1970-04-15 15:06 ../
0 lrwxrwxrwx 1 root root 37 1970-04-15 15:06 bootdevice -> /dev/block/platform/soc/1d84000.ufshc
0 drwxr-xr-x 2 root root 2.4K 1970-04-15 15:06 by-name/
0 brw------- 1 root root 7, 0 1970-04-15 15:06 loop0
0 brw------- 1 root root 7, 8 1970-04-15 15:06 loop1
0 brw------- 1 root root 7, 80 1970-04-15 15:06 loop10
0 brw------- 1 root root 7, 88 1970-04-15 15:06 loop11
0 brw------- 1 root root 7, 96 1970-04-15 15:06 loop12
0 brw------- 1 root root 7, 104 1970-04-15 15:06 loop13
0 brw------- 1 root root 7, 112 1970-04-15 15:06 loop14
0 brw------- 1 root root 7, 120 1970-04-15 15:06 loop15
0 brw------- 1 root root 7, 16 1970-04-15 15:06 loop2
0 brw------- 1 root root 7, 24 1970-04-15 15:06 loop3
0 brw------- 1 root root 7, 32 1970-04-15 15:06 loop4
0 brw------- 1 root root 7, 40 1970-04-15 15:06 loop5
0 brw------- 1 root root 7, 48 1970-04-15 15:06 loop6
0 brw------- 1 root root 7, 56 1970-04-15 15:06 loop7
0 brw------- 1 root root 7, 64 1970-04-15 15:06 loop8
0 brw------- 1 root root 7, 72 1970-04-15 15:06 loop9
0 drwxr-xr-x 3 root root 60 1970-04-15 15:06 platform/
0 brw------- 1 root root 1, 0 1970-04-15 15:06 ram0
0 brw------- 1 root root 1, 1 1970-04-15 15:06 ram1
0 brw------- 1 root root 1, 10 1970-04-15 15:06 ram10
0 brw------- 1 root root 1, 11 1970-04-15 15:06 ram11
0 brw------- 1 root root 1, 12 1970-04-15 15:06 ram12
0 brw------- 1 root root 1, 13 1970-04-15 15:06 ram13
0 brw------- 1 root root 1, 14 1970-04-15 15:06 ram14
0 brw------- 1 root root 1, 15 1970-04-15 15:06 ram15
0 brw------- 1 root root 1, 2 1970-04-15 15:06 ram2
0 brw------- 1 root root 1, 3 1970-04-15 15:06 ram3
0 brw------- 1 root root 1, 4 1970-04-15 15:06 ram4
0 brw------- 1 root root 1, 5 1970-04-15 15:06 ram5
0 brw------- 1 root root 1, 6 1970-04-15 15:06 ram6
0 brw------- 1 root root 1, 7 1970-04-15 15:06 ram7
0 brw------- 1 root root 1, 8 1970-04-15 15:06 ram8
0 brw------- 1 root root 1, 9 1970-04-15 15:06 ram9
0 brw------- 1 root root 8, 0 1970-04-15 15:06 sda
0 brw------- 1 root root 8, 1 1970-04-15 15:06 sda1
0 brw------- 1 root root 8, 10 1970-04-15 15:06 sda10
0 brw------- 1 root root 8, 11 1970-04-15 15:06 sda11
0 brw------- 1 root root 8, 12 1970-04-15 15:06 sda12
0 brw------- 1 root root 8, 13 1970-04-15 15:06 sda13
0 brw------- 1 root root 8, 14 1970-04-15 15:06 sda14
0 brw------- 1 root root 8, 15 1970-04-15 15:06 sda15
0 brw------- 1 root root 259, 0 1970-04-15 15:06 sda16
0 brw------- 1 root root 259, 1 1970-04-15 15:06 sda17
0 brw------- 1 root root 259, 2 1970-04-15 15:06 sda18
0 brw------- 1 root root 259, 3 1970-04-15 15:06 sda19
0 brw------- 1 root root 8, 2 1970-04-15 15:06 sda2
0 brw------- 1 root root 259, 4 1970-04-15 15:06 sda20
0 brw------- 1 root root 259, 5 1970-04-15 15:06 sda21
0 brw------- 1 root root 259, 6 1970-04-15 15:06 sda22
0 brw------- 1 root root 259, 7 1970-04-15 15:06 sda23
0 brw------- 1 root root 8, 3 1970-04-15 15:09 sda3
0 brw------- 1 root root 8, 4 1970-04-15 15:06 sda4
0 brw------- 1 root root 8, 5 1970-04-15 15:06 sda5
0 brw------- 1 root root 8, 6 1970-04-15 15:06 sda6
0 brw------- 1 root root 8, 7 1970-04-15 15:06 sda7
0 brw------- 1 root root 8, 8 1970-04-15 15:06 sda8
0 brw------- 1 root root 8, 9 1970-04-15 15:06 sda9
0 brw------- 1 root root 8, 16 1970-04-15 15:06 sdb
0 brw------- 1 root root 8, 17 1970-04-15 15:06 sdb1
0 brw------- 1 root root 8, 18 1970-04-15 15:06 sdb2
0 brw------- 1 root root 8, 32 1970-04-15 15:06 sdc
0 brw------- 1 root root 8, 33 1970-04-15 15:06 sdc1
0 brw------- 1 root root 8, 34 1970-04-15 15:06 sdc2
0 brw------- 1 root root 8, 48 1970-04-15 15:06 sdd
0 brw------- 1 root root 8, 49 1970-04-15 15:06 sdd1
0 brw------- 1 root root 8, 50 1970-04-15 15:06 sdd2
0 brw------- 1 root root 8, 51 1970-04-15 15:06 sdd3
0 brw------- 1 root root 8, 52 1970-04-15 15:06 sdd4
0 brw------- 1 root root 8, 64 1970-04-15 15:06 sde
0 brw------- 1 root root 8, 65 1970-04-15 15:06 sde1
0 brw------- 1 root root 8, 74 1970-04-15 15:06 sde10
0 brw------- 1 root root 8, 75 1970-04-15 15:06 sde11
0 brw------- 1 root root 8, 76 1970-04-15 15:06 sde12
0 brw------- 1 root root 8, 77 1970-04-15 15:06 sde13
0 brw------- 1 root root 8, 78 1970-04-15 15:06 sde14
0 brw------- 1 root root 8, 79 1970-04-15 15:06 sde15
0 brw------- 1 root root 259, 8 1970-04-15 15:06 sde16
0 brw------- 1 root root 259, 9 1970-04-15 15:06 sde17
0 brw------- 1 root root 259, 10 1970-04-15 15:06 sde18
0 brw------- 1 root root 259, 11 1970-04-15 15:06 sde19
0 brw------- 1 root root 8, 66 1970-04-15 15:06 sde2
0 brw------- 1 root root 259, 12 1970-04-15 15:06 sde20
0 brw------- 1 root root 259, 13 1970-04-15 15:06 sde21
0 brw------- 1 root root 259, 14 1970-04-15 15:06 sde22
0 brw------- 1 root root 259, 15 1970-04-15 15:06 sde23
0 brw------- 1 root root 259, 16 1970-04-15 15:06 sde24
0 brw------- 1 root root 259, 17 1970-04-15 15:06 sde25
0 brw------- 1 root root 259, 18 1970-04-15 15:06 sde26
0 brw------- 1 root root 259, 19 1970-04-15 15:06 sde27
0 brw------- 1 root root 259, 20 1970-04-15 15:06 sde28
0 brw------- 1 root root 259, 21 1970-04-15 15:06 sde29
0 brw------- 1 root root 8, 67 1970-04-15 15:06 sde3
0 brw------- 1 root root 259, 22 1970-04-15 15:06 sde30
0 brw------- 1 root root 259, 23 1970-04-15 15:06 sde31
0 brw------- 1 root root 259, 24 1970-04-15 15:06 sde32
0 brw------- 1 root root 259, 25 1970-04-15 15:06 sde33
0 brw------- 1 root root 259, 26 1970-04-15 15:06 sde34
0 brw------- 1 root root 259, 27 1970-04-15 15:06 sde35
0 brw------- 1 root root 259, 28 1970-04-15 15:06 sde36
0 brw------- 1 root root 259, 29 1970-04-15 15:06 sde37
0 brw------- 1 root root 259, 30 1970-04-15 15:06 sde38
0 brw------- 1 root root 259, 31 1970-04-15 15:06 sde39
0 brw------- 1 root root 8, 68 1970-04-15 15:06 sde4
0 brw------- 1 root root 259, 32 1970-04-15 15:06 sde40
0 brw------- 1 root root 259, 33 1970-04-15 15:06 sde41
0 brw------- 1 root root 259, 34 1970-04-15 15:06 sde42
0 brw------- 1 root root 259, 35 1970-04-15 15:06 sde43
0 brw------- 1 root root 259, 36 1970-04-15 15:06 sde44
0 brw------- 1 root root 259, 37 1970-04-15 15:06 sde45
0 brw------- 1 root root 259, 38 1970-04-15 15:06 sde46
0 brw------- 1 root root 259, 39 1970-04-15 15:06 sde47
0 brw------- 1 root root 259, 40 1970-04-15 15:06 sde48
0 brw------- 1 root root 259, 41 1970-04-15 15:06 sde49
0 brw------- 1 root root 8, 69 1970-04-15 15:06 sde5
0 brw------- 1 root root 259, 42 1970-04-15 15:06 sde50
0 brw------- 1 root root 259, 43 1970-04-15 15:06 sde51
0 brw------- 1 root root 259, 44 1970-04-15 15:06 sde52
0 brw------- 1 root root 259, 45 1970-04-15 15:06 sde53
0 brw------- 1 root root 259, 46 1970-04-15 15:06 sde54
0 brw------- 1 root root 259, 47 1970-04-15 15:06 sde55
0 brw------- 1 root root 259, 48 1970-04-15 15:06 sde56
0 brw------- 1 root root 259, 49 1970-04-15 15:06 sde57
0 brw------- 1 root root 259, 50 1970-04-15 15:06 sde58
0 brw------- 1 root root 259, 51 1970-04-15 15:06 sde59
0 brw------- 1 root root 8, 70 1970-04-15 15:06 sde6
0 brw------- 1 root root 259, 52 1970-04-15 15:06 sde60
0 brw------- 1 root root 259, 53 1970-04-15 15:06 sde61
0 brw------- 1 root root 259, 54 1970-04-15 15:06 sde62
0 brw------- 1 root root 259, 55 1970-04-15 15:06 sde63
0 brw------- 1 root root 259, 56 1970-04-15 15:06 sde64
0 brw------- 1 root root 259, 57 1970-04-15 15:06 sde65
0 brw------- 1 root root 259, 58 1970-04-15 15:06 sde66
0 brw------- 1 root root 259, 59 1970-04-15 15:06 sde67
0 brw------- 1 root root 259, 60 1970-04-15 15:06 sde68
0 brw------- 1 root root 259, 61 1970-04-15 15:06 sde69
0 brw------- 1 root root 8, 71 1970-04-15 15:06 sde7
0 brw------- 1 root root 259, 62 1970-04-15 15:06 sde70
0 brw------- 1 root root 259, 63 1970-04-15 15:06 sde71
0 brw------- 1 root root 259, 64 1970-04-15 15:06 sde72
0 brw------- 1 root root 259, 65 1970-04-15 15:06 sde73
0 brw------- 1 root root 259, 66 1970-04-15 15:06 sde74
0 brw------- 1 root root 259, 67 1970-04-15 15:06 sde75
0 brw------- 1 root root 259, 68 1970-04-15 15:06 sde76
0 brw------- 1 root root 8, 72 1970-04-15 15:06 sde8
0 brw------- 1 root root 8, 73 1970-04-15 15:06 sde9
0 brw------- 1 root root 8, 80 1970-04-15 15:06 sdf
0 brw------- 1 root root 8, 81 1970-04-15 15:06 sdf1
0 brw------- 1 root root 8, 82 1970-04-15 15:06 sdf2
0 brw------- 1 root root 8, 83 1970-04-15 15:06 sdf3
0 brw------- 1 root root 8, 84 1970-04-15 15:06 sdf4
0 brw------- 1 root root 8, 85 1970-04-15 15:06 sdf5
0 brw------- 1 root root 8, 86 1970-04-15 15:06 sdf6
0 brw------- 1 root root 8, 87 1970-04-15 15:06 sdf7
0 brw------- 1 root root 8, 88 1970-04-15 15:06 sdf8
0 brw------- 1 root root 8, 89 1970-04-15 15:06 sdf9
0 drwxr-xr-x 2 root root 40 1970-04-15 15:06 volmgr/
0 brw------- 1 root root 254, 0 1970-04-15 15:06 zram0
The command below produces an empty 71 byte archive.
Bash:
$ adb -s XXXXXXXX exec-out 'cat /dev/block/mmcblk0 | gzip' > backup/partitions/mmcblk0.tar.gz
$ ls -shlap backup/partitions/mmcblk0.tar.gz
4.0K -rw-rw-r-- 1 tanhok tanhok 71 Aug 5 18:26 backup/partitions/mmcblk0.tar.gz
Look inside here:
How To Gather Information About Partition Layouts
Ameer Dawood edited this page on 2 Jun 2013 · 7 revisions Note: I have obtained the below information with great effort and difficul...
shincdevnote.blogspot.com
jwoegerbauer said:
Look inside here:
How To Gather Information About Partition Layouts
Ameer Dawood edited this page on 2 Jun 2013 · 7 revisions Note: I have obtained the below information with great effort and difficul...
shincdevnote.blogspot.com
Click to expand...
Click to collapse
Bash:
$ adb -s XXXXXXXX shell '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 8192 sdb
8 17 5120 sdb1
8 18 128 sdb2
8 0 247013376 sda
8 1 8 sda1
8 2 32768 sda2
8 3 1024 sda3
8 4 512 sda4
8 5 512 sda5
8 6 1024 sda6
8 7 10240 sda7
8 8 10240 sda8
8 9 307200 sda9
8 10 262144 sda10
8 11 512 sda11
8 12 307200 sda12
8 13 307200 sda13
8 14 14680064 sda14
8 15 102400 sda15
259 0 102400 sda16
259 1 64 sda17
259 2 64 sda18
259 3 16384 sda19
259 4 131072 sda20
259 5 131072 sda21
259 6 131072 sda22
259 7 230478156 sda23
8 32 8192 sdc
8 33 5120 sdc1
8 34 128 sdc2
8 48 131072 sdd
8 49 104 sdd1
8 50 128 sdd2
8 51 2048 sdd3
8 52 1024 sdd4
8 64 2621440 sde
8 65 512 sde1
8 66 4096 sde2
8 67 8192 sde3
8 68 524288 sde4
8 69 1024 sde5
8 70 4096 sde6
8 71 32768 sde7
8 72 8192 sde8
8 73 65536 sde9
8 74 512 sde10
8 75 98304 sde11
8 76 512 sde12
8 77 512 sde13
8 78 128 sde14
8 79 80 sde15
259 8 64 sde16
259 9 24576 sde17
259 10 2048 sde18
259 11 32 sde19
259 12 32 sde20
259 13 32768 sde21
259 14 128 sde22
259 15 2048 sde23
259 16 16384 sde24
259 17 512 sde25
259 18 4096 sde26
259 19 8192 sde27
259 20 524288 sde28
259 21 1024 sde29
259 22 4096 sde30
259 23 32768 sde31
259 24 8192 sde32
259 25 65536 sde33
259 26 512 sde34
259 27 98304 sde35
259 28 512 sde36
259 29 512 sde37
259 30 128 sde38
259 31 80 sde39
259 32 64 sde40
259 33 24576 sde41
259 34 2048 sde42
259 35 32 sde43
259 36 32 sde44
259 37 32768 sde45
259 38 128 sde46
259 39 2048 sde47
259 40 16384 sde48
259 41 4 sde49
259 42 1024 sde50
259 43 256 sde51
259 44 256 sde52
259 45 32768 sde53
259 46 4 sde54
259 47 4 sde55
259 48 8192 sde56
259 49 65536 sde57
259 50 128 sde58
259 51 512 sde59
259 52 28 sde60
259 53 128 sde61
259 54 4096 sde62
259 55 2048 sde63
259 56 65536 sde64
259 57 32768 sde65
259 58 307200 sde66
259 59 16192 sde67
259 60 16192 sde68
259 61 16192 sde69
259 62 16192 sde70
259 63 16192 sde71
259 64 8096 sde72
259 65 16192 sde73
259 66 16192 sde74
259 67 16192 sde75
259 68 128 sde76
8 80 131072 sdf
8 81 104 sdf1
8 82 2048 sdf2
8 83 2048 sdf3
8 84 2048 sdf4
8 85 128 sdf5
8 86 2048 sdf6
8 87 2048 sdf7
8 88 2048 sdf8
8 89 4 sdf9
OMG. It depends on what partition layout Android OS is based on.
It's on you to find that out.
jwoegerbauer said:
OMG. It depends on what partition layout Android OS is based on.
It's on you to find that out.
Click to expand...
Click to collapse
Where can I find which ones even exist to compare my situation against?
Code:
adb shell "[ -e '/proc/mtd' ] && echo 'is MTD layout'"
adb shell "[ -e '/proc/emmc' ] && echo 'is EMMC layout'"
adb shell "[ -e '/proc/dumchar_info' ] && echo 'is MTK layout'"
jwoegerbauer said:
Code:
adb shell "[ -e '/proc/mtd' ] && echo 'is MTD layout'"
adb shell "[ -e '/proc/emmc' ] && echo 'is EMMC layout'"
adb shell "[ -e '/proc/dumchar_info' ] && echo 'is MTK layout'"
Click to expand...
Click to collapse
None of the above.
Really weird. No more clues by me. Sorry.
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!