[KERNEL] [April 4] OnePlus 8 Pro ElementalX 2.06

Search This thread

dladz

Senior Member
Aug 24, 2010
14,971
5,306
Liverpool
Huawei Watch 2
OnePlus 10 Pro
There is no fingerprint option in the settings option


Ok you need to provide a lot more information than what you have already!

What phone??
What option?
What OS?
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.
 
Last edited:
Oct 13, 2020
6
1
Ok you need to provide a lot more information than what you have already!

What phone??
What option?
What OS?
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
 
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
14,971
5,306
Liverpool
Huawei Watch 2
OnePlus 10 Pro
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


That's no problem mate, so I've attached my screen grab of about phone.

You can see the model is IN2023 so this is the EU model.

I think yours may be the Chinese version looking at the OS H2OS I think, so does your phone not have google apps?

I would flash back the stock kernel apparently that fixes it.

If you are indeed using hydrogen OS then I would convert to global, although this probably isn't the place to talk about that.

Search within this thread for the keyword fingerprint, you can do this from the top of the page by clicking the setting cog then choosing the settings I have in the image I've uploaded, other people have had this issue.

Also as you've had a problem with your fingerprint it would make sense to back up your persist partition, again search for how to do this.

Personally I've never had to do any of this
 

Attachments

  • Screenshot_20210109-135836.jpg
    Screenshot_20210109-135836.jpg
    217.5 KB · Views: 129
  • Screenshot_20210109-140800.jpg
    Screenshot_20210109-140800.jpg
    214.2 KB · Views: 129
  • Like
Reactions: luckydedaojing

alex moymoy

Senior Member
Nov 2, 2015
194
51
@flar2 Hi 🙂 do you support custom ROMs?
Or better, does your kernel works on custom ROMs?
Thanks for your work and keep strong 😉
Thanks in advance ☺️
 

dladz

Senior Member
Aug 24, 2010
14,971
5,306
Liverpool
Huawei Watch 2
OnePlus 10 Pro
Battery looking good.

Can't seem to get the phone to go to 0-1% overnight, have managed this with every other phone but this. 1-3% but 9 times out of 10 it's 3-5%

Deep sleep is by the looks of it doing it's job.
 

Attachments

  • Screenshot_20210112-025348.jpg
    Screenshot_20210112-025348.jpg
    370.7 KB · Views: 137
  • Screenshot_20210112-025325.jpg
    Screenshot_20210112-025325.jpg
    307.3 KB · Views: 130
  • Screenshot_20210112-025401.jpg
    Screenshot_20210112-025401.jpg
    372.2 KB · Views: 124
  • Screenshot_20210112-025316.jpg
    Screenshot_20210112-025316.jpg
    312.3 KB · Views: 121
  • Screenshot_20210112-025657.jpg
    Screenshot_20210112-025657.jpg
    297.8 KB · Views: 128

dladz

Senior Member
Aug 24, 2010
14,971
5,306
Liverpool
Huawei Watch 2
OnePlus 10 Pro
New update has been released

11.0.3.3

Tested your kernel with the EU/UK version of the phone.

There's a bug in the firmware though, the screen takes a second or more to turn on when unlocking your phone.

Same symptom with your kernel @flar2

Not sure there's a great deal that can be done about it.

PS: stock and patched boot images in my payload dumper guide.
 

tohtorin

Senior Member
EDIT: Managed to get it compile but dont know why.

Hi and very sorry to bother you with this but it seems that there is only quite a few people who can help me with this..

I've been using ElementalX for years now (almost ten years?) but now with OP8T I've decided to try to compile kernel by myself. I am very experienced Linux admin, but pretty poor developer.

I managed to get furthest with commits in attached picture.

I tried with my CentOS building server and with ubuntu as well. No luck with either one.

Clang version:

Android (6305083 based on r377782c) clang version 10.0.5 (https://android.googlesource.com/toolchain/llvm-project 0cb1afdb060d6619a9837ab6866cf4adf2336416)
Target: x86_64-unknown-linux-gnu

Toolchain cloned from:


My compiling commands:

export ARCH=arm64
export SUBARCH=arm64
export DTC_EXT=dtc

make O=out ARCH=arm64 op8-perf_defconfig

PATH=/home/drgreen/android/clang/bin:/home/drgreen/android/toolchain/bin:${PATH} make -j$(nproc --all) O=out ARCH=arm64 CC=clang CLANG_TRIPLE=aarch64-linux-gnu- CROSS_COMPILE=aarch64-linux-android-

It starts to compile and compiles for like 5-10 minutes untils it fails to this error:

make[3]: *** No rule to make target 'arch/arm64/boot/dts/qcom/apq8016-sbc.dtb', needed by '__build'. Stop.
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [../scripts/Makefile.build:642: arch/arm64/boot/dts/qcom] Error 2
make[1]: *** [arch/arm64/Makefile:172: dtbs] Error 2
make[1]: *** Waiting for unfinished jobs....

I would appreciate if you have even a smallest moment for my issue :D

Love your kernels and eagerly waiting ElementalX 2.00 (saw from github that its coming..)

My goal is actually now to try to keep with as stock as possible with only wireguard suppor built inline.

Thanks in advance!
 

Attachments

  • Screenshot_20210130_131001.png
    Screenshot_20210130_131001.png
    272.3 KB · Views: 102
Last edited:
  • Like
Reactions: dladz and BrickL0rd

BrickL0rd

Senior Member
Dec 29, 2010
236
33
near Vienna
OnePlus 8T
loved your kernels for htc m7 and m10, still using exkm. wondering if there is an update coming for the 8T.
kinda new to 1+ and kinda lost and out of the loop since my P30 was unmodded. so is the 2.xx kernel version working for the 8T/ last firmware A11?

cheers
 

Top Liked Posts

  • There are no posts matching your filters.
  • 41
    ElementalX Kernel
    for OnePlus 8 Pro
    p3890301369-11.jpg


    ElementalX is designed for maximum stability. It is made for people who depend on their phone every day.


    Features:
    -Optimized for performance and battery life
    -Advanced color control (RGB, hue, saturation, contrast, value, K-Lapse)
    -Adjust vibration
    -Wake gestures (S2W & DT2W)
    -Sweep2sleep
    -Block wakelocks
    -CFQ, noop, BFQ, deadline, FIOPS, SIO, maple and zen i/o schedulers
    -Adrenoboost option
    -Option to disable fsync
    -Option to disable touchboost
    -WireGuard support


    Installation
    1. Flash directly in EX Kernel Manager (root is required to flash in the app)

    Notes

    Stay up to date with EX Kernel Manager. The latest updates are always available through the app. EXKM can be used to configure settings, backup and flash zips and img files, run scripts and install kernel updates quickly and easily. EXKM is compatible with all devices and kernels and is the best supported and most complete kernel manager available.

    Thanks to @tbalden for getting this running on the 8 Pro

    Downloads

    Android 10
    ElementalX-OP8-1.08



    Source code:
    https://github.com/flar2/OnePlus8







    .


    XDA:DevDB Information
    ElementalX OnePlus 8, Kernel for the OnePlus 8 Pro

    Contributors
    flar2
    Source Code: https://github.com/flar2/OnePlus8

    Kernel Special Features:

    Version Information
    Status:
    Beta

    Created 2020-05-11
    Last Updated 2020-08-03
    8
    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.
    7
    Some of you may remember a few years ago I had an app called Wake Gestures. It stopped working and I never got around to fixing it, but I left the wake gestures function in most of my kernels. Good news for those who liked that app, I've added support for Wake Gestures to Button Mapper and it is supported on the OnePlus 8 series as well as almost every other phone with sweep2wake built into the kernel (root is required)

    Wake Gestures allows you to set an action for a swipe in any direction or a double tap, while the screen is off. OnePlus has basically the same feature, but Button Mapper lets you assign basically any action. From basic stuff like toggling the flashlight or wifi, to broadcasting custom intents or executing root commands. Lots of possibilities.

    You need version 1.45 of Button Mapper, which is only on XDA Labs for now:
    https://labs.xda-developers.com/store/app/flar2.homebutton
    6
    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 ..

    No kernel on the OP8 Pro Forums is flashing a custom dtbo.img as far as I can see. Feel free to double check.

    Most kernels include custom dtb in their AK installers. Some kernels might flash them to the wrong place (appended dtb), instead of the new separate dtb section introduced in Android 10.
    Restoring the correct stock boot.img will overwrite these changes however, as the dtb is still part of the boot.img unlike a custom dtbo.img. So I don´t see this problem being caused by restoring a boot.img.

    What can cause problems indeed like @osm0sis mentioned is restoring a boot.img that doesn´t match either the firmware variant (ba, aa, etc) or that is not matching the correct firmware version such as flashing 10.5.6 vs 10.5.9 and having a mismatch there.
    Using the dtb from 10.5.6 on a device running 10.5.9 will result in a crashdump screen as described by users. I tested this myself since it took OnePlus a week to update the source. Once I removed the dtb from my AK3 zip, I was able to boot a 10.5.6 source built kernel Image with 10.5.9 dtb.

    I saw quite a few posts where people uploaded a boot.img for other users without detailing the variant specifically for example.
    I advise everybody to take their own backups of their boot.img´s and not rely on others. It´s good practice and can help you to recover your device.

    Another thing to keep in mind that maybe not everybody is aware of when taking their own backups, which can result in mismatching boot.imgs:
    If you flash an OTA via OnePlus Updater and backup the boot.img without doing a complete reboot after the OTA, you will end up with a boot.img from the OLD firmware not the updated one if I´m not mistaken. @flar2 can gladly correct me here, but I think EXKM always backs up the active slot.
    So if you´re on slot a, flash OTA via OnePlus Updater (this is flashed to slot b), go to EXKM to backup the boot.img you will end up with a backup of the outdated firmware, since slot a is still the active one. The OS switches slots on the reboot following the OTA Update.


    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

    You´re probably restoring a mismatching boot.img. This results in modmagic for kernel modules failing (stock kernels have modmagic enabled) and the WLAN driver cannot be loaded.
    EX-Kernel disables this modmagic check for kernel modules, hence WiFi works fine for you again.
    You need to flash exactly the same boot.img from the firmware you´re running to get back to stock.
    6
    If the problem is flashing alternate dtbo.img from other kernels, perhaps I will add a dtbo partition backup to EXKM as well, that way you can save the stock dtbo.img before flashing other kernels. You would need that for compatibility with ElementalX as well.