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!
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
ScottHW said:
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
Click to expand...
Click to collapse
As advised flash the stock firmware. DATA won't be affected.
ashyx said:
As advised flash the stock firmware. DATA won't be affected.
Click to expand...
Click to collapse
Really? Many posts I've seen have noted that "all user data will be deleted".
Do I just use ODIN, and flash AP? No app, or user data will be erased, or formatted like that?
A few mention "Initializing with Smart Switch"; I haven't done that before. Is that different than flashing firmware?
ScottHW said:
Really? Many posts I've seen have noted that "all user data will be deleted".
Do I just use ODIN, and flash AP? No app, or user data will be erased, or formatted like that?
A few mention "Initializing with Smart Switch"; I haven't done that before. Is that different than flashing firmware?
Click to expand...
Click to collapse
Searching for that question directly, it seems like flashing a ROM (e.g. stock firmware) will not directly erase user data; downloads, photos in DCIM, etc.
But, sounds like any user-installed apps will be erased (so any internally stored data would be lost).
And, data stored in system apps would be lost, too; e.g. tabs that were open in Chrome.
There's no way around the FRP lock, eh?
Here is Samsung's statement about FRP (Factory Reset Protection)
It describes the Google account "protection" features, but doesn't really describe how FRP lock leads to bootloops.
https://www.samsung.com/us/support/frp/
Factory Reset Protection (FRP) Feature
What is Device Protection, or Factory Reset Protection (FRP)?
Android devices provide built-in security features you can use to protect your device and information, including screen locks and data encryption. Data protection, or Factory Reset Protection (FRP), is a security feature on Android devices with Lollipop 5.1 and higher.
FRP is automatically activated when you set up a Google Account on your device. Once FRP is activated, it prevents use of a device after a factory data reset, until you log in using a Google username and password previously set up on the device.
How does FRP work?
When you perform a Factory Data Reset, all settings are returned to the factory default settings. All data is erased, including files and downloaded apps.
If you have a Google Account set up on the device, FRP is active. This means that after the reset, you'll be required to log in to the Google Account using the username and password. If you have multiple Google Accounts set up on the device, you can log in using any of the accounts.
If an unauthorized person tries to reset the device by another method, the device would still require log-in using the Google username and password. This means that if your device is lost or stolen, another person would not be able to reset it and use it.
What do I need to know about FRP?
If you want to reset your device to factory defaults, make sure you know your Google Account and password, because you'll need to log in at the end of the reset.
If you want to reset your device to factory defaults, but don't remember your Google username and/or password, you can do one of these:
Check your devices Account settings for your account name, and reset your password via the device or at www.google.com.
It can take 24 hours for the password reset to sync with all devices registered to the account.
Remove the account before you reset the device.
If you already reset your device, but don't remember your Google username and/or password, the device can't be used. In that case, you can do one of these:
If you know your Google username but can't remember the password, you can reset your password on the device, or at www.google.com. It can take up to 24 hours for a new password to sync with all registered devices. After 24 hours, you can try logging in to your phone with the new password.
If you have multiple Google Accounts, and you can't remember which Google Account you set up on your device, visit https://www.google.com/android/devicemanager.
Log in with your Google username and password and check the list of devices registered to the account. If you don't see the device listed on the account, it means the device is registered to a different account. Use the same process to check for devices linked to your other Google Accounts. When you find the registered account, use it to log in to your device.
If you can't remember any of your Google Account information, you can send your device, along with proof of purchase, to an authorized Samsung Service Center. Samsung has special tools to reset the phone to factory defaults with no protection enabled.
Click to expand...
Click to collapse
Looking for a Samsung Authorized Support Center, apparently there are ZERO listed around Omaha, NE.
http://support-us.samsung.com/cyber/locator/asc_locator.jsp
There must be ASC's somewhere; I'm hesitant to mail the phone away because I think the tech will just wipe it. The whole point is to maintain the data :-/
What do I need to flash to remove "Custom binary" ?
Will flashing the bootloader back to stock unlock the FRP lock?
That's BL throuh ODIN, right?
Do I have to flash AP ?
Won't that remove all user apps and their data, and any user data associated with system apps?
ScottHW said:
What do I need to flash to remove "Custom binary" ?
Will flashing the bootloader back to stock unlock the FRP lock?
That's BL throuh ODIN, right?
Do I have to flash AP ?
Won't that remove all user apps and their data, and any user data associated with system apps?
Click to expand...
Click to collapse
Not being funny, but you're panicking over nothing. I can pretty much guarantee you will NOT lose any data, apps or settings. The DATA partion is untouched by stock firmware.
Just flash the whole stock firmware(not repair firmware) and you'll be fine.
If you're super paranoid about losing data then just flash the AP part.
ashyx said:
Not being funny, but you're panicking over nothing. I can pretty much guarantee you will NOT lose any data, apps or settings. The DATA partion is untouched by stock firmware.
Just flash the whole stock firmware(not repair firmware) and you'll be fine.
If you're super paranoid about losing data then just flash the AP part.
Click to expand...
Click to collapse
Thanks for the reassurance. I am pretty paranoid, because I feel like such an ass for making such a dumb mistake.
Will I lose:
Contacts?
Text messages??
Chrome Bookmarks???
My numerous open Chrome tabs?!?!
I'm just trying to understand what's happening, know what I'm doing.
Because I was clearly stupid enough to uncheck OEM Unlock. (WTF was I thinking?!)
ScottHW said:
Thanks for the reassurance. I am pretty paranoid, because I feel like such an ass for making such a dumb mistake.
Will I lose:
Contacts?
Text messages??
Chrome Bookmarks???
My numerous open Chrome tabs?!?!
I'm just trying to understand what's happening, know what I'm doing.
Because I was clearly stupid enough to uncheck OEM Unlock. (WTF was I thinking?!)
Click to expand...
Click to collapse
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
ashyx said:
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
Click to expand...
Click to collapse
Thanks for the more specific information.
I've never found any discussions about how to solve the frp lock bootloop, with the intention of preserving user data.
If you will indulge me a bit more, I'd like to learn, test, and then share this for others.
Do you know exactly Custom binary blocked by FRP lock ""security" works?
Where is the flag that gets tripped?
In order to solve this bootloop, technically just Boot loader and Recovery need to be flashed (the exact versions must be used, or comparability issues can occur).
Bootloader should be simple enough: BL is one of the specific upload choices in Odin.
Recovery is a .bin that's contained with the AP.tar, correct?
Is it possible to specifically flash only the Recovery?
(I am reading other posts and pages as I write this, sorry if some of these points and questions seem "obvious"; I'm still learning. Aren't we all )
This thread is particularly detailed re: ODIN flashing, although it is from 2013, and for a specific device
https://forum.xda-developers.com/showthread.php?t=2154762
ScottHW said:
Thanks for the more specific information.
I've never found any discussions about how to solve the frp lock bootloop, with the intention of preserving user data.
If you will indulge me a bit more, I'd like to learn, test, and then share this for others.
Do you know exactly Custom binary blocked by FRP lock ""security" works?
Where is the flag that gets tripped?
In order to solve this bootloop, technically just Boot loader and Recovery need to be flashed (the exact versions must be used, or comparability issues can occur).
Bootloader should be simple enough: BL is one of the specific upload choices in Odin.
Recovery is a .bin that's contained with the AP.tar, correct?
Is it possible to specifically flash only the Recovery?
(I am reading other posts and pages as I write this, sorry if some of these points and questions seem "obvious"; I'm still learning. Aren't we all )
This thread is particularly detailed re: ODIN flashing, although it is from 2013, and for a specific device
https://forum.xda-developers.com/showthread.php?t=2154762
Click to expand...
Click to collapse
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
n00b mistake
ashyx said:
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
Click to expand...
Click to collapse
Sh!t, sorry, boot.ing /= bootloader. Rookie mistake. #StillLearning
OK, so boot.img and recovery.img should both be contained within the AP component of stock firmware.
I can just flash those two, can't I?
ashyx said:
No, I didn't mention the bootloader, that is a different part of the firmware. The boot and recovery images have a .img extension and should be flashed under AP.
It is the bootloader that detects non official firmware and trips the FRP flag. If it's disabled in settings via OEM UNLOCK the bootloader ignores it and allows the device to boot.
Click to expand...
Click to collapse
Is there any non-GUI way to toggle the OEM UNLOCK?
Bootloader? Download mode? Recovery? Fastboot? ADB?
I assume not, since that might be a "security" risk. And also, if there were, problems like this would have solutions posted mentioning how to do that.
Sh!!!!!!!t... I was thinking I would have screenshots of the exact build that's loaded on my phone. That way I can find the right stock firmware.
Seems those screenshots are still in the phone, didn't get moved to external memory
All I know for sure is it's Andorid 5.1.1, but that probably isn't specific enough to get the exact right boot and recovery images.
I intend to flash the boot.img and recovery.img to my phone. Hopefully, this will avoid any data loss, while clearing the FRP lock bootloop.
I got the stock firmware for Android 5.1.1 for my Galaxy A3 (2016) (SM-A310M) here:
https://www.sammobile.com/firmwares/galaxy-a3-/SM-A310M/TTT/download/A310MUBU2APE2/73991/
This set of instructions says to extract the .img file(s) to flash, then just .tar them up using 7zip, and flash it as AP in ODIN.
http://howto.highonandroid.com/sams...extract-stock-recovery-from-samsung-firmware/
But... this one says to use Unified Android Toolkit, option ‘8’ (Create an Odin flashable tar), and then flash with ODIN.
https://skipsoft.net/flashing-a-single-partition-i-e-system/
Fortunately, I have a Galaxy A3 (2017) (SM-A320Y), which I was just about to upgrade to for my daily driver. It's blank, running Android 7.0, so it means I can test this process, see if data is preserved, with almost no risk to actual data. Got that firmware here:
https://www.sammobile.com/firmwares/SM-A320Y/COO/download/A320YDXU1BQH2/189605/
Ironically... I don't yet have a great method to intentionally trip the FRP lock bootloop
I think rooting and then unchecking OEM Unlock should do it (that's what wrecked my A310M)
FRP lock - Usb does not recognize
Hi, Everyone!
Sorry my english.
My problem is the same as yours.
however, after this frp lock message appeared, my phone goes into download mode, but the pc does not recognize any more. what can i do to get flash from the rom stock and solve the frp lock problem.
Help me, please!
Thank you all
ScottHW said:
No idea what possessed me to do it (it was late), I unchecked "OEM Unlock", and bricked my phone.
(Android 5.1.1, stock recovery, rooted)
It's stuck in a bootloop with the red message "Custom binary blocked by FRP lock."
I've read many other posts stating that flashing stock firmware will unbrick the phone. That's great, the hardware can be saved. But I need the data; contacts, txts, photos.
What are my options?
Is there any way around FRP lock? I understand tit's intended as a security feature, and basically only happens when people do idiot stuff like unchecking OEM Unlock. So I doubt many devs/hackers have put much focus on developing workarounds.
Theoretically, Samsung may have the capacity to unlock the FRP lock. Is this a thing? Does anyone know anything about sending it to a Samsung tech center? Probably they would have difficulty guaranteeing the phone sender should have rightful access to the phone, so perhaps they provide no pathway?
@ashyx, I've read your posts, you're frankly a wizard. Any thoughts? Thanks
Frustrated with myself,
- Scott
Click to expand...
Click to collapse
FRP Custom binary Lock
ashyx said:
It will be exactly as it was before. Nothing will change.
There are only 2 binaries that need flashing, boot and recovery, however unless you are flashing the exact firmware you had previously you may get compatibility issues, so it's best to just flash the whole firmware.
Click to expand...
Click to collapse
Could you help me to get access to my data? I'm running port of S8 on my S7 and got bootloop. Someone told me that even if I'll flash AP only I might lose my data because of difference in the way the memory is formatted.
Blackion said:
Could you help me to get access to my data? I'm running port of S8 on my S7 and got bootloop. Someone told me that even if I'll flash AP only I might lose my data because of difference in the way the memory is formatted.
Click to expand...
Click to collapse
If they're both stock based firmware then you can just flash the stock S7 firmware. Data should remain untouched.
Hi
I am just stuck with the same problem. I have downloaded the latest Stock ROM. But unsure which options to select in ODIN and what files to select.
I presume only select AP. Also, hope I will not lose any data.
Please help me out.
Hi everyone, i’m having an extremely weird issue with my Samsung J5 Prime (SM-G570Y/on5xelte). First of all; sorry for bad english, this post will be a bit long.
So i want to unlock OEM, to install custom recovery and custom ROM (and being able to login with google account from gms (Google Play Service app)).
i activate developer options.
Then go to Settings > Developer Options, but OEM Unlock is missing (i did'nt have the screenshot of the settings), i already try every method to reappear it but nothing worked.
Trying my luck, im rebooting my phone to download mode, on there i didn’t see any text that says OEM Unlock, i tried to flash OrangeFox Recovery using ODIN. And suprisingly it worked, i even double-checked it by actually booting to recovery. i did'nt expect it to work though...
Then i install RadicalQuack Custom ROM, and do some root-level customization.
But as soon as i try to login Google account from Google Play Service (this didnt affect web login or any other login) on Stock/Custom ROM, and reboot the phone... my phone was FRP locked, i was shocked because my configuration isn’t even backed up.
I have to flash stock rom in download mode, get to setup, login google, remove the account, then i can get rid of FRP lock.
And at this point is where everything is confusing.
If i use stock rom without any changes, the "OEM Unlock" option is'nt appearing at all.
But if i use custom ROM (in this case i use RadicalQuack), the "OEM Unlock" option Appears (until i remove "ro.frp.pst" in build.prop)
So i can do anything but CANNOT login using Google Account from Google Play Services or get FRP locked and All data destroyed.
Now my question is, is it safe to enable "Unlock OEM"? Because i dont know if OEM Unlock is currently enabled or not, i dont know how to check if the bootloader is actually locked, i dont want to get locked forever on samsung stock and bloated shtt again.
PS:
Somehow... i can login Google account without getting FRP locked by:
Unlocking OEM (on the custom ROM ofcourse, since it won't be visible on stock ROM anyway...)
and removing "ro.frp.pst" (especially "ro.frp.pst=/dev/block/persistent") on /system/build.prop, /system/vendor/build.prop, /vendor/build.prop
what did you do?
Hiii, what did you do? I need to unlock oem un my j5 prime
Same Problem Happens to me But Now How you use custom rom without getting frp lock please Tell I Have Also J5 prime And Same Happens to me also I need to flash stock rom from which my custom rom get erased