Hi all,
I have my Nexus 5 since December and I really like it. But since 2 or 3 weeks my device randomly reboots. I used the franco kernel and my first assumption was that it is causing the reboots, so I went back to the stock kernel some days ago. But the device continued to reboot. It reboots randomly. I am not able to assign the reboots to specific app or something. I haven´t tried a factory reset yet, because it would take me a long time to configure the device.
I attached the last_kmsg.log I captured directly after the last reboot. One of the last entrys is: Kernel panic - not syncing: Fatal exception in interrupt.
Maybe someone with more knowledge can have a look at it?
Could this be software or a hardware issue?
thanks in advance for any help
These are what i recommend you actions are:
1) Factory reset the device (You can take a nandroid backup and a titanium backup first)
is it still rebooting? if no, start to restore your apps/data one by one until you locate the one that causes the reboots. Is yes:
2) Return to stock factory images all round.
is it still rebooting? If no, ROM / Kernel issue. if Yes, potentially hardware issue
DasPantoffeltier said:
Hi all,
I have my Nexus 5 since December and I really like it. But since 2 or 3 weeks my device randomly reboots. I used the franco kernel and my first assumption was that it is causing the reboots, so I went back to the stock kernel some days ago. But the device continued to reboot. It reboots randomly. I am not able to assign the reboots to specific app or something. I haven´t tried a factory reset yet, because it would take me a long time to configure the device.
I attached the last_kmsg.log I captured directly after the last reboot. One of the last entrys is: Kernel panic - not syncing: Fatal exception in interrupt.
Maybe someone with more knowledge can have a look at it?
Could this be software or a hardware issue?
thanks in advance for any help
Click to expand...
Click to collapse
I would flash the rom first without an wipe and run it with stock kernel.
Dont know if you run a custom rom or not
I run stock rom with custom kernel. Since I experienced the reboots I changed back to stock kernel.
I will try your suggestions on the weekend.
thanks for your answers
I set my phone back to totally stock last Saturday and I had no rebooty since then. I will monitor this for a another week and will root and flash a custom kernel when there are no reboots until then.
Related
I recently unlocked/rooted my Xoom and flashed Tiamat 1.4.4 kernel. At some point over the next few days, I noticed that my Xoom was randomly doing full reboots periodically while idle with the screen off. I started backing my overclock down from 1.5, to 1.4, and then to the stock 1.0ghz. I have also tried doing a full factory wipe from CFW and then restoring from the backup I created when I first flashed the kernel, and the reboots still persist. I also find it odd that I can run a stress test in SetCPU for 1+ hour with no reboot or hang. Is anyone else having this issue on this kernel? Is my only option to flash back to the stock kernel? Could this be a hardware issue?
burgerearmuffs said:
I recently unlocked/rooted my Xoom and flashed Tiamat 1.4.4 kernel. At some point over the next few days, I noticed that my Xoom was randomly doing full reboots periodically while idle with the screen off. I started backing my overclock down from 1.5, to 1.4, and then to the stock 1.0ghz. I have also tried doing a full factory wipe from CFW and then restoring from the backup I created when I first flashed the kernel, and the reboots still persist. I also find it odd that I can run a stress test in SetCPU for 1+ hour with no reboot or hang. Is anyone else having this issue on this kernel? Is my only option to flash back to the stock kernel? Could this be a hardware issue?
Click to expand...
Click to collapse
I did have this, about once or twice per day with 1.4.4. After I updated to Tiamat ROM 1.0, I have had no spontaneous reboots.
Sent from my Xoom using XDA Premium App
Thanks for the quick reply. Any idea what piece of the ROM might have caused the fix? There are parts of the Tiamat ROM that I don't need, and would like to avoid what I can. Also, does anyone know of an app that will create an event log that will stay throughout a reboot to help troubleshoot the cause? I tried OSMonitor but it wipes on reboot.
burgerearmuffs said:
Thanks for the quick reply. Any idea what piece of the ROM might have caused the fix? There are parts of the Tiamat ROM that I don't need, and would like to avoid what I can. Also, does anyone know of an app that will create an event log that will stay throughout a reboot to help troubleshoot the cause? I tried OSMonitor but it wipes on reboot.
Click to expand...
Click to collapse
Sorry, I have no idea.
Sent from my Xoom using XDA Premium App
I have had my TF for a week or so, and have had no issues whatsover. I have am rooted, running a custom kernel.
All of the sudden I am having the TF reboot at random places, and now it is freezing even in CWM recovery. I wiped everything and went back to stock and still having the problem (on 3.1). Anyone else with this issue, and does it sound like hardware at this point? I think I may return it today, but I am nervous since the screen on this one is perfect.. don't want to get one with light bleed like my last.
Thanks guys.
yes. A quick search will show you the multitudes of threads regarding this issue.
skydirt said:
yes. A quick search will show you the multitudes of threads regarding this issue.
Click to expand...
Click to collapse
Yeah.. I get that.. I have been on XDA for 4 years.
I understand the freezes and reboots happen and are happening and other people are having them happen, however per my subject line I was looking for people who are having it happen while they are in their recovery mode. I have had the tab freeze after booting into recovery, as well as during a restore and backup. I wasn't having any issues for an entire week and without any kernal or rom mods this just started. (SPECIFICALLY IN RECOVERY MODE AS WELL AS NORMAL MODE)
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
sassafras_ said:
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
Click to expand...
Click to collapse
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
superevilllama said:
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
Click to expand...
Click to collapse
Hey there superevilllama, glad to see you back on XDA. Question, are you running custom firmware, ie. custom kernel, ROM, etc? If so, I would suggest downloading the stock firmware from ASUS and flashing back completely to stock and see if that alleviates any issues. If this continues to happen on a completely stock system, you might have faulty hardware.
It was the kernel...
Alright guys.. It was the kernel. I wiped and reset to stock, thinking I had already went back to stock kernel but apparently flashed the same kernel instead of stock.
I checked Clemsyn's kernel thread and # 17 of his had other people getting lockups and reboots too, OC or not. Gave me a scare because I did a bunch of things at one time.. updated kernel, got a new keyboard dock, updated setcpu.
I kept freezing all over the place and rebooting, OC or not. Thought I restored back to stock kernel but I didn't. Thought it was wierd as I had no issues before. Back to 16 of Clemsyn's kernel and all is well, both when not overclocked and OC to 1.5ghz.
I appreciate your help guys. Glad to know my TF is still in good shape. Good thing because the replacement I got had bbaaadd light leakage. Now I can just take it back.
Yes, it was the kernel.
More importantly, it looks like it was the clock speed.
sassafras
It is wierd that it froze in recovery mode tho. I thought recovery had its own kernel, I didn't think it used whatever kernel I had flashed. Eh either way I am glad it is working.
I bought a brand new HTC chacha some 4 weeks back and had my first abnormal restart the very next day. I tried everything, did factory resets. changed the SD card and even re-flashed a fresh stock ROM but the problem didnt go away. The log files kept on saying kernel panic, not syncing, error during data -xcfer. I took the set to repair after having tried all of this since there is no warranty offered for HTC sets in my region, I was told by the HTC service technician there was a hardware problem with my phone and that I have to sign a dead approval since my phone can be bricked during the repair process.
I had earlier ran a RAM CPU stress test app which showed no errors with the hardware. In a last attempt to save my first android phone I flashed cyanogenmod 7 on my phone. My phone worked flawlessly for 3 weeks or so, yesterday I decided to give the stock ROM another try and I restored "BACKUP" from the time I flashed the custom rom and yet again within 12 hours had another abnormal reset. the log showed the same kernel panic.
Can anyone offer any info regarding this?
waqaszahid said:
I bought a brand new HTC chacha some 4 weeks back and had my first abnormal restart the very next day. I tried everything, did factory resets. changed the SD card and even re-flashed a fresh stock ROM but the problem didnt go away. The log files kept on saying kernel panic, not syncing, error during data -xcfer. I took the set to repair after having tried all of this since there is no warranty offered for HTC sets in my region, I was told by the HTC service technician there was a hardware problem with my phone and that I have to sign a dead approval since my phone can be bricked during the repair process.
I had earlier ran a RAM CPU stress test app which showed no errors with the hardware. In a last attempt to save my first android phone I flashed cyanogenmod 7 on my phone. My phone worked flawlessly for 3 weeks or so, yesterday I decided to give the stock ROM another try and I restored "BACKUP" from the time I flashed the custom rom and yet again within 12 hours had another abnormal reset. the log showed the same kernel panic.
Can anyone offer any info regarding this?
Click to expand...
Click to collapse
no help?
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
NotReallyKnown said:
Hey guys, i'm posting here because I have a huge issue with my phone.
I think I have an idea of what caused my phone to go haywire, but i'm gonna post my phone specs:
Red Nexus 5 32gb
Rooted
Franco Kernel
4.4.2 (however, I think it may have somehow updated to 4.4.3 OTA somehow, which may be the root of the problems)
TWRP
Nandroid backup but done once i've been experiencing these problems
-The phone boots up normally and then abrubtly freezes.
-The dialogue "Unfortunately, the process com.android.systemui has stopped."
-I press ok, the screen turns black
-"Unfortunately, Update Device has stopped"
-I press ok, shortly after, both prompts pop up again repeatedly.
I literally have no way to get to the home menu, even using Safe Mode.
My main priority is to at least recover my SMS files. And obviously fix my phone..
Click to expand...
Click to collapse
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
simms22 said:
reflash your rom, or flash another rom. if using stock, you can reflash the factory img or find a rooted stock rom. anyways, you DO want to update to 444, as many bugs have been fixed from 442 to 444. if yoy dont want to lose any data, grab a stock rooted rom and flash it dirty, as in dont wipe a single thing. and your phone can not update itself, only you can let it update. and with you using franco kernel, it can not flash an ota, you would have to do it manually.
Click to expand...
Click to collapse
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
NotReallyKnown said:
Do you mind linking me a good thread on how to dirty flash a rom? I've been looking all over and i'm getting a lot of results that simply don't work.
Edit:
Nevermind, found out how to use adb. Can you at least tell me where the SMS files are stored? I used Textra.
Click to expand...
Click to collapse
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
simms22 said:
well, theres no such thing. as most everyone will tell you the proper way is to clean flash, you wont find a dirty flashing thread. regardless, im known for my dirty flashing of everything. generally, what you do to dirty flash is make a backup in recovery first, then just flash what you need to flash, without wiping anything. the thing about dirty flashing is that you dont lose any data(while clean flashing you do).
where the sms files are stored, i have no idea. have you checked if your sms app created a file?
Click to expand...
Click to collapse
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
NotReallyKnown said:
So what I should do is push the rooted stock rom somewhere into my phone and use TWRP to install it straight?
Click to expand...
Click to collapse
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
simms22 said:
right. adb push it to your phone, then flash it in twrp. if the dirty flash doesnt work out(chances are that it will) then you would have to wipe data(factory reset) and reflash.
Click to expand...
Click to collapse
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
NotReallyKnown said:
You are a f**king god. It worked perfectly! Thank you so much!
Why isn't Dirty Flashing suggested by most?
Click to expand...
Click to collapse
because most follow older "proper" ways to flash software. and the proper way to flash, and to make sure all is working as should, is to clean flash. dirty flashing can cause issues, but its issues that are usually fixable. the problem is that most dont know that, or how to fix. 99.99% of issues caused by dirty flashing are caused by corrupt or incompatible data. where a data clearing for that particular app will usually fix. anyways, roms based on the same sourcw, and not far from what you are running, you can dirty flash. roms that have a different base than what you are running, you should factory reset first.
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
wangdaning said:
Dirty flashing has the potential of causing conflicts and issues. Of course it is not so bad if you back up your data. One problem though, is you might use your phone for a few weeks before the issues show up, then suddenly you are unable to backup data. So you lost a week or two of stuff.
By the way, I often dirty flash when I run into issues. After that though, it is a good idea to back everything up, wipe, and reflash everything. Limits potential issues arising and also causes of said issues.
Click to expand...
Click to collapse
issues from dirty flashing do not appear weeks later, dirty flashing issues show up right away. all dirty flashing issues are caused by data, whether corrupt or incompatible. other issues are blamed on dirty flashes, but arent the real cause. issues like app fc's are the most common, and very fixable. the only issues that arent fixable are when you dirtt flash two completely different roms that are based on different sources, or different android versions. i have dirty flashed every single thing ive flashed onto my n5, since december, no issues. the only issue i had dirty flashing my n5 was dirty flashing L over rastakat. and the issue was minor. everything worked great except the status bar didnt go down all the way. why did it mess uo? because of incompatible data from rastakat with the new status bar code in L.
You are correct Simms, but it must be noted that you dirty flash the same version, for dirty flash to work. If just updating a rom it is usually fine, but if they have made a major change then it is not.
Have no tales to tell of my N5, but my Samcrap S3 (cracked the screen and she died, then I bought this bad boy ) had issues that would appear later. Maybe due to the dirty flash. Who knows, that is why I mentioned a clean flash rules that out.
Anyway, backing up everything leads to a carefree life!
Hi bro, i need some help here, suddenly my GT2 (GSM) will auto reboot after every 15-60 minute. It was running fine for the past 10 month since have install cyanogenmod cm-10.1.3.
The weird part is, not only it reboot, it will do a rollback to a fix setting every time it reboot.
- Let say, as a normal you have many application install, many photo or file in your phone
How it happen, as a normal user, I went to uninstall any application via application manager or Delete some photo from my gallery. It show success deleted..... but soon after few minute my phone rebooted by itself. After this reboot i notice what i just delete/remove come back again. Seems like there is a restore being done.
I also try to reset to setting using phone manager, and it fail
I try to boot in to recover mode, such as
clear data/factory reset
clear cache
go to advanced>wipr dalvic
Install cyanogenmod cm-10.1.3, cyanogenmod cm-10.1.2 or even cyanogenmod cm-10.1.1
I have try clear data/factory reset, clear cache, go to advanced>wipr dalvic
or any other combine setting i can think of.... it fail too
once i reboot my phone, it still went back to this Fix Setting, every thing just come back.....
even i select install new OS
Any ideas what happen?
Thanks
Look here for similar issue. Maybe move conversation there and see if together a solution is found.
http://forum.xda-developers.com/showthread.php?t=2859471
Sent from my Nexus 4 using XDA Premium HD app
Yes, it look simular to my issue, can you help PM me the step, so that will give it a try. Now i just been force to bought a new smart phone as my current not working.
Read about these issues from various thread, this is happened due to broken emmc. The only step will have to replace it.
If someone can developed a kernel to prevent this issue which is happen to omap4 device
Unfortunately most kernel, maybe all current kernel, did not apply this.
jak978 said:
Read about these issues from various thread, this is happened due to broken emmc. The only step will have to replace it.
If someone can developed a kernel to prevent this issue which is happen to omap4 device
Unfortunately most kernel, maybe all current kernel, did not apply this.
Click to expand...
Click to collapse
So this is due to broken emmc, and i need to ask someone to replace it at some cost
is there a way to check the issue is emmc or just some software/firmware/rom issue
Till now, my phone still stay the same, it will reboot after sometime. I even try to flash it with other ROMS and even update my phone with the latest CWM or PhilZ, i even get the message of update success/status ok. But after a reboot, my phone still went back/revert to that same "OLD" setting with every thing still there. Restore to factory still fail, look like my phone is as good as a brick phone...
Anyone know of a way to resolve it?