• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Root and 2.2

mdroid20

Newbie
Aug 18, 2010
10
0
Simple question that i cant seem to find the answer to. I know on the D1, the answer to my question would be yes, but on the DX when 2.2 drops OTA, will DLing it drop root? and once 2.2 is on, will we be able to "re-root".

I know there are loopholes in 2.1 that allow root, but i wasn't sure if 2.2 had similar things going on.

Reason i ask is because at minimum i want 2.2 on my DX b4 i keep it activated (right now i'm tethering it off my D1 for things i want to use it for). I know the pete's of the world are working on things, but i was just wondering. Thanks
 
Simple question that i cant seem to find the answer to. I know on the D1, the answer to my question would be yes, but on the DX when 2.2 drops OTA, will DLing it drop root? and once 2.2 is on, will we be able to "re-root".

I know there are loopholes in 2.1 that allow root, but i wasn't sure if 2.2 had similar things going on.

Reason i ask is because at minimum i want 2.2 on my DX b4 i keep it activated (right now i'm tethering it off my D1 for things i want to use it for). I know the pete's of the world are working on things, but i was just wondering. Thanks

Make the search button your best friend. This has been spoken about many times

http://androidforums.com/all-things-root-droid-x/149775-froyo.html

That is just one of the many

Look up "pdanet"
Free tethering without root
 
Upvote 0
Simple question that i cant seem to find the answer to. I know on the D1, the answer to my question would be yes, but on the DX when 2.2 drops OTA, will DLing it drop root? and once 2.2 is on, will we be able to "re-root".

I know there are loopholes in 2.1 that allow root, but i wasn't sure if 2.2 had similar things going on.

Reason i ask is because at minimum i want 2.2 on my DX b4 i keep it activated (right now i'm tethering it off my D1 for things i want to use it for). I know the pete's of the world are working on things, but i was just wondering. Thanks

Since 2.2 hasn't dropped yet, nobody knows for sure... That said, many suspect that the 2.2 OTA will close the vulnerability that was used to gain root.
 
Upvote 0
With 2.2 so close to release, I'm debating whether to root now or just wait until after 2.2? If I root now, then there may potentially be problems updating to 2.2 once the OTA update hits. But if I wait until 2.2 updates first and THEN root, I'm thinking I'll be better off because it'll be a long time before another official update release.

If we knew for sure what's going to happen to current rooters when the 2.2 OTA update hits, then I might consider doing it now.

Actually, I'm not even sure I *want* the 2.2 update! There's an audio streaming bug with Froyo that Google is patching, but haven't heard whether this will be included in the Droid X's 2.2 update? There are also a couple of other bugs that are introduced with Froyo, and the benefits don't seem to outweigh the potential problems.

Is there a way to root now and prevent the phone from updating to 2.2 when it comes out?
 
Upvote 0
When my phone arrives, I intend to root it. When the Froyo OTA update comes out, or when Birdman's copy is released, I will simply un-root and upgrade. Then it's just a simple matter of re-rooting I think.
edit: HolyGrail pointed-out (see this post below http://androidforums.com/all-things-root-droid-x/132353-how-prevent-ota-updates.html#post1287239) that deleting (or disabling) the SystemUpdater.apk is the better way to go to keep OTA updates from happening.

As always, take care / caution about what you delete / remove or alter!

Here's my original post:

To keep OTA updates from coming in, you would rename your /etc/security/otacerts.zip file to something else (say "/etc/security/otacerts.zip-bak"). Cheers!

edit: there's also a copy of otacerts.zip in /system/etc/security, so it might be a good idea to rename that file too.
 
Upvote 0
When my phone arrives, I intend to root it. When the Froyo OTA update comes out, or when Birdman's copy is released, I will simply un-root and upgrade. Then it's just a simple matter of re-rooting I think.

No don't rename it

Its not the exact same but its still applicable

What Pete had to say
Peter Alfonso

I have been notified by a few Bugless Beast users that they have been receiving the OTA update notification and were wondering what to do. The reason for this is because Bugless Beast V0.4 is based on FRF84B, an earlier build than the new OTA update (FRG01B). A few months ago many of us would have simply renamed or removed otacerts.zip from /system/etc/security to block OTA updates but we quickly learned that this method drained battery life tremendously because it constantly caused the updated to redownload. The patch I will provide below will update the build keys and fingerprint to "trick" the system into thinking it is the latest build. Therefore no more OTA update notifications.
 
Upvote 0
EDIT: Nevermind. I know what you were referring to now.

Tell him that, not me. I'm just quoting/linking.

EDIT2: By the way, the post is clearly showing an update on an original post. He wasn't saying to do that re-naming process. He said to simply remove or rename SystemUpdater.apk to stop the OTA update from initiating automatically.

Yeah I was just trying to talk about renaming otacerts.zip and not to do it...thats all
 
Upvote 0
With 2.2 so close to release, I'm debating whether to root now or just wait until after 2.2? If I root now, then there may potentially be problems updating to 2.2 once the OTA update hits. But if I wait until 2.2 updates first and THEN root, I'm thinking I'll be better off because it'll be a long time before another official update release.

Actually, the Gingerbread update is scheduled for October, I believe.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones