Root [Verizon] I Seem To Have Kept Root After The OTA

[RichSz]

I didn't expect it but that may be what happened. I got tired of the nagging about the OTA of a week or so ago (yes, they wore me down) so I took the stupid OTA from the stupid carrier and let it do whatever to my stupid phone. I figured I'd lost root so I didn't even check.

This morning I remembered I installed Voodoo OTA Rootkeeper and protected root. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper

That couldn't really work, could it? For a goof I had it restore root. It said it worked. OK, rebooted and noticed the initial Samsung screen now has a opened padlock like my unlocked GNex does. I never noticed that before (it may have been there, I don't reboot a lot). Finished booting and opened TiBU which agreed that I had root! I accidentally did the impossible, I think.

Full disclosure, I actually paid for the root app so maybe that was a factor. https://play.google.com/store/apps/details?id=com.noshufou.android.su

Now when I look at the about screen it says my SELinux status is "permissive". Do they all say that? I never paid attention.

Here is the "proof".

If you all agree that this worked as I believe, I'll add it to the sticky. In any case, do your research and don't trust me blindly. I just stumbled around and here is the result. There may be important factors I haven't documented. Proceed at your own risk.

 

[ackoolness]

wow -_- I also installed voodoo yesterday jussssssssssst incase it would actually work, knowing that on the google play page it states that it doesnt work with samsung phones.

I disabled/froze the update programs to stop that stupid pop up, but for safe measure im still going to wait.

 

[ackoolness]

Hey RichSz, did you have a custom recovery installed?

 

[Frisco]

I didn't expect it but that may be what happened. I got tired of the nagging about the OTA of a week or so ago (yes, they wore me down) so I took the stupid OTA from the stupid carrier and let it do whatever to my stupid phone. I figured I'd lost root so I didn't even check.

This morning I remembered I installed Voodoo OTA Rootkeeper and protected root. https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper

That couldn't really work, could it? For a goof I had it restore root. It said it worked. OK, rebooted and noticed the initial Samsung screen now has a opened padlock like my unlocked GNex does. I never noticed that before (it may have been there, I don't reboot a lot). Finished booting and opened TiBU which agreed that I had root! I accidentally did the impossible, I think.

Full disclosure, I actually paid for the root app so maybe that was a factor. https://play.google.com/store/apps/details?id=com.noshufou.android.su

Now when I look at the about screen it says my SELinux status is "permissive". Do they all say that? I never paid attention.

Here is the "proof".

If you all agree that this worked as I believe, I'll add it to the sticky. In any case, do your research and don't trust me blindly. I just stumbled around and here is the result. There may be important factors I haven't documented. Proceed at your own risk.

Your thread title reminded me of my Fascinate experience.. I'd rooted it just to learn about it so I could help others, but then unrooted using the method provided at XDA.. re-rooted with another method to learn about that one, then along came an update via OTA and root access remained (checked with su in terminal, Root Explorer system file access, etc).

No VooDoo stuff, though.. other than my chicken blood stuff with the Mikey doll. But that's a different story.

 

[RichSz]

Hey RichSz, did you have a custom recovery installed?

No I don't. 100% stock just rooted. I've disabled a lot of Verizon and Samsung bloat but did that through Settings/Application manager not with TiBU.

 

[Hadron]

How big an OTA was it? I could imagine some small patch leaving the superuser binary intact maybe.

 

[RichSz]

I don't know. I seem to remember the OTA was smaller than the desktop version released earlier but both were supposed to kill root and screw up tethering. I haven't tested that part yet.

 

[jhawkkw]

If I recall, the desktop version was like a full image flash which is why it was bigger. It was also why rootkeeper didn't work because it would destroy the copy made by the program to protect root. The ota didn't touch the place where the copy was stored and thus was safe.