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.

Reverting From GB to a 340 Based Rom

Just to clarify for several out there new to leaks. Correct me if I'm wrong anyone:
Going from "unrooted" GB leak:
1. unstall RSD Lite and Drivers, Run RSD Lite
2. Hold volume down+camera+power until screen flickers and release and you should have the white lettered bootloader screen.
3. plug phone in and RSD will see it and run the full .340 sbf
4. Phone will reboot when done into old .340 stock
5. Run z4root and then bootstrap in to install new rom.
Going from "rooted/deodexed" GB:
1. Use droid 2 bootstrap (or dx bootstrap with usb debugging disabled) to boot into clockwork.
2. For good measure clear data/cache, dalvik cache, battery stats.
3. flash maderstock or monster 340.zip
4. Immediately reboot only as to not brick
5. Run z4root and then dx bootstrap in to install new rom
**No you can not install a .340 rom directly from GB rooted or otherwise. You must flash back to .340 first**
Thats what I understand is that RSD was only used for the unrooted GB leak due to the fact we couldn't access clockwork. Hope this is correct and helps out.

Hm. It seems that it is easier to get back from deodexed GB than I thought. Yesterday I did it via RSD Lite – it was a REAL PAIN.

Sorry for noob question, my camera doesn't work and I can't play any MP3 file
anybody could help me, please

why wont it show up in rsd lite
my phone isnt being detected in rsd lite any suggestions. i have every possible driver i can think of installed no errors just not working.
please need help asap. trying to fix a friends phones before he goes out of town.

zz0122 said:
Sorry for noob question, my camera doesn't work and I can't play any MP3 file
anybody could help me, please[/QUOTE
You need to update your system. Sbf to the correct bootloader version and the get an OTA update
Click to expand...
Click to collapse

still no luck in getting the phone to be detected by rsd lite and ive tried everything i can find through searching google. any help would be greatly appreciated. thanks.

MahaVoodoo said:
Hm. It seems that it is easier to get back from deodexed GB than I thought. Yesterday I did it via RSD Lite – it was a REAL PAIN.
Click to expand...
Click to collapse
How did you rsd yours back to .340. I cant get mine to be detected by rsd. all appropiate drivers have been installed and have recieved no errors of any sort phone just not being detected by rsd.

Not sure if I answered this in the other thread or my browser didnt update. To get my rsd lite to see phone in bootloader go config >device id>first come first serve.

Make sure you have all the needed Motorola Drivers. rsdLite would not see mine untill i installed all the latest drivers...then a piece of cake

[Q] [URGENT] [HELP REQ] Err: A5,70,39,00,27

Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?

AMcKeeCT said:
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
Click to expand...
Click to collapse
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.

bigshotrob22 said:
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
Click to expand...
Click to collapse
+1
I thought I bricked my first phone when i constantly bootlooped until I tried this combo.
From what I understand your recovery is messed up. So then loading the full sbf loads that, but fails to load the system. in which case your sbf the system only sbf and then reboot and you should be able to boot.

I have done this a few times as well. You may have to flash the full sbf a few times for it to take, but it will work
Sent from my DROIDX CM7 nightly using XDA Premium App

http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
That is my vote. Worked like a charm for me and my bro. His X was very skrewed...

[Q] Milestone 2 in bootloop

Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz

Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...

Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz

Bootloader 70.13

thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz

MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.

Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz

Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz

Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz

You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen

Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz

This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!

How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.

When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium

Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz

I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help

Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.

ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine

I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.

Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.

HELP, i can't flash any sbf's available

Guys,
This is irritating.
It's not the first time that i brick my Defy and flash a SBF, but this time he got me. Nothing works. I have tried like 20 different ones today but no luck. I don't remember exactly what android version i flashed last time, like a half a year ago.
I am using RSD Lite v5.6, i go through the whole process of flashing but at the end the phone shuts down and RSD lite shows just PASS at the result, that's it.
Any ideas guys?
EDIT:
Ok, i got it working after all, but , i had to install a defy+ sbf. i don't now if everything will go smoothly or not from this point.
I\ll keep you updated.

Same problem
Hi
I have same problem. I flashed some sbf (while trying to recuse my defy), and after that, I can't boot up. But after every sbf, still black screen... And the biggest problem is, that I can't reach http://sbf.droid-developers.org/ for others SBF.
So, I have a question for you. What SBF worked for you? Now I'm trying to download this one http://forum.xda-developers.com/showthread.php?t=1263212.
Thanks