phone keep on rebooting when fully charged - Moto X Q&A

my phone start acting up. i charged it to a 100% then it would keep on restarting till it reach 60% or 30% and then it would quickly drain the battery away... can any body help me solved this problem, i really love my phone.. I'm in India by the way :crying:

Are you rooted? OS version?
Can you provide more details from when this started to happen?
Thank me if I helped you!

I'm not rooted, and my os is 5.1.1 happened last month.. i tried doing a factory reset still didn't do me any good

Last update for Moto X is 5.1 not 5.1.1
You maybe can try factory reset because you are stock

I've tried to reset it, it doesn't work apparently, it got stuck at the Motorola logo and same thing happen if I use the recovery mode sometimes I can't even go to recovery any expert suggestions?

Related

[Q] Help! Post-Root problems

Hey all, I recently tired to root my SGH-i537 att active but ran into problems afterwards. After I rooted I would boot up my phone with a unlock icon, not a big problem, but i was getting security notices an was unable to even slide the wi-fi search to on let alone connect to one. Another problem i ran into was my kernel was destroying my battery! i would charge for 6 hours and only go up to 70% ot have it die in an hour. After all that frustration i unrooted using the SuperSU unroot button. While I am now unrooted(i think) my battery is still dying insanely quickly, I cannot even attempt to connect to wi-fi, and i am still booting up with the unlocked icon. At this point I just want to wipe it and start new but when i did a factory reset all of the problems listed above were still occurring. Should I find a stock ROM and try and have that downloaded on? I have no clue what to do and i need help please D:.

Bricked Mobile? Flashed wrong kernel

Hello, everyone.
I have already installed CM11 on my Moto G XT-1040, peregrine. I was curious to learn a bit more about kernels and tried to download one and flash it via TWRP. The problem is that I got one from XT-1032, falcon, without noticing it. The kernel is XPerience 17+ and it's frozen on the boot until this very moment. What should I do? Did I brick my phone or is there a way to recover it?
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
I put it to charge... any ideas of the next step? It responded, at least to the charging.
So, now to the real question... can I try to flash the old kernel again? If yes, how?
(I'm really hoping to enter the recovery mode!!)
I'm hoping someone can help me out!
Thanks in advance,
Rodolfo.
Nevermind, I got it backed up and restored it.
rodolfoakira said:
Hello, everyone.
I have already installed CM11 on my Moto G XT-1040, peregrine. I was curious to learn a bit more about kernels and tried to download one and flash it via TWRP. The problem is that I got one from XT-1032, falcon, without noticing it. The kernel is XPerience 17+ and it's frozen on the boot until this very moment. What should I do? Did I brick my phone or is there a way to recover it?
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
I put it to charge... any ideas of the next step? It responded, at least to the charging.
So, now to the real question... can I try to flash the old kernel again? If yes, how?
(I'm really hoping to enter the recovery mode!!)
I'm hoping someone can help me out!
Thanks in advance,
Rodolfo.
Click to expand...
Click to collapse
If anyone had the same problem, I hope you guys had a backup file on TWRP, which restores almost everything but the bootloader logo from the other kernel.
Good news, the problem was solved just with the Recovery Mode. It needed to get into the bootloader, which was only possible after the battery died.
rodolfoakira said:
Oh. It seems that the battery got the phone killed and it finally turned off. (Feels like having some kind of Apple device, which cannot be turned off until the battery is still alive).
Click to expand...
Click to collapse
Holding the power button for 20 seconds or so didn't work?
No it didn't. Unfortunatelly. D:
unwired said:
Holding the power button for 20 seconds or so didn't work?
Click to expand...
Click to collapse
No it didn't. Unfortunatelly. D:
No commands were working at the time. Just the frozen bootloader screen from the wrong kernel. When the battery died, after some 5 minutes or so of charge I managed to turn it on on the bootloader and put it on recovery mod. Wow, I killed all my nerves, thinking I lost my close-to-new phone. Then backup saved my day!

[Q] HTC One M7 - Noscreen lock/off after Android Lollipop update

Hello everyone,
I received an OTA update last night for my phone for Android Lollipop. If I had known better, I wouldn't have updated it.
Since the update, my screen doesn't timeout or lock, it just restarts. If I press the power button to turn the screen off, it restarts. I can either shut the phone off completely or keep the screen on, which obviously kills the battery pretty quick.
I tried doing factory reset already, issue is still there. I tried wiping cache partition, same issue.
At this point, I would really like to downgrade to KitKat. Is that possible? And if so, how? I'm on a Vodafone UK contract. My phone is not unlocked.
Any other solution that might help. I don't know what else to do. Please help.
rosesor said:
Hello everyone,
I received an OTA update last night for my phone for Android Lollipop. If I had known better, I wouldn't have updated it.
Since the update, my screen doesn't timeout or lock, it just restarts. If I press the power button to turn the screen off, it restarts. I can either shut the phone off completely or keep the screen on, which obviously kills the battery pretty quick.
I tried doing factory reset already, issue is still there. I tried wiping cache partition, same issue.
At this point, I would really like to downgrade to KitKat. Is that possible? And if so, how? I'm on a Vodafone UK contract. My phone is not unlocked.
Any other solution that might help. I don't know what else to do. Please help.
Click to expand...
Click to collapse
sounds like your phone is broken ..return it if it's Locked and never rooted
Finally fixed
In the end, I had to unlock the bootloader, root the phone and flash a customer ROM (Android Revolution). It worked! Now, I can finally switch my screen off without the phone restarting!
Thanks,
Rose
rosesor said:
In the end, I had to unlock the bootloader, root the phone and flash a customer ROM (Android Revolution). It worked! Now, I can finally switch my screen off without the phone restarting!
Thanks,
Rose
Click to expand...
Click to collapse
you also lost your warranty in the process. If it had not worked you would have been stuck paying for a repair
I'm happy it worked out for you

Upgraded to Nougat - Phone froze on reboot, forced to wipe data. HELP!

I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Cassetti said:
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Click to expand...
Click to collapse
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
dandrumheller said:
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
Click to expand...
Click to collapse
Pretty much what I've figured. Sounds like I'll just have accept they're lost and move on. Thx

All help needed, is my note 4 dying ?

Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Pigoath said:
Hello.
I have a Galaxy Note 4 SM-N910T2. In january of this year i upgraded it to 6.0.1 (N910TUVU2EQI2) from 4.4.4(N910T2UVU2AOG1) using the SM-N910T firmware for the upgrade, everything was working perfectly but the day before yesterday i wanted to perform a wipe cache because the phone was being a bit laggy. after the wipe cache was perform and i hit the reboot, the recovery got stucked on Verifying DMhash tree. so after 30 minutes i took the battery out and powered on my phone, the problem is: The phone started to freeze, reset it self even the process system crashed. I read that downloading the Wake Lock power management helps and it did but i didn't want to use this app forever so i downgraded back to 4.4.4 it's original firmware, it does run better but now my phone reboots itself and it freezes just a little bit. Also i've got the Process system is not responding do you want to close it?
Things i've done so far:
1- Reflashed 4.4.4, 3 times, i've done wipes before reflashing and after. Nothing
2-Flashed TWRP wiped everything, repaired the file system, Flashed the stock again (4.4.4) nothing.
I'm not going back to 6.0.1.
Do i have to buy a new phone or maybe a new rom with a kernel will help ?
Click to expand...
Click to collapse
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Trex888 said:
All i can say is your phone mmc chip is about to die soon or later you will get mmc_read failure message and your phone wont be able to boot into the system and you won'tbe able to flash anything.
My best suggestion is sell it ASAP.
Click to expand...
Click to collapse
I came across the mmc_read failure before I realized it was happening and have been researching ways to at least verify there was nothing important on the device before retiring it to Samsung heaven.
Instead of useful advice, everyone seems to be spouting "sell it ASAP" as though it doesn't make you trash as a person to attempt selling it as any sort of working device. The inclusion of "ASAP" and lack of "with a disclaimer" tends to suggest they aren't recommending you actually tell anyone about the issue.
Good advice would be to back up everything you can now and begin looking for a new device. You could attempt to sell it for parts, but make sure to inform people of the situation. If it is that close to failure, chances are it will still be well within the 30 day return policy on most sites and they always favor the buyer. Your device is already ruined, but there is no reason to destroy your reputation with it.

Categories

Resources