Database Users

Can't access recovery!

OK, so I have a D2 that someone gave me. It was completely stock (not rooted), but had all of their stuff on it still so I decided to do a factory restore through the android menus. The process started and the phone got stuck at the "M" logo, I left it for a few hours, and never budged.
I can NOT get into recovery, holding "X" and power on battery or connected to USB does nothing, have tried about 50 or 60 times now.
I can get to the bootloader and flash a new sbf (tried 2.3.20, 2.2.20, and downgrading the bootloader to d2.35) aside from the d2.37 bootloader I don't know of any other sbf's to try untill the GB one leaks, and who knows when that will be. I am using RSD lite 4.9 on win 7 x64, and 2.3.20 does not error out, also it identifies the phone as "s flash omap..." something instead of A955 or droid.
Sorry for the lengthy post, any help would be appreciated.
Edit: I tried flashing the 2.3.20 sbf from an ubuntu live CD with no joy. I just don't understand, i'm not getting any errors with ADB, it completes just fine, so recovery should be there for me to go into. The better part of 2 days trying to figure this out now.

Just a quick question, is recovery included in 2.3.20 full sbf?

Try it on a different computer. That worked for me. S flash is OK. As long as it says connected, you're good. You need to sbf. As long as you can get into Bootloader (2. 37)you can sbf.
Sent from my DROID2 using XDA App

That was the next thing I was going to try, need to get an OS on my old laptop to try, I have been busy so I should get to that sometime before the weekend. Dug out an old OG Droid that had the same issue that I could never figure out too, and got a custom recovery flashed, but no success on the full SBF or restoring a backup. Hopefully it is just this PC that is not playing nicely.
Thanks for the suggestion.

You can't get into recovery after you SBF? Is that what you mean?

wrichards2009 said:
You can't get into recovery after you SBF? Is that what you mean?
Click to expand...
Click to collapse
Exactly, it's like recovery is not there. Powering up while holding X does nothing, all I get is the "M" logo. I've let it sit and eat a whole battery just sitting on the "M". I will try to flash on another computer or two tonight and post my results.

Well I finally had time to try on another computer, and no luck. Used a freshly downloaded SBF, moto drivers and RSD Lite 4.8. Also I hadn't thought to check the logs before, and the FlashErrorLog has 4 errors, ERROR: AP Die ID, BP Die ID, AP Public ID and BP Public ID.
Everything went same as before, RSD completes with no errors. (well almost completes when I use my Motorola branded cord, stops at rebooting phone, and with my wifes LG branded cord, it reboots into the bootloader automatically, strange)
If anyone else has any ideas, I'm just at a complete loss here, willing to try something drastic at this point.

Having a similar problem, so hope you don't mind me piggybacking on your thread. I'm running 2.3.3 rooted on my D2, and I cannot boot into recovery either, but also can't get SBF to recognize my device on any computer. Any ideas?

How to get into Clockwork Mod
Is there a way to enter Clockwork MOD recovery on a rooted phone Manually? I am away from a computer, phone seems to be bricked need to get into recovery MANUALLY ...................

[Q] reboot loop, can't get Windows to see phone to SBF, etc

Okay - I can't seem to find a single thread that has a working solution to this.
Had Gingerale 2.0 on the Droid X. Was acting funny so decided to go up to CM7.1 now that it's supported. Had trouble getting into Clockwork via ROM Manager then via Bootstrap. Was about to try re-rooting (even though it is definitely rooted) but then ran into this problem..
First, when in standard recovery, I could not install the CM ROM because it failed to match the md5 sum (I'm presuming it's an md5). Not sure if that's normal, though, since it's the standard recovery and not clockwork.
After a system reset, which I did read somewhere, now the phone is stuck in a loop. Gets to the "DROID" noise, then the red-eye circle thing, then back to "DROID."
I cannot get the phone to show up on a computer - Win 7 in VM, Win 7 on laptop, Win 7 on desktop - so that I can try doing an SBF on it (which I have never done, but I think I have all the parts).
Thoughts on how I can get it to show up? Or other options?
thanks.

You may need to install drivers if you haven't already.
Try the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App

Drivers are installed. The "new device found" pop up never shows. Just acting as if it's not there.atnall.

kaiyen said:
Drivers are installed. The "new device found" pop up never shows. Just acting as if it's not there.atnall.
Click to expand...
Click to collapse
Try setting the connection type to either 'charge only' or 'PC mode'. Also try cycling through the different options.
I also would definitely recommend going the Linux route via 1kds's bootable SBF distribution.
Sent from my DROIDX using XDA App

The phone doesn't see the computer (any of them) either. The most it does is randomly start doing the boot loop again. If it's looping, by definition I can't get to the "charge only" or "PC mode" screen.
I will consider the linux distribution.

kaiyen said:
The phone doesn't see the computer (any of them) either. The most it does is randomly start doing the boot loop again. If it's looping, by definition I can't get to the "charge only" or "PC mode" screen.
I will consider the linux distribution.
Click to expand...
Click to collapse
Sorry for bad information lol.
The phone will enter bootloader mode successfully though?
Sent from my DROIDX using XDA App

No problem - the hardest thing is that I can't quite find the exact problems I'm having when doing searches. So the "usual" answers dont' seem to apply.
Bootloader mode - not 100% sure what that is. It starts up, I get the "M" and then the "DROID" sound. Then I get the spinning robotic eye thing, then it goes back to DROID. Over and over.
I can go into the standard recovery but not bootstrap nor clockwork (both of which I have installed in the past) and I know it's been rooted successfully.
I have wiped the entire phone while in the standard recovery several times but no luck.
thanks for any help. Worst case, I'm going to Verizon tomorrow and just going to show them it not working over and over, and try to get all my data off of it. Get a new phone. But I'd like to figure out what's up and/or get CM on here eventually.
allan

There's your issue.
Your phone must be in bootloader mode to SBF.
Hold both volume buttons and press the power button (press, NOT hold) and your phone will boot into bootloader mode.
The bootloader screen should show your bootloader version and say 'OK to program'.
From there, simply use RSD Lite or the Linux method to SBF.
After you SBF your device you must boot into stock recovery and format data and cache.
Sent from my DROIDX using XDA App

I haven't tried doing the SBF yet but THANK YOU. Ever reference I got to getting the phone into any kind of mode was just recovery. I had not found this bootloader mode option until now. Just missed it or whatever in other posts!

R2D2 - Bootlooping, SBF failed 0x70BE

Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!

http://droid.koumakan.jp/wiki/SBF
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html

Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!

ezsbf has helped a lot of people
Sent from my MB870 using xda premium

so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas

Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2

did you try wiping cache or data?

delete this

jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up

[Q] (Q)Razr m Rsd Lite problems....

Hi guys, im an idiot and my razr m is stuck at the very end of the stock boot animation. so i have downloaded the fastboot files, put my phone in fastboot mode, but every time i hit "start" on RSD it says, "the phone failed to switch to fastboot mode"
what do i do? thanks so much

ok.........
straw5254 said:
Hi guys, im an idiot and my razr m is stuck at the very end of the stock boot animation. so i have downloaded the fastboot files, put my phone in fastboot mode, but every time i hit "start" on RSD it says, "the phone failed to switch to fastboot mode"
what do i do? thanks so much
Click to expand...
Click to collapse
so i figured out i was using x64, so i went to my desktop, tried the same process. now it is saying, "failed flashing process unknown boot command"(getvar)
any suggestions would be great folks, im pretty new to this, did have a droidx and successfully flashed rsd lite years ago.
Thanks!

straw5254 said:
so i figured out i was using x64, so i went to my desktop, tried the same process. now it is saying, "failed flashing process unknown boot command"(getvar)
any suggestions would be great folks, im pretty new to this, did have a droidx and successfully flashed rsd lite years ago.
Thanks!
Click to expand...
Click to collapse
Are you using the latest version of RSDlite (6.1.4)?
I was trying to work on the Razr M with an old ver of RSDlite and it does not work.

straw5254 said:
so i figured out i was using x64, so i went to my desktop, tried the same process. now it is saying, "failed flashing process unknown boot command"(getvar)
any suggestions would be great folks, im pretty new to this, did have a droidx and successfully flashed rsd lite years ago.
Thanks!
Click to expand...
Click to collapse
you need to remove any lines containing "var" "GetVar" or "oem" from the xml file and boot your phone into fastboot mode by holding all buttons

Droid Pro not being picked up by RSD Lite

I've read just about every thread and no luck. I updated to a CM port by vanillaLVL, and forgot to back up.
I want to use an sbf to go back to 2.3.3 so I can start fresh with a better rom because his rom doesnt have good in call volume and messes up my bluetooth.
So far every thread about fixing RSD Lite will not work for me.
RSD Lite will not recognize my Droid pro, whether I use Bootloader, CWM, or Usb Debugging mode while phone is on. I have tried looking at every fix, but nothing works. Any tips on how to fix RSD Lite, or how to fix my phone to get it back to stock? I tried using update.zips but I always get an error in the build.prop stopping the update.

Cortal said:
I've read just about every thread and no luck. I updated to a CM port by vanillaLVL, and forgot to back up.
I want to use an sbf to go back to 2.3.3 so I can start fresh with a better rom because his rom doesnt have good in call volume and messes up my bluetooth.
So far every thread about fixing RSD Lite will not work for me.
RSD Lite will not recognize my Droid pro, whether I use Bootloader, CWM, or Usb Debugging mode while phone is on. I have tried looking at every fix, but nothing works. Any tips on how to fix RSD Lite, or how to fix my phone to get it back to stock? I tried using update.zips but I always get an error in the build.prop stopping the update.
Click to expand...
Click to collapse
When i BSF mine i used version 5.6, do you have Moto drivers installed? also just in case make sure you are using a 32 bits version of Windows

I think my windows is 32 bit, and I dled the newest Motorola drivers from the site, but still doesn't work :/ my phone can't access stock recovery either, so might that be causing the issue?
Sent from my DROID Pro using Xparent Red Tapatalk 2

Cortal said:
I think my windows is 32 bit, and I dled the newest Motorola drivers from the site, but still doesn't work :/ my phone can't access stock recovery either, so might that be causing the issue?
Sent from my DROID Pro using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Hey dude... Okay to start off ill tell you what you need... you need to download the base drivers from motorola and have a 32 bit windows computer... What you want to do from there is uninstall your previous drivers... reboot your pc then install them... reboot your pc... now comes the tricky part... take your droid and hold down the volume keys and the button on the right side of your phone and while holding all thoes down hold the power down too .. wait about 30 secs or till the lcd slightly lites up and let go a simple menu should pop up on your phone... now plug in your phone and wait for 10 min if nothing shows up unplug it and plug it in with a different cord and if nothing pops up in 5 min open rsd lite and your phone should show up... now browse to your .sbf or your .sbf.zip and start the flashing process (just click start)..... tell me if this works please!!!
Sent from my DROID Pro using xda app-developers app

Hate to sound amateur but sometimes its just the specific computer. I bricked my xprt at my friends house and tried to sbf it with his 32 win 7 laptop and the drivers kept failing.
Sent from my Nexus 7 using xda app-developers app