10 replies to this topic

[elrostan]

Stock Verizon OG Droid JellyBean (pretty sure,) battery died while out and about camping. I have an external battery so I tried charging (i've used this battery before many times, np) and the phone is stuck at the droid eye animation (stays there for at least an hour.)

 

At my laptop (Win 8): ADB installed - correctly.... I think. When the phone is stuck in boot mode, my laptop sees the device (unknown device, can't browse) and ADB lists the device serial number and I can issue commands, like adb reboot-bootloader. This command works fine, the phone goes into AP fastboot mode, same as if I had gone there manually on the phone. I get:

 

AP Fastboot Flash Mode (S)

0A.77

eMMC Info: Size 16G

To return to normal mode - first press power key to power down

Device is LOCKED. Status Code: 0

 

Battery OK

OK to program

Transfer Mode:

USB Connected

 

At this point, when the phone is in AP Fastboot mode, ADB does not list the device. Commands don't work, etc. When I plug/unplug the USB cable or try other ports, the Transfer Mode: changes appropriately. Windows lists the device as Fastboot CDMA_Spyder S

 

At all times, RSD Lite v6.1.5 does not see the device, I have installed the Motorola drivers (have to be otherwise Win 8 wouldn't see the device at all, right?)

 

Originally, I wanted to try clearing the cache, etc so I could maybe rescue some of the pics, tracks, etc or maybe all. At this point, I'm just trying to see if I can bring it back to life.

 

Any ideas??

[ZKK007]

Since you can get into adb, try this:

Please Login or Register to see this Hidden Content

 

It will return you to stock and potentially wipe everything on the internal SD.

[elrostan]

I'm thinking that won't work because my phone doesn't show up in ADB when I'm in AP Fastboot mode, a prereq for that utility. Am I wrong? The utility says you have to be in fastboot mode and since my phone doesn't show up in fastboot mode... the utility won't work right? While i'm in fastboot mode, commands don't work and the device is not listed in ADB

[Memnoch73]

You may need to find a Win7 PC. Win8 is notorious for have ADB issues.

 

Also ADB and fastboot are 2 different things. Usually ADB is used with the OS booted so that may be why it's not seeing it. In that case the Utility MAY see it.

[ZKK007]

I would try it since your fastboot mode says "USB connected" so it should be able to send/receive data.

 

Make sure you are NOT using USB3.0 since that can cause issues too.

[elrostan]

Well, changed from USB3 to USB2 port and RSD Lite now sees the device as connected. ADB still doesn't show the device when in Fastboot mode but I guess that's okay (Win8 buggy.)

 

With this spark of hope, I'm going to try Matt's utility option #2 first as I'd like to recover some data first (that right there's justification to root & backup like I used to do...) but I'll wipe if I need to.

 

I've read somewhere that you can clear the cache and that may help some devices, how does one do that? Is that something I should try or maybe N/A for my situation?

[Memnoch73]

When you get to the first fastboot screen you should have an option to go into recovery. That will take you to a dead android screen. hit both volumes at the same time to bring up the menu. There you can clear cache and reboot to see if that works.

[ZKK007]

How did you get on?

[elrostan]

Found the cache clear menu option, thanks! Unfortunately it didn't help, I still have the issue.

 

I'm of to Krav Maga for a couple of hours, I'll try Matt's utility when I get back.

 

<fingers crossed>

[elrostan]

I did manage to execute option #2 of Matt's utility, it did not resolve the issue, no change.

 

I'm back from Krav and now my phone charge lvl is too low, Hopefully it will charge while in the boot loop, otherwise I think I'm pooched

 

Unless there's a better way to charge? I had it plugged into the wall but it was off, no white led

[elrostan]

Okay, got it charged. The 1st time i ran option 2 it took barely about 50 sec (and didn't change the boot loop status) so I decided to run a second time. It took several minutes to run but still no fix. I cleared the cache and tried a third time. It was identical to the second round with the same results.

 

At this point, i gave up on trying to save my data and ran option 3. Looked pretty much the same as option 2 except the motorola device manager started itself up and after a bit, the phone completed it's re-boot and went through the initial setup process.

 

It looks like the hardware is working, it's charging, the radios work, as far as I can tell everything is good to go!

 

Thanks to everyone that responded, much appreciated!