OTA 4.2 & SuperSU v0.98 - Nexus 7 Q&A, Help & Troubleshooting

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.

Related

Help new update wont install

I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!
Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......
I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714
oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk
Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...
cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.
aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.
You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App
I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.
Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk

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

Lost root after 4.2 update. Need help!

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

Can I hide my Root status from an app permanently?

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

[Q] How to temporary unroot my phone

Hi,
I'm rooted running stock.
My bank's app requires that the phone will be unrooted (it won't let me sign in). Is there a way to make the app think that I don't have root access, or is there a way to temporary unroot my phone, for when I'm using the app?
I've tried to disable the root from SuperSU, to use RootKeeper OTA, and this thread instructions, and some more market apps, but none of these worked. Even titanium backup didn't believe me that I'm not-rooted
Can you guys help me out?
Thanks
Alkonost said:
Hi,
I'm rooted running stock.
My bank's app requires that the phone will be unrooted (it won't let me sign in). Is there a way to make the app think that I don't have root access, or is there a way to temporary unroot my phone, for when I'm using the app?
I've tried to disable the root from SuperSU, to use RootKeeper OTA, and this thread instructions, and some more market apps, but none of these worked. Even titanium backup didn't believe me that I'm not-rooted
Can you guys help me out?
Thanks
Click to expand...
Click to collapse
Most apps just look if you have a superuser.apk in /system/app/. Try to put "com." at the beginning of the name. So you don't have "superuser.apk" but "com.superuser.apk". I already done this and i have root and the app thinks im unrooted.
Thanks a lot! This + Rootkeeper made the app think I'm not rooted
Sent from my Nexus 4 using xda app-developers app

Categories

Resources