yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Ramer:
I couldn't agree more. Life is so much easier with OTG. Also, (and only because I found this on Kickstarter awhile back) Meenova has a great OTG device about the size of a quarter. If you're like me and started accumulating microSD cards, it's a very handy way to put them to some use again.
[Nexus 7 Original Development] SkOrPn:
Haha, now you know that's a very very bad button... Yeah when you use the Factory Reset swipe, it does a full factory reset but does not touch user files. You really should get used to using that instead of the wipe menu because you will find it makes life much easier on you. Its all you need for a clean rom install. No more having to transfer files back onto the device. UNLESS your stupid like me and can't stop formatting from etx4 to f2fs and back again... jeez I must have formatted 6 times today trying to get the perfect setup.... I'm not going to sleep very well with a permanent image of TWRP stuck in my head.... ;)
[Nexus 7 Original Development] brizey:
I still like to wipe system myself to be sure... Every once and a while a dev leaves out the wipe from the script. And while I'm in there I just wipe data and cache while in at it which is the same as factory reset. Heck most of the time anymore I just use twrp manager or goo manager.
[Nexus 7 Original Development] fridlack:
Same problem here, followed OP instructions an I stuck on slimkat boot animation, any idea?

EDIT: i made the process again and it works, dunno why, but i enjoing slimkat with ALL-F2FS, thanks so much
[Nexus 7 Original Development] BelvedereWRX:
Apologies for the dumb question but I didn't see it mentioned in this thread or the ROM thread. After a reboot using this modified f2fs recovery (flashed via fastboot) I lose the red back arrow. Does this mean the flash isn't sticking, or is that normal?
[Nexus 7 Original Development] FReaKRaNT:
No red arrow = no modded recovery

Cheers, FReaKRaNT
[Nexus 7 Original Development] BelvedereWRX:
So it's not sticking. Any ideas as to why?
[Nexus 7 Original Development] adomol:
Do you have a theme applied?
[Nexus 7 Original Development] BelvedereWRX:
No themes at all.

I'd like to mention I was able to successfully get Omni f2fs up and running, but the modded recovery not sticking issue still lingers. It seems odd to me, it makes doing anything an inconvenience because it can't read the FS when not in F2FS. I assume that's the reason anyway.
[Nexus 7 Original Development] adomol:
How exactly are you installing twrp, can you detail the process? Might help with figuring out whats going on.
[Nexus 7 Original Development] SkOrPn:
This sentence makes no sense. How did you format F2FS if you don't have a modified recovery installed?

What do you mean by "it" ?

+1

I'm curious as well. If he can't get the modded recovery to flash how did he format partitions and flash the modded F2FS ROM?
[Nexus 7 Original Development] BelvedereWRX:
Using fastboot to install the f2fs modified image.

Boot into fastmode.

fastboot flash recovery modifiedf2fs.img

Restart into recovery

The first boot into modified recovery is successful, displaying the red back arrow. Attempts afterwards I'm back to the "normal" non-red arrow and I assume, non-modified recovery.

Sorry if it wasn't clear. I commented earlier that the modified recovery wasn't "sticking", I was able to boot into modified recovery long enough to follow the f2fs rom's install instructions. The rom was installed successfully and I verified that the fs was in fact, f2fs with diskinfo. The problem is, after a reboot, the modified recovery is lost and I'm back to normal. I assume that's why it can't read/write to the f2fs partitions.
[Nexus 7 Original Development] SkOrPn:
Very interesting indeed. I have never heard of this before. Once the recover flashes there is no scientific reason why it would spontaneous reflash itself to the non modified version.

I wonder if you need to present this question to the TWRP devs?
[Nexus 7 Original Development] BelvedereWRX:
Ok so it's possible I haven't lost my mind then? lol

It seemed pretty cut and dry to me, you flash an image and that's what's written. Surely normal twrp isn't being re-written on reboot.

So to be clear, as long as I'm in the f2fs/modded recovery I should see the red back arrow, correct? And just in case there's some bug with a color change or something, is there something I can do to verify I'm in normal or modded recovery while booted into recovery? I've just assumed I wasn't with the normal colored back button combined with the fact that the fs couldn't be mounted.
[Nexus 7 Original Development] SkOrPn:
No your not losing your mind. Its just a glitch in the matrix. The modded recovery has a red back button, but since yours isn't staying red there must be something wrong with the image. I would download it again, and reflash using fastboot. Also, I think we need a version that specifically states it is a modified version, however I'm sure that is what the red button is for in the first place.

If everything is working, you may not need to do anything at this time, but the next time you have some hours to waste, I would put the device back to clean state before moving on. Also jump into bootloader and make sure your on 4.23. Maybe you need the latest bootloader for that recovery to work. Everything I said is just drawing at straws and may or may not work. YMMV
[Nexus 7 Original Development] bufferpl:
I cant restore anything with titanium backup. Is there any way to work around this problem?
[Nexus 7 Original Development] BelvedereWRX:
I appreciate the feedback. Good point with the img, I'll try an alternate mirror and grab another copy like you suggested.

So far I'm not too concerned as the rom is working great but I would like to back it up though.
[Nexus 7 Original Development] SkOrPn:
The first time I flashed the modified recovery it only entered into the recovery interface once. I flashed the roms, formatted etc and everything worked great. However, the next time I needed to go into the recovery it would never get past the TWRP splash screen. I kept flashing the recovery and trying again but never went back in. Finally 2.7.0.0 was released and I tried that, and it worked just fine. Not sure if it was the new version, or a corrupted initial image. I had downloaded it several times, and yet it would not enter into the UI.

Sometimes there just is no explanation that anyone can ever provide. That's when I call it a glitch in the matrix.. :D
[Nexus 7 Original Development] :
You could try flashing it through terminal. Not sure it would make a difference at all but anyway

su
dd of=/path/to/modifiedtwrp.img if=/dev/block/platform/sdhci-tegra.3/by-name/SOS
[Nexus 7 Original Development] BelvedereWRX:
Thanks guys. One more question. I'm a little rusty with the scene (haven't tweaked since the CM9 days) but is there an option for any type of bare metal backup I can perform if I can't do it in recovery?

I'd like to backup my current state before I start trying to re-flash recovery.
[Nexus 7 Original Development] :
Not sure what you mean but you can boot a recovery without writing it to the NAND.

fastboot boot recovery.img

Then us the backup option in the booted recovery which will back up all partitions including recovery

Or you can back up partitions individually using the dd command

ls /dev/block/platform/sdhci-tegra.3/by-name

dd of=/dev/block/platform/sdhci-tegra.3/by-name/PARTITIONNAME if=/sdcard/PARTITIONNAME.img
[Nexus 7 Original Development] adomol:
Wow, I never knew you could boot recovery like that. Great tip! That may come in handy for me some day.
[Nexus 7 Original Development] utdps:
Need some help. Followed instructions to a T, although it feels out of order. Why should I install the ROM and GAPPS, and then Format the drive. Doesn't that erase it? Ok, here's where I'm at. I had the correct recovery installed with the red back arrow. Installed the FormatPartitions.zip, then SlimRom, and GAPPS. Then I went to Format the disk. I went to file explorer and as I thought, nothing showed up. I tried to push files over but got errors so I tried to reboot recovery. The TWRP splash appears but never loads. One of the times the SlimRom splash showed, but after 10 mins nothing happened so I rebooted. I've been trying to flash the recovery again (and it says successful in fastboot) but it isn't helping, it won't boot to the recovery. Before I did all the formatting, I was able to reboot to the modified recovery several times, so it's not like I have a bad file or it didn't stick.

So basically I have a paper weight right now. Can anyone help me on what I should do or try?
[Nexus 7 Original Development] Juhful:
Ok I did the same thing, after flashing rom you are suppose to format data only and we formatted everything so there was nothing left on the sdcard, I used fastboot to go back to stock rom then once I got back on Nexus 7 stock I used flashify to flash the modded recovery again and followed the directions again and it worked perfectly, so remember after flashing the f2fs rom and gapps format Data only and all should be well, that's how I did it but I'm fairly new at all this but this worked for me, good luck!
[Nexus 7 Original Development] utdps:
I'm trying to follow the restore to stock thread, and I'm getting this error when trying to flash the bootloader again. If I try to skip that step, it says my bootloader (4.13) is too old to flash the .zip. Since you just did this, did you run in to this issue or were you on the 4.23 bootloader already and just flashed the stock zip?

fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.520s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.758sv

EDIT: Nevermind, I got into the correct recovery now. It must have been one of the first steps of erasing the cache or recovery, and then trying to re-flash the recovery fixed it. I should be able to figure it out now.
[Nexus 7 Original Development] adomol:
You are flashing one of the bad bootloaders. Here is a link to the good one: http://www.androidfilehost.com/?fid=23060877489996594

Google has some bad bootloaders floating around... don't ask me why, cause I don't know.

Anyway start here and give f2fs a go again... The instructions for installing are completly in order.

[EDIT] Just noticed your edit!
[Nexus 7 Original Development] utdps:
Thanks, got it all working now! And an updated bootloader as well!
[Nexus 7 Original Development] ronedogg:
To revert back to multirom can I do this?

1. Install multirom app and auto install recovery.IMG and modded recovery.

2. Flash in multirom restorepartitions.zip.

3. Format everything.

4. Restore backup form before f2fs.

5. Profit.

Or do I gotta restorepartitions.zip before I do anything basically is my question.
[Nexus 7 Original Development] fKm:
I did exactly all what the OP says and got stuck into a bootloop. Now I can not get rid of it. I can not event restore the partitions with the zip. Every time I try to start the modified TWRP recovery I see the TeamWin image and then my N7 reboots.

I can flash a standard TWRP but I can not flash any zip with it because it can not mount any partition.

Can anyone please tell me how I can flash something again?

Edit: Okay, restored the stock image. Now I will try all over again.
[Nexus 7 Original Development] austin_dreq:
Why there are two files with different sizes with only ONE instruction on how to use the ZIP? What to do with "TWRP-recovery img" and when to use?:D
[Nexus 7 Original Development] SkOrPn:
I guess you don't read very well, so I will copy the instructions from the OP.

You need:

- Two files you can download above (img and FormatPartitions.zip)

- A ROM with "All-F2FS" support (Like my SlimKat version)

- GApps (i think you want PlayStore.) Usual GApps. Slim AiO work well.

Copy a ROM with "All-F2FS" support to your N7

Copy GApps to your N7

Copy FormatPartitions.zip to your N7

Reboot in bootloader

Flash this recovery with Fastboot (Maybe Flashify works too)

Reboot in new recovery

Flash FormatPartitions.zip

Reboot recovery (It's needed for some reasons..)

Flash ROM

Flash GApps

Go to Wipe Menu and Format Data (Not a simple wipe)

Reboot

Done.

It very clearly tells you what to do with these two files.
[Nexus 7 Original Development] austin_dreq:
Thanks for the clarification mate...

Any alternative way in flashing recovery other than Fastboot? What is Flashify?
[Nexus 7 Original Development] SkOrPn:
Flashify is a Google play store app that can flash recoveries from within the Android OS. Its good for when you flash a bad recovery and it no longer works, etc. That is the only time I use it. It recently saved me from a corrupted recovery file. There is also "Flash image GUI" app as well, it has even better reviews.
[Nexus 7 Original Development] utdps:
I would just use fastboot. You're going to have to push files over anyway unless you have a USB OTG. If/when you find yourself in trouble (I and at least a few others have on this), and you're not ready to use fastboot or ADB, it's not going to be good. Just for day to day flashing needs though, Flashify works great, as long as you have a booting ROM to use.
[Nexus 7 Original Development] Fransis88:
can you please make a version of TWRP to F2FS support for tilapia, with the modified recovery to be for grouper only lets me install roms grouper and I lose 3G.

Tilapia with TWRP would need support F2FS.

Thanks in advance!
[Nexus 7 Original Development] bray424:
So after a week of flashing recoveries, formatting data, restoring factory images and changing file systems, I finally stumbled on a solution for my "encrypted storage password" woes, and I figured maybe this might help someone else (this only applies to standard roms with F2FS data partitions, not all-f2fs roms).

When I first saw legolas' kernel thread announcing f2fs support, I tried it with the then current Cm11 rom and his kernel, and everything worked fine the first try. A few days later, faux released his newest kernel with f2fs support and I tried it out and everything was working great. About a week later I saw the cm11 changelog had some new features so I tried to update, and that's when I started getting the password screen. For another week I tried everything I could think of to get it working, until last night when I decided to start from scratch and do everything I did the first time I turned on f2fs, and then it hit me: when I first did it, I used legolas' kernel first, then added faux's kernel a few days later, whereas now I was trying to flash cm11 and go straight to faux's kernel. I decided to try a clean install with the latest cm11 and first install legolas' kernel then flash faux's, and everything worked fine (well except for the phone process crashing when you first boot but you can just delete that fron priv-app).

So from what I can figure, legolas' kernel installs something that other f2fs kernels don't, so you need to flash it first. I'm not sure if you can flashmone right after the other or if you need to boot with legolas' kernel at least once, but I booted with his and rebooted after the first input screen I saw the flashed faux's and everything worked fine.

As a side note, while I assumed that faux's kernel would be the way to go, it doesn't seem to have dithering enabled or if it does its a very ugly implementation of it, which is why you see bars in the background of the settings screen. Legolas' kernel doesn't have this issue, which is why you get one smooth gradient on the settings screen and why I'm sticking with it for the time being.
[Nexus 7 Original Development] Androguide.fr:
Hi [MENTION=2743057]legolas93[/MENTION], amazing work.

I'm trying to implement f2fs support to my kernel for the Xperia Z1.

I have ported the f2fs kernel driver and it builds fine, so now I need to modify the recovery.

In order to get the recovery to use mkfs.f2fs when formatting data, do you build TWRP with both those flags, or only the F2FS flag ?

TARGET_USERIMAGES_USE_F2FS := true
TARGET_USERIMAGES_USE_EXT4 := true

Do you have the source for your modified TWRP (with the red key etc...) on github somewhere ?

Also, for your "All F2FS" roms, do you just modify the fstab to use f2fs for the system partition, or are there other tricks ? If there are, can you please tell me more about it ?

Thanks for your work.
[Nexus 7 Original Development] qu3becker:
You might want to check this thread if you haven't already: http://xdaforums.com/showthread.php?t=2634271

Salutation à mes cousins français.
[Nexus 7 Original Development] ThinkAlot:
Hi could someone upload a flashable version of the f2fs twrp? I'm not near a computer at the moment and really wanna try this out on this dead day at work.
[Nexus 7 Original Development] ronedogg:
I hate to ask questions like this.... But do you have any plans on doing multirom with this?
[Nexus 7 Original Development] adomol:
He already did: http://xdaforums.com/showpost.php?p=50700654&postcount=4
[Nexus 7 Original Development] ronedogg:
That's just for f2fs not all-f2fs..... There is a difference.

Also you signature is misleading. Its for 1gb free not 11gb :)
[Nexus 7 Original Development] austin_dreq:
Good advice! :highfive:
[Nexus 7 Original Development] ScumDroid:
This is some solid work [MENTION=2743057]legolas93[/MENTION]. Installed fine first try (checked with diskinfo, all partitions are f2fs). I tried flashify for the recovery, i was curious to see if it worked, it did. Just setting Your modded SlimKat up now. :highfive:

**EDIT** [MENTION=2743057]legolas93[/MENTION] Donation sent. Thanks again for your work.
[Nexus 7 Original Development] legolas93:
I have to thank you a lot for your support :) Really appreciated!!

Happy to see that the procedure is solid and worked at first try!!

Thank you again!
[Nexus 7 Original Development] adomol:
I have to say I'm enjoying your work too [MENTION=2743057]legolas93[/MENTION], i have had all-f2fs slimkat installed since my post back on 3/11. And using this device has felt like I've got a new toy again. Smooth, stable and very responsive. Gives my N7flo a run for its money!
[Nexus 7 Original Development] LiquidSolstice:
"password to decrypt storage"

I figured out what the problem was. It's a lot simpler than what you describe.

The reason why I (and I imagine, you as well as the others) are running into this issue has to do with how we're reading the instructions. When the OP says "Format Data" and not to use the "Wipe/Factory Reset", I assumed he was referring to wiping the partitions through the Advanced Wipe menu.

What he's actually referring to is the Format Data button to the right of "Advanced Wipe". The one where you have to manually type "yes" to properly format your storage. That's where I went wrong, and I hope that helps you out too.

Combined with OP's build of Slim, I can safely say I'm greatly enjoying my aging tablet again. Thank you!
[Nexus 7 Original Development] ThinkAlot:
Hi, I followed the instructions exactly and now I'm getting a bootloop at the slimkat screen. Then I went into recovery and formatted data again and now I'm stuck at the Google screen. Anybody know why this is happening? I successfully did the f2fs procedure yesterday(with help lol) but wanted to try the "all f2fs" and see the difference.

EDIT : i tried it the 2nd time and it worked perfectly fine. i can instantly see the difference especially the speed and smoothness. the idea of buying a new android tablet is going on-hold for now.

thank you very much for this. 6100 on quadrant and 15100 on quadrant with GPU @ 486.
[Nexus 7 Original Development] T-Keith:
I'm running slim Kat, but whole it's working OK, I'm not a fan. Is there a more stock looking rom out there compatible with all f2fs.
[Nexus 7 Original Development] adomol:
What do you mean by more stock? Is it Nova Launcher that you don't like? You could always switch to Google Now for a stock look. As for Slimkat, it is a very smooth running and stable rom with some very nice features. I would not switch it before playing with a launcher or two to dial in a desirable UI. But that's just me.
[Nexus 7 Original Development] LiquidSolstice:
Change DPI back to 213, change wallpaper, flash PA Gapps with the Google Experience Launcher, and don't use TRDS. If you do that you won't be able to tell the difference between stock and Slim.
[Nexus 7 Original Development] adomol:
This would definitely do the trick for a straight stock look. And the for the DPI tweak, I'm pretty sure you can do that right in .../system/build.prop

[EDIT] Amen on your Cyanogenmod message! Just noticed that.
[Nexus 7 Original Development] T-Keith:
It has nothing to do with the launcher. I don't like the goofy multitasking, and it has a weird dark theme, I can't tell my calendar apart they all look black.
[Nexus 7 Original Development] Hanger84:
Very nice work. I'm trying this out now, but I did encounter one small issue with the recovery though that I did not have with the normal TWRP. My N7 doesn't show up when I try to use ADB sideload. I'm not sure of what exactly the cause is, but I'm certain that it's not a driver issue, since I can sideload files with the normal version of TWRP.
[Nexus 7 Original Development] kufikugel:
Then turn off trds which you have enabled lol. Then all is stock themed.
[Nexus 7 Original Development] T-Keith:
Wrong. The real dark slim is off and colors are still off, still has the annoying multitasker.
[Nexus 7 Original Development] kufikugel:
Then something other is wrong for you. Look at the sources all stock and nothing dark themed.
[Nexus 7 Original Development] T-Keith:
Check out my calendar, all those events should be different colors. It's not stock themed, they modified Google Apps for theming.
[Nexus 7 Original Development] kufikugel:
1. This is aosp calendar and not Google calendar. Two different apps

2. If you do not believe me look at the sources. It is stock

3. If it does not show the correct colors for appointments something is off with your calendar sync to Google.

See attached picture....slim calendar trds off.

View attachment 2664166
[Nexus 7 Original Development] adomol:
Which gapps did you flash? If you don't want the dark themed stuff flash pa gapps instead of slim gapps.
[Nexus 7 Original Development] T-Keith:
Yeah I flashed the slim gapps which comes with aosp themed, but that doesn't really fix anything because it doesn't get rid of the multitasking. So I'm really looking for another rom.
[Nexus 7 Original Development] Lisac1606:
Get OmniRom, all-f2fs.
[Nexus 7 Original Development] T-Keith:
Installed Omni rom, had to use PA mini gapps, but it works great. No ugly mods like slimkat and performance seems much better. Thanks a million.
[Nexus 7 Original Development] fossean:
I didn't expect it to work, but I just used the modified TWRP in the OP to flash Slimkat on my tilapia. Downloaded the latest stable tilapia Slimkat from here http://is.gd/5VXjeX , then used 7-zip to replace the boot.img and updater-script from slimkat 4 linked here http://is.gd/k5uRVJ (all thanks to legolas93 who developed the modified TWRP and modified Slimkat for grouper):good:

Thanks are due also to Ronedogg who describes here http://is.gd/mgbRMC which files should be replaced. I initially tried with the files attached in Ronedogg's post but the flash failed for some reason.
[Nexus 7 Original Development] ReznovHuang:
file corruption?

I download the recovery for many times

and then......

C:\windows\system32>fastboot flash recovery grouper.img

error: cannot load 'grouper.img'

MD5: 6d3f5b6f2f1b26d29ca8705743ad895a

Is that correct?
[Nexus 7 Original Development] johnminator:
Getting a type of decrypted error on device after doing this. Am i doing something wrong. I am flashing the recovery with Nexus tool root kit. Also i have tried with flashify but it all i get is this.

Please help this looks soooo nice please help
[Nexus 7 Original Development] adomol:
Most likely the data partition isn't formatted to f2fs.