Related
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
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
Guys i know nemesis is banned on xda but still i need immediate help.
Guys yesterday i downloaded and flashed Nemesis V2 on my phone then it was working fine it was on stock kernal after that i put my phone on charge and went to sleep when i wake up i saw the phone has not charged a bit rather it has decreased to 17%.
I thought it is a kernel problem and flashed percy gnu#10. But then also the problem persisted rather it was worsened then i switched off the device and put it to charge and it worked well. I tried flashing stock rom via odin but the problem remains same. Guys plz help asap.
DO NOT mention the name of banned roms in xda. BTW, i think it is caused by:
1. Battery itself
2. Internal Hardware
3. Charger adapter
Sent from my little beast using xda-app
Might be hard ware problems,
But you could try deleting battery stats in CWM in might help.
install stock rom twice
or maybe you charge it in electric shutdown lol:silly:
Hardware error for sure, get another charger or get your phones's charging slot tested.
Sent from my **** using xda premium
Look at your charging slot and charger plug.
Maybe it has dust or something in.
Had the same issue few weeks ago, i had some tomato sauce in there, dont ask, i dont know
Anyway i solved this special kind of brick with a simple toothpick and cleaned everything.
Thnx guys changing the charger helped me out.
Requesting moderator to close the thread.
Sent from my room using sgy hyp8.
souroking said:
guys i know nemesis is banned on xda but still i need immediate help.
Guys yesterday i downloaded and flashed nemesis v2 on my phone then it was working fine it was on stock kernal after that i put my phone on charge and went to sleep when i wake up i saw the phone has not charged a bit rather it has decreased to 17%.
I thought it is a kernel problem and flashed percy gnu#10. But then also the problem persisted rather it was worsened then i switched off the device and put it to charge and it worked well. I tried flashing stock rom via odin but the problem remains same. Guys plz help asap.
Click to expand...
Click to collapse
it might be that your battery is no longer usable
buy a new one
You have no choice！install a new Rom and it will work well！helpful to you！
Sent from my V926 using Tapatalk 2
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
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?