Last night I received the notification that there was a security update for my phone. I plugged it into the charger and let it apply the update. Something must have gone wrong during the update as the phone is unusable. It is not bricked as it will boot and get to the lock screen. However, once you go to swipe up I get a series of "Unfortunately, the process X has stopped." messages. Most of them are for com.motorola.process.system or NFC process. Occasionally, I will get one for GApps. It never allows me to get to the home screen even with a reboot.
Any ideas as to what I can do? The phone is stock, not rooted or unlocked.
Thanks.
Related
Okay, I have been having a serious issue with my D3 lately. One time, my phone just randomly rebooted, and then it would get stuck at the red "Droid Eye" screen, where it would be laggy and such after a while. Eventually the screen would time out in like 2 minutes. After it turned off, I could not get it to turn back on. Basically dead, except I could still get notifications and even a phone call. But I could not act on any of them. it's like the phone's heart is still beating, but I can't turn the screen on. I pull the battery and reboot and it does it again. SOMETIMES if I keep touching the red eye screen I can get to get to the lock screen, but the wallpaper won't load and it's basically frozen. I even tried booting into safe mode and that didn't help. I took it to Verizon, they said they've a couple other people with a similar issue on the forums. They did a factory reset, and that has been the only solution to the issue. I have had it 3 times now, and this time I'm sticking with the Blur launcher and keeping only the essential apps installed. I'm assuming this is a software issue, and I'm currently trying to figure out if it is related to a certain app that was installed. Hoping they will fix this with an update! ANYBODY ELSE HAVING THIS ISSUE? if so, any leads on another fix or what it could be?
sounds like a software issue. a factory reset doesn't do anything other than change the software.
I had a similar issue on my droid 1. it was rooted and when I installed a gingerbread from I forgot who, it got stuck at the eye, kept rebooting, and occasionally, i'd get calls and it still wouldn't work. I look forward to root.
out of curiousity, did you have to take it to the store to factory reset or is there an option for it in the bootloader(I know its locked but I have no idea to what degree)
The first time I took it to the store they did it for me, but yeah there's an option in the bootloader. Just took my back to Verizon cuz this was the 4th time it's done it, they're sending me a new one! It's okay, cuz my nice screen open 'click' sound was gone on the keyboard lol
Anyone else have an issue with this phone following the update that just rolled out recently? Since my wife updated today, every time she unlocks the phone it does not respond to any screen presses, from lock screen or from main screen when lock screen is disabled.
Phone was never rooted, so i know that's not the problem. as it sits right now, we did a factory reset (at Verizon) and it did not fix it. Any help would be appreciated.
dudeicles said:
Anyone else have an issue with this phone following the update that just rolled out recently? Since my wife updated today, every time she unlocks the phone it does not respond to any screen presses, from lock screen or from main screen when lock screen is disabled.
Phone was never rooted, so i know that's not the problem. as it sits right now, we did a factory reset (at Verizon) and it did not fix it. Any help would be appreciated.
Click to expand...
Click to collapse
You could try reverting it back using the guide here to see if it rules out your upgrade. I've been running 24A a couple days and countless others have upgraded, haven't heard this complaint yet.
I have a rooted LG G4 (H815) and T-Mobile. About a week ago, Bluetooth stopped working properly. It will turn on for about 6-8 seconds, then shut off again. I've tried power cycling, removing the battery, and booting into Safe Mode. No joy.
Additionally, when I try using T-Mobile's "FamilyWhere" app to locate other phones on my plan (my daughter tends to misplace hers), I've started getting a big blue Error box that says, "Unauthorized: MSISDN failure" (whatever that is).
The phone is running Android 5.1. I thought it came with 4.4, though I'm not 100% sure. I'm wondering if an OTA update got pushed to the phone in the last week or so and screwed something up.
Can anyone help? Thanks.
Burlisoft said:
I have a rooted LG G4 (H815) and T-Mobile. About a week ago, Bluetooth stopped working properly. It will turn on for about 6-8 seconds, then shut off again. I've tried power cycling, removing the battery, and booting into Safe Mode. No joy.
Additionally, when I try using T-Mobile's "FamilyWhere" app to locate other phones on my plan (my daughter tends to misplace hers), I've started getting a big blue Error box that says, "Unauthorized: MSISDN failure" (whatever that is).
The phone is running Android 5.1. I thought it came with 4.4, though I'm not 100% sure. I'm wondering if an OTA update got pushed to the phone in the last week or so and screwed something up.
Can anyone help? Thanks.
Click to expand...
Click to collapse
UPDATE: I uninstalled FamilyWhere and re-installed, then rebooted the phone and the MSISDN message is gone and the app is working correctly. Bluetooth still fails, however.
I just updated my s6 with the marshmallow update. I keep getting this notification: "Security notice. Unauthorized actions have been detected. Restart your phone" I thought maybe it was because I turned off permissions for a lot of the stock apps like calendar, email, etc since I use other apps for those. But I've restarted 4 times over 6 days and the notice came up again today. How in the heck do I get it to go away? It is driving me nuts. From searching for info, it seems this has happened on other galaxies on other carriers with previous updates and getting a new update was the only thing to fix. Am I just SOL?
Anyone having this issue after updating to Marshmallow? I even just did a factory reset and didn't restore anything and it came up with in 10 minutes of using the phone again.
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Were you rooted ?
reboot took longer than normal, should have left it
factory reset will clear up everything lol
prgopala said:
Were you rooted ?
Click to expand...
Click to collapse
I am not rooted. Gave up my rooting back when it made Google pay and Pokemon Go a complete ***** to use, even with magisk. So I've left this stock out of the box.
lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Hey got the same issue as you. Either it's stuck on a black screen (adb works), either it hangs on Applying update when starting the phone. Can't seem to get past this crap... I'm trying with a patched magisk image btw, not sure if it's the issue, I already applied the magisk adb commande in order to remove the magisk modules but to no avail.