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!

Update 4.5.621.en.us

Memige

New Member
Hey Community,

I got a forced auto-update this morning and wouldn't you know it, it bricked my phone instantly:blink:. Poking around the forums a bit, it seems like people in similar situations either had to junk the phone and get a new one, root the phone (voiding their warranties), or go through some long technical process involving downloading a new operating system or some such.

So two questions:

1: What is the official response to this situation? My stock, unmodified phone bricking from an official update sounds like someone dropped the ball, and being as the company is a full fledged reputable business, and not some traveling trinket vendor, I'd expect them to pick it back up themselves instead of expecting me to fix it.

2: What exactly is the testing process on these updates? Releasing a buggy patch is one thing, releasing one that effectively destroys the hardware sounds less like a QA slip up and more like a malicious virus. Seriously, over my years of using computers I've encountered my fair share of viruses, and to be frank, none where as damaging as this "official" patch seems to have been.



I'm holding off getting enraged or crazy about this as I'm waiting to given tech support the benefit of the doubt here. I love Verizon, and I love my Droid X. I just want it to work again :(

-Memige
 
Last edited:
Everyone that's had this happen thus far seems to have gotten a replacement or the option to upgrade regardless of where they are in their contract.

As to testing, they do some in-house, but part of the testing is to leak it slowly to a few bunches at a time both to save bandwidth and to catch any glitches quickly, in theory anyway.
 
Back
Top