yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AgentSmith:
Fstrim in Android doesn't support f2fs yet. I'm sure that when it does it will respect the discard flag. In the mean time does this matter to the end-user? The point is that fstrim doesn't / can't interfere.

Is it possible to check if the f2fs cleaner works?

Would there be a situation where fstrim is better than f2fs's own cleaner? I mean, there must be a reason why they make fstrim f2fs compatible.
[Samsung Galaxy Nexus] osm0sis:
Tethering should work as long as you've got SELinux set to Permissive on CM-tree based ROMs, and with either setting on pure AOSP-based ROMs.
[Samsung Galaxy Nexus] fleckdalm:
I have done a clean wipe because I switched to f2fs. However I'm not sure since when it stopped working...
[Samsung Galaxy Nexus] osm0sis:
We've got people with your same basic setup running with no issues so there must be something different about your settings.. If I were you I'd backup then see if a clean ROM flash fixes it. :good: :)
[Samsung Galaxy Nexus] fleckdalm:
Yeah I will try it...

Edit: the clean flash solved the issue!
[Samsung Galaxy Nexus] paganwinter:
Used latest TWRP Recovery (TWRP-2.7.1.1-F2FS/EXT4-MAGURO) and Kernel (DirtyV-UR 6/28) from the OP.

Got the latest Vanir (vanir_maguro_4.4.4.071314 from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/maguro/) and used poo706's Tool (http://xdaforums.com/galaxy-nexus/development/tool-galaxy-nexus-ext4-to-f2fs-rom-t2794702) to convert to F2FS.

Got Bank's GApps (from http://xdaforums.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857).

Followed the work around from the second post (http://xdaforums.com/showpost.php?p=53024798&postcount=9575).

Everything went smoothly.

Got stuck at Google Logo.

Tried flashing ROM and GApps again, still no luck.

Finally got an older Commotio (http://xdaforums.com/showpost.php?p=53005551&postcount=9461) and the same Bank's GApps.

This time it worked fine.

What exactly did I do wrong? Only thing I can think of is, that I probably didn't convert the Vanir to F2FS right. I did get a couple of errors for .NET not being present, even though I used the .bat file to convert.

Anything terribly wrong with the files I chose? (ROM, Kernel, GApps)?
[Samsung Galaxy Nexus] osm0sis:
You are clearly way on the ball and super motivated, so please do these tests you're proposing and report your findings for the community, maybe in their own thread, "F2FS Tuning for the GN". It would be of great benefit and greatly appreciated, I'm sure. I'm not even on f2fs yet, and have just been going by what Smitty, aosp, metalspring and others have reported with some minor (purely academic) research of my own. :)
[Samsung Galaxy Nexus] poo706:
There's no reason that the bat file would complain about .net. Vanir must have changed something recently, check out the last couple of pages of my converter thread. Someone else had exactly the same issue. There appears to be a conflict with smitty 6/28 that's included with my converter and recent vanir, recent liquidsmooth, and possibly others. Some have said fancy was the answer and some have said smitty 6/15 was the answer.

Sorry to say smitty that I'm going to release a new version of my converter suite and include fancy instead to see how it goes.

[poo]
[Samsung Galaxy Nexus] paganwinter:
Damn it! soooooo many threads to look up before getting into all this... :silly:

Thanks for the quick reply!
[Samsung Galaxy Nexus] crazyeats:
[MENTION=2800589]paganwinter[/MENTION] give the android version of poo's converter a try. If ur getting errors on windows then that's where I'd start.
[Samsung Galaxy Nexus] paganwinter:
Seems to be some issue with latest Vanir+SmittyV

http://xdaforums.com/showpost.php?p=54146755&postcount=224
[Samsung Galaxy Nexus] crazyeats:
Hope all is well now.
[Samsung Galaxy Nexus] mrgnex:
Yeah I had issues with that too. The 15-6 is the latest that works. Or fancy r51 ;)
[Samsung Galaxy Nexus] poo706:
ATTENTION TOROPLUS USERS ON F2FS

I have adapted the work of [MENTION=4913579]CPA Poke[/MENTION], who orchestrated a unified EXT4/F2FS grouper LiquidSmooth. I believe I have successfully ported that over to us. Everything works like it should on my ext4 toropus, so I need a F2FS tester. The updater-script will detect what fs /system is already formatted for and run the appropriate command when wiping. It will also detect whether you have all F2FS, all EXT4, or just data EXT4 and rebuild the kernel with the appropriate fstab. I made sure to have the discard option specified on the f2fs partitions. Please install just the ROM (ie no external kernel) to make sure that the kernel rebuilding goes correctly. And it's odexed, fyi.

Relevant commits:

https://github.com/LiquidSmooth/android_build/commit/13249f806654e7e034ae9bd5761adcec10f92078

https://github.com/LiquidSmooth-Dev...mmit/e265a022a69d5be9f6670fb1badc7c8588f88141

Test build download:

<removed>

I'm making a maguro version right now, I'll try to get it posted tonight, may have to wait until tomorrow.

[poo]

Edit: removed link
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3927368]poo706[/MENTION] Didn't I sort of already do that for Liquid Smooth/ROMs? I'll edit this in a minute with a link to the post. The ramdisk edit thing is new and cool, but if you've already got a unified ramdisk you don't need to. :)

Edit: Here we are.. http://xdaforums.com/showpost.php?p=53312320&postcount=10192 ;)

His way might be better, I don't know. I thought mine was pretty clean though. :good:

P.S. Off to see friends and family for a couple days then off to Ireland for a week with like 8 friends! Wish my still-recovering-from-a-broken-leg ass some of that Irish luck! :laugh:
[Samsung Galaxy Nexus] poo706:
Oh yeah, I do remember seeing that. Here I thought I pulled off something special. I perused the threads real quick and found only one other rom that was unified, and that was only as of a week ago.

Did anyone implement your method in their rom that you know of?

[poo]
[Samsung Galaxy Nexus] osm0sis:
Maybe LS, but all the ROM maintainers seemed pretty staunch about having separate builds even though I made it simple. No idea why.

Anyway feel free to adapt mine or merge it with CPA's or whatever makes the most sense. Keep us posted. :)

Edit: Oh, I just remembered the guy who was converting Carbon ROM zips to f2fs started using my method too. :good:
[Samsung Galaxy Nexus] a3361035:
Both are inferior to Motorola's elegant fallback solution imho:

http://review.cyanogenmod.org/#/c/65480/

Universal for any fs combinations, no multiple fstabs, no repacking of ramdisks.

P.S. Unrelated. Updated my old post:

http://xdaforums.com/showpost.php?p=54136358&postcount=11071

tldr: /system does indeed irrevocably lose ~100MB; f2f-tools outdated; gnex emmc not really suited for f2fs; upstream f2fs as used in this kernel inferior to Motorola's f2fs
[Samsung Galaxy Nexus] bsmitty83:
Have fun in Ireland buddy [emoji106]
[Samsung Galaxy Nexus] poo706:
Seems silly to want to maintain two builds when there's so little difference between them.

I'll keep doing it the CPA way, at least for now. I totally understand it, I spent a good part of the day on it, and you know, keep it in the LS fam-uh-ly. I really don't care about the method, just the end result. And I like the idea of keeping the LS kernel, for those that might actually want the stock kernel.

[poo]
[Samsung Galaxy Nexus] osm0sis:
We weren't really talking about the fstab issue there, but I completely agree. Unfortunately that's a ROM commit, and for some reason CM seems hesitant to let it through the Gerrit, and most ROMs don't like adding things until they have.
[Samsung Galaxy Nexus] bsmitty83:
Hello Everybody , Sorry its been a while ,, I've been really busy lately and havent had any time to do much . but I updated the op with 3 new kernels , as always let me know how they work for you , I'm stil especially interested in the reboot bootloop issue , if you experience it plz post it so I know what I did woorked or not .

I'm still around , will still be around , hopefully it wont be another month before a new update ......;)
[Samsung Galaxy Nexus] krweby:
Cool downloading now.
[Samsung Galaxy Nexus] Hetalk:
[MENTION=4608636]bsmitty83[/MENTION] I'm running latest RSR. I did try to reboot a few times and didn't see the google logo bootloop issue I had earlier.

I'll try again after few hours and see how it goes.

Thanks for the fix.
[Samsung Galaxy Nexus] sam45:
Seems to be fixed! Thanks, I hated that bug :)
[Samsung Galaxy Nexus] crazyeats:
Killed over half me battery rebooting with no bootloop. Running latest RSR. Good work.
[Samsung Galaxy Nexus] cujo6801:
And here's your reward for a job well done....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] Hetalk:
Nice gun.

Damn, I need to start kernelling :D
[Samsung Galaxy Nexus] thecoolkid:
Seriously? You're more interested in the gun? xD You are definitely meant for being a geek xD
[Samsung Galaxy Nexus] Oehr:
sweet! *installing*

any chance we can get updated recoveries so that encryption works? i really want to upgrade to f2fs^^

current one fails at "wrong password"
[Samsung Galaxy Nexus] a3361035:
We can forget fstrim. F2FS does not support FITRIM:

http://article.gmane.org/gmane.linux.file-systems.f2fs/1308
[Samsung Galaxy Nexus] ILA:
Yeah, but it should have TRIM... (but it doesn't work on any ROMs as well)
[Samsung Galaxy Nexus] demlv:
Newest DirtyV (7/17) working great except for the bootloop on reboot, which is still present for me. :(
[Samsung Galaxy Nexus] Punkiderma:
same for me.

slimrom weekly 6.4 f2fs, fsync ON
[Samsung Galaxy Nexus] EAK128:
The reboot issue is fixed for me running newest DirtyV and Slimkat, but ext4 and the official twrp recovery(2.7.1.0)

Great job as always bsmitty83
[Samsung Galaxy Nexus] demlv:
Still a problem here.... slim 6.4 ext4 with philz recovery.
[Samsung Galaxy Nexus] Hetalk:
That's cos I don't have a gun.
[Samsung Galaxy Nexus] a3361035:
What exactly do you mean and how did you come to that conclusion?

F2FS should notify one when mounting with discard option if not supported:

https://lkml.org/lkml/2013/3/17/15
[Samsung Galaxy Nexus] KreNtal:
Same here
[Samsung Galaxy Nexus] aditya.jazzmaster:
Me too
[Samsung Galaxy Nexus] Hetalk:
Strange. I've tried rebooting umpteen times on the latest RSR and havent seen a bootloop.

I'm on latest alpha paranoid.
[Samsung Galaxy Nexus] bsmitty83:
Strange indeed , hopefully now people will see how maddening this is for me . its not an issue for some but not others , makes it very tough to pinpoint the problem
[Samsung Galaxy Nexus] Hetalk:
Only thing I see is that I'm using RSR version of your kernel. Others might be using another version.

Did you forget packing something into one of these builds? :D
[Samsung Galaxy Nexus] Punkiderma:
Personally, I'm using smittyV. It seems to me that the bootloop problem occurs when the phone starts lagging: sometimes, my phone become a little slow and hotter than normal,so I reboot and often, in situation like that one,I got the boot loop issue
[Samsung Galaxy Nexus] aditya.jazzmaster:
Same problem like my phone.

I using AOSPA space & RSR version.
[Samsung Galaxy Nexus] ILA:
Simple google search... :) Look at this. Under the "Features"->"Implemented" it says "TRIM support". I haven't looked at the code behind F2FS yet, so please correct me if I'm wrong ;)
[Samsung Galaxy Nexus] crazyeats:
Bootloop back this morning on RSR with liquid
[Samsung Galaxy Nexus] a3361035:
Non sequitur. I don't think you do know what trim[1] is nor do random google searches disprove the words of actual F2FS devs.

[1] F2FS does support online discard, but not batch discard. That's still one kind of trim: http://lwn.net/Articles/417809/

===

Open F2FS questions:

A) Is F2FS really a good idea when Galaxy Nexus' eMMC FTL doesn't align with F2FS sections? (besides F2FS being experimental in itself) [1]

B) Why follow upstream F2FS instead of Motorola's when Motorola explicitly warns about upstream? [2]

C) Why is f2fs-tools outdated [Ver: 1.1.0 (2012-11-29)] in TWRP-2.7.1.1-f2fs-MAGURO, but F2FS itself latest? Upstream does not recommend [3]

D) Does fs_mgr's e2fsck work with F2FS? (besides F2FS' fsck not being able to repair anything) [4]

E) Mount options:

E.1) Why isn't inline_data set? Don't see the harm [5]

E.2) background_gc=on is default, why is it explicitly set?

E.3) Why is active_logs=2, when the default is 6 and F2FS documentation emphasis efficient cleaning using multi-head logs?

F) Are there any reliability tests?

G) Are there any robustness tests?

[1] https://www.kernel.org/doc/Documentation/filesystems/f2fs.txt

>cat /sys/block/mmcblk0/device/name
VYL00M
>cat /sys/block/mmcblk0/device/preferred_erase_size
524288

[2] http://xdaforums.com/showpost.php?p=51565669

[3] http://git.kernel.org/cgit/linux/ke...N?id=dd1ba078fae270c4174a221a873026fea85aae32

[4] Like:

>dmesg
fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
e2fsck: /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata: clean, 17263/887696 files, 639160/3549691 blocks

[5] https://lkml.org/lkml/2013/11/10/48
[Samsung Galaxy Nexus] ILA:
Thanks for the usefull links, it will be a good read :)

...and please don't assume things you don't know about me, mmkay? Nobody is trying to disprove anything nor anyone :)
[Samsung Galaxy Nexus] midnightdevil66:
No bootloop issues for me on SmittyV

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dezful:
Google logo bootloop on restart still persists on DirtyV-URSR { 7/17 }. Also, I got SOD once on this kernel version. :)

F2FS, LiquidSmooth, ART, Suspend trim checked (synapse).
[Samsung Galaxy Nexus] crazyeats:
How long you been running latest Smitty? I had no reboot issues on dirtyRSR till after a full day of use.
[Samsung Galaxy Nexus] midnightdevil66:
Since yesterday....

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] demlv:
To be clear, those of us with the problem are not experiencing spontaneous reboots. Our phones end up in a bootloop at the Google logo when we manually reboot them.
[Samsung Galaxy Nexus] crazyeats:
Agreed. Not a single freeze or crashed reboot. Just when I intentionally reboot the device. IMHO its a very minimal setback on an awesome kernel. I can live with that. Makes this old gnex a new machine.
[Samsung Galaxy Nexus] EAK128:
People having bootloops on reboot, maybe try switching to the official twrp recovery and test if it's still bootlooping for you.
[Samsung Galaxy Nexus] crazyeats:
As far as I know the official twrp for the gnex doesn't support f2fs. I could be wrong
[Samsung Galaxy Nexus] krweby:
The issue has been around since the kernel after 4/19. So it was before f2fs was introduced to the equation. And I'm still on the standard twrp and having the issue.
[Samsung Galaxy Nexus] EAK128:
It doesn't. Just thought it might be recovery related for some that are still having bootloops.
[Samsung Galaxy Nexus] demlv:
I tried official cwm official twrp and now philz. Bootloops on all three. Not complaining. Still love the kernel. :)
[Samsung Galaxy Nexus] bsmitty83:
The only clue I have to work with on this reboot issue is that it affects only some and not others . idk what that means but its a start. I'll see if I cant figure it out . its really tough for me because it doesn't happen at all on my nexus
[Samsung Galaxy Nexus] pvkiniyan95:
i think people claiming reboots should post their complete settings coz i noticed changing the I/O scheduler to anything else other than zen is hard and changing rab more than 512 in Zen is pain in the a** for me. I cannot change my Governor or overclock it. The stock settings are perfect any changes to it gives a reboot to me. Vanir never works for me now, i m stuck with FML ....being a flashaholic, it hurts

one thing for sure, the ART almost killed me...the overheating during optimisation it caused made the cell network reception terrible, i can only get 3 bars while my bro on the same network gets full
[Samsung Galaxy Nexus] LibertyMonger:
I have never been able to run any of these special kernels everyone raves about. A.S.K.P. or any except for a few basic ones like Franco. Every time I try one that everyone else seems to love I get freezes and reboots.
[Samsung Galaxy Nexus] bsmitty83:
People aren't getting random reboots or freezes , its when they reset their phone , it bootloops . but not for everybody .
[Samsung Galaxy Nexus] pvkiniyan95:
yeah, those resets stops synapse from restoring the settings, the workaround is to power off instead of rebooting either in recovery or adb
[Samsung Galaxy Nexus] namtombout:
Only time I got the reboot bug was after I lowered the regulator voltages and rebooted while the phone was charging.
[Samsung Galaxy Nexus] krweby:
It is when you have the phone reboot from the menu. If you shut the phone down then power it back on it isn't a problem. I have a toro not sure if the others having the issue are on a different model.
[Samsung Galaxy Nexus] nonoperez:
Not a single problem here, just speed and smoothness.

Latest PA and Dirty.
[Samsung Galaxy Nexus] santi1993:
No soft reboots reported?

Sent with love [MENTION=887416]tap[/MENTION]a
[Samsung Galaxy Nexus] cujo6801:
Ever since I installed smittyV 7/17....

When I reboot my phone...

It spits on me then says

You like that don't you *****..

Sent from the "DOG" pound
[Samsung Galaxy Nexus] dlabadie:
Same here - boot loop on reboot on toro using any of the 3 kernels.
[Samsung Galaxy Nexus] warlock9_0:
Latest aokp + SmittyV and no bootloops yet
[Samsung Galaxy Nexus] GilGameshn1:
I can say people that have toro experience it more ... Could be related ... Maguro and not a single issue to report .
[Samsung Galaxy Nexus] poo706:
I've certainly had it plenty on my toroplus.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
I should have a test version soon , I might have found the culprit maybe
[Samsung Galaxy Nexus] Reinvented:
It's probably because you went with Sprint.
[Samsung Galaxy Nexus] poo706:
Yeah, I'm sure that's it.

[poo]
[Samsung Galaxy Nexus] Reinvented:
Had a Toroplus a little while back,

never. again.
[Samsung Galaxy Nexus] poo706:
I was being sarcastic. Any issues I've had with this phone is not because it's a sprint model.

[poo]
[Samsung Galaxy Nexus] Reinvented:
I was sarcastic from the beginning as well :) :highfive:
[Samsung Galaxy Nexus] wisefreakz:
Guys, since Vanir is taking too long for updating, and past 7 nightlies didn't feel good for me, which ROM do you guys recommend?

Cheers
[Samsung Galaxy Nexus] amd_h4x0r:
definitely try LiquidSmooth http://xdaforums.com/galaxy-nexus/verizon-develop/rom-liquidsmooth-v3-1-kitkat4-4-3-toro-t2575560

or one of [MENTION=3927368]poo706[/MENTION]'s unofficial builds http://xdaforums.com/galaxy-nexus/verizon-develop/rom-liquidsmooth-v3-1-toro-t2793284

EDIT:

Maguro versions

http://xdaforums.com/galaxy-nexus/development/rom-official-liquidsmooth-kitkat-4-4-3-t2667078

http://xdaforums.com/galaxy-nexus/development/rom-liquidsmooth-v3-1-maguro-toro-t2793275
[Samsung Galaxy Nexus] wisefreakz:
Thank you... I see both are for toro. Will search the maguro variant.

Cheers
[Samsung Galaxy Nexus] poo706:
There's maguro for both.

[poo]
[Samsung Galaxy Nexus] amd_h4x0r:
edited my post above with Maguro flavors :)
[Samsung Galaxy Nexus] osm0sis:
Just popping in since this hostel Wi-Fi is badass. ;)

The fstrim command works with f2fs on Linux. This is a fact. Meaning it should also work for Android, we just don't know why it doesn't yet. That's why [MENTION=4015637]rkpeterson[/MENTION] was asking.

As for the rest.. [MENTION=2838735]aosp[/MENTION] [MENTION=4608636]bsmitty83[/MENTION]

P.S. We all probably caught herpes from the Blarney Stone today. :D
[Samsung Galaxy Nexus] cujo6801:
I hope you're having a great time bro...

Sent from the "DOG" pound
[Samsung Galaxy Nexus] pvkiniyan95:
guys ramdisk is not supported in 4.3.1 right???? coz i m planning to convert a good 4.3.1 rom to f2fs and see how it works.....afaik dirtyV, burstalarm, fml, fancy are f2fs compatible but all of em uses ramdisk...just need confirmation b4 i waste my time
[Samsung Galaxy Nexus] bsmitty83:
Anyone with the reboot issues please try this kernel and let me know if it fixes it or not , if you dont have the reboot issue then no need to flash this , as it is identical to the last SmittyV minus some changes to get rid of the reboot bootloop
[Samsung Galaxy Nexus] a3361035:
Stupidly repeating it, does not make it true.

The fact remains that two of Samsung's core F2FS devs said ~3 weeks ago that fstrim does not work. [1]

Claiming otherwise would need extraordinary proof.

[1] http://article.gmane.org/gmane.linux.file-systems.f2fs/1308

===

Moto G (F2FS on /data) and Moto G GPE (ext4 on /data) were unified in CM through swapping fstab at init:

https://github.com/CyanogenMod/andr...mmit/b28c24cb2d1ff3744d34c8811d4632019c5188ea
[Samsung Galaxy Nexus] thoiloidainhan:
If you have proof to say otherwise then just post it. No name calling here. Don't turn this awesome thread into another war zone. Or u can just go back to your cm11 thread where u do most of the posting last time I checked. Peace

PS if its not obvious yet I pressed thank by accident
[Samsung Galaxy Nexus] chongns:
i think here is a more suitable thread for your question. that is the thread Gelaxy Nexus's f2fs starting to glow. get back here to post your result or your finding once you have anything to help on developing this kernel.

thanks in advance. :fingers-crossed:
[Samsung Galaxy Nexus] AgentSmith:
Just switched from dirtyv-sr to smittyv but I didn't regain 1080p recording in camera. Is this normal behavior?
[Samsung Galaxy Nexus] Unzitron:
Wipe data and cache for the camera. That should fix it.
[Samsung Galaxy Nexus] sergialess:
Hi. With the SR version I'm not able to record video at 720p. The camera app freezes.

Cache and Data wiped, but no luck here. Thanks anyway for this fantastic kernel.
[Samsung Galaxy Nexus] Marco618:
Sometimes i get a crash that says "system.ui has stop wotking" is that a kernel problem?
[Samsung Galaxy Nexus] nonoperez:
Same here

Same here, I returned to DirtyV standard version.

Using PA with google camera app.
[Samsung Galaxy Nexus] sergialess:
Could you do a test?

- Start recording a video

- During recording, touch the screen to take extra pics.

- Stop recording.

- Go to gallery, review the pics. For me, all pics are corrupted.
[Samsung Galaxy Nexus] nonoperez:
Yes, all green, but I don't really use this feature. It's a known bug.
[Samsung Galaxy Nexus] bsmitty83:
Anyone with the reboot issues please try this kernel and let me know if it fixes it or not , if you dont have the reboot issue then no need to flash this , as it is identical to the last SmittyV minus some changes to get rid of the reboot bootloop

http://xdaforums.com/showthread.php?p=54296838
[Samsung Galaxy Nexus] osm0sis:
I appreciate the up-to-date information, but drop the attitude please. I recalled someone posting screenshots of it working on their Linux box but not in their phone back when we first started experimenting with it; apparently I was (or they were) mistaken, and I have no problem admitting it.

As I asked you previously, since you're clearly so passionate and motivated on the subject, go do all the f2fs tests you keep demanding and come back when you have some results to post.

Cheers from Galway. ;)
[Samsung Galaxy Nexus] massoudsh:
I use dirtyv-UR 7/17+Vanir 7/13 converted to F2FS and haven't any problem. All things are fine for me, no sod, no reboot & no boot loop.
[Samsung Galaxy Nexus] krweby:
Been running it for a day now. No problem yet. But last time I think it was 3 days running it and running Google music for two hours straight before it started. I'll let you know.
[Samsung Galaxy Nexus] AgentSmith:
Had tried that already but it doesn't work hence the question. :) I'm on a fairly recent CM nightly.
[Samsung Galaxy Nexus] Punkiderma:
Nothing, still have bootloop issue.

From system, I restart to recovery and I get into bootloop.

Also, while before I just needed to keep volume buttons pushed and then boot to system or recovery to end bootloops, now it doesn't work like this anymore.

If, from bootloader menu, I select recovery or system, I get into bootloop again.

The only thing I can do is enter into bootloader menu, select power off, then switch the device ON again.