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
Related
Dear all,
I was on Quarx CM10 build 20121118, then just tried this http://forum.xda-developers.com/showthread.php?t=2080556 and managed to kill my phone. I think what happened was that the data partition was full and an empty services.jar was written back. But whatever I thought I am a lucky guy because I did a full backup in custom recovery just the night before.
So I went into custom recovery, did a factory reset, wiped all I could and selected restore system and data.
But all I get is "Error while restoring /system" And "error while restoring android secure".
I spent the whole day searching the forum, found something about formatting system/data to ext3, tried that with no change.
Any help would be greatly appreciated. Would be even greater if you could explain the steps understandable for an idiot like me.
Thanks in advance,
Matthias
mmbytes said:
Dear all,
I was on Quarx CM10 build 20121118, then just tried this http://forum.xda-developers.com/showthread.php?t=2080556 and managed to kill my phone. I think what happened was that the data partition was full and an empty services.jar was written back. But whatever I thought I am a lucky guy because I did a full backup in custom recovery just the night before.
So I went into custom recovery, did a factory reset, wiped all I could and selected restore system and data.
But all I get is "Error while restoring /system" And "error while restoring android secure".
I spent the whole day searching the forum, found something about formatting system/data to ext3, tried that with no change.
Any help would be greatly appreciated. Would be even greater if you could explain the steps understandable for an idiot like me.
Thanks in advance,
Matthias
Click to expand...
Click to collapse
You can't restore nandroid of CM10/9, i dont know why, but i also can't restore cyanogenmod nandroid backups, stock roms backups are restoring fine, but cm - still no luck. PS: your system is ext3, because we have locked boot. Data and other partitions restoring fine except cm backups.
mmbytes said:
Dear all,
I was on Quarx CM10 build 20121118, then just tried this http://forum.xda-developers.com/showthread.php?t=2080556 and managed to kill my phone. I think what happened was that the data partition was full and an empty services.jar was written back. But whatever I thought I am a lucky guy because I did a full backup in custom recovery just the night before.
So I went into custom recovery, did a factory reset, wiped all I could and selected restore system and data.
But all I get is "Error while restoring /system" And "error while restoring android secure".
I spent the whole day searching the forum, found something about formatting system/data to ext3, tried that with no change.
Any help would be greatly appreciated. Would be even greater if you could explain the steps understandable for an idiot like me.
Thanks in advance,
Matthias
Click to expand...
Click to collapse
That's the point formatting system & data to ext3, but make sure don't wip data & cache after rom installed without reboot , since you're still under CM10's bootmenu.
Hope this helps .
Sent from my GT-N7100 using xda app-developers app
donf6938 said:
That's the point formatting system & data to ext3, but make sure don't wip data & cache after rom installed without reboot , since you're still under CM10's bootmenu.
Hope this helps .
Click to expand...
Click to collapse
Sorry, no. I do not understand what you mean. Could you please describe the steps?
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 guys, hoping you can help me out. Noob, yup.
Nexus 7 2012 Wifi.
My Nexus was getting slow, so I successfully converted my system, data, and cache to F2FS with SlimKat.
In the process of this, I converted my Cache, System, and Data to F2FS.
The SlimKat F2FS rom was working fine. All was well.
Here's where I made a series of errors...
I decided to restore the Nexus back to factory settings/stock 4.4.4. I had some problems with my nandroid files, so I decided just to convert things back manually in TWRP. My thought process was to: A. convert Data and Cache back to ext4, B. Install factory rom from System, C. convert System back to ext4.
My thought process was apparently wrong.
Here's what I did:
1. I copied the 4.4.4 Factory Image (.tgz) to the sdcard (first mistake. I assumed the official download was a .zip but it was a .tgz).
2. In TWRP, i converted the Cache and System to ext4.
3. Tried to install stock 4.4.4 rom but couldn't install it because it was .tgz.
4. Not knowing what else to do, I converted the Data to ext4 as well. So in my eyes, everything was "put back" to ext4 like it was before. Since everything was "back to normal", I thought Nexus Root Toolkit could take me the rest of the way back to normal.
5. In Nexus Root Toolkit, I tried to "Flash Stock + Unroot", but it gave me errors (picture is attached)
6. Now I'm in bootloader. Trapped. I can't even get back into TWRP anymore (and I don't understand why).
Sorry for the noob trouble. Hopefully there is still hope for my Nexus.
Thanks in advance for any help.
In fastboot mode (i.e. Bootloader), use fastboot to flash the latest TWRP or a factory image
thunderdust said:
Hi guys, hoping you can help me out. Noob, yup.
Nexus 7 2012 Wifi.
My Nexus was getting slow, so I successfully converted my system, data, and cache to F2FS with SlimKat.
In the process of this, I converted my Cache, System, and Data to F2FS.
The SlimKat F2FS rom was working fine. All was well.
Here's where I made a series of errors...
I decided to restore the Nexus back to factory settings/stock 4.4.4. I had some problems with my nandroid files, so I decided just to convert things back manually in TWRP. My thought process was to: A. convert Data and Cache back to ext4, B. Install factory rom from System, C. convert System back to ext4.
My thought process was apparently wrong.
Here's what I did:
1. I copied the 4.4.4 Factory Image (.tgz) to the sdcard (first mistake. I assumed the official download was a .zip but it was a .tgz).
2. In TWRP, i converted the Cache and System to ext4.
3. Tried to install stock 4.4.4 rom but couldn't install it because it was .tgz.
4. Not knowing what else to do, I converted the Data to ext4 as well. So in my eyes, everything was "put back" to ext4 like it was before. Since everything was "back to normal", I thought Nexus Root Toolkit could take me the rest of the way back to normal.
5. In Nexus Root Toolkit, I tried to "Flash Stock + Unroot", but it gave me errors (picture is attached)
6. Now I'm in bootloader. Trapped. I can't even get back into TWRP anymore (and I don't understand why).
Sorry for the noob trouble. Hopefully there is still hope for my Nexus.
Thanks in advance for any help.
Click to expand...
Click to collapse
Instead of doing these whole procedure via .bat file plss try it manually yourself and install latest twrp and then format your system and other partitions with desired format and then flash manually system.img and other stuff manaually
Solved!
Hey guys, thanks for the help.
Here's what got me through it:
1. Learn how to fastboot, adb, etc. WITHOUT Nexus Root Toolkit so you understand what's going on.
2. Don't assume that any USB port or laptop will give you the same results. My attempts to flash the system with a custom rom failed time and time again. On the advice of other threads, I tried the same thing again via a different USB port, and voila it worked! Perhaps it was not a 2.0 port.
In summary, I needed to fastboot erase, then fastboot flash the partitions. And most of all, I had to try it on a different USB port if it failed unexpectedly.
Hope this helps somebody else!
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.
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.