Related
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Use the original usb cable and use Smartswitch recovery, on the back is your serial number you need. And then keep on trying in Smartswitch, it took me a while but it worked and could restore my S6 to stock. And fixed Knox and the FRP lock. And I also tried everything but Smartswitch recovery saved my phone.
Sent from my SM-G928F using XDA-Developers mobile app
SOLVED
Hello, I after countless attempts with firmware that seemed to stock it did not work I SOLVED downloading the firmware directly from the Samsung server using "SAMFIRM" and then flash it with ODIN.
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
vooks said:
Just found myself here. My perfectly working S7 Edge Nougat now has frp on and do-verity.
Click to expand...
Click to collapse
nazreen nasaruddin said:
HI, i just have the same issue .
Have you found the solution?
tried everything.
Hopefully you can help
Click to expand...
Click to collapse
Here's the thing. I had a guy help me fix the FRP problem. And even he had some trouble doing so. And this was done last year, so I only kind of remember how he helped fixed it and I can't guarantee your guys' issue will be fixed if you follow my steps. And you guys may have to know the email and password associated with the phone. I took care of the dm-verity issue on my own afterwards.
Again, I THINK these steps may work, so please don't get mad if these steps don't work. if you guys can, try to flash TWRP or a custom kernel (via ODIN). I know you guys may be having the same problem, but try it out first. If you can't, try finding a combination file for your device (yes, combination file. On Google, search for "[model number] combination file" and download it). Afterwards, flash it to your phone via ODIN. This will allow the phone to boot up, but it's functionality will be very limited. Now, I think this is where you'll be able to login to Google in the settings and the FRP problem will be fixed, IIRC. If you can't login or don't have the details, there's not really much more I can help out with since I believe this is what fixed my problem (really fuzzy memory, sorry). Try rebooting and flashing TWRP again. The combination file itself may have fixed the issue.
If the above fixed the frp problem, GREAT! You should now be able to flash TWRP via ODIN. When you flash TWRP, the dm-verity problem should be fixed, as well. But now your phone needs a ROM and custom kernel. So now find the ones you want. Your phone should be working now!
If for whatever reason your phone still won't work, let me know. I may have another solution.
CrazyTechnoBoy said:
This is my aunt's phone I'm trying to fix. From my understanding, the reason the dm-verity verification fail is occurring is because it had TWRP (which uses dm-verity). And I should be able to flash TWRP to fix it, but since it has the FRP lock on, I can't flash it (custom binary blocked when I try to odin flash). Shouldn't be an issue since I have the email and password associated with the phone, but since the dm-verity fail is preventing the phone from properly booting, I can't do anything.
Just to make it easier to understand
What should fix the phone
- Flash TWRP (so I can flash a custom ROM/kernel)
- Login with the FRP associated account
Problems
- Can't odin flash TWRP because of FRP
- Can't fix FRP because phone won't login because of dm-verity
I've already tried flashing the stock firmware multiple times via ODIN, Kies, and Smart Switch. And I've also tried flashing only the kernel, but the FRP prevents that from going through.
Like I said, I have the account login info associated with the phone, so if there's a way to remotely disable the FRP, that'd be great. Thanks for the help!
Click to expand...
Click to collapse
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
godkingofcanada said:
Dont try to flash a zip you downloaded. Connect to smart switch and tell it to restore the phone. It downloads the right firmware for you.
Click to expand...
Click to collapse
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
CrazyTechnoBoy said:
Naa. I did that. Plenty of times. It simply didn't work. Lol. By saying I tried flashing the stock firmware via Smart Switch, I meant I let Smart Switch do its work. It might work if you only had one issue or the other, but if you have both FRP and dm-verity isses, it probably won't work.
Click to expand...
Click to collapse
you make me calm, cause i think combination file will save my phone which also i encountering the same like what you encountered before. and now i've read this post that you solved by flashing the combination file. i'm still waiting for my combination file cause i have binary 5 official rom while the combination files that i found is binary 4.
thanks!
I have a phone that after installing the June security patch no longer works unless in airplane mode. WiFi works but if you enable the cell service the phone will crash as soon as it establishes connection to the cell network.
I have tried to reset cache and have run a factory reset.
Is there a way to reflash the update to possibly correct the problem?
Will installing a custom ROM resolve my problem?
zeroibis said:
I have a phone that after installing the June security patch no longer works unless in airplane mode. WiFi works but if you enable the cell service the phone will crash as soon as it establishes connection to the cell network.
I have tried to reset cache and have run a factory reset.
Is there a way to reflash the update to possibly correct the problem?
Will installing a custom ROM resolve my problem?
Click to expand...
Click to collapse
If bootloader unlocked, try flashing stock ROM from TWRP. Our device has one such thread for the same. If that's working well, go with any custom ROM. If bootloader not unlocked, take risk, it's mostly safe though, and unlock it.
Kaiwalya said:
If bootloader unlocked, try flashing stock ROM from TWRP. Our device has one such thread for the same. If that's working well, go with any custom ROM. If bootloader not unlocked, take risk, it's mostly safe though, and unlock it.
Click to expand...
Click to collapse
Ok, I will attempt to unlock the boot loader and then I assume that I follow instructions in this thread: https://forum.xda-developers.com/g4-play/development/fxz-harpia-twrp-flashable-fastboots-t3554840
Hey all,
I have the dreaded KG State: Prenormal
firstly i rooted my device, installed TWRP, and then Flash a ROM and No Verify etc...
which worked fine
i was messing around and broke it so thought id just flash the rom again
formatted all the data. and installed the rom again.
this time i didnt flash the No Verify
and in the settings of the rom i installed the Pie Bootloader (Silly Me)
Booting into the Rom, i had no Signal or anything, so thought id reboot my device
ended up soft bricking it ( only official binaries are allowed to be flashed)
I eventually read up on the information here.
worked out i had to Flash back to Stock
Flashed Back to Stock.
Android Pie now as Bootloader is now Version 6 so i have to use Pie (XSA-G950FXXS6DSL3)
Just want to know, if its still the same 7 Days and will reset my KG State
or if it wont come back now.
its odd because under Developer Menu, i still have OEM Unlocking and can turn it on and off
however cant flash TWRP.
should i be leaving OEM unlocking off?
should i flash and then do a Full Wipe again?
what is the next step now?
Thanks to anyone who replies
TL;DR
Soft Brick my S8 Pie Boot-loader
KG Stage PreNormal
will it still take 7 days to reset this?
Jackstuart555 said:
TL;DR
Soft Brick my S8 Pie Boot-loader
KG Stage PreNormal
will it still take 7 days to reset this?
Click to expand...
Click to collapse
you must be a long time lurker or a member of other forums for your first post to have TL;DR in it and for you to have successfully rooted etc etc etc
anyways, yes. You have to wait 168 hours from the time you flashed the stock firmware. The thing youre running into is that the toggle will only let you switch it once per firmware flash. You will need to Odin restore the device back to stock with the CSC not HOME_CSC. Boot, enter your credentials, let it do its thing for 168 hours, then enable dev options and then toggle the unlock.
Did this method work? I waited 168h without sim or wifi but the kg state was still prenormal.
No this didn't work
waited 168 hours (175h)
still in KG State Prenormal
I have now flashed again stock firmware, went into recovery mode and wipe cache/ wipe data/factory reset
although says my firmware info was not valid down the bottom of the recovery
not to sure what is going on
anyway starting my 168H again see what happens
Jackstuart555 said:
I have now flashed again stock firmware, went into recovery mode and wipe cache/ wipe data/factory reset
although says my firmware info was not valid down the bottom of the recovery
not to sure what is going on
anyway starting my 168H again see what happens
Click to expand...
Click to collapse
I hope this will work.
I'm in the exact same situation as you with my SM-G950F.
6 months I've been trying to root my phone again.
Mahiem said:
I hope this will work.
I'm in the exact same situation as you with my SM-G950F.
6 months I've been trying to root my phone again.
Click to expand...
Click to collapse
Did it work?
Jackstuart555 said:
I have now flashed again stock firmware, went into recovery mode and wipe cache/ wipe data/factory reset
although says my firmware info was not valid down the bottom of the recovery
not to sure what is going on
anyway starting my 168H again see what happens
Click to expand...
Click to collapse
set the time to 8 days before the actual day and it should let you flash anything, at least it was like that in my case lol
Mahiem said:
Did it work?
Click to expand...
Click to collapse
no, still KG State Prenormal
think its screwed until a new way to get around it, is found
Jackstuart555 said:
no, still KG State Prenormal
think its screwed until a new way to get around it, is found
Click to expand...
Click to collapse
Damn! I heard that the only way to do it is by a paid service. I'm too stubborn to pay for this.
We'll have to be patient I guess.
anyone who fixed this issue?
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
ugh, the active line... there hasnt ever been much support for those. All you can really do is keep flashing the stock firmware and hope that the errors resolve themselves.
Side note: have you noticed how they stopped making the active phones? They were a dismal failure. All they are is the regular phone in a case that you cant take off :/
dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
Might try redownloading a different firmware from a differ location. I had this issue on a lg back in the day the camera wouldnt work no matter what I always restored stock with one firm I had. And it ended up being a bad download. Another possibility is a bad NFC chip. If it's new I'd have it warranted
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
dchalkley said:
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
TheMadScientist said:
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
Click to expand...
Click to collapse
Yeah, it's working on the 5CSI3 build from October 2019, there's been two recent updates since then (and another will come at the end of the month). I don't know what's happening as no one else has reported this issue .
Just wanting to be on the most recent version for security and the annoyance of having data wiped every update.
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Vcek said:
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Click to expand...
Click to collapse
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
moncd6 said:
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
You can backup your data with Samsung backup and restore to Samsung cloud or to your PC with Samsung's Smart Switch app.
As for tutorial I'll try to make one with images for the latest ROM G892AUCU5CTF4 dated 20-Aug-2020 with August security patch. I'll upload it later as I still have to backup my phone before updating.
Thanks!
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
moncd6 said:
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
Click to expand...
Click to collapse
It doesn't have any bugs but some people have issue with flashing new builds, if you have this issue just install CSI3 build or earlier
dchalkley said:
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
... And to top it all off the NFC app is draining my battery.
Click to expand...
Click to collapse
Same. I also tried CTA2 and CTL1. Everything after CSI3 has NFC crashing and excessive battery drain. I've tried multiple flashes on multiple phones.
dchalkley said:
I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Same.
dchalkley said:
I don't know what's happening as no one else has reported this issue .
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
Click to expand...
Click to collapse
Same here. I used Odin 3.14.1, though.
Vcek said:
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Click to expand...
Click to collapse
This did not work for me, not even with "Nand Erase" checked.
moncd6 said:
It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...
Click to expand...
Click to collapse
Same. The problem of the secret dialer codes not working parallels the NFC problem for me; that is to say that it doesn't work on any firmware after CSI3.
moncd6 said:
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
Click to expand...
Click to collapse
Can you please upload G892AUCS5CSI3? it's all dead links i got
rerenz said:
Can you please upload G892AUCS5CSI3? it's all dead links i got
Click to expand...
Click to collapse
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
voidxor said:
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
Click to expand...
Click to collapse
Finally, it works! My NFC is back. Thanks, pal.
Hey guys...I know I posted this in the persist thread, but I figured it might deserve a dedicated post here just in case there's a bigger issue at play or is something that's relatively unknown.
So long story short, unlike many on here I wanted to go back to a stock, locked, unrooted state after being unlocked & rooted (otherwise stock OOS) for a couple months. Unfortunately, upon doing this my fingerprint scanner stopped working (instantly errors with "enrollment was not completed - fingerprint registration error, please try again" when trying to enroll a fingerprint).
So when the guide came out the other day to repair the fingerprint scanner I tried it. I started off by re-unlocking my bootloader (from full stock, locked, unrooted) so that I could grab the persist partition backup that I hadn't done before. After rebooting suddenly, magically my fp scanner started working again. Then after verifying I could enroll several fingerprints, I booted to TWRP (didn't flash it, just booted) and flashed the magisk zip.
After this, I rebooted and backed up my now-working persist.img partition.
I then did a factory reset from the settings menu, which should return the device to 100% stock. After the reset, I verified during initial setup that the fp scanner was still working properly. I then rebooted to fastboot, and upon re-locking the bootloader received a g.co/ABH message in red saying the device was corrupt and that it would not boot.
I then used the latest 10.5.10 MSM tool to re-flash back to full stock again, which caused it to then boot up as expected. At this point, I tested the fp scanner again during initial device setup and it was once again back to not working.
I then re-enabled OEM unlocking in settings and rebooted to fastboot again. Another bootloader unlock. After reboot I tested the fp scanner again during initial device setup. Lo and behold, it's back to working again.
So I stopped midway through the fp enrollment (just hit back, didn't complete) and rebooted back into fastboot mode. Re-locked bootloader again and booted back up. FP scanner again back to not working with the same "enrollment was not completed - fingerprint registration error, please try again" error.
And once again I re-unlocked the bootloader, enrolled a FP during setup, and then used the MSM tool again. After MSM it again produced the same results - FP scanner wouldn't work upon reboot.
And before anyone asks - I am in contact with OP support for either a warranty replacement or a repair...but this whole situation just doesn't make even the slightest bit of sense to me. Basically my FP scanner works perfectly fine with an unlocked bootloader, but any attempt at re-locking it renders it useless. I do have a working persist backup, but obviously can't flash it from a locked state. Anyone else have any suggestions on something to try, or at least have any sort of theory as to why this behavior would be happening? I have never had a phone where attempting to RE-lock the bootloader has been such a freaking pain.
No one has any idea on this, or theories as to what could be taking place and causing this? OP support has been a total trainwreck so far.
Hi, Did you get a solution for this ? I am facing the same issue of fingerprint sensor not working after relocking the bootloader, although in my case I did not have to reflash the persist img. It works when unlocked and stops working when locked. As usual OP after sales are not really helpful. Thanks
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
shakathesaint said:
Greetings,
same issue here.. has anybody an answer to this problem? It's driving me crazy...
Thank you very much!
Click to expand...
Click to collapse
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
AarSyl said:
I've been trying to solve this issue today, as we speak. However, it seems like the guide to restore the FP reader does not apply to our phone (I have the OP8, but it behaves exactly the same) because we still need root to restore the FP reader, and it will be lost upon relock. In other words, we are stuck. OEM repair/replacement seems to be the only solution.
Click to expand...
Click to collapse
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Related, on 11.0.2.2 magisk and unlocked, my fingerprint sometimes won't recognize at all and forces password unlocks. No corrupt persist or delete and re register a finger solved it.
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
Oh, thank you! I will certainly try!
shakathesaint said:
I'm glad there's someone else who's trying to figure it out!
I'd like to do two more tests, but I can't until this weekend since I'm out of town.
But maybe you already tried and it doesn't work anyway:
Since the md5 checksum of "persist.img" is different whether the lockscreen is set or not, I'd like to unset any kind of lockscreen in Oxygen's settings before relocking the bootloader, in order to see if it makes any difference;
if 1. doesn't work, try to overwrite "persist.img" in fastboot with an image saved BEFORE relocking the bootloader (it should be fastboot flash persist persist.img).
At the moment I'm out of ideas.
Click to expand...
Click to collapse
I'm writing just to update about the tests above: unfortunately neither of them is working, so I'm starting to think there's no other solution than sending the phone to RMA.
Has any one found a solution for this? Im facing exactly the same problem.