Can you flash this via adb sideload instead? (Im unrooted/stock)
My bad, you can adb sideload spark kernel through LOS recovery. However, I think you need to be rooted.
Can you flash this via adb sideload instead? (Im unrooted/stock)
Like I said before, that resulted in bootloader loop. However, I used FKM with previous script mentioned after restoring the rom and now it works
No, it works fine in either slot.I got it to flash and reboot no problem, on latest StagOS. But yest I went thru several different ROMs and sometimes I could flash BluSpark no problem and sometimes no matter if I had flashed it the last time I was on "said ROM" but this time it's wld not boot no matter what I did. I think maybe the problem is, if ur on a ROM w/BluSpark, if u switch ROMs if u don't reflash stock dtbo, vendor_boot, and boot imgs for "said" rom b4 and switching roms that is the problem that keeps u from flashing kernal after switching roms. So now I reflash those imgs, reboot into stock rom(no root, no kernal) then back to BL and then flash the 3 imgs to go into recovery to go to different rom(lol) then once set up and rooted I can flash BluSpark fine.. I am not sure....
Edit/update
Ok, so testing my theory, I went from having StagOS on slotA(I restored dtbo, vendor_boot and boot) and then rebooted, went to BL, flashed new imgs for SparkOS, went to recovery, wiped and adb sideload the new ROM.. after setting up and rooting I attempted to flash BluSpark. I was on slotB, also I had went from one ROM on slotA and now different one on slotB. Forced to fastboot.. I had to reflash Spark imgs, then I went to recovery and adb sideloaded ROM again to get to slotA.. Then I successfully flashed BluSpark!
So for BluSpark to work you either 1) have to be on slotA or 2)u need to have whatever ROM u are on, on both slots..thank you eng.stk for great kernal!! Maybe u can confirm/deny my theory..
While is possible, I don't recommend because of what's above.Can you flash this via adb sideload instead? (Im unrooted/stock)
thanks for that, i tried the r96 version on StagOs with FKM and it kept going to fastboot, it worked perfectly with Kernel FlasherIf you guys want a nice free and open source app tp flash kernel zips, backup and restore stock partitions and so on, check out Kernel Flasher:
![]()
[DEV] Kernel Flasher
Kernel Flasher is an Android app to flash, backup, and restore kernels. Features Flash AK3 kernel zips Backup and Restore kernel partitions Mount, Map, and Resize vendor_dlkm Save dmesg and logcat Planned and Potential Features Keep original...forum.xda-developers.com
![]()
GitHub - capntrips/KernelFlasher: Kernel Flasher is an Android app to flash, backup, and restore kernels.
Kernel Flasher is an Android app to flash, backup, and restore kernels. - GitHub - capntrips/KernelFlasher: Kernel Flasher is an Android app to flash, backup, and restore kernels.github.com
There's the ability to save the kernel flash log to Downloads folder and share it here in case of any hiccups.
It's done by @capntrips , which has been doing quite some work in all this logical partitions/avb stuff we've been talking about, both on AK3 and other mods/solutions.
Highly recommended.
Can you please describe the steps you made in detail & what copy.zip file? Im in a bootloop altough i restored vendor_boot, dtbo and boot images.Yeah, It took me couple of hour of experiment in getting spark kernel to get it working, because it keep sending me back to fastboot menu even on LOS 28 June update. I installed it through Fk manager, it sent me to fastboot menu even though I flashed every img files. Then I adb sideload copy.zip after flashing LOS rom and Gapps, reboot to system and reboot to recovery to flash magisk and reboot to system again and then reboot to recovery and then use LOS recovery to flash spark kernel successfully.
Can you please describe the steps you made in detail & what copy.zip file? Im in a bootloop altough i restored vendor_boot, dtbo and boot images.
Dirty flash the rom and start overCan you please describe the steps you made in detail & what copy.zip file? Im in a bootloop altough i restored vendor_boot, dtbo and boot images.
Your super partition is dirty. You probably got it while using that copy partition zip.Still not able to flash this kernel even with the new app. I'm on a LE2127 (TMO OP9P) w/ LOS 19.1 and Magisk 25.1. Everytime I try to flash the kernel, it fails and my phone gets soft-bricked if I reboot. I've been able to recover to stock LOS w/o having to wipe data fortunately. I've flashed C.48 firmware (and the copy partition zip) as well but still fails. I've attached the logs from the kernel flashing app. Thanks.
Edit: I can do a logcat if the app logs aren't sufficient. Thanks.
Growing partition 0
Not enough space to resize partition
Creating vendor_dlkm_ak3 failed. Aborting...
fastboot flash odm_a odm.img
fastboot flash product_a product.img
fastboot flash system_a system.img
fastboot flash system_ext_a system_ext.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_dlkm_a vendor_dlkm.img
Thanks for the info - Works perfectly now.Your super partition is dirty. You probably got it while using that copy partition zip.
Also got it after use it a couple times. I advise people to stay away from that zip, it misses some stuff we have in newer devices.
Flash OOS 12 in both slots to get proper fw installed.
Go for regular LOS flash in both slots.
Unpack your LOS zip to get img and flash the logical partitions in fastbootd (NOT fastboot)
do it for slot a AND b
Kernel apps like FKM or EXKM.hi, in the changelog says that there are some boost options turned of, how can i activate them ?
these ones:
1. Kernel apps like I saidthese ones:
- msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driveradrenoboost ready (disabled by default)
- and could i install this blu_spark r96 in oos 12_c48 ?.
- ThinLTO build with custom upstream LLVM 14.x (Clang 14.0.5 + LLD linker + IAS)
- Couple cleanup reverts
- Fix some build naming and actions
- For root, Magisk 25.1 or newer is mandatory
- Merge lineage-19.1-20220719-nightly kernel updates
- For root, Magisk 25.1 or newer is mandatory
- Merge lineage-19.1-20220712-nightly kernel updates
- For root, Magisk 25.1 or newer is mandatory
- Merge lineage-19.1-20220726-nightly kernel updates
- Small rebase and cleanup
- Flash vendor_dlkm temporary fix
- AnyKernel3 updates (v20220727)
- For root, Magisk 25.2 or newer is mandatory
Changes are needed for C.61 fw, will push a build today or tomorrow when I update my LOS.With Crdroid based on OOS12 firmware C.61 you can't install this kernel it just out right fails. Hopefully it will be updated soon!
- Build with Google Clang 12.0.5 + LLD linker
- Synchronize codes for OnePlus 9/Pro Oxygen 11.2.6.6.LE25AA
- Several build error fixes and quirks handled
- Compilation improvements an cruf removed
- Some goodies already merged like filesystem stuff, cpu governor & boost/msm perf, TCP algos, wakelock blocker, vibration and haptic feedback control, gpu adrenoboost, etc
- All drivers builtin, wifi stack and datarmmnet merged from CAF
- net/wireguard: merge v1.0.20210424
- Synchronize codes for OnePlus 9 Oxygen 11.2.10.10
- f2fs: shrink node_write lock coverage
- AnyKernel3 updates (v20211215)
- Couple init runtime adjusts to better UX
- For root, Magisk 23.0 or higher is mandatory
- Build with Google Clang 14.0.1 + LLD linker
- wakelock blocker updates
- Couple build reverts
- AnyKernel3 updates (v20220126)
- For root, Magisk 24.1 or newer is mandatory