Database Users

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?

G935f nougat root problem

i have tried every twrp but phone stucks on galaxy s7edge screen when trying to access recovery ? plz anybody ?

i have done many posts related to my s7edge g935f , its just kept in the cupboard and cant use it from several months because of the dmverity error , i need to root it and use custom rom plz ?

Put the phone in download mode, use Samsung Smartswitch to reinstall stock rom

surfer3000 said:
Put the phone in download mode, use Samsung Smartswitch to reinstall stock rom
Click to expand...
Click to collapse
i have already done that , it stuck on modem part , secure check radio fail and when i flash without modem , it successfully flashed but root issue , when i flash twrp , it doesnt boot into into twrp and stuck on logo?

I do not believe that you see a "modem" part when using smart switch? Otherwise use Samsung Kies for S7 edge. And do the Firmware Upgrade and Initialization menu item

surfer3000 said:
I do not believe that you see a "modem" part when using smart switch? Otherwise use Samsung Kies for S7 edge. And do the Firmware Upgrade and Initialization menu item
Click to expand...
Click to collapse
i have done every try , it doesn't accept the modem part , i am teally confused about it , so much long time passed and just kept the phone useless, samsung switch is showing it g935f o2u model but not accepting o2u firmware too

suhaibahmad said:
i have done every try , it doesn't accept the modem part , i am teally confused about it , so much long time passed and just kept the phone useless, samsung switch is showing it g935f o2u model but not accepting o2u firmware too
Click to expand...
Click to collapse
Mmmm, before u flash TWRP, u should enable oem unlock on developer option

aditia581999 said:
Mmmm, before u flash TWRP, u should enable oem unlock on developer option
Click to expand...
Click to collapse
yes i have enabled that and also usb debugging

What to do : Reflash the stock firmware , after that is completed , turn off the phone , and install on your pc : the No verify Opt encrypt 5.0 from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
And the SuperSu file from here :
https://download.chainfire.eu/supersu
Now go download the latest Odin, and connect your phone.
Flash the Twrp 3.1.0.0 ( be aware to choose the file for Hero2lte) and reboot to recovery.
DO NOT LET IT BOOT INTO THE SYSTEM.
IF IT DOES , IMEDIATLEY CLOSE THE PHONE AND BOOT INTO RECOVERY .
Once you are in recovery , firstly go to wipe and do a factory reset .
Then connect your s7E to the PC while you are in the TWRP , and copy the SuperSu file and the verity opt oncryption to the storage.
Note: if you have an SD card inserted , copy the files to the SD not the internal storage.
Now , pay attention , If you don't do the next steps in the right order , you may brick your beautiful 800$ phone.
So pay attention , you have to firstly run the No verity encrypt file.
After it's done, go back >reboot>reboot in recovery.
Now search the file and run it (the SuperSu file)
It will take a bit longer to flash the SuperSu.
After it's done , reboot
Note: your phone should reboot 2 times , If it doesn't or it reboots more than 3 times, CLOSE your phone , and repeat the whole process.
IF your phone reboots 2 times , your are good to go .
The first BOOT May take some time (usually around 6 minutes) and it may loop a couple times, DO NOT INTERRUPT THE PROCES !
IF your phone boots up successfully, configure it and run a root checker , it should say : congratulations your device is rooted.
IF IT doesn't, well you have had to mess something up during the process.
Hope that helped , let me know if it did

allahTch said:
What to do : Reflash the stock firmware , after that is completed , turn off the phone , and install on your pc : the No verify Opt encrypt 5.0 from here:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.0.zip
And the SuperSu file from here :
https://download.chainfire.eu/supersu
Now go download the latest Odin, and connect your phone.
Flash the Twrp 3.1.0.0 ( be aware to choose the file for Hero2lte) and reboot to recovery.
DO NOT LET IT BOOT INTO THE SYSTEM.
IF IT DOES , IMEDIATLEY CLOSE THE PHONE AND BOOT INTO RECOVERY .
Once you are in recovery , firstly go to wipe and do a factory reset .
Then connect your s7E to the PC while you are in the TWRP , and copy the SuperSu file and the verity opt oncryption to the storage.
Note: if you have an SD card inserted , copy the files to the SD not the internal storage.
Now , pay attention , If you don't do the next steps in the right order , you may brick your beautiful 800$ phone.
So pay attention , you have to firstly run the No verity encrypt file.
After it's done, go back >reboot>reboot in recovery.
Now search the file and run it (the SuperSu file)
It will take a bit longer to flash the SuperSu.
After it's done , reboot
Note: your phone should reboot 2 times , If it doesn't or it reboots more than 3 times, CLOSE your phone , and repeat the whole process.
IF your phone reboots 2 times , your are good to go .
The first BOOT May take some time (usually around 6 minutes) and it may loop a couple times, DO NOT INTERRUPT THE PROCES !
IF your phone boots up successfully, configure it and run a root checker , it should say : congratulations your device is rooted.
IF IT doesn't, well you have had to mess something up during the process.
Hope that helped , let me know if it did
Click to expand...
Click to collapse
thanks for such a nice tutorial , the problem is my phone is o2u and flashing issue in the modem part even i have tried with samsung switch , anyhow that is not a big issue now whenever i only flash ap , the phone boots successfully and i can enable oem unlocking and developer option and when i flash twrp and wants to boot into it , the phone stuck there

suhaibahmad said:
thanks for such a nice tutorial , the problem is my phone is o2u and flashing issue in the modem part even i have tried with samsung switch , anyhow that is not a big issue now whenever i only flash ap , the phone boots successfully and i can enable oem unlocking and developer option and when i flash twrp and wants to boot into it , the phone stuck there
Click to expand...
Click to collapse
I had the same issue to fix.
open smart switch and use the emergency initialization and recovery feature.
it will ask for your model and serial number which is on a sticker on the back of your phone.

Cosmic Blue said:
I had the same issue to fix.
open smart switch and use the emergency initialization and recovery feature.
it will ask for your model and serial number which is on a sticker on the back of your phone.
Click to expand...
Click to collapse
I have tried that , that also stucks in the modem part and give radio fail secure check error , i cant even flash it , i was thinking i will root it and install a custom rom but it cant boot to twrp , and if i just flash the AP part then the device boots successfully and the imei and baseband everything ok . Just the hidden codes not work , its really a weird issue , im really confused about it

suhaibahmad. When you refer to "whenever I only flash AP"you are referring to using ODIN, NOT SMARTSWITCH. There is a difference.

surfer3000 said:
suhaibahmad. When you refer to "whenever I only flash AP"you are referring to using ODIN, NOT SMARTSWITCH. There is a difference.
Click to expand...
Click to collapse
on smartswitch it stucks in the modem part and flash radio fail error on the screen . and now come to odin , if i just flash AP in odin then the phone boots successfully but not good performance and cant even root it

Plz anybody help , my phone is just a piece of .....

S7 edge bootloop

Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do

nonechap said:
Hi,
I realy need your help,
I have a S7 edge who is stuck at the samsung logo.
I have flashed some stock rom (all in 7.0) via odin 3.12 after a wipe factory but nothing. So i decided to try it with Kies and smartSwitch but still nothing.
I have access to recovery and download mode.
FRP lock: On
The phone is not rooted, and the usb debugging not enabled.
The phone print this in the download mode:
ODIN MODE
Download speed: FAST
Product-Name: SM-G935F
Current Binary: Samsung Official
System Status: Custom
FRP lock: ON
Secure Downlaod: Enabled
Warranty Void: 0(0x000)
RP SWREV: B:1 K:0 S:0
After the installation of the flashed rom in the download mode, the phone reboot with a blue screen, a progress bar but it stop to 32%, and then it is printed "erasing.." and the phone reboot and is still stuck.
I have re-tryed with Kies, now the phone is with a green screen with 2 white Gears : "android is starting" but it is still stuck (i let him all the night but nothing)
i don't know what to do
Click to expand...
Click to collapse
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.

Or you can continue to use Odin which when you plug the USB in will show that a connection is made even though the phone says it's not in download mode.

Cosmic Blue said:
You have to use smart switch emergency recovery function to restore your phone. It is a stand alone function within smart switch.
All you need is your phone model and serial number.
Apparently you missed a step when preparing your phone for flashing.
Click to expand...
Click to collapse
I did an emergency recovery with my phone model and serial, same with kies.

nonechap said:
I did an emergency recovery with my phone model and serial, same with kies.
Click to expand...
Click to collapse
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.

Cosmic Blue said:
If that did not work, it looks like the memory chip on the mother board is damaged. Take it in if it is still under warranty.
Click to expand...
Click to collapse
it is not under warranty anymore, should i replace the motherboard ?

@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you

rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse
In this case, when i flash the rom, should i use the 4 files or only the AP file ?

nonechap said:
In this case, when i flash the rom, should i use the 4 files or only the AP file ?
Click to expand...
Click to collapse
use old odin

rony raj said:
use old odin
Click to expand...
Click to collapse
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)

nonechap said:
What version of odin should i use ?
And i have to use only the AP file or the 4 files of the 7.0 rom after the bootloader update? (AP BL CP CSC)
Click to expand...
Click to collapse
odin v3.09 or 3.12
update bootloader and modem from given first post by me

rony raj said:
odin v3.09 or 3.12
update bootloader and modem from given first post by me
Click to expand...
Click to collapse
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?

nonechap said:
Yes i know but when i have updated the bootload with the 2 files you gave me, i have to reboot in download mod and flash the 7.0 rom, but i have download the rom and i have 4 files, so should i flash only the AP or the four files ?
Click to expand...
Click to collapse
tell me rom on your device before bootloop
6.0 or 7.0

rony raj said:
tell me rom on your device before bootloop
6.0 or 7.0
Click to expand...
Click to collapse
6.0.1

nonechap said:
6.0.1
Click to expand...
Click to collapse
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/

rony raj said:
then flash 6.0 firmware
download from here
https://www.sammobile.com/firmwares/database/SM-G935F/
Click to expand...
Click to collapse
I tried but still nothing, i think i have to replace the motherboard ?

nonechap said:
I tried but still nothing, i think i have to replace the motherboard ?
Click to expand...
Click to collapse
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs

rony raj said:
try another chance
To do the S7 FRP OFF - Put phone in download mode
Once phone is in download mode.
Flash the files which i will provide.
You Only need to flash boot.tar via odin for respective models (example for s7 use G930 Qualcomm folder) for (s7 edge use G935 Qualcomm folder)
Once you flash the boot tar file. The phone will reboot and it will enable ADB. Run the Bat file which i will provide and it will remove the FRP lock
Once done put the phone in Downlaod mode and flash stock ROM.
The whole process takes less than 10 mins.
Same Idea for S7 Exynos phones... put phone in downlaod mode and then flash the file (G930F(ENGroot) for s7 models & (G935F_Root for s7 edge models). Once done phone will reboot. Then use this bat file (g935f.bat). Once this is executed locks will be removed and phone will go in download mode. Flash stock Boot.img and ALL DONE.
download
https://mega.nz/#!Tw0TAI6I!jCGuxGrwqCGEy3flcRqF9EpzbaTkby7SJ_slKRaXqRs
Click to expand...
Click to collapse
After flashing boot.tar, when i run the .bat, it says error: closed
EDIT: i have to enter into the recovery mod and select "adb update" in order to make my phone detected by my computer

Those files are for the S7. Do they work for the S7 Edge also?
Edit - I tried it and it fails in odin. My phone is bricked.
rony raj said:
@nonechap bro
upgrade you bootloader before flash nougat rom
bootloader is here
https://www.androidfilehost.com/?fid=529152257862714907
modem is here
https://www.androidfilehost.com/?fid=529152257862714909
open odin and boot your phone into download mode
[1]Connect phone and wait until you get a blue sign in Odin
[2]Place the desired BL file in the [BL] slot.
[3]Place the desired CP file in the [CP] slot.
[4] Go to the Options section and make sure Auto Reboot, Re-Partition and F. reset time are unmarked.
[5]Push [Start]
Once odin reports "Success..." message in the Message box, boot your phone into download mode again
then flash again 7.0 roms via odin
then boot in recovery and wipe data and cache
and reboot device
be patience first boot takes 15 minutes or more
if fail you cant boot your device untill system status changed to official due to knox restrictions or bootloader changed to latest
if not boot that means your bootloader not update by odin due to frp lock is on
if you are on marshmellow before flash 6.0.1 firmware to boot device
firmwares are here
https://www.sammobile.com/firmwares/database/SM-G935F/
i suggest if device boots unlock bootloader first to disable knox
hit thumbs up if i helped you
Click to expand...
Click to collapse

Works !!!
Sorry to revive an old thread but I think it might help people recover from a bootloop with a bit of addtional explanation than initially provided.
So I have an S7 Edge as a backup phone and hadn't used it for a while. Google FRP was activated. I tried to update to a newer firmware through Odin (can't OTA since it's from Tmo and i'm in Canada). Anyways for whatever reason it failed in the middle and I was stuck in a bootloop that wouldn't stop. I tried downgrading, I tried factory, I tried new versions, nothing would do, I'm assuming because of FRP.
So I followed Rony Raj's post https://forum.xda-developers.com/showpost.php?p=71906126&postcount=17 but kept getting stuck. The thing is once you flash the proper Boot.tar file, the phone will appear to still be in a bootloop. You will have to go with the screen (the phone) and the sound of the connection and disconnection from your computer. So basically just sync with the sounds and time it so you open the ''S7 & S7 Edge QUALCOMM.bat'' file at the exact time your phone reconnects and it'll work. I had to do it about 6-7 times before i got it right.
When that is done your phone will restart in download mode. When you do just flash the latest version of the firmware you get from AndroidFileHos*.com or Sammobil*.com. Make sure you select all 4 files in Odin (BL, AP, CP and SELECT CSC HOME for CSC - NOT CSC).
Once all that is done your phone will restart and everything should be fine, well that worked for me
Thanks a lot to @rony raj for putting together the files and the steps to save my G935

unlock bootloader SM-G901F DTM

I am looking for a way to unlock the bootloader on my Samsung Galaxy S5 Plus (Sm-g901f, kccat6) with German t-Mobile branding (DTM) in order to flash Lineageos on it.
Is there a known way (executable for a newbie in Android flashing)?
Unfortunately my handset does not have a "OEM unlock" button in the developer options.
Is it possible to verify if the bootloader is locked apart from flashing a custom recovery and checking if it has been installed persistently?

i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then

k2828 said:
i think you just have to flash twrp. if i remmeber correctly i had the same message that my bootloader was locked with my s4 i9506 back then
Click to expand...
Click to collapse
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.

ooo yes thats a common odin bug for some phones..

dial25and said:
Even though my answer was posted a month ago, I want to present my solution:
As I said above, flashing TWRP did not worked on the way that all installation guides told me. But not because my bootloader was locked, the reason seems to be a bug (or is it a feature ) in TWRP.
The problem was, that the Stock OS is overwriting the bootloader on the first normal start.
What you have to do in order to prevent this mechanism:
1. Uncheck Auto-Reboot in Odin.
2. After Odin shows "PASS" shut your phone down and reboot it manually to the recovery.
3. In TWRP select Reboot and then System.
4. Done.
Now I am a lucky user of a LineageOS powered phone.
Click to expand...
Click to collapse
Why to shut down ?
When Odin passed !
Press download mode command keys
When screen goes black
Immediately press recovery commands !
And if u failed to reboot to recovery,flash firmware with nand erase all option !
As i experienced this issue!

T280 - Can not flash back to stock, secure check fail (boot)

Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request

ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.

Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.