yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
I stand corrected my mistake
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] arter97:
I'm directly in talk with the head of f2fs with various f2fs related issues, most recent one being GC.

He agrees improvements should be made with Google's solution and he's in the process of coming up with new patch-sets.

Until Google fully figures out optimal GC maintenance settings, I strongly recommend every kernel developer to pick my rapid GC.

(FYI, the GC issue doesn't matter much on which f2fs version you're using.)

You will encounter a major hit on write performance after a few weeks/months of usage if you don't use rapid GC(unless you use your phone really lightly).

Check /d/f2fs/status with uptime of about 3 days with my rapid GC and Google's.

It's a stark contrast.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey :)

Thanks for chiming in here.

In order to fix two kernel warns I returned to stock f2fs plus f2fs stable patches from the f2fs stable git. While doing that I reverted rapid GC on my kernel.

I´ll plan on reintroducing it soon, but I´m taking things slow, one at a time.

Thanks for your work on that matter and the insight provided here. Usually my phone has no uptime of 3 days but I noticed it´s not yet ideal on pixel 3. Again thanks for your insight!

Have a nice day and keep up your work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NOTilyass:
Is there any noticeable performance boost with f2fs ?! App opening ? Game smoothness ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
More reasons to hate f2fs :rolleyes:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
this

i personally wasnt a fan of F2FS

with correct mount options i believe EXT4 can be more efficient / durable

would you be considering introducing arter97s rapid GC? maybe as a test build to see how it compares to stock?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] arter97:
Yeah I agree the road's a bit bumpy, but I think it's worth it.

ext4's journalling overhead is a lot worse than lfs overhead of f2fs, so it's a bit forgiving if you think we're just deferring journalling overhead to GC.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
one of the first things i did on my ext4 devices was remove journaling all together, it never showed signs of slowing down or corrupt files, also removing barriers helped, for others, the journal was on writeback mode (those who were afraid to remove journal all together)

i wonder how EXT4 with no journaling would compare to F2FS? it feels as though my pixel 2xl with EXT4 and no journaling was snappier / faster than my 3xl.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] arter97:
lmfao.

Your device will be so f***ed up when you have random reboots / have to forcefully reboot.

Why don't you use ext2 while you're at it?

Even if you do all that, it'll still be slower and less efficient than f2fs.

The ext4 vs f2fs argument is pointless. f2fs already won. It's just a matter of time for other OEMs to adopt f2fs.

f2fs is already enforced for Android Go devices.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
That is not a clever thing to do. Actually, why?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
Even though it clearly has stability issues... ext4 never screwed me over, but f2fs has corrupted data on me before. Google forcing fsck on boot is also pretty concerning, and makes it seem like the whole f2fs stack is delicately held together with duct tape.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] arter97:
This all varies from person to person I guess. My ext4 experience was horrible on various Linux devices including my servers to desktop and mobile. I use xfs when stability is the biggest concern.

I had corruption issues with f2fs only on the early days. I can't remember f2fs corruption in recent days, so I think you should be fine.

Regarding fsck, it makes sense. The kernel records to the superblock about corruption. The "-a" option from fsck.f2fs means it'll only fix corruption that the kernel recorded.

IIRC, ext4 is doing the same. It's just that fsck.f2fs is more verbose and the boot log is kinda ugly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
i never had random reboots or have had to force reboot, i never ran custom roms just stock roms with magisk.

i kept regular backups so the risk was worth it to me, i have forcefully rebooted my device a few times before because i was curious as to what would happen and everything was still working fine, only once i had lost a .txt document i was working on, it lost the last few lines but the original document was still intact

also im sure you know ext2 and ext4 have difference features, not only journaling...

i dont have hard data to back up my anecdote, but yes i definitely notice my pixel 2xl is smoother slightly faster than my 3xl (my 2xl is stock with no barriers and no journaling), but this might have to do with something else.

i have also had my oneplus 6 formatted f2fs and it was considerably slower than ext4, but again it might have to do with something else.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NOTilyass:
I still get horrible lag on the lockscreen !
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Clean flash stock ROM > Problem solved.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kdrag0n:
The problem will return within a week or two.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
Not if he clean flashes this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kdrag0n:
It's awfully tempting. Are you over the edge yet?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
april patch, and april sultan kernel

this phone feels like a oneplus 6T now.

everything is so snappy.

great job [MENTION=4800121]Sultanxda[/MENTION] you finally got right what google couldnt.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rwolf91:
couldn't agree more.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Gordietm:
I'm on stock and flashed this kernel directly over Proton kernel. No problems, however Wireguard is not connecting properly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] blaze9090:
How Do I do that?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zx2c4:
Can you export the wireguard log (settings-->export log to file) and send it to team *at- wireguard d0t com?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
flashed over proton as well, no issues
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hilla_killa:
Does magisk have to be flashed after, or does kernel preserve magisk?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dukat0s:
Flash kernel , then magisk :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] JeromeLeung:
Seems like the selfie camera isn't working. Is it just me?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] peikojose:
Happens here too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] keaheng:
Camera works fine here
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
Could you give a log (dmesg)?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] JeromeLeung:
Let me know if this isn't the right log
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Reno and bbr? Give me a break dude.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
what's this about?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Hahaha. Figure it out bro. I will give you hint. TCP. I'm using Reno now cause default bbr blows
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bbender716:
Same.

---------- Post added at 12:45 AM ---------- Previous post was at 12:44 AM ----------

Give Sultan the benefit of the doubt, man. I'm sure he'll be incorporating more features / improvements soon. I'm just happy he has this up for our device.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
I'm sure he has his reasons. That doesn't mean I have to agree. TCP depends where you are. And a host of other criteria that I won't get into here. Google choose CFQ for a reason.

Edit : I give no human the benefit of the doubt. Even the Sultan of Swing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bbender716:
I hear you. However isn't cfq a scheduler, not TCP algo? I believe Google's default is Cubic iirc.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Yes, my mistake. See, we can work together. Lol. I'm just testing you. Cubic FTW
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bbender716:
Lol nice. Agreed on TCP for the most part although I've had better success with Westwood+ but Cubic is a close second.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] zx2c4:
Please point to precise research justifying your quasi-inchoate demands for various TCP congestion control algorithms. There are plenty of papers proposing new congestion control algorithms, but research into what's best on mobile networks using the algorithms available the Linux kernel is a bit harder to find.

Back in 2013, Alfredsson-Del Giudice-Garcia-Brunstrom-De Cicco-Mascolo argued that Westwood+ was the best all around algorithm for cellular networks in terms of bufferbloat and low latency with multiple flows. That was then. But more recently, in 2018, Atxutegi-Liberal-Haile-Grinnemo-Brunstrom-Arvidsson argued that BBR was a good choice for generally low latency networks, such as well performing 4G and 5G flows or operators with particular queue configurations, while NewReno sometimes performed well under other higher latency situations. Most significantly, in 2017, Fi-Chung-Jiang compared Cubic and BBR on Verizon's network while moving on the highway and concluded that without a doubt BBR gave favorable performance. Drawing on their conclusion, it would seem that BBR might be a fairly decent choice, but hey, we're quite possibly wrong.

I'm all ears to hear differing opinions, but please cite your sources so that I can read the paper/blogpost/whatever. Otherwise we'll start flagging misleading or unsubstantiated posts that don't add anything to the discussion.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
It was amazing smooth on March 27, but i did start to notice very micro stutters. Looking forward to trying April update + kernel :D.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Shutters/lags still exist:(

Stock Rom + 2nd April build
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
yea i notice some microstutters but it doesnt affect apps opening or anything, its just the animation.
[MENTION=4800121]Sultanxda[/MENTION] are you considering adding arters rapid GC?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
[MENTION=4800121]Sultanxda[/MENTION]

Given the news here, is your bluecross/crosshatch kernel officially deprecated, and will not be receiving anymore updates past 4/2/2019?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] avetny:
What the F !!!!! Back to pixel 2XL ????

I hope that post is April Fool's !
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
It isn't.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] avetny:
Wow !!! Whatever..... disappointed
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
Yeah. I'll put EOL in the thread title.

There are other kernels you can use ¯\_(ツ)_/¯ This kernel actually has very few users.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] avetny:
Forget about kernel. Its about very, very serious guy leaving us.

Im gonna switch to iOS.???
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
You could switch to 2 XL ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
A wise advice.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] avetny:
855 is outside having fun. Im using 845 just because of you and franco. Please don't make me go back to 835 sultan ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
835 so nice though
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] avetny:
Absolutely agree, is polished to hell !!!!! But gpu no matter what is not that good? plz don't leave us
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] :
"the specs !!!!!"
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
I see you also had problems quoting avetny's messages. XDA is high quality :silly:

What are you doing with your phone that isn't enough for the 835's GPU? Also, 2 XL is so cheap; I ordered a 128GB 2 XL off ebay for $276. It's really a steal considering I paid 4x more than that for my 3 XL...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
noo why are you leaving pixel 3 xl? :(((( don'tt
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
what happened sultan?

that was a short run..:(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
What really pushed me over the edge was some recent update from Google that caused all the stuttering that I haven't been able to fix. Even when using a kernel other than my own, my "flagship" phone frequently stutters extremely badly when I use my device normally (e.g., I frequently get bad stutters when switching between apps). My Pixel 3 XL did not stutter like this when I first got it, and many others with a Pixel 3/XL are reporting lag issues as well.

This recent issue is not the only reason I'm giving up on this phone though. Here are my other major issues:

-Several times a day, my mobile internet connection dies while my phone says it is still connected to LTE. This means that sometimes when my mobile internet dies while the phone is in my pocket, my phone won't think that anything is wrong and it will stay disconnected until I take out my phone, realize that mobile internet is dead, and cycle through airplane mode to recover. My mobile network connection actually died while I was writing this...

-There appears to be some phantom battery drain issue that drains through the battery quickly even when the largest power consumer, the CPU, is asleep. This is probably caused by some peripheral draining more power than it should be or a peripheral that is not properly sleeping when it's supposed to. I first noticed this a few days after I received my 3 XL and left it on my desk powered on overnight with nothing installed on it (and without it being connected to the internet). The battery lost a significant amount of its charge by the time I looked at my 3 XL in the morning. To contrast this, after I stopped using my 2 XL, my 2 XL sat on my desk powered on for a couple weeks before its battery was drained.

-The Pixel 3/XL's glass body is one of the most ridiculous hardware designs I have ever seen. The back of my friend's 3 XL shattered when he dropped it. Phones made of aluminium and plastic don't do this, and have the added benefit of not making phones weigh a metric f*ckton. My 2 XL feels like a sturdy feather in my hands compared to the delicate brick that my 3 XL is. I thoroughly hate phones made out of glass and I hate ceramic phones even more.

-The use of f2fs when it clearly still suffers from performance and stability issues is infuriating. If my data gets corrupted or my f2fs partition's performance crumbles due to the lack of garbage collection or some other issue in f2fs, then it doesn't matter to me how fast f2fs is. I just want my phone to work.

-Although I'm not affected by the Pixel 3's screen flashes, the fact that Google has not fixed such a prominent hardware issue several months after the device has been released is very upsetting. If my 3 XL has hardware issues, I definitely cannot count on Google to fix them.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I understand your frustration. As for loss of network, I haven't had this at all. I believe it could be hardware related? Since you didn't experience this on 2 XL, so its not carrier related. I use strong case protection lol, I am used to dropping phones, so for me thats what it is.

Well, I hope you reconsider and return :(. I unlocked bootloader and rooted because of this kernel only. I did notice some lag and stuttering in April. I was going to report that when I have apps that require more memory, the phone does freeze and i have to clear everything for it to work.

My Galaxy S8, never ever gave me performance issues like this tbh. And this is Samsung UX we're talking about. It has been more smooth and lag free.

I can't afford to change phones or anything :(. But thank you for your contribution and everything. It is greatly appreciated.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Lots of people using ur kernel but they don't reply the thread. If you could fix the shutters, I think at least 50%people will stick to this kernel:svetius:

Thanks for your hard work anyway
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
[MENTION=4800121]Sultanxda[/MENTION] really going to miss this kernel

i did notice that the stuttering and lag reduces greatly after one day of usage (i.e if i dont restart for a day or so) and it becomes faster without stutter

really hope you reconsidering killing your kernel

its one of the reasons i unlocked, ive used most other kernels but i keep coming back to this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
If I sell my 3 XL for $650, then I'll end up with more than half of that left after buying a 2 XL for $276. Pretty affordable "upgrade" :silly:

I don't know what's causing the stutters, which is part of why I'm giving up :/ It's not caused by any change I've made.

I get stutters consistently no matter how long it's been since I've rebooted my phone.

If I wanted to keep this kernel alive, I would need to keep my 3 XL, which is worth around $650. That's a lot of money to throw away for a device I don't want to use. I plan on selling my 3 XL as soon as my 2 XL arrives.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] arter97:
[MENTION=4800121]Sultanxda[/MENTION]

Just out of curiosity, go run Androbench once.

I have a feeling f2fs tuning is responsible for your lagfest.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
Screenshot attached.

FWIW, I still had lags with a kernel that had your f2fs GC patch.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] arter97:
Yeah your I/O seems normal.

That's unfortunate :/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
I'm pretty sure it's a scheduling issue anyway. Finding and fixing the issue is beyond what I'm willing to do for a phone I shelled out $1k for though.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
That is a great resale value for now! I paid $870 CAD from google store, which is $650 USD based on current exchange rate. But, selling S8 and S9 covered me. pixel 2 xl screen is LG, and it is horrible for me.

However, thank you for everything! I am gonna miss this kernel!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
I've got a 128 GB model; I'm guessing you bought a 64 GB one.

Pixel 2 actually has an excellent screen, but I don't like small phones or small batteries.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] billyt1:
Yo mine always dropping signal like that two I thought it was just a Google Fi thing itll have full lte and I'll have to switch to US Cellular using the fi codes To get signal and when I do switch my cell number changes to some weird 516 number then I'll call a contact in my phone and some random person will answer and to beat it all if I'm bluetoothing Pandora to car radio and it loose it's singal I have to turn Bluetooth off back on turn radio off back on jus to get back synced
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
yup

wasnt really happy with any other kernel other than Sultans

so ill be wiping, locking my BL and flashing Android Q

Edit

Scratch that

I miss root too much

Guess this month I'll be on sultans until May comes out then I'll have no choice but to jump ship if he quits development :sadface:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Is anyone who is experiencing lag using non stock gestures?

I was using fluid navigation

I uninstalled it, and went back to stock navigation bit use the launcher attached

And phone is responding much better

Can someone confirm?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
I'm using one plus gestures and always have so I don't know if stock relieves it .

Does sultan use non stock gestures too because he's having the same issues
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
I don't use gestures.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Any gesture application that uses Accessibility services will make your interface lag, period. Try GMD gestures.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Oh...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NOTilyass:
Did you leave the 3xl development for good ?! Maybe waiting for Q performance improvements ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Sultanxda:
Yep, left for good.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] NOTilyass:
is the 2XL noticeably smoother than the 3XL ?? I'm curious how many differences did you notice going back to 2xl ?!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
My girlfriend says something similar... [emoji6]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ram4ufriends:
https://xdaforums.com/pixel-2-xl/development/kernel-sultan-kernel-t3802152/page79
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RogerF81:
Then you're really lucky, at least in Germany, you have to pay at least $100 more for a 2XL :/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
Because of all the stupid **** that EU is forcing upon the European countries, yes..
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] aydinbahadir88:
Ends in bootloop after flash this Kernel

AOSiP ROM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Meowdib:
It's EOL after all :p
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RogerF81:
Yeah, so true. But even second hand devices are that expensive, considering it's a 1,5 year old one.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kevindriod:
Thanks for providing.

There are several errors while building this kernel from your source code. One of the errors is about Wireguard.

https://github.com/kerneltoast/android_kernel_google_bluecross

Does it require an extra setting for building the kernel, or is there a guide for this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kdrag0n:
The problem with BBR as it is in this kernel is that it doesn't have a functional pacing implementation. BBR as of 4.9 is supposed to be used with the FQ qdisc because it provides pacing, but FQ has its own issues that make it non-ideal, e.g. microfreezes. BBR cannot properly operate without working pacing because the pacing rate is its main controlled parameter (source). Upstream has had a pacing implementation directly in the TCP stack since 4.13 which solves both issues and could potentially make BBR the ideal mobile congestion control algorithm for most cases as per ReBBR, but this commit has not been backported to 4.9 as far as I can tell.

I've yet to get this working in my own kernel as the speed drops to 0.10 Mbps at most and 0.02 on average after backporting it and reviewing each change several times, so I've stuck to Westwood+ as the default TCP congestion control algorithm. It'd be great if someone more knowledgeable (including you) could attempt to backport this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] avetny:
Flash stock boot img (do not reboot)

Flash TWRP

Flash sultan kernal

Flash Magisk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] cjx11111:
Im in stock rom！

Flash sultan kernel

Flash magisk 18.1 r17

and reboot to the system！

and just cant reboot to twrp anymore！
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Donric13:
Did you flash stock boot? So you have to reflash twrp. Now you may need to boot/flash twrp through fastboot.