Database Users

[Q] defy+ - tried to install miui, didn't work

Hi Guys and Girls, I hope this is the right place for my question. Sorry if I sound like a 12-year old - my english is not really the best...
I own the Motorola Defy+, and I tried to get rid of motoblur. I installed SndInit 2.0, did a reboot, did a backup, did factory reset, wiped dalvik cache and picked the miui-rom I had previously placed on my SD. The installation went pretty good, my phone told me that it finished the installation and I did another reboot.
After the reboot I get the red M (default Motorola-logo just like before I was meddling around with the phone) but just for a very short period of time and then I get a black screen with white letters (slightly out of proportion) saying:
Bootloader
09.10
Err:A5,70,00,00,23
Battery OK
OK to Program
Transfer Mode:
USB
When I remove the USB-cable the last two lines are replaced by:
Connect USB
Data Cable
Do you guys have any idea, how I could get MIUI, CM or anything else running on my phone again? I'd even be quite happy to have the stockrom running again, since a phone with ****ty motoblur is still better than no phone at all.
I'd be really grateful for any kind of help, thanks in advance.

The miui you installed was for defy or defy+? And , can you access to recovery?
Motorola Defy CM7 RC 1.5 OC 1GHz

You have forgot to do 2 things. this might be the problem .
Do:
1. Factory reset.
2. wipe data cache.
3. wipe dalvik cache.
4.install MIUI rom.
5. wipe once again data cache.
6. reboot.
If you can access recovery again . my guess you can..

Thank you guys for taking care of me!!
@LeonardoJegigzem
The MIUI is called miui-ger_DEFY_1.12.23_FULL_EN_DE.zip - it's for Defy but I've read in forums that it should run on Defy+ aswell.
@VoLtrex31
I can't access recovery (I'm assuming you're talking about the "push volume-down when blue LED turns on"-recovery?), the screen I described in OP appears right after the red-M shows up for the first time.
You are right, I didn't wipe data cache neither before, nor after the installation.

Thats not good.
Search in the forums for how to access the recovery via your computer..
This might be your only way.
Ask more forums for technical help since xda is not the best forum for asking for help.
because i am not an expert .
But don't worry i bet many people got that problem too so there is a solution .

at last you have stock recovery(i think)
to access it (on defy) ress and hold VOL DOWN and power button.
Than after(about 10 sec) you'll get an exclamation mark.
Now press VOL UP and DOWN at the same time and you can wipe data.
If phone boots up perfectly yo can reinstall 2ndinit.
If not.. i think that you have to flash the appropriate sbf via rsd lite.

buruss said:
at last you have stock recovery(i think)
to access it (on defy) ress and hold VOL DOWN and power button.
Than after(about 10 sec) you'll get an exclamation mark.
Now press VOL UP and DOWN at the same time and you can wipe data.
If phone boots up perfectly yo can reinstall 2ndinit.
If not.. i think that you have to flash the appropriate sbf via rsd lite.
Click to expand...
Click to collapse
Now that's great news - the folks at motorola seem to know that ppl want to avoid ****ty motoblur and **** up their phones so they built an easy way to rescue broken phones.
I will try that asap - right now I'm using an old sony ericsson Xperia X8 - want my Defy+ back!
Thanks buruss!

Hi guy,I know about what you talking.
1. everytime i stuck on "white letters" i recovered my defy+ with RSDLite and correct SBF file.
2. If you have 2.3.6 version of stock rom,miui or any common cm7 won't work - afaik. You must downgrade (somewhere is topic about it) or use cm7.2 or cm9
Sent from my MB526 using XDA App

mikrom.cz said:
Hi guy,I know about what you talking.
1. everytime i stuck on "white letters" i recovered my defy+ with RSDLite and correct SBF file.
2. If you have 2.3.6 version of stock rom,miui or any common cm7 won't work - afaik. You must downgrade (somewhere is topic about it) or use cm7.2 or cm9
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
Yea, I 've been through the same today/yesterday, and after a lot of cursing I can tell you it is exactly like this T.T you have to re-flash the stock ROM 2.3.6 again, and then if you find a way to downgrade/install Miui-CM/basically anything than staying with the stock ROM, let me know! xD
Just relax, I'm telling you this because yesterday I could have killed a dragon with my bare hands, but a soft brick is NP, as long as RSDlite recognizes your phone you can always going back to safety, from what I've learnt hard bricking a Defy is veryveryvery hard, thanks/due to a locked boot loader

Hey Guys, first let me thank you! I'm feeling quite happy now knowing that I'm not the only one with this kinda problem and I'll try the RSDlite-rescue-mission in a few days.
Happy new year everybody!

mikrokosmonaut said:
Hey Guys, first let me thank you! I'm feeling quite happy now knowing that I'm not the only one with this kinda problem and I'll try the RSDlite-rescue-mission in a few days.
Happy new year everybody!
Click to expand...
Click to collapse
I guess it's inevitable, when you start trying this and that custom ROM, sooner or later you're going to screw it up xD but it's actually good when that happens, because you know 100% you can fix everything - you did it once, you'll do it again
Happy new year!

miui uses the 2.2 froyo as base, since all the defy plus have gingerbread miui wont boot, miui hve boot.img and davtree.img in the rom.zip, if you flashan old boot.img in to a newer defy plus with new bootloader(2.3.6) you get an error, ho to fix it, try deleting the boot.img and devtree.img from the zip and replace the 2.3.6 boot.img and devtree.img form 2.3.6 and add it to the zip( miui rom) and try to flash it again and see if it works

You guys are awesome! Phone is booting again
installed RSDlite 5.3.1
downloaded the latest .sbf for my phone and my provider
let RSDlite do its magic and now everything's working just fine.
Next thing to do - try again to get rid of motoblur!

It's not 100% true, I installed MIUI over my 2.3.4 Gingebread and it worked like a charm
Only problem is, I can't install it anymore now that I'm on 2.3.6, but 2.2 is not strictly needed, 2.3.4 worked as well

Hey, guys! I have the exact same problem. I tried to install a Galnet MIUI ROM over at galnetmiui.co.uk, and i messed it up. I didn't really know what i was doing. Perhaps i forgot to wipe cache after installation. Have the exact same error message as mikrokosmonaut.
I was running my mb 256 with android 2.3.6, as far as I know, i have to use RSD Lite to istall stock rom again. Where do I find the correct SBF? My phone was bought without a service provider subscribtion, so I have no clue where to find the right SBF. I have no objection against having blur on the phone.
Can anyone help?

hi guys!!
i've tried to install miui on my defy+ 2.3.6.. like i read on this thread i modified the .zip file changing the boot.img and devtree with the original one.
but mt defy can't boot.. stuck at motorola logo..
what can i do?? does anyone managed to install miui on a defy+ 2.3.6?
now i'm using cyanogen and it works fine, but i prefer miui
thanks!!

daede86 said:
hi guys!!
i've tried to install miui on my defy+ 2.3.6.. like i read on this thread i modified the .zip file changing the boot.img and devtree with the original one.
but mt defy can't boot.. stuck at motorola logo..
what can i do?? does anyone managed to install miui on a defy+ 2.3.6?
now i'm using cyanogen and it works fine, but i prefer miui
thanks!!
Click to expand...
Click to collapse
I don't think MIUI work on 2.3.6. you need CM7.2, or maybe some latest nightly version of MIUI

mikrom.cz said:
I don't think MIUI work on 2.3.6. you need CM7.2, or maybe some latest nightly version of MIUI
Click to expand...
Click to collapse
thanks for your reply! indeed i'm using cm 7.2.. it works pretty well, except some delays! never heard about miui nightly! i did a research on google but i couldn't find anything.. any idea??
thanks again!

hi again!
i was thinking.. you said miui shouldn't work on 2.3.6 and i guess you are right! so if i do the same thing i did (change the boot and devtree file in the latest miui.zip that is 2.3.7 if i'm not wrong) but using files from android 2.3.7?
maybe i try to explain myself better..
i make a nandroid backup of my cm 7.s2 which is 2.3.7.
then i change the files boot and devtree from cm 7.2 to the latest miui.
should it work? what do you think?
thanks again

Hi, folks! *GREAT NEWS!*
Some guys over at the devs section on the thread below have found a froyo sbf with bootloader 6 (the same as the defy 2.3.6 sbf)!!! This means we can use it to downgrade to froyo and install MIUI over it!
http://forum.xda-developers.com/showthread.php?t=1486731
I haven't tried it yet, but will flash later today or tomorrow. You should read through some of the posts and decide for yourselves if you want to try or not.
All the best!
-If I managed to help you in any way, please press the thanks button!

[Q] Stuck on Google logo, can't access recovery mode

I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance

Do you still see the blue led for custom recovery?

Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF

Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.

fiskenigaten said:
Do you still see the blue led for custom recovery?
Click to expand...
Click to collapse
I see the blue led, but it goes on to green regardless of what I do (power+voldown does nothing). I've tried to access recovery mode several times, but the phone doesn't respond. Maybe I'm doing something wrong.
rperdue5 said:
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Click to expand...
Click to collapse
I've read the guide, but my original SBF is missing ever since MegaUpload's demise. Is it possible to use the Nandroid backup instead?

Auris 1.6 vvt-i said:
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
Click to expand...
Click to collapse
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?

Hmetool said:
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Click to expand...
Click to collapse
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..

arpith.fbi said:
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
Click to expand...
Click to collapse
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.

Hmetool said:
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Click to expand...
Click to collapse
Hi,
I faced a similar issue but it was since I flashed CM9 for Defy in my Defy+ with 2.3.6(stock) ! Nothing was working and I would get some boot errors! I rectified it by flashing full SBF and then rooting. Well if you want I can provide you with the SBF I have but it is for 2.3.6 and so you will loose downgradability. I have 4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage with me. However, you can also give Walter's fixed SBF and Nandroid backup a try

Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?

Hmetool said:
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Click to expand...
Click to collapse
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.

Auris 1.6 vvt-i said:
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Click to expand...
Click to collapse
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
One question: by full wipe you mean data/cache/dalvik cache or is there anything else that I'm missing?

Hmetool said:
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
Click to expand...
Click to collapse
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Hmetool said:
One question: by full wipe you mean data/cache/dalvik cache
Click to expand...
Click to collapse
Exactly.

Auris 1.6 vvt-i said:
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Exactly.
Click to expand...
Click to collapse
Yep, that's exactly what it is..

I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.

Hmetool said:
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Click to expand...
Click to collapse
Sounds great Well since CM9 nightly is still a long way to go, you may want to dual boot CM7 and CM9. Install CM7 as primary and dual boot to CM9.
Guide: http://forum.xda-developers.com/showthread.php?t=1375156

i did the same thing on my defy im a noob and need alor of help.
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.

blackhack516 said:
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
Click to expand...
Click to collapse
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA

do u have a link?
labsin said:
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
Click to expand...
Click to collapse
do u have a link

[Q] Install 10.11 and kernel update in DEFY greenlense.

Hi, i have some questions about the 2ndboot updates. I had tested cm10 for a while now (but currently in cm7.2), but i got a little lost with this whole kernel update.
1st of all, in quarx page i don't see a "cm10-2ndboot-nightly-defy/" folder, just the one for defy+, this new builds are only for defy plus yet?, or there work on both devices?
and if they do, how sould i install them, do they change to 2ndboot by themselves or do i have to do it myself?

elpiole said:
Hi, i have some questions about the 2ndboot updates. I had tested cm10 for a while now (but currently in cm7.2), but i got a little lost with this whole kernel update.
1st of all, in quarx page i don't see a "cm10-2ndboot-nightly-defy/" folder, just the one for defy+, this new builds are only for defy plus yet?, or there work on both devices?
and if they do, how sould i install them, do they change to 2ndboot by themselves or do i have to do it myself?
Click to expand...
Click to collapse
They are for both and no change is required from your part in the bootmenu settings

I've tried flashing 10.11 and update.zip today, with no luck.
I first tried flashing over my original cm10 (9.12 - froyo kernel, on green lens) - wiped cache, then dalvik.
boot loops on red led
then i tried wiping all data/cache and flashing both again
same boot loops
next i tried flashing a new sbf (t mobile usa 2.1 updated to 2.2 - then rooted and 2ndinit)
now still waiitng at red led on boot, but no boot loops.
I have read the bootup time is very long the first time, but I've let it sit over 15 minutes, and tried a battery pull and let it sit another 15 minutes.
I am about to try again from nordic deblur 2.2 sbf
Am i doing something wrong? I'm not an expert at this stuff, but i'm usually pretty good about following directions. please help!
Amazing job again Quarx and everyone!

Start fresh; use the ultimate wiper for defy and flash cm11/10, and them flash only update v2
Sent from my MB526 using xda premium

tronjojo said:
I've tried flashing 10.11 and update.zip today, with no luck.
I first tried flashing over my original cm10 (9.12 - froyo kernel, on green lens) - wiped cache, then dalvik.
boot loops on red led
then i tried wiping all data/cache and flashing both again
same boot loops
next i tried flashing a new sbf (t mobile usa 2.1 updated to 2.2 - then rooted and 2ndinit)
now still waiitng at red led on boot, but no boot loops.
I have read the bootup time is very long the first time, but I've let it sit over 15 minutes, and tried a battery pull and let it sit another 15 minutes.
I am about to try again from nordic deblur 2.2 sbf
Am i doing something wrong? I'm not an expert at this stuff, but i'm usually pretty good about following directions. please help!
Amazing job again Quarx and everyone!
Click to expand...
Click to collapse
I think You've misundersttod my friend. There no long time of bootlooping. Theres a long first boot. Boot lopping shouldn't happen continuously.
Maybe following the steps below from a post on the defy general forum should help
nidhish91 said:
OOk guys so I found this thread which shows MS2 got a custom kernel. The proceduce is bit difficult but can be modified for working for Defy too.
Hope has struck back again.
http://forum.xda-developers.com/showthread.php?t=1908687
Update: 2ndboot module sources are here:
https://github.com/czechop/2ndboot
Quarx puts his kernel here:
quarx2k.ru
Sdcard symlink Fix:
http://forum.xda-developers.com/showpost.php?p=32428611&postcount=392
Thanks to walter.
-------------------------------------------------------------------------------------------------------------------------------
BIGNOTE: Green lens users who flashed redlens builds please dont try using flash, you will end up burning it like me and many others.
STEPS TO FOLLOW WHEN YOU HAVE BOOTLOOPS OR BLACK SCREEN WITH RED LED ON:
-1st of all set default boot to 2nd-boot
-Go to recovery and flash the 24.9 build
-Then flash the kernel 6.10
-After that flash the latest build
-Wait and you will have your phone working proper.
!
Click to expand...
Click to collapse
Also you cont just go down to a previous sbf version. Youve flashed a custom kernel. You would need to go to your standard kernel which you would find elsewhere. I think the CM10 faqs have the 525 and 526 kernels

i followed the same procedure as last time, but this time starting from the nordic deblur sbf and everything worked fine. no bootloops. long first boot time. If anyone tries this, do NOT use the official tmobile USA sbf. didn't work for me at all. I'm guessing that's why i had problems with 9/24 build as well.

Flashing nordic to workaround red led + black screen ?
tronjojo said:
i followed the same procedure as last time, but this time starting from the nordic deblur sbf and everything worked fine. no bootloops. long first boot time. If anyone tries this, do NOT use the official tmobile USA sbf. didn't work for me at all. I'm guessing that's why i had problems with 9/24 build as well.
Click to expand...
Click to collapse
Hi,
Your message rings a bell to me !
I have tried to flash cm10 18/10 + update_v4 on my Defy (green lens) but I have failed, I always get stuck on red led + black screen. Waiting or removing battery and retrying did not help. Wiping did not help either. I am coming from cm7, had never flashed cm9 or cm10 before, and before cm7 my phone was on french froyo stock rom 3.4.2-164.
Do you think I should try to flash another sbf, such as nordic deblur sbf as you did ?

Is your bootloop like that:
Splashscreen -> red LED + black screen -> Splashscreen -> red LED + black screen
If yes, you should think about upgrading your bootloader...
Had the same problem and was on BL5, some people in Support thread had the same prob on BL5...
So I flashed this chinese rom, rooted and upgraded to cm10 and everything worked fine for me.
Use this SBF just as a stepstone to CM10, because it may break your flashlight or ****.
Make sure you have snd-init on your sd, cause there is no gapps on the sbf...
well thats it...

esok44 said:
Is your bootloop like that:
Splashscreen -> red LED + black screen -> Splashscreen -> red LED + black screen
If yes, you should think about upgrading your bootloader...
Click to expand...
Click to collapse
In my case, it's not looping, it is stucked on red led + black screen.

did you wipe cache and dalvik?
or did you try a clean installation?
wich sbf was the last one you flashed?

[Q] Defy Bricked. Really bricked.

- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899​(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.​I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.

There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?

if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature

I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense

Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf

Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.

vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions

corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?

First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all

I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)

vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see

corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D

UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?

vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting

corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.

vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life

corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.

vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above

Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas

@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7

[Q] [HELP] Bricked Defy - black screen, white led, no sbf works

Hi all
So, I have a problem with my Defy (MB525 green lens). The best will be, if I'll write my full story. Here is it:
Story
I had Defy with CM 10. It had bloated battery. I wasn't using it for 6 months because I have another phone.
Some time ago, I decided, that I'll give Defy to my grandfather. On Tuesday this week I bought new original battery. I put it in the Defy, and charge it. I could boot up my old system as I wrote, CM 10. While it was charging, I detected that I haven't got SD Card. On the other hand, I found some 4GB Samsung SD, which had my father in his Desire. The SD Card had 3 partitions, which I tried to delete, and make only one, with GParted. After I did it, Linux and Windows can't see it. (This is almost other problem, which I'm trying to solve here http://crunchbang.org/forums/viewtopic.php?pid=350683)
But, when I put the CD Card to Defy, in TWRP recovery I could see some strange symbols. I thought, that I can repair something when I wipe SD Card. When the battery charged, I decided to do factory reset and wipe SD card. Here is my first failure. In TWRP I went to custom wipe, and here I marked everything including system and I wiped it. Then I remembered that system is recovery too. TWRP wrote, that everything except SD-Ext and SD was wiped. I known that this will be a problem. Yes, after reboot only Motorola logo without recovery.
I think, there was only one option - flash SBF, which I did. I went to stock bootloader and with sbf flash in Linux, I flashed this:
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
And than this:
CM7RC1.5_16_09_11_custom.sbf
After reboot, I got bootloop. I tried to replace battery, do factory reset but nothing helped. That time I haven't got working card, so I couldn't flash some zip via CWM recovery. Thus, I again flash another SBF, but I don't really remember which. Probably some official CEE Froyo however, I'm not sure.
After that and reboot, I got only black screen with white led lighting while USB was connected. When I wanted to go to stock bootloader, still black screen, but I can flash SBF, and while flashing, screen have brightness and text about flashing.
I knew that this is little hard brick. I again tried to flash other SBF which I have or I downloaded (yes, again I don't know which). One of SBFs which I flashed was some fixed Chinese SBF . That made my defy booting, screen working, but still bootlooping. I couldn't reach any recovery.
Again, I flashed other SBFs, CM's too but nothing worked and I got black screen again.
And this was end of my story.
Current situation
I have Defy (MB525 green lens), with unknown framework an it had only black screen and what only I can do, is break Defy with hammer or flash some SBF.
So, here is list of all SBF files, that I have downloaded and probably tried to flash: (No order)
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
CM7RC1.5_16_09_11_custom.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANO2DE_P048_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
DFPRC_U_4.5.3-109_DPP-6-7_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P025_A019_HWp3a_Service1FF.sbf
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
JORDN_U3_97.21.51.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF.sbf
4.5.1-134-DFP-132-gingerbread-BL6-fixed.sbf
4.5.2-109-DHT-22-gingerbread-BL5-fixed.sbf
3.4.2-177-003-nordic-froyo-fixed.sbf
3.4.2-179-002-tmobile-froyo-fixed.sbf
4.5.1-134-DFP-74-gingerbread-BL5-fixed.sbf
4.5.3-109-DPP-11-gingerbread-BL5-fixed.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN.sbf
Probably that is all what I have.
I've read many topics with similar problem and guides, but nothing helped me, or SBFs were unavailable.
So, what have I to flash, or which guide to try, if I want working Defy?
Sorry for my not good English
Thanks
UPDATE
sterver1 said:
Wohooo!!
Story
After a long time (4 months)...
Accidentally today I found my favorite custom ROM - MoKee OS, for Defy. I said to myself: "Hm, I have some time... I'll try to flash this MoKee on my Defy and maybe it solve my problem with (not) charging/unknown battery for system."
I picked out box with Defy from drawer, wiped the dust, took the Defy and said: "Sh*t! I haven't got SD Card!" Fortunately I found one. I download MoKee OS zip on that SD Card, put it to Defy, booted to recovery and flash MoKee OS zip. (...with full wipe of course...) Then rebooted to system.
Uselessly. Still unknown battery. "Hmm, It doesn't matter. Maybe here are some new stuffs which can solve my problem." And I continued to finding something, that can solve my problem. After a while I found ROMs with new 3.0 Kernel by Quarx. HERE. I downloaded CM 11 EXPERIMENTAL with this kernel and update recovery and flashed them. I didn't read thread. After reboot system didn't boot up and TWRP was inaccessible. I found why when I read some posts from that thread. HERE. But I couldn't flash that zip via recovery because I couldn't open recovery. So I mount /system to USB from bootloader and added files from zip manually to /system partition. After reboot it jammed on booting up. But TWRP was accessible so I did full wipe and flashed CM 11 EXPERIMENTAL and than that fix zip by @lorcotti. After that it finally booted up and battery was working and charging!
And they all lived happily ever after. :laugh:
SO, If you have some problem as me (unknown battery after flashing GB SBF on MB525), try this:
1. Download recovery and some ROM from [Kernel][GPL] Development 3.0 Kernel and fix from this post.
2. Put all zips on your SD Card.
3. Boot up to recovery.
4. Flash update-recovery.zip.
5. Reboot to recovery.
6. Do full wipe.
7. Flash ROM with 3.0 Kernel.
8. Flash Fix.
9. Wipe cache and dalvik cache.
10. Reboot to system.​
If you want, you can flash GAPPS via recovery too.
But this will not be for daily usage! 3.0 Kernel by Quarx have a lot of bugs!
Thanks all!
Click to expand...
Click to collapse

Yeah!
Today I again tried to flash chines SBF. This one: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
...and now I have bootable phone . I read many topics again and I got to know how to aces stock recovery. So I made wipe on this chines ROM and I can boot without loop, but I can only do emergency call with SIM it is the same. So, now, I don't know, what have I to do/flash, how to root it and flash here custom rom. Can I use SuperOneClick if it probably haven't got turned on USD Debugging?

Back on black
So, I made sbf file with depacker...
CMG39 from JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF
and all others from JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF except CMG31.
Than the bootscreen changed from chines logo to grey motorola logo and I got Bootloader (9.00) Error A5,70,39,00,27. After that I flashed another sbf and I got Error A5,70,00,00,23. Than I flashed DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf and now I again have only black screen. F*ck!
I tried to flash my made sbf and chines one (JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF) too but nothing...
Really here is nobody who can help please??? I want give Defy as Christmas gift. :crying:

OK, so repetition.
What mistakes I've made
1. I wipe wipe all including system partition in TWRP without any flashable zip on SD card.
2. I continued with flashing original SBF, while I have usable CWM.
3. I flashed many no downgradable GB SBFs.
4. I flashed Defy Plus SBF on Defy.
I hope that there is still hope.
Somehow to downgrade, flash only CWM where I can flash nandroid backup or I don't know what else...

a gingerbread sbf should also work on green lens defy as there is no diff. in hw... instead the cam
have you tried a factory reset in stock recovery after sbf flash ?
Sent from my MB526 using xda app-developers app

Now, after all (which I tried) SBFs I get only black screen. I tried many GB SBFs too, but still black screen...
I'm going to try some another Poland SBFs and than if that won't work, I'll try to flash all in Froyo CEE SBF particularly.
Thanks for your response.

Once you've flashed GB stock sbf you can't go back staight to froyo or else
Read the beginners guide and the SBF matrix sektion carefully.. if you haven't...
Sent from my MB526 using xda app-developers app

DFP 231 has been flashed by you, so no froyo sbf will work. Black screen on dfp 231 indicates some eMMC problem, because bl version is highest(no error possible). IMHO only service centre can disable bl check or replace the main board to fix the problem
The problem should have been solved at the boot loop issue by wiping from stock recovery, no network solved by baseband/radio fixes. Check the rsdlite log file to confirm checksum/access errors. I think that the custom sbf somehow messed up either eMMC or efuse(less likely, unheard of).
For sdcard error wipe everything using hdd llf. If any error persists it's a hardware issue
Sent from my MB526 using Tapatalk 4

@bone101
I know, I read it few times, and I know how it is (not) working. But, after all GB SBFs I got only black screen, so maybe were not correctly flashed... I'm using Linux and here is sbf_flash for flashing SBFs, and in it I can't view informations about phone as in RSD Lite... But maybe, it will work in wine..
Do you now, that if I flashed GB SBF, I have to flash another GB to solve my problem, because no Froyo will work?
@thekguy
I know how I can solve others problems. Only what I need help to solve is black screen.
Can't I flash something which support that high BL or it won't work?

check if you get into Bl. modus
press vol. up & then power button
tell what you see
Sent from my MB526 using xda app-developers app

That's what I'm saying, the black screen problem occurs due to bl version mostly, and you have highest bl, so in theory black screen is impossible. Unfortunately I have never seen in this forum any defy recovering from black screen after flashing dfp231. Check rsd log from windows if possible. Froyo sbf cannot work under any circumstance. You must flash only gb sbf
Sent from my MB526 using Tapatalk 4

@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 173002052f066b010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: d0d8842b4879dd27b9eb94f970fbeec252fcb2f4
BP Public ID: 0000000000000000000000000000000000000000
Click to expand...
Click to collapse
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!

sterver1 said:
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
Click to expand...
Click to collapse
I'm stuck in same problem, downloading this sbf you mention before, hope it works. Fu^kin defy, it sucks

@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=1216982
DOWNGRADE
If you come from Android 2.1 and never flashed Android 2.2 you can use the fixed sbf-files method. With this method you will have a option to downgrade to you personal stock Android 2.1 via direct sbf flash.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
It will only work if you never flashed a Android 2.3.6 full sbf.
Click to expand...
Click to collapse
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.

have you tried cm11 ?
or ms2ginger by walter79
Sent from my MB526 using xda app-developers app

sterver1 said:
@Alejandrissimo
Good luck...
Click to expand...
Click to collapse
Working and rooted, thanks for your help

Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
please see your PN

sterver1 said:
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
from http://forum.xda-developers.com/showthread.php?t=1216982
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
Click to expand...
Click to collapse
Congrats man! Seems that rsdlite on Windows is the most reliable solution. Now to fix everything just flash cm10 (jelly bean) or later rom. It includes fixes for camera and battery
Again, no downgrading bl(not even jtag will work)
Sent from my MB526 using Tapatalk 4

Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
Hehe, I'm glad...

sterver1 said:
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Hehe, I'm glad...
Click to expand...
Click to collapse
There's a cm7 2ndboot build which should work for you. Try cm10.1 or above, problem should be solved.
JB wiui includes those fixes, as does cm7 2ndboot. I don't think that wiui GB has them. I would personally go for cm10.1 or above
Sent from my MB526 using Tapatalk 4