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

Root Upgrading to 2.2.2 from rooted 2.2.1?

Ekim Gram

Member
Hi all,

So, I rooted 2.2.1 a few months ago and now the new OTA from Verizon is pestering me constantly. I love staying updated but I'm not sure if updating to 2.2.2 would mess anything up. Should i stay away from doing so?
 
If you have a custom recovery you can just click install now and the OTA will fail at the custom recovery screen.
 
If you have a custom recovery you can just click install now and the OTA will fail at the custom recovery screen.

The only concern I have are about rumors Verizon is collecting MEDI's of users who reject OTA updates as a method to flag people who may be rooted or running unauthorized ROM's for further scrutiny. Thoughts on this anyone?
 
The only concern I have are about rumors Verizon is collecting MEDI's of users who reject OTA updates as a method to flag people who may be rooted or running an unauthorized ROM's for further scrutiny. Thoughts on this anyone?


I heard it was false but dont count on it if its true theres not much we can really do.
 
If you have a custom recovery you can just click install now and the OTA will fail at the custom recovery screen.

TBH I don't remember if I have custom recovery. If it was a part of the 2.2.1 rooting guide D2A wrote then yes, I do.
 
Couple of points:

1. Even if they are collecting info that you didn't take the update, what does that really mean? Are they going to send you a nasty letter? If you are worried about your warranty, and if you have a problem and they ask about the update, I would just say that I tried to take the update but it must have failed.

2. I would also wait until someone figures out whether or not the update can be rooted before you take it. I did not see anything earth shattering in the update which would make me want to give up root.

Just my 2 cents.

DZ
 
Couple of points:
2. I would also wait until someone figures out whether or not the update can be rooted before you take it. I did not see anything earth shattering in the update which would make me want to give up root.
DZ

This may be true but the notification is extremely annoying. Are Velocity 1.1 users getting this notice? Perhaps I'll finally get around to installing that and enjoying my Ally for what it can be.
 
This may be true but the notification is extremely annoying. Are Velocity 1.1 users getting this notice? Perhaps I'll finally get around to installing that and enjoying my Ally for what it can be.

Yes I'm still getting the notification running V1.1.

Haven't accepted it yet but eventually I'm going to give in and tell it to install and let it fail just to get rid of the message, I doubt even if they keep track of who doesn't take the update that they can really do anything about it, except not warranty your phone.
 
I got the "update ready" notification overnight and I could not get it to go away, so I pretended like I was going to go through with it. I clicked the restart and install button and it hung trying to reboot. I rebooted by holding power then choosing reboot. The phone came back up normally without the notification thus far, I also have no updates available when I click the system update button inside of "about phone". I am hoping the notification does not come back.

Oh yeah, Velocity 1.1 with GNM's Amon Ra 2.2.1 recovery.
 
I got the "update ready" notification overnight and I could not get it to go away, so I pretended like I was going to go through with it. I clicked the restart and install button and it hung trying to reboot. I rebooted by holding power then choosing reboot. The phone came back up normally without the notification thus far, I also have no updates available when I click the system update button inside of "about phone". I am hoping the notification does not come back.

Oh yeah, Velocity 1.1 with GNM's Amon Ra 2.2.1 recovery.

It will not come back

The reason it failed to install as you described above is because of the custom recovery. Since it failed the notification will not come back, just as previous ota's
 
It will not come back

The reason it failed to install as you described above is because of the custom recovery. Since it failed the notification will not come back, just as previous ota's

This is not true. I 'went through" with the update a couple of days ago. I woke up this morning and the notification is back.
 
This is not true. I 'went through" with the update a couple of days ago. I woke up this morning and the notification is back.
I'm running Velocity 1.1 & I tried to accept it, it didn't take, & hasn't came back....that was last week. as far as the update itself it's ABSOLUTELY useless if you're running Velocity 1.1 bkuz the MINOR fixes that the update has ARE included in Velocity 1.1 as stated in other threads
 
I realize that. I'm on velocity 1.1 I was just stating that I "went through" with the vze update to get the notification to go away. It didn't take as expected and the notification went away for several days but it has now come back.
 
I realize that. I'm on velocity 1.1 I was just stating that I "went through" with the vze update to get the notification to go away. It didn't take as expected and the notification went away for several days but it has now come back.

I am aware of this, looking into
 
So after reading this thread (I had the same question as the OP almost word for word), the conclusion for now is to wait for a Velocity update that will take care of or get rid of the recurring prompt for the update. Is that correct?

By the way I believe I'm using Velocity 1.0 script v31. (Says 1.0 in the settings anyway.) Should I install 1.1?
 
So after reading this thread (I had the same question as the OP almost word for word), the conclusion for now is to wait for a Velocity update that will take care of or get rid of the recurring prompt for the update. Is that correct?

By the way I believe I'm using Velocity 1.0 script v31. (Says 1.0 in the settings anyway.) Should I install 1.1?

Yup!!!
 
Back
Top Bottom