I've just replaced my screen and was stuck on infinite loop. It turned out to be the fingerprint sensor, in order to bypass the infinite loop, I disconnected the sensor and reconnected it.
So now that I managed to get in, I headed to the security settings, deleted all previous fingerprints. However, I keep receiving "Enrollment was not completed. Fingerprint registration error, please try again."
Update:
so I've found 2 threads on xda, that deals with that error:
https://forum.xda-developers.com/t/guide-fix-persist-img-loss-of-finger-print-sensor.4125909/
https://forum.xda-developers.com/t/...y-to-calibrate-the-fp-sensor-via-808.4217197/
However, now fingerprint is not showing at all! wondering if someone has any clue how to solve this
Update 2:
Update:
I wanted to see what would happen if I updated Oxygen to the latest update, turned out it brings back the fingerprint, however it seems that I've lost access to the vendor folder (unable to browse the directory under "/mnt/vendor"
Related
Since it locked up, upon restart it can't get past the eLocity boot animation and after a minute it will restart itself and begin the cycle again. I tried the blank screen fix for corrupted firmware and after going through with it I am right back to where i started.
Another thing was also a bit weird while trying to get a bluetooth connection going with my pc I noticed the name of the tablet was a7-040. The only thing I did prior was getting access to the android app store. Somehow my a7-004 that was apparently identifying itself as a7-040 locked up and keeps restarting.
eLocity customer service came through!
after a short back and for with 2 solutions that didn't quite work i got instructions for an A7+ restore that reverts EVERYTHING to factory.
everything is on this page of theirs. if you follow the instructions on the pdf it will have a link that doesn't work. that link is for this page and the zip file on it.
elocitynow.com/prod_a7-plus_recovery.shtml
Hi There,
Shortly after updating my Nexus 4 to 4.2.2 OTA today the screen went blank and I've been unable to get it to function correctly again.
The phone is still showing some signs of life, I am getting notification LEDs and I am unable to unlock the phone with facial recognition even though the screen remains blank - I can tell from the vibration and the LED stopping that it has unlocked. Pressing the power button to lock it starts the notification LED again.
I have tried a hard boot (Volume Down + Power) and the screen did come on to display the google logo followed by the X but as soon as they had been shown it returned to a blank screen.
Does anybody have any ideas of what this could be or how to solve it or should I contact Google in regards to this issue?
Thanks in advance for any help
seems like the OTA update has corrupted somewhere. You should reboot into bootloader and use fastboot to flash the stock 4.2.2
Is there anything else worth trying before doing that? I wouldn't have a clue where to start as this is my first android device
Ok so I got it working but did lose all my data. If anyone else comes across this issue I had to boot into recovery mode and do a full wipe/factory reset. The first time i did this the phone started up with no problems but during configuration when I entered my Google account the blank screen strangely returned so I again did a full wipe in recovery mode, skipped the 'set-up google account' step and then entered it manually later in settings once the device had started up.
No idea what caused this and if its a bug in 4.2.2 or an issue with some settings in my google account that are being backed up and restored to the phone but either way I had no problems until 4.2.2 update installed and the issue occuring even after first data wipe rules out any third party apps being the cause.
I had a similar problem after updaing that the screen stay blank and it wo'nt unlock
As soon as i disable the bluetooth the problem solved.
It's happened when i paired it with my pc
Hi guys,
I have a strange issue with my phone. After the upgrade to 7.0 my fingerprint sensor has stopped working. When i try try to access it it says that an error has occured and prompts me to restart my device. The weird thing about it is that it is very warm to the touch every time my screen is on. After a reset to factory settings i see that the sensor is getting warm after the security initialisation on the first setup. I have two guesses:
- it is a hardware issue
- the sensor is constantly being used by some background service and gets into error.
I tried to downgrade to 6.0.1 but odin keeps crashing at cache.img .
Any ideeas on what to do ?
Thanks !
Probably a hardware issue mate, I'd get it checked out
Hi All,
I installed DP2 today via OTA (fully stock, locked bootloader) on restart I have to enter my password to boot/unecrypt. When the phone is started I have to type in the password as fingerprint won't work after restarting.... at this point the screen goes blank and drops me back to the lock screen. I know it is the correct password as there is no error and it is the same password I booted with.
Is anyone else experiencing this? I think it will be a factory reset for me! (
Thanks Andi
I reset my phone and am very pleased that the google backup is so much more fully featured these days.
I think that the issue may have been caused by my companies MDM software as there was an alert / notification I could not read/action.
All working nicely on dp2 now
Hello,
So today I woke up today to find my device stuck in the google text bootloop, did a quick search on how to fix it and found this guide : https://www.xda-developers.com/nexus-6p-bootloop-fix/
I did everything and I guess it worked correctly, except the fact that now my bootloader being unlocked I stumble upon the "your device can't be checked for corruption" error, and so I'm stuck on another different bootloop. Locking the bootloader fixes the corruption error but I'm back to my previous google bootloop (even if I flashed the image that was in the guide).
So whether the bootloader is locked or not I'm stuck on one of the two bootloops (by the way I tried flashing a factory image after that but didn't fix the google loop).
Is there any way I can fix it?
Thanks!
Keagghan said:
Hello,
So today I woke up today to find my device stuck in the google text bootloop, did a quick search on how to fix it and found this guide : https://www.xda-developers.com/nexus-6p-bootloop-fix/
I did everything and I guess it worked correctly, except the fact that now my bootloader being unlocked I stumble upon the "your device can't be checked for corruption" error, and so I'm stuck on another different bootloop. Locking the bootloader fixes the corruption error but I'm back to my previous google bootloop (even if I flashed the image that was in the guide).
So whether the bootloader is locked or not I'm stuck on one of the two bootloops (by the way I tried flashing a factory image after that but didn't fix the google loop).
Is there any way I can fix it?
Thanks!
Click to expand...
Click to collapse
The corruption error you get from unlocked bootloader is nothing to worry about. It should resume after the message is displayed. Unless it pauses then you can resume by pressing the power button .
Exodusche said:
The corruption error you get from unlocked bootloader is nothing to worry about. It should resume after the message is displayed. Unless it pauses then you can resume by pressing the power button .
Click to expand...
Click to collapse
Well the problem is just that it goes into a loop, this message into google text into this message into google text etc
I'm still stuck in a bootloop except that instead of only having google text switching into black screen it's now google text switching into corruption error :/
Keagghan said:
Well the problem is just that it goes into a loop, this message into google text into this message into google text etc
I'm still stuck in a bootloop except that instead of only having google text switching into black screen it's now google text switching into corruption error :/
Click to expand...
Click to collapse
You will just have to try the bootloop threads an hopefully something will get it working. However even if you do phone will be slower maybe time for upgrade.