I have a Moto G running Lineage OS. This has been running fine for a couple of months now. However, a couple of days ago it turned itself off and wouldn't go past the Lineage boot animation.
After reading several threads I tried clearing all data from the phone and reinstalling Lineage. Then it worked for two or three days and then the same thing happened.
Does anyone have suggestions other than reinstalling Lineage again?
What might be the cause?
did you make any modifications to /system? what and how you flashed? maybe you should try with another rom
Did you try logcat? A moto g in my household had a symptom like this due to a bad line in the wifi network history file. But there could be any number of other causes. Logcat should give some clue.
Sent from my Moto G (5) Plus using Tapatalk
I followed the instructions on the page doe the Falcon rom a couple of months ago. Everything worked fine. I made no modifications to system or anything else.
I read some posts on that the battery might be the cause. Is that plausible?
Related
Hey everyone.
So, this started happening to my Nexus (stock, unrooted, locked) after the 5.0.1 OTA update: youtube.com/watch?v=BolnMQx3LGs
It started in the first days of January, after receiving the 5.0.1. update. The phone randomly restarts and gets in a boot loop. For the last month it happened once or twice every week, often making the phone useless for several hours. I posted on the Nexus help forums, noticed a lot of people with the same problem as me, but no solutions.
Today I had enough and sideloaded Kitkat again. So far so good, but I don't want to celebrate just yet.
Has this happened to anyone here. Is there a reason for this to be happening or a solution?
I wish I had the answer. My wifes' stock rooted N5 did this 2 weeks ago and I could not keep it booted into recovery long enough to flash any images. I bought myself an N6 then I wiped my CM11 N5 and loaded stock 5.0.1. for her and put in her sim. She was fine for the last two weeks. Now today she says it is doing it to this phone. The first phones' issue looked exactly like your youtube video. Not your standard bootloop. Wiping cache and dalvik did not fix. A couple other threads mention they suspect kernel. Assuming I can get it to stay on the bootloader I will probably flash elementalX and see if that solves it.
thionylx said:
I wish I had the answer. My wifes' stock rooted N5 did this 2 weeks ago and I could not keep it booted into recovery long enough to flash any images. I bought myself an N6 then I wiped my CM11 N5 and loaded stock 5.0.1. for her and put in her sim. She was fine for the last two weeks. Now today she says it is doing it to this phone. The first phones' issue looked exactly like your youtube video. Not your standard bootloop. Wiping cache and dalvik did not fix. A couple other threads mention they suspect kernel. Assuming I can get it to stay on the bootloader I will probably flash elementalX and see if that solves it.
Click to expand...
Click to collapse
Sounds like a stuck power button to me.
Sent from my Nexus 5 using XDA Free mobile app
Hi Xda, to start sotty for my bad english.
i've a strange bug on my moto g
i've use for many time Cm11,cm12 and others aosp based rom without problems,(my moto g have 16 months) but now , from about two months when i install aosp based rom when i reboot my moto lost data and time everytime., also in TWRP and Philz recovery data is wrong.
instead if i flash stock rom, Motorola or GPE everything work perfect, in recovery time is wrong but when reboot is not lost time.This forces me to keep the stock rom, because on AOSP i've problem with messaging programs like whatsapp that tell me wrong data every reboot, or with data monitoring programs.
I've investigated and i think is a bug related to time_daemon service...but i don't find a solution...i think is change something on aosp sources but I can not understand why this problem occurs only for me.
Can anyone help me?
Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.
Hi
I've got a Moto g XT1032 and I've been having issues with it I'm still not sure if its the hardware at fault.
It's had a few different custom ROMs which were OK but then it started having issues like freezing and running really slow/jumpy so I put a different ROM on and all seems OK but none have lasted.
It's been stuck in the draw for about 5 months but thought I would give it another go.
I remember though that some ROMs wouldn't install TWRP would give errors and I can't get how to work out which ROMs will work and about upgrading the bootloader but can't remember how
I'm useless at the adb stuff also I've never really had much luck I normally transfer the ROM through windows explorer.
So at the moment its all been erased and I'm wanting to know the next step ,is there some kind of deep format to stop what might me causing the errors
The TWRP version on there now is v2.8.6.0(is this correct)
Thanks for reading
I'm using a Moto G 1st gen with CyanogenMod 13 official nightly. The memory used by system in the first few hours after boot is about 300-350MB. But after that it increases constantly and then reaches up to 500MB. That is only the memory used by system.
During first few hours (Attachment 2)
After many hours (Attachment 1)
I know that in Android a full memory is a good thing and it is not like Windows, but my phone slows down and starts lagging a lot when all the memory is eaten up by the system. I have tried going into safe mode, uninstalling xposed, disabling certain apps I thought to be the cause of the problem, upgrading to the latest nightly, updating gapps, beating my head against a wall, etc. but I couldn't figure out the problem. Please help me if you can and if you need any additional information please tell me.
I would also same thing is happening with MM, but not all roms
That is something that almost all roms present. Not only in marshmallow, i've experienced this in 12.1 especially in cyanogenmod based roms.