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

System Update?

for those wanting to stop the nag message there are threads here detailing how to do it... the one about 3 threads down has the new build number you need for your build.prop file.
 
Hm. I've seen the update message a couple of times.

- The first time it said to reboot my Dinc to install the update, so I did. It gave me a "low memory" message, and when it managed to come back, ALL my shortcuts were gone, replaced with some default set. :( Seemed like a factory reset. I figured I had the update. But Software Number says 4.08.605.2, I guess that means I'm not updated. Can one of you gurus confirm this?

- The second time I was plugged into my laptop (as "Disk Drive"), and it said it would reboot to install the update in 7 seconds. It didn't. I unplugged and rebooted. Looked like a normal "DROID" reboot. Still at 4.08.605.2.

I don't really care either way (as long as it doesn't loose stuff or brick my phone), but I'd sure like to know how to know if the update has actually been installed. Any help?

Yeah, yeah, I've done my time combing the forum. Not seeing a clear answer.

TIA
 
Sounds like you answered your own question, if you don't see 4.08.605.15 then you did not get it.

I only got the update once and it failed due to low memory. Memory will stay low so i plan to never get this. Life is good!!!!
 
hemifever said:
fine. I quit whining long enough to back it all up and reload the OS. Internet is working again. Verizon said it could be temporary as the install will eventually come back and force itself on. I don't know a thing about the rooting and being able to deny the update for good.
Click to expand...

Good. If you don't want the nag, root. Believe me, it's an interesting ride. If I could do it so can you. Been very satisfied. Disabled the nag and deleted the update. Remember that update that would not load? Gingerbread. It improved the way storage was handled. But a fresh clean install was the best way to get it to work as intended. Start with this thread. It's an exact road map to rootsville. Remember, if a no obligation like me can do it so can you.
 
Looks like all the pieces are stacking up niceley for a "CLASS ACTION LAWSUIT" for the folks at Verizon. If they would just acknowledge that there is an issue, and work on a soulution, then things would look a bit different. I've had great service over the years, but their declining support and "just get a new phone" attitude makes me a bit suspicious. Maybe someone should post the words "CLASS ACTION LAWSUIT" in the thread over at the Verizon forum and see if that prompts a response...
 
Not sure if that would even be possible since Big Red can simply blame Google and HTC for all their woes...
 
Verizon sold the phones to the consumers, and it's their network that the update came across. If HTC's update had a bug, it's Verizon's responsibility to it's customer base to ensure that an update is reliable before it get's pushed out (that is, if Verizon still understands that it's the consumer who makes them tick, not the technology... I'm sure the exuecutive management team understands that the consumer is ultimately the cash cow, but has no respect or regard for how they extract that cash from the consumer).

I don't like to speculate, but I've been in enough board room discussions to see this kind of strategy being openly discussed, with the end result being a financial gain or increase in efficiencies, regardless of the possible negative impact to reputation or public impression.

This is the first time I've commented on a thread here, but this issue is a bit suspect. I'm on night 4 of the reboot cycle and allthough the phone is working fine in the morning, I'm waiting to see if it ever finishes up doing what it's doing... whatever that is (which is another seed of speculation alltogether).
 
Yeah - that's certainly true and your contract is with VZW and not Google or HTC. It just wouldn't surprise me though if they didn't have a get out clause or something buried deep in the T&Cs.

I can only begin to imagine the levels of frustration users must be going through with this though - more so because I've an an Incredible myself. I stuck with FroYo after I rooted so have avoided this nightmare.
 
Well around 2am every night my phone continues to reboot until 5am. This is definitely the strangest bug I have seen. I just let it do its thing with no changes in sight. I hope I never need my phone during those times or forget to plug it in.
 
Mine rebooted on Wednesday and Thursday last week at 3:35 am and then stopped. It started again this week on Wednesday and Thursday at 3:35 again. Weird cycle...The only good thing is I get up at 3:30...:p

I am just getting tired of this crap and believe that it will be fixed..
 
Yes. I believe that there are quite a few of dinc users who have never installed the patch for gingerbread. I know my daughter hasn't, and doesn't want to. She just puts up with the repetitive nags and moves forward. As long as it makes and recieves calls, text, accesses Web content, she is satisfied. If the camera or music quit, that could tweak a nerve. But all that stuff still works soooooo, she just keeps hitting install later. Not really a terrible strategy.
 
it's been about a week since I received the update that did not install because of the low memory issue. I have never received the update prompt again and it's been over a week now. they must have stopped sending it to my phone.
 
ONJFan said:
it's been about a week since I received the update that did not install because of the low memory issue. I have never received the update prompt again and it's been over a week now. they must have stopped sending it to my phone.
Click to expand...

I didn't get the nag for a few days until I rebooted. Then when it showed up again I said to heck with it and pressed restart and install. The phone just hung after that. I went back to the home screen then restarted the phone. No update was installed... I don't think. I mean it's still running like normal...
 
As I mentioned before I only got the update once, its been over a week. Today I took my battery out to start using my extended battery again and when I put the new battery in, low and behold I got the update again, I quickly grabbed by cam and took a pic. Unfortunately, I had turned off my 3G when it came up and when I went to turn it back on the update was gone. I went into setting to see but I still have the old software so it didn't work again.

I freed up some internal memory prior and wanted to see if this would really install but it failed again. I took battery back out but the update prompt has not returned.

Here is what it looks like:

onjfan-albums-orig-incredible-recent-update-picture6482-orig-inc-recent-update-july-2012.jpg
 
I've tried to update for the last week or so and now have succeeded. Here's my story. I hope it will help someone else. I've tried to get assistance from HTC, but after a number of dead ends they were left with the reset option, which I totally refused. I have 200 installed apps, data, etc and was not about to go that route. I have a 32GB SD card and had already moved any apps that were capable of going there. I should also note that I am not rooted. My first call to HTC related to the 2-3 AM wake-up cycle after an update failed due to low memory. After much discussion, the tech pointed me to an obscure web address to download an memory fix apk. It installed as a "memory hotfix" app. It may have helped with the common low memory notification. I don't think it helps with the low storage notification. My next attempt to install the update (prompted by changing the system date back) was met with the process hanging on the "rebooting now" message. This occurred several times until I learned how to the wipe the system cache partition (Support: Wipe cache partition to clear system memory: HTC Amaze 4G / One S / Sensation 4G / Wildfire S / T-Mobile G2 / myTouch 3G Slide / myTouch 4G / myTouch 4G Slide). Now the phone rebooted, but the installation was not successful and I received a low storage message. At this point I removed large apps and updates on the phone storage until I had at least 350MB free. Clearing the cache partition, re-downloading the update, and running the installation went through I've had no problems and no early morning re-boots. I'm no expert, but this worked for me. Good luck.

P.S. I communicated all of this to HTC tech support and they were very appreciative.
 
nytroutbum said:
I've tried to update for the last week or so and now have succeeded. Here's my story. I hope it will help someone else. I've tried to get assistance from HTC, but after a number of dead ends they were left with the reset option, which I totally refused. I have 200 installed apps, data, etc and was not about to go that route. I have a 32GB SD card and had already moved any apps that were capable of going there. I should also note that I am not rooted. My first call to HTC related to the 2-3 AM wake-up cycle after an update failed due to low memory. After much discussion, the tech pointed me to an obscure web address to download an memory fix apk. It installed as a "memory hotfix" app. It may have helped with the common low memory notification. I don't think it helps with the low storage notification. My next attempt to install the update (prompted by changing the system date back) was met with the process hanging on the "rebooting now" message. This occurred several times until I learned how to the wipe the system cache partition (Support: Wipe cache partition to clear system memory: HTC Amaze 4G / One S / Sensation 4G / Wildfire S / T-Mobile G2 / myTouch 3G Slide / myTouch 4G / myTouch 4G Slide). Now the phone rebooted, but the installation was not successful and I received a low storage message. At this point I removed large apps and updates on the phone storage until I had at least 350MB free. Clearing the cache partition, re-downloading the update, and running the installation went through I've had no problems and no early morning re-boots. I'm no expert, but this worked for me. Good luck.

P.S. I communicated all of this to HTC tech support and they were very appreciative.
Click to expand...

I have been in touch with HTC suport for the last week. I am dealing with a cretin. :(We have gone round and round in circles and so far not achieved one iota of progress. My USB cable did not work, and I am trying to get a new one. :rolleyes:You would think I am asking for the earth - and my phone is still under warranty. I imagine he is stalling until the warranty period expires then he can tell me to go away. :mad:SO - any advice I read on here - I am unable to replicate as the USB CABLE DOES NOT WORK!!! :mad::(:confused:(And I am going on holiday in a few days unable to access the internet because I only have 2 -3 mb of internal memory. Is anybody else unable to install app updates?
 
nytroutbum said:
I've tried to update for the last week or so and now have succeeded. Here's my story. I hope it will help someone else. I've tried to get assistance from HTC, but after a number of dead ends they were left with the reset option, which I totally refused. I have 200 installed apps, data, etc and was not about to go that route. I have a 32GB SD card and had already moved any apps that were capable of going there. I should also note that I am not rooted. My first call to HTC related to the 2-3 AM wake-up cycle after an update failed due to low memory. After much discussion, the tech pointed me to an obscure web address to download an memory fix apk. It installed as a "memory hotfix" app. It may have helped with the common low memory notification. I don't think it helps with the low storage notification. My next attempt to install the update (prompted by changing the system date back) was met with the process hanging on the "rebooting now" message. This occurred several times until I learned how to the wipe the system cache partition (Support: Wipe cache partition to clear system memory: HTC Amaze 4G / One S / Sensation 4G / Wildfire S / T-Mobile G2 / myTouch 3G Slide / myTouch 4G / myTouch 4G Slide). Now the phone rebooted, but the installation was not successful and I received a low storage message. At this point I removed large apps and updates on the phone storage until I had at least 350MB free. Clearing the cache partition, re-downloading the update, and running the installation went through I've had no problems and no early morning re-boots. I'm no expert, but this worked for me. Good luck.

P.S. I communicated all of this to HTC tech support and they were very appreciative.
Click to expand...
the partition clear worked with the last system update that had install issues. hopefully it works with this one.
 
Has anyone determined if this will remove our ability to root the device? My phone is now retired to at home wi-fi duty and I want to root now.
 
I thought the ability to root had been blocked when GB first came out and that you need to downgrade to 2.2 to get there.

There are plenty of stickies that describe the process.
 
I'm rooted/unlocked and using a custom 2.3.4 ROM but can't figure out how to disable that pesky system update message. I tried renaming otacerts.zip under /etc/security but the update reminders keep coming. Has anyone else had luck with another method?
 
I got the system update prompt again, this time it said your phone will reboot in 10 secs, started counting down and then it never rebooted.

Has anyone else had that?
 
You must log in or register to reply here.
Back
Top Bottom