Hi all,
I have a SM-G900F Galaxy S5. In Stock ROM (BL Locked) the phone suffer random reboots, the phone crash like 2 seconds an then reboots, no mater what are you doing (Using S-Health, Youtube, Phone...) So I've tried unlocking BL and installing a Custom Stock ROM with the same behaviour. Switched to CM11 and the phone reboots less times, but it still crashing and rebooting.
I've tried to to a logcat dump but it only shows a error with the light detector.
Should I try something more to detect where is the error?
Regards,
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!
Hi all!
Recently i rooted my S5 due to touchwiz being too slow to function properly. The first rom that I installed was the unofficial cyanogenmod 13. After my third reboot, the message com.android.phone has stopped appeared, and I my phone rebooted constantly. I had access to my phone for about 3 minutes before the message comes up again and It crashes. I then installed the mokee rom, and the same problem has occurred after a few reboots, with the same time interval for the message to pop up. I have tried solutions such as resetting the phone cache etc and even solutions offered by this thread, http://forum.xda-developers.com/show....php?t=2436229.
Could any one offer a solution that may help?
All responses are greatly appreciated!
Hello,
since one week I have the problem that my Galaxy S7 edge freezes and reboots many times a day. The problem starts on jesse n-rom v1.2. Now I flash via Odin the original 6.0.1 but it doesn t help. Also in TWRP the phone freezes sometimes.
Can anyone help me?
Beta firmware, Beta ROM, this is likely to happen. What do you expect? That's what can happen unfortunately. What exactly happened when you tried to go back to MM?
And please don't double post - xda rules.
After flashing to MM the system nedds four times to reboot and after I enter my sim pin the screen freezes again and the system reboots. Sometimes i have a bit more time until the screen freezes againe. If the screen freezes i can See sometimes a streak with different colours.
Hello. I have A Samsung S7 SM-G930A. I was using smartview to cast to my laptop and it overheated the phone and completely drained the battery. I don’t know if that is the cause of my problem but I’m just mentioning it because my problem started around the time I did that. The phone now overheats several times a day. It freezes for like 10 seconds then starts a boot loop. It could take up to an hour to finally come on again often with my intervention to force restarts. During usage, simple actions like switching data on and off, incoming calls, switching apps or simply responding to an SMS leads to a freeze then boot loop. When plugged in during this state it rather boots into recovery mode. I have the latest version of the patched Odin so before suggesting answers here’s what I’ve already done. I have flashed variations of firmware from the trusted sources (sammobile, updato, etc), I have done NAND erase, I have flashed PIT, I have flashed to G930U and back to G930A, I have done numerous factory resets and cache partition wipes, I have updated all apps (samsung and google apps included). Most of the time flashing only solved the problem for like 2 hours and it was back to the boot loops. Could this be a battery issue? The phone has not fallen or been exposed to the sun for long. It’s always with me indoors. I have tried everything I can think of. I will appreciate your help on concluding if the phone is dead for good. Thank you and sorry for the long question.