What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

VZW Stopped the OTA

All those who've been running the 217 leak have had no problems, so I'm wondering if the problem is with updating the phone itself and it's not 217 that's the problem.

That could be the case, as far as phones being bricked the only thing that the tech support person I spoke with mentioned was to make sure I had at least 50% battery remaining. He did tell me that people are getting excited when they see the update and kicking it off with 10% battery remining, only to have the phone die in the middle of the update and become bricked. Maybe they are implementing a battery level check so this does not happen. I am surprised that the Droid 4 does not have this since when I try for updates on my wife's HTC Rhyme it checks how much charge is remaining before it can proceed.
 
I did the fastboot method yesterday, rooted, installed safestrap, backedup, added eclipse rom, removed rom and haven't had a problem at all, maybe its just certain phones having issues. Ill keep anything odd or out of the ordinary posted. Also a side note, my battery life is amazing with ics, Ihavent had to charge once today and I started at 0530 with about 70% battery and moderate to constant use. :) soooo happy.
 
Just because you don't see it posted in a forum, doesn't mean it's not happening. Fact of the matter is he said I wasn't the only one that had the issue and wasn't the first he'd seen about it that day. For you to think the only way issues are confirmed is through a forum is crazy.

For an unrooted phone with no issues previously to crash a day after an update...even if I didn't work IT it would be easy to figure out what the issue was.

If you want to defend the update by all means go ahead but fact is it is pulled and even if a select few users had hardware issues, that's one too many.

It may be the case or it may not be the case. But so far, on this website alone you're the only one mentioned how the update bricked your phone. I am not saying you did anything wrong or that the tech was right. But by now you would see other complaints about the update bricking phones or at least the update was delayed or stopped.
 
If it bricks your phone and doesn't have insurance... would they still replace your phone after year 1? If so, refurb or brand new? I would hate mine to bricked and they replace it with refurb. I don't want the Maxx either, we already have 3 at my house. Although I do envy them when they're still on their first full charge when i'm already on my second one.
 
Assuming the tech is right and there are some bugs with the OTA they released and have to make a new version (let's say 218 for example), they will have to find a way to push that to those who received the OTA. Maybe they'll add a line to the system check allowing it to apply from ICS 217?
 
In the XDA thread someone mentioned that the update was suppose to go out just the soak testers and they instead started the normal phased deployment. May or may not be true. I think the community can agree that .217 is pretty stable and is a marked improvement over the last GB update. I'm personally enjoying the fastest GPS lock ever on any device I've owned. On the D3, I'd have to turn off the GPS then back on for the darn thing to work. GB on the D4 I was lucky if it got a lock in five minutes on the top of a mountain with clear skies.

This thread got me a bit concerned since I forced the update last night and it would be just my luck that it'd have a problem. Thankfully we have such an awesome community that if there was a problem, there'd be a way to get out of it.ilovedf
 
In the XDA thread someone mentioned that the update was suppose to go out just the soak testers and they instead started the normal phased deployment. May or may not be true.ilovedf

For whatever reason, the standard Moto soak test procedure sends the update to two groups: 1) the official soak testers, who provide feedback in the private Motorola forums set up for the test 2) a somewhat larger set of "others" who just get the update, without necessarily knowing anything about it.
I guess this group calls Verizon if there are issues (soak testers are told not to, as VZ and Moto call centers haven't been trained on the update). Not quite sure why this is considered a good idea, but that is what happens!

So given the number of people here who didn't get the update, I don't think there is any evidence that a full phased rollout was accidentally begun, just that some here were in the planned "others" group.
 
Is there any way to know when the official roll out will begin.

There is not alot of info out there on this update. Only that it started a few days Ago. I have only seen on here and on xda that the OTA Push was cancelled and also that the OTA hasnt really begun yet.... Because there is not much chatter about it I feel like I'm alone in not having recieved the update yet. I keep checking the settings -> About Phone-> System Updates and getting no update needed at this time.... :crying: I'd prefer to wait for the OTA but im getting antsy.... Sigh...
 
Last edited:
There is not alot of info out there on this update. Only that it started a few days Ago. I have only seen on here and on xda that the OTA Push was cancelled and also that the OTA hasnt really begun yet.... Because there is not much chatter about it I feel like I'm alone in not having recieved the update yet. I keep checking the settings -> About Phone-> System Updates and getting no update needed at this time.... :crying: I'd prefer to wait for the OTA but im getting antsy.... Sigh...

The soak test is not quite complete (very soon it will be) and then the general OTA will begin.
 
i just got off the phone with a moto rep.. they are still doing the update. but it is sent out in batches by device ID... I got the OTA on one phone(in Washington state) while i was awaiting a warranty replacement... the replacement phone cant get the OTA yet because the device ID isnt in this batch of phones.

he told me to expect it within the next 2 weeks.
 
i just got off the phone with a moto rep.. they are still doing the update. but it is sent out in batches by device ID... I got the OTA on one phone(in Washington state) while i was awaiting a warranty replacement... the replacement phone cant get the OTA yet because the device ID isnt in this batch of phones.

he told me to expect it within the next 2 weeks.

Thanks for this bit of info. I really appreciate it. 2 weeks is a long wait tho :(
 
Got this updated on my Wifes D4 and my mothers D4 both updated OTA with NO issues and running great. My wifes which was formally on the 215 leak is now getting better battery.
 
Just did "About Phone, System Updates" (for about the 3rd time today). Downloading!

edit: Downloaded and verified in about 30 min.
 
Last edited:
Back
Top