I have converted my Nexus 7(grouper) to all f2fs and flashed slimlp. How do I convert it Ext4 file system and flash CM 12 Nightlies.?
I believe it's the same way you converted to F2FS, but this time select "EXT4" and not "F2FS".
I thought of doing that, but better get to know from someone who has done that before.
Flashing factory image restored to ext4.. That is safest method to do this.
After you convert everything back ext4, you can convert the data and cache back to f2fs because the nightlies in cm12 support this. You just need to leave the system partition as ext4 since this isn't supported yet.
Yup, I have seen those options, but didn't convert it to F2FS.I am giving my tab to my brother and he is not interested in flashing and all, but before giving I wanted to try baton(I have a one plus one), that's why I have flashed CM12.1. I was unable to get baton work.
Related
Hello folks,
Well, we all know that the stock Moto G filesystem is F2FS. But surprisingly, the Moto G GPe has a native Ext4 support. Since F2FS is supposed to have about a 30% better performance, I decided to try out the convert to F2FS feature in Philz recovery. So I formatted my system and cache to F2FS (since it didn't give me an option to wipe data and data/media to convert) and flashed a ROM. Currently, I seem to be facing a bootloop.
Anyway, has anyone else tried something like this? If yes, then please share your experience here.
Cheers.
It would be great if that would be possible,then you could jump from retail stock to GPe more easly. I have an XT1032 stock rom and i'd really like GPe,but my concerns are that would i be able to stock XT1032 again from GPe? You know,for F2FS and if i wanted to flash custom roms again to have better support. Any thoughts on my question? And look the first post,this is really interesting since if you'd want custom roms and you are on GPe,you wouldnt need to flash stock ROM to avoid bugs with custom roms and GPe
TWRP also include a format to f2fs <-> ext4 option:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
http://teamw.in/project/twrp2
Wipe > Advanced Wipe > <Select Partition> > Repair or Change File System > Change File System
I will test this out tomorrow when I have some time.
U need a kernel support somewhat like this in nexus 5 for f2fs
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
Stock kernel supports f2fs, GPE kernel does not. Development of a GPE kernel that supported f2fs would be ideal, assuming the GPE stock ROM also functions correctly with a f2fs formated USERDATA partition.
Has anyone even tried to flash boot.img from stock,and then converting in philz?
DeHuMaNiZeD said:
Has anyone even tried to flash boot.img from stock,and then converting in philz?
Click to expand...
Click to collapse
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
lost101 said:
/boot/ (kernel+ramdisk) does not need to be formatted. Flashing boot.img before or after wouldn't make any difference.
Click to expand...
Click to collapse
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Sent from my Moto G using XDA Premium 4 mobile app
Using TWRP to reformat 'data' from f2fs to ext4 wipes SDCARD and didn't even change the format. Right now it appears if you plan on moving between GPE and non-GPE and possibly back again, keep a full firmware image for both.
EDIT: Actually it appears TWRP did format correctly. But the GPE kernel can't get past the Bootloader. Perhaps there are other partition table differences.
After another try..the following works fine.
Migrate to GPE:
1) In TWRP, wipe, and format 'Data' from f2fs to ext4 (this will wipe internal storage.)
2) Sideload / adb push GPE ROM or flash ROM and Kernel via fastboot.
3) Reboot
Return to Motorola Stock:
1) In TWRP, wipe, and format 'Data' from ext4 to f2fs (this will wipe internal storage.)
2) Sideload / adb push Stock ROM or flash ROM and Kernel via fastboot.
3) Reboot
rudi_j7 said:
Well, I tried using TWRP, but it ended converting my phone back to dual sim.
Click to expand...
Click to collapse
I re-read your OP. The GPE Kernel expects the 'userdata' partition to be ext4. Unless someone develops a custom kernel to support it; you will never be able to run the GPE ROM with an f2fs 'userdata.'
Because you set all partitions to F2FS. Only need to change /data to F2FS. Leave system and cache ext4. You would need a ROM with a patched fstab and then a kernel supporting f2fs for system and cache to be in F2FS as well. Plus major benefit is in /data, not system and cache. I tested full F2FS on my N4 and it was more a pain with less gain. /data is all that should be F2FS.
Sent from my Moto G using Tapatalk
You can get it by deleting the partition / data and change it later by f2fs with TWRP fastboot erase boot partition and flash the boot.img from the stock 4.4.4 rom motorola everything from GPE and I have it so it shows more fluid
I converted a stable version of cyanogenmod into f2fs format. Everything was going well until I accidentally updated it and now it just sits on a bootloop. Anyone have any ideas how I can fix this without wiping. No i didnt get to create a nandroid.
lovesmyandroid said:
I converted a stable version of cyanogenmod into f2fs format. Everything was going well until I accidentally updated it and now it just sits on a bootloop. Anyone have any ideas how I can fix this without wiping. No i didnt get to create a nandroid.
Click to expand...
Click to collapse
The update you installed likely reformatted your system and cache partitions back to ext4. Try reformatting them and reflashing your ROM.
Alternatively, you could also try just flashing an f2fs-compatible kernel first to see if that gets it booting for you. That may be all you need if /data is still formatted as f2fs.
Did you used TWRP to convert to f2fs ?
Hi there,
I searched a lot on the subject, but I'm still not sure if/how this would work:
Can you install a factory image or an OTA update on a F2FS formated Nexus 7 2012?
Currently I have a lollipop custom ROM and kernel, with all F2FS and TWRP running on my Nexus 7. Could I install a custom F2FS kernel on my F2FS formated Nexus 7, like Phantom, and then only flash system.img and userdata.img from a lollipop factory image? Then, could I simply flash future OTA update zips?
Thanks!
It will just format it back to ext4. I've been trying to get f2fs to wepork on mine but I can't get the damn thing to recognize and side load. So I keep having to reflash official builds and it just rewrites everything to the stock build. I flashed the whole thing as f2fs wiped the device.
bill3508 said:
It will just format it back to ext4. I've been trying to get f2fs to wepork on mine but I can't get the damn thing to recognize and side load. So I keep having to reflash official builds and it just rewrites everything to the stock build. I flashed the whole thing as f2fs wiped the device.
Click to expand...
Click to collapse
Hi,
I got as far as (in short):
- Flash factory image
- Flash openrecovery TWRP
- Backup system and data (you have to make some space on system first, e.g. by moving some apps over to data)
- Format system, cache and data to F2FS in TWRP
- Restore system and data backup with "Use rm -rf instead of formatting" checked in TWRP settings
- Flash boot.img from Phantom kernel
I got this to work with LP 5.02, but for some reason with 5.1 the system restore failed so far... As for updates, I thought that, in the same way, you could just restore a system backup of a newer factory install over your actual system, but I haven't tried that yet.
Then again, this all is quite tedious. I'm not very advanced in img or ROM modification, but I'd like to know what one would have to modify in factory images or ROMS to make them F2FS compatible. For JB there are ressources out there, but I haven't found anything for LP so far... Anyone?
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Simply formating cache to f2fs makes already such a difference? Interesting, will give this a try. This would be a fairly easy solution to have a fast stock experience. I might try formating data to f2fs as well (and restoring backup), but leaving system on ext4. This way you may be able to simply flash the system image from future factory images to update your system, that would be a good enough solution for me.
First try updating to 5.1.
5.1 is running and performing so much better than on 5.0.2.
Even with ext4 filesystem and stock kernel.
Sent from my Nexus 7 using XDA Free mobile app
I already am on 5.1. Intitially it ran pretty good indeed, but I'm starting to get occasional lags again now. Not as bad as before, but still not as smooth as with JB when it was new... Like I said earlier, I haven't managed to do the TWRP f2fs backup and restore method for some reason with 5.1, but keeping system on ext4 might do the trick, so I'll try that and see if it improves upon stock 5.1...
rbeavers said:
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Click to expand...
Click to collapse
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
maksmtl said:
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
Click to expand...
Click to collapse
I'm using Franco Kernel(r82). It supports F2FS(formatted /cache and /data to F2FS) and it works flawlessly.
TWRP backups fail on stock 5.1 with f2fs/franco?
I downloaded the 5.1 factory image; installed it using the included batch file; installed franco r82 and formatted /cache and /data to f2fs. It seems to run reasonably well, but TWRP 2.8.5.1 and 2.8.6.0 both fail to make a backup, giving an unspecified error when backing up the data partition. Do you experience the same thing? Do you know of a workaround?
maksmtl said:
Hey rbeavers, what kernel did you flash? I tried with Phantom Kernel r1 and r2, and I get NFC force close at startup, which prevents from using the tablet...
Thanks.
Click to expand...
Click to collapse
Franco Kernel(r82) sorry so late.
Still working great! Only gripe 2 - 3 second delay on waking up.
rbeavers said:
All I did was on 5.1 flashed a F2FS kernel then in TWRP formated cache. It was like night and day.
Click to expand...
Click to collapse
rbeavers said:
Franco Kernel(r82) sorry so late.
Still working great! Only gripe 2 - 3 second delay on waking up.
Click to expand...
Click to collapse
Running really good so far with Franco Kernel and Cache and Data in f2fs. Thanks guys.
I also don't get that wake delay btw. Maybe wipe cache again?
@CCarson: I made a successful backup using TWRP 2.8.6.0. Maybe backup your sdcard and then re-format data. Also, don't know if this applies to you, but if you have the 16GB model, the 5.1 factory image formated mine to 8GB, so I had to re-format data once to get it back to 16GB and only then I changed it to f2fs.
Hi, so I recently stumbled upon the following thread: http://forum.xda-developers.com/showthread.php?t=2716306
Apparently it is possible to get F2FS working on the M8 GPE, however, the above rom is verizon only.
I wanted to see if anyone wants to join me in figuring out exactly how they managed to do so, by helping brainstorming and testing.
So far, there's already kernel and recovery support for F2FS for the regular M8, so our goal would be to figure out what changes need to be made rom-side.
Thanks for reading!
BlissPop works with F2FS. You just have to format /cache and /data to f2fs and flash the rom. Works out of the box.
As for /system, it stays with ext4.
Ok, so I finally found and settled on a kernel with f2fs support. The Simplicity 1.1 kernel for my stock, but modified 5.1.1 TW system. I've tried to follow the guides out there on how to convert the /data and /cache partitions to f2fs. I've followed them to the T and every time I reboot, it comes up saying the data partition is damaged and gives me the option to reset the phone, so I always end up rebooting to recovery and converting back and restoring from my nandroid backup and all is well. I hate being defeated and want to give this a shot, so if anyone has successfully done it or has any advice, it would be truly be appreciated! Thank you all for your time
Chuck
Which recovery you use to format to f2fs