New OTA on Verizon Support

i do think part of the issue is that htc updated all the sprint and tmobile phones and released are gb update and patch all at the same time and ever one wants it and there servers just cant handle it we are going to have to wait it out and let server traffic calm down before we are going to have more sucess espically if your trying to pull the whole gingerbread update and not just the patch.
 
Just had a colleague in Philly running full stock without any previous version of GB installed check for updates and he gets back Service Unavailable.
 
Same for me. Just outside of New York City and getting Service Unavailable from the "Check Update".
 
Was this a full GB update or just the delta between 605.3 and 605.5 with the security fix?

It depends on whether you got the previous GB OTA or were still on Froyo MR2. If you got the previous GB OTA, you'll just get the smaller patch file, whereas the other you'll need/get the full GB install that has the patch rolled into it.
 
It depends on whether you got the previous GB OTA or were still on Froyo MR2. If you got the previous GB OTA, you'll just get the smaller patch file, whereas the other you'll need/get the full GB install that has the patch rolled into it.

The reason I'm asking is that I'm not aware of ANYONE actually getting the full OTA install. Nobody has reported that they got the full 605.5 (146 megs) OTA install yet. Only reports of "I got it" and a few "I got the 15 meg update.

The few people I know who are running full stock and didn't get 605.3 for the two days it was available are all getting SERVICE UNAVAILABLE message.

I'm just wondering if its only pushing out to those people who already have 605.3?
 
It gets pushed in batches, I believe by MEID number or some other unique phone identifier. I don't believe it gets pushed based on what current software version you may have. The service unavailable is most likely do to the servers getting hammered or they have taken some of them down to load the new update and will bring them back online when ready. And most people here probably already have the last GB OTA or flashed the full RUU (from Android Police), so they'll end up with just the small patch file. It would be nice though if posters could provide more detail so we can make a better determination on this stuff. :)
 
The reason I'm asking is that I'm not aware of ANYONE actually getting the full OTA install. Nobody has reported that they got the full 605.5 (146 megs) OTA install yet. Only reports of "I got it" and a few "I got the 15 meg update.

The few people I know who are running full stock and didn't get 605.3 for the two days it was available are all getting SERVICE UNAVAILABLE message.

I'm just wondering if its only pushing out to those people who already have 605.3?

I don't know if this helps, but I have 605.3 and I've hit a solid wall of "service unavailable" and "Error 2304" messages since about 5PM last night.

It is possible that they are getting the 605.3 folks upgraded first, since they have the smaller upgrade file and can be upgraded more quickly, and they also have the Voicemail notification bug that was introduced in 605.3, but I kinda doubt that.

I think the servers are just swamped. It also happened during the 605.3 upgrade - some people had it pushed to them overnight, some got the notification followed by a connection failure followed by "no updates available" for a while (like me), then came back into queue and were re-offered the upgrade a few hours later. And a lot of people ran into a lot of "service unavailable" messages because the servers were swamped.

I expect that the problems are going to last while this time. HTC is upgrading a lot of phones at the moment. Their servers are probably severely overloaded.

Early reports of this Gingerbread build are overwhelmingly positive. It looks unlikely that Verizon will feel the need to pull this build. This looks like the build that may finally fulfill all the promise this phone has to offer. So there's no desperate rush to get this one, it should stay up on the servers until everyone is upgraded this time.

Be aware that it may be a week or two before everyone gets it, though, since the last build only reached a small number of people and was up for about 24 hours (and wasn't coinciding with major updates to several other HTC phones). In fact, if every HTC Sense phone out there gets upgraded in a two-week period, I'd be deeply surprised and impressed.

If you're in a huge rush and can handle dealing with a factory reset, the RUU is only a download away, and you'll be running the same stock firmware everyone else is (and quite probably with a lower possibility of problems since you'll get a "factory fresh" build).

Otherwise, just keep checking every few hours, and eventually you'll get your Gingerbread lovin' :-*

:D


Note: Last time, I did a battery pull and it was very shortly after that I was offered 605.3. It was probably a coincidence (correlation is not causation), and I did it during a peroid of "No Updates Found", not during a "Service Unavailable" peroid. But hey, if you wanted to try it, it can't hurt.

Especially if you haven't restarted in a while - when you do eventually get the upgrade it might go a little cleaner if you've had a recent full reboot.
 
Just for the record, I'm still on Froyo with MR2, and when I check for the update, I get nothing; meaning, the checking for updates box comes up and then just goes away. I don't even get the service unavailable message.

Maybe they're rolling out the patch for those who got the first GB update before they send the full OTA to the rest of us? Not sure....
 
I don't know if this helps, but I have 605.3 and I've hit a solid wall of "service unavailable" and "Error 2304" messages since about 5PM last night.

It is possible that they are getting the 605.3 folks upgraded first, since they have the smaller upgrade file and can be upgraded more quickly, and they also have the Voicemail notification bug that was introduced in 605.3, but I kinda doubt that.

I think the servers are just swamped. It also happened during the 605.3 upgrade - some people had it pushed to them overnight, some got the notification followed by a connection failure followed by "no updates available" for a while (like me), then came back into queue and were re-offered the upgrade a few hours later. And a lot of people ran into a lot of "service unavailable" messages because the servers were swamped.

I expect that the problems are going to last while this time. HTC is upgrading a lot of phones at the moment. Their servers are probably severely overloaded.

Early reports of this Gingerbread build are overwhelmingly positive. It looks unlikely that Verizon will feel the need to pull this build. This looks like the build that may finally fulfill all the promise this phone has to offer. So there's no desperate rush to get this one, it should stay up on the servers until everyone is upgraded this time.

Be aware that it may be a week or two before everyone gets it, though, since the last build only reached a small number of people and was up for about 24 hours (and wasn't coinciding with major updates to several other HTC phones). In fact, if every HTC Sense phone out there gets upgraded in a two-week period, I'd be deeply surprised and impressed.

If you're in a huge rush and can handle dealing with a factory reset, the RUU is only a download away, and you'll be running the same stock firmware everyone else is (and quite probably with a lower possibility of problems since you'll get a "factory fresh" build).

Otherwise, just keep checking every few hours, and eventually you'll get your Gingerbread lovin' :-*

:D


Note: Last time, I did a battery pull and it was very shortly after that I was offered 605.3. It was probably a coincidence (correlation is not causation), and I did it during a peroid of "No Updates Found", not during a "Service Unavailable" peroid. But hey, if you wanted to try it, it can't hurt.

Especially if you haven't restarted in a while - when you do eventually get the upgrade it might go a little cleaner if you've had a recent full reboot.

Thanks for the thoughtful response. Unfortunately its my daughter's phone and she wants to stay stock...at least until the warranty expires:cool: I did recommend the battery pull and full reboot though. It can't hurt right?
 

Trending Posts

Members online

Forum statistics

Threads
956,411
Messages
6,968,099
Members
3,163,539
Latest member
Lounduchand