zandroidx

I'm helping out a friend who has a rooted Original Droid running stock FRG83G. On my rooted Droid X, I just use titanium backup to freeze the "Updater" app. I can find no such app on his phone. I've seen some of the "How Tos", but none of them discuss the latest update. Besides, we'd like to block ALL updates, and the root explorer methods that are listed seem like they must be performed whenever a new OTA is released. Is there no app or process we can just freeze with Titanium Backup?

PhilosoRaptor

Just move the .zip from the /cache folder. I wouldn't worry about them pushing anymore updates OTA. I'm amazed the Droid even got one this far out in its life cycle.

zandroidx

Won't it just download another zip when it finds out there is an unapplied update?

icecold

In case deleting the .zip file out of the cache doesn't work, this should!

To prevent the update notification, you will probably just have to change the build.prop values...

So, change...

ro.build.description=voles-user 2.2.2 FRG83G 91102 release keys
to
ro.build.description=voles-user 2.2.3 FRK76 185902 release keys

and

ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.2/FRG83G/91102:user/release-keys
to
ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.3/FRK76/185902:user/release-keys

That should take care of the update notification


assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/voles/sholes/sholes:2.2.2/FRG83G/91102:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/voles/sholes/sholes:2.2.3/FRK76/185902:user/release-keys");

Last edited by icecold; November 28th, 2011 at 04:12 PM. Reason: Changed fingerprint to description

zandroidx

OK, my concern with changing the keys is that it's not my phone. I'm concerned with possible problems down the road for him. Let's say I change the keys, then another update is released and he takes the update (either intentionally or unintentionally), will the phone be ok since he skipped the previous update?

As an aside, if he takes this current update do you know if he will lose root? Our goal here is to keep root. He has no problems with the phone the way it is, so he doesn't want any updates that might make him lose root, even if re-rooting might still be an option (is it?).

icecold

As with any of the other updates, it will break root...

Create a backup of the build.prop, so he can always change back fairly easily... Keep a copy of the .zip file someplace on the SD card... That way you can always go back and install if needed. But I highly doubt any additional updates are going to be sent out, unless they are to fix this current one...

EDIT: It appears that SuperOneClick is not working on rooting after the latest update after looking in another thread.

zandroidx

Thanks. I'll just modify his build.prop like you said.

Lock-N-Load

shouldnt the first ones in red actually be

ro.build.description=voles-user 2.2.2 FRG83G 91102 release keys
to
ro.build.description=voles-user 2.2.3 FRK76 185902 release keys

that is, I think you put fingerprint where it should be description in the first line to edit

__________________
TABLET: Asus Transformer Prime - rooted

PHONE: D1 + Pete's FRG01B | JDLFG's 32.25 1.25 | Pete's Baseband C_01.43.01P | My metamorph battery mod | Droid X Bootanimation

icecold

Yes, you are correct. Thanks for the catch...

Lock-N-Load

so, removing to cache will NOT work as already stated.

the above modified tweak to the 2 lines in build.prop WILL work.

teddyearp

Hmm, an interesting development on the A855 front. I have just read and replied to a few threads about 2.2.3/FRK76 tonight. I/we would have thought that updates for the A855 were done.

I am anxious to see if someone can 'catch' this file and PM me with a means for me to download and tear it apart to see what it entails. . . .

NVM folks, I have now read the other posts about this update and now am grabbing them up.

Last edited by teddyearp; November 25th, 2011 at 10:11 PM.

byno

Alternatively, you could use Root Explorer and modify the build.prop file (located in the phone's internal storage at System/build.prop).