Custom binary blocked by cc mode - Samsung Galaxy S7 Edge Questions and Answers

Custom binary blocked by cc mode - Samsung Galaxy S7 Edge Questions and Answers

Hi
I installed TWRP and then Renovate ROM.
It worked great....then I took a flight. When the phone restarted it says "custom binary blocked by cc mode"
Please can you let me know how to remove. TWRP gives me a terminal, and my SD card can copy on any file.
I see the command "devmem 0xF91CF8C 32 0xFF000000" can fix but I don't have devmem. Where can I get this file/program or how can I remove "cc mode"
Please help

Deansmithok said:
Hi
I installed TWRP and then Renovate ROM.
It worked great....then I took a flight. When the phone restarted it says "custom binary blocked by cc mode"
Please can you let me know how to remove. TWRP gives me a terminal, and my SD card can copy on any file.
I see the command "devmem 0xF91CF8C 32 0xFF000000" can fix but I don't have devmem. Where can I get this file/program or how can I remove "cc mode"
Please help
Click to expand...
Click to collapse
did u enable Enable OEM Unlock before flashing the recovery?? or did u just flash it.... the solution i found was to reflash stock rom then probably go back and flash the same rom again and re-do what u did but before all that enable OEM unlock as soon as u flash stock firmware
note im not rooted or on another rom simply trying to help https://www.s7fanclub.com/2016/05/fix-custom-binary-blocked-frp-lock-galaxy-s7-edge.html is this the same error??

FRP lock vs CC mode brick
Hi
I wish it was an frp lock.
But if I wipe then entire device it still says "blocked by cc mode".
If I didn't have TWRP installed then I would have lost the phone.
To fix my phone I need /dev/mom which can called by "busybox devmem", but I don't have this and am looking for it. Once I get it I should add it to the SD and then copy across.
Thanks for your support.
Regards

Did you find a solution yet? I have the error for about 3 months and could not use my phone since that

Any fix?
i have this error in my galaxy s7 plz reply

FIXED
I fixed it.
This is the solution:
1.- TWRP INSTALLED
2.- Download your rom
3.- Extract boot.img and recovery.img from AP file from your rom using winrar.
4.- Copy boot.img and recovery.img to your phone.
5.- Flash FIRST boot.img then flash recovery.img
Now try to boot to download mode and you will see that "Download is blocked by cc mode" is not anymore, flash your rom with odin.
Thats all!

Why did this error occurred in first place ? If it isn't due to oem unlock disabled then its a new sort of error.
Sent from my S7 Edge using XDA Labs

Fabreitor said:
I fixed it.
This is the solution:
1.- TWRP INSTALLED
2.- Download your rom
3.- Extract boot.img and recovery.img from AP file from your rom using winrar.
4.- Copy boot.img and recovery.img to your phone.
5.- Flash FIRST boot.img then flash recovery.img
Now try to boot to download mode and you will see that "Download is blocked by cc mode" is not anymore, flash your rom with odin.
Thats all!
Click to expand...
Click to collapse
Does this really work? If we flash the stock recovery we will loose any facility to recover the phone back. Normally the CC Mode is enabled by an MDM which pushes a security policy like XenMobile.

Confirmed works perfectly.
Sent from my SM-G955F using Tapatalk

Yep it works
---------- Post added at 11:14 PM ---------- Previous post was at 11:04 PM ----------
Sorry for not answering, i recently read it

Related

Help installing a ROM.zip from ASUS on ZE500KL

Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks

Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?

Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed

Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.

kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.

Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip

Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.

Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.

Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172

I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??

Can you try to ADB Sideload the ASUS ROM?

sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.

Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.

If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.

up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:

2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases

Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy

I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script

Hi,
I'll test it, and will give feed-back
Thanks

ZE550KL bricked ?

Hi,
I was at work Sunday night when the phone offers me an update, not wanting to lose my data I re-growth that has Tuesday morning during my last round (which takes me roughly 25/30 minutes ). So I run the update and go round when I come back I have the phone on the screen of blocked boot ...
Considering I'm looking since yesterday, I have already tried many tutorials that did not work.
I tried everything flashed like to start from zero but nothing worked. I have every time a message like: failed can't install image not signed OR dtb not found ...
I have access at fastboot and nothing else.
There's way to save this phone I for 3 months or it is good to wedge a table ?
Thx in advance
edit :
ok, i do this
http://www.asus-zenfone.com/2015/10/how-to-root-asus-zenfone-2-laser-ze500kl.html
and this
http://forum.xda-developers.com/showpost.php?p=66894780&postcount=5
and i have now acces to recovery mode
Edit 2 :
http://www.asuszenfoneblog.com/2015/04/how-to-flash-asus-zenfone-2-via-adb.html with the firware Version V13.10.7.1(Andriod M) https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
but after reboot i have the message : ERROR : Can't load invalid boot image !
i lose th recovery and i can't flash the boot ( remote dtb not found ) ...
edit 3 :
the phone has restarts with the original firmware but I have so manipulated that I do not know what I did
I remember using the following links : http://www.asus-zenfone.com/2015/09/how-to-flash-asus-zenfone-2-laser.html ans the stock rom for 550KL
when I reinstall the rom of origin, such would not boot and I had to boot the mod_boot.img picture (Flashtool boot mod_boot.img), which launches the phone and now more problem. It remains to remove the root which should be easier than the rest.

@Genux888 This link takes to ZE500KL's firmware downloads https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
Your phone model is ZE550KL but you first attempted to flash MM ROM of ZE500KL
Thats why you got error: invalid boot.img and you lost recovery.
I don't know where you got mod_boot.img from. Neverthless, here's the simplest fix-
1. Download ZE550KL's Stock_boot_recovery.zip
This zip contains stock signed recovery.img and boot.img. Extract it and copy both .img files to the folder where you have adb and fastboot files.
Download correct firmware for your ZE550KL of the correct SKU. You can find your SKU on your phone's box.
WW SKU : Download ZE550KL's firmware v1.17.40.1531 for WW SKU only
Let me know if your phone's SKU is not WW
Copy the firmware zip (UL-Z00L-WW-1.17.40.1531-user.zip) to your external sd card.
2. Connect your phone to computer and Reboot phone to fastboot mode.
3. Now run the following commands
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot oem reboot-recovery
3. Third command should reboot your phone to recovery mode.
Now, in recovery mode-
A) select "wipe cache partition" then select yes
B) select "apply update from sdcard" then select "UL-Z00L-WW-1.17.40.1531-user.zip" and finally select "yes"

stuck at verifying update package

MITHI-N said:
stuck at verifying update package
Click to expand...
Click to collapse
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.

sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Hi can you put a link to OTA, I tried searching for it but could only get the full firmware from the asus website.

sziraqui said:
Reboot to fastboot mode (instructions in post#1) and execute this command
Code:
fastboot erase system
Then flash the ota from recovery.
Click to expand...
Click to collapse
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things

MITHI-N said:
Removed, putback battery & followed all steps, successfully installed 1531 rom
Then upgraded to Asus Marshmellow, Everything working.
But when I try to clear data & cache from new recovery I get couple of errors stating unable to mount /asdf & few other things
Click to expand...
Click to collapse
I did the following-
Input: "Wipe cache partition"
Output: E: unable to mount /asdf (invalid argument)
Input : "mount /system"
Input: "wipe cache partition"
Output: Cache wipe complete
E: unable to mount /asdf
E: Can't open /asdf/recovery/last_log
This shows that I am able to wipe cache after mounting /system (though it doesnt make sense)
I didn't wipe data as I don't want to setup my device again. You may try if wiping data works after mounting /system. Alternatively, you can flash stock 1.15's recovery (download from post #2)
and flash in fastboot mode using
Code:
fastboot flash recovery recovery.img
(assuming you recovery.img file is present in the folder where you have fastboot files)
And, here on XDA, we hit "thanks" good button if a post was helpful to us.

Sorry to reply so late but I managed to unlock my phone has put version 5.0, the update to 6.0, UNLOCK the boot, root the phone and install the TWRP may close 2 or 3 hours after my last post.
thank you.

i really like it when people post all the steps taken and links in their problem posts.
this is great.
(no, that is NOT sarcasm)

The best solution out there for zoold 550kl
This is the best answer for the rooted asus zenfone 2 550kl for upgrading to marshmellow stock .Thank you...

Help
@sziraqui My phone is in a bootloop and I honestly know pretty much nothing as to how to fix it.. I know it's the ZE551KL, but that's pretty much it. Is there any way youcan help me out? thanks in advance

Stock recovery for MM?
Anyone have stock recovery for MM upgrade from LP?

Problem Not Solved
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..

I've seen you've tried a lot.
I'd suggest you try this... As long as you can send your phone to fastboot and can pc/add your way through you'll be able to unbrick it. This takes a bit of time as you'll be dealing with two huge downloads (system.img and stock rom) but it should do the trick.
Follow the guide here:
https://www.asus.com/zentalk/thread-80274-1-1.html
---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------
utkarshdev20 said:
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
The guide at https://www.asus.com/zentalk/thread-80274-1-1.html talks about flashing boot.img first then a huge (1.7GB) system.img second then recovery.img last.
So it could mean the boot.img and system.img needs to be dealt with first before you have any chances of getting your recovery to work.
Follow the steps closely, I've been able to fix a brick with it twice.

NO way to boot into Recovery or Fastboot!!!!!!!!!!!!!
Phone got bricked!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
When connected to PC(Windows), I only get 8 local disk partitons (ext4) asking to format!!!!!!!!!!!
And one with image partition(BOOT)
What to do now to regain access to either fastboot or to recovery!!!!!!!!!!!!!!!!!
PLEASE Reply!!!!!!!!!!!!!!!!!!

utkarshdev20 said:
I am Also facing same type of problem but the difference is :
- I am only able to enter fastboot mode only when i am connecting my phone to pc via datacable.
- After flashing recovery.img and boot.img also i am not be able to go to recovery mode..
Can someone please Help..
Click to expand...
Click to collapse
I can help you but first i neef some info about your phone..how it got bricked?was your phone rooted?

[ZE500KL] Can't load invalid boot image!

Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !

CzeroXCI said:
Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !
Click to expand...
Click to collapse
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img

Muminek111 said:
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img
Click to expand...
Click to collapse
My phone version is 13.10.10.34 can I flash this boot image????

Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.

Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Muminek111 said:
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible

Sharashchandra said:
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
Click to expand...
Click to collapse
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.

Muminek111 said:
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.
Click to expand...
Click to collapse
After flashing also the same problem persists
Thankyou

Sharashchandra said:
After flashing also the same problem persists
Thankyou
Click to expand...
Click to collapse
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.

Hello M having ASUS ZenFone 2 laser ze550kl model with marshmallow version.. I tried to unlock boot loader but m unable to do so.. Please help me..

just flash this zip https://yadi.sk/d/0NFnYyTG36XzWv using TWRP recovery(in menu "install").
just flash this..
it works perfectly fine

make sure you use the latest TWRP for your device.

Hey bro you can watch this video and follow the steps then your phone will definitely right back.....
https://youtu.be/_Ca10N-XQJk

I have also this problem .
But i can't enter in the recovery menu , it doesn't work.
P.S. sorry for my english

Muminek111 said:
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.
Click to expand...
Click to collapse
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
UPDATE:
=======
Aaaaaanyway, I downloaded 2 kinds of stock roms from the Asus official site;
1. UL-ASUS_Z00E-WW-13.1010.1612.53-user (the latest:- M) and...
2. UL-ASUS_Z00E-WW-12.8.5.222-user (and older version:- actually, the pre-installed version)
after flashing the first one over and over again; after and before wiping my phone and cache over and over again, NOTHING HAPPENED; no change!!! still kept throwing back the error message.
So I decided to flash the second one, and for a split second, I was happy cos the error had disappear...only for me to wait for eternity and in vain for the phone to boot (that is, even if it could). suddenly, I realized what had happen....the phone couldn't boot pass the ASUS logo, neither could it load recovery again (as it used to). It only boots into ADB, but of course, that will require USB DEBUG MODE to be ON to be able for the phone to be detected through ADB (which is far from possible due to the numerous wipes I performed).
CURRENT SITUATION: I can't ADB, I can't get into recovery, and I'm stacked with the logo at boot......when the phone is completely turned off and placed on charge, the battery shows an empty battery with the loading (status) sign (but it charges, even without the OS being able to display the process).
Don't know whether anyone is facing same, or I can start a new thread with this? and I need help before taking it to a 3rd party repairs (since we don't hv Asus customer care in our country yet).
Will be glad to find help.
PS: The computer still detects the phone as an ADB Android device, and to me, that's a beacon of hope.

abodan09 said:
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
Click to expand...
Click to collapse
This problem will resolve to open the bootloader.

Muminek111 said:
This problem will resolve to open the bootloader.
Click to expand...
Click to collapse
I don't think I got that...do u mind explaining further??? thank you!

abodan09 said:
I don't think I got that...do u mind explaining further??? thank you!
Click to expand...
Click to collapse
You can not flash the older version stock rom from stock recovery.
Flash latest stock rom.
Download this twrp: https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Download this ulock bootloader: https://drive.google.com/file/d/0B7F3ZXr565GkMWNwUkZJa1BUVUU/view?usp=drivesdk
Download this supersu: https://drive.google.com/file/d/0B7F3ZXr565GkOTcxb2VPbmQzT2M/view?usp=drivesdk
Restart to fasboot mode.
Command: fastboot boot twrp.img
From twrp flash first zip ulock bootloder then flash zip supersu.
Reboot.
---------- Post added at 08:39 PM ---------- Previous post was at 08:15 PM ----------
Android 6
Must be first opened bootloader then can modified boot image.

Same ERROR,you just need to flash the unlock bootloader file
UnlockBL.zip
Click to expand...
Click to collapse
https://goo.gl/nVq9e7

i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..

christin7 said:
i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..
Click to expand...
Click to collapse
Test:
Try to flash boot.img of your firmware version from fastboot mode but use command: fastboot boot boot.img. Reboot system. Then let me know.

Zenfone 3 doesn't boot to Android

Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*

SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I used to be difficult to use TWRP menu, then the menu advanced Wipe Wipe then select all topics except the MicroSD and then manage Otg Wipe it !! Flash Stock Recovery to be done to make Flash official rom first official rom files onto the MicroSD example, I was. UL-ASUS_Z012D-WW-13.20.10.79-user. To change its name Then insert the MicroSD MOFD_SDUPDATE Recovry Mode, then select update to zip and then choose File. "MOFD_SDUPDATE.zip" I will wait a little longer for the update firmware and set up virtually everything is not lost through the OTA.
ผมเคยเป็นแก้ไม่ยากใช้ TWRP แล้วเข้าเมนู Wipe แล้วเข้าเมนู advanced Wipe ทำการเลือกทุกหัวข้อ ยกเว้น MicroSD และ Otg แล้วจัดการ Wipe ครับ!! เสร็จแล้วให้ทำการ Flash Stock Recovery เพื่อที่จะใช้ Flash official rom ก่อนอื่นทำไฟล์ official rom ลงไปยัง MicroSD ผมยกตัวอย่างเป็น UL-ASUS_Z012D-WW-13.20.10.79-user ให้เปลี่ยนชื่อเป็น MOFD_SDUPDATE แล้วนำใส่ MicroSD แล้วเข้า Recovry Mode แล้วเลือก update to zip แล้วทำการเลือกไฟล์ "MOFD_SDUPDATE.zip" แล้วรอสักพักอาจจะนานหน่อยเพราะเป็นการ update firmware ข้อมูลและการตั้งค่าทุกอย่างจะไม่หายเสมือนอัพผ ่าน OTA

I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom

SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
I got the same issue, where did you get these files?

roosevelt84 said:
I got the same issue, where did you get these files?
Click to expand...
Click to collapse
I have the exact same error. Same here. Please someone can post download link.

SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I found a solution, and now my ZF3 is working but its showing a second screen with a error when it boots.
1 - download a zip file rom from asus site
2 - open it with winrar or another of your choice
3 - go to \META-INF\com\google\android
4 - open the updater-script with a text editor
5 - search for all the words WW_Phone and replace it for omni_ze552kl
6 - save the change and close, update the file inside the compressed zip
7 - put the zip rom inside your phone and flash it through twrp, done!
*sorry about english, its not my native lang.

Hi SuperDizor,
The issues you are having are both caused by the installation of TWRP 3.0.2. that was compiled for the Zenfone 3 using omni_ze55kl as the device type instead of WW_ZE552KL or CN_ZE552KL. I assume that the person that compiled it tried to make TWRP as universal as possible (instead of making two different versions, one for each device type - the TWRP code would have been the same except for this string...). However, the updater checks for this device type string and fails (unless you modify the updater config file as described in the post above). This is also why flashing stock recovery solved your issue.
The second error message you have, the one with dm-verity not being in enforcing mode was caused by having you install TWRP and allowing it to modify the system partition. This was necessary in the past but not anymore. When you flash TWRP, the first time you start it, it ask for your permission the make the system read-write, and you should refuse, as TWRP will function anyway and you will not get the dm-verity error. The dm-verity thingy is a software module in the bootloader (aboot to be precise) that checks the integrity of the system partition. TWRP has to force it in non-enforcing mode since it modifies the system partition and your device would not boot if it left dm-verity in enforcing mode. When you don't let TWRP modify the system partition (ie staying read-only), it does not change the dm-verity mode and you don't get warning messages. Don't worry, TWRP will still enable you to root your device and do whatever it does even if it is in "read only" mode.
Hope this helps !

I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.

Same happened with my device too. How did you fix it? Can you please let me know the procedure for same.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Niemer said:
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Click to expand...
Click to collapse
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same. Thanks

SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
but how to flash? its not booting in recovery mode.

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

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

Database Users

welcome