I searched for hours and only found incomplete bits and pieces, so I hope you guys can help me.
I flashed my G920F with FrankensteinS6 (a custom rom with the latest stock kernel) and everything works fine, but I can't get the fingerprint sensor to work, it always prompts me to restart the device.
I found a few posts stating that I have to flash the correct bootloader in order to get fingerprints to work again.
I just flashed the BL/AP/CP and CSC of the latest stock firmware. I tried to activate the fingerprint lock on the stock os to eliminate the custom ROM as a factor. However, it didn't work: I get the exact same error. Even after wiping the cache and performing a factory reset, it still shows that error. Also, the fingerprint sensors shows "Version: Null" in the *#0#* menu. Any ideas?
Strel0ka said:
I searched for hours and only found incomplete bits and pieces, so I hope you guys can help me.
I flashed my G920F with FrankensteinS6 (a custom rom with the latest stock kernel) and everything works fine, but I can't get the fingerprint sensor to work, it always prompts me to restart the device.
I found a few posts stating that I have to flash the correct bootloader in order to get fingerprints to work again.
I just flashed the BL/AP/CP and CSC of the latest stock firmware. I tried to activate the fingerprint lock on the stock os to eliminate the custom ROM as a factor. However, it didn't work: I get the exact same error. Even after wiping the cache and performing a factory reset, it still shows that error. Also, the fingerprint sensors shows "Version: Null" in the *#0#* menu. Any ideas?
Click to expand...
Click to collapse
There's a zip floating around that flashes the stuff for the fingerprint sensor
Related
Update: Sorry about the title, it should be "[Q] All Nexus 5 SENSORS mysteriously non-functional?"
Well, I usually don't post under Q&A, Help & Troubleshooting unless I'm stumped...
I was flashing an OMNI-hammerhead update a couple days ago on my N5 and noticed something funny, the orientation sensor on my phone didn't seem to work, and I couldn't tilt my phone anymore. I quickly googled the problem expecting somebody with a similar problem but I haven't found one yet... I figured it was just a bad build, so I opened up TWRP and reflashed the zip for my original working OMNI install. The orientation sensor still didn't work... So I booted back into recovery and did a systen-data-cache-dalvik wipe and reflashed OMNI. Still, the sensor wouldn't work. I installed Android Sensor Box and opened it up and it said the only available sensor was the sound sensor. Furthermore, when I was taking a look through the sysfs none of the usual device firmware directories were showing up. `lsmod` seems to show that all of the kernel modules are loaded for my phone, and re-flashing my phone to stock android didn't help either. Finally, today I decided to back up my /data/media folder and reflash everything, including the radio and bootloader using the Unified Android Toolkit. Still, after all of that, the only sensor that shows up is the sound sensor. No compass, no accelerometer, nothing. What should I do? What should I try?
joshumax said:
Update: Sorry about the title, it should be "[Q] All Nexus 5 SENSORS mysteriously non-functional?"
Well, I usually don't post under Q&A, Help & Troubleshooting unless I'm stumped...
I was flashing an OMNI-hammerhead update a couple days ago on my N5 and noticed something funny, the orientation sensor on my phone didn't seem to work, and I couldn't tilt my phone anymore. I quickly googled the problem expecting somebody with a similar problem but I haven't found one yet... I figured it was just a bad build, so I opened up TWRP and reflashed the zip for my original working OMNI install. The orientation sensor still didn't work... So I booted back into recovery and did a systen-data-cache-dalvik wipe and reflashed OMNI. Still, the sensor wouldn't work. I installed Android Sensor Box and opened it up and it said the only available sensor was the sound sensor. Furthermore, when I was taking a look through the sysfs none of the usual device firmware directories were showing up. `lsmod` seems to show that all of the kernel modules are loaded for my phone, and re-flashing my phone to stock android didn't help either. Finally, today I decided to back up my /data/media folder and reflash everything, including the radio and bootloader using the Unified Android Toolkit. Still, after all of that, the only sensor that shows up is the sound sensor. No compass, no accelerometer, nothing. What should I do? What should I try?
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915
wolfu11 said:
Here you go.
http://forum.xda-developers.com/google-nexus-5/general/sensors-fix-nexus-5-t2704915
Click to expand...
Click to collapse
Hmm, it was really that simple?
Huh, who'da thought...
Thanks!
Hi all,
Got my OnePlus One last week. It's a Chinese version that comes with ColorOS. I immediately tried to flash CM11 nightly onto it after I checked the phone is working.
For some reason I thought I could flash CM11 directly, and so the first thing I did was installing TWRP 2.8.0.1. Then, I copied CM11 zip in to /sdcard , booted to TWRP recovery, wiped all partitions (including System) and then flashed CM11. In hindsight, I believe it was the wrong way to get CM11. I could have wiped something really important (sensors drivers?) when wiping System.
Initially, CM11 nightly seemed to work OK. Then I noticed the Auto-Rotate is not working at all. I installed CPU-Z and *gasp*, there's not a single sensor listed in the CPU-Z Sensors tab!
I spent hours today trying various methods (flash CM11S, flash ColorOS, flash /persist, /reserve4 partitions). However, the sensors are still dead! Besides auto-rotate, I think auto-brightness, proximity sensors are all dead.
Is there any way to get the sensors working again? Your help is much appreciated!
Try http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 and see if your sensors work after restoring to factory images.
Someone else said only twrp 2.7 is supported for opo, another guy had similar device breaking problems with 2.8.
I'm using TWRP 2.8.0.1 and have no problems. TWRP 2.8 had problems, but 2.8.0.1 resolved them.
Thanks a lot for the quick reply, zephiK! I've run flash-all.sh and I'm in CM11S now.
CPU-Z no longer shows an empty Sensors list! however, only the following 4 sensors have readings:
AK8963 Magnetometer
AK8963 Magnetometer Uncalibrated
TMG-3993 IR_Gesture & Proximity
TMG-3993 Ambient
No readings for the rest...
Does auto rotate work? I'm not really sure how your sensors disappeared in the first place, its very odd.
/system is wiped on every ROM flash anyway so that's not the reason. Glad it's working better at least. Any more issues with the sensors other then some not showing?
Nope, the auto-rotate is still not working.
I've just rebooted CM11S, and... the Sensors tab in CPU-Z became empty again! This is very strange indeed...
I think t is a kernel problem,
Maybe you van flash the original boot.img
Rebooted again. The list of sensors are showing in CPU-Z again, and the same 4 lines have readings (AK8963 Magnetometer, TMG-3993). Still no auto-rotate.
My gut feeling is that there is a low level corruption in one of the "special" partitions. By special I mean the ones that are there but not included in any of the ROMs or factory images. Unfortunately, I don't have a NANDROID backup to restore from (Huge mistake on my part).
Is there a way to download an NANDROID image containing those special partitions?
@gurby1, I thought about kernel problem too, but I've tried flashing many ROMs and kernels:
CM11S 33R
CM11 Nightly 20140296
Franco Kernel r20
ColorOS 2.0 beta
ColorOS 1.2
and the results were the same - broken auto-rotate.
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
DecemberNexus said:
Bump. I'm still looking for a full partitions dump of the OPO.
Something similiar to this one for LG G3: http://forum.xda-developers.com/showthread.php?t=2766437
Click to expand...
Click to collapse
Hello,
Did you find a solution ? I have exactly the same issue as you. It even worst, I don't see any sensor on my device. I have installed many ROMs without any success. I hope it is not a HW problem
Thanks.
Guys.. I also have this issue..
Glad if there any solution on this...
Same problem
Guys any solution yet? I'm getting annoyed by this so much.. Please post here if u have found any solutions. Thx.
I also have the sensor problem which is all sensor is "not supported" in antutu and empty in CPU-Z sensor tab. I fixed it by flashing the persist.img from this thread http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Dzhedaj said:
I know it's a very old topic, but was someone able to recover the non working sensors? It's hard to believe it's a hardware issue, as the proximity sensor should be completely separate from the e.g. accelerometer...
Tried flashing all .bin files via fastboot with no luck...
Click to expand...
Click to collapse
Have you try flash the persist.img?
TheDynamiteGuy said:
Have you try flash the persist.img?
Click to expand...
Click to collapse
Tried flashing everything, modems, persist.img, etc. Nothing helps, so seems something is toast in the hardware...
Hey guys, I recently flashed the Stock ROM PI3. The flash was successful, but I soon found out I have lost a lot of functionality in my phone. My sensors stopped working. My phone doesn't count steps anymore, can't auto-rotate, IR Blaster doesn't work, Heart rate sensor doesn't work, waving your hand over the front screen doesn't wake the screen anymore. The only sensor that seems to work is the fingerprint sensor. I have tried wiping data/cache and reflashing the stock ROM, at the link mentioned earlier, but nothing has solved this issue. If anyone has any idea what is going on, that would be very helpful!
Try to download the firmware again and then try flash it. Also make sure you have the latest version of odin
Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.
I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.
Anyone else experience this? It happened after upgrading magisk, then reflashing dtbo and re patching with an earlier version of magisk.
Fingerprint gestures still works inside the OS. And when I try to register a new fingerprint, it reads my finger up until the last "read" then throws an error that the fingerprint registration has failed.
I actually have had this error, wifi also stopped working. It's something to do with Flash Kernel and the current way we have to be unlock. If you flash a stock kernel or the modded one with safteynet pass it should go back to normal.
Thanks for the reply, I wiped and started over before I saw your reply. Next time I'll try the OEM kernel first!
Anyone still having the issues with Fingerprint Hardware and Wifi after updating Magisk and flashing a new kernel? I updated Magisk to 15.3 today and also tried flashing Flash Kernel, and I can't get Wifi or fingerprint to work. Have tried flashing back to the Stock+Safetynet Pass Kernel, but still having the same issues.
I just received this error this week.
So, I should just flash stock firmware and it should be good?
Same description: fingerprint won't unlock/verify, but the gestures still work within the OS. Very annoying.
I had to flash a factory image to fully wipe in order to fix this error.
Swiftkey might be the issue
On mine -- Swiftkey was the culprit. Try removing Swiftkey.