yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Hmmm I'm using magisk..Tried installing without magisk after too. Hell's core installing fine
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
I'm using Magisk on a just built crDroid with the new ElementalX and it's purring along. FWIW.

Thanks as always for the fast updates and superb kernel [MENTION=4684315]flar2[/MENTION] !!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Really odd I clean flashes

Flashed PN

Flashed twrp

Rebooted to twrp

Flashed elemental kernel

Flash magisk

Reboot

Anything I did differently that might have caused a problem. Never has a problem before
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jlee08517:
After flashing pn, boot up and then reboot to twrp and flash elemental.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] hokiealumnus:
You left out flash TWRP after Magisk, but aside from that I don't see anything wrong.

That said, I bake the kernel into the ROM, not flash it separately.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] y2grae:
do we need a version sig flash on this update?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pcriz:
Booting into the OS isnt required. Not saying its wrong but it should work with the steps that are quoted.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Yeah I tried re flashing elemental twice after booting up anyway

Might be a one off

Will try again from the top another time:)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] xryptic:
Does any body know can I after a factory image, flash EX Kernel. After a successful reboot, flash Supersu (than sign) and reboot to system. Will I loose Ex Kernel or do I need to flash EX Kernel again?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] chazall1:
All functioning fine here on 1.12
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
I've seen this behavior before, and on multiple Pixels. I would like to know the cause and if there is a resolve:

I update my multiple Pixels every month when patches are released. After flashing the factory image and booting into TWRP, I flash EX. Sometimes, Aroma steps me through all the options while other times the only choices I get are the CPU frequencies. That is, the selection goes from CPU freqs directly to install. I am not prompted for I/O scheduler, slide to wake, etc.

I'd appreciate any info.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
You need supersu installed before flashing ex kernel to see those options in the aroma installer.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
Wow that was quick. Thank you. I just found another post (belonging to you I think with similar info). That makes sense. So in the case of Magisk and its needed flashing order (1-EX, 2-Magisk, 3-TWRP, 4-Signer), I will not be able to access those settings?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
Unfortunately not, afaik. I've never used magisk though so maybe another user can shed light on that
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
I tried to flash EX again (now that the device is already rooted w/ Magisk) but still did not get any options other than CPU freqs. So to your point, it needs to see SuperSU, not just root. With Magisk, the I/O Scheduler is also unavailable. Tradeoffs I guess...
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] GillRigged:
With the new June build I either have ElementalX with no recovery or TWRP with no bootable kernel (just keeps booting to recovery). Started using this kernel last month because I wanted to try out the tweaked version of Magisk which at first Aroma Installer gave me all options but then all other times would only show the options with SuperSU. So, I ended up going back to SuperSU since there's many trade-offs with using Magisk. One of these trade-offs is using FlashFire.

I have never been able to get Google images to flash properly from my computer and have been relying on either Unified Toolkit or FlashFire. However, this month I have been having issues with FlashFire most likely due to boot.img issues (signing?) Unified Toolkit hasn't been very reliable for image updates since January which has forced me to use FlashFire (always rooted) but that has never been successful at updating the kernel for me.

So, this month with the Android boot changes I tried using FlashFire since Skip hadn't updated Unified yet with the June builds and my PXL went into a bootloop. Managed to get the device to load the bootloader and tried to reboot to recovery. Hmmm ? no recovery. I used Unified to boot a temp TWRP, flashed the latest version of TWRP, boot sign v8, rebooted to TWRP, flashed SuperSU, boot sign v8 and then​ rebooted to OS. No OS. Just booted back to TWRP. Okay. I flashed ElementalX and boot sign v8 (not sure if that's necessary or not) and rebooted to OS. Great! Loaded up just fine but no root.

By this time I felt like all I needed to do is reflash SuperSU, reboot OS, reboot recovery, reflash ElementalX (I want those additional options) and then I should be good to go. Nope. No recovery. Wtf Tried several times and it's always only TWRP installed or ElementalX with no recovery. There seems to be no in-between with the June build for me.

Today, Skip updated the Unified Toolkit with the June builds and I started over with the full image flash. After that I flashed TWRP and SuperSU. Everything seemed to be just fine but I really like ElementalX (still have it on my deb) but same issues. Still one or the other. Anyone have any ideas?

---------- Post added at 11:09 PM ---------- Previous post was at 10:20 PM ----------

Update: I no longer can boot to bootloader. Now I can't even use Unified Toolkit to reflash images.

---------- Post added at 11:27 PM ---------- Previous post was at 11:09 PM ----------

Thank God for FlashFire. I was able to reflash the June build and regain access to the bootloader.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] GillRigged:
Well, I just can't seem to have TWRP, ElementalX 1.12, and SuperSU 2.82 with the June build for whatever reason. However, I had no issues installing the modified Pixel version of Magisk. So, back to that again this month which if fine with me since I like being able to use Android Pay and Netflix updates from the PlayStore.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
Here is what I did on June2017 update:

1. Copied flash-all.bat, bootloader img, radio img, image zip and twrp rc1 img into platform-tools folder.

2. Copied EX1.12 zip, SuperSu2.82 zip, twrp rc1 zip, VerifiedBootSignerV3 zip in my phone root folder.

3. Connected phone to laptop via USB.

4. Rebooted phone in bootloader mode.

5. Checked connectivity by response to command: fastboot devices.

6. Removed '-w' flag and then ran flash-all.bat and let it do its thing. The phone rebooted at the end of this step.

7. Checked android version and stuff, and then rebooted phone in bootloader mode.

8. fastboot boot twrp_rc1.img.

9. In twrp, flashed twrp_rc1.zip.

10. Flashed SuperSu2.82.zip.

11. Flashed VerifiedBootSigner_v3.zip.

12. Rebooted phone (it will bootloop about twice before coming on).

13. Rebooted phone in recovery.

14. Flashed EX1.12 and rebooted phone.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] GillRigged:
Hmmm. Maybe it's Rc2 that's causing the problems. I have been doing a temp boot into rc1, flashing rc2 and then so on.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] liam_davenport:
Everything fine here. Latest img + ElementalX v1.12 + SuperSu v2.82
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bemagrp:
This is exactly what i am doing and never failed for me.

Always using rc1 over rc2, because of reliability for nandroid backups.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jlee08517:
The aroma settings won't come up if it's rooted with magisk. Only supersu
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] imjimmy:
Hi - Thanks for the instructions.

Did these steps result in data/apps being preserved? Is this a dirty flash? Meaning can we use these instructions to flash over every month the security patch?

In the past, I used to use a custom ROM so I could just dirty flash the ROM and the kernel every month. But now I am trying with a rooted stock ROM with Elemental X kernel. So wanted to know the best way to preserve data and flash Kernel update + google security patch update every month.

Thanks.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] JimSmith94:
That's how I do it every month. Removing '-w' from flash-all.bat does a dirty flash without removing data and apps.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
Yes. Data and apps are preserved. Remember to remove -w from flash-all.bat. this is how I do it each month.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ithehappy:
So why not download the full OTA image and flash that? Or is there any benefit in doing the -w method?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sruel3216:
id like to know this also.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
[MENTION=4684315]flar2[/MENTION] is a phucking machine with no mercy!

Thanks for all the quick updates on such a new device. I always recommend Elemental X to anyone running CleanROM or stock!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
If i wanted to revert my phone back to stock and remove root, how would i do so?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Golf c:
Factory image.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
yea where do i get that? im new to this stuff, so when ppl say flash to stock image, i need step by step lol.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Golf c:
I would suggest you do some studying before you dip your wick!

https://developers.google.com/android/images
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] entraik:
im on a mac os. Would going into the bootloader and using the command 'flashboot flash (stockbootfilename).img' work?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] eRajesh:
Yes, it will.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Golf c:
Nope,

Extract boot.img from factory zip.

Place in platform tools folder.

Open command prompt in platform tools folder so you have the right path.

Type "fastboot flash boot_a boot.img"

If that don't work then try

" fastboot flash boot_b boot.img"

We are all learning this new structure of this device.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
As always... This kernal kicks a$$!

[MENTION=4684315]flar2[/MENTION], any chance of O/C? I like to push it up just a tiny bit. Other than that the kernel is awesome! Thanks for all your hard work!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
Definitely, but that will come later when recovery is finished and I work on the installer.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
Awesome man! Everything on the latest version is working great! Thanks again for the time and effort!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Scott:
Wow big jump in performance! Google should hire you :silly:

On stock I was about 7 devices down :confused:

Elemntal X brought me to the top :highfive:

[IMG="Elemental X .5"]http://xdaforums.com/attachment.php?attachmentid=3920137&stc=1&d=1477806005[/IMG]​
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] italia0101:
Awesome stuff, how much brighter does it get with hbm
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] nbhadusia:
What's the best app to use to control the kernel features like tap to wake etc? Has the new kernal effected battery life? Thanks!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jaythenut:
Definitely [MENTION=4684315]flar2[/MENTION] app to say thanks https://play.google.com/store/apps/details?id=flar2.exkernelmanager
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] italia0101:
Out of curiosity what's your geekbench... Wonder if we can over clock this to stock 821 speeds.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] sulpher:
Oops I forgot to check before I flashed... whats the pixel's stock governor/scheduler? (does stock really come with fiops?)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] TK 421:
DONE! Great kernel and APP. Even have the widgets for the performance modes!!!:D best I have ever used. Thanks [MENTION=4684315]flar2[/MENTION]!!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Golf c:
Sched
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] andresee:
[MENTION=4684315]flar2[/MENTION] will sound control for the speaker be possible? Everything is running great. Thanks again for your work.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
I don't think the OTA will flash unless you reflash the stock boot.img first.

I find it easier to download the factory image, remove the -w in the install script and go from there.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
For me, the OTA flashes fine even with a modified boot image. I did the OTA flash via TWRP process twice, but decided go to back using the full image in subsequent updates.

Here is why: With the full image, my procedure is that after "flashall", I catch the auto reboot (hold down vol down) so it goes directly back to the boot loader, then boot to TWRP, flash TWRP, all the mods/SU, then boot system. This way, the system boots with root and kernel exactly has it was when I shut it down to run the update.

With OTA, the first boot wipes out the root, which actually ends up being a longer process. In other words, with the OTA update, you have to let it boot without root, then restart the phone, and root. It seems like the part of the OTA process occurs during the first boot. Although this is not a problem, I prefer the full image method.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ithehappy:
Hmm, thanks. I did flash an OTA image via ADB on a modified boot.img too (but can't be 100% as it was long back), but I was simply meaning which one is the cleanlier method out of the two.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] imjimmy:
When exactly due you press the volume down button after the Flash -all script stops running. Usually when the scripts stops, it get backs in the bootloader where one can reboot system or go to recovery.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
Whenever I use the flash-all script, at the end of the flash, the phone reboots the system automatically (it does not reboot into bootloader). So I start to pay attention when it starts to flash the vendor image. At the conclusion of the flash, and as soon as the display goes black, I hold down the vol-down button. This causes the phone to reboot into the bootloader. From there, I fastboot boot twrp.img to flash the kernel, su, etc.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] ithehappy:
LoL that's what I thought from your original comment, and I know I am wrong, but it feels like doing that is somehow breaking a process to complete! But I am sure you know better, but still it feels kind of uneasy feeling doing that.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
I used to do that but now I let it reboot. You'll see a dialog about finishing updates if you let it reboot. I don't know what it's doing or if it's important, but it's probably best to let it do its thing.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
Yup, I know what you mean. I too had concerns, but when I root/EX/twrp before first boot, it still goes through the "finishing updates" on first boot and I never have any problems.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] pacman photog:
Flar2 anything for o? TWRP isn't working ATM. But maybe kernel in fastboot?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
I did a clean flash to May stock image (via flash-all). Then proceeded with TWRP RC2, and PureNexus. Then flashed SR1-2.82 SuperSU. Have root and everything running fine.

I flashed EX 1.12 and during the installation I have no option for gestures etc like I previously did, ideas?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] dmb219:
That's strange, EX options are absent when you don't have root but you say your root was good. I haven't tried the same combo, been stock for a couple weeks. I didn't have much luck with twrp rc2. Let us know what you find.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Tried again.

1. flash-all, flashed april bootloader on a/b just in case

2. Booted PN, setup phone etc

3. Rebooted to TWRP, flashed SR1-2.82, rebooted

4. Confirmed have root, rebooted to TWRP

5. Install EX, still no gesture options

Edit: went back to SR3-2.79 and options are back. Must be issue with 2.82
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] piccit:
Can't you just set the options in the app?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Reuben_skelz92:
Did it definitely install the kernel?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Soon as I saw no options for gestures upon install I exited the install.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] snovvman:
I saw the same re no options. For me, once 2.82 is flashed, if I let the system boot then go back to TWRP to flash ex, the options are there. It would seem that 2.82 completes the root process during first boot.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Didn't work for me. I had root, had adaway setup with root etc, but no options installing ex. Flashed SR3-2.79 and options were back.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Hi - I have stock ROM, rooted with SU 2.82, TWRP RC2 and EX 1.12. Everything runs perfect, except I accidently enabled Screen backlight dimmer on default while installing Elemental X kernal in the aroma installer. This takes down the screen brightness (I have disabled adaptive brightness in display). Now the setting sticks on every reboot. So the brightness of the phone becomes lower everytime I reboot. To fix this I have to toggle backlight screen dimmer OFF on EX Kernel Manager and then toggle adaptive brightness in Display settings to fix the brightness. This has to be done every reboot.

I was thinking of dirty flashing the Kernel again to run through the installer again and chose NOT to enable the backlight dimmer, so that the setting sticks.

However, whenever I reboot to recovery in TWRP, I am not able to flash the Kernel. It says enter password in MOUNT- Decrypt Data. If I hit cancel, and try to browse for the Kernel installer zip, I don't see my internal storage files and folder.

Can someone please help on how to flash this kernel again on top of existing settings via TWRP? Will I have to change slot and flash. TWRP says I am in slot A, and if Change slot, system goes into a bootloop. Thanks in advance.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Droid1019:
Just go to TWRP and flash the kernel. It'll just take you back through the install steps. Reboot. Enjoy.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] piccit:
You need to enter your password/pin in TWRP to decrypt data
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] bemagrp:
So, enter your password or swipe, or disabled it in security before rebooting to twrp.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] iamjimmy:
Thanks so much. That worked perfect.

---------- Post added at 01:51 AM ---------- Previous post was at 01:50 AM ----------

Thanks a bunch. Stupid omission on my part.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Riley Martin:
Safety Net and root

This kernel is amazing and gives me the much-needed patch for the safetynet check. After rooting my phone the patch no longer worked. I tried both rooting before and after the kernel install. Is this a known limitation, that safety net won't work on a rooted phone regardless of the patch?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] 3aucla1r3:
Yeah, EX will hide the unlocked bootloader but it won't hide root. It is an amazing kernel, you're right!
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Riley Martin:
Thanks for that info. I only use root to silence the camera without having to change settings or volume. I tried non-root options but they don't work well.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] gverma1:
Edit: nothing to it. Simply enabled OEM Unlocking option again and accepted all security messages and entered my pin.

Old query: Hi. On my phone, I went inside Developer Options and accidentally tapped on the top ON/OFF toggle (which enables/disables developer options). Along with that toggle, OEM unlocking toggle also switched off. I immediately turned the developer options toggle back on. However, OEM unlocking toggle is still in off mode. Do I simply tap it to make it On? Will this wipe my phone? Am confused. Anybody has faced this earlier? Thanks
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jiexi:
So i lost the gestures menu in the EX Manager app when updating the june bootloader and vendor on newest Pure Nexus rom using magisk even though the options were there before. Is this a problem with being on EX 1.12, or with the new bootloader/rom? or... should i just be using supersu now?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Juzman:
Issue with Magisk. Use SuperSU 2.79. :)
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] fiveighteen:
What do you mean by use SuperSU 2.79? In conjunction with Magisk Manager? At which point do we flash it?

Right now I've done the following and everything is working fine except the kernel doesn't see root and doesn't give me those extra options (as described by [MENTION=4622637]jiexi[/MENTION]):

Updated to June factory image with full wipe

ROM (PureNexus)

TWRP (3.0.1 RC2)

VBS8

Reboot

Vendor Image

Magisk (12.0 for Pixel)

TWRP

VB8

Reboot

ElementalX (1.12)

Reboot

Every time I've tried flashing SuperSU 1.79 SR3, I end up in some kind of boot loop and start over flashing. It's been a pain.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jiexi:
you need to use SuperSU 2.82

http://www.supersu.com/download
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Iceman248:
What exactly is the issue with Magisk?
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] carlylemiii:
You don't get the gesture options when you're installing Elemental.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] Iceman248:
Do you know why Magisk doesn't work with it though? I know it used to when I had it earlier, so I'm wondering what exactly is wrong and whether it's supposed to be resolved in that highly anticipated v13.
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] joetheshmo:
Probably SElinux
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] jschill31:
Hello,

I have EX running fine on June with Magisk...etc with SaftyNet passing. I see a lot of issues/questions on how to flash but not much on optimal settings and such? I went ahead and purchased EX tuning to support the dev as this is a solid stock based kernel. What should I be tweaking to gain better deep sleep times? I am seeing many with 7 hours or so SOT, are you just using sched and leaving all other adjustments as is? I am an old timer so I believe in reading through a thread. I did see the same type of question asked a few times but a couple were during the whole SU binaries issue and most had other challenges to overcome. Honestly this is not being asked because I have an issue, the kernel is doing what it should. I am new to Magisk on this device as I have always gone the SU route. I just want to make sure I am taking advantage of what can be while keeping things updating. There just seems to be a lot of "what if" on the horizon lately and my Pixel XL is not like my Nexus devices...

Cheers
[Google Pixel XL ROMs, Kernels, Recoveries, & Other] flar2:
There hasn't been a lot of tweaking on this device because it is so well optimized out of the box. The config app is more for controlling extra features like sweep2wake, sound and color control, vibration, etc. This kernel also adds high brightness mode, which is really useful outdoors.