yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] nathanchance:
What ROM are you using? I know Chroma and Pure Nexus have been updated so you don't even need it any more. Regardless of ROM, just dirty flash your ROM zip, then flash the EX zip with SELinux Enforcing checked in the Aroma installer. If it fails to boot, reboot into TWRP and flash EX again with that setting unchecked.
[Nexus 6  Original Android Development] flar2:
Update!!!

Update for Android 6.0.1

For stock ROM:

If you want root, you must use SuperSU 2.61 found here:

http://xdaforums.com/showpost.php?p=64161125&postcount=3

Flash SuperSU 2.61 in recovery, then flash ElementalX in recovery

You only need to install SuperSU the first time. Once you are successfully rooted, you can install any future update of ElementalX without reflashing SuperSU again.

If you install other kernels after this, you must flash stock boot.img, then SuperSU 2.61, and then ElementalX.

For pre-rooted custom ROM:

Just flash ElementalX

Download

ElementalX-N6-3.07

Changes:

-update for Android 6.0.1
[Nexus 6  Original Android Development] kevdog98:
I am using the stock from with EX 3.07. I have reflashed EX 3.07 with no luck. Boot ing is not my problem just the 4000% or so changing every few seconds issue. Thanks for your help.
[Nexus 6  Original Android Development] flar2:
Flash stock boot.img from 6.0.1, then flash SuperSU 2.61, then flash ElementalX
[Nexus 6  Original Android Development] nathanchance:
Installation on a custom ROM

For those who want to install ElementalX on a custom ROM with SuperSU installed as a system app (tested on Chroma, may work on others, gonna try Pure Nexus when it is released):

Systemless root:

1. Flash the stock boot.img for MMB29K from here (not necessary on Chroma, depends on the ROM).

2. Flash the UnSU zip from here.

3. Flash the SuperSU v2.61 from here.

4. Flash ElementalX 3.07.

5. Reboot.

6. ???

7. Profit.

System root:

1. Flash ElementalX 3.07.

2. Reboot.

3. ???

4. Profit.

End result: EX is installed, gestures work, SELinux is in Enforcing, camera works, root works.

[MENTION=4684315]flar2[/MENTION], followed the above process, worked like a charm. Quick question though, [MENTION=4577048]daihard[/MENTION] said that he flashed 3.07 with Chroma 12/07 which is based on 6.0.1 without doing systemless root, keeping SuperSU v2.52 and root worked fine. Is the installation process in your post only applicable for stock or is it necessary for custom ROMs as well? Thanks for the quick work!
[Nexus 6  Original Android Development] flar2:
My instructions are just for stock, I didn't know there were custom ROMs already.

For custom ROMs, just flash the kernel.
[Nexus 6  Original Android Development] nathanchance:
Sweet, modifying post. Good to know systemless root works though.
[Nexus 6  Original Android Development] daihard:
Thanks guys! I've already re-flashed Chroma with SuperSU 2.61 just to be safe, but it's great to know it's going to work either way. :)
[Nexus 6  Original Android Development] altimax98:
Got an odd issue after flashing. Immediately after flashing the kernel and SuperSU on 6.0.1 stock it bootlooped twice but got into the system, all was well. I went to reboot it and now it is deadlocked at the Google logo with the padlock.

Nothing I can do will get it past this screen or into the bootloader/recovery. A PC never recognizes it. I have a lot of rooting etc experience but never come across this, any thoughts?

Also, a reboot (Pwr+Vol-) just brings it right back to this same screen, even the bootloader menu never appears with that keypress
[Nexus 6  Original Android Development] -DarkKnight-:
If we already have systemless root which patches out boot image, will elementalX interfere?
[Nexus 6  Original Android Development] flar2:
No, just flash ElementalX. The order doesn't matter.
[Nexus 6  Original Android Development] Nikki1993:
Just compiled a PureNexus 6.0.1 build myself, and followed your method (I skipped the boot image part). System boots fine. It's currently upgrading. I will update the post to confirm if SuperSU actually works.
[Nexus 6  Original Android Development] Formhault:
There's got to be modem-carrier related issues at play then. I can't get past 5 hours, and I don't crank the display all the way up...

Perhaps the fact that no carriers in my country comercialize the phone, so no Romania-related optimizations were done, matters? I refuse to believe my battery is that fudged up, otherwise, barely being able to hold 70% of its initial charge...

---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------

I don't use dark layers. Stock theme, so... white everywhere, lol. Could that really be it...? :eek:
[Nexus 6  Original Android Development] Nikki1993:
Didn't work with systemless root method on purenexus. After upgrading phone either bootloops or constantly crashes systemui after unlocking. Note that I didn't flash stock boot image prior.
[Nexus 6  Original Android Development] siggey:
http://androidfact.com/amoled-screen-battery-drain-black-vs-white-homescreen/
[Nexus 6  Original Android Development] isaakmg:
Thanks for the new version...

But, the battery...

Whith stock kernel I haven't this problem in 6.01....

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] DarkSorcerer:
It works fine upgrading this way. Thanks!
[Nexus 6  Original Android Development] suku_patel_22:
Working fine on latest Cataclysm. I. Am running it without root.
[Nexus 6  Original Android Development] flar2:
You don't use systemless root on pre rooted custom ROMs

Reflash pure nexus, then flash elementalx. That's all there is to it.
[Nexus 6  Original Android Development] Nikki1993:
I was following the guide of nathan who tried it with chroma rom.

At the moment userdebug builds crash systemui anyway. When I dirty flash over 6.0 phone is just unusable, constantly restarts to. Lockscreen every 2 seconds. But that's off topic for purenexus thread.
[Nexus 6  Original Android Development] flar2:
No, just no. Why would I release a kernel that does that? Problem is on your end. If there is even a problem. Probably solved by rebooting. And totally not related to the kernel.

Please have a little more patience before bothering me with stuff like this.
[Nexus 6  Original Android Development] nathanchance:
I think you would need that boot.img so v2.61 plays nice with it since I don't know if Pure Nexus's kernel is updated to 6.0.1. Also, you would want to run the UnSU zip before anything else, not sure if you did that or now.

Idk I gave up on systemless root for the time being. Nice idea but it doesn't do anything for the Nexus 6 with Android Pay so v2.52 is fine for me.
[Nexus 6  Original Android Development] flar2:
Systemless works great on stock

For custom ROMs, it's just best to use whatever they use
[Nexus 6  Original Android Development] nathanchance:
I always forget that you run stock on all of your devices lol.
[Nexus 6  Original Android Development] altimax98:
[MENTION=4684315]flar2[/MENTION] Have you seen my issue before? Worked perfectly fine after the flash and then never booted again. http://xdaforums.com/nexus-6/help/bricked-nexus-6-typical-thread-t3266409

I figured I would link it instead of posting the whole issue again. I am at a total loss, never had this occur before, Nexus devices are almost always recoverable.
[Nexus 6  Original Android Development] flar2:
I saw that but I really don't know what happened or how to fix it, sorry. I can assure you it's not related to EX or SuperSU. Could be hardware
[Nexus 6  Original Android Development] altimax98:
I wasn't sure if you had ever gotten your device to this state in testing.
[Nexus 6  Original Android Development] flar2:
No, I've never been able to mess up a nexus. That's why I thought maybe hardware. Perhaps the volumes button is not working.
[Nexus 6  Original Android Development] altimax98:
I was thinking that too as I recently did the frame swap, but the buttons have never given me even the slightest issue so for them to fail at the same time the phone locks is an odd similarity. Plus the volume and power rockers run on the same cabling so if the cabling was the issue they both would fail.

The only other time I have ever had a phone brick was the Galaxy Nexus. One flat out died coming home from a trip (mobo failed) and the other was the Q_BULK mode on the same phone but I got it booting and it never gave me an issue again.
[Nexus 6  Original Android Development] kevdog98:
That worked but I do not have system access. I can not edit build.prop. Can you help me with that?
[Nexus 6  Original Android Development] Nikki1993:
I wanna keep my stock android system intact. What for Elementalx Kernel Manager need BusyBox for? Since I need to install BusyBox in the system partition (which I would rather avoid doing).
[Nexus 6  Original Android Development] ConTejas2:
[MENTION=4684315]flar2[/MENTION] or anyone else that'd like to chime in - I just switch back to a "stock" rom that uses "the latest hC with 6.0.1 ramdisk." Bit confused by the warning in your OP. Is the only issue with flashing this over other kernels one may have flashed after their rom...aka if your rom was built with a custom kernel I can just flash EX? Or do I need to flash stock kernel before? The rom I was using was built with EX so never had to wonder. Thanks!
[Nexus 6  Original Android Development] Danvdh:
you will be flashing EX over stock ramdisk, will be fine
[Nexus 6  Original Android Development] Formhault:
I know that... just didn't come across any good dark Layers themes... or had the time to feddle with them.
[Nexus 6  Original Android Development] ConTejas2:
It's your build I flashed, sir! Double thanks Dan:highfive:
[Nexus 6  Original Android Development] Danvdh:
I actually just updated the ROM to just include a stock kernel that gets systemless root installed automatically after the flashing process, now its 100% elementalX compatible!

just bought your app btw [MENTION=4684315]flar2[/MENTION]

good work
[Nexus 6  Original Android Development] simms22:
last version.. ok, ill give it a go. .06 was nice, well except for the reboot.
[Nexus 6  Original Android Development] J0ESK0:
s2w or d2w not working all the time

Has anyone else had the problem where the screen won't wake, no matter how many times you sweep or tap? I've had this issue every now and again even on the latest release. The power button will wake the phone instantly though so its definitely not frozen or anything like that. It's just really odd that this keeps happening and was wondering if I'm the only one.
[Nexus 6  Original Android Development] jtwlbz:
I just got my phone shut down. no reboot. running 0.07. stock rom decrypted.

Sorry no logcat...
[Nexus 6  Original Android Development] bikeryder007:
I will tell you my situation to see if it helps you. I ran version 6 the whole time it was out with zero issues. Then, I flashed version 7 last night.

I run stock kernel settings only changing color and dt2w. This morning my alarm did not go off, and my phone was powered all the way off.

Sorry, I did not get a log, as I had to get to work. If it happens again, I will try to get one for you.
[Nexus 6  Original Android Development] flar2:
Logcat won't help, I need this:

adb shell su -c cat /sys/fs/pstore/console-ramoops > kmsg.txt
[Nexus 6  Original Android Development] jtwlbz:
I got this..

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

tmp-mksh: cat: /sys/fs/pstore/console-ramoops: No such file or directory
[Nexus 6  Original Android Development] flar2:
Thanks for checking, was this attempted on the next boot after the shutdown? That file is only present if there was a kernel panic on the previous boot.
[Nexus 6  Original Android Development] jtwlbz:
I am sure I did this after shut down and power up myself. Maybe not kernel related. This was my first time shut down. I've never had shutdown or reboot with nexus6 or nexus 5 with your kernel. I will monitor more and report.
[Nexus 6  Original Android Development] chubby65:
Yeah I got that too

Them i installed this from play store

https://play.google.com/store/apps/details?id=com.bassel.andylog
[Nexus 6  Original Android Development] flar2:
If the file is not present after the crash, it must be some kind of hard lockup

0.07 is clearly unstable, 99.9% sure it's the elementalx governor. Wish I could get a log or have it happen on my phone so I could see what's going on. I think I'll remove the input boosting from the governor and see what happens, since it is very similar to the cpu-boost that caused problems with ondemand.
[Nexus 6  Original Android Development] laureanop:
I've had SODs with Lean, Sensei, and one with Elemental 0.7 last night. No oc,no uc no UV.

I think my sod's are related to no CPU boost combined with lowered screen off max (both 1.19 and 1.574). I don't get sod's with stock kernel.
[Nexus 6  Original Android Development] dsmitty166:
No issues here on elementalx gov at all
[Nexus 6  Original Android Development] chubby65:
I've got a log couldn't do it in adb shell only managed it through the app

Don't know if it's any good but here you are

https://www.dropbox.com/s/ppfm748t9euw0yq/log--(15-Dec-2014-16-53-36).txt?dl=0
[Nexus 6  Original Android Development] xxfwmxx:
Been running 0.07 with elementalx governor all day with no issues at all. Been really smooth
[Nexus 6  Original Android Development] wolfeyes30:
Same here.

Running great. Thank you
[Nexus 6  Original Android Development] Johnny424:
elementalx governor has been working fine on my phone all day.

I did discover between lean and ex that I had to increase my voltages by 5 across the board to oc to 2803ghz. weird thing is under normal use I never had a random reboot. between on demand, interactivex and elementalx governors. but the minute i try to run a benchmark with antutu it would reboot. increasing voltages fixed it. don't understand why it wouldn't reboot in day to day with all the things I do along with gaming.. strange
[Nexus 6  Original Android Development] flar2:
Been good for me too, but enough people have reported problems that I think there is an issue. Keep using it and see what happens. If you do get a reboot or shutdown, please try to get a log. It seems to be a hard lockup, which means it's hit or miss whether the kernel log is actually saved or not. And it seems to happen when the phone is idle.
[Nexus 6  Original Android Development] flar2:
That app is providing a logcat, which is is Android logging, and it's trying to find /proc/last_kmsg.

/proc/last_kmsg is the old location for last kernel messages, now with linux 3.10 there is a new way of saving the logs

The log I need for this problem is /sys/fs/pstore/console-ramoops
[Nexus 6  Original Android Development] paychex:
No instability here. Double tap to wake might be a little slow
[Nexus 6  Original Android Development] flar2:
Update

I removed elementalx governor, re-enabled cpu-boost and applied imoseyon's fix to ondemand. Stay with 0.7 if it's working for you. For others, let's try this version to make sure everything else is stable.

Download:

ElementalX-N6-0.08 (alpha)

Changes:

-remove elementalx gov

-re-enable cpu-boost

-disable cpu-boost while using ondemand
[Nexus 6  Original Android Development] WhammyDroid:
Why isn't the prior version of Super SU supported (v2.52)? I ask because I cannot remove apps from the system partition in order to install others like xposed.
[Nexus 6  Original Android Development] flar2:
Chainfire is not updating the older version any more and it's a hassle for me to patch sepolicy for every ROM version of every kernel I release. Systemless is the future.
[Nexus 6  Original Android Development] Danvdh:
I like it better this way

rooting is so easy, I just use the stock kernel in my release and the updater-script does the rest

I suggest all rom dev's implement root this way moving forward, let's give app developers no choice but to adapt to a systemless root, Setting SElinux permissive or patching sepolicy every update to use out dated 2.52 is not wise at all

#ROOT
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");

on the fly boot.img root patching :D allows for a simple flash of elementalx latest and all is gravy, sepolicy was a pain in the arse to be honest

I really like this kernel man, I had that split screen issue too but I caught it inside my 30days with Telus, I got my device swapped out luckily.
[Nexus 6  Original Android Development] Droidphilev:
Hmm, i'm *nearly* sure that i flashed 3.07 together with SuperSu 2.52 on a debloated 6.0.1 stock rom yesterday without any problems. I flashed a lot though because of some Multirom tests so i may be wrong.
[Nexus 6  Original Android Development] Danvdh:
SELinux was permissive then, not recommended anymore. the root method has evolved to something much cleaner and better
[Nexus 6  Original Android Development] magnamentis:
just change the permission of the directories that contain things you want to get rid of to "777"
[Nexus 6  Original Android Development] Formhault:
Does this mean that root in 6.0.1 isn't working...? :eek:
[Nexus 6  Original Android Development] jtwebfusion:
Kernels working great for me in systemless root mode on the stock rom(N6). Finally got Android pay working. Thanks!
[Nexus 6  Original Android Development] Brotuck:
When installing the kernel i get the option to set or unset permissive.

Is it correct that i cannot change this setting anymore after booting ? EX Kernel manager does not have this setting..
[Nexus 6  Original Android Development] flar2:
Everything works fine.

You can't change it after boot, only before. I may fix this someday, but I'm not a fan of permissive, there is no reason for it anymore.

I can't have the setting in my app, it got banned from the play store because of that.
[Nexus 6  Original Android Development] kashb91:
[MENTION=4684315]flar2[/MENTION] since busybox is necessary for the app to work, where should I install it to? Don't want to to install to system to lose Android pay
[Nexus 6  Original Android Development] flar2:
I have to look through the app and see exactly what requires busybox, as most of the common commands like echo and cat are available on stock. Something in there might use it, but you should be mostly fine without busybox.

You can install busybox in alternate locations, I posted instructions somewhere yesterday, or you can use Busybox Pro.
[Nexus 6  Original Android Development] kashb91:
OK cool. I'll try to find your post if I run into problems with the app then.
[Nexus 6  Original Android Development] magnamentis:
you can download busybox form playstore (stericson always works) and run it as user app, just keep in mind that you have to install latest version, it think it's 2.41 after installing the app. i tried on 6.0.1 with systemless root as well as with old root (2.52 + EX3.06) works with both approaches.
[Nexus 6  Original Android Development] suku_patel_22:
Does elemental governor skip so many cpu steps?
[Nexus 6  Original Android Development] organick87:
can the wake gestures app be used as a stand alone?

is it possible to use the wake gestures app found on elementalx.org alone with a different, non-elemental x kernel? reason being is i run Chroma and until the 6.0.1 release the dev baked in hellscore, but with 6.0.1 he switched to stock google (unsure if a third-party kernel will make its way back in yet) so i wanted to stick with hellscore since it's what i know and am used to, but hells doesn't include wake gestures so that's why i want this app stand-alone. thanks
[Nexus 6  Original Android Development] flar2:
It works with any kernel that implements wake gestures. I don't know exactly which kernels include them, but I'm pretty sure there are several options for this device.
[Nexus 6  Original Android Development] organick87:
within the Kernel Adiutor app (my personal kernel manager choice) there is a wake gestures section. so, if i utilize hellscore kernel or whatever else, do i go into this menu in KA and disable all wake gestures listed there THEN go into YOUR wake gestures app and enable gestures?
[Nexus 6  Original Android Development] flar2:
You just need the wake gestures app.
[Nexus 6  Original Android Development] spevil07:
Sounds nice, but at witch location have you installed busybox??

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6  Original Android Development] nathanchance:
I installed mine in /su/bin, works like a charm with systemless root.
[Nexus 6  Original Android Development] magnamentis:
you serious? LOL can happen, i know but you just have to read the post you quoted, it's clearly written: "run as user app" the term "user app" is used as opposed to system app.
[Nexus 6  Original Android Development] organick87:
I need KA to tweak other aspects of the kernel. So since I need to keep it is why I asked what to do with the gesture settings in there in order to play well with your app.
[Nexus 6  Original Android Development] flar2:
The wake gestures app should take care of all the settings. Just leave the gesture settings in KA alone.
[Nexus 6  Original Android Development] lords8n:
Can someone verify the correct procedure for systemless root with EX?

I'm flashing PureNexus 6.01 pre-rooted: Clean wipe, Flash ROM, flash GAPPS, flash Su2.61, flash EX?

Thanks.
[Nexus 6  Original Android Development] nathanchance:
Flash ROM, GApps, UnSU (to get rid of SuperSU 2.52), SuperSU 2.61, ElementalX 3.07.
[Nexus 6  Original Android Development] lords8n:
Thanks.

So clean wipe not necessary? Coming from PN 6.0.
[Nexus 6  Original Android Development] nathanchance:
I don't think so, it is a rebase but not a complete rebase like from 5.1.1 to 6.0. I dirty flashed Chroma 6.0 to 6.0.1 without issues.
[Nexus 6  Original Android Development] Khizar:
Tbh these days I only recomend clean flashing when someone has issues, other than that I say make a backup and try a dirty. I know ppl who've been dirty flashing since LP and have had no issues, on the same rom of course. It all depends on how you have your device setup(whether it's heavily modded with xposed and stuff) and how it reacts.

However that being said I personally prefer starting from scratch on every new android update, old habits die hard. I prefer fastbooting stock and then flashing recovery, rom, etc.. Just depends on how you like your phone and how your phone likes to be upgraded. LOL some devices are picky about such things.
[Nexus 6  Original Android Development] Phrodini:
You're using multirom?
[Nexus 6  Original Android Development] Droidphilev:
I think he means where to install the busybox files, not the busybox app. I think i will also need to buy the Busybox pro version as i cant install to other locations out of /system
[Nexus 6  Original Android Development] magnamentis:
i recommend to possible ways to avoid issues flashing further zips after superSU 2.61, both are feasible:

a) after flashing superSU 2.61 reboot into recovery and continue flashing the remaining zips thereafter

b) flash superSU 2.61 as the very last zip

anything else except step 1 ( logically LOL ) does not really matter in which order.

---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------

ah... ok, yes i recommend pro version, using pro version for years, for such critical tools it's always worth it to not safe money in the wrong place LOL
[Nexus 6  Original Android Development] nathanchance:
SuperSU needs to patch the stock kernel, not a custom one so step B may cause issues. SuperSU then EX will cause no issues since SuperSU will patch the stock kernel and then EX will make its ramdisk changes to it so step A should be fine. I've done that at least 10 times amongst all of my tests with ROMs the past few days and never once ran into an issue.