SuperSu problems - T-Mobile LG G3

Well for some reason the SuperSu keeps saying i have to update the binary and i already have the some what the latest one the 2.41 I'm on cm12 lollipop its getting a little annoying and also I'm trying to use gamekiller it keeps saying root permission and i already grant it permission i need help i didn't even have this problem when i was in the stock lg firmwire I really need help thanks

If you updated without rebooting into TWRP, you might want to try it the boot to TWRP way. I have experienced issues if I do it the other way. Worth a shot.

Related

Cyanogenmod Installer

Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Capa1970 said:
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Click to expand...
Click to collapse
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
WearySky said:
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
Click to expand...
Click to collapse
I am not rooted.
Capa1970 said:
I am not rooted.
Click to expand...
Click to collapse
I wasn't able to find any way to get around Knox without rooting, but I may not have looked hard enough.
If you're willing to root first, CF Auto Root was super easy to do:
http://forum.xda-developers.com/showthread.php?t=1963790
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Capa1970 said:
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Click to expand...
Click to collapse
That *is* a Knox message, for sure.
So it looks like the Cyanogenmod team were not able to circumvent Knox for their CM installer. It's probably just a matter of time. Here is the full Knox notification:
"An application attempted to access system on your device without authorization. This attempt has been blocked. Updating your security policy may solve this problem. Deleting applications obtained from unauthorized sources may improve security."
There are three options at the bottom of the screen: Cancel, Update, and View Apps.
Update: I was able two days ago to use the Cyanogenmod Installer and I am now running CM!! First time for me to ever root and flash a Rom (I was an iPhone guy).
The phone is faster and smoother. I never liked the Touchwiz lag and most of the Touchwiz features worked inconsistently. The only thing that I miss is the camera. I have not found any bugs yet and so am very happy thus far.

[Q] Update error 407

I'm rooted stock 4.3, I hear the S3 has the 4.4.2 update? Is that true? What is the error in the attached screenshot mean as well? I'm connected to wifi and I get the error no matter what.
I also have another issue I'm curious about and rather than making a second post I'll ask that too.
I have the supersu app. My rooted apps completely detect root and work. I want to change from the supersu app to the Superuser app for personal preference. I get stuck at 'Making sure new su works'. Why? I also get this no matter what.
Screenshots of both issues attached.
The latest is 4.3. If you are rooted then you most likely have a custom recovery and that is why whatever OTA update you are trying to get is failing.

HTC Desire HD Superuser problem.

I need some help with Superuser. Currently running Mustaavalkosta 's CM11 BR4 and Superuser version 3.1.3 (46).
After clean installing the ROM, Superuser works and allows me to grant root permission to apps. Temp unroot works but updating the binary immediately results in 'downloading manifest... fail!' and if I click the 'try again' button, Superuser crashes. No big deal cause everything that I need it to do, works. A couple of days later however it just stops working and no longer grants permissions... I still have root. Temp unroot stops working and crashes Superuser when I try to use it. The file /system/bin/su still exists.
Things I tried:
- clear Superuser data
- uninstall Superuser and reinstall from Play Store
- install SuperSU
None of the above works.
Please somebody help me out here, I don't want to keep restoring my Nandroid cause it still is alot of work. Thanks
After doing some more research I think I fixed the problem by flashing the latest SuperSU.zip instead of installing it from the Play Story where it wouldn't let me update the binaries. I can now grant root access again to apps.
Still no idea what caused the Superuser issues but I 'm glad with this 'workaround'.

[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)

[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.

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

Categories

Resources