Bought this device in March, and it has been a SERIOUS headache with random reboots, and bootloops, crash dumps, and app crashes. Successfully rooted the device to try to fix the issue. Even with the root tools, I was still getting these issues. So this is how I fixed it on my phone:
1: I noticed a "carrier services" update. Instead of updating, I powered off the phone.
2: I removed the sim and SDcard from the device
3: Then powered up the phone without the sim and SDcard ion the device.
4: I let the phone sit for 5min (just to make sure all the starup software was loaded).
5: I updated "Carrier Services"
6: After the update was complete, I powered off the phone
7: Inserted the sim and SDcard
8: powered back up
9: let sit for 5min
So far.. my phone has been working without any random reboots for a record 5 days and counting.
I'm not sure which one, or if all these steps fixed it, but it might help another frustrated user.
Related
Problem:
Phone dialer lags several seconds before placing call. At times dial screen will say dialing and never put call through. When hitting end call nothing happens. Phone must be rebooted.
About Phone Settings:
Mobile Network State: Disconnected
Build JDQ39.I545VRUAMDK
USB debugging unchecked
Actions:
1. Rooted phone with all-in-1 toolkit (including clean up), installed TWRP, made recovery. Flashed Hyperdrive. Noticed phone issue.
a. Would also get a periodic RED TRIANGLE and message to re-insert SIM card.
2. Restored to factory – modem, recovery, kernel, stock rom. Re-rooted phone. Re-installed TWRP but no other Apps.
3. Tried to install Synergy through TWRP. Boots to Samsung screen and nothing more.
4. Restored to factory (step 2). Still getting phone dialer lag / non-response.
5. Currently on stock ROM with annoying message to take OTA update…
Thoughts, anyone else experiencing similar situation, recommendations?
Does Synergy need to be loaded to the internal SD card to work? Is TWRP bad?
Good day all
I bought this device from a seller of eBay (from USA), I am in South Africa
I had to network unlock this device, and it all ran perfect, no issues whatsoever
Recently I have noticed my device doing random reboots, once every day(literally), it will reboot when I take it off from charging or when I press pwer button to wake up. After reboot, it will show the Glowing Samsung Logo, and just stay there continueously.
To fix this, I need to do a factory reset, or just clear the Data partition then it works fine again.
This happens at random, so every day I need to reinstall all the apps, it is such a pain, and obviously something is wrong...
Device: Samsung Galaxy Note LTE (i717)
ROM: Blackstar Blackjelly 4.1.2
Baseband: I717 UCMD3
Recovery: TWRP (latest v.)
Just for the record, ,it all started happening recently, the first time it happened, I was browsing 9gag using the app, then my device rebooted in my hand while scrolling, agter going to recovery, my sdcard and internal sdcard has been formated, and all internal partitions has been formated to....
I have no idea what is causing this but I am pretty sure it is not the rom, since I have had this rom for a while now...
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
BachMinuetInG said:
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
Click to expand...
Click to collapse
after running the logcat with "
Code:
adb logcat > logcat.txt
" for just more than 2 hours, i stopped it...it is 1250kb, see attached, it is compresssed in a zip file
p.s. Im quite positive it shouldnt take that long
any help would really help!!!
Hi Guys.
I'm at the end of my rope here ...
A few months back I updated my phone and my wife's phones to NC5, towelroot, TB freeze knox, etc. Both have been working great, until: last night my wife's phone crashed while playing music. Now it's stuck in some sort of strange "dies during startup" mode ...
When the phone is powered on, all the apps start crashing ("unfortunately, weather.com has crashed", "unfortunately, Google play services has stopped responding"). The phone freezes, and then reboots. It hangs at the Verizon loading screen, and I get lines of digital pixilated noise across the bottom. Hold power and the phone turns off; when you restart it, it loads up, and crashes as the OS loads (you get about 15 seconds where the phone is usable before it dies).
Notes: Xposed is not loaded on her phone. She's running NC5, stock. SD card has been removed.
Things I've tried:
Odin-flashing NC5 (no wipe) ... no change
Odin-flashing NC5 (full wipe) ... no change
Recovery - delete all user data and cache ... no change
Swapping her battery for mine ... no change
Power off, full charge overnight ... no change
Removed battery for 5 minutes before trying again ... no change.
Its now back fully at stock with no user data. It boots up into "Welcome to your new phone", but before you can even select "English" as the language, you get: "Unfortunately, Messaging has stopped." The phone hanges, then reboots and gets stuck at the Verizon splash. (Note: sometimes, it just hangs and doesn't reboot.)
Anyone ever seen this? Is it a HW problem, or is there something I can do?
Thanks in advance!
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Have you performed a factory reset? (It will delete all your data and apps)
rp-x1 said:
Have you performed a factory reset? (It will delete all your data and apps)
Click to expand...
Click to collapse
Yes, when the phone was new and the restarts were annoying. It fixed it for 1 day. The next day it was restarting again.
This would point to an app you've installed causing the issue. Factory reset again and install each app one by one until the restarts happen to find out which.
SteveTM said:
Hey guys! This is my first thread here, but I knew this site before. I've got an M4 Aqua E2303, Android 5.0, Build 26.1.A.2.167 (upgraded from .99 with TWRP to keep the root.).
The story : I've got this phone like 4 months ago, I was so happy etc... After it updated to 5.0 it kept restarting randomly. Total random, when it was not under using, if I use it, it does not restart itself. Sometimes the restarts occurs when it's under charging, and sometimes when I want to unlock it and use it, and sometimes total randomly, and sometimes it shuts down. For different verions the problem was different too. On 26.1.A.2.99 it was the worst, it restarded and stuck on the boot screen until reached 0% battery. On 26.1.A.2.128 It turend off the screen, but the phone was running and the LED was red (even when fully charged) and only started with the hard off button in the SD card slot.
I've got the default "Diagnostics" app, now it says that the Phone got system errors 42 times in 10 days. It was worse before (over 140). But it doesn't say why did it restart, I'm hoping for help from any of you, who had this issue and solved it, or someone who knows a better diagnostic tool that will explain what caused the system fault.
I appreciate all the helps!
Click to expand...
Click to collapse
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
cmstew said:
If you used the pre-rooted zip to maintain root while updating to the latest android, this will fix your rebooting problem. Follow this guide:
http://forum.xda-developers.com/m4-aqua/general/guide-fixing-random-gplay-app-install-t3338362
Click to expand...
Click to collapse
Will try it when I'll have time for it, thanks for the help!
I have infocus epic 1 device and its standby is terrible from the day of purchase(>2.5%/*h).It stays awake 100% of time.I rooted the phone on sole purpose of fixing it.after doing some research now i am sure it's something related to radio layer interface because when i don't install sim card mobile goes deep sleep 98% of time.better battrey stat show's kernel wakelock ttyC0 as main culprit.i think com.android.phone is the reason behind it.i have found one tedious solution to fix it.first i ve to freeze the package com.android.phone pluck the sim out restart the phone put sim back in and defreeze the package.but rebooting the phone again starts the problem.but i want to completely fix it without need to do so.also it would be hepful if i can some how block mandatory restart after inserting sim in the sim slot so i dont have to freeze and defreeze the package com.android.phone
I think you should try a (few) different SIM card(s). It may be the card itself that causes problems.
Then, I’d reboot the phone, after entering the PIN, wait a minute of so for everything to initialize, and then check dmesg (aka the kernel/driver log), or even logcat for that time period.
Also, if you can, try making a complete backup image of your system (all partitions), and
1. try a factory reset of your phone (ideally flashing the original system on there after the factory reset), or even
2. flash an older Android (6? 4.4?),
and see if the problem exists there too.
You should be able to find the newest/best case where it works, vs the oldest/worst case where it doesn't, and then look at what’s different between the two (with some graphical diff tool, using dmesg and logcat output among other things, for example) , especially with regard to your problem, to find the answer.