Related
Hey guys! So I read around about rooting Android 6.0.1 and I only see systemless root. I am rooted right now using systemless root and it works fine, but my question is, is there a way to root 6.0.1 with traditional system root? Or is systemless the only way? Just curious really. Will systemless most likely be the future of rooting and the way it's going to have to be done from now on to keep Android Pay working?
Sent from my Nexus 6
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
Thanks for the response! And I wonder if it will be what it is for now! It's the only way to keep Android Pay working while the device is rooted correct? Android Pay refuses to work with a traditionally rooted device?
Sent from my Nexus 6
StykerB said:
I don't know of anyone who's made the kernel mods required for traditional root. I'd say that systemless root is probably going to be the only way to root from now on at least on nexus devices. Chainfire outlines things that don't work with systemless root on the supersu forums.
Click to expand...
Click to collapse
I did. I still use SU2.52. But only until this weekend. I'm switching to systemless too.
Actually building a permissive kernel is really straightforward, needs one line of code added. The build is about five minuters then with abootimg you can just replace the existing with the newly buil kernel in the boot.img, and flash it.
I can give you details if you're interested.
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
Mine works perfectly.
kamkar said:
Hi
I have a serious problem with ES File Explorer. This app (and maybe other Apps) says device isn't root, since I cant use ES in root explorer mode.
I heard Titanium Backup has the same issue with this future root!
now I back to 6.0 and waiting for a solution.
Click to expand...
Click to collapse
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Krzysiek_CK said:
Mine works perfectly.
Click to expand...
Click to collapse
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
H4X0R46 said:
The first systemless root did that, go back to that thread and get the newest version and flash that, fixed that issue.
Sent from my Nexus 6
Click to expand...
Click to collapse
I tested 2.61, is problem fixed in 2.62.3? because I must flash 6.0.1 and setup phone again!
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
simms22 said:
i rooted the old fashioned way, there's no difference except you also have to flash a custom kernel when flashing supersu.
Click to expand...
Click to collapse
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
H4X0R46 said:
Same way it was with 6.0 right? And Android Pay doesn't work with traditional root? Does it break anything else besides Android Pay?
Sent from my Nexus 6
Click to expand...
Click to collapse
ive no use for pay, so never tried. i assume its broken..
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
carmatana said:
Sorry,
I have a Nexus 6 with 6.0.
I am trying to find how to update to 6.0.1 with no-enforced-encryption and then do a systemless rooting but I cannot find the instructions to do this
Seems that just flashing stock, TWRP and the flashing supersu 2.61 from there is enough to have systemless root, right?
but what about no-force-encrypt?
Probably I am changing the discussion but have not found a good thread, apologies.
Thanks in advance.
Click to expand...
Click to collapse
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
H4X0R46 said:
What you probably wanna do is go for a custom kernel that doesn't force encryption. Most if not all don't force it! Elementalx is a good one, maybe elite kernel, and so many others! I use ElementalX on mine, my favorite kernel. www.elementalx.org if you wanna try that one! Others are found here on XDA!
EDIT: Looks like elementalx says to use SuperSU 2.61 or later, which is systemless, I would try another. Maybe elite or another one.
Click to expand...
Click to collapse
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
I would say yes, I'm 90% sure but could be wrong. I would flash the a new update with fastboot.
carmatana said:
Thanks !!! I will check them, I always have tried to be as close to stock as possible but I think it is time to try something new.
One question: Do Custom Kernels interfere with OTA updates?, this is one of the advertised advantages of systemless rooting and is one of my favorites.
Thanks again
Click to expand...
Click to collapse
Any mod stops ota's. Root, kernels....You will have to flash full images to get updates. You can skip the userdata part and save your apps and data. But you will have to flash.
Not a big deal, it an extra couple of commands just like the kernel you want to flash.
Thanks!
kamkar said:
How? I pass this steps to install and root 6.0.1:
First of all, I have a clean install of 6.0.1
then flash TWRP
In TWRP, install SuperSU 2.61 that flash a custom boot.img automatically. after dalvik/cash wipe, reboot to OS
After that, reboot to recovery again and flash a custom kernel
but supersu doesn't work and ES file explorer says device doesn't have root permission.
however, I need read/write permission in /system folder to delete some useless apks
Click to expand...
Click to collapse
Clean 6.0.1 followed by systemless root installation as expained in the Root done right thread.
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
I haven't seen a thead posted about this so I figured I'd get some input from people that have used both or either of the 2 root options.
What do you prefer and why? What are the pros and cons?
I know SuperSU is very well known and I'm familiar with it from the Galaxy S phones. Magisk is fairly new, but from what I heard it works well with Nougat and the other nice thing is that magisk can be toggled.
I'm not sure if there is any benefit to that or not, but I'd like to hear some feedback.
I'm interested to know more about this as well, but this is what I read about it.
Yes, Magisk can be toggled, so you can use Android Pay when you need it and then get back to being rooted.
However, for some reason, my AdAway adblocker just wouldn't work with Magisk+phhSU. No idea why. Everything else root worked well. When I had to clean flash the official Nougat, I decided to stick to good'ol SuperSU. I don't need the toggle function and everything worked great since.
So I've used both and can say this. Magisk works on both SuperSU and phhSU, although the later offers a different functionality. The toggle feature is an older feature of Magisk as they now have a hide feature baked in. This is the same as SUHide for SuperSU. I have yet to get SUHide working on the 3t, but I have it working on a few other phones. SuperSU+SUHide is great if you only want to run Root on your phone and hide systemless root from applications without having to really toggle Root. From my experience (YMMV), toggling root breaks things more than hiding. The only reason I have found to run Magisk is if you want to run Xposed as well. Xposed works with SuperSU, but Magisk does a pretty good job of UI integration with some of the pieces.
DarqAnshin said:
So I've used both and can say this. Magisk works on both SuperSU and phhSU, although the later offers a different functionality. The toggle feature is an older feature of Magisk as they now have a hide feature baked in. This is the same as SUHide for SuperSU. I have yet to get SUHide working on the 3t, but I have it working on a few other phones. SuperSU+SUHide is great if you only want to run Root on your phone and hide systemless root from applications without having to really toggle Root. From my experience (YMMV), toggling root breaks things more than hiding. The only reason I have found to run Magisk is if you want to run Xposed as well. Xposed works with SuperSU, but Magisk does a pretty good job of UI integration with some of the pieces.
Click to expand...
Click to collapse
Awesome, thanks for the input! That's definitely helpful. So you would recommend going with magisk? Would you say magisk works equally as well on all versions of OOS? 3.5.* and the new 4.*+ (nougat) version?
m0d hipp¥ said:
Awesome, thanks for the input! That's definitely helpful. So you would recommend going with magisk? Would you say magisk works equally as well on all versions of OOS? 3.5.* and the new 4.*+ (nougat) version?
Click to expand...
Click to collapse
Keep in mind, your mileage may very and these are only my opinions. With that said I will say this:
I've only had my OnePlus 3t for about 3 weeks, so I only really used it on the latest version of OOS 3.5. It seems to work fine on 4.*, however, it did take me a few extra steps and sideload.
I honestly would go with SuperSU / SUhide if I could get it to work on 3T correctly like it does on my other devices. Right now I have this weird forever and a day boot time with SUHide.
Magisk works almost as well in my experience and on the devices I do run xposed on runs even better in my opinion. The new Magisk doesn't turn root off but does mask root from certain apps such as android pay. The interface, in my opinion, has gotten better over the iterations. Magisk also does allow you to flash from the direct input, which depending on your skill can help out greatly.
I would say this. If you require
Xposed
UI
live updates of actual software similar to TWRP's new loader
ability to flash from app
Use Magisk
If you like simplicity and raw power go with SuperSU. I did try the SUHide Gui but found Magisk's version much easier and reliable.
Thanks again! That's super helpful!
Guys, Im running Tugapower and I cannot root the rom. Any of you know how to fix it? I run the zip file to root and I start to phone and looks that works but after couple of minuts is not rooted anymore. Anyone else?
Has anybody used the the latest version of superuser with oos 4.0?
That's the SR2 2.79 version. The one before turned off sims and a reflash of 4.0 sorted out.
And the info on Magisk has been informative. Thanks!
As someone who has used phhSu and SuperSU (I've also paid for SuperSU Pro) I find either do the job and that SuperSU is good for getting a ROM going while I prefer to then re-root with phhSU after I have my ROM set up for daily use, although the only annoying thing with phhSU is that TB detects the su binary as being a non-SuperSU one so it pops up an extra warning.
Either is fine, just pick the one you like better I guess.
How did you guys flash a systemless root without triggering DM-Verity?
From my understanding, we flash superSU after flashing TWRP and allowing modifications, because superSU disables/bypasses DM-Verity
Am I missing something here?
Freyelis said:
How did you guys flash a systemless root without triggering DM-Verity?
From my understanding, we flash superSU after flashing TWRP and allowing modifications, because superSU disables/bypasses DM-Verity
Am I missing something here?
Click to expand...
Click to collapse
With SuperSU 2.79 you don't need no-verity patch.
m0d hipp¥ said:
I haven't seen a thead posted about this so I figured I'd get some input from people that have used both or either of the 2 root options.
What do you prefer and why? What are the pros and cons?
I know SuperSU is very well known and I'm familiar with it from the Galaxy S phones. Magisk is fairly new, but from what I heard it works well with Nougat and the other nice thing is that magisk can be toggled.
I'm not sure if there is any benefit to that or not, but I'd like to hear some feedback.
Click to expand...
Click to collapse
Actually Magisk doesn't give root but the modded version of Phh's Superuser does.
One of the main difference is that Phh's Superuser (and Magisk) are open source. Once Chainfire will leave his SuperSU project you will have to fully trust CCMT.
@topjohnwu
I'm sure you've read the google+ message or the post on the front page in regards to Chainfire stopping development on all current root-related apps. This includes thus SuperSU (which was sold to CCMT a long time ago and they did absolutely nothing with) and FlashFire (which i use to flash an OTA and keep root intact.
Now with that in mind, magisk is pretty much the only root solution now and i'm starting to look into it. I've already installed the manager and will flash the stock rom at a later point. First a question.
What would be the proper way to flash an OTA (on my 6P, for as long as it will get them) and keep magisk root intact? (i know my way around ADB a bit and twrp, usually i ADB BOOT the latter, not install it). Has anyone tried the latest magisk with flashfire on a 6?
I'll appreciate your input.
Regards,
Ch3vr0n
I'm also interested in getting OTAs installed while preserving root and magisk, on my Pixel XL. I can't get it working properly using the suggested method from @topjohnwu
May i suggest you make your own topic then? It will do neither of us any good of replies to our issue get lost in replies to the other
I did already.
I just showed that I am interested in a proper solution as well. I have not asked specifically about my issue, but wanted to tell you that the "official" way (which is well documented) doesn't work for some users (it's not only me).
yeah but you have a completely different device. So what's not working for you, isn't even relevant in case. Thanks for the interest though
and a quick bump.
Ch3vr0n said:
Has anyone tried the latest magisk with flashfire on a 6?
Click to expand...
Click to collapse
Hopefully you're aware that you can no longer even purchase FlashFire on the Google Play Store, so it's not a solution going forward...
Who said that was a problem. I've been using pro since day 1. Pro users don't have the time issue and it works just fine.
Sent from my Nexus 6P with Tapatalk
OTA installation tips (from the official Magisk docs):
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
I know that A/B device users have been reporting negative results with the documented method, but fortunately it's not applicable in this case.
Have seen a bunch of reports of Flashfire not working properly with later release of Magisk, but can't confirm since I've never used it.
That leaves the last described method. Should always work, but by then I usually feel it's a lot easier to just use fastboot to flash the latest factory image...
I have some phones with Magisk, and are not A/B devices. Magisk gets lost after the OTA, I just reflash it, reinstall the 4 Magisk modules I use, and open each app that requires root so I can grant root access to them again. Of course, add to Hide the banking and other apps that need it. Not too much trouble for me, even if I usually receive weekly OTAs. Wish I could save the Superuser and module settings of Magisk before flashing, then I can just restore it.
I have long used supersu and have been having lots of troubles with Magisk including many root apps not working properly. I know all about the potential issues with supersu but might be willing to accept that. So has anyone gone this route? Or is it simply not possible with this device? Thanks