How to resize system partition size - Xiaomi Mi 8 Pro Questions & Answers

Hello,
i was looking for a help,i wanted to flash GSI MIUI 13 on my mi 8 pro.but GSI img file size are larger than targeted device.so i have to resize system partition.but I'm noob for resizing pertition size,is anyone can help me out to do that?
and one more to know is it harmful to do resizing?
and if i resize it , am I able to go back previous partition size.i mean if I want to flash stock rom again.
please help me out guy's I'm really stuck here.

Related

[Q] How to add extra space to the /system folder?

Hi guys, i have this streak 5 with CM9 ICS ROM Installed,
I also have an 8gb internal SD installed.
I wanted to add extra space to the /system/app folder, because currently it only has 1mb of space left, and i wanted to install Google Now which needs 60mb of space.
How do i actually expand or mount extra space to the /system folder/partition? Thanks..
for stock rom or original custom rom... not gonna happen...
but with modified custom rom.. there is light... read the thread on my signature and be sure to read till the end to get the idea how is it possible...
deysmacro said:
for stock rom or original custom rom... not gonna happen...
but with modified custom rom.. there is light... read the thread on my signature and be sure to read till the end to get the idea how is it possible...
Click to expand...
Click to collapse
Saw the threads and i think i need some more light on doing this.
I realize that i need gparted thingy and do some modifications to the recovery and also the custom rom itself.
I basically just wanted to increase the /system folder size of my CM9 probably to 512mb or more,
I've read that i need to apply streak5sd8 layout to the innerSD, but my question is how?
Got any links on step-by-step method on customizing my custom rom, recovery, and partition?
Thanks

modify stock rom partition layout

Hello All,
i read from the internet and get the idea/method how to unpack and repack the img file, gether the stock (original) partition layout from the device through terminal.
but my goal is to modify the partition layout in the stock rom in the update.zip released by the manufacture.
could somebody point me to which file(s) i should modify?

[GUIDE][Lollipop]Dual Boot CM and/or Stock OS

This guide is show you how to install second OS in SDCard, so you can have two complete separate OS (each have their own /system, /data and /cache), this will be useful if you want to try out a new ROM or a new version, like CM or latest Stock build etc. I have pre-build 2 ROMs in this guide. and list the instructions of how to do it in post #2.
The whole method is just an implementation of @SHM (Modding.MyMind) guide that inside the post here, so all the credit goes to him:
http://forum.xda-developers.com/showpost.php?p=62460895&postcount=325
Highlight of the steps:
1. Partition a SDCard (32GB or bigger) to have 3 ext4 partitions after regular FAT32 partition
2. Flash two customized flashable zip in twrp so that:
boot image flashed to /dev/block/mmcblk0p18 (regular boot partition)
system image flashed to /dev/block/mmcblk1p2 (sdcard)
The boot image contains the fstab file, it has been updated to use partitions on sdcard as the /system, /data and /cache for the 2nd OS.
And of course, the flashable zip has updater script changed so that, it will flash they system image to correct partition on SDCard.
Note / Limitation:
1) After boot to 2nd OS on the SDCard, theoretically, while you are in Android OS, everything should work. The speed/performance may differ depends on the SDCard read/write speed.
2) TWRP, except flash the zip to install the customized system image to SDCard, all other function will not work for the 2nd OS, The backup/restore function is still working on the primary OS /system, /data etc.
3) Boot partition (/dev/block/mmcblk0p18), this partition will decide which OS it will boot, and the boot image should corresponded to your OS system partition. So if you flashed above boot image for 2nd OS, it will find /system on SDCard and boot it. And if you flashed (or restore) your primary OS boot image, then it will boot to your primary OS /system.
Things you need before you start:
1. MT2L03 with Lollipop installed, TWRP installed, and have a backup of your primary OS (at least /system, and /boot partitions)
2. An empty SDCard that is 32GB or bigger, strongly recommend class 10 or faster. (16GB will work, then you don't have much external space left)
Steps to install 2nd OS to sdcard:
(Note, I will call the empty SDCard as sdcard#2, and your current sdcard in the phone as sdcard#1.)
1. Make a backup of your current OS using twrp, include at least /system and /boot, to your sdcard#1.
2. Install the PartitionWizard (files location below) on windows, and put the empty SDCard#2 to computer sdcard reader.
3. Launch Partition Wizard, and carefully re-partition your SDCard#2 to following:
(pls refer to xda wiki about the usage: http://forum.xda-developers.com/wiki/SD_card_partitioning )
1st Partition: FAT32 primary size: (Total size minus 15000MB), for example, for 64GB(60000MB) card, choose 45000MB
2nd: ext4 primary size: 1800MB (/system for 2nd OS)
3rd: ext4 primary size: 12500MB (/data for 2nd OS)
4rd: ext4 primary size: rest space, should be great than 200MB (/cache for 2nd OS)
Since partition 2/3/4 total size is 14320MB, thus the 1st partition size is (Total size minus 15000MB)
4. Apply the change, this will take some time (like 20 to 30min).
5. Once sdcard#2 is re-partitioned and formatted, unplug and re-plug sdcard#2 to windows again. Right click the sdcard drive letter, and click "Open" to open the FAT32 partition. ( I found double click the drive letter will give error if the FAT32 is bigger than 32GB, but right click and open works)
Copy two flashable zip (file location below) to the sdcard#2.
6. Reject the sdcard#2, and remove it from windows machine.
7. In Mate2 phone, go to settings, storage, and un-mount your current SDCard#1, after it is unmounted, take out the sdcard#1 and put it to a save place. Do not mess the two sdcards!!
8. Put in the sdcard#2 to the phone, and reboot to TWRP.
9. Install the two zip you download in step 5 from sdcard#2. Reboot.
How to go back to your primary OS:
a. Put in sdcard#1 to the phone, boot into TWRP, restore your /boot partition from the backup you took in above step 1. then reboot.
How to switch to the 2nd OS on the sdcard again:
a. Put in sdcard#2 to the phone, boot into TWRP, flash the "MT2L03_xxx_BootOnly.zip" you downloaded in step 5.
Files to download:
PartitionWizard in above step 2:
http://tinyurl.com/q62m68x
location: under Lollipop/SD_Partition_Tools
FileName: pwfree91.exe
This tools is mentioned in XDA wiki: http://forum.xda-developers.com/wiki/SD_card_partitioning
You can use any tool you know to do the re-partition, above tools is what I used and it works.
Customized flashable in zip in above step 5:
http://tinyurl.com/q62m68x
location: under Lollipop/OS_on_SDCards
FileName:
If you want install B309 as 2nd OS, please download "MT2L03_B309_DBoot_BootOnly.zip" and "MT2L03_B309_DBoot_SystemWithRoot.zip"
If you want install CM12 as 2nd OS, please download "MT2L03_CM12_0820_DBoot_BootOnly.zip" and "MT2L03_CM12_0820_DBoot_SystemWithRoot.zip". (Please note the GApp is already included in the zip)
Attached two screenshot of the partition tool, one for 32GB, one for 64GB. Please note though the pic showing in GB, but when config the size, please use MB to make sure the partition size is accurate and big enough.
//reserved
I am not sure how many people is interested in dual boot, so for now, I have pre-built B309 and CM12 only.
In order to build a customize ROM for installing in SDCard, as detailed in SHM original post, two steps are required:
1) For Mate2, after split the original boot image, and unpack the ramdisk, only need following cmd to update the fstab:
cd ramdisk
sed -i 's/platform\/msm_sdcc.1\/by-name\/system/mmcblk1p2/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/userdata/mmcblk1p3/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/cache/mmcblk1p4/g' fstab.qcom
Then repack it back to boot2.img. Please note the un/repack boot image tool need support DTB section.
2) Then in the updater script of /META-INF/com/google/android/updater-script, install system.img to /dev/block/mmcblk1p2, and still install the new boot2.img to /dev/block/mmcblk0p18.
@SHM, Unfortunately, many tools mentioned in original post, the Aparted tool, and the android binary mkbootimg etc all have problem running under Lollipop, so for now, I am doing all the ROM modification under linux.
Lol. You just had to do it. Lol awesome work. And you picked up on that fast. Thanks Xordos.
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
MikeyLee said:
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
Click to expand...
Click to collapse
I think if huawei mention 64gb probably because they didn't have 128gb to test when they release the phone. 128gb has nothing special compare with 64gb card. But I could be wrong since I don't have 128gb.
For general use, no need to partition 128gb card unless you want to do something like this thread.
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
SHM said:
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
xordos said:
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
Click to expand...
Click to collapse
Yea, it's pretty nice. You can even modify the TWRP recovery for use with making backups and restoring to each Rom specific to their partition. Look at TWRP Unified and check out it's script inside the ramdisk. Modify the script to check some stuff and tell it which fstab to use . This way when you jump back and forth between roms just by the boot.img you flash TWRP will automatically recognize the change upon it booting up and target the partitions properly when you make a backup/restore. Put some thought into all of this and I am sure you could take this thread a bit further.
There are projects out there that are designed for multibooting on android devices but you would need to port one of them.
Sent from my C525c using Tapatalk
Just an update that the AParted app works for Lollipop now. Tested it out on my external sd tonight by resizing my fat partition without losing any of my contents and adding additional partitions with multiple filesystem's such as f2fs and ext4. Quick and effective .
Sent from my Ascend Mate 2 using Tapatalk
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Can't waiting.
MT2-User said:
Can't waiting.
Click to expand...
Click to collapse
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
You run all three (or four including stock one)?
MT2-User said:
You run all three (or four including stock one)?
Click to expand...
Click to collapse
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Could they or some of them share Data?
MT2-User said:
Could they or some of them share Data?
Click to expand...
Click to collapse
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
oh ic
MT2-User said:
oh ic
Click to expand...
Click to collapse
The app implements this feature but I'm working it out if that makes you feel better lol.
Sent from my Ascend Mate 2 using Tapatalk
Damn nice work SHM.. Congrats. And thanks!
Moody66 said:
Damn nice work SHM.. Congrats. And thanks!
Click to expand...
Click to collapse
I have it working %100 now. Its 3:35 am where I am at so time for bed. Sharing apps works as well between roms.
Sent from my Ascend Mate 2 using Tapatalk

how to make new persist partition

I think i deleted my persist partition, which contains camera and sensors. I tried to copy the content via Windows but that didn't work. Can someone please tell me what to command or which tool could help me? I am new to unix, and sorry for bad english...
like this https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
or this https://www.quora.com/How-do-I-re-create-persist-partition-in-Android
no one can help?
There is in fact a way you can solve your problem
First, do you have access to your recovery? And if yes, is it the stock recovery or TWRP?

Some Help please... updated...

Hi!
I noticed that all change i made in system or vendor build.prop are ignored, or in some other xml files, even if i made a factory reset!
I try to add camera2 API and doesn´t work as example, APN changes to, etc...
The files i add, Change after boot still like stock but if i mount it on twrp it shows the changes i made!
Why?!
After some research i think there is no way to tweak system or vendor.
In some way i think vendor and system are writed in data when is flashed and stay in encriped data partition and when it boot only read data.
I read in some where that images only are use for fast update like dual images something problably the tweak image is not the one in use...
https://source.android.com/devices/tech/ota/ab/
Only customs ROMs will work maube because it have their own boot images and works in a diferent way.
I think it is the end of stock mods... :\
Thanks
Hello i had the same problem in android 10 miui 11.0.3 // you will need to reinstall your stock rom from https://xiaomifirmwareupdater.com/miui/platina/ fastboot rom using mi flash tool
After flash done flash twrp / magisc / install root explorer.
After that you should be able to edit again these files.
Or you can use twrp file manager to edit that .xml files // find a recovery that have the ability to edit those files.

Categories

Resources