Stuck after 2.1 upgrade.

Discussion in 'Android Tech Support' started by kblakely, Apr 5, 2010.

  1. kblakely

    kblakely New Member

    Joined:
    Apr 5, 2010
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Rochester, NY
    Ratings:
    +0
    Well, I ran the 2.1 upgrade on my Moto Droid, this morning and have been stuck on the startup screen (flashing red eye) all day. Not sure what my next step is. I'm guessing I will have to do a factory reset, but I've been holding off because I would rather NOT lose all my data... if at all possible.

    Anyone else seen this... and more important, anyone got any suggestions ???
     
  2. PrawoJazdy

    PrawoJazdy New Member

    Joined:
    Apr 5, 2010
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I can't offer much, but after two hours of waiting for this screen to go away I removed my battery after powering down would not work from the power button. This was a mistake and now my phone displays a data corrupt error and will only go to boot loader screen when powering up. Call Verizon or go to a Verizon store before you do anything.
     
  3. Jonny Kansas

    Jonny Kansas Administrator
    Staff Member Rescue Squad

    Joined:
    Jan 21, 2010
    Messages:
    16,012
    Likes Received:
    6,710
    Trophy Points:
    1,278
    Location:
    Michigan's Upper Peninsula
    Ratings:
    +8,020
    Current Phone Model:
    Huawei Nexus 6P
    Twitter:
    jonny_ks
    Not sure exactly what their policy on you trying to manually install the update instead of waiting for the ota, but I'd recommend you go to VZW as well. I'd just tell them that something went wrong while you were installing the update (try to avoid letting them know that it wasn't ota) and hopefully they can flash it and fix it for you...but you'll most likely lose your data.

    If they can't fix it, hopefully they can get you a new one (in which case, you'll still lose your data...)
     
  4. kblakely

    kblakely New Member

    Joined:
    Apr 5, 2010
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Rochester, NY
    Ratings:
    +0
    Thanks for the quick reply. I'm not sure what OTA stands for but this WAS the official update pushed to my phone (not a manual install).

    I figured either way I would be doing a reset... so that's what I did. Got the phone back but obviously lost all my apps... what a pain.

    If I had it to do over I would skip this "upgrade".
     
  5. afm528

    afm528 New Member

    Joined:
    Nov 12, 2009
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I'm afraid I may be in the same boat. I started the OTA upgrade while connected to my laptop via USB and now I'm stuck on "BootLoader 2C.6C Battery OK OK to Program Transfer Mode: USB" which is usually what I see when I try to charge a completely dead Droid via laptop USB cable. I've had this on my screen for at least 30 mins, so I'm assuming that something went wrong. Am I hosed? Do I need to reset, or is there some prayer that the install is just really slow? (I know, I know....)
     
  6. kblakely

    kblakely New Member

    Joined:
    Apr 5, 2010
    Messages:
    5
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Rochester, NY
    Ratings:
    +0
    Can you get to the recovery screen (startup holding the X)?

    I had mine plugged into the wall charger, so it wasn't a battery issue. After doing a factory reset I did have 2.1 so the install apparently went fine... I just was stuck on the boot screen.

    To anyone going to do an upgrade... be sure you back up as much of your info as possible. My contacts were in Gmail and synced almost instantly and the Android market did remember what apps I had purchased... so it was not as painful as I thought it was going to be. Just plan on doing a lot of downloads, for a while.
     
  7. afm528

    afm528 New Member

    Joined:
    Nov 12, 2009
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I got impatient, pulled the battery out and then restarted and everything was fine, but no upgrade. I'll wait a bit to see if they try to push it to me again. I'm considering rooting my phone, so I guess now's the time to back everything up anyway. thanks for the reply
     
  8. JMac84

    JMac84 New Member

    Joined:
    Nov 21, 2009
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    I'll give you my story. I had the same update problem as kblakely. Updated, and stuck at the blinking red eye for at least an hour when I came upon this thread. So I went ahead and called VW support. Support tech was very nice although hadn't yet heard of this problem. He excused himself for a few moments, came back and told me to go ahead and pull the battery, which I did. I was instructed to pop the battery back in and try to start the phone. Stuck again at the blinking red eye.

    He then said oh well, phone must be bricked, I will send you a new one. Hmmm, ok by me i guess. So I set that up, hung up the phone, and thought what the hell, new phone coming, I might as well try resetting the phone myself.

    I had to look up on the interwebs how to go about doing that, but quickly found it and after pulling my sd card, went ahead and formatted and reset and reactivated the phone. Well, what do you know, it booted right up and after checking the firmware version, it has the 2.1 update!

    As I type this i just checked and 31 applications have been restored. So except for a few cosmetic details (resetting my 3 screens) my phone seems to be mostly back to normal.

    Soooo, here is my slight dilemma. I have a new phone coming in the mail (overnighted tomorrow), and i am supposed to send this phone back. So do I keep the new phone? or call VW back and cancel the order? I'm thinking I'm gonna send this phone back and keep the new one (this one has that pesky headphone jack issue that drives me nuts).

    Whatcha think?
     
  9. Jonny Kansas

    Jonny Kansas Administrator
    Staff Member Rescue Squad

    Joined:
    Jan 21, 2010
    Messages:
    16,012
    Likes Received:
    6,710
    Trophy Points:
    1,278
    Location:
    Michigan's Upper Peninsula
    Ratings:
    +8,020
    Current Phone Model:
    Huawei Nexus 6P
    Twitter:
    jonny_ks
    Bordering on fraud there, but IMO, if you've got a headphone jack issue, that's a hardware problem, and that's totally covered by your warranty...
     
  10. JMac84

    JMac84 New Member

    Joined:
    Nov 21, 2009
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    Sorry to hijack your thread kblakely, hopefully you at least get some useful info from my experience.

    I am certainly not interested in defrauding VW, but if you (Jonny Kansas) think that the headphone jack issue (which I have been living with for a while) is copacetic, I'm gonna send this one in.
     
  11. Jonny Kansas

    Jonny Kansas Administrator
    Staff Member Rescue Squad

    Joined:
    Jan 21, 2010
    Messages:
    16,012
    Likes Received:
    6,710
    Trophy Points:
    1,278
    Location:
    Michigan's Upper Peninsula
    Ratings:
    +8,020
    Current Phone Model:
    Huawei Nexus 6P
    Twitter:
    jonny_ks
    Well, what's the problem? Is it doing the thing where you can't get sound to play out of the phone after you unplug it?

    I mean...Technically speaking, Idk how long the warranty is good for...and if you got insurance, there's the $50 (I think) deductible.

    BUT, if you send it back and they see that it's no longer bricked and they're not happy about it, I'm sure they'll let you know... :D
     
  12. JMac84

    JMac84 New Member

    Joined:
    Nov 21, 2009
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    1
    Ratings:
    +0
    already made the cancel call, oh well, honesty wins begrudgingly. I will wait and see if the headphone problem continues as I have been looking around and apparently this update addresses the problem. so we'll see.....

    So i have gone from fairly satisfied with my VW update experience to fairly unsatisfied. Its gonna take me a bit to get my phone back to where it was before. Its was still gonna be a pain in the ass, but dulled by the fact that it was going to be a newer phone....not anymore, just a pain in the ass.

    So who is responsible for this entire update clusterf#*% VW or Motorola?