Related
Ok so I had rooted my D2 a few days ago and had been looking into backup/recovery apps. Now however it seems as if my phone is no longer rooted. Is this possible? I thought I had read another thread where someone else was having this problem but was unable to find it. I tried to open up my superuser app and titanium backup app, but both ended in a failure and asked if my phone was rooted. Thanks in advance for anyone's help with this!
Also, just noticed that my superuser app isn't working correctly. The widget changed from being labeled "superuser" to "superuser permissions". I had assumed that this was after my phone had updated some other applications, however the superuser app won't turn on, it just gives me a black screen. When I tried to update through the market it said "Package file was not signed correctly". I'm unable to find the app on my phone so I can delete and try to download it again fresh. Thanks again for any advice anyone has!
~noob
Yeah. Phones can unroot themselves. This usually happens when the phone updates itself. Don't stress though... just root your phone again.
So, then with the superuser permissions app that I found on my phone...if I were to re-root my D2 with a different method of rooting vs the first way, would I be able to uninstall that superuser permissions app if I wanted? Thanks for such a quick response!
k_minlam01 said:
So, then with the superuser permissions app that I found on my phone...if I were to re-root my D2 with a different method of rooting vs the first way, would I be able to uninstall that superuser permissions app if I wanted? Thanks for such a quick response!
Click to expand...
Click to collapse
What was your first method. I would just use z4root. Also, did you install a custom rom? If so maybe reflash the rom after you are rooted again.
Sent from my ultra fast Liberated Droid 2
I had used the 1-2-3 step for rooting as my husband had suggested that. I have z4root installed now but haven't done anything yet. My husband had suggested I get some back-up apps for my phones system and also one for my apps in case I kill my phone. Will the droid 2 bootstrap back-up/restore my original phone system in case I do mess it up?
Sent from my DROID2 using XDA App
I remember reading about having to unroot your phone from the Froyo update. I have the Z4root but it only has a root button.
1. Is it advisable to unroot for OTA update?
2. Any resources for Z4unroot?
Thank for helppin' a n00b out.
It is correct that you'll need to have your phone unrooted to receive the update. Are you rooted with z4 now? If so you should be able to click on z4 and have the "unroot" option appear. If it doesn't appear I have no idea where you should go. Did you do a nandroid backup as well? !
Sent from my DROIDX using XDA App
Unrooting has never been necessary. You just need to be on the stock rom without any system apps removed.
How about frozen apps in Titanium Backup... need to unfreeze?
Dr, you're saying leaving phone rooted will not stop ota? I don't want update. Have frozen 2.2.1 updater in titanium and some other bloatware as well. I was informed doing all this would stop update.
Sent from my DROIDX using XDA App
Being rooted will change nothing about the update. I can't speak to how Titanium Backup freezes apps, but I know in the past if someone removed/renamed apps in the /system/apps folder the update failed.
You should google/search this site for answer on how to avoid downloading the update if that's what you want.
What needs to happen in order for you to receive the update is that you must be on stock blur rom that came with the phone as well as not have any programs that prevent it from updating IE bootstrapperx, titanium pro, romwork (or w/e its called) etc. A lot of programs used to do Rome like the ones mentioned above have built in code to tell the ota update to basically go **** itself
Sent from my DROIDX using XDA App
PM me i'll hook you up
I didn't have to unroot when I did the 2.2 OTA update. But just before I updated, I did unfreeze all the crapware I froze with Titanium Backup. Didn't have a single issue. Once I was on 2.2, I froze all the crapware again.
i have never un-rooted my phone for any updates. They always pass fine if rooted. Only fail if you have messed with bloatware or have a bootloader installed. You even keep the Super User App, but it just has lost root rights so it will no longer work until you re root the device
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
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.
I need help guys. I'm currently rooted running ParinoiAndroid 3.00 and Franco Kernel #82. I'm trying to download the Good for Enterprise App from the Play Store and install for my work email, but the app won't install becasue of my Root status. Is there a way to hide the root status from this app at all times. I really don't want to unroot my phone.
:fingers-crossed:
Not sure if this will work...
Go to SuperSU -> Settings.
There in Access, give default access as Deny
Then set up the whole Good for Enterprise thing
Then once the setup is done, set default access as Prompt again.
rhoadster91 said:
Not sure if this will work...
Go to SuperSU -> Settings.
There in Access, give default access as Deny
Then set up the whole Good for Enterprise thing
Then once the setup is done, set default access as Prompt again.
Click to expand...
Click to collapse
Thanks for the suggestion, but I gave it a try and it didn't work.
Any other ideas????
Unroot. Install. Re-root. ?
Sent from my Nexus 4 using xda app-developers app
chrisrozon said:
Unroot. Install. Re-root. ?
Click to expand...
Click to collapse
I do not think unrooting 4.2.2 is wise. I heard 4.2.1 rooting techniques do not work for 4.2.2.
Gjohnson7771 said:
Any other ideas????
Click to expand...
Click to collapse
Umm... nothing I can think of right now... If you have a spare device you can unroot that, install it on that device, setup your phone, root it, copy its data from /data/data and then restore it in your Nexus 4 Long shot.
rhoadster91 said:
I do not think unrooting 4.2.2 is wise. I heard 4.2.1 rooting techniques do not work for 4.2.2.
Umm... nothing I can think of right now... If you have a spare device you can unroot that, install it on that device, setup your phone, root it, copy its data from /data/data and then restore it in your Nexus 4 Long shot.
Click to expand...
Click to collapse
Ok, that's not good. I guess I will need to do more research on unrooting 4.2.2.
And no this is my only device. I have a couple of old Iphones but that won't do me any good. Oh and if I was to unroot it and install the software, wouldn't the device be wiped when I re-root it and flash a custom ROM?
Gjohnson7771 said:
Oh and if I was to unroot it and install the software, wouldn't the device be wiped when I re-root it and flash a custom ROM?
Click to expand...
Click to collapse
After re-rooting it, backup the data using Titanium. Then flash custom ROM and restore App + data.
rhoadster91 said:
After re-rooting it, backup the data using Titanium. Then flash custom ROM and restore App + data.
Click to expand...
Click to collapse
I'm not sure if you would know this answer or not, but in an app like Good Enterprise does it normally just search for root status upon initial install or does it look for the root status periodically.
Also, I had plans to unroot using the SuperSU "Full unroot" option or even the Nexus 4 tool kit. Are either one of these methods the unroot techniques you were referring too? I really don't want to brick my device if its unwise to unroot.
bump.......
Gjohnson7771 said:
I'm not sure if you would know this answer or not, but in an app like Good Enterprise does it normally just search for root status upon initial install or does it look for the root status periodically.
Also, I had plans to unroot using the SuperSU "Full unroot" option or even the Nexus 4 tool kit. Are either one of these methods the unroot techniques you were referring too? I really don't want to brick my device if its unwise to unroot.
Click to expand...
Click to collapse
I would have tried to check it myself first before suggesting you the solution (I had even downloaded the app) but turns out setting up Good Enterprise requires more than just downloading and installing it. I am not sure if it checks the root status periodically but in this case looks like the only option we have is to hope that it checks only during initiation. However, if the app is any good, I think it will check root status periodically to maintain security (because a lot of app information is compromised on a rooted phone)
Also, I do not think you will brick your phone if u attempt to root 4.2.2. Simply rebooting it in fastboot mode will give you option to revert to stock even in the worst situations. Still, cannot rule out the risk.
Anyway, a simple Google Search revealed this which could be a potential solution
Well thanks for all the info. I'll see what I can figure out.
Un rooting is quite simple , nothing to worry about!
By the way, Good permissions can be set by your administrator. They have the option to allow root, to check every time, Or to check once. It all depends on how your company configures it.
Sent from my Nexus 4 using xda app-developers app
Well, I was able to use nexus 4 toolkit to uproot and relock the boot loader. The app install fine after that and is working properly.
Thanks for the replies. For some reason I was thinking I would have to return the phone back to stock to uproot it, I'm glad I was able to keep my custom ROM and kernel. 1 more question, was re-locking the boot loader necessary or could I have kept it unlocked?
voodoo ota root keeper has a temporary unroot option, grab it from the playstore , much easier than unrooting your phone, also root survives an ota from google. You probably could have left the bootloader unlocked.
easy way ??
An easy way to hide root is renaming the superuser app/apps in the below location.
/system/app
This method did the charm for me for few apps. But the disadvantage is, it will hide root for all apps..
Workaround
http://forum.xda-developers.com/showthread.php?t=2040163 - thread talking about workaround for GFE