Database Users

[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-N910G Stock - Contently freezing, restarting to download mode and data lose

Hey all,
I found few similar threads, but none of the solutions worked for me. So here's my situation
Problem : N910G Singapore Starhub, used for more than 1 and half years without major issues. Suddenly started to randomly freeze and then restart.
Got worse very quickly. Started to get freezed at Samsung logo. Most of the time had to remove the battery to re-try booting.
What I've done so far:
Cache cleared -> Didn't work
Factory reset -> Was ok with less lag (Freezing) for sometime, then same again
Installed TWRP. Flashed PIT file. Following an XDA post, flashed Samsung stock Android 6 released to India -> Was ok for couple days, was better than 5.1 in terms of responsiveness and battery life. After few days, again freeze. restart
Flashed with stock 5.1 released for the correct region. -> freezing, restarts. Wifi passwords are not getting saved (Have to re-enter upon restart). Restarts end up in download mode. very rarely passes the Samsung logo
Rooted and tried to change build prop ro.securestorage.support (or something similar) and see whether passwords are getting saved -> Still passwords are not getting saved. /efs is accessible.
Now the device never boots properly. Some apps are missing after restarts. Always ends up in download mode. Recovery is working fine though.
You guys have any idea what else I should try before throwing this away?
Thanks in advance.

cyclo.sl said:
Hey all,
I found few similar threads, but none of the solutions worked for me. So here's my situation
Problem : N910G Singapore Starhub, used for more than 1 and half years without major issues. Suddenly started to randomly freeze and then restart.
Got worse very quickly. Started to get freezed at Samsung logo. Most of the time had to remove the battery to re-try booting.
What I've done so far:
Cache cleared -> Didn't work
Factory reset -> Was ok with less lag (Freezing) for sometime, then same again
Installed TWRP. Flashed PIT file. Following an XDA post, flashed Samsung stock Android 6 released to India -> Was ok for couple days, was better than 5.1 in terms of responsiveness and battery life. After few days, again freeze. restart
Flashed with stock 5.1 released for the correct region. -> freezing, restarts. Wifi passwords are not getting saved (Have to re-enter upon restart). Restarts end up in download mode. very rarely passes the Samsung logo
Rooted and tried to change build prop ro.securestorage.support (or something similar) and see whether passwords are getting saved -> Still passwords are not getting saved. /efs is accessible.
Now the device never boots properly. Some apps are missing after restarts. Always ends up in download mode. Recovery is working fine though.
You guys have any idea what else I should try before throwing this away?
Thanks in advance.
Click to expand...
Click to collapse
If you know how, I'd use Odin to restore the factory image if you're running the factory software. Performing a hard reset is always the best way to go, however if you're still having problems then I'd download the latest firmware from Samsung's firmware site and then Odin.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button. *

Android.Ninja said:
If you know how, I'd use Odin to restore the factory image if you're running the factory software. Performing a hard reset is always the best way to go, however if you're still having problems then I'd download the latest firmware from Samsung's firmware site and then Odin.
Click to expand...
Click to collapse
Thanks for the reply Android Ninja. As the last resort, I did flash the correct stock firmware which I downloaded from Sammobile. But it didn't really fix the issue. So should I unroot and use Kies instead? Because I can't find a way to download the fireware from Samsung, if that's what u meant. thanks

lag, freeze, restart after 6.0.1

hey guys, today i bought a used NOTE 4 for my mother, and when i checked the version it was 6.0.1...so i wiped everything and restarted the phone to get the best performance....but the phone lags and freezes a lot, especially in the camera, and it keep restarting all the time....what should i do? should i try to flash another FW through ODIN?

You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.

ithehappy said:
You mean you used the Factory reset option? That's not a full wipe, just resetting stuffs. And yes, you know the answer, wipe everything from a custom recovery, then flash stock MM ROM (always latest) via Odin. Earlier versions did have a reboot problem though, and lags here and there, but that's expected, but the last release, PE1, has got rid of all those problems, its a very good release already, and I am sure upcoming releases will only make it better. There are no major bugs at all, I don't even find any minor bugs except the need for a separate app to clear default apps selection.
Best of luck.
Click to expand...
Click to collapse
the phone is stock, it has the stock recovery, and i have the PE1 version, the exact name is "MMB29M.N910FXXU1DPE1"...and still got a lot of lag, freeze and rebooting.....is there another version?
EDIT: ok, so i flashed another MM through odin ( first time it gave me a fail) and then done a factory reset, now it's so much better, maybe not as smooth as my S6 but really fast and smooth enough...thanks for the help
EDIT: today the phone started to shutdown completly....not reboot....and you need to press the power button 10 seconds to reboot it or turn it on...is there any advice?

Guys . Ib tead the whole thread over last few day had wake lovk runnimg last couple weeks. Lastnight used kies for reset and it crashed half way.
I then used odin 307 and went back to stock 501
It booted strarted to restore from google apps ect .
I allowed the 1st 601 update
All apps running aok no crashing freezing no wakelock .. its asking for another 601 update. Im gonna hold back
Hope this helps .. will post agian in gew days with any updates
Good luck !!

Just download and install Wake Lock from Google Play Store. I had the same problem and more. Once I installed Wake Lock (on a fresh install from Android 5 up to all the 6.0..1 builds) phone doesn't shut off or freeze. Most importantly no more Boot Loops..

N910F stock crash and bootloop after 6.0.1 update

Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!

Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?

Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake

nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?

tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update