Maybe I could get some help, long shot but maybe. I have been flashing roms for quite awhile, on 5+ phones to be exact. I can get EVERYTHING to work and run perfect except fingerprint only worked on first custom ROM flash, now none work. At all. When I try to add a fingerprint, It brings up the fingerprint image on screen and even reacts to me pressing but it will not register a fingerprint. No errors like, "partial fingerprint" or "Fingerprint not recognized" nor any confirmation. I've fastbooted back to several versions of OOS(9.0.11,9.0.12,etc.) on both partitions and tried and tried. Nothing. It still works 100% on stock. The weird part about custom now is when it tells me to setup a fingerprint, it says its located on the back of the phone but I remember my first custom flash said it was on screen.
I know the support is still new for custom with FP but nobody seems to be commenting these issues. Is it normal for right now?
Any support appreciated!
Pseudo_Soldier said:
Maybe I could get some help, long shot but maybe. I have been flashing roms for quite awhile, on 5+ phones to be exact. I can get EVERYTHING to work and run perfect except fingerprint only worked on first custom ROM flash, now none work. At all. When I try to add a fingerprint, It brings up the fingerprint image on screen and even reacts to me pressing but it will not register a fingerprint. No errors like, "partial fingerprint" or "Fingerprint not recognized" nor any confirmation. I've fastbooted back to several versions of OOS(9.0.11,9.0.12,etc.) on both partitions and tried and tried. Nothing. It still works 100% on stock. The weird part about custom now is when it tells me to setup a fingerprint, it says its located on the back of the phone but I remember my first custom flash said it was on screen.
I know the support is still new for custom with FP but nobody seems to be commenting these issues. Is it normal for right now?
Any support appreciated!
Click to expand...
Click to collapse
Did you solve your problem?
Which custom rom are you trying?
Did you flash the stock rom from the fastboot Rom Zip with the flash_all.bat way?
Before you flash a custom rom you should check the features lists/search the thread.
Most devs post in the OP if fingerprint works or not. And 9/10 the question has been asked and answered in the thread a few times.
I've done the flash_all_partitons.bat to go to complete stock. And nah it's not fixed, just living without it for now. I'm on luisroms RR build. I've tried I think just about all of them, no go.
And I have checked features and comments, why I'm posting here in questions, not in rom threads. All custom roms support FOD fingerprints now. Just not my phone it seems.
Weirdly TWRP can't decrypt my data on custom roms at all even though they support it. Thinking something the fastboot flashes don't touch is messed up somehow. Idk
I am having the same issue on the current Candy ROM. Screen flashes as if capturing a fingerprint but never does. FP is supported according to the dev and no one that I saw had this issue in the ROM thread. FP reader did work with OMNI and stock, of course. Thanks in advance for any help!
Related
I replaced NottachTrix with a nightly build of CM7 yesterday night and did a factory reset and formatted the cache partitions. So far it feels really smooth, but there are two issues:
- Phone is periodically getting reset, even when in idle.
- Finger print scanner is not detecting any finger swipes.
Is the issue due to using a nightly build stamped 20120826. Is it because of the build being unstable. Could someone point me to a recent nightly build that is stable enough? If not, how to figure out what is the reason for reboots and FP scanner not working?
I had the rebooting problem when I installed cm7 stable. Do a fast boot erase and reinstall the nightly cm7…reboot should be fixed. However not sure about the fingerprint reader…might have to check if the rom even supports the fingerprint reader.
Oh btw post your questions in the q&a section as you'll get more help and people will skin you for posting in the wrong section.
giqbal said:
I had the rebooting problem when I installed cm7 stable. Do a fast boot erase and reinstall the nightly cm7…reboot should be fixed. However not sure about the fingerprint reader…might have to check if the rom even supports the fingerprint reader.
Oh btw post your questions in the q&a section as you'll get more help and people will skin you for posting in the wrong section.
Click to expand...
Click to collapse
Thanks for the reply. Regarding posting in the wrong forum, I just posted here because I found a past post with a similar discussion in this forum, so used the breadcrumb to navigate up, but perhaps that post itself was in he wrong forum. I will see if I can move it myself, but I doubt having that ability, so request a mod to move before folks start skinning me live
I am going to look up now what is involved with fast boot erase, as I have never done that. Meanwhile, I briefly flashed another ROM called mrom, to see if FP scanner would work. I didn't do a factory reset so some things appeared broken, but I was looking for any sign of the FP working, however no luck so switched back to the previous rom. I have seen posts mentioning that FP scanner works in CM7, so I am assuming that this is a configuration problem, rather than support or hardware.
Did you try latest nightly?
I am currently using latest nightly from CM7 and I am facing absolutely no problem. Give it a shot.
Thanks,
Jinesh
=jinesh10085]I am currently using latest nightly from CM7 and I am facing absolutely no problem. Give it a shot.
Thanks,
Jinesh[/QUOTE]
I finally got a chance and tried the latest nightly, and with in 5 minutes, the phone rebooted. Could this be due to some hardware issues? I did a "fastboot erase boot" and "fastboot erase system" before flashing the new nightly build, and did the usual wipe of cache partitions. Did I miss anything?
I owe an update after using it for a few days, so here it is. After updating with another recent nightly, the reboots haven't stopped, but the frequency has gone down quite a bit. I am beginning to think one of the root apps might be causing this, but the process of elimination to find the root cause a lengthy process, unless there is some diagnostic information somewhere that can give a clue.
Regarding the battery performance, there is a marked improvement. When the usage is marginal, I am almost able to get two full days (with an 1800mAh battery). I am attaching the snapshot of the recent battery usage.
Interestingly, the FP scanner is now working. The last "fastboot erase" probably what fixed it. However, I almost immediately disabled the FP security on the lockscreen, as I found out that you can't fallback to an alternative method to unlock. The thought of FP scanner suddenly stopping to respond and not having an alternative method was enough to do this.
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
santos.moreno3 said:
Thank you for sharing this, I have to say in my case it is not working now i did get the phone rooted and then added jovys rom then did my setup the fingerprint scanner worked for me, then i installed dynamic rom and then the later update of same rom and then the fingerprint scanner is no longer working for me there is a new update for the rom i am going to flash and see if it works now as in a previous version the bloat from samsu g had been removed and with jovys rom being stock rooted it was still there, so i am wondering if it has to do with some of the bloat from Samsung and it being removed that breaks the fingerprint scanner, i will report after i flash the new version of dynamic.
Click to expand...
Click to collapse
I first noticed the problem while I was on Dynamic Kat 1.1 and thought the same thing, that it was something to do with the Sammy apps, but it still didn't work after updating to DK 1.2. I've had it both working and non-working whilst running the same ROM (1.2,) and the only thing different between the two instances was the fact that I configured it while I was in stock in one instance.
This is important information. Hopefully the devs will be able to fix this asap. Thanks!!
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
android242 said:
Wow thank you BotsOne! I'm having the same issue. I'll try this in the morning. Before I rooted, I set up the fingerprint scanner and it worked fine the I switched back to swipe, then rooted. After rooting I installed Jovys rom and lo it hasn't worked since. Does the lock screen have to be set to fingerprint scanner at the time of flashing roms or can you set it up once and move on from that point forward? Thanks again!
Click to expand...
Click to collapse
Honestly I'm not sure. We need a few more people with the same error to get to the bottom of what's going on here. I could be way off with my assumption. We need a bit more info.
Cool I'll try tomorrow and report back..
BotsOne said:
Earlier today I was mucking about and decided to play around with the fingerprint scanner for the first time. When I went in to settings and clicked the fingerprint manager, I received an error stating that the scanner is borked, and to reset my device to fix it. Rebooting did not fix the issue.
Soon I found another person with the same issue, who said that he was able to fix it by flashing stock NJ7 via Odin. After a bit of chatter we realized that neither he nor I had set up the fingerprint scanner before flashing a ROM. We basically booted the phone and went straight to rooting it, and flashing ROMs on it.
I can confirm that re-flashing the stock ROM via odin allowed me to set up the scanner successfully, and that the functionality has not been affected by any subsequent ROM flashing.
I do not understand the mechanism behind why this happens, it is just my experience. Perhaps there is some sort of validation that is run the first time you use the scanner, making sure you are running official firmware, and then setting a flag somewhere? How then would that flag be saved for all subsequent rom flashes? Hidden partition or some ****? Hardware flag? I dunno I don't get it, but I figured out how to fix it by golly. Hopefully this helps someone else.
If any others can confirm the same issue, we may want to add this as a step in the rooting/romming how-to threads, so that others don't run into the same issue.
One good thing is that when I flashed stock via odin, it didn't wipe my data. I was able to then flash TWRP and then Dynamic Kat again, keeping all of my settings the whole way through. Ended up not being as much of a hassle as I thought it was going to be :good:
Click to expand...
Click to collapse
Yes, I am quoting the entire op...
Give me some more evidence of this and I will edit the Root & Recovery Guide immediately... I have seen conflicting posts on this matter too... Also, is not clear if private mode does continue to work after rooting or not... Can anyone confirm... (without flashing any roms... from original unrooted to rooted) Private mode... does work or not??? (Private mode is not suppose to work after rooting... but some say it does work???)
Nice post! Come on people... help...
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
I think this may be an additional problem for flashers, but not necessarily the same one I am addressing. The reason I say this is because I hadn't configured the scanner at all previous to when I discovered that mine didn't work, the error completely prevents me from opening the fingerprint manager. I couldn't even enable the fingerprint function to begin with. Does that make sense?
Not trying to argue just trying to make sure we are on the same page =)
Just noticed my fingerprint scanner isn't working. Wtf lol
Sent from my SM-N910T using Tapatalk
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
inphamous36 said:
Before you back up your rom, disable fingerprint scanner and delete saved fingerprints. If you don't and you go do your backup and ever plan on using the scanner again on that backup, it won't work. One of the guys thinks it has to do with the fingerprints being encrypted so when you restore, it can't decrypt it and locks you out.
I can confirm personally that disabling it before you do your backup then flashing a new rom then restoring your old backup, the fingerprint scanner will still work. Just have to set it up again. But that is a whole lot easier then flashing stock with odin again and starting over.
Click to expand...
Click to collapse
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
COCODRILO45 said:
i notice this problem as soon as i flashed first rom the only way o get it working again is flashing back to stock odin but no matter what i do as soon as i flash a rom I get a error message ? here the post another member had the same problem
http://forum.xda-developers.com/note-4-tmobile/help/fingerprint-sensor-error-t2918069
Click to expand...
Click to collapse
force70 said:
Thats not entirely accurate.
I set up my stock rom with the FP scanner...backed up in twrp as usual and i have flashed 4 roms since then and had to set it up gain each time and never had a problem. Ive never disabled it once.
sent from Canada via my Note 4, 3, 2 or One X+
Click to expand...
Click to collapse
JawjaBill said:
So what exactly must be done to preserve fingerprint scanner functionality before flashing a custom rom?
Click to expand...
Click to collapse
inphamous36 said:
Have you tried restoring a backup and using the scanner? That's when it breaks. I can flash roms fine without having to disable it, but it didn't work after I restored a rom that had it enabled. Locked out of it
Click to expand...
Click to collapse
keitht said:
I can tell you my history. I setup the fingerprint scanner right away before flashing anything as it is a must have feature for me. Later, I flashed a couple different ROM's and never had an issue. Just had to setup the fingerprint again. So my guess is if you set it up before flashing any ROM, you should be good. At least I was. I haven't had to disable before flashing or anything like that.
Click to expand...
Click to collapse
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
I think once you root the KNOX counter gets tripped preventing private mode.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
Yeap I know... but there is this:
http://forum.xda-developers.com/galaxy-s5/development/mod-enable-private-mode-knox-0x1-t2904723
That almost nobody seems to know... It's actually possible to regain Private Mode after a tripped Knox... (Not impossible)
TEKHD said:
And... We ALL agree that Private Mode is Not working...? Right... No Private Mode since rooting... Right? There is absolutely nobody with Private Mode still working after rooting...
Click to expand...
Click to collapse
Well now....never tried it but just did and its working for me. Rooted, jovy23 deodexed stock, twrp.
The day i got my phone i odin'd update then installed twrp, then wiped everything but int & ext sdcard, rebooted to recovery, wiped again then flashed the deodexed stock rom.....just tested fingerprint unlock last night for the first time, no problems and just now tested private mode and again that works for me.
keitht said:
I think once you root the KNOX counter gets tripped preventing private mode.
Click to expand...
Click to collapse
So I've been searching all the internet regarding my problem and found none to have my problem.
I was using popwiz rom and after a while my fingerprint sensor stopped working with the error "An error has occureed with the fingerprint sensor. If this message appears repeatedly, restart your device."
Because I needed my G900FQ, I ignored the issue for a while. Found S7 insanity which has a fingerprint bug and forgot about the problem.
Yesterday wanted to check out official MM for my S5, and had to reflash stock lollipop. Then I remembered my fingerprint problem so I tried to set it up. I kept getting that nasty error, tried deleting cache, tried deleting data with Titanium. Reflashed stock 2 times again, nothing worked. Until I was ready to give up and go to bed. Then it suddenly started working. Managed to set it up and activate fingerprint unlock.
Now is the bummer!
I CAN UNLOCK with fingerprint if waiting about 3 seconds after turning screen on.
I CANNOT ADD FINGER through settings, I get the nasty error message.
Tried to enter factory tests and under NormalScan button says Version 0.0.0.0 and in SensorInfo says Ready and stays that way.
I tried to enter factory tests very fast after unlocking with fingerprint and I got, only once and for a brief moment, the right Version and SensorInfo, and Normal Scan showed data and graph.
Now I will try to install official MM firmware with Odin.
Anyone has any ideas to what the cause may be ? And maybe a solution ?
Thanks in advance
L.E. I installed official MM firmware and now fingerprint sensor works when unlocking and adding fingers, but when I try to unlock my phone while it is connected to a power source I get the nasty error message again and prompts me for my backup password. Any advice would be deeply appreciated.
Flash a stock ROM and factory reset?
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
*Detection* said:
Flash a stock ROM and factory reset?
Click to expand...
Click to collapse
laurent.siku said:
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
Click to expand...
Click to collapse
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
It's obvious that by flashing a stock rom over a custom one will leave bugs. Did full wipe (system, data, cache&dalvik, even phone internal sd) before flashing stock, every time. Thanks anyway..
*Detection* said:
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
Click to expand...
Click to collapse
Well maybe next time add that fairly important info to your main post, instead of hoping everyone is psychic, and then throwing a hissy fit when they suggest something you have not stated you already tried.
Hello,
I just upgraded my phone to OOS 9.0.13 and xXx to 6.0. Since then, I can no longer use my fingerprint sensor properly. I can see the icon on my phone but it's a bit darker and when I place my finger on it to unlock, nothing happens. However, if I tap it multiple times, it tells me I'm pressing it too fast but there's no animation like there is when you unlock your phone.
I deleted the fingerprint I had already and now I can't setup a new one because of what it's doing. I power cycled the device, cleared dalvik cache.. still no luck. All I did was booted to recover, flashed the new OOS version, flashed TWRP installer, rebooted to recovery, flashed magisk, flashed Blu_Spark kernel, rebooted system. I've never had this issue before and the fingerprint sensor was working just fine before I made this change.
Any ideas? I've disabled xXx in Magisk and it still didn't work.
Thanks!
mobbdeep said:
Hello,
I just upgraded my phone to OOS 9.0.13 and xXx to 6.0. Since then, I can no longer use my fingerprint sensor properly. I can see the icon on my phone but it's a bit darker and when I place my finger on it to unlock, nothing happens. However, if I tap it multiple times, it tells me I'm pressing it too fast but there's no animation like there is when you unlock your phone.
I deleted the fingerprint I had already and now I can't setup a new one because of what it's doing. I power cycled the device, cleared dalvik cache.. still no luck. All I did was booted to recover, flashed the new OOS version, flashed TWRP installer, rebooted to recovery, flashed magisk, flashed Blu_Spark kernel, rebooted system. I've never had this issue before and the fingerprint sensor was working just fine before I made this change.
Any ideas? I've disabled xXx in Magisk and it still didn't work.
Thanks!
Click to expand...
Click to collapse
It could be the kernel. Doing a search found results in the blu_spark thread with fingerprint issues.
dj_ooms said:
It could be the kernel. Doing a search found results in the blu_spark thread with fingerprint issues.
Click to expand...
Click to collapse
Definitely makes sense now that I think about it. I thought at first only custom ROM's were having that issue
mobbdeep said:
Hello,
I just upgraded my phone to OOS 9.0.13 and xXx to 6.0. Since then, I can no longer use my fingerprint sensor properly. I can see the icon on my phone but it's a bit darker and when I place my finger on it to unlock, nothing happens. However, if I tap it multiple times, it tells me I'm pressing it too fast but there's no animation like there is when you unlock your phone.
I deleted the fingerprint I had already and now I can't setup a new one because of what it's doing. I power cycled the device, cleared dalvik cache.. still no luck. All I did was booted to recover, flashed the new OOS version, flashed TWRP installer, rebooted to recovery, flashed magisk, flashed Blu_Spark kernel, rebooted system. I've never had this issue before and the fingerprint sensor was working just fine before I made this change.
Any ideas? I've disabled xXx in Magisk and it still didn't work.
Thanks!
Click to expand...
Click to collapse
i have the same issue with mine. but i have the stock rom so i dont have any idea how to fix it. i hope there's something wrong with some software update but i rly dont know. If you find something let me know
how is everyones fingerprint scanner? I don't wanna do onscreen cause it's slower than the rear, what about the 7? I'm almost gonna stay with my 6 just because there's no rear anymore....
with every update it becomes quicker, no issues.. there is a big difference since the early updates.
entwicklun said:
how is everyones fingerprint scanner? I don't wanna do onscreen cause it's slower than the rear, what about the 7? I'm almost gonna stay with my 6 just because there's no rear anymore....
Click to expand...
Click to collapse
Traditional sensors are superior in speed and accuracy the in-display fingerprint is garbage and not ready for market. If it's a dealbreaker for you stay with the 6.
entwicklun said:
how is everyones fingerprint scanner? I don't wanna do onscreen cause it's slower than the rear, what about the 7? I'm almost gonna stay with my 6 just because there's no rear anymore....
Click to expand...
Click to collapse
I find it to be excellent. Slightly slower than my 3T, but just as accurate. And MUCH more accurate than my work-provided iPhone 6. The reader learns over time; after about a week or two it was working optimally.
Rear facing FP scanners are the worst in my opinion. A common use case for me is to have the phone on my desk and I like unlocking it without having to pick up the phone to access anything on the back.
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...