Ok you need to provide a lot more information than what you have already!
When did you unlock?
Have you used any tools?
Have you gone back to stock?
What do you have installed now and what have you installed before?
When / how did you install elemental X?
If all else fails there's a guide to retrieve your fingerprint.
Are you stating that your fingerprint option is missing from your ROM or run kernel options?
You've provided so little information I can't begin to help you
On the page before this, in this thread someone else had the same issue, flashed the stock boot img and then it worked again.
Sorry i'm a novice
I will re-complete the information
phone: oneplus 8pro
OS: H2OS 10.5.14
BL unlock： unlock
Kernel installed through elemental X APP
Have not used other optimization tools
I refreshed the brand new H2OS 10.5.14 ROM again
Install the kernel through the EX APP again
The fingerprint option disappears in the setting interface again
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.
@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