Related
I was on stock 1.8.3. I have never rooted before. I tried the gingerbreak.exe and gingerbreak.apk method. Do I have root? Well, you tell me. I did alot of reading here to see what to do. I installed Rootcheck and Connect bot. According to both of them I have root.
I've installed Titanium backup (free) and Shootme (was one of the apps recommended to use to see if have root).
Each time I open Backup I get the following message: Your system settings will prevent you from restoring applications. To correct this, go to your phone's Settings, then in "Applications" and tick the "Unknown Sources" checkbox. I don't have an "Unknown Sources checkbox.
Each time I run Shootme I get the message: Shootme has been granted Superuser permissions...Trying to start server....Failed starting server. Please check you have "Root" access on your device and enabled access to the lower level graphics.
I have Superuser in my apps. Everything Ive installed for the rooting process shows up there as allow (ConnectBot, Gingerbreak, Root Check, Shootme Titanium Backup).
Regarding Sideloading........
I've tried to enable sideloading using Gladenable. It shows:
Allow Superuser request on your phone. Files copied. Press any key to continue. I press enter.
It asks Do you want to install sideloading? [y/n] I type y and hit enter.
It shows Allow Superuser request on your phone..
Permission denied. Press any key to continue.
I don't need tethering so i type n. Phone reboots.
I tried using Superoneclick's Allow Non Market Apps. This is what it shows:
OK
Checking for sqlite3
Pushing sqlite3...
1177 KB/s (24120 bytes in 0.020s)
OK
chmod sqlite3...
OK
Getting settings.db location...
/data/data/com.android.providers.settings/databases/settings.db
OK
Checking value... (requires root)
Non-market applications are disabled.
Allow non-market apps... (requires root)
OK
Checking value... (requires root)
FAILED
I tried to see if i could install a non market app from Amazon. i downloaded it but got the unsafe app warning and it wouldn't install.
Can someone help me here? Am i rooted? Why can't I sideload?
Thanks
Go here --------->
Root Checker
Try this, double-click Superuser to make sure it's actually running and then go back into Titanium Backup. If that's not working, then download "Busybox" (if it's not already showing in your app drawer). Download,install, and let BusyBox do its thing.
I had to go through that stuff to use Titanium Backup with Gladroot...
ccrows said:
Try this, double-click Superuser to make sure it's actually running and then go back into Titanium Backup. If that's not working, then download "Busybox" (if it's not already showing in your app drawer). Download,install, and let BusyBox do its thing.
I had to go through that stuff to use Titanium Backup with Gladroot...
Click to expand...
Click to collapse
I clicked superuser (not sure how to double click on my phone), and opened it. I then went into manage apps and checked to see if it was running. It was. I opened Titanium backup and got the same message as before.
I checked the market for Busybox. There were a couple Busybox apps by different people. I installed the one with the most downloads, by(stephen stericson). It shows in my app drawer as Busybox Installer. It says I'm rooted. Not sure what to do with it from there though. I again opened T. Backup again and still get the same message..
dwaded said:
I clicked superuser (not sure how to double click on my phone), and opened it. I then went into manage apps and checked to see if it was running. It was. I opened Titanium backup and got the same message as before.
I checked the market for Busybox. There were a couple Busybox apps by different people. I installed the one with the most downloads, by(stephen stericson). It shows in my app drawer as Busybox Installer. It says I'm rooted. Not sure what to do with it from there though. I again opened T. Backup again and still get the same message..
Click to expand...
Click to collapse
That is weird.
I have the Bell version so unfortunately I can't speak for newer AT&T firmware.
This is my 5th Android phone, and gaining root on this is the biggest PITA I've ever dealt with. Half the time you're rooted and the other half you're not. I kinda knew that things weren't gonna be easy when Superoneclick had issues with this device.
Anywhoo I'm waiting for an "Official" stock Bell SBF to surface before into the deeper end of the pool on this device...
I played with Titanium Backup tonight. It let me do a backup. But I still get the same message whenever I open it Your system settings will prevent you from restoring applications. To correct this, go to your phone's Settings, then in "Applications" and tick the "Unknown Sources" checkbox.
I still can't get sideloading enabled.
download "terminal emulator" from the market, open it, and type "su" and then enter. if you see a # sign, you are rooted. if not, you are not rooted.
CaelanT said:
Go here --------->
Root Checker
Click to expand...
Click to collapse
Sh*t. Well thats gunna be handy. Thanks!
Well I am rooted.
And after numerous attempts with Gladenabler I finally have sideloading. I tried something different. With the phone connected to the computer I turned USB debugging off then turned it on. Then ran Gladenaber. On the first try I finally got the superuser request, but the sideloading permission was still denied. I tried it one more time and whoo hoo it gave me sideloading.
Thanks for the replies
Don
I have a HTC IS. I have rooted it .... well ...
In fact, if I use terminal emulator, I do have root access: su brings the prompt sign to #.
But, if I use connectbot, then not root access: su does bring the message "permission denied".
Is this correct??
Thanks
update:
-----------
I used Root check and it reported that my root access was not properly configured.
I booted in recovery mode, and activated "check permissions". Next, root check confirmed my root access.
since upgrading superuser to 3.0, I can no longer access Titanium Pro
It says it has root permissions in superuser, but Titanium Backup says it cannot acquire root priveleges.
I ununstalled and reinstalled both programs, then TB would hang at the asking for root permissions screen first time. Next time I go in, it gives me the error about no priveleges. If I click switch Profile, I get asked to give it su permissions, which I click allow and tell it to remember, but it still gives me the same error. After a phone reboot, it goes back to sticking on the 'asking for root access' screen.
I used Rootchecker to check my access, it tells me Busybox is installed correctly and that I have root access. Juice Defender continues to work fine as well in the areas requiring root access, as do the adblock programs
I have no idea at all what to do! Please help…
Keiron
Try this...
I just checked mine and everything works fine. I would try deleting Titanium and then re-install it and see if that helps, or try going into SU and erase Titanium's permissions and then try to run it again so it has to ask for superuser access again.
Hope that helps
Solved
just sorted it... Seems it was an app called application protect, didn't like the update. Disabled it and all good now. I had it set to ask for pattern logo password on su access... Worked before, not after...
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
jsgraphicart said:
I just saw this on the XDA home page. Its a new super user app. As we know, the SU app on CM7 is a little buggy and doesnt always give super user permissions. Maybe this app will work better for us. Im going to be trying it out soon.
http://forum.xda-developers.com/showthread.php?t=1538053
UPDATE: So I installed it and tested all my root apps. Seems to work well. I will give it a day or two and see if I have any of the apps fail to get root permissions. If this works and fixes the SU problems we have, then this is a great thing for us CM7 users.
Click to expand...
Click to collapse
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Thanks Moon Shadow. The only time I had it hang on "asking for root access" is with Titanium Backup. I think that had to do with the SuperSU app freezing though when trying to get into the settings tab in the app. It just freezes up when selecting that and I had to go into application seetings and manually force stop the app. After that, everything worked fine. I think its just that settings tab for some reason.
The way I installed it was installed SuperSU from the market, then uninstalled the old Super User through the market. I then opened SuperSU and it asked to update so I did. After that, I went through all my root apps and the new SuperSU prompt popped up for all and I granted access. I too see the old SU in the app drawer. Opening that though shows that the only thing that its granting root access to is the new SuperSU app. It doesnt seem to be conflicting with anything so far.
Moon Shadow - NM said:
Since I am very familiar with ADB and the command line, I tore apart the apk in the linked thread OP to make sure I understood what was happening during the install. I moved the original su binary and Superuser.apk to my emmc (internal memory card), manually pushed the new files out to my phone, and then rebooted.
Once CM7DX2 came all the way up, I started doing some testing and noticed the the original Superuser APK was still showing up in my app drawer. If DOESN'T appear to be conflicting with the new SuperSU APK, but I'm not sure. I have had a few times of the SuperSU app stop responding and asking to either force close or wait. After hitting wait a few times, I ended up just FCing the app.
Once everything smoothed out, the SuperSU seems to have worked, bu, I was still receiving "not responding" messages from the SuperSU app when apps were asking for Root access.
I am going to also cross-post this to the linked OP thread and see if Chainfire wants more digging into this.
Also, as a side note, I think the reason the CM7DX2 Superuser APK was still appearing is that it MAY be installed as part of 2nd-init. I'm not 100% sure about this.
So, in conclusion, for CM7DX2, I think this needs more digging in to and I will offer to work with Chainfire to see what we can do.
Ciao!
Click to expand...
Click to collapse
Kind of random but Moon, you are a goddamn machine. The moment something great releases you take it apart and make it better. Good **** man, good ****.
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
xawen said:
Just including my experience...
SuperSU is working like a champ, but had major issues until I removed Superuser completely.
Here's how I installed:
- Install SuperSU from market
- Uninstall Superuser from settings > applications
- Launch SuperSU and allow it to update it's binary
- Delete superuser.apk from system/apps (use root explorer, es file explorer, terminal, etc...)
- Reboot
Since changing over to SuperSU, I haven't seen a single hang while an app is requesting su permissions.
Click to expand...
Click to collapse
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Sent from my MB870 using Tapatalk
i find this relevant to my interest any one else test
Xb0i said:
i find this relevant to my interest any one else test
Click to expand...
Click to collapse
Follow xawen's directions and you'll be fine. It works like a charm.
Sent from my MB870 using xda premium
cant uninstall superuser from settings- applications. doesnt give the option
Xb0i said:
cant uninstall superuser from settings- applications. doesnt give the option
Click to expand...
Click to collapse
Did you go Settings> Applications> Manage Applications and hit the app? If you dont see that option, go into Titanium Backup (an app you have no excuse not having) and uninstall it. Then go into Root explorer and follow the above directions to totally remove it. Then reboot. It may seem like it isnt totally gone cause you may see the icon somewhere, but it likely is gone and a reboot is needed in order to confirm.
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Xb0i said:
yea got the tiBu. but i tried force stopping and clearing data and uninstall never popped up. thought about removing in TiBu buts thats not what it said in the instructions.
Click to expand...
Click to collapse
Its what I did. Its a bit of a deviation but it got the job done and thats what matters, ya know?
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Xb0i said:
wow pretty bizzare i cant find superuser in TiBu! whats goin on lol
Click to expand...
Click to collapse
Did it disappear after you rebooted? If you have root explorer, go into system/app and see if SU is still gone. If so, you're in good shape.
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Xb0i said:
to clarify
before i even started i backed up original superuser.apk to a folder on sdcard from root explorer, then
i downloaded supersu from market.
went to settings-app-manage apps- etc no choice to uninstall. force stopped- cleared data, still no uninstall option.
went into titanium backup to uninstall from there and superuser wasnt even listed in the apps! (ok weird)
only option left is to just delete from root explorer then continue continue to launch supersu, update binaries and reboot but im holding off.
Lowend was supersuper listed in titanium for u? y isnt it showing up in my list. i find it odd
Click to expand...
Click to collapse
I can't find superuser in TB either... it is kind of weird...
i believe u cant delete superuser from tibu cus u need superuser for root access so its like a paradox. i dunno y instructions were as someone showed cus it seems the only way to get this to work properly is delete from root explorer. but im gunna hold off till someone confirms this more legit
I don't understand why you're holding off...if SuperSU is active, go for the reboot and see if the old superuser app clears.
Sent from my MB870 using xda premium
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Xb0i said:
id rather not have a headache if it messes something up.
this thread however gives some detail on supersu
looks like sum apps look for the presence of superuser.apk in data/app and possibly system/app.
a dummy file looks like it can resolve issues. ill switch when more testing is done on CM7dx2.
forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
It's odd that you guys don't see the uninstall option for it... Do you see it in Market (err...Google Play, stupid name)? That's another way to get the uninstall done. If it doesn't show up there, you should be able to use root explorer and delete it from /data/apps and /system/apps.
When we installed CM7, the instructions had us update Superuser from market. That would have installed it in /data/apps, so it just needs to be yanked from there. Uninstall via market, tibu, settings>apps or manual through root explorer should all do the same thing. Then you can delete the built in one from system.
Also, if for some reason the whole process breaks down on you...there's a flashable version of the original Superuser that will probably get you going again. I haven't tried it on CM7 though...
jsgraphicart said:
Same here. This new SU seems to fix the issue we had with the old one. The only problem is that damn settings tab. It freezes the app.
Click to expand...
Click to collapse
The most recent update (pushed yesterday) fixed this for me.
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
I have been having this same issue on rooted stock gs4. It's temperamental when it comes to root I've noticed. One day I was able to turn it app off of auto start and when I installed a new app it wouldn't let me do it and su says I'm granted
I'm experiencing the same issues. Auto Start Manager is the only feature that has this issue.
Sent from my SPH-L710 using XDA Free mobile app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
I always face this issue also, what I do as a temporary fix is, go to the SuperSU app, then "Forget" Clean Master, open Clean Master and try to disable an app from Auto starting, grant root and the app will be disabled I hope it works for you too
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Unfortunately this does not work for me.
I have granted root access according to SuperSU Pro however when trying to stop autostarting apps in Clean Master it reminds me to allow access.
I even get a popup massage from SU stating that the app got granted root access.
Whats happening here? Does anyone have a work around?
Deleting Cleanmaster in SuperSU doesnt help. It is always the same unfortunately.
Best Regards
J
I too also have problems with the autostart function in Clean Master on my Optimus Zone II
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Re:Re: [Q] CleanMaster Root Access Failed
Vtrendzzy said:
First of all, if you've root then you shouldn't use clean master. That's so naive.
About the permissions. Even after root your system partition stays in read only mode. I'm guessing this okay. You should check that out first.
Click to expand...
Click to collapse
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
DerDoktorEsq said:
Ok, (I know Im gunna reget this), but why?, in your option, should Clean Master NOT be used, since it need so many "root" functions in order to work? Ive used it for years. Rooted or no, (mostly rooted), and why do all the "autostart" apks, (ROM Toolbox, Autostarts, Autostart Manager,etc) work just fine. I've tryied it with r-w on system on, sooooo....next...?
Click to expand...
Click to collapse
I can't argue over this. Best options for you 1. Root Cleaner (high priority) 2. SD Maid Pro (medium priority)
See the difference yourself.
fix?
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
dillweedinc said:
Has anyone figured out what the issue is here? It worked just fine on cm12 but stock Lilli nope. Root issues for sure it must have something to do with system partition. Has anyone fixed this issue?
Click to expand...
Click to collapse
Has anyone figured out what the issue is here?²
hey..the main culprit is supersu app
yoongkc said:
I have already given root access to the app Clean Master. Under the 'Autostart Manager' page, I tried to remove apps that autostart by itself. However, the app pop out a message indicating 'Failed to Grant Root' and reminded me to grant root access.
I went back to the superuser app, it was indicated that root access has been granted.
Any way to solve this problem?
Click to expand...
Click to collapse
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Clean master root access
wow. cool...,ill try that,
thanx
it's supersu problem
StoneyJSG said:
I am glad I am not the only one having this issue. I recently updated an app via the play store and clean master told me it was auto starting. I tried to block it, but it keeps telling me root access failed and to grant it. Well I've granted it root 18 times now and it still says root failed. I have tried everything to get it to work...clear logs, tell superSU to forget clean master, give it global default, etc. Nothing seems to work and it's pissing me off.
Click to expand...
Click to collapse
Just go thru my above post..it will definitely work..so give it a try... flashing new supersu 2.49 resolved the problem for me.?
Yep its working again. I tried 2.48 cuz somebody said it worked for them, but i had no luck there. 2.49 did the trick, thx for letting us know in the thread.
tycoon78[stoner] said:
Clean master is not working on 2.46(I mean the autostart manager) I noticed this yesterday..i flashed a new Rom first it was having Supersu 2.46 version in which CM was not working but after flashing Supersu 2.49 CM is working plus in Google store supersu 2.46 beta is there which won't work...my clean master started working again normally like before after installing SuperSU 2.49...so try flashing or installing supersu 2.49
Link for supersu zip (Flashable zip)
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Its working for me too.
Thanks tycoon78 for the tip
RE:RE:RE: [Q] CleanMaster Root Access Failed/SuperUser
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Ahhh! Thank you so much tycoon! It works for me after updating super user!
QUOTE=Alison.Souza;60674697]Its working for me too.
Thanks tycoon78 for the tip [/QUOTE]
DerDoktorEsq said:
The new Super SuperUser Apk 2.49 from chainfire, did not work for my CleanMaster blocking apks from autostarting on my little optimus 2....:crying: any other suggestions?
Click to expand...
Click to collapse
I just rooted my s6 edge and was having the same issue with 2.46. Luckily when I updated to 2.49, I was unable to block the autostartup apps.
I installed Greenify on my HTC M7 with Cyanogenmod 12, but didn't get the 'Grant Root Access' question. Now Greenify can't hibernate.
I tried deleting and re-installing the app, but it didn't help a bit. Also tried using superuser apps, but still no root access question. For I think that's the cause why Greenify can't hibernate my apps in Root mode. Any ideas on how to fix this?
You could check your SuperUser/Super SU to ask for greenify root permission again. What probably happened was that you failed to respond in the short window of time to allow root access to greenify when the popup appeared for the first time & now it is denied unless you manually tell your SuperUser/SuperSU to ask again. Do check the log for permission allowed/denied in your SuperUser/SuperSU app. Hope it helps.
Salman Babri said:
You could check your SuperUser/Super SU to ask for greenify root permission again.
Click to expand...
Click to collapse
Have Useruser installed right now, but can't find this option? No apps in application list. Can you tell me how I should do the above?
Looks like a problem with root access on my phone