Development [KERNEL] [blu_spark r136] [A13 Sep 2023]

[zyonee]

Yeah I personally don't have it disabled either, vbmeta patch works nicely.
But some people have issues without messing with the flags, there's some particular stuff to some setups that sometimes triggers verity/verification.
Less common nowadays but stil happens form time to time.

Also: my bet A13 stable is coming next week

@eng.stk Yeah, trying to patch vbmeta gave me the famous "system corrupted" screen. Solved by reflashing without wipe of course, but still a dead end for me. But like I said, disabling dm-verity without touching the verification flag did it for me.

On another note, would it be possible to implement doubletap2wake in the kernel? It's really needed for this device imo, as single tap and/or lift to wake keeps activating the screen in my pocket.

 

[capntrips]

@cultofluna Can you please explain what the the difference between --disable-verity and --disable-verification is? I'd like to understand this better.

--disable-verity only affects the hashtree (verity) devices, whereas --disable-verification affects all of Verified Boot.

On Pixel 6 at least, during the initial boot, Verified Boot loads the vbmeta partition, which contains hash descriptors for abl, bl1, bl2, bl31, dtbo, gsa, ldfw, pbl, pvmfw, tzsw, and vendor_boot. It also has a hashtree descriptor for vendor_dlkm and chain descriptors for boot (which contains its own embedded vbmeta image), vbmeta_system, and vbmeta_vendor. When verification is disabled, it only loads the top level vbmeta and none of the chained ones. When the device is unlocked it ignores the hashes in the various descriptors. I think the hashes are also similarly ignored when verification is disabled, but I can't confirm that, as I've never done any testing on a locked device.

As for the vendor_dlkm verity device, its hashtree descriptor, and the issues some people have booting on custom kernels, I'll quote myself from another thread:

The issue is Magisk 24303+ no longer strips avb from fstab, so when the phone boots, first stage mount looks at the fstab entry for vendor_dlkm, which references vbmeta, so it looks at the hashtree descriptor for vendor_dlkm in vbmeta and tries to setup a verity device using those values, but vendor_dlkm for the kernel is different from stock, so those values are incorrect, mounting fails, and the device bootloops.

If you have verity or verification disabled, first stage mount ignores avb in the fstab entry and mounts the partition directly.

I cut the bits about how AK3 and Hashtree Patcher deal it from the quote, so follow it back for more detail on that.

 

[zyonee]

--disable-verity only affects the hashtree (verity) devices, whereas --disable-verification affects all of Verified Boot.

On Pixel 6 at least, during the initial boot, Verified Boot loads the vbmeta partition, which contains hash descriptors for abl, bl1, bl2, bl31, dtbo, gsa, ldfw, pbl, pvmfw, tzsw, and vendor_boot. It also has a hashtree descriptor for vendor_dlkm and chain descriptors for boot (which contains its own embedded vbmeta image), vbmeta_system, and vbmeta_vendor. When verification is disabled, it only loads the top level vbmeta and none of the chained ones. When the device is unlocked it ignores the hashes in the various descriptors. I think the hashes are also similarly ignored when verification is disabled, but I can't confirm that, as I've never done any testing on a locked device.

As for the vendor_dlkm verity device, its hashtree descriptor, and the issues some people have booting on custom kernels, I'll quote myself from another thread:



I cut the bits about how AK3 and Hashtree Patcher deal it from the quote, so follow it back for more detail on that.

Thank you very much for the detailed explanation!

 

[ctfrommn]

Question for one of the developer minded on here......Im trying to build my kernel for Bluejay (Pixel 6a) which is extremely similar to the Pixel 6/6 Pro and am using Googles/Androids method (https://source.android.com/setup/build/building-kernels). It seems very straight forward and Ive built literally thousands of kernels & Roms over the years but for some reason even building this bone stock results in a non boot situation.

Is there something Im missing with this device or method I should be aware of or is there a simpler way to do this? Ive historically just used my own build scripts but the repo structure of these devices is so different and there are so many modules loading that I figured I would try the AOSP approved method first

Thanks for any insight.

 

[eng.stk]

blu_spark_r84 (A13 beta)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.
For flashing and easy of install logging, Kernel Flasher by @capntrips is recommended

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


Changelog:

• Merge android-gs-raviole-5.10-t-beta-4 (android-t-beta-4_r0.5)
• drivers: google-modules: Merge branch android-gs-raviole-5.10-t-beta-4 (android-t-beta-4_r0.5)
• defconfig: update from TPB4.220624.008
• AnyKernel3 updates (v20220802)
• For root, Magisk 25.1 or newer is mandatory

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

 

[jejemc]

hello @eng.stk please for pixel 6a thanks

 

[snake218]

A noob question:

Using kernel flasher, pixel 6, i see there are 2 kernel slots, but only slot B gives me the option "flash".
So all i have to do is select flash in slot B, select latest blu spark kernel file and flash it, it's that correct?

 

[phaino00]

A noob question:

Using kernel flasher, pixel 6, i see there are 2 kernel slots, but only slot B gives me the option "flash".
So all i have to do is select flash in slot B, select latest blu spark kernel file and flash it, it's that correct?

If slot b is where your os is installed, then yes. But, as you mention, slot a does not give you the option to flash, so you are good to go flashing on slot b.

 

[snake218]

If slot b is where your os is installed, then yes. But, as you mention, slot a does not give you the option to flash, so you are good to go flashing on slot b.

Thanks for your reply, flashed successfully to Slot B.

Zram is set to 3gb, should I need to enable it to 4gb on kernel manager?

 

[liver20]

Can i flash over despair kernel?

 

[phaino00]

Can i flash over despair kernel?

I've read that some have had success, but it is best practice to reflash the factory image (or appropriate images, boot, vbmeta and dklm), then flash new kernel.

When reflashing factory image, you'll lose root; so you will have to reflash patched image prior to flashing new kernel.

 

[liver20]

I've read that some have had success, but it is best practice to reflash the factory image (or appropriate images, boot, vbmeta and dklm), then flash new kernel.

When reflashing factory image, you'll lose root; so you will have to reflash patched image prior to flashing new kernel.

Flashed over and works like a charm

 

[eng.stk]

blu_spark_r85 (A13)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.
For flashing and easy of install logging, Kernel Flasher by @capntrips is recommended

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
Download config: HERE


Changelog:

• ThinLTO build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
• Sync with oriole-tp1a.220624.021
• For root, Magisk 25.2 or newer is mandatory

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

 

[eng.stk]

Seems like google saved a surprise for the modders yet again.

PSA: Once you update to Android 13 on Pixel 6, you can't go back

Android 13 is out for Pixel devices today. But if you have a Pixel 6, 6 Pro, or 6a, you may want to make sure you're ready before updating.

www.androidauthority.com

Word of advice: flash A13 to both slots before any modding or tinkering with the device.
There's seems to be cases where if the phone fail to boot, reverts to the previous slot and if it's A12 the device get's stuck and utterly bricked.
I just sideloaded the OTA twice to cover A and B slot, better safe than sorrow...

 

[Kenaz Rune]

I'm having this exact same issue and can't figure it out for the life of me. Did you ever get this solved?

As luck would have it, someone created a kernel flash tool that's available on this forum. Sorry I didn't see your message before now. I'm not caught up on the thread, but I'm sure it's been mentioned a few times

 

[eng.stk]

blu_spark_r87 (A13)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.
For flashing and easy of install logging, Kernel Flasher by @capntrips is recommended

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
Download config: HERE


Changelog:

• ThinLTO build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
• google-modules: add some missing build flags
• wireguard updates
• AnyKernel3 updates (v20220827) for better flashing support after OTA/sideload
• For root, Magisk 25.2 or newer is mandatory

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

 

[snake218]

blu_spark_r87 (A13)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.
For flashing and easy of install logging, Kernel Flasher by @capntrips is recommended

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
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

Sorry for the newbie question, but it's safe to flash in latest beta version T1B1 Pixel 6? And related to first question, if this Kernel is based on A13, can be flashed on any version of android 13 that will come, or we always should wait and flash a new Kernel version for every A13 update? Thanks.

 

[eng.stk]

Sorry for the newbie question, but it's safe to flash in latest beta version T1B1 Pixel 6? And related to first question, if this Kernel is based on A13, can be flashed on any version of android 13 that will come, or we always should wait and flash a new Kernel version for every A13 update? Thanks.

Kernel is made for stable patchset by the monthly update.
Sometimes there's changes in betas and new updates that make kernel not compatible/unstable.
I don't recommend running in other than stable releases.

 

[Zaxx32]

Another noob-ish question...

I was a big fan of bluspark on my P4a but alas it went back to google for $300 of my P6a (they wouldn't lemme put it towards a
P6 ) My Q: Is there anyway to make b-s for the 6a just based on what u gleaned from making the 6's kernel and what the 6a source code tells you...or do u need a 6a in-hand to do it? I'm guessing u need a 6a in hand. Had to ask cuz it's slim pickins for a 6a kernel. Saoorry for strayni...

 

[eng.stk]

blu_spark_r94 (A13)

New build is up!

Build is unified for raviole, should work both on Pixel 6 (tested) and Pro variant.
For flashing and easy of install logging, Kernel Flasher is recommended

You can use Kernel Flasher/FKM download kernel feature, just import the link bellow in the app updates/flash section.
Download config: HERE


Changelog:

• drivers: google-modules: Merge branch android-gs-raviole-5.10-android13 (android-13.0.0_r0.14)
• drivers: google-modules/vendor: fix build errors for clang-15
• arm64 module: remove (NOLOAD)
• Sync with oriole-ota-tp1a.220905.004
• For root, Magisk 25.2 or newer is mandatory

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