Hi,
I was root and made the update to 4.1.57
I know theres no root solution for now for the 4.1.57 update. So, is any way to delete the SuperUser icon from the drawer
If you temp unroot, to watch Amazon Video, then restore root do you have to load apps and such all over again?.
No you don't.
Sorry if this has already been mentioned.
I am running stock ics xxlpq and skygo is working fine for me.
The Rom which i am using is stock, flashed with odin.
Here is how i got it working....
[*]Flash cf-root with odin.
[*]download buildprop editor.
[*]Create a backup of buildprop.
[*]Edit buildprop and change root.build.version.release to 2.3.7
[*]Flash with stock kernel
[*]Run superuser and install such binaries
[*]Download Voodoo OAT root keeper
[*]Run OAT root keeper and select temp root
[*]Download a use Skygo
You can get root gain by using ota root keeper but remember not to run Skygo when you are not rooted or you will have to install Skygo and then install it again.
Sorry for the quick shoddy guide. I have posted this from my S2 and in a bit of a rush.
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
Hi i have a n7 3g on 4.2.1 rooted..i installed also ota rootkeeper
Now i nave the 422 update downloaded but i ve read the rootkeeper is not functioning on 422 so now if i install the update will my root be safe opening rootkeeper band rerooting with it?
I ve a stock ROM and kernel..just unlock bootloader and root..
sent from rootilapia
I'm also stock rom/kernel, rooted and have cwm recovery, supersu, and voodoo ota rootkeeper. I told ota rootkeeper to backup root. I copied the update file to the N7 and ran the update through cwm recovery. After the update I kept root and kept cwm recovery by answering Yes to a prompt about disabling flashing stock recovery (thus keeping cwm recovery) and Yes to a prompt about recovering root. Very easy overall.
R: Help for updating
Hi to copy the update.zip you used adb or just wired to PC and copied it in the -root of sd?
If i install the update downloaded by the nexus and then run rootkeeper would be good or better install it through recovery?
Really thanks
sent from rootilapia
I downloaded the update (6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip) to my computer and from there to the N7 via usb cable. That way I could easily check the md5 checksum and I don't always trust d/l straight to the N7 although it should work fine. You can even install the zip from the download folder.
Do you have root via Superuser or Supersu? With Supersu and ota rootkeeper (told it to backup root) I kept both root and my cwm recovery. Without them, the update will flash the stock recovery overwriting a custom recovery like cwm or twrp and you will loose root. Even so, you can re-root after getting 4.2.2 and you can install a custom recovery.
I'm not sure if Superuser or twrp recovery gives the same results as I had, but the setup I posted above works beautifully. You do need to backup root with rootkeeper before flashing the update.
i lost root after updating even with rootkeeper. i simply flashed the supersu file i already had on my sd and all is fine
R: Help for updating
I have supersu and i ve configured rootkeeper when just installed means i checked everything
So now if i download the update for nakasig and install it through cwm and then put super su.apk in root of SD and then open rootkeeper and restore root will work?
sent from rootilapia