• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Motorola Droid 1 no signal and will only boot to bootloader

I have a Moto Droid 1 rooted from spf recovery via .zip. I then used Rom Manager to install Clockworkmod Recovery and flash Cyanogenmod 6.0 (Froyo).

It worked absolutely fine for about a month. Then last night, I found my phone upstairs on AC, and it was on the bootloader menu. I restarted it and found it would only boot into the bootloader. I booted into recovery and tried to reboot from there. This worked but when my phone booted into Cyanogenmod, it had no signal at all.

After resetting it a few times, I tried doing a factory reset. The problem persisted. I tried wiping the cache partition. Still won't connect. I rerooted. Still won't connect. I did what I thought was flashing my ROM again, but it didn't seem to work (I'm not sure how I could tell). When I try to restore Nanroid, it says "no files found".

Now it won't boot into the OS at all, just into bootloader.

Wat do?? Is there something important I'm forgetting? Thanks guys.
 
I tried flashing the stock ROM back onto my phone using RSD Lite. It got to 100% and then said FAILED. My phone's screen is still hanging on "SW Update in progress..."

Here's the error code: "Error switching phone to BP pass through mode (0x70BE); phone disconnected"

I tried moving the file to the root of my C drive, too, still no luck.

Is my Droid bricked?

Now my bootloader just says "code corrupt", and I can't boot into the recovery console AT ALL

I know I made a nandroid backup, but Clockworkmod Recovery says "no files found" when I try to restore. Does this mean the nandroid backup was incorrectly made?
 
Upvote 0
When I flashed Rsd lite it also said failed on rsd lite but I just clicked the (show device ) button and I succeeded. For some reason it always says failed but it doesn't. Try to flash the stock sbf again and try clicking the show device button when it says failed. You should be back to stock then and can reroot if you want.
 
Upvote 0
When I flashed Rsd lite it also said failed on rsd lite but I just clicked the (show device ) button and I succeeded. For some reason it always says failed but it doesn't. Try to flash the stock sbf again and try clicking the show device button when it says failed. You should be back to stock then and can reroot if you want.
Just tried this - my phone disappears from the device list but its screen continues to hang on update in progress...

I'm going to try again, I'm thinking I may have used 32-bit drivers, and I'm running 64-bit W7. So we'll see.

Another question. If I take it to the VZW store in its current state (boots immediately to bootloader and says "code corrupt", won't boot into recovery, stock or otherwise) and tell them it "just happened", will they warranty replace it? Or will they laugh in my face?

Nothing, still.

I attatched the error log, it mentions a "super-file". Is the file I'm flashing not the right one?
 
Upvote 0
when i rooted my droid it hung at 99% as well but it actually worked fine for me anyway...
It gets all the way to 100% and then says failed with the following error codes:


15:11:48, October 09, 2010
Line: 517
ERROR: AP Die ID: 0780010190880304000000000400

15:11:48, October 09, 2010
Line: 524
ERROR: BP Die ID: 0000000000000000000000000000

15:11:48, October 09, 2010
Line: 531
ERROR: AP Public ID: ffffffffffffffffffffffffffffffffffffffff

15:11:48, October 09, 2010
Line: 538
ERROR: BP Public ID: 0000000000000000000000000000000000000000

15:17:52, October 09, 2010
Line: 1834
ERROR: Phone[0000]: Error switching phone to BP Pass through mode
File: X:\test_dev_usb\flash\code\flashdll\FlashOp.cpp
Device ID: 0

15:18:02, October 09, 2010
Line: 692
ERROR: Phone[0000]: The "Motorola_Flash" Interface could not be found.

The super-file is not secure and for re-flash;

the phone needs a super-file that is not secure and for reflash.
File: X:\test_dev_usb\flash\code\flashdll\MIFlash.cpp
Device ID: 0

15:18:02, October 09, 2010
Line: 587
ERROR: Flash failure: Phone[0000]: Error switching phone to BP Pass through mode (Error Code: be),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=257
File: X:\test_dev_usb\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones