Tab 2 Odin Failing - Galaxy Tab S2 Q&A, Help & Troubleshooting

I got an unlock code from T-Mobile and unlocked my S2 ( T817T, fully updated 5.1.1 ). I downloaded Odin 3.11 and have tried all 4 TWRP files:
twrp_2.8.7.1_LL_5.1.1_t710.tar
twrp_2.8.7.1_LL_5.1.1_t810
twrp_3.0.2-1_sm-t710
twrp_3.0.2-1_sm-t810
When I start the unlock in Download mode it reports:
Product Name: SM-T817T
ODIN MOE
Download speed: Fast
Current Binary: Samsung Official
System Status: Official
FRP Lock: ON
Secure Download : Enabled
KNOX Warranty Void: 0
AP SWREV: B:2 K:0 S:0
For all 4 TWRP images it completes the first block of the install progress bar then fails. When it fails the screen on my S2 reports:
FRP LOCK: ON
Custom Binary(RECOVERY) Blocked by FRP Lock
and the console of ODIN says:
<ID:0/005> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<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> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?

You need to enable OEM unlock in developer settings.

ashyx said:
You need to enable OEM unlock in developer settings.
Click to expand...
Click to collapse
Ok, that part worked. I saw the black screen go by with the installing SU but it looks like I'm in a reboot loop now.
** Edit, It looks like I put on a 5.0.2 recovery for a "T817" instead of 5.1.1 for T817T which doesn't exist. I only found the T817, T817P and T817R4....

Nomadadon said:
Ok, that part worked. I saw the black screen go by with the installing SU but it looks like I'm in a reboot loop now.
** Edit, It looks like I put on a 5.0.2 recovery for a "T817" instead of 5.1.1 for T817T which doesn't exist. I only found the T817, T817P and T817R4....
Click to expand...
Click to collapse
You can use TWRP for the T810 or T815.
Which supersu version did you install or did you allow twrp to install it's own version?

ashyx said:
You can use TWRP for the T810 or T815.
Which supersu version did you install or did you allow twrp to install it's own version?
Click to expand...
Click to collapse
Never got that far with TWRP. I'll try it next. I have BETA-SuperSU-v2.52.zip downloaded, but with Heimdall don't see how to install it.

Ok, It looks like installing all 3 steps from http://forum.xda-developers.com/tab-s2/general/guide-root-tab-s2-t3205019 ( You have to reboot after step 2 ) works. I've got root.

Related

Logo Hangs

So one day i decided to update my S6 from 5.0.2 to 5.1.1. I downloaded smart switch and updated through there.
The phone worked perfectly until I realized I need to root my phone so I attempted to root through TWRP using UPDATE-SuperSu 2.46.zip and I got stuck in a boot loop.
Then I searched google how to get out of my problem and somewhere along the line, I deleted my OS by deleating System in the wipe section of TWRP.
I tried to flash the stock rom but Odin gives me this error:
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am at my wit's end here and I really need some help so please reply if you have any useful information to get my phone back to normal.
I'm not sure if this has to do with anything but my phone says:
SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2
Sonicboom9004 said:
So one day i decided to update my S6 from 5.0.2 to 5.1.1. I downloaded smart switch and updated through there.
The phone worked perfectly until I realized I need to root my phone so I attempted to root through TWRP using UPDATE-SuperSu 2.46.zip and I got stuck in a boot loop.
Then I searched google how to get out of my problem and somewhere along the line, I deleted my OS by deleating System in the wipe section of TWRP.
I tried to flash the stock rom but Odin gives me this error:
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am at my wit's end here and I really need some help so please reply if you have any useful information to get my phone back to normal.
I'm not sure if this has to do with anything but my phone says:
SW REV. CHECK FAIL. DEVICE: 3. BINARY: 2
Click to expand...
Click to collapse
Make sure the tar file in Odin is the latest 5.1.1 version. Samsung has patched the bootloader so that no one can downgrade anymore. Do you know what version 5.1.1 you were running before? If so, download that exact version.
Sent from my SM-G925T using Tapatalk
xmayhemreturnsx said:
Make sure the tar file in Odin is the latest 5.1.1 version. Samsung has patched the bootloader so that no one can downgrade anymore. Do you know what version 5.1.1 you were running before? If so, download that exact version.
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
I've downloaded the T-mobile 5.1.1 version because I have not found a MetroPCS version. I hope that is the version I had before.
I downloaded it from here: http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387 (the first link)
EDIT: Currently going to try this out. I'll let you know if it works or not: http://forum.xda-developers.com/tmo...x-recovery-seandroid-enforcing-error-t3144011
EDIT 2: Doesn't work it just says md5 file invalid. Binary Check Failed.
EDIT 3: FIXED MY PHONE I just used the latest version of 5.1.1. Thanks for pointing me in the right direction xmayhemreturnsx. Link for the latest version for anyone else who needs help:http://forum.xda-developers.com/tmo...firmware-g920tuvu3doi1-g920tuvu2doh6-t3213001

Firmware upgrade/reactivation lock

Odin name (high speed)
Product name SM-N910t
CURRENT BINARY: Samsung Official
system Status: Official
reactivation lock : on
KNOX WARRANTY VOID:0x0
qualcom secureboot:Enable (csb)
RP SWREV:S1 T1, A1, A2, P1
secure download: enable
My Note 4 is completely and ultimately unusable. I got it from a move-sale (They were moving away) anyways, after I got home and charged it I found that it had been reactivation locked with a Samsung account (none of the exploits worked) so I went and tried to flash it with android 4.4.4 and it errored. So I unplugged it and removed the battery and then I got this awesome new bootup screen (you guys should get it. Its RAD!!) Firmware Upgrade Encountered AN ISSUE please select recovery mode in kies (kies didn't work) After that I tried flashing it with a rom on ODIN and it was stuck at 3% and made no progress. Then I found this forum http://forum.xda-developers.com/note-4-tmobile/help/phone-stuck-firmware-upgrade-t3197091 (at the very bottom) I couldn't do that solution.
---------this-is-the-error----------
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
IMAGES
http://imgur.com/a/XzYFh
If the phone was updated to 5.1.1 you can't go back to 4.4.4
Since your getting the failed message, probably odin to 5.1.1
according to you link he odin the pit then it reset then odin flash stock recovery. in your picture you both odin pitfile and twrp.
dont think theresanything u can do..
gmenik6 said:
according to you link he odin the pit then it reset then odin flash stock recovery. in your picture you both odin pitfile and twrp.
Click to expand...
Click to collapse
that helped, now I'm stuck with a plain old 5.1.1 reactivation lock
If it helps with detail I only get these screens. welcome Samsung, then missing simcard, then it asks for a Samsung account

[STOCK][Odin] OFFICIAL T713 STOCK FIRMWARE T713XAR1APD9

Here is the official stock firmware for the New (2016) Galaxy Tab S2 8.0" T713.
Use this to restore your tablet or fix a soft brick.
This requires Odin to flash.
Model Name: Galaxy Tab S2 8.0
Model: SM-T713
Country: Cellular South (XAR)
Firmware Version: T713XXU1APD9
OS: Android Marshmallow
OS Version: 6.0.1
PDA: T713XXU1APD9
CSC: T713XAR1APD9
Download T713XAR1APD9 Here
Hello everybody!
Sorry if this si not fine for me to post in this thread, but I think my question is quite related, in case I apologize in advance.
I recently bought a Galaxy tab S2 8" (SM-T719).
I installed the TWRP and applied SuperSU (as per guide: http://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627)
All fine...
Only later I recall that I stupidly forgot to make a complete STOCK backup. If I need, can I use the STOCK provided in this thread even if it is for T713?
The only difference I see comparing the specs is the additional 2G support.
Thank you in advance and thanks to everybody for the great work!
PS: if it can be usefull to anybody I can make a BACKUP of the current state of the tablet.
Best regards!!
DeeXii said:
Here is the official stock firmware for the New (2016) Galaxy Tab S2 8.0" T713.
Use this to restore your tablet or fix a soft brick.
This requires Odin to flash.
Model Name: Galaxy Tab S2 8.0
Model: SM-T713
Country: Cellular South (XAR)
Firmware Version: T713XXU1APD9
OS: Android Marshmallow
OS Version: 6.0.1
PDA: T713XXU1APD9
CSC: T713XAR1APD9
Download T713XAR1APD9 Here
Click to expand...
Click to collapse
Can we use the firmware for T813 as well?
Or do you know a source where to get that firmware?
Thanks...about to Root and went to SamMobile and another Samsung site to get Stock in case of any problems Rooting....But Its NOWHERE to be found!!! A quick Google search led me here to trusted XDA!!! Thanks Bro!!
I cant believe there is no development for this 713 Tab! I have bought or tried everything Samsung and this is a a great tablet...I had the Tab S 32GB and sold it...never found another..and Note Edge also that had nooo development as well...I guess I get the things that are not popular..2014 Note 10.1 and Note Pro 12.2 there are NO Roms on those either! My Note 5 is the only thing I get to flash...But thanks again...I needed this
Sent from my SM-T713 using XDA-Developers mobile app
DionWhite33 said:
I cant believe there is no development for this 713 Tab!
Click to expand...
Click to collapse
This will change when I get my hands on one Friday
I've just tried to flash this firmware for my SM-713 tab and it does not go past the Samsung logo (fading in/out).
I used Odin 3.10.7 and extracted the file "T713XXU1APD9_T713XAR1APD9_HOME.tar.md5" then pointed the AP field in Odin, to the file and flashed.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> modem.bin
<ID:0/005> adspso.bin
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> sec.dat
<ID:0/005> cmnlib.mbn
<ID:0/005> keymaster.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Bhups said:
I've just tried to flash this firmware for my SM-713 tab and it does not go past the Samsung logo (fading in/out).
I used Odin 3.10.7 and extracted the file "T713XXU1APD9_T713XAR1APD9_HOME.tar.md5" then pointed the AP field in Odin, to the file and flashed.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> modem.bin
<ID:0/005> adspso.bin
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> sec.dat
<ID:0/005> cmnlib.mbn
<ID:0/005> keymaster.mbn
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Factory reset
Lightn1ng said:
Factory reset
Click to expand...
Click to collapse
Thanks!!!
Factory rest worked great!!
Bhups said:
Thanks!!!
Factory rest worked great!!
Click to expand...
Click to collapse
Awesome!
Lightn1ng said:
This will change when I get my hands on one Friday
Click to expand...
Click to collapse
Are you cooking something up? I cant wait! Im also getting an update from Samsung thats about 285MBs...looks to small to be Firmare.maybe its a Security Patch?
Sent from my SM-T713 using XDA-Developers mobile app
DionWhite33 said:
Are you cooking something up? I cant wait! Im also getting an update from Samsung thats about 285MBs...looks to small to be Firmare.maybe its a Security Patch?
Sent from my SM-T713 using XDA-Developers mobile app
Click to expand...
Click to collapse
Lightning ROM... Its in the dev forums...
There's a newer version for this firmware T713XXU1APG1 (build 01.07.2016, the one in the first post is build 20.04.2016). I'm not sure what the difference is. Has anybody already downloaded the new version and saved it somewhere on the Internet? A free download from https://samsung-firmware.org/model/SM-T713/region/XAR/ takes almost 7 hours.
dxxvi said:
There's a newer version for this firmware T713XXU1APG1 (build 01.07.2016, the one in the first post is build 20.04.2016). I'm not sure what the difference is. Has anybody already downloaded the new version and saved it somewhere on the Internet? A free download from https://samsung-firmware.org/model/SM-T713/region/XAR/ takes almost 7 hours.
Click to expand...
Click to collapse
I've hosted the file on a separate mirror on Mega: https://mega.nz/#!uZ0S2LKJ!cv9_833R1kUVndRl4lpIM_UV51WiCtbVrWAd9S3m2TQ. No file changes, just a download/rehost.
Image restore via Odin fails with blue caution triangle screen
I had my S2 SM-T713 8.0 Rooted and tried to install Lightning. The WiFi failed, so I flashed the WiFi fix. Still no WiFi. Restored the rooted TWRP backup. It booted up to the lock screen, but refused to allow me to use the only pin that had ever been entered on the machine.
After numerous attempts to get around the pin issue, I attempted to flash this stock firmware via Odin. Every attempt failed at a different point. MD5 double checked and matched. The latest attempt ran as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> adspso.bin
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am stuck at the blue screen saying that An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software. That software reports that my device is not supported. The other thing on the screen is a message that SU REV CHECK FAIL : [aboot]Fused 2 > Binary 1. I also cannot turn off the screen.
I have been rooting and running numerous ROMS on phones and tablets for 6 years. Any hope left?
stock firmware
Sooo, I made the fatal mistake of rooting with out having the back-up stock os...... long story short, now I cant find out which version of the firmware I need. Can i find out what the stock firmware was by my TABLETS' model number??? btw......
SM-T713NZKEXAR is my model and i cant seem to find it anywhere.
please helppp
dirtymikeandtheboyz said:
Sooo, I made the fatal mistake of rooting with out having the back-up stock os...... long story short, now I cant find out which version of the firmware I need. Can i find out what the stock firmware was by my TABLETS' model number??? btw......
SM-T713NZKEXAR is my model and i cant seem to find it anywhere.
please helppp
Click to expand...
Click to collapse
Use the one linked in the OP.
Before you odin twrp or anything else let the tablet update to the latest firmware.
Success after loading the new updated Samsung firmware from link in post by dxxvi.
"I had my S2 SM-T713 8.0 Rooted and tried to install Lightning. The WiFi failed, so I flashed the WiFi fix. Still no WiFi. Restored the rooted TWRP backup. It booted up to the lock screen, but refused to allow me to use the only pin that had ever been entered on the machine."
Finally had success after loading the new updated Samsung firmware from link in post by dxxvi (took almost 20 hours slow load). Confirmed that it does require a factory reboot after hanging at Samsung logo.
The new firmware allows you to choose whether to require a pin after reboot or just accept fingerprint input.
There is a newer version of of the firmware T713XXU2APJ1, release date 05.10.2016
HELPP
Model - sm-t713nzkexar
had a issue with wifi not working when flashing custom rom, long story short... i wanted to go back stock firmware and is the T713XAR1APD9 not the stock firmware for my device?? i tried to flash and it failed, and for some reason i cant attach the screenshot of the log in odin, but after failure while still in "download mode", at the top of screeen tablet says,
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"

N900A Complicated hard brick help.

My phone is SM-N900A
First of all, I didn't know that it was rooted then when I downloaded the latest updates it was un-rooted.
Because I'm ignorant and didn't know what to do, I tried re-rooting it via KINGO. But, it always fail at 90%
I always get this problem in my ODIN SW REV CHECH FAIL : [sbl1]Fused 2 > Binary 1
The next thing I did was skipped the procedure and tried rooting it thus, resulting to my phone being hard bricked.
Afterwards, I downloaded the stock rom for my phone so that I could try un-bricking it.
However, when I try to flash it with stock rom It kept failing and getting the same results ODIN SW REV CHECH FAIL : [sbl1]Fused 2 > Binary 1
So, what should I do now? I really love this phone and I want to unbrick it then re-root it again.
Would you guys help me in this complicated failure of mine.
Here's the Odin text:
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What ROM was on your phone before flashing? Did you confirm the model # in download mode?
audit13 said:
What ROM was on your phone before flashing? Did you confirm the model # in download mode?
Click to expand...
Click to collapse
My ROM was for N900A Android 5.0
Model # do you mean the product name? If it is, it says SM-N900A.
ODIN MODE
PRODUCT NAME: SM-N900A
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD : ENABLE
UDC START
This what it says in Odin mode
Did you try using different USB cables and all available USB ports?
audit13 said:
Did you try using different USB cables and all available USB ports?
Click to expand...
Click to collapse
I'll try using different cable and ports.
But, if it still didn't work, what do you think its problem?
Can it be fixed?
* I tried every usb ports and cable I have, it is 5 to be exact but I still get the same results.
Did you get the ROM from samsung-updates.com or sammobile.com? It's the latest ROM for the phone?
audit13 said:
Did you get the ROM from samsung-updates.com or sammobile.com? It's the latest ROM for the phone?
Click to expand...
Click to collapse
It's the latest ROM Android 5.0
The latest ROM I see for the sm-n900a is only 4.3: http://www.sammobile.com/firmwares/database/SM-N900A/

SECURE CHECK FAIL: (Recovery)

Hello i've been trying to flash CF Auto Root to my Verizon Note 5 (SM-N920V) and odin has loaded up the boot img and recovery from the new CFAR site (desktop.firmware.mobi) and when i try to install CFAR it loads up and almost finishes and after recovery and cache it fails and my phone says SECURE CHECK FAIL : (Recovery) and I heard that Root was possible on Nougat through CFAR. And well that was the outcome. I know the bootloader is not unlockable but is there any way whatsoever that it can be unlocked or bypassed? Something. Maybe a custom pre rooted kernel that can be flashed thru ODIN? Is there anyone who has any idea how to successfully root?
Any help would be appreciated
(Nougat 7.0 Security patch 2.1.18)
USB Debugging enabled
OEM Unlock ticked
Why tf does samsung and verizon have to be like that?
Has this ever been resolved? I've tried rolling back to 6.0.1 as well, but no success.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> cache.img.ext4 <- Stuck here with the Secure Check Fail : (Recovery) on phone
jxkertv said:
Hello i've been trying to flash CF Auto Root to my Verizon Note 5 (SM-N920V) and odin has loaded up the boot img and recovery from the new CFAR site (desktop.firmware.mobi) and when i try to install CFAR it loads up and almost finishes and after recovery and cache it fails and my phone says SECURE CHECK FAIL : (Recovery) and I heard that Root was possible on Nougat through CFAR. And well that was the outcome. I know the bootloader is not unlockable but is there any way whatsoever that it can be unlocked or bypassed? Something. Maybe a custom pre rooted kernel that can be flashed thru ODIN? Is there anyone who has any idea how to successfully root?
Any help would be appreciated
(Nougat 7.0 Security patch 2.1.18)
USB Debugging enabled
OEM Unlock ticked
Why tf does samsung and verizon have to be like that?
Click to expand...
Click to collapse
Locked bootloaders cannot be unlocked, in any way whatsoever if said so by Samsung or your carrier.
Its like tha because Samsung and Verizon probably dont want your bootloader to be unlocked. The bootloader is the same thing that prevents you from downgrading.
Odin is a leaked tool anyways.
Its not only on samsung, its on devices like Motorola, HTC, etc.
EagleStrike33 said:
Has this ever been resolved? I've tried rolling back to 6.0.1 as well, but no success.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> cache.img.ext4 <- Stuck here with the Secure Check Fail : (Recovery) on phone
Click to expand...
Click to collapse
Check your recovery/AP file, there is something wrong with it. Or, you have a locked bootloader which prohibits this activity. You can try grabbing the PIT file from CSC by extracting it.

Categories

Resources