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
Hello Guys,
I am in a serious problem which i am not able to solve since long time. I am facing a serious issue in my Motorola Defy+ / Mb526. I was running cm 10, then i flashed my phone once, then i tried to root it once again but i was getting "read only file system error/ No root permission error". But now even after flashing my phone my previious data is also not erased. I am not able to root it. I searched a lot but i'm not getting any answer so i started a new thread. Please help me to root my phone without which it is useless,...............emergency.........:crying::crying:
Which cm10 build do you use?
Cm10 is usually rooted
Sent from my MB526
juli9797 said:
Which cm10 build do you use?
Cm10 is usually rooted
Sent from my MB526
Click to expand...
Click to collapse
My phone was rooted at that time running JB 4.1.2. After that i flashed my phone so i lost the root permissions,then i tried to root it again and got the errors.
What did you flashed after that?
The 1204 build does nothave root permissions it is a known bug.
Sent from my MB526
Is there any solution for that
Sent from my GT-S5830 using Tapatalk 2
I think you 2 are in a misunderstanding here...
Viraj, have you flashed a stock, Motorola ROM?
Whatever is the case, you should have been more specific in the first post
Hi all, I've been reading DEV section for few months by now, in order to get confident in getting CM10 on my defy+.
Yet, I haven't well understood wether my current configuration will ease the process or not.
Would someone kick in with very appreciated info?
Here's my current setup:
defy+ with stock 2.3.4
kernel 2.6.32.9
build 4.5.1-134_DFP-89
the phone has been rooted with SuperOneClick, and has 2ndInit v.2.3 installed.
I have access to bootmenu, and have already performed a "backup all".
I've heard rumors about BL5 systems not being straigtforward to be flashed with CM10.
Neither is available a FullSBF for this particular version of android for me to restore the phone as it was when I bought it (so I'm a little worried).
Thanks in advance, manuele
Try directly flashing cm10 first, wiping data and dalvik cache first. Then sometimes cm10 may reboot once without loading up fully, so just let it be. If still stuck then flash dfp 231(your region/carrier one) and repeat above steps
Sent from my MB526 using xda premium
This sounds like trial&error, tnx anyhow. I will be more specific with my question:
is it possible to operate CM10 in defy+ from a BL5 stock?
Some people have, some people couldn't. I understand your question but it is a probability at best
Sent from my MB526 using xda premium
I didn't want to post this in development... to be brief, I had a Defy during the CM7 days, then I gave it to somebody else and didn't follow the Defy threads when CM9 went out. As such, I do not know how it was possible to boot a different kernel.
Unless I got it all wrong, in CM10 Quarx is working on a modified 2.6 and a 3.0 kernel, which wasn't something deemed possible due to the locked bootloader and missing Motorola signing key. What changed?
Czehop user from milestone thread has booted last year in September a custom kernel with the old method 2ndboot but he achieved to boot with the radio. The old 2ndboot method was but without radio (phone).
Sent from my MB526 using xda app-developers app
Hi,
I hope I made this in the right section but I've got myself into a really nasty problem and I know how to fix it after spending full 10 hours. Maybe this will help anybody.
I re-used my Arc after a while and learned about custom roms and all. I've updated to Stock 2.3.4 - Stock 4.0.4 - Ultrakitkat 2.0.1 - Stock 4.0.4 (back because of trying to compare performances between custom and stock) - Ultimate HD 5.0.1.
When going from Ultrakitkat to Stock 4.0.4, after a day I woke up and found my phone rebooting Android on a loop while in the wall-charger. Went to take a shower and the phone was dead.
Charger didn't work, put it on my laptop USB and went on, only to find the battery at 100%. When disconnecting the phone, it immediately went blank and didn't turned on. I've looked for this problem for so many hours and tried flashing my romand kernel for some time (including phone drops dead WHILE in flashing) and trying out different way's to connect and boot but nothing worked. Installed many battery tools and apps but still nothing.
I;ve searched a lot and didn't found any conclusion anywhere, but combining every information online I've solved it!!
Apperantly there is an error inbetween roms, that when you go from custom rom + certain kernels, back to stock rom, it stops recognizing the battery.
To solve this (for me it worked):
Flashtool stock TFT 4.0.4
Fastboot flash the LUPUSV16 kernel (the magic trick!)
Turn on phone, and put it on a charger for 15 minutes, it should start recharging somewhere and show the correct battery %
I wanted to use the Ultimate HD just for a try and when flashing (I use Advanced Stock Kernel) + Ultimate HD
DO NOT WIPE BATTERY STATS! This will recreate the problem.
This worked for me and I hope this will help someone too who's thinking there is a problem with the battery.
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
0 or 100 percent battery
hridayharia said:
Mostly reflashing the kernel does the job
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
Leaving the phone turned off for some hours worked for me!
Thank you!
if you dont want see this problem
do not downgrade to stock kernel
Same issue here.. after fastbooting stock ftf.. Phone not charging and not recognized in fastboot/flashmode
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Swapyyyyy said:
Guys worked for me
Flash rush kernel after downgrading and tada its done.
Its just coz rush recognizes the hardware chip algorithm for battery stats
Sent from my Xperia Arc S using Tapatalk
Click to expand...
Click to collapse
yes, it works flashing other kernel but i encountered a another problem. I lost some of the apps and keep geeting crashing report from diferent sistem apps Does some know how to extract those battery fix from those kernel am apllly it to stock kernel?