Database Users

help! Defy wont boot, white light at top, rsdlite doesnt recognise

Deleted by user

I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App

Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.

Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse

Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App

Guess what, it works!!!
Deleted by user

Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse

I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure

Deleted by user

got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable

To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...

Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd

I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do

Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave

Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder

I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

[Q] lesson learned: don't update after root! (moto defy)

when i got my moto defy for xmas last year, i had my older brother root it for me. i really had no idea how to safely use root, but i liked being able to overclock and all the other features. the phone was a little buggy just because it was on 2.1 and no updates yet. once an update came out, i installed it and got a great performance increase. later, i realized that it was not working right. whenever i hold down an on-screen button, the touch sensitivity "timed out" after only about 1.5 seconds, unless i kept my finger moving around on the screen. and every few times i reboot the phone, this glitch goes away until i reboot again and then it is back. root was also taken away, and none of the one click roots work. also, when the 2.2 update came out, i got the error message when rebooting after installing the update and it did not work. i tried wiping the phone several times, no luck. i am now interested in fashing a custom rom and rerooting. would this fix it? there must be a special way to do it since my phone is so messed up. i would like 2.2 or 2.3, and 720p vid would be cool too. the version i have now is 2.1.1, so can anybody suggest a rom that is stable and will work ok?. one more question, when i flash a rom, will it leave my apps and settings alone or do i have to start over?

Have you tried using SuperOneClick to root the phone? (You'll need to install the Motorola drivers for it to work.)
In most cases, you will lose your apps and settings when you flash a new ROM. But, if you figure out a way to root it, you can back everything up in Titanium Backup first, and restore it afterward.
If you just want to start from scratch, try wiping everything in the stock recovery. To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition".
If that doesn't work, I'd recommend flashing a new Froyo sbf using RSD Lite. Here's a quick tutorial:
1) Install the Motorola drivers and RSD Lite on your computer. See this guide for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
2) Download the sbf file that you want to flash, and save it to your PC. Many sbf files can be found here: http://forum.xda-developers.com/showthread.php?t=966537 WARNING: If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again.
3) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
4) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete. Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
Then you should be able to root, install custom recovery, and flash custom ROMs to your heart's content.
Good luck!

Thanks! Sorry to be a noob, but how do I know if a rom /sbf will work? Doesn't it matter what android version I have now? 2.1.1 is it
Sent from my MB525 using XDA App

Most custom ROMs for the defy require that you upgrade to Android 2.2 (Froyo) first. I can explain how to do that, if you like. What country are you from, and what cellular service are you using?
Before doing anything to your phone, you should read this guide: http://forum.xda-developers.com/showthread.php?t=1216982

Take a backup using titanium backup. This takes Care of all app and games. Then flash froyo. Go hd to install a custom rom like cm7. Guides are there for this. Restore all app and games with data from titanium backup

all this stuff is like you are speaking french to me. could somebody link me a sbf that has 720p video capability, 2.2 of some sort, and that is going to work with my current version(2.1.1)? i am still confused if the glitch i described will be fixed, and if it matters that i installed an update from motorola after i rooted. i really hate to be such a noob, but i don't have time to read all the guides and stuff. thanks for all the help, i just need a little more detail as i am very new to all this. I have T-Mobile USA
and one more thing: i just looked at some of the sbf's in the guide you showed me, the only 2.2 US file was from Megaupload, and F***King SOPA shut it down. now we feel the effects of this horrible law.

The best base (Froyo 2.2.2) for using a custom rom :
http://sbf.droid-developers.org/umt...RDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf.gz
Flash and enjoy CM7, Miui...
But honestly you need to read a little bit before... Or I can explain in french to you if you prefer... :-D

ritchrocko said:
all this stuff is like you are speaking french to me. could somebody link me a sbf that has 720p video capability, 2.2 of some sort, and that is going to work with my current version(2.1.1)? i am still confused if the glitch i described will be fixed, and if it matters that i installed an update from motorola after i rooted. i really hate to be such a noob, but i don't have time to read all the guides and stuff. thanks for all the help, i just need a little more detail as i am very new to all this. I have T-Mobile USA
and one more thing: i just looked at some of the sbf's in the guide you showed me, the only 2.2 US file was from Megaupload, and F***King SOPA shut it down. now we feel the effects of this horrible law.
Click to expand...
Click to collapse
If your DEFY has a greenish-yellow camera lense (as most do), you won't get 720p video capability no matter which sbf you use. (Unfortunately, it's a hardware limitation.) Most custom ROMs will enable you to take widescreen videos, though.
You don't need to use a T-Mobile USA sbf, by the way; you can use any Froyo (Android 2.2) sbf you want (except for Chinese ones, which will burn out your camera flash). You just have to change the cellular radio baseband afterward, to match the frequencies used by T-Mobile USA. That's easy to do; just use the "DEFY baseband switcher" app: http://forum.xda-developers.com/showthread.php?t=1052745 (Many custom ROMs, like CM7, already include the basebandswitcher app.)
Since you don't want to search through the forums for a guide on how to flash an SBF, here's one I wrote for a friend a while ago:
Flashing SBF firmware with RSD Lite
Follow this guide to flash firmware files (with .sbf filename extension) on the Motorola DEFY. This is useful for “de-bricking” a phone that won’t boot (provided the bootloader still works), or if you want to do a clean install of the Motorola stock firmware. I don’t recommend flashing SBF files unless absolutely necessary, however, since the process is dangerous: there is a slight possibility that your phone could become “hard-bricked” if something goes wrong. (A phone is hard-bricked when you can’t even access the bootloader to flash new firmware.) It is much safer to flash or modify firmware using ClockworkMod custom recovery, which doesn’t mess with the bootloader. (See step 3 for more info.)
Before flashing any new firmware on your phone, I strongly recommend reading this Beginners Guide: http://forum.xda-developers.com/showthread.php?t=1216982
WARNINGS:
A corrupted SBF, power failure on a critical part of the formatting, or some weird issues while creating partitions can lead to a “hard-bricked” phone (i.e., a phone that can’t even be restored by flashing new firmware, because you can’t get into the bootloader). It is recommended that you flash your phone from a laptop with a fully charged battery, to reduce the risk of losing power while flashing. Use good cables, and be sure that the PC doesn’t go to sleep during the flashing process.
If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again. (You can, however, install DEFY+ firmware without losing downgradeability, using the “fixed SBF” method. See this guide for more information: http://forum.xda-developers.com/showthread.php?t=1216982 )
The Chinese version of the DEFY has a different kind of LED for the camera flash. Using the camera flash with that firmware can permanently damage the LED.
Before installing any new firmware on your phone, backup your stock firmware, so that you can return your phone to its original state in case you ever need to send it to Motorola for repair. The firmware for the US T-Mobile version of the DEFY was never released as an SBF file, so you won’t be able to restore the phone to its original state unless you have a full system backup of the stock firmware. (See note at step 3 of the guide below.)
1) Install the Motorola drivers and RSD Lite on your computer.
See these guides for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
http://forum.xda-developers.com/showthread.php?t=897445
2) Flashing new firmware using RSD Lite will erase everything on your phone’s internal memory (but not the SD card), so backup your contacts, settings, and any apps you’ve downloaded. I recommend using Titanium Backup, which is available free on the Android Market.
Note: your phone must be rooted before installing Titanium Backup. You can root the DEFY using SuperOneClick. Rooting the phone voids the warranty, but you can use SuperOneClick to un-root it if needed. See this guide: http://www.addictivetips.com/mobile...d-samsung-captivate-with-super-one-click-app/
As explained in the guide, you need to unmount the SD card and enable USB debugging before running SuperOneClick. The latest version of SuperOneClick can be downloaded here: http://forum.xda-developers.com/showthread.php?t=803682
3) Download the sbf file that you want to flash, and save it to your PC. If you are doing a “clean install” of CyanogenMod 7, I recommend using the 3.4.2-179-2 CEE DEBLUR sbf. Links to download it can be found in this thread: http://forum.xda-developers.com/showthread.php?t=966537
It would be a good idea to keep that file on your PC, in case you ever need to de-brick.
4) Optional step: before flashing an SBF file, it is a good idea to wipe data and cache in the stock recovery. (I usually forget to do that, though, and I haven’t had any problems.) To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition". (At least, that is the procedure on Android 2.2. If I remember correctly, on Android 2.1 you had to tap somewhere on the touchscreen to get the menu to display, and the touchscreen was also used to navigate the menu.)
5) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
6) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. (WARNING: read the above warnings about file versions and downgradeability.) After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete.
7) Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
8) Root the phone using SuperOneClick. See this guide: http://www.addictivetips.com/mobile...d-samsung-captivate-with-super-one-click-app/
As explained in the guide, you need to unmount the SD card and enable USB debugging before running SuperOneClick. The latest version of SuperOneClick can be downloaded here: http://forum.xda-developers.com/showthread.php?t=803682
9) If you're not going to install a custom rom and you used an sbf that is not for T-Mo USA, you'll have to change the baseband frequencies. Install the baseband switcher app: http://forum.xda-developers.com/showthread.php?t=1052745 Open the app and click on the “Americas” tab, and select one of the “US T-Mobile” options. (The “US T-Mobile 3.4.2-107-9” option works well for me.) The phone will have to be rebooted again.

I need Help - Serious Acting up of Phone

I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.

live_free said:
I'm on my 3rd Atrix now, after two previous phones just stopped working.
Now I was having crashing problems no matter what rom I went to and other problems, like the power button not working in CWM and freezing all over.
So I had to sbf to 2.3.4 preroot/unlocked to be able to get back to a starting point. I did everything properly and now am in a boot loop, and I've done a battery pull. The farthest it has got is "welcome to blur" screen then starts to loop again.
Click to expand...
Click to collapse
what sbf did you flash? is it att bell etc? need some more info to help you out.

aideneisley3 said:
what sbf did you flash? is it att bell etc? need some more info to help you out.
Click to expand...
Click to collapse
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204

live_free said:
ATT-2.3.4_Pudding_preroot.sbf
http://forum.xda-developers.com/showthread.php?t=1138204
Click to expand...
Click to collapse
STEPS:
1) Have the correct Motorola drivers installed for your PC (i.e. x32-bit or x64-bit).
2) Download RSD Lite (Links above) & install on your PC.
3) Choose a sbf file to download and flash from Motorola Atrix Firmware Super Thread: http://forum.xda-developers.com/showthread.php?t=1125944
If you are currently running firmware 4.5.91, I suggest that you only flash back to this firmware version. Flashing back to a eariler sbf/firmware version may have unintended consequences, the most serious of which is bricking your device.
*Note: U.S. AT&T users should only flash AT&T sbfs, internationl users should only flash their particular sbf versions.
4) Read the above sbf hints, trick, etc. to help prevent RSD Lite problems/errors.
5) Open RSD Lite and load the sbf file that you downloaded.
6) Put your device in RSD Protocol Mode by powering OFF, and upon powering back ON, hold both the power button and the volume UP button. Device should now say "Entering RSD Protocol Mode."
7) Connect your device to your computer via the usb cable, and select your device by clicking/highlighting it in RSD Lite.
8) Select START in RSD Lite and let the sbf flash process fully complete before disconnecting the device from the PC. There will be several reboots and the process make take 5 - 10 minutes to complete a FULL sbf flash.
9) If you have any errors or problems as a question, prefably in the Q&A section.
this is what i have done and worked for me! good luck
i copied this from the noob guide found here http://forum.xda-developers.com/showthread.php?t=1154600

Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.

live_free said:
Yeah I did that. I am flashing the complete stock 4.5.91 to see if that does anything.
Click to expand...
Click to collapse
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!

aideneisley3 said:
yeah the one in the atrix firmware superthread at the top is the one i recommend it gets you back to stock fresh out of the box you might have to go through the unlock again even though your already unlocked and of course you will have to root again.
hope it works for you!
Click to expand...
Click to collapse
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.

live_free said:
I just did that, and no same problem. So it looks to be a hardware problem, not a software one. At least from my perspective.
Click to expand...
Click to collapse
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf

aideneisley3 said:
did you flash this one? 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
Yes. Same exact problem.

live_free said:
Yes. Same exact problem.
Click to expand...
Click to collapse
oh ok well then i'd have to agree with you then maybe it is a hardware problem... sorry i wasn't much help.
it wouldn't hurt as a last ditch effort to use motorola's software update program that you can download from their site it will tell you that there is no update and ask if you want to use it to restore your phone basically it reflashes it...
haha thats all i got. maybe someone else could offer more help.
good luck! =]

live_free said:
I did everything properly and now am in a boot loop, and I've done a battery pull.
Click to expand...
Click to collapse
apparently not.

in his defense replacement phones are refurbished (cough... broken and maybe fixed to like new). motorola gave me a replacement with broken senor so the screen didn't turn off when i was in a call and that was out of the box and when they replaced that one the screen was messed up it had super bright spots all over the screen so it is possible that it is moto's fault.
not saying it is moto's fault but that it is possible lol

Defy+ wont boot no screen, nothing. [fixed]

Hey
I tried to get my phone faster and found the [ROM][Minimal] Nothing But Speed 1.0 Thread.
I downloaded the rom that says Recommended SBF for Defy+: DEFYPLUS_U3_4.5.1-134_DFP-132 (I use it too)
Flashed it with RSD lite all went well it said now rebooting left it 5 mins nothing.
So I hit the power button wait few minutes nothing, Pull battery out for a few minutes put it back in hold the power button for like 30 secs wait few mins, no lights, no screen, no vibration, not a damn thing.
Battery was at 80% when I started and I have tried to hook up a USB wire with red and black hooked onto positive and negative as had trouble flashing last time and it said battery was low so had to do that. It wont show anything!
I should of left it as I am not sure how to fix this if you cannot even get it to start booting.

No one have any idea whats going on?

Was your previous rom a higher version than 132?
I tried to flash a 1321 rom to my defy plus which was OTA updated to 231 and it seemed to kill it. No response. Plugging in the USB cable would light the led and rsdlite would show connected. So i just flashed my 231 ROM again and it worked.
If you plug in your phone to usb and run rsdlite, see if it shows connected. If so, just flash the correct rom and it will work again.

I did try to flash the new rom 4.0.1 I think it was but got a error at boot (tried this before but used different steps this time hoping it would work) But before I was able to flash it back to 2.3.5 and it updated to 2.3.6 no problems at all.
This time it wont boot. It shows a white light if I hit the power when the USB is connected but not the charger and RSD lite did not show it was connected. Might try it a few times with different ways like connecting phone then starting it or starting it then connecting the phone see if any will read it.
Apart from that only other thing I can think of is take it back and hope they cant get it working and send me a new one. Or they will get it working and not sure what they do if its had custom roms flashed, I guess I will have to pay for the repair?

Ok got it to flash in RSD lite. I tried to flash the rom that worked last time but it still wont boot at all.
I think I may need a CM9 SBF file as I flashed the CM9 kernel and gapps or something. I did not do this last time I tried.
Would this be why I cannot flash back to the ROM that was working before?? and if so how can I get the kernel back or a ROM that will work with the one I have?

Being that the defy is virtually unbrickable, all you need to do is flash a stock 2.3.6 rom, but make sure that the CG/BL version is the same as the version you were running previously. Most probably try 132/1321 since these are the latest rootable roms. If there's a chance that you were running 231, then these roms will leave your defy dead, and you will have to flash a 231 rom. Kernel doesn't really matter, because a full stock SBF will have everything needed to bring the phone back to life.
Edit: i just realised: i hope you're not trying to flash rom zips through rsdlite. only sbfs. thought of this since you said you flashed a 4.0.1 rom which should NOT be an sbf. if you meant that you flashed the ICS rom through the clockworkmod, then ignore this whole para.

ok not sure what the version is how can I tell??
I followed the instructions on this page
forum.xda-developers.com/showthread.php?t=1432100
I think I downloaded the one that says:
NEW Latest build by Epsylon3: 16 Apr 2012
Edit:
Oh sorry I am a bit of a NOOB but where is the best place to fine SBF files for the versions I have I seen there are heaps on here but not sure what ones are right to use.

Ok I have it going again thanks. I think I must of had the 231 rom as all the rest but that didnt work.
Can I flash any rom with the 231 version??? as this is a german one not sure if that will matter but if I come into problems I might need to flash a new one.

Since you want to install ICS, doesn't really matter.
Follow the steps here to root 231: http://forum.xda-developers.com/showthread.php?t=1542956 These are full SBFs so your earlier 231 download would be wasted i guess.
Then install ICS from here: http://forum.xda-developers.com/showthread.php?t=1432100
Or some other rom if you like.

Yeah thanks, I already found that thread before had as I found out in about 30mins of installing it that it wont root.
I think I am going to keep it 2.3.6. Do you run ICS?? I tried to install it twice and got problems both times using 2 different ways and the link you posted was one of them.
What is the fastest rom?? will I be able to do the nothing but speed 1 rom now or have I upgraded to high?
I just wanted to get alot of crap off and get it a little faster but I dont want to overclock it.

I actually own an xperia play (previously used a blade), i'm helping a friend with his defy+.
Originally the plan was to root and debloat because the stock phone was painfully and surprisingly slow and laggy. In the meantime he decided to upgrade OTA to 231 (came with 1321 stock) in the hopes that the update would speed it up. Since 231 has a painful root procedure of downloading two SBFs, we then decided to go the whole hog and upgrade to ICS.
First tried Quarx's Apr 20th, but the buttons backlight stayed on. I know there's a fix for that, but then decided to try Epsylon's Apr 17th. Working fine so far. Only gripes are the lack of HWA means opera mobile etc. won't run, but making do with mini/next.
Since there is now a root method for 231, you can run any rom that uses a GB kernel. Just install 2nd init first, then boot into CWM and install a rom. Note that for the defy+, if you install the CM9 kernel, the system seems to die, so only install the CM9 rom.
99% after you switch to ICS you wouldn't wanna go back to 2.3.

[Q] Defy near death or worse. Please help!

Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock

Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App

As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.

Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade

Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App

You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?

Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!

Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.

Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock

If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2

Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above

corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?

Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.

I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!

Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.

I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock

It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again

Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2