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

Security update being tested...

Ah, was wondering what kinda confused when my Droid was showing an update available this morning... I did not apply the last one, so I'm going to do a Nandroid backup and try applying without wiping...

Not very optimistic, but I'll give it a shot...
 
For those looking for the update, I found the file in /cache...

EDIT: Removed the file, can re-add if wanted/allowed...
 
It seems (from OPs link) that this disables root. I haven't been unrooted since I got the phone basically and don't want to start now. If I apply this, what's the easiest way to get root back?

I got the update notice last night and it keeps popping up wanting me to update it constantly. I'll try moving it from the /cache directory as mentioned above for now.
 
I got this update this morning and now my Droid is much slower. Screen is very slow to repaint after any app I'm in. It use to be only a few apps that did this.
Not very happy. Still like the Android system, but not my Droid
 
after updating my phone it appears for some odd reason that my market, facebook and google+ apps don't work anymore, it claims they no longer exist.
 
To prevent the update notification, you will probably just have to change the build.prop values...

So, change...

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

and

ro.build.fingeprint=verizon/voles/sholes/sholes:2.2.2/FRG83G/91102:user/release-keys
to
ro.build.fingeprint=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");
 
For what it's worth, I installed this update overnight, and have since had 2 hard crashes. In all my time owning this phone, i've only had a crash or two, but in the last 12 hours, it's crashed twice. Not liking the looks of this update at all.
 
I'm avoiding this one like the plague. Figures it pops up the day I decide it's finally time to root the old droid after 2 years, lol.
 
what a joke that they do this at the end of the life cycle of this phone. I have no, zero, none, zilch intentions of installing this. In the past, for those of us that are rooted, build prop edits will stop it.
 
Never rooted my Droid. I got the update notification yesterday morning and installed it. So far I haven't really noticed any difference.
 
Unrooting and rerooting a phone should be second nature to people that use rooted phones. Superoneclick makes it ez.
 
vey said:
Unrooting and rerooting a phone should be second nature to people that use rooted phones. Superoneclick makes it ez.
Click to expand...


The problem is that this update blocks the two known exploits that were used in the past to root these phones in the first place. After applying the update you cannot root the phone anymore, based upon P3Droid's tweet the same day.
 
johnlgalt said:
The problem is that this update blocks the two known exploits that were used in the past to root these phones in the first place. After applying the update you cannot root the phone anymore, based upon P3Droid's tweet the same day.
Click to expand...

Which would be a definite drag because I run at least a half-a-dozen apps that need root to run at all. It also makes sense to call this a security release because I was just reading on CNET(?) that Android is now leading the pack when it comes to malware. The experts put the blame on Market and that all it took was $25 to start uploading on Market with virtually no oversight by Google.

It's yucky drudge work to test all the software, so why not just block root and make it easy? Sounds like that is what they did.
 
My Wifes Droid got the update and hasn't noticed any difference in performance or stability. Don't know how it would be negatively affecting other phones. It seems any update is a bad update these days though :(.
 
The only thing I've seen bad about this particular update (thus far, but I honestly haven't looked closely) is that it blocks the exploits that allowed us to have root level access on the phones.

But the timing of the update is what confuses me - many people have moved on from this phone, replacements are hard to come by, and it was a vanilla phone when it was released - no locked nothing. Why block root on this virtually obsolete phone now?
 
johnlgalt said:
But the timing of the update is what confuses me - many people have moved on from this phone, replacements are hard to come by, and it was a vanilla phone when it was released - no locked nothing. Why block root on this virtually obsolete phone now?
Click to expand...

I'm angry. I got the notice this morning and installed it... but I'd planned on finally rooting and installing a custom ROM over the holidays. I'll be very... peeved if I'm really screwed out of that.
 
Well, you can - read my reply in the other thread you posted in.

It's not completely broken, but Zerg is broken. SuperOneClick and rageagainstthecage work, as does manually rooting.
 
icecold said:
To prevent the update notification, you will probably just have to change the build.prop values...

So, change...

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

and

ro.build.fingeprint=verizon/voles/sholes/sholes:2.2.2/FRG83G/91102:user/release-keys
to
ro.build.fingeprint=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");
Click to expand...

Is there an easy way to do this? I can't afford to lose root at all (left side of the touchscreen doesn't work and I'm using a root only app to compensate for this, I put a new digitizer in and the touchscreen got better but still not 100% functional).

Not quite sure where those files/folders are and how to update the names.
 
johnlgalt said:
The only thing I've seen bad about this particular update (thus far, but I honestly haven't looked closely) is that it blocks the exploits that allowed us to have root level access on the phones.

But the timing of the update is what confuses me - many people have moved on from this phone, replacements are hard to come by, and it was a vanilla phone when it was released - no locked nothing. Why block root on this virtually obsolete phone now?
Click to expand...

This really puzzles me too. Why now ? and why this phone ?
Is the actual security update the closing off of the Root possibility ?
Is Verizon on a powertrip to close off all Root possibilites ? Seems extreme to do this for such an old phone.
Kind of upset about it that they are doing this.
 
MountainRatMat said:
Is there an easy way to do this? I can't afford to lose root at all (left side of the touchscreen doesn't work and I'm using a root only app to compensate for this, I put a new digitizer in and the touchscreen got better but still not 100% functional).

Not quite sure where those files/folders are and how to update the names.
Click to expand...

You'll need to be already rooted to do this, and build.prop should be located somewhere in the system tree - My DROID is dead right now so I cannot say where exactly it is.

az_r2d1 said:
This really puzzles me too. Why now ? and why this phone ?
Is the actual security update the closing off of the Root possibility ?
Is Verizon on a powertrip to close off all Root possibilites ? Seems extreme to do this for such an old phone.
Kind of upset about it that they are doing this.
Click to expand...

Well, not all root exploits are broken, since Superoneclick and rageagainstthecage and the manual method still work. Apparently it only breaks Zergrush.

I replied to your other post in ATR with link for the manual method - other posts in that thread have links for Super and rage.
 
For Clarity's sake, Here are the full instructions:

0) Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)

1) Download ES File Explorer (Or any other root file editor) I use Root Explorer - JG

2) (Only if you're using ES File Explorer) In ES File Explorer, go into Setting > Root Settings and enable both check boxes

2) (Only if you're using Root Explorer) navigate to /System and then press the Mount R/W button at the top

3) {Navigate to /system/} and copy/paste build.prop to /sdcard/ (just in case)

4) Open & edit /system/build.prop

5) change...

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

and

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

6) Reboot the phone

That should take care of the update notification
 
You must log in or register to reply here.
Back
Top Bottom