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
Related
Edit : just checked. My phone is running the newest updated but im gonna try to unroot and reroot one more time even though I already tried and it could not unroot.
So I went to install the new update via stock recovery and it seemed to work. I go check system settings and its still showing 2.3.2 and not the newest one. I go to try and root and it says everything works and my phone is rooted. Thing is there is no super user app that appeared on my last droid 2. What's the issue?
Sent from my DROID2 using XDA App
Try it again and use the 1 click root for 2.3.20 from here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html
komputerfreek said:
Edit : just checked. My phone is running the newest updated but im gonna try to unroot and reroot one more time even though I already tried and it could not unroot.
So I went to install the new update via stock recovery and it seemed to work. I go check system settings and its still showing 2.3.2 and not the newest one. I go to try and root and it says everything works and my phone is rooted. Thing is there is no super user app that appeared on my last droid 2. What's the issue?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It might be that you just lost the app and just need to get it off the Market.
JDunc said:
It might be that you just lost the app and just need to get it off the Market.
Click to expand...
Click to collapse
Yeah, I saw it was rooted and just went to market and got Superuser app and installed, I have root. I don't know why it did not show the superuser app even thought it said the apk was transfered.
Mine did the same. After I rooted using the one click method, it said it was a sucess. Tried to use Root Explorer, and it said failed getting superuser permission. Checke my SD card, and there was no Superuser.apk there. I copied it to the SD card from the one click directory, and it was sucessful. When trying to use Titanium Backup, had trouble with Busybox. Titanium downloaded a new Busybox, and all is now well.
Sent from my DROID2 using XDA App
Latest update is out in the wild: 3.8.7.XT610. Info here
apparently this is a 43.8MB file
updated Blur
not Gingerbread
Wonder if it supports root??
jhalsey205 said:
Latest update is out in the wild: 3.8.7.XT610. Info here
Wonder if it supports root??
Click to expand...
Click to collapse
I saw a post by Android wizard extraordinaire, CellZealot, over at MyDroidForums, who claims :
"... it supports root and is an excellent build. It also supports using the band unlock and GSM performance is far superior to the previous radio firmware. Overall this build is incredibly stable and without question the best build yet for this phone."
That's good enough for me.
Has anyone received this OTA yet? Nothing yet for my two in NY (one rooted, one not).
Sent from my DROID PRO using Tapatalk
Does this update require that I unroot my phone prior to it?
Could any person who has received the update upload it somewhere, please? I cannot wait to update my phone and root it again. I have tried to update it but it keeps telling me I have the latest software version.
Scanned the net and no one has posted the update...hopefully someone here will soon
nottin in new jersey checked on moto droid pro system update whats up with this enyone got this update runnin thankssss
There was a renewal. Loading ...
:-(
Was rooted. Installed OTA update without problems. Then applications like Titanium Backup can not longer get root privileges. Ran Z4Root to Permanent Root again, it crashes and leaves phone unstable, most of the time freezing a few seconds later and I have to remove battery :-(
fpont1 said:
Was rooted. Installed OTA update without problems. Then applications like Titanium Backup can not longer get root privileges. Ran Z4Root to Permanent Root again, it crashes and leaves phone unstable, most of the time freezing a few seconds later and I have to remove battery :-(
Click to expand...
Click to collapse
Blarg, don't like the sound of that. I'm nit sure that my wife uses any root apps but there is just something wrong with an android phone that does not have root.
I used SuperOneClick 1.7 to get root again after apply this update.
Sent from my DROID PRO using XDA App
raphael888 said:
I used SuperOneClick 1.7 to get root again after apply this update.
Sent from my DROID PRO using XDA App
Click to expand...
Click to collapse
Thanks, will try it myself then...
raphael888 said:
I used SuperOneClick 1.7 to get root again after apply this update.
Click to expand...
Click to collapse
Thanks very much for the tip... worked a treat!
Guys pleaaaaaaaaaaase, can someone upload the update file off his SD card?
received the update and rerooted again
Received the update and was able to root using the aroot method, z4root will not work .
Download aRoot!
rafeee2 said:
Guys pleaaaaaaaaaaase, can someone upload the update file off his SD card?
Click to expand...
Click to collapse
I second that!! Bloody takes them ages this time ... wonder why the holdup with some devices?? Its not like theres a million of Droid Pros out there ...
OK, so I can also root with SuperOneClick 1.7 after the update, but the apps like Titanium still can't get root from the SuperUser app. adb shell su also gets Permission denied (after reboot). Any hints?
Edit: problems solved by using aRoot. My conclusion: run aRoot post-update, not z4root nor SuperOneClick.
I lost root after the update and tried Z4Root with no results. SuperOneClick worked after I tried both root methods and rebooted the phone.
I am using AntTek App Manager to remove bloat without any issue. The phone seems more responsive and I have not had any random reboot until now.
Yep - aroot after the update worked. Re-froze the junk via Titanium and my Pro is running well.
For those like me who didn't know how to use aRoot:
Quoted from designgears
http://forum.xda-developers.com/showthread.php?t=981866
http://ponack.net/designgears/atrix/aRoot/
"How to use:
note: xp users, you will get an error about the TIMEOUT function, ignore it.
Enable USB Debugging on your phone (settings > applications > development > enable USB debugging)
Plug your phone into your computer
Extract aRoot.7z
Run aRoot.bat (run unRoot.bat to unroot)"
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.
Hi guys, I just updated my N7 to 4.2 and I lost root during the process. I made a su backup with Voodoo OTA rootkeeper before I did the install. After the install was complete, went back into voodoo to restore root, rebooted, and did a root check using 3 different apps. Voodoo shows my device rooted and root checker and titanium backup cannot find my root access. Is there something I did wrong, and is there any way to restore root access without a fresh wipe. Thanks in advanced!!!
Try uninstalling your root App and then reinstalling it. You also might want to wipe cache and data for your root App in Apps under Settings. Do this before uninstalling.
If that doesn't work push root to your device using one of the many methods available.
Sent from my Nexus 7 using xda premium
ezas said:
Try uninstalling your root App and then reinstalling it. You also might want to wipe cache and data for your root App in Apps under Settings. Do this before uninstalling.
If that doesn't work push root to your device using one of the many methods available.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tried that with no luck. I am trying Wug's toolkit right now, but android 4.2 doesn't show up under the model list.
Need to push the superuser app via fastboot. Either adb or use wugs toolkit.
Sent from my Nexus 7 using Tapatalk 2
Testingchip said:
Need to push the superuser app via fastboot. Either adb or use wugs toolkit.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Wugs worked perfectly. THANKS!! For anyone who is having the same problem, I used wugs toolkit, and I chose Nexus 7 "any build type" under the model type.
Glad you got it. I did the update at work and had the same problem till I got home to the pc.
Sent from my Galaxy Nexus using Tapatalk 2
silentbeatz said:
Wugs worked perfectly. THANKS!! For anyone who is having the same problem, I used wugs toolkit, and I chose Nexus 7 "any build type" under the model type.
Click to expand...
Click to collapse
I hesitate asking thjis but being greener than grass I need you if you would please explain in very noob terms how to push superuser in Wugs. I use the tool kit and was sucsefully rooted in 4.1.2 but the "upgrade" to 4.2 has brought me back to square one and having spent the money on apps like titanium backup I would like to one again use them. Thanks and sorry to be so needy but I'm trying.
patience1 said:
I hesitate asking thjis but being greener than grass I need you if you would please explain in very noob terms how to push superuser in Wugs. I use the tool kit and was sucsefully rooted in 4.1.2 but the "upgrade" to 4.2 has brought me back to square one and having spent the money on apps like titanium backup I would like to one again use them. Thanks and sorry to be so needy but I'm trying.
Click to expand...
Click to collapse
I ran into same problem, if you use Wug Toolkit, make sure you set to "android Anybuild". this Toolkit is not yet updated for 4.2.
There is another Nexus Toolkit by Mark Skippen which was updated to 4.2, however you need to donate to get the latest version. It works well for me
It's woth the donation of Pounds 5 or $8++ something
Good Luck
dominicvn said:
I ran into same problem, if you use Wug Toolkit, make sure you set to "android Anybuild". this Toolkit is not yet updated for 4.2.
There is another Nexus Toolkit by Mark Skippen which was updated to 4.2, however you need to donate to get the latest version. It works well for me
It's woth the donation of Pounds 5 or $8++ something
Good Luck
Click to expand...
Click to collapse
All fine and dandy and I dont mind spending the money but if I use Wugs do i just plug in to the computer open Wugs choose any build and then hit root? TIA and thanks for responding. Like I said NOOB
silentbeatz said:
Hi guys, I just updated my N7 to 4.2 and I lost root during the process. I made a su backup with Voodoo OTA rootkeeper before I did the install. After the install was complete, went back into voodoo to restore root, rebooted, and did a root check using 3 different apps. Voodoo shows my device rooted and root checker and titanium backup cannot find my root access. Is there something I did wrong, and is there any way to restore root access without a fresh wipe. Thanks in advanced!!!
Click to expand...
Click to collapse
Hi did you by any change have SuperSU v.0.98 installed prior to the upgrade with survival mode enabled?
Thanks,
JBIRD
I rooted and now cant access the google app store and my weatherbug elite seems to not be loading. What can I do?
douggiephresh said:
I rooted and now cant access the google app store and my weatherbug elite seems to not be loading. What can I do?
Click to expand...
Click to collapse
Please link to the root guide you followed. After you rooted did you do anything else to the phone? You can try downloading the .apk file for the google play store. There are guides online to install .apk files manually.
http://www.androidpolice.com/2013/04/25/download-latest-google-play-store-4-0-27/
I used the motochopper method. I have since installed titanium backup pro but I had this problem before installing that.
douggiephresh said:
I used the motochopper method. I have since installed titanium backup pro but I had this problem before installing that.
Click to expand...
Click to collapse
You may want to try restoring to factory with Kies and trying again.
Having already rooted wont effect a factory reset? Have you rooted your S4 using the same method?
I am actually restoring my rooted phone with Kies right now. I can confirm after its done that there weren't any issues. There is a disclaimer in Kies saying there may be issues if your phone is rooted.
Where did you find that option in kies?
douggiephresh said:
Where did you find that option in kies?
Click to expand...
Click to collapse
With your phone plugged in go to Tools > Upgrade firmware
And mine just finished successfully.
Remember you can delete busybox and su in your system directory to unroot your phone before you system restore in Kies.
Relys said:
Remember you can delete busybox and su in your system directory to unroot your phone before you system restore in Kies.
Click to expand...
Click to collapse
Thanks for the tip, didn't know that.
RandomHandle said:
Thanks for the tip, didn't know that.
Click to expand...
Click to collapse
Here's the source:
http://forum.xda-developers.com/showthread.php?t=2257058
I personally testing it and it works. The method to return the status from "Custom" to "Official" while keeping root was very nice.