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
Related
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?
hi, all!
Modify /init.rc configure file is my plan, in android(linux) box, /(rootfs) locate RAM.
So, modify ramdisk.img(initrd.img) is aim, However, I find any image file except recovery backup image:
[email protected]:/ # /system/xbin/busybox find / -name '*.img'
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/boot.img
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/recovery.img
/system/etc/firmware/modem.img
Did the partition that ramdisk.img save in not mount by kernel ?
My phone information:
all partition:
[email protected]:/ # ll /dev/block/
brw------- root root 254, 0 2012-11-30 22:08 dm-0
brw------- root root 7, 0 2012-11-30 22:07 loop0
brw------- root root 7, 1 2012-11-30 22:07 loop1
brw------- root root 7, 2 2012-11-30 22:07 loop2
brw------- root root 7, 3 2012-11-30 22:07 loop3
brw------- root root 7, 4 2012-11-30 22:07 loop4
brw------- root root 7, 5 2012-11-30 22:07 loop5
brw------- root root 7, 6 2012-11-30 22:07 loop6
brw------- root root 7, 7 2012-11-30 22:07 loop7
brw-rw---- root system 179, 0 2012-11-30 22:07 mmcblk0
brw------- root root 179, 32 2012-11-30 22:07 mmcblk0boot0
brw------- root root 179, 64 2012-11-30 22:07 mmcblk0boot1
brw------- root root 179, 1 2012-11-30 22:07 mmcblk0p1
brw------- root root 179, 2 2012-11-30 22:07 mmcblk0p2
brw------- root root 179, 3 2012-11-30 22:07 mmcblk0p3
brw------- root root 179, 4 2012-11-30 22:07 mmcblk0p4
brw------- root root 179, 5 2012-11-30 22:07 mmcblk0p5
brw------- root root 179, 6 2012-11-30 22:07 mmcblk0p6
brw------- root root 179, 96 2012-11-30 22:07 mmcblk1
brw------- root root 179, 97 2012-11-30 22:07 mmcblk1p1
drwxr-xr-x root root 2012-11-30 22:07 platform
drwxr-xr-x root root 2012-11-30 22:07 vold
mounted partition:
[email protected]:/ # mount|/system/xbin/busybox grep mmc
/[email protected] /system ext4 ro,noatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
had be linked partition:
[email protected]:/ # ll / |/system/xbin/busybox mmc
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 08:00 [email protected]_ro -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p5
[email protected]:/ # cat /proc/mtd
dev: size erasesize name
[email protected]:/ #
My phone do not use mtd ?
what other technology my phone used? and, what can I locate recovery and boot partition ?
Ramdisk is inside boot.img, you must use dsixda's kitchen to decompile it.
Sent from my PC36100 using xda app-developers app
Yes, the ramdisk is inside the boot.img. The recovery.img contains its own ramdisk. The partition is a basic format created just for android. The first 0x30ish bytes contain offsets and sizes for the kernel image, ramdisk, kernel command line, and stuff like that. And no, the ramdisk is not compiled; you do no decompile it. It is compressed. You can pull the ramdisk out of the partition and decompress it using standard commandline tools.
The structure of the PIT is defined below:-
Code:
Based on PIT GT-I9500_adonis_20130322.pit
Block Size = 0x200
Partition Name Image Name LEN LEN in BLK OS Partition Physical Partition
BOOTLOADER sboot.bin 0x(000F FC00) 0x(0000 07FE) 0x50 0x50
PIT adonis.pit 0x(0000 2000) 0x(0000 0010) 0x46 0x46
MD5HDR md5.img 0x(0010 0000) 0x(0000 0800) 0x47 0x47
BOTA0 - 0x(0040 0000) 0x(0000 2000) 0p1 0x01
BOTA1 - 0x(0040 0000) 0x(0000 2000) 0p2 0x02
EFS efs.img 0x(0140 0000) 0x(0000 A000) 0p3 0x03
m9kefs1 m9kefs1 0x(0040 0000) 0x(0000 2000) 0p4 0x04
m9kefs2 m9kefs2 0x(0040 0000) 0x(0000 2000) 0p5 0x05
m9kefs3 m9kefs3 0x(0040 0000) 0x(0000 2000) 0p6 0x06
CARRIER carrier.img 0x(0140 0000) 0x(0000 A000) 0p7 0x07
PARAM param.bin 0x(0080 0000) 0x(0000 4000) 0p8 0x08
BOOT boot.img 0x(0080 0000) 0x(0000 4000) 0p9 0x09
RECOVERY recovery.img 0x(0080 0000) 0x(0000 4000) 0p10 0x0A
OTA - 0x(0080 0000) 0x(0000 4000) 0p11 0x0B
CDMA-RADIO modem_cdma.bin 0x(0080 0000) 0x(0000 4000) 0p12 0x0C
RADIO modem.bin 0x(0580 0000) 0x(0002 C000) 0p13 0x0D
TOMBSTONES tombstones.img 0x(1000 0000) 0x(0008 0000) 0p14 0x0E
TDATA tdata.img 0x(0040 0000) 0x(0000 2000) 0p15 0x0F
HIDDEN hidden.img 0x(2300 0000) 0x(0011 8000) 0p16 0x10
PERSDATA persdata.img 0x(00C0 0000) 0x(0000 6000) 0p17 0x11
RESERVED2 - 0x(0040 0000) 0x(0000 2000) 0p18 0x12
CACHE cache.img 0x(8180 0000) 0x(0040 C000) 0p19 0x13
SYSTEM system.img 0x(ACC0 0000) 0x(0056 6000) 0p20 0x14
USERDATA userdata.img 0x(0000 0000) 0x(0000 0000) 0p21 0x15 (this is grown on the remaining flash space, depending on the model 16/32/64)
The offsets in the flash are as follows:-
Code:
Flash Reserved Area 0 (mmcblk0boot0 - hidden by kernel)
Partition Name Start Address
BL1 0x(0000 0000)
BL2 0x(0000 3C00)
BL3 0x(0000 7C00)
TZSW 0x(000D 8400)
DDI 0x(001F FC00)
Flash Reserved Area 1 (mmcblk0boot1 - hidden by kernel)
<empty>
Flash User Area (mmcblk0)
Partition Name Start Address Mount Point
GUID Header 0x(0000 0000 0000)
GPT Header 0x(0000 0000 0200)
PIT 0x(0000 0000 4400)
MD5HDR 0x(0000 0000 6400)
BOTA0 0x(0000 0040 0000)
BOTA1 0x(0000 0080 0000)
EFS 0x(0000 00C0 0000) /efs
m9kefs1 0x(0000 0200 0000)
m9kefs2 0x(0000 0240 0000)
m9kefs3 0x(0000 0280 0000)
CARRIER 0x(0000 02C0 0000)
PARAM 0x(0000 0400 0000) /param
BOOT 0x(0000 0480 0000) /boot
RECOVERY 0x(0000 0500 0000) /recovery
OTA 0x(0000 0580 0000)
CDMA-RADIO 0x(0000 0600 0000)
RADIO 0x(0000 0680 0000) /modem
TOMBSTONES 0x(0000 0C00 0000)
TDATA 0x(0000 1C00 0000)
HIDDEN 0x(0000 1C40 0000) /preload
PERSDATA 0x(0000 3F40 0000) /persdata/absolute
RESERVED2 0x(0000 4000 0000)
CACHE 0x(0000 4040 0000) /cache
SYSTEM 0x(0000 C1C0 0000) /system
USERDATA 0x(0001 6E80 0000) /data (this is grown on the remaining flash space, depending on the model 16/32/64)
wow full info is good
I believe this PIT is not from I9500, but from I9502.
PIT from I9500 should be different (at least without CDMA-RADIO partition)
I9505
Code:
aboot -> /dev/block/mmcblk0p6
apnhlos -> /dev/block/mmcblk0p1
backup -> /dev/block/mmcblk0p23
boot -> /dev/block/mmcblk0p20
cache -> /dev/block/mmcblk0p18
carrier -> /dev/block/mmcblk0p28
efs -> /dev/block/mmcblk0p10
fota -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p24
hidden -> /dev/block/mmcblk0p27
m9kefs1 -> /dev/block/mmcblk0p13
m9kefs2 -> /dev/block/mmcblk0p14
m9kefs3 -> /dev/block/mmcblk0p15
mdm -> /dev/block/mmcblk0p2
modemst1 -> /dev/block/mmcblk0p11
modemst2 -> /dev/block/mmcblk0p12
pad -> /dev/block/mmcblk0p9
param -> /dev/block/mmcblk0p19
persdata -> /dev/block/mmcblk0p26
persist -> /dev/block/mmcblk0p17
recovery -> /dev/block/mmcblk0p21
rpm -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p3
sbl2 -> /dev/block/mmcblk0p4
sbl3 -> /dev/block/mmcblk0p5
ssd -> /dev/block/mmcblk0p25
system -> /dev/block/mmcblk0p16
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p29
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p29
sorg said:
I believe this PIT is not from I9500, but from I9502.
PIT from I9500 should be different (at least without CDMA-RADIO partition)
Click to expand...
Click to collapse
You can believe what you want but do you really think I would post wrong info?
There are also other strange partitions like the Qualcomm MDM efs sh1ts. Seems them make some things common between models.
Odia said:
There are also other strange partitions like the Qualcomm MDM efs sh1ts.
Click to expand...
Click to collapse
i9502 uses Qualcomm modem for second CDMA SIM-card, so no wonder if there are partitions for Qualcomm MDM.
May be I9500 uses the same PIT as I9502, or may be somehow you've got wrong PIT.
At least I9505 uses different PIT according to your post.
Hi, Odia. Thank you for info.
What do you think - what CDMA partition is doing in this PIT for 9500? Maybe they made the identical partition table for all models 9XXX and it's just emty here? At least it's not mounted. Because no one model except for I9502 has second CDMA module. 9500 - no LTE, GT-I9505 with LTE and a Korean variant with LTE (SVH-E300S).
Ivan_Belarus said:
Hi, Odia. Thank you for info.
What do you think - what CDMA partition is doing in this PIT for 9500? Maybe they made the identical partition table for all models 9XXX and it's just emty here? At least it's not mounted. Because no one model except for I9502 has second CDMA module. 9500 - no LTE, GT-I9505 with LTE and a Korean variant with LTE (SVH-E300S).
Click to expand...
Click to collapse
Sorry for the late reply, I did not notice your post.
I am really not sure what Samsung think here, since the I9502 PIT has an extra 2 partitions for the second radio and it's EFS, when I get some free time, I will post full details on the i9502, i9505 and i9508.
Odia said:
Sorry for the late reply, I did not notice your post.
I am really not sure what Samsung think here, since the I9502 PIT has an extra 2 partitions for the second radio and it's EFS, when I get some free time, I will post full details on the i9502, i9505 and i9508.
Click to expand...
Click to collapse
Thank you for reply. Look forward for that. Look at my info for a while. From my I9500. Pay attention on # of blocks.
Code:
lrwxrwxrwx root root 2013-05-02 13:07 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-05-02 13:07 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-05-02 13:07 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-05-02 13:07 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-05-02 13:07 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-05-02 13:07 CDMA -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-05-02 13:07 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-05-02 13:07 HIDDEN -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-05-02 13:07 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-05-02 13:07 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-05-02 13:07 PERSDATA -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-05-02 13:07 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-05-02 13:07 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-05-02 13:07 RESERVED2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-05-02 13:07 SYSTEM -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-05-02 13:07 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-05-02 13:07 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-05-02 13:07 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-05-02 13:07 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-05-02 13:07 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-05-02 13:07 m9kefs3 -> /dev/block/mmcblk0p6
And
Code:
major minor #blocks name
253 0 409600 zram0
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 8192 mmcblk0p9
259 2 8192 mmcblk0p10
259 3 8192 mmcblk0p11
259 4 8192 mmcblk0p12
259 5 90112 mmcblk0p13
259 6 262144 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 573440 mmcblk0p16
259 9 12288 mmcblk0p17
259 10 4096 mmcblk0p18
259 11 2121728 mmcblk0p19
259 12 2830336 mmcblk0p20
259 13 9379840 mmcblk0p21
Ivan_Belarus said:
Look at my info for a while. From my I9500. Pay attention on # of blocks.
Click to expand...
Click to collapse
Not sure what you mean by this, the info matches what I wrote in the OP.
Odia said:
Not sure what you mean by this, the info matches what I wrote in the OP.
Click to expand...
Click to collapse
Maybe I'm wrong, but if you take boot.img 0p9
In OP: 0x200 x 0x4000 = 800 000 in HEX, Size comes to: 8 388 608 bytes in DEC. It's ok.
In my post: #blocks = 8192 = 0x2000.
As you write block size is 0x200 = 512 in DEC. So, my size = 512 x 8192 = 4 194 304 bytes. Why?
It would be equal with block size 0x400.
Ivan_Belarus said:
Maybe I'm wrong, but if you take boot.img 0p9
In OP: 0x200 x 0x4000 = 800 000 in HEX, Size comes to: 8 388 608 bytes in DEC. It's ok.
In my post: #blocks = 8192 = 0x2000.
As you write block size is 0x200 = 512 in DEC. So, my size = 512 x 8192 = 4 194 304 bytes. Why?
It would be equal with block size 0x400.
Click to expand...
Click to collapse
Thats because physical to virtual mapping, my OP is physical from FlashIC and how the bootloader see's it, you should not mix the two or you will have strange results
Odia said:
Thats because physical to virtual mapping, my OP is physical from FlashIC and how the bootloader see's it, you should not mix the two or you will have strange results
Click to expand...
Click to collapse
Of course I used the OP data. Now everything is clear for me. Thanks. P.S. Would you attach your PIT(9500) file, please.
Odia said:
The structure of the PIT is defined below:-
Dear Odia. Is it possible to attach a valid pit file in this post? I have a S4 i9500 that has a soft brick. I can access it from ODIN and ADB, but I cant mount anything there.
The phone stucks on logo and I think the partition are corrupted, because this problems happen after I'm trying to unmount the internal sdcard (a message appeared for me, when I'm trying to change the vold.fstab files). During process of unmount, the phone froze and I restarted it. After this, the phone doesn pass of the Samsung logo and goes to recovery mode, with a various messages about impossible to mount the directories.
Because of this, I think the only way is to flash a new pit to rebuild the partition. Is this correct?
I really appreciate your help, if possible!
Tks a lot!!!
Click to expand...
Click to collapse
rgbarros said:
Odia said:
The structure of the PIT is defined below:-
Dear Odia. Is it possible to attach a valid pit file in this post? I have a S4 i9500 that has a soft brick. I can access it from ODIN and ADB, but I cant mount anything there.
The phone stucks on logo and I think the partition are corrupted, because this problems happen after I'm trying to unmount the internal sdcard (a message appeared for me, when I'm trying to change the vold.fstab files). During process of unmount, the phone froze and I restarted it. After this, the phone doesn pass of the Samsung logo and goes to recovery mode, with a various messages about impossible to mount the directories.
Because of this, I think the only way is to flash a new pit to rebuild the partition. Is this correct?
I really appreciate your help, if possible!
Tks a lot!!!
Click to expand...
Click to collapse
Odia, just informing you that I solved the problem. I used a adonis.pit and put the phone alive!!! Tks a lot!!!
Click to expand...
Click to collapse
Odia said:
The offsets in the flash are as follows:-
Click to expand...
Click to collapse
How did you go about reading and generating this? (The hidden-by-kernel mmcblk0boot0 / 1.)
@Odia: now with new firmware MGG (brand vodafone Italy, only for I9505) is impossibile to go back to a previous firmware from this new one, i think sammy update bootloader. I found this your useful thread here
[Util] Sboot Checker, is possible in your opinion to do something similar for this new situation on I9505? Must first extract old bootloader from pit file right?
Sorry if i go little OT here, if you want to write me in pm.
Thanks, regards
I'm trying to extract pit from my S4,
but I can't be sure about command.
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
is that correct? my S4 is 32GB.
Sent from my SHV-E300S using Tapatalk
Please check i9500
Can someone please check this I think my partitions are not right this is on 4.3, I cannot adb push to system anymore
[email protected]:/ $ su
[email protected]:/ # ls -l /dev/block
brw------- root root 7, 0 2013-11-28 07:58 loop0
brw------- root root 7, 1 2013-11-28 07:58 loop1
brw------- root root 7, 2 2013-11-28 07:58 loop2
brw------- root root 7, 3 2013-11-28 07:58 loop3
brw------- root root 7, 4 2013-11-28 07:58 loop4
brw------- root root 7, 5 2013-11-28 07:58 loop5
brw------- root root 7, 6 2013-11-28 07:58 loop6
brw------- root root 7, 7 2013-11-28 07:58 loop7
brw------- root root 179, 0 2013-11-28 07:58 mmcblk0
brw------- root root 179, 1 2013-11-28 07:58 mmcblk0p1
brw------- root root 259, 2 2013-11-28 07:58 mmcblk0p10
brw------- root root 259, 3 2013-11-28 07:58 mmcblk0p11
brw------- root root 259, 4 2013-11-28 07:58 mmcblk0p12
brw-rw---- system radio 259, 5 2013-11-28 07:58 mmcblk0p13
brw------- root root 259, 6 2013-11-28 07:58 mmcblk0p14
brw------- root root 259, 7 2013-11-28 07:58 mmcblk0p15
brw------- root root 259, 8 2013-11-28 07:58 mmcblk0p16
brw------- root root 259, 9 2013-11-28 07:58 mmcblk0p17
brw------- root root 259, 10 2013-11-28 07:58 mmcblk0p18
brw------- root root 259, 11 2013-11-28 07:58 mmcblk0p19
brw------- root root 179, 2 2013-11-28 07:58 mmcblk0p2
brw------- root root 259, 12 2013-11-28 07:58 mmcblk0p20
brw------- root root 259, 13 2013-11-28 07:58 mmcblk0p21
brw-rw---- system system 179, 3 2013-11-28 07:58 mmcblk0p3
brw------- root root 179, 4 2013-11-28 07:58 mmcblk0p4
brw------- root root 179, 5 2013-11-28 07:58 mmcblk0p5
brw------- root root 179, 6 2013-11-28 07:58 mmcblk0p6
brw------- root root 179, 7 2013-11-28 07:58 mmcblk0p7
brw-rw---- system system 259, 0 2013-11-28 08:01 mmcblk0p8
brw------- root root 259, 1 2013-11-28 07:58 mmcblk0p9
brw------- root root 179, 8 2013-11-28 07:58 mmcblk1
brw------- root root 179, 9 2013-11-28 07:58 mmcblk1p1
lrwxrwxrwx root root 2013-11-28 07:58 param -> /dev/block/mmcblk0p8
drwxr-xr-x root root 2013-11-28 07:58 platform
brw------- root root 1, 0 2013-11-28 07:58 ram0
brw------- root root 1, 1 2013-11-28 07:58 ram1
brw------- root root 1, 10 2013-11-28 07:58 ram10
brw------- root root 1, 11 2013-11-28 07:58 ram11
brw------- root root 1, 12 2013-11-28 07:58 ram12
brw------- root root 1, 13 2013-11-28 07:58 ram13
brw------- root root 1, 14 2013-11-28 07:58 ram14
brw------- root root 1, 15 2013-11-28 07:58 ram15
brw------- root root 1, 16 2013-11-28 07:58 ram16
brw------- root root 1, 17 2013-11-28 07:58 ram17
brw------- root root 1, 18 2013-11-28 07:58 ram18
brw------- root root 1, 19 2013-11-28 07:58 ram19
brw------- root root 1, 2 2013-11-28 07:58 ram2
brw------- root root 1, 20 2013-11-28 07:58 ram20
brw------- root root 1, 21 2013-11-28 07:58 ram21
brw------- root root 1, 22 2013-11-28 07:58 ram22
brw------- root root 1, 23 2013-11-28 07:58 ram23
brw------- root root 1, 24 2013-11-28 07:58 ram24
brw------- root root 1, 25 2013-11-28 07:58 ram25
brw------- root root 1, 26 2013-11-28 07:58 ram26
brw------- root root 1, 27 2013-11-28 07:58 ram27
brw------- root root 1, 28 2013-11-28 07:58 ram28
brw------- root root 1, 29 2013-11-28 07:58 ram29
brw------- root root 1, 3 2013-11-28 07:58 ram3
brw------- root root 1, 30 2013-11-28 07:58 ram30
brw------- root root 1, 31 2013-11-28 07:58 ram31
brw------- root root 1, 32 2013-11-28 07:58 ram32
brw------- root root 1, 33 2013-11-28 07:58 ram33
brw------- root root 1, 34 2013-11-28 07:58 ram34
brw------- root root 1, 35 2013-11-28 07:58 ram35
brw------- root root 1, 36 2013-11-28 07:58 ram36
brw------- root root 1, 37 2013-11-28 07:58 ram37
brw------- root root 1, 38 2013-11-28 07:58 ram38
brw------- root root 1, 39 2013-11-28 07:58 ram39
brw------- root root 1, 4 2013-11-28 07:58 ram4
brw------- root root 1, 40 2013-11-28 07:58 ram40
brw------- root root 1, 41 2013-11-28 07:58 ram41
brw------- root root 1, 42 2013-11-28 07:58 ram42
brw------- root root 1, 43 2013-11-28 07:58 ram43
brw------- root root 1, 44 2013-11-28 07:58 ram44
brw------- root root 1, 45 2013-11-28 07:58 ram45
brw------- root root 1, 46 2013-11-28 07:58 ram46
brw------- root root 1, 47 2013-11-28 07:58 ram47
brw------- root root 1, 48 2013-11-28 07:58 ram48
brw------- root root 1, 49 2013-11-28 07:58 ram49
brw------- root root 1, 5 2013-11-28 07:58 ram5
brw------- root root 1, 50 2013-11-28 07:58 ram50
brw------- root root 1, 51 2013-11-28 07:58 ram51
brw------- root root 1, 52 2013-11-28 07:58 ram52
brw------- root root 1, 53 2013-11-28 07:58 ram53
brw------- root root 1, 54 2013-11-28 07:58 ram54
brw------- root root 1, 55 2013-11-28 07:58 ram55
brw------- root root 1, 56 2013-11-28 07:58 ram56
brw------- root root 1, 57 2013-11-28 07:58 ram57
brw------- root root 1, 58 2013-11-28 07:58 ram58
brw------- root root 1, 59 2013-11-28 07:58 ram59
brw------- root root 1, 6 2013-11-28 07:58 ram6
brw------- root root 1, 7 2013-11-28 07:58 ram7
brw------- root root 1, 8 2013-11-28 07:58 ram8
brw------- root root 1, 9 2013-11-28 07:58 ram9
drwx------ root root 2013-11-28 07:58 vold
brw------- root root 253, 0 2013-11-28 07:58 zram0
[email protected]:/ #
First how to find location of boot image in device? I want to take current boot image. Do modifications and later flash that boot image back to device.
I have searched correct block device and did some image files with dd command but they were not boot images. I tried with several tools.
Here is some listing from the phone with adb shell commands.
Code:
[email protected]:/proc # cat partitions
major minor #blocks name
179 0 30512256 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 665600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 1572864 mmcblk0p7
179 8 28077696 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
Code:
[email protected]:/ # ls -l /emm*
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p7
[email protected]:/ #
Code:
[email protected]:/dev/block # ls -al
brw------- root root 7, 0 2014-03-12 12:54 loop0
brw------- root root 7, 1 2014-03-12 12:54 loop1
brw------- root root 7, 2 2014-03-12 12:54 loop2
brw------- root root 7, 3 2014-03-12 12:54 loop3
brw------- root root 7, 4 2014-03-12 12:54 loop4
brw------- root root 7, 5 2014-03-12 12:54 loop5
brw------- root root 7, 6 2014-03-12 12:54 loop6
brw------- root root 7, 7 2014-03-12 12:54 loop7
brw-rw---- root system 179, 0 2014-03-12 12:54 mmcblk0
brw------- root root 179, 32 2014-03-12 12:54 mmcblk0boot0
brw------- root root 179, 64 2014-03-12 12:54 mmcblk0boot1
brw------- root root 179, 1 2014-03-12 12:54 mmcblk0p1
brw-r----- root system 179, 2 2014-03-12 12:54 mmcblk0p2
brw------- root root 179, 3 2014-03-12 12:54 mmcblk0p3
brw------- root root 179, 4 2014-03-12 12:54 mmcblk0p4
brw------- root root 179, 5 2014-03-12 12:54 mmcblk0p5
brw------- root root 179, 6 2014-03-12 12:54 mmcblk0p6
brw------- root root 179, 7 2014-03-12 12:54 mmcblk0p7
brw------- root root 179, 8 2014-03-12 12:54 mmcblk0p8
drwxr-xr-x root root 2014-03-12 12:54 platform
[email protected]:/dev/block #
/dev/block/mmcblk0boot0 looked promising but I made image of it by by command dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot.img
But the image was not boot image.
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /storage/sdcard0 vfat rw,dirsync,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ #
I can make full image by dding /dev/block/mmcblk0 but it would be better to get the parts separately.
Is there easy way to find where the boot image is located?
I checked block device sizes
/dev/block/mmcblk0p8 is the internal flash area for user, about 28G. Boot image boot loader etc must be in mmcblk0p1 - mmcblk0p7
Size of the block devices
Code:
/dev/block/mmcblk0 31244550144
/dev/block/mmcblk0boot0 2097152
/dev/block/mmcblk0boot1 2097152
/dev/block/mmcblk0p1 1024
/dev/block/mmcblk0p2 10485760
/dev/block/mmcblk0p3 10485760
/dev/block/mmcblk0p4 6291456
/dev/block/mmcblk0p5 681574400
/dev/block/mmcblk0p6 132120576
/dev/block/mmcblk0p7 1610612736
/dev/block/mmcblk0p8 28751560704
/dev/block/mmcblk1 8178892800
I got these with script
Code:
#!/system/bin/sh
command="/sdcard/busybox blockdev --getsize64"
for f in /dev/block/mm*
do
result=`$command $f`
result="$f \t $result"
echo $result
done
Via Terminal Emulator:
"su
cat /proc/partitions"
When again other command: dd if=/dev/block/(boot_partition_which_showed under /proc/partitions) of=/sdcard/boot.img
Root your device and try MtkDroidTools.
Use MTK SP_Flash_tool to flash image back.
In proc partitions there were two boot related devices listed
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
I made images from both of those but there was nothing inside the images which looked like boot image.
I found that there is /dev/bootimage
Code:
[email protected]:/ # ls -l /dev/boo*
crw-r----- root system 234, 10 2013-01-01 06:30 bootimg
I made image from that. The image is 4.3G. Very large. Anyway I found bootimage inside that. Then I made another smaller one with
Code:
# dd if=/dev/bootimg of=/sdcard/testboot.img count=12000
I can unpack that image in linux with tool unpack-MT65xx.pl. I tried to repack the exact same files without modifying. But repacking the image with repack-MT65.pl generates file which is different.
cnexpat said:
Is there easy way to find where the boot image is located?
Click to expand...
Click to collapse
Looking for same
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!