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

VZE Froyo 2.2.2 Update Discussion Thread

When I fist got the ally, I rooted and removed the bloat ware and LG home crap and was 900 percent happy with it. I actually think it ran better then the thunderbolt I have now does. But I had a very tragic hardware failure and I received a new ally sporting 2.2 and that's where my love for LG ally ended... Once I get a computer that can actually recognise the ally I'm rooting and going back to 2.1..

Try the Verizon drivers from Drivers & Resources - LG Forum
 
I had to remove velocity 1.1, the OTA kept showing up and if I tried to download anything from the market over 5megs it would hang and keep downloading till the battery was dead. Guess I have to wait till the folks running and doing the updates for velocity come up with a solution for this. I've tried the "fixes" to stop and correct the OTA issue but without success. Just let us know when it hits and I'll try it again
 
I had to remove velocity 1.1, the OTA kept showing up and if I tried to download anything from the market over 5megs it would hang and keep downloading till the battery was dead. Guess I have to wait till the folks running and doing the updates for velocity come up with a solution for this. I've tried the "fixes" to stop and correct the OTA issue but without success. Just let us know when it hits and I'll try it again

Does your Ally have Fastboot access?
 
Well, even after editing the file mentioned somewhere above which allows the Market to show us and install the Ally Upgrade Utility and then running the VZE update (which of course fails on V1.1) I just got my 5th notification for the VZE System update. I ran it and, as usual, it stalled out trying to reboot, so I manually rebooted, and the notification is gone (until next time).

If anyone has found a way to stop the VZE update notification short of completely wiping the Ally prior to installing Velocity 1.1, please let me know. If it comes down to that as the only solution I'll do it. But quicker options are always a plus. :)

>>>>>>To our devs, >>>>>>if I have to do the full wipe and install, which is the best suggested guide to follow at this point? Some procesures seem to have evolved since Velocity 1.0 was released.
 
If anyone has found a way to stop the VZE update notification short of completely wiping the Ally prior to installing Velocity 1.1, please let me know. If it comes down to that as the only solution I'll do it. But quicker options are always a plus.

For what it's worth, I went back to stock recovery and VZD (using the nandroid in this thread) and let the phone update to VZE properly. I then flashed amonra in fastboot, flashed Velocity 1.1 from amonra, and not a day later the update notification showed up.

So I don't know what to do other than run stock to get rid of the update. Then again, letting it download and fail once a week or so isn't something I'm losing sleep over.
 
For what it's worth, I went back to stock recovery and VZD (using the nandroid in this thread) and let the phone update to VZE properly. I then flashed amonra in fastboot, flashed Velocity 1.1 from amonra, and not a day later the update notification showed up.

So I don't know what to do other than run stock to get rid of the update. Then again, letting it download and fail once a week or so isn't something I'm losing sleep over.

Nor I, but finding a solution would be a good thing.

The worth of your post, to me, is great. It seems even going through all that doesn't stop the repeat notifications. So what your post provides is knowledge to save me 'time', which is one of my most prized commodoties. I thank you for letting me know this. I won't bother with trying to take the 'scratch installation' route then.

Maybe someone could cook up a utility that works like selective call blocking, but blocks update notifications instead?
:D

Somehow our carrier sees the Ally running Velocity on 2.2.1 as not being updated to 2.2.2. We need to trick that process into reporting we already have 2.2.2. But I have no idea how to do that.
 
I'm just going to wait until the devs ccook up something new into changing the revision number to match that 2.2.2 verizon update. I'm sure in 1.2 they will already have even better updates. I'm also wondering if verizon is pushing this update soo hard because they are implementing "snoopware" in it to see how naughty we all are.
 
Does your Ally have Fastboot access?


After getting my phone I used SOC to get root (works fine for me) then immediately made a backup of my stock rom through recovery before downloading or doing anything. I then downloaded Velocity 1.1 and then copied it over to my sdcard. Then rebooted back into recovery and wiped data, dalvik, (everything) and then installed velocity 1.1 to a basically stock phone. After that I re-downloaded and used Titanium to re-install all my programs. Everything worked great but for some reason the stupid 2.2.2 ota update kept coming up sometimes several times a day and at other times it might be a couple of days between "visits". The 5 meg thing might have been them reading the state of my phone and blocking it or another problem altogether not sure as I didn't play with it too long as I was getting very frustrated with the ota kicking in all the time. It might have been due to it being overclocked, etc causing the Download problems. I am waiting on Velocity 1.2 and hope it works well as I doubt that Verizon or LG are working on any other updates for the Ally...
 
After getting my phone I used SOC to get root (works fine for me) then immediately made a backup of my stock rom through recovery before downloading or doing anything. I then downloaded Velocity 1.1 and then copied it over to my sdcard. Then rebooted back into recovery and wiped data, dalvik, (everything) and then installed velocity 1.1 to a basically stock phone. After that I re-downloaded and used Titanium to re-install all my programs. Everything worked great but for some reason the stupid 2.2.2 ota update kept coming up sometimes several times a day and at other times it might be a couple of days between "visits". The 5 meg thing might have been them reading the state of my phone and blocking it or another problem altogether not sure as I didn't play with it too long as I was getting very frustrated with the ota kicking in all the time. It might have been due to it being overclocked, etc causing the Download problems. I am waiting on Velocity 1.2 and hope it works well as I doubt that Verizon or LG are working on any other updates for the Ally...


Open the velocity toolkit, open terminal emulator and start the velocity script by typing
Code:
velocity
and let it update, then you will need to type it again becuase it exits out of the script. it may update twice. And if it does, do it again and it will fix the update. If you look aroun all things root and the velocity forum, its bene there FOR A WHILE NOW. If you dont know about the velocity toolkit and the amazing script. Youre missing out.
 
Open the velocity toolkit, open terminal emulator and start the velocity script by typing
Code:
velocity
and let it update, then you will need to type it again becuase it exits out of the script. it may update twice. And if it does, do it again and it will fix the update. If you look aroun all things root and the velocity forum, its bene there FOR A WHILE NOW. If you dont know about the velocity toolkit and the amazing script. Youre missing out.

This wasn't a problem with Velocity updating, it's the stupid one from verizon. I checked and yes I do have fastboot. Velocity is great I love it, and I'm going to instal 1.2 when it comes out - I've tried installing it on a "back to stock" but the stupid verizon 2.2.2 update keeps coming up. So what you're saying is to re-install velocity 1.1 - goto the toolkit - open the terminal emulator and type velocity let it run then go through the terminal steps a second time and that will stop verizons 2.2.2 from trying to update? (just trying to make sure as I've tried everything else that had been suggested in the velocity forum)
 
This wasn't a problem with Velocity updating, it's the stupid one from verizon. I checked and yes I do have fastboot. Velocity is great I love it, and I'm going to instal 1.2 when it comes out - I've tried installing it on a "back to stock" but the stupid verizon 2.2.2 update keeps coming up. So what you're saying is to re-install velocity 1.1 - goto the toolkit - open the terminal emulator and type velocity let it run then go through the terminal steps a second time and that will stop verizons 2.2.2 from trying to update? (just trying to make sure as I've tried everything else that had been suggested in the velocity forum)


Im not saying to update velocity. Im saying to start the velocity script, the SCRIPT will update. Maybe once, probably twice. Then open it again and it will fix the update issue.
 
They found a way to trick the Ally into telling Verizon it is up to date, and incorporated it into the script updates. Ever since I did as suggested here the update notifications stopped. It works. :)
 
Im not saying to update velocity. Im saying to start the velocity script, the SCRIPT will update. Maybe once, probably twice. Then open it again and it will fix the update issue.

So to get this straight, when you type velocity in the terminal it will download updates to the script (or patch it) and I may have to do this twice or more to be sure it takes or gets or downloads all the available scripts which for lack of better words patches/updates the velocity rom? Not trying to be mean just having way to many brain farts and am trying to be sure I get this all correct in my head... lol

So now I should be able to flash the velocity1.1 zip after wiping user/data/dalvik (everything) then use Titanium Backup to restore everything except for the data. (restore the apps not their data). Then open the toolkit - open the terminal and type velocity (this part maybe two or three times) and I should then be good to go? Sorry to be a pain just wanting to be sure.....
 
No problem, just do a full wipe, you can restore apps and data, just not system data.

Then start the velocity script by typing "velocity" in terminal. I know after i reflashed they updated twice, and then after starting the scipt again it patched it and rebooted to stop the notification.
 
Back
Top Bottom