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.
Related
Hey everyone. I am not new at rooting phones but this appears to be the one phone that is giving me issues.
My note 4 is telus, was n910w
installed this rom:
http://forum.xda-developers.com/note-4-tmobile/development/rom-vision-x-n4-intl-t2943448
working beautifully thus far but I cant seem to root....
I have tripped KNOX 5 times so far trying to do it, each time it appears my phone is not rooted as titanium cannot verify SU, and aswell I have a root checker which tells me it is not rooted.
I have tried several versions of ODIN, and cf auto root n910t, AND V.
Do I maybe have to reinstall my rom? Or is there something I am missing because this is frustrating me....
Is there something I am doing wrong? Superuser IS on my phone, but its not doing anything but being there.... Please any kind of help would be appreciated as I am stumped.
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Framaroot
Sent from my Trident-A1 using XDA Free mobile app
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
This worked, I am a dummy lol
Thanks alot!
Glad I could help
Glad you got it worked out but note that you can only ever trip Knox once. Once it's tripped it's tripped, so don't worry about it.
neofreek01 said:
I'm not sure what rom you are running but I do know there were some issues with su and lollipop in the beginning that required you to go into superuser app setting 's and change from prompt for root to allow all requests. For some reason it wouldn't prompt for root for root apps. But if you changed it it would auto.atically allow root apps root access
Click to expand...
Click to collapse
I had lost root after flashing the PopRocks ROM. Couldn't figure it out and stumbled across this post. Now it works perfectly. Thanks! :good:
Hi Guys, I know a lot of people here on xda cannot go on their daily lives without root on their phone, but there are these pain in the bottom applications that refuse to run when root is detected. my only means of hiding root back then was using an xposed module, may I know if someone else have an idea on how to hide root from apps? thanks in advance!~
SuperSU Pro has the option that works for some apps. Not sure if it is in the standard version.
Best solution is to boycott HBO.
root cloak still works with 5.1.1. you can find it here in the forums. get the latest alpha version and it should work.
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.
banking app, not baking app, f**ks sake
Hello there. I have been using stock android 7.1.1 for a while and decided to try using roms again (Pure Nexus). One of the apps that i need is "Vipps" its a Norwegian banking app used to transfer money to friends and stuff, but its notorious for finding root. I used to use xposed and root cloak on android 6, but i know well it dosent work with 7. Magisk dosent hide it, suhide dosent hide it.
After installing Vipps it rejects opening promting me with "Vipps does not support rooted devices". Only thing is its running a ROM that comes with no root.
- Cheers, Kristiansja
edit: root checker doesn't find annything either
kristiansja said:
banking app, not baking app, f**ks sake
Hello there. I have been using stock android 7.1.1 for a while and decided to try using roms again (Pure Nexus). One of the apps that i need is "Vipps" its a Norwegian banking app used to transfer money to friends and stuff, but its notorious for finding root. I used to use xposed and root cloak on android 6, but i know well it dosent work with 7. Magisk dosent hide it, suhide dosent hide it.
After installing Vipps it rejects opening promting me with "Vipps does not support rooted devices". Only thing is its running a ROM that comes with no root.
- Cheers, Kristiansja
edit: root checker doesn't find annything either
Click to expand...
Click to collapse
Go into the root settings and remove root. Mind you this cause some of the features of the rom to stop working. Apps like that are not only looking for root but also for unlocked bootloaders. So if those apps are important to you then might want to stick to a fully stock set up and relock your bootloader.
zelendel said:
Go into the root settings and remove root. Mind you this cause some of the features of the rom to stop working. Apps like that are not only looking for root but also for unlocked bootloaders. So if those apps are important to you then might want to stick to a fully stock set up and relock your bootloader.
Click to expand...
Click to collapse
Pure Nexus comes without root
kristiansja said:
Pure Nexus comes without root
Click to expand...
Click to collapse
Go into developer option and turn off USB debugging. After that, reboot the phone and see if Vipps is working. If that doesn't work, I have one more suggestion.
It's probably checking ro.build.tags and/or ro.build.type. These are set to test-keys and userdebug on PN (if I remember correctly) and some apps need them to be set to release-keys and user. It could also be looking for other prop values and possibly also busybox (also included in PN, I believe).
Or BusyBox...
Sent from my Nexus 6 using Tapatalk
Hallo,
managing some different devices and run them mostly with custom ROMs, rooting was again and again a topic in this endeavour. During this course I've came accross so many resources but it isn't 100% clear for me. This is an attempt to get any uncertainties resolved.
Any input is welcome.
There are many explaining what rooting means, gaining administrative rights on the file system of your phone (in linux, root or superuser is the username of the master admin). With root access, you can install and uninstall anything you want on the phone. But resources what rooting actually does on modern Android are widely scattered around but I haven't found place yet where it all is well explained in one decent post. I've gone through some articles but still don't fully understand what it does and how can I hide later on as it certain apps won't run if they detect if a phone is rooted. These are my resources:
Best way to hide Root and SuperSU from apps that otherwise block access on Lineage?
Question about LOS root, SuperSU and Magisk
Does magisk manager go well with lineage os
LOS Root or Magisk?
As I mainly looked in to rooting LineageOS many resources are referring to this ROM after rooting you have to manage binaries
XDA-Developers Root Directory
iSu
phh's SuperUser
Magisk on xda Magisk Root
SuperSU
Magisk Root
LOS root addon on xda LOS root addon
unsorted collection:
https://techviral.net/top-best-root-apps/#4nbspTrickster_Mod
https://forum.xda-developers.com/showthread.php?t=803682
https://techviral.net/best-tricks-for-rooted-android/#13_Top_10_Best_Root_Apps_2016_for_Android
https://techviral.net/secure-rooted-android-from-security-threats/
https://www.androidauthority.com/root-android-277350/
https://en.wikipedia.org/wiki/Rooting_(Android)
I just wanted to know. If this is true for a root. I mean, does this sound like a properly rooted device under these circumstances?
Taken from a chat log...
"Device is now rooted but PLEASE TAKE NOTE:
1.Do not uninstall SuperSU
2.Do not Factory Reset
3.Do not turn off developer options
4.Do not disable OEM Unlock (if you have this setting)
5.Do not enable Reactivation Lock (if you have this setting)
6.Do not install System Updates"
03:01
why not factory reset? Does this sound like a permanent root?
Confused
2ISAB said:
why not factory reset? Does this sound like a permanent root?
Confused
Click to expand...
Click to collapse
depending on the method and ROM, root related modification could be overridden when flashing. This is one of the reasons why I kicked off this thread. I want to outline it in more details (as soon as I have some spare hours)
PackElend said:
depending on the method and ROM, root related modification could be overridden when flashing. This is one of the reasons why I kicked off this thread. I want to outline it in more details (as soon as I have some spare hours)
Click to expand...
Click to collapse
Well it's a N7 stock rom for my M9 using the controversial Oneclickroot advertised on XDA.
So I just want to know if they root permanently using team viewer remote root. ?
2ISAB said:
So I just want to know if they root permanently using team viewer remote root. ?
Click to expand...
Click to collapse
can't tell you need to ask in the specific thread
2ISAB said:
I just wanted to know. If this is true for a root. I mean, does this sound like a properly rooted device under these circumstances?
Taken from a chat log...
"Device is now rooted but PLEASE TAKE NOTE:
1.Do not uninstall SuperSU
Click to expand...
Click to collapse
Uninstall it should not be a problem, the su binary already in /system (system way) and in boot image (systemless way). But if you remove SuperSU from that app you will LOSE root!
2ISAB said:
2.Do not Factory Reset
Click to expand...
Click to collapse
It's because some devices play not good with Factory Reset with root. Like my ASUS ZF2, everytime I try to factory reset + root, the device lost boot.
2ISAB said:
3.Do not turn off developer options
Click to expand...
Click to collapse
Read note 4 and 5 below.
2ISAB said:
4.Do not disable OEM Unlock (if you have this setting)
Click to expand...
Click to collapse
OEM Unlock will allow your phone to root. If you are rooted and you disable this option, your phone will brick (as it will enable the device to check system signatures). I had this mistake and my SS phone said on reboot "Custom binary blocked by FRP lock"
The fix would be full stock ROM flash.
2ISAB said:
5.Do not enable Reactivation Lock (if you have this setting)
Click to expand...
Click to collapse
Read note 4.
2ISAB said:
6.Do not install System Updates"
Click to expand...
Click to collapse
This is not true. Some device can still install OTA, but you must unroot. Else your phone might get hard bricked.
2ISAB said:
why not factory reset? Does this sound like a permanent root?
Click to expand...
Click to collapse
Yes, it's a permanent root. You can unroot if you want.