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

[Q] Nexus one modem seems busted, bricked?

Hi all,
I've bought a Nexus One from a friend that went to US a while ago (I live in Brazil). My N1 was exhibiting an overheating & reboot issue whenever I used the 3g connection.
2 weeks ago, just after a phone call, it rebooted and did not come back. I took the battery out for the night, but still did not come back.
The bootloader is unlocked, but I was using stock gingerbread. I can get into fastboot, but not recovery. I tried the PASSIMG method a couple of times, and tough the flashing did succeed, the phone keeps stuck at the X logo.
The last radio flash was 5.08, when ginger came. Does this means my device is bricked? To make matters worse, it seems I'm out of warranty...any of you guys have any clue to help me? Or is it all lost and I should get a new phone??
Thanks!

If you're booting - you're not bricked. Brick = NOTHING on the phone, no reaction whatsoever to anything, won't turn on.
Anyway, since you have your bootloader unlocked - fastboot flash recovery recovery.img, and then try to boot into recovery, see if it works. Read the Wiki to help yourself.

Hi Jack, thx for the reply!
I already tried that; the flash succeeds, but I cannot get into recovery. If I try to reboot into recovery, it still gets stuck at the X logo.
I understand that brick == nothing at all; but I suspecting that the GSM modem is history. I was already having rebooting problems with it, and now it seems that it's dead and the phone will not boot because of it. Does this makes sense?

Have you tried "fastboot boot recovery.img"?

danger-rat said:
Have you tried "fastboot boot recovery.img"?
Click to expand...
Click to collapse
Just tried it, the phone reboots, but vibrates 7 times and does not boot, still in the X logo...

7 vibrations - means you have some HW problem, and the phone won't boot. Yes, I guess that even though you're not bricked, the phone isn't usable and needs to be fixed/replaced. Sorry.

That was what I was afraid....I had this "7 vibration" stuff happen before, but I was able to get it back on track...
Thx all for the help, time to get a new gadget

[Q] Defy M motorola locked boot and recovery will not open!

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

Ive got problem in a big way

Basically the jist of the story goes like this.. I was on the TBH official full gingerbread rooted OTA and i decided to try out a different rom so i made a backup and flashed it... the new rom i flashed i ended up not like it so i said ok whatever ill just nandroid back to my backup i had made.. so i nandroid back to my backup and im getting crazy force closes everywere and then my bootstrap dosent work anymore
So then i say ok ill just SBF it not a big deal.. So i proceed to flash the official .340 SBF file with RSD and it goes through the entire process... it flashes the entire thing fine and does all the checksum matches ETC and they all pass.. then at the VERY end of the process im talking like 99% done when it says "Switching to BP Pass Thru Mode" it FAILS and stops the entire process... I then proceed to unplug my phone and even if i pull the battery or do anything whatsoever it goes straight to the bootloader screen
I tried flashing it again... it always works and is perfectly fine up until 99% where it says switching to BP pass thru mode and then it fails and is over with... I even tried the gingerbread SBF file and nothing is working and the phones stuck at the bootloader screen with the "Code Corrupt" message
What can i do here? Ive never had problems with RSD and SBFing in the past and its always worked on this machine... Im also a little hesitant to bring it into verizon or something with this problem because its stuck on the bootloader screen which is obviously something im probobly not suppose to even know exists
Also i have no access to stock recovery or anything whatsoever

Joe92T said:
Basically the jist of the story goes like this.. I was on the TBH official full gingerbread rooted OTA and i decided to try out a different rom so i made a backup and flashed it... the new rom i flashed i ended up not like it so i said ok whatever ill just nandroid back to my backup i had made.. so i nandroid back to my backup and im getting crazy force closes everywere and then my bootstrap dosent work anymore
So then i say ok ill just SBF it not a big deal.. So i proceed to flash the official .340 SBF file with RSD and it goes through the entire process... it flashes the entire thing fine and does all the checksum matches ETC and they all pass.. then at the VERY end of the process im talking like 99% done when it says "Switching to BP Pass Thru Mode" it FAILS and stops the entire process... I then proceed to unplug my phone and even if i pull the battery or do anything whatsoever it goes straight to the bootloader screen
I tried flashing it again... it always works and is perfectly fine up until 99% where it says switching to BP pass thru mode and then it fails and is over with... I even tried the gingerbread SBF file and nothing is working and the phones stuck at the bootloader screen with the "Code Corrupt" message
What can i do here? Ive never had problems with RSD and SBFing in the past and its always worked on this machine
Click to expand...
Click to collapse
in the stock recovery do a factory rest...that will fix it

I have no access to stock recovery

Stock Recovery
Home+Power Button
Search to enter the menu and volume up+down to navigate and camera button to select

Ok. Problem, my brother in laws phone is stuck at bootup and stays. Tried to back up, to the back up and still stays stuck. Tried factory reset. And still nothing... Stuck. Any suggestions? Pls help and thank you in advance.
*WALK in the WORD*

SBF
dhaymond said:
Ok. Problem, my brother in laws phone is stuck at bootup and stays. Tried to back up, to the back up and still stays stuck. Tried factory reset. And still nothing... Stuck. Any suggestions? Pls help and thank you in advance.
*WALK in the WORD*
Click to expand...
Click to collapse
Put phone in bootloader mode power+volume down+camera and SBF to 2.3.340

[Q] Droid 2 Bootloader after sbf

Okay, I had bricked this phone earlier when I screwed up the flashing of a custom rom, but figured I'd fix it when I had time. Now when I need it to work, it won't
I have flashed the phone a total of about 15 times (RSDlite, sbf_flash, ezsbf, everything), and every time it goes to the bootloader screen.
I tried factory resetting it from recovery. Recovery and Bootloader mode both work, but I can't seem to boot up the phone.
Once, the phone booted android and the welcome screen was shown, then it shutdown after 10 seconds.
Is there a key combination I can press to boot regular?
And have I maxed out the rewrites to the flash?
Any help would be appreciated

rhcp1253 said:
Okay, I had bricked this phone earlier when I screwed up the flashing of a custom rom, but figured I'd fix it when I had time. Now when I need it to work, it won't
I have flashed the phone a total of about 15 times (RSDlite, sbf_flash, ezsbf, everything), and every time it goes to the bootloader screen.
I tried factory resetting it from recovery. Recovery and Bootloader mode both work, but I can't seem to boot up the phone.
Once, the phone booted android and the welcome screen was shown, then it shutdown after 10 seconds.
Is there a key combination I can press to boot regular?
And have I maxed out the rewrites to the flash?
Any help would be appreciated
Click to expand...
Click to collapse
What sbf file are you using?

These
Albinoman said:
What sbf file are you using?
Click to expand...
Click to collapse
1FF-p2a_droid2_cdma_droid2-user-2.3.3-4.5.1_57_DR2-31-110719-release-keys-signed-Verizon-US.sbf
VRZ_A955_2.3.20_1FF_01.sbf
and EZSBF 1KDStaz_D2_4.5.601.iso

There's a couple of us with this problem. See my thread just a few down from this. Not sure what is going on. I've tried everything, eventually just settled on buying a DroidX instead of waiting for a fix.

I can get to recovery and bootloader, the problem is it won't boot

Have the same problem, you should be trying to get back to an earlier SBF, if you upgraded to 2.3.4, give up, still has no solution, since the SBF 2.3.4 has not leaked voi