Hi all, first I would like to start the thread clarifying that I already searched the forums for the solution for this problem.
See, I have a MS2 with two batteries, one generic and one original. Today, I was using the MacGyver method to flash an sbf back to stock rom, and when it finally ended, I realized that the phone was not showing the battery percentage, and said the battery was invalid, (impossible, it came with the phone). So, I thought changing the battery for the generic one would solve the problem, but it didn't. I've tried deleting battery stats, dalvik cache, reflashing the sbf, changing roms (CM10, CM10.1, CM10.2) and still no solution.
Thanks, and sorry for my extremely poor english, it's been a while since I used the language for the last time.
Related
Hi all,
Nasty problem with my 1 month old Motorola Defy+ (MB526)
Last weekend I installed ICS9 from Quarx (20120318 build). I did this using 2ndinit CWM. Made an android backup of my stock setup, I did this over my stock SBF 4.5.1.-134_DFP-74. Used the gapps.zip and battery fix.
The system worked pretty well, but time by time it was unstable. When turned off, it had lots of difficulty to boot up again, lots of reboots and 2-3 battery pulls.
I was planning to flash another ROM when I had the time. Yesterday it worked well, started fully loaded, used it as MP3 for long time, when I went to sleep it was 48% (the accu).
This morning, I stepped in car and phone turned out to be dead. Connected it to my car charger, and it came back to life. However, immediate reboot etc. So I decided to (while driving) put back my stock nandroid backup.
It all turned out well. Stock ROM booted but gave the notice (translation from dutch): "Battery of your device is invalid and cannot be charged. Replace the battery with a battery from your Motorola"
hmm, tried it with my USB cable at the office, and now at home again with the normal charger..
What happened? Any ideas on how to solve this?
The complication is that now my device is rooted and has 2ndinit starter, warranty is more difficult.
Solution: red lens battery fix
I’m not sure it’s exactly the same issue, but my Defy+ totally refuses to charge with Quarx CM9 build 20120318 + CM9 kernel from [1].
Unfortunately I noticed only once the battery was dead empty.
I couldn’t even get it to boot with the USB charger pluged in, and the only way I could get it to boot again was to charge my battery pack in friend’s Defy.
Then I applied the « Battery fix for red lens » provided here [1] which kind of fixed the problem. Now the battery charges again, but it won’t charge over 80/85%.
I had done a « Clean battery stats » from the boot menu after installing CM9 before this whole story, so I don’t know if it had any effect.
If anyone knows better please let me know!
The instability you noticed may be due to the Android debug bug… in CM9 builds. You have to leave Android USB debug (from System params->Debug features, translated from french on, otherwise it will lag like hell most of the time and drain the battery due to the init process eating up the CPU.
[1] http://forum.xda-developers.com/showthread.php?t=1432100
Hi, I installed the battery fix immediatly after flashing the Quarx ROM, so that should not be the problem.
In the meanwhile I have been trying some things with the battery calibration software. That one flawlessy sees that my battery is 100% charged (i did that using the mcguyver method). But, resetting the calibration file on the phone won't help.
In the meantime I have been able to delete all traces (2ndinit boot, titanium backup and unrooted my phone) so I am considering to RMA the phone, no matter the fact how long that is going to take..
Unless, someone here has a last excellent advice..
fokkeh said:
...the mcguyver method...
Click to expand...
Click to collapse
Great! You have just fried your battery (like a few others who tried going McGyver). Get a new battery now and don't use the McGyver method again
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
fokkeh said:
From what do you draw this conclusion?
The battery showed more problems BEFORE i used the mcguyver method than after. When the problems started I never even heard of the method. I used it to regain life in my mobile (which I am using atm) and charge the battery, which was succesfull. Charger over USB does not work (because battery is not recognized), but that problem occured before the mcguyver.
So until now for me it did not cause the problem, but it helped me to be able to use my phone again, much better than before. I performed the method very accurately and I am 100% sure it did not make contact with connectors it should not connect to.
Click to expand...
Click to collapse
Well now that your phone is alive, then go to stock and reclaim warranty! Do RMA.!
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
fokkeh said:
Yes I will, restored everything to stock and deleted trace from MicroSD.
But, I am still annoyed by the fact that my phone will be gone for 3-4 weeks
Click to expand...
Click to collapse
I understand that bro!! Even my phone was away for couple of weeks recently! Just pray they don't flash the latest SBF(BL7_ as they did in mine!
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Puckying said:
Does flashing a full sbf not work either? like this http://forum.xda-developers.com/showthread.php?t=1574651
Click to expand...
Click to collapse
Hi, this morning everything changed again, I decided to give it one more try with the latest Quarx CM9 nightly (20120330), wiped data, flashed nightly.zip, gapps and kernel but waited with the battery. After that I wiped cache, dalvik and battery stats.
Reboot and battery seems alive? very strange. But I don't want the kind of buggy CM9 builds anymore, so decided to put back my 2 hours old nandroid backup, using Restore.
Strangly, battery problem was back again. ****! Than just for fun I did data/cache/dalvik/battery stats wipe on stock, and that did not help either.
Now I am back on CM9 again, but thats running O.K. (battery is working!) but not stable enough for me. CM7 (cannot remember which build) gave the problem as well.
With the latter in mind I think (and thus agree with you) flashing a fresh SBF will probably solve the problem, but I am not 100% sure. I want to be able to put back my stock setup for possible RMA. My stock is 4.5.1.-134_DFP-74 and I cannot find that one on internet. And I cannot put it back to stock otherwise right?
The one Pranks gave you in your post (4.5.1-134_DFP-1321) is that a deblurred one? Because when I put a new one, I would like it to be a deblurred. I hate all the bloatware.
I have no idea, but I think he said it was from his own defy so I am guessing it the complete original blurred thing.
---------- Post added at 01:57 PM ---------- Previous post was at 01:31 PM ----------
I redid the cm9 flashing too and now at least it is telling me the battery is charging. But it stays stuck at a big battery icon and a red led is on.
Will see if it goes past that screen with a bit more juice.
---------- Post added at 02:06 PM ---------- Previous post was at 01:57 PM ----------
Yessss, it started up!
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
fokkeh said:
All is fixed. I flashed the proposed stock non-fixed SBF and now running stock 2.3.6 without any battery problems. Excellent The SBF is rootable.
I removed BLUR by editing build.prop as proposed somewhere on this forum. you have to perform full wipe after editing the build.prop) I am very happy with me new DEBLURRED stock. Titanium can remove other bloatwhere like "cardiotrainer".
Happy
Click to expand...
Click to collapse
Cardiotrainer however for me is one of the most imp app!!
I did a search and looked through the threads, some were similar but none were exactly like mine... which has me worried. also google didn't help... which has me worried
My battery charges, and discharges ( i think) normally. I don't see any problem with the actual usage. But, the battery indicator only updates when it is plugged in or unplugged, or i restart it. while it's running it doesn't update, so i have to guess at the level of battery.
I just bought a "re-certified" one from newegg. it did the latest ICS OTA update immediately after turning it on. It had this problem on stock OTA, but i have since rooted it with ViperMOD (still stock ROM), and the issue is still there.
I have read about battery calibration, deleting battery stats, etc - would these be applicable? how do I actually go about doing it?
Thanks for any info!
I would backup all my data (Using Titanium Backup), backup your ROM then either flash to something new or delete all your data. Obviously you can restore everything once your done but just to see if this is a software or hardware issue.
Have you tried any other battery widget? Does it update in settings -> about tablet -> status and/or settings -> battery?
If not, you should try reflashing like mike suggested.
I have tried "Beautiful Widgets" battery widget, as well as stats - and they all show the same level.
ty, will do. do you have a recommendation for rom? stock like with stability and battery life? no dock...
Android Revolution HD look ok?
thanks again
yeah didn't help. i did a wipe from within CWM, and installed Android Revolution.
Is there anything i can do to wipe to wipe it further, safely? before i go through the process of trying to RMA it.
I am fully charging it and then will reset the battery stats and discharge it, as that's said to be good anyway once in awhile and i don't have anything better to do...
if it comes down to it, how might i unroot before sending this back? i have the image from before flashing, but that was after rooting and installing CWM.
Deleting battery stats won't improve your battery life. It's a MYTH.
http://www.xda-developers.com/andro...-battery-stats-does-not-improve-battery-life/
https://plus.google.com/105051985738280261832/posts/FV3LVtdVxPT
The correct way to calibrate your battery is to discharge it 2-3 times after flashing a new rom/kernel.
Hi! I'm using CM9 (4.1) on my Motorola Defy and I got a problem that seems pretty simple to solve but I can't figure it out.
Recently I had some problems with the SIM card, just to find out I just had to change the baseband to receive signal.
But it seems that after trying to solve that problem playing with recovery (bootmenu), each time I try to change the baseband and I restart so it takes effect, the phone just doesn't remember what I did previously, asking for the Google account all over again. And, obviously, the baseband didn't change as well.
I already tried wiping the cache, doing factory reset, and wiping dalvik and battery stats. Any help would be appreciated
Edit: Just in case, I had the SIM card problem before flashing CM, I mean, just after I rooted the phone
Hi!
I've been using cooked ROMS from xdadevelopers for a long time, but since a few weeks (using the last [ROM GNEXUS PORT] JRO03L 4.1.1 RC) my Galaxy started to get crashes every 5 minutes, and after each crash, the battery dropped from 99% to 2%. If I had the phone off for a long time, it recovered part of the battery, but it would never switch on again until I plug it in. At the same time I got the message of IMEI invalid.
Yesterday I changed the ROM to the one of SLIM BEAN 2.5, and I got the same problem.
Does anyone has the same issue? Is it a problem of battery or did I do something wrong in the process?
Thank you very much! Any advice would be highly appreciated, as right now I have no phone :-s
Do you have an IMEI backup? I would recommend going back to GB, restore the IMEI, flash CM9, flash whatever you like.
Sent from my Gameboy Color
Thanks for your answer!!! I have backup of the EMS. I've never restored it, but I'll look for the info in the forum.
I'll follow your advice as right now is the only thing I didn't try.
I'll let you know :-s
pituti said:
Thanks for your answer!!! I have backup of the EMS. I've never restored it, but I'll look for the info in the forum.
I'll follow your advice as right now is the only thing I didn't try.
I'll let you know :-s
Click to expand...
Click to collapse
I meant EFS
Battery may need replacing.. I had exactly the same symptoms about a month ago on cm10 and devil kernel. After trying everything from factory resets, new roms, different kernels and numerous battery calibrations, it was, in the end, a new battery and another complete wipe, going all the way back to froyo via gingerbread and wiping absolutely everything (before reinstalling cm10), that solved my problems. You can pick up a new battery online for about £7.00.
I think a dodgy rom download was the reason of all the problems, of the wrong imei and, maybe, the kernel voltages were corrupt which caused the problems with the battery stats going all over the place and the phone switching off. The constantly having to plug the charger in to get the phone to boot up again was imo what overcharged and ruined the battery.
I searched but could not find a similar thread.
On my Defy (green lens), I was running 10.1 July build.
I got a new battery and used it one day. When it was low, I turned off the phone and put my old battery and rebooted. Everything was fine.
Since I have also a battery charger, I charged my new battery through it and when the old one was draining, I swapped it with the new one again and turned on the phone.
Ever since, the phone is stuck on the CM animation.
I would like to know what is the best way forward for me.
s_u_n said:
I searched but could not find a similar thread.
On my Defy (green lens), I was running 10.1 July build.
I got a new battery and used it one day. When it was low, I turned off the phone and put my old battery and rebooted. Everything was fine.
Since I have also a battery charger, I charged my new battery through it and when the old one was draining, I swapped it with the new one again and turned on the phone.
Ever since, the phone is stuck on the CM animation.
I would like to know what is the best way forward for me.
Click to expand...
Click to collapse
Wipe your /data and /cache partitions and reboot. If that doesn't work, wipe everything and reflash the ROM. If you're worried about your data you can make a backup, before wiping, and then restore your apps+data with Titanium backup from the TWRP backup. I wouldn't restore system apps/settings.
Recovery
I did a stock recovery. Somehow it did not fix my problem. Then I did a custom recovery and wiped data, cache and dalvik.
As a result, all my apps were wiped out (not a problem) and perhaps some of my data as well.
However the result was a much better 4.1.2 experience.
Everything works fast - no lags whatsoever.
Only problem is that the icons for People and Messaging in the Dock disappear after some time. This has happened more than 3 times in the last 24 hours.