Database Info

Android (Samsung) partitions list

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

[Kernel] Siyah_I9305 Discussion..

As per some comments by G.K i thought it was going to be ported by now but things change , not sure whats
Happening ill leave it open incase we have some news regarding it.

btemtd said:
I spoke to Gohkan regarding porting his kernel to I9305 he said the only reason -not likely- is because he tried this before without owning the device and it was quite hard as he could not test it, especially when bugs arise it got quite frustrating for him. But he was more then happy to give a helping hand to any dev that would like to port his kernel. I guess the best way also is if there is a bug the Dev that ported the Kernel will need to Liase with Gohkan instead of all the users flooding him with bug reports. He mentioned Devs from US variant ported his kernel no problem. So if any of our devs would like to help, Let me know and I can speak to him or just message him and say "you are a dev and want to port his kernel where do we start". I am willing to help with what ever is needed, just let me know
I mean Perseus is 1 AWESOME kernel if you ask me , only thing is there is no interface to tweak it like Siyah's Stweaks. I was told he is working on something tho. Anyways Its always good to have a variety to choose from
Click to expand...
Click to collapse
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],

Just checked out liquid smooth for nexus. Looks amazing. Cant wait!!!
Sent from my GT-I9305 using xda premium

The first version is allways difficult!
Congratulations to all equipo.(GT I9305 LTE SiyahKernel)

has one been made?

Amplified said:
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],
Click to expand...
Click to collapse
I have Emailed You and I have also PM'd you, I have not received any reply. So evryone Its still in the air at the moment Its up for grabs who ever wants to start, If I knew what to do I would of started already. I myself need some guidance especially with kernels..

I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.

gokhanmoral said:
I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.
Click to expand...
Click to collapse
It would be great to have another choice of kernel

This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6

btemtd said:
This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
Click to expand...
Click to collapse
I also need the partition sizes.
so please post "df" and "mount" outputs from adb shell.
it seems that the layout is different but if the formats are the sizes are similar I can get dual boot feature work as well.
and also please post "ls -l /dev/input /dev/block" output

Ok I will get it done now, If somebody is quicker feel free to post for Gohkan

I hope this is right

btemtd said:
I hope I did it right for you Gokz please confirm
Click to expand...
Click to collapse
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.

gokhanmoral said:
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.
Click to expand...
Click to collapse
Bro Not a problem at all.. Do not rush, and thank you so much. I am here if you need anything

if it helps i have dumped a text version of the shell outputs:
Code:
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/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p13 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p11 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.suffick.node-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.uberdroidstudio.ubermusic-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:17 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
df
Filesystem Size Used Free Blksize
/dev 896M 84K 896M 4096
/mnt/asec 896M 0K 896M 4096
/mnt/obb 896M 0K 896M 4096
/efs 19M 4M 15M 4096
/cache 1007M 17M 990M 4096
/system 1G 1001M 510M 4096
/data 11G 6G 4G 4096
/firmware 199M 45M 154M 4096
/tombstones 251M 18M 233M 4096
/storage/sdcard0 10G 6G 4G 4096
/mnt/asec/com.suffick.node-1 2M 256K 1M 4096
/mnt/asec/com.uberdroidstudio.ubermusic-1 3M 1M 1M 4096
/storage/extSdCard 29G 28G 1G 32768
ls -l /dev/input /dev/block
crw-rw---- root input 13, 64 2012-10-18 11:10 event0
crw-rw---- root input 13, 65 2012-10-18 11:10 event1
crw-rw---- root input 13, 74 2012-10-18 11:10 event10
crw-rw---- root input 13, 66 2012-10-18 11:10 event2
crw-rw---- root input 13, 67 2012-10-18 11:10 event3
crw-rw---- root input 13, 68 2012-10-18 11:10 event4
crw-rw---- root input 13, 69 2012-10-18 11:10 event5
crw-rw---- root input 13, 70 2012-10-18 11:10 event6
crw-rw---- root input 13, 71 2012-10-18 11:10 event7
crw-rw---- root input 13, 72 2012-10-18 11:10 event8
crw-rw---- root input 13, 73 2012-10-18 11:10 event9
crw-rw---- root input 13, 63 2012-10-18 11:10 mice
brw------- root root 254, 0 2012-10-18 11:10 dm-0
brw------- root root 254, 1 2012-10-18 11:10 dm-1
brw------- root root 7, 0 2012-10-18 11:10 loop0
brw------- root root 7, 1 2012-10-18 11:10 loop1
brw------- root root 7, 2 2012-10-18 11:10 loop2
brw------- root root 7, 3 2012-10-18 11:10 loop3
brw------- root root 7, 4 2012-10-18 11:10 loop4
brw------- root root 7, 5 2012-10-18 11:10 loop5
brw------- root root 7, 6 2012-10-18 11:10 loop6
brw------- root root 7, 7 2012-10-18 11:10 loop7
brw------- root root 179, 0 2012-10-18 11:10 mmcblk0
brw------- root root 179, 1 2012-10-18 11:10 mmcblk0p1
brw-rw---- system radio 179, 10 2012-10-18 11:10 mmcblk0p10
brw-rw---- system radio 179, 11 2012-10-18 11:10 mmcblk0p11
brw------- root root 179, 12 2012-10-18 11:10 mmcblk0p12
brw------- root root 179, 13 2012-10-18 11:10 mmcblk0p13
brw------- root root 179, 14 2012-10-18 11:10 mmcblk0p14
brw------- root root 179, 15 2012-10-18 11:10 mmcblk0p15
brw------- root root 259, 0 2012-10-18 11:10 mmcblk0p16
brw------- root root 179, 2 2012-10-18 11:10 mmcblk0p2
brw------- root root 179, 3 2012-10-18 11:10 mmcblk0p3
brw-rw---- system radio 179, 4 2012-10-18 11:12 mmcblk0p4
brw-rw---- system radio 179, 5 2012-10-18 11:10 mmcblk0p5
brw-rw---- system radio 179, 6 2012-10-18 11:10 mmcblk0p6
brw-rw---- system root 179, 7 2012-10-18 11:11 mmcblk0p7
brw------- root root 179, 8 2012-10-18 11:10 mmcblk0p8
brw------- root root 179, 9 2012-10-18 11:10 mmcblk0p9
brw------- root root 179, 16 2012-10-18 11:10 mmcblk1
brw------- root root 179, 17 2012-10-18 11:10 mmcblk1p1
lrwxrwxrwx root root 2012-10-18 11:10 param -> /dev/block/mmcblk0p7
drwxr-xr-x root root 2012-10-18 11:10 platform
brw------- root root 1, 0 2012-10-18 11:10 ram0
brw------- root root 1, 1 2012-10-18 11:10 ram1
brw------- root root 1, 10 2012-10-18 11:10 ram10
brw------- root root 1, 11 2012-10-18 11:10 ram11
brw------- root root 1, 12 2012-10-18 11:10 ram12
brw------- root root 1, 13 2012-10-18 11:10 ram13
brw------- root root 1, 14 2012-10-18 11:10 ram14
brw------- root root 1, 15 2012-10-18 11:10 ram15
brw------- root root 1, 2 2012-10-18 11:10 ram2
brw------- root root 1, 3 2012-10-18 11:10 ram3
brw------- root root 1, 4 2012-10-18 11:10 ram4
brw------- root root 1, 5 2012-10-18 11:10 ram5
brw------- root root 1, 6 2012-10-18 11:10 ram6
brw------- root root 1, 7 2012-10-18 11:10 ram7
brw------- root root 1, 8 2012-10-18 11:10 ram8
brw------- root root 1, 9 2012-10-18 11:10 ram9
drwx------ root root 2012-10-18 11:10 vold
im running stock XXALI5 on my Optus i9305

i got my s3lte today and lol when using phone actually missed the features of ur kernel cnt wait for port
Sent from my GT-I9305 using Tapatalk 2

His working on a few things with other phones this weekend so i am hoping we should have this by next week some time . (Hopefully) his a busy man
Sent from my GT-I9305 using xda app-developers app

anyone up for porting will pm dev bwt this. cnt wait to gt this kernel on i9305. best kernel ever
Sent from my GT-I9305 using Tapatalk 2

No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app

Im happy to be kernel Guinni Pig
btemtd said:
No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse

[Q] where is ramdisk.img ?

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.

Need help for the repartitioning of Z3 in order to install Windows 11

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!

Use custom rom inside Android Emulator

Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ 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
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3

dangelob said:
Hi,
This is my first project that I'm currently working on.
I recently bought a android dashcam which UI I would like to change based on my personal preferences. Unfortunately I'm struggling to setup an environment where I can test the changes I make before replacing the original UI on the device itself. I identified the SystemUI.apk to be the place where the manufacturer made customization. I will be using the SystemUI.apk built from AOSP and making my changes based on that. I had no luck trying to decompile the SystemUI.apk in a way that I could build it again.
I was thinking that I could use an android emulator to use the same ROM as the device itself. The manufacturer did not provide any support in providing stock firmware images in any way. So I used the following steps to 'export' the firmware.
1. Unlocking the bootloader using the Identifier Token so I can flash images using fastboot. TWRP was not an option here because I could not find any images for my device nor could I port an TWRP image myself.
2. Enable ADB debugging over usb
3. Enable ADB root privileges using the password: 2846 (if i remember correctly)
4. Use ADB remount and ADB root to gain privileges over the partitions
5. Gain information on partition data
6. Use ADB pull to export images based on partitions
After following the above steps the next thing was to import the images into an emulator. I used the following steps to do this:
1. Create a new device within Android Studio that has the same screen size and os.
2. Replace the system.img, ramdisk.img with the exported variants in ~/Android/Sdk/../arm64-v8a
3. Turn off EncryptUserData inside advancedFeatures.ini to prevent errors like partitions that are unable to encrypt
4. Use the command below to start the emulator
Code:
~/Android/Sdk/emulator/emulator -avd Junsun_A104_API_27 -verbose -show-kernel
5. After running the emulator I receive the error below and the screen of the emulator stays black.
Code:
Please append a correct "root=" boot option; here are the available partitions:
fe00 2867200 vda driver: virtio_blk
fe10 67584 vdb driver: virtio_blk
fe20 819200 vdc driver: virtio_blk
fe30 409600 vdd driver: virtio_blk
fe40 524288 vde driver: virtio_blk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
My assumption is that the emulator does not contain the same partition model used on the device. I could try to export each partition but I wouldn't know how to let the emulator know how to use these partitions. I tried to export the kernel and import it inside the emulator without luck. I did not receive any errors that way.
So my main question is:
- Is there any way I can import the device's rom inside an android emulator
Spoiler: Emulator Config
AvdId=Junsun_A104_API_27
PlayStore.enabled=false
abi.type=arm64-v8a
avd.ini.displayname=Junsun A104 API 27
avd.ini.encoding=UTF-8
disk.dataPartition.size=800M
fastboot.chosenSnapshotFile=
fastboot.forceChosenSnapshotBoot=no
fastboot.forceColdBoot=no
fastboot.forceFastBoot=yes
hw.accelerometer=yes
hw.arc=false
hw.audioInput=yes
hw.battery=yes
hw.camera.back=virtualscene
hw.camera.front=emulated
hw.cpu.arch=arm64
hw.cpu.ncore=4
hw.dPad=no
hw.device.hash2=MD5:7834f5e80eb849ceb46ce01cd4c704f7
hw.device.manufacturer=User
hw.device.name=Junsun A104
hw.gps=yes
hw.gpu.enabled=no
hw.gpu.mode=off
hw.initialOrientation=landscape
hw.keyboard=yes
hw.lcd.density=120
hw.lcd.height=320
hw.lcd.width=1480
hw.mainKeys=no
hw.ramSize=2560
hw.sdCard=yes
hw.sensors.orientation=yes
hw.sensors.proximity=yes
hw.trackBall=no
image.sysdir.1=system-images/android-27/default/arm64-v8a/
runtime.network.latency=none
runtime.network.speed=full
sdcard.size=512M
showDeviceFrame=no
skin.dynamic=yes
skin.name=1480x320
skin.path=_no_skin
skin.path.backup=/home/dangelo/Android/Sdk/skins/tv_1080p
tag.display=Default Android System Image
tag.id=default
vm.heapSize=48
Spoiler: Partition data
$ 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
254 0 1572864 zram0
179 0 30670848 mmcblk0
179 1 5120 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 35840 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 6144 mmcblk0p5
179 6 6144 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 1024 mmcblk0p8
259 1 1024 mmcblk0p9
259 2 1024 mmcblk0p10
259 3 4096 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 1024 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 1024 mmcblk0p16
259 9 1024 mmcblk0p17
259 10 1024 mmcblk0p18
259 11 1024 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 2048 mmcblk0p21
259 14 25600 mmcblk0p22
259 15 1024 mmcblk0p23
259 16 10240 mmcblk0p24
259 17 20480 mmcblk0p25
259 18 1024 mmcblk0p26
259 19 35840 mmcblk0p27
259 20 2867200 mmcblk0p28
259 21 153600 mmcblk0p29
259 22 409600 mmcblk0p30
259 23 1024 mmcblk0p31
259 24 1024 mmcblk0p32
259 25 27059183 mmcblk0p33
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
253 0 27059167 dm-0
output using the ls command with arguments that I forgot
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 boot -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 cache -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 fbootlogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsbd -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 gpsgl -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_deltanv -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_gdsp -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_ldsp -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_modem -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 pm_sys -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 sml_bak -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 system -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2022-04-29 14:35 uboot -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_bak -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 uboot_log -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 userdata -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vbmeta_bak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 vendor -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2022-04-29 14:35 wcnmodem -> /dev/block/mmcblk0p20
Spoiler: Device information
Device name: Junsun A104
Android: 8.1. Oreo API level 27
CPU:
64bit
ARM64-V8A
Spreadtrum SC9832e
Memory: 2GB
Kernel architecture: aarch64
Kernel version: 4.4.83-00001-g213b4e3
Click to expand...
Click to collapse
All you should need is the system.img and the kernel, then extract the system.img untill you find the /system/app and/or the /system/priv-app(whichever folder contains your UI.apk), extract a copy of the UI.apk. Then use APKtool to remove the signature on the apk file then decompile the apk file then make your modifications then recompile and re-sign the apk file. Then place the newly modified UI.apk in the system folder where you extracted it from(overwrite/delete the old version of the apk). Then compress all the files back into the system.img like it was originally and then try to use your newly modified system.img in your emulator.
Try using Bluestacks or one of the other leading android emulators instead of using Android Studio.