Related
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 flashed both the VRZ_MB810_2.3.34_1FF_01 and 602 SBF to my Droid X with 30.04 bootloader and followed the steps to get the phone into recovery mode but it still won't work.
Steps:
1) Downloaded both SBF files
2) Opened RDS Lite 5.4.4
3) Clicked 3 dot button and uploaded VRZ_MB810_2.3.34_1FF_01
4) When it said manually power up your phone I unplugged USB, took out the battery, put the battery back in, put it back into bootloader mode, then plugged the USB back in and it said Finished
5) Unplugged USB cable
6) Pressed power to exit out of bootloader screen
7) Pressed home button and held it while pressing power. I released the power button after I saw the Red Motorola Logo and the Exclamation point never showed up.
I did these same steps with the 602 SBF file and it still wouldn't work.
There isn't water damage or anything to the phone. The phone froze at the Motorola Logo yesterday when the battery was pulled out and memory card.
I'd appreciate some help.
crossover37 said:
I flashed both the VRZ_MB810_2.3.34_1FF_01 and 602 SBF to my Droid X with 30.04 bootloader and followed the steps to get the phone into recovery mode but it still won't work.
Steps:
1) Downloaded both SBF files
2) Opened RDS Lite 5.4.4
3) Clicked 3 dot button and uploaded VRZ_MB810_2.3.34_1FF_01
4) When it said manually power up your phone I unplugged USB, took out the battery, put the battery back in, put it back into bootloader mode, then plugged the USB back in and it said Finished
5) Unplugged USB cable
6) Pressed power to exit out of bootloader screen
7) Pressed home button and held it while pressing power. I released the power button after I saw the Red Motorola Logo and the Exclamation point never showed up.
I did these same steps with the 602 SBF file and it still wouldn't work.
There isn't water damage or anything to the phone. The phone froze at the Motorola Logo yesterday when the battery was pulled out and memory card.
I'd appreciate some help.
Click to expand...
Click to collapse
Try using the Linux method, or try an older version of RSD Lite.
Also, try updating your Motorola USB drivers, and redownload and recheck the md5sum on the 602 SBF file.
Sent from my DROIDX using XDA App
First off are you using RSD Lite to sbf? I was stuck in bootloop after trying to to upgrade my custom ROM without reading all the directions....anyway after trying everything I found the 2.3.34 sbf file along with RSD Lite worked out perfect. After you will have to re-root and upgrade back to gingerbread
I'm stubborn, personally...
But it can't hurt to make the suggestion...
I've been using v4.8 RSD ever since it came out.
And I refuse to upgrade simply because I know it works.
As previously suggested, maybe try a downgrade on RSDlite.
Edit:
And again, make sure you have the correct drivers...and MD5 matching downloads.
I haven't seen seen this mentioned in any of these posts regarding SBF's, but my preferred method is the 1KDS bootable Linux ISO disc. I am not sure about posting links to other forums, but a quick Google search would point you in the right direction.
Just burn with a disc image burner and boot from CD at your PC's BIOS and bam SBF, super easy and has never failed me.
Sent from my GT-P7510 using Tapatalk
dxh3378 said:
I haven't seen seen this mentioned in any of these posts regarding SBF's, but my preferred method is the 1KDS bootable Linux ISO disc. I am not sure about posting links to other forums, but a quick Google search would point you in the right direction.
Just burn with a disc image burner and boot from CD at your PC's BIOS and bam SBF, super easy and has never failed me.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I agree, I always reccommend the Linux method.
Sent from my DROIDX using XDA App
use rsd lite 4.9 and flash 602 sbf. do not unplug the cable from your phone until it says manullaly reboot your device. otherwise you might not sucessfully flashed correctlly.
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!
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