Database Users

[Q] Need to sbf but can't get into Clockwork bootstrap

Managed to get my Droid 2 to a point where it will not go beyond the M screen on boot. I've tried pulling the battery over and over again and cannot get to the Clockwork bootstrap. I've also tried plugging it in and pulling the battery many, many times.
So I figure the next best step is to .sbf this mofo.
I've downloaded & installed rdslite, the USB drivers. Also have the Droid 2 .sbf files. Droid.Co_Downloader.exe pulled down RSD Lite v4.8 though rather than 4.7. And the link to 4.7 is now showing as invalid. Will 4.8 work for what I'm trying to do?
Also, when I plug in my phone RSD Lite never shows anything in the devices table. What are the steps to get my phone to show up? Plug in phone, power on, turn on RDS Lite? The tutorial seemed to be aimed at people who still have working phones in that it has you adjusting setting on the phone i.e. enable debug mode.
Sidenote, I know debug mode is disabled on my phone. Does that mean RSD Lite isn't going to work?
Help!

I think if you pull and replace the battery at the M it should reboot into recovery, and if it won't do that you can always try sliding out the keyboard and booting the phone while holding the X key to see if it will dump you into the stock recovery

Ok, some more reading uncovered hitting the physical keyboard's Up arrow and powering on will take the phone to the Bootloader and once in the bootloader my pc recognized it.
And then RSD Lite showed my device in the table but it didn't show up as the A955 it was Model "S Flash OMAP3630 MI".
Currently flashing DROID2_X6_2.2.20 .sbf, hopefully that pans out.

Thanks, I tried the battery pull thing A LOT of times. Never went into bootstrap. Not sure what's going on there.
I tried the stock recovery but got the Android-exclaimation mark icon which I presume means the stock recovery was F-ed up.
Really hope this sbf recovery works.

Ok, disaster averted.
Looks like rebooting into the bootloader was the secret. Hope that is helpful to someone else who's bricked their phone.
BTW, used RSD Lite version 4.8 and that worked with my Droid 2.

aplus01 said:
Thanks, I tried the battery pull thing A LOT of times. Never went into bootstrap. Not sure what's going on there.
I tried the stock recovery but got the Android-exclaimation mark icon which I presume means the stock recovery was F-ed up.
Really hope this sbf recovery works.
Click to expand...
Click to collapse
Glad you got it working! For future reference if you want the stock recovery, after you hold x and get to the exlamation point, press the search key on the keyboard. (The little magnifying glass) and it should take right Into it.
Sent from my DROID2 using XDA App

Me too!
Search key? Good to know. Man, that could have saved me quite a bit of time I think.
So now that I've restored everyting I'm going to risk it all and install the fission rom again.
It's less intimidating now that I know how to sbf restore. Hopefully I won't need to this go round.

Just follow the instructions as they are laid out and you shouldn't run into much trouble. Also, be sure to let the device sit for a bit after you reboot from clockwork, as it could take a good 15 minutes before it fully boots up the first time, and interrupting that could put you back at square one

Could you add [SOLVED] to your thread title please. Thanks

Help please

hello everyone i am in big trouble,
I was making a custom rom for my home use and i changed some icons. I also accidentally deleted my launcher2.apk file so i have no way of getting to any apps from the homescreen and it just shows a black screen with a status bar on my homescreen. There is nothing i can do and since i wiped by defealt it dosen't have USB debugging on and no service so i can't get a txt and go to the messaging app and then somewhere from there. So i am freaking stuck on a black screen. the lock screen is fine but i also can't get to the bootstrap recovery. I am thinking of doing a a wipe using RSD lite but i tried that a while ago on my dell and it didn't work (a few weeks ago). it would get to 99% and then just stop and say failed. If i get it bricked I would be fine because I could go into verizon and say that my phone just stopped booting on after using it for a while and the battery ran out or something like that but right now it still boots up. What can i do?!!?!?!?!? i desperatley need my phone or my parents are going to murder me (but i guess a new phone would be a good christmass present even though it would be a huge bummer not to have a smartphone and just have a little normal slider phone or something like that). I am supposed to be pretty good with tech stuff since i made roms before except right now i'm stumped since rsd lite usually dosen't work.
thanks,
ljbaumer

If you do SBF then follow these instructions to the letter (I just SBF'd my Droid2 last night):
Get the 2.3.20 SBF file
Get RSDLite 4.8 or 4.9
Install the latest Motorola drivers
Start RSDLite and select the SBF file
Turn on your phone while holding the up key on the keyboard. This should boot up into a screen with just some text
Connect your phone to your computer
Start the SBF
Eventually RSDLite will tell you to manually power up your phone. Your phone should be in a boot loop at the Droid eye logo at this point
Disconnect your phone and pull the battery
Wait 30 seconds or so and put the battery back in. Turn on the phone while holding up on the keyboard
Connect the phone to your computer. RSDLite should say 'SUCCESS' at this point
Disconnect your phone and turn it off
Turn your phone back on while holding the 'X' key on the keyboard
When you get the Android dude with an exclamation point in a triangle push the search key (magnifying glass) on the keyboard
Select both 'Clear cache' and 'Clear data' on from the list. Clearing the data might take a minute or two so just sit tight
Reboot the phone. It might take a few minutes to boot back into stock Blur. You'll get the account setup screen when it's done

thanks for the fast reply. downloading the stuff right now and going to try in 30 minutes once the download is done. the sbf is VRZ_A955_2.3.20.zip right?

Yup. It should contain a file named VRZ_A955_2.3.20_1FF_01.sbf that's 434MB.

Just wondering, how would I sbf my Droid 2 on a MacBook. I just ditched Windows and got a new MacBook Pro and I am trying to figure it out.

I was trying to figure out the same thing but I just gave up so I am moving the files over to my 7 year old dell inspiron 6000 and hoping it will work!

flashing right now..... scared out of my wits.... plzzzz work.....
status: interface Ap-OS: flashing code group 39 executed: 27%
doing some crazy stuff.... this is pretty cool.

Spitemare said:
If you do SBF then follow these instructions to the letter (I just SBF'd my Droid2 last night):
Get the 2.3.20 SBF file
Get RSDLite 4.8 or 4.9
Install the latest Motorola drivers
Start RSDLite and select the SBF file
Turn on your phone while holding the up key on the keyboard. This should boot up into a screen with just some text
Connect your phone to your computer
Start the SBF
Eventually RSDLite will tell you to manually power up your phone. Your phone should be in a boot loop at the Droid eye logo at this point
Disconnect your phone and pull the battery
Wait 30 seconds or so and put the battery back in. Turn on the phone while holding up on the keyboard
Connect the phone to your computer. RSDLite should say 'SUCCESS' at this point
Disconnect your phone and turn it off
Turn your phone back on while holding the 'X' key on the keyboard
When you get the Android dude with an exclamation point in a triangle push the search key (magnifying glass) on the keyboard
Select both 'Clear cache' and 'Clear data' on from the list. Clearing the data might take a minute or two so just sit tight
Reboot the phone. It might take a few minutes to boot back into stock Blur. You'll get the account setup screen when it's done
Click to expand...
Click to collapse
OMG dude your freaking awesome!!!! you just saved my phone!!!
thank you so much!
ljbaumer

No problem.
Sent from my DROID2 using XDA App

[Q] Droid 2 bricked after GB update, SBF will now work for me....help!!

I installed Gingerbread that was recently released by team black hat, it was working perfectly for a few days, then all of a sudden.....im stuck at M logo. So i followed P3Droid's instructions , down loaded all the necessary files and tried to flash the 2.3.20 sbf file and nothing happens. When i connect my phone to RSD Lite (tried 4.7, 4.9) it does not recognize my phone, it says my phone model is sflash, not droid 2 or a955. I went ahead and tried to flash but when it hits 100% it says please manually power up phone and i do....still stuck at M logo. Im ****ed, my phone is a brick, this suck! Everyone elses phone I root works perfect, except mine.....please help me if u can!!

make sure you have the correct moto drivers on your computer and make sure they are for the correct bit of your OS also. whenever i sbf the phone reboots itself.

I got all the updated files...i found it weird that my phone dosnt power up on its own. In rsd lite does it show ur phone model or show it as sflash? Mine shows as sflash, thats what i think the prob is.

evilteam00 said:
I got all the updated files...i found it weird that my phone dosnt power up on its own. In rsd lite does it show ur phone model or show it as sflash? Mine shows as sflash, thats what i think the prob is.
Click to expand...
Click to collapse
Mine shows up as sflash, but the SBF has always worked correctly, even when flashing back from 2.3
Have you ever SBF'd before, and if so, has it worked?
Also, have to tried getting into the stock recovery? Try to, and wipe data and cache and see if that helps any.
Also, you may try uninstalling the moto drivers, rsd, redownload and reinstall them, and also try redownloading the SBF file.

orkillakilla said:
Mine shows up as sflash, but the SBF has always worked correctly, even when flashing back from 2.3
Have you ever SBF'd before, and if so, has it worked?
Also, have to tried getting into the stock recovery? Try to, and wipe data and cache and see if that helps any.
Also, you may try uninstalling the moto drivers, rsd, redownload and reinstall them, and also try redownloading the SBF file.
Click to expand...
Click to collapse
Ive flashed SBF'd SPrecovery a long time ago with my droid 1, it worked fine. Tried uninstalling the drivers sbf file and rsd, then reinsalled them. When I hold X and power my phone just stays stuck on the M logo. Im not sure what im dokng wrong...i followed the steps from here...http://forum.xda-developers.com/showthread.php?t=770224

What sbf are you using? I use the full system sbf from here:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
Try that if you aren't using that one.
Also, what bootloader version do you have? Mine is 2.37
Sent from my Liberated DROID 2

This happened to me, and I almost **** a brick. You need to hold down the power, and X buttons simultaneously, until the exclimation point in the triangle comes up. Then hit the Search button on the keyboard, which is directly below the X. If it's not working flash And again, and make sure you have the correect drivers from Motorola on your PC.
Sent from my LiberatedDROID2 using Tapatalk

AKSurprise said:
This happened to me, and I almost **** a brick. You need to hold down the power, and X buttons simultaneously, until the exclimation point in the triangle comes up. Then hit the Search button on the keyboard, which is directly below the X. If it's not working flash And again, and make sure you have the correect drivers from Motorola on your PC.
Sent from my LiberatedDROID2 using Tapatalk
Click to expand...
Click to collapse
He already said that he cannot get into stock recovery.
Besides, GB stock recovery is different from froyo. Instead of hitting the search button, you have to hit vol up and vol down at the same time. Then use the volume keys to go up and down, and the power button to select.

I think i may need a working droid 2 to make sure the drivers all installed correctly.....a guy was helping me out and he thinks thats the prob. I had 2.37 bootloader and the full system sbf file, that didnt work so I went to bootloader 2.35 with full sbf, and still stuck at M logo. I hope its the drivers cuz before my phone bricked i diddnt have the latest drivers...Gotta wait a few hours till i get another droid 2 to see if that was the prob. Thanks for the suggestions.

Help please! yet another potential brick

Ok so up until yesterday, I was running Liberty 1.5 and things were peachy. Yesterday morning I got bit by the gingerbread bug and decided to install Gingerale 2.0. Installed, fine, done.
After I was running it for a while I decided I wanted to go back to liberty to do a titanium backup to move my old stuff over. Stupid move I guess. To get into recovery I installed bootstrap. Rebooted my phone, Droid eye bootloops ensued from then on.
So I tried SBF'ing and the first first time I did it I got an error on misallocation of RAM. So I did a battery pull, did it again, and everything appeared to be alright. It did the flash, rebooted the phone, and the droid eye logo appeared. However it was still bootlooping at the droid eye. I've tried several different SBF files, making sure all of them were 30.04 bootloader like I have. Boot loops regardless.
I'm kinda at an end point I'm not sure where to go from here. Can anyone plllllease chime in?

After a sbf it is normal to have to do a clear data/factory reset. With phone off, press and hold home and power buttons until the M shows up then ONLY RELEASE THE POWER BUTTON, when the little andy and exclamation pop up you can release home button and press search use volume buttons to move down to clear data then camera button to select.
Sent from my DROIDX using XDA App

Haaa you saved my life dude thank you

[Q] ERR:A5,69,35,00,27 after SBF

This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!

It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App

Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.

what rom was the phone running when you had the original issue?

Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.

I have the same Problem with my Defy+ what can i do?

I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.

Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.

Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.

Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!