Database Users

[Q] Please help - S4 Keeps Rebooting - VIDEO

Hello All
My Samsung Galaxy S4 (GT-I9505) keeps on freezing then rebooting in an unusual way.
The problem is intermittent, it would constantly happen in certain periods and happen less frequently in other periods. At the moment, i can beerly use my phone for 1 minute before it does it again and again. And in this minute apps are just crashing. I get the pop-up messages of applications crashing. I tap ok only for the same message to instantly reappear.
Unfortunately, the process com.android.systemui has stopped
Unfortunately the process com.google.process.gapps has stopped
The issue would happen when the phone is in sleep mode (screen turned off), while im using it, in safe mode or even when its rebooting or on the splash screen.
I am using the original battery and charger that came with the phone and never flashed or rooted my phone. I have however had to flash it couple of months ago after it bricked all by itself. I used one of the firmwares from www.samsung-updates.com
See this video to understand exactly what is happening
https://drive.google.com/file/d/0B4l5hw87RbUXeUMzUkp5ZFZVMHM/view?usp=sharing
Please give me ideas/suggestions of what to do

omaral92 said:
Hello All
My Samsung Galaxy S4 (GT-I9505) keeps on freezing then rebooting in an unusual way.
The problem is intermittent, it would constantly happen in certain periods and happen less frequently in other periods. At the moment, i can beerly use my phone for 1 minute before it does it again and again. And in this minute apps are just crashing. I get the pop-up messages of applications crashing. I tap ok only for the same message to instantly reappear.
Unfortunately, the process com.android.systemui has stopped
Unfortunately the process com.google.process.gapps has stopped
The issue would happen when the phone is in sleep mode (screen turned off), while im using it, in safe mode or even when its rebooting or on the splash screen.
I am using the original battery and charger that came with the phone and never flashed or rooted my phone. I have however had to flash it couple of months ago after it bricked all by itself. I used one of the firmwares from www.samsung-updates.com
See this video to understand exactly what is happening
https://drive.google.com/file/d/0B4l5hw87RbUXeUMzUkp5ZFZVMHM/view?usp=sharing
Please give me ideas/suggestions of what to do
Click to expand...
Click to collapse
Have you tried to do a factory reset?

iJo09 said:
Have you tried to do a factory reset?
Click to expand...
Click to collapse
Yes I did a factory reset and wiped the cache

omaral92 said:
Hello All
My Samsung Galaxy S4 (GT-I9505) keeps on freezing then rebooting in an unusual way.
The problem is intermittent, it would constantly happen in certain periods and happen less frequently in other periods. At the moment, i can beerly use my phone for 1 minute before it does it again and again. And in this minute apps are just crashing. I get the pop-up messages of applications crashing. I tap ok only for the same message to instantly reappear.
Unfortunately, the process com.android.systemui has stopped
Unfortunately the process com.google.process.gapps has stopped
The issue would happen when the phone is in sleep mode (screen turned off), while im using it, in safe mode or even when its rebooting or on the splash screen.
I am using the original battery and charger that came with the phone and never flashed or rooted my phone. I have however had to flash it couple of months ago after it bricked all by itself. I used one of the firmwares from www.samsung-updates.com
See this video to understand exactly what is happening
https://drive.google.com/file/d/0B4l5hw87RbUXeUMzUkp5ZFZVMHM/view?usp=sharing
Please give me ideas/suggestions of what to do
Click to expand...
Click to collapse
1. It seems you recovered one image of one backup with the recovery.
2. SOLUTION: Reflash the firmware through ODIN. The latest for your phone is this one: HERE.

omaral92 said:
Yes I did a factory reset and wiped the cache
Click to expand...
Click to collapse
Try to flash firmware package with the latest version of ODIN and Sammy drivers, also use the original cable that came with the phone. Often, cables that aren't Samsung genuine fail to flash firmware.
If this doesn't solve your problem, then you might try a firmware reflash with PIT file. If nothing works, your processor (or motherboard) it's likely fried. Take it to a service centre

Joku1981 said:
1. It seems you recovered one image of one backup with the recovery.
2. SOLUTION: Reflash the firmware through ODIN. The latest for your phone is this one: HERE.
Click to expand...
Click to collapse
I have reflashed it using the firmware provided in the link but it is still playing up. any other suggestions?

[Q] Reboots after Lollipop

Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.

I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.

After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.

Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.

I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin

I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.

ehh not all have been closed

What is the root exploit for Verizon Note 3 with 5.0?

recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use

I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.

I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.

VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.

I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.

Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1

[N910F]Random reboots (links to logs included)

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!

SM-G900A Freezes then restart or crash repeatedly

Hello, my galaxy started to freeze and crash 2 months ago. At first i didn't mind it because it just happens once in a while. But 3 weeks ago, the freeze and crash became more frequent up to a point that even though i'm not doing anything to the phone, it just freeze then restarts. I researched the web and found some solutions, first i've tried to reset to factory settings. i used the wipe data/factory reset in recovery mode. it said the reset is successful then i've restarted the phone and i just loops on the samsung black screen or just crashes during the welcome screen. Then i tried to reinstall the firmware using odin. first i used the 4.4.4 tar (from this forum), the odin said the flash is okay, but when the phone starts up, it just loops on the samsung black screen or just crashes during the welcome screen. so i tried using the downgrade to 4.4.2 tar (from this forum), after successfully flashing it, my phone started to boot. but after i completed the first time process and i'm updating/downloading apps, it started to freeze and crash again, this became a frequent thing again. it just freeze and crashes anytime. i've tried reflashing the 4.4.2 again using a different cord and port, but the same thing still happens. Do you guys know if there is still some way to solve this?
Note: I've got this phone from my father when i visited him in the USA (last June 2015), then when i went home (in the Philippines), i didn't unlock the phone so i it didn't have any sim card since then. is this a factor in the phone's behavior?
Thank you

Up.. hopes someone can help me with this
Update: I've tried using another battery and the situation is still the same.

Reocurring Boot Loops, Hardware?

Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!