Development [KERNEL] [blu_spark r98] [A13]

Search This thread

electronika

Member
Jan 28, 2022
10
8
@eng.stk i accidentally flashed blu_spark r94 with Kernel Flasher...without backing up my stock kernel. could you please detail what partitions i need to flash back to stock for future OTA updates?
boot, dtbo, vbmeta, vendor_dlkm, and vendor_boot. However it is better and easier to do a dirty flash (flash.android.com and just disable wipe device and force flash)
 

eng.stk

Senior Member
Mar 29, 2011
7,175
60,917
OnePlus 5T
OnePlus 6
blu_spark_r96 (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:
  • ThinLTO build with custom upstream LLVM 15.x (Clang 15.0.2 + LLD linker + IAS)
  • Merge branch android-gs-raviole-5.10-android13 (android-13.0.0_r0.20)
  • ANDROID: fips140: split dump-section+add-section into 2 ops
  • Mark some functions nocfi for now to satisfy clang15 (thanks freak07)
  • Wireguard updates
  • 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 :)
 

theimpulson

Senior Moderator / Dev Cmt. / RD / Dev Relations
Staff member
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.
Hi @eng.stk, if possible, could you share the build environment instructions for building and packing the kernel to get the flashable zip? I got a nothing phone yesterday and was looking at how to build a standalone kernel now without the whole android build environment.
 

eng.stk

Senior Member
Mar 29, 2011
7,175
60,917
OnePlus 5T
OnePlus 6
Hi @eng.stk, if possible, could you share the build environment instructions for building and packing the kernel to get the flashable zip? I got a nothing phone yesterday and was looking at how to build a standalone kernel now without the whole android build environment.
You should not need anything fancy, it's a simple vendor_boot hdr_v3 device.
I manage to build for it just for the lolz early on (1.0.1.A063), a bunch of qcom/vendor builtin tree fixes to build monolithic and you're of to the races.
 
  • Like
Reactions: theimpulson

Galaxea

Senior Member
Jun 17, 2010
424
103
Google Pixel 6
I used PixelFlasher to upgrade from the June Beta to T1B3.221003.003 (without a wipe) and when I flashed this kernel after rebooting it hangs on the Google bootup "G" screen.

I have never had this kernel hang on me before. Any ideas please?
 
  • Haha
Reactions: Mrcactuseater
I used PixelFlasher to upgrade from the June Beta to T1B3.221003.003 (without a wipe) and when I flashed this kernel after rebooting it hangs on the Google bootup "G" screen.

I have never had this kernel hang on me before. Any ideas please?
When you upgraded to the latest, did you flash to both slots? That is the recommended procedure for Android 13.
 
  • Like
Reactions: Galaxea

eng.stk

Senior Member
Mar 29, 2011
7,175
60,917
OnePlus 5T
OnePlus 6
I used PixelFlasher to upgrade from the June Beta to T1B3.221003.003 (without a wipe) and when I flashed this kernel after rebooting it hangs on the Google bootup "G" screen.

I have never had this kernel hang on me before. Any ideas please?
r96 is for TP1A.221005.002, not for device betas.
If you're using betas, stick to stock kernel.
 

Ph0z3

Senior Member
Jul 7, 2010
923
186
Kansas City
I'm wanting to install this, but haven't rooted anything since my P2xl on Android 10.

I don't have a clue where to start with this phone! I'm wanting to stay fully stock / no-root. Just the kernel. Is that worth it?

Extra: latest Android 13 & using Arco Linux.
 
  • Haha
Reactions: Mrcactuseater

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    blu_spark_r98 (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:
    • ThinLTO build with custom upstream LLVM 15.x (Clang 15.0.4 + LLD linker + IAS)
    • Merge branch android-gs-raviole-5.10-android13 (android-13.0.0_r0.44) Nov 20022.2
    • Merge wifi CVE's from kernel_common/android13-5.10
    • AnyKernel3 updates (v20221019)
    • 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 :)
    2
    Universal SafetyNet Fix. See the Pass SafetyNet/PlayIntegrity section here.
    1
    I'm wanting to install this, but haven't rooted anything since my P2xl on Android 10.

    I don't have a clue where to start with this phone! I'm wanting to stay fully stock / no-root. Just the kernel. Is that worth it?

    Extra: latest Android 13 & using Arco Linux.
    1
    I don't have a clue where to start with this phone! I'm wanting to stay fully stock / no-root. Just the kernel. Is that worth it?
    If you care about Google Pay, banking apps, etc, after unlocking your bootloader, you'll have to root and install USNF, regardless of kernel.

    Beyond that, I haven't tried using the kernel without root, so I'll have to defer to others for that.
    1
    what is usnf just got the pixel 6 yesterday and unlocked bootloader, rooted with magisk. the phone updated itself to the latest beta though. i have 1 banking app detecting root no matter what i do. and also can i install this kernel on the latest beta version
    Like I already said earlier, kernel is for stable ROM, not betas.
  • 61
    DWHxIK

    Kernel features:
    • Build with custom upstream LLVM 15.x (Clang 15.0.4 + LLD linker + IAS)
    • ThinLTO full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
    • Less is more: stockish kernel+modules+dtb builds based on Google latest sourcedrop for max stability (android-gs-raviole-5.10-android13)
    • Full kernel tree with OEM integrated drivers, for minimal build overhead and fast deploy
    • Systemless installer (doesn't touch system/vendor partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
    • Removed some debug and logging options
    • Misc ARM performance and battery patches
    • CVE security patches, general upstream and fixes for important subsystems when applicable
    • No OC, use 250HZ base timer frequency
    • Enhanced TCP methods (westwood is default, BBR and others available)
    • Some I/O control tweaks, advanced filesystems enabled (NTFS3 5.15 backport, ExFAT upstreamed, , CIFS & NFS)
    • ZRAM set at 4G (default lz77eh with lzo-rle, zstd, etc available)
    • WIP: Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
    • Gamepad support enabled (xbox, ps4, switch)
    • USB2 Fast Charge (force USB CDP mode up to 1500mA with MTP on)
    • Wakelock blockers available
    • TWRP Support(LZMA/LZ4 Ramdisk)
    • Wireguard updates
    • Compatible with Kernel Flasher, EXKM, FKM , Kernel Adiutor and others


    DOWNLOAD KERNEL ZIP
    Kernel Flasher/FKM download configs: HERE
    (No mirrors please)​


    Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
    If you come from other kernel or have any issues, you should restore your stock setup or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
    If you are upgrading between blu_spark versions, just flash the kernel zip.

    About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
    If you're using custom ROMs (including stock based ones) you're much on your own. I'm mostly interested on debugging stuff in stock and stable ROM.
    Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.

    Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img/vendor_boot.img/vendor_dlkm.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock. You can also flash boot.img/vendor_boot.img in fastboot and vendor_dlkm.img in fastbootd from you stock ROM. Or just dirty flash your full OTA ROM zip.


    Source Code: https://github.com/engstk/pxl6
    Don't forget to hit thanks, it's free ;)
    33
    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:
    • Build with Google Clang 12.0.5 + LLD linker
    • Full kernel based from kernel/gs+google-modules @ android-gs-raviole-5.10-android12-d1 (android-12.0.0_r0.17) (Nov 2021.1)
    • Several build fixes and improvements (check git for details)
    • drivers: google-modules: make it build and additional fixes, remove cruft
    • Disable some debug and logging
    • FS and F2FS improvements
    • Enable advanced TCP congestion control (westwood default)
    • Add wakelock blocker framework
    • Tuned a couple IO and ZRAM runtime stuff
    • AK3 updates (v20211118) plus my own additional fixes for hdrv4 flashing (big shouts @osm0sis for the help)
    • For root, canary Magisk 23015 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 thanks, it's free :)
    15
    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 :)
    14
    blu_spark_r45 (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:
    • Merge branch android-gs-raviole-5.10-android12-qpr1-d (android-12.0.0_r0.36) (Jan 2022.1)
    • Rebase and cleanup
    • Wireguard updates (linux-5.10.y)
    • For root, Magisk 23016 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 thanks, it's free :)
    14
    blu_spark_r81 (A13 beta)

    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:
    • ThinLTO build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS)
    • Rebase to branch android-gs-raviole-5.10-t-beta-4 (android-t-beta-4_r0.4)
    • Additional build/google-modules/vendor fixes
    • wireguard and exfat updates
    • Couple cleanup reverts
    • 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 :)