yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Android Development] chrisxbell714:
???

So....idk if anyone has used this thread and its recoveries for current builds of oreo roms... but...no matter what I do I cannot get F2FS to work with any oreo rom I throw at it. With the 3.2 f2fs recovery I flashed from this thread my internal storage gets deleted upon re-entering twrp...every single time. So I decided to flash the 3.1 twrp recovery to see if it made a difference...with 3.1, when I flash the august 13th build of resurrection remix in 3.1 it says and I quote "E3004: This package is for device: angler; this device is ." It literally tells me my device is "." . Ive been flashing since the motorola cliq. I have plenty of experience with custom roms and twrp. Something is F*cked up here LoL. And of course I have the latest bootloader, radio, and vendor image from august.

When I tried the 3.2 twrp from DEVILOPS 007, after flashing Resurrection Remix, gapps, Magisk, and Anykernel, it shows the boot animation then goes to a screen that says it failed to decrypt my phone and it tells me to reset my phone...

Is there a trick to this? I even tried the instructions for using F2FS by "secretcow" here https://xdaforums.com/showpost.php?p=69980946&postcount=2497. But I still cant get this to work.

I'm lost? This has never happened before with any other phone I have had.
[Nexus 6P Android Development] chrisxbell714:
...This recovery screwed some sh*t up. So after trying these recoveries and failing. The day after my last post I re-flashed back to the "stock" twrp that they have posted on twrp's site. I Have been running resurrection remix with magisk 16.7, open gapps, and anykernel for a while now. No issues. I decided last night i wanted to add fingerprint and pattern security. I set it up and went about my day. For whatever reason I started having wifi issues. Where my wifi literally wouldn't activate? Never happened before. Ever. With this phone. Just throwing this out there, I have NEVER had ANY decrypting issues with any roms or official recoveries. So...I rebooted to see if the wifi issue was fixed. Upon reboot....a screen came up...saying my phone couldn't be decrypted and the data was "Corrupt"? I have not backed up my apps with titanium. I have not backed up my texts or call log. NOTHING backed up because of how impulsive this issue was...Im a little frustrated but I understand at the same time. Apparently I'm going to have to start from scratch meaning...completely wiping my phone to stock. Re-Lock my device. Then go through the whole unlock bootloader re-rooting process because The recoveries I flashed from this thread has obviously screwed something up software wise. F*cked up man. But I understand I flashed experimental software that had little to no testing. I appreciate what the people in this thread has tried doing. But listen to my warning. IF YOU FLASH these experimental recoveries....something may go askew.

EDIT: I forgot to add that trying to make a backup with twrp after this decrypting issue...twrp literally couldn't back up my data instead it came up with an error.

EDIT AGAIN...I just did a full wipe and reflashed resurrection, gapps, magisk, and anykernel...my phone failed to decrypt...WTF? I'm on official 3.2.3 twrp...I havent fully factory reset my phone to stock yet...I needed my phone right now. I will respond back after fully going flashing to stock...I work overnights and its 1:48 pm EST so maybe tomorrow...?

EDIT a third time: Why did TWRP come up with my set unlock pattern after fully wiping my phone? Im in a WTF state right now.

Thank you again for the people who tried making this possible but...its just too buggy for any user to use...even after flashing back to an official recovery. Its not your fault you didn't know.
[Nexus 6P Android Development] chrisxbell714:
Alright so whoever has problems after flashing this recovery I know a way to fix any issues you may have. Follow this guide carefully.

Here's what you do.

1. BACKUP YOUR INTERNAL STORAGE TO YOUR PC if you have anything worth saving!

2.Download minimal ADB and Fastboot from here (https://xdaforums.com/showthread.php?t=2317790) I personally install it to the root of my C: drive.

3. Go to fastboot on your phone. Go to the minimal adb and fastboot directory and right click and run as administrator the file "cmd-here.exe"

type fastboot devices to make sure your device is shown. Then type...

fastboot erase system

then

fastboot erase userdata

then

fastboot erase cache

then

fastboot erase recovery

4.Download TWRP from here (https://dl.twrp.me/angler/) then rename it to recovery.img then copy "recovery.img" to the minimal adb and fastboot directory and then run the command...

fastboot flash recovery recovery.img

5.Here we go...download whichever stock zip from this site that suits you (https://developers.google.com/android/images#angler) I used the august zip because resurrection hasn't updated to September yet but choose whichever you want then extract the contents to your "minimal adb and fastboot" directory, make sure when you extract the zip that you copy the contents of the folder inside the zip to the minimal adb and fastboot directory and NOT JUST THE FOLDER!

After you extracted the contents of the stock firmware, then run...

"flash-all.bat" in fastboot. You will probably get some minuscule errors about system and data etc...trust me let it do its thing. It'll take a couple minutes to complete the process. If it ended well your phone will reboot and the command prompt will close on its own.

6.Your phone has now rebooted and will come up with the usual sceen saying it cant be checked for corruption blah blah etc etc, let it do its thing. You will finally see the stock boot animation. Let it load until it gets to the setup screen. I waited about 2 minutes then turn off your phone by holding the power down button. Wait about 30 seconds when it goes black then hold power and volume down to get to fastboot.

7.RE-FLASH TWRP using

fastboot flash recovery recovery.img

8.Download the corresponding 3 images from here...bootloader, vendor, radio... (https://kantjer.com/image/) rename them to bootloader.img, vendor.img, radio.img it just makes it easier. Then copy them to the Minimal adb and fastboot directory.

flash them in fastboot using the commands...

fastboot flash bootloader bootloader.img

then

fastboot flash vendor vendor.img

then

fastboot flash radio radio.img

9.ALMOST DONE! Reboot to recovery through fastboot by using the volume keys.

10. Copy all of your internal storage goodies back to your phone! MAKE SURE YOU DO A FULL WIPE WHILE IN TWRP BEFORE FLASHING ANY CUSTOM ROM!

You should be back to normal. I know I am! I took a lot of time typing this out to make it as simple as possible! Please thank me but especially the devs for the software that they have proudly contributed and please show appreciation to the Android community!
[Nexus 6P Android Development] AzraelsKiss:
Although your method is very thorough, it seems a bit overly complicated to me... First of all, if you want to be completely thorough, you may want to explain the ways to put the device into fastboot in step three. I wholeheartedly agree that if you're having issues with your device after using custom ROMs/recoveries, you should try flashing back to stock and start over, but it shouldn't be absolutely necessary to wipe those partitions, because flash-all.bat should wipe the necessary partitions. Also, it shouldn't be necessary to flash TWRP before flashing stock, because flash-all.bat will flash the stock recovery anyways. Same goes for flashing bootloader, vendor and radio after flash-all.bat has already flashed all three.

Personally... I prefer to follow [MENTION=6555069]Heisenburg[/MENTION]'s guide at https://xdaforums.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 when flashing back to stock, or most any other tip or trick related to the N6P. But that's just me.

Finally... If you were only having decryption issues, you may have only needed to format userdata with "fastboot format userdata" to remove encryption rather than completely reflash stock, but as I said, I do recommend reflashing to stock if nothing else seemed to help.

Have a good one!
[Nexus 6P Android Development] shaikhalid007:
Bro one question . does f2fs have a huge impact on performance. To be specific gaming performance???
[Nexus 6P Android Development] chrisxbell714:
c

Honestly it has performance gains when writing to emmc. It can increase write speed tremendously. But it "CAN" reduce read speeds. According to benchmarks (i prefer real world performance) You could get maybe 5-25% less in read speeds depending on what you are doing although you could see read speed increases in certain events. Overall it is a better file system in terms of performance compared to ext4. I love f2fs but its limited to earlier versions of android currently for our phone...lets face it our phone is getting out of date. Time to upgrade soon...

Look here for benchmark readings of ext4 vs f2fs https://xdaforums.com/showthread.php?t=2697069

---------- Post added at 03:07 PM ---------- Previous post was at 03:01 PM ----------

I already know some of what I have put might be unnecessary but I prefer to be extremely thorough and ocd with my phones. Better safe than sorry. After flashing the flash-all.bat my phone wouldn't boot. I had a similar issue with another phone. So I put in to the guide to flash twrp before and after. I have always liked a clean slate before flashing anything including stock roms. I know a phone cant boot without recovery and I dont know if these custom recoveries on this thread messed with my recovery partition so I added flashing twrp. I have experienced dramatic issues with not being thorough in the early ages of android scratching my head wondering what in the hell could have gone wrong following someone else's guide. I just aim for perfection that's all. I do appreciate the feedback though. Im just really OCD lol
[Nexus 6P Android Development] shaikhalid007:
But the performance may differ from device to device

Those benchmarks are true. But not accurate for this phone

I want your experience was the gaming performance better???

Because i play pubg like 4 hrs a day. I have ctt mod installed. 2 big cores disabled to prevent over heating.

Getting decent performance. But not on par since i m a pro player i wish to get better performance thanks for your reply
[Nexus 6P Android Development] chrisxbell714:
Sorry for the wait. I have ctt with magisk...what a difference, no more throttling. Still how are you not getting overheating issues? I have my phone at 3 cores at 1.2 ghz (it performs pretty damn well) and playing certain games the temp goes over 60c! I don't throttle anymore but the phone is to hot for the battery to last. I replaced my battery in November last year I already have to replace it again...it dies at around 20% due to the heat overtime. But...in terms of frames per second I don't see any gains at all UNLESS the game writes a lot of information to your emmc/internal storage otherwise If you want a more "fluid" gaming experience then set the gpu governor to performance and set it to 600mhz and increase cpu frequencies if you have it underclocked. Otherwise f2fs will not show any FPS improvements. F2fs is more for write operations not read and...when battlegrounds is loaded its loaded to the ram not on the fly like for most applications/games. Sorry to say in MOST cases ram(to a phone) is stuck at whichever setting the chipset sets it at, there are no options for ram overclocking unless your a software engineer/coding professional. If its a home computer....that's a different story. F2fs is more for file operations.
[Nexus 6P Android Development] shaikhalid007:
Thanks for your very explaining explanation. Now i understand.i have also replaced battery once.now it dies at 50 percent i m going to replace it once more before given up on 6p.and i m also running ctt mod alongside elementalx.can you post screenshots of your setup??

Thanks again
[Nexus 6P Android Development] chrisxbell714:
Yeah Ill definitely send some screens. I use EX Kernel Manager. You can buy it from play store.
[Nexus 6P Android Development] shaikhalid007:
Thanks but.how is your battery temp so low?? My battery temp when idle is 35 c and when using 37-40
[Nexus 6P Android Development] chrisxbell714:
As of right now i'm in an A/C'd room so my cpu temp is low. BUT don't look at my battery temp because I got scammed on amazon...They showed a pic with a battery sensor with my replacement but when I got the battery in my hands there was no sensor...so the battery temp remains the same at all times.
[Nexus 6P Android Development] shaikhalid007:
This is my setup

Elementalx

Ctt mod
[Nexus 6P Android Development] chrisxbell714:
ALSO I forgot to mention I use "anykernel" now as my go-to kernel. I used to use elemental X.

---------- Post added at 12:40 PM ---------- Previous post was at 12:36 PM ----------

If your using ctt mod it tells you to you MSM thermal instead of the other options...figured id let you know that....oh and by the way elementalx ALWAYS parks the "BIG"(cortex A57) cores, elemental x drops performance when it comes to the cortex a57 cores.

---------- Post added at 12:43 PM ---------- Previous post was at 12:40 PM ----------

dude use "cool tool" from playstore its free, and it shows all eight cores. Watch your 4 cortex a57 cores drop off(park) even with ctt. look on the bottom left of my screenshots you'll see it :) BUT you need selinux permissive if you want to see cpu usage percentage.
[Nexus 6P Android Development] Anuvadak:
Hey, guys

May anybody share the last WORKABLE version of this great creation, please?

Version 3.2.0 I suppose:rolleyes:
[Nexus 6P Android Development] DroidFire:
You ever find it? Cuz I'm trying to find it as well. An thanks in advance for to anyone that help us find this ver of twrp
[Nexus 6P Android Development] TaZeR369:
Does this still work with all of todays roms up to but not including android 10? If so can it be used in such a way as to make use of the feature of changing the file system type on an active rom, then upgrading it to the latest official verison of TWRP would the system still work then? Thanks.
[Nexus 6P Android Development] nathanchance:
Most likely a combination of both. f2fs auto trims so the file system never gets bloated from dead or dirty segments.
[Nexus 6P Android Development] ariefabuzaky:
One by one my app keep failing to launch, first gboard then nova, substratum. its happen when my device in idle or long sleep

PN with f2fs
[Nexus 6P Android Development] bsg411:
Starting to happen to me too....and I cant get substratum to work at all.
[Nexus 6P Android Development] hecksagon:
Anybody have any luck getting encryption to work after conversion to F2FS? Every time I've tried it has somehow been converted to EXT4 and is corrupted, causing a bootloop.
[Nexus 6P Android Development] ariefabuzaky:
What rom ?
[Nexus 6P Android Development] hecksagon:
PN and the Uber ROM that was posted in the other F2FS thread in General. Both work fine unencrypted but fail to boot after encryption is enabled. For now I have moved back to EXT4 since the benefit of F2FS is not worth the loss of encryption.
[Nexus 6P Android Development] ffh2303:
I've followed the instructions in the first page and two pages back, but I can't make the /data partition stick to f2fs. It either bootloops or gets returned back to ext4.

ROMs I've tried

- Pure Nexus 21st Jan build

- DU RC 13th jan build

- Nitrogen 13th Jan build

Kernels i've tried

- Flash 23rd Jan build

- Franco r45

TWRP used was the one in the first post

Only once f2fs stuck with PN and Flash kernel, but when i rebooted install SuperSU it bootlooped. phh Superuser will not install at all with the TWRP, it says Error 1.

I've redownloaded the ROMs, kernels and TWRP multiple times in case anyone asks.
[Nexus 6P Android Development] Pollie81:
Strange thing, 2 days a go i tried f2fs for the first time on saosp and flash kernel 21-1 and it worked immediately.

yesterday i reverted back to ext4 to try another rom and now i can't get f2fs working anymore.. this time i'm using flash 23-1 though..

it either bootloops or it reverts the data partition automatically back to ext4.
[Nexus 6P Android Development] bmg1001:
As for SuperSU, there was an XDA article on why it doesn't work with F2FS. As for the main issue, when formatting to F2FS, what does the TWRP log say? Does it say "Wiping data without wiping /data/media" or something else?

Also, are you trying to restore data too or are you going for a clean flash?
[Nexus 6P Android Development] ffh2303:
It says formatting with makefs.f2fs

I was trying to clean flash. As for the SuperSU, i was using the 2.79 SR3. Before using SuperSU I was trying to use phh's superuser from here https://superuser.phh.me
[Nexus 6P Android Development] bmg1001:
Good. That means F2FS is being formatted correctly. Usually, that would be it for clean flashes. It still messes up afterwards?
[Nexus 6P Android Development] ariefabuzaky:
Any other way to know if f2fs working .?

i reboot to recovery i saw my data and cache already on f2fs, its work didn't ya ?
[Nexus 6P Android Development] justin1221:
I haven't had freezes. It is smooth but I don't see any difference in app opening or anything like that compared to ext4.
[Nexus 6P Android Development] :
If its not sticking after reboot you have to format in TWRP. Its the format when you type "YES" and it wipes everything. Make sure you have all backup that you need. Reboot. Than format Data and Cache to F2FS. Then reboot let it boot then reboot back to recovery, and check to see if it still is F2FS. Flash compatible ROM and Kernel, mods, etc..I havent had any trouble with supersu, using same one as you.
[Nexus 6P Android Development] LazerL0rd:
There is an article on xda by [MENTION=4898097]arter97[/MENTION]. It states this problem as a needed loopback support for SuperSU's ext4 boot.img, as well as something else.

What you have to do (found out on my 5X), is the flash SuperSU FIRST. THEN your kernel of choice. Personally, ik that franco kernel has this implemented in it's changelog, I'm not sure about the Flash Kernel support. It's cause the "anykernel" flashes onto of some SuperSU contents to fix it. (SuperSU can't do this as lots of people still use ext4 and I think there's limitations). :good:
[Nexus 6P Android Development] bmg1001:
Alright, I think I figured out why sometimes /data gets reverted back to EXT4. It seems to be affecting clean flashes only. I was doing a clean flash for PureNexus and I flashed Magisk, then after rebooting, I noticed Magisk was nowhere to be found and my data was back to EXT4. I believe this has to do with something going on during the first boot process wiping /data to EXT4, which would explain Magisk not installing properly. You see, when you flash Magisk, it writes some files to /data that auto-install during the first boot, and when flashing a Magisk Module (they usually check for Magisk on install), they detect fine before the first bootup, but they can't find it after the first bootup, when everything is suddenly EXT4 again. I think a possible workaround is doing a clean flash with everything on EXT4, then after the first boot, go back to recovery, and then try following the directions on switching to F2FS while keeping /data.

I am testing this right now as I post this...

EDIT: I can confirm that F2FS did stick with this method and I immediately knew it too because everything did legitimately run a good amount smoother (and I double-checked with TWRP.)
[Nexus 6P Android Development] ariefabuzaky:
So the magisk is the problem ?
[Nexus 6P Android Development] spuri78:
Do you mind sharing your flashing instructions then based on your findings?
[Nexus 6P Android Development] bmg1001:
No, but it helped me discover the problem.

This is what I did.

1. Revert everything back to EXT4.

2. Flash your ROM like you usually would. You might as well flash the F2FS-supported kernel now too.

3. Let it boot, as soon as you reach the setup screen, let it sit for a minute in case it's downloading stuff in the background, then reboot back to TWRP.

4. Backup /data to a safe place.

5. Format /data and /cache to F2FS.

6. Once /data and /cache are on F2FS, go to TWRP Settings and enable "use rm -rf instead of formatting"

7. Restore /data from your TWRP backup.

8. Reboot and you should be on F2FS.

It's essentially the old method of getting F2FS and keeping your data, but this is for those who want a clean flash, well, as clean as possible.
[Nexus 6P Android Development] Dbj.Dhaval:
I tried the same method with nitrogen rom and flash kernel the phone rebooted Bt when I reboot the phone once again it won't go past Google logo then had to clean install and again data got revert back to ext4
[Nexus 6P Android Development] bmg1001:
You got a boot loop? Wow, if it's not one thing it's another. F2FS is just too tricky (or I don't understand it enough either...)

It isn't always the same for every device I suppose. F2FS is technically still in development but it should be stable enough to not have these problems :/
[Nexus 6P Android Development] nathanchance:
But so is ext4 :p and nearly every other file system in the Linux kernel: https://github.com/torvalds/linux/tree/master/fs

Sorry I can't be much more help guys, I just simply can't format my phone constantly to try and reproduce a lot of these issues.
[Nexus 6P Android Development] iron maiden:
Hi, I have installed pure nexus and flash kernel 25 January recovery twrp f2fs I changed data and cache and reboot bootloop thanks

regards
[Nexus 6P Android Development] Dbj.Dhaval:
Yes I tried every possible method mentioned in every thread Bt still no luck. Only cache has been converted to f2fs. Bdw does one can change system to f2fs? For say nitrogen rom. It does support f2fs. Also I wish some video was there from scratch to end so that it can b bit easy.
[Nexus 6P Android Development] nathanchance:
F2FS on system is really dumb, since it is read only 99% of the time, which makes it better suited for EXT4.
[Nexus 6P Android Development] Pollie81:
i'm going to test some more today but i'm realy getting the sense that when your data automatically returns to ext4 or you get in a bootloop you simply flashed something that isn't f2fs compatible.

it's a shame that so little roms are f2fs compatible.

strange thing i got it working once on saosp but since then i can't get it to work anymore, i've read about f2fs many times the past years and just now i took the step to actually try it.

and i have to say i love it, it's just that minor step to full smoothness. those little hickups and lag during opening of apps/menu's and during scroll are all gone..

and now i'm eager to get it working again, which it did yesterday with uberstock but uberstock is simply not my favourite.. [MENTION=6842057]The Flash[/MENTION] How hard is it to make a rom f2fs compatible?

edit:

so uberstock was working on f2fs..

i rebooted to recovery and wiped like you do a clean flash, but first i had ticked the format option in twrp. (the one that's changes the format method to rm-rf or something like that)

then i flashed saosp, supersu sr3,flash kernel and gapps and booted the phone. and luckily it's still working on f2fs, both data and cache!
[Nexus 6P Android Development] nathanchance:
New recovery available at the download link in the OP, compiled from the latest sources.
[Nexus 6P Android Development] ariefabuzaky:
Anyone know what this mean
[Nexus 6P Android Development] Woodrow256:
Ive been using f2fs for months and ive never messed with use "rm -rf instead of formatting". Its worked every time. Is this step required for everyone? If so why does it work for me without it?
[Nexus 6P Android Development] :
Just if you wanna restore a backup.
[Nexus 6P Android Development] Pollie81:
So for a clean flash of a rom when you wipe system, caches and data this option isn't necessary?
[Nexus 6P Android Development] minhgi:
wow..I haven't have any problem with F2FS on both my Nexus 5x or 6p. Both of my devices run Resurrection rom and Flash kernel. Maybe it was the consistent between setup that I don't see any issue.

And both phones are very heavy modified.