14 replies to this topic

[jgattonii]

First of all, a special thanks to Dan for Motoshare 2!

In an effort to follow his instructions for preparing for no further Moto exploits, I'd like to embrace my noobiness and ask the question point-blank: what do I need to do to keep my su safe? I've tried combing through existing posts but they all say different things. Can someone please advise on what I should do now? Thanks in advance and I hope that the results will help others too!

[Memnoch73]

You don't have to do anything except don't take any future OTA updates without checking in here to find out the instructions to keep root safe

[jgattonii]

Thank you, Memnoch. Would it be accurate to say thay Moto is unable to push automatic updates?

[Notc]

The bionic isn't going to be getting any more updates, this was the end of the road for us.

[Memnoch73]

Thank you, Memnoch. Would it be accurate to say thay Moto is unable to push automatic updates?

They can push them just fine if they ever do is the question but it is your responsibility to not let them install. 

 

The bionic isn't going to be getting any more updates, this was the end of the road for us.

 

This is probably pretty accurate.

[jgattonii]

Thank you, both.  In retrospect, I might should've posted this as more of a general question than one specifically related to Bionic...  I understand that I may not have to worry about future updates w/ this phone, but what about another one?  At the end of the day, I'd like to know how to solidly protect any rooted android device - even staying secure through an automatic push & install scenario.  I recognize that this has not been common practice for past updates, but I'd like to know I had protection against it - in case one ever were to, e.g. similar to the way Windows will get tired of a user postponing the update and will finally update & re-boot on its own.  

 

I've read posts mentioning Nandroid backup, SafeStrap, Titanium Backup, Voodoo OTA Rootkeeper, etc., but I'm honestly not sure which ones of those (or others) that I'd need to look into further - or even whether some of them do the same things as another one.

[Memnoch73]

Voodoo is what you are looking for. It has options to protect/save root and then temp-unroot to take an OTA update

[jgattonii]

Sounds good.  I appreciate the recommendation.

[SamuriHL]

One thing....if you go into your Superuser app of choice (ChainDD, Koush, SuperSU, etc) and it updates the su binary, make sure you go into Voodoo, delete the protected su, and re-protect it to get an updated backup.  That should keep you out of trouble.

[jgattonii]

Thank you Samuri. I noticed that the superuser included with Dan's exploit is different than ones I've had before. Does it automatically update su binaries only when I open the app? Is that something I should do on a regular basis or just before messing with stuff?

[jgattonii]

Just for clarification, my noobiness comes from this being the first root that I've ever started trying to understand what is actually happening vs. one-clicks in the past.

[SamuriHL]

Yes, it will update when you open the superuser app if necessary.  And you should in fact do that regularly.

[jgattonii]

Good to know. Thank you for this information and all the help you're also giving on the exploit thread.

[Eric214]

But you should only update the SU in the stock side right? Also, install the Voodoo OTA  rootkeeper on the stock side as well NOT on any of your custom installed ROMs.

 

Eric

[SamuriHL]

Voodoo should be on stock side.  su should be updated everywhere.