I've had an issue with constant restarting since the 8.1.0 update. My device just crashes and restarts randomly on it's own. The model is XT1794. I've done a google but it's yielded nothing.
The phone was previously my relative's and it's already been sent to lenovo for fixes but it didn't help at all.
If someone could help me out that would be great because I really want to use the Moto G5s but this is just holding me back.
Related
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
I had the same problem. The phone would freeze and randomly reboot. Sometimes the system crashes and asked me for the typed-in password (not fingerprint). Sometimes when I charge the phone, and unplug the power cable, the charging led stays lit and the battery has to be pulled. I decided to switch the battery with my wife's Note 4 and see if the effects remained. So far I haven't had any problems after switching the battery, so I believe the battery may be the cause of all these issues. I'll keep you updated on the issues.
I'm back. The battery replacement didn't fix the reboots. I think my phone's hardware is permanently damaged. :crying:
have you downgraded?
and can you help me with my problem?[
AlexanderDAB said:
have you downgraded?
and can you help me with my problem?[
Click to expand...
Click to collapse
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
ajumatt said:
I'm downgrading to stock 5.1.1 right now. I'll keep you updated. I placed an order for a Galaxy S7 Edge International Version (G935F) yesterday.
Click to expand...
Click to collapse
can you downgrade to Android 5.0.1 and help me with my problem?
its something completely different to this topic
I've been having the same issue, started about 2 weeks ago. phone would start being sluggish then if I continue tapping on screen, it'll reboot. At least once I saw it go into recovery & reinstall firmware(?). Another time it just sat at the bootloader screen waiting for software download or something till I took out the battery. Most likely it's a software issue related to 6.0 update or updates afterwards. taking out the SD card helped a bit.
but basically got annoyed & upgraded to LG V20 today. Coincidentally, there was another person at the AT&T store with a Note 4 having the same issue.
Mine just rebooted twice on me a while ago, first is emergency calls only now the reboots then what. And yes the slow charging is a problem too. MM got serious issue dam att
Sent from my SAMSUNG-SM-N910A using XDA-Developers mobile app
adavis1201 said:
I was just wondering if anyone else has an issue with their Note 4 rebooting randomly with no external input. This started happening with the Android 6.0 update both on the download from here and the AT&T official release, Any Ideas? I've already purchased a new battery due to a separate issue, any idea?
Click to expand...
Click to collapse
use wakelock its an app u get it from play store.it makes ur cpu always running.some how it fixes the problem of random reboots. dl it and set it to partial lock (the 5th option)
Same problem. Just started a few weeks ago. REALLY frustrating having to enter my password every 3-4 minutes. NEVER buying another Samsung, too many damn issues with this phone.
My reboots tend to happen once the phone goes below 60% battery. It's fine above 60%. Once it goes below 50%, the reboots tend to happen with any intense network activity. The phone will often go from 50% to 22%. I forgot what the 30's and 40's look like. I will try the Wakelock app.
Ugh. I posted about this a few weeks ago. It's started happening more frequently and will occasionally go into a boot loop or show 0% battery even though there's a charge.
Has anyone found any solution? I haven't tried wiping / resetting but I'm getting close to trying it.
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
k.babymamma said:
Here is a cautionary tale for you. My completely stock, unroooted phone started acting the same exact way. On the 4th or 5th battery pull (to fix a frozen screen) it just crapped out. It's totally unresponsive. Deader than a door nail. Tried everything. The download mode, discharging by power button depression/battery removal, etc. Adb shell command does not detect it. Nor Odin. Computer throws up a qhsusb_bulk error when I plug it into pc. I have NO CLUE how to fix it & I am desperately seeking a solution. Please proceed wisely with your oddly acting phones & don't let this happen to you.
Click to expand...
Click to collapse
Same issue. Just got off the phone with Samsung support, all possibility of having this particular phone with this particular issue sent in for evaluation has been suspended. Translation, they know it is an issue and will not stand by the changes they push to their products (latest OS). I am researching the prospect of legal action since THEY pushed the new OS against my request. Shouldn't that affect the warranty or coverage? Consulting my attorney friends as we speak. Will let you know. I am not sure how WakeLock will help, it is not going to sleep, it is repeatedly power cycling through a kernel process until the battery overheats or it reboots.
Same issue
Since Marshmallow, my 910A will get sluggish or freeze, shut down, sometimes reboot and sometimes just brick (temporarily). Sometimes--more often in recent days, I get a "dll_mmc read fail" message and the target that says do not stop downloading. No matter what I've tried--factory and soft resets, cache clearing, battery pull, replacement, and SD card switch, contacting AT&T and Samsung rep--it doesn't seem to change. This is a daily issue and becoming more frequent. Any suggestions or do I just need a new phone? Thank you.
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
jb1207 said:
Hello everyon everyone.
I have the SM-P600 version, everything was good until the beginning of the week when touchpad began to go off without reason, and completely random.
I first reinstalled several official ROMs from the most recent to the oldest, with no significant improvement
Then i rooted and tried Lineage, it looked good for a while, but in the end same problem.
Please note, when the tablet begins to mess, the reboots are occuring more and more often and after a while it turns in a loop and im not even able to switch it off.
Samsung logo display, black screen, logo, black screen, etc ...
I think rather for a battery-side problem, if some people have faced similar problem, I'm taking help.
Do you know if by chance we can use the tablet without battery to test this theory?
Thank you in advance for any answers.
Click to expand...
Click to collapse
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
marshallartsoz said:
I think I'd be taking a close look at the physical power button. Seems to me that if it had gone flakey it could cause something like this.
Click to expand...
Click to collapse
Hello and thanks for you answer,
Just to precise i never faced this issue while flashing an official or custom ROM, dont know if it is just luck or it can help in anything
Anyway ill try to check it the power button just in case
It's weird I just started having this exact problem myself. One morning I unplugged it and it had shut itself down overnight. Since then it randomly reboots. Sometimes I can get 20/30 minutes out of it, but once it starts, it can get into multiple reboots with the only way to stop it is to plug in the charger. I tried wiping cashe/dalvic (no help). Nothing was recently changed (including apps). Tried resoldering battery connector (battery was replaced a year or so ago with OEM Sammy). The P600 is rooted with TWRP installed, but no custom ROM. Usually the reboots start while I'm doing something (surfing, email, etc.), but I don't think it will do it while sleeping. I'm considering the power button, but I don't see this exact problem anywhere else, but this post. Any ideas?
OK. My tablet has taken a turn for the worse. Now it is stuck in a continuous boot loop. I tried the power switch, no help. I tried booting into TWRP, and it went back into rebooting before I could do anything. Strange thing is I can put it into download mode indefinitely without it rebooting. Should I ODIN back to stock? I tried the resoldering of the battery connection earlier. Any other ideas?
Hello, 2 weeks ago my xt1670 went out for no reason, when re-igniting it constantly restarted, entered in recovery mode, clear data and cache, twice... but it didn't work, I downloaded the "Lenovo moto smart assistant", Reinstall the same operating system and it didn't work either, I thought it could be a problem with the batteries, I bought a new one, but it wasn't the problem, When I finally got it on and kept going like this, after leaving it off for a long time, notice that the audio wasn't working, the videos made an error back when I tried to play them, I had to plug on a headset to make it work, but after a while restarted for no reason again, I don't know if it's a an audio codec problem, Energy input or something else, help me please.
exactly what im facing can anyone help please???
Yesterday night, I've successfully rooted my phone (wich i was really proud of after not realizing for an hour i was using the wrong twrp version).
Well after using it for a bit and getting all my backups over it, when I started Huawei health my phone froze, heated up and afterwards rebooted.
After trying to start Huawei health again, it worked fine but after some time the same things happend again. Well that lead me to uninstall Huawei health, wich i did but afterwards my phone started to freeze randomly. I tried to reproduce it after restarts but it seemingly was random.
So After that I booted my phone into save mode to see if the problem was dependent of the software. In save mode, my phone worked perfectly fine.
This left me thinking, its not a problem with the software, more like a problem with an app but since Huawei health was uninstalled i couldn't call wich app it could be.
The last thing wich i can do (or so i think any other ideas are always welcome) is to longtrace my phone and maybe find out with that what the error is but since i never used traces i am not quiet sure if that would help or even show what's wrong.
Anyone ideas what could cause this?
Hello, I have an a5y17lte with latest official LineageOS 18.1 build which yesterday started exhibiting an issue with the screen where when waking it up the screen stays black. I was able to fix it by force powering it off, but soon it happened a couple more times, one time the screen not turning on after the 1st force reboot and thus requiring multiple force power offs to start working again. Later on during that day there were no issues with the screen, but since this morning this happens constantly and regularly and it always takes more than one force reboot to fix it. I have tried reflashing the system image, which worked for a bit before it started doing the same thing once again. Does anyone have a clue what could possibly be causing this?