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.
Related
I tried restoring the stock battery icon using ACS 1.1 and my phone got stuck in an endless reboot cycle. I kind of started freaking out as my phone had been acting flawlessly prior to this and I was scared of corrupting my data. I had a recent restore point saved (I have MyBackup make one every morning while I'm sleeping) but that would mean I'd have to wipe my phone and after everyone complaining about how hard it is for them getting ACS 1.1 to work on there phone I was scared to test my luck a second time. I thought the only other option would be a battery pull which would lead to bad data with bad backups. So instead of following one of those two options I three finger rebooted out of the loop and immediately three finger booted into CWM. I wiped only my cache and dalvik and then reflashed 1.1 over the existing one. I then rebooted and the only things I had to do were reflash my Vision kernel and delete a few apps that I did not want that come with the ACS rom that got reinstalled. I assume none of my data got corrupted and I know this probably won't save everybody from corrupted data due to endless reboots but just thought I'd share my method. So far everything has been running just as good as ever.
The radio is ED05
The kernel is the one that came with it.
However the phone randomly reboots when I am talking on the phone and sometimes when I answer the phone (happened once) it kept ringing on my end but I could still here the person on the other end.
Also the battery is constantly draining fast.
I can get through most of the work day, but it will be about 20%
I've fully charged it and let it run dead.
I rooted and used the MIUI Rom on my wife's and mine fascinate.
Any suggestions?
Did you mean 1.9.16. If so that version had the same kind of bugs and ran odd on my phone too while it ran fine on a friends phone. Don't know why it runs so differently on phones but try the latest 10.28.1.1. It has been running the best out of any one the last month for me. You can find it on miui.us in the fascinate forum. The original port had a broken flash on the camera and weblexa fixed in the 10.28.1.1 version. I've been on it all week no reboots or phantom rings yet.
Do I just boot to recovery and wipe Dalvik Cache and Wipe Cache Partition and install zip from SDCard?
Would you advise to delete battery stats?
Yes just boot to recovery through the power menu. The recovery associated with the 3 button method doesn't work you have to use the one you boot into from the power menu. For best results wipe data/ factory reset too. Sometimes if you just wipe the caches it will act funny. You can wipe battery stats too if you want. I don't do it every time but if it seems it's reading wrong I will go back and clear it later. Since it seems it drains fast you may want to clear the battery stats. I get about 17hrs out of mine with moderate use.
I think I downloaded 10.28.1.0. from the website miui.us. I will download the one from the forum and go from there.
Good luck hope it works well for you. It's a great rom on this phone.
Sent from my SCH-I500 using Tapatalk
MIUI + Fascinate + this forum = lolwatwhichthreadagain
I installed the new update 10.28.1.0 and it seems to work pretty well.
I have a few issues however. I cannot install new programs from the Android Market, it says there is no room available, when there is, and the File Explorer crashes all the time now.
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!!
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
I always wipe cache/dalvik when dirty flashing my rom updates and never had that problem.
I'm guessing you have a bad battery, otherwise it wouldn't have behaved as you described. If you're lucky it's just a glitch - try a few charge cycles :fingers-crossed:
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
lewmur said:
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
Click to expand...
Click to collapse
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
ShadNuke said:
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
Click to expand...
Click to collapse
Rule of thumb, flash stock ROMs via odin and custom ROMs via TWRP. My choice would be a custom ROM and then BACKUP!!!:laugh:
edit: If you rooted the device a long time ago, that means you haven't been getting any updates. You may well be clear back on Android 6 while the latest custom ROMs are 10 and the latest stock is 8.1. You can get the latest stock with Frija, which is a free download.
I'll have to take a look on my SD card, I recall using Titanium backup, so I'll have to check. Do you have any recommendations? Warranty is gone, so I'll likely install a new ROM, I usually do once it's up anyway
I only browse Reddit, Facebook, a couple other social media apps and I'll play the odd game.