Database Users

[Q] Recovery is not seandroid enforcing

Just got a Galaxy S4 i9505 rotted it with Kingo Root, installed rashr went to flash something and it installed a recovery and now I get Recovery is not seandroid enforcing, but researched it up and used odin to get past that, but now everytime i try to get into recovery I get that error again.
How can I reflash a recovery that works? I have tried re-rooting again but nothing.
Now it just doenst seem to start just shows the Samgung logo and does nothing.

What exactly are you saying? That you can't boot into recovery?
Rooting has nothing to do with a recovery.
Install TWRP recovery with Odin.
You could also try flashing a bootloader or the stock rom again to make your phone boot. And root properly with CF Auto Root

I meant it like the root program I used that installed the original recovery, I have tried TWRP with odin but it says it is done but still wont boot or go into recovery

How owuld I flash the stock rom?
Was meant to click edit not double post sorry

You have to untick "Auto reboot" in odin. After twrp flashed turn off the phone and use the key combination to boot into recovery.

I think i flashed an older version of twrp cant find a link to a jar for 5.0.1
Ok i managed to get twrp working, but it still alwayss just shows the Samsung logo

Just to clarify one thing here for the audience, "Recovery is not SEAndroid Enforcing" is not an error. All custom recovery images are set to permissive mode to enable them to perform their magic. Since this is a hole in the device's security, the bootloader displays that message to let you know this. A similar message is displayed when a custom kernel is installed, except in that case the message is "Kernel is not SEAndroid Enforcing". Since this is an expected message, the only way to properly get rid of it is to not install a custom recovery or, in the case of the kernel warning, a custom kernel.
@Apexpredator12, with your S4 in its current state, you should flash your stock ROM via Odin and make sure your device is totally operational. After that, use Odin to install CF-Autoroot. DO NOT USE KINGOROOT! With CF-Autoroot you will have your S4 rooted. From there, if you wish you can install a custom recovery, though with the caveat that installing a custom recovery will result in a "Kernel is not SEAndroid Enforcing" message. As mentioned above, this is a normal message and not an error.

Ok thank you, where can I get a stock rom for the i505 only seeing custom ones
I am just so foncused I am used to the SP that was quite easy to do, the version I have is 5.0.1 the stocks I have found are 4.4 etc and just not sure what ones to use without bricking my phone again

If you have a 5.0.1 stock ROM, you can use that. If you really need earlier ROMs, you can get them from samsung-updates.com or sammobile.com.

Yeah I was looking but they seem to be .img files which I cant seem to flash with odin

sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.

Strephon Alkhalikoi said:
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Click to expand...
Click to collapse
I have tried loading a .img with odin but it doesnt seem to detect them

Apexpredator12 said:
I have tried loading a .img with odin but it doesnt seem to detect them
Click to expand...
Click to collapse
You are extracting to much. You can't flash .img with Odin as far as I know. You need to flash the archive in which the .img is packed.

Lennyz1988 said:
You are extracting to much. You can't flash .img with Odin as far as I know. You need to flash the archive in which the .img is packed.
Click to expand...
Click to collapse
I have managed to get stock installed with odin everything works but I cant find CF-Autoroot for galaxy s4 i9505 version 5.0.1

Strephon Alkhalikoi said:
sammobile.com packages the .tar.md5 files in a zip. I don't know about samsung-updates.com, but its img files should be installable via Odin.
Currently sammobile.com is having server issues, but there should be a thread on XDA where you can also download ROMs.
Click to expand...
Click to collapse
EDIT: managed to fix the twrp thanks allot for your help much appreciated.

Galaxy S7 soft bricked

I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus

gus_zernial said:
I have a Galaxy S7 SM-G935FD International Edition which, thru a long sequence of missteps, I have gotten to the point where I can only get to the Samsung Logo Screen or the ODIN download mode (ie. no boot). I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC. But I am unable using any key sequence to get into any TWRP recovery mode - only the two modes above. I tried to convert the Superman rom on this forum to a tar also, but flashing stopped after Aroma at starting NAND write. In my many missteps, what I was trying to accomplish is to debloat and root the phone, at least to gain root access using Android adb. I was able to do this on my previous S6 Edge, but Samsung's vast security barriers have defeated me.
Steps to recover from this mess greatly appreciated ...... hopefully steps I can complete using ODIN ............ thx, Gus
Click to expand...
Click to collapse
Flash Stock Rom via ODIN.

Joku1981 said:
Flash Stock Rom via ODIN.
Click to expand...
Click to collapse
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus

Check this thread http://forum.xda-developers.com/showthread.php?t=3335065 I don't know if you have experience with Odin process. Google it preferably look at YouTube video, if you feel shaky on Odin concepts.
Sent from my SM-G935F using Tapatalk

gus_zernial said:
I was unable to find a stock rom for the international. I found a zipped UK no carrier stock rom. Since ODIN doesn't flash zipped files, I unzipped and saved to a tar file using 7-Zip on Win10. Attempts to flash the tar file using ODIN crashed ODIN on the PC. I'm not sure what's wrong, as I used the same method to flash the zipped TWRP file, and finished with a "success"
I note that I have a message saying kernel is not seandroid enforcing. Somehow I think using ODIN to flash a stock rom is being blocked by some Samsung secutity feature I cannot identify and haven't overcome. Gus
Click to expand...
Click to collapse
1. "I flashed TWRP 3.0.2-0-herolte, apparently successfully, by converting the zipped file I found to a .tar and using ODIN 3.10.7 on a Win10PC." Reflash this FILE via ODIN coz you flashed wrong one and boot in it. Go to next step if doesn't work.
2. Flash Stock ROM via ODIN. SM-G935FD use the same firmwares that SM-G935F.

Careful with ODIN. Make sure you are running on the latest version, as I myself has problems using it for the Galaxy S7 Edge on an offer version
Sent from my SM-G935F using Tapatalk

maybe my question will be weird lol...how can i sofbrick a s7 g930p to be exact and then i can just unbrick flashing the U firmware? thanks.

Custom binary locked by SECURE IMAGE (boot.img)

Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me

Stock Firmware for S7 Edge G935T UVU3APG1
Duggi1663 said:
Hello guys hoping to get some help with this issue. So...I flashed the update for SuperSU on my S7 Edge using FlashFire, after flash it went into boot and this is what i got; "Custom binary blocked by SECURE BOOT (boot.img)" on left cornor and "Security Error: This phone has been flashed with unauthorized software & is locked. Call your phone operator for additional support." I can go into recovery mode, I tried to factory reset but did not work. Any help would be greatly welcome. I am still noob at this so please go ez on me
Click to expand...
Click to collapse
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers

Duggi1663 said:
Update..
So... I decided to flash Stock Firmware and now its working like a charm . hope this helps others with the same situation. Cheers
Click to expand...
Click to collapse
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.

First of all you wanted to Flash SuperSu.... Did you enable Android Debugging.... Then check OEM Unlock?
If not you messed up there...
Next You need use Odin to flash CF-Root. You are now running a patched Kernel and SuperSU
Use TWRP app to install twrp for your device.

i have the same exact problem, been trying to flash stock firmware but cant get it to work. help please!!!! which firmware? can i get a link please!!!!!!!!!!

qwewqa said:
Its not necessary to flash stock, simply reflashing the engboot will suffice, and does not wipe the device.
Click to expand...
Click to collapse
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!

BobTheTenth said:
Hello, having same issue. Didn't realize you can only make backups with flashfire, not actually flash them back with the program too...
I have the original files I installed with Odin, are one of these the engineering boot file? (BL, AP, CP, CSC?)
Or are you talking about something else...? Thanks!
Click to expand...
Click to collapse
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .

qwewqa said:
You flash the engboot file you used to root the device, the one you placed in AP and is around 20 mb in size (not the actual firmware) .
Click to expand...
Click to collapse
Thanks!

Recovery locked

Installing TWRP on Galaxy S4 GT-I9515 (Value Edition)

Hello everyone,
I was thinking about installing Lineage OS on my Samsung Galaxy S4 GT-I9515 (Value Edition) currently running Stock Android Version 5.0.1 without root.
Is the version of Lineage OS and TWRP I found at https://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-cm14-1-galaxy-s4-jfvelte-gt-i9515-t3534552 appropriate for that purpose?
Now, my confusion arises from the fact that different guides seem to give incomplete or even contradictory instructions on how to approach that. As a first step, I need to install a custom recovery, such as TWRP:
Does this require my device to be rooted?
Some guides apparently require my bootloader to be unlocked; Is this necessary? If so, how do I do that?
Other guides suggest that I use Odin. Is this the correct approach? Does my bootloader need to be unlocked for that method? Is a root required?
Anything else I should pay attention to?
Thank you very much in advance

You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin

Not able to root S4 GT-I9515
TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
I tried to flash CF-Auto-Root on my phone after completing the flash till reset on odin phone gets restarted and is showing following messages on top left corner on the samsung s4 logo screen
recovery booting....
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
it is not going any further than this please help.

TheFixItMan said:
You need to find a guide for your phone
Different phones have different processes
For example Motorola phones require you to unlock the bootloader where as Samsung phones Iv worked with you don't
Some devices you have to root first before you can flash twrp while others you flash twrp first then root
For most Samsung phones around the age of yours you can root using CF-Auto-Root
This is done via odin and all you do is put your phone in download mode load the img file into odin & flash
The same is true for flashing twrp
Here are the files for your phone
CF-Auto-Root
TWRP
Flash each image in odin
Click to expand...
Click to collapse
the twrp file bricks the phone

raffux3 said:
the twrp file bricks the phone
Click to expand...
Click to collapse
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google

TheFixItMan said:
What do you mean by brick?
Does the twrp boot?
You must boot twrp straight after it's flashed - if you don't and your phone starts to boot you need to reflash it (once booted to twrp for the first time the recovery will stick)
Also if you swipe to allow modifications in twrp your rom may not boot unless you disable dm-verity - this can be done with a root zip eg CF-Auto-Root or magisk
Remember you may need to do other steps like enabling adb debugging & oem unlock before using CF-Auto-Root
You also may need to root before flashing twrp
That is the twrp for the S4 GT-I9515 - if you have a different variant it will not work
If you have a different model of S4 check the twrp website to see if there is an official version
I don't own your device - I'm sure there's guides that will you step by step process if you Google
Click to expand...
Click to collapse
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)

raffux3 said:
when you install it with odin, it starts for some seconds and stops with a FAIL. So the smartphone become bricked!!! I have the same model of s4 (I9515)
Click to expand...
Click to collapse
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that

TheFixItMan said:
Flashing a recovery should not brick your device - you are just replacing stock recovery with a custom one - your phone should boot regardless but anyway
I assume you have enabled USB debugging - enabled oem unlock (if it's on your device) and flashed CF-Auto-Root first
I also assume you are flashing the tar image in the AP section of odin (you may need to Unzip to get filename.tar)
If you have done all the above search Google for a step by step guide for your device
Since I don't own this device I can't offer anymore support than that
Click to expand...
Click to collapse
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always

raffux3 said:
of course. i have installed root before and after I tried to install twrp recovery but it failed. Now I don't know how I can do to restore my s4. :crying:
I'm trying all prcedures for install the original firmware but odin fails always
Click to expand...
Click to collapse
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)

TheFixItMan said:
Long as it's the correct firmware for the device no reason why it wouldn't flash
Check download mode & make sure that the model number matches the firmware
If the firmware is also failing to flash I would guess there is a problem with your setup rather than the files (assuming the files are correct)
Click to expand...
Click to collapse
I have re-installed the usb drivers and odin works fine finally. I will try to root and install twrp again...thank you for support

[Q] Cant flash Stock rom anymore

Hello everybody,
I got a Samsung Galaxy S7 Edge (SM-G935F) DBT version and flashed a Custom ROM (Firmware? idk the difference).
I did that like this: youtube.com/watch?v=_1ofpLHMVvA
Unfortunately there were a few problems there, like the camera is awful now (Bad quality and other camera apps didnt made it better).
So now I want back my Stock ROM. (Yes, Unfortunately I didnt made a Backup)
But I cant get it back, neither with TWRP or with Odin.
At Odin its stops at system.img and fails than and at TWRP I guess I used the wrong Rom because is said Zip file is corrupt!.
The following Stock ROM did I use for Odin and TWRP: updato.com/firmware-archive-select-model?record=2A12F0CE03CD11E7963AFA163EE8F90B
At Odin I unziped it and added it the right way: (BL, AL, CP and CSC).
At TWRP I didnt unziped it and used it like it is.
I hope you can help me there.
I have already made the following:
Changed USB Port
Changed USB cabel
Used Smart Switch
And yes, I can still install custom roms like LineageOS and Resurrection easily via TWRP.
Greetings, Darkatzu.

bump

Darkatzu said:
bump
Click to expand...
Click to collapse
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs

shah22 said:
Which procedure you followed to root and install custom rom?
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Is that important? I dont think so...

Darkatzu said:
Is that important? I dont think so...
Click to expand...
Click to collapse
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs

shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
shah22 said:
so you need to flash latest nougat for your country/region alongside twrp
Click to expand...
Click to collapse
So far so good.
shah22 said:
you can download latest stock firmware for your region from samfirm application or updato
Click to expand...
Click to collapse
As I did. (both)
shah22 said:
also download odin version 3.13.1, latest twrp recovery
Click to expand...
Click to collapse
Already done.
shah22 said:
super su and no verity opt encrypt from here on xda forums
Click to expand...
Click to collapse
Ok I didnt done that, but now I got I did.
shah22 said:
first check and enable oem unlock
Click to expand...
Click to collapse
Done.
shah22 said:
flash stock rom
Click to expand...
Click to collapse
Aaaand failed as I described already.

Darkatzu said:
I showed a Video Tutorial how I did that.
The reason why I did that, is for me: Not important.
And yes, I did OEM unlock.
So far so good.
As I did. (both)
Already done.
Ok I didnt done that, but now I got I did.
Done.
Aaaand failed as I described already.
Click to expand...
Click to collapse
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs

shah22 said:
Maybe you are using an older bootloader ? Can't say for sure whats causing it, the method you used above I think required system modifications, but you are using a march 2017 stock rom, so it looks updato don't has V2 bootloader firmwares for DBT, problems may happen when flashing an older bootloader on a newer one, it could also be your pc or other hardware problem, but in case try again and download samfirm from here : https://forum.xda-developers.com/attachment.php?attachmentid=3803841
Enter DBT as your region and model SM-G935F , it will download the latest stock available, be sure option for auto decrypt, check crc32 and binary nature are ticked.
After that check oem unlock and usb debugging is enabled and follow the steps :
1. Put phone in download mode, use original usb cable, and make sure pc usb port is working correctly. Also phone must be charged above 50%.
2. Download odin 3.13.1 from here https://forum.xda-developers.com/attachment.php?attachmentid=4431597&d=1519662712
Latest twrp available https://eu.dl.twrp.me/hero2lte/twrp-3.2.1-1-hero2lte.img.tar.html
Latest no verity opt encrypt https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
Latest stable super su https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
3. Put phone in download mode, extract the firmware downloaded above from samfirm tool and put the respective files in their boxes, use CSC and NOT HOME_CSC. Make sure no option other than F.reset time is ticked in odin options. Begin the flash procedure. After it is completed, don't reboot and place twrp zip downloaded from above in the AP tab of odin. After it is completed, stay in download mode and hold power+home+vol down to reboot from download mode and immediately switch to vol up button to boot in twrp recovery menu.
4. In twrp recovery menu, you need to swipe for system modifications or tick read only ( if you previously allowed for system modifications then you can do it again it doesn't matter, but if you previously didn't swipe for system modifications then tick read only and download systemless zip from https://forum.xda-developers.com/s7-edge/development/samsung-systemless-devbase-encryption-t3517178 )
I will recommend this as you won't need to flash dm verity.
5. Now, go to wipe> format data in twrp recovery, after its done, flash super su and system less zip through twrp to get system less root if you don't want to get dm verity error hassle when flashing stock roms OR flash super su and no verity opt encrypt if you already have allowed system modifications. After that reboot. It may take sometime.
Also to note if you never allowed system modifications before in twrp, and you don't want to root either, then you can safely flash stock without flashing twrp or going through further steps.
This is what I could best explain according to my limited knowledge, if you still fail to flash stock in odin, then I am not sure it may be your pc or other hardware problem and you may need a repair box, try checking on another pc or some expert user to help. Good Luck.
These steps are only for installing stock rom back on previously rooted S7 edge devices using custom roms and for rooting a stock rom.. and only applies to SM-G935F
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
As I already said: As I did. (both)
I already tried with samfire.
Same error.

Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs

shah22 said:
Sorry I couldn't be much help. Does it always stucks in odin at system.img? Looks like its a hardware problem in your pc/usb ports or phone's usb jack. Try getting your phone checked by a repairer, flashing from another pc or changing usb cable. Also try running odin as an admin or try with an older odin version. Good Luck
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Yes it suck always at system.img!
And I can easily flash custom roms via. TWRP.
And I can flash TWRP via Odin without any errors.
Do u even read my post?
Changed USB cabel
Click to expand...
Click to collapse
And yes, I changed PC 2 and yes tryed other versions of Odin LIKE where AP is named as PDA.

Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs

shah22 said:
Strange thing if you could flash recovery but not the stock rom, looks like you need to get it checked by a tech. But as a last resort did you tried using pit file and repartition ticked? To get the pit file extract the CSC file and you will find .pit file there, open pit tab in latest odin and select that pit file, then tick repartition box and proceed to flash with all other files selected in their respective boxes. If its still the same then I guess I can be of no more help. Cheers !
!! Warning : Using pit file is never recommended and it could brick your phone permanently if there is any power outage/usb disconnection during flashing with pit, it is used to correct file system partitions if they are changed/corrupted. Its better to outweigh benefits with potential danger. Also a pit file will erase all partitions first, then write flash data from beginning and if you again stuck at system.img when using pit file, you will be left with a permanent brick. So I will recommend to get it checked by a tech if you want stock rom that bad and don't do any risky thing with your pricey phone
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
A tech is 2 expensive for me.
And yes, I already did it with pit file and the whole CSC file.

#push

#push

#push

#push

Darkatzu said:
#push
Click to expand...
Click to collapse
try with chimeratool, it worked for me, l use a free license to download the firm from server and install it

#push

shah22 said:
It is, because you will need no verity opt encrypt to flash too alongside official stock rom in order to use stock rom if you rooted by system modification method, with oreo 8.0 I think no verity zip is not working, so you need to flash latest nougat for your country/region alongside twrp , no verity zip and super su, you can download latest stock firmware for your region from samfirm application or updato, also download odin version 3.13.1, latest twrp recovery, super su and no verity opt encrypt from here on xda forums, first check and enable oem unlock, flash stock rom and then flash twrp through odin, then boot in twrp recovery and flash no verity and super su zips, to get detailed info on above steps search the forums. AND PLEASE TELL WHATS ASKED IF YOU WANT TO GET HELPED.
!! NOTE : IF YOU ROOTED FIRST TIME BY SYSTEM MODIFICATION METHOD, AND THEN INSTALLED CUSTOM ROM, THEN FLASHING STOCK ROM BACK WILL PUT YOU ON A DM VERITY ERROR. ALWAYS REMEMBER TO ENABLE OEM UNLOCK IN DEVELOPER OPTIONS BEFORE DOING ANYTHING!
HAVING OEM UNLOCK DISABLED AND THEN ROOTING VIA SYSTEM MODIFICATION METHOD, AND THEN FLASHING STOCK ROM WILL PUT YOU IN A HARD BRICK SITUATION WITH BOTH DM VERITY ERROR AND CUSTOM BINARY BLOCKED ERROR !!
As far as I know the above situation has no solution if you get into this mess and only a memory swap on board or some box can fix this. I know many users here on xda are stuck on this situation. Some users said they fixed this by using nand erase all and re partition using pit file options during flashing in odin, but I really doubt enabling these options will solve this if not making problems worse. Anyone is welcomed to correct me if the above situation has any solution. BUT THAT IS WHY SYSTEMLESS ROOT IS THERE TO AVOID ALL THIS...
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks

hikouka71 said:
hi, i used this thread to root my regular s7 from sprint, am i going to be able to just flash the latest firmware back to stock and be good to go or am i hosed?
thanks
Click to expand...
Click to collapse
No, i don't think so as you already flashed engineering kernel, i won't recommend but if you already tried, do post your results ..
Sent from my S7 Edge using XDA Labs