• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

"SECURE CHECK FAIL : recovery"- Odin Rooting Error

I have been trying to root my GS7 Edge (SM-G935V) with Odin and keep getting this error message on the phone's download screen:

"SECURE CHECK FAIL : recovery"

Here is the Odin message log:

<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hero2qltevzw-hero2qltevzw-smg935v.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

OEM Unlock and USB debugging are both on. I have searched many different forums and have had no success. Any suggestions would be great.
 
Ok the thing is Bootloader is locked right?
So i need to unlock it first and ChainFire Auto root will do the trick ?
If you had a way to unlock the bootloader, I'm sure you would shock and awe alot of people.

C.F. autoroot will do nothing for your device but possibly cause a soft brick. Root & a bootloader unlock are two different things.
 
If you had a way to unlock the bootloader, I'm sure you would shock and awe alot of people.

C.F. autoroot will do nothing for your device but possibly cause a soft brick. Root & a bootloader unlock are two different things.

Ok no way then.
what i meant is after i unlocked BL then root using CF-AR
 
Bro how do you fix this problem, Secure Check Fail: boot.img... how to back it to normal?, even i restart the phone it keeps coming back.
 
#1 :

You can test to see if a firmware is corrupt by comparing its md5 signature to the one on the server.

Otherwise, it may be that the boot loader is utterly incompatible with your phone just like @James L said . You can’t just put firmwares from other Samsung phones in to ODIN and think that it will work if that is the case.

If you are sure that your download file is complete, remove .md5 by renaming it. Try flashing afterwards, it wont calculate the checksum. Be aware that the hash tag Md5 check sum is there for a reason so if this is the route you choose proceed at your own risk.

#2:

If you can still get into your recovery module (TWRP in my case), then you can use a micro-sd or OTG flash drive to flash a custom Rom onto the device.

#3:

Try to enter into your settings and de-activate “Reactivation Lock Security”. Reactivation lock might be the main cause of the problem, many users has report success only after disabling it.
 
#1 :

You can test to see if a firmware is corrupt by comparing its md5 signature to the one on the server.

Otherwise, it may be that the boot loader is utterly incompatible with your phone just like @James L said . You can’t just put firmwares from other Samsung phones in to ODIN and think that it will work if that is the case.

If you are sure that your download file is complete, remove .md5 by renaming it. Try flashing afterwards, it wont calculate the checksum. Be aware that the hash tag Md5 check sum is there for a reason so if this is the route you choose proceed at your own risk.

#2:

If you can still get into your recovery module (TWRP in my case), then you can use a micro-sd or OTG flash drive to flash a custom Rom onto the device.

#3:

Try to enter into your settings and de-activate “Reactivation Lock Security”. Reactivation lock might be the main cause of the problem, many users has report success only after disabling it.

bro how to check if my original firmware is not yet corrupted, and i still can open my recovery mode and download mode
 
Back
Top Bottom