Hi all, I've been having random reboots as of late. I tried factory resetting, installing night lies, and then back to stock rom, and I installed different kernels also. I tried Franco and ak but both still give me reboots. I have a system log, but not sure what it means. It seems to have an error near the end of the log.
One is a .txt file, the other is a .log file.
Any help would be greatly appreciated.
Related
Greetings, all. Long time reader, first time posting.
I had recently flashed the HFS and EB ICS roms, and both were running without issue. Then, out of the blue, I stopped receiving SMS. I could still send, but could not receive. I had read on the HFS thread that a few others had experienced this issue. After searching various threads and forums, I couldn't find a solution. After a re-flash of both HFS and EB didn’t fix the problem on either, I flashed a couple of GB roms, and was still unable to receive SMS. Finally, I restored back to Stock GB and SMS worked fine.
I am sometimes able to receive SMS on ICS when WIFI Calling is active, but it is inconsistent.
I’ve tried the following to remedy this issue, with no success:
CWM>Wipe Data, Cache, and Dalvik, Flash rom and Gapps.
CWM>Wipe Data, Cache, and Dalvik, Format Data, System, and Cache, Flash rom and Gapps.
Same steps as above, but with G2x Scrubber (sometimes scrubbing twice) thrown into the mix.
Re-downloading roms, in case of file corruption.
Fixing permissions before and after first boot.
Master reset before and after first boot.
GetRIL.
SMSC Update.
APN delete, restore, manually enter, etc.
Tried multiple SMS apps (Stock, GO, Handcent).
Flashing Gapps after first boot.
Skipping Google account setup on first boot.
I followed all rom installation instructions, including waiting ten minutes before touching the phone after first boot.
I suppose the only thing I haven’t tried is flashing a different Kernel after flashing the rom. My only other thought is to flash the Stock recovery, then re-flash CWM and try it all again.
If anyone has any suggestions, your assistance would be greatly appreciated.
Battery pull?
iArtisan said:
Battery pull?
Click to expand...
Click to collapse
If only it were that simple; but, no, I tried that as well.
Unfortunately I don't have anything to add other than I'm having the same issue with ICS and CM7 roms. I can receive SMS on MIUI and Bionix and have gone through the same troubleshooting steps. I'll add that I've tried a different SIM as well...no dice.
I saw someone post on another thread that they resolved this issue through T-mobile customer support, but I'm skeptical.
EDIT: Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
akelty said:
Maybe I'll at least save you some time...I also tried going all the way back to stock recovery like you mentioned with no luck.
Click to expand...
Click to collapse
Thanks. After reading that, I didn't bother trying. I'm happy to say I did a warranty excahnge and ICS is running beautifully on my new G2x, though I still wish I could've figured out what the issue was with the last one. Thanks again for your response and trying out that fix.
If anybody's still following this thread I found a solution for GB roms that cannot receive SMS. I had trouble with EaglesBlood and tried flashing the Trinity kernel...viola! Getting all my texts now.
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.
I was running a rooted stock ROM when I wanted to install Franco kernel r32. After installing the kernel I kept getting random reboots. While using nearly all applications after sometime the screen just freezes and then in 10 seconds the phone reboots. This keep s happening again and again. Can anybody help me with this? I really want to run franco kernel.
@starbriganza To resolve problem, you need to do logcat, look here - How To Logcat, then place your question and attached log here.
I'm using a stock based ROM and never had this with r32. I'm assuming you made backup before flashing, so restore pre-kernel backup-> WIPE cache/dalvik-> install zip again. Worked everytime. Also try re-downloading the kernel zip, may have bad download. Also make sure your recovery is doing proper job of wiping the data. Good luck.
Are you sure it's just Franco Kernel try another kenel? Maybe try downloading it and installing again just for peace of mind.
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Synyster06Gates said:
I've got a bit of an issue here. Out of nowhere (I've had the latest OTAs for about 2 weeks now) I am unable to receive SMS. When one tries to come through I got a "com.android.phone has stopped". I was bone stock, no unlocked bootloader or anything. Since then, I have tried a couple different ROMs but still seem to be unable to get SMS. MMS come through fine and I can send outgoing messages, but SMS do not work. Data also seems to work fine.
Any ideas would be incredibly helpful.
Thank you!
ETA : On the first boot of a stock + root install, I was able ot send one before getting the error. I don't understand. After the error pops up once, I can not get any more SMS.
ETA 2 : I have flashed the factory CM11 image and still get the issue on CM11. I am at a loss and have no idea what else to do. It seems to be a hardware problem.
ETA 3 : Here is my exact crash report.
java.lang.NullPointerException: Attempt to invoke virtual method 'long com.android.internal.telephony.SmsMessageBase.getTimestampMillis()' on a null object reference
at android.telephony.SmsMessage.getTimestampMillis(SmsMessage.java:625)
at com.android.internal.telephony.InboundSmsHandler.notifyAndAcknowledgeLastIncomingSms(InboundSmsHandler.java:621)
at com.android.internal.telephony.InboundSmsHandler.handleNewSms(InboundSmsHandler.java:510)
at com.android.internal.telephony.InboundSmsHandler$DeliveringState.processMessage(InboundSmsHandler.java:397)
at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:966)
at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:789)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
Click to expand...
Click to collapse
Raketemensch23 said:
I had the exact same problem on my wife's OPO, rooted, stock ROM, though it turned out slightly differently. The update gave the never-ending com.android.phone error. You can go into Airplane Mode to stop the crash. I read through the crash logs, and figured it was something to do with the APN. I deleted the APN, turned off Airplane Mode, and the crash stopped.
Phone and SMS work fine, as does wi-fi. However, I couldn't get any data at all. Not a great solution. I couldn't manually set the APN either, since I got a "APN Settings not allowed for this user" message, and removing the SIM, rebooting without it, then inserting it again, didn't help.
Also, root was removed. I installed TWRP and re-flashed the SuperSU zip file (make sure you go directly into recovery after the fastboot reboot or it'll flash Cyanogen Recover on top of TWRP and you have to start over!).
I did a full Titanium Backup as well as a Nandroid backup to a USB-OTG drive. Next step is to do a factory reset in TWRP and see if that fixes the APN issue.
Click to expand...
Click to collapse
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Synyster06Gates said:
Unfortunately nothing has worked. I have fully wiped the phone MANY times. I installed 4 different 5.0.2 ROMs, rolled back to factory 4.4.4 ROM via fastboot, and even tried a 5.1.1 ROM this morning. The only time it crashes is when I receive a text.
Click to expand...
Click to collapse
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
The_Symbiote said:
Have you tried flashing a new modem at all? It seems the only thing that would be the same still after flashing all of those various ROMs would be the modem. Seeing as you have issues with the communication, I'd say modem would be a good thing to try..
Try flashing your rom, then the appropriate modem, then boot.
You can get your modem from either here (for OxygenOS) which should work for CM12, 12.1, etc. or here (for CM11/CM11s)
Click to expand...
Click to collapse
I'm beginning to think T-Mobile had an issue with the OPO devices or something. I was speaking with someone across the country (eliminating a tower problem) that was running Oxygen OS and I had restored to COS12 at the time. Both of our devices suddenly got all the texts that had previously not come in and they started working correctly at the same time. As of right now it seems I'm good to go.
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
natboy said:
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
Click to expand...
Click to collapse
To make things clearer. Previous what ROM were you on? After your proclaimed (OTA), what was the ROM suppose to be?
I went from the Oneplus One CM 4.4.4 to the CM 5.1 OTA. Not sure why you're don't believe me..
I think I might have bad memory or flash or something at this point..
So since yesterday I've tried using the tutorials here to flash stock Kitkat with the same errors happening. When it boots up, I get a done of crashes on things like gapps and process.acore. I also tried flashing the stock Lollipop; both using the non fastboot and fastboot way. Every time wiping everything with all the same results. The only rom I've had some slight uptime with has been slimrom without gapps as there's not much running there. Once I add the gapps package to it, processes start crashing again.
Does anyone know of a memory/cpu/flash test I could try, or any other suggestions? Thank you.