Hi all,
Short version: Need to get phone in fastboot mode. Device OS is bad. Holding power + volume down will not bring up the fastboot menu. Suggestions? (more details below).
Long Version:
A friend of mine gave me his bricked Droid X (MB810) and told me I could have it if I could get it working (he upgraded to the X2 when this bricked). The phone died when it was receiving an update from Verizon. He had not modified or hacked it any way before giving it to me.
I have flashed the device with a list of SBF files using RSDLite 5.6. For most of the SBF files, the phone just sits at the motorola boot logo. Version 2.3.32 gets to the android/exclamation point screen where pressing 'search' brings up the 'Android system recovery (3e)' screen with the error messages 'E:Can't mount CACHE:recovery/command' and 'E:Can't mount CACHE:recovery/log'.
I have spent hours tracking down solutions to those two errors with no luck.
Tinkering and reading on the web for the past 5 days has left me with the supposition that the radio isn't flashing correctly. Directions for flashing this part of the device say I need to fastboot the device and communicate with it over ADB. Multiple places on the web say to get the Droid X to fastboot either do some stuff in the OS (which I can't do because of no working OS) or boot the device while holding down the power + volume down buttons. This does not work, I always end up back at the android/exclamation mark.
The phone is probably bricked permanently, but it was a free phone and I am willing to put some time into it.
Thank you in advance.
I don't believe that our Droid X's can access fastboot mode. Any recovery that has to be done must be done through SBFing.
I would keep trying to SBF.
Sent from my DROIDX using XDA App
1. Hold Camera + Volume Down + tap Power to bring up the bootloader.
2. Connect to PC and SBF
3. Once RSDLite shows "rebooting" and the phone says "SW Update complete," the phone will flash off. Hold the power and home keys when this happens.
4. Once the M logo comes up, release the power and continue to hold the home key
5. wipe data/cache.
6. Reboot.
You (typically) cannot boot to any other bootloader but the one used for mainly SBF. It's locked and encrypted. I assume you're coming from a Samsung or HTC device.
mxgoldman said:
1. Hold Camera + Volume Down + tap Power to bring up the bootloader.
2. Connect to PC and SBF
3. Once RSDLite shows "rebooting" and the phone says "SW Update complete," the phone will flash off. Hold the power and home keys when this happens.
4. Once the M logo comes up, release the power and continue to hold the home key
5. wipe data/cache.
6. Reboot.
You (typically) cannot boot to any other bootloader but the one used for mainly SBF. It's locked and encrypted. I assume you're coming from a Samsung or HTC device.
Click to expand...
Click to collapse
Thank you! I will try this tomorrow. I had to leave the phone at work where there is a lithium battery charger.
This is actually my first smart phone, I am learning quite a lot trying to fix this. Jumping into the deep-ish end.
mxgoldman said:
1. Hold Camera + Volume Down + tap Power to bring up the bootloader.
2. Connect to PC and SBF
3. Once RSDLite shows "rebooting" and the phone says "SW Update complete," the phone will flash off. Hold the power and home keys when this happens.
4. Once the M logo comes up, release the power and continue to hold the home key
5. wipe data/cache.
6. Reboot.
You (typically) cannot boot to any other bootloader but the one used for mainly SBF. It's locked and encrypted. I assume you're coming from a Samsung or HTC device.
Click to expand...
Click to collapse
Once again thank you for taking the time to write, but I'm a little confused now when I look through your directions.
These look like directions for loading a new SBF file, not for accessing fastboot. I need to connect to my phone through ADB and to do that I need to turn on fastboot. The bootloader works fine on the phone.
magnet_man said:
Once again thank you for taking the time to write, but I'm a little confused now when I look through your directions.
These look like directions for loading a new SBF file, not for accessing fastboot. I need to connect to my phone through ADB and to do that I need to turn on fastboot. The bootloader works fine on the phone.
Click to expand...
Click to collapse
The Droid X cannot boot into fastboot mode. You will have to follow the directions listed above to SBF. SBFing will accomplish what you are hoping to do with fastboot mode.
A little more info:
SBFing returns the device to pure stock, just like you took it out of the box for the first time. Being able to SBF is a failsafe, meaning no matter what happens to a device at the software level, and SBF will always return a device to stock if done properly.
I hope I have given you enough information to get your device working.
infazzdar said:
The Droid X cannot boot into fastboot mode. You will have to follow the directions listed above to SBF. SBFing will accomplish what you are hoping to do with fastboot mode.
A little more info:
SBFing returns the device to pure stock, just like you took it out of the box for the first time. Being able to SBF is a failsafe, meaning no matter what happens to a device at the software level, and SBF will always return a device to stock if done properly.
I hope I have given you enough information to get your device working.
Click to expand...
Click to collapse
Well thanks for the info, I have tried this solution along with many others, installed the software on another laptop, verified the SBF files with MD5, and I always end up back in the same place. I'm 99% certain the phone has a hardware issue.
The end result of everything results in the following error message on the 'Android system recovery (3e)' screen:
'E:Can't mount CACHE:recovery/command'
'E:Can't mount CACHE:recovery/log'.
Wiping the data/cache results in the errors changing to:
'E:Can't open /cache/recovery/command'
Thanks again for the help. I might tinker with it on and off for the next few days. If I find a fix, I'll be sure to come back here and post it.
Sorry to resurrect an old post... but did you get it to work? Normally RSD Lite puts you into bootloader mode automatically but maybe it can't in this case. To do it manually you:
a) pull the battery.
b) put it back in.
c) start holding down both volume buttons (right side)
d) turn it back on
e) when the screen flashes let go of the buttons, you should see a message saying "Bootloader" on it
f) Plug in to the USB. Now RSD Lite can go to town - of course this assumes you have the drivers installed.
Also - did you call Verizon or Motorola? I did because of recent trouble and they seem to believe their updates never break anything. Of course unlike your friend I have rooted and rommed my phone... but it wasn't until I installed their update that my data connection broke.
No I never got it to work. I tried all that and more. In the end I passed it to a friend who had done bootloader work on this particular model of phone and he couldn't get it to work (he even used a software version that he had used recently to do his phone). It has to be a hardware failure at this point. I'll probably sell it for parts. I don't see Verizon or Motorolla being to keen on helping me since I go the phone second hand, have attempted to modify it since acquiring it, and it's not tied to my Verizon account.
netraven5000 said:
Sorry to resurrect an old post... but did you get it to work? Normally RSD Lite puts you into bootloader mode automatically but maybe it can't in this case. To do it manually you:
a) pull the battery.
b) put it back in.
c) start holding down both volume buttons (right side)
d) turn it back on
e) when the screen flashes let go of the buttons, you should see a message saying "Bootloader" on it
f) Plug in to the USB. Now RSD Lite can go to town - of course this assumes you have the drivers installed.
Also - did you call Verizon or Motorola? I did because of recent trouble and they seem to believe their updates never break anything. Of course unlike your friend I have rooted and rommed my phone... but it wasn't until I installed their update that my data connection broke.
Click to expand...
Click to collapse
After re-reading what you said the problem you're having isn't really all that similar to mine other than the "broke after update" thing...
Anyway, I talked to Motorola for my issue and they offered to fix it even though it's out of warranty - I hate being without a phone, but if I can't fix it myself then I may take them up on it. So you might just give it a go - after all it's THEIR update that broke the phone, not your tinkering.
mxgoldman said:
1. Hold Camera + Volume Down + tap Power to bring up the bootloader.
2. Connect to PC and SBF
3. Once RSDLite shows "rebooting" and the phone says "SW Update complete," the phone will flash off. Hold the power and home keys when this happens.
4. Once the M logo comes up, release the power and continue to hold the home key
5. wipe data/cache.
6. Reboot.
You (typically) cannot boot to any other bootloader but the one used for mainly SBF. It's locked and encrypted. I assume you're coming from a Samsung or HTC device.
Click to expand...
Click to collapse
When I do that, I see:
Code:
Bootloader
D0.11
Battery OK
OK to Program
Connect USB
Data Cable
Is this the "fastboot"?
For the millionth time there is no fastboot
:banghead:
Reread how to sbf.
If you feel comfortable enough do it again.
Sometimes you have sbf 2-3 times.
First time I sbf'd was my d2.
I had a major freak out because it would not work!
Wtf!!!
Viola! Third times a charm!
If I remember right it came up the same as what you posted.
Just make sure you have at least 50%
Battery charge and start over. Not from where you left over. Reboot PC is good placebo too. Lol.
Any ways start over as if its your first time sbf the phone.
As I said it may take several tries, be patient, take your time.
You may run into:
Phone bootlooping, reboot with out rebooting, other silly things.
Take out battery start over.
Rsd SHOULD pick up where it let off.
Keep us posted !
Sent from my DROID X2 using Tapatalk 2
Neo3D said:
When I do that, I see:
Code:
Bootloader
D0.11
Battery OK
OK to Program
Connect USB
Data Cable
Is this the "fastboot"?
Click to expand...
Click to collapse
This is your bootloader mode, where you can SBF. You have an odd bootloader version. Are you sure that's what it read?
Sent from my Galaxy Nexus using Tapatalk 2
infazzdar said:
This is your bootloader mode, where you can SBF. You have an odd bootloader version. Are you sure that's what it read?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yep, that's exactly what it read.
I've tried sbf'ing 9x now and I still get fail each time. I have tried it 3x each with RSD Lite versions 4.9, 5.0, 5.6 (rebooting PC after each un/install).
I am trying to sbf 2.3.4 so I can install Liberty ROM. I got the sbf from here:
http://forum.xda-developers.com/showthread.php?t=1703640
Downloaded it 2x to make sure the download is not corrupt.
Any ideas?
That link is for Droid X2 SBF files. You're posting in a Droid X forum. So do you have the X or the X2?
Sent from my Liquid X
newmanx4 said:
That link is for Droid X2 SBF files. You're posting in a Droid X forum. So do you have the X or the X2?
Sent from my Liquid X
Click to expand...
Click to collapse
I have the Droid X2 Global.
Neo3D said:
I have the Droid X2 Global.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ftmfl.....
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Neo3D said:
I have the Droid X2 Global.
Click to expand...
Click to collapse
I can't be of any help with that.
Sent from my Liquid X
Neo3D said:
Yep, that's exactly what it read.
I've tried sbf'ing 9x now and I still get fail each time. I have tried it 3x each with RSD Lite versions 4.9, 5.0, 5.6 (rebooting PC after each un/install).
I am trying to sbf 2.3.4 so I can install Liberty ROM. I got the sbf from here:
http://forum.xda-developers.com/showthread.php?t=1703640
Downloaded it 2x to make sure the download is not corrupt.
Any ideas?
Click to expand...
Click to collapse
I can't offer much assistance with an X2, but RSD Lite has never worked well for me. I recommend using the Linux method to SBF, if at all possible.
Sent from my Galaxy Nexus using Tapatalk 2
I have to admit that I laughed extremely hard after reading this topic thread when I saw the Star Trek pictures. I needed that.
Anyway. I might be able to help if you still need? I have both the Droid X and X2.
I'm actually restoring my Droid X via the Bootloader (who the other fellow views as the Fastboot) using RSD Lite 5.7 to SBF .621.
Bam. I just completely restored my original Droid X for my son. I'm visiting with him about a day's ride from home. Thanks for those quick RSD Lite instructions.
Anyway. I plan to tinker with my Droid X2 once I get home this weekend, so perhaps I could try helping you while I restore and tinker with my X2.
Sent from my Motorola Droid RAZR Maxx running JellyBean RAGE ROM 2.2 and using the Tapatalk app.
Related
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
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.
good night friends!
I'm here asking for this help not for lack of looking for the solution, sorry my bad english, I'm from Brazil and I
defy caught in a bootloader, I tried almost everything I found here in the forum, but most of the problems is
reset solved by making the recovery, but in my defy the recovery does not open, the flash works only power + vol up, already
I spent several roms to no avail, could someone help me run my recovery? grateful heart
list of roms flashead
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FFJORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbfz
JORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbf
JRDNEM_U3_2.34.1_DEBLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA02B.0R_USAJORDANRTCEE_P029_A019_HWp3_Service1FF.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTHKTW_P021_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_3.4.2_164-003_VFBLUR_SIGN_SIGNED_USAJRDNEMARAB1B8VFFR03A.0R_PDS03C_USAJRDNFRYOVFFR_P028_A014_M004_HWp3_Service1FF.sbf
Motorola_Defy_Nu___Android_2.2_FroYo
shadow_defy_2.3.3_85_Orange
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
mmec2 said:
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
Click to expand...
Click to collapse
I really can not, no way to go to the screen with the robot android! he goes right on the logo motorola M!
can it be hardware problem?
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
farsight73 said:
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
Click to expand...
Click to collapse
I'm using motorola rsd 4.9 with updated drivers, what happens is install the rom normal after reboot gets stuck in the Motorola M logo, the software update site does not recognize my phone, do all these roms that I would be no my phone?
im tried this roms now
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
3.4.3_11-Stock.UKTmobile_BLUR
but no results!
don't worry about it, dude.
maybe you can try the way followed:
1.power off your defy;
2.remove the battery from the phone;
3.plug the usb cable into the phone without battery;
4.open RSD and chose one of the roms your listed, but 3.4.2-177-005 NORDIC prefered,
5.take the battery into your phone, now your can see the "connected" on RSD;
6.click the "start" button to flash;
7.wait the phone reboot completely, usually it'll reboot.
if not reboot, remove and on your battery, power on your phone, then press the "volume - and power" botton together, you can enter the robot screen, press volume up and down botton together, usually you can enter the recovery, then chose wipe 3 and 4, totally you can save your defy~~
Be sure to have enough battery while flashing..
Get the phone into bootloader (hold volume down when switch on) and flash an SBF like one from the list you've attached using RSD lite. Surely you have used RSD Lite before?
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
jdearauj said:
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
Click to expand...
Click to collapse
This same friend, I have the same problem, is this a hardware problem? I move the roms but not normal
Vol I login recovery - + Power key
http://forum.xda-developers.com/showthread.php?t=966537
Try flashing nordic, if fails arabic, if fails, 2.3.3, if fails probably corrupt nand broken hardware.
Before and after every flash always try to access recovery (volume down) and WIPE. reboot and wait crossing fingers, if it fails to boot flash next sbf, try to go recovery + wipe; reboot, cross more fingers; if fails to boot try next sbf and repeat.
The reason for this is that you can flash a lower version but it wont boot, so you have to flash a higher and higher version until you get one that works.
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
zyxwvut said:
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
Click to expand...
Click to collapse
OMG Exactly!!!! i have same problem and nobody seems to be able to tell me what to do, they keep saying same thing about trying various SBF's and Vol down + power method. No matter what SBF file I successfully flash with, i cannot get into boot recovery mode.
I have heard before from desperate users that they were able to revive their phone by flashing a full 2.3.4 sbf. This however comes with downsides of not being able to downgrade to froyo by flashing ANY froyo sbf's. There is a way to downgrade back to froyo but its a dirty method. Even after downgrade you can't just flash a sbf, you will always need to restore nandroid and flash fixed sbf
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
ssfirme said:
Well somehow i bricked my phone,I'm stuck on the Motorola logo,i try using sbf but it does not recognize my phone, oh yeah i had install cm7 diet rom witch really would not let me get into recovery cuz it kept saying that my phone was a htc bravo? So i try a droid bootstrap to see if that work and that's when my phone got bricked, can someone please help,and yes i tried going into recovery by pressing the volume and power button and it takes me into recovery and brings me to the Android and exclamation but that's it, even if i pressed the lower right corner nothing happens
Click to expand...
Click to collapse
Press both volume buttons on the screen with the android and exclamation mark. That'll take you to stock recovery where you need to wipe data and factory reset.
If you have to flash the sbf again, try using sbf_flash on Linux. It'll flash in times where RSD won't recognize your phone.
Linux Live\sbf_flash tut
sbf_flash binary is in attachments
Only use Defy 2nd-init for recovery
(and once its installed, steal /system/bootmenu/* and /system/bin/bootmenu from Defy CM9 from June 5th on up -- touch bootmenu is pretty awesome; replacing the bootmenu isn’t for the feint of heart.)
the only problem is i dont have linux i have windows 7
Use rsdlite sri I don't have a link on me
Sent from my Galaxy Nexus using XDA
Had same type of problem on Friday. Followed this post http://forum.xda-developers.com/showthread.php?t=1559109 now I'm back up and running.
ssfirme said:
the only problem is i dont have linux i have windows 7
Click to expand...
Click to collapse
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
yes i have it in bootloader mode
Did you install everything before plugging phone in?
Try uninstalling everything motorola related and reinstalling just the drivers....On a previous Win7 install nothing was recognized, but on a reinstall of the entire system it worked fine and still does. I still recommend the Linux way over RSD because it will flash your phone regardless, provided you can access the loader.
I still haven't gotten native tethering to work with Windows, but then again, I quit trying sometime around December or January.
ssfirme said:
ok i install the motorola usb drivers and start up rsd lite but it does not regocogize my phone
Click to expand...
Click to collapse
This is for all those people who are having trouble flashing with RSDlite in Vista & WIndows 7.
If I am right, RSD lite does not seem to recognize the sbf file after you select it and instead the "start" button remains grayed out.
If that's the case, here the solution:
I had a similar problem and sucessfully used the command line parameters for RSDlite to force a flash. I managed to get a signed/unsigned firmware installed.
You need to copy the firmware you want to flash into the RSDlite directory in your program files folder.
Make sure you are in bootloader mode first.
Then, open command prompt and "cd" to the RSDlite directory
eg:
> cd C:\
> cd Program Files
> cd motorola
> cd RSDlite
>
now for the flashing type:
> SDL.exe -f xxxx.sbf -t 2
where xxxx.sbf is the firmware you are flashing to the phone.
flashing will begin shortly afterwards.
It worked for me, but in the end, show FAIL STATUS.
skeevy420 said:
I dual boot between the two
If you have a blank cd and a usb drive\sdcard you can just use a Linux Live environment -- you never install Linux at all -- and you can use sbf_flash from there.
RSD Lite version that works and tutorial
And since it hasn't been mentioned yet, holding volume up + power on boot access the boot recovery to flash sbf's. Just make sure you have at least 50% battery before flashing or you might get an actual brick.
What your dealing with is nothing more than a recovery screw up. I had the same problem last night installing touch recovery -- it wiped /bootmenu/ instead of installing to it. Solution is to flash sbf, reboot, wipe data/factory reset from stock recovery, reboot, eebluroffee at first screen, root, enable non market apps, Defy 2nd init flash something that's better than stock.
Click to expand...
Click to collapse
Thank you sooooooooooooooooo much!
After several hours of messing with my brothers Bravo, I finally got it working by following your instructions.
Really: I'm speechlees man.
hard bricked my phone
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
dzdonce said:
hello. i'm looking for any help to this issue: i believe i hard bricked my bravo somehow. it was running one of the first MIUI rom for two or more years. but became slow and laggy thru last months. and the other day it just freezed while i was browsing the call log. no reaction to the pover button at all, had to take out the battery. now it gives no reaction to any combination of button presses ( power; vol up + power ; vol down + power), the only signal what see is white LED light when į connect the phone to the PC. When phone is connected to the pc freshly, and when i press Vol down + Power, Windows 7 releases "clink" sound and device manager tries to show that "Motorola USB Device" is connected, but quickly disapears with another Windows sound. RDS lite 5,0 doesnt recognize phone too.
Is there any chance to bring this phone alive? any advise will be appreciated.
p.s. english isn't my native. sorry for the mistakes
Click to expand...
Click to collapse
Not sure if this will help since I did not watch the video myself, but a quick Google search gave me a video describing how to take a Motorola USB cable and modify it to unbrick a phone. I did not watch the video yet so I don't know how relevant it is to your problem. But just by looking at the video preview it looks like the difficulty level may be pretty high... Here is the link:
http://m.youtube.com/watch?v=XwwI_6doBWk
Sent from my LG-D415 using XDA Free mobile app
so heres my dilemma, my gfs droid 2 screen stop responding (cant get it off lock screen). I need to erase everything before I send it back to where I got it, but i cant get into thephone to do a reset and when i boot into recovery, the magnifying glass doesnt seem to work so i cant get past the exclamation point. Is there any other way that I could wipe this phone?
When you see triangle, ! , and android andy
Press both volume buttons, that changed with gb
Sent from my DROID3 using xda premium
what to do when it still won't reboot?
sd_shadow said:
When you see triangle, ! , and android andy
Press both volume buttons, that changed with gb
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I got this far with my d2. Thanks. After choosing the wipe and reboot option it still boots only to the moto splash screen. it dims a bit after a few seconds and that is all she wrote. I've left it there for an hour.
Any moves to make now? I'd like to get it working. I am willing to learn whatever it takes.
Thanks.
flash sbf
try ezsbf in my list
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
don't leave phone on, if it doesn't boot in 5mins it is not going to boot
and battery will not charge like that
Sent from my XT894 using xda premium
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
is it bootloader D0.11 or D2.37?
help unbrick droid 2
sd_shadow said:
How to Enter Bootloader: (used to flash .sbf recovery images)
Power down the phone.
Slide the keyboard out.
Press and hold the up arrow (↑) key.
Press the lock/power button.
Once the SBF loader screen pops up, release the up arrow key.
is it bootloader D0.11 or D2.37?
Click to expand...
Click to collapse
This is a bootloader screen I get, and it gives me no choices to arrow down.
Bootloader
D2.37
Code Corrupt
Battery Low -- flash
Cannot Program -- flash
This happened after an OTA update, and now I am new to this forum, and trying to get this phone back working, Any help would be greatly appreciated.
I have adb loaded, and have used it to root, su with clockworkmod a CDMA Sprint phone to put into the Page Plus service network, so I have some experience - mostly willing to try just about anything.
The battery should be charged up.
I got this once, after leaving the phone sit for about two days, battery out.
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
I mainly use this phone for VoIP service, but was eventually going to try to put Cyanogenmod 7 on it, and then this happened.
Any advice / help / pointers to somewhere, or something would be greatly appreciated.
s1x8 said:
This is a bootloader screen I get, and it gives me no choices to arrow down.
Bootloader
D2.37
Code Corrupt
Battery Low -- flash
Cannot Program -- flash
This happened after an OTA update, and now I am new to this forum, and trying to get this phone back working, Any help would be greatly appreciated.
Click to expand...
Click to collapse
update failed
I have adb loaded, and have used it to root, su with clockworkmod
Click to expand...
Click to collapse
phone needs to be complete stock or update will fail
a CDMA Sprint phone to put into the Page Plus service network, so I have some experience - mostly willing to try just about anything.
The battery should be charged up.
Click to expand...
Click to collapse
usually battery will not charge, when the code is corrupted
I got this once, after leaving the phone sit for about two days, battery out.
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
you can try flashing 1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf.zip with rsd lite hopefiully the battery is charged enough,
if flash fails because of low battery you will need on of the following
Spare Battery Charger for Motorola Droid 2
a charged spare battery
TBH Factory Adaptor
I mainly use this phone for VoIP service, but was eventually going to try to put Cyanogenmod 7 on it, and then this happened.
Any advice / help / pointers to somewhere, or something would be greatly appreciated.
Click to expand...
Click to collapse
Thank you, and another question for the droid 2
I can't seem to get the drivers to work, I've tried about everything but booting into XP mode - not sure how to do that, as I am on a Windows Vista machine. Any advice, or process for that? I've tried it as Admin, and also a User, but no progress. The drivers are loaded through executing the msi file, but when I plug the phone in the computer doesn't detect phone, and the drivers don't show up in device manager, either.
win 7 64bit?
try Motorola Drivers Installing and Troubleshooting
---------- Post added at 12:41 PM ---------- Previous post was at 12:40 PM ----------
right vista, try the link
s1x8 said:
I can't seem to get the drivers to work, I've tried about everything but booting into XP mode - not sure how to do that, as I am on a Windows Vista machine. Any advice, or process for that? I've tried it as Admin, and also a User, but no progress. The drivers are loaded through executing the msi file, but when I plug the phone in the computer doesn't detect phone, and the drivers don't show up in device manager, either.
Click to expand...
Click to collapse
Spare battery charger on the way!
Also, I ordered a new battery, the old one, was, well, old, and could not hold a charge long enough to get through the flashing step. Once I figured this out, I was able to flash the phone, and then perform a factory reset, and it is back to the original. It wouldn't take the flash for CM but the phone is rooted now.
Thank you for your help!