yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] pfraga68:
HELP DIGILAND DL1036 stock rom (urgent) constantly rebooting
[Samsung Galaxy S21+] M0neyPenny:
How do I change screen res? Option does not appear in settings/display
[General Questions and Answers] Jthackston789:
I have a Samsung A12 and I can't root it in fact I can't get anything to work I have never rooted a phone before can someone plz help my oem is not showing up either.
[General Questions and Answers] pojr:
welcome to xda. in order for your phone to be unlocked, you have to unlock your bootloader.

has that been done yet? if not, do you know what that is?
[General Questions and Answers] Jthackston789:
No I've heard of it but I'm not sure sorry
[General Questions and Answers] Deleted member 1890170:
To root a device's Android it's NOT required that device's bootloader gets unlocked.
[General Questions and Answers] pojr:
is that so? i always needed to unlock my bootloader in order to flash roms and magisk. but i know a lot has changed recently. maybe there's some exploit that allows you to root without needing to flash anything. hopefully you're not talking those suspicious apps like kingroot or whatever.
[General Questions and Answers] Deleted member 1890170:
Take note that Android OS is rooted when SU binary is present within it. Android OS has NOTHING to do with device's bootloader ( what is comparable to BIOS of a Windows PC ).
[Xiaomi Mi Pad 5 Pro] mkcs:
This is extracted from the offical recovery ROM for rooting. Patch it with Magisk followed by flashing the patched boot.img via fastboot.

A more detailed guide about rooting can be viewed here:

https://www.getdroidtips.com/root-xiaomi-mi-pad-5-pro/#1-How-to-Extract-and-Patch-Bootimage-using-Magisk

Boot image of MIUI V12.5.8.0.RKZCNXM Stable: https://mega.nz/file/2p8ymbxA#LsZp-wLF06AK4sqz4r6HBEg2VFSutyecbh1xsKodyR8
[Redmi Note 9 Questions & Answers] Gordon3002:
I tried to install TWRP on a Redmi Note 9 but it doesn’t work, it always boots in Xiaomi’s recovery. Can someone help me ?
[Redmi Note 9 Questions & Answers] VD171:
How did you install it?
[Redmi Note 9 Questions & Answers] Gordon3002:
I tried installing it by using a program that does it automatically and also using the command prompt. I think I need to flash other files too and not only TWRP.
[Redmi Note 9 Questions & Answers] VD171:
Share screenshots, please.
[Touch Cruise General] gainasp:
I have upgraded to the 6.1 rom. In the previous official rom, when using the bluetooth in my car, the agenda, received calls, missing calls and made calls were downloaded to the car and accessible through the car controls.

Now, when using the bluetooth in my car, the agenda is downloaded but the call lists are not. This is quite inconvenient, since the most common calls are there and I have a big agenda which is difficult to go through by using the car controls.

Any idea in how to fix this?

Thanks a lot.
[Google Pixel 6] eng.stk:
blu_spark_r29 (A12)

So here's blu_spark for the oriole (and probably raven ;p)

Been cracking around on this since I got the device a couple weeks ago.

The new GKI kernel stuff(which imo will kill custom kerneling in the future) and the "let's use 10GB of garbage device tree to build a kernel" is not really for me.

So I decided to put on an full tree with all the vendor stuff on it, with less that 5% of what Google proposes we can play with the device just fine.

My primary objective was also to make a full builtin kernel, but seems like init expects modules and other stuff to be in place so it's a no go, at least for now (maybe with some further init stages crack it's possible, idk)

So kernel output is splitted across boot.img, vendor_boot.img and vendor_dlkm.img.

I also take the time to make AK3 basic hdr v4 compliant (big shouts to @osm0sis for being the best wingman, as always). Because fastboot is tedious and since it's 2021 there's no room for that in my builds.

You can flash the AK3 kernel zip in your favorite kernel app with autoflash functions or with TWRP when/if available. If you want/need to go stock again, instructions are on OP.

Besides Pixel 6, this should work on Pro also, but I can only test on Oriole, let me know how it goes on Raven if you're brave enough.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit thanks, it's free :)
[Google Pixel 6] ne0ns4l4m4nder:
Just installed using FKM will be testing :) thanks for the hard work
[Google Pixel 6] phaino00:
Great to see blu_spark kernel on the Pixel 6. Thanks. Installed last night and ready to give the kernel a go today.🥳👍
[Google Pixel 6] Flawn:
lovin to see it!

gonna flash asap :)
[Google Pixel 6] Flawn:
Where are we able to tune this? EXKM & FK don't show anything for me.
[Google Pixel 6] eng.stk:
It's work in progress, some stuff are to indicate what I want to add later on.
[Google Pixel 6] cultofluna:
Thanks for kernel...

To go back to stock all three images ( boot, dtbo, vendor dlkm) can be flsahed through EX kernel manager actually....
[Google Pixel 6] vandyman:
Flashed the kernel using EX-Manager.

So far, so good on my P6.
[Google Pixel 6] eng.stk:
"with TWRP or kernel app" "fastboot" "dirty flash OTA zip"

People can use what is easier/better for them if there's the need to restore stock.

I don't use dtbo, I don't patch anything there.
[Google Pixel 6] arvylas:
Is this the reason there aren't many custom kernels up until now? I thought the GKI would make things easier at least after some time that devs get more accustomed with it.

Btw nice to see you here I was running your kernel for the past few months on op8pro.
[Google Pixel 6] cultofluna:
Of course...

Just sharing the info that vendor dlkm img can also be flashed on the phone through the ex manager ( not other kernel manager) ..

Otherwise on fastbootd

@eng.stk booted fine on 6pro
[Google Pixel 6] allenjthomsen:
Great to see you on Pixel 6 @eng.stk been using your kernel on most of the devices that i have granted 1 or 2 dont have it but like always you're on your a game and i look foward to how much battery savings we will get with this kernel over time. Seems great so far btw on your kernel.
[Google Pixel 6] eng.stk:
Nice, thanks for testing out :)
[Google Pixel 6] eng.stk:
Well GKI is for getting vendor/oem life easier the way updates are maintained.

Actually the choices the big G has made over time complicate the aftermarket tinkering.

They are making thinks too convoluted for instance, keeping source scattered all over the place creating artificial dependencies, using a build backend full of unneeded junk, output goes in random places just because, images full of junk with multi-ramdisks and padding with weird layouts, etc.

They started complicating ROM stuff, partitions, etc. Then they went after gapps and root. Now it's kernel.

Android is becoming ChromeOS imo.

Doesn't mean things can't be modded, just the way they are going is deterring to do it.
[Google Pixel 6] kpirnie:
Excellent to see you here mate! Just got my 6, so I want to give myself some stock time with it, but Im sure I'll be flashing soon 😁
[Google Pixel 6] eng.stk:
Nice to see here dude, enjoy your oriole 👍
[Google Pixel 6] kpirnie:
so far loving it. making a modified case so I can attach it to my telescope ;)
[Google Pixel 6] ne0ns4l4m4nder:
Been working pretty well, I've had a couple of weird freezing and things becoming unresponsive but besides that it's working great.
[Google Pixel 6] cultofluna:
On 12L got improved...
[Google Pixel 6] cyrus104:
Would like to see how to compile this kernel, have a couple of kernel config changes I'd like to make.
[Google Pixel 6] nutpants:
just installed this on my pixel 6 (feb update)with ex kernaal manager. battery was pretty bad for the first 6 hours or so, but right now it seems to be getting back to normal. ill report back later on how it is battery wise.

the fingerprint reader feels like it works a little better, but not a ton. the phone it self might feel a little faster at first glance

exfat support does not appear to work with my linux formatted usb stick
[Google Pixel 6] eng.stk:
stock ROM doesn't have vold with exfat support.

Either get a modded one or get tools to mount it manually.
[Google Pixel 6] bobbarker2:
Do we need an updated kernel for

Battery always seems bad after a new install in a small window of time. First 12-24hrs on this kernel I saw screen-off battery usage at 5-6%. But the next day, idle battery usage is around 1%. You have to look at usage over a longer period of time than 6 hours, otherwise statistics are completely skewed.
[Google Pixel 6] nutpants:
right now im at 48 hours on the new kernel, and from what i see its 2% more an hour screen on time and .3 % an hour screen off time for battery usage over the oem kernel ill keep testing for another dya or two to see if it improves
[Google Pixel 6] RobbyRobbb:
Do you mean this in order of keeping the fingerprint detection feature functioning, or in regards to something else? Kcal is the only reason I have ever been interested in custom kernels and the interest remains with this phone. Fingerprint detection means nothing compared to true color accuracy.
[Google Pixel 6] kpirnie:
One of the biggest "fixes" I have seen with the fingerprint reader is to add multiples of the same fingers. I personally have seen a 75% success rate go up to 98% just by adding another of the same finger. And this goes back to the November update when this all started
[Google Pixel 6] a g bell:
I thought everyone did this😱maybe just former OnePlus owners like me 😁
[Google Pixel 6] paratox:
@eng.stk did you read about DirtyPipe (CVE-2022-0847) vulnerability? should we worry about it?
[Google Pixel 6] eng.stk:
Yeah, although it needs some particular conditions to be exploited, it can bring potential problems.

I'll check out available patches.
[Google Pixel 6] eng.stk:
blu_spark_r54 (A12)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 6] Daenjel:
It would be too much to ask for you to add display controls to the kernel? I really wanna try to fix this sh*t show of a display I've got
[Google Pixel 6] bobbarker2:
This exploit requires Linux 5.8 or later; the code path was made reachable by commit f6dd975583bd ("pipe: merge anon_pipe_buf*_ops"). The commit did not introduce the bug, it was there before, it just provided an easy way to exploit it.

Dirty Pipe Linux Privilege Escalation ≈ Packet Storm

Information Security Services, News, Files, Tools, Exploits, Advisories and Whitepapers

packetstormsecurity.com

Edit:. Oops didn't see you already saw this.

@Daenjel eng.stk addressed this a page or two back.
[Google Pixel 6] RobbyRobbb:
Would if I pay you to add this functionality? Does that make the difference?
[Google Pixel 6] bush911:
Has anyone tried r54 on March build?
[Google Pixel 6] bush911:
It seems does not work well with the March build. It took longer to finish booting, and system ui not responding for a moment.

I am going to flash it again when @eng.stk finishes updating, as blu_spark kernel sleeps very well for me.

Cheers
[Google Pixel 6] eng.stk:
blu_spark_r57 (A12L)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 6] simonk206:
It seems FKM download config is still r54

Edit: it's r57 now
[Google Pixel 6] sakerhetz:
I installed blu_spark_r57 (A12L) but have a corrupted system now!
[Google Pixel 6] m3oh:
Confirmed, Installed from FKM, corrupted system, Stoping Google logo. Sideloaded the ota.img, system boooted. Strange that the corrupted system warning still exist..
[Google Pixel 6] sakerhetz:
Did the same , installed OTA. IMG, but at start still a data corrupted message but it boots at least.
[Google Pixel 6] xxxxgrizz:
magisk can't >=24303
[Google Pixel 6] eng.stk:
What Magisk version? what modules? A12L March stable update? Any beta flashed before?

Without complete troubleshoots and data, trying to figure out stuff is difficult.

I never encountered in all the flashes I did, seems like some people hit it in certain conditions while triggering verity.

I discussed this also with other devs, nobody is sure what exactly triggers it. At the boot menu, pressing start manually should allow booting normal.

I advise people to stick with Magisk stable and run with --disable-verity --disable-verification updates to avoid such troubles while is not fixed.

Some threads to read about this situations:

https://xdaforums.com/t/unlocked-pi...anually-flash-dec-2021-factory-image.4374799/

https://xdaforums.com/t/new-solutio...be-trusted-and-may-not-work-properly.4400091/

https://xdaforums.com/t/kernel-22-0...pro-aka-raviole.4358435/page-53#post-86600561

https://xdaforums.com/t/kernel-22-0...pixel-6-pro-aka-raviole.4358435/post-86613197
[Google Pixel 6] Alxoom33:
Is this kernel updated for P6Pro A13 DP2?
[Google Pixel 6] sakerhetz:
-Magisk-3dc7d77e(24304

-disabled-verity --disable-verification

-No modules

I tried it 2 times , first time i had some modules on magisk and was "device corrupt"

2 nd time i tried without modules but still the same result "device corrupt"

i'm on pixel 6 and never had this before with spark kernel.

( My phone is normal again, i used the Android flashtool and rolled system back to febr 2022).

regards

Robert
[Google Pixel 6] eng.stk:
Nope.
[Google Pixel 6] eng.stk:
24303 ad 24304 is know to be specially bugged.

Some people have come to working state trying the workarounds I linked

Stick to stable MM and ROM releases and -disabled-verity --disable-verification is my advice.
[Google Pixel 6] bobbarker2:
In trying to update to March, I tried to flash kernel and I got device corrupt bootloop. I did a flash-all without -w then flashed the Magisk patched boot img to get it booting again but still corrupt device screen.

But to get rid of the corrupt device screen I did a flash all on my current slot, then I changed active_slot in fastboot, reboot bootloader and flash-all on that slot. Flashed Magisk patched img and now I am on March with no corrupt device.

This was all on Magisk 24304 but I've had problems with an unbootable corrupt device after flashing a custom kernel in other occasions too. I've never had a device where the process of flashing has been so unreliable.
[Google Pixel 6] eng.stk:
The problem is that people flash all kind of sutff including beta and derps can happen more often.

I flash hundreds of builds on this device alone and never encountered any issue.

I stick to stable stuff only. People should also unroot and remove all magisk data before attempting anything else.
[Google Pixel 6] bobbarker2:
While that is true, there is also something whacky going on that is not fully explained or understood. If I tried flashing a custom kernel right now, with my phone on the March update, Magisk 24.3 stable, I would get Corrupt Device and bootloop. Then it would take me 45 minutes of boring time to try and get it to work again. I've posted logs previously as this was an issue some months ago and there was no solution found.

I agree, the majority are probably issues like flashing from one custom kernel to a different one, but I've been flashing devices for 10 years now and have never had one that's been so flakey. People who know what they are doing (xda developers) have bricked this phone.. I count myself lucky that hasn't been the case for me.

I'm not "blaming" you, I'm simply sharing my experiences.
[Google Pixel 6] m3oh:
Thanks for the links. Corrupt device gone, your kernel is up on my P6. And stable magisk too :)
[Google Pixel 6] eng.stk:
There's at least 4 or 5 situations other devs and myself are discussing, half is not even flashing related.

I encountered a bug in MM that has nothing to do with flashing and will introduce a bootloop on P6.

Very skiled people are trying to figure out stuff, but devs are not magicians.

People can use what works and minimize issues or just fool around with the device.

Either is fine by me, just don't come cry later ;)

Using stable ROM with verify off (google still says its a must to flash custom stuff in their oficial documentation), rooting with stable Magisk and flash the kernel after, will work fine.

Using safetynet-fix module will also work fine, I have it on my setup.

Some stuff I linked above work for some as a workaround, which is useful.

Positive input is the way.
[Google Pixel 6] i42o:
Will this work on Android 12 March latest update with P6 pro?
[Google Pixel 6] phaino00:
The most recent version is updated for March. It works for both the 6/6pro.
[Google Pixel 6] i42o:
Thank you
[Google Pixel 6] eng.stk:
blu_spark_r60 (A12L)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 6] kpirnie:
awesome mate. I'll test in a day or 2 :) Finally unlocked mime for flashing and rooted it lololol
[Google Pixel 6] kpirnie:
Ooooo it feels good to be back on this kernel =)

Excellent job as always mate!
[Google Pixel 6] sakerhetz:
Does Kernelupdate r 60 work on April update???

BTW ... Blue spark best kernel ATM.
[Google Pixel 6] eng.stk:
Yes, works for March/April
[Google Pixel 6] capntrips:
After a lengthy startup with the G logo and progress indicator (~1 minute), the lock screen appears, but my touchscreen doesn't function at all. The hardware keys seem to work fine, and I'm able to adb into it. I tried searching the thread, but I didn't see a solution. Neither cycling the screen nor rebooting helped.

I'm on stock SP2A.220405.004 (and I've never installed any of the betas) using Magisk 24306 (though I also tried 24.3 stable) and r60 of the kernel.

I tried installing it with FKM and running AK3 directly.

The following logs are from a clean install. The only thing I did prior to kernel install is enable developer tools and install Magisk (no modules):

dmesg

logcat

Note: I have the exact same issue with the Kirisakura kernel.
[Google Pixel 6] eng.stk:
Magisk stuck/reboot issues already been discussed in every thread and on this one last page.

There's a couple things you can try, other than that nothing I can do for you.

I advice people to have stock ROM flashed with Magisk stable before flash custom stuff, keep verify off between updates.
[Google Pixel 6] Grifello:
@eng.stk can i try to install your kernel in my raven with crdroid installed in your opinion?
[Google Pixel 6] capntrips:
Unless I'm missing something, I'm not sure that applies here, since it boots up just fine. I just can't interact with the screen.

I reflashed stock SP2A.220405.004 with disable flags, installed Magisk 24.3 stable, and installed r60 of kernel with the same issue:

dmesg

logcat

Edit: It turns out I had an extra vendor_dlkm partition (in addition to vendor_dlkm_a or vendor_dlkm_b) in both super partition slots. I did a fastboot wipe-super then flash-all, and everything started working.
[Google Pixel 6] eng.stk:
Ah ok, didn't understand first what you meant.

That's somewhat funky, generally that happens with failed OTA or messing with super resize. What have you been doing?

Not a kernel or zip install issue per se. Curious that you were having a bootable device without several drivers not being properly loaded.

Having the ROM in a clean state is first step ofc (fastboot IMGs takes care of that generally).
[Google Pixel 6] eng.stk:
Probably if it matches the A12.1L March or April ROM updates.
[Google Pixel 6] capntrips:
Oh yeah, I totally did it to myself. I was working with lptools and on a static fastbootd binary to find a way to properly resize and flash vendor_dlkm on a running system.

The flash-all script didn't remove it, though it probably wouldn't have hurt anything just having it out there, but AK3 was defaulting to the unslotted one when it searched for the partition to flash.
[Google Pixel 6] Grifello:
ok thanks. just installed and evertything seems fine
[Google Pixel 6] ajsmsg78:
I did and it's working fine for me.
[Google Pixel 6] sakerhetz:
Does blu_spark_r60 (A12L) also work on pixel 6 may 2022 update or is it better to wait for coming version?
[Google Pixel 6] eng.stk:
Incoming 😁
[Google Pixel 6] eng.stk:
blu_spark_r65 (A12L)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 6] sakerhetz:
Cool👍👍
[Google Pixel 6] rolarocka:
I'm on A12 May Stock and Magisk stable root. I flash blu_spark with FKM script and that's all I need to do? Will Magisk and modules be kept?

Tyvm 😀
[Google Pixel 6] phaino00:
Yes. Just flash through FKM and all modules will be retained.
[Google Pixel 6] rolarocka:
Thx, worked 😍
[Google Pixel 6] Galaxea:
Would really like to try this kernel on 13 beta 2. Will it work as is?
[Google Pixel 6] eng.stk:
Nope, this is for A12.1
[Google Pixel 6] Galaxea:
Thanks. Will wait for 13 version then.
[Google Pixel 6] eng.stk:
blu_spark_r71 (A12L)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.

You can use FKM download kernel feature, just import the link bellow in the app flash section.

FKM download config: HERE

Thanks to @capntrips awesome work on avb patching, AK3 installer takes care of verity/verification situation for you, automatically patching vbmeta.

Meaning verity/verification status should not be an issue with newer Magisk versions and similar situations, allowing booting custom images with avb on.

Changelog:

Keep in mind: I will give no active support for custom ROMs (including stock based ones).

I am mostly interested on debugging stuff in stock ROM (with logs and reproducible steps to replicate the issue).

No mirrors please

Don't forget to hit like, it's free :)
[Google Pixel 6] nguyenson91hp:
Anyone flash r71 on ProtonAOSP? Mine stuck at Proton logo.
[Google Pixel 6] eng.stk:
You need to use ROM with the June updates merged in.
[Google Pixel 6] nguyenson91hp:
Oh I see. Is there anyway to flash the r65 and wait until then?
[Google Pixel 6] Slim2none4u:
Thank you for the fast update :)
[Google Pixel 6] eng.stk:
Stick to Magisk 24.3 if you're on old versions, should work fine.
[Google Pixel 6] Hot-Proton:
Hi @eng.stk nice to see you again. I switch to Pixel too.
[Google Pixel 6] cosy6ay:
will this work on jun update with magisk@v25?
[Google Pixel 6] eng.stk:
Welcome! Good choice 😁
[Google Pixel 6] eng.stk:
Yes, ofc.