[Q] [Defy+] Downgraded To CM7 from CM9 & Battery Shows Question Mark - Defy Q&A, Help & Troubleshooting

Last night I rooted my Defy+ with CM7(latest nightlies from defy-cm.net), applied battery and camera fix, everything worked perfectly and I enjoyed it.
I tried little experimenting then installed CM9(usedEpsylon builds) and flashed the kernel mentioned here(http://forum.xda-developers.com/showthread.php?t=1432100&page=3) but then I noticed it had lot of bugs and my phone started having a lot of weird reboots.
So I thought of reverting back to CM7 and then problem of the battery popped up. Battery now shows a question mark and I dont know whether it could charge or not. After reading a lot I thought it would be better to revert to CM9 just incase if the battery isn't charging and I'd have to find a workaround for charging.
Although I love CM9 very much but I can't stick to it because of the camera and a lot of instability.
After studying forums I realised it may be because of the incompatible kernel for CM7. So the only way I could get teh original kernel is by flashing the original SBF. But the problem arises is that I cant find the same build for my device and I am little skeptical about flashing with different SBF. Also I have no nandroid backup as such. Nearest I could find a SBF was with 4.5.1-134_DFP-1321. Also I have gone through all the Walter79 posts and his SBF collection too and it doesnt have the SBF for my DEFY+.
Can somebody guide me with the workaround?
My DEFY+ specifications:
system version - 45.0.891.MB526,AsiaRetail.en.03
model number - mb526
android version - 2.3.4
baseband version - epu93_u_00.60.00
kernel version - 2.6.32.9-gbdd614e [email protected]#1
build number - 4.5.1-134_DFP-891

I am having the same problem, even after resoring to the original the battery keeps giving me a question mark and the phone shuts down.
I can boot it into recovery by plugging it in but whatever rom I flas the battery keeps going to question mark.
I am becoming a little sacred I killed my phone now..

Same problem with me. flashing my stock nandroid backup did not solve the problem..
http://forum.xda-developers.com/showthread.php?t=1569336
I put everything back to stock, because without the mcguyver trick I am not able to charge my battery..
I am sending it RMA this monday

So you say that even if I flash a SBF, the battery problem won't solve?? I thought it was just because of a kernel incompatibility otherwise why would the battery charge while I'm using CM9?
Sent from my MB526 using XDA

Oh!!! It seems there are two threads of the same name!!!! I replied here
You may find a solution
---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------
Hi,
My Defy+ also came with the same SBF version however I updated it to another one and now service center updated it to another one(which is unrootable!!) So be careful while choosing the SBF(Don't worry I will tell you which one should be safe! ). First:
There are issues with battery charging with CM9. moreover you should have tried Quarx's build CM9 for Defy+. Both CM7 and CM9_Defy+ of quarx are more stable!! however, as per memory serves I remember flashing CM7 for Defy when I had the version of SBF you have, so I believe even CM9 for Defy should work(No need to flash extra kernels if you flash the Defy versions of CM).
Now coming to the SBF part you may go for this SBF(from my dropbox). It is 4.5.1-134_DFP-1321 version SBF. That will update your phone to 2.3.6 and BL6. Thus you won't be able to downgrade to any Froyo kernels and will have to use CM7 and CM9 for Defy+ builds(use Quarx's build this time). However NEVER flash the version with DFP-231!!! It has BL7 and is still not rootable!!! ( Thanks to dumb service center people I am stuck with this!!)

It happened because of some network problem here and I don't see any option to delete the other post.
I'm downloading the SBF right now and wish that the problem gets solved and I can use CM7 again with no battery issue.
Sent from my MB526 using XDA

I did flash Quarks new nightly that was just posted. All worked fine at first and then I rebooted and since then it will no longer boot. If I plug it in I can get into recovery but if I let it try to start up I get a big battery with a question mark in it. I will try this sbf and thank you so much for helping

Also I notice that your sbf file is quite huge compared to the same file by walter79.. Is it just that he zipped it and you didn't?
Sent from my MB526 using XDA

Puckying said:
I did flash Quarks new nightly that was just posted. All worked fine at first and then I rebooted and since then it will no longer boot. If I plug it in I can get into recovery but if I let it try to start up I get a big battery with a question mark in it. I will try this sbf and thank you so much for helping
Click to expand...
Click to collapse
Welcome Make sure you don't drain your battery much. I have seen many users using CM9 with this prob. However there is a battery fix if you want to try. Search it in Q&A also someone posted recently. Sorry don't have time now to search!
meherranjan said:
Also I notice that your sbf file is quite huge compared to the same file by walter79.. Is it just that he zipped it and you didn't?
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Its of big size because:
1.) I didn't zip it.
2.) Its a full SBF not fixed. A fixed SBF has its cmg39 deleted which contains BL version and also all system image! Dis is done to maintain downgradability and thus needs a nandroid backup too!

pranks1989 said:
Welcome Make sure you don't drain your battery much. I have seen many users using CM9 with this prob. However there is a battery fix if you want to try. Search it in Q&A also someone posted recently. Sorry don't have time now to search!
Its of big size because:
1.) I didn't zip it.
2.) Its a full SBF not fixed. A fixed SBF has its cmg39 deleted which contains BL version and also all system image! Dis is done to maintain downgradability and thus needs a nandroid backup too!
Click to expand...
Click to collapse
I added the battery fix as well but then the battery had already drained. It went really fast from 90% to completely dead.
I shall try the McGyver trick today and see if it will respond again after that.

Puckying said:
I added the battery fix as well but then the battery had already drained. It went really fast from 90% to completely dead.
I shall try the McGyver trick today and see if it will respond again after that.
Click to expand...
Click to collapse
Oh okay..!! Ya then try the McGyver trick.. But be careful at it or you may end up frying your battery!!

I am a bit worried about that too so it is still laying there, ready to try but my courage lacks.
My husband is an elctro man and will be home tomorrow so I think I will wait till then.
I wonder after flashing the new sbf it will again recognise the battery..

I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf

Puckying said:
I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf
Click to expand...
Click to collapse
My problems are solved as well I did not want to work on CM9 anymore. To much problems and instability.
http://forum.xda-developers.com/showthread.php?p=24340090#post24340090

fokkeh said:
My problems are solved as well I did not want to work on CM9 anymore. To much problems and instability.
http://forum.xda-developers.com/showthread.php?p=24340090#post24340090
Click to expand...
Click to collapse
Puckying said:
I reflashed cm 9 and now everything is up and running again. Battery is charging.
I will see how it holds up over time , if all else fails I can still flash the full sbf
Click to expand...
Click to collapse
Good to know the problem is solved! Probably you should wait till a stable CM9 (Defy+) comes out

I flashed a full sbf, the one that was posted but now can no longer receive calls or texts.
I can ring out so there is a connection. but nothing comes through. I have saerched all over the place , installed the baseband changer. But no incoming calls...

Puckying said:
I flashed a full sbf, the one that was posted but now can no longer receive calls or texts.
I can ring out so there is a connection. but nothing comes through. I have saerched all over the place , installed the baseband changer. But no incoming calls...
Click to expand...
Click to collapse
The SBF I posted is for India. You should flash an SBF that suits your region. You said you installed baseband switcher but baseband switcher works only after rooting and you need to make correct changes. So, since you are flashing full SBF I suggest flash the one for your region. There should not be any prob then!

Yes I am doing so now Thanks again. Steep learning curve here
And I rooted at once with super one click
---------- Post added at 03:52 PM ---------- Previous post was at 03:03 PM ----------
No difference, still no incoming calls..
Phew! Fixed. No more modding for a bit..well not today anyway

pranks1989 said:
The SBF I posted is for India. You should flash an SBF that suits your region. You said you installed baseband switcher but baseband switcher works only after rooting and you need to make correct changes. So, since you are flashing full SBF I suggest flash the one for your region. There should not be any prob then!
Click to expand...
Click to collapse
No problems here (In the Netherlands) with your ROM (asia version).

Thanks guys for the answers. I'm now running CM9(quartz build) with no kernel flashing. Camera works fine and everything as well. I think I'll stick to this for sometime. Although I see little lag in the homescreen animation and drawers stack animation. But as it is a nightly and still under development, it is quite expected. Also I'll keep using it anyway so that I can help in the development of CM9 by bug and automatic reports submissions.
This was all possible because of the SBF mentioned here..
Sent from my MB526 using XDA

Related

[Q] Rooting a U8800 that's currently on 2.2...

Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.
If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.
dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.
A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800
You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.
as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...
The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!
Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.
First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).
Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.
What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?
Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?
You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.
and now i have blue screen.. what can i do? or have i bricked it?
Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder
basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..
Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.

How to get the latest roms working on 525?

I seem to be having problems with flashing the 2nd boot quarx roms
I do a full data + cache + dalvik wipe, install the rom + gapps, then wipe cache + dalvik and restart the phone..
It boots up and is laggy as hell but it shouldn't be because no one else has such problems.
Do I have to flash a kernel or something? I've never flashed one before and all my previous cm7, cm9, cm10 (not 2nd boot) worked perfectly without it
Any help? I'm still on a very old build and wanna use the current ones but can't seem to get it to work
I'm using a regular green lens 525
Sent from my MB525 using Tapatalk 2
I've been installing these roms on 2nd init.. Do I HAVE to install it on 2nd boot only?
Sent from my MB525 using Tapatalk 2
sixaxis94 said:
I seem to be having problems with flashing the 2nd boot quarx roms
I do a full data + cache + dalvik wipe, install the rom + gapps, then wipe cache + dalvik and restart the phone..
It boots up and is laggy as hell but it shouldn't be because no one else has such problems.
Do I have to flash a kernel or something? I've never flashed one before and all my previous cm7, cm9, cm10 (not 2nd boot) worked perfectly without it
Any help? I'm still on a very old build and wanna use the current ones but can't seem to get it to work
I'm using a regular green lens 525
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I can't even get my green lens to boot into any build past 0912... I've had no problem with cm7, cm9 or cm10 until 0924 and later. I'm sorry I can't help but I'm throwing my hat in the ring..
bulbouscorm said:
I can't even get my green lens to boot into any build past 0912... I've had no problem with cm7, cm9 or cm10 until 0924 and later. I'm sorry I can't help but I'm throwing my hat in the ring..
Click to expand...
Click to collapse
Many ppl have/had this problem (me too).
The workaround is flashing another sbf.
Could you gave details of your parent sbf?
sixaxis94 said:
I've been installing these roms on 2nd init.. Do I HAVE to install it on 2nd boot only?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
No, 2ndboot is set automatically after flash. And the only thing u should change in bootmenu is vsels. Governor must be interactive - don't change it
Your workaround might be similar as above, especially if u your last stock ROM was froyo 2.2.1
sixaxis94 said:
I seem to be having problems with flashing the 2nd boot quarx roms
I do a full data + cache + dalvik wipe, install the rom + gapps, then wipe cache + dalvik and restart the phone..
It boots up and is laggy as hell but it shouldn't be because no one else has such problems.
Do I have to flash a kernel or something? I've never flashed one before and all my previous cm7, cm9, cm10 (not 2nd boot) worked perfectly without it
Any help? I'm still on a very old build and wanna use the current ones but can't seem to get it to work
I'm using a regular green lens 525
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
To get rid of the laggs you should also install the kernel update http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_18.10_v4.zip after flashing the Nightly from 18th-Oct
Then you should be fine
corrinti said:
Many ppl have/had this problem (me too).
The workaround is flashing another sbf.
Could you gave details of your parent sbf?
No, 2ndboot is set automatically after flash. And the only thing u should change in bootmenu is vsels. Governor must be interactive - don't change it
Your workaround might be similar as above, especially if u your last stock ROM was froyo 2.2.1
Click to expand...
Click to collapse
I've never messed with sbfs before so I have no idea.. Right now I don't even have a pc on me to use rsdlite or anything (traded mine for an ipad, haha)
Is it difficult to flash a new sbf?
Swift2603 said:
To get rid of the laggs you should also install the kernel update http://quarx2k.ru/cm10-2ndboot-nightly-defy(+)/update_for_18.10_v4.zip after flashing the Nightly from 18th-Oct
Then you should be fine
Click to expand...
Click to collapse
I flash this right after I flash the rom right?
A random question, does anyone have this problem: when someone calls, it sometimes takes like 10 seconds for the phone to match the number to an existing contact.. As in, if my mom calls, it shows up her phone number and takes around 10 seconds for "mom" to appear as the caller
Sent from my MB525 using Tapatalk 2
sixaxis94 said:
I've never messed with sbfs before so I have no idea.. Right now I don't even have a pc on me to use rsdlite or anything (traded mine for an ipad, haha)
Is it difficult to flash a new sbf?
I flash this right after I flash the rom right?
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
Yes flash it right after the ROM.
Flashing an sbf is not difficult, but you will need a PC.
Regarding your random question: It should be fixed in the latest Nightly. I just tried it
Swift2603 said:
Yes flash it right after the ROM.
Flashing an sbf is not difficult, but you will need a PC.
Regarding your random question: It should be fixed in the latest Nightly. I just tried it
Click to expand...
Click to collapse
The only sbf I've heard of is something like 'Nordic deblur'.. Is that what I'm supposed to flash?
And also, is it worth doing all that? I mean, should I just stay with the stuff I have now and wait for a rom that's compatible without the sbf stuff? I don't really have much of a problem since I'm only using my phone for calling, texting and playing music
Regarding the side question, thanks.. It is kinda irritating, but I can live with it
Another side question.. Has epsylon stopped working on the defy permanently?
sixaxis94 said:
The only sbf I've heard of is something like 'Nordic deblur'.. Is that what I'm supposed to flash?
And also, is it worth doing all that? I mean, should I just stay with the stuff I have now and wait for a rom that's compatible without the sbf stuff? I don't really have much of a problem since I'm only using my phone for calling, texting and playing music
Regarding the side question, thanks.. It is kinda irritating, but I can live with it
Another side question.. Has epsylon stopped working on the defy permanently?
Click to expand...
Click to collapse
Well, with a limited usage you can stay with your last built. Don't suppose that newer CM10, at least till any bigger change in the system, will be again compatible with some old kernels.
And no, Epsylon just has temporary other job but probably will be back this year, sooner or later
Ps. Flashing sbf is not difficult, what requires some knowledge or just reading is choosing of a proper sbf file
Another ps. if u don't want now to mess with sbf but need fast, reliable system with great battery why not give a chance to CM7.2?
corrinti said:
Many ppl have/had this problem (me too).
The workaround is flashing another sbf.
Could you gave details of your parent sbf?
Click to expand...
Click to collapse
p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
corrinti said:
And the only thing u should change in bootmenu is vsels. Governor must be interactive - don't change it
Click to expand...
Click to collapse
Why not? I changed it to Smartass without problems. (Now I changed it back to Interactive)
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
I have got defy green lense.
earlier I was on cm7.2 with cm7 froyo kernel. after that cm10-nightlies, then aokp-kayant.
I recently flashed 18/10quarx v4-update as below:
1.data-cache-dalvik wipe
2.flash18/10, then flashv4, then flash gapps.
3.wipe cache-dalvik
4.reboot.
its all working well.
In the above sequence I have noticed many times that if cm10 is not working, first flash cm7.2 with cm7 froyo kernel & then flash cm10, it happened to be working on three defys I know.
also my boot logo is "Google" which I think is related to cm7 froyo kernel.
all these are observations, no technical expertise? do try?
I forgot to mention one thing that on first boot it appeared as if I have stucked on boot loop. after boot animation again on boot logo then again boot animation. but it booted finally.. so have patience.. first boot is different from earlier night lies.
nastys said:
Why not? I changed it to Smartass without problems. (Now I changed it back to Interactive)
Sent from my flying overclocked Motorola Defy+ MB526 with CyanogenMod 10 and custom kernel using XDA app
Click to expand...
Click to collapse
I didn't say you cannot, I meant you shouldn't as the phone will most probably work not so stable or more laggy or will not take your changes into account etc etc
---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------
bulbouscorm said:
p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
Click to expand...
Click to collapse
This is a standard problem for US T-mobile users. In your case to go past 12/09 build (as even 24/09 could not work for you) flash CEE 2.2.2 build - than you will be able to flash the newest builds and do not lost your warranty if you have one valid
See also here
sasays said:
I have got defy green lense.
earlier I was on cm7.2 with cm7 froyo kernel. after that cm10-nightlies, then aokp-kayant.
I recently flashed 18/10quarx v4-update as below:
1.data-cache-dalvik wipe
2.flash18/10, then flashv4, then flash gapps.
3.wipe cache-dalvik
4.reboot.
its all working well.
In the above sequence I have noticed many times that if cm10 is not working, first flash cm7.2 with cm7 froyo kernel & then flash cm10, it happened to be working on three defys I know.
also my boot logo is "Google" which I think is related to cm7 froyo kernel.
all these are observations, no technical expertise? do try?
I forgot to mention one thing that on first boot it appeared as if I have stucked on boot loop. after boot animation again on boot logo then again boot animation. but it booted finally.. so have patience.. first boot is different from earlier night lies.
Click to expand...
Click to collapse
I'll check it out
Sent from my MB525 using Tapatalk 2
This is a standard problem for US T-mobile users. In your case to go past 12/09 build (as even 24/09 could not work for you) flash CEE 2.2.2 build - than you will be able to flash the newest builds and do not lost your warranty if you have one valid
See also here
Click to expand...
Click to collapse
This worked perfectly. Thank you so much.
sasays said:
I have got defy green lense.
earlier I was on cm7.2 with cm7 froyo kernel. after that cm10-nightlies, then aokp-kayant.
I recently flashed 18/10quarx v4-update as below:
1.data-cache-dalvik wipe
2.flash18/10, then flashv4, then flash gapps.
3.wipe cache-dalvik
4.reboot.
its all working well.
In the above sequence I have noticed many times that if cm10 is not working, first flash cm7.2 with cm7 froyo kernel & then flash cm10, it happened to be working on three defys I know.
also my boot logo is "Google" which I think is related to cm7 froyo kernel.
all these are observations, no technical expertise? do try?
I forgot to mention one thing that on first boot it appeared as if I have stucked on boot loop. after boot animation again on boot logo then again boot animation. but it booted finally.. so have patience.. first boot is different from earlier night lies.
Click to expand...
Click to collapse
I tried this method twice but it's not working :/
I guess I'll have to do that sbf thing sometime.. Crap
Okay so I've managed to get hold of a computer and I've read up on how to flash an sbf but I have a few questions..
1. If I flash a full sbf, will I have to root my phone, put clockwork mod etc again?
2. How do I know what my parent SBF is? I bought my defy in India, if that helps
3. Which SBF should I flash? I saw walter's link to all the stock SBFs but do I have to flash one of those or something else?
Sent from my iPad using Tapatalk HD
sixaxis94 said:
Okay so I've managed to get hold of a computer and I've read up on how to flash an sbf but I have a few questions..
1. If I flash a full sbf, will I have to root my phone, put clockwork mod etc again?
2. How do I know what my parent SBF is? I bought my defy in India, if that helps
3. Which SBF should I flash? I saw walter's link to all the stock SBFs but do I have to flash one of those or something else?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
So we know you have green lens, now we need your BL version. It is required to find proper sbf file (I'm not sute about Asian sbfs, usually for Europe green lense are BL4).
Thus go to this thread and download BL See and Root tool for use with your PC - as it is Chinese, then see post #309 in this thread how to use it.
And yes, if you flash full sbf then you have to root it with SuperOneClick and install 2ndInit - that's all.
But you can also try to flash directly one of the sbfs from above mentioned thread - you can find there also newest 2nd boot builds in sbf form
corrinti said:
So we know you have green lens, now we need your BL version. It is required to find proper sbf file (I'm not sute about Asian sbfs, usually for Europe green lense are BL4).
Thus go to this thread and download BL See and Root tool for use with your PC - as it is Chinese, then see post #309 in this thread how to use it.
And yes, if you flash full sbf then you have to root it with SuperOneClick and install 2ndInit - that's all.
But you can also try to flash directly one of the sbfs from above mentioned thread - you can find there also newest 2nd boot builds in sbf form
Click to expand...
Click to collapse
Ran it, it says BL version is 4.
I checked the stock SBF page again, and noticed something. My baseband is set to 3.4.3-331 and there are only 2 SBFs with that number ("Taiwan" and "Hong Kong/Taiwan"). Should I flash one of them?
Also, my phone came unlocked. It didn't come with a contract or anything, if that helps

CyanogenMod for Defy+

Hey
My brother has a Defy, and I have a Defy+. He strongly recomended me to install CM on my Defy+, and after I saw CM7 on his Defy I really grew to like it.
The Problem is, I can't see an official CM support for Defy+:
http://www.cyanogenmod.org/devices/motorola-defy
As the link states: "Official CyanogenMod support is ONLY for the Motorola Defy, NOT the Motorola Defy+. "
So what are my options instead? I'm looking for a good rom, preferably android 3 or 4 that must support Hebrew.
Currently using rooted stock 2.3.6 rom.
Thanks in advance!:victory:
here to you: http://download.cyanogenmod.org/?device=jordan_plus&type=nightly CM7 for Defy+
anyway, good roms are CM9 by Epsylon, Wiui, CM10 by Quarx and Xperia D. look in the development section
I'm about to do this for my Defy+ for the first time too. It's got the latest firmware update pushed out from Motorola (BL7?) so I'm following the gizmolord tutorial for rooting it (not allowed to hyperlink yet) for rooting it. If anyone has the time for checking it for errors I should be aware of I'd be most grateful.
Anyway, my real question for this post is: is CM7.2 for upgrading Defy (not +) and CM7 effectively the same thing for Defy+?
Edit: Another question: how do I back up (save an image of - "nandroid"? my phone before I wipe data/factory reset the phone, which seems to be required before rooting it?
I realise there are CM9's for Defy+ but I reckon I'll wait around for JB+ (10.2?) to get to a stable point before I go with moving away from Gingerbread.
Thanks for any comments/answers in advance.
ricketyclik said:
I'm about to do this for my Defy+ for the first time too. It's got the latest firmware update pushed out from Motorola (BL7?) so I'm following the gizmolord tutorial for rooting it (not allowed to hyperlink yet) for rooting it. If anyone has the time for checking it for errors I should be aware of I'd be most grateful.
Anyway, my real question for this post is: is CM7.2 for upgrading Defy (not +) and CM7 effectively the same thing for Defy+?
Edit: Another question: how do I back up (save an image of - "nandroid"? my phone before I wipe data/factory reset the phone, which seems to be required before rooting it?
I realise there are CM9's for Defy+ but I reckon I'll wait around for JB+ (10.2?) to get to a stable point before I go with moving away from Gingerbread.
Thanks for any comments/answers in advance.
Click to expand...
Click to collapse
Firstly if gizomolord's tutorial is a program that roots the device for you, don't use it, because BL7 devices (I'm fairly sure yours would be) need to be rooted manually. You can follow the instructions in my signature under 'Status' for the files and instructions needed to root your device.
Secondly, I'm not quite sure what you mean in your first question. CM7 is Gingerbread and CM7.2 would just be a 'more up-to-date' version.
About the nandroid, from what I know you can only perform a nandroid after rooting your device. As for preparing to root there are a few things I did:
You can back up your SMS and Call Logs using programs from the Google Play Store. During rooting, your sdcard will be safe and so you can back most thing onto it.
You can back up your contacts to Google.
You can remember what apps to download from the Google Play Store once you have rooted.
That's all I did. There may be a way to backup but nandroid backs-up your current ROM which means you need root to be able to do so.
I hope that helps you! And if you need any help with rooting don't be afraid to ask (plus I wrote instructions and added files to my spare DropBox which you can find in my signature)
z3ro-grav1ty said:
Firstly if gizomolord's tutorial is a program that roots the device for you, don't use it, because BL7 devices (I'm fairly sure yours would be) need to be rooted manually. You can follow the instructions in my signature under 'Status' for the files and instructions needed to root your device.
Secondly, I'm not quite sure what you mean in your first question. CM7 is Gingerbread and CM7.2 would just be a 'more up-to-date' version.
About the nandroid, from what I know you can only perform a nandroid after rooting your device. As for preparing to root there are a few things I did:
You can back up your SMS and Call Logs using programs from the Google Play Store. During rooting, your sdcard will be safe and so you can back most thing onto it.
You can back up your contacts to Google.
You can remember what apps to download from the Google Play Store once you have rooted.
That's all I did. There may be a way to backup but nandroid backs-up your current ROM which means you need root to be able to do so.
I hope that helps you! And if you need any help with rooting don't be afraid to ask (plus I wrote instructions and added files to my spare DropBox which you can find in my signature)
Click to expand...
Click to collapse
Thanks very much for that z3ro. I did use your tutorial in the end (gizmodo's was similar, but less detailed) but since I'd downloaded their sbf's I used those. I also did the sms and call log backing up. There is, as far as I can tell, no way to make a backup of a rom of a device that isn't rooted, so I just gave up on that idea and stepped into the void. It all worked a treat. I'm feeling so confident now I think I might try Jelly Bean
ricketyclik said:
Thanks very much for that z3ro. I did use your tutorial in the end (gizmodo's was similar, but less detailed) but since I'd downloaded their sbf's I used those. I also did the sms and call log backing up. There is, as far as I can tell, no way to make a backup of a rom of a device that isn't rooted, so I just gave up on that idea and stepped into the void. It all worked a treat. I'm feeling so confident now I think I might try Jelly Bean
Click to expand...
Click to collapse
Good for you mate If you need any further help, don't hesitate to ask
pochopsp said:
here to you: http://download.cyanogenmod.org/?device=jordan_plus&type=nightly CM7 for Defy+
anyway, good roms are CM9 by Epsylon, Wiui, CM10 by Quarx and Xperia D. look in the development section
Click to expand...
Click to collapse
Hmmm, they are all good looking, I'll try the CM7 first and then decide what's next.
Thank you so much for this
How do I install? Usual cleaning & wiping in Recover Mode, then "install from zip file" option, wipe again and done?
ricketyclik said:
Thanks very much for that z3ro. I did use your tutorial in the end (gizmodo's was similar, but less detailed) but since I'd downloaded their sbf's I used those. I also did the sms and call log backing up. There is, as far as I can tell, no way to make a backup of a rom of a device that isn't rooted, so I just gave up on that idea and stepped into the void. It all worked a treat. I'm feeling so confident now I think I might try Jelly Bean
Click to expand...
Click to collapse
Good to know you found your answers
z3ro-grav1ty said:
Good for you mate If you need any further help, don't hesitate to ask
Click to expand...
Click to collapse
Thank you for helping the other guy !
TheBirdOfHermes said:
Hmmm, they are all good looking, I'll try the CM7 first and then decide what's next.
Thank you so much for this
How do I install? Usual cleaning & wiping in Recover Mode, then "install from zip file" option, wipe again and done?
Click to expand...
Click to collapse
wipe data, chache and dalvik chache, flash cm7, flash gapps, reboot
z3ro-grav1ty said:
Good for you mate If you need any further help, don't hesitate to ask
Click to expand...
Click to collapse
Thanks z3ro. Here's one for you: I've got Quarx's CM7.2 running, after trying CM7, and both go through battery much faster than stock Motorola - which had a nice battery saver setting, not available in the CM's.
I've read that this is as much about which kernel you're using as anything. So:
Can I flash a new SBF without flashing a new ROM? If so, is it advisable? and
I can't figure out how to do a nandroid backup. I've got 2nd init installed, but cant see the option anywhere in its menu. Does a nandroid backup back up just the ROM and settings, or those plus the SBF?
ricketyclik said:
Thanks z3ro. Here's one for you: I've got Quarx's CM7.2 running, after trying CM7, and both go through battery much faster than stock Motorola - which had a nice battery saver setting, not available in the CM's.
I've read that this is as much about which kernel you're using as anything. So:
Can I flash a new SBF without flashing a new ROM? If so, is it advisable? and
I can't figure out how to do a nandroid backup. I've got 2nd init installed, but cant see the option anywhere in its menu. Does a nandroid backup back up just the ROM and settings, or those plus the SBF?
Click to expand...
Click to collapse
Ok firstly I'll answer about nandroid backup. Once you have 2ndInit install, you'll encounter a blue led on bootup. If you press Volume Down then you'll be taken to the bootmenu screen. From there select recovery and then custom recovery. You'll now see the CWM recovery screen. Now select backups and restore and this is where you can make your nandroid backup. Select backup all and let it finish.
As for battery drainage, I've been using CM10 with now problems at all. In fact my current configuration Quarx's CM10 (17/02 build) and JellyX Kernel (22/03) has been exceptionally good! Very stable, just may take a few tries (as in a couple of flashing attempts) to get it to boot up
Now with sbf's you should really note that there is a stock SBF (which you can locate a list of in the Development section) and if you own a Defy+ there are some sbf's needed to root your phone.
As far as ROM's are concerned, to change from one ROM to another you need to perform a full wipe (data/cache/dalvik) then you flash the ROM and gapps and the another cach and dalvik wipe and then reboot your device.
I'm not entirely sure what you mean by flashing a new sbf without flashing a new ROM. All I can say is: you use the stock SBF to restore everything (unroot + go back to stock android version) or it is used, as I said, to help root the Defy+. ROM's do not require the flashing of a new sbf. Kernel's don't require you to flash a new sbf either, however it is suggested to reflash (or just flash) the ROM that you want to use.
------I'll link something here in a bit-------
EDIT: Here! <--- just a general flash procedure if you need
If you encounter any problems along the way, restore to stock SBF, re-root, install 2ndInit, and flash again.
Hopefully that answers most things
z3ro-grav1ty said:
Ok firstly I'll answer about nandroid backup. Once you have 2ndInit install, you'll encounter a blue led on bootup. If you press Volume Down then you'll be taken to the bootmenu screen. From there select recovery and then custom recovery. You'll now see the CWM recovery screen. Now select backups and restore and this is where you can make your nandroid backup. Select backup all and let it finish.
As for battery drainage, I've been using CM10 with now problems at all. In fact my current configuration Quarx's CM10 (17/02 build) and JellyX Kernel (22/03) has been exceptionally good! Very stable, just may take a few tries (as in a couple of flashing attempts) to get it to boot up
Now with sbf's you should really note that there is a stock SBF (which you can locate a list of in the Development section) and if you own a Defy+ there are some sbf's needed to root your phone.
As far as ROM's are concerned, to change from one ROM to another you need to perform a full wipe (data/cache/dalvik) then you flash the ROM and gapps and the another cach and dalvik wipe and then reboot your device.
I'm not entirely sure what you mean by flashing a new sbf without flashing a new ROM. All I can say is: you use the stock SBF to restore everything (unroot + go back to stock android version) or it is used, as I said, to help root the Defy+. ROM's do not require the flashing of a new sbf. Kernel's don't require you to flash a new sbf either, however it is suggested to reflash (or just flash) the ROM that you want to use.
------I'll link something here in a bit-------
EDIT: Here! <--- just a general flash procedure if you need
If you encounter any problems along the way, restore to stock SBF, re-root, install 2ndInit, and flash again.
Hopefully that answers most things
Click to expand...
Click to collapse
Thanks z3ro. On reading this I realize I'm confusing SBF's with kernels. An SBF is kernel + ROM? If so, when I flashed to CM7.2 I flashed kernel as well? Quarx's instructions say flash Froyo (which I didn't do, having a Defy+) then install the ROM.
BTW, my phone's rooted, hence having CM7.2 loaded.
ricketyclik said:
Thanks z3ro. On reading this I realize I'm confusing SBF's with kernels. An SBF is kernel + ROM? If so, when I flashed to CM7.2 I flashed kernel as well? Quarx's instructions say flash Froyo (which I didn't do, having a Defy+) then install the ROM.
BTW, my phone's rooted, hence having CM7.2 loaded.
Click to expand...
Click to collapse
Yeah I had a feeling you confused the two. Well an sbf (I guess) is a kernel+ROM. Ok having a defy+ makes things a lot easier because that's the model I have as well.
Quarx's nightlies come with their own kernel so when you flash them, the install the kernel. (Go into phone settings > scroll down to the bottom and click on about phone > check to see if kernel version is there, it should be the same as your current ROM)
Then again, I went straight to CM10, but I'm fairly sure CM7 should be the same.
Well since you are rooted, I just recommend performing a nandroid backup, then flashing whatever ROM (and Kernel if you want) you feel comfortable with.
I recommend Quarx's 18/03 build for CM10 (before his experimental wi-fi builds), ParanoidAndroid 2.5.3 (however there hasn't been much activity of late), and the combination I mentioned earlier of Quarx's 17/02 and JellyX 22/03.
TheBirdOfHermes said:
Hey
My brother has a Defy, and I have a Defy+. He strongly recomended me to install CM on my Defy+, and after I saw CM7 on his Defy I really grew to like it.
The Problem is, I can't see an official CM support for Defy+:
http://www.cyanogenmod.org/devices/motorola-defy
As the link states: "Official CyanogenMod support is ONLY for the Motorola Defy, NOT the Motorola Defy+. "
So what are my options instead? I'm looking for a good rom, preferably android 3 or 4 that must support Hebrew.
Currently using rooted stock 2.3.6 rom.
Thanks in advance!:victory:
Click to expand...
Click to collapse
leave cm7 n flash your phone with cm10 on any of the links provided here
http://forum.xda-developers.com/showthread.php?t=1768702
choose the latest one maybe around march24th build. its perfectly stable.
press thanks if helped.
my device:>>> Motorola defy plus(running on cm10.1 by quarx)
z3ro-grav1ty said:
I recommend Quarx's 18/03 build for CM10 (before his experimental wi-fi builds)
Click to expand...
Click to collapse
This. I love it! No more radical battery drain, and seems really stable. Nice clean UI too
I was expecting JB to be a pain to learn, but on the face of it it seems to be quite similar to GB, at least in UI terms.
ricketyclik said:
This. I love it! No more radical battery drain, and seems really stable. Nice clean UI too
I was expecting JB to be a pain to learn, but on the face of it it seems to be quite similar to GB, at least in UI terms.
Click to expand...
Click to collapse
I'm glad you fixed your wi-fi drain, it seems that problem is quite evident in CM7 builds
z3ro-grav1ty said:
I'm glad you fixed your wi-fi drain, it seems that problem is quite evident in CM7 builds
Click to expand...
Click to collapse
I don't think it was related to wifi. I hardly ever have it on.
ricketyclik said:
I don't think it was related to wifi. I hardly ever have it on.
Click to expand...
Click to collapse
sorry I meant battery not wi-fi
I want to install too
shubhu2604 said:
leave cm7 n flash your phone with cm10 on any of the links provided here
http://forum.xda-developers.com/showthread.php?t=1768702
choose the latest one maybe around march24th build. its perfectly stable.
press thanks if helped.
my device:>>> Motorola defy plus(running on cm10.1 by quarx)
Click to expand...
Click to collapse
Hey Bro,
I want to install CM10.1 too....but i am confused which link to download and each link shows multiple file. Also if i install CM10.1 how much my internal memory will decrease? Since originally we are having 1.2Gb in DEfy +. What are the things that not working in the version that you installed??
Thanks in advance.
jountha said:
Hey Bro,
I want to install CM10.1 too....but i am confused which link to download and each link shows multiple file. Also if i install CM10.1 how much my internal memory will decrease? Since originally we are having 1.2Gb in DEfy +. What are the things that not working in the version that you installed??
Thanks in advance.
Click to expand...
Click to collapse
Go for CM10, I would not suggest CM10.1 for you yet. The multiple download link each have a date - correspond each date to the changelog on Quarx's thread and choose a stable one (NOT and experimental build) - I suggest 18/03 for you because you don't seem too familiar yet.
z3ro-grav1ty said:
Go for CM10, I would not suggest CM10.1 for you yet. The multiple download link each have a date - correspond each date to the changelog on Quarx's thread and choose a stable one (NOT and experimental build) - I suggest 18/03 for you because you don't seem too familiar yet.
Click to expand...
Click to collapse
does cm10 quarx 18/03 has major bug? eg: battery drain,connectivity problem etc..
currently on cm7.2. wish to upgrade to cm10..

[Q] All ROM works except CM10

Why does only CM10 not work for me?
Known facts:
-Unimportant, but: All ROM I tried worked (many variants of CM 7.x, many variants of CM9, MIUI, WIUI), except the JB ROMs.
-Neither of the working ROMs have, had 2nd boot. (I did not find not-CM10 roms with 2nd boot...)
-With CM10 nightlies before 2013 ~january: after installing CM10 I could not wipe dalvik cache. the screen refreshed when I clicked on it.
-I tried the march 26 nightly, i could wipe dalvik, but it won't boot the same way it did not before.
What happens:
-Switch on, Motorola logo, blue, than red led (which signals it is 2nd boot) and it stucks for a minute, NO boot animation, bootloop
-Overinstalling (CM9 wipe data, cache, dalvik, flash CM10, than flash another CM10 over CM10 without wiping) won't help. For some phones it worked, don't think im so bad.
-I tried clean install from stock
Thoughts:
-It seems like it's losing some kind of permissions about R/W internal memory (thinking from the previous dalvik wipe issue)
-It has (had???) problem with dalvik wiping (before the screen just refreshed upon clicking the menu, now it seems to do what it should)
-It installs really fast...
-It has problem with 2nd boot? Maybe that's why it won't start
-It does not have boot animation. Does not freeze either, so: can it be, that it does not install properly? Problems with drive format?
Something that also came to my mind (idk why):
-Can ext3/ext4 f__k it up?
-How 2nd boot can make it not to start?
Manners I do know nothing about:
-Kernel (can it cause problems?)
-BL version (does it matter?)
Firstly what phone model (MB525 green or red/MB526).
I would highly recommend flashing your stock sbf, re-rooting your phone, installing the latest 2ndInit (2.3), and then flashing CM10.
As far as I know CM10 is ext4, so format to that if you encounter any further problems.
Kernel - stick with what comes in the CM10 nightlies.
BL - depends on your phone.
z3ro-grav1ty said:
Firstly what phone model (MB525 green or red/MB526).
I would highly recommend flashing your stock sbf, re-rooting your phone, installing the latest 2ndInit (2.3), and then flashing CM10.
As far as I know CM10 is ext4, so format to that if you encounter any further problems.
Kernel - stick with what comes in the CM10 nightlies.
BL - depends on your phone.
Click to expand...
Click to collapse
1:MB525 bayer module
2:Tried, same problem
3:format from CWM before flash?
4:should i pre-install any kernel, or not then?
Hi!
I've had the same problem. Also on MB525, red lense. I have not managed to make it work either. Preinstalling kernel does not work for me. Formatting does not work either.
However, there is a possible solution, which I have not had the time to try out yet, and was suggested to me in this thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Simply put, you can try flashing a custom SBF with CM10 pre-loaded on it through RSDLite, and then update to the latest versions. Just head over to this thread over here:
http://forum.xda-developers.com/showthread.php?t=1691901
And try with one of the 2nd boot SBFs. I will also be trying this method out shortly. If you manage to get anything done with this method, please report here, so that I know as well!
-----
If you find this helpful, please hit the Thanks! button! :highfive:
Eneekay said:
Hi!
I've had the same problem. Also on MB525, red lense. I have not managed to make it work either. Preinstalling kernel does not work for me. Formatting does not work either.
However, there is a possible solution, which I have not had the time to try out yet, and was suggested to me in this thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Simply put, you can try flashing a custom SBF with CM10 pre-loaded on it through RSDLite, and then update to the latest versions. Just head over to this thread over here:
http://forum.xda-developers.com/showthread.php?t=1691901
And try with one of the 2nd boot SBFs. I will also be trying this method out shortly. If you manage to get anything done with this method, please report here, so that I know as well!
-----
If you find this helpful, please hit the Thanks! button! :highfive:
Click to expand...
Click to collapse
are you saying that 2ndboot SBFs exist? where have I been? under a rock? my god..
gonna try it in a few days, but i'm scared about the failure as it never worked before, but now you gave me hope thnx. :good:
gyorgyszemok said:
are you saying that 2ndboot SBFs exist? where have I been? under a rock? my god..
gonna try it in a few days, but i'm scared about the failure as it never worked before, but now you gave me hope thnx. :good:
Click to expand...
Click to collapse
Even if you fail, you can always wipe/flash an SBF if necessary and revert to your nandroid backup. I might try it today, if I have enough time, but no promises. When you try, please report here.
It seems I have BL version 5, but from an SBF with a size of ~35mb
Each time my phone went so bad I couldn't get to CWM:
-RSD Lite Flash: Éclair (JORDN_U3_97.21.51.sbf)
-Stock Recovery wipe cache, data
-Root
-install 2nd init
-Restore with cwm backup&restore "2011-06-11.14.14.27" which I downloaded from a guide
-Wipe data, cache, dalvik
-Reboot instantly into Bootloader
-RSD Lite Flash: firmware.sbf with CG31.smg version 5 (downloaded from the same site where "2011-06-11.14.14.27" cwm backup was)
-This flash it fast, cuz the firmware.sbf is ~35mb
-Reboots (via RSD Lite) to Froyo and it's rooted...
So, my BL version is...? 5? How important is this?
I started trying out some of the SBFs. From now on I will be reporting everything on this Thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Eneekay said:
I started trying out some of the SBFs. From now on I will be reporting everything on this Thread:
http://forum.xda-developers.com/showthread.php?t=1782832&page=132
Click to expand...
Click to collapse
It seems like our phones are more alike then the others. Do you usually recover with the fixed sbf and the 2011. dated nandroid backup? whats your cg version? mine's 5. so it's more likely the cause that we have gingerbread CG version...
gyorgyszemok said:
It seems like our phones are more alike then the others. Do you usually recover with the fixed sbf and the 2011. dated nandroid backup? whats your cg version? mine's 5. so it's more likely the cause that we have gingerbread CG version...
Click to expand...
Click to collapse
Yes, I recover the same way you do, and the CG version is the same... This is what I thought as well, that it is because of the Gigerbread CG. I have no idea about any workarounds though...
Eneekay said:
Yes, I recover the same way you do, and the CG version is the same... This is what I thought as well, that it is because of the Gigerbread CG. I have no idea about any workarounds though...
Click to expand...
Click to collapse
-But I don't know if we have the Gingerbread CG like many others, why don't they have this problem? I could guess pretty much people recovered their phone the same way like us...
-It must be something about the kernel the CM10 uses, and the CG version! ...or the drive format (ext3,4)?
-I also read about your failures (in the other topic) flashing modded SBFs, so I definitely won't try them until we have a solution.
-Months earlier I found something about this problem (CMX bootloop), and the user could flash 2nd init CMX, but not 2nd boot. I haven't found that entry since then... And neither did I find 2nd init CMX ROMs.. Quarx must have took it down rendering them useless.
Argh! It's just so annoying! Stuck at ICS, the highest ROM available... And that's so buggy! I use Euroskank CM 7.2 now... But it's ugly (was... I modded it...), and it's like mentally disabled compared to a JB rom...
Are there any other JB defy ROMs out there? Which do not rely upon Quarx's build?
gyorgyszemok said:
-But I don't know if we have the Gingerbread CG like many others, why don't they have this problem? I could guess pretty much people recovered their phone the same way like us...
-It must be something about the kernel the CM10 uses, and the CG version! ...or the drive format (ext3,4)?
-I also read about your failures (in the other topic) flashing modded SBFs, so I definitely won't try them until we have a solution.
-Months earlier I found something about this problem (CMX bootloop), and the user could flash 2nd init CMX, but not 2nd boot. I haven't found that entry since then... And neither did I find 2nd init CMX ROMs.. Quarx must have took it down rendering them useless.
Argh! It's just so annoying! Stuck at ICS, the highest ROM available... And that's so buggy! I use Euroskank CM 7.2 now... But it's ugly (was... I modded it...), and it's like mentally disabled compared to a JB rom...
Are there any other JB defy ROMs out there? Which do not rely upon Quarx's build?
Click to expand...
Click to collapse
CM10 uses ext4, in bootmenu (after you press volume down at the blue led during boot) go to tools and then file systems (something like that) then you can format to ext4 (wipes data and cache).
At the moment that's all I can really help you with because my model (defy+) works differently to yours.
All I can recommend is working from stock. Also isn't there a fix for some MB525 models?
http://forum.xda-developers.com/showthread.php?t=2124536
Sent from my MB526 using xda premium
thekguy said:
http://forum.xda-developers.com/showthread.php?t=2124536
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks! Will check it out.
z3ro-grav1ty said:
CM10 uses ext4, in bootmenu (after you press volume down at the blue led during boot) go to tools and then file systems (something like that) then you can format to ext4 (wipes data and cache).
At the moment that's all I can really help you with because my model (defy+) works differently to yours.
All I can recommend is working from stock. Also isn't there a fix for some MB525 models?
Click to expand...
Click to collapse
I know how to format, but thanks for answering.
It seems the root of the problem comes from the fixed sbf (so called firmware.sbf) with the CG version 5, which does something about downgrading. As stated in the other link we should upgrade to BL7 with a Defy + SBF, but I don't want to make that risk...
SO: The problem, why we can't make CM10 works is that our Defy MB525 has CG31.smg version of 5 from the downgrading fixed SBF!
How to fix that? Should I really upgrade to BL version 7? What can it do with my device?
gyorgyszemok said:
I know how to format, but thanks for answering.
It seems the root of the problem comes from the fixed sbf (so called firmware.sbf) with the CG version 5, which does something about downgrading. As stated in the other link we should upgrade to BL7 with a Defy + SBF, but I don't want to make that risk...
SO: The problem, why we can't make CM10 works is that our Defy MB525 has CG31.smg version of 5 from the downgrading fixed SBF!
How to fix that? Should I really upgrade to BL version 7? What can it do with my device?
Click to expand...
Click to collapse
+1
It seems to me that our beloved Defy is not much worth the trouble anymore... I am staying on CM7 which is amazingly fast and stable, and thinking about grabbing a new Android headset soon...
If you've got a red lens, you can upgrade boot loader version, and you'll have to flash a battery fix for gb and ics roms, and jb will work fine without it. If you have a green lens, then you will not be able to use camera with stock. It will work with jb roms though
Sent from my MB526 using xda premium
thekguy said:
If you've got a red lens, you can upgrade boot loader version, and you'll have to flash a battery fix for gb and ics roms, and jb will work fine without it. If you have a green lens, then you will not be able to use camera with stock. It will work with jb roms though
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Bootloader? Could you point us to the right direction?
You mentioned that the flashing is fast. So i think it may not flash properly. So flash 2 or 3 times with same rom. This happend to my old captivate. Captivate devs suggesting a second flash for their roms. (Only formating was occur during first flash in some devices. Thats why they suggest second flash)
Thanks
Sent from my Motorola Electrify using Tapatalk 2
Eneekay said:
Bootloader? Could you point us to the right direction?
Click to expand...
Click to collapse
You can try flashing a newer sbf( with higher bl version). It seems to work for some people

[RESOLVED] Flashed the wrong SBF

Hi All,
I have a motorola green lens defy and stupid me flashed a DEFY PLUS SBF into it by accident. Now when I try to flash a known working regular defy SBF into it or any other regular defy SBFs, the screen just goes black and does nothing even though RSD lite detects it. When I flash the DEFY PLUS sbf back into it, the red moto logo shows up and then goes into the bookloader showing ERR: A5, 69, 35, 00, 27
The defy plus sbf is DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
I am guessing that its probably permanently bricked since I used the wrong SBF.
Help would be appreciated.
coacoapuffs said:
Hi All,
I have a motorola green lens defy and stupid me flashed a DEFY PLUS SBF into it by accident. Now when I try to flash a known working regular defy SBF into it or any other regular defy SBFs, the screen just goes black and does nothing even though RSD lite detects it. When I flash the DEFY PLUS sbf back into it, the red moto logo shows up and then goes into the bookloader showing ERR: A5, 69, 35, 00, 27
The defy plus sbf is DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.rar
I am guessing that its probably permanently bricked since I used the wrong SBF.
Help would be appreciated.
Click to expand...
Click to collapse
I also tried the SBF on this link but didnt work
http://forum.xda-developers.com/showthread.php?t=1009203
Also wanted to mention that I can't get into CWM nor the screen with the triangle exclamation mark.
You are stuck with the Defy + SBF. That happened to me and I am still using my normal Green lens Defy with a Defy + BL7 SBF on it.
Try to flash a proper BL7 SBF, because you have no other choices. When you find the proper one (with root!!!), you will have to throw a 2ndInit on it and flash a JB or ICS based ROM, because of the camera issue.
Please update this thread with your success!
ToMpI97 said:
You are stuck with the Defy + SBF. That happened to me and I am still using my normal Green lens Defy with a Defy + BL7 SBF on it.
Try to flash a proper BL7 SBF, because you have no other choices. When you find the proper one (with root!!!), you will have to throw a 2ndInit on it and flash a JB or ICS based ROM, because of the camera issue.
Please update this thread with your success!
Click to expand...
Click to collapse
Thanks for your help! I did exxactly what you said and loaded in a BL7 SBF for Defy + and it came alive!
I used DEFYPLUS_U3_4.5.1-134_DFP-2312.sbf.gz
So I guess my question now is how using a Defy+ sbf will affect the phone. Everything seems normal so far, even the camera works. Does it just clock the CPU to 1GHz which is really the only diff between the 2 phones?
coacoapuffs said:
Thanks for your help! I did exxactly what you said and loaded in a BL7 SBF for Defy + and it came alive!
I used DEFYPLUS_U3_4.5.1-134_DFP-2312.sbf.gz
So I guess my question now is how using a Defy+ sbf will affect the phone. Everything seems normal so far, even the camera works. Does it just clock the CPU to 1GHz which is really the only diff between the 2 phones?
Click to expand...
Click to collapse
You won't experience any differences except the Play Store will show your device as a Defy+ (MB526), which is not a problem. You are able to use your phone as it supposed to be, but you should install JUST 2NDBOOT ROMS!!! Otherwise your camera won't work, so you should use CM9, CM10, or CM10.1 both MIUI and "stock". This SBF will overclock your phone as it does with a Defy+, so your stock CPU frequency will be 1GHz. You can leave it stock or you can overclock and undervolt it for better battery life.
I hope I helped you .)
ToMpI97 said:
You won't experience any differences except the Play Store will show your device as a Defy+ (MB526), which is not a problem. You are able to use your phone as it supposed to be, but you should install JUST 2NDBOOT ROMS!!! Otherwise your camera won't work, so you should use CM9, CM10, or CM10.1 both MIUI and "stock". This SBF will overclock your phone as it does with a Defy+, so your stock CPU frequency will be 1GHz. You can leave it stock or you can overclock and undervolt it for better battery life.
I hope I helped you .)
Click to expand...
Click to collapse
Yup! you definitely helped. Saved my life lol. I was this close to getting another phone.
After following your steps and got it running, I followed the link below to get the phone rooted. So now its all good. To bad I cant get back to GB. JB just runs too slow on my defy. Not as snappy as GB. Any who, I did thank your replies, hope it went through!
http://forum.xda-developers.com/showthread.php?t=1542956
coacoapuffs said:
Yup! you definitely helped. Saved my life lol. I was this close to getting another phone.
After following your steps and got it running, I followed the link below to get the phone rooted. So now its all good. To bad I cant get back to GB. JB just runs too slow on my defy. Not as snappy as GB. Any who, I did thank your replies, hope it went through!
http://forum.xda-developers.com/showthread.php?t=1542956
Click to expand...
Click to collapse
Because you have BL7 you are not really able to use CM7 builds, because most of them are not for 2ndBoot phones, EXCEPT MS2GINGER 5, which is for 2ndBoot phones with working camera and tweaked kernel, so it's fast. Give it a try!
http://forum.xda-developers.com/showthread.php?t=1140839
ToMpI97 said:
Because you have BL7 you are not really able to use CM7 builds, because most of them are not for 2ndBoot phones, EXCEPT MS2GINGER 5, which is for 2ndBoot phones with working camera and tweaked kernel, so it's fast. Give it a try!
http://forum.xda-developers.com/showthread.php?t=1140839
Click to expand...
Click to collapse
Yeah, I did find the MS2SGINGER but I believe that one is still blur. I cant stand blur lol.
I am running CM10.1 nightly right now. Hangs up pretty frequently and have to remove battery to reset it.
The only other GB ROM I know that works is DEFYPLUS_U3_4.5.1-134_DFP-231_CN and that's definitely blur.
I will give the CM10.1 a try for a week. I might have to switch to MS2SGINGER and just suck it up with the blur if the CM10.1 turned out unusable.
Not a whole lot of options I have here until 10.1 becomes stable
Ideally I would like MIUI 10.1. I really like the GB versions of MIUI but MIUI10.1 runs even slower than CM10.1
There's one crazy problem that I found with the CM10.1. When the Wifi is on on my Defy, it some how interferes with my computer's Wifi and causes my computer Wifi to not work at all. It was a bit frustrating so I ended up using 3G instead lol. I would report this problem but since I am new I can't post in the development forum.
Ok, CM10.1 ended up freezing up on me again and decided that I had enough of that lol. I did find out that installing a new launcher gets rid of the motoBlur headache from MS2GINGER, so now I got that going smoothly with ADW.
Thanks for your help ToMpI97. I think I am all set to go.
coacoapuffs said:
Ok, CM10.1 ended up freezing up on me again and decided that I had enough of that lol. I did find out that installing a new launcher gets rid of the motoBlur headache from MS2GINGER, so now I got that going smoothly with ADW.
Thanks for your help ToMpI97. I think I am all set to go.
Click to expand...
Click to collapse
Try to install XPERIA D. You should try it. I am using it for 2 weeks and I'm totally satisfied with it. I think this is the best ROM I've ever had on my Defy.
http://forum.xda-developers.com/showthread.php?t=2133698
flash the stock sbf using rsd lite software by entering into bootloader mode(vol + power button).read all in one defy guide for full flashing of sbf files
ToMpI97 said:
Try to install XPERIA D. You should try it. I am using it for 2 weeks and I'm totally satisfied with it. I think this is the best ROM I've ever had on my Defy.
http://forum.xda-developers.com/showthread.php?t=2133698
Click to expand...
Click to collapse
I will definitely try it out if I have to flash again. But I am happy with MS2GINGER right now. Snappy, no issues, very good battery usage.
I am going to try and not mess with the SBFs and new ROMs as much. flashing ROMs is how I got into this mess in the first place Lol. Every time I flash ROMs, something goes wrong and 30 hrs of my life would be gone trying to fix it. So I am done with it for now
ToMpI97 said:
You are stuck with the Defy + SBF. That happened to me and I am still using my normal Green lens Defy with a Defy + BL7 SBF on it.
Try to flash a proper BL7 SBF, because you have no other choices. When you find the proper one (with root!!!), you will have to throw a 2ndInit on it and flash a JB or ICS based ROM, because of the camera issue.
Please update this thread with your success!
Click to expand...
Click to collapse
i did it too
flash a defy+ accdently on a defy red lens and now its working like a defy+ but i am having alot of problems with that/
cm7.2 giving me com.android.phone stop working
or on a miui a hot boot loop
is it a wrong sbf that causing this?
yaniv2203 said:
i did it too
flash a defy+ accdently on a defy red lens and now its working like a defy+ but i am having alot of problems with that/
cm7.2 giving me com.android.phone stop working
or on a miui a hot boot loop
is it a wrong sbf that causing this?
Click to expand...
Click to collapse
That's probably because of the SBF. You can live with it, but you SHOULD INSTALL CM10 or CM10.1 based ROMs. These will solve your problems.:fingers-crossed:
ToMpI97 said:
That's probably because of the SBF. You can live with it, but you SHOULD INSTALL CM10 or CM10.1 based ROMs. These will solve your problems.:fingers-crossed:
Click to expand...
Click to collapse
Its not a heavy rom that eat battary and ram? defy isnt a strong phone
They are quite usable for me atleast. For miui hot boot loop try a data and cachewipe
Sent from my MB526 using Tapatalk 2
Thinking about messing with my phone again. Is MSGINGER and XPERIA D still the only option right now for BL7 and 2ndboot?
bump

Categories

Resources