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?
Related
I've been using the google edition rom on safestrap for weeks now, and today I turned on airplane mode, and then when I turned it back off the phone says I have no signal. I've restarted multiple times, went back to the stock ROM, restored from and couple day old backup and even re set up the google edition rom, still no signal. Anyone have anything similar, or help they could give?
Edit: I called an emergency number to see if it's still at least physically functional and that works, so there's definitely no hardware damage.
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
hi guys i have an issue with my device (i9500) since i had a bad efs partition which i successfully restored from a backup.
The device works perfectly, but as soon as you lock it, and wait a few seconds, you can't unlock it anymore. Screen stays black, and the only way to get it started again is by removing the battery. Then it keeps on working perfectly, apps, games, everything is fine, as long as you don't lock it (by pressing powerbutton or auto lock)
Either then it crashes or restarts.
Things i've done already:
- Soft reset
- Hard reset + cache wiped
- tried many different roms
- fresh stock rom installed with Odin.
Problem still persists.
I've recently discovered that I don't have this problem on miui 7 running on 4.4 2. But as soon as I install flyme which is on 5.0.1 or any other lollipop rom or even stock lollipop then the phone either crashes while I'm using it or freezes at lockscreen and I can't unlock it. Please help guys cause I really wanna get back to my flyme rom on lollipop.
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
abenco said:
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
Click to expand...
Click to collapse
Oddly enough, the OTA update is the only thing that worked on mine.
Gizmoe said:
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
Click to expand...
Click to collapse
It really is weird. I'm back on MM now and its working fine. I guess I stay here until the next build comes up and then I'll see what happens.
Same issue here. stock rom, received OTA and now I have the excess battery use, and thanks to the post boss above, the same proximity sensor issue. Phone goes black in middle of call with no way to get back to the screen to hang up, change to speakerphone, etc. It stays black sometimes, even after the other party hangs up, requiring me to reboot. PITA.
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
You have to unlock the bootloader but thats pretty much it. After you flash you can relock it if you want.
I could fix that problem by removing the screen protector.
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
No not rooting. You have to unlock the bootloader and then fastboot flash a factory image. It's best to leave the bootloader unlocked too, unless you are going to leave it stock and never tinker with it again. But if you ever need to flash an image again or use twrp or anything fastboot related you will need an unlocked bootloader.
I have the same problem with my phone. Android 7.1 seems to fix this.
Enviado de meu Nexus 6P usando Tapatalk
I had the same problem, but fixed it by installing a sensor reset app from Play Store, then uninstalled the app.
Just talked to Huawei tech support. My 6P wasn't rotating the screen and whenever I was in a call, wouldn't dim the screen. Such a small feature but we all take it for granted. Anyway, she told me to enter recovery (Power+Volume Up) and "Wipe Cache Partition" rebooted and running like a champ. ?
I recently updated my phone to Nougat, about two days ago and was working fine, but suddenly the phone calls started to malfunction. I can't hear anything, even when it's calling another phone. Is someone experiencing the same with the same phone or similar models?
Hi, backup all of your data and perform a factory reset from settings. DO NOT perform a wipe from recovery as this will turn on FRP lock. I had the same problem after updating to nougat i couldn't hear anything when calling and also couldn't receive calls. My model is also J510MN. Factory reset seems to have solved the problem.