I got a replacement Moto z4, and it appears that any time I try and set up my fingerprint, it gets to the exact same point, and then stops. The part halfway through setup where it says to start doing the sides of your finger.
I've factory reset three times, fully updated to the newest firmware (July), and can't seem to find out what's wrong.
Normally I'd chalk it up to the device, and swap it out again. But I already did that, and this is the second one in a row with the issue.
It does read the fingerprint the first half of setup, and then shows this error (see image).
Verizon variant, July update. (Also did it before updating).
Was it a one-to-one exchange? If not maybe you were given back the same (problematic) phone?
Did you try the fingerprint login before updating?
Is there a screen protector?
I guess the last resort is to try to do a rescue using the LMSA software and get a clean reinstall of the latest firmware.
Related
has anyone run across this issue when you set a specific time out, the screen dims after the specified time but does not lock, it stays on?
my phone was working just fine, stock not rooted, took the latest update and after that i've been having nothing but weird issues, the other day the notification area at the top was not working, i had to basically check every app, messages etc manually to see updates, had to factory reset the damn thing, now this screen issue, the phones is only 1 month old.
any input?
thanks
I'm having very weird issues with screen lock. I'm be on the phone and the device will randomly lock and not let me unlock it without restarting the phone.
The new update is when it all started. I don't want to do a factory reset, but it's looking like I might have to?
So I bought the S6, new, never been opened, sealed etc, let it charge the proceeded to turn it on. Then comes the welcome bit and startup, this is where it went tits up. Apparently everything stopped responding, google maps stopped responding, voice commands stopped responding, etc. Thought nothing of it, skipped through everything, got into home screen and then "Touchwiz has stopped responding". So naturally I though oh dear. Oh, it also started restarting on it's own randomly as well, I tried booting in safe mode, disabling things, that didn't work, sometimes it would even get in a bootloop, loop 3 times and then start.
I tried updating it, didn't work, tried flashing it with "G920FXXU3QOLD_G920FH3G3QOJ1_G920FXXU3QOJB_HOME", problems still persist. It's currently on 5.1.1, it wont update in settings, just starts downloading more than 1.2gb's of downloads then says "Software update has stopped responding".
Tried samsungs live chat, was awful, they didn't present any useful information.
I'm wondering if it's just 5.1.1 being awful, because when I boot to the system recovery menu thing where it has the blue screen with android logo, then has yellow exclamation mark, that doesn't reboot on it's own at all. Never reboots in download mode either. Phone is not rooted, knox hasn't been tripped or anything, so I'm left clueless. What do I do? Bought this phone, what, 4 days ago ish. Came here yesterday. My question is, if I flash it with idk, a 6.0.1 update in odin or something, will that fix the problems?
Hi,
It seems to me that you have a defective device, you can either try reflashing the stock firmware and then factory resetting, I believe that it really is a software issue, but as it's brand new (as you stated), you can return it to the store and get another one.
There are quite a few guides to flashing stock firmware back, hope you can do it .
All the best,
~Lord
Sent from my SM-G920I using Tapatalk
See this photo:
https://goo.gl/photos/Ns9nKJotNX7mZnhz6
It seems that the digit in the top right corner of notification stops updating, and always showing the old time.
It will only update if i try to switch the time format to 24h and switch back, and it stays there since then.
A reboot will fix it but the bug may appear randomly. So I may get the wrong time and be late...
Pixel XL using totally stock rom without root or unlock, build number NDE63X(manually updated through google's full ota link, i didn't recieve any ota update since bought with NDE63N)
Anyone has the same issue?
Same issue here this morning with my Pixel.
After an hour the time was up to date again.
Build number NDE63V
Haven't had this problem on the pixel yet, but used to get it once and a while on my Samsung phones. I always thought it had to do with the network feeding the phone the wrong information. After a while it would update and be back to normal
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be too basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Stoksie said:
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be to basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Click to expand...
Click to collapse
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Stoksie said:
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Click to expand...
Click to collapse
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Stoksie said:
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Click to expand...
Click to collapse
It could have been something in system that got changed during the update but the data from before the change is still there and conflicting with whatever changes were made. Some kind of saved system data that can only be wiped by factory reset or reflashing.
Sent from my SM-S903VL using Tapatalk
I did a factory reset, lost a lot of photos that had started being saved on the phone and not the sdcard after the upgrade to Marshmallow. Have had to accept that but unfortunately the bizarre behavior did not stop and it continues on and off, sometimes so bad that I cannot dial a number on it and other times it happens but I can get in between the action and dial or send a text etc. I have gradually been stopping things like notifications from google apps and traffic reports from google maps (this may have had a good effect) and anything that might be doing constant checks. It seems to have quietened down over the last day or so and I even got to play a game on it but the next option is to send it away to an engineer. I just thought that I would let you know the outcome of the factory reset.
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.