[HELP] Cyanogenmod 12 Root Access - T-Mobile LG G3

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

Related

[Q] Rooted but SuperSU stopped by KNOX [FIXED]

Hi sorry I am new here, I looked around and did not see an answer to this
I rooted my S3 yesterday using Kingo Android root and as far as I can tell everything worked properly (other apps detect that phone is rooted) but SuperSu is not working because Knox keeps on blocking it. I read a few fixes like just uninstalling SU and reinstalling via the play store but Kingo installed SuperSu as a system app so I cannot do this.
Do I have to reroot or is there an easy way to reinstall SuperSU so that knox is not in the way (all none of the ways to deactivate Knoxs from within the phone do not work because none of my root apps have superuser), I am a bit of a noob when it comes to cell phones.
An suggestions? Also I am looking to keep the data that is already on the phone
EDIT: I got it working
For anyone else having this issue I went to chainfire's website and downloaded the newest version of SuperSU
I opened the Zip found the apk (found in the common folder) and uploaded it to my phone.
Using the default filemanager I opened and installed the apk.
Since it is a higher version then the one in the store it let me update the original failed SU install.
Upon starting SU it updated the binaries and also disabled knox.
Just tried this way and it worked for me thanks. I had same issues there was no option to update from store and Knox kept stopping such..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] "Unfortionately superuser has stopped" Error messege PLZ HELP

Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
kingart93 said:
Hello to all,
I recently rooted my sgs3 sph-L710 v4.3 and am experiencing some problems. Whenever I try to open superusers it automatically closes, and I receive a notification saying, "security notice an attempt to access a secure area on your phone without authorization has been blocked." After doing some research online I discovered that the 4.3 version is protected by KNOX. Online sources state that in order to defeat the KNOX system you must update supersu, but I am not sure how to do that. Whenever I download supersu from the Google play store there is no option to update it. I would really appreciate any help thanks.
Click to expand...
Click to collapse
Have you checked to make sure you haven't lost root? When you install an app from Google play, you get the latest version.
sent from my GS3
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
I did it!!!
Mr. Struck said:
Also, have you actually opened up the SuperSU app? You need to open it up (not just download it) so that it will prompt you about disabling Knox, and it might also prompt you to update the binaries. And which custom recovery are you using? If need be, you can flash the SuperSU zip from recovery, and if you are using Philz Touch (HIGHLY recommended) there is an option to have it check for root before booting back into system.
Click to expand...
Click to collapse
Yes I finally got it to work I just re rooted the device and superuser was gone. However, i downloaded supersu and it prompted me to update, i did and I was able to bypass knox! I think it was a problem with the method I used to get my phone rooted the first time. The video tutorial I watched the first time told me to uncheck the 2 boxes that come prechecked on odin i believe one of them was auto reboot i cant recall the other one. Then I took out the battery of the phone and selected the root file through mod recovery mode and that was it. The second time around I left the boxes checked and my phone auto restarted. I then downloaded supersu updated,rebooted, and Visalia!!!
Thanks guys I appreciate the help.

Root broken after nightly cm12.1 update

I am not very knowledgeable with the android operating system as a whole, I tried to learn as much as I can but mostly just wanted functionality so I installed cm12.1 for simplicity and root capabilities. Everything was going fine until one day the superuser built into cm12 stopped working after a nightly update(about 3 weeks ago i think), I didn't know what to do, so I tried downloading the app superuser from the play store. When I launched the app there was a notification saying the binaries needed updating and it wasn't working so I found the xda tread for SU 2.46 and downloaded it from chainfire's website. Then everything was back to normal, root checker was showing proper root and all apps were working fine.
When I updated to the current nightly (20151229) and booted back up I had the same problem where root checker shows no root and none of my apps work. So I thought all I need to do is reflash the binaries for SU. After I selected to reboot but right after the s4 mini screen it goes to a black screen and stays there.
Just reading about superuser now, I read that there can only be one super user method so I am thinking that when I downloaded SU from the play store I broke the cm12 internal rooting method, which caused real problems when I flashed the nightly as it overwrote that new method.
What I don't get is why cm12's superuser stopped working in the first place? If somebody knows what I am doing wrong I would really appreciate the help!
My plan as of now is to try and remove the app cleanly remove the app superuser and hopefully restore function to the in built cm12 superuser.
PLEASE HELP :cyclops:

Root access problems on Cyanogenmod 13

Hello to all (i have no idea if i am posting this in the right place sorry)
I have recently installed Cyanogenmod 13 on my Asus Zenfone 2 Laser/Selfie (1080p) (Asus-Z00T)
My phone works grate besides the fact that i have root access problems.
First i enabled developer options then enabled root (as now since Cyanogenmod 12 it is hidden) i installed busybox i grant it root access .So far so good nothing unusual i then install clean master then give it root access then when i try to use clean master to stop apps auto starting and i got an error no root access i then installed lucky patcher granted it root access no problem then when i tried patching a app to remove adds i got another root access error.
(I have had problems like this on Cyanogenmod 12)
Now with Cyanogenmod 11 if i get a little root bug i just go to super user app under system settings and delete the app access and then give it new root access again that solves the problem.
IT would seam that since CM12/CM13 there is no superuser app on board and no superuser settings either i have looked everywhere and i just can't find it.
I have the feeling that now root has become just a developer option it is not as good as on Cyanogenmod 11 but i could be wrong.
Could anyone help me please ?? is there a way to fix root access errors ???
The supersu type settings are in settings /privacy/privacy guard
Sent from my ASUS_Z00A using Tapatalk
Try re-rooting your device, in the worst case, flash stock rom, then flash cyanaogenmod and then root your device.
Hope this solves your problem.

Snapchat gives "login temporarily failed" error with CM ROM

Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app

Categories

Resources