Database Users

Rooted but some apps say other wise.

I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.

njswift10141980 said:
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
Click to expand...
Click to collapse
Install busybox installer from the market and install/update busybox. See if that fixes your issues. Also try installing SuperSu from the market, opening it, and updating su binary when it opens.

Did you run the busybox free app?
Sent from my Nexus 7 using xda premium

Metallice said:
Install busybox installer from the market and install/update busybox. See if that fixes your issues. Also try installing SuperSu from the market, opening it, and updating su binary when it opens.
Click to expand...
Click to collapse
I installed busybox installer and when I try to install/update it says it failed. As for SuperSu, it doesn't give me an option to update the su binary.
ScipioWarrior said:
Did you run the busybox free app?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I ran busybox free and it says it's unable to verify whether or not certain utilities needed for this app to run are present and functional on my device. This problem could be caused by a device that is not properly rooted or by superuser settings that are misconfigured

njswift10141980 said:
I'm in need of some help, I'm rooted or so i'm lead to believe, I used wugfresh's method http://forum.xda-developers.com/showthread.php?t=1766475 and everything seemed to work as planed but when i try to use TB or rom toobox it tells me I don't have root. I also tried root check and that comes back telling me I don't have proper root access. Can someone show me some love and help me out.
Thanks.
Click to expand...
Click to collapse
Likely not but thought i'd ask - Did you update to 4.1.1 after initially rooting?
Sent from my Nexus 7 using Tapatalk 2

Did you have the apps that use root before you rooted? I've noticed with some apps (that work with and without root) sometimes dont register that root is installed on your device so perhaps you should try redownloading them from the play store.

animatechnica said:
Likely not but thought i'd ask - Did you update to 4.1.1 after initially rooting?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I installed the update after rooting.
jonnyg1097 said:
Did you have the apps that use root before you rooted? I've noticed with some apps (that work with and without root) sometimes dont register that root is installed on your device so perhaps you should try redownloading them from the play store.
Click to expand...
Click to collapse
I've had the apps for a while on my droid x but I waited until after I rooted to also install them on the N7. I also tried uninstalling them and reinstalling them but they still don't work.

njswift10141980 said:
Yes, I installed the update after rooting.
I've had the apps for a while on my droid x but I waited until after I rooted to also install them on the N7. I also tried uninstalling them and reinstalling them but they still don't work.
Click to expand...
Click to collapse
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.

neilrl79 said:
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
Click to expand...
Click to collapse
He should've used voodoo over the air rootkeeper to back up n save his root. So once you update, you can easily restore rot with one click in that app instead of having to use roottoolkit again.

neilrl79 said:
When you take an update it unroots your device. Re-root it with the tool and you'll be fine.
Click to expand...
Click to collapse
I feel like a moron especially since I froze the updater on my droid x, I'll give it a try when I get home from work, is there anything special I should do or will I just have to click the root button?
demandarin said:
He should've used voodoo over the air rootkeeper to back up n save his root. So once you update, you can easily restore rot with one click in that app instead of having to use roottoolkit again.
Click to expand...
Click to collapse
I will have to look at this app.
I will report back later.

Just rerooted and it looks like everything is working, thanks everybody

No SuperUser prompt in (stock) ICS

I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. After applying "Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB

diggerb said:
I have a Galaxy Tab 10.1 (PT-7500R from Rogers), trying to root on the new official ICS.
I have followed the directions at http://forum.xda-developers.com/showthread.php?t=1239185
CWM installed and works fine. "After applying Samsung_Galaxy_Tab_10.1_root.zip" in CWM, I boot into Android, I see SuperUser in my app menu and can bring up its interface.
However, when I try to launch a su-required function (such as Reboot Recovery in ROM Manager), I don't get a prompt for SU permissions.
I have tried this with both OTA and manual (Odin3) installs of the official ICS from Rogers, from unrooted stock Honeycomb, several times.
I don't encounter this problem with stock Honeycomb... rooting that version appears to work fine.
I have experimented with some community builds, perhaps I have installed an incompatible kernel that needs replacing? I don't know, but any advice would be greatly appreciated.
Regards,
diggerB
Click to expand...
Click to collapse
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Sent from my SAMSUNG-SGH-I747 using xda premium

nakedninja42 said:
Have you tried to see if superuser had an update in the market? I recommend to also make sure the binary is up to date in the superuser app.
Click to expand...
Click to collapse
Thank you for your reply.
I updated to the latest version in Play Store, it shows Binary v2.3.1-ef , update check shows latest version 3.1.1 but when I click Update, it fails on the step "Gaining root access..."
Cheers
diggerB

You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2

Tyxerakias said:
You're not rooted anymore. The superuser app is there but it can't do anything since the su is missing. You have to re-root.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the feedback... but I just went back into CWM and applied the root again, still in exactly the same boat.

Thanks to all, I found a solution in another thread: http://forum.xda-developers.com/showthread.php?p=31179418#post31179418
Superuser just didn't want to work. The SuperSU root method referred by the OP in that thread worked great. All is well again. Until next time of course.

Hi, if you go to "www.galaxytabhacks.com" you will find the solution, there is an upgrade to superuser.

OTA 4.2 & SuperSU v0.98

Has anyone been successful in update their Nexus 7 device with the following configuration:
1. Stock ROM
2. Rooted
3. SuperSU v0.98 (recently updated)
4. Voodoo RootKeeper
5. DPI set to 160, need confirmation but assuming this needs to be reverted back to 213
I have been viewing other posts of successful upgrades but with prior versions of SuperSU, so I was hoping i could find that one person who has the above configuration and was successful in updating.
Thanks,
JBIRD

Apart from 4, the Rootkeeper, that was my setup when I updated from 4.1.2 via the 4.2 OTA (adb sideload).
Worked fine.
Re-rooted using superboot and am happycat ever since.

SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.

rmm200 said:
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
Click to expand...
Click to collapse
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?

jbird92113 said:
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
Click to expand...
Click to collapse
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.

rmm200 said:
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
Click to expand...
Click to collapse
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?

jbird92113 said:
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
Click to expand...
Click to collapse
Yes!

rmm200 said:
Yes!
Click to expand...
Click to collapse
One last thing, I changed my DPI settings to 160, do I need to revert to back to 213...

I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you recommend to be on the safe side that I disable supersu as well prior to the upgrade?
Thanks again...

Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app

Oh, you didn't mention you were on Safestrap. That may bring up some additional issues. And you do need to revert your build.prop to the original. With any luck, you have a build.prop.bak that you can restore. SuperSU hasn't caused me any problems, but I don't use multi-user.

rmm200 said:
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Thanks again for all your help..

jbird92113 said:
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Click to expand...
Click to collapse
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.

If you use MSkips Nexus 7 Toolkit and use option 8 it will not only unlock the boot loader, but root, install busy box, your choice of either cwm or twrp, recommends using the 3.34 bootloader, and recommends using SuperSu 0.98 due to problems with superuser not being updated yet. I can attest to the fact that the 4.13 bootloader causes root issues. At least on my 7. Apparently that isn't so on all 7s.
Sent from my Nexus 7 using xda premium

rmm200 said:
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
Click to expand...
Click to collapse
I am not going to use the multiuser feature as I am the only one who uses the tablet. Will rerooting work on the primary user?

Seems to work fine.
Sent from my Nexus 7 using xda app-developers app

So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium

Gigabitex2 said:
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Only problems I have seen are trying to set up / use a second user while rooted.
Stay away from multi-user and you should be fine.
Note - problems I have reported with SuperSU may just be related to multiuser and root, no matter how you get root.
I have not tried the "superuser" app, so I have no idea if the problems will be the same.

[ROOT][HOW TO] Install Google Play Store

Update 06/28/15
NOTICE: I do not own a kindle anymore so I don't know if this still works. I may still be able to upload a more updated version of the apks though, PM and I'll let you know.
Cheers!
____________________________
NOTICE: You need to be Rooted
The KFHDX 7"(Thor) and KFHDX 8.9"(Apollo) 13/14.3.2.4 and all previous versions CAN be rooted.
I rooted my KFHDX 7"(Thor) version 13.3.2.3.2 with the toolkit.
This is what I did to get the Playstore working with no error pop-ups.
First:
Download and install these two apps onto your Kindle: "Xposed Framework" and "HDXPosed.apk"
Launch the "Xposed" application
Go to framework and click install
Go to modules and enable HDXPosed
Reboot
Also, If the download link for the HDXPosed module goes down. Here is the module's thread. http://forum.xda-developers.com/showthread.php?t=2618158
Then install these apks: https://mega.co.nz/#F!8Q10yAiZ!4GVoGr7FJtXauVI3kvPSMQ
Mirror: https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk

Angel0fDeath said:
This is what I did to get the Playstore working with no error pop-ups.
First:
Then install these apks: https://mega.co.nz/#F!8Q10yAiZ!4GVoGr7FJtXauVI3kvPSMQ
Mirror: https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
After you install the apks open the Playstore and sign in.
Click to expand...
Click to collapse
Confirmed, it works great for me. I have a couple apps that I cannot install from the Play store, but almost everything works just fine. Thanks much!

98HTTR91 said:
Confirmed, it works great for me. I have a couple apps that I cannot install from the Play store, but almost everything works just fine. Thanks much!
Click to expand...
Click to collapse
No problem. Glad I could help [emoji41]
Sent from my rooted Kindle Fire HDX 7"

Gr8 :laugh:
HDXposed also disables the OTA (if I m not wrong).
So can I skip the OTA update block from HDX toolkit 0.94 ?

blade22 said:
Gr8 :laugh:
HDXposed also disables the OTA (if I m not wrong).
So can I skip the OTA update block from HDX toolkit 0.94 ?
Click to expand...
Click to collapse
It's supposed to but I don't think it does. Some users have reported they were updated.
For Example:
jjrizzelcincy said:
it does not work at all for blocking the update,i have rooted over 25 of these things 7's and 8.9's and just about all of them have been updated,,,,since i dont have them in hand i was not able to try the work around ,,,but as far as it blocking the update it does not!
Click to expand...
Click to collapse
I seriously recommend you use the toolkit to block ota updates.
Sent from my rooted Kindle Fire HDX 7"

blade22 said:
Gr8 :laugh:
HDXposed also disables the OTA (if I m not wrong).
So can I skip the OTA update block from HDX toolkit 0.94 ?
Click to expand...
Click to collapse
Someone else can confirm ( @Faznx92 ??), but I don't think HDXposed disables OTA anymore. Your best bet will be the block with the toolkit.

Alright :good:
now there is also a very old method of "Kindle Free" for achieving the same result and many users confirmed it also works till now and safe

I literally tried every way possible but none work
I have tried every way possible I saw on Google to install Google Play Store onto my Kindle Fire HDX 8.9 but none work as I keep getting this message I tried Kindlefree didn't work I tried this one didn't work and I tried Android Cowboy's way and it didn't work please help! imgur. com/1CwVwS9.jpg

Angel0fDeath said:
This is what I did to get the Playstore working with no error pop-ups.
First:
Then install these apks: https://mega.co.nz/#F!8Q10yAiZ!4GVoGr7FJtXauVI3kvPSMQ
Mirror: https://onedrive.live.com/redir?res...4&authkey=!AIVXLFXAOWDeM0Q&ithint=folder,.apk
After you install the apks open the Playstore and sign in.
Also if you want to add a second Google account this is one way I found. (if you know another way please tell me)
1.If you don't have google play music, download and install it.
Once you open it you should be able to see and tap on Add account.
2.If you've already signed in:
Open Google Play Music.
Go to settings.
Tap on Google Account.
Then tap Add account.
Sent from my rooted Kindle Fire HDX 7"
Click to expand...
Click to collapse
Just tried it out and everything is working good so far!!! Thanks again for the guide and all your help man!

FatAmerica said:
I have tried every way possible I saw on Google to install Google Play Store onto my Kindle Fire HDX 8.9 but none work as I keep getting this message I tried Kindlefree didn't work I tried this one didn't work and I tried Android Cowboy's way and it didn't work please help! imgur. com/1CwVwS9.jpg
Click to expand...
Click to collapse
Do you have Xposed framework installed and the HDXPosed module enabled?
Sent from my Nexus 5 using Tapatalk

Angel0fDeath said:
Do you have Xposed framework installed and the HDXPosed module enabled?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Correct I do

FatAmerica said:
Correct I do
Click to expand...
Click to collapse
Did you restore your kindle to factory settings AFTER the failed attempts but BEFORE trying this method again? It's possible some of the file you tried before are causing the error now.

icedtrip said:
Someone else can confirm ( @Faznx92 ??), but I don't think HDXposed disables OTA anymore. Your best bet will be the block with the toolkit.
Click to expand...
Click to collapse
Right. HDXposed doesn't block ota. There was another app that does but I lost track of it. It is somewhere on the threads.

ZMOT7S said:
Did you restore your kindle to factory settings AFTER the failed attempts but BEFORE trying this method again? It's possible some of the file you tried before are causing the error now.
Click to expand...
Click to collapse
Well I heard you can't factory reset after you Rooted otherwise you brick your device as I don't want to Brick it again -_-

The toolkit is an amazing piece of work. When I got my new kindle the other day it came with 14.3.1 so the toolkit got me going in no time and blocked ota. :happy:
Sent from my LG-D800 using XDA Premium 4 mobile app

FatAmerica said:
Well I heard you can't factory reset after you Rooted otherwise you brick your device as I don't want to Brick it again -_-
Click to expand...
Click to collapse
Did you uninstall previous gapps before trying my steps?
Sent from my rooted Kindle Fire HDX 7"

Angel0fDeath said:
Do you have Xposed framework installed and the HDXPosed module enabled?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes

factory reset
FatAmerica said:
Well I heard you can't factory reset after you Rooted otherwise you brick your device as I don't want to Brick it again -_-
Click to expand...
Click to collapse
As far as I know a factory reset on stock firmware with simple root. Will not brick
the device you may lose the superuser app if you did not have it installed two system. But Per my experience you will not brick or lose root. If somebody knows better please chime in .

The only time a factory reset is harmful is if you're already stuck in a boot loop.

Thanks
Worked Awesome for me thanks this is what the HDX was missing:laugh:

No CM13 Root Option? (Solved)

I'm on CM13, I was rooted and everything. I had SuperSU installed also. But upon realizing that I didn't need it because CM13 had a root permission manager built in, I uninstalled it. Upon rebooting there is now no option to root in developer settings except through ADB and I'm no longer rooted. Is there anyway to fix this without reinstalling the OS and starting from scratch?

-WhiteHawk- said:
I'm on CM13, I was rooted and everything. I had SuperSU installed also. But upon realizing that I didn't need it because CM13 had a root permission manager built in, I uninstalled it. Upon rebooting there is now no option to root in developer settings except through ADB and I'm no longer rooted. Is there anyway to fix this without reinstalling the OS and starting from scratch?
Click to expand...
Click to collapse
You are rooted, CM comes prerooted. Did you turn on the cm root manager in settings?
Additionally, SuperSU is much better than cm manager, you really should use it.

ldeveraux said:
You are rooted, CM comes prerooted. Did you turn on the cm root manager in settings?
Additionally, SuperSU is much better than cm manager, you really should use it.
Click to expand...
Click to collapse
I did have CM root manager and root enabled in developer settings, but then the option went away and my apps are telling me I'm not rooted. I only have the option to enable root through ADB, as seen in the attached screenshot.

-WhiteHawk- said:
I did have CM root manager and root enabled in developer settings, but then the option went away and my apps are telling me I'm not rooted. I only have the option to enable root through ADB, as seen in the attached screenshot.
Click to expand...
Click to collapse
1) stop cross posting
2) you have 2 options. Reflash the Rom and hope it fixes whatever you did to bork it. Or install supersu like you should do anyway.

ldeveraux said:
1) stop cross posting
2) you have 2 options. Reflash the Rom and hope it fixes whatever you did to bork it. Or install supersu like you should do anyway.
Click to expand...
Click to collapse
Sorry, I've been desperate.
I'll look to see if there are any new nightlies and flash them or reflash the one I'm on. Reinstalling SuperSU fixed nothing, although it works. A lot of my root apps (ES file explorer, SELinux mode changer) are still telling me I don't have root, although SuperSU granted them root permission.

-WhiteHawk- said:
Sorry, I've been desperate.
I'll look to see if there are any new nightlies and flash them or reflash the one I'm on. Reinstalling SuperSU fixed nothing, although it works. A lot of my root apps (ES file explorer, SELinux mode changer) are still telling me I don't have root, although SuperSU granted them root permission.
Click to expand...
Click to collapse
Did you flash the supersu zip rather than installing through the store? That should work!

ldeveraux said:
Did you flash the supersu zip rather than installing through the store? That should work!
Click to expand...
Click to collapse
Ah okay I'll try that then. I had installed it from the store.

ldeveraux said:
Did you flash the supersu zip rather than installing through the store? That should work!
Click to expand...
Click to collapse
Everything is up and running after taking your advice, thanks! I'll be sure to follow the forum rules better for now on too (sorry) lol

-WhiteHawk- said:
Everything is up and running after taking your advice, thanks! I'll be sure to follow the forum rules better for now on too (sorry) lol
Click to expand...
Click to collapse
Nah, was definitely joking about that glad you got it working though

ldeveraux said:
Nah, was definitely joking about that glad you got it working though
Click to expand...
Click to collapse
Ah okay lol