Hello.
I have bought a galaxy note 4, but I am experiencing the following problem: almost every application crashes ("unfortunately, application has stopped") really frequently - it's a matter of minutes, sometimes seconds. I can launch browser, open a couple of pages, then it crashes. Setting up google voice search crashed about 3 times before I could set it up. Play market often crashes just when I open it (sometimes it doesn't). S-voice can crash just after booting the phone. Even launcher often hangs a few seconds then reboots.
The device originally was on android 4, but the issues I am experiencing were manifesting already. I thought that updating it to android 5 could fix them, but the problem remained.
I have tried factory resetting the device and clearing cache - no effect.
Is there anything else I can try or my only option is to go to official service?
Thank you in advance.
Sounds like data partition corruption to me. I had that on my note 2, which, funny enough, was caused by a bad battery. But once I got a fresh battery, I flashed the stock rom in Odin with a pit file to repartition and it's been fine ever since.
So as a last resort you could try that. I don't think your situation is as severe as that. Have you factory reset stone updating?
You could also try to format the data partition via recovery (and wipe the other partitions + reinstall your current stock rom on the device after it's good and cleaned). See if that resolves it. If not you'll have to go the Odin route.
Related
Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .
*bump*
I have the same problem. Help would be highly appreciated. : )
*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?
Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...
I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1
[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.
The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!
Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart
Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!
Hello, I've been using TEKXodus N4 Rom for my Canadian (Global Live Wind) on my Note 4 running 5.1.1 for about 4 months now. I have not experienced any problem with the rom until 3 days ago. My phone would just freeze for a good 10-20 seconds randomly when I open apps, surf the web, etc. It started when I was using snapchat and I though I had too much friends (around 80) on my snapchat that it would freeze when I load my friends stories but it seems it's not just the app. I tried clearing cache but it did not fix anything. It was so bad that I couldn't bear to use my phone. I finally decided to flash to stock 4.4.4 kitkat and 5.0.1 but it seems the lag is still there. I've even had instances where my phone would just restart on it's own and when I turn my phone off it would turn on by itself. I've cleared cache, davlik cache and everything there is to clear and it still freezes. I've even ran into a point I cleared everything including my own OS and was stuck for a day in finding a way to boot up my phone lol. I also forgot to say during that time the only thing I did not clear is the files on my sd card so I wiped my sd card as well and it still didn't do lick. I've led to believe that I may have a virus or that my phone hardware is fried. If there is anyone who could help me I'd be grateful...
I also had a problem after I installed a stock 5.0.1 where I couldn't update my phone because it said I don't have enough storage space and I know for a fact I have 24gb free space..
I've got a Canadian G2 D803. I have been using AICP 10 (aicp_d803_lp-10.0-NIGHTLY-20151225), the last lollipop release. I used this because in January when I tried MM release, it caused random soft boots at the time.
With the AICP 10 lollipop, it was mostly working fine until Friday when it all of a sudden doing soft reboots. It wasn't just a single isolated instance. It began doing it constantly. Every time it finished booting up, after a minute or so, it would soft reboots itself. In addition, when it constant soft reboots, the time would reset to linux default of 1970-01-01. Because it only stays in boot completed for only a minute, it wasn't long enough to sync time with service provider or ntp servers. Manually correct the time and a few soft reboots later would reset back to default 1970-01-01.
I should also note that this is not the first time it happened. I traveled to China in May, and this soft reboot loop kept happening. But the problem stopped after I disable auto time sync. But this time, I disable time sync and it's not working.
My main issue right now is I want to backup all the apps and data with Titanium Backup before wiping the phone or moving to another phone. But it only completed boot for 1 minute before it soft reboots by itself again. Within the 1 minute time, for multiple reboots, I uninstall some recent apps. However, so far it doesn't have any effect. I've also tried clearing dalvik and data cache in TWRP. While the phone boots and runs through the "optimizing" app on boot, it doesn't soft reboot, not until it completes booted into the OS. Here is a more detailed list of things I have tried so far without success:
I'm completely at a loss right now as I just want to backup the apps and data first. Does anyone experience something like this before? Anyone has any clue about this or similar issues?
I do have a logcat and kmsg. I don't think I'm allowed to attach to the post because I'm new to XDA. Where can I post it?
Thanks in advance for any help.
Have T-Mobile version of the S7 Edge, stock, never rooted. Yesterday Samsung apps did a few updates, and a few hours later the phone began to have:
(A) apps crash with the message "Unfortunately X Has Stopped"
and(B)reboots, some of which are stuck on T-mobile logo (until I reboot the phone a few more times)
A lot of the apps that are crashing are official Samsung/Google apps, including Play store, Google Play Services, Samsung Pay Framework, com.samsung.faceservice, and etc. Usually this happens when opening a new app. Sometimes it happens in succession and a dozen messages will pop up over each other.
The reboots happen right after the phone freezes for a few seconds (often does this when entering settings > applications. Often the reboots get me stuck on the tmobile logo, with it vibrating every ten seconds or so. Holding power + left vol to reset it works half the time, then it boots normally.
The only other symptom I've noticed is in recovery I see the following message: "dm-verity verification failed"
---------------------
Things I have tried which have not helped:
1. Going into Google web services, Play, Play service and wiping cache.
2. Rebooting into recovery and wiping cache.
3. Rebooting into recovery, and doing full wipe/factory reset.
3.1. Made sure to wipe cache before and after
4. Using Odin to flash stock firmware
4.1. Used the right firmware, (G935TUVU4APK1)
4.2. Made sure to wipe cache + factory reset before and after
5. Using Odin to flash stock firmware + full nand wipe + repartition
5.1. Made sure to wipe cache + factory reset before and after
Still have the same issues. Not exaggerating, each time, as soon as the phone boots past the tmobile logo, and gets to welcome screen, some of the app crashes begin (most consistently com.samsung.faceservice, and almost every round, the phone reboots at least once before I finish setup.
---------------------
I am completely out of ideas. haalp
I am experiencing something similar. Android 6.0.1, with December security patch (7 is not out yet for my Norway TEN phone..). Has happened since purchase.
Every time I update applications in the Play Store, the entire phone freezes.. sometimes I also get a horisontal line across the screen, about 3mm in width. After about 20 seconds the phone reboots into the Samsung logo and starts booting up. At that point, it will reboot about 3-20 times depending on the app that I update. Sometimes clearing the cache works, but only about 1/4 times. It gets insanely hot if connected to a charger (about the temperature of burn marks on skin).. I tried master reset, and it vanishes for a little while before it returns, even if I don't install any applications at all. Been handing it in to Samsung a few times, but they always just tells me that either it is normal, or nothing is wrong.. I don't really know what to do anymore. I am suspecting a hardware failure that happens when it is put under stress.. but since it happens 1 or 2 times per day, the workshops don't have the patience to just keep testing it hard, instead they just run a normal stress test and say that everything is fine.
StOrigen said:
stock, never rooted.
Click to expand...
Click to collapse
StOrigen said:
"dm-verity verification failed"
Click to expand...
Click to collapse
StOrigen said:
Used the right firmware
Click to expand...
Click to collapse
If that all three are as you said then your NAND may be damaged.
This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)