Hello happy new year, i see Cyanogenmod 11 comes with a superuser tab so i assume it's rooted, but root checker says my device isn't rooted.
I tried installing it anyways and rebooted the phone, no errors. But after i rebooted i saw a forum post saying i could get my phone bricked if i run xposed on an unrooted phone.
So i unistalled it before running the app again.
What should i do? Can i just install xposed with CM 11 as it comes or i need to do something else first?.
I've used eRoot with GB, ICS, JB with no issues but it doesn't work with Kitkat, so i'm not sure if i should just install it or what.
I really want some modules but i don't wanna break the phone :c
Installing Xposed on non rooted phone can't brick your device simply because root operations can't be done.
Xposed needs root access for installation process.
Madbezier said:
Hello happy new year, i see Cyanogenmod 11 comes with a superuser tab so i assume it's rooted, but root checker says my device isn't rooted.
I tried installing it anyways and rebooted the phone, no errors. But after i rebooted i saw a forum post saying i could get my phone bricked if i run xposed on an unrooted phone.
So i unistalled it before running the app again.
What should i do? Can i just install xposed with CM 11 as it comes or i need to do something else first?.
I've used eRoot with GB, ICS, JB with no issues but it doesn't work with Kitkat, so i'm not sure if i should just install it or what.
I really want some modules but i don't wanna break the phone :c
Click to expand...
Click to collapse
Go into developer options and make sure root access is set to apps, or apps and adb.
Common sense isn't all that common
Download set up first and then run the file after complete it.
Hi to everyone! I have to say I'm puzzled about my phone, since I got him I started to do some tweaks here and there, when I still used the stock ROM, I used the toolkit to root, install TWRP bootloader and my first custom ROM in this phone (it was Slimkat btw). Since that ROM was kinda stable, I used for like a year, until recently I flashed via TWRP the latest Lollipop AOSP, I have to say it's great for this phone... but suddenly I realized that there was no Superuser or SuperSU app, so I decided to run the Rootchecker and somehow my device is not rooted anymore!
I tried to Root again with the one click toolkit, but it didn't work, and all other method I tried didn't work either. Posting this thread is my last cry for help to root my device, please help me!
You have to flash SuperSU apk with TWRP.
Use Google to find the last version by Chainfire and everything will be OK
Sent from my Optimus 4X HD using XDA Free mobile app
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.
Hi guys, I am getting tired of not being able to use several banking apps, and therefore would like to unroot the phone. I've tried several hide my root apps, including RootCload and xpsosed framework without success. Would be grateful if anyone could help me to do a perm unroot. I've tried the full unroot functionality in SuperSU, but that doesn't seem to work. Are there any ADB commands or any files I can flash in order to unroot? Btw, running CyanogenMod 13 st. of Sept version.
All help greatly appreciated.
killbox said:
Hi guys, I am getting tired of not being able to use several banking apps, and therefore would like to unroot the phone. I've tried several hide my root apps, including RootCload and xpsosed framework without success. Would be grateful if anyone could help me to do a perm unroot. I've tried the full unroot functionality in SuperSU, but that doesn't seem to work. Are there any ADB commands or any files I can flash in order to unroot? Btw, running CyanogenMod 13 st. of Sept version.
All help greatly appreciated.
Click to expand...
Click to collapse
As far as I know you can't disable root access in Cyanogen, even if you turn it of in developer settings.
sent from my Mi5
CM (since 12? 13?) has its own root mechanism which is built into the ROM, you can't disable that.
Ah, ok. That seems to add up, since I've tried several options to disable it. Are there any ways to hide the root that actually work? rootcloak and xposed framework didn't work for me.
killbox said:
Ah, ok. That seems to add up, since I've tried several options to disable it. Are there any ways to hide the root that actually work? rootcloak and xposed framework didn't work for me.
Click to expand...
Click to collapse
Like everybody has stated: CM and root are combine
If you like unroot, then loose CM and flash Miui using fastboot
marcel112 said:
Like everybody has stated: CM and root are combine
If you like unroot, then loose CM and flash Miui using fastboot
Click to expand...
Click to collapse
If you build with "eng" or "userdebug", yes.
If you build with "user" then no root is included, you need then SuperSU or similar to get root access back.
I have such a "user" build with own releasekeys available, if someome wants to test his apps with it, let me know.
I used CF Auto Root a while back to root my Nexus 6 (months ago). It did the trick getting the bootloader unlocked and rooting the phone. I then proceeded to install TWRP and then installed Pure Nexus. From then to know the phone has been a joy to use. This ROM is fantastic.
Recently I decided to look into custom Kernels, Elementalx is the one I have been reading up on. I installed the kernel, and then purchase the EX Kernel Manager. Using the app I realized that the phone wasn't rooted, or so it told me. I test this with the Root Checker Basic App and it confirmed that the phone was not rooted.
I am not sure what happened but what I wanted to do was run the SuperSU zip via TWRP again, but wanted to ask you guys if this would be an issue. I can't see why it would but it Rooth had already been achived and then it was gone so..... I just wanted to ask in case.
Sorry that this was a little long winded. Thanks in advance.
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Strephon Alkhalikoi said:
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Click to expand...
Click to collapse
Thanks for the quick reply. That makes sense. I will run SuperSU again. Take care.