Database Users

stuck on JORDN_U3_97.21.51.sbf (2.1)

hi guys, having major issues here.
i'm on JORDN_U3_97.21.51.sbf, a t-mobile 2.1 rom. i have rooted with an old version of superoneclick because 2.1.1 wouldnt work, i've installed sndinitdefy 1.4.2 which all goes fine.
the problem comes when flashing any froyo 2.2 sbf, none of them work. In RSD at the reboot stage it just says PASS rather than rebooting, and it sticks at the motorola screen. ive tried with 4.9 and 5.x RSD.
i literally dont know what to try next. how can i get onto a froyo rom?
ive tried flashing straight from 2.1 to a CM7 and PAYS rom which didnt work either.
everytime the sbf fails im forced to flash back to JORDN_U3_97.21.51.sbf, which always works fine.
please help

Try 2.3 gb using nandroid + fixed sbf may work n did u wipe b4 n after flashing??
Sent from my MB525 using XDA Premium App

if your on tmobile 2.1, try updating thru settings and download the update ota, or root phone then update via zip, which I think is somewhere in the dev forum. Root first then install 2init.
E. Try redownloading your sbf
Got a Headache? It's all in your Head.

how come some sbfs are 160mb and others 16-17mb?
have you got the link for the tmobile zip??
thx
i did try wiping between roms

if i were u i wouldn't update to 2.2.2
2.1 is much more better and less bugs.
http://forum.xda-developers.com/showthread.php?t=1140839
could be good.
hope it helps.

nogoodusername said:
Try 2.3 gb using nandroid + fixed sbf
Sent from my MB525 using XDA Premium App
Click to expand...
Click to collapse
link please? what does fixed sbf mean? is that the difference between the 160mb and 16-17 sbf files?
i cant update OTA as I dont have a sim card. Wifi only unfortunately!

guys this is the thread that got me in this mess http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
how do i undo this

Stuck with ROM JORDN_U3_97.21.51.sbf
Hello
I know there is a long time for that post.
But I am stuck, exactly in the same situation, I flash JORDN_U3_97.21.51.sbf
and now I can't do nothing.
PLEASE HELP !!
Thanks in advance

me too, is your phone working ok on this build?
Hi guys,
how did you get on with getting out of this build and was it working ok on your phones?
if you look at my other post I have no phone signal or capability at all plus plenty of other problems.
Cheers
Tim
I know there is a long time for that post.
But I am stuck, exactly in the same situation, I flash JORDN_U3_97.21.51.sbf
and now I can't do nothing.
PLEASE HELP !!
Thanks in advance[/QUOTE]

timb138 said:
Hi guys,
how did you get on with getting out of this build and was it working ok on your phones?
if you look at my other post I have no phone signal or capability at all plus plenty of other problems.
Cheers
Tim
I know there is a long time for that post.
But I am stuck, exactly in the same situation, I flash JORDN_U3_97.21.51.sbf
and now I can't do nothing.
PLEASE HELP !!
Thanks in advance
Click to expand...
Click to collapse
[/QUOTE]
try this
http://forum.xda-developers.com/showthread.php?t=1486731

Is your battery charged ?
MB525 red lense

timb138 said:
Hi guys,
how did you get on with getting out of this build and was it working ok on your phones?
...
Thanks in advance
Click to expand...
Click to collapse
[/QUOTE]
Flash the JDGC_U6_2.1.3.0 SBF
Then root with SuperOneClick and proceed as per the guides.

Thank you, Jalal-jap, Thank you God!!!
Oh my god!
Thank you soooooooo much Jalal-jap.
Many thanks also to dlhxr for bringing this to xda and to d4d9 on mfunz for finding this gem.
My phone is fully restored to 2.2.2 froyo!
I haven't checked camera because of possible flash burn out mentioned in dlhxr's post but battery and all other functions are now fully working and I have a phone signal again!!!!
This definately looks like an original motorola build and is very responsive & smooth. All be it most of the menu's are in Chinese.
At last a solution to all those bricked defys at the bottom of drawers, lets see what the developers can do with it to make further improvements on the defy.
---------- Post added at 10:21 AM ---------- Previous post was at 09:35 AM ----------
OK now for the good stuff.
I followed the guide here http://forum.xda-developers.com/showthread.php?t=1807899 and it works but see below for observations.
I haven't repeated the instructions below so read the other post this is not a guide.
ran superoneclick and it took much longer than before - it reboots twice so don't disconnect until its finished.
ran 2ndint old version - 1.4.2 and installed 2nd init no problems - had earlier problems with latest 2ndinit in that it installed but i never got the blue led to boot into recovery, possibly due to the state my kernel and boot system were in but the older one definitely works.
rebooted into boot menu vol down @ blue led
cleared user data, cache, devit cache
installed cm10 zip from sd card
rebooted and then realised i hadn't recleared cache, opened recovery again on boot (@ blue led)
cleared cache and rebooted again.
chinese boot screen logo came up for about 30 secs (dont panic) then the spinning CyanogenMod wheel for a while then it started jelly bean!!
All seems fine except I dont have a battery icon at present and the red led is illuminated (thinking about it I accidentally wiped the battery data when clearing the davik so this may be my bad!)
Never used jellybean before so gonna have a play, try overclocking / undervolting again for a while then post back.
I`m one big happy bunny right now and thanks again to all of you that helped directly or indirectly to get me to this point

timb138 said:
Oh my god!
Thank you soooooooo much Jalal-jap.
Many thanks also to dlhxr for bringing this to xda and to d4d9 on mfunz for finding this gem.
My phone is fully restored to 2.2.2 froyo!
I haven't checked camera because of possible flash burn out mentioned in dlhxr's post but battery and all other functions are now fully working and I have a phone signal again!!!!
This definately looks like an original motorola build and is very responsive & smooth. All be it most of the menu's are in Chinese.
At last a solution to all those bricked defys at the bottom of drawers, lets see what the developers can do with it to make further improvements on the defy.
---------- Post added at 10:21 AM ---------- Previous post was at 09:35 AM ----------
OK now for the good stuff.
I followed the guide here http://forum.xda-developers.com/showthread.php?t=1807899 and it works but see below for observations.
I haven't repeated the instructions below so read the other post this is not a guide.
ran superoneclick and it took much longer than before - it reboots twice so don't disconnect until its finished.
ran 2ndint old version - 1.4.2 and installed 2nd init no problems - had earlier problems with latest 2ndinit in that it installed but i never got the blue led to boot into recovery, possibly due to the state my kernel and boot system were in but the older one definitely works.
rebooted into boot menu vol down @ blue led
cleared user data, cache, devit cache
installed cm10 zip from sd card
rebooted and then realised i hadn't recleared cache, opened recovery again on boot (@ blue led)
cleared cache and rebooted again.
chinese boot screen logo came up for about 30 secs (dont panic) then the spinning CyanogenMod wheel for a while then it started jelly bean!!
All seems fine except I dont have a battery icon at present and the red led is illuminated (thinking about it I accidentally wiped the battery data when clearing the davik so this may be my bad!)
Never used jellybean before so gonna have a play, try overclocking / undervolting again for a while then post back.
I`m one big happy bunny right now and thanks again to all of you that helped directly or indirectly to get me to this point
Click to expand...
Click to collapse
good luck

to tidy up and give pointers to anyone else that ends up on this thread from a search.
The battery ? icon and red led issue has now been fixed using the red lense fix for cm10. A bit strange as I have a green lense defy but presume its the red lense / defy+ kernel in the chinese BL6 rom that has caused the issue.
I originally installed the 2013 cm10 2nd boot daily over the bl6 froyo, but then reflashed using 2013 daily cm10 1st boot version to see if it was 2nd boot version problem but no difference.
As that problem is fixed I have overclocked to 1200Mhz and the phone is working much better than it ever has.
battery is lasting a full day which it often didn't using stock at 800MHz so the latest build is obviously much more efficient.
One thing I noticed after flashing back to the 1st build rom is that my wifi signal is much weaker than it was on the 2nd boot version but as I have now set everything up and got the phone set up as I want it I wont change back for a while, it works and that's the main thing.
my settings are:
25vsel1 @ 300mhz
42vsel2 @ 650mhz
60vsel3 @ 1200mhz
threshold set at 90%
very stable, no hangs or reboots, cpu mflops 1 core = 30.1
Quadrant full benchmark results = 1560
good enough for me!!
No other issues found as yet.
Thanks to all who helped once again - hopefully I can pass it on in the future.

[Q] Defy won't go past the boot logo

Good day everyone! I would like to ask for some help if it wouldn't bother.
I previously have WajkIUI 1.10.21 installed on my 2nd init. I have installed the Multiboot plugin (http://forum.xda-developers.com/showthread.php?t=1364659) and installed the CM9 12-2-2012 build on 2nd boot.
However when I updated the 2nd boot to CM9 12-11-2012 build, the 2nd boot stays stuck on the red M logo. Because of that, I installed the "kernel" on 2nd boot which was supposed to boot the build. Unfortunately, it only resulted to a boot loop for my CM9.
When I tried to boot from 2nd init (which still has my WajkIUI), it suddenly stopped booting as well. I tried to recover using my recovery file but to no avail, 2nd init still won't boot.
So my phone's condition now is: it is able to run CWM recovery on both 2nd boot and 2nd init. Will I still be able to boot my 2nd init? Will I still be able to restore to my latest recovery file? If yes, can anyone guide me on how to fix my 2nd init boot?
Thank you very much everyone!

I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok

esok44 said:
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
Click to expand...
Click to collapse
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )

arvs0z said:
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
Click to expand...
Click to collapse
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data

esok44 said:
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
Click to expand...
Click to collapse
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.

arvs0z said:
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
Click to expand...
Click to collapse
Yeah it is....
AHHHHH damn it.
hmmmm well nevermind, think i will stay with ICS...
titanium backup works, so maybe as a tip for you:
install old rom,
make backup,
install ics,
restore backup,
some data may be back

Yes, I tried that before but for some reason, during restore, Ti force closes on my ICS.
Anyway, I'm fine without my old data for now Thanks Esok

same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?

die2mrw007 said:
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
Click to expand...
Click to collapse
try removing the battery. then put it back in and power up. see if it boots up. depending on which cm7 rom you were using, there's a known "stuck in boot" problem and removing battery method will overcome it.

^ Yes, try removing the battery and restarting the phone. One other solution could be applying the 2.2 Kernel after the installation of CM7 (only if you are using Defy and the base ROM of CM7 is 2.2) because I tried installing a CM7 nightly and had to apply the kernel

Kernal
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?

phatboyjr said:
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
Click to expand...
Click to collapse
are you saying you were still on stock rom and you tried to install cm7? what was your stock rom and have you flashed any full sbf? what were the steps you did to install cm7?

Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..

to install CM7 follow the steps in this faq :
http://forum.xda-developers.com/showthread.php?t=1065798

phatboyjr said:
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
Click to expand...
Click to collapse
so far so good. could be the rom you were flashing. were you trying to flash the nightlies by any chance? all the latest nightlies do not come with the kernel. you either have to flash the stable release first, or the cm7-kernel-signed.zip, inorder to have the correct kernel before you can flash the nightlies.
do not flash any full gb sbf or you can get yourself in trouble.

[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] Downgrading from 2ndboot to CM9/10

Dear All,
I am using MB526 (Defy+) and I have updated my phone to 2nd boot nightly by Quarx. (Thanks a lot for your great work buddy).
Now, I have a problem, since then My phone is running very slow, email taking time to showup. Messages taking time, Phone app also very slow.
I tried searching the entire XDA community but unable to find the post to downgrade from 2ndboot nightly to CM9, i liked CM9 best with great battery backup.
Can you please help me with, How to Downgrade from 2ndboot to CM9, I have not taken any nandroid backup and need to do it really fast.
Any help will be highly appreciated. Please help Quarx and team.
Regards,
Amit Sharma
Thanks everyone for help, my Defy+ is working absolutely fine now. with CM9 currently.

[email protected] said:
Dear All,
I am using MB526 (Defy+) and I have updated my phone to 2nd boot nightly by Quarx. (Thanks a lot for your great work buddy).
Now, I have a problem, since then My phone is running very slow, email taking time to showup. Messages taking time, Phone app also very slow.
I tried searching the entire XDA community but unable to find the post to downgrade from 2ndboot nightly to CM9, i liked CM9 best with great battery backup.
Can you please help me with, How to Downgrade from 2ndboot to CM9, I have not taken any nandroid backup and need to do it really fast.
Any help will be highly appreciated. Please help Quarx and team.
Regards,
Amit Sharma
Click to expand...
Click to collapse
- What version are you on? Tried the newest nightly from November 9th? It runs like a charm!
If you want to downgrade anyways, go ahead as follows:
- First of all you should save your apps with Titanium Backup or similar.
- Afterwards enter the CWM-Recovery and make a full backup (in case something goes wrong, you can go back CM10)
- Make a full wipe
- Install CM9 + ICS Gapps
- Boot your phone
- Install Titanium Backup from PlayStore
- Restore your apps. IMPORTANT: Don't restore apps that are only working with Android 4.1.x (like anything Google-related) This might give you trouble (force close e.g.). You should install these apps from the play store again.

Swift2603 said:
- What version are you on? Tried the newest nightly from November 9th? It runs like a charm!
If you want to downgrade anyways, go ahead as follows:
- First of all you should save your apps with Titanium Backup or similar.
- Afterwards enter the CWM-Recovery and make a full backup (in case something goes wrong, you can go back CM10)
- Make a full wipe
- Install CM9 + ICS Gapps
- Boot your phone
- Install Titanium Backup from PlayStore
- Restore your apps. IMPORTANT: Don't restore apps that are only working with Android 4.1.x (like anything Google-related) This might give you trouble (force close e.g.). You should install these apps from the play store again.
Click to expand...
Click to collapse
Thanks for the update, I am using "CM10-20121109-NIGHTLY-mb526" - 9th November one, But my phone is not working properly, dont know the reason for the same.
I tried using the mentioned to go on CM9 but it says that your phone is restricted and you need to do full wipe to use it, I tried CM9 and 10 but nothing works.
I am facing these problems currently.
- Lock Screen takes time after pressing power key (2-3 seconds)
- Contacts are not showing properly, most of the time not responding.
- Phone app also not responding properly, very Slow
Please help if you can, Appreciate your support. I am using MB526 (Defy+) with red lense, if it help.
Regards,
Amit Sharma

Build of 0211 is better than 0911
I agreed with Mr. Amit I am trying all roms of 2nd boot Quarks.
I also felt that some apps / games runs slow on 0911 hence turn back to 0211. ** with update for cm file manager.

avi_tandel said:
I agreed with Mr. Amit I am trying all roms of 2nd boot Quarks.
I also felt that some apps / games runs slow on 0911 hence turn back to 0211. ** with update for cm file manager.
Click to expand...
Click to collapse
avi_tandel; thanks for your help, can you help me with the way to downgrade to CM9? someone please, please, please help.
Regards,
Amit Sharma

For the downgrade to CM9:
-DataWhipe/Fullwhipe
-Install the Cm9 nightly you want
-install Gapps
-Format Cache/Dalvik Cache
(I recommend a Nandroid of your running System so that you can return if the installation fails)
And btw. i would recommend CM7.2 for example Whiterabbit1.7.1
CM10 is way too slow in my opinion(Yes Slimbean and everything else is also slow)

Steveletack said:
For the downgrade to CM9:
-DataWhipe/Fullwhipe
-Install the Cm9 nightly you want
-install Gapps
-Format Cache/Dalvik Cache
(I recommend a Nandroid of your running System so that you can return if the installation fails)
And btw. i would recommend CM7.2 for example Whiterabbit1.7.1
CM10 is way too slow in my opinion(Yes Slimbean and everything else is also slow)
Click to expand...
Click to collapse
Dear Friends, I did the same but unable to login now. it says
Encryption unsuccessful
Encryption was interrupted and cant complete. As a result, the data on your phone is no longer accessible.
Please help dear friends. please save me.
Regards,
Amit Sharma

[email protected] said:
Dear Friends, I did the same but unable to login now. it says
Encryption unsuccessful
Encryption was interrupted and cant complete. As a result, the data on your phone is no longer accessible.
Please help dear friends. please save me.
Regards,
Amit Sharma
Click to expand...
Click to collapse
EDIT: I just saw your post in the other thread. Would you mind to mark this as solved? Thx
Perhaps you should describe more detailed what you are trying to do when the error message pops up, and you should give the error message word by word.
I am not familiar with data encryption but your post sounds as if you have lost your data partition now. If that is the case you should completely wipe your phone and start over with flashing a fixed sbf-file. That would be the smartest way to rescue your smartphone (sorry, couldn't withstand :cyclops

[Q] Cannot install any CM7.X (result in a bricked Defy+)

Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!

lucasfpaixao said:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
Click to expand...
Click to collapse
I have the same problem! but with a Defy (green lense)

bufa said:
I have the same problem! but with a Defy (green lense)
Click to expand...
Click to collapse
I just got the same problem yesterday. The bootloader screen came with with an error. I FLASHED AN SBF, AND THEN AFTER INSTALLING SNDINIT, I FORMATTED SYSTEM AND DATA TO EXT3 USING BOOTMENU. NOW CM7.2 RUNS FINE.

/tmp softlink
lucasfpaixao said:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
Click to expand...
Click to collapse
it sounds to me that it can be a problem with /tmp softlink - you need to remove the softlink and create /tmp as a new directory ( I can't post links yet, but if you search for "defy+ /tmp softlink" you get a nice guide as a first result) Hope that help!

workaround with partitions
hotdog125 said:
I just got the same problem yesterday. The bootloader screen came with with an error. I FLASHED AN SBF, AND THEN AFTER INSTALLING SNDINIT, I FORMATTED SYSTEM AND DATA TO EXT3 USING BOOTMENU. NOW CM7.2 RUNS FINE.
Click to expand...
Click to collapse
Thanks for the tip. Maybe the problem was the file system. Yesterday I tried a lot of times with other CM7.X resulting in the same problems. I get bored and needed to solve as soon as possible this phone (that is my mom's). So I tried CM10. It worked without problems as worked in the very same phone (mine).
So I think hotdog125 is right but I haven't tested formatting the partition to ext3 yet. I searched on the web about CM7 partition support but I cannot find any secure information about it.
I will remain my mom's phone in CM10 by now. It's working well.
Does anyone know how a documentation about CyanogemMod versions and partition support?

To install CM7 u need SndInitDefy 1.4.2
lucasfpaixao said:
Hi folks. I have a problem with CM7.X (tried update-cm-7.1.0-jordan-signed.zip and cm-7.2.0-jordan.zip) ona DEFY+ (MB526) with stock ROM (which means from the ROM from the local mobile telephony).
I cannot install any CM7 ROM. I result in a "bricked phone" forcing me to restore it according to this guide: http://forum.xda-developers.com/wiki..._Bootloader_v7
I tried it 3 times with 2 ROMS: (2 times with update-cm-7.1.0-jordan-signed.zip and 1 time with cm-7.2.0-jordan.zip).
It results in a Bootloader error (Err:A5,70,00,00,23)
UPDATE: I try one more time with cm-7-20130301-NIGHTLY-jordan.zip (it is confuse that CM 7.2 is market as "stable" but there is new CM 7.2 market as "nightly". In this case the phone reboots to the M logo, I can get to the recovery mode but the phone frozes in the red motorola logo after it (forcing me to take the battery out).
I restored this phone again using the DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRETBR_P018_A016_M001_HWp3_Service1FF.sbf.gz
But I still want to install the CM 7.2.
OLD: Now the phone is restored to the SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
Andoird version 2.3.6
Kernel version
2.6.32.9-ge281b6e
[email protected] #1
Build number
4.5.1-134-DFP-231
I already checked the MD5 of the downloaded zip files.
I have another DEFY+ phone with CM10 working perfectly. I never got problems in the process. I can't understand why it always "brick" this another DEFY+ (mom's phone) when installing CM7. I get no erros on the installation process. I'm using the SndInitDefy_2.3.apk.
Yes, I wiped data/factory reset and wiped cache partition before I installed the zip.
What is missing?
Thanks in advance!
Click to expand...
Click to collapse
Your problem is that you ar using the SndInitDefy_2.3.apk that is for ICS and JB i had the same problem when i flashed my MB525 whit CM 7.2 By jordan i was lucky that i backed up my phone and was able to restore the stock rom whitout RSDLite. After i recoverd to stock rom i uninstalled SndInitDefy_2.3 and installed SndInitDefy 1.4.2 and i was able to flash CM 7.2 whit no problem hope this information help's you :good:

ionix2727 said:
Your problem is that you ar using the SndInitDefy_2.3.apk that is for ICS and JB i had the same problem when i flashed my MB525 whit CM 7.2 By jordan i was lucky that i backed up my phone and was able to restore the stock rom whitout RSDLite. After i recoverd to stock rom i uninstalled SndInitDefy_2.3 and installed SndInitDefy 1.4.2 and i was able to flash CM 7.2 whit no problem hope this information help's you :good:
Click to expand...
Click to collapse
Thanks a lot for the answer. I think you are absolutely right.
As far as I know there is no information about bootloaders and CM 7/9/10 compatibility. Does anyone know some place about it? It should have a documentation to prevent problems like this.

Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.
Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom
The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.
The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.
And lastly, formatting to ext3 is required only when downgrading from jb builds
Sent from my MB526 using Tapatalk 2

thekguy said:
Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.
Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom
The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.
The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.
And lastly, formatting to ext3 is required only when downgrading from jb builds
Click to expand...
Click to collapse
thekguy, thank you for the explanations.
I've read something about kernel and ROM compatibility. But, as I remember, this is a problem for old Defy phones with green lens and not for Defy+ phones. So I never care about the kernel version and also the guides for installing custom ROMs never report compatibility of the kernel version for Defy+ users.
Where we can find trustable documentation about ROM and kernel compatibility?

thekguy said:
Firstly, there's no link between boot loader version and cm7/9 compatibility. Your boot loader version may only influence your kernel version(froyo or gb), which is defy and defy+ build respectively, used for gb based roms.
Also, the notion that 2ndinit versions are incompatible with any rom is again wrong. In fact, you should always use the latest one(2.3 I believe). I have been using that version to install any rom from gb to jb over the stock rom
The OP should use the defy+ builds compatible with the gb kernel for cm7; I think the problem is that the defy build is based on the froyo kernel and when the kernel included in cm7 replaces the newer gb kernel(from the stock sbf), the boot loader error is triggered.
The reason why cm10 works perfectly is because of the custom kernel used in that build making the stock kernel version irrelevant to some extent.
And lastly, formatting to ext3 is required only when downgrading from jb builds
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Being on BL7 does not mean that one cannot use CM7, but it may mean that CM9/10 compatibility is hampered and does not guarantee that it will work. Is his mother's Defy+ also on DFP231? If not, then that may explain it...
And do not use MB525 CM7 builds on a Defy+, there's a different kernel. CM10 works because it uses 2ndboot, but CM7 relies on 2ndinit, therefore the GB kernel is of importance. You cannot downgrade from a GB kernel from a BL7 stock ROM to a froyo MB525 kernel.

Since defy and defy+ do not share a stock kernel by default(a defy+sbf can be installed on defy) this issue arises. You have to use the defy+ builds for gb roms and for newer roms there's no such problem
Sent from my MB526 using Tapatalk 2

Hi guys, I really need some help.
This Defy+ (MB256, my mom's phone) is wierd.
Remembering: The first thing I tried with this phone was flash CM7.1 but it fails. I needed to recover it from SBF, and it recovered without problems for two or three times while I was trying to flash CM7.
I finally gave up and tried CM10 and it worked! So I leave this phone with this system.
The problem is: this is a unstable version. The reboots and the broken reboots (that needs to wipe to factory reset and install every app again) was driving me nuts (and my mom too).
So I decided to install CM7.2 that is much, much, much more stable on it.
First, I install CM7.2 on my DEFY+ (i also have the same mb526). I downgrade it from CM11 successfully. Yes, I formatted the partition to ext3 before and it worked like a charm! And I see that CM7.2 is really much more stable on this device. So, I just wanted to make the same with my mom's phone.
And the problems started again. But now is worst!
First, after wipe and formatted the partition to ext3 and flashed CM7.2 without erros. So I tried to reboot BUT the Recovery bootloader advises me something like: "there is no operating system, are you sure you would like to continue?"
I simply did it. I get a blank screen. No Bootloader, no M logo, nothing.
And now I'm almost stucked trying to revive it. I already tried some SBF for DEFY+, anyone recovers that phone.
The exactly two I used before ( SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar and DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRE TBR_P018_A016_M001_HWp3_Service1FF.sbf.gz) failed.
1- The first SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar get the phone stuck on a yellow triangle with a exclamation, NO RECOVERY MENU (when turn it on holding vol -).
2- The second simply boots to a blank screen. Anything. Nothing shows. I actually see the screen turning on (backlight) but not is printed on the screen.
EDIT: I forgott to say that with the last cited SBF I get to bootloader with this error: A5,69,35,00,27 after the phone boots with M logo when trying to boot it normally.
I can still use RSD Lite to flash SBF files. I tried some others:
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF (2).sbf.gz gives me the same triangle with explamation.
I already tried to make a force reset according to this:
https://www.youtube.com/watch?v=Rji_wEAxnVo
But it simply not shows the menu itens, the brightness of the screen changes (more and less) when I tap simultaneously on Vol + and Vol -. But any recovery menu option shows on the screen.
I'm stuck, and I'm almost hopeless. But I now there's something to do to recover it.
Please, could someone help me!!!?

lucasfpaixao said:
Hi guys, I really need some help.
This Defy+ (MB256, my mom's phone) is wierd.
Remembering: The first thing I tried with this phone was flash CM7.1 but it fails. I needed to recover it from SBF, and it recovered without problems for two or three times while I was trying to flash CM7.
I finally gave up and tried CM10 and it worked! So I leave this phone with this system.
The problem is: this is a unstable version. The reboots and the broken reboots (that needs to wipe to factory reset and install every app again) was driving me nuts (and my mom too).
So I decided to install CM7.2 that is much, much, much more stable on it.
First, I install CM7.2 on my DEFY+ (i also have the same mb526). I downgrade it from CM11 successfully. Yes, I formatted the partition to ext3 before and it worked like a charm! And I see that CM7.2 is really much more stable on this device. So, I just wanted to make the same with my mom's phone.
And the problems started again. But now is worst!
First, after wipe and formatted the partition to ext3 and flashed CM7.2 without erros. So I tried to reboot BUT the Recovery bootloader advises me something like: "there is no operating system, are you sure you would like to continue?"
I simply did it. I get a blank screen. No Bootloader, no M logo, nothing.
And now I'm almost stucked trying to revive it. I already tried some SBF for DEFY+, anyone recovers that phone.
The exactly two I used before ( SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar and DFL_U3_4.5.2_51-50_SIGNED_USADEFYB15RETBRLA007.0R_STABLE45LADEFYRE TBR_P018_A016_M001_HWp3_Service1FF.sbf.gz) failed.
1- The first SBF DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar get the phone stuck on a yellow triangle with a exclamation, NO RECOVERY MENU (when turn it on holding vol -).
2- The second simply boots to a blank screen. Anything. Nothing shows. I actually see the screen turning on (backlight) but not is printed on the screen.
EDIT: I forgott to say that with the last cited SBF I get to bootloader with this error: A5,69,35,00,27 after the phone boots with M logo when trying to boot it normally.
I can still use RSD Lite to flash SBF files. I tried some others:
DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF (2).sbf.gz gives me the same triangle with explamation.
I already tried to make a force reset according to this:
https://www.youtube.com/watch?v=Rji_wEAxnVo
But it simply not shows the menu itens, the brightness of the screen changes (more and less) when I tap simultaneously on Vol + and Vol -. But any recovery menu option shows on the screen.
I'm stuck, and I'm almost hopeless. But I now there's something to do to recover it.
Please, could someone help me!!!?
Click to expand...
Click to collapse
Hi, the black screen is typical when the flashed stock ROM is wrong. You need to found the correct SBF. Your Mom's Defy is an MB526 right? We must be assume that have originally a bl6 sbf (gingerbread ROM 2.3.5). Beginning with a this Cain of ROM if don't work try with a bl7 ROM. Ever you need beginning from more down to highest.
Enviado desde mi MB526 mediante Tapatalk

Thank you!
Casteleugim said:
Hi, the black screen is typical when the flashed stock ROM is wrong. You need to found the correct SBF. Your Mom's Defy is an MB526 right? We must be assume that have originally a bl6 sbf (gingerbread ROM 2.3.5). Beginning with a this Cain of ROM if don't work try with a bl7 ROM. Ever you need beginning from more down to highest.
Enviado desde mi MB526 mediante Tapatalk
Click to expand...
Click to collapse
Hi @Casteleugim. Thank you! Your advice was correct. I tried this ROM: http://www.mediafire.com/download/rsdmersgb0j4uyo/DEFYPLUS_U3_4.5.1-134DFP231.rar.gz
And the phone boots again with this wierd chinese ROM.
I said that this phone is wierd, so I think this wierd ROM solve it`s dependencies! :victory:
Thank you!