[Q] TWRP Restored Successfully On /Data(f2fs) But Device Won't Boot. - Nexus 7 (2013) Q&A

Hi guys,
I am getting interested in these ROM flashing things recently, so I backed up /System /Data /Boot by TWRP after I installed all apps I want.
Just today, I tried to restore from one of my backups but couldn't get it work. CM12 just stuck on the boot animation screen forever.
The backup & restore processes were all perfect without any error, the MD5 also matched.
Here are some basic facts I made:
1. I wiped /System /Data /Cache /D-Cache before restoring.
2. I wiped /Cache /D-Cache after restoring.
3. Reflasing kernel -> NO change
4. Reflashing /System /GApps -> NO change
5. Fix Permission ->NO change
6. Wipe /Data = CAN boot
7. Restoring from another backup -> NO change
So clearly there is something wrong with /Data.
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
[Spec]
Nexus 7 2013 WIFI(flo)
TWRP 2.8.6
Kernel Glitch for Flo/Deb - r320
(No overlock, No additional drivers)
CM12 Nightly 20150405
gapps itvends.com/gapps/gapps-lp-20141212-signed.zip
/Data /Cache=f2fs
/System = ext4

akipapa said:
Hi guys,
I am getting interested in these ROM flashing things recently, so I backed up /System /Data /Boot by TWRP after I installed all apps I want.
Just today, I tried to restore from one of my backups but couldn't get it work. CM12 just stuck on the boot animation screen forever.
The backup & restore processes were all perfect without any error, the MD5 also matched.
Here are some basic facts I made:
1. I wiped /System /Data /Cache /D-Cache before restoring.
2. I wiped /Cache /D-Cache after restoring.
3. Reflasing kernel -> NO change
4. Reflashing /System /GApps -> NO change
5. Fix Permission ->NO change
6 Wipe /Data = CAN boot
So clearly there is something wrong with /Data.
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
[Spec]
Nexus 7 2013 WIFI(flo)
TWRP 2.8.6
Kernel Glitch for Flo/Deb - r320
(No overlock, No additional drivers)
CM12 Nightly 20150405
gapps itvends.com/gapps/gapps-lp-20141212-signed.zip
/Data /Cache=f2fs
/System = ext4
Click to expand...
Click to collapse
Without restoring data, it boots up properly?

Thanks for your reply.
I didn't try that, but I tried to wipe /data(not format) after restoring, and it booted fine.

akipapa said:
Thanks for your reply.
I didn't try that, but I tried to wipe /data(not format) after restoring, and it booted fine.
Click to expand...
Click to collapse
Your wlcm... And u can always press that thanks button if I helped...

akipapa said:
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
Click to expand...
Click to collapse
I see that you changed your file system to f2fs.
Did you flash a modified TWRP to support the new file system after changing it?
Sent from my Canvas Turbo using Tapatalk ^~^

User17745 said:
I see that you changed your file system to f2fs.
Did you flash a modified TWRP to support the new file system after changing it?
Sent from my Canvas Turbo using Tapatalk ^~^
Click to expand...
Click to collapse
I thought twrp2.8.6 supports f2fs because I could format f2fs and browse f2fs /data with its file manager.
Does it need further modifications?

akipapa said:
I thought twrp2.8.6 supports f2fs because I could format f2fs and browse f2fs /data with its file manager.
Does it need further modifications?
Click to expand...
Click to collapse
I looked up on the internet and it seems that it does support f2fs.
What about the kernel, does your kernel support it?
I guess if you were using the same kernel earlier with f2fs then kernel should also not be the problem here.
Maybe it's just a faulty backup.
I don't know much about f2fs myself.
Maybe you should contact someone who does.
Sent from my Canvas Turbo using Tapatalk ^~^

User17745 said:
I looked up on the internet and it seems that it does support f2fs.
What about the kernel, does your kernel support it?
I guess if you were using the same kernel earlier with f2fs then kernel should also not be the problem here.
Maybe it's just a faulty backup.
I don't know much about f2fs myself.
Maybe you should contact someone who does.
Sent from my Canvas Turbo using Tapatalk ^~^
Click to expand...
Click to collapse
I'm sure this is not about kernel, because I tried restore /boot and reflash the kernel.
Besides the kernel that I use works fine with f2fs.
I also tried to restore another backup with no luck, maybe they both were faulty...

akipapa said:
I'm sure this is not about kernel, because I tried restore /boot and reflash the kernel.
Besides the kernel that I use works fine with f2fs.
I also tried to restore another backup with no luck, maybe they both were faulty...
Click to expand...
Click to collapse
You mean 2 backups with faulty data partition?
That's highly unlikely to happen.
When you took those backups, did TWRP showed any error?
Sent from my Canvas Turbo using Tapatalk ^~^

akipapa said:
Hi guys,
I am getting interested in these ROM flashing things recently, so I backed up /System /Data /Boot by TWRP after I installed all apps I want.
Just today, I tried to restore from one of my backups but couldn't get it work. CM12 just stuck on the boot animation screen forever.
The backup & restore processes were all perfect without any error, the MD5 also matched.
Here are some basic facts I made:
1. I wiped /System /Data /Cache /D-Cache before restoring.
2. I wiped /Cache /D-Cache after restoring.
3. Reflasing kernel -> NO change
4. Reflashing /System /GApps -> NO change
5. Fix Permission ->NO change
6. Wipe /Data = CAN boot
7. Restoring from another backup -> NO change
So clearly there is something wrong with /Data.
I'm thinking the f2fs /data just can' be restored by TWRP? but I couldn't find such information on the web.
Can anyone confirm this?
Thanks!
[Spec]
Nexus 7 2013 WIFI(flo)
TWRP 2.8.6
Kernel Glitch for Flo/Deb - r320
(No overlock, No additional drivers)
CM12 Nightly 20150405
gapps itvends.com/gapps/gapps-lp-20141212-signed.zip
/Data /Cache=f2fs
/System = ext4
Click to expand...
Click to collapse
I read that the last CM nightlies got some sort of new compression implemented and that's why there's problems with restoring data. You'll have to wait for the TWRP creator to repair it

matcho13579 said:
I read that the last CM nightlies got some sort of new compression implemented and that's why there's problems with restoring data. You'll have to wait for the TWRP creator to repair it
Click to expand...
Click to collapse
That explains everything, thanks for the information.

akipapa said:
That explains everything, thanks for the information.
Click to expand...
Click to collapse
I'm glad I helped

same issue here
falcon, cm12.1 20/04 , twrp

Related

[Q&A] [REF] LVM Partition Remapping

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

[GUIDE] Convert to f2fs

All,
Since there was no clear directions on how to convert to f2fs, I decided to make a quick guide.
This *SHOULD* be device agnostic, however, I wrote it using my T-Mobile Note 3 running LeanKernel 3.12.3.
I'm not responsible if you screw up your data/device. Do this at your own risk.
1) Make sure you're on a kernel that supports f2fs. STOCK KERNELS WILL NOT WORK!
2) Boot into TWRP (at least version 2.8.1.0)
3) Make a backup to either external_sd or an OTG USB device. **THIS STEP IS REQUIRED**
4) After the backup is complete, go back to the TWRP main menu and select wipe
5) Select Advanced Wipe
6) Select the desired partition (cache OR data) and click FS OPTIONS ** DO NOT TRY TO CONVERT ANY OTHER PARTITIONS THAN CACHE AND/OR DATA UNLESS YOUR KERNEL SUPPORTS IT**
NOTE: YOU MUST DO THESE ONE AT A TIME!
7) check f2fs and then wipe
8) Ensure when finished it says current partition type f2fs
9) Repeat steps 5-7 for each partition you are convert ** DO NOT TRY TO CONVERT ANY OTHER PARTITIONS THAN CACHE AND/OR DATA UNLESS YOUR KERNEL SUPPORTS IT**
10) Go back to the TWRP Menu and select Restore
11) Select the backup you just made, and select only the partitions you are converting and restore (ignore warnings about ext4; these are normal)
12) Once restore has completed, go back to TWRP Menu and reboot into system.
13) Profit.
I know there are other kernels that support it, but my personal preference is leanKernel 3.12.3. You'll find it here: http://forum.xda-developers.com/showthread.php?t=2488233 thanks to @Imoseyon
If you need TWRP, you'll find it here: http://forum.xda-developers.com/showthread.php?t=2467001 thanks to @bigbiff
Enjoy, and again, don't blame me if you mess up your device/lose your data/etc.
What is the advantage and disadvantage of doing this procedure? Is compulsion kernel compatible?
Sent from my SM-N900T using xda premium
derride8 said:
What is the advantage and disadvantage of doing this procedure? Is compulsion kernel compatible?
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
This post sums it up pretty well.
As for compulsion, you'll want to check that kernels thread and/or the dev to find out.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
Do apps take up twice as much space on f2fs? That's the only difference I can see so far after the conversion.
toastido, Thanks for the guide. I followed the directions, am on lean kernel 3.13 which has f2fs support. When I restored, I noticed that system was reformatted back to ext4, while I got the warning on the cache and data partitions. Did I miss a step or is there a way to prevent the reformat?
rmarinella said:
toastido, Thanks for the guide. I followed the directions, am on lean kernel 3.13 which has f2fs support. When I restored, I noticed that system was reformatted back to ext4, while I got the warning on the cache and data partitions. Did I miss a step or is there a way to prevent the reformat?
Click to expand...
Click to collapse
Yes, go into the settings for twrp and look for the option to use rm -rf instead of formatting during wipe. Make sure that's selected.
Sent from my leanKernel 3.13 powered stock 4.4.2 (NF9) SM-N900T
toastido said:
Yes, go into the settings for twrp and look for the option to use rm -rf instead of formatting during wipe. Make sure that's selected.
Sent from my leanKernel 3.13 powered stock 4.4.2 (NF9) SM-N900T
Click to expand...
Click to collapse
That was it, Thanks!
Thanks @toastido
I imagine dp/lk will be the same
I get an error when changing the file system from ext4 to f2fs using TWRP 2.8.7.0.
It looks like this:
E:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p25 process ended with ERROR=1
E: Unable to wipe /data
E: Unknown MTP message type: 1
E: Error changing file system
I tried using TWRP 2.8.5.0 with the same result. I also tried to format data. Same result.
Gotta use 2.8.4.0 as that was the last version I was able to format data without error. Kevp75, love your rom as my daily for my note 3 but cannot use your kernel when I try this method but lean kernel 6.2/6.3 works fine.
prican25 said:
Gotta use 2.8.4.0 as that was the last version I was able to format data without error. Kevp75, love your rom as my daily for my note 3 but cannot use your kernel when I try this method but lean kernel 6.2/6.3 works fine.
Click to expand...
Click to collapse
lean works with all 3 partitions?
kevp75 said:
lean works with all 3 partitions?
Click to expand...
Click to collapse
Just Data and Cache worked, tried with system but just get loops.
prican25 said:
Just Data and Cache worked, tried with system but just get loops.
Click to expand...
Click to collapse
Right on!
System not really needed anyways as it's read-only, but the testing I've done had shown a significant boost on read
Thanks bud!
SUCCESS
Thanks for the guide. I was attempting this week following a different guide which was very similar. I have a Tmobile Note 3 and was unable to achieve this with TWRP 2.8.5 and up as those directions said to use 2.8.1.0 and up.
This time I used 2.8.1.0, the latest Lean kernel and DomPop v5. I converted Cache, Data and System. Upon Reboot it would not boot. I suspect this could be the current ROM or TWRP version I used which is just an assumption. I have not thoroughly investigated. I am going to create a new Nand, convert /System and then test the latest Dominion S6 port ROM among a few other 5.1.1 ROMs.
Note: I am not affiliated with any ROM I mentioned in this post.
Thanks again for the Guide. So far the difference is very noticeable with /Data and /Cache converted.
kevp75 said:
Right on!
System not really needed anyways as it's read-only, but the testing I've done had shown a significant boost on read
Thanks bud!
Click to expand...
Click to collapse
Have successfully get system to stick on f2fs... I have tried all but still goes back to ext4
austino pele said:
Have successfully get system to stick on f2fs... I have tried all but still goes back to ext4
Click to expand...
Click to collapse
It doesnt "mysteriously" just go back to ext4.
Something you are doing or flashing is formatting it back
kevp75 said:
It doesnt "mysteriously" just go back to ext4.
Something you are doing or flashing is formatting it back
Click to expand...
Click to collapse
Alright thanks
austino pele said:
Alright thanks
Click to expand...
Click to collapse
Check in the zip you are flashing.
You should be able to mod the updater-script
Look for the mount lines... (if it's not a CM/AOSP rom/mod)
You can change them to along these lines, and it should keep the f2fs
Code:
run_program("/sbin/mount", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
run_program("/sbin/mount", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
run_program("/sbin/mount", "/dev/block/platform/msm_sdcc.1/by-name/cache", "/cache");
Obviously you'll need to change to your device, but so long as you have Busybox installed, this will mount as filesystem independant
good luck mate

[Tutorial] how to format data & cache from ext4 to f2fs (cm12.1)

Maybe there is someone who do not know how to format the data and cache partition to f2fs (cm12.1 only), so I create this thread. Hope this tutorial can help.
The first step, copy the file mkfs.f2fs from /sbin to /external-sd (recommended). You can use file manager like root Explorer for example.
The second step, reboot the device into recovery mode(twrp recovery), copy back the files mkfs.f2fs from /external-sd into the /sbin
Step three, in the recovery mode, select wipe> advanced wipe> checklist cache> fs option > change fs> and click f2fs and Swipe for change. (if you don't see f2fs buttons, you must have a custom theme for twrp, or reload your themes to make f2fs button is visible. @vbvn thank's for your tips bro).
Repeat the same steps for the data partition.
And yeah,,, now you have data and cache partition in the f2fs formats...
Don't forget to backup Internal sd to safe your data (like a photos or mp3 for example).
For more detailed step, you can ask Google for it.
Greetings.
Sorry for my bad English
Screenshot
Thanks, that worked. I got the option for F2FS immediately after copying the file, though I have to copy it every time I have to format the partition else it says binary not found.
Good tip op. Also one can do a nandroid on data. Once cache and data has been converted you can restore data and reboot.
Sent from my HM 1SW using Tapatalk
What r the benefits of f2fs file system?
Sent from my HM 1SW using Tapatalk
kuldeepraj said:
What r the benefits of f2fs file system?
Sent from my HM 1SW using Tapatalk
Click to expand...
Click to collapse
Short version, it makes your phone fast.
does the stock MIUI or developer MIUI ROM support this type of formatting?
!Aman! said:
does the stock MIUI or developer MIUI ROM support this type of formatting?
Click to expand...
Click to collapse
Don't think so.
No it doesn't. And MUI will not read ext4 for you ext card either.
Sent from my HM 1S using Tapatalk
Can I use this method to format only system partition , will it be effective
Because I use dual boot and secondary ROM is miui v5
Thanks
Sent from my HM 1SW using xda Forum
as9333 said:
Can I use this method to format only system partition , will it be effective
Because I use dual boot and secondary ROM is miui v5
Thanks
Sent from my HM 1SW using xda Forum
Click to expand...
Click to collapse
1. Yes, you can use this method to format /system.
2. As /system is read only, and F2FS doesn't really improve read speed, it won't be effective.
3. I haven't tested this, but I have seen no reports or have no reasons to believe miui supports F2FS.
There goes your answers. For next time, please read the thread, and use this little thing called Google. I've heard it's kinda awesome.
Will it work ?????
If i format system to f2fs, will the rom work ??
TheMightyDeep said:
If i format system to f2fs, will the rom work ??
Click to expand...
Click to collapse
Any armani-dev based ROM should work just fine. Which is, almost every source based custom room out there.
the rom is working but it's waaay to slow, please how to revert back?
Berinjo said:
the rom is working but it's waaay to slow, please how to revert back?
Click to expand...
Click to collapse
Just the way you formatted to F2FS. Except this time, select EXT4.
Thnx for the guide @ippatt
Tip:-
no need to install additional theme. after copying file to sbin, just use "reload theme" option and F2FS option becomes visible...
OP may be updated with this tip.. thanks.
vbvn said:
Thnx for the guide @ippatt
Tip:-
no need to install additional theme. after copying file to sbin, just use "reload theme" option and F2FS option becomes visible...
OP may be updated with this tip.. thanks.
Click to expand...
Click to collapse
Thank's @vbvn,will be updated soon... :thumbup:
So I just have to do this for /cache and /data, and that will wipe data and cache, right ? Or will that wipe external / internal SD card as well?
I can just backup my data using titanium and do this procedure and just restore the data ?
Sent from my HM 1SW using Tapatalk
i think ijust had an bootloop after formating to f2fs, how to fix it??
Edit: just fixed, i had to pull out my baterry twice & now boot perfectly & FAST....)
Edit Again: seem to be if i flash exposed framework from twrp it ended up bootlop at reboot system, gues exposed hasn't fully support of f2fs or maybe there is something wrong with my phone, mcurrently my phone work fastly after flash CM12.1 R18+GAPPS+SuperSU 2.46
@ippatt
Nice tuts. F2FS menu comes out after I copied the mkfs using the TWRP Recovery's File Manager. The only problem is, why did I get the log "E:Unable to mount /cache" after formatting the /cache into F2FS? This happens with the /data too. "E:Unable to mount /data". What went wrong? :S

Problems after Updates and Wipes

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

[FLASHABLE_SCRIPT][UPDATED_ERRORS FIXED] Increase system space to 1.2/2GB [15/7/2017]

-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

Categories

Resources