Disclaimer: I am not responsible for bricked devices, obviously
Unlike most people here, I do not find the "dual-boot" feature particularly useful due to its buggyness and quirky configuration plus it made the available space for the /system partition divided, leaving only 600++ MB for each system1 and system2. This guide is using CWM v6.0.5.1 (R11) by furniel and donbo.
Prerequisites:
CWM Recovery V6.0.5.1
a Mi 3w (probably doable for the Mi 4 too)
ADB drivers installed
Not necessary, but do back up system1 if you wish to conserve your current ROM and config.
As parted cannot resize partitions, /system (system1) and /system1 (system2) partitions will have to be removed and re-created with the desired size, this is why backing up system1 is favourable.
Reboot to recovery and connect your phone
Open a cmd window (or terminal, if you're using linux), and connect through adb by typing;
Code:
adb devices
adb shell
If everything is fine and you get a shell input (#), start parted by typing;
Code:
parted /dev/block/mmcblk0
unit MB #to set storage unit as MB
print #shows partition table. do remember to screenshot this
Output of "print" should be something like this
Code:
Number Start End Size File system Name Flags
1 0.02MB 2.10MB 2.08MB sbl1
2 2.10MB 3.15MB 1.05MB rpm
3 3.15MB 4.19MB 1.05MB tz
4 4.19MB 5.24MB 1.05MB DDR
5 5.24MB 6.29MB 1.05MB ssd
6 6.29MB 7.34MB 1.05MB dbi
7 7.34MB 11.5MB 4.19MB aboot
8 11.5MB 16.8MB 5.24MB bk1
9 16.8MB 21.0MB 4.19MB misc
10 21.0MB 29.4MB 8.39MB logo
11 29.4MB 67.1MB 37.7MB bk2
12 67.1MB 68.7MB 1.57MB modemst1
13 68.7MB 70.3MB 1.57MB modemst2
14 70.3MB 70.3MB 0.00MB fsc
15 70.3MB 134MB 64.0MB bk3
16 134MB 136MB 1.57MB fsg
17 136MB 168MB 32.0MB bk4
18 168MB 201MB 33.6MB bk5
19 201MB 218MB 16.8MB boot
20 218MB 235MB 16.8MB boot1
21 235MB 252MB 16.8MB recovery
22 252MB 268MB 16.8MB ext4 persist
23 268MB 336MB 67.1MB fat16 modem
24 336MB 403MB 67.1MB fat16 modem1
25 403MB 1074MB 671MB ext4 system
26 1074MB 1745MB 671MB ext4 system1
27 1745MB 2147MB 403MB ext4 cache
28 2147MB 15758MB 13610MB ext4 userdata
Remove partition "system" (system1) and "system1" (system2);
Code:
rm 25
rm 26
Create new partitions after deleting them, partition size is up to you;
Code:
mkpartfs primary ext2 403 1645 # 403MB is the start of the partition ending at 1645 MB, this will be for system1
mkpartfs primary ext2 1645 1745 # Do the same for system2
print # show the partition table to confirm that the partitions are created
name 25 system # name the partition as "system" for system1
name 26 system1 # again for system2
print # check again
quit
Convert newly created partitions to ext4 from ext2;
Code:
#for system1;
tune2fs -j /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
# for system2;
tune2fs -j /dev/block/mmcblk0p26
e2fsck -fDp /dev/block/mmcblk0p26
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p26
e2fsck -fDp /dev/block/mmcblk0p26
Go back to parted to check whether it's applied;
Code:
parted /dev/block/mmcblk0
unit MB
print
It should be like this (if you followed my partition sizes)
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15758MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 0.02MB 2.10MB 2.08MB sbl1
2 2.10MB 3.15MB 1.05MB rpm
3 3.15MB 4.19MB 1.05MB tz
4 4.19MB 5.24MB 1.05MB DDR
5 5.24MB 6.29MB 1.05MB ssd
6 6.29MB 7.34MB 1.05MB dbi
7 7.34MB 11.5MB 4.19MB aboot
8 11.5MB 16.8MB 5.24MB bk1
9 16.8MB 21.0MB 4.19MB misc
10 21.0MB 29.4MB 8.39MB logo
11 29.4MB 67.1MB 37.7MB bk2
12 67.1MB 68.7MB 1.57MB modemst1
13 68.7MB 70.3MB 1.57MB modemst2
14 70.3MB 70.3MB 0.00MB fsc
15 70.3MB 134MB 64.0MB bk3
16 134MB 136MB 1.57MB fsg
17 136MB 168MB 32.0MB bk4
18 168MB 201MB 33.6MB bk5
19 201MB 218MB 16.8MB boot
20 218MB 235MB 16.8MB boot1
21 235MB 252MB 16.8MB recovery
22 252MB 268MB 16.8MB ext4 persist
23 268MB 336MB 67.1MB fat16 modem
24 336MB 403MB 67.1MB fat16 modem1
25 403MB 1645MB 1242MB ext4 system
26 1645MB 1745MB 99.8MB ext4 system1
27 1745MB 2147MB 403MB ext4 cache
28 2147MB 15758MB 13610MB ext4 userdata
You can quit adb now, process is finished. Reboot and restore your back up (if you have made one earlier) or flash a rom through CWM
Do comment/reply if you are having difficulties or otherwise
Thank you so much
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One command is miswritten
mkpartfs primary ext2 1812 3070
It should be
mkpartfs primary ext2 1645 1745
shrisangram said:
One command is miswritten
mkpartfs primary ext2 1812 3070
It should be
mkpartfs primary ext2 1645 1745
Click to expand...
Click to collapse
Lol thanks! Fixed. Didn't notice that
can we use the remaining size of system to data partition?
cause i dont need big size of system, i need for app instead, can we do it?
Thanks,
Will this have any effect if I have to do fastboot of MIUI in future?
Is this method safe since we are playing with partition table?
arif920629 said:
Disclaimer: I am not responsible for bricked devices, obviously
Unlike most people here, I do not find the "dual-boot" feature particularly useful due to its buggyness and quirky configuration plus it made the available space for the /system partition divided, leaving only 600++ MB for each system1 and system2. This guide is using CWM v6.0.5.1 (R11) by furniel and donbo.
...
Do comment/reply if you are having difficulties or otherwise
Click to expand...
Click to collapse
why did these steps??
tune2fs -j /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p25
e2fsck -fDp /dev/block/mmcblk0p25
I was thinking this isn't possible all this while, thank you for posting this amazing tutorial! I have no use for the second system partition either, but instead, I actually needed more system space to flash bigger Gapps! Thank you so much!
Amruth Pillai said:
I was thinking this isn't possible all this while, thank you for posting this amazing tutorial! I have no use for the second system partition either, but instead, I actually needed more system space to flash bigger Gapps! Thank you so much!
Click to expand...
Click to collapse
Did u try it? Is it working?
I would like to know why you have changed the format of the file systems from ext3 to ext4.
srvoleti said:
I would like to know why you have changed the format of the file systems from ext3 to ext4.
Click to expand...
Click to collapse
Code:
[B]Ext4[/B]
[LIST]
[*]Ext4 stands for fourth extended file system.
[*]It was introduced in 2008.
[*]Starting from Linux Kernel 2.6.19 ext4 was available.
[*]Supports huge individual file size and overall file system size.
[*]Maximum individual file size can be from 16 GB to 16 TB
[*]Overall maximum ext4 file system size is 1 EB (exabyte). 1 EB = 1024 PB (petabyte). 1 PB = 1024 TB (terabyte).
[*]Directory can contain a maximum of 64,000 subdirectories (as opposed to 32,000 in ext3)
[*]You can also mount an existing ext3 fs as ext4 fs (without having to upgrade it).
[*]Several other new features are introduced in ext4: multiblock allocation, delayed allocation, journal checksum. fast fsck, etc. All you need to know is that these new features have improved the performance and reliability of the filesystem when compared to ext3.
[*]In ext4, you also have the option of turning the journaling feature “off”.
[/LIST]
With all these features, and an option to... who wouldn't?
Amruth Pillai said:
Code:
[B]Ext4[/B]
[LIST]
[*]Ext4 stands for fourth extended file system.
[*]It was introduced in 2008.
[*]Starting from Linux Kernel 2.6.19 ext4 was available.
[*]Supports huge individual file size and overall file system size.
[*]Maximum individual file size can be from 16 GB to 16 TB
[*]Overall maximum ext4 file system size is 1 EB (exabyte). 1 EB = 1024 PB (petabyte). 1 PB = 1024 TB (terabyte).
[*]Directory can contain a maximum of 64,000 subdirectories (as opposed to 32,000 in ext3)
[*]You can also mount an existing ext3 fs as ext4 fs (without having to upgrade it).
[*]Several other new features are introduced in ext4: multiblock allocation, delayed allocation, journal checksum. fast fsck, etc. All you need to know is that these new features have improved the performance and reliability of the filesystem when compared to ext3.
[*]In ext4, you also have the option of turning the journaling feature “off”.
[/LIST]
With all these features, and an option to... who wouldn't?
Click to expand...
Click to collapse
OK, Thank you for the info.
system2
Why is system2 still exist with 100MB size? I think it will cause error if you do OTA update because MI3 OTA update by default will flash update to system1 and then system2 in the next OTA. Unless if you stick to custom rom or always manually flash update to system1
srvoleti said:
I would like to know why you have changed the format of the file systems from ext3 to ext4.
Click to expand...
Click to collapse
changed? ext4 is default.
m11kkaa said:
changed? ext4 is default.
Click to expand...
Click to collapse
When I checked yesterday, the existing partitions it was shown as ext3 but now it is shown as ext4. That's why I asked that at that time.
This guide also works on Mi2S,its exact copy of it actually (except a minor difference in partition layout).
can anyone pls make a video of this tutorial?
got struck there
iwjy said:
Why is system2 still exist with 100MB size? I think it will cause error if you do OTA update because MI3 OTA update by default will flash update to system1 and then system2 in the next OTA. Unless if you stick to custom rom or always manually flash update to system1
Click to expand...
Click to collapse
Ah, yes, I have the same question, actually...we DO need system2 to be usable atleast, right?
naruse99 said:
can we use the remaining size of system to data partition?
cause i dont need big size of system, i need for app instead, can we do it?
Click to expand...
Click to collapse
can someone make tutorial to resize data partition?
Someone pls confirm the tutorial. Want to try very badly
what to do after step 1??
i am getting this...
anyone, pls help..
Related
Thanks to @munjeni for tipping me off in the right direction and to @judas1977 + @Tesla-MADAL93 for having done this on the Ace 2 I come from ~~
Everything else in this post applies to Gingerbread, scroll down to the 5th message for a more clear guide centered around a 4.1.2 ROM.
This is my annotated diary about the last 2 hours, I'm sorry if the story feels a little bit Dadaist but I don't want to encourage people who don't feel ready to try it, so please read all of it first and if anything is unclear ask instead of doing!!
I installed Busybox 1.22.1 (iirc) and replaced the default shell with bash (install Bash-X from market, copy /S/xbin/bash over /S/bin/sh, remove app if you like to). All of this was done with Gingerbread .188 and CWM 5.5.0.4 from Supercharged kernel.
Original partition table, with names added:
[email protected]:~$ adb shell
Code:
sh-4.2# fdisk -u -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders, total 15515648 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 2047 1023+ 0 Empty #### TA ("Trim Area") IMEI, BL UNLOCK, SIMLOCK ETC -- DO NOT TOUCH
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 2304 3327 512 f0 Linux/PA-RISC boot #### SBL? Mem-init? Power management? PARAM?
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2048 2303 128 f0 Linux/PA-RISC boot #### unknown, as above
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 3328 15269887 7633280 5 Extended #### GROUPS ALL FOLLOWING PARTITIONS FOR THEM TO FIT INTO THE 4-PARTS MBR SCHEME
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 4096 20479 8192 4a Unknown #### another of the 4 unclear partitions
/dev/block/mmcblk0p6 20480 26623 3072 83 Linux #### MODEMFS (Samsung's "EFS") RADIO CALIBRATION
/dev/block/mmcblk0p7 26624 36863 5120 70 Unknown #### no idea either
/dev/block/mmcblk0p8 36864 53247 8192 83 Linux #### IDD (apparently related to usage stats reporting)
/dev/block/mmcblk0p9 53248 86015 16384 48 Unknown #### KERNEL
/dev/block/mmcblk0p10 118784 2215935 1048576 83 Linux #### SYSTEM
/dev/block/mmcblk0p11 2727936 6922239 2097152 83 Linux #### DATAFS
/dev/block/mmcblk0p12 2215936 2727935 256000 83 Linux #### CACHEFS
/dev/block/mmcblk0p13 86016 118783 16384 48 Unknown #### FOTAKERNEL?
/dev/block/mmcblk0p14 6922240 15269887 4173824 c Win95 FAT32 (LBA) #### SDCARD/EMMC/UMS
Partition table entries are not in disk order
so let's rearrange this list for easier thinking & reading
Code:
/dev/block/mmcblk0p1 1 2047 1023+ TA
/dev/block/mmcblk0p3 2048 2303 128 ?
/dev/block/mmcblk0p2 2304 3327 512 ?
/dev/block/mmcblk0p5 4096 20479 8192 ?
/dev/block/mmcblk0p6 20480 26623 3072 MODEMFS
/dev/block/mmcblk0p7 26624 36863 5120 ?
/dev/block/mmcblk0p8 36864 53247 8192 IDD
/dev/block/mmcblk0p9 53248 86015 16384 KERNEL
/dev/block/mmcblk0p13 86016 118783 16384 FOTAKERNEL?
/dev/block/mmcblk0p10 118784 2215935 1048576 SYSTEM
/dev/block/mmcblk0p12 2215936 2727935 256000 CACHEFS
/dev/block/mmcblk0p11 2727936 6922239 2097152 DATAFS
/dev/block/mmcblk0p14 6922240 15269887 4173824 SDCARD
great, the important (for us) stuff is contiguous so we can delete those partitions and recreate them
(if fdisk works like parted we must do that in numerical order, so system>data>cache>ums)
we must delete and recreate partition 13 with the same sizes
OTOH fdisk lets us experiment without saving in real time (!!!) but let's do this in recovery mode
Let's research the sizes we want first -- I find Link2SD's graphical df the best way to do this (see photo 1)
so 540 MB for /system should be enough (I have 454M used, account a safety margin as I integrate updates + FS overhead + 1000 vs 1024 units)
4,14 MB used on /cache... 7,8 MB should be more than enough (same size I used on my Ace 2 which had about 5 MB used there)
this large size is for dalvik cache on ROMs that store it there (vm.dalvik.dexopt-data-only=0 and vm.dalvik.dexopt-cache-only=1 or something)
494 MB on /data, but I'd probably want to change apps and stuff... let's try with 1,25 GB
but if we remove /system we'll have to reflash the rom from a zip, which I'd need to make...
let's leave that partition alone for this first time
reboot now
Click to expand...
Click to collapse
Launching fdisk:
#### SONY
#### SONY (red green blue lightbar)
#### + button
#### CWM-based recovery v5.5.0.4
[email protected]:~$ adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
#### No shell in ramdisk? Very lame...
#### [Mounts and storage]
#### [Mount /system, unmount everything else]
[email protected]:~$ adb shell
sh-4.2# fdisk -u /dev/block/mmcblk0
Command (m for help):
What I did in fdisk:
u #### change units to sectors
d #### delete
14
d
13
d
12
d
11
c #### disable cylinder rounding
n #### new
l #### logical partition
First sector (3334-15269887, default 3334): 2215936
Sector 2215936 is already allocated #### Apparently this version of fdisk makes you waste a sector...
First sector (2215937-15269887, default 2215937): Using default value 2215937
Last sector or +size or +sizeM or +sizeK (2215937-15269887, default 15269887): +1600M
#### CACHEFS:
n
l
First sector (3334-15269887, default 3334): 5340938
Sector 5340938 is already allocated
First sector (5340939-15269887, default 5340939): Using default value 5340939
Last sector or +size or +sizeM or +sizeK (5340939-15269887, default 15269887): +8M
#### FOTAKERNEL
n
l
First sector (3334-15269887, default 3334): 86016
Sector 86016 is already allocated
First sector (86017-15269887, default 86017): Using default value 86017
Last sector or +size or +sizeM or +sizeK (86017-118783, default 118783): Using default value 118783
t
Partition number (1-14): 13
Hex code (type L to list codes): 48
Changed system type of partition 13 to 48 (Unknown)
#### USB STORAGE
n
l
First sector (3334-15269887, default 3334): 5356564
Sector 5356564 is already allocated
First sector (5356566-15269887, default 5356566): Using default value 5356566
Last sector or +size or +sizeM or +sizeK (5356566-15269887, default 15269887): Using default value 15269887
c
Partition number (1-14): 14
Hex code (type L to list codes): c
Changed system type of partition 14 to c (W95 FAT32 LBA)
w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
sh-4.2# reboot
Now enter CWM again and factory reset -- you'll get an error as it can't delete /sdcard/.android_secure as it's unformatted
(and for that matter this CWM can't format /sdcard either...)
No problem apart from skipped heartbeats, boot into Android and format it from the settings! (see photo 2)
Well, the last screenshot speaks for itself... but I'll repeat, don't try this at home! (Have a friend try it so you'll have someone to blame if it gets bricked)
Very interesting... It causes problems?
Inviato dal mio ST25i utilizzando Tapatalk
ale467 said:
Very interesting... It causes problems?
Click to expand...
Click to collapse
Unlike my example, you must have over 50M free on /cache (at least in Gingerbread) or cheat by bind-mounting it somewhere else... or give up on directly installing stuff from the market
I tried bind mounting /cache to /data/local/tmp/cache but Google Play is still broken, so I guess you'll want a 57M partition there...
Also, you can always return to stock layout by flashing a full ROM in green light download mode, then wiping /sdcard from settings
I'm going to update this for 4.1, it's even somewhat easier and more predictable
----------------
1: think of the rough partition sizes
Code:
system (350M)
data (1,5G)
cache (280M) ## keep in mind whether ROM uses this for dalvik-cache and at least in 2.x Google Play downloads there
sdcard (remaining space)
2: make sure you have some files ready
→ROM in recovery zip format
→Backup of everything you want
→Kernel with fdisk in ramdisk
→ADB known working in recovery and normal mode
→Fixed busybox (http://forum.xda-developers.com/attachment.php?attachmentid=1057725&d=1336884034)
3: enter recovery and dump partition table (adb shell, fdisk /dev/block/mmcblk0, p)
Unlike my previous experiment, I'll calculate sizes in cylinders -- harder but fdisk appears to work better that way
Code:
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
[...]
/dev/block/mmcblk0p10 1857 34624 1048576 83 Linux #SYSTEM
/dev/block/mmcblk0p11 42625 108160 2097152 83 Linux #DATAFS
/dev/block/mmcblk0p12 34625 42624 256000 83 Linux #CACHEFS
/dev/block/mmcblk0p13 1345 1856 16384 48 Unknown #FOTAKERNEL, move this on another line if it helps you think better but put it back there after calculations
/dev/block/mmcblk0p14 108161 238592 4173824 c Win95 FAT32 #UMS
so our work area starts at cylinder 1857 and ends at 238592!
4: calculate partition sizes (I'll only list start & end cylinders for clarity)
Code:
/dev/block/mmcblk0p10 1857 12538 << 1857 + (350000000÷32768)
/dev/block/mmcblk0p11 12538+1 >> 12539 58315 << 12539+(1500000000÷32768)
/dev/block/mmcblk0p12 58315+1 >> 58316 66861 << 58316 +(280000000÷32768)
/dev/block/mmcblk0p13 1345 1856
/dev/block/mmcblk0p14 66861+1 >> 66862 238592
5: remove partitions (d, 14, d, 13, ..., 10)
6: create partitions (n, l, 1857, 12538, repeat for next row)
7: retype partitions (t, 13, 48, t, 14, c)
8: save changes (w, reboot) - enter recovery again, you should get 5 "E: Can't {mount|open} /cache/[...]" lines
9: go to mounts and storage and run all 4 formats, sdcard will probably fail -- if it doesn't skip to step 13
10: install fixed busybox (adb push '/home/riki/Desktop/busybox' /cache/)
11: enter adb shell, make it executable (chmod +x /cache/busybox)
12: format media partition (/cache/busybox mkfs.vfat /dev/block/mmcblk0p14)
13: quit shell, mount /sdcard in CWM
14: adb push your ROM to /sdcard, install it and reboot!
This is so interesting, I've being doing this on a Samsung Galaxy SCL to fix it as its internal storage and /data partition were totally corrupted. I used parted instead of fdisk to repartition the external SD and edit then kernel's RAM disk to make it mount /data in one of the new partitions. Because of this that I've been doing lately, I'm thinking of using fdisk in my Xperia U too to have more available space in internal SD, that would be great, as I use dual boot feature.
I think I'll do this when I'm be fed up of Jelly Bean being the main ROM and KitKat just the secondary one.
By the way, I think it can be possible to leave enough free space before mmcblk0p14 to create my secondary ROM's partitions there (mmcblk0p15 for /system, mmcblk0p16 for /data and mmcblk0p17 for /cache) instead of creating system.ext4, data.ext4 and cache.ext4 inside my internal SD and mounting them in loop devices... What do you think? Could I brick my phone doing that? I've asked here too just in case.
The only thing I'd have to do is to format my mmcblk0p15 using mke2fs to set the same UUID as in mmcblk0p10 just if my secondary ROM doesn't boot (but I think this wouldn't be necessary):
Code:
mke2fs -T ext4 -O has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize -U [COLOR="Silver"][mmcblk0p10's UUID][/COLOR] -I 256 /dev/block/mmcblk0p15
You've explained this how-to so well, @Ryccardo! Thanks for this tutorial.
Many, many thanks to you, sir!
Thanks to you i was able to increase data partition on my P (similar partition scheme to U).
Other tutorials weren't so useful than yours and i was searching quite a lot. Thank you, live in wealth!
What many refer to as the "internal SD Card" is actually a partition of the internal memory module that is formatted FAT32 for cross-platform use, and dedicated to user storage (usb transfer, downloads, photos & videos, etc). Other partitions of the internal memory module use file system formats that are more specific to the linux-based operations of Android, kernels, bootloaders, etc.
The total size of the internal memory module of the SGH-i777 is 15.8 GB, and it is partitioned as shown in the table below.
Booted into Android: Settings > Storage, you should see reports for:
- "INTERNAL STORAGE" ~2GB
- "INTERNAL STORAGE" ~11.5GB
- IF you have an SD Card installed, you should see a third report named "SD CARD"
(Using the partition table as reference)
The first "internal storage", displays the status of the /data partition. This partition is populated by user-installed apps & data, as well as the user-specific data for /system apps.
The second "internal storage", displays the status of the user-storage partition.
Stock I777 Partition Table:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
The path to user-storage (both internal and external) may vary from Android when booted into recovery.
Booted into Android
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/block/vold/259:3 /mnt/secure/asec vfat rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Booted into CWMR
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/block/vold/179:9 on /storage/sdcard1 type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
Booted into TWRP
internal & external user-storage are located at /emmc & /sdcard
These path names more appropriately represent the type of memory used. eMMC = embedded Multimedia Card
http://en.wikipedia.org/wiki/MultiMediaCard#eMMC
http://www.pcmag.com/encyclopedia/term/64404/emmc
The inconsistency with android's naming system can be an issue for apps that write OpenRecoveryScripts while booted into android, to be performed in recovery.
Code:
mount
/dev/block/mmcblk0p11 on /emmc type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk0p11 on /and-sec type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk1p1 on /sdcard type vfat (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
Code:
TWRP CWMR & AOSP Device Label FileSys size (MB)
mmcblk0 179:0
mmcblk0p /efs /efs 179:1 EFS ext4 20
mmcblk0p2 179:2 SBL1 1.2
mmcblk0p3 179:3 SBL2 1.2
mmcblk0p4 179:4 PARAM 8
mmcblk0p5 /boot /boot 179:5 KERNEL 8
mmcblk0p6 /recovery /recovery 179:6 RECOVERY 8
mmcblk0p7 /cache /cache 179:7 CACHE ext4 246
mmcblk0p8 259:0 MODEM 16
mmcblk0p9 /system /system 259:1 FACTORYFS ext4 504
mmcblk0p10 /data /data 259:2 DATAFS ext4 2016
mmcblk0p11 /emmc /storage/sdcard0 259:3 UMS FAT32 11634
mmcblk0p12 /preload /preload 259:4 HIDDEN ext4 504
mmcblk1 179:8
mmcblk1p1 /sdcard /storage/sdcard1 179:9 {whatevr} FAT32 {as purchased}
This information above was helpful for me recently, and although these devices are well aged, I hope that the info. can be useful for someone else.
We have @SteveMurphy and @razen_kain to thank for encouraging me to compile and post this stuff.
From an ADB shell, or within a terminal emulator, "mount" will give you a report of the currently mounted devices, and their mount points, permissions and more.
The original partition table posted is reported from gparted, within an ADB shell
adb devices
^if it returns your device serial, then ADB can see your device
adb shell
^starts a shell session on the device
parted /dev/block/mmcblk0
^starts a gparted session on disk "mmcblk0", the internal memory module
print
^displays the partition table
If I have any of this information incorrect, or if there's more information that should be included, please let me know.
There's an entire world of fstab, device mapping, and volume daemons that I am NOT savvy with, so I chose not to run down that rabbit hole.
This is fantastic stuff! I know you put a lot of work into it, so thanks for all the research you've accumulated and shared.
cyril279,
Very helpful info. Nice job on compiling and posting the info. Thanks for taking the time to do it and for continuing to help in this forum.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Great work man! We really appreciate you putting your time and effort into this. I am curious though what the 959g looks like. I know the recovery is on a different partition but that is the only difference Im aware of.
We would only know for sure if we analyze a 959 phone, but I'm going to guess that the partition table would be exactly the same. Notice that mmcblk0p6 is Recovery, and on the I777 that partition is not used.
so I wanted to try this but my android says:
Code:
C:\Users\Allan Romero>adb shell
[email protected]:/ $ parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
/system/bin/sh: parted: not found
127|[email protected]:/ $
is there a way to fix this, I wanted to compare the partition tables of my SGH-S959G to the SGH-I777, reason being was that when I go to download mode it says model S959G and I wanted to see if it can be changed to show the i777 under model.
micallan_17 said:
so I wanted to try this but my android says:
Code:
C:\Users\Allan Romero>adb shell
[email protected]:/ $ parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
/system/bin/sh: parted: not found
127|[email protected]:/ $
is there a way to fix this, I wanted to compare the partition tables of my SGH-S959G to the SGH-I777, reason being was that when I go to download mode it says model S959G and I wanted to see if it can be changed to show the i777 under model.
Click to expand...
Click to collapse
Did you boot into recovery before you ran adb shell? First boot into recovery, next type adb shell and you will get a ~ # prompt, then type parted /dev/block/mmcblk0 followed by print.
creepyncrawly said:
Did you boot into recovery before you ran adb shell? First boot into recovery, next type adb shell and you will get a ~ # prompt, then type parted /dev/block/mmcblk0 followed by print.
Click to expand...
Click to collapse
Oh I see, your tip fixed it, so I got this:
Code:
C:\Users\Allan Romero>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
(parted)
someone with more inside knowledge can let us know if there are any differences perhaps?
so based on comparison by looks:
code from cyril279:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
code from mines:
Code:
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 317MB 262MB ext4 CACHE
8 317MB 333MB 16.8MB MODEM
9 333MB 870MB 537MB ext4 FACTORYFS
10 870MB 3018MB 2147MB ext4 DATAFS
11 3018MB 15.2GB 12.2GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
micallan_17 said:
is it safe to say that flashing the i777 bootloader (odin screen one) to the SGH-S959G would basically convert it to an i777?
Click to expand...
Click to collapse
I suppose, but what I don't get is why it matters? The devices are practically identical, excepting the 959 having the separate partition which is a great thing and something the i777/i9100 lacks.
So what I'm asking is because our two phones are almost the same and can flash the same roms/kernels/recovery, what does it matter if it says '959' or 'i777'?
SteveMurphy said:
I suppose, but what I don't get is why it matters? The devices are practically identical, excepting the 959 having the separate partition which is a great thing and something the i777/i9100 lacks.
So what I'm asking is because our two phones are almost the same and can flash the same roms/kernels/recovery, what does it matter if it says '959' or 'i777'?
Click to expand...
Click to collapse
oh, I see I didn't know about the separate partition, I guess it doesn't really matter what it says on it, thanks for the reply
Cheers
Great info. Thanks fellas.
anyone fhave a new pit file for the s959g to increase system partition been searching for hours or would the one for the i777 work fine. I don't want to loose my separate recovery partition. I want to be able in install full slim gaaps
Created one don't need now.
This thread assumes there is no ROM released for recovery and you need to start from scratch to build a recovery.
After doing a lot of searching I have put together of list of items needed to build your own partition.xml file based on your specific device.
#1 A rooted phone is a must! You need to be able to backup all partitions including the partition table. Using DD is your friend here.
To build the partition.xml file you'll need the to know the following items at a minimum-
1 partition label
2 size in kb
3 type
There are other parameters such as bootable, readonly and filename but for purposes of this post we'll only work with the first three
You can use a variety of commands to get the partition label and size. e.g.-
# cat /proc/partition
# mount
# df
# parted /dev/block/mmcblk0
# ls -l /dev/block/platform/"some number".sdhci/by-name
Probably the most useful command will come from parted. (Assuming you already have it installed in your system. How to install it is another topic I won't cover here to keep this topic on track)
Code:
[email protected]_STUDIO_C_5_5_LTE:/system/bin # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC H8G1e (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 134MB 67.1MB fat16 modem
2 134MB 135MB 524kB sbl1
3 135MB 135MB 524kB sbl1bak
4 135MB 136MB 1049kB aboot
5 136MB 137MB 1049kB abootbak
6 137MB 138MB 524kB rpm
7 138MB 138MB 524kB rpmbak
8 138MB 139MB 786kB tz
9 139MB 140MB 786kB tzbak
10 140MB 141MB 1049kB pad
11 141MB 143MB 1573kB modemst1
12 143MB 144MB 1573kB modemst2
13 144MB 145MB 1049kB misc
14 145MB 145MB 1024B fsc
15 145MB 145MB 8192B ssd
16 145MB 156MB 10.5MB splash
17 201MB 201MB 32.8kB DDR
18 201MB 203MB 1573kB fsg
19 203MB 203MB 16.4kB sec
20 203MB 237MB 33.6MB boot
21 237MB 2334MB 2097MB ext4 system
22 2334MB 2367MB 33.6MB ext4 persist
23 2367MB 2401MB 33.6MB ext4 apedata
24 2401MB 2669MB 268MB ext4 cache
25 2669MB 2703MB 33.6MB recovery
26 2703MB 2704MB 1049kB devinfo
27 2751MB 2752MB 524kB keystore
28 2752MB 2819MB 67.1MB oem
29 2819MB 2820MB 524kB config
30 2820MB 7818MB 4999MB ext4 userdata
You can see we can get the start, end and total size of each partition as well as the partition names.
Now we need to translate partition names into the "type" value in our partition.xml file. (Where type="some long string of numbers with dashes in between") Here is the list I have come up with so far assuming we have a GPT partition structure in our device. Always verify these values for your specific device! You have been warned.
Code:
098DF793-D712-413D-9D4E-89D711772228 rpm
0A288B1F-22C9-E33B-8F5D-0E81686A68CB modemst2
20117f86-E985-4357-B9EE-374BC1D8487D boot, recovery
20A0C19C-286A-42FA-9CE7-F64C3226A794 DDR
2C86E742-745E-4FDD-BFD8-B6A7AC638772 ssd
400FFDCD-22E0-47E7-9A23-F16ED9382388 aboot
57B90A16-22C9-E33B-8F5D-0E81686A68CB fsc
638FF8E2-22C9-E33B-8F5D-0E81686A68CB fsg
A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4 tz
D4E0D938-B7FA-48C1-9D21-BC5ED5C4B203 dbi or sdi depending on device
DEA0BA2C-CBDD-4805-B4F9-F428251C3E98 sbl1
EBBEADAF-22C9-E33B-8F5D-0E81686A68CB modemst1
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 modem, pad, system, userdata, persist, cache
You can get these values from using the gptfdisk binary as seen in this post
forum.xda-developers.com/showpost.php?p=33358988&postcount=2 (Thanks to E:V:A)
or head on down to the spoiler section here and you can see what the labels look like- (Partition GUID Code)
https://translate.google.com/transl...ersion/index.php?t552073-420.html&prev=search
Lastly my assumption is that if the partition size is not evenly divisible by 1024 you would round up to the next nearest kb value.
33.6MB=33600kb
33600/1024=34406.4 (cant have a partial kb left over so round up)
34407
33.6MB=34407kb. Let's plug this vaule into our xml file
size_in_kb="34407"
I'm new at this. If ANY of this is wrong please comment and correct. I hope this will help!
Currently I am analysing partition.xml file in AndroidGo(nhlos) (chipset msm8909). I want to know what are the utilities of below parameters:
1) partition label
2) size in kb
3) type
4) bootable
5) readonly
For example: <partition label="boot" size_in_kb="32768" type="20117F86-E985-4357-B9EE-374BC1D8487D" bootable="false" readonly="true" filename="boot.img"/>
Please let me know , so that it will be helpful.
So, trying to install LineageOS on a stock Sony Xperia T, I got to trying to unify the userdata and now I have a 2GB "Internal Storage" (on /sdcard) partition and no "Legacy SDCard" partition. So clearly I messed up. I looked at the source code of the unify_userdata-20170128.zip file and it looks like all it does is delete the old UserData and SDCard partitions and then creates a new partition using all the sectors that were previously divided between these two partitions.
My question is this: is this correct? Why did android have two partitions of ~2Gb for Internal Storage and ~10Gb for the Legacy SD Card? Does the unify_userdata script really just delete these two and make one partition from the freed space?
And also, how can I fix my phone? In adb shell, df reports that the userdata partition (number 14) is mounted at /sdcard and is 2GB, but fdisk says that partition 14 has the label Userdata and is 13Gb. So how can it be mounted and only show a size of 2Gb?
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 423.7M 16.0K 423.7M 0% /dev
tmpfs 423.7M 24.0K 423.7M 0% /tmp
/dev/block/mmcblk0p13 246.1M 4.2M 241.8M 2% /cache
/dev/block/mmcblk0p14 2.0G 35.0M 1.9G 2% /data
/dev/block/mmcblk0p14 2.0G 35.0M 1.9G 2% /sdcard
Code:
# fdisk -l /dev/block/mmcblk0
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 7423 1536K 0700 Boot
3 7424 10495 1536K 0700 Boot2
4 12288 53247 20.0M 0700 Kernel
5 53248 55295 1024K 0700 TZ
6 57344 63487 3072K 0700 modemst1
7 65536 71679 3072K 0700 modemst2
8 73728 79871 3072K 0700 fsg
9 79872 90111 5120K 0700 ramdump
10 90112 106495 8192K 0700 apps_log
11 106496 139263 16.0M 0700 FOTAKernel
12 139264 2654207 1228M 0700 System
13 2654208 3166207 250M 0700 Cache
14 3166208 30535646 13.0G 0700 Userdata
Hi,
I deleted all the partitions on Poco F1 in assumption that fastboot flashing creates partitions but I was wrong. I would really appreciate if anyone (preferably with 64GB device) provide me the output of parted /dev/block/sda.
Thank you
hello, the partitions are
1 24.6kB 45.1kB 20.5kB switch
2 45.1kB 73.7kB 28.7kB ssd
3 73.7kB 524kB 451kB bk01
4 524kB 786kB 262kB bk02
5 786kB 1053kB 266kB bk03
6 1053kB 1577kB 524kB keystore
7 1577kB 2097kB 520kB frp
8 2097kB 4194kB 2097kB bk04
9 4194kB 8393kB 4198kB misc
10 8393kB 16.8MB 8409kB logfs
11 16.8MB 33.6MB 16.8MB oops
12 33.6MB 50.0MB 16.4MB devinfo
13 50.3MB 67.1MB 16.8MB bk05
14 67.1MB 134MB 67.1MB ext4 persist
15 134MB 201MB 67.1MB ext4 persistbak
16 201MB 268MB 67.1MB logdump
17 268MB 403MB 134MB minidump
18 403MB 1275MB 872MB ext4 cust
19 1275MB 1342MB 67.1MB recovery
20 1342MB 1611MB 268MB ext4 cache
21 1611MB 57.0GB 55.4GB ext4 userdata
you need to create them using parted
i got my device working with this tutorial:
alee.pwf said:
hello, the partitions are
1 24.6kB 45.1kB 20.5kB switch
2 45.1kB 73.7kB 28.7kB ssd
3 73.7kB 524kB 451kB bk01
4 524kB 786kB 262kB bk02
5 786kB 1053kB 266kB bk03
6 1053kB 1577kB 524kB keystore
7 1577kB 2097kB 520kB frp
8 2097kB 4194kB 2097kB bk04
9 4194kB 8393kB 4198kB misc
10 8393kB 16.8MB 8409kB logfs
11 16.8MB 33.6MB 16.8MB oops
12 33.6MB 50.0MB 16.4MB devinfo
13 50.3MB 67.1MB 16.8MB bk05
14 67.1MB 134MB 67.1MB ext4 persist
15 134MB 201MB 67.1MB ext4 persistbak
16 201MB 268MB 67.1MB logdump
17 268MB 403MB 134MB minidump
18 403MB 1275MB 872MB ext4 cust
19 1275MB 1342MB 67.1MB recovery
20 1342MB 1611MB 268MB ext4 cache
21 1611MB 57.0GB 55.4GB ext4 userdata
you need to create them using parted
i got my device working with this tutorial:
Click to expand...
Click to collapse
Hey thanks bro.
I also recovered my device, I guess I will try installing Windows again
Thanks
Could you give the output for the poco 128gb model
I kinda did the same thing
Any tut help ,i got same problem
bethtinker said:
Could you give the output for the poco 128gb model
I kinda did the same thing
Click to expand...
Click to collapse
Hi, sorry I didn't see this thread. I think partitions would be same as 64gb model, just give remaining space to last partition i.e. userdata
alee.pwf said:
hello, the partitions are
1 24.6kB 45.1kB 20.5kB switch
2 45.1kB 73.7kB 28.7kB ssd
3 73.7kB 524kB 451kB bk01
4 524kB 786kB 262kB bk02
5 786kB 1053kB 266kB bk03
6 1053kB 1577kB 524kB keystore
7 1577kB 2097kB 520kB frp
8 2097kB 4194kB 2097kB bk04
9 4194kB 8393kB 4198kB misc
10 8393kB 16.8MB 8409kB logfs
11 16.8MB 33.6MB 16.8MB oops
12 33.6MB 50.0MB 16.4MB devinfo
13 50.3MB 67.1MB 16.8MB bk05
14 67.1MB 134MB 67.1MB ext4 persist
15 134MB 201MB 67.1MB ext4 persistbak
16 201MB 268MB 67.1MB logdump
17 268MB 403MB 134MB minidump
18 403MB 1275MB 872MB ext4 cust
19 1275MB 1342MB 67.1MB recovery
20 1342MB 1611MB 268MB ext4 cache
21 1611MB 57.0GB 55.4GB ext4 userdata
you need to create them using parted
i got my device working with this tutorial:
Click to expand...
Click to collapse
sd24sep said:
Hi,
I deleted all the partitions on Poco F1 in assumption that fastboot flashing creates partitions but I was wrong. I would really appreciate if anyone (preferably with 64GB device) provide me the output of parted /dev/block/sda.
Thank you
Click to expand...
Click to collapse
Hi. me to deleted all the partition in my poco. I can not restore the partition table, the mini tool partition wizard does not see the connected phone as storage. how u format storage and create partition? plees help
Lss6219 said:
Hi. me to deleted all the partition in my poco. I can not restore the partition table, the mini tool partition wizard does not see the connected phone as storage. how u format storage and create partition? plees help
Click to expand...
Click to collapse
Partition software for computer wouldn't be useful to manipulate internal partitions of a phone, use parted (arm Linux static binary), push it to phones internal storage using recovery/adb and then you can create partitions.
sd24sep said:
Partition software for computer wouldn't be useful to manipulate internal partitions of a phone, use parted (arm Linux static binary), push it to phones internal storage using recovery/adb and then you can create partitions
Click to expand...
Click to collapse
Parted does not detect a phone connected in fastboot mode. I loaded the phone into the tvrp recovery and turned on the MTP mode and it is determined through the adb devices command, but the parted does not see it. By the way, I managed to mount only the Vendor and Firmware section in the mtp, the rest are not selected
Lss6219 said:
Parted does not detect a phone connected in fastboot mode. I loaded the phone into the tvrp recovery and turned on the MTP mode and it is determined through the adb devices command, but the parted does not see it. By the way, I managed to mount only the Vendor and Firmware section in the mtp, the rest are not selected
Click to expand...
Click to collapse
Bro you are confused, you still running parted on computer while phone is connected. Let me give you rough step by step,
1. Boot phone into TWRP
2. Connect phone to computer
3. adb push parted /cache (use appropriate path for parted, and only cache partition needs to be mounted, so umount if any other partitions are mounted)
4. adb shell (run rest of these commands in adb shell)
5. cd /cache
6. chmod +x parted
7. ./parted (notice ./)
8. Then parted will start and running locally on phone (not on computer) then proceed with creating partitions.
Sorry for delay, I rarely login to xda. Best luck.
E:\New folder (2)\New folder\parted>adb push parted /cache
7748 KB/s (464372 bytes in 0.058s)
E:\New folder (2)\New folder\parted>adb shell
~ # cd /cache
/cache # chmod +x parted
/cache # ./parted
Error: No device found
Retry/Cancel? cancel
/cache # chmod +x parted
/cache # ./parted
Error: No device found
Retry/Cancel? cancel
/cache #
what should i do in this situation ?