Hi,
my G3 and me have a small problem.
I wanted to update from official Cyanogenmod 12.1 to 13.0, backed up my data, etc.
First, there were tno Problems, but very fast battery drainage, and that my mSD card was now not "sdcard1" anymore but some numbers.
I tried fixing permissions in TWRP, had a bootloop. Updated TWRP (now 3.0.0 installed) and it worked somehow.
After one night it said process.acore quit unexpectedly. I had some crashes of the Google Play Services as well.
Then, it would boot, give me like 10 Seconds, and then jump to the boot screen of Cyanogenmod.
I tried to wipe data,system,dalvik. First there were problems with wiping dalvik, then there were problems with wiping system.
It says can't mount system: invalid argument. When looking around with twrp file explorer, the system folder is empty.
I would really appreciate your help!
You must check the partition type. Check if this as Ext4 or f2fs. In any case, try to repair the system of partitions from TWRP.
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Codagon said:
Okay, so:
Filesystem of /system is ext4
When trying to fix:
Repairing System using ef2fsck....
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with ERROR: 8
Unable to repair file system.
I assume it's because its ext4 and not f2fs?
btw I found something that may be important: when I try to wipe /cache, it takes forever.
Click to expand...
Click to collapse
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
cesarandres_8911 said:
Try to reinstall cyanogedmon 12.1 without wipes. Then, you enter again to the recovery and apply the wipes. I am not sure if for our model, cyanogedmon is compatible with the type of partitions f2fs and if is required a kernel with support for f2fs file system. You could try to changing the partitions (file system to f2fs), installing the rom and see if it starts but could cause a boot loop. Make a nandroid before making any changes.
Click to expand...
Click to collapse
Okay, i will try this tomorrow and then report back!
Thank you so far
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Codagon said:
Okay,
when trying to install the latest Snapshot of official CM, it just says ZIP File is corrupt. It said the same about an older build I still had on my PC.
When I try to flash the CM 13.0 build i had previously, TWRP just goes black and reboots (into recovery).
I also have to manually mount /system every time. If I try to mount /system again after dismounting it, it says 'failed to mount /system : Invalid Argument' .
This applies to all other partitions but the external SD Card.
When I try to change the file system to f2fs, it says OPeration successfull, but it didn't change anything, and the file system keeps being displayed as ext4.
Furthermore, i can't just 'Reboot Recovery' with TWRP- I have to take ot the Battery every time.
Click to expand...
Click to collapse
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
jokerpappu said:
Why dont you start from the beginning.flash lp kdz through lg up then try installing cm 13.it might work for you.
Click to expand...
Click to collapse
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Codagon said:
I didn't want to lose my files
But it seems this is the only way soon- TWRP is giving me Error 7 when trying to flash CM 13.0. ....
:crying:
Click to expand...
Click to collapse
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
cesarandres_8911 said:
Which is your recovery version? If your recovery version is 3.0, you could try performing a downgrade of your recovery. If the errors persist, make an clean installation of the rom from LG Flash Tool (KDZ).
Click to expand...
Click to collapse
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Codagon said:
My Version is indeed 3.0. I had 2.8 before. Should I downgrade even further?
What would you recommend?
Besides:
I tried saving my files with the Terminal and [cp * /data/data/media/ /external_sd/Backup -r] and others, but it keeps giving me Zero-Byte Files.
Is this due to the Recovery version too?
You guys really are a big help! Thanks!
Click to expand...
Click to collapse
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
cesarandres_8911 said:
I think that you try to save an empty folder. Use any backup applications to accomplish this. I have installed recovery twrp version 3 and I have no problem.
Click to expand...
Click to collapse
Ok but doing it woth cp * /sdcard/WhatsApp it keeps doing the same.
The only thing that matters to me now are my WhatsApp Images
I was able to grab the chatlogs but not more.
Sometimes it even copies all pictures (Like 8.000 files) but all of them are 0-Bytes.
I will try the downgrade tomorrow.
Thank you so far!
Were you able to resolve this? I have an identical issue. I was playing CoC on my LS990 with CM13 before it went black and now it always boots in to twrp recovery 3.0. The only thing that mounts is the external sd card.
I've tried the following and all fail:
adb push cm13 and then install from recovery
adb sideload cm13
lg flash tool via firmware upgrade, roms:ZV4, ZV6, ZV8
Is the internal sd damaged? Please help XDA gods. Thanks
Related
I have a problem, and I'm dealing with it since this saturday. I really need my phone this evening so I really want help. My phone has since saturday a bootloop with every rom. Today I found out that it could have something in common with a error in the recoveryscreen which says it can't mount /data. CWM and the stock recovery both have this problem. Can please anyone help me? I'm really confused, because I have tried everything.
//I've discovered that the problem is that the /data partition is crashed. Is is possible to recreate the internal partition table?
install a stock rom then re-install cwm 5.0.2.7
Msulviu said:
install a stock rom then re-install cwm 5.0.2.7
Click to expand...
Click to collapse
I have done that already a few times.
Try flashing an ext4 converter, or re dd'ing an empty RFS format partition into place.
Already done. When I try to use ext4formatter in CWM it doesn't give an error, but when I try to do the data reset I will get an error again because it can't mount (and unmount) /data.
//And how do you add a RFS partition on the phone? Or do you mean on the SD?
Factory reset?
Have you tried doing a factory reset with Kies?
be_born said:
Have you tried doing a factory reset with Kies?
Click to expand...
Click to collapse
Thank you for trying to help, but your answer is stupid. It's impossible to go to Kies without a (working) rom...
I think I just found something interesting to know. I tried again to install Cyanogenmod 7.2 (ported by Phiexz) and in the Aroma installer I looked at the System Info. Almost everything looks fine, but this is not good I think:
Data Size : -1MB
Free : -1MB
(/mnt/sdcard) : -1MB
Free : -1MB
Click to expand...
Click to collapse
Are those partitions crashed? And how do I resize or reformat them back?
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Or reflash back to the stock recovery and use that to format the partitions back to RFS.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Darkshado said:
Which ext4 converter did you use?
Phiexz's if I remember correctly, uses the formatting tools included in the recovery. Mine has its own, separate binaries.
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Good luck,
Darkshado
Click to expand...
Click to collapse
I did use Phiexz's first yes. But I can't install yours. And where do I have to use dd commands? :$
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Darkshado said:
What do you mean by "can't install mine"? Is there an error message or you're not sure how to do it?
If so, just apply it from the SD card like any other update.
The dd command has to be input through ADB shell while in recovery. So get ADB working if you haven't already.
Click to expand...
Click to collapse
I did know how to install a zip, but I tried 2 times and I think both were a bad download. Now I'm installing your Ext4 Converter.
// YOUR EXT4 CONVERTER WORKED!!! After a week without a phone it finally worked! Thank you so much!
Glad to hear that!
I had a similar problem of being unable to mount /system after installing a CM9 beta (can't remember which) and ended up solving it like that.
Hey guys i have a question relating to this dscussion. I have my gio running CM9 and i recently used BML5 to find my phone's unlock code. I have a nandroid backup of Rooted stock ROM, and when i tried to flash back to it, it said "Could format dev/block/stl13". I have the CWM 5.0.2.7 with RFS and EXT4 support, so it should work. What is the problem?
That's the thing; the exact behavior of those RFS+ext4 CWM builds when changing from one type to the other hasn't been very well documented.
I'm not sure they can format back to RFS properly.
You could always try that empty RFS partition set and attempt a restore afterwards.
What can i do if dd says, that it can't open '/dev/block/stl13': Invalid argument? I placed the data.rfs to the root directory of sdcard. Am I doing something wrong?
Can't mount /data
Hello, I have a bricked phone, and no idea why, and so far I'm unable to fix it. I've been waiting for an RMA so I can send it back to GSM Nation to evaluate and hopefully fix. My problem started when Samsung support told me to do a factory reset of my Samsung Galaxy S3, and it rebooted, then said it could not find or mount /data or anything therein. I have Not, repeat NOT, rooted my phone, it had the stock Android 4.3 OS and updates from T-mobile. The tech at the Samsung Experience Shop in the Best Buy store could not reflash it, when Kies tries to talk to the phone in Side Load mode it freezes or something, nothing happens. I downloaded ODIN 3 on Dad's win XP laptop, and in ODIN download mode the computer sees it as a new device with no driver to make it talk to it, and the drivers I've downloaded simply will not install. The installers die as soon as they run having done nothing. I am using my Samsung Chromebook to write this and have no Linux machine to work with. I am at a loss. Can you help me? Maybe I could re-install android using a microSD card?
I have the solution for data partition crash or any other partition
please do it with your responsibility but your phone is alreay bricked so it doesn't matter
hi every one i 've been through this problem for a long time and just yesterday hamdo lilah i discovered the solution it is by repartitioning your partitions with a pit file . i tried this method with samsung galaxy fit and it works even the pit file is for samsung .all you have to do is open odin included in the package then select pit file included then click start and there you go 'even if it doesn't show PASS ' after that just flash a stock rom ' or maybe any rom ' and that's it you are ready to go . i uploded the package on gulfup cause i have no account in mediafire enjoy if you face any problem just contact me or add a replay
gulfup.com/?rP8hfs
Q&A for [REF] LVM Partition Remapping
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [REF] LVM Partition Remapping. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
When I try flashing the setuplvm, it fails with error message "unable to mount /data." I am using TWRP 2.8.0.1 and have tried wiping the data. Is there anything I can do to fix this issue?
alpha_5 said:
When I try flashing the setuplvm, it fails with error message "unable to mount /data." I am using TWRP 2.8.0.1 and have tried wiping the data. Is there anything I can do to fix this issue?
Click to expand...
Click to collapse
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Entropy512 said:
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Click to expand...
Click to collapse
I have the same problem. I had the ZIP on external SD with omni nightly and gapps.
Same error and no LVM.
Try the twrp from omni thread. Flash setuplvm and than update to twrp 2.8.0.1.
jebulol said:
I have the same problem. I had the ZIP on external SD with omni nightly and gapps.
Same error and no LVM.
Click to expand...
Click to collapse
Also, the other question is: Did you reboot recovery after flashing setuplvm???
Entropy512 said:
Also, the other question is: Did you reboot recovery after flashing setuplvm???
Click to expand...
Click to collapse
Yup.
I flashed TWRP 2.8.0.1, tried to install setuplvm and got "unable to mount /data." Rebooted and flashed latest Omni and realized it didnt work.
Entropy512 said:
Did you flash setuplvm from the external SD per the instructions given elsewhere?
I plan on updating setuplvm sometime soon, but the issue you describe sounds like what happens if the ZIP resides on internal storage.
Click to expand...
Click to collapse
Yes, I am flashing from the external SD card. Here is what I see when I try it.
E: Could not mount /data and unable to find crypto footer.
Updating partition details...
E: Unable to mount '/data'
Full SELinux support is present.
Installing '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'...
Checking for MD5 file...
Skipping MD5 chck: no MD5 file found
Unmounting data partition
Extracting LVM tools
Unmounting sdcard partitions
Creating LVM physical volumes
Adding LVM physical volumes to volume group
Creating userdata logical volume
Rescanning and activationg LVM volumes
Formatting LVM volume
E: Error executing updater binary in zip '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'
Error flashing zip '/external_sd/setuplvm_find7_FULL_WIPE_09012014.zip'
Updating partition details...
E: Unable to mount '/data'
I will also add that if I go to "Mount" in TWRP I am unable to select "data." The phone boots up fine and seems to be working properly otherwise.
Hi,
This happened to my X9076 too about a week back and that was due to my mistake of installing the rom right away without rebooting the recovery first.
If you also missed that very crucial part, I'm pretty sure all you have to do is clear the data, run the reversal LVM zip, boot to recovery again, run the partition mapping, then boot recovery one more time and after that just install the rom + gapps as usual.
I however accidentally booted up the system directly after the failed install which got me the Android is encrypting splash screen for 1 minute or 2 then telling me it failed and booted. After that TWRP couldn't access the /DATA at all.
I eventually got around it by flashing stock recovery and colorOS. The newer releases didn't work though, I took the oldest ones from OPPOforums and that worked.
After that I could flash back to TWRP, run the partitioning as supposed to and install Omni.
i've been wanting to try out omni with lvm for a while, but is lvm complete?
i also read that there's some issues with twrp, i'm a bit confused, which twrp version do i use?
i'm currently running a rom with an unified partition
i just have to return to split layout then flash the setup lvm in latest twrp recovery?
thanks in advance
binaryfalcon said:
i've been wanting to try out omni with lvm for a while, but is lvm complete?
i also read that there's some issues with twrp, i'm a bit confused, which twrp version do i use?
i'm currently running a rom with an unified partition
i just have to return to split layout then flash the setup lvm in latest twrp recovery?
thanks in advance
Click to expand...
Click to collapse
There have been some odd issues with the following:
1) setuplvm does not play nice with newer TWRP. I have some guesses why... In a few places in the Omni thread I gave manual instructions for doing the conversion in an ADB shell, those will work
2) For some reason, the app "TWRP Manager" flashes a bogus version of TWRP that has issues
Other than those two issues, LVM is complete, I've been running it for two months now. I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Entropy512 said:
There have been some odd issues with the following:
1) setuplvm does not play nice with newer TWRP. I have some guesses why... In a few places in the Omni thread I gave manual instructions for doing the conversion in an ADB shell, those will work
2) For some reason, the app "TWRP Manager" flashes a bogus version of TWRP that has issues
Other than those two issues, LVM is complete, I've been running it for two months now. I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Click to expand...
Click to collapse
appreciate the response
what do I need flash?
which twrp version do I use?
It's just a compatible twrp then setuplvm then flash omni?
any help appreciated, can't wait to try it out
Entropy512 said:
I just need to figure out why TWRP 2.8.0.1 (especially when flashed via TWRP Manager) behaves oddly.
Click to expand...
Click to collapse
I downloaded TWRP from http://techerrata.com/browse/twrp2/find7 and flashed using fastboot. Still had issues.
jebulol said:
I downloaded TWRP from http://techerrata.com/browse/twrp2/find7 and flashed using fastboot. Still had issues.
Click to expand...
Click to collapse
That should work fine on a device that is already in the LVM configuration. It does have issues with setuplvm currently though.
Someone who had issues with setuplvm and TWRP 2.8.0.1 finally posted a recovery.log - For some reason, TWRP 2.8.0.1 is not unmounting the sdcard partition, which causes issues when setuplvm tries to convert that partition into an LVM PV.
From now on, anyone with issues with setuplvm (or other issues within recovery) needs to post /tmp/recovery.log - This can be obtained via ADB with:
Code:
adb pull /tmp/recovery.log
when you are in TWRP after you've tried (and failed) to do whatever you're trying to do
Why? This provides MUCH more information about what went wrong than just the basic screen results/console output such as what alpha_5 posted a few posts back.
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
---------- Post added at 03:47 PM ---------- Previous post was at 03:17 PM ----------
Wendigogo said:
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
Click to expand...
Click to collapse
I tried and it's written in TWRP recovery : factory reset doesn't wipe personal data (in /data/media).
AWESOME JOB !
Wendigogo said:
I'm not sure how this lvm implementation works ...
If I wipe /data in a twrp lvm compliant recovery, what will happen? It will wipe only /data stuff in lvm pool or the whole "partition" (including internal sdcard)?
Enjoy!
EDIT : I want to make a "factory reset" but without erasing my personnal datas (photos etc.).
---------- Post added at 03:47 PM ---------- Previous post was at 03:17 PM ----------
I tried and it's written in TWRP recovery : factory reset doesn't wipe personal data (in /data/media).
AWESOME JOB !
Click to expand...
Click to collapse
Correct. It's the same way all Nexus devices since the GNex (and most other devices) are - a factory reset does an rm -r of everything outside of /data/media instead of formatting the whole partition.
Of course, it's a good idea to periodically back things up in case the filesystem gets hosed to the point of needing a format. (Extremely rare on ext4 these days, common for f2fs in my experience)
Entropy512 said:
Correct. It's the same way all Nexus devices since the GNex (and most other devices) are - a factory reset does an rm -r of everything outside of /data/media instead of formatting the whole partition.
Of course, it's a good idea to periodically back things up in case the filesystem gets hosed to the point of needing a format. (Extremely rare on ext4 these days, common for f2fs in my experience)
Click to expand...
Click to collapse
Yes, always following the 3 main rules when playing with my devices :
1- Make a backup
2- Make a backup
3- Make a backup
And as I do that oftenly my backups are never outdated.
Enjoy!
Setting up LVM on oppo find 7 from a custom rom?
Hello,
I am tired of my app space always out (I can't update apps now and have limited my apps to about 1/2 of what I normally would have).
From quite a ways back, I had installed Gummy, I think M4, right around when they stopped supporting the rom.
My question is how would I set up LVM from this point in time? I'm unsure how to revert back to any colorOS system (and I would prefer never to go back that way anyway, however I do see cos1.2 in a restore kernal section). I have TWRP 2.7.1.0 currently in use.
update: I see that twrp from the OS, can download the latest TWRP so I am currently DL and will try to install 2.8.7.1. If this successfully gets installed, can I flash the LVM program directly, then a 5.x or later D.U., Nameless, or OMNI rom afterwards?
Your help would be greatly appreciated as I have put this off for way too long however understand it's an amazing phone w/lots of hardware capability.
Update: downloading 2.8.7.1 from the app's interface didn't work well. I had to get back into flashify and install from local file version 2.8.5.0. When I get into bootup>TWRP, i have a split screen where the left side is scrolling slowly downwards. All functionality is normal just screen split flipping is annoying.
Hi.
Anyone give me working download link for "set up LVM" and "remove LVM" flashable zip please.
I can't download them from oppo forum.
Hi Entropy512, All,
I have installed succesfully LVM with the last OmniRoma Available but everytime I try to download something or take a picture with the camera, It says "For use camera, insert and SD Card". I checked the threat and I do not find any clue of how to solve this. Probably I miss something in the configuration process.
Any help?
Thanks in advance
-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
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
joloxx9joloxx9 said:
Hi guys have weird problem with my phone. Sometimes when I want to make nandroid I can see error 255 always on system partition . When I restore system partition I can do nandroid.
Next thing, when I want to delete any system app using titanium backup, after restart app is back again and im not getting free spacer in system partition. Also very often when I restore nandroid system doesn't want to boot, it just stuck on boot logo.
It is happening since last few weeks. What should I do to fix it?
Format all partitions then clean flash of rom?
Click to expand...
Click to collapse
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
That would work if you arent rooted with otg ...the you could image the system and fix it on a Linux box with fsck
Click to expand...
Click to collapse
Could you please tell me How can I fix IT?
joloxx9joloxx9 said:
Could you please tell me How can I fix IT?
Click to expand...
Click to collapse
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
The method you mentioned will work. Format everything and reload. I wish that recovery systems for Android supported fsck. Actually, if you have busybox installed, even under tmpfs, you might be able to get to a shell to run fsck. I can't try it now, but it worth a shot.
Click to expand...
Click to collapse
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
joloxx9joloxx9 said:
No Way to run fsck. I will try to format everything later then send files from PC and install fresh system on the phone.
Click to expand...
Click to collapse
for future reference, there is a "Repair filesystem" option in twrp. It says it runs e2fsck, which works for ext4. It won't hurt an f2fs filesystem, but I don't think it will repair it either. I'm seriously considering switching my /data to ext4 just so I have proper recovery tools.
My OP3T does have fsck.f2fs on the system, which means you can fix your data by opening a Terminal session from TWRP and then running :
Code:
fsck.f2fs /dev/block/dm-0
should fix your data corruption should you see this error again. For ext4, you use e2fsck rather than fsck.f2fs. This is also what you would use on /system (which is /dev/block/sde20 on my phone) should that ever be mounted read/write and get corrupted (pretty low chance even if you do mount it read/write as writes are low frequency and ext4 has a rock solid journal).
WARNING: Device numbers are for my OP3T and may be different on other devices or even on non-US devices.
Hey,
I'm new in this kind of stuff but need help as fast as possible. So I tried to root the phone but let me tell you something else. When I enter TWRT (boot into) and try to install the .zip file it shows weird folder names that I can't see on the computer. I have Win10 if this matters and Android 8.0 or 8.0.1. The folders are:
acct
boot
cache
config
cust
data
license
mnt
and it goes like that. The problem is that about 85 or 90% of these folders aren't visible on my computer when I plug in my phone... The System is mounted in TWRP and everything is mounted. I tried wiping all the data. I have unlocked bootloader. Also when I go to some of these folders I see REALLY strange folder names like: 671hnsuh1b%nqjus Or something like. I've found out that it's encrypted but I just want to root the phone and find the .zip file. Also can someone explain me these acct, boot, license, vendor, version and other folders that aren't visible on my PC? Please help. I'm so confused, not clue what's going on...
You need to use the format data option to decrypt the internal storage. Better use SD card or USB OTG to flash the root file. Anyway don't wipe the oeminfo or vendor partition in any case and take a backup of all partition beforehand.
kksnis said:
You need to use the format data option to decrypt the internal storage. Better use SD card or USB OTG to flash the root file. Anyway don't wipe the oeminfo or vendor partition in any case and take a backup of all partition beforehand.
Click to expand...
Click to collapse
Well, I already used this option. The format data option and it's still the same. Maybe the version of my twrp helps: 3.1.1-1
Aspect13 said:
Well, I already used this option. The format data option and it's still the same. Maybe the version of my twrp helps: 3.1.1-1
Click to expand...
Click to collapse
Strange. What is the android version?Did you had any lock screen set before formatting? Can you please share a screenshot or log during formatting, if you have any. Anyway you can use adb sideload to flash the .zip file.Cheers
kksnis said:
Strange. What is the android version?Did you had any lock screen set before formatting? Can you please share a screenshot or log during formatting, if you have any. Anyway you can use adb sideload to flash the .zip file.Cheers
Click to expand...
Click to collapse
My android version is 8.0 so it's oreo. I've also noticed that the 3.1.1-1 version of twrp is the only one from what I tried that I can install the newer versions gave me an error. I had lock screen and it was code not a fingerprint but I wasn't prompt for a code after booting into twrp. Adb sideload seems to fail all the time so I can't do it :/.
The logs from wiping data are:
Updating partition details...
..done
Full SELinux support is present.
MTP Enabled
Starting ADB Sideload feature...
Starting ADB Sideload feature... (And it failed now wipe logs.):
Fomatting Data using mkfs.f2fs...
Done.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
...done
So yea I'm so sad tbh with this... I'll try to install new twrp after the wipe if the wipe didn't help and will tell you if I get an error when I try to boot into NEW twrp.
EDIT: Ye still an error.
Maybe you have a link to the newest working twrp?
Nevermind got it. Downloaded the modded twrp by TEAM MT I guess from here: https://forum.xda-developers.com/honor-8-pro/development/wip-twrp-3-1-1-0-duk-t3625798 Works perfectly and SOLVED!