Database Develop

[Info] Rooted user? Learn to update properly

*The below post covers up to 4.4.4 only. for 5.0, read this thread: http://forum.xda-developers.com/goo...asic-overview-root-options-lollipop-t2947144*
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
OTA's are simple for unrooted, noob users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.
OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended
Please note, rooted users will still receive the OTA notification. You do not need to apply it though. Some Custom ROMS even receive it.
Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.
In short, it's just not the best option, Why would anyone ever choose "not the best"?
It all depends what you want to keep going forward.
I don't want root or custom recovery
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located
I want to keep root
You have a couple options here.
You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.
Alternatively, you can flash a pre-rooted zip*. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.
With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
*Please note with Android 5.0 Lollipop, you need to flash a ROM.zip, Permissive kernel and SuperSU all at once. You have to download all 3 files and flash them one after the other in that order. You can flash some custom kernels, such as elementalx straight over permissive kernel. Also, you can ONLY flash elementalX as it allows root to run at boot (without permissive kernel) however, some apps NEED permissive to run anyway
OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.
If you still want to (return to stock in order to) accept OTA updates, even after reading this thread (perhaps because doing things properly mean more work for you) then perhaps you shouldn't be rooted. Having, maintaining and understanding root takes effort and if you're not willing to put the time in, you will become a danger to your phone and possibly a drain on this forum too We write lots of guides and info threads for your benefit. If you have questions, please just ask.
adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)
All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )
OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)

Always informative Mr. RootSU

stankyou said:
Always informative Mr. RootSU
Click to expand...
Click to collapse
Thanks. I try

Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!
I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?
Thanks
...sent from the Nexus 5000

I still remember rocking your dGB ROM during the Desire days. LOL

but my rooted and modified nexus 5 did receive an ota.. can i or should i apply it? or my rooted and unmodified nexus 5 did receive an ota.. can you decribe to me what would happen if i do apply it?

Thanks for this, really informative.

simms22 said:
but my rooted and modified nexus 5 did receive an ota.. can i or should i apply it? or my rooted and unmodified nexus 5 did receive an ota.. can you decribe to me what would happen if i do apply it?
Click to expand...
Click to collapse
Ooh good point. I'll mention that.

androidsnax said:
Thanks for this - I am rooted and have a basic knowledge of fastboot from unlocking and rooting the N5 last year and the N4 before that.. however, as I've not touched it for about that long it's probably about time I start the reading process again to get ready for some Lollipop action!
I had been planning on getting the factory images from Google and using fastboot to fresh flash it - looks like that's not really necessary tho?
Thanks
...sent from the Nexus 5000
Click to expand...
Click to collapse
If you want to keep root, The best thing to do would be to wait for a pre-rooted rom.zip - which should also contain the custom boot.img needed to give root permissions...
Just make sure you do all your backups first if you want to keep stuff.

Oh and if anyone has any suggestions for things I should include in the OP, please let me know.

rootSU said:
I see a lot of threads asking about updating to Lollipop and about returning to stock to receive OTA updates.. from rooted users.
I have created this thread as I have strong feelings about rooted users and OTA's in general, so I wanted to collect my thoughts together in a single thread to hopefully persuade rooted users to avoid OTA updates. Of course, you're free to choose to ignore this.
OTA background
OTA's are simple for unrooted, noob users. They are minimal effort, quick and require no knowledge. However they have a propensity to go wrong - often resulting in a user having to factory reset to get things working.
OTA's are designed to be small to save on data usage. This is achieved by not supplying the entire ROM, kernel or app, but instead, including patches. These patch files (*.p) will unpack the recovery.img, bootloader.img, boot.img or *.apk and insert the new code into it. This means the OTA expects an exact version to install. You cannot skip an OTA and expect to apply a later one because the code in the patch might not "fit". Also, this is why modified users cannot apply an OTA. There are ways for rooted, stock kernel, no modification users to apply OTA updates but it is not recommended
Why shouldn't rooted users apply OTA's if they can?
Well if you are modified, you have to first return completely to stock to apply an OTA. This is a relatively long process compared to other options available to you. If you are simply rooted with stock kernel and no modifications, you can simply re-apply root after accepting the OTA, but it's a bit messy and still - it's an OTA that can go wrong. I think part of OTA's appeal is you can do it anywhere - but this is also it's biggest problem. rooted users need resources to be available to them so they can remedy whatever needs remedying after application.
In short, it's just not the best option, Why would anyone ever choose "not the best"?
So what are the actual options?
It all depends what you want to keep going forward.
I don't want root or custom recovery
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located
I want to keep root
You have a couple options here.
You could like above, fastboot flash individually the system.img and boot.img (not recovery.img) then reflash supersu from your custom recovery. Please note, with lollipop as of now, you need as special modified boot.img, not the stock one - so this still is not the quickest method.
Alternatively, you can flash a pre-rooted zip. Within a couple of hours of the factory image becoming available, guys from XDA will release pre-rooted zips that you simply flash from a custom recovery. This will be a quick process. Put the zip on your /sdcard, boot into recovery and flash it.
With both these options, you very well may need to factory reset after flashing roms, especially if it's a version jump - just as you may need to do with an OTA update. The benefit of being rooted however, is that you can use titanium backup to backup your apps and take a Nandroid backup too, rooted users upgrading should keep these available on the sdcard before updating.
Conclusion
OTA is designed for noobs. Granted, those root users asking how to return to stock or thinking OTA is the only update method available - are also noobs... If you're going to be rooted, you should understand what you have and what it means to be rooted. Familiarise yourselves with fastboot. Familiarise yourself with your recovery. Learn how to take backups and you will get much more out of your phone that constantly wasting time returning to stock, applying OTA's then re-rooting. You're wasting time doing this - it's a fools errand. I hope this thread helps to open your eyes and your minds.
useful links
adb and fastboot. What is it? How can it help you? - basic information about adb and fastboot (by @rootSU)
All you need to know about Android | Read this before you post/root ! - Understand the basics before you root (by @abaaaabbbb63 )
How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5 - Understand how to undo whatever you do before you root (by @abaaaabbbb63 )
OTA Help-Desk - Understand how OTA's work and what this means if you are rooted (by @Sandman-007)
Click to expand...
Click to collapse
Seems like we've gone with what I previously said about people who want OTAs while rooted
You should also add that if one STILL wants to take OTAs for some silly reason, even after reading this thread, he/she should stay away from root access completely and use their phone like any other unknowledgable/ignorant person would, like someone that OTAs were meant for. :angel:

Lethargy said:
Seems like we've gone with what I previously said about people who want OTAs while rooted
You should also add that if one STILL wants to take OTAs for some silly reason, even after reading this thread, he/she should stay away from root access completely and use their phone like any other unknowledgable/ignorant person would, like someone that OTAs were meant for. :angel:
Click to expand...
Click to collapse
Yep

Well said, sir. Nice work.

stankyou said:
I still remember rocking your dGB ROM during the Desire days. LOL
Click to expand...
Click to collapse
Ha. Oh wow.

Thank you so much.

Nice information thx

rootSU said:
Oh and if anyone has any suggestions for things I should include in the OP, please let me know.
Click to expand...
Click to collapse
Probably goes without saying but a link to a pre-rooted ROM where you mention this option would be great. When available of course.
Only because finding a stock pre-rooted ROM at times like these can be a task even for vets. Having it right there would be very useful for those peaking in on this already informative thread.
Thanks

tgrgrd00 said:
Probably goes without saying but a link to a pre-rooted ROM where you mention this option would be great. When available of course.
Only because finding a stock pre-rooted ROM at times like these can be a task even for vets. Having it right there would be very useful for those peaking in on this already informative thread.
Thanks
Click to expand...
Click to collapse
na, very easy. basic aosp/stock rooted roms(these are what you want) will be in the android development section of the nexus 5. always. in the original development section, there will be original roms only.

rootSU said:
If you no longer want root, simply return to stock using google's factory images. The factory image package contains all the files needed to return to stock:
- boot.img
- recovery.img
- bootloader.img
- system.img
- cache.img
- userdata.img
- radio.img
It also includes a windows batch file (.bat) and a Linux shell script (.sh) that will automate the above. This will wipe your data.
If you don't want to lose your sdcard data, if you have a custom recovery, you can factory reset, fastboot flash individually the recovery.img, system.img and boot.img as this will keep /data partition in tact, which is where your /sdcard is located @Sandman-007)
Click to expand...
Click to collapse
Also, you can edit flash-all.bat and find entry:
Code:
nulfastboot -w update image-hammerhead-ktu84p.zip
and remove "-w" and save it. Then just execute flash-all.bat and the script will flash all the images without wiping data. I always do that way and never had data wiped.

Nice advices once again and I totally agree with OTA subject.
I used Lollipop a few days then I went back to KK and I do not plan to update soon. Since I didn't follow recent discussions about Lollipop I have a question: flashing a rooted flashable zip won't be a mess? e.g unavailable /sdcard, a 32Gb storage that becomes 16Gb (actually that's what I had - clean flash of course)... Lollipop is really different compared to KK so would it not be more appropriate to flash the factory imgs (without restoring user data from KK) before enjoying Lollipop's stuff?

[ROM] Stock US Unlocked/Developer Sense 7 Marshmallow AIO Thread (wp_mod) (s2s_mod)

The official Sense 7 for MM is out!!
For those who haven't or cannot receive the OTA and you cannot wait, here is it!
In this post you can find the followings:
Firmware
Aroma Stock Rom
Root Info (System/Systemless)
Disable S-ON System Write Protection
Sweep to sleep module
FAQ
Firmware
Here is the full firmware pack before flashing the rom. You can choose stock or the one with no red text.
Unzip the firmware zip, and change mid and cid in android-info.txt to your own one.
This firmware will not wipe data!! Flash without any fears
S-OFF Only!! S-ON users can try flashing this rom with older firmwares.
Stock: DevDB Download
No red text: DevDB Download
Aroma Stock Rom (With selectable root ,wp_mod, s2s_mod)
The installer will install everything for you.
If you want root, take a look at the next section for some info about root methods.
I haven't got much time, so I'm using block flashing for convenience. Will update to file based flashing if I had time, but users wouldn't feel any difference.
DevDB Link​
Important!! If you choose systemless root, please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in boot loop.
Root Info
Marshmallow root has been much more difficult than simply flash a zip in recovery, because it also requires a modified boot image to work. This root is achieved with SELinux enforced using Chainfire's method.
Chainfire gave us with two rooting methods include:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
If you are already on the stock rom and you want root, this is where you'd be interested with.
Choose your preferred root method above, and follow the correspond instructions below.
Instructions:
Traditional:
Flash m8-mm-su-boot.zip in attachment with TWRP
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the traditional one above), if you've rooted with other methods, please re-flash your system back to pure stock
Flash m8-mm-su-boot-systemless.zip in attachment with TWRP
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in bootloop.
Disable S-ON System Write Protection
After you rooted, you might find out that your system partition is locked up, this is because of HTC's system write protection on S-ON devices, and here is a handy mod for you to bypass it. Original mod by flar2, I modified it to work on MM.
Instructions:
You have to use the traditional root method above to make this work!!
Flash m8-mm-wp_mod.zip in attachment
Sweep to Sleep module
A handy mod to turn of the screen by swiping the bottom of the screen. Original mod by flar2, I modified it to work on MM.
Instructions:
This will flash files to system, there is no point in using systemless method, but it should be OK
Flash m8-mm-s2s_mod.zip in attachment
FAQ
Q: After choosing full wipe, my contents in internal storage are all gone!!
A: No, it's not. It seems that Marshmallow treats my full wipe script differently. After each clean flash, it will move all previous files in /sdcard into /sdcard/0. You can just move them back to the proper locations. No big deal!
Q: I cannot install Busybox in system / I cannot use adaway !!
A: Flash wp_mod.
Q: I used systemless root and wanted to keep my system partition intact, how do I install Busybox?
A: Download Busybox Pro, type /su/bin as the installation path for busybox. You cannot do it using the free version, unfortunately.
Q: **** app cannot access external SDcard!!
A: Look at this explanation:
Since Kitkat (2 years ago man), we don't have direct external storage write permission. Google consider it insecure, so they implemented this feature. The reason why you can access external SDcard easily before is because most roms on XDA already contains a hack in /system/etc/permissions/platform.xml. You should not rely on this hack forever, please take a look below.
In lollipop and after, Google provided a much secure and better way to grant external storage access to third party apps, first of all take a look at this article for details:
http://www.androidpolice.com/2014/1...s-automatic-mediastore-and-improves-security/
So instead of using the old platform.xml hack in the old Kitkat days, adopt yourself with this new behavior of Android!! If a certain app cannot access SDcard, ASK THE DEVELOPER to add support for this API!!
Many apps already have support for this API. I'll take Titanium Backup for example, as lots of you cannot find the way to use it on externals SD. In Menu>>Preferences>>Backup Location, you can choose Document Provider on top of the detect button.
In the provider, open the menu on the top right corner and select "Show SDcard", then you'll see External Storage in the left side. Select external SDcard in the document provider and press the button on the bottom, the app will then be granted access to the whole external storage. You can then create a new folder in TiBack and select it as your backup location.
Other apps also follows the instructions above, you just have to manually set up the folder where the app can access, in the case which most of us would love to give access to the whole SDcard, I set the location to the root of external storage. Each app has independent permission, so you have to manually grant each app you wish to access external storage.
Q: I want OTA, what should I do?
A: Look at the following info
To accept OTA updates, you need the following:
Your MID should be 0P6B11000 or 0P6B12000
Your CID should be BS_US001 or BS_US002
You have to keep system partition untouched
You have to have stock recovery
So before anything, if you want to accept OTA, you have to change MID, CID, flash the stock firmware. The tricky part is the system partition and the recovery. The easiest way is when the OTA comes, flash the stock rom again without root, flash stock recovery through fastboot, then apply OTA. But if you like to go the hardcore way, here comes a tutorial:
fastboot flash systemless_boot.img
fastboot boot TWRP.img(so that you can use TWRP but you didn't actually flash it)
Flash systemless SuperSU
By doing so you can accept OTA at anytime.
Credits:
@Chainfire for the new root methods and SuperSU
@flar2 for wp_mod.ko and s2s_mod.ko
XDA:DevDB Information
Stock Sense 7 Marshmallow , ROM for the HTC One (M8)
Contributors
topjohnwu
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Stable
Created 2015-12-03
Last Updated 2015-12-03

Will this work on a CDMA device?

@topjohnwu nicework dude....

skinbis said:
Will this work on a CDMA device?
Click to expand...
Click to collapse
I'll take a look.

Sticky
Sent from my HTC6525LVW using Tapatalk

tell me the no red text will work on s-on?
i think both of this frimware not work on s-on

The suspension is almost as big as when MM first came out

Good work!
Where is the downloading link to the rom?
Edit:The rom is uploading....Sorry.

b-george said:
Good work!
Where is the downloading link to the rom?
Edit:The rom is uploading....Sorry.
Click to expand...
Click to collapse
Still uploading shouldn't take much longer about another half an hour or so.

topjohnwu said:
I'll take a look.
Click to expand...
Click to collapse
Thanks

Is it possible to flash on S-ON device?

It seems that the systemless boot isn't working as expected lol
Fixing
Edit: Fixed, everything is now uploading

Hi. Can i flash on 6 sense firmware ?
Wysłane z mojego HTC One M8 przy użyciu Tapatalka

Can u upload some pics ?

topjohnwu said:
It seems that the systemless boot isn't working as expected lol
Fixing
Edit: Fixed, everything is now uploading
Click to expand...
Click to collapse
Prepping my device in the meantime, thanks!
Any ETA on the upload?

topjohnwu said:
It seems that the systemless boot isn't working as expected lol
Fixing
Edit: Fixed, everything is now uploading
Click to expand...
Click to collapse
does the firmware provided here will wipe internal SD?

JEANRIVERA said:
does the firmware provided here will wipe internal SD?
Click to expand...
Click to collapse
Firmware updates never wipe that.

Zulake said:
Firmware updates never wipe that.
Click to expand...
Click to collapse
you are so wrong!!! there are firmware that does wipe internal SD that is the reason why asked

JEANRIVERA said:
you are so wrong!!! there are firmware that does wipe internal SD that is the reason why asked
Click to expand...
Click to collapse
Well I have never ever seen those, and I've been flashing ROM's since the HTC Desire HD.

Zulake said:
Well I have never ever seen those, and I've been flashing ROM's since the HTC Desire HD.
Click to expand...
Click to collapse
whats the procedure to flash a firmware please?

XT1068 overwhelmed, just want root

So browsing through all the development threads I can't seem to find a basic root tutorial. I just want to root the stock rom so I can use greenify to improve the wife's batt life. I understand I'll need to unlock the bootloader. The phone is now a year old so no warranty left anyway. Any help would be appreciated.
EDIT: Sorry it's a XT1063, not 1068.
Sent from my KFFOWI using Tapatalk

Unlock the bootloader using this guide http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728 : Warning - unlock will factory reset your device.
Flash the recovery http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
(in fastboot mode from first tutorial, use command
Code:
fastboot flash recovery xxxx.img
)
Then copy the supersu zip to your device, boot into recovery and install it. https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip

Thank you sir. That's disappointing you have to wipe to unlock boot loader. In that case I might as well flash a ROM. I know asking about "the best" rom is frowned upon but what's a good stable daily driver that I can flash once and forget about it, since it's not my phone.
Side question, rooting then upgrading to official marshmallow will kill root I assume?

1. Personally I use temasek's CM13 - while updates are not as frequent, the feature set is pretty nice. And it is quite stable. http://forum.xda-developers.com/moto-g-2014/development/rom-temasek-s-unofficial-cm13-t3264678/
2. I don't think you will be able to upgrade to Marshmallow with a modified device using the standard OTA method. This works, though http://forum.xda-developers.com/moto-g-2014/general/6-0-soak-moto-g-2014-t3255883
PS : For Marshmallow, if you are using a stock ROM, root is to be done with SuperSU's 2.6x zip file, don't use the older versions.
Most custom ROM's are CM based, and therefore, have root inbuilt. So you don't need to do anything more about that if you flash a custom ROM.
PPS : Next time quote or mention me, so I get a notification. Thanks.

How to install ElementalX Kernel

I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.

The kernel is the boot.img. Just flash it via TWRP and it will automatically be present.

And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Better flash superSU2.65.zip (latest atm).

Not necessarily better. Versions after 2.62 have a number of comments across various threads saying that root doesn't work for them. 2.62 uses a different method from the later versions. 2.62 works fine for me and (from the silence in the forums) for most people, so upgrading to 2.64/2.65 is probably taking an unnecessary risk.
And again, why try to install a different kernel on a working rooted device? It makes no sense to me unless there's an amazing function that will make a discernable difference, and personally I don't believe that any kernel makes that much of a difference in real-life normal usage.

dahawthorne said:
personally I don't believe that any kernel makes that much of a difference in real-life normal usage.
Click to expand...
Click to collapse
Not something i'd agree with since CPU governors and I/O schedulers can make allot of difference to "real life normal usage", obviously this depends on what the developer impliments and user choice.

there are times that I'll run elementalx kernel, but I ALWAYS change the governor and scheduler. always. as I can't stand the way that its set up. personally, I always use ondemand with deadline :angel:

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Wondering how you achieved root.I am unable using the stock kernel.TWRP installed just fine.Do you mind sharing your procedure?

Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.

To install elementalx, just flash in recovery.
dahawthorne said:
And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...
Click to expand...
Click to collapse
Silliness. Why are you even on xda with that attitude? He probably wants to install it so he can use some of the added features and enhancements.

"Why are you even on xda with that attitude?" Ditto. We're all entitled to our opinions, and my opinion is that a lot of noobs do stuff just to see what happens, and the result is that they're in forums asking after the event "How do I fix this?" rather than "How do I do this?", and in both cases without any particular need or reason or understanding of what they want. And this is a typical thread - an admitted noob wants to install a specific kernel, and still hasn't said why (though he/she has thanked me, which I appreciate ). I think that to warn noobs about unnecessary tinkering is doing them a service - isn't that why we all respond to questions?

dahawthorne said:
Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.
Click to expand...
Click to collapse
Thanks very much -so to be clear that was with the Stock kernel?
I am running 3.10.40-g557ba38
Trying to avoid a brick situation,sorry to be a bother..

Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.

Awesome thanks again.

dahawthorne said:
Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.
Click to expand...
Click to collapse
Thanks again-this worked out perfectly and I am running Cyanide which has made me very happy so far.REALLY fast and smooth.Everything working great so far.Loving my N6- who needs Samsung! I just had to edit the .xml file for the Music volume other than that the ROM seems about perfect.

[Help] Explain systemless Root

Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.

TokedUp said:
Hello. Please be gentle. I'm new to Systemless Root and need some clarification. I've done a lot of reading about it but still need some info. Im not bashing anything or anyone, I'm not trying to be a wise ass, I'm genuinely confused. From the vague installation process I read somewhere it seems that u already need to be Rooted with TWRP installed to install Systemless Root. Right? So what's the point of rerooting a phone thats already rooted? I would think it would be more useful to have it as another root method. So we can start off Locked and Unrooted, then use Systemless to root. Currently my N6 is locked and Unrooted because I have no use for Root at the moment yet all of my previous Android phones have been unlocked and rooted. Please explain to me what I'm missing here. Thanks guys. Happy New Year to u.
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 and this http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 for starters. BTW Google is your friend and you can`t be rooted to use systemless root and obtain root.

I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...

dahawthorne said:
I'm probably a lot less experienced than gee2012 and many others in the forum, but here's my very high-level understanding. I hope that the more knowledgeable members can add to or correct this as necessary.
First, you need to unlock the device (fastboot oem unlock), since you can't do much with a locked device. Not only that, but time and time again I've read pleas from users saying "My device is bricked and I didn't unlock it so I can't now enable developer options" - the responses have been generally "Sorry, you're stuffed then, send it back". Unlocking wipes the device, so make backups of whatever essential data you have.
You don't need to install TWRP permanently in order to root. I myself (after asking members for advice) temporarily booted into TWRP (fastboot boot twrp.img - when you reboot from TWRP it disappears and you're back to stock recovery). While TWRP is temporarily running, you can use it to install SuperSU.
The benefit of the new SuperSU (and also doitright's systemless root method) is that it maintains a stock system image, so in theory you have the benefits of superuser root but you can still get OTA updates, which are now much more frequent because of the security amendments. Chainfire (the SuperSU creator) says that he was able to install an OTA after having used the SuperSU unroot function, though he then had to re-root.
Hope this helps - and that it's correct...
Click to expand...
Click to collapse
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K

TokedUp said:
Thanks man. That makes certain things more understandable. The thing I still don't understand is the actual install process. I'm am stock, so ur saying I would just have to unlock BL then temp flash TWRP to flash the SU zip? If not what are the exact steps for installing?
BTW I'm on 6.0.1 MMB29K
Click to expand...
Click to collapse
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.

gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os

holeindalip said:
I don't want to be that guy but USB debugging is not needed to unlock the BL,it is only needed while in Android os
Click to expand...
Click to collapse
True, but i always enable it by default

gee2012 said:
- Enable OEM UNLOCK in developer options and enable usb debugging
- Unlock the bootloader
- Reboot
- Flash TWRP (2.8.7.1 is the lastest afaik)
- Message by TWRP to modify the system, click no
- optional: If you format data you decrypt the phone (will wipe all files completely), reboot after if you choose to do so
- In TWRP flash the latest systemless superSU.zip (2.66) zip, link http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
- TWRP will say you`re not rooted, ignore it
- Reboot
- Install BusyBox from Play and you`re done.
Click to expand...
Click to collapse
Thank you so much!

TokedUp said:
Thank you so much!
Click to expand...
Click to collapse
Tip: instead of flashing TWRP you can also boot it up ( fastboot boot nametwrp.img) to flash zip files and keep your stock recovery if you want to.

@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.

Busybox is the space efficient way of the basic Unix commands like ln, pwd, chown, chmod, etc. So all apps that want to do some low level file system dabbling, like Android terminal, Titanium backup, or Linux installs, they need it. https://en.wikipedia.org/wiki/BusyBox
From Marshmallow, Android now uses toybox instead by default, which is quite the same, with a little different licensing. It's also in the AOSP source, so all user built AOSP roms already have toybox, so there's no need for busybox to install.

dahawthorne said:
@gee2012 - "Install BusyBox from Play and you`re done"
I still don't get what exactly Busybox offers. I've been running fine on Marshmallow for several months without it. I installed it once because it was suggested as a fix for the constant nagging of AutomateIt Pro to reboot, and it made no difference, so I uninstalled it again.
Can you (or anyone) give me specific examples if where it actually makes a difference? Which functions won't work without it? I haven't come across any yet as far as I know.
Click to expand...
Click to collapse
Apps like Rom Toolbox Pro, Franco Kernel Updater and Kernel Adiutor and lots of other application like Xposed framework (and its modules) and most (if not all) of the custom roms will not work (correctly) without BusyBox. All custom roms anyway have a BusyBox version by default installed Busybox https://en.wikipedia.org/wiki/BusyBox and https://www.google.nl/url?sa=t&rct=...6Z0ltw&usg=AFQjCNG-nKYoEI3kiDm4pgtRWbXFRTpI6A for instance.
Its an essential app for when you are rooted and want to do more with your phone and its not smart to not install it

Thanks, both. I like istperson's comment best : "there's no need for busybox to install." That would be why I haven't seen any negative impact from not having Busybox then. Still, money well spent to help development...