My Moto G (gen. 1) reboots randomly. Sometimes it works fine for a few hours and sometimes it will restart in a loop until I shut it down completely.
When it first happend it had bootloader unlocked and was running Lineage OS. I installed stock rom and it didn't help either.
I think it might be a problem with hardware but how would I find out what is broken? Or is there something that I'm missing? I don't have a warranty and don't want give it to a service and pay since it's an old phone and it won't probably be worth it.
Edit: The screen goes blurry before it reboots.
Related
Only got the phone today and all. At stock as far as I know. If you lock and then unlock the phone, this can fix the issue. Until the next time you lock and unlock the screen that is. It does not happen if you boot into the boot menu/recovery, it does begin to happen in the Android boot up sequence, a specific point, in fact. The phone is plugged in the video because I was charging it, but it does it when not plugged in as well. Factory reset doesn't do much but why would it? As I say, it was already at stock. Seems to be an issue peculiar to me because I can't find anything about it. Any ideas?
I'd say your phone is faulty. You should ask for it to be replaced. Sorry.
My LG G2 shuts down(freeze and then turn off instantly with no shutdown animation) when doing tasks such as updating/restoring apps or uploading/downloading files. It then doesn't even boot up after a couple of minutes. Then when it decides it's ready to start booting it will (A)Show the LG logo for half a second and then shut down again, (B) Get to the boot animation and then freeze in the middle of it and shutdown, and (C) Fully boot up and works for 1-8 hours and then shut down again.
This isn't an overheating problem. This doesn't seem like a battery problem either. I have TWRP installed and restoring to Stock made the phone not shutdown during boot, but still does randomly when doing tasks mentioned above.
I have no idea what the problem is here. I haven't installed/updated any apps recently that would cause this problem.
I have also noticed that in the past when uploading files such as 3-5 gb TWRP backup files to my PC my phone also overheats and turns off.
What's happening? Is something hardware related in the phone broken like a chip or is it a software issue?
Nothing? I'll just give this to a repair shop then. Currently using the Galaxy S5 and I'm hating every moment except the water resistance >: (
Still...
Well I just upgraded to the G3 and it is complete bull****, can anyone help me fix this phone or should I just get another G2?
Hey man. It's hardware. Flash back to stock, get rid of your root flag and send it in for repair. Mine was doing the exact same thing.
Sent from my LG-D800 using XDA Free mobile app
Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.
Hey guys I need your help, I was using my phone yesterday and suddenly it turned off and got stuck in a bootloop but not the normal ones. At first I figured it was something with the software or anything and went to sleep. The bootloop is unique in that sometimes it passes the Alcatel screen and goes to the bootanimation, but most of the time it stays at the Alcatel screen and reboots, I've even seen it boot normally then turn off and get stuck again. I tried the Q Mobile software, it was successful and now I'm in stock, but its still the same. I've been thinking its an overheating issue or something with the hardware. I dunno if I can fix it, can you guys help?
Gorep1xel said:
Hey guys I need your help, I was using my phone yesterday and suddenly it turned off and got stuck in a bootloop but not the normal ones. At first I figured it was something with the software or anything and went to sleep. The bootloop is unique in that sometimes it passes the Alcatel screen and goes to the bootanimation, but most of the time it stays at the Alcatel screen and reboots, I've even seen it boot normally then turn off and get stuck again. I tried the Q Mobile software, it was successful and now I'm in stock, but its still the same. I've been thinking its an overheating issue or something with the hardware. I dunno if I can fix it, can you guys help?
Click to expand...
Click to collapse
If mobile Q didn't fix it then yes it sounds like a hardware/warranty issue.
It turns out it died for sure today, it wouldn't even turn on. RIP phone, u were such a good phone
My G3 (never been rooted, running stock Lollipop) softbricked three days ago for seemingly no reason (I was scrolling through Youtube videos and the screen just froze all of a sudden) and went into a bootloop. It's able to go into download and recovery mode, but not much else. USB debugging isn't turned on (and since the phone won't boot up normally, I presume there's not a way to turn it on now.) Is there any way, at this point, to recover the files on it?
Kinda.
My g3 did the exact same thing and it turned out to be a battery problem. First, let it sit on the charger and try to boot for a max of 10 minutes, if that dont work, see if a store that carries the g3 battery will let you buy one, recover the files, and return it. If putting a new battery in solve the problem atleast. But, that what i did, except i just ordered a new battery and its working fine now.