Related
OK so my mother decides to buy the same phone I have, the Galaxy Note 4. She thought she'd put on the fingerprint lock, which worked fine, then for some reason, stopped working. She claims she did not set up a backup password, so therefore I cannot see a way to get into the phone. I did find a zip to flash that would supposedly remove the fingerprint lock, but upon booting into recovery and into the option to apply an update from an SD card (I forgot the exact text), it gave me a message that dm-verity verification failed and I could not apply an update from the drive. What can I do to fix this? I don't want to have to FDR, but if that's the only options, I might bite the bullet and do that.
JOSHSKORN said:
OK so my mother decides to buy the same phone I have, the Galaxy Note 4. She thought she'd put on the fingerprint lock, which worked fine, then for some reason, stopped working. She claims she did not set up a backup password, so therefore I cannot see a way to get into the phone. I did find a zip to flash that would supposedly remove the fingerprint lock, but upon booting into recovery and into the option to apply an update from an SD card (I forgot the exact text), it gave me a message that dm-verity verification failed and I could not apply an update from the drive. What can I do to fix this? I don't want to have to FDR, but if that's the only options, I might bite the bullet and do that.
Click to expand...
Click to collapse
I'm not sure about this but I don't think an FDR will fix your problem either. I remember someone else having a similar issue with the fingerprint reader and after trial and error we figured out that an FDR doesn't touch the files used to manage the reader.
I don't think Fingerprint lock will allow you to use it unless you enter a backup password. In any case, if a factory reset doesn't work, you might try taking it to you mom's carrier and see if they can unlock it for you. They'll be able to identify that the phone belongs to her account and maybe have the tools to reset it. Try giving the carrier a call. Other than that, I have no idea.
nahoku said:
I don't think Fingerprint lock will allow you to use it unless you enter a backup password. In any case, if a factory reset doesn't work, you might try taking it to you mom's carrier and see if they can unlock it for you. They'll be able to identify that the phone belongs to her account and maybe have the tools to reset it. Try giving the carrier a call. Other than that, I have no idea.
Click to expand...
Click to collapse
Yes, I advised her to take it to the Verizon store where she got it for assistance. She just assumed that I could help her with everything (literally) since she has the same phone...but not that, unfortunately.
You cant use the fingerprint lock without a backup password. it wont let you use it without one, in case the fingerprint doesnt work. If on the lockscreen you see "Enter backup password" that means she entered it. The backup password is 6 character long with a number, it didnt require any caps letter.
fatmaninc said:
You cant use the fingerprint lock without a backup password. it wont let you use it without one, in case the fingerprint doesnt work. If on the lockscreen you see "Enter backup password" that means she entered it. The backup password is 6 character long with a number, it didnt require any caps letter.
Click to expand...
Click to collapse
That's what I thought. Well, she got it fixed at the Verizon store.
Sent from my SM-N910V using Tapatalk
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Have the same problem. It has something to do with your persist partition. Perhaps you saved it via twrp? I had a save but don´t find it. **** happens.
I erased everything and flashed every fastboot rom via edl or normally. My fingerprint is broken!
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Veran125 said:
Yeah, I used TWRP back in time. But I start to think that's it's a hardware issue. It happened after I had to open my phone to get into EDL mode.
Click to expand...
Click to collapse
In my case it´s a software issue... I used to open my phone, but when my fp broke when I was trying to fix goodix for our new bootleggers rom. I did the fix from official telegram group and a after that, root explorer could mount persist (this was the issue, why fp couldn´t be safed in gsi´s using a pie vendor), but the fp still couldn´t be safed. That means, now it could connect data and changed sth. badly...
I had the same problem. But I had a backup of the twrp sections of the persist and efs. I restored these partitions and flashed 9640 miflash. now the fingerprint works fine
So as long as my fingerprint sensor is recognized, it's most likely not a hardware issue? Furthermore did I unbrick my phone by flashing with EDL mode. Isn't everything formatted then? But I also downgraded to Oreo after that, could that be the reason?
Veran125 said:
But I also downgraded to Oreo after that, could that be the reason?
Click to expand...
Click to collapse
No
My fingerprint recognition works now with rr gsi. I will try wheather the problem is solved on stock too. I just went back too rr gsi, becouse I have a fully working data partition for it and luckily my fp started to work again. Idk what´s the problem.
Veran125 said:
Some days ago I bricked my phone, but made it work again with the EDL method. Everything works again, apart from the Fingerprint sensor. I'm quite sure that I assembled it correctly, because it's clearly recognized(also when I use the swipe on fingerprint sensor to see notifications feature). It's recognized until the last bar at the registration, but then it always fails. I've tried several roms(stock and custom), but always the same.
Any suggestions for a fix?
Thanks in advance
Click to expand...
Click to collapse
Thanks to @eremitein we have a flashable zip that restores the persist image. Just flash via twrp - works for me!
https://forum.xda-developers.com/showpost.php?p=79368367&postcount=25
Thanks a lot, it really works.
Good that I wrote here before I reopened my phone.
Hi, A lot of people are having issue regarding security of device as you cant change your pin and it wont let you enter your pin by showing wrong pin. You cant even have any security after doing a factory reset.
I have done everything to fix it , even took it to samsung repair center, still no success so I have sent it to samsung warranty today.
I have done these things to fix it but nothing worked.
1. Tried online samsung and google "find my phone" service" to fix it as it is shown on some sites for older phones.
2. Reset the phone through recovery.
3. Install fresh firmware through Odin. Then installed both beta versions.
4. Installed orignial firmware mine was VAU.
5. Installed the first firmware of s10 plus. With Nand reset and partition using PIT file.
6. Took it to samsung, they tried 2 different firmwares to fix it but all in vain.
In the end Samsung told me that it might be issue after security patch done for screen protector. They cant do anything at the moment and I have to wait for a fix through update but I have sent my phone to warranty.
I posted this issue in Q&A last day after having issue. But now I can see There are a lot of people affected by this. In my opinion it is Beta 2 issue.
Once you encounter this issue, you are helpless until samsung fixes it. Until then just keep your data, no need to do factory reset or new firmware, as it wont do any help.
What?... Never had any of these issues dude
twoxa said:
What?... Never had any of these issues dude
Click to expand...
Click to collapse
I also got this first time. It is very frustrating and I spend 7 hours to fix it but nothing worked. Until now i have seen 5-6 people who are facing this issue after beta 2. More might come.
I'm also facing this problem, hope Samsung fix this ASAP.
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
madvinegar said:
Those who have this problem, did you sideload manually the updates or have you enrolled and been part of the official Beta program?
Click to expand...
Click to collapse
I sideloaded it.
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
madvinegar said:
To be on the safe side, I have enabled remote unlock and also just tried it to see that everything works. This deletes all your biometrics but at least you can use your phone till a fix is issued.
Thanks for letting us know. Worst case scenario, you can roll back to Pie via Odin, correct?
Fyi: After remotely unlocking the phone, I was able to successfully setup again pin, face and fingerprint biometrics. I cannot understand why this problem affects some people and others are not affected. Why is this triggered by certain phones...?
Click to expand...
Click to collapse
I did rolled it back but didnt work for me. my issue is persistent and even samsung service centre could not fix it. I gave my phone in warranty because I am not sure how much samsung will take to fix this issue and they might be able to fix it. Lets see what samsung will say.
am not having any of these issues on S10+ Beta 2
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
bomp306 said:
I have the same issue. My phone restarts twice a week automatically and after my scheduled restart my pin is no longer working.
I've formatted my phone and now stuck on Beta software as Smart Switch won't downgrade anymore.
I installed via official Beta Enrolment (Samsung Members App) - in the UK.
Was and currently still running the Beta 2 software.
Click to expand...
Click to collapse
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Does this have anything to do with the recent update in the biometrics (fingerprint issue).?
I cannot understand why this bug was not seen right after the update to Beta2, but only after 3-4 days...
---------- Post added at 10:08 AM ---------- Previous post was at 10:06 AM ----------
The good thing is that this bug affects also the ones who officially enrolled to the Beta program, so this means that Samsung must be working to release a fix. At least I hope...
kazim.asghar said:
You can use odin to go back to normal build but there is high probability that it wont fix the issue.
Click to expand...
Click to collapse
I'm on latest android 9 stable via ODIN but the problem with biometrics and pin lock keep in the phone, I did every wipes with no results
Hotfix rolling out now OTA
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
AshishV95 said:
Could somebody share the OTA zip? If somebody knows how to fetch it (if it's possible)?
Thank you.
Click to expand...
Click to collapse
It's already shared in the appropriate thread.
Intratech said:
Hotfix rolling out now OTA
Click to expand...
Click to collapse
Fixed!!
Just need to restore all my apps again now..
should change the thread to SOLVED now that samsung has released a hotfix for it
bomp306 said:
Fixed!!
Just need to restore all my apps again now..
Click to expand...
Click to collapse
Is it fixed? Can you change pin code?
I flashed it and I have absolutely non of the issues you're having. I have an unlocked S10+ on Verizon and I'm running the ZSJF build
Just received this
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Oh no, seems like I have to stuck in version 10.0.10.0 forever ... :crying:
slimshady76 said:
Just got it here in Argentina.
EDIT just can't believe the Xiaomi ****ers took the DT2W function from us and never reinstated it.
Click to expand...
Click to collapse
Hopefully we will get it back with Android 10. I'm using superior os 10 till we get it.. so far it works pretty nicely.
Also got the update. The size looks ok for a simple security patch and minor fixes so nothing major.
Phone starts ok, no problems so far.
This is the first update that no one is complaining about yet... so it's a change in the right direction for the Xiaomi OTAs.
Xiaomi Mi A2 users (they got it 3 days earlier) said that it even works fine with Magisk.
I had 2 odd things happen as a result of installing this OTA.
1) USB Debugging was turned off. No other developer things seem to have changed, just that toggle was off.
2) My timezone was changed. Almost like the phone temporarily forgot I didn't want to use network-provided timezone (it often picks the neighbouring state, which has a 1-hour offset from here).
I've never had this happen with previous OTAs.
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
My dad didn't have this issue. Make sure it isn't your network provider having this problem
If you don't enroll your fingerprint before updating to v 10.0.16 ,you can't do it after the update
benropo said:
Hi, after updating device to November 1 patch device have no network signal. I can't call or receive calls. I have restored phone and still not working. Anyone with the same problem? What can I do to rollback to previous version? Thanks in advice
Click to expand...
Click to collapse
Hello, if someone is experiencing the same problem, I resolved it flashing the official stock rom with Miflash tool. Cheers
This update has definitely done something to the signal mine is falling onto 2G a lot, before that I was steady on 4G. Once it hits 2G it stays on it regardless of the signal strength until you restart the phone. It is very annoying.
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
downloadonlyaccount said:
Getting permanent SD card issues - "integrity check" notification after each unlock or even "incompatible card" message from time to time. Anyone else with this?
Click to expand...
Click to collapse
This sounds like the known issue with new/fast cards. There's a thread where it was discussed.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
That's a problem that sometimes occurs since Pie came out. Restarting the mobile should fix it.
vinylmeister said:
After this update recent apps not working anymore. All apps are closing immediately, not minimizing. Does someone having the same issue?
Click to expand...
Click to collapse
My multitasking seems to be very bad after the update...
Hello,
I have Mi A2 lite with magisk installed, and I am unable to perform the november OTA update.
here is what I do:
1. In magisk : Uninstall > restore images
After doing this, magisk still looks the same:
2. Launch the OTA update.
I first have this screen:
red message translation: "Install will resume when the phone is not active. Click on resume to finish installation now"
3. Clicking on resume will start the installation, but it fails after some moment:
4. After that, I go back to Magisk: Install > Direst install to avoid having Magisk uninstalled after reboot. When doing this, here is the screen:
I don't understand why my OTA is refused...
Is there something to setup in magisk hide ? In order to hide magisk from the OTA updater ? or anything else ?
/system could have been modified, you can try flashing only that partition to solve the issue
nehuy said:
/system could have been modified, you can try flashing only that partition to solve the issue
Click to expand...
Click to collapse
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
takhama said:
Do you know where I can find the system image for 10.0.15 ? I was not able to find it in the threads, only boot images !
Click to expand...
Click to collapse
The upgrade tool writes a log to logcat. It says which partition it does not like.
adb logcat | grep update_engine
There have been no fastboot image released for 10.0.15.0. I have backups of both system and vendor (since they both seem to be modified every OTA for me). If you can confirm that either of these is needed I can try to upload it somewhere. Note that these are very large partitions.
Alternatively, you could use the 10.0.13.0 fastboot and OTA from there. Make sure to backup data before doing this.
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
applesucksLmao said:
ok so, my phone's fingerprint sensor will just show "fingerprint sensor calibration needed" when trying to register a fingerprint. I've tried to nand erase and repartition, clean flash install, magisk install, hard reset etc but it wont work. It passes all the fingerprint tests fine.
I didn't buy or change any parts from the phone, it's still oem
what can i do to solve this? thanks
Click to expand...
Click to collapse
Hey, did you ever find out something?
I just got that problem too
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Captain_cookie_200 said:
weird. its funny how samsung killed my fingerprint all together. it died just by sitting over night. stock and Knox was intact. its permanently gone.fw downgrade doesn't help.
Click to expand...
Click to collapse
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Mighty_Rearranger said:
I *think* it has something to actually do with the calibration. The problem is that the sensor calibration needs to be performed with some application/equipment that either doesn't exist or is exclusive to samsung service centers.
I suspect we're gonna need some hacky workaround like the IMEI thing, which BTW never got really fixed.
Click to expand...
Click to collapse
i see..