Stuck on Bootloader from OTA...

[TheSwaggeR]

I don't understand what just happened here. I SBF'ed back to Froyo, took on the new GB OTA, downloaded it, asked me to install it and I press ok. I watched it install and it looked all good then it went to the Bootloader. I have not been able to get out of the Bootloader for the past 2 hours now.

I've tried several different methods to get me out of it like... battery pull, power on + x, power on + up dpad (this brings you back to the Bootloader too). I tried SBFing back to Froyo again to try again but it says FAIL on RSD Lite and something about Unable to retrieve initialization values from INI file. So I'm out of luck trying to SBF.

This is what the Bootloader currently says...

Bootloader
D2.37
Err:A5,69,35,00,27

Battery OK
OK to Program
Connect USB
Data Cable

I have tried connecting USB cable to it but it doesn't do anything. I mean, it does change from..

Connect USB
Data Cable

to...

Transfer Mode:
USB

Anybody have this problem? This is starting to piss me off.

 

[UrbanBounca]

Have you tried downloading the SBF again?

Sent from my DROID2 using Tapatalk

 

[d4dEf@c@]

I don't understand what just happened here. I SBF'ed back to Froyo, took on the new GB OTA, downloaded it, asked me to install it and I press ok. I watched it install and it looked all good then it went to the Bootloader. I have not been able to get out of the Bootloader for the past 2 hours now.

I've tried several different methods to get me out of it like... battery pull, power on + x, power on + up dpad (this brings you back to the Bootloader too). I tried SBFing back to Froyo again to try again but it says FAIL on RSD Lite and something about Unable to retrieve initialization values from INI file. So I'm out of luck trying to SBF.

This is what the Bootloader currently says...

Bootloader
D2.37
Err:A5,69,35,00,27

Battery OK
OK to Program
Connect USB
Data Cable

I have tried connecting USB cable to it but it doesn't do anything. I mean, it does change from..

Connect USB
Data Cable

to...

Transfer Mode:
USB

Anybody have this problem? This is starting to piss me off.

This happened to me the first time I installed the OTA. I had to SBF with rsdlite. At least you're at the bootloader. Sorry bro, it's all you can do.

Posted from my D2 with CM7GB

 

[TheSwaggeR]

Yes I did try SBFing, like I mentioned. It failed. I redownloaded a fresh copy of the SBF and it still failed.

I have RSD Lite version 4.5.3 Multi Flash/Multi Flex program. Could that be the problem?

 

[TheSwaggeR]

Ugh, got another problem now. Apparently being on the Bootloader killed my battery from 100% to 0% in 3 hours.

Now it just says:

Battery Low
Cannot Program

I've got it plugged into the wall now. Hopefully it corrects itself. I changed Motorola Drivers and RSD Lite to 4.7 so I wanted to see if that will work or not but I can't now because of the stupid battery issue.

 

[chaaaad]

I thought you can't charge your phone from the boot loader unless you have a dev cable?

 

[TheSwaggeR]

You can get it out of the "Battery Low, Cannot Program" issue if you have it plugged into the wall and not the PC via USB. Apparently none of this works. Tried everything I could to get the battery charged up again but it doesn't seem to want to charge at all.

Either my motherboard got fried or the battery got fried from Verizon's GB OTA. Thanks Verizon, always counting on your stupidity.

 

[TheSwaggeR]

Ok, I just may be in luck and may cancel out the CLN (which I hope cause I don't want someone else phone that crapped out on them). Had to ghetto charge it which required me being extremely precise with the wall charger and where it needs to go in to give juice to the battery. Had to hold it there for 10 minutes or so. Replaced it with the actual original charger. Now the charge light is finally back on.

Once I can get the battery image to come up, I'll be extremely happy. Allow it to charge to 100% and then redo the SBF with correct RSD Lite program and Motorola Drivers. Pretty sure the original RSD Lite was the cause of not allowing it to SBF properly. Hopefully the OTA doesn't mess it up again on the 2nd attempt.

Let us pray!

 

[hond2]

I also got stuck at bootloader despite everything looking like it was going right. I was mobile when I needed to sbf so I used the TBH sbf.zip. Success. Download update, success. Install, no errors, good. Auto reboot=new bootlogo then bootloader! NO! Used Ubuntu FULL sbf when I got home. Now all is good. At some point I do remember thinking my battery was suddenly way lower than I thought it should have been, so I popped in a spare Chinese/Ebay battery I keep around.

Sent from my DROID2 using DroidForums

 

[TheSwaggeR]

I have officially revived my phone! Even the rep from Verizon said it would be impossible to fix it. Well, I defied the grim news and took on a challenge that many would given up on easily. I will be writing a report shortly on addressing the issues, what I found, what I did, the persistent problems, and the necessary steps I took to get it all up and running again.

 

[TheSwaggeR]

How it happened:

This initially started when I was trying to provide information to another D2 user. The D2 user couldn't see his screen and asked how many clicks down/up were to get to the wipe data on CWR. I provided the info to him in another thread. To my horror, when I tried backing out of the menu to reboot my phone back up, it went ahead and wiped all my user data. I was currently on MIUI 1.8.12.

So, I figured since I messed up I might as well go for it and SBF back to Froyo to take on Verizon's GB OTA. I did this by buying TBH's app. It has a flashable SBF zip (2.3.20). Everything went well with that zip as far as I could see.

I then proceeded to go ahead and take on VZW's GB OTA after the phone had settled down from all the activity going on after the SBF. Everything looked good when the phone shut off so the GB OTA could install. Once the installation was over the red Motorola logo appeared and I was excited to see the new GB. Instead, I was greeted with a Bootloader and what appeared to be an assortment of errors in different numbers and letters.

What I did:

- Shut the phone off via Power button and Power it back on (fail)
- Hold Power button + x. This takes you to the stock recovery. Instead, it took me straight back to the Bootloader (fail)
- Pull the battery out, reinsert it after 3 seconds and Power on (fail)
- Pull the battery out, reinsert it after 3 minutes and Power on (fail)
- Hold Power button and up button on physical keyboard (success without errors like mentioned above)
- Boot up RSD Lite, used 2 different versions and try to SBF (fail on both versions)

The result of many unsucessful attempts and the consequence:

The result of trying everything I knew and looking up different methods ended up killing my battery, while being stuck in the Bootloader, within 3 hours of the problem occurring.

New problem arises:

Due to a dead battery, I decided to just leave it on the wall charger. Many people fail to understand that charging from your PC (computer) does not provide an adequate cycle of power supply to your phone. It will still charge but going from 20% to 100% on a wall charger (AC) should take 2 hours versus going from 20% to 100% from your PC (computer) would take roughly 4 to 7 hours.

When I checked in on the battery, I was greeted with a new problem on the Bootloader:

Battery Low
Cannot Program

So, with that new problem I knew I was going to have to fight with reviving the battery before I could revive the crippled Android OS.

What I did for the battery issue:

- Left it on the wall charger during each test on different periods of idle time (failed)
- Plugging the USB into the PC (computer) shows charge light on (success)
- Plugging the charger into the wall outlet shows charge light on (fail)

Diagnosis: The Android OS is not established on a Bootloader therefore it has no way of reading and recognizing a charge no matter what you do.

Things You Could Try To Get A Charge Or Get The Bootloader Running In Your Favor: You could try to power off the phone, take the battery out, reinsert it, hook it up to the wall charger, wait a few minutes and just tap the Power button once. If you get the battery charging image then you are good to go to get it charged up. If this does not help and takes you to the Bootloader with the same persisntent Battery Low, Cannot Program message then you need to either borrow a battery or get another battery that you have and is charged up and see if that fixes the problem

If you should finally resolve that issue, you should see a Battery Ok message and then attempt to SBF again.

Since none of this worked for me and I had no battery to borrow I had to do things the hard way. I took it to the VZW store, where I bought it, and hoped the VZW rep would change out the battery and get something going so I could finish up the rest. He comes back and says he has no idea what is wrong with it and it looks impossible to fix. He admitted to changing out with a fresh battery (which I would later question him saying that because that's what would be the cause of the problem with the battery issue).

21 Hours Later:

Before I grew too tired and it was 2am in the morning, I had decided to just slightly push the charger into the slot of my D2 (from the wall charger) and the charge light came on finally. I used tape to hold it in place. If I pushed it all the way in, it would shut off, the Bootloader would come on and the Battery Low, Cannot Program would be flashing before my eyes yet again.

I went back to work on this phone around 11:30am this morning. I noticed the charge light was not on anymore and I was thinking the battery finally got charged up. I powered it on and sure enough it said Battery OK on the Bootloader.

So, I quickly booted up the Linux SBF (follow this link http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html) and plugged the USB via my laptop to my D2. Everything went good but then the phone shut off on me midway during the SBF process. However, I did notice that something caused the battery to get along slightly better with the charger but it wasn't charging up the way it needed to charge up.

Last Resort for Battery Issues (Beware! Research before you do this!)

Basically I need my battery to have enough charge so I could run the Linux SBF on it. I had to think about this one for awhile and then it struck me. Most of my phones I've had have been Motorola brands. I went digging for some of my old Motorola chargers. Found 3 of them. What I did next is something you have to research because anything bad could happen. I cut off the end of the micro-USB (the end that plugs into your phone). There were 3 wires. Red, Yellow, and Black.

Red is positive (+)
Yellow is temperature charge (T)
Black is negative (-)

On the back of the D2's battery there is a + (red positive) and a - (black negative) next to the terminals. Basically I took the red and black wire, stripped it down to expose the threads and sandwich the red with the phone's terminal and battery's terminal and the same for the black wire. I allowed it to stay in place for about 30 minutes. Some people say 5 to 10 minutes is enough time for it but that all depends on what kind of phone you have. Smartphones like the D2 require a little more time for this kind of charging. I would not recommend to leave it in there for the same amount of time that you leave it on your regular wall charger.

I was greeted with Battery Ok on the Bootloader but had a new message, Corrupt Code. I knew I was on the right track because I read up on the Corrupt Code and that is easily fixed with a fresh SBF.

Once the 30 minutes passed I booted up the Linux CD with the SBF on it and quickly went to work on reviving the Android OS.

20 minutes later, the phone is back up and running on Stock Froyo and currently charging, off the wall charger, the way it should.

If anyone has any questions regarding being stuck on the Bootloader or Battery Low, Cannot Charge then please post your messages here. I will be glad to assist you in getting it back up and running again since I have a ton of more information on what to do to fix this up.

Bottom line... nothing is impossible.

 

[ldopa]

Freaking Bravo! That, my friend, was an intriguing read. It was like a droid forums digest article. So happy you're back!

CM7GB-601

 

[UrbanBounca]

That's too much work, IMO. I appreciate the guide, but wow.

 

[TheSwaggeR]

Haha, thank you very much! I'm very happy to be back on again.

 

[TheSwaggeR]

That's too much work, IMO. I appreciate the guide, but wow.

It may be, but if you're someone like me that just won't give up easily on different issues then you would understand where my dedication comes from. I'm an avid programmer (PC and somewhat for the Droid now) and amateur technician. Both of those play a big role in my hobby in understanding the concepts of how technology works and accepting challenges to work on issues without giving up.