• 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

Hmm. Thats strange. Ive never heard of it reappearing. Not to insult your intellegence, but u havent flashed another rom since then have you? Because it will appear once, everytime u flash a new rom. Otherwise, this is new for a reoccuring update. I myself only recieved it once and havent since then.
 
I am curious whether the two of you installed the app that is supposed to get the updates, and then "installed" the update, which failed?

Or did you just 'install' the update, and that failed?

Or, did you click on "cancel" at any point in the above?

When I did the update, without installing the "update app" it downloaded the update, then said it had to reboot the Ally, but it hung while preparing to reboot. I rebooted the Ally, and then cleared the update notification from the top. I have not seen nor heard from the update since. (So far, anyway.)
 
ccsoccer03 said:
Hmm. Thats strange. Ive never heard of it reappearing. Not to insult your intellegence, but u havent flashed another rom since then have you? Because it will appear once, everytime u flash a new rom. Otherwise, this is new for a reoccuring update. I myself only recieved it once and havent since then.
Click to expand...

So if I were to restore a Nandroid I made right after updating to 1.1, but before the VZ update I let it 'try and fail to do', the update notice will appear again? Good to know.
 
I've also had the notification pop back up. I haven't flashed a ROM since attempting to install the update. I got all the way through the "failure" process the first time (notification, download update, click install, reboot, notification gone, no update installed), and I'm going through the process again this time.

I never installed the app required to do the update, wonder if that has anything to do with the notification re-appearing?
 
Zoandroid said:
I am curious whether the two of you installed the app that is supposed to get the updates, and then "installed" the update, which failed?

Or did you just 'install' the update, and that failed?

Or, did you click on "cancel" at any point in the above?

When I did the update, without installing the "update app" it downloaded the update, then said it had to reboot the Ally, but it hung while preparing to reboot. I rebooted the Ally, and then cleared the update notification from the top. I have not seen nor heard from the update since. (So far, anyway.)
Click to expand...

I didnt install the, but should I and retry it? And no i was on velocity 1.1 the whole time now ne ROM
 
haven't flashed a rom since i did the install.

I hit the download button. IT downloaded did the reboot and install option. Phone rebooted and loaded the recovery program. I then did another reboot and it was gone.
 
Same here. I downloaded the 12.7MB file to 'install' it (NOT), and it stalled out on the 'now rebooting' step, just as before. I pressed the Home key on the Ally's face, and it went to the home screen. So I rebooted manually. No more notification........til next time??

I wonder if we will all end up having to install the updater and accept the update from stock Froyo and then reflash Vel. 1.1, just to stop seeing the message periodically?
 
I had installed the 2.2.2 update to zve on my Rooted Ally. After I got the update and it was finished, I flashed to Velocity 1.1. The Android version has reverted back to 2.2.1 but still at software zve. I also get the system update message now, I download it, install it, and reboot phone. It'll go away for a few days to a week then come back. Could it be that Verizon or LG is reading that the phone is at 2.2.1 and resends the stupid update info? On system updates it keeps telling me I'm up to date - at least until the next time the icon shows up. Is there a way to change or make the system (in Velocity1.1 rom) think that it is running 2.2.2 and have it show 2.2.2 on the Android Version?
 
I'm getting the update notification popping back up too. It would be nice to find a App to block OTA update notifications......
 
So, I went looking over at XDA to see if such an application is available or in the works. What I found was this. Not good news.

forum.xda-developers.com/showthread.php?t=1031359&highlight=block+system+update

If this is true, and it does seem likely, we will probably have to start accepting updates somehow.
 
If I were Verizon, and I'm certainly not, I'd take my list of known rooted devices, forward them to my warranty and tech support departments and not bother with the rest.

What does Verizon really hate about rooting?
- It technically voids your warranty, but people still get phones replaced when they brick them. Money lost.
- It increases tech support requests, ranging from people playing dumb to dumb people call Verizon for help unrooting or making something work after they broke it. Money lost, time lost, call center techs unduly stressed.

Clearly state that rooting = no warranty, no tech support, and we track it, so we'll just flag your phone in the system and turn you away, and its a win for Verizon, and probably a win for the dev community. Rooting is risky, a lot of people don't get that, this may educate some of the masses.

A complete lockdown, no-go on rooting is unlikely in the US, given that the whole court case with jailbreaking and iOS kind of went toward the jailbreaking side, and its hardly fully resolved. I doubt that's a can of worms Verizon especially wants to play in.
 
In the end, whatever they do or don't do, we can all rely on our masterful and clever devs to keep us going. I can agree with your thoughts, for sure. And it seems silly to stop service to someone who roots, because they would ultimately be losing the monthly revenue that customer is paying, regardless of being rooted or not.

But if they are pinging phones to see if they are updated, which seems to me to be an easy task for them, we may possibly keep getting update notifications 'forever' until we accept the update.
 
death2all110 said:
Looking into a fix for this.
Click to expand...

Would the following work? I found it on XDA, but I don't know if it was specific to a phone model. I do know that file does reside in my Ally where this path points to. Here is what the guy said:

"changed the otacert.zip (mv /system/etc/security/otacerts.zip /system/etc/security/BAKotacerts.zip) with out any booting issues. I'll have to wait and see if that blocks any future updates."

Do I dare try this, or is that not a good idea?
 
death2all110 said:
Yeah that will work but still need some other form of solution.
Click to expand...

May I ask why this one isn't a good 'end solution'? If it works it could be built into one of the Velocity Scripts to rename the file. Or would that file somehow get restored as time passes?
 
I can't even find the file you have to download in order for the update to be able to "install" properly. When I tried looking in the Market, it couldn't find the file. (Not the Update itself; that cheerfully pops up every few days and invites me to install it again.) When I tried downloading it from the web, it wants to confirm my device and then tells me it's not compatible. GRRRR !!! Annoying!!

EDIT: Found the fix for this issue anyway - see the thread http://androidforums.com/ally-all-things-root/332856-protected-apps-problem-velocity-1-1-a.html
 
Just got my 3rd System Update Available notification, while rebooting after making a Namdroid (preparing to accept Script 34 OTA). This time I have made no changes to the ROM since the last notice. Clearly this won't quietly 'go away'.

I read that the 'fix' mentioned above,modifying that file described in the fix, is considered risky. Netizenmt, did you try it, and is everything OK since?
 
Zoandroid said:
Just got my 3rd System Update Available notification, while rebooting after making a Namdroid (preparing to accept Script 34 OTA). This time I have made no changes to the ROM since the last notice. Clearly this won't quietly 'go away'.

I read that the 'fix' mentioned above,modifying that file described in the fix, is considered risky. Netizenmt, did you try it, and is everything OK since?
Click to expand...


Ya i got my third update icon. Anything to fix it yet
 
You must log in or register to reply here.
Back
Top Bottom