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
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Hey there,
I had something similar back when I tried to root my evo 4g the first time, what I did was go to the carrier store (in my case Sprint) and acted like one day just started to act weird and they replaced it for its "factory defects"
P.S. Some stuff I learned was that I damaged the usb port.
GOOD LUCK
Sent from my beloved EVO 4G
rpierce said:
My phone is rooted and i cannot enter the custom recovery menu. I can get to the dx recovery. Tried sbf but rsd lite nor my pc will recognize the phone. PC says that the driver cant be located in bootloader menu even tho i do have the moto drivers installed. any suggestions on how to get it to work to run the sbf. I've tried all delete options in recovery menu probably screwed myself.
Click to expand...
Click to collapse
a trick to get into clockworkmod recovery, turn the phone off and plug into the wall, try to turn on....well not really try, turning on the power button should boot to cwm
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Bricked in need of help
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Macificient said:
heres the problem. i was running shuji rom on rooted gb.596. attempted to full sbf back to 3.3.340 after sbf completed successful i was unable to access recovery. i tried holding power and home button, but all i get is a android with exclamation point inside a box. tried holding search button as i usually do. but i can not wipe data or factory reset. Ran rsd lite 4.8 with full sbf 3.3.340 again and im still stuck at the sturdy click logo(custom boot logo). i would greatly appreciate any advice. or a link to wipe data from my computer.
Click to expand...
Click to collapse
U might try pushing the power button instead of the search button when the droid and exclamation mark are on screen. Hope that helps
TappaTappaTappa
sanjeeva7 said:
I have a paperweight and are in desperate need for help.
I was running 2.1 and rooted using the birdman method. So finally decided to upgrade to GB.
RSD Lite 4.9 - everything but text messaging was working on .602
Reflashed with .340 - text messaging not working but all apps worked fine.
Upgraded to RSD 5.4.4 and now my phone is a paperweight. SBF gets to the very last step and fails. Error switching phone to BP Pass through mode (0x70BE)
So go back to RSD 4.9 and try to flash sbf - same error
Created a linux cd to try and sbf GB.
Can't post links so world wide web dot droidxforums dot com slash droid-x-sbf slash 23638-linux-solution-your-windows-rsd-lite-problems dot html
It appears to complete with no errors, the flash completes, the cd boots into linux.
Now my phone is stuck at Bootloader 29.01. Can't do anything. I can access recovery but wipe, cache, factory reset just brings me back to the bootloader screen.
Click to expand...
Click to collapse
U might have a corrupt file missing something... try downloading the sbf file from droidmodderx's website he's got sbf for froyo and gb
TappaTappaTappa
Did you upgrade through SBF, or OTA?
What is your bootloader version?
Sent from my DROIDX using XDA App
You can try the .602 sbf linux boot disk found HERE
It works every time for me and on any computer (that can boot from a cd)
D.
sounds like, judging by your bootloader version...you may be needing to find the 2.1 sbf, flash to that, take the OTA to gingerbread.... and you may have a little more luck with current roms once your bootloader is 30.0#
Just SBF. That will fix your trouble. Almost Impossible to "Brick" the DX.
Current Situation:
When I say bricked, I mean BRICKED in all caps. The phone is completely unresponsive. If I try to turn it on – no good. If I try to put it in bootloader mode – no response. If I hold the volume button down and depress the power – no menu displays. I get no ‘M’. I get nothing. Except…
If I fire up RSD Lite 4.9 and plug in the phone, it does recognize something. Under model it displays “S Flash OMAP3630”. If I load up an sbf file (I’ve been following Higgsy’s incomparable “How To” guide - http://forum.xda-developers.com/showthread.php?t=853674 and using the generic UK sbf file he recommends) and depress “Start” within RSD Lite, the phone will display “SW Update In progress…” in white blocky text. RSD Lite says it’s executing and, after several minutes will display a Status of “Finished” and a Result of “PASS”. On the phone, the screen goes dark but a white notification light displays. While the phone is still plugged in, I can depress the power button on and off and RSD Lite will recognize it’s there (if it’s on) or not recognize the phone is there (if the power is toggled off).
Note that the battery is fully charged.
I’ll give you a little background info:
Background:
I purchased Defy phones for my wife and me for Christmas. Her’s is working fine, is unrooted, and has only a few apps beyond stock (Angry Birds of course!). But of course I had to play with mine. All went well until I (stupidly) installed the latest T-Mobile update which removed my root access. This was not acceptable to me as I had overclocked my phone for performance purposes. I had a really hard time getting root access back until I at last found a version of SuperOneClick that did the trick.
By this time I had reset the phone back to factory settings. So I thought “Well, I might as well flash some cool ROM”, so I flashed a Gingerbread themed Froyo cooked up for the Defy. Unfortunately, it didn’t work (for whatever reason). I was stuck at the dreaded ‘M’.
Next I started following Higgsy’s guide (as mentioned above) but I guess I screwed something up because now the phone is totally unresponsive except as detailed above.
So where do I go from here? Some possibilities:
Flash T-Mobile 2.2 test sbf?
Link?
Flash Original SBF?
Link?
I’ve still got my wife’s phone which is working perfectly fine. Is there a way to copy files from her phone to my dead phone and get some life?
Do you guys have some other steps you’d recommend?
I’d really like to get my phone working again and would much appreciate the help. Many thanks in advance.
(Note that I’m a Noob so please don’t assume I know anything!)
(Yet another note: I'm in the USA.)
Which .sbf's and in which order did you install them?
The same happened to me after I'd flashed the 3.4.2 sbf, then tried to downgrade back to 2.34. it went blank and I had to reflash 3.4.2 again.
If you've flashed 2.51 or 3.42 then you can't downgrade from them. So the fix would be to flash the same rom again.
I have the same problem and this how i fix it
1.http://forum.xda-developers.com/showthread.php?t=892026&highlight=low+battery your phone will show in rsd lite
2.flash http://forum.xda-developers.com/showthread.php?t=933555 with him you get a error that can not be installed
3. disconnect phone from USB and remove the battery
4. Replace the battery in the phone and power up, and phone immediately go into the bootloader
5. Flash bootonly http://forum.xda-developers.com/showthread.php?t=899450
6. and finaly flash http://forum.xda-developers.com/showthread.php?t=922430
it works for me
sorry for bad english
Solved
I flashed http://forum.xda-developers.com/showthread.php?t=922430 per your suggestion and I'm now up and running. Thank you.
Motorola Defy bricked
hi
i have a question about my defy. The white led is still shining but there is no connection to the pc. I connected via USB-cable.
pls HELP!!!!!
I have a similar issue as the OP..
I originally rooted the phone using simpleoneclick... then I overclocked it using setvsel...
it was running fine for an hour or so, and then I ran quadrant (several times over the course of the hour) and the final time, it rebooted during the middle of a test, and then it would just keep looping the bootup moto logo and "android" screens.
at that point I could still enter the bootloader and recovery screens. I tried wiping data and resetting to factory defaults with no avail.
Finally I followed a thread on flashing a new rom to the phone with RDSLite and the uk rom. After getting it to finish flashing and it showing a 'Finished' and 'PASS' status as the OP mentioned, te phone now no longer responds. Power button does not trigger the screen to go on, regardless of if I try to press the volume buttons with it or not.
The only response I get from it is when it is connected to the computer, the white led turns on, and the computer (and rdslite) recognizes it. I can still flash it with rdslite and the screen turns on displaying the SW update In progress message...
but that's about all I can get it to do.
Any help and advice would be greatly appreciated
edit: I should also mention that after the uk 2.21 rom I've also tried the china 2.2.1 roms.... Should I also try flashing the 2.51 uk version as well?
Okay, I tried a few more roms and this one "JRDNEM_U3_3.4.2_117-00..." has everything back up and running...
however now i'm running into the issue of apps that i've 'downloaded' not actually installing...
bricked
same problem here. rsd can detect my phone but still failed flashing. i changed and renamed the /sbf but still doesnt work... please help
MB525 Defy Bricked
MB525 Defy bricked and rsd cannt detect my phone failed . ... please help
its dead. Actually i uninstalled busybox and in this process all the system files also deleted by busybox. now phone is not starting. if anyone can suggest. I was using MIUI rom. can any one make it alive again.
[email protected]
. ....please help
Same problem here, but my phone is only detected by a friend's laptop. I think I have to flash Defy+ rom
try to flash sbf use rsd
If your phone is detected by RSD Lite, then you have an easy fix in just flashing a new sbf. If it's not detected and you can't charge your battery, you're going to have to use the MacGyver method.
if sbf doesnt work u better send it to warranty
Well. On my computer the phone isn"t even recognized. Maybe because some RSD Lite files are missing and it need them to detect bricked defy (i did reinstalled RSD Lite)
If it's recognised on your friend's computer but not on yours then it means that you probably have the versions of the motorola drivers or rsd lite that have problems.
white led solution
hope for defy with only white led light turning on. This assumes that you have already have mototola drivers and RSD lite installed.
Background : I only had defy one day when I decided to flash it with miui. I bricked on the first time with bootloops. Did research and got drivers and rsd lite. managed to find three stock t mobile roms and flashed to stock Tom, then flashed miui, since then I've been switching between miui and cm7.
Problem : After a few months of use, I decided to flash stock rom to see how the battery life would be like. Bricked it the first time with bootloops. I thought I had flashed it with wrong rom because the first time I flashed back to original rom I did not delete the roms that I thought were the original roms. So after first failure I tried to flashed with the other roms I had. after the third rom it would not go into bootloader, only white led would turn on. Tried macguiver, did not work so save your usb cable, don't mess with it ain't gonna work.
Two part solution: I realized that when I plugged phone with usb I would hear the usb tone on win 7. When to device manager and saw the other device or something like that was appearing and disappearing when I would connect and disconnect phone. I clicked it and it said Motorola device or something like that, it was sensing my defy! defy drivers were wipe out due to bad flash. I had mototola drivers so I clicked on update and searched for mototola drivers on hard drive. I had rsd lite on and it recognized the defy after driver update, even though the bootloader screen was not on and just the white led was on.
decided to flash rom that have me bootloop and it flashed it but still gave me a bootloop., by the way, the update part of bootloader showed up after a while.
Second part of solution: googled problem and found out that the phone has a stock recovery. its the robot with the triangle exclamation mark. when you get to it you have to touch the extreme lower right hand corner of the screen to get to where you can wipe data and cache. when you start wiping data / cache you have to press on ok?? on lower left hand of the screen repeatedly until wipe is complete. then reboot and tada it boots up to stock tmo USA defy.
this is the stock rom I used : JORDN_U3_6.36.0
F Y I
if you ever try to flash a rom and it just bootloops, just go into stock recovery and wipe data and cache and you should be able to boot into android.
I'm Mc Gayvering my phone. Just tried a led directly connected to USB and fried it
This is my last hope
Is your phone worked?
I have the same problem. I try many ROM,But all of them dosn't work.
When I put in the battery,it shows Bootloader,When i flash a ROM use RSD,the phone always display SW Update In progress... Then the RSD's status is error verifying code group XX(XX=32/33/39/40 etc.) checksums.
What should I do?
THS.
Help :mad :
Hello, I'm having a problem with my Motorola Defy, he is not popping no FBS. he is not linking a black screen, but the white light is on, but when I try to install the SBF appears SW Uplidate im Progress .. can someone help me
wesleybinho said:
Hello, I'm having a problem with my Motorola Defy, he is not popping no FBS. he is not linking a black screen, but the white light is on, but when I try to install the SBF appears SW Uplidate im Progress .. can someone help me
Click to expand...
Click to collapse
dude this is all same **** u flashed wrong sbf.
flash the sbf service flash higher or same version which came by default wid ur phone.
flashes here http://and-developers.com/sbf:defy
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.
I have Motorola Defy MB252
When i bought the phone i installed MiUI to it. I have been since always upgraded MiUI using its updater. Yesterday I was drooling after the Android 4 for the Defy and decided I would try it out. I had some rom loader with 3 buttons installed on the Android. I pressed the one with boot rom manager button or something like that – I cant precisely recall what the buttons said or what was the name of the program. After this the phone booted and got stuck to the Motorola logo. I then tried to recover the phone to working state by flashing different SBF files from umts_jordan/list.php. None of them work – I am currently stuck in situation where the phone wont even show the Motorola logo. The phone automatically goes to the SBF flash state. Im flashing from Windows using the RSD like v5.5. Latest SBF I flashed was 3.4.2_145_finland\JRDNEM_U3_3.4.2_145-003_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA039.0R_UCAJRDNFRYORTCOREEU_P009_A006_HWp3_Service1FF.sbf
I only get blank screen with white front indicator led shining. I can get to flash state and it will only then print its programming it. The RSD lite says flashing was OK.
I did not keep good track what SBF files I have tried to flash.
I’m desperate – do you have any ideas what I should do?
[EDIT]
I flashed Defy-BL6Downgrade.sbf. Now i can get to Bootloader 09.10 (i see the normal bootloader when booting the phone but still no android).
FIXED EVERYTHING: Follow instrucsions in thread #1152377 post #8