yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Nitemare3219:
Really wanting to use the new functions (which require root) in 0.4, but root seems like a complex situation right now. Can we get some clarification on IF and HOW root can be accomplished WITH this kernel? Or do we need to wait for flar2 to bake it into the kernel?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
well didn't you say to flash boot elementalx first, and then flash boot the root image? I did that.. it doesn't show elemental as my kernal after i flashboot the root image after flash booting elemental
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] andresee:
Did you look to see if it was running in about phone. And also you need to fastboot flash not fastboot boot. But i would assume ElementalX is not loaded.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
ok so right now i should flashboot flash elemental x img, and then flashboot boot root img?

and if i wanted to uninstall elemtnal x, i couldn't right?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Update!!

Changes for 0.05:

-add vibration control

Obviously you'll need root to play with this stuff.

Here's the procedure:

1. reboot to bootloader

2. fastboot flash boot_a EX-PXL-0.05.img

3. fastboot boot boot-to-root.img

4. Profit...

I just pushed an update to EX Kernel Manager. Version 2.93 fully supports the Pixel. It fixes the crash on the Graphics screen, adds vibration control, updates to work with all GPU settings, and fixes Kernel Backups.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
If i flashed to the wrong bootslot the first time, is there any consequence? I did it to a ... but then saw ur OP and found out mine was b, so im doing it to bootslot b now.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
It's probably OK
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
You can uninstall by flashing the stock boot.img
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
probably?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Hey [MENTION=4684315]flar2[/MENTION] I'm using the latest EXKM - however when I tap "Graphics" it FC's, guessing the app needs updating?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
same
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
An update to fix that is rolling out now. Keep an eye out for version 2.93
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
where do i get stock boot.img file?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Awesome mate, all over it!

Edit: Literally just showed up. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] apascual89:
I just updated from play store and all good here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
It's been like that all along. I think all kernel use these methods since Marshmallow, since the ramdisk needs to be preserved for things like root.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TonikJDK:
TWRP RC2 is bootlooping on install with May also. Even a boot to TWRP img and SU install loops stock. Just an fyi on what we are seeing.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garrettsessions:
Sorry for the confusion - I've been following your post here for a while: https://xdaforums.com/showpost.php?p=69786454&postcount=719

I'll look into TWRP. Thank you!!!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Update!!

Download:

ElementalX-P-1.10.zip

Changes:

-May security update
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Oh, I forgot about that, it was unique to this device. Hmm, now I'm curiious why it doesn't work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
It happens even on stock so I think twrp and supersu will need to be updated to work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Yes, I just updated and installed TWRP and SuperSU, bootlooping.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Version 1.10 works fine on the stock ROM from April.

Will have to investigate the changes for May.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JimSmith94:
From one of the other threads about the May security update bootloops:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kbtoiz:
I read on Reddit today that the May update breaks TWRP and SU, and cause bootloop. I dont think is your kernel.

I just came here to ask how you can update the kernel thru the Elemental app?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
In my brief reading this evening it seems that the may bootloader has brought incompatibility with twrp and supersu. Flashing the April bootloader on the may firmware works.

To answer your question about updating using exkm, go to the burger menu and tap ElementalX (or tap the very bottom part of the home screen, where it shows uptime and current kernel) and then tap the blue button and choose express(to keep current settings) or custom (which uses the aroma installing to make changes.) The kernel will download to /sdcard/ElementalX

You can have the app reboot into twrp but you still need to manually flash the kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kbtoiz:
Ok sir! Thanks!:good:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Tylog:
Flash the Bootloader from April , the issues With the May build coming through the new bootloader. May update with april bootloader, twrp and SuperSu works.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xocomaox:
Yeah, the Kernel Manager only acts as a downloader for the file, since you have to manually flash it. Hey, it beats going out to this thread every time!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] b4u2:
Is there a place/forum where people share there settings? I am mostly gaming on my device and looking for settings that deal with that. Better battery life (SOT) would be nice but i do realize that gaming eats up a lot. So just looking to see what others (Gamers) have set up.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
RE: May bootloader problem

https://source.android.com/security/bulletin/2017-05-01#eop-in-htc-bootloader

I haven't tried to debug this yet, but it appears that replacing the boot.img or kernel in any way causes a bootloop. I'm not even equipped to debug this kind of thing, you would need someone like jcase who knows a lot about HTC bootloaders.

I wonder how long we will be able to use the April bootloader without something else breaking?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
Running great on 1.10

Thank You
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
Built new crDroid with ElementalX 1.10 and it's working great. Thanks for the awesome kernel, and crazy fast updates [MENTION=4684315]flar2[/MENTION] !
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Latest PureNexus + EX 1.10 is running beautifully [MENTION=4684315]flar2[/MENTION] -- Going to stay away from May's bootloader for now. That would be why I was getting the ramdump.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] yahya1054:
For some reason when o install this kernel google splash screen boots up quicker than other kernels + I really like CPU times just awesome flar2 thank you digging your kernel thank you!

Rums great on pixel dust :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garrettsessions:
Chainfire posted this. Maybe it helps? https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Yes, that will do the trick
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Does that mean you would need to redo EX with the signed boot, for it to work on the May bootloader?

Will it still work on April's bootloader if it is signed?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dablitzkrieg:
I'm on the latest pure Nexus. Will 1.10 work or will cause bootloops?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Yes, it will still work.

The kernel itself is compatible with everything, the boot loops are caused by using an unsigned image on the may bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 5.1:
Hello,

You can install it... :)

Cheers...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Yes...but if you have the latest may bootloader you'll need to wait for my next release.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Tylog:
The best will be we make ourselves a "bootloader is to blame" macro :D
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ih8un:
Just a few quick questions if someone can please help

Is there any point flashing this kernel without the EXkernel app?

How do I identify which bootloader version date I'm using? I'm currently on latest ROM PN 7.1.2 and Elemental 1.09, but unsure which bootloader version and date, and as I understand the May bootloader would cause a bootloop with version 1.10 of this kernel

Thanks :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
The kernel is quite usable without a kernel tuning app. You can set up quite a few options during the AROMA installation. But obviously it's nice to have the flexibility that EXKM provides.

You can check the bootloader version by running 'fastboot getvar all' or just visually checking the bootloader screen.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Iceman248:
Can someone explain to me the changes in this kernel? May security update has it sounding like it fixed the May bootloader issue, which personally I don't care about. I'll stay on April. So I'm just not understanding what's changed in this kernel.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 5.1:
Hello,

The May release hasn't fixed anything yet. But the developers are now aware of the issue. The next release is supposed to work with May bootloader.

Cheers...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
Here's the May security bulletin. It's a long list, not just the bootloader fix that is causing unsigned boot.img to not boot. [MENTION=4684315]flar2[/MENTION] ported the fixes affecting the stock kernel to ElementalX 1.10.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Nothing really important, just a few minor security updates, one of which requires the boot image to be signed. Otherwise, these don't have a noticeable effect on anything.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Iceman248:
Okay, so I'll just stick with current version then. I don't see any reason to update, as like I said, I'm not going after the May bootloader anytime soon. I see no reason to. Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Eventually you should update. The security stuff is way overhyped, but it's still a good idea to stay up to date.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] SuperNickyP:
So, basically gonna have to have the zip sign the image now. Like Chainfire is doing.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Yeah, it should be no big deal. I will probably look at it this weekend. I don't find it urgent at the moment since nobody could install it without an updated TWRP anyway.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
Chainfire has posted a verified boot signer archive that should be flashed after boot image is modified and before a reboot to recovery / system. Updated TWRP isn't required because you can fastboot boot unsigned TWRP boot image.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] micmars:
Yes, but if you plan on remaining on Elemental X, I believe that you'll want to wait for flar2's update, inasmuch as his kernel will have a signature unique for him.

It is my understanding that future updates will require using the same signature or bootloops so recur.

Sent from my Pixel XL, #WhiteUIsMustDie, #EndDarkAppOppression
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
The entire boot.img is being signed, not just the kernel. Every developer will have to use a generated key, so TWRP, SuperSU, Magisk, and all custom kernels will be signing the boot.img with different keys. Since multiple reboots to recovery / system are usually required, the bootloader will encounter different signatures. If this will indeed result in a bootloop, then we're just better off using a separate signing zip like Chainfire's after modifying the boot.img and before rebooting to recovery / system in order to maintain the same signature.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] micmars:
Boot=kernel.

I understand that the kernel is being signed, but I believe that zip only signs the modified image of the partition only if a modified kernel or recovery image is unsigned.

Something about which I'm unclear is if the different components of the sector (boot and recovery) can have separate signatures.

If they cannot, then flashing that common zip from Chainfire would be needed with each flash, or it's bootloops.

If they can, then I'd think waiting for flar2's update is warranted.

Chainfire's post on the topic is here,

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606

Sent from my Pixel XL, #WhiteUIsMustDie, #EndDarkAppOppression
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
On our device recovery and kernel ARE parts of the boot.img. Not sure what you're referring to when you say "the sector (boot and recovery)". A partition has one signature, the entire boot.img is signed.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] micmars:
Yes, you are right about the boot image containing recovery and kernel and the entire thing being signed.

Thank you.

Then what of my original question? Must recovery and kernel have the same signature for future iterations of a given kernel?

Sent from my Pixel XL, #WhiteUIsMustDie, #EndDarkAppOppression
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
TWRP, SuperSU and custom kernels will all be signing the same partition. Only the last signature will matter as it will be the one seen by bootloader during the following boot. I don't see how seeing a different signature during a subsequent boot cycle will cause the bootloader to abort.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] micmars:
Because of this block of text in the post by Chainfire...

If anyone locks the bootloader, documentation implies that the device will require that same signature after it's unlocked.

It's why Chainfire recommends that developers use a unique set of keys for each supported device. I have never relocked my bootloader, but there are those who do.

The issue is far narrower than my original posts on the matter implied, but it still seems to me to be an issue that developers will redress, irrespective of whether it matters to one whom keeps his or her device unlocked.

Sent from my Pixel XL, #WhiteUIsMustDie, #EndDarkAppOppression
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Update!!

The only change here is that the installer now signs the boot image. I installed it many times in different scenarios and so far so good.

Many thanks to [MENTION=631273]Chainfire[/MENTION] for figuring this out

Download:

ElementalX-P-1.11.zip

Changes:

-add boot signing to installer
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
It's even narrower than that. There's a great pinned thread in General by [MENTION=2376614]jcase[/MENTION] titled "[PSA] Read before relocking your bootloader". He unequivocally states "If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it." In other words, bootloader should only be re-locked after flashing a stock factory image, which would obviously overwrite any custom signed boot.img. So this is definitely not an issue if one follows best practices.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] micmars:
I agree with you.

Yet I've been on xda long enough to have borne witness to users with little sense of sanity or hesitation.

When I first read Chainfire's post, I took note of the warning and kept it, but I clearly flubbed on most of the details as to why.

I've no disagreement with anything you've posted, but what a senior RD suggests may not be what the dev community collectively does.

The element of time will bear this out.

Sent from my Pixel XL, #WhiteUIsMustDie, #EndDarkAppOppression
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dmb219:
Thanks for the update, installation went fine. Stock with this kernel is the way to go for me. Hard to beat.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
Chainfire has posted VerifiedBootSigner v2 with better error handling.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
I have always rocked Pixel XL with stock Google images, twrp'd, rooted, ElementalX'd. Currently am on April image. Should I do the following:

- In bootloader, flash May factory image after removing -w (so that my data is safe).

- Phone reboots automatically. Go back to bootloader.

- fastboot boot twrp img

- In twrp, fastboot flash twrp zip (i prefer rc1 since i dont use magisk and prefer to have backup/restore option)

- Still in twrp, install latest supersu (2.79SR3)

- Still in twrp, install Ex1.11

- reboot system

With Flar's Ex1.11, do I need to use Chainfire's VerifiedBootSigner-v2.zip?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
Not if you're not rebooting to system after installing SuperSU and before installing ElementalX.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
I am also wondering if this is the step by step directions to update to May updates?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] garrettsessions:
Going forward is TWRP the only way to install or will the fastboot flash kernel command work? Thanks for the quick update!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Reboot after installing SuperSU

You don't need to flash the verifoedbootsigner zip. EX installer signs it.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Signing requires an Android environment to work, so you you need to use TWRP.

If you don't want to flash TWRP permanently, you can just fastboot boot TWRP and install EX.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
Reboot after installing su but before installing 1.11? Or reboot recovery after installing su then Install 1.11 sorry I'm a little confused?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
Won't I have to flash chainfire's bootsigner zip after flashing SuperSU and before reboot? Also, is it reboot system, or reboot recovery? Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Yes, and reboot system.

I'm not sure if you *need* to reboot directly after installing SuperSU, but I always do and never have problems that way.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] kirschdog1:
Delete sorry not kernel related.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
Just to re-iterate this in case flar2's answer wasn't clear. (It wasn't to me until I read it twice ;) ) I also always reboot to system after installing SuperSU. In this scenario, VerifiedBootSigner-v2.zip should be flashed before the reboot if on May bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JimSmith94:
Sorry if this has already been addressed and I missed it. Does this kernel signing the boot image eliminate the need to install Chainfire's boot signer, or should they both be used?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
If ElementalX is the last thing you're flashing, you don't need to flash Chainfire's boot signer. If you have a non-stock boot.img and need to reboot to system or recovery before flashing ElementalX or after you've flashed another package modifying the boot.img, then use Chainfire's zip.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JimSmith94:
Thanks for the quick reply and explanation! Since I root with Magisk I'll use Chainfire's zip too.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Kisakuku:
Updated directions for flashing Magisk and custom kernels on May bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
Elx 1.11 all working as expected. However I have not updated to the May bootloader.

Thank You
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JakeDHS07:
Tested with May bootloader and still cannot get it to boot. Back to April.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 5.1:
Hello,

What setup are.you running? ROM, recovery, SU?

Good luck...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JakeDHS07:
Pixel XL

Right now May update booting with April Bootloader

ElementalX kernel

RC2 TWRP

NO SuperSU I use Magisk which is why I use RC2 as it doesn't flash with RC1

---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------

Even flashing the kernel last which as far as I understand signs with the 1.11 version I still can't get May Bootloader to boot at all.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 5.1:
Hey,

What happens? Bootloop?

Is TWRP properly installed? What happens if you boot to recovery from bootloader? Does it boot RC2 zip you installed?

Good luck...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JakeDHS07:
Indeed bootloop. The only way I can get it to boot is to flash the April Bootloader again
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
Did you flash the VerifiedBootSigner-v2.zip at all?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JakeDHS07:
Yes I attempted it a few times. It fails every time
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 5.1:
Hey,

I had bootloop too. Did the boot signer zip installed properly? After bootloop, I powered the phone down and booted bootloader. And started over again: fastboot boot TWRP, install TWRP zip and boot signer zip.

Don't know why, but it worked this time. Not sure why?!

Running Pure Nexus homemade build with May security patch, installed over fresh N2G47O factory image. Plus TWRP RC1, SuperSu 2.79 sr3 and EX Kernel.

Also, installed in order: ROM, TWRP, boot signer v2 zip, reboot. SuperSu, boot signer, reboot. Ex Kernel, boot signer, reboot.

Good luck...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dablitzkrieg:
FYI, it still shows for me 1.10 in kernel version, after flashing 1.11
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ridobe:
Not here.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dablitzkrieg:
Reflash fixed it
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
So I installed May update and was able to boot phone after flashing twrp, supersu2.79SR3 and bootverifiedsigner-v3. Then I rebooted to recovery and flashed EX1.11. After selecting my options, selected 'Install ElementalX'. Now stuck at 30% for more than 5 min.

What should I do?

EX flashing stuck at 30% in twrp.

Edit: still stuck at 30% after more than 10 min. Pl suggest should I reboot and reflash EX1.11?

Edit 2: got it working by rebooting again into recovery and reflashing EX1.11. After EX1.11, simply rebooted system WITHOUT flashing bootsigner.zip. All well now. Cheers!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] veskostoev:
Hi, if i am on latest PN 7.1.2 and EX 1.10 is it safe to update kernel to 1.11 i read some bootloop coments. How is safety to update thru EX app or TWRP? Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
Bootloop is there only with May bootloader. That too if you don't flash either EX1.11 last before rebooting, or chainfire's verifiedbootsigner-v3 last before rebooting.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
I have been running Ex 1.11 sense it was released. No issues but I am not on the May bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
I couldn't get 1.11 to boot with May bootloader on PN 7.1.2. I tried the following:

1. Boot to bootloader

2. fastboot flash bootloader N2G47O & reboot to bootloader

3. fastboot boot twrp-rc1.img

4. install EX-1.11 & twrp-rc2

5. boot

It bootlooped, so back to April.