Related
Can anyone help me out here?
I'm on the stable unofficial cm7.2 from alquez. Now the nightly builds are being released, but everytime I update by installing the zip via cwm my link2sd goes all nuts.
When I reboot after flash I get a mount warning, so I do a reboot.. then I try all sorts of things but all the liniks seem to be messed up and my internal memory goes full to capacity.
Does anyone know how to update without messing up my link2sd? I have to restore my nandroid everytime and so I don't get to use the nightlies.
I'm using an 8GB SD partitioned ext4 to 1GB.
Getting back up and running from a CM7 Nightly Update
1/ NANDROID BACKUP TO GET BACK TO WHERE YOU WERE IF YOU HAVE TO
2/ Titanium backup of all apps/data and system data
4/ Backup Titanium backup, ES File Explorer and LINK2SD apk's to SD card (Always have them there anyways!) using ES File Explorer
3/ Full wipe and install of new nightly and gapps
4/ Use CM7 File Explorer to reinstall TB, ES File, and LINK2SD
5/ Run Link2SD and relink SD Ext
6/ Turn on autolinking in settings
7/ Reboot
8/ Full titanium restore (files will auto relink to SD Ext with autolink on)
9/ Mass unlink the files you want on the Internal memory
10/ Redo your widgets on desktop
All your settings including WiFi, Google accounts, apps settings and data, System and Cyanogenmod settings will be retained.
Like I said. Pretty much all you have to redo is widgets.
*se-nsei. said:
Can anyone help me out here?
I'm on the stable unofficial cm7.2 from alquez. Now the nightly builds are being released, but everytime I update by installing the zip via cwm my link2sd goes all nuts.
When I reboot after flash I get a mount warning, so I do a reboot.. then I try all sorts of things but all the liniks seem to be messed up and my internal memory goes full to capacity.
Does anyone know how to update without messing up my link2sd? I have to restore my nandroid everytime and so I don't get to use the nightlies.
I'm using an 8GB SD partitioned ext4 to 1GB.
Click to expand...
Click to collapse
After flashing new build of CM7
go to link2sd, then recreate mount script choosing your correct partition (ext4 in this case)
fully reboot (not quick reboot)
all your app should now shown correctly
alexyie said:
After flashing new build of CM7
go to link2sd, then recreate mount script choosing your correct partition (ext4 in this case)
fully reboot (not quick reboot)
all your app should now shown correctly
Click to expand...
Click to collapse
Sometimes you can lose some but not all of your linked apps and they won't relink dalvik or libraries.
Last attempt at a normal update and remount script I lost 69 apps that refused to relink.
If you want to be safer than sorry...
d33ps1x said:
1/ NANDROID BACKUP TO GET BACK TO WHERE YOU WERE IF YOU HAVE TO
2/ Titanium backup of all apps/data and system data
4/ Backup Titanium backup, ES File Explorer and LINK2SD apk's to SD card (Always have them there anyways!) using ES File Explorer
3/ Full wipe and install of new nightly and gapps
4/ Use CM7 File Explorer to reinstall TB, ES File, and LINK2SD
5/ Run Link2SD and relink SD Ext
6/ Turn on autolinking in settings
7/ Reboot
8/ Full titanium restore (files will auto relink to SD Ext with autolink on)
9/ Mass unlink the files you want on the Internal memory
10/ Redo your widgets on desktop
All your settings including WiFi, Google accounts, apps settings and data, System and Cyanogenmod settings will be retained.
Like I said. Pretty much all you have to redo is widgets.
Click to expand...
Click to collapse
OMg. That's the same as installing any custom ROM, just keeping the settings (which I backup anyway). I can't do this nightly! I might as well just update when there are major major improvements such as kernal, etc.
Can't we like, use a patch or something that saves all the links when updating, or something like that?
*se-nsei. said:
OMg. That's the same as installing any custom ROM, just keeping the settings (which I backup anyway). I can't do this nightly! I might as well just update when there are major major improvements such as kernal, etc.
Can't we like, use a patch or something that saves all the links when updating, or something like that?
Click to expand...
Click to collapse
I'll work something out.
I too, always do full backup with Titanium, then full wipe, clear dalvik cash, install new CM build, then restore app using Titanium again.
My question is, why when I reinstall new build, gapps are always present, I don't have to install them again? I always do factory reset, clear cash partition and dalvik cash before update.
Wildfire S powered by CM 7.2
No.12 said:
I too, always do full backup with Titanium, then full wipe, clear dalvik cash, install new CM build, then restore app using Titanium again.
My question is, why when I reinstall new build, gapps are always present, I don't have to install them again? I always do factory reset, clear cash partition and dalvik cash before update.
Wildfire S powered by CM 7.2
Click to expand...
Click to collapse
They're present because you included them in the full titanium backup.
--
Cool if you can d33p
d33ps1x said:
I'll work something out.
Click to expand...
Click to collapse
that would be great, thanks in advance.
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Does it contain only data, and not the actual ROM?
How should I go about using such a backup when doing a restore? Should a ROM be installed first, followed by the restore? If so, must the ROM match the backup exactly -- that is, must it be the ROM under which the backup was performed in the first place?
kirkers said:
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Click to expand...
Click to collapse
That's a pretty close analogy. Only difference is I don't think it captures partitions...but I'm not sure about that. (It's not clear to me, for instance, if you did a nandroid of a phone with the EXT4 mod implemented and tried to install it on a phone without the EXT4 mod, exactly how that would play out.)
As an example, though, I took a nandroid of my stock phone immediately after I rooted it and got S-off. I then played around with various CM7, CM9, and JB ROMs for a weekend, but reloaded the stock nandroid Sunday night before going back to work on Monday. (I need a reliable phone for work.)
My phone was restored to exactly the way it was when I took the nandroid snapshot. I had to re-download a handful of app updates and email that had arrived since the time I took the nandroid to "catch up" to the present time, but that's all.
kirkers said:
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Does it contain only data, and not the actual ROM?
How should I go about using such a backup when doing a restore? Should a ROM be installed first, followed by the restore? If so, must the ROM match the backup exactly -- that is, must it be the ROM under which the backup was performed in the first place?
Click to expand...
Click to collapse
It is everything on your phone at the current time when you made a backup. Including your rom, apps, files, boot animation and e.t.c.
Sent from my EVO using Tapatalk 2
Impact of EXT4 partition on nandroid backup + restore?
sully9292 said:
It is everything on your phone at the current time when you made a backup. Including your rom, apps, files, boot animation and e.t.c.
Click to expand...
Click to collapse
MysticCobra said:
[The PC clone image is] a pretty close analogy. Only difference is I don't think it captures partitions...but I'm not sure about that. (It's not clear to me, for instance, if you did a nandroid of a phone with the EXT4 mod implemented and tried to install it on a phone without the EXT4 mod, exactly how that would play out.)
Click to expand...
Click to collapse
Thanks for the clarifications and the personal experience story. It helps calm my nerves. :fingers-crossed: Now it is clear that the nandroid is a full snapshot, close to being a clone image.
Can anyone address MysticCobra's point about the EXT4 partition?
As a rule, I have followed ROM Manager app's recommendation to partition the sdcard to allow apps to be stored on it. This is what the EXT4 partition is designed to do, as far as I understand such things.
If I format the sdcard with EXT4 (which in my experience wipes out all data on the card), and then restore a nandroid that came from an older EXT4-formatted sdcard of the same size or smaller than the new sdcard, would the nandroid restoration go smoothly?
What would happen if the new sdcard did NOT have an EXT4 partition?
Thanks in advance for further advice.
:good: Cheers!
kirkers said:
Thanks for the clarifications and the personal experience story. It helps calm my nerves. :fingers-crossed: Now it is clear that the nandroid is a full snapshot, close to being a clone image.
Can anyone address MysticCobra's point about the EXT4 partition?
As a rule, I have followed ROM Manager app's recommendation to partition the sdcard to allow apps to be stored on it. This is what the EXT4 partition is designed to do, as far as I understand such things.
If I format the sdcard with EXT4 (which in my experience wipes out all data on the card), and then restore a nandroid that came from an older EXT4-formatted sdcard of the same size or smaller than the new sdcard, would the nandroid restoration go smoothly?
What would happen if the new sdcard did NOT have an EXT4 partition?
Thanks in advance for further advice.
:good: Cheers!
Click to expand...
Click to collapse
Nandroid backup/restores don't touch the sdcard. They backup to the sdcard but the nandroid only handles /system, /data, /data/data, /cache, boot, and recovery.
The ext4 partition is not the same as the ext4 mod that MysticCobra mentioned. The mod converts /data, and /cache to ext4 and changes the ramdisk to mount them as ext4. The no data limit one also disables the mounting /data/data so the phone will share the apps and app data with a 750MB. Your app data is intact with the no data limit mod but a backup is still advised. No wipe updates don't touch the filesystem in /data or /cache but the mod may need to be flashed again for the ROM to boot correctly as the ramdisk is overridden on all updates. Technically with the normal data one you are good on later cm7 and ICS/JB ROMs as it's already ext4.
If you want to undo the mod the best thing is to wipe /data and /cache and reflash the ROM.
For further reading check the first link in the link below:
http://forum.xda-developers.com/showthread.php?t=1623038
So here's the thing: I made a TWRP backup of my 16GB nexus before I returned it yesterday (multitouch issues, dead pixels) but see now that people are reporting an OTA update that fixes the multitouch issue. I would rather not restore that backup since it is the JSS15J system, so is there a way I can get the data of at least a few apps and restore them individually somehow?
Thanks!
Titanium Backup can do that.
danvee said:
Titanium Backup can do that.
Click to expand...
Click to collapse
Ok, can it read the data in the TWRP folder? I have used TB a lot in the past but didn't think it might be able to use the TWRP data.
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
danvee said:
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
Click to expand...
Click to collapse
Ah, need the pro version. Hmm, thanks. I'll check it out.
Coronado is dead said:
Ah, need the pro version. Hmm, thanks. I'll check it out.
Click to expand...
Click to collapse
Use Nandroid Backup Manager. It's free.
It can restore apps and/or data, SMS messages, Call logs and more from your nandroid backup. It can also decompress the backup if it's compressed.
Advance Restore and just click restore data only on twrp
danvee said:
If it's not compressed (I never do), TiBu can do it perfectly.
In Titanium backup pro in it's menu is the option to 'extract from nandroid backup' .
Did it just last week, so I know the current version works.
Click to expand...
Click to collapse
thank you man thank you. i just had this http://forum.xda-developers.com/showpost.php?p=49548141&postcount=136 problem and your post is gonna help me i hope thanks. btw im on 4ext recovery
MrPhilo said:
Advance Restore and just click restore data only on twrp
Click to expand...
Click to collapse
Good day: Are you indicating that TWRP has an advanced restore feature?
Advance Restore and just click restore data only on twrp ????
I don't see any advanced menu in TWRP (Looks like all or nothing)?
Or, did you mean that Nandroid Manager has an advanced menu?
Regards
galearned said:
Are you indicating that TWRP has an advanced restore feature?
Advance Restore and just click restore data only on twrp ????
I don't see any advanced menu in TWRP (Looks like all or nothing)?
Click to expand...
Click to collapse
TWRP backups each partition separately, thus it can also restore any single partition so also /data
tetakpatalked from Nexus 7
tetakpatak said:
TWRP backups each partition separately, thus it can also restore any single partition so also /data
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
"so is there a way I can get the data of at least a few apps and restore them individually somehow?"
Pfeffernuss said:
"so is there a way I can get the data of at least a few apps and restore them individually somehow?"
Click to expand...
Click to collapse
Of course. TWRP has no advanced backup&restore features because it doesn't need them: you will be prompted before each backup&restore action about the partitions.
For data of just single apps use better Titanium Backup. It can extract them from your nandroid backups
tetakpatalked from N7100
MrPhilo said:
Advance Restore and just click restore data only on twrp
Click to expand...
Click to collapse
does it restore gapps too?
javigbox said:
does it restore gapps too?
Click to expand...
Click to collapse
I think some of the gapps data is flashed to system, so it won't be able to completely restore it but after flashing gapps, you should be able to extract google apps with data intact from TWRP backup
jassalmithu said:
I think some of the gapps data is flashed to system, so it won't be able to completely restore it but after flashing gapps, you should be able to extract google apps with data intact from TWRP backup
Click to expand...
Click to collapse
Exactly what I do.
marsmallow 6 will update apps + data from your google account. Not sure it's fully implemented yet but it's supposed to work. I've tried it yesterday with a Mm6.0.1 on nexus 7 2013 and many apps were already configured. Not all of them. Going from MM6 to MM6.0.1 might complicate it so maybe it's better to restore with google and do a little work by yourself, to make sure. I gave up on those restore apps. It also give you the opportunity to do a clean up
Coronado is dead said:
So here's the thing: I made a TWRP backup of my 16GB nexus before I returned it yesterday (multitouch issues, dead pixels) but see now that people are reporting an OTA update that fixes the multitouch issue. I would rather not restore that backup since it is the JSS15J system, so is there a way I can get the data of at least a few apps and restore them individually somehow?
Thanks!
Click to expand...
Click to collapse
I'm sure somebody is already aware of this;just sharing coz this awed me![emoji33]
You need to ..extract/restore individual data files from nandroid backup?
Restore data to an app when switching between ROMs or OS versions?
Well TWRP IS THE ONLY THING YOU NEED! And a PC of course.
Bless the Devs[emoji7][emoji28]
Forget Nan managers, tar.extractors & the insanely complex Bash terminal commands
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
2.Go to data/data and locate the data folder of the app you wish to extract; will be in the format 'com.app name'
3.Push 'Select folder' tab on the screen; it gives you option to COPY the file
4.Move up & paste the data/data file on your readable memmory: sd/ext.SD
And that's it!! Just connect to the PC & pull the file & there u have: your APP DATA FILE!
I was tired using zip extractors, changing file names & struggling with command prompts; then found this[emoji4]
Hope it helps[emoji106]
Sent from my GT-N5110 using Tapatalk
---------- Post added at 08:57 AM ---------- Previous post was at 08:24 AM ----------
DIGVIJAY24 said:
I'm sure somebody is already aware of this;just sharing coz this awed me![emoji33]
You need to ..extract/restore individual data files from nandroid backup?
Restore data to an app when switching between ROMs or OS versions?
Well TWRP IS THE ONLY THING YOU NEED! And a PC of course.
Bless the Devs[emoji7][emoji28]
Forget Nan managers, tar.extractors & the insanely complex Bash terminal commands
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
2.Go to data/data and locate the data folder of the app you wish to extract; will be in the format 'com.app name'
3.Push 'Select folder' tab on the screen; it gives you option to COPY the file
4.Move up & paste the data/data file on your readable memmory: sd/ext.SD
And that's it!! Just connect to the PC & pull the file & there u have: your APP DATA FILE!
I was tired using zip extractors, changing file names & struggling with command prompts; then found this[emoji4]
Hope it helps[emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
And believe me, I could repack the data into my new ROM just like that!
Not sure if this messes up with your system but I'm going great so far.
So you Upgraded to a higher OS and find some of your apps to be crashing on your new ROM & have a nandroid of your stock:
You are going to switch data files between stock & custom ROM!
1.Flash the Stock ROM & copy app data from the system files to readable memory, as mentioned above, just add a letter & Rename the copy(which again you can do with TWRP!) so that TWRP may not confuse with the new folder
2.Flash the new ROM, uninstall the app that crashes & install the compatible version from the store
3.Allow storage permission from settings; open the app & perform some action so that a storage directory is created,if not already, in the system storage
4.Boot to TWRP recovery in the new ROM , so now you have the data/data folder of the new app you just installed(which is empty) as well as the data/data folder from your stock ROM on your SD/Ext.SD
5. You know were this is going[emoji16] Delete the data/data folder on your running ROM & MOVE(again with TWRP only!) the one from SD ,after restoring its original name, to the data folder from were you just deleted the other.
6.Wipe Dalvik/caches & reboot
7. Other than receiving a pop up that there may be some trouble with your android system, on startup, everything works just fine for me & the App is fully restored!![emoji7]
Didn't even use a PC!!
Such a tool TWRP is[emoji7][emoji120][emoji120][emoji120]
Forgive me, but try this at your own risk, coz as a newbie Im completely unaware of the consequences
Hope this helps somebody[emoji4]
Sent from my GT-N5110 using Tapatalk
DIGVIJAY24 said:
1. Go to File manager on TWRP recovery, it can read the system data i.e. data/data/ file (while your other file managers can,only data files on SD or ext.SD)
Click to expand...
Click to collapse
I don't understand this step. I go to file manager, then navigate to /external_sd/TWRP/BACKUPS/... and there are files like data.f2fs.win009. Now what?
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
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