bootloader 2c.6c

Discussion in 'Motorola Droid' started by jessie2010, Jan 1, 2010.

  1. jessie2010
    Offline

    jessie2010 New Member

    Joined:
    Jan 1, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    my motorola droid will not boot up. all i get on screen is...

    bootloader
    2c.6c

    battery ok
    ok to program
    connect usb
    data cable


    any suggestions on how to fix. the phone is only about 6 weeks old. never been wet or dropped.

    thanks
  2. messenger13
    Offline

    messenger13 New Member

    Joined:
    Nov 18, 2009
    Messages:
    76
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Cleveland, OH
    This is the screen I get when my USB cable is connected to my laptop when I tried to boot my DROID. I'm assuming your DROID is not connected to the USB cable. But perhaps there is something in the USB port that is shorting it out, or something. Try blowing in there and see if it'll boot then. Sounds weird I know ... it's all I can think of.
  3. Wincing Devil
    Offline

    Wincing Devil New Member

    Joined:
    Nov 29, 2009
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    I was gonna give my Geocoords, but the Droid crash
    I just had this happen. I turned it off and back on again.

    [​IMG]
  4. ChevyNo1
    Offline

    ChevyNo1 Premium Member Premium Member Developer

    Joined:
    Dec 28, 2009
    Messages:
    5,354
    Likes Received:
    5
    Trophy Points:
    0
    I just had this happen also ... no fix???
  5. Torm
    Offline

    Torm New Member

    Joined:
    Feb 10, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    I have the same Issue

    I have the same problem, every time i try to restart my Droid i get
    Bootloader
    2c,6c





    battery ok
    Ok to program
    connect usb
    data cable

    The only way i have been able to get my phone to boot is to turn it off and on over and over until it finally completes the boot sequence. I really want better solution to this problem because it seems that i have to restart the thing pretty regularly because of other issues
  6. summerfish
    Offline

    summerfish New Member

    Joined:
    Dec 24, 2009
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    0
    I just had this happen to me today. I was charging my phone in my car and this morning I came out and it had this error, but mine stated Charging Low Battery. If we can pinpoint the reason we can help others. I'm running Smoked Glass Rom, 0.99.3.b SirPsycho. Those would be the only things that would cause any issues I would think.
  7. R1Lover
    Offline

    R1Lover New Member

    Joined:
    Nov 6, 2009
    Messages:
    1,702
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Northern Ca
    Maybe verizon is trying to push an update and it's messing with some rooted phones? lmao
  8. summerfish
    Offline

    summerfish New Member

    Joined:
    Dec 24, 2009
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    0
    You know I was actually thinking that. When was the first push done for 2.0.1? If it's around the same time as those other posts, then we may be right.
  9. tevoid
    Offline

    tevoid New Member

    Joined:
    Mar 30, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    March 30th, 2010
    I just got the same message on my phone. I've only had it about 4 months if that.
    My wife and I have the same phone, but unfortunately I can't find out if hers is doing the same thing.
    I do think the problem is related to either the type of usb cord used to connect to a PC or that it could have something to do with the operating system. Today was the first time I ever plugged my phone into a PC with Windows 7 to receive a charge.
  10. summerfish
    Offline

    summerfish New Member

    Joined:
    Dec 24, 2009
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    0
    I still stand by the fact that it's with each push. Mine was plugged into my car charger but the car was off so it wasn't charging and i found my phone with the error. Dunno...
  11. MotoRolla
    Offline

    MotoRolla New Member

    Joined:
    Apr 3, 2010
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    I don't know how many people other than myself had this issue, but I was able to clear it up after tons of frustration. My error was slightly different (it said CODE CORRUPT under the boot loader numbers) but all that it needed to work again was:
    1. Removing the battery and MicroSD card.
    2. Replacing the battery after about a minute
    3. Booting (past the error) and properly shutting the phone down from the menu.
    4. Remove battery, replace MicroSD, replace battery, reboot and serve.

    Boots and reboots fine for me now.
  12. PetRiLJoe
    Offline

    PetRiLJoe New Member

    Joined:
    Mar 28, 2010
    Messages:
    279
    Likes Received:
    1
    Trophy Points:
    0
    Location:
    Opelika, AL
    I'm glad you fixed your problem, but no one else in this thread seemed to post whether or not their phones have been modified from the original OS or not. I'm interested if it was a Verizon thing conflicting with user modifications such as rooting as ROM upgrades or if it was something else.
  13. MotoRolla
    Offline

    MotoRolla New Member

    Joined:
    Apr 3, 2010
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    0
    My phone was stock except for forcing the 2.1 update with the file from google. I did not have it rooted, themed, or modified at all.
  14. Andrew89
    Offline

    Andrew89 New Member

    Joined:
    Apr 4, 2010
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    I just had this problem this morning, but mine was easily fixed. I pulled the battery and sd card, then replaced battery and booted it. Turned off phone and replaced my sd card and all was good!
  15. PrawoJazdy
    Offline

    PrawoJazdy New Member

    Joined:
    Apr 5, 2010
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    0
    My phone is less than 2 months old. I love it and it does everything I need for business and pleasure. However Friday I got the update for 2.1 notification and began the install.

    I accepted the update and the phone went to reboot after about 10 minutes of loading and install OTA.

    The screen remained on the Droid "eye" screen for over an hour during the reboot. I plugged in the phone to the wall during this time and waited another hour.

    After hour 2 I tried to turn off the phone. It wouldn't shut down. After another 20 minutes I decided to pull the battery.

    I reinstalled the battery, got the Motorola "M" logo and then it booted up fine to homescreen. Phone froze at home screen. Could not touch anything including apps, app drawer, phone button, hard keys such as menu etc... In other words it was a very pretty electronic paperweight.

    Repeated the above two steps for about an hour and then after my 10th or 11th attempt to remove the battery I got the boot loader screen with the error in this thread upon power up.

    Pulled battery and SD card. Replaced battery and turned on phone. Got Motorola "M" logo. Then boot loader.

    Repeated until Sunday and gave up after searching all the forums and trying every trick including reflash. Called Verizon warranty center.

    Tried booting to safe mode and doing hard reset per Tech instructions. Would not boot to safe mode and could not get to home screen to reset the phone.

    Called Verizon again this morning and they are overnighting me a new Droid. When it arrives I have to use my current battery, insert it into phone and boot up. Then send my current brick back to Verizon.

    For the record, my phone liquid indicator shows no signs of water. Meaning its White with solid Red "X's" as is the battery's indicator. I've not dropped it, its never been wet or even used in the snow or brought into the bathroom during a shower. I've also never rooted the phone or installed non market approved apps or anything silly like the picture generating apps for phone calls. (whatever those are) I've babied it and read that most users had no troubles with the update.

    Has anyone else had something similar?

    I'm really happy they are over nighting me a new phone. It gives me some confidence in their customer service.
    Last edited: Apr 5, 2010
Search tags for this page

battery ok ok to program connect usb data cable

,
boot loader 30.4 battery ok connect usb data cable motorola
,

bootloader 2c.6c

,
bootloader 2c.6c battery ok ok to program
,
bootloader 2c.6c battery ok ok to program connect usb data c
,
bootloader 2c.6c battery ok ok to progran connect usb data c
,

droid bootloader 2c.6c

,
droid connect usb data cable
,
motorola bootloader 2c.6c
,
motoroloa droid ok to program