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

Security update being tested...

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.



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.

Much appreciated ! Thank you.
Is there an easy way to unroot from that one ?
 
From manual, yes, IIRC, you first move / delete the su binary, then reboot, then remove the superuser app as you would any other app.

I think that's all that is required.
 
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.

Ahh, I figured out why, after the update the two different rootless tethering apps I have no longer work.
 
I just got my notification this morning. Because I am on Page Plus, neither OTA, nor WIFI updating will work for me. All that happens is a triangle when it reboots to install the update. Question is, will I keep getting notified? Stay tuned and I will let you know.

EDITED
Three days. Time to change the .prop file.
 
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

Make sure you follow step 6, Reboot the phone, I didn't reboot the first time and started getting the update message again after about 10 hours of use. Hopefully it is fixed now after the reboot. Just thought I'd throw that note in there.

Thanks for the instructions, I seemed to have suppressed the update!
 
Back
Top Bottom