I just got it for Black Friday. Enabled developer mode, turned on OEM Unlock and USB debugging, fired up Odin and my phone is telling me the following when I boot it into recovery:
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930U
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD : ENABLE
From what I've been able to google, this means my bootloader is still locked. If I try to flash CF-Root with Odin, I get this:
Code:
SECURE CHECK FAIL : recovery
And in Odin, the log looks happy as a clam, then tells me
Code:
FAIL! (Auth)
And kills the process
I'm really not sure why this is happening, since my Developer menu consistently shows OEM Unlock as being enabled. I know Odin detects the phone, it doesn't seem to be an issue with computer -> phone connection.
I've tried flashing CF-Auto-Root-herolte-heroltexx-smg930f.zip and CF-Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip, as well as TWRP 3.0.0-0. Nothing seems to work, Odin always kills the process and I get the same "SECURE CHECK FAIL: recovery" message. I've got no idea what to do.
Also, FWIW, I have the SDK, ADP and JDK all up to date.
OEM unlocked within the developer options means nothing. That only applies if the phone has the ability to be unlocked. The phone you purchased is locked.
troby86 said:
The phone you purchased is locked.
Click to expand...
Click to collapse
Exactly, the 930u is unlocked to all carriers, but its bootloader locked. Take it back and get the international 930f version.
Well this stinks. I thought only the T-Mobile version had a locked bootloader? This explains why I can't find anything about how to root it.
The T-Mobile version can be rooted by flashing the engineer boot image. I've done it and returned to stock to confirm. You can find the guide somewhere in the Verizon S7 thread I believe.
[/B]
darthjoe229 said:
I just got it for Black Friday. Enabled developer mode, turned on OEM Unlock and USB debugging, fired up Odin and my phone is telling me the following when I boot it into recovery:
Code:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930U
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD : ENABLE
From what I've been able to google, this means my bootloader is still locked. If I try to flash CF-Root with Odin, I get this:
Code:
SECURE CHECK FAIL : recovery
And in Odin, the log looks happy as a clam, then tells me
Code:
FAIL! (Auth)
And kills the process
I'm really not sure why this is happening, since my Developer menu consistently shows OEM Unlock as being enabled. I know Odin detects the phone, it doesn't seem to be an issue with computer -> phone connection.
I've tried flashing CF-Auto-Root-herolte-heroltexx-smg930f.zip and CF-Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip, as well as TWRP 3.0.0-0. Nothing seems to work, Odin always kills the process and I get the same "SECURE CHECK FAIL: recovery" message. I've got no idea what to do.
Also, FWIW, I have the SDK, ADP and JDK all up to date.
Click to expand...
Click to collapse
hi there? Just wondering if you were able to fix this problem. I Have that same problem. i tried rooting my galaxy s7 with the octopus box and when it rebooted got stuck on bootloop. Thanx
Unable to Root S7
I am also have a similar issue. I am unable to disable the secure boot. My phone is requiring me to have it enabled. When attempting to disable/ set none it is grayed out and says blocked by administrator. I also have EOM unlock set and the other requirements. My Odin log is below.
Phone info:
S7 SM-G930t (T-mobile)
OS 7.0
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> cache.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
danielCP45 said:
I am also have a similar issue. I am unable to disable the secure boot. My phone is requiring me to have it enabled. When attempting to disable/ set none it is grayed out and says blocked by administrator. I also have EOM unlock set and the other requirements. My Odin log is below.
Phone info:
S7 SM-G930t (T-mobile)
OS 7.0
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> cache.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ALL Snapdragon S7s are bootloader locked
troby86 said:
The T-Mobile version can be rooted by flashing the engineer boot image. I've done it and returned to stock to confirm. You can find the guide somewhere in the Verizon S7 thread I believe.
Click to expand...
Click to collapse
Greetings Bro. I'm Using G930V Verizon Qualcomm Variant. android Oreo latest version security level 25 dec 1 2019 can I root, install custom Rom and TWRP. I tried so many times but failed
Related
I've been running CM on and off on this thing for almost 2 years straight upgrading all along the way (including nightlies as recent at late july this year) well after dealing with some instability issues I figured I'd try to flash my phone back to stock and see if I could get things back fully operational GPS, non-crashing chrome etc.
So I fired up Odin 3.07 and tried flashing a 4.3 ROM to it and it's been down hill from there.
I should have done more research before attempting the restore but tried the method that worked in the past of just getting a copy of stock ROM and flashing it with Odin.
After the initial flash returned a failed result, I tried rebooting the phone and trowing in the towel, but apparently I jacked up my bootloader and now I can't flash my phone at all.
I tried both methods in the next link including re-partitioning with pit files at the bottom of the article and no luck, I also tried "upgrading" with Kies and that fails too.
http://forum.xda-developers.com/showthread.php?t=2586319
I've tied just about every stock version I could find and all that happens is the update fails with an output like whats shown below.
Update1: I've also tried the debricking procedure in this forum with no luck.
Has anyone seen this behavior?
Sorry if this post lacks details.
--Phone Output--
ODIN MODE
PRODUCT NAME: SCH-I535
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOM SECUREBOOT: ENABLE
BOOTLOADER RP SWREV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1
--Odin Output--
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_I535VRUCNC1_I535VZWCNC1_2198062_REV09_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
You updated to a version with a locked bootloader...
JTAG seems to be the only solution at the moment.
0xDFA said:
You updated to a version with a locked bootloader...
JTAG seems to be the only solution at the moment.
Click to expand...
Click to collapse
I was afraid that was the case.
Thanks for the feedback.
(Sticker Info)
Samsung Galaxy S4
Model: GT-I9505
FCC ID: A3LGTI9505
SSN: -i9505GSMH
(Software Info)
Model: GT-I9505G
Android Version: 4.4.2
Baseband Version: I9505XXUFNA5
Kernel Version:
3.4.78--KT-SGS4-KK4.4-TWGE-INTL-02.05.2014---g5601ab2
[email protected] #1
Wed Feb 5 12:08:05 MST 2014
Build Number: KOT49H.02.18.2014
Warnings on boot up:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
(The phone has been rooted previously but has been unrooted, TeamWRP is installed)
I rooted my phone a while ago and tried loading a custom ROM. However I definitely installed the wrong ROM as the kernel that came with it would not work, I then installed a custom Kernel to get the phone to a usable condition. This has been fine up until recently when certain apps claim the phone is rooted or crashing unexpectedly and also claiming the phone is a security violation.
I'm trying to restore the phone to the factory Samsung TouchWiz ROM/Google Android Factory ROM with no errors.
I've checked for a couple weeks now and as far as I'm aware I haven't found anything that relates to my problem.
Any help will be deeply appreciated!
If you wish to return to stock then please take a look at this guide here. You should have no problems following the instructions.
Good luck
Attempted flash
UPDATE: I had a backup and was able to restore the phone to working condition however I am back to square one with the original problem
Tried the method you posted and unfortunately it failed and this happened:
Odin3 v3.04
tar file = I9505XXUEMK9_I9505H3GEMJ2_H3G.zip 1.43 GB
Odin Log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMK9_I9505H3GEMJ2_I9505XXUEMK9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Android Log:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY: Custom
SYSTEM SATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START: [224,1440]
SW REV. CHECK FAIL : fused : 4 , Binary : 3
Now the phone boots saying “Firmware upgrade encountered an issue. Please select firmware recovery mode in Kies & try again.
Problem is the phone isn’t being detected by KIES.
Any thoughts?
I have looked everywhere for a solution to this problem and found a few posts refering to similar situations but not once did I find an answer that worked. I will go into as much detail as I can about what caused it and what I've tried so far. 6 hours of failed attempts and I've made absolutely no progress whatsoever.
Before I Begin:
I have flashed different firmwares and ROMs to my G870A over the last couple years and occasionally ran into a soft brick here and there but never had any issues recovering with ODIN or a factory reset. I'm slightly familiar with the process.
-Installed and reinstalled Samsung drivers including the ones provided with Kies.
-Running ODIN as Administrator
-Using stock firmware files I have saved in the past that worked 100% of the time
-Factory reset/wiped cache
-Using the USB cable provided by Samsung
-Running Windows 7
-Service is AT&T
How I Bricked It:
It's been a year since I last did a major flash so I don't remember all the specifics but I believe I installed the 5.0 update from stock and applied the ROM file G870A_OC5_Stock_Rooted_ROM.zip and left it at that. It ran perfectly fine until I unrooted via SuperSU as I no longer needed root access. Immediately afterwards the app crashed and refused to open so I rebooted the phone. I did not apply any updates but I found myself stuck on the AT&T logo. I waited 15 minutes and nothing happend. Booted into recovery and factory reset/wiped the cache. Booted up again and waited 15 minutes at the logo. Nothing.
What I've Attempted So Far:
-Flashing G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 with Odin.
Results:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<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> aboot.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)
-Flashing the original ROM I used to root the device: G870A_OC5_Stock_Rooted_ROM.zip. Same results.
-Flashing 2 other stock firmware files including one from sammobile. Same results.
-Tried a different version of Odin
-Tried to connect with adb from the command line. All commands result in error.
-Samsung Kies fails to detect the phone
Bootloader Screen When Attempting Flash:
ODIN MODE
PRODUCT NAME: SM-G870A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRENTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Recovery Screen Firmware Version:
Android system recovery <3e>
LRX21T.G870AUCU1BOC5
I would really appreciate any kind of help resolving this problem and retrieving access to my phone as its WAS in great condition. At this point I no longer care about tripping KNOX. Let me know if you need anymore information as I probably forgot something.
Nothing at all? I had to resort to calling the AT&T service store, Samsung support in Best Buy, as well as a cell phone repair place. One lady **** herself, one referred me to the Google search engine, and cell phone repair said XDA was a forum for meeting up with local software engineers. If anyone could refer me anywhere more specific then Google.com I would really appreciate it. Thanks.
Hi,
Try posting your question here:
http://forum.xda-developers.com/sprint-galaxy-s5/help
The experts there may be able to help.
Good luck!
Samsung Galaxy S7 (SM-G930T) T-Mobile
Info on ODIN Download screen
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G930T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: On
WARRENTY VOID: 0x0
QUALCOMM SECUREBOOT: Enabled
RP SWREV: B4(2, 1, 1, 1, 1) K1 S3
SECURE DOWNLOAD: Enabled
I have referenced the guide I followed. GUIDE. I followed all the instructions. After root I used the Debloater and my phone was incredibly slow and inefficient. So, I used the fix V15. Yet again, slow, hot and a whole host of problems. So, I follow the unroot guide. I continued encounter this error on odin when attempting to unroot.
Code:
<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.1205)..
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And this error on my phone:
Code:
SW RV CHECK FAIL: [system]Fused 3>Binary 1
After trying at least 4 different AP's
Code:
TMB-G930TUVS2APB8-20160317155535
TMB-G930TUVU2APC8-20160402115527
TMB-G930TUVU1APB6-20160310103828
TMB_G930TTMB4BQB1
I got frustrated and Held any button I could to get that stupid screen to go away. I was met with "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software. So, I go to do that. And the smart switch software does not support my phone. So, I boot into Recovery mode Wipe Cache, Wipe everything I can and try to reboot and I can only go from DOWNLOAD mode to recovery mode. I read somewhere on here that you can't Rollback firmware so I try the newest firmware and maybe that will work. I encounter no issues in ODIN and no issues on my phone Once my phone reboots it goes to the Samsung Galaxy S7 splash screen with the Unlocked lock and doesn't do anything past that. So I try to boot to recovery mode and that's when I get caught in a loop. My phone went from a flashing "Recovery booting" then if I tap a bunch of VOL UP/DN HOME and POWER combinations It will go to splash screen and flash the splash screen numerous times. I can now get it back to Download mode after messing around with it. But I have no idea what I need to do.
If I need to provide any more information let me know.
How Do I mark this as solved? I Used ODIN to update my bootloader to the newest version. then used the most current AP CP and CSC there is. It's booted up and installed. Now I'm just restoring and Going to restart to make sure everything is working correctly.
Hey guys, I've come into possesion of a Galaxy Note 5 that my cousins seemed to have messed with. A long while back I played with flashing firmware etc on my own phones so I assume that is what happened here. It attempts to start up, getting to the Note 5 splash screen then black screens, then splash screen and so on. I couldn't stop it without a hard reset (Volume down + Lock).
The phones details:
Samsung Galaxy Note 5 (was known working no more than a week ago) Product name: SM-N920I I saw version 6.0.1 somewhere in the menus, I believe this to be the current version of android available to Note 5 phones in Australia? I cant find the build number anywhere that I can access.
Has anyone got any clues? I'll include the ODIN screenshot and text from the phone in download mode. It may also be worth noting I can get into recovery mode, but not safe mode. I've tried wiping partitions etc, nothing there worked.
Download Mode pre failed flash:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N902I
CA_ TYPE: CA_3
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download : Enabled
KNOX WARRENTY VOID: 1 (0x0500)
RP SWREV: B:3 K:0 S:1
I gain "SECURE CHECK FAIL : (BOOTLOADER)" after the failed ODIN flash.
Recovery menu shows -
Android Recovery
MMB29K.N920IDVS3BQA3
samsung/nobleltedv/noblelte
6.0.1/MMB29K/N920IDVS3BQA3
user/release-keysAt the bottom -
Supported API: 3
dm-verity verification failed...
I can't post a screen shot of ODIN due to an inactive account, so I will copy paste that text here as well.
<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/005> Odin engine v(ID:3.1205)..
<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> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Like I said above, the phone was working fine last week, saw it myself at a family get together. He said something about not being able to play Mario Run, and I've heard there are issues with rooted devices with Mario Run so perhaps hes tried to unroot the device and messed up the process?
I'm fairly tech savvy, so I should be able to fix it. I just don't know where to really go from here thanks to lack of experience.
How screwed is this phone?
EDIT: I also just want to state that I couldn't find any info about the "SECURE CHECK FAIL : (BOOTLOADER)" message anywhere. A lot about aboot and other stuff, but no bootloader.