Related
-By following this you can can increase /system space from default 800MB to 1.2GB/2GB
-You can flash gapps on CM ROMs without insufficient space issue.
-You can flash regular MIUI ROMs too,without any issue.
Statutory warning
*Repartition can kill your phone forever if anything goes wrong,so proceed with caution (and make sure you have at least 30% battery)
*This process would format your internal sdcard,backup its contents
*I'm not responsible If your phone dies during this procedure under any circumstances beyond control
Prerequisites:
1)Redmi 1s partition script_system space 1.2GB.zip/2GB.zip
2)Parted
3)Twrp v3.0.2-1.zip
4)Download and copy all these files to external sdcard
Procedure:
1)Flash Twrp recovery(incase if aren't already using it).
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manager for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Redmi 1s partition script_system space 1.2GB.zip/2GB.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)Install your ROM(don't flash gapps now).
9)Back again to Twrp start screen select "Wipe"-->Advanced wipe-->select/mark "System"-->press "Repair or change file system(notice that size hasn't increased to 1.2GB/2GB)-->Resize file system.
10)Back(though size of partition appears unchanged, its actually increased to 1.2GB)-->Back>select/mark"System"-->Repair or change file system-->Notice size of partition increased.
10)Back to Twrp start screen and flash gapps,that's it.
Reset to default partition:
1)I am also giving link for flashabe script file "Reset to default partition.zip" for restoring default partition sizes.
2)Boot in to Twrp--->Advanced--->File manager--->Browse to the location of file "parted"--->Select "parted"--->Copy File--->/sbin.
3)Now using Twrp File manager browse /sbin--->parted--->select parted--->chmod 755.
4)You can also use "aroma file manager" instead of Twrp file manage for copying "parted" to "/sbin" and changing it's permissions to 755.
5)In Twrp flash "Reset to default partition.zip" and wait for the script to finish execution(recovery will reboot automatically once this process finishes).
6)In Twrp--->Wipe--->Advanced wipe--->Mark in "Dalvik/ART Cache"__"Cache"__"System"__"Data"__"Internal Storage"--->Swipe to wipe.
7)Reboot recovery.
8)that's it you are back to default partition.
PS:
1.Need for "Resizing System partition"(step 9) comes only with CM14.1(haven't tried other CM versions or other custom roms) no need to do that if you are flasing MIUI ROMs(i,e you can skip step 9 if you are flashing MIUI ROMs)
2.If you still need more System space or want to further modify partition table(only if you know what you are doing),you can edit "update-binary" file inside the zip as per your needs.
Credits:
1)forumber2_ Samsung Galaxy S III.
2)slst_for his valuable input.
3)owaisnaim & fefifofum Twrp for redmi 1s.
Downloads:
1)parted:https://drive.google.com/folderview?id=0B6_hhjS3nx4IU05yLVc2Mk9uOEk
2)Repartition script Redmi 1s_1.2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRkJFZzAtMjZEa2s
3)Repartition script Redmi 1s_2GB system space:https://drive.google.com/folderview?id=0B6_hhjS3nx4IRXlDZUU1cEJ3Smc
4)Reset to default partition:https://drive.google.com/folderview?id=0B6_hhjS3nx4IeGtXb0liazdLWVk
5)TWRP 3.0.2-1.zip:https://drive.google.com/folderview?id=0B6_hhjS3nx4IdzFHXzdfNXVCYm8
good work mate
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
no you just have to go to
wipe >mark on system>click repartition
go back you can see system size 1.2gb
after doing this can i flash latest twrp ?
vhick said:
Great tutorial! Have a some questions:
1. After successfully doing this, If I decided to full clean wipe system, data, cache, dalvik cache, internal storage, and format data, the size will be reset? Do I need to do all the steps again?
2. If I decided to go back in default partition size I just flash that to reset all the steps? Or there will be a steps to reset all I've done?
Thank you.
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
vinayak.ghimire said:
after doing this can i flash latest twrp ?
Click to expand...
Click to collapse
Ya you can.
and whats the size of userdata and cache partition ?
vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Based upon the scenario, the only concern is the system partition coz newer or update partition is too large. Cache partition is ok because it only use as a temp file partition. The userdata partition is large as internal storage because it shared as the same partition. That is the good thing at xiaomi phones, data partition is large as long as you have space in internal storage.
Sent from my HM 1SW using Tapatalk
vinayak.ghimire said:
and whats the size of userdata and cache partition ?
Click to expand...
Click to collapse
Install diskinfo app and check
Thanks for the script. It will help us a lot in now and in future also.
I know, i am asking too much. I bet we all are from developers but I will be very glad if you can provide me link of flashable file of TWRP and philz recovery 6.55.
Thanks Loads.
Anyone have checked this tutorial working ??
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Here is screenshot
apoorvpandey41 said:
I checked this tutorial working fine. Thanks for this awesome tip. Here the flash able zip of twrp
Click to expand...
Click to collapse
Thanks mate appreciated.
Thanks man works perfectly fine. Awesome tutorial.
Guys please help me:
Today morning I reparationed my Redmi 1s as the Op said. it went successful. after using for 5hours I've found an update from CM. So I updated using CM UPDATER APP. after reboot I've lost my Google play store and Google app (after updating to todays CM update using CM UPDATER APP). When I went to see the system partition size, it's size went back to the default 782mb (around 782mb, I don't remember exact size).
I checked whether it is disabled or what in apps. But I can't find there also. I tried Show system apps and reset app preferences, but nothing showed them.
I tried to get them back (play store and Google app) by resizing the partition to 1.2 gb (wipe>advanced wipe> Mark system>change or resize partition>back> checked system partition size whether 1.2gb or not>wipe cache and dalvik cache> reboot to system). But nothing worked.
So please help me in getting them back. Please exclude solution such as factory reset or flash gaggs again.
Is anybody else also facing the same issue or it's just me?:crying::crying::crying:
freeshared said:
1.You can do all the wiping as usual, size of partition wil stay as it is and won't get reset,but if you're flashing current version of cm14.1 again you need to resize "System" partition before flashing gapps.
2.You additionally need to change "System" partition too to F2FS and than to EXT4(like you do with "Data" partition),in case you're going back to default partition.
I forgot to mention point 2 in OP,I will now add this there
Click to expand...
Click to collapse
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
sharathe100111 said:
please give detailed instructions to get back to default partition as i am not anymore able to flash any rom on my device. Sometimes it strucks at patching system image unconditionally and sometimes shows error 7 in twrp. And not even being able flash using adb sideload. Please give detailed instructions to revert back to default partition
Click to expand...
Click to collapse
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
freeshared said:
1)Detailed instructions for returning back to default partitions are given in op under the sub header "PPS", nothing more to add to it,just follow as it is.
2)I myself havent faced any issues till now iam currently on cm14.1 6-12-2016 version
3)Saw your posts on cm41.1 thread too,so you're on latest twrp
but still facing error 7,If possible post a screenshot of error 7(coz it never happed for me)
4)coming to the issue at hand,could you able to mount cache,system and data partitions.In twrp go to wipe>>advanced wipe>>select "cache">>Repair/change filesystem and see if everything(regarding partition size)is ok there.
Then do same for system and data too and check how are those partitions,if possible post screenshots.
Post your relpy as soon as possible.
Click to expand...
Click to collapse
Thank you brother for your reply. Now i am on miui as i am not being able to go to CM14 anymore. But i can flash CM11. (it seems i can use only kitkat).
Here are the screenshots: for MOUNT, ADVANCED WIPE, CACHE, SYSTEM, DATA. And problem struck on patching system image unconditionally
When I try to restore stock backup it bootlop and didn't complete boot until I do hard reset
What should I do and which partitions should I restore
I am on 64bit twrp
ahmedAZ said:
When I try to restore stock backup it bootlop and didn't complete boot until I do hard reset
What should I do and which partitions should I restore
I am on 64bit twrp
Click to expand...
Click to collapse
System - rom
Data - app data & settings
Boot - kernel
It's best practice to restore a backup with the recovery version to which the backup was made
You may want to format data first (will delete everything on internal storage)
Wipe
Format data (option on right)
Restart to recovery then restore backup
If you don't restore data make sure you wipe it in advanced wipe
You must restore at least system & boot
Don't restore anything other than system data & boot unless you are doing it to solve a problem specific to other partitions
ahmedAZ said:
When I try to restore stock backup it bootlop and didn't complete boot until I do hard reset
What should I do and which partitions should I restore
I am on 64bit twrp
Click to expand...
Click to collapse
Flash no-verity-opt-encrypt-6.0 zip file (link here https://build.nethunter.com/android-tools/no-verity-opt-encrypt/) immediately (before rebooting into the system) after restoring your TWRP stock backup .
hi,
I bought a new redmi note 8 phone, unlocked the bootloader, installed TWRP .
Everything worked fine, until now. Now I want to backup my current modified stock ROM, but TWRP failes.
I got the problem very fast: TWRP can read all files and folders on the microSD car, but not in the internal storage folder.
Everything can be read by TWRP, except the sdcard folder.
Here he only shows strange names
something like:
Quote:
2h8P9lGY8I1A884LMsBjaA
2u+nb0LdBNopRSa5LehsvB
75aTrCvYkWG+R+lrcRz6WA
DcwYkwSKokq8Rm5lYc4YYC
Please help me
Reboot to recovery again and decrypt phone
eric00x said:
Reboot to recovery again and decrypt phone
Click to expand...
Click to collapse
How to decrypt permanent without losing data?
Ahmad5544 said:
How to decrypt permanent without losing data?
Click to expand...
Click to collapse
to decrypt phone :
Make sure you have a backup of your data copied in PC.
- In TWRP go to Wipe and select Format Data(don't go to advanced). Type yes and format data. [This process will format all your internal so make sure your data is backed up].
- Go back to TWRP home and Reboot > Recovery (Don't reboot system).
- Flash this zip.
- Reboot > System.
unfortunately there's no way to decrypt without losing data. Also if you're on a decrypted device then you have to format data everytime you flash any rom or update your current miui rom..I suggest using orangefox recovery to prevent this in future. Follow this guide for orangefox recovery.
Hi,
I was following this guide to finally update my redmi note 8 to MIUI global 11.0.12.00 (I don't remeber which version exactly I had before). I flashed the zip with TWRP and everything went fine, but I cannot boot now, I always go into TWRP when rebooting.
What could be causing this? I was rooted before, through magisk, and I did not reflash it. Would that help?
Any help appreciated
Edit: I installed magisk through TWRP, which was successful but I still wasn't able to boot. I then reflashed the OTA update and immediately installed magisk, which also did not work.
I read that flashing the stock recovery might help, but I don't know what to try next
Edit: I extracted boot.img from the OTA zip and ran fastboot boot boot.img, still got sent to TWRP
Edit: I flashed the stock recovery, now instead of booting into TWRP I boot into the MIUI recovery, which I suppose makes sense. I really wish there's something I can do without wiping my data.
I've reflashed twrp for now, and I'm gonna sleep for today. Hopefully I have some replies by the morning. Next I'm planning to flash the latest rom directly from en.miui.com (11.0.11.0)
Thanks
Also, in case I have to do a factory reset, which partitions can I then restore with TWRP (If I back them up now)? Most of all I really want to keep my app data. Am I forgetting anything else that's important?
try this...
1.flash dtbo.img
2.flash dm-verity
I hope it works
oindividuo said:
Hi
Click to expand...
Click to collapse
if you were decrypted you have to flash DFE again (Disable_Dm-Verity_ForceEncrypt_03.04.2020)
if not backup your data partition and reset sys config by deleting (data/system + data/user_de/0/com.android.settings + com.androidsystemui + cache + dalvik)
if it still dosn't work make a copy of the folder (data/data/your app name) wipe data and restore the data of your app after instaling it and hope it will work
Baim alif said:
try this...
1.flash dtbo.img
2.flash dm-verity
I hope it works
Click to expand...
Click to collapse
Just to clarify, dtbo.img is the one inside the OTA zip and dm-verity can be the Disable_Dm-Verity-09.02.2018.zip file found here? https://miui.blog/any-devices/dm-verity-opt-encrypt-force-encryption-disabler-xiaomi/
loopypalm said:
if you were decrypted you have to flash DFE again (Disable_Dm-Verity_ForceEncrypt_03.04.2020)
if not backup your data partition and reset sys config by deleting (data/system + data/user_de/0/com.android.settings + com.androidsystemui + cache + dalvik)
if it still dosn't work make a copy of the folder (data/data/your app name) wipe data and restore the data of your app after instaling it and hope it will work
Click to expand...
Click to collapse
I'm not sure if I was decrypted, I never flashed DFE before. So I should try the second set of instructions, right?
Also, I meant the data from all my apps, but hopefully I can just copy the full /data/data folder and restore it the same way
Baim alif said:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Click to expand...
Click to collapse
use this bro
oindividuo said:
I'm not sure if I was decrypted, I never flashed DFE before. So I should try the second set of instructions, right?
Also, I meant the data from all my apps, but hopefully I can just copy the full /data/data folder and restore it the same way
Click to expand...
Click to collapse
if you never flashed dfe before don't do it
you will have to format data (not wipe) and it will erase also internal storage
follow the 2nd set ...
make a bkp of 'data' partition (you can use 7zip to explore it) and restore app data but that's not garanteed
Baim alif said:
use this bro
Click to expand...
Click to collapse
So first I flash dtbo with fastboot (fastboot flash dtbo dtbo.img?), then boot into twrp, then flash dm-verity?
Thank you
good luck bro
Baim alif said:
good luck bro
Click to expand...
Click to collapse
Now I'm not being redirected to TWRP, but I'm in a bootloop :/
loopypalm said:
if you never flashed dfe before don't do it
you will have to format data (not wipe) and it will erase also internal storage
follow the 2nd set ...
make a bkp of 'data' partition (you can use 7zip to explore it) and restore app data but that's not garanteed
Click to expand...
Click to collapse
Alright I can boot now, I'm restoring the automatic backup from google drive, though I don't think it contains app data, right? Anyway, this is much more than I was expecting this morning. I will make a new full twrp backup when it finishes and then attempt to restore the old /data/data backup and hope for the best. I still need magisk too, but that's honestly not a priority rn
Thank you very much for your guidance
oindividuo said:
Alright I can boot now, I'm restoring the automatic backup from google drive, though I don't think it contains app data, right? Anyway, this is much more than I was expecting this morning. I will make a new full twrp backup when it finishes and then attempt to restore the old /data/data backup and hope for the best. I still need magisk too, but that's honestly not a priority rn
Thank you very much for your guidance
Click to expand...
Click to collapse
you can't browse data folder without root
you can do it with the recovery file manager but it will take too much time
orangefox file manager is better if you don't want root ...
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.
reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.
reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work
loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?
reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes