Hi,
I bought my m8 international about 2 months ago. It was working fine up to now, with an occasional crash and reboot (4 times since I have it). Since yesterday evening it has crashed and restarted about 20 times. I have no idea what has changed and there seems to be no consistent reason for the crash. I tried to restore to factory settings and even clear the SD card, but on the first reboot it crashed when I was entering my sim unlock code.
I rooted all my previous phones but did not try it on this one yet, so it is completely stock.
Is there a way to find out what is causing the crashes without having root?
thanks for your replies.
Fyretb
Fyretb said:
Hi,
I bought my m8 international about 2 mpnths ago. It was working fine up to now, with an occasional crash and reboot (4 times since I have it). Since yesterday evening it has crashed and restarted about 20 times. I have no idea what has changed and there seems to be no consistent reason for the crash. I tried to restore to factory settings and even clear the SD card, but on the first reboot it crashed when I was entering my sim unlock code.
I rooted all my previous phones but did not try it on this one yet, so it is completely stock.
Is there a way to find out what is causing the crashes without having root?
thanks for your replies.
Fyretb
Click to expand...
Click to collapse
I take it you have updated the firmware via OTA's? I had a similar experience when I first got my M8 (a couple of weeks ago), it would reboot randomly several times a day, tried factory resetting and it didnt help. I installed the prompted OTA's and running 4.4.3 which fixed it. Was a bit annoying as I was trying to hold off updating until I seen what my options were for root/s-off etc, now I have the latest bootloader and would have to use Sunshine to s-off. Still havent rooted as everything is running great for me at the moment so happy enough.
gsmyth said:
I take it you have updated the firmware via OTA's? I had a similar experience when I first got my M8 (a couple of weeks ago), it would reboot randomly several times a day, tried factory resetting and it didnt help. I installed the prompted OTA's and running 4.4.3 which fixed it. Was a bit annoying as I was trying to hold off updating until I seen what my options were for root/s-off etc, now I have the latest bootloader and would have to use Sunshine to s-off. Still havent rooted as everything is running great for me at the moment so happy enough.
Click to expand...
Click to collapse
Yeah, installed all the OTA's, but last one was a couple of weeks ago. I just double checked, but there's nothing to update at this point.
Fyretb said:
Yeah, installed all the OTA's, but last one was a couple of weeks ago. I just double checked, but there's nothing to update at this point.
Click to expand...
Click to collapse
Are you getting the HTC error log messages when you boot up again, should appear as a notification? I got a few of these when mine was crashing, you can view the log if you tap into the notification. It will be a massive log, I tried copying and was going to paste to an email or doc but it wouldnt let me as there was too much data.
gsmyth said:
Are you getting the HTC error log messages when you boot up again, should appear as a notification? I got a few of these when mine was crashing, you can view the log if you tap into the notification. It will be a massive log, I tried copying and was going to paste to an email or doc but it wouldnt let me as there was too much data.
Click to expand...
Click to collapse
Yeah, I get those. As you say it's massive and not readable, at least not for me. I couldn't even manage copying it..
Related
I've been having problems with the phone giving an error message saying that the SIM card was removed and then immediately it is recognized and the phone is restarted automatically to start using the network. It has been happening on full stock ROM (old and new versions), rooted and unrooted, locked and unlocked bootloader (FreeGee) and on custom ROMs. I've had the SIM card replaced multiple times without helping. I can't remember back to when it first started, but it started again after getting the phone back from repair (all they did was a software update, but that's another story) I have the issue until I reinstalled Cerberus and Tasker. Upon uninstall of both apps, I haven't had the issue for the last 5 days. Anyone else have issue with either of these apps on an E973 (Bell)? Is it even possible that they could be causing this issue or is the timing just a coincidence? I'll try adding the apps back one at a time and see if I can get the problem to start again with either one.
Sorry about the wrong thread, I could have sworn I was in Q&A when I posted. If anyone wants to move it that would be appreciated.
mike1767 said:
I've been having problems with the phone giving an error message saying that the SIM card was removed and then immediately it is recognized and the phone is restarted automatically to start using the network. It has been happening on full stock ROM (old and new versions), rooted and unrooted, locked and unlocked bootloader (FreeGee) and on custom ROMs. I've had the SIM card replaced multiple times without helping. I can't remember back to when it first started, but it started again after getting the phone back from repair (all they did was a software update, but that's another story) I have the issue until I reinstalled Cerberus and Tasker. Upon uninstall of both apps, I haven't had the issue for the last 5 days. Anyone else have issue with either of these apps on an E973 (Bell)? Is it even possible that they could be causing this issue or is the timing just a coincidence? I'll try adding the apps back one at a time and see if I can get the problem to start again with either one.
Sorry about the wrong thread, I could have sworn I was in Q&A when I posted. If anyone wants to move it that would be appreciated.
Click to expand...
Click to collapse
Anyone have solution for this issue ?
Hi everyone. I have a sporadic problem with my vanilla note 3 from t mobile. Its a totally random occurrence but sometimes it will freeze(loose all input functionality) sometimes it will just stay black screen(no input taking) and usually (not always) it will reboot itself after this happens(sometimes a battery pull is required). Is this a memory leak issue? Thanks for any help. Sometimes it will run fine for a week or 2 and then all the sudden it will start acting up.
Was it rooted? I had a similar issue before mine was rooted, some of the system load programs that I didn't use would start up and then grab all resources. ..
Mine was doing the same thing while rooted with towelroot. Even after I unrooted it was doing the same thing. I didn't try a factory reset, but T-Mobile is sending me a replacement phone.
JimSmith94 said:
Mine was doing the same thing while rooted with towelroot. Even after I unrooted it was doing the same thing. I didn't try a factory reset, but T-Mobile is sending me a replacement phone.
Click to expand...
Click to collapse
no it was never rooted and I cant get the bloatware off if its not rooted right?
same problem
im running dompop 3.5. about to install .4. but i have not been able to add any lockscreen except swipe. when i try another it unmounts my external sd card. if i reboot my phone it will reboot until it gets ready to stop doing it. some times it loads and says something about system ui not loading and asks me if i want to wait or push ok. freezes and reboots when it wants to. goes blank. i have factory reset it, fised permissions, and re flashed updates and rom clean and dirty. still does it. someone please help. phone is only a year and some months old. also my nandroid backups wont work. they are not all partitons or they just plain fail.
craigo198 said:
Hi everyone. I have a sporadic problem with my vanilla note 3 from t mobile. Its a totally random occurrence but sometimes it will freeze(loose all input functionality) sometimes it will just stay black screen(no input taking) and usually (not always) it will reboot itself after this happens(sometimes a battery pull is required). Is this a memory leak issue? Thanks for any help. Sometimes it will run fine for a week or 2 and then all the sudden it will start acting up.
Click to expand...
Click to collapse
If it was my phone I would do cache wipe first, if still no go then full factory reset and I would then reinstall most important programs first.
Restarting phone every few days is not a bad idea on it's own and BTW when was the last time you cleaned garbage from it?
Hello everyone. Since the Title has character limit im gonna have to explain myself here better.
Ive had my HTC One M8 for 4 years now. Pretty much since it came out in 2013. I installed ARHD back in 2014 and its been working just fine ever since. A couple of months ago i decided to go back to 45.0. Everything went smooth and everything works just fine.
But a week ago the phone decided to just go woopdido and it wouldnt open up any apps in Playstore although i could still see them. So i tried to restart it and when i did it got stuck at the HTC Logo. I tried to restart it a few times but it kept getting stuck. I was super confused due to the reason that i havent really done anything with my phone besides since the day i installed ARHD 45.0. I got desperate so i reinstalled it but this time with 53.1 and that went fine too except for one fishy thing and that was that i remember before when installing ARHD, when it got 30% it wouldnt take 2-3 minutes for it to finally start installing the ROM. It would take a couple of seconds for it to start right away and be done.
After installing 53.1 phone worked just as fine except for the fact that it was slower than it has ever been before. Which was also weird. Either way. After a couple of hours of it working, setting up every app i needed i restarted it and again it was stuck at the HTC Logo. Welp i guess..
So after that crap i went back to 45.0 again. It went good and all except it keeps getting stuck at 30% for a while but whatever. Going back to 45.0 though didnt help. Keeps repeating the same crap after a while. After a restart when having the phone doing nothing for hours gets it stuck at HTC Logo again. I literally cannot do anything with it atm and i have no clue how to go further from here as i have not had this before.
The HTC One M8 is rooted. S-Off everything you really need. The current TWRP version i have is 3.1.1.0.
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
redpoint73 said:
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
Click to expand...
Click to collapse
It was released in 2014? Welp why did i think it was 2013? Either way.
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right. The firmware is fine and all for the current version i have. It was for 53.1 too.
And out of the blue it just got stuck on the HTC Logo. I tried something and it was updating the SuperSU which actually was the reason why it got stuck on the HTC Logo. I installed 2.79 and now it boots just fine and the phone is back on speed again. Apparently 2.82 has issues which is the version i assume it tried to update to through both TWRP and Playstore.
sp3tan said:
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right .
Click to expand...
Click to collapse
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
redpoint73 said:
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
Click to expand...
Click to collapse
Yeah it does. I also forgot to mention that my microphone went to sh*t also. But its not because of this event. Although after this last reinstall i did the microphone picks up my voice better than it did before it went crap. But people cant still hear me when they call me
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
cswee1932 said:
As the title says, phone has randomly rebooted
... twice in the last few minutes, both times I had picture in picture going while sending a text...has anyone else experienced this? Also, the boot time is amazingly fast at least!
Chris
Click to expand...
Click to collapse
Did you do a wipe when you flashed or just update? If you just did an update, I would try to reinstall and let it wipe the device.
Yup. I'm experiencing this as well. Happened to me twice yesterday. Maybe try a factory reset?
Sent from my Pixel XL using Tapatalk
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
I've had 3 reboots since jumping on Oreo. Did my update the clean way through a factory reset and flashing a factory image. Stock, unrooted.
humdrum2009 said:
Having the same issue did a complete factory install with the stock image.
Then rooted not sure if that is causing my issues but, is anyone else stock not rooted having random reboots?
Click to expand...
Click to collapse
Stock, updated via ota... Having 5 to 6 reboots per hour. Google is sending a replacement phone.
Maybe you have to do a factory reset.
Reason why i havent upgraded. Still on a rock solid nougat until google fix all this problems. Maybe 8.1 or so. Seem like reboot is a common problem with the pixel,. All thread about orea theres someone talking about his reboot problem in many different sites.
jerryhou85 said:
Maybe you have to do a factory reset.
Click to expand...
Click to collapse
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
sandibhatt said:
Did that too. It is even rebooting in safe mode after a factory reset Hence the return...
Click to expand...
Click to collapse
That sounds much like a hardware failure... :crying:
I had random reboots too coming from DP4 to FInal. No more random reboots since I flashed the factory images
Is 8.0 the version that is the start of the new OS updating system? I wonder if the partitioning is getting all screwed up? I think I'll stay on 7.1.2 for a bit longer till this gets ironed out.
Sent from my Pixel XL using Tapatalk
Stock, bootloader unlocked, Oreo by OTA, and 1 random reboot and 1 random power off
Sent from my sailfish using XDA Labs
Not gonna upgrade to Oreo.
Is there such a way?
nabbed said:
Not gonna upgrade to Oreo.
Is there such a way?
Click to expand...
Click to collapse
Just don't download the OTA till they send out a patch. That's what I'm doing.
Sent from my Pixel XL using Tapatalk
when i first updated to oreo and rooted it, i ran into the rebooting issues some of you are experiencing. i think the root of my issue was busybox. i did a clean install of oreo again the other day and rooted, but didnt put busybox on the phone. phone ran fine for a day, so i tried giving busybox another go. the reboot issues came back. hope this helps
Mine only reboots randomly if I have YouTube picture in picture enabled once I disabled it I haven't had any reboots maybe try to disable that
Just did the update a couple hours ago and so far so good. Picture in picture works too. Stock, GPE on VZW, no root or anything.
Sent from my Pixel XL using Tapatalk
Guys, anyone still getting random on persistent reboots on Oreo with Pixel (XL)? I'm doing my second factory reset atm and monitoring these two threads on buganiser - 1, 2. Basically people started getting reboots after upgrading to Oreo and one notable common thing is: 'Sense Key : Hardware Error [current]' which Google reps assigned to the threads read as hardware issue (probably with Toshiba's memory chips being prone to overflow/overload (?)). They haven't answered my question why is it only happening on Oreo though. I REALLY don't want to go through the warranty process again only to get a device with the same problem as I still believe it can be fixed in 8.1. Is there anyone who had similar issues that got fixed with the 8.1 Beta? Cheers!
I'm experiencing the random reboots too.
Oct. 8.0, Magisk, Root
I almost missed an alarm due to this, so I think I may go back to Nougat. Not only does it reboot, but it gets stuck in the boot screen. If I hold Power and reboot, it comes up though.
Hello! I am going to describe my issue with 2 years old nexus 5x which is restarting randomly.
It all started a couple of days ago when my phone started to ask me to enter PIN code. That happened randomly. After entering the code my phone worked completely ok.
But yesterday it started restarting on its own. The restart happened once, than I suddenly got a message before loading screen saying: "Your device is corrupt. It can not be trusted and may not work properly".
Today my Nexus restarted around 10 times. These restarts do not depand on phone usage, since it is restarting randomly (when charging, when not charging, when using it, when screen is off).
I decided to clear cache partition factory reset it and update apps. Unfortunately that did not help, since my phone is restarting even more frequently. Normally it freezes for 5 seconds and than restarts. Sometimes I still get the message: "Your device is corrupt...", but not always.
My Nexus has not been modified (it is not rooted and it is running android 8.1 with november security patch). Also apps have been installed only from play store and not from unknown sources.
I would really need your help. Has anybody experienced any similar issues or does anybody know what could cause the restarting?
Thank you in advance.
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
rp158 said:
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
Click to expand...
Click to collapse
Thank you for your response. Is installing a custom rom the only possible soultion?
No. It's no solution. It's a vague trial.
tic_tac7 said:
Thank you for your response. Is installing a custom rom the only possible soultion?
Click to expand...
Click to collapse
If you are original owner of phone for up to 30 months, go here and let LG fix (or attempt to) the phone. Mine required two repairs. If you are not in the US, check with LG support in your country.