Hello XDA, I recently flashed over the top of old build from linage to the newest build and my fingerprint scanner has stopped working it will not let me add fingerprints yet I'm still able to use gestures to Swype down notifications. I've tried factory resetting. I've tried formatting data, I've tried re flashing system..
I have not tried going back to stock firmware and reflashing ROM nor have a tried to go back to previous build. I'm using the latest official TWRP. Some one please help, this is not a hardware issue it has to be software. It was working fine on previous build.
Can't u post in that thread or search a little bit - https://forum.xda-developers.com/mi-a1/how-to/discussion-lineageos-15-1-abhishek987-t3758998/page9
Related
hi,
i installed the latest modem for my s5 last night and when i restarted my phone i couldn't use my fingerprint anymore
so i went to settings/ fingerprint i saw this message (check pic) i am using shorat rom, so i did a clean install of the rom again and no luck it didn't work. i tried to install another custom rom and this time it worked so it is a software related problem.
but i really love that shorat rom so i went back is there a fix for my problem of could i find the fingerprint APK somewhere so i coud install it again?
or any other help would be great
I recall seeing threads which mentioned that rooting + custom ROM's break certain TouchWiz features.
I hope this is not! I recommend that you browse the appropriate Custom ROM thread and search for the specific problem.
I've had my phone for a few months now
I flashed the Skydragon 6.0.1 ROM yesterday and I wanted to move back to 5.1.1
So I did, I flashed the TWRP for 5.1.1 and I flashed the Stock OOS 2.2.0
But now, my home button works and Im able to register my fingerprint but after I selected use fingerprint to unlock it doesn't unlock
I've tried every solution on the Internet such as
1) Force stop com.oneplus.fingerprint and hard reset
2)Use software nav buttons
3)Factory reset
Nothing seems to work
I love the fingerprint feature in the OP2
Someone please help me out.
When I dialled *#808# and checked the finger print auto test and it said PASS
So Im sure its not a Hardware error
You should probably flash the old modem back. Can you please get into the security settings inside settings and tell me if you have a force close. If you get a force close you have to flash the old modem.
By saying modem I mean firmware. You can find it in OnePlus 2 Android development > taker18's cyanpop's second post.
Or in blissmallow thread second post.
Sent from my ONE A2003 using Tapatalk
I have the exact opposite issue. My FPS works with all ROMs except H2OS 6.0.1. Let me know if you find a solution. Might help me fix my problem.
kane1234 said:
I've had my phone for a few months now
I flashed the Skydragon 6.0.1 ROM yesterday and I wanted to move back to 5.1.1
So I did, I flashed the TWRP for 5.1.1 and I flashed the Stock OOS 2.2.0
But now, my home button works and Im able to register my fingerprint but after I selected use fingerprint to unlock it doesn't unlock
I've tried every solution on the Internet such as
1) Force stop com.oneplus.fingerprint and hard reset
2)Use software nav buttons
3)Factory reset
Nothing seems to work
I love the fingerprint feature in the OP2
Someone please help me out.
When I dialled *#808# and checked the finger print auto test and it said PASS
So Im sure its not a Hardware error
Click to expand...
Click to collapse
I had the same problem. Do a wipe then flash this it worked for me
https://drive.google.com/file/d/0B97c1b2UXMxCZkh3T0VzSmlCWms/view?usp=docslist_api
Sent from my ONE A2003 using Tapatalk
Thanks guy, I fixed the problem by flashing a persist.img
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...
I used to have Havoc OS and everything was working fine but the location. it never worked for some reason and i needed it on my everyday life.
So used UPPERCUT to install stock ROM, ONLY to quickly realise that CAMERA, FLASHLIGHT and YouTube didn't work.
(when opening camera there was only a black screen, flashlight said i was using a camera app and YouTube was endlessly loading without showing my feed)
I wiped everything and flashed stock ROM from here: https://forum.xda-developers.com/lg...-h870-eu-30b-rom-t4007979/page10#post83380121
STILL having the same problem.....
when using havoc OS i didnt have this problem...
any ideas?
Did you flashed Nougat first? If not flash Nougat
to further explain my problem,
even though Camera used to work fine on HAVOC OS,
now even when using a Hardware Tester from Play Store, the app can't find a the camera...
can flashing stuff on your phone kill hardware?
I had a similar issue with a H872. Camera & proximity wouldn't work after flashing back to stock Oreo from Havoc. Someone here suggested flashing back to Nougat. Lo and behold...it fixed all my issues. I then performed software updates to get to the latest stock version.
Good luck!