I have no idea what ROMs it will or won't work with, there are too many. For many years now, my kernels are made to work with stock ROMs.ok so the answer is no, i cannot boot.... why does it get advertised if it's going to result with me unable to boot? @flar2
Yep but as the apps installed surely there should be a validity check for the OS in use on that device right?I have no idea what ROMs it will or won't work with, there are too many. For many years now, my kernels are made to work with stock ROMs.
Get the app, if it offers it and you're on stock then it'll workHi, is anyone using this on the 8t? If so how is it compared to radioactive kernel? I saw radioactive is no longer being maintained and im looking for an alternative.
I had problems with charging with standard chargers.Hi, is anyone using this on the 8t? If so how is it compared to radioactive kernel? I saw radioactive is no longer being maintained and im looking for an alternative.
trueI have no idea what ROMs it will or won't work with, there are too many. For many years now, my kernels are made to work with stock ROMs.
Update original ONEPLUS software and then flash the correct kernelLost finger print android 10 after updating from magisk patched stock boot, would someone help me to fix this issue?
But I need android 10, what is the best kernel version ?Update original ONEPLUS software and then flash the correct kernel
Try omega or bluSpark. But why don't go to Android 11?
My Tesla keeps disconnected on android 11
Try omega kernel
It's not a Kernel issue, just coincidenceOP8 pro Androi 10 10.5.12, i flashed ElementX 1.08, kernel working fine but when watching facebook video the phone getting hot, CPU about 42 cel ( enviroment 20cel), never meet with stock.
I might be able to shed a bit of light.
The QCom CrashDump Mode seems to be due to a kernel or dtbo mismatch, for example @mauronofrio and I noticed it when the kernel was updated between OOS versions but not in TWRP's .img. The solution was to always use the latest prebuilt stock kernel and use the one from India, IIRC.
So, if I had to guess why restoring a kernel backup might cause this issue, I'd probably think perhaps the user made that backup before getting an OTA or something, so once they went to restore it it wasn't for the correct OOS version anymore.
So none of that would be flar2 or EXKM's fault, but more on the end user for not understanding how their device behaves or updating their backups.
It's either that or also could be the audio modules. I seem to recall ending up in download mode once while fooling around with the audio modules.
@czerdrill, @old_fart can you please report exactly steps how you backup and restore through the exkm app ( before getting crashdump)
Are you sure you didn't try to restore a backup from a previous oos ?
---------- Post added at 09:14 AM ---------- Previous post was at 08:42 AM ----------
That's i believe the issue...
Most custom kernels are using custom dtbo
So users when they restoring stock kernel through your app the stock dtbo it doesn't be restored...
It will be very useful to add a dtbo.img backup ..
I go to kernel backup, click the saved backup i have and say yes to restore. I want to be clear i don't think it's ekxms fault either, it's something i did I'm sure. It's possible i restored from an earlier version although i make it a habit to backup after each update.
In another instance i restored the stock kernel and lost wifi and lte. Was only able to get them back after flashing elemental again.
I don't know what I'm doing wrong but was just sharing my experience.
Sent from my IN2025 using Tapatalk