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] Defy bricked - any hope?

Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading

The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.

Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice

ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium

nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.

I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk

I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.

what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium

When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.

Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk

I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate

Is the general consensus that this is an unfixable hardware issue, then?

Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow

[Q] 2ndinit not working on MB525

Hi all,
I am new here and I hope this is the right place to ask this question. Tried searching the forum but haven't found any satisfying advice about my issue. So let me explain first:
I have been installing CM10 with 2ndinit on my MB526 Defy+, worked just fine. Now I am trying the same with MB525 Defy. What I've did so far:
Installed ROM from here sbfDOTdroid-developersDOTorg/umts_jordan/list.php, Retail Central Europe release with file name JRDNEM_U3_2.51.1_DEBLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTCEE_P031_A020_HWp3_Service1FF.sbf
deleted data and cache partition
used SuperOneClick to root it, no problem here
restarted couple of times and deleted data/cache
copied the latest SndInitDefy_2.3.apk to the SD card
installed and allowed superroot to use it
Installed with Sucess message and the green text stating it was installed correctly.
restarted gazillion times and cleared data/cache, also tried everything again from the beginning with the same sbf.
NOW I noticed some difference but maybe I am not right. On my MB526 from this moment on there was a white LED lit and after I restarted the phone it went dark and the blue one lit which is just fine.
With the MB525 there is no white LED, only when the device is off and charging, now when I power it on no LED light is lit so seems like the 2ndinit is not working correctly but I have no clue why. Any suggestions what to do, what to check or any other way of installing CM10 without using 2ndinit? I understand that clockworkmod should be able to help here, but I can't see Defy listed in supported devices.
Very grateful for any advice.
UPDATE: tried with something called defy_recovery-1218-0326-signed.apk from modmymobileDOTcom/forums/639-motorola-defy-development/559244-clockwork-mod-recovery-moto-defy.html and it installed the custom recovery, however when I clear all data/cache/dalvik, install either 2ndboot release from quarx CM10-20121205-NIGHTLY-mb526.zip or release for MB525 directly CM10-20120924-NIGHTLY-mb525.zip and google apps gapps-jb-20121011-signed.zip and try to reboot, then it stays on the old froyo motorola logo forever and nothing happens. Picked out battery and clearing data/cahce didn't help. I am ready to surrender.

Maybe you could try a different stock kernel. I had something similar with MB526. What I did was flashing a different stock kernel and that helped.
Sent from my MB526 using xda app-developers app

domokos said:
Maybe you could try a different stock kernel. I had something similar with MB526. What I did was flashing a different stock kernel and that helped.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Thank you for suggestion. Haven't tried that, how dumb of me . Will try it as soon as I'll get to that phone and let you know. In the meantime if anyone else has some other suggestions I will be happy to read them

[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

defy+ rom stucks in defy at starting

i've an defy. stucks when i tried to upgrade CM10 and. solved it with flash to eclair. then i tried again to upgrade and done many thing. suddenly it bricked. rsd didnt find it, only white LED visible. then with mcgyver method i tried many factory rom, none worked. then i tried defy+ factory rom and its respond.
ok, now i realise my defy is with defy+ bootloader 9.10. and with rom
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbfh with it
its works untill a restart. when i flash with it with RSD lite (5.3/4.9/5.6) after some time it says "please manually power up this device" then its stucks at Motorola animated logo...nothig happend after it...
please any awesome guy of XDA help me to restore my device to defy or defy+...

murad12s said:
...then its stucks at Motorola animated logo...nothig happend after it...
Click to expand...
Click to collapse
Go into stock recovery and wipe data and cache. That must be done after every time you flash with SBF.

Antiga Prime said:
Go into stock recovery and wipe data and cache. That must be done after every time you flash with SBF.
Click to expand...
Click to collapse
WoW!!! its simple and works!!!
but another problem occurs, battery not working, charging....
camera too!!!

murad12s said:
WoW!!! its simple and works!!!
but another problem occurs, battery not working, charging....
camera too!!!
Click to expand...
Click to collapse
The only thing I can think of is that your phone is a Defy (MB525, with a SoC camera module) and you flashed a Defy+ (MB526, with a Bayer camera module) ROM on your phone.
When that happens, your camera will only work if you flash any of the JB Roms with 2nd boot (basically any new latest ROM), as far as I know, since it's impossible to downgrade back to stock Android 2.1/2.2.
Regarding your battery, it is charging, but the system doesn't know it is, because, kind of like stated above, the Defy+ comes with a 1700 mah battery, and the Defy comes with a 1500 mah battery, therefore the system doesn't know which one it is.
Search for certain battery fixes here on XDA, and flash the one that corresponds to the battery you have.
If you haven't (which is most likely true), you should have probably read this first.

murad12s said:
i've an defy. stucks when i tried to upgrade CM10 and. solved it with flash to eclair. then i tried again to upgrade and done many thing. suddenly it bricked. rsd didnt find it, only white LED visible. then with mcgyver method i tried many factory rom, none worked. then i tried defy+ factory rom and its respond.
ok, now i realise my defy is with defy+ bootloader 9.10. and with rom
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbfh with it
its works untill a restart. when i flash with it with RSD lite (5.3/4.9/5.6) after some time it says "please manually power up this device" then its stucks at Motorola animated logo...nothig happend after it...
please any awesome guy of XDA help me to restore my device to defy or defy+...
Click to expand...
Click to collapse
FOLLOW THOSE STEPS http://forum.xda-developers.com/showthread.php?p=49558256#post49558256