Develop Bugs

[HELP] Cyanogenmod 12 Root Access

After months of sitting on the stock rooted rom I finally decided to install CM12 [Official] this morning.
everything is working fine but I have one issue. I've lost my root during install and can't seem to get it back.
So far I've installed SuperSU from the play store and the only thing that happens after telling me that the su binaries need to be updated is me getting the failed message when i hit update. I've also tried the secondary option of installing through TWRP but once you click that it does absolutely nothing.
Obviously there's something that i'm missing or doing wrong. does anybody have any input

Under development you have to enable Root for it to work
Sent from my LG-D851 using Tapatalk

That's the thing.... It is enabled under development.
I've restarted my phone numerous times and even did another fresh install enabled it again and the only difference this time around is that root checker is saying i have root now but supersu still wont update the binaries.

Root is now built into Privacy Guard for CM Roms, so if you need to manage anything you have to go to Privacy Guard in the settings. (In other words supersu is no longer needed)

I dont know if you should do this, but i did....
I launched odin and "re-rooted" my phone and it worked.
I already had Cyanogenmod 12 installed. I just put it in download mode and installed supersu through odin and its worked so far

SuperSU and Xposed are built in to Cyanogenmod 12. There is no need for either. Enable root access under Developer Options from the settings.
Sent from my LG-D851 using XDA Free mobile app

Why won't SuperSU update on CM13?

My Tab Pro 8.4 has been bootloader unlocked since I got it months ago. It has always run a custom ROM, usually just CM12 nightlies with root from SuperSU flashed in TWRP and no Xposed or other "fancy" stuff installed. Since the CM nightlies shifted to CM13 I can't get SuperSU to "update" (the notice that says you must update SuperSU). I've tried reflashing, I've tried wiping and doing new installation from CM13, I've tried different versions of SuperSU. Nothing works to successfully install an updated SuperSU. I've never had this problem before. I've read everything I can find and found several places where something like this is being discussed, but no path to resolution. How can I fix this?

I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.

Sicron said:
I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.
Click to expand...
Click to collapse
I've tried using only the built-in root method. I set it to "both APPS and ABP" (or whatever that last option is). That's not enough for Root Explorer, not enough for PIE Control, not enough for AdAway, at least in my case. All those apps still indicate that I'm not rooted.

Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Hmmm. Well, that'd be a great solution for me so I'll give it another go. Wipe wipe wipe, flash a CM13 daily, flash CM13 GAPPS, wipe Dalvic cache and cache, reboot. In Settings, enable Developer Options, set Root Access to Apps and ADB. Reboot. If that's not the recommended procedure I hope someone will let me know.

Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Well, maybe the problem I have is different than the one I THOUGHT I had. Wiped, installed CM13 daily, installed CM13 GAPPS, set Root Access in System/Developer Options/Root Access to Apps and ADB. I guess root access exists but I'm not sure. In Root Explorer I CAN switch folders from Read/Write to Read Only (normally a root only option) and AdAway installed and ran fine. BUT -- in PIE Control I still get "Can not, rooted only" when I try to use the "Back" command. There is often a "hashtag" (or "pound sign") symbol in the Status Bar, just as there would be if I needed to update SuperSU, but the symbol is on the far RIGHT and doesn't correspond to any message in the drop down box. Plus, I have never seen the pop up box that normally appears to ask me if I want to grant root access to an app or process. So, what am I? Partially rooted?

It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)

otyg said:
It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)
Click to expand...
Click to collapse
What I'm reading here makes sense but there must be another variable. My phone (Moto X Pure) is running a custom MM ROM, SuperSU DOES install and run just fine, I get all the expected root prompts and controls and the Back button (which requires root) works in PIE Control. I'm guessing, therefore, that the "problem" lies with CM13 as a specific MM ROM rather than with all MM ROMs. Time to flash a different MM ROM on my SM-T320.

Warning sign in notification telling me KingRoot is bad?

Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?

joppy said:
Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
Click to expand...
Click to collapse
Fulmics has SuperSu installed as System application,there was no need to install KingRoot..
Also if you have two Root apps (same like SuperSu),then your phone isn't going to have a good time..
So delete KingRoot and stay with SuperSu.
Greetings.

Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?

joppy said:
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
Click to expand...
Click to collapse
The best choice is to uninstall it.Because it has setted it's self as a system application.
But also i think it has an option (in-app) "Uninstall".
In addition if Kingroot is unable to uninstall by using the inapp option then try installing an app from Play store called " System app remover" and delete it from there.
If nothing works then doing a clean re-installation of the ROM would be a great option.
A Tip:Never install an other Root application while you have SuperSU.
Let's take Kingroot for an example, when you have SuperSU and install Kingroot then automatically Kingroot detects that you have an other root application and it set's it's self as system app.

System app remover did the trick. Removed the King Root app. Result is o/c that adaway is no longer working. So I get to play around with SuperSU now. As I am new to SuperSU I am not sure how to get the correct settings. Should I make SuperSU a system app? Or set permanent full root?
Btw, I never had any problems running King Root. It was even a very nice way to charge the phone because King Root made charging go faster.
I've been thinking about the warning sign I got, and could it possible be a generic warning because King Root had root access? Meaning I would get the same warning with other apps with root access?
It seems strange that King Root that is mentioned som many times here on XDA should be crapware. Surely some smart people would have noticed and made posts about it? I am thinking maybe I panic'd and removed King Root prematurely?

Darn it. SuperSU won't run or allow me to set root access to apps. So no TWRP does not work, adaway does not work, root checker confirms I don't have root anymore and to make things worse, SuperSU says I need to upgrade, so I downloaded the latest version as a zip file to install from TWRP but guess what, no more root access. I will try to boot manually into TWRP and install SuperSU. Hopefully that will work.
And reading SuperSU thread it clearly says I must have ROOT prioer to install SuperSU.
Is there are fulmics setting somewhere I have overlooked? Can I set root from within fulmics tweaks?

Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.

joppy said:
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
Click to expand...
Click to collapse
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?

Sotiris02 said:
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Click to expand...
Click to collapse
Seems I am good after all. Turned out I messed up the fulmics 6.1 badly when trying to get adaway for youtube to work. So now I got fulmics 6.5. Yeah I know it is not the latest but I had slow internet connection and 6.5 was already downloaded but not yet installed so I just picked that and did a swipe, and twrp install of fulmics 6.5.
I did however install king root 5.01 again to get an easy way of getting everything else important installed that requires root.
If I don't see more warnings I think I will be fine. If I do I will take the plunge for superSU and read up on that before making the switch.
If I see those warning signs again I will try not to panic and try to keep calm

Missing 'Root Access' option after updating lineageOS 14.1 on Motorola Moto G 2015

Last night I downloaded and updated 'lineage-14.1-20170721-nightly-osprey-signed.zip' for my Motorola Moto G (2015). After installation I noticed that Root Grant prompt was a little different from the previous. Anyway, after granting root permission to some apps I suddenly found that those apps aren't working anymore. I went to developer options and found out that the Root Access option is gone. The Manage Root option was also grayed out. I tried to remove and reflash the SU addon a couple of times but it didn't work. I installed Root Checker and it's telling me that the Device Is Not Rooted Properly. I also tried downgrading the updates to the previous nightly. But nothing worked. Any type of help/suggestion would be really appreciated. (I'm quite new to this ).

debsntt said:
Last night I downloaded and updated 'lineage-14.1-20170721-nightly-osprey-signed.zip' for my Motorola Moto G (2015). After installation I noticed that Root Grant prompt was a little different from the previous. Anyway, after granting root permission to some apps I suddenly found that those apps aren't working anymore. I went to developer options and found out that the Root Access option is gone. The Manage Root option was also grayed out. I tried to remove and reflash the SU addon a couple of times but it didn't work. I installed Root Checker and it's telling me that the Device Is Not Rooted Properly. I also tried downgrading the updates to the previous nightly. But nothing worked. Any type of help/suggestion would be really appreciated. (I'm quite new to this ).
Click to expand...
Click to collapse
Strange error. Mabe you should backup your data, wipe system, cach, dalvik and flash lineage...singned.zip and addonSU..zip

Magisk v16(1600) keeps updating to the same version?

Hello all, Im having an interesting problem on my Z2 Play. Phone is rooted, stock rom, Xposed, using Magisk v16.0 and v5.6.4.
Every so often Magisk says there is an update (v16.0 which im on), it stops working, and then seems to have uninstalled itself after this update notification. I install this "update" , v16.0(1600) (same one every time) and everything works again. Then in a few weeks Magisk says there is an update again....v16.0(1600), it stops working, uninstalls itself, etc.
Is this normal behavior? Should I try to install version 16.3? Any help would be appreciated.
Sorry if i missed this being covered before. I did search but didnt see anything.

Something uncompatible.
Do not let it auto update

Mark2014 said:
Something uncompatible.
Do not let it auto update
Click to expand...
Click to collapse
Turned it off....didnt work. Still randomly says theres an update, and uninstalls itself.
Any other suggestions?
Gonna try the Beta 16.4 build.....

steveindajeep said:
Turned it off....didnt work. Still randomly says theres an update, and uninstalls itself.
Any other suggestions?
Gonna try the Beta 16.4 build.....
Click to expand...
Click to collapse
Install a firewall application, and make Magisk offline (block it from the app). No update notification any more

Mark2014 said:
Install a firewall application, and make Magisk offline (block it from the app). No update notification any more
Click to expand...
Click to collapse
its not the notification that bothers me...its the random uninstalling itself lol. Ill see how the beta fairs. thanks

steveindajeep said:
Every so often Magisk says there is an update (v16.0 which im on), it stops working, and then seems to have uninstalled itself after this update notification.
Click to expand...
Click to collapse
Goodluck.
But I think the problem is Magisk can connects to internet to get info. So, make it offline.