yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] DanielF50:
Go to Settings, About phone & tap on "Android version" to check if you're running "5 March 2022" under "Android security update" and "SP2A.220305.013.A3" under "Build number", if those show anything else then you're not running the March stable update and shouldn't flash the March kernel. Any update AFTER March 2022 is 12.1 (12L), but you should only flash the kernel pertinent to your particular build.

Not to be rude, but if you don't know which update you're, or how to check it, then you probably shouldn't be flashing a custom kernel in the first place. I get that we all start somewhere, but the first port of call for modifying something is to learn how to use it, how it works, and assessing what you want to achieve.

-------

Please advise is this isn't the correct thread to ask this, but thought it relevant as it's regarding the Direct USB Access feature that freak07 ported to the March kernel, so should hopefully reach more users with experience of this feature, in this thread.

Has anyone actually had Direct USB Access working for anything other than DAC? I've tried to use it to plug my USB ODBII scanner into two separate vehicles using AndrOBD & although it seems to be able to recognise and connect to the device, it doesn't transmit any data - this worked on my old phones, but not on the Pixel 6 Pro, so I'm just wondering if Google has only partially fixed Direct Access in QPR 1.1, or if something's just funny my end. Thanks!
[Google Pixel 6 Pro] thieftime1980:
I have installed ProtonAosp Rom and want to install this kernel but I have bootlop every time what am I doing wrong?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Got any Magisk Modules installed?

Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can reenable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
[Google Pixel 6 Pro] thieftime1980:
I do not have any modules installed, first I wanted to install the kernel, but every time I stocku and on costum rom I have a bootlop already
[Google Pixel 6 Pro] Freak07:
april update is out. :)

no source update pushed from google yet. I guess it´ll happen in a few hours when I´ll be asleep.

I went ahead and flashed the latest release for march stable kernel without any issues so far.

If you can´t wait, it should be fine to flash based on that short experience.

If you want to be absolutely sure there will be no issues due to incompatible source/firmware, I´ll try to update the kernel with any new potential changes in the source for april as soon as I find time, which will hopefully/probably be tomorrow if everything goes as expected. :)

I wish everybody a great day/evening.
[Google Pixel 6 Pro] Lughnasadh:
Stock kernel on April update is still 5.10.66. Was hoping they would bump it up to 5.10.102 for the dirtypipe fix. Since from what I've heard Google doesn't like backporting that much ("from what I've heard"--could be totally wrong about this. Saw a writing from Greg Kroah-Hartman from Linux alluding to this), guessing the dirtypipe fix isn't in this month's build, built I'm sure Freak07 will let us know, as usual.

We're very lucky to have him around to keep our pipes clean 🙃
[Google Pixel 6 Pro] kiekan:
Question: Is the haptic strength tied to a kernel driver or something in the rom? If the former, would it be possible to try and restore the P6P's haptic intensity back to the pre-March strength? The more subdued haptics that have been introduced in the March update are not especially effective.
[Google Pixel 6 Pro] Freak07:
I see what you did there :cool::D

While the kernel doesn't necessarily needs to be bumped to 5.10.102 to include the fix as the commit was merged separately to a few branches already, there's confirmation now. :(

Source for April dropped, it's not included.

https://twitter.com/i/web/status/1511069563441528833

Next update will allow adjusting vibration strength back to higher strength via the CleanSlate config app, thanks to @tbalden 's relentless work! :)

Alright I'm off for today. See you all tomorrow!
[Google Pixel 6 Pro] Ghisy:
Hey, does the CleanSlate app only have a paid version? Or is there a free version as well?
[Google Pixel 6 Pro] roirraW "edor" ehT:
From the CleanSlate thread in this section (free versions at bottom):
[Google Pixel 6 Pro] Nemuritor01:
Hi, I was one of the first guys to report this issue, with DAC problems.

I've had the Beta installed on my pixel 6 pro, few weeks ago. When I tested it, it did not work properly, as far as I can state:

- Yes, Hibby App played music, but just phones native (processed) sampling rate. Most tracks just 24/48

Before the BeTaa Rom Hibby did not play music at all.

- USB audio Player pro played no music. Still error message.

- Neutron similar as Hibby App

So from my point of view, it a progress, that some apps play music, but I do not believe they really make use of the DACs full capabilities.

At least kn my devise. Few weeks ago (before I read this article) I switched back to the stable ROM, because of battery drain issues with the beta ROM. So I can not test right now.

Can you check if the apps are playing the correct bit rates?
[Google Pixel 6 Pro] swieder711:
Running April update with Root using Magisk 24301 and Kiris 2.0.1.

All is good.
[Google Pixel 6 Pro] Lughnasadh:
For what it's worth, thought you and others might find this interesting if you haven't seen it yet.

"Samsung, on the other hand, seems to have patched the Dirty Pipe vulnerability on its affected devices with the April SMR (security maintenance release)."

April Security Update Doesn't Fix Dirty Pipe Vulnerability... Or Does It?

Google has released the April 2022 security update to its Pixel phones but it doesn't seem to have patched the Dirty Pipe vulnerability.

www.androidheadlines.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks @Freak07! Now patiently waiting for AFH to quit the spinning "Searching for mirrors...". 😂 (both in Chrome on Windows and on Android)

Edit: I Control-F5'd and it loaded almost immediately on the PC.
[Google Pixel 6 Pro] awakener777:
Of course I just updated Magisk prior to installing April update 😆
[Google Pixel 6 Pro] scott.hart.bti:
@Freak07 fantastic work as always. Thanks for the quick update. You are always on top of it.
[Google Pixel 6 Pro] a63548:
@Freak07 You are simply amazing! Thank you so much for such a wonderful kernel. Also just a heads up the thread date still is for March I think instead of April :)
[Google Pixel 6 Pro] bigJbig:
Sorry if it is off topic.

I am on the April patch and using Kirisakura latest 2.1.0 kernel. Bank Apps detected root. I have config Denylist, rename the Magisk App, and even frozen it. However, bank apps still detected root. When I flash back to the stock kernel or CleanSlate, bank apps work fine and can't detect root.
[Google Pixel 6 Pro] Freak07:
Your best bet is to flash back the beta and submit the feedback directly to Google if it´s not working as expected.

It´s on Google to add proper support for that. Once proper support is added apps might need to be updated to work correctly on the Pixel 6 since it´s kind of a "new" SoC.

You can let the UAPP devs know on their forum that Google started adding support on the A12L beta and see if they can start working on it.

It says 44kh/16bit during playback of a flac downloaded from bandcamp when using my dragonfly DAC via hiby.

It´s interesting that Samsung pushed ahead there and also great to see that some OEMs take the initiative and push ahead of the Google bulletin there.

I know for example that HTC in the past was pretty much up to date with security fixes ahead of the "official" android security update fixes.

But it requires testing and more resources to diverge so most OEMs are just happy to stick with whatever Google provides.

I checked the kernel build date of stock April kernel yesterday. It dates January 21st, the fix for dirty pipe was pushed February 20th to Linux.

https://twitter.com/i/web/status/1511412061582024709

The kernel has nothing to do with an app detecting root, at least I didn´t hear of any app that would check anything there. Are you sure it´s not just the reboots that fix it temporarily while flashing back stock?

Google pay works fine for me on my end and safetynet is passing as well.

Did you try flashing the universal safetynet fix to make sure you´re passing safetynet as well?

If your specific banking app really detects something that´s unique to my kernel it might be hard to fix. You can tell me which app and I can test on my end too if it´s available for download here. But if it requires a login to fail, you might need to check the logs.
[Google Pixel 6 Pro] bigJbig:
Thank you for your reply.

Yes, I flashed universal safetynet fix and it is

passed. Gpay is also working fine.

The bank app is call HSBC and CITI BANK.
[Google Pixel 6 Pro] slickrasta:
This won't work on my Pixel 6 updated to the 12.1.0 April update, always gets stuck in boot loop. I'm manually flashing 2.1.0 after installing powerhint v9 and patching the boot.img using Magisk stable 24300 when that failed I tried 24305 as well. Downloaded multiple times, patched multiple times. After I flash all 4 files using the commands below it just gets stuck in a boot loop. I even tried flashing the 3 files before vendor_dlkm and vice versa, no luck. I'm very confused why others report no issues. Can someone help me?

adb reboot bootloader

fastboot reboot fastboot

fastboot flash vendor_dlkm vendor_dlkm.img

fastboot reboot bootloader

fastboot flash dtbo dtbo.img

fastboot flash boot magisk_patched.img

fastboot flash vendor_boot vendor_boot.img
[Google Pixel 6 Pro] Lycidias:
Thanks 🙏 new build is working awesome on raven April update ☺️
[Google Pixel 6 Pro] spr33:
Just wanted to double check that the latest release works on the L beta before flashing?
[Google Pixel 6 Pro] shizonic:
I have exact the same situation! With stock kernel everything works including my bank app. If I flash the kernel 2.1.0 SafetyNet passes still, but my bank detects root and won't open... I tried everything... Including clearing files of Google Play Services, multiple reboots, etc.

My bank app is "PostFinance". But I saw that the "Xiaomi Home" detects root too even if the app opens... It just gives a short message which says that root was detected.
[Google Pixel 6 Pro] daniel.1983:
Same here, my bank app is VR SecureGo plus. I already got this issue with the previous version of this kernel.
[Google Pixel 6 Pro] awakener777:
I'm on stock kernel. I also use Citi bank app and it always detects root. Hiding root used to work, but it seems it no longer does. No issues with other banking apps (I don't use HSBC). I'm not sure why this is.
[Google Pixel 6 Pro] kpirnie:
Mine did the same... initially... I'm old school, coming from SuperUser to Magisk, to now..,. newer Magisk that no longer has MagiskHide...

I had to go to Preferences, then enable Zygisk, and then add my bank app, my card app, and my health insurance app to the deny list, and then they worked fine.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I had the same problem, but I wanted to wait to see if anyone else reported it.

I always use the full firmware flash with -w removed, I then boot up stock unrooted, make sure everything's working, then go back to fastboot and flash the stock rooted kernel, then I normally flash the custom kernel.

What didn't work for me at this point (use ExKM to flash the custom kernel):

Flashing 2.1.0 from the stock rooted kernel - the 2.1.0 package didn't detect my Magisk Stable v24.3 rooted stock kernel.

I then did the full flash-all.bat again (still without -w), and repeated the process - stock kernel, stock rooted kernel, then flash custom 2.1.0. It always resulted in bootloops.

There are some other variations of things I tried that didn't work.

What worked for me:

From the stock rooted kernel, I flashed the 2.0.1 package, which detected my Magisk Stable v24.3 rooted stock kernel and applied Magisk to the 2.0.1 kernel.

Rebooted

With the rooted 2.0.1 kernel successfully working, I then flashed 2.1.0 and it detected Magisk, and everything worked 100%.

Apologies @Freak07 - I haven't grabbed logs...yet.
[Google Pixel 6 Pro] cmh714:
For me, IIRC, I flashed the new kernel (wasnt watching the screen), and then when I looked over it was finished, but the device hadnt rebooted.......so I just flashed again, watching the screen this time, and it rebooted and came up fine....TY for all your efforts!!!
[Google Pixel 6 Pro] jac0b:
@Freak07

Can I use a kernel optimization app like FDE.AI with this kernel or will that cause issues?
[Google Pixel 6 Pro] DanielF50:
It's interesting that a lot of people are having issues with installing 2.1.0.

I did have an issue flashing the April SYSTEM update with -w removed (device corrupt), which I was able to fix by manually force flashing all partitions with fastboot (a & b), but had zero issues when flashing Kirisakura 2.1.0 - maybe this was due to me forcing a reflash of a particular partition?

Once I had flashed April system update & booted once (to finalise update), I booted Magisk (fastboot boot <img>), direct installed 24.3 in Magisk Manager, rebooted again, flashed Kirisakura 2.1.0 in EXKM & rebooted once more, but have had no issues after installing & have had no issues with any apps detecting root after installing 2.1.0 - I've tried all my banking apps, Google Pay, stock trading apps, restaurant apps (suprisingly, 3 of these check for root/hooking!? lol)
[Google Pixel 6 Pro] kpirnie:
I dont want to hyjack the thread, would you mind if I PM you about the manual flashing all permissions...
[Google Pixel 6 Pro] Freak07:
Seems like april firmware doesn´t like my current build environment then. No clue why.

Attached are two new boot.imgs for you to try.

The raven one I confirmed working myself. It´s crucial to flash the powerhint module before, flashing the images.

@roirraW "edor" ehT I suppose your talking about flashing the kernel.zips via EXKM and not the images manually?

The post you´re referring to seems to be about flashing all the images manually via fastboot/fastbootd.

I flashed 2.1.0 on top of stock april kernel and also on top of itself or a prior version of the kernel without any issues on my end. It flashed fine and no bootloops.

I don´t understand this

From the stock rooted kernel, I flashed the 2.0.1 package, which detected my Magisk Stable v24.3 rooted stock kernel and applied Magisk to the 2.0.1 kernel.

If you´re rooted and flash the 2.0.1 zip, there´s no need to "re-root" the device as flashing the kernel.zip will just keep root.

You can´t flash the kernel.zip without being rooted previously except if there´s some TWRP with working decryption available somewhere?

no, it´s made for stable firmware. you´ll face some touch issues with the latest release. need to find time to update the beta kernel.

no, please don´t use any of that nonsense when running this kernel.

Unfortunately I think it´s beyond my control to do anything about it. I haven´t heard of any apps checking for anything changing in the kernel to detect root. It might be something wonky with magisk, something related to reboots, some other weird combination of running a module and a kernel together.

Some apps check for for a folder called TWRP or something similar. I don´t know if maybe the same is true for EXKM?

I don´t know why apps would check for traces of kernel backports and detect root that way for example. It makes not much sense.

I can check a few of those specific apps on my end, but without logs or reversing those apps there might be nothing I can do as the kernel is not involved in this.
[Google Pixel 6 Pro] awakener777:
Yes, I do this and it works fine for ten apps. However, Citi still detects it, at least enough to leave a message. As far as I can tell, the app functions fine. Upon opening the app, the in the picture appears. I just can't see it being a kernel issue, especially considering I'm on stock kernel.
[Google Pixel 6 Pro] kpirnie:
Yeah, it's not a kernel issue. It's a root issue. If the app still works... maybe ignore the image, and chalk it up to simply an annoyance? On my end, I don't get that popup for any app once I added them to that list. (I did get popups and the apps would crash after showing them, before I added them)

Maybe ask over in the Magisk support forum? I know he's gone to work for Google, so I do not know how much effort or time he actually puts into Magisk anymore. In fact, I'd likely ask in here: https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/ instead...
[Google Pixel 6 Pro] kpirnie:
I'd say this is certainly somethng that is sporadic mate. For instance, once I was able to get on the april build, I was able to root with magisk (off topic), and then flash your v 2.1.0 kernel. With no issues what-so-ever (other than my own self-induced issues [I ended up flashing the firmware wrong after coming from A13 DP2, and semi-bricked for a bit... lololol] )
[Google Pixel 6 Pro] Az Biker:
@Freak07

2.1.0 running smooth!

Flashed it via EXKM after updating to April image and Magisk 24.3 stable (step by step instructions in my sig), no issues.

Thanks for all your work and efforts!
[Google Pixel 6 Pro] Lughnasadh:
Just to chime in, I had no problems updating and flashing the kernel.

Updated to April build (of course disabling any pertinent modules beforehand) via flash-all while removing the -w and replacing it with --disable-verity --disable-verification (Yes, yes, I know everyone says there is no need to do this anymore since Canary 23016, but I still think something is wonky and it also prevents getting the "device corrupt" message if things go astray, thus preventing me from having to wipe/clean flash or take other recourses to get rid of the corrupt message. To each their own, so don't @ me 🙃 ).

Then patched the boot image with Canary 24305, moved the patched boot image via adb pull (I know most just transfer the boot image using file transfer from phone to PC but it's been noted that once in a while this method can corrupt a boot image, which is why in John's instructions he says to use the adb pull method), and flashed the patched boot image.

Then flashed Kirisakura 2.1.0. No problems with anything and all is working as it should. Don't use any banking apps so can't chime in on that discussion.
[Google Pixel 6 Pro] awakener777:
It doesn't really bother me at all. I just wanted the other user with the Citi app experiencing root detection on this kernel to know I see it on the stock kernel as well.

Nice to know you didn't have issues with 24305!
[Google Pixel 6 Pro] roirraW "edor" ehT:
Whoops! Indeed, my mistake about that.

No, I meant that what ended up working for me was:

I flash-all.bat without -w the full April firmware.

I booted and verified everything was working stock.

I flashed the stock kernel that I rooted with Magisk Stable v24.3.

Booted/verified working again.

I used ExKM to flash your Raven 2.0.1 zip, which of course on its own through your process recognized that I was rooted, so flashing the zip indicated that it was applying root to it as well.

I then flashed your Raven 2.1.0 zip, which did likewise, applying Magisk correctly on its own.

I didn't try to apply Magisk to the kernel manually.

I had previously tried three times the whole process of:

flash-all.bat without -w

Used the rooted stock April kernel and ExKM to flash the Raven 2.1.0 zip

All three times I would get a boot loop. I had my Magisk Modules disabled at the time.
[Google Pixel 6 Pro] krystiano:
Why some of you doing too many things to update than root and flash kustom cernel.

(Without wipe device)

Using stable magisk 24.3

First:

Disable all modules. (just in case )

Using android flash tools to update to new month without any tick in advanced mode.

After update:

Patch boot.img using magisk and flash to phone.

Than :

Just flash Kirisakura kernel using FKM

Reboot , enable all modules in magisk

Reboot and happy days , enjoy your phone.

@Freak07 thank you for your work.

Second month and working 👍👍👍👍👍👍👍💪💪💪💪💪

Forgot @jcp2 thank you aswell 🥰
[Google Pixel 6 Pro] Utini:
Works fine for me. Flashed with EXKM.
[Google Pixel 6 Pro] m3oh:
No problem after Install 2.1.0. P6 with april update and 2.0.1 kernel.

THX
[Google Pixel 6 Pro] Freak07:
okay I see now. I got confused, thanks for clearing that up. :)

the exact same process that failed for you, worked just fine for me (I also used EXKM yesterday to flash the zips). I flashed the april factory image without wiping and started from a "clean" rooted stock firmware to flash the 2.1.0.zip.

Very weird quirks that sometimes seems to happen on this device. Also weird that flashing 2.0.1 before fixed it for you as there were no changes in the april source or other changes that could cause any bootloop kernel wise.

If something goes wrong with the magisk helper module creation, the device will fail to boot starting with 2.0.1 as the direct USB port from the beta firmware requires a firmware file to be replaced systemlessly via magisk so we can use that updated kernel driver. Maybe it was due to that. Though I fail to see what that should be an issue.

That´s why it´s also crucial to flash the powerhint magisk module in case the manual installation (flashed the images) is used, prior to the images in fastboot.

thanks for the confirmation of my suspicion there!

Just to add that tiny bit, I´m also using 23305 without problems at the moment.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Absolutely, you're welcome. I suspect some kind of quirk as the culprit as well. I had checked the MD5 hash of everything involved before flashing, including checking the kernel 2.1.0 zip on the phone itself. I wouldn't know what hash the stock April boot.img with Magisk 24.3 should be, but since the phone booted fine with it, I don't expect that to be the problem.

I'm pretty much expecting a P6P root-related quirk every 2-3 months for myself. LOL! At least the dice didn't roll "corruption" for me the last 2-3 months.
[Google Pixel 6 Pro] GrandMstrBud:
How do you spoof TTL? I'm looking at tethering via USB or hotspot without carrier detection. Is that possible?
[Google Pixel 6 Pro] arvylas:
@Freak07

I feel like the app launching is slower than before. I saw that you mentioned improved launching speed in you changelog but for me feels the other way around.
[Google Pixel 6 Pro] Utini:
Is undervolting on the P6P a thing?

I do it on my laptop and HTPC and wonder why I am not doing it on my phone aswell?
[Google Pixel 6 Pro] Admiral2145:
Just curious... Anyone able to take the Ota and use magisk to flash root on the Ota and reboot into April or any of the last 2 months... I always have to download the Ota and flash it with computer.
[Google Pixel 6 Pro] vassosman:
Flashed the zip file from yesterday with FKM and Stable Magisk for Root
[Google Pixel 6 Pro] bush911:
Flashed the zip file from with FKM and Stable Magisk for Root

Everything is fine.

By the way, I have those two flags disabled
[Google Pixel 6 Pro] jac0b:
Running pretty good.

Kernel 2.1.0

April update
[Google Pixel 6 Pro] ttle54:
Flashed April build and 2.1.0 kernel on my Pixel 6 Pro yesterday. Things are running smoothly, battery drain is better as well.
[Google Pixel 6 Pro] slickrasta:
The new boot img worked perfectly on oriole 12.1.0 April update patching with Magisk canary 24305, thanks! Keep up the great work with the excellent kernel.
[Google Pixel 6 Pro] bush911:
same here on Pixel 6, It seemed no more smooth than 2.01. I have temperoralily rolled back to stock