Hey guys I've been trying to look this up but I haven't found any answers..
My fingerprint option in security is totally gone and Moto action's sensor navigation just doesn't work. Now I'm not sure what I did for that to happen but my guess is that it has something to do with flashing oreo twrp flashable zip (unsuccessful) and reverting back to stock nougat.
After restoring nougat and booting system I had an error for wrong pattern. I fixed this issue with a lockscreenkey.zip fix available on these forums. Until recently I never went back to set fingerprints in the settings so I never realized that it was gone. The other security options are still there though, only fingerprint is missing.
I have a feeling that doing a complete stock fastboot firmware flash would fix this but I was hoping for another solution
Edit: this problem is solved guys ... I went for the full fastboot firmware solution and it's working. Sry for creating a thread like this for nothing.
Related
So I changed from my old ROM to Dirty Unicorn, all went well, but no pin lock on the lock screen, when I try to change that the settings part of the lockscreen lock will crash, but it will ask me for a pin to access it, tried 3 more ROMS, same problem, I have now just tried Imperium and the problem is still here!?
I have never encountered this before, anyone know how I could fix this? Also my backups fail (can't access some folder or something) so I can't even restore to my version beforehand
Any and all help is appreciated
Edit: Just going back to DU so you all know what ROM I'm running now
So I installed the beta and decided to go back to 7.1.2.
I did a normal wipe in TWRP then reinstalled SAOSP.
The first problem I noticed was that the phone was slow to turn the screen on after pressing the power button or the fingerprint scanner.
The second problem was that the proximity sensor wasn't working in phone calls. I then checked a few others sensors and noticed that the rotation also want working.
I downloaded a sensor checking app and it showed that the proximity sensor had a value of 5 but it didn't change when covering the sensor.
First thought was a bad flash, so I re-wiped and installed a Nand backup that I knew was good. Same thing happened, so I tried PN. That didn't work.
Downloaded stock zip, backed up personal data, then did a complete wipe with the zip, internal data included. The problems stayed even on stock.
I have since read through whatever threads I could. This seems to be a random issue people have had in the past. Yet is particularly prevalent after the o beta.
Most people have suggested to just re-flash stock but that hasn't worked. The only suggestion I have read otherwise is to also lock and then unlock the bootloader in the process as well.
Who else has this problem and has anyone found a fix yet?
Ok, someone posted in another thread (PN) that the locking and unlocking the bootloader worked for them.
If you have the issue try it out.
Just remember to copy all your internal data to your PC or other storage to save it.
https://forum.xda-developers.com/showpost.php?p=72397601&postcount=10078
Link to solution
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
neth15 said:
To fix this, I flashed O DP2 factory image again and then stock 7.1.2 factory image. Now everything's working and I'm rocking Dirty Unicorns 7.1.2
Click to expand...
Click to collapse
I tried it this way but after flashing back to 7.1.2 stock, I now get a crash of com.android.phone immediately after booting, followed by a reboot.
Tried clearing cache but didn't help. Anyone know what to try to fix the crash?
UPDATE: Wiped data and now it's fine.
hi i have had the pleasure of using the developer oreo img and enjoyed it,but decided to reflash stock noughat img
until the official oreo comes out.heres where my issue started,after a successful flash and start up,my sim no
longer shows as inserted,i even tried a restore of my noughat back up.the only way my sim will work nowis with the
oreo stock img reflashed..anyone else have this isssue
Are you sure you flashed all the files included in the Nougat fastboot package zip? There must be an image called 'modem' and anoter 'dsp' which should take care of that.
Try reflashing the Nougat image once again.
I will try again
Having the same exact issue
Flashing the MR3 factory image results in no SIM card, same with fkashing MR1 @TheCrazyLex
EDIT: reflashed again the next day and it's now working....ugh annoying
Had exactly the same issue. Although on initial boot back to Nougat, everything worked fine.
It was only after a restart or two the SIM was then undetected.
I'm flashing stock Nougat again just now, hopefully that resolves it for me too.
EDIT. Ok I've now tried flashing multiple images, they all flash successfully and boot successfully, but none of them are detecting a SIM card.... any ideas anyone?
EDITS AGAIN: It would appear now working after flashing Oreo again, then back to Nougat. Very odd....
I want to lock the bootloader again, which is how I ended up in this mess, so I'm now flashing latest Global ROM again, rebooting and then attempting to lock the bootloader again.
I shall update with results.
any update in the same boat
I'm still having same issues,I'm just using Oreo which is working really well.only downfall I noticed is tethering doesn't seem to be working on it
Are you running the right image as Razer and Three have their own build so wanted to point this out as ThreeUK may not work right with the Razer build. i Remeber them saying something about making sure you use the right build
UPDATE - if anyone is having this issue.
--Take the Oreo preview and flash_all.bat via bootloader
--Let it boot and get in to Android just so you can enable debugging via dev options
--reboot to bootloader and flash_all.bat with the latest Three or Global image
--Again let it boot and enable debugging again
--Now reboot to bootloader, and do BOTH the following in fastboot:
---- fastboot flashing lock_critical
---- let it reboot and go back to bootloader again and perform the next lock
---- fastboot flashing lock
Once finally back in, only then did I have a locked bootloader + working SIM card.
Hope this helps someone.
Locking the bootloader doesn't fix things lol. I was on Oreo yesterday and flashed back to nougat and had signal and relocked the bootloader then 10 minutes later .y phone rebooted and lost sim. Only was to get it back was flashing Oreo then booting then flashing nougat mr1 and got my sim back. Then I locked bootloader and took the ota and now I'm back to normal and can take otas again
This is such a weird issue. like for instance I went back to MR1 from Oreo and had signal but when I picked the bootloader and ota to MR3 it was gone.then just unlocked bootloader flashed MR3 still nothing. So went back to Oreo and it worked and then flashed MR1 again and randomly worked even after the ota to MR3
So absolutely random.
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
SIM card issue
Hey @parky169, @Roxas598, @linuxct, @kickassdave, @joemossjr
Thanks for posting about this issue that you saw about the SIM not being detected. Our engineers would like to learn more about this and EXACTLY what happened. Can you please PM me with the details:
What carrier you guys are on?
What was the previous build you were on before you flashed the Oreo developer build?
Can you please walk me through EXACTLY what happened that caused the SIM to go undetected
Were any APNs changed prior/after?
Were any changes made to the files or phone (rooted, custom ROM, etc.) prior to flashing the O build?
How did you resolve this situation? Is this repeatable?
Thanks again for testing the developer build! Please PM me if you run into any more issues!
Best,
Khanger
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Same issue as the rest. I wonder if this will work with the Oreo OTA modem img, I'm gonna give it a shot. I will report back
EDIT: Well there is probably no reason it shouldn't have worked I would assume the modem images are identical in 8.1 Dev and 8.1 OTA, but it does work by putting the 8.1 MR0 OTA modem img in the 7.1 MR3 and flashing. Honestly i ws too lazy and didn't want to wait for the Dev image to download and I already had a copy of the 8.1 OTA ON MY pc.
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Jonlines94 said:
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Click to expand...
Click to collapse
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
NoXXX said:
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
Click to expand...
Click to collapse
Any update on this? I am in the same boat after standard OTA update. Can not save apns either. (at&t)
Thanks!!!
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Thanks for finding a fix. I was worried my phone was jacked up. I was having the same issue. I wanted to downgrade from Oreo since there is an issue with HDMI not having audio. I got signal now whoooo
Hey so I'm new to the OnlePlus 5T. I used to be on the 3T and never had any issues like this, I was a flashaholic on that device so I know my way around the process of flashing custom roms. Or at least I thought so?
So before I ask, here's what I'm running:
- Latest OOS Firmware, I believe 9.0.4
- Resurrection Remix Pie (Official), Dumpling.
- TWRP (Can't remember the version but it's the latest by codeworkx, was posted this month)
- I AM encyrpted
- I AM rooted with the latest Magisk
So here's what I did: Yesterday I got irritated by the lack of official RR updates, so I tried out an unofficial luisroms build. I reverted back because I realised not much had changed, but when I restored my backup I couldn't get into my phone as it said I needed a password even though I made sure to remove all lockscreen security before making the backup in the first place.
After a few hours of trying, I got in but couldn't register a fingerprint. It just wasn't recognising my finger when I tried to actually set it and stayed on the "Touch the fingerprint sensor" screen.
So I went back to Oxygen OS, made sure I was fully updated and encrypted and then re-flashed official Resurrection Remix Pie for Dumpling.
(Important: As of this point, the fingerprint sensor was working perfectly again, so the physical sensor is working fine!)
I've only just got the phone fully set up, I removed the lockscreen security (Including the fingerprint) and went into TWRP. I made a backup. Then I rebooted back into the OS and now when I'm trying to apply my fingerprint again, it's not recognising my finger. Exactly the same as it was before I re-installed OOS.
So summary: TWRP Backups and Restores are breaking my phone's ability to use the fingerprint sensor. Is this a known issue, and how do I fix it?
Thanks for your time, hopefully the good people of XDA can help me out here :good:
EDIT: Progress has been made, ish.
By going into root/data/system/users/0 and deleting "fpdata" and "settings_fingerprint.xml" I can now get the fingerprint setup to recognise my finger in the settings, but right as I'm about to do the final fingerprint press to set it up I get the error: "enrollment was not completed. Fingerprint enrollment didn't work. Try again or use a different finger"
FURTHER EDIT: So as unrelated as it seems, with the issue happening right after making a backup in TWRP, it appears the issue was caused by a Magisk module called NFS-INJECTOR. Not knocking that project, it's amazing and I'm still using it, but after disabling it in magisk and rebooting I was able to set a fingerprint just fine. I've now re-enabled the module and all seems to be working correctly. I've reported the issue over there and linked to here for steps to reproduce, hopefully it's something that can be fixed. I'll leave this up in case anyone else experiences the same thing.
Hello guys, ive sucessfully rooted ( Magisk 20.3) my device SM-A505G, everything working, excep for fingerprint scanner, sucks i know. Before rooting my phone worked just fine, so its not a hardware related stuff.
I full flashed SM-A505GT binary 5 stock rom (Android 9) on my phone, BL, AP, CP and CSC.
Curious thing is, i went looking for the com.fingerprint service and it is missing, its probably the cause of my nightmare. Do any of you know how to solve this problem? I would install any rom, stock or custom to solve it. It would be easier if i could just install the missing fingerprint service back, i have no clue how to do it.
When i try to add any fingerprint on settings menu or after factory reset it says: "An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device". Ive restarted multiple times and problem persists.
PS: I tried to flash another stock rom, binary 5, now from SM-505G, and that did not work aswell, everything works, except from fingerprint scanner. I keep getting the same message i mentioned above. I hope i can restore the fingerprint function of my phone.
Thanks in advance
I did some search and found that installing TWRP after december update patch breaks all the sensors, that is my case. Is there any solution for this problem yet (for A50)? I have no clue how to put my fingerprint scanner to work again. Sorry for my grammar, this is not my main language.
Fire_GT said:
I did some search and found that installing TWRP after december update patch breaks all the sensors, that is my case. Is there any solution for this problem yet (for A50)? I have no clue how to put my fingerprint scanner to work again. Sorry for my grammar, this is not my main language.
Click to expand...
Click to collapse
Nope,after twrp update breaks all sensor but not FP.Fp sensor is broken only on gsi.Stock rom workin.There is new twrp with working all sensors.On a50 grup telegram
muhamet said:
Nope,after twrp update breaks all sensor but not FP.Fp sensor is broken only on gsi.Stock rom workin.There is new twrp with working all sensors.On a50 grup telegram
Click to expand...
Click to collapse
Im using the stock rom i have downloaded from samfirm, the official one, even when i flashed it without installing twrp my FG was still broken, not working. What i have to do to get it back to work? Could you pls post the link
Fire_GT said:
Im using the stock rom i have downloaded from samfirm, the official one, even when i flashed it without installing twrp my FG was still broken, not working. What i have to do to get it back to work? Could you pls post the link
Click to expand...
Click to collapse
@samsunggalaxya50