Database Users

[Q] OTA update from 4.2

It has been a long time since I have ever done an OTA update.
On most devices I'm typically running a custom ROM and do updates by flashing a new zip from a custom recovery.
I am currently running 4.2 that I got from here:
https://developers.google.com/android/nexus/images#nakasi
I flashed a custom recovery, flashed SuperSU via recovery, and installed BusyBox from the Play Store.
Now my Nexus 7 says it has an update.
Questions:
Will I be able to use OTA Rootkeeper and do this update?
Does OTA Rootkeeper also keep busybox?
Will I have to re-install my programs?
If there is an update to 4.2 why is 4.2 the latest thing I see on the google website I linked to above?

Will I be able to use OTA Rootkeeper and do this update?
Click to expand...
Click to collapse
Root keeper should work fine since of is only a minor update.
Does OTA Rootkeeper also keep busybox?
Click to expand...
Click to collapse
Busybox won't be removed with an OTA update.
Will I have to re-install my programs?
Click to expand...
Click to collapse
No, all your programs will still be there after the upgrade.
[/QUOTIf there is an update to 4.2 why is 4.2 the latest thing I see on the google website I linked to above?
Click to expand...
Click to collapse
Google hasn't built the new factory images for 4.2.1 yet.

EvanA said:
Busybox won't be removed with an OTA update.
Click to expand...
Click to collapse
How is it that su gets removed during an OTA but not but not the busybox executables?
How are the busybox executables different?
Does an OTA explicitly go after su?

I have a notification for an android update as well. I'm rooted and unlocked, running stock. So, I just want to install an app from the market called root keeper before installing the update and all is well?

OTA rootkeeper is the app.
It worked for me, and app usage is fairly simple.
The SU app doesn't get removed, it's still there, it just doesn't have access, but OTA rootkeeper restores it.
I updated yesterday I think, the update mostly fixes that December issue, nothing major, it's a <1,5MB update.

issak42 said:
The SU app doesn't get removed, it's still there, it just doesn't have access, but OTA rootkeeper restores it.
Click to expand...
Click to collapse
Technically, what is going on here under the hood?
What do you mean by "doesn't have access"?
I don't fully understand how root works on Android between the binary su and the SuperSU Android app.
Does the OTA mess with setuid bits or something?
Does it lose access during the "Android is upgrading... Optimizing Apps" after it reboots?
I will do the update using OTA rootkeeper, right now I'm just trying to gain a higher understanding of what is going on.
Edit: Update successful. I have TWRP installed and this is what it looked like. Gave me a scare for a second.
http://i.imgur.com/gAcnt.jpg

FunkyELF said:
Technically, what is going on here under the hood?
What do you mean by "doesn't have access"?
I don't fully understand how root works on Android between the binary su and the SuperSU Android app.
Does the OTA mess with setuid bits or something?
Does it lose access during the "Android is upgrading... Optimizing Apps" after it reboots?
I will do the update using OTA rootkeeper, right now I'm just trying to gain a higher understanding of what is going on.
Edit: Update successful. I have TWRP installed and this is what it looked like. Gave me a scare for a second.
http://i.imgur.com/gAcnt.jpg
Click to expand...
Click to collapse
I honestly don't know what is it that OTA rootkeeper does, I had doubts too. I'm not a developer of said app, so the questions you have should really be addressed towards the dev.
I know the feeling, I have TWRP too, and it gave me a mini heart attack
I'm glad everything worked out!

issak42 said:
I honestly don't know what is it that OTA rootkeeper does, I had doubts too. I'm not a developer of said app, so the questions you have should really be addressed towards the dev.
I know the feeling, I have TWRP too, and it gave me a mini heart attack
I'm glad everything worked out!
Click to expand...
Click to collapse
OTA rootkeeper makes a backup of the such binary and restores it after the upgrade. It works quite well, actually.
Sent from my Nexus 7 w/ PA and m-kernel

EvanA said:
OTA rootkeeper makes a backup of the such binary and restores it after the upgrade. It works quite well, actually.
Sent from my Nexus 7 w/ PA and m-kernel
Click to expand...
Click to collapse
It does work well indeed. So basically, root access isn't lost, but OTA update removes the su apk, and rootkeeper restores it?
I don't understand how it can restore root without root access

issak42 said:
It does work well indeed. So basically, root access isn't lost, but OTA update removes the su apk, and rootkeeper restores it?
I don't understand how it can restore root without root access
Click to expand...
Click to collapse
I'm running a rooted stock nexus with twrp. I screwed up with the first 4.2 OTA and had to reroot with fastboot, supersu, etc. When this new one came up last night I installed OTA RootKeeper from the playstore and backed up su with it. I ran the update this morning and had root back in seconds with rootkeeper. Works well, just as described above. The googling involved in my last screwup saved some headaches this time.
Thanks to ALL on this forum.

issak42 said:
It does work well indeed. So basically, root access isn't lost, but OTA update removes the su apk, and rootkeeper restores it?
I don't understand how it can restore root without root access
Click to expand...
Click to collapse
It doesn't need root access to restore root because BusyBox remains installed. Basically what the app does to restore su is remount the system as read and write then use BusyBox to copy the su binary back to where it should be.
Sent from my Nexus 7 w/ PA and m-kernel

[Q] What happens to root when doing OTA update?

I recently read that there is going to be a 4.2.2 update to the Nexus devices.
I was wondering what will happen to my rooted 4.2.1 phone? will it update properly? will I need to root again after the update?

you normally need to re-root after ota unless you have rootkeeper

I add an additional question..
If I have a flashed a new kernel and twrp, do I have to restore to stock and before I can update?

You need stock images for ota so yes, you have to flash stock kernel, recovery and if the kernel meddled with the system files, you need to flash stock system image as well
Sent from my Nexus 4 using Tapatalk 2

From 4.2->4.2.1 clockworkmod actually intervened on reboot and did what it had to (with prompts) to maintain recovery and root, first time that has happened for me and I was pleasantly surprised. I was stock + unlock + root, no kernel or other system changes.
I have AOKP now though so I guess I'll just wait for goo to notify me.

thephantom said:
you normally need to re-root after ota unless you have rootkeeper
Click to expand...
Click to collapse
The application doesn't support original Superuser and not SuperSU for a very simple reason. The same feature OTA protection feature is already present in SuperSU.
This is about Rootkeeper. I have stock, rooted and SuperSU. Does this mean that I don't need Rootkeeper and if I get the OTA update, I keep root?

Guzanni said:
The application doesn't support original Superuser and not SuperSU for a very simple reason. The same feature OTA protection feature is already present in SuperSU.
This is about Rootkeeper. I have stock, rooted and SuperSU. Does this mean that I don't need Rootkeeper and if I get the OTA update, I keep root?
Click to expand...
Click to collapse
On my GNex I have supersu. Just installed 4.2.2 update. I had to reroot by flashing latest supersu thru cwm. The update still over wrote the su file in the xbin folder
Flowed and Tapped from my Nexus

thephantom said:
On my GNex I have supersu. Just installed 4.2.2 update. I had to reroot by flashing latest supersu thru cwm. The update still over wrote the su file in the xbin folder
Flowed and Tapped from my Nexus
Click to expand...
Click to collapse
Thanks for your reply. So this means that I still have to use Rootkeeper.. or won't it work? Do I have to do it like you did?

Guzanni said:
Thanks for your reply. So this means that I still have to use Rootkeeper.. or won't it work? Do I have to do it like you did?
Click to expand...
Click to collapse
Well, as I didn't install Rootkeeper now, I can't say for sure. Before I was able to preserve it. You can simply root again. Doesn't take more than a minute
Flowed and Tapped from my Nexus

[Q] How to use SuperSU?

Hi,
I got an update on my LG G2 D802 and i have ROOT, i downloaded SuperSU because someone told me that i can update my device with it, but i dont know how.
Can someone explain me how to use it? what should i do in the SuperSU to update my device?
Thank you.

Uh...i don't think supersu can update your device. All it does is handle root.
Gesendet von meinem LG-d802 mit Tapatalk

ckyy said:
Uh...i don't think supersu can update your device. All it does is handle root.
Gesendet von meinem LG-d802 mit Tapatalk
Click to expand...
Click to collapse
But i saw that it have OTA Survival in the Settings.
Are you sure that i cant to update with it?
On my previous theard i asked if i can update, and someone told me that he updated his G2 with the SuperSU, but i dont know how to do this too..

itaylubo2 said:
But i saw that it have OTA Survival in the Settings.
Are you sure that i cant to update with it?
On my previous theard i asked if i can update, and someone told me that he updated his G2 with the SuperSU, but i dont know how to do this too..
Click to expand...
Click to collapse
OTA survival means that when your carrier sends out an OTA update for your device, you should still have root afterwards. Normally without OTA survival you will lose root after updating. SuperSU has nothing to do with updates, it is simply a firewall between apps and the root of your device. :good:

If you have OTA survival turned on in SuperSU, AND you have stock recovery, then theoretically, you can do the OTA update and still have root when it's finished. But it isn't 100% successful.

Also OP...
http://forum.xda-developers.com/showthread.php?t=2443934

souleman said:
If you have OTA survival turned on in SuperSU, AND you have stock recovery, then theoretically, you can do the OTA update and still have root when it's finished. But it isn't 100% successful.
Click to expand...
Click to collapse
I have stock recovery, so i should turn on the OTA Survival in the SuperSU and to start to update?
I saw in the settings of the SuperUser that it have also OTA Survival, should i turn it on too?
Thank you.

DO NOT DO OTA'S IF YOU ROOTED. Period.

khaytsus said:
DO NOT DO OTA'S IF YOU ROOTED. Period.
Click to expand...
Click to collapse
I received an ota last night (whilst very drunk) . I have a rooted but otherwise completely stock rom with stock recovery and the ota installed without a problem and I remained rooted even though I hadn't set my superSU to maintain root. My system updated from 10a to 10f.
It would appear that an ota will install with root as long as you have stock recovery and have not made changes to the system partition. (apart from the su binary of course.)

bobsie41 said:
I received an ota last night (whilst very drunk) . I have a rooted but otherwise completely stock rom with stock recovery and the ota installed without a problem and I remained rooted even though I hadn't set my superSU to maintain root. My system updated from 10a to 10f.
It would appear that an ota will install with root as long as you have stock recovery and have not made changes to the system partition. (apart from the su binary of course.)
Click to expand...
Click to collapse
Yes, but I like to keep things simple for people.
Recovery is what will get you, or a modified ROM. But.. Ah, it doesn't matter, people will do it anyway.

itaylubo2 said:
I have stock recovery, so i should turn on the OTA Survival in the SuperSU and to start to update?
I saw in the settings of the SuperUser that it have also OTA Survival, should i turn it on too?
Thank you.
Click to expand...
Click to collapse
You shouldn't have SuperSU and SuperUser both on the phone. Remove one of them (probably SuperUser as it doesn't play well with some things).
It is recommended not to do an OTA if you are rooted. If you wait a few days, someone will have a flashable version of the OTA on here.
Having a modified stock rom very rarely causes any issues. It can, but it doesn't very often. 99% of the time, it's because someone is running a different recovery, and still blames it on the ROM. But unless your ready to flash it back to how it was when you opened the box, just wait a couple days.

souleman said:
You shouldn't have SuperSU and SuperUser both on the phone. Remove one of them (probably SuperUser as it doesn't play well with some things).
It is recommended not to do an OTA if you are rooted. If you wait a few days, someone will have a flashable version of the OTA on here.
Having a modified stock rom very rarely causes any issues. It can, but it doesn't very often. 99% of the time, it's because someone is running a different recovery, and still blames it on the ROM. But unless your ready to flash it back to how it was when you opened the box, just wait a couple days.
Click to expand...
Click to collapse
But i have stock recovery and stock ROM, it is matter?
I realy dont know what to do when the Kitkat 4.4 will comes...

itaylubo2 said:
But i have stock recovery and stock ROM, it is matter?
I realy dont know what to do when the Kitkat 4.4 will comes...
Click to expand...
Click to collapse
To be safe you could always unroot your phone before updating since everything is stock you won't be losing much and you won't be taking any unnecessary chances. Plus the root might not stick with such a big update even with root survival so you might have to reroot it again after the update anyways.
This is pretty much the same thing everyone had already said, I don't think anyone here would tell you it's worth taking the risk -even if it's just a slight risk since you don't have a custom recovery installed- that will only be saving you the few minutes it'll take to reroot your phone.
Sent from Sprint LG G2

kcerica said:
To be safe you could always unroot your phone before updating since everything is stock you won't be losing much and you won't be taking any unnecessary chances. Plus the root might not stick with such a big update even with root survival so you might have to reroot it again after the update anyways.
This is pretty much the same thing everyone had already said, I don't think anyone here would tell you it's worth taking the risk -even if it's just a slight risk since you don't have a custom recovery installed- that will only be saving you the few minutes it'll take to reroot your phone.
Sent from Sprint LG G2
Click to expand...
Click to collapse
How i Unroot my phone? just doing Factory Reset?

There should be an unroot option in the supersu settings
Sent from Sprint LG G2

itaylubo2 said:
How i Unroot my phone? just doing Factory Reset?
Click to expand...
Click to collapse
Uninstall SuperUser, then in SuperSu there is an option to unroot the phone.

souleman said:
Uninstall SuperUser, then in SuperSu there is an option to unroot the phone.
Click to expand...
Click to collapse
I downloaded SuperSU, and after i delete it.
and i did Reboot, and the Superuser dissapeard, but i still have ROOT, i can use Freedom, Market Unlocker and Auto Hide Soft Keys.
Now i downloaded SuperSU again, and i saw in the "Description" that the SuperUser should be removed when i download the SuperSU.
If i'll do Full Unroot from the SuperSU, it will work on LG G2 D802 with stock ROM&Recovery?
Thank you very much !!!

itaylubo2 said:
I downloaded SuperSU, and after i delete it.
and i did Reboot, and the Superuser dissapeard, but i still have ROOT, i can use Freedom, Market Unlocker and Auto Hide Soft Keys.
Now i downloaded SuperSU again, and i saw in the "Description" that the SuperUser should be removed when i download the SuperSU.
If i'll do Full Unroot from the SuperSU, it will work on LG G2 D802 with stock ROM&Recovery?
Thank you very much !!!
Click to expand...
Click to collapse
Yup. Full Unroot in SuperSu will delete the files from the /system partition that give you access to root.

souleman said:
Yup. Full Unroot in SuperSu will delete the files from the /system partition that give you access to root.
Click to expand...
Click to collapse
It will work for 100%? In the Root Exporer, i search in the /system/bin for the "su" and i didnt found it, also i didnt found the SuperUser.apk in the /system/app, i can find only in the /system/xbin the "su" file.
It should be like this? because i saw some videos on Glalaxy Note 2 that he have all except the su file in the /system/xbin..

itaylubo2 said:
It will work for 100%? In the Root Exporer, i search in the /system/bin for the "su" and i didnt found it, also i didnt found the SuperUser.apk in the /system/app, i can find only in the /system/xbin the "su" file.
It should be like this? because i saw some videos on Glalaxy Note 2 that he have all except the su file in the /system/xbin..
Click to expand...
Click to collapse
There shouldn't be an su files after unroot. Is either superuser.apk or supersu.apk in either /system/app or /data/app?

[Q] Superuser and SuperSU conflicting

Hello all,
I've been running into some issues with Superuser and SuperSU while running the CM11 nightlies. I restore all of my apps using the built-in Superuser from CM11, and then I go into SuperSU to update the binary (I want to use SuperSU as my main Root app) and update the binary successfully. All is well, but then it seems that Superuser will then take over as my main root app and then I need to continuously update the SuperSU binary.
Does anybody have any idea why SuperSU is not sticking as my root app, or how to "disable" Superuser?

skadude66 said:
Hello all,
I've been running into some issues with Superuser and SuperSU while running the CM11 nightlies. I restore all of my apps using the built-in Superuser from CM11, and then I go into SuperSU to update the binary (I want to use SuperSU as my main Root app) and update the binary successfully. All is well, but then it seems that Superuser will then take over as my main root app and then I need to continuously update the SuperSU binary.
Does anybody have any idea why SuperSU is not sticking as my root app, or how to "disable" Superuser?
Click to expand...
Click to collapse
i think you can only have one or the other not both running

jaythenut said:
i think you can only have one or the other not both running
Click to expand...
Click to collapse
I can't find a way to disable Superuser without completing removing Root Access for my phone.. :/ Do you know how to disable Superuser?

skadude66 said:
I can't find a way to disable Superuser without completing removing Root Access for my phone.. :/ Do you know how to disable Superuser?
Click to expand...
Click to collapse
on cm dont think you can ask on your rom thread

jaythenut said:
on cm dont think you can ask on your rom thread
Click to expand...
Click to collapse
Thanks, I'll try that out!

root and superSU

I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)

BallaratBloke81 said:
I was updating superSU on my note 3 after root. I tried to use game killer, only to get the message that root wasn't available. I loaded up superSU and was told that the binary couldn't be found... I downloaded a root checker and it said that root access was there... So I unrooted and re rooted. Same deal.
I'm not sure how to fix the issue.
Can anyone please help
(SM-N9005)
Click to expand...
Click to collapse
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005

thahim said:
Somethings wrong with your su I think. Have to given privillages to game killer in su?
Sent from Galaxy Note 3 SM-N9005
Click to expand...
Click to collapse
I have given it privileges. But when I open supersu says there is something wrong with su binary.

BallaratBloke81 said:
I have given it privileges. But when I open supersu says there is something wrong with su binary.
Click to expand...
Click to collapse
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....

ultramag69 said:
Have you deleted then given Super SU privileges back? I find installing a new rom can sometimes screw with them....
Click to expand...
Click to collapse
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)

BallaratBloke81 said:
When I first got the phone it had a rom full of provider bloatware. I flashed another stock Roma to get rid of it. Then I flashed xnote and decided OT wasn't for me, so I went back to stock (without bloats)
Click to expand...
Click to collapse
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...

ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
Yes hello, can someone please upload the note 3 4.3 touchwiz apk, i accidentally deleted mine, so please.

ultramag69 said:
Delete the apps from SU then when prompted give them permission again - like normal you will need to re-open them again and get the "Grant root access" prompt from SU...This may work, has for me everytime...
Only other thing I would do if this didn't work would be re-stock and start from scratch...
Click to expand...
Click to collapse
I have already reflashed stock back to my phone, re rooted and the problem still exsists
Currently I'm on stock again (downloaded from sammobile)
Every time I open superSU, it tells me there is a problem with the SU BINARY (when I was rooted. I'm not trying to use super SU unrooted lol)

Just rooted again and its still the same...

Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.

antique_sonic said:
Reflash stock, full wipe from stock recovery, reroot.
Or u have done a full wipe from stock recovery after flash stock firmware?
Sent from N9005, somewhere on this earth.
Click to expand...
Click to collapse
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?

BallaratBloke81 said:
Yeah, done all of that. Is there a way to manually wipe the SU binary and reinstall? The root checker app says root access is allowed
Is there another way to see if it's the SU binary or game killer having issues?
Click to expand...
Click to collapse
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked

Rosli59564 said:
If you attempts to fix root access denied on game killer then it won't work. Gamekiller/gamecih/gameguardian doesn't work with android 4.3 and above.
I however tried gamecih with cm based rom last week & it worked
Click to expand...
Click to collapse
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?

BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?

gee2012 said:
Its not a superSU issue, guess the dev needs to update the gamekiller app. Do you have root privileges with other root apps?
Click to expand...
Click to collapse
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU

BallaratBloke81 said:
Not as of yet. The photo of the warning I posted, comes up when I open SuperSU
Click to expand...
Click to collapse
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.

gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
I can't even get into the app to unroot

BallaratBloke81 said:
OK, so you're saying those kind of apps will no longer work?
What about the SU binary issue?
Click to expand...
Click to collapse
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot

gee2012 said:
Try unrooting superSU from the app itself and reflash the latest (1.94 i think) superSU.zip in recovery or with Flashify (if compatible ,Playstore) flash CF Root in downloadmode. Hope that helps.
Click to expand...
Click to collapse
ES explorer can't get root access either.
Should I flash superSU.zip straight over the top using recovery? Or is that not a good idea?

Rosli59564 said:
Your SU binary got issue but yes even you solve it those apps won't work.
Try uninstall it from playstore. There is also flashable supersu
http://download.chainfire.eu/204 but I never use it either or maybe reroot
Click to expand...
Click to collapse
I have unrooted (flashing stock rom using recovery) and rerooted (using CF auto root... Or whatever it's called) many times.