Database Users

Can't unlock bootloader, can't finish OS setup

So I upgraded to Nougat on my P9 Lite, unlocked boot loader, used twrp, flashed roms and everything went smooth. Saw a more up-to-date version with no bugs, so I had to downgrade to MM first.
I followed a guide, but I messed up somewhere and ended up having my bootloader locked, and I can't access the OS to enable developer options and oem unlock from settings. The reason why I can't access the OS is that I am stuck in the setup. I am stuck at the part where I have to sign in to my google account. It doesn't show a keyboard, only a microphone, and I can't use that for my password (it won't let me).
Any ideas?
TL;DR messed up during downgrading from Nougat to MM, now TWLR is gone, bootloader is locked and my main issue is that when I get to the google account sign in part during OS setup, there is no keyboard (I can only use dictation) so I can't sign in... So I'm stuck
Also, can I unlock bootloader without access to OS, without being able to navigate to settings, enable developer options and then oem unlock?

1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).

Jagiel88 said:
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Click to expand...
Click to collapse
It is obligatory, I couldn't skip it. I tried to use other methods of signing in, but then it asked me to reset password at the end.
Both Phone and FRP are locked
I think I have missed this, but I can't do it via fastboot because I keep getting "Command not allowed" whenever I try to unlock bootloader or do anything via fast boot.
Also, thank you so much for your time and input. It is much appreciated.

That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).

Jagiel88 said:
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Click to expand...
Click to collapse
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD

No problem, unfortunately I haven't tried Nougat yet, so search for help on down/upgrade Nougat beta <-> Marshmallow threads .

youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?

islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
Click to expand...
Click to collapse
There is 1 thing to unlock in settings . U have OEM lock

youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
ScaleneVirus288 said:
There is 1 thing to unlock in settings . U have OEM lock
Click to expand...
Click to collapse
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.

islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
Click to expand...
Click to collapse
Unlock bootloader, after that you able to flash rom.
You use this command?
fastboot oem unlock YOUR_OEM_CODE
If you tip:
fastboot devices
What's you see?

SM-320FN FRP lock, custom OS installed, how to recover?

Hello,
Me, naab - accidentally turned off OEM boot options (didn't noticed), and restarted the phone (SM-320FN).
Now I have "custom binary blocked by FRP lock" message on boot. I've been using LineageOS 13, so I can't boot it right now.
How to recover this phone? Is is possible to reflash it via Samsung Kies (to the stock FW), then I unlock OEM Boot option and reflash it again to LOS? Or can I type some magic in console via ADB?

Fisz said:
Hello,
Me, naab - accidentally turned off OEM boot options (didn't noticed), and restarted the phone (SM-320FN).
Now I have "custom binary blocked by FRP lock" message on boot. I've been using LineageOS 13, so I can't boot it right now.
How to recover this phone? Is is possible to reflash it via Samsung Kies (to the stock FW), then I unlock OEM Boot option and reflash it again to LOS? Or can I type some magic in console via ADB?
Click to expand...
Click to collapse
Read this
https://forum.xda-developers.com/showthread.php?t=2154890
https://www.ayudaroot.com/root/root-galaxy-j3-sm-j320fn/

How to restore original imei & s/n {g935f}

Hello guys.
SORRY FOR MY ENGLISH.(i'm italian)
A mobile phone shopkeeper modified my IMEI & S/N. Now my phone don't boot because i setted the "OME UNLOCK" option to OFF. Now my phone have got FRP LOCK : ON, so i flashed original rom, but at the boot the recovery turns to me this message"dm-verity-verification-failed". When i flash a TWRP the download mode turns to me this message "CUSTOM BINARY (BOOT) BLOCKED BY FRP LOCK". At this point i flashed a COMBINATION F60 ROM (FACTORY BINARY ROM) to restore my IMEI. This rom boots but the IMEI remain unchanged. Unlike the download mode, this Factory Binary rom allows me to use ADB. How should I proceed to make my phone working? Thank you all, you are my only hope.

kalirobot said:
Hello guys.
SORRY FOR MY ENGLISH.(i'm italian)
A mobile phone shopkeeper modified my IMEI & S/N. Now my phone don't boot because i setted the "OME UNLOCK" option to OFF. Now my phone have got FRP LOCK : ON, so i flashed original rom, but at the boot the recovery turns to me this message"dm-verity-verification-failed". When i flash a TWRP the download mode turns to me this message "CUSTOM BINARY (BOOT) BLOCKED BY FRP LOCK". At this point i flashed a COMBINATION F60 ROM (FACTORY BINARY ROM) to restore my IMEI. This rom boots but the IMEI remain unchanged. Unlike the download mode, this Factory Binary rom allows me to use ADB. How should I proceed to make my phone working? Thank you all, you are my only hope.
Click to expand...
Click to collapse
It seems they changed imei may be because it was blacklisted. Imei wont get corrected without a box repair. And that dm verity issue will occur when you root using modification on system partition and it wont go away even after a reflash. You should have used systemless root. But you can bypass dm verity by flashing no verity opt encrypt from this link
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Flash it using twrp, and your phone should work on stock rooted rom with twrp recovery.
Sent from my S7 Edge using XDA Labs

I have got FRP : ON, will FRP block me? When i flash a twrp, FRP blocks the installation. Is this the same situation?

kalirobot said:
I have got FRP : ON, will FRP block me? When i flash a twrp, FRP blocks the installation. Is this the same situation?
Click to expand...
Click to collapse
Yes if its frp lock, try flashing no verity zip latest version using AP tab of odin. If it fails too, then you need to install custom rom through odin, then install twrp recovery.
Sent from my S7 Edge using XDA Labs

shah22 said:
Yes if its frp lock, try flashing no verity zip latest version using AP tab of odin. If it fails too, then you need to install custom rom through odin, then install twrp recovery.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Odin don't recognizes the zip, so i have to flash it only writing his route. But the flashing don't start anyway.

You can't flash or boot custom binaries with FRP lock on.
You need to disable FRP lock by enabling OEM unlocking under developer options (You tap on build number 7 times in settings, about phone, software information).
More information about flashing dm-verity here: https://forum.xda-developers.com/showpost.php?p=70488012

benjamen50 said:
You can't flash or boot custom binaries with FRP lock on.
You need to disable FRP lock by enabling OEM unlocking under developer options (You tap on build number 7 times in settings, about phone, software information).
Click to expand...
Click to collapse
I can install only a Factory binary firmware that don't has got the OEM option!

kalirobot said:
I can install only a Factory binary firmware that don't has got the OEM option!
Click to expand...
Click to collapse
You are pretty damn stuck, did you tried samsung smartswitch? You have dm verity error which wont let you boot stock rom and then you have oem unlock off which prevents from installing custom roms, so you are pretty badly stuck. Any advanced member with adb shell knowledge can help you now. But try smartswitch atleast.
Sent from my S7 Edge using XDA Labs

Smart switch doesn't work in this situation, i need help with adb.

Adb doesn't work durng the download mode.Adb works only during the "factory binary rom" mode. With some command i get errors of root permission. If nobody can help me with Adb, can i took the phone to somebody that has got the box to restore the original imei? Can i resolve the error in this way?

kalirobot said:
Adb doesn't work durng the download mode.Adb works only during the "factory binary rom" mode. With some command i get errors of root permission. If nobody can help me with Adb, can i took the phone to somebody that has got the box to restore the original imei? Can i resolve the error in this way?
Click to expand...
Click to collapse
https://www.androidsage.com/2017/06...w-to-enable-oem-unlock-on-any-android-device/
See this and try the fastboot method, and yes a box should fix this oem lock issue.
Sent from my S7 Edge using XDA Labs

shah22 said:
https://www.androidsage.com/2017/06...w-to-enable-oem-unlock-on-any-android-device/
See this and try the fastboot method, and yes a box should fix this oem lock issue.
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
i'm following your guide, adb works but when i cornfirm the command to reboot in fastboot mode, the phone restarts itself normally in my factory binary rom... I need your help.

kalirobot said:
i'm following your guide, adb works but when i cornfirm the command to reboot in fastboot mode, the phone restarts itself normally in my factory binary rom... I need your help.
Click to expand...
Click to collapse
Bro if it didn't work for you then i guess it wont, you should try using box, these adb commands don't work for every device, but here are the steps, give commands without commas ;
1. Make sure usb debugging is enabled in developer options.
2. Type 'ADB devices' to see if it displays your device.
3. Type 'ADB reboot bootloader'
4. Type 'ADB fastboot devices' and it should display your device in fastboot
5. Now type 'fastboot OEM unlock'
6. Again type 'fastboot OEM device-info' to check the status of oem unlock.
7. Last type 'fastboot reboot' to reboot phone to OS.
If these commands don't work for you, then i am sorry only a box can solve your issue. Good Luck.
Sent from my S7 Edge using XDA Labs

Hello guys, i resolved the problem with a box. Now i have got Android 7.0. The phone works well and now FRP is on off. But there is now another problem. The bluetouth doesn't start and when i turn off the wifi, the phone forgets all the saved wifi passwords. I need your help. Thanks of all.
Ps: Who repaired my phone yesterday, installed an app called "OctoNetwork". Without it internet(2g 3g 4g) doesn't work.

kalirobot said:
Hello guys.
SORRY FOR MY ENGLISH.(i'm italian)
A mobile phone shopkeeper modified my IMEI & S/N. Now my phone don't boot because i setted the "OME UNLOCK" option to OFF. Now my phone have got FRP LOCK : ON, so i flashed original rom, but at the boot the recovery turns to me this message"dm-verity-verification-failed". When i flash a TWRP the download mode turns to me this message "CUSTOM BINARY (BOOT) BLOCKED BY FRP LOCK". At this point i flashed a COMBINATION F60 ROM (FACTORY BINARY ROM) to restore my IMEI. This rom boots but the IMEI remain unchanged. Unlike the download mode, this Factory Binary rom allows me to use ADB. How should I proceed to make my phone working? Thank you all, you are my only hope.
Click to expand...
Click to collapse
first if ur phone boots then turn on oem unlock and then try flashing whatever u want

try flashing the stock rom again but this time make sure
to tick the box next to update bootloader

RIP S7 EDGE G935FD Can any one help me?

ON U7 Binary with FRP LOCK ON (thats my mistake i turnoff oem unlock after updating to new bootloader on twrp and restarted it)
DM VERIFICATION FAILED
NEED U7 BINARY (COMBINATION FIRMWARE)
or CAN ANYONE TELL ME HOW TO TURN OFF FRP LOCK so that i can flash twrp
or any other method to erase full device so that only mode will be left to flash firmware

The safest way is to boot into download mode and flash in stock rom in odin. Make sure you have the correct stock rom.
Set up the phone as usual, after login to your Google account, you can skip the rest of the phone setup.
Then go settings - accounts - Google and remove your Google account.
Then you can continue to do what you wanted to do. Google frp is switched off.
Sent from my SM-G985F using Tapatalk

vash_h said:
The safest way is to boot into download mode and flash in stock rom in odin. Make sure you have the correct stock rom.
Set up the phone as usual, after login to your Google account, you can skip the rest of the phone setup.
Then go settings - accounts - Google and remove your Google account.
Then you can continue to do what you wanted to do. Google frp is switched off.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
I tried flashing the right firmware but it always says frp lock on
and dm verification failed error 255 blob verification failed
i remember my google id and password but the main issue is phone is not booting up normally it always shows NO COMMAND and then restart itself
also not able to open recovery
IF ANYONE KNOWS HOW TO FLASH ONLY SYSTEM.IMG from previous firmware i can return to U6 and will flash U6 Factory Binary to turnoff oem unlock

Tapas27s said:
I tried flashing the right firmware but it always says frp lock on
and dm verification failed error 255 blob verification failed
i remember my google id and password but the main issue is phone is not booting up normally it always shows NO COMMAND and then restart itself
also not able to open recovery
IF ANYONE KNOWS HOW TO FLASH ONLY SYSTEM.IMG from previous firmware i can return to U6 and will flash U6 Factory Binary to turnoff oem unlock
Click to expand...
Click to collapse
Bro.. Using odin. That's using pc. You screwed up big time and I don't know why you wanted to change the bootloader.
Sent from my SM-G985F using Tapatalk

I flashed firmware using odin..
I want to change bootloader because U7 binary is not on internet U6 is.. thats why

vash_h said:
Bro.. Using odin. That's using pc. You screwed up big time and I don't know why you wanted to change the bootloader.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
After updating to latest bootloader i turn off oem unlocking and that cost me this.. dead phone

I purchased a phone off a guy on facebook for like $60 knowing that it was locked, but not realizing what FRP was exactly and how hard it would be to bypass. I thought I was locked out of my phone as well. Tried everything...odin, Samsung Pro Tool, various random little programs floating around, and all the youtube videos showing FRP bypass glitches. Spent maybe 20 hours trying to figure it out..but FRP always came back. Then, by total accident, I got it to work. Try this: on first boot after flashing the firmware you'll come to a point that says "Installing Applications" or something along those lines. It should occur after the samsung logo but before you get to the "Welcome!" screen. When you see that, turn your phones screen off, wait a second, and then turn it back on. If you are lucky, it will bring you to the normal lock screen and if it does, you'll be able to pull the drop down settings menu from which you can click on the button to bring up the full settings, from which you need to then login to wifi then go back and add a google account. From what I gather, there seems to be a point during the setup process that exists after boot and before FRP actually activates where Android is up and running in terms of it's basic functions before the setup process gets far enough to be able to check the FRP status/engage it. So again:
1. Flash Firmware
2. Boot phone
3. When screen says "Installing Applications" (black screen with a white progress bar) turn your screen off via power putton.
4. Turn screen back on.
5. If you are greeted by the standard android lock screen, try to access the drop down setting toggle switches.
6. If 5 works, click the settings icon to enter into the full settings menu.
7. Go to connections-Wifi and login into your wifi network
8. Back button to main settings menu, then to accounts, add Google account.
9. If you are able to add your google account, that should be it. You'd be able to enter into android and FRP would be disabled. Might need to restart phone.
The above worked for me on a Binary A 8.0 setup. Again, zero luck trying anything..pro software, combination firmwares, etc...that is the only thing that worked. Good luck.

freakwithracket said:
i purchased a phone off a guy on facebook for like $60 knowing that it was locked, but not realizing what frp was exactly and how hard it would be to bypass. I thought i was locked out of my phone as well. Tried everything...odin, samsung pro tool, various random little programs floating around, and all the youtube videos showing frp bypass glitches. Spent maybe 20 hours trying to figure it out..but frp always came back. Then, by total accident, i got it to work. Try this: On first boot after flashing the firmware you'll come to a point that says "installing applications" or something along those lines. It should occur after the samsung logo but before you get to the "welcome!" screen. When you see that, turn your phones screen off, wait a second, and then turn it back on. If you are lucky, it will bring you to the normal lock screen and if it does, you'll be able to pull the drop down settings menu from which you can click on the button to bring up the full settings, from which you need to then login to wifi then go back and add a google account. From what i gather, there seems to be a point during the setup process that exists after boot and before frp actually activates where android is up and running in terms of it's basic functions before the setup process gets far enough to be able to check the frp status/engage it. So again:
1. Flash firmware
2. Boot phone
3. When screen says "installing applications" (black screen with a white progress bar) turn your screen off via power putton.
4. Turn screen back on.
5. If you are greeted by the standard android lock screen, try to access the drop down setting toggle switches.
6. If 5 works, click the settings icon to enter into the full settings menu.
7. Go to connections-wifi and login into your wifi network
8. Back button to main settings menu, then to accounts, add google account.
9. If you are able to add your google account, that should be it. You'd be able to enter into android and frp would be disabled. Might need to restart phone.
The above worked for me on a binary a 8.0 setup. Again, zero luck trying anything..pro software, combination firmwares, etc...that is the only thing that worked. Good luck.
Click to expand...
Click to collapse
phone is not booting up .. In your case phone boots up
in my case phonde dont boot up after flashing firmware it says no command and then shows dm verity error
if my frp was off i would flash twrp and set up my phone..
My case frp on
dm verity error error 255 cannot flash target
i had to fix one of these.... Frp or dm verity..
When my phone was on i made a mistake by turning off oem unlocking then restarting it
that cause me this dead phone..

Tapas27s said:
phone is not booting up .. In your case phone boots up
in my case phonde dont boot up after flashing firmware it says no command and then shows dm verity error
if my frp was off i would flash twrp and set up my phone..
My case frp on
dm verity error error 255 cannot flash target
i had to fix one of these.... Frp or dm verity..
When my phone was on i made a mistake by turning off oem unlocking then restarting it
that cause me this dead phone..
Click to expand...
Click to collapse
Did you try booting the phone in safe mode?

freakwithracket said:
Did you try booting the phone in safe mode?
Click to expand...
Click to collapse
How to boot phone into safe mode when your phone doesn't boot at all
My phone boots up and stuck on NO COMMAND BLUE SCREEN AND THEN SHOW THis

Tapas27s said:
How to boot phone into safe mode when your phone doesn't boot at all
My phone boots up and stuck on NO COMMAND BLUE SCREEN AND THEN SHOW THis
Click to expand...
Click to collapse
I don't know why even at this point of time when there are forums like xda and every basic thing pinned on internet why do people try to intentionally do new/f*** things
In other words, try to fix something which isn't broken..
No, you don't "accidentally" turn oem unlock off.. you need to scroll the screen halfway and then 'tap' right buttons on right screen to enter developer options and then scroll to oem unlock option and tap on it "intentionally" to see what happens
Not trying to be rude or to pick on you.. but it is hillarious how much people in s7 edge forums are 'accidentally' turing oem unlock off.. my inbox is full of such messages ..
I think xda has some issue displaying words correctly.. otherwise this simple basic sentence is posted everywhere on the xda forums :
"YOU NEED TO ENABLE OEM UNLOCK BEFORE DOING ANY UMOFFICIAL MODIFICATION TO YOUR PHONE"
Do you know oem unlock means to unlock bootloader to flash anything other then official OEM ? Failing which will cause phone to reject unofficial modifications and become a brick..
Also let me tell you this luxury of unlocking bootloader is so easily available on samsung phones ..
Do you know how difficult it is now to unlock bootloader of huawei devices ? They stopped providing unlock codes and its a premium charged service now to unlock huawei bootloaders..
And still.. when samsung has made it so easy .. one tap bootloader unlocking and still people mess it to see "what happens".. is ironic really
Ok , the point of all this was not to flame on you or anyone.. but to LET OTHERS KNOW THAT THIS IS NOT A GREAT IDEA TO TURN OEM UNLOCK OFF AFTER YOU MODIFIED YOUR PHONE IN ANY WAY..
Now, to get on your problem.. this cannot be solved by any combination rom ..
The reason your phone cannot boot is because your device's drk (device root key) is corrupted/modified/missing.. which causes dm (device mapping) verity error, it occurs in two types :
1. 1st type is when you enable system modifications in twrp plus dm verity is enabled in the kernel and you "accidentally" turn oem unlock off..
dm verity kicks in this scenario and prevents phone from booting..
BUT your EFS/NV data partition containing DRK is NOT corrupted/modified/missing in this type of error.
This happens when you root your phone with NON-SYSTEMLESS method and oem unlock being turned off..
In this case, just a stock samsung firmware reflash would solve this. Like it happened with @ freakwithracket , he only had frp problem due to oem unlock turned off, and he was able to solve it.
Now the 2nd type which you and many others suffered here too.. this one is akin to a hard brick and trust me when i say hard brick it means it is very very difficult (if not impossible) for average users (including me too) which are noobs to mess in android/linux guts..
I say it is nearly impossible for average users to fix it when even master ChainFire have had difficulty in such..
Refer to his vital post here : https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
And i am just a noob, i just did some research to get knowledge.. thats what everyone should do before posting..
2. This type 2 dm verity mostly kicks in for unfortunate users when:
They enabled system modifications in twrp, and rooted phone using NON-SYSTEMLESS method.
They decided to jump in the death valley (literally lol) by turning OEM UNLOCK OFF.. why though ? :emo_y.tho:
3rd and main reason : FOR SOME REASON THEIR DEVICE'S NV DATA/EFS PARTITION (WHICH CONTAIN DRK) IS CORRUPTED/ENCRYPTED/MODIFIED IN SUCH WAY THAT WHILE ROOTED AND OEM UNLOCK ENABLED IT CAUSES NO PROBLEM IN BOOTING CUSTOM ROMS (BECAUSE OEM UNLOCK IS ON AND CUSTOM ROMS HAVE DM VERITY DISABLED IN KERNELS) BUT YOU CAN ONLY BOOT CUSTOM ROMS WHICH HAVE DM VERITY CHECK DISABLED.. YOU CANNOT BOOT STOCK UNMODIFIED ROM.. (FOR BOOTING STOCK ROM YOU NEED TO INSTALL TWRP AND FLASH NO VERITY ZIPS IN IT)
BUT WHEN OEM UNLOCK IS TURNED OFF, IT CAUSES DM VERITY ERROR PROBABLY DUE TO CORRUPTED/ENCRYPTED/MODIFIED EFS/NV DATA (CONTAINING DRK) WHEN BOOTING STOCK UNMODIFIED ROM AND YOU CANNOT BOOT WITH ANY MODIFIED BINARIES LIKE TWRP OR CUSTOM ROMS OR NO VERITY ZIPS DUE TO OEM UNLOCK BEING OFF WHICH CAUSES CUSTOM BINARY BLOCKED BY FRP AND STOCK BINARY BLOCKED DUE TO DRK PROBLEM (SO YOU GET KIND OF HARD BRICK)
BUT WHICH CANNOT BE SOLVED BY REFLASHING STOCK.. OR ANY COMBINATION ROM..
Now how it can be solved ..
1. Surely can be solved by opening android's/linux guts along with opening your phone's guts and maybe using some hardware tools/boxes too (which frankly only developers can do)..
2. Surely a hardware box can solve this.. (for repairers)
3. Not 100% sure (may work) , editing your stock firmware to "REMOVE" recovery partition and flashing it .. SO THERE IS NO RECOVERY PRESENT BUT PHONE CAN BOOT AND YOU CAN GO IN SETTINGS TO ENABLE OEM UNLOCK..
AND YES, RECOVERY CHECKS DM VERITY AND BLOCKS BOOTING.. (BUT AS MASTER CHAINFIRE SAID THIS MAY NOT WORK BUT PLEASE TRY ! )
I will refer you two posts.. 1st post for following 2nd (box) method above, 2nd post for the 3rd method above..
1. Using box (this may work) https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
This guy here was able to fix something like this too using a box : https://forum.xda-developers.com/s7-edge/help/s7-edge-t4073957/post82232707
2. Using no-recovery method
https://forum.xda-developers.com/s7...-g935f-custom-binary-dm-t4073925/post82134961 - just apply the method on official downloaded stock firmware you had in your phone before it got this problem OR another firmware with a MATCHING bootloader number..
Good luck !
Edit : Was your imei okay and network working?
Pro/experimental tip .. always backup your efs partition (first thing you do after installing twrp), if you have efs backup before all this (which you expect to NOT be corrupted).
Only do this *IF YOU GOT A BACKUP OF EFS (FIRST TIME AFTER INSTALLING TWRP)*..
1. Extract that backup and copy prov_data folder (not a flashable zip) to phone internal memory..
2. Open root explorer , navigate to efs partition (delete all files there EXCEPT FACTORY APP.. DELETE THE PROV_DATA FOLDER THERE TOO) or go in twrp recovery and do this.
3. The moment you delete these files you will not reboot again in phone..
use these commands in adb shell while in twrp
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
(Note: S7 Edge on android 8's path may differ, just replace with correct one)
Don't reboot phone..
After this, device's original drk is restored, but need to be activated, go in download mode from twrp.. flash correct combination rom, go into combination recovery from download mode (without booting into combination rom) do factory data wipe and clear cache and reboot now into combination rom.. your original drk should be okay now.
Warning
*DON'T DO THIS IF YOU DON'T HAVE UNTOUCHED/UN-CORRUPTED (NOT CORRUPTED) EFS BACKUP !*
*YOU NEED TO MAKE YOUR PHONE BOOTING AGAIN TO DO THIS ! AND BEFORE DOING ALL THIS YOU NEED TO REFLASH YOUR CORRECT STOCK FIRMWARE IN ODIN THEN GO IN RECOVERY AND FACTORY DATA WIPE AND CLEAR CACHE, THEN ROOT YOUR PHONE TO GET SU PERMISSIONS THEN BOOT INTO PHONE TO DO ABOVE*
*DON'T DO THIS IF YOU ARE NOT SURE ABOUT ADB COMMANDS*
Successfully doing this can restore drk so if you "accidentally" turn off oem unlock again you won't have a hard brick again.. (Nah, just kidding lol..)
IF YOU DON'T HAVE ORIGINAL EFS BACKUP.. NEVER DO THIS EXPERIMENTAL PROCESS..
Original post reference : https://forum.xda-developers.com/showpost.php?p=67840769&postcount=1
All credits to their respective contributors.
Edit 2 : how to check if your drk is corrupted/modified/missing??
(Always try this after backing up all stuff and making SURE THAT OEM UNLOCK IS ON!!)
Simply flash stock unmodified rom (BUT ALWAYS KEEP OEM UNLOCK ON AT ANY COST), then go in recovery from download mode directly without booting phone, do a factory data wipe and clear cache then reboot phone.. if you can boot into stock unmodified rom without any verification errors.. then your drk is intact (immediately make a backup of your phone's efs partition using any method/tool but systemless root is preferred)
If it gives verification errors, then your drk has problem as described above .. you cannot boot unmodified stock rom and oem unlock being enabled is essential for your phone to be alive.. Flash twrp and then no verity zip to eliminate the dm verity error in stock unmodified rom..
OR flash any custom rom to your liking (most have dm verity disabled in them)
Sorry for the huge word wall, but i thought it is essential information to share
Sent from my S7 Edge using XDA Labs

shah22 said:
I don't know why even at this point of time when there are forums like xda and every basic thing pinned on internet why do people try to intentionally do new/f*** things
In other words, try to fix something which isn't broken..
No, you don't "accidentally" turn oem unlock off.. you need to scroll the screen halfway and then 'tap' right buttons on right screen to enter developer options and then scroll to oem unlock option and tap on it "intentionally" to see what happens
Not trying to be rude or to pick on you.. but it is hillarious how much people in s7 edge forums are 'accidentally' turing oem unlock off.. my inbox is full of such messages ..
I think xda has some issue displaying words correctly.. otherwise this simple basic sentence is posted everywhere on the xda forums :
"YOU NEED TO ENABLE OEM UNLOCK BEFORE DOING ANY UMOFFICIAL MODIFICATION TO YOUR PHONE"
Do you know oem unlock means to unlock bootloader to flash anything other then official OEM ? Failing which will cause phone to reject unofficial modifications and become a brick..
Also let me tell you this luxury of unlocking bootloader is so easily available on samsung phones ..
Do you know how difficult it is now to unlock bootloader of huawei devices ? They stopped providing unlock codes and its a premium charged service now to unlock huawei bootloaders..
And still.. when samsung has made it so easy .. one tap bootloader unlocking and still people mess it to see "what happens".. is ironic really
Ok , the point of all this was not to flame on you or anyone.. but to LET OTHERS KNOW THAT THIS IS NOT A GREAT IDEA TO TURN OEM UNLOCK OFF AFTER YOU MODIFIED YOUR PHONE IN ANY WAY..
Now, to get on your problem.. this cannot be solved by any combination rom ..
The reason your phone cannot boot is because your device's drk (device root key) is corrupted/modified/missing.. which causes dm (device mapping) verity error, it occurs in two types :
1. 1st type is when you enable system modifications in twrp plus dm verity is enabled in the kernel and you "accidentally" turn oem unlock off..
dm verity kicks in this scenario and prevents phone from booting..
BUT your EFS/NV data partition containing DRK is NOT corrupted/modified/missing in this type of error.
This happens when you root your phone with NON-SYSTEMLESS method and oem unlock being turned off..
In this case, just a stock samsung firmware reflash would solve this. Like it happened with @ freakwithracket , he only had frp problem due to oem unlock turned off, and he was able to solve it.
Now the 2nd type which you and many others suffered here too.. this one is akin to a hard brick and trust me when i say hard brick it means it is very very difficult (if not impossible) for average users (including me too) which are noobs to mess in android/linux guts..
I say it is nearly impossible for average users to fix it when even master ChainFire have had difficulty in such..
Refer to his vital post here : https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
And i am just a noob, i just did some research to get knowledge.. thats what everyone should do before posting..
2. This type 2 dm verity mostly kicks in for unfortunate users when:
They enabled system modifications in twrp, and rooted phone using NON SYSTEM LESS method.
They decided to jump in the death valley (literally lol) by turning OEM UNLOCK OFF.. why though ? :emo_y.tho:
3rd and main reason : FOR SOME REASON THEIR DEVICE'S NV DATA/EFS PARTITION (WHICH CONTAIN DRK) IS CORRUPTED/ENCRYPTED/MODIFIED IN SUCH WAY THAT WHILE ROOTED AND OEM UNLOCK ENABLED IT CAUSES NO PROBLEM IN BOOTING CUSTOM ROMS (BECAUSE OEM UNLOCK IS ON AND CUSTOM ROMS HAVE DM VERITY DISABLED IN KERNELS) BUT YOU CAN ONLY BOOT CUSTOM ROMS WHICH HAVE DM VERITY CHECK DISABLED.. YOU CANNOT BOOT STOCK UNMODIFIED ROM.. (FOR BOOTING STOCK ROM YOU NEED TO INSTALL TWRP AND FLASH NO VERITY ZIPS IN IT)
BUT WHEN OEM UNLOCK IS TURNED OFF, IT CAUSES DM VERITY ERROR PROBABLY DUE TO CORRUPTED/ENCRYPTED/MODIFIED EFS/NV DATA (CONTAINING DRK) WHEN BOOTING STOCK UNMODIFIED ROM AND YOU CANNOT BOOT WITH ANY MODIFIED BINARIES LIKE TWRP OR CUSTOM ROMS OR NO VERITY ZIPS DUE TO OEM UNLOCK BEING OFF WHICH CAUSES CUSTOM BINARY BLOCKED BY FRP AND STOCK BINARY BLOCED DUE TO DRK PROBLEM (SO YOU GET KIND OF HARD BRICK)
BUT WHICH CANNOT BE SOLVED BY REFLASHING STOCK.. OR ANY COMBINATION ROM..
Now how it can be solved ..
1. Surely can be solved by opening android's/linux guts along with opening your phone's guts and maybe using some hardware tools/boxes too (which frankly only developers can do)..
2. Surely a hardware box can solve this.. (for repairers)
3. Not 100% sure (may work) , editing your stock firmware to "REMOVE" recovery partition and flashing it .. SO THERE IS NO RECOVERY PRESENT BUT PHONE CAN BOOT AND YOU CAN GO IN SETTINGS TO ENABLE OEM UNLOCK..
AND YES, RECOVERY CHECKS DM VERITY AND BLOCKS BOOTING.. (BUT AS MASTER CHAINFIRE SAID THIS MAY NOT WORK BUT PLEASE TRY ! )
I will refer you two posts.. 1st post for following 2nd (box) method above, 2nd post for the 3rd method above..
1. Using box (this may work) https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
This guy here was able to fix something like this too using a box : https://forum.xda-developers.com/s7-edge/help/s7-edge-t4073957/post82232707
2. Using no-recovery method
https://forum.xda-developers.com/s7...-g935f-custom-binary-dm-t4073925/post82134961 - just apply the method on official downloaded stock firmware you had in your phone before it got this problem OR another firmware with a MATCHING bootloader number..
Good luck !
Edit : Was your imei okay and network working?
Pro/experimental tip .. always backup your efs partition (first thing you do after installing twrp), if you have efs backup before all this (which you expect to NOT be corrupted).
Only do this *IF YOU GOT A BACKUP OF EFS (FIRST TIME AFTER INSTALLING TWRP)*..
1. Extract that backup and copy prov_data folder (not a flashable zip) to phone internal memory..
2. Open root explorer , navigate to efs partition (delete all files there EXCEPT FACTORY APP.. DELETE THE PROV_DATA FOLDER THERE TOO) or go in twrp recovery and do this.
3. The moment you delete these files you will not reboot again in phone..
use these commands in adb shell while in twrp
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
(Note: S7 Edge on android 8's path may differ, just replace with correct one)
Don't reboot phone..
After this, device's original drk is restored, but need to be activated, go in download mode from twrp.. flash correct combination rom, go into combination recovery from download mode (without booting into combination rom) do factory data wipe and clear cache and reboot now into combination rom.. your original drk should be okay now.
Warning
*DON'T DO THIS IF YOU DON'T HAVE UNTOUCHED/UN-CORRUPTED (NOT CORRUPTED) EFS BACKUP !*
*YOU NEED TO MAKE YOUR PHONE BOOTING AGAIN TO DO THIS ! AND BEFORE DOING ALL THIS YOU NEED TO REFLASH YOUR CORRECT STOCK FIRMWARE IN ODIN THEN GO IN RECOVERY AND FACTORY DATA WIPE AND CLEAR CACHE, THEN ROOT YOUR PHONE TO GET SU PERMISSIONS THEN BOOT INTO PHONE TO DO ABOVE*
*DON'T DO THIS IF YOU ARE NOT SURE ABOUT ADB COMMANDS*
Successfully doing this can restore drk so if you "accidentally" turn off oem unlock again you won't have a hard brick again.. (Nah, just kidding lol..)
IF YOU DON'T HAVE ORIGINAL EFS BACKUP.. NEVER DO THIS EXPERIMENTAL PROCESS..
Original post reference : https://forum.xda-developers.com/showpost.php?p=67840769&postcount=1
All credits to their respective contributors.
Edit 2 : how to check if your drk is corrupted/modified/missing??
(Always try this after backing up all stuff and making SURE THAT OEM UNLOCK IS ON!!)
Simply flash stock unmodified rom (BUT ALWAYS KEEP OEM UNLOCK ON AT ANY COST), then go in recovery from download mode directly without booting phone, do a factory data wipe and clear cache then reboot phone.. if you can boot into stock unmodified rom without any verification errors.. then your drk is intact (immediately make a backup of your phone's efs partition using any method/tool but systemless root is preferred)
If it gives verification errors, then your drk has problem as described above .. you cannot boot unmodified stock rom and oem unlock being enabled is essential for your phone to be alive.. Flash twrp and then no verity zip to eliminate the dm verity error in stock unmodified rom..
OR flash any custom rom to your liking (most have dm verity disabled in them)
Sorry for the huge word wall, but i thought it is essential information to share
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
1 ST METHOD TRIED with modified AP ( name boot.img as recovery.img and system.img )
Result in direct booting and samsung logo then it gets off suddenly and shows No command with blue screen view 1st pic
2nd method tried modified ap with bl cp csc result in stuck with samsunt logo for about 15 mintues watch 2 nd pic
3rd Tried modified ap with bl cp csc and with pit file..
Also result in stuck with samsung logo
4TH I TRY FLASHING 2nd modified ap ( rename boot.img as recovery,original boot.img and system.img)
Then i put my phone into boot process
Showed samsung logo and then it shows button lights..i was waiting for the screen to say insatlling applications like the galaxy app and smart switch but instead of that.. it showed nothing and reboots into blue screen with no command and shows this image

shah22 said:
I don't know why even at this point of time when there are forums like xda and every basic thing pinned on internet why do people try to intentionally do new/f*** things
In other words, try to fix something which isn't broken..
No, you don't "accidentally" turn oem unlock off.. you need to scroll the screen halfway and then 'tap' right buttons on right screen to enter developer options and then scroll to oem unlock option and tap on it "intentionally" to see what happens
Not trying to be rude or to pick on you.. but it is hillarious how much people in s7 edge forums are 'accidentally' turing oem unlock off.. my inbox is full of such messages ..
I think xda has some issue displaying words correctly.. otherwise this simple basic sentence is posted everywhere on the xda forums :
"YOU NEED TO ENABLE OEM UNLOCK BEFORE DOING ANY UMOFFICIAL MODIFICATION TO YOUR PHONE"
Do you know oem unlock means to unlock bootloader to flash anything other then official OEM ? Failing which will cause phone to reject unofficial modifications and become a brick..
Also let me tell you this luxury of unlocking bootloader is so easily available on samsung phones ..
Do you know how difficult it is now to unlock bootloader of huawei devices ? They stopped providing unlock codes and its a premium charged service now to unlock huawei bootloaders..
And still.. when samsung has made it so easy .. one tap bootloader unlocking and still people mess it to see "what happens".. is ironic really
Ok , the point of all this was not to flame on you or anyone.. but to LET OTHERS KNOW THAT THIS IS NOT A GREAT IDEA TO TURN OEM UNLOCK OFF AFTER YOU MODIFIED YOUR PHONE IN ANY WAY..
Now, to get on your problem.. this cannot be solved by any combination rom ..
The reason your phone cannot boot is because your device's drk (device root key) is corrupted/modified/missing.. which causes dm (device mapping) verity error, it occurs in two types :
1. 1st type is when you enable system modifications in twrp plus dm verity is enabled in the kernel and you "accidentally" turn oem unlock off..
dm verity kicks in this scenario and prevents phone from booting..
BUT your EFS/NV data partition containing DRK is NOT corrupted/modified/missing in this type of error.
This happens when you root your phone with NON-SYSTEMLESS method and oem unlock being turned off..
In this case, just a stock samsung firmware reflash would solve this. Like it happened with @ freakwithracket , he only had frp problem due to oem unlock turned off, and he was able to solve it.
Now the 2nd type which you and many others suffered here too.. this one is akin to a hard brick and trust me when i say hard brick it means it is very very difficult (if not impossible) for average users (including me too) which are noobs to mess in android/linux guts..
I say it is nearly impossible for average users to fix it when even master ChainFire have had difficulty in such..
Refer to his vital post here : https://forum.xda-developers.com/showpost.php?p=72204306&postcount=978
And i am just a noob, i just did some research to get knowledge.. thats what everyone should do before posting..
2. This type 2 dm verity mostly kicks in for unfortunate users when:
They enabled system modifications in twrp, and rooted phone using NON SYSTEM LESS method.
They decided to jump in the death valley (literally lol) by turning OEM UNLOCK OFF.. why though ? :emo_y.tho:
3rd and main reason : FOR SOME REASON THEIR DEVICE'S NV DATA/EFS PARTITION (WHICH CONTAIN DRK) IS CORRUPTED/ENCRYPTED/MODIFIED IN SUCH WAY THAT WHILE ROOTED AND OEM UNLOCK ENABLED IT CAUSES NO PROBLEM IN BOOTING CUSTOM ROMS (BECAUSE OEM UNLOCK IS ON AND CUSTOM ROMS HAVE DM VERITY DISABLED IN KERNELS) BUT YOU CAN ONLY BOOT CUSTOM ROMS WHICH HAVE DM VERITY CHECK DISABLED.. YOU CANNOT BOOT STOCK UNMODIFIED ROM.. (FOR BOOTING STOCK ROM YOU NEED TO INSTALL TWRP AND FLASH NO VERITY ZIPS IN IT)
BUT WHEN OEM UNLOCK IS TURNED OFF, IT CAUSES DM VERITY ERROR PROBABLY DUE TO CORRUPTED/ENCRYPTED/MODIFIED EFS/NV DATA (CONTAINING DRK) WHEN BOOTING STOCK UNMODIFIED ROM AND YOU CANNOT BOOT WITH ANY MODIFIED BINARIES LIKE TWRP OR CUSTOM ROMS OR NO VERITY ZIPS DUE TO OEM UNLOCK BEING OFF WHICH CAUSES CUSTOM BINARY BLOCKED BY FRP AND STOCK BINARY BLOCED DUE TO DRK PROBLEM (SO YOU GET KIND OF HARD BRICK)
BUT WHICH CANNOT BE SOLVED BY REFLASHING STOCK.. OR ANY COMBINATION ROM..
Now how it can be solved ..
1. Surely can be solved by opening android's/linux guts along with opening your phone's guts and maybe using some hardware tools/boxes too (which frankly only developers can do)..
2. Surely a hardware box can solve this.. (for repairers)
3. Not 100% sure (may work) , editing your stock firmware to "REMOVE" recovery partition and flashing it .. SO THERE IS NO RECOVERY PRESENT BUT PHONE CAN BOOT AND YOU CAN GO IN SETTINGS TO ENABLE OEM UNLOCK..
AND YES, RECOVERY CHECKS DM VERITY AND BLOCKS BOOTING.. (BUT AS MASTER CHAINFIRE SAID THIS MAY NOT WORK BUT PLEASE TRY ! )
I will refer you two posts.. 1st post for following 2nd (box) method above, 2nd post for the 3rd method above..
1. Using box (this may work) https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
This guy here was able to fix something like this too using a box : https://forum.xda-developers.com/s7-edge/help/s7-edge-t4073957/post82232707
2. Using no-recovery method
https://forum.xda-developers.com/s7...-g935f-custom-binary-dm-t4073925/post82134961 - just apply the method on official downloaded stock firmware you had in your phone before it got this problem OR another firmware with a MATCHING bootloader number..
Good luck !
Edit : Was your imei okay and network working?
Pro/experimental tip .. always backup your efs partition (first thing you do after installing twrp), if you have efs backup before all this (which you expect to NOT be corrupted).
Only do this *IF YOU GOT A BACKUP OF EFS (FIRST TIME AFTER INSTALLING TWRP)*..
1. Extract that backup and copy prov_data folder (not a flashable zip) to phone internal memory..
2. Open root explorer , navigate to efs partition (delete all files there EXCEPT FACTORY APP.. DELETE THE PROV_DATA FOLDER THERE TOO) or go in twrp recovery and do this.
3. The moment you delete these files you will not reboot again in phone..
use these commands in adb shell while in twrp
1. su
2. cd /efs
3. mv /data/media/0/prov_data /efs/
4. chmod -R 755 /efs/prov_data
5. chown -R root:root /efs/prov_data
(Note: S7 Edge on android 8's path may differ, just replace with correct one)
Don't reboot phone..
After this, device's original drk is restored, but need to be activated, go in download mode from twrp.. flash correct combination rom, go into combination recovery from download mode (without booting into combination rom) do factory data wipe and clear cache and reboot now into combination rom.. your original drk should be okay now.
Warning
*DON'T DO THIS IF YOU DON'T HAVE UNTOUCHED/UN-CORRUPTED (NOT CORRUPTED) EFS BACKUP !*
*YOU NEED TO MAKE YOUR PHONE BOOTING AGAIN TO DO THIS ! AND BEFORE DOING ALL THIS YOU NEED TO REFLASH YOUR CORRECT STOCK FIRMWARE IN ODIN THEN GO IN RECOVERY AND FACTORY DATA WIPE AND CLEAR CACHE, THEN ROOT YOUR PHONE TO GET SU PERMISSIONS THEN BOOT INTO PHONE TO DO ABOVE*
*DON'T DO THIS IF YOU ARE NOT SURE ABOUT ADB COMMANDS*
Successfully doing this can restore drk so if you "accidentally" turn off oem unlock again you won't have a hard brick again.. (Nah, just kidding lol..)
IF YOU DON'T HAVE ORIGINAL EFS BACKUP.. NEVER DO THIS EXPERIMENTAL PROCESS..
Original post reference : https://forum.xda-developers.com/showpost.php?p=67840769&postcount=1
All credits to their respective contributors.
Edit 2 : how to check if your drk is corrupted/modified/missing??
(Always try this after backing up all stuff and making SURE THAT OEM UNLOCK IS ON!!)
Simply flash stock unmodified rom (BUT ALWAYS KEEP OEM UNLOCK ON AT ANY COST), then go in recovery from download mode directly without booting phone, do a factory data wipe and clear cache then reboot phone.. if you can boot into stock unmodified rom without any verification errors.. then your drk is intact (immediately make a backup of your phone's efs partition using any method/tool but systemless root is preferred)
If it gives verification errors, then your drk has problem as described above .. you cannot boot unmodified stock rom and oem unlock being enabled is essential for your phone to be alive.. Flash twrp and then no verity zip to eliminate the dm verity error in stock unmodified rom..
OR flash any custom rom to your liking (most have dm verity disabled in them)
Sorry for the huge word wall, but i thought it is essential information to share
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
interesting.
Sent from my SM-G985F using Tapatalk

Tapas27s said:
1 ST METHOD TRIED with modified AP ( name boot.img as recovery.img and system.img )
Result in direct booting and samsung logo then it gets off suddenly and shows No command with blue screen view 1st pic
2nd method tried modified ap with bl cp csc result in stuck with samsunt logo for about 15 mintues watch 2 nd pic
3rd Tried modified ap with bl cp csc and with pit file..
Also result in stuck with samsung logo
Click to expand...
Click to collapse
You wont stuck on samsung logo for long.. eventually it will boot in and you could enable oem unlock..
WAIT ATLEAST FOR 30 MINUTES ON SAMSUNG LOGO, MAYBE IT WILL LET YOU IN..
If it didn't worked your phone wouldn't have booted.
Try as said in post..
system.img + [renamed] recovery.img (which is boot.img) see if it works
If not then try : system.img + [renamed] recovery.img + boot.img (which means system.img + boot.img + boot.img) see if this works
If not then try : system.img + [renamed] recovery.img + boot.img + userdata.img .. see if it works ?
If not try : system.img + [renamed] recovery.img + userdata.img .. see if this works.
Try flashing only AP in odin , if don't works .. use BL+CP+CSC too
First try with normal csc , then try with Home_Csc too
Don't use pit file..no use..
Try with combinations i said above.
If couldn't fix, pm me, we try to fix on tv. Good luck
Edit : I SEE DM VERITY IS NOT KICKING IN.. YOU JUST NEED TO GET IN PHONE TO ENABLE OEM UNLOCK..
You just need to try different combinations to get inside..
Maybe use userdata.img too ??
I think you need to try with : system.img + [renamed] recovery.img + boot.img + userdata.img ..
Sent from my S7 Edge using XDA Labs

Thanks thanks thanks thanks!!!!
shah22 said:
You wont stuck on samsung logo for long.. eventually it will boot in and you could enable oem unlock..
WAIT ATLEAST FOR 30 MINUTES ON SAMSUNG LOGO, MAYBE IT WILL LET YOU IN..
If it didn't worked your phone wouldn't have booted.
Try as said in post..
system.img + [renamed] recovery.img (which is boot.img) see if it works
If not then try : system.img + [renamed] recovery.img + boot.img (which means system.img + boot.img + boot.img) see if this works
If not then try : system.img + [renamed] recovery.img + boot.img + userdata.img .. see if it works ?
If not try : system.img + [renamed] recovery.img + userdata.img .. see if this works.
Try flashing only AP in odin , if don't works .. use BL+CP+CSC too
First try with normal csc , then try with Home_Csc too
Don't use pit file..no use..
Try with combinations i said above.
If couldn't fix, pm me, we try to fix on tv. Good luck
Edit : I SEE DM VERITY IS NOT KICKING IN.. YOU JUST NEED TO GET IN PHONE TO ENABLE OEM UNLOCK..
You just need to try different combinations to get inside..
Maybe use userdata.img too ??
I think you need to try with : system.img + [renamed] recovery.img + boot.img + userdata.img ..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
THANKS THANKS THANKS!!!!
it successfully booted
i signed in and turn on the oem unlock option with usb debugging now i am just reflashing the firmware and then twrp then dmverity opt zip then magisk then i will charge and use my phone
thanks alot!!! @shah22

Tapas27s said:
THANKS THANKS THANKS!!!!
it successfully booted
i signed in and turn on the oem unlock option with usb debugging now i am just reflashing the firmware and then twrp then dmverity opt zip then magisk then i will charge and use my phone
thanks alot!!! @shah22
Click to expand...
Click to collapse
Glad it worked..
JUST DON'T TURN OFF OEM UNLOCK AGAIN "ACCIDENTALLY"
So you used system.img + [renamed] recovery.img + boot.img + userdata.img ??
Post your exact steps here so others may benefit
Sent from my S7 Edge using XDA Labs

shah22 said:
Glad it worked..
JUST DON'T TURN OFF OEM UNLOCK AGAIN "ACCIDENTALLY"
So you used system.img + [renamed] recovery.img + boot.img + userdata.img ??
Post your exact steps here so others may benefit
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
STEPS
1 EXTRACT FILES FROM AP TAKE 2 FILES BOOT.IMG AND SYSTEM.IMG
MAKE A COPY OF BOOT.IMG TO ANOTHER FOLDER AND RENAME IT AS RECOVERY.IMG
2 YOU HAVE NOW 3 FILES BOOT.IMG, RENAMED RECOVERY.IMG AND SYSTEM.IMG
3 DOWNLOAD AUTO TAR 2.0 AND MAKE TAR MD5 FILE
4 SO YOU HAVE MODIFIED AP FLASH IT ALONG WITH CP BL AND HOME CSC AND WAIT TO BOOT THE PHONE ( CHARGE YOUR PHONE ATLEAST 10%)
THEN THERE YOU GO WELCOME SCREEN SIGN IN AND AFTER TURN OFF THE OEM UNLOCK OPTION BY GOING INTO DEVELOPER OPTIONS BY CLICKING ON THE BUILD NUMBER SEVERAL TIMES AND ALSO TURN ON THE USB DEBUGGING
THEN YOU HAVE TO REFLASH THE FIRMWARE
THEN AFTER FLASH TWRP THEN DM VERITY ZIP AND THEN MAGISK TO ROOT AND THEN BOOT INTO SYSTEM AND ENJOY
THANKS FOR HELPING me @shah22

Ah nice, so you need to flash HOME_CSC to make it work.. thats what i wanted to confirm ..
Enjoy
Edit : in your No. 4 step : we turn "ON" OEM UNLOCK in the developer option but you wrote "turn off" ? ..
Sent from my S7 Edge using XDA Labs

shah22 said:
Ah nice, so you need to flash HOME_CSC to make it work.. thats what i wanted to confirm ..
Enjoy
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
If you need to flash clean try ODD CSC and if you want to save data flash HOME CSC

shah22 said:
ah nice, so you need to flash home_csc to make it work.. Thats what i wanted to confirm ..
Enjoy
edit : In your no. 4 step : We turn "on" oem unlock in the developer option but you wrote "turn off" ? ..
Sent from my s7 edge using xda labs
Click to expand...
Click to collapse
hey sim card not working..
I am using jio sometimes it is showing networks with volte and sometime it is showing nothing..and thanks for editing my point

Need help returning Verizon Galaxy S7 Edge to factory ROM and FRP Lock

Needed to unbrick a SM-G935V, had trouble finding the right ROMs and eventually got​COMBINATION_VZW_FA60_G935PUCUBATA1_BIT_11_B_05_01_22.tar.7z to work​
However now that put me at version 11 and none of the factory images or combo files I can find will flash via Odin because of that.
Does anyone have a way to return my S7 Edge to factory or near factory VZW function?

Ok got a good factory image from SamFw, loaded fine with Odin, however the FRP is engaged. I cannot find a good Version 11 VZW combo file to wipe the FRP with. Does any one have a good lead on a combo file to wipe the FRP
For ****s and giggles I've tried a few programs like FRP Hijacker and SamFw FRP tool.
Hijacker says it returns the phone to "clean slate" but when it reboots FRP is still engaged
FRP Tool cannot connect since the phone cannot enter engineering service mode via the secret code when FRP locked, so it cannot perform the frp wipe.

Using COMBINATION_VZW_FA60_G935PUCUBATA1 I get the phone to launch into Factory Binary, however it identifies itself as a SM-G935A (supposed to be 935V)
USB debugging is on
And I can easily use both FRP Hijacker and SamFw FRP tool, both confirm "Frp Removed"
However once I reflash the phone via Odin with SM-G935V_VZW_G935VVRSBCTC1_fac files and it returns to a Verizon OEM phone, the FRP is still engaged in the start up screen and cannot use the phone.
Am I missing a step here?

Ok I cannot for the life of me defeat the FRP lock.
Did a full wipe through TWRP
Ran FrpDestroyer 1.1 under TWRP (3.0 hung up?) 1.1 confirmed "FRP overwrite with zeros"
Maybe I'm not doing something is the correct order?
I tried combo bins, tried making a custom combo bin, each time i return to the factory files, it's still locked

armonic said:
Needed to unbrick a SM-G935V, had trouble finding the right ROMs and eventually got​COMBINATION_VZW_FA60_G935PUCUBATA1_BIT_11_B_05_01_22.tar.7z to work​
Click to expand...
Click to collapse
boot too safestrap after you flash above
Then flash zip from this post 2 in this thread
[Rom][VZW_CRI1][Stock_Oreo_PreRooted_Easy_Unroot/Root][Safestrap_Preinstalled]
This is for Verizon Only. Other Carriers will be available on their pages from here on out You Do Not Need To Be Rooted To Install This Rom You Must Be On Stock Verizon Oreo Firmware Before Starting This Takes Some Patience To Install All...
forum.xda-developers.com
Then download stock firmware from samfw.com and flash stock firmware in odin using the regular csc file not the home csc one

jrkruse said:
boot too safestrap after you flash above
Then flash zip from this post 2 in this thread
[Rom][VZW_CRI1][Stock_Oreo_PreRooted_Easy_Unroot/Root][Safestrap_Preinstalled]
This is for Verizon Only. Other Carriers will be available on their pages from here on out You Do Not Need To Be Rooted To Install This Rom You Must Be On Stock Verizon Oreo Firmware Before Starting This Takes Some Patience To Install All...
forum.xda-developers.com
Then download stock firmware from samfw.com and flash stock firmware in odin using the regular csc file not the home csc one
Click to expand...
Click to collapse
Rad! Thanks for the help. I actually got it unlocked using another method but here's what I can't understand.
In TWRP I could run FRP Destroyer v1.1 and v3.0. Both reported FRP overwritten with no errors
In Factory Binary I could access the engineering test mode via the secret code in a dialer and I could run a script via the ADB commands to clear the FRP, also which would report back FRP cleared.
But the only thing that actually worked was using an AT&T firmware that still allowed me to access the test mode via emergency dialer then run the ADB FRP clear scripts while in test mode only in a factory firmware.
It did not work if I was using any other firmware even though the programs I was using said it was.

armonic said:
Rad! Thanks for the help. I actually got it unlocked using another method but here's what I can't understand.
In TWRP I could run FRP Destroyer v1.1 and v3.0. Both reported FRP overwritten with no errors
In Factory Binary I could access the engineering test most via the secret code in a dialer and I could run a script via the ADB commands to clear the FRP, also which would report back FRP cleared.
But the only thing that actually worked was using an AT&T firmware that still allowed me to access the test mode via emergency dialer then run the FRP clear while in test mode only in a factory firmware.
It did not work if I was using any other firmware even though the programs I was using said it was.
Click to expand...
Click to collapse
I don’t know anything about the other methods. Also safestrap is not a full version of twrp so some things don’t work in it.

armonic said:
Rad! Thanks for the help. I actually got it unlocked using another method but here's what I can't understand.
In TWRP I could run FRP Destroyer v1.1 and v3.0. Both reported FRP overwritten with no errors
In Factory Binary I could access the engineering test mode via the secret code in a dialer and I could run a script via the ADB commands to clear the FRP, also which would report back FRP cleared.
But the only thing that actually worked was using an AT&T firmware that still allowed me to access the test mode via emergency dialer then run the ADB FRP clear scripts while in test mode only in a factory firmware.
It did not work if I was using any other firmware even though the programs I was using said it was.
Click to expand...
Click to collapse
So were did you get hte at&T firmware?

beastiezee said:
So were did you get hte at&T firmware?
Click to expand...
Click to collapse
A guy on reddit that goes by "instrumentalimix" helped me out a bit.
The file name was Samfw.com_SMG935A_ATT_G935AUCUBCTB1_fac.zip This Rom let me access the emergency dialer and test mode.
Also jumped from Odin over to Z3X SamsungToolPro to install it. Not sure why he didn't flash with Odin.