Anybody on stock rom updated to AT&T's D80010o try restarting their phones yet? After the update my in call volume keeps reverting back to 90% every time I reboot the phone. It's like the setting won't save. I lower it because initially after the update it's like 90%, then when I reboot the phone it goes back up to 90%. Anybody seen this bug?
Hello everyone
I am having a strange problem with my phone.
The problem started a few days after the Ota update to 4.4.2 NC1 (may not be related)
The sound on the phone the speakers the touch tones the ear phones everything just used to go off randomly. Initially a reboot used to fix it. But progressively it got worse and phone would get stuck at att logo.
Initially tried a master reset and it resolved the issue temporarily a few days after it was back to its old tricks.
Then I tried to refres stock with Odin and the behavior was same, works fine for a day or two and then no sound and then boot loops.
Yesterday I tried to install hyper drive room with safestrap. It has lost sound couple of times, but till now reboot has fixed it.
Could you guys please help me on this as I have spent couple of months on it and now it's messing with me
Thanks in advance for your help
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
Hey, so when ever I make a call (I can dial but when I hit call) my phone will lock up, then the screen goes black, shuts off and turns back on. It happens when I answer or reject incoming calls as well. This only started happening when I updated my S5 to lolipop, I unrooted, and when back to the S5 stock kitkat ROM, full factory reset before going to lolipop, phone calls worked fine rooted and unrooted in KitKat, so it makes me think it's a lolipop issue. Since running into the problem I've tried, going back to kitkat and upgrading again, factory resetting from within lolipop, wiped caches, and such, and I just can't get it to work. Any ideas would be greatly appreciated. It can't be hardware related since calls work fine on kitkat right?
Hello guys!
I'm facing a veeery weird issue with my ZB602KL.
I've left it charging overnight and when I woke up, it was turned off with 87% of battery.
Turned it on again without any troubles but now the phone just won't stay turned on when idle.
The only way I can leave it blocked without turning itself off is letting some background app running, such as a music player. Otherwise, the phone will go off 30 seconds after I press the lock button.
It doesn't turn off when screen is on or using any apps (no matter how long)... but as soon as I lock it, without anything running on the background, it goes off. :crying:
Any thoughts? Stock ROM, no root, tried factory reset, wiping cache, upgrading the firmwire again and nothing seems to work.
Thank you all for your attention!! :fingers-crossed::fingers-crossed::good::good:
Marcelo
Morning guys!
Yesterday I spent the phone battery until It reached 0% and left It charging It to 100% without interruptions... But It didn't work as well.
I'm definetely out of ideas
Downgrade the firmware if the problem started after ota update...(you need unlocked bootloader and root for that)..else take it to service center..
this problem happening to me
i've try factory reset and upgrade to android 10 but both still causing this sudden death
anyone has overcome this?
i'm about trying custom rom but still hoping to stick with stock rom
pranavkpr said:
Downgrade the firmware if the problem started after ota update...(you need unlocked bootloader and root for that)..else take it to service center..
Click to expand...
Click to collapse
this happen long after ota update and sadly, i've passed my warranty period