Hello lads! The last few days I have been trying to fix a huge problem with my Galaxy S4 i9505. I had been using the Google 4.4 rom for almost a month without any problem. One day, when my phone was low on battery it shutted down and I plugged it in my charger to power it on again. When it turned on I was prompted to the screen you see when you use the 4.4 rom for the first time. I had all my apps but everything was resetted. Every setting, all the app data, messages, etc. I thought this was a one time thing so I used about an hour to get everything back to normal again. Then the next day, same happened again. Phone turned off because of low battery, and everything was reset. I tried to google it but with no luck, so I did a factory reset and flashed the newest Google rom (4.4.2) with a new kernel called Ktoonsez. Got everything back to normal again and used my phone for a couple of hours before it just suddenly shutted down once again, but this time with almost full battery. When i tried to turn it on I was stuck on the Google loading animation and had to reflash 4.4.2. It turned back on and this time I decided to let the phone stay stock to see if any of my problems was caused of my apps or settings. It lasted for 2-3 days before the same thing happened again... I tried to flash different modems, other roms and firmwares but nothing have helped so far. I am also prompted with a message each time I turn the phone on which tells me that com.android.phone has stopped working. I have tried several factory resets, wiped dalvik, wiped cache, but still has the same problem... I have now given up trying and wonder if anyone of you know what I can do to fix the problem? Any tip is much appreciated and I hope to hear from you! Thanks!
edit: figured out I posted this is the wrong forum as this is for s4 active and i have a i9505. Sorry! Anyway, please comment if you know how to fix it. Thanks!
Fredrik
Related
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Andy.WP7 said:
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Click to expand...
Click to collapse
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
What firmware/ROM are you using?
What firmware/ROM are you using?
Click to expand...
Click to collapse
I am still using the stock Froyo ROM that the phone came with. The phone is rooted and I've installed a SpeedMod Kernel. However, both (rooting and new kernel) have happened months ago, so I doubt that they have anything to do with the problem.
(partial) solution found
Since a phone that crashes every night, using all settings in the process, is fairly useless, I decided that I might just as well trash it completely by trying (and maybe failling ) to install a custom firmware. So I downloaded Darky 10.1 and thanks to an excellent installation guide, I actually managed to install it.
Since then, my phone does no longer crash every night - it now reboots a couple of times a day The good thing is, though that after the reboot, the phone is back "in action" after maybe two minutes and it does not lose any data, setting or anything. So, it's not ideal, but much better than before ...
I was going to recommend trying a new ROM, but I found that as a workaround rather than a solution to your problem.
Did you perform a wipe or no-wipe install?
Kops said:
Did you perform a wipe or no-wipe install?
Click to expand...
Click to collapse
As I had pointed out in my first post, the crash that happens every night breaks something so that I can no longer receive calls and have to do a factory reset. Thus, the phone was basically wiped, already, before I did the installation and I then did a no-wipe install.
You are right, of course that this is more of a work around than a solution, but since I was thinking about putting on a new ROM for a while, already, anyways, it is a fairly good work around for me - and I really like Gingerbread and DarkyROM so far.
Kops said:
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
Click to expand...
Click to collapse
In the end it turned out to be a hardware problem and I needed to get the phone replaced.
Hi there,
Okay, so I have been facing this weird and annoying problem(makes me sometimes throw the phone towards the wall, thanks to AHD solid build otherwise it must have been broken by now). Whenever I turn on the wifi and connect to the network, my phone hangs and freezes for like 10-20s and then restarts. It first started happening around 4 months ago and I have owned this device for more than a year. I cleaned flashed the stock rom again and it was fine and a week later it all started again. And the process of me flashing(Clean flash) again and freezing problem has become a loop. I have clean flashed like 5-6 times in these 4 months but the problem persists. I know some people say that this issue develops when there is a shortage of ram but I use the basic apps which I have been using for years. I clear my cache from time to time and have enough internal storage capacity always. I also have around 250-300mb free ram on average.
I have tried cm11, Validus, Lollipop roms on my AHD but they always have some bugs which makes me stay away from them. I like the fluidity and stability of stock therefore most of the time I stay stock.
Just yesterday when I connected to my home wifi the phone froze as usual and restarted. On restarting it automatically connected itself again with the network and froze and restarted again. This continued for like 10 times in loops, after which I immediately went into the settings and turned off the wifi as the phone restarted.
Please help me out, the phone has become unusable for me.
One thing more, I made a nandroid backup of stock rom JB 4.1.1 AT&T the very first time I flashed a custom rom on my phone and after clean flashing(format system, wiping cache, wiping user data, dalvik cache) I restore the rom from that backup. Basically I have never flashed the rom through RSD Lite.
So maybe I should try flashing with RSD Lite and see if the problem persists?
Seriously, would anyone care to help?
Or I'm just wasting my time here? Isn't this community built to help people?
It's not a problem I've had, but I'd say start from scratch. Go back to stock, then re root and try again.
Sent from my LG-D850 using XDA Free mobile app
Thanks. I'll try. Hopefully it would fix the problem
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
are you using a custom kernel?
JustusIV said:
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
Click to expand...
Click to collapse
Did you change your Android password within the past 72 hours?
cam30era said:
Did you change your Android password within the past 72 hours?
Click to expand...
Click to collapse
Nope...
its not that i just cant connect, its like the hardware is broken.
and just did a complete factory image flash.
still broken
I had this happen to my N6 last week. It started after running the battery completely flat so the green LED lit when I charged it. The fix having repeatedly wiping seemed to be draining battery completely again until the green LED lit when I charged it. It has worked fine ever since.
JustusIV said:
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
Click to expand...
Click to collapse
I have the exact same issue and have tried everything from fully returning to stock which worked a little better but still not well and also tried different radios etc etc and roms... dont know what the deal is.. nothing on the internet seems to help its almost like no one knows how to fix it or its really rare... ugh
hackahero said:
I have the exact same issue and have tried everything from fully returning to stock which worked a little better but still not well and also tried different radios etc etc and roms... dont know what the deal is.. nothing on the internet seems to help its almost like no one knows how to fix it or its really rare... ugh
Click to expand...
Click to collapse
First contacted square trade as that is my insurance, they said contact Moto because it is still under warranty. Did that, Moto said they would replace it. I said i don't want to go without a phone and they said they can charge me 25 and put a 500 hold on my account but they would send the phone first. Said OK phone arrives on Tuesday.
Just as an FYI they did basically say did you factory reset it.... but that is all the trouble shooting.
If anyone is interested in my symptom. Wifi is just always stuck at "turning on" every once in a while it will be off. but when you try to turn it on it just gets stuck again.
When it is stuck you can not turn it off.
paulwoodhouse said:
I had this happen to my N6 last week. It started after running the battery completely flat so the green LED lit when I charged it. The fix having repeatedly wiping seemed to be draining battery completely again until the green LED lit when I charged it. It has worked fine ever since.
Click to expand...
Click to collapse
Might be worth an RMA. see my previous post.
Don't know if I'm a little too late to this post... .But it happened to my Nexus 6 too, tried everything, wipe cache, factory reset, root, delete /persist/wifi but nothing worked....
However, luck seems to be on my side when I went into Google Connectivity Services under Setting--> Apps... and wipe its cache and tried to disable it (but stopped before I did). Then reboot the phone once i wiped all the data from the Google Connectivity Services Apps and VIOLA! It's working now!
*EDIT... It worked for about an hour (allowing me to dl all the apps) but now it has failed again....
I have the same issue as soon and I unlock the bootloader
any ideas? Im going to root again the device and load a different to see if it makes any difference
I am experiencing this as well. Was working fine yesterday and when I tried to go to Android M Preview 3 this happened. Whats worse is that this is happening right after I switched from Unlimited Data on TMo to Project Fi with 3GB. Making this even more frustrating is that Project Fi support says the preview images are now compatible with Project Fi. Isn't that something they should be telling people up front?!
I'm having the same issue on marshmalow, it suddenly started to happen some weeks ago.
First times was solved with phone reboot.
Then was required to clean cache before restart
Now I've tried reclutance suggestion (delete data from google connectivity services and reboot but the problem persist?
I'm using 6.0.1 stock rom without root
I don't want to perform a factory reset
Any suggestion?
here too...close the wifi
All tried doesn't work,
Wipe cache
Wipe dalvik cache (via fastboot as I do not have a custom recovery neither unlocked the boot or root, my phone is completely original)
Also tried to delete wifi data
Any suggestion?
RMA
I'm continuing to have issues with my Motorola Nexus 6 phone.
It is running stock android 6.0.1
I never unlocked it or rooted (Sadly cause If i do so I were able to backup my apps and settings with titanium backup and restore it before a full device reset )
The problem started some weeks ago.
First symptom was that i was unable to enter on Settings -> Data usage (Every time receives an "unfortunately, settings has stopped" message)
Then some days have difficult to connect to wifi or disconnect (at that moment I didn't investigate the issue, just retry considering the issue was on router side)
After some time I realize that the problem was on the phone, specially cause it started to stuck turning on wifi, but for some days just turning off phone and turning it on again solves the issue.
With the time it becomes more and more frequent and turning it off and on didn't solve anything so I've reboot into recovery mode and perform a clear cache but it doesn't solve the issue.
Looking here and at other forums found that this issue is really common and some people solves it trough ADB with "adb shell pm clear com.android.settings" I've tried it but it didn't solve anything.
Even when many people didn't solve it with a factory reset I want to try it, but I need to be able to backup one app data (If could backup everything will be the best but at least need to backup blockchain app (Also have an issue with them as provider and couldn't log in from another device or website, just this device has a session already approved and open)
Any suggestion?
I've upgraded/downloaded to almost any possible rom and the problem is still here
Looking on forums found that is a very common issue since marshmallow in many devices (Specially Nexus)
Most people couldn't fix it but some could.
the problem is with devices macaddress that shown 02:00:00:00:00:00 and get stuck turning on
there are solutions in forums that seems to be a little bizarre like drain battery to 0 and full recharge (This one works for me once)
,others like deleting Google connectivity services cache, or deleting /persist/wifi folder completely
But I found one for nexus 5 who replaces the full /persist partition with a dump and edit the files and permissions with macaddress information.
This seems to have logic and provides an explanation about why the problem persist after, factory reset or rom changing so I want to try it in nexus 6.
Could someone provide me a dump of it?
There is an app: https://play.google.com/store/apps/d...nam.partitions, that makes the process of making a partition backup easy. The persist partition is on /dev/block/mmcblk0p26
Thanks in advance
Did you solve your problem? Because I have the same. Did you try to change Mac address on device?
Hello everyone,
This is my first post on XDA so please forgive me if I'm doing something wrong.
So my story, I got a refurbished unit at Swappa, I updated to the newest version directly (G920TUVU3DOI1) and it was working fine for the first week or so. Then the reboots started happening, I didn't give it too much thought but looked into it anyways.
At first I thought it was a problem with the WiFi and I tried to keep it off for a while, and it did work for a day but again the restarts kept happening, and now with the phone turning off during the night (no apparent loss in battery mind you).
Then I went to rooting and custom kernels.
I installed unikernel v8-0002 through Odin3_v3.10.6 and I tried removing some Samsung apps with TitaniumBackup in case there was some conflict happening but the restarts kept happening.
Then I installed a custom ROM, "XtreStoLite_ROM_v2.4_Deo-Mod-Edition_XXU3COI9_G920-5-F-I-T-W8-K-L-S" to be more specific.
And to my surprise it worked great, no restarts or shutdowns for about 2-3 weeks, it was great!
But then out of the blue the restarts started happening, they started slow, about 2-3 a day.
But after a few days they went to 10-20 and after that 100-200 a day.
Something was definitely wrong. So I installed the original firmware again (G920TUVU3DOI1_G920TTMB3DOI1_G920TUVU3DOI1_HOME) and booted to the stock firmware, restarts kept happening of course (didn't expect them to stop).
So I retreaded my steps and installed multiple other kernels (Unikernel V9, Vindicator, multiple different flavors of them). Also I installed multiple ROMs (Arrow_ROM_v6.0.0, and DN5 - S6 FLAT - EDGE v4 OJ5 - deodex) but nothing seems to work;
I did multiple wipes, storage wipes, cache wipes, factory resets (from GUI and twrp-2.8.7.2-zeroflte) but every time the same thing happens.
I did notice that the phone stutters and freezes, a behavior that I have not experienced before.
I installed CatLog and got multiple log files when the phone restarts but all of them are different and there is no "pattern" to be found (at least in first inspection). I want to upload them but my post count prohibits it.
Please let me know what can I do, I will reply to your questions ASAP so at least I can get some light into what is happening.
Thank you!
I'm in the same boat. Never had a problem before. Received my phone back from Samsung after a screen repair and now, doesnt matter what rom, kernel, patch, it always ends in random reboots. Most often when I'm scrolling or if a page is loading something in the background. It does a lot of hot reboots (not full shutdown and start ups) so its quick but infuriating. Tried everything, slowly losing my patience.
Any idea what it could be? Something related to Knox? Bootloader/Modem?
#3
Hello, I am too having the same problem. Even after a factory reset
Hey, I need help, today I tried to replace the stock battery of my S5 with a replacement battery which came with the phone I bought in Amazon, but I noticed that the second battery was fake since it weighted less than the original one, but I was desperate for more battery life (since updating to MM my battery last 1 day and a half max when it used to hold charge 2 and a half days), I turned my phone off and changed the batteries, I turn on my cellphone everything seems alright but then a pop up (Unfortunately the process com.android.phone has stopped working) appears and I'm like, alright, that's new, and accept, but then it appears again and again every 7 seconds, I rebooted, no change, I followed some online instructions (disable the process, delete cache, data, force stop, wiped the cache partition) but nothing works, so I switched the batteries back, thinking it would fix everything but to my surprise, the pop up still appears, and my SIM is not recognized anymore, can't make calls, can't do anything SIM related, please help me i don't want to wipe the phone again since I just restored all my data like 2 days ago, thank you.
If you aren't rooted you will most likely than not have to restore. That sound like something went corrupt with in the sec.phone apk or even system wide. I don't think it was the battery that did it tho.
Anyone more knowledgeable might have a better solution, good luck.
sejodesign said:
If you aren't rooted you will most likely than not have to restore. That sound like something went corrupt with in the sec.phone apk or even system wide. I don't think it was the battery that did it tho.
Anyone more knowledgeable might have a better solution, good luck.
Click to expand...
Click to collapse
I guess it's firmware because I hard reset my phone and after the first reboot the problem came back