Phone Failed Odin MF3 - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Hey guys,
I think I bricked my phone beyond repair! I attempted to use Odin to Restore my phone to MF3 stock using the tar files that were generously provided. During the Odin restore it failed, not sure what exactly happened. I have used the same files to restore the same mf3 phone on two other occasions. Now my phone won't boot to recovery or Odin mode and just says that firmware update encountered an issue. Please select recovery mode in Kies and try again. The Kies recovery never works and I am left with a phone that is a brick. Will bestbuy be able to do anything through the smart tool? Or anything I can do?
Thanks!
Sent from my iPhone using Tapatalk

You could try here...
http://forum.xda-developers.com/showthread.php?t=2360859
or pull the battery, wait a minute, and put it back and see if you can use the correct key combination to get back into download mode and try ODIN again.

Thanks for the suggestions. But nothing seems to kick it out of this Kies recovery mode. I'm sending it back to samsung. Hopefully they can repair or ship me a new device as I am still under warranty.
Sent from my iPhone using Tapatalk

dtruong23 said:
Thanks for the suggestions. But nothing seems to kick it out of this Kies recovery mode. I'm sending it back to samsung. Hopefully they can repair or ship me a new device as I am still under warranty.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me.. I worked for hours and finally about gave up, but tried flashing the I337 PIT file thru Odin in the Pit option.. It said failed but I pulled the battery and rebooted into recovery then restarted.. Google for the pit file.. It's on my computer but if you can't find it I can upload it for you.. Good luck!
Btw, the screen that says "firmware has encountered an issue" should still be able to be recognized in Odin..
I had to get on my computer anyway, so here is the file I used for the PIT box in Odin 3.09.. Hope it works for you!
https://www.dropbox.com/s/fptxnxsqevjhnt9/SGS-I337_16GB.pit

im having a simular problem. I keep getting this error when i try to use odin to restore back to stock.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

iammeHD said:
im having a simular problem. I keep getting this error when i try to use odin to restore back to stock.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you do the latest update to MK2?

nerdyblonde said:
Did you do the latest update to MK2?
Click to expand...
Click to collapse
Im not sure what that is, i just wiped my phone and now im stuck at a boot loading screen and i can get recovery/download, and i was told to use odin to flash back to stock

Related

Phone in very bad condition! Help needed!

Hi guys yestarday i was try to get back to stock firmware after i have flashed a custom rom ([ROM][ICS][4.0.3][BUILD23][BETA2.02][add ons]AOKP-android open kang project) and from that moment when i turned on odin and started it, it all went wrong! Odin dosent not do his job!
yestarday odin did this
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9000XXJVU_CL851880_REV03_user_low_ship.tar.m d5 is valid.
<OSM> MODEM_I9000XXJVU_REV_00_CL1092175.tar.md5 is valid.
<OSM> GT-I9000-CSC-MULTI-OXAJVU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Today i downloaded the sam firmware (because i have been told that the firmware i have is bad) so i downloaded another one.
put my mobile in downloade mod, set the files where they belong, connected the phone with my usb, and started.
this is what odin did
<OSM> GT-I9000-CSC-MULTI-OXAJVU.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 1684)
<OSM> All threads completed. (succeed 0 / failed 1)
I need wxperienced people to anserw me this or anybody who had something like thhis kind of a problem!
Pls help!
I dont know what to do anymore
I want my phone back!!!
Untick re-partition.
+1
Alson try to install any ROM with diff. versions of ODIN.

Need help with odin

So i purchased my s4 today at a best buy, and i followed the following guides to root my phone and now im stuck at the boot logo screen. I can access recovery (i used Safe Strap, but it wont let me get to it as i have to get past this screen im stuck at) and download mode. Any help will be great as, im really new at all of android rooting and dont know much about it.
I have been told to use odin to flash back to stock, but i get the following error on odin 1.85
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I would try Odin again. Sometimes it can take multiple attempts
And you're sure you're on MF3? just checking

SGH-I337 Softbricked Solved

If you soft-bricked your SGH-I337 and Odin Fails Authentication you are probably on MF3 Firmware and need to download the MF3 Tar Files and Odin 3.07
Insert the files into Odin like in the picture and run it. Should finish and reboot your phone. Thanks to everyone on XDA who figured this out.
My I337 was stuck on "Unauthorized Software" message. Every time I ran an Odin process I would get a failure. I was not able to make any progress until I came across this thread. I followed these instructions and made no progress. I added a "PIT" file I found on an earlier thread to this process. Odin still failed, but now I am stuck at "Firmware upgrade encountered an issue" message. I view this as some kind of progress! It suggest using Kies to proceed with recovery. Unfortunately Kies does not recognize the device. I am still getting Odin failures (see list below).
I think I am taking in for service, unless some one has a suggestion.
<ID:0/011> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> sbl1.mbn
<ID:0/011> NAND Write Start!!
<ID:0/011> sbl2.mbn
<ID:0/011> sbl3.mbn
<ID:0/011> rpm.mbn
<ID:0/011> aboot.mbn
<ID:0/011> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Removed!!
Try to flash with Odin but with out bootloader.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app

Possibly Soft-Bricked my Device, willing to try anything!

Basically my device is the Samsung Galaxy S7 Edge, obviously. SM-G935A. It is the AT&T version, and I believe I may have soft bricked it. I played with roots and never successfully rooted it before, but now it is most likely soft bricked. I turned off the device, turned it back on, and I got stuck on a frozen AT&T boot logo. I was able to get into Recovery Mode later on and I have factory reset it several times, but each time I do, it loads directly back into Recovery mode. I have tried several different versions of ODIN, and several different ROM's and Firmware's with each version of ODIN and I get errors every single time.
At this point, I'm willing to try anything, so if you suggest something to me, I will give it a shot because I just want my phone back.
Thanks in advance, I appreciate anything.
You need to start by flashing your original rom with odin, then follow tutorials on xda on methods to root your model.
Deano89 said:
You need to start by flashing your original rom with odin, then follow tutorials on xda on methods to root your model.
Click to expand...
Click to collapse
What exactly do you mean by my original rom? If you could provide a link I would really appreciate it.
EDIT: I found an original AT&T rom, and it would not flash correctly. The log is below.
<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> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone: SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot
Same issue here man, i been trying everything with no success. My phone keeps rebooting from the samsung logo. Nothing has been successfully flashed either.
If anyone has any firmware or ROM's or versions of ODIN you could suggest. Original firmware, stock ROM's, custom ROM's, unlocked ones, whatever, please post them and I will try them.
Try flashing all the ROM files apart from BL
Just AP, CP, CSC
*Detection* said:
Try flashing all the ROM files apart from BL
Just AP, CP, CSC
Click to expand...
Click to collapse
I believe I may have tried that last night, however, I didn't save the log. It got me a bit farther, I believe. I will try it again today and post the log this time.
Thanks for the response!
Download Samsung Kies 3 from here:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Then once you downloaded/installed kies you put your device in Download mode.
In Kies 3 go to the top menu bar and select Tools > Firmware upgrade and initialization.
It will prompt you to enter your device's model name and in the next window it will ask for your Serialnumber (which is on the back of your device (rip dbrand skin) )
After that a download will start in Kies 3 and now you just have to wait for it to download and install.
Good luck!
LennARTpas said:
Download Samsung Kies 3 from here:
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Then once you downloaded/installed kies you put your device in Download mode.
In Kies 3 go to the top menu bar and select Tools > Firmware upgrade and initialization.
It will prompt you to enter your device's model name and in the next window it will ask for your Serialnumber (which is on the back of your device (rip dbrand skin) )
After that a download will start in Kies 3 and now you just have to wait for it to download and install.
Good luck!
Click to expand...
Click to collapse
Will give this a shot now that I know how to use Kies. I installed it last night while I was trying to fix it, and I thought it was just a different driver haha.
Pyroshox said:
Will give this a shot now that I know how to use Kies. I installed it last night while I was trying to fix it, and I thought it was just a different driver haha.
Click to expand...
Click to collapse
Let me know if you fixed the issue you're having!
Pyroshox said:
What exactly do you mean by my original rom? If you could provide a link I would really appreciate it.
EDIT: I found an original AT&T rom, and it would not flash correctly. The log is below.
<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> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone: SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2 [1] eMMC write fail: aboot
Click to expand...
Click to collapse
Download the newest Odin version.
Make sure the re-partition mode is OFF.
Try again with the base firmware from Sammobile
@LennARTpas - I am trying this on a separate computer, but I am getting errors that my device is not supported and that the S/N is incorrect even though I have typed it in several times. Any assistance would be greatly appreciated.
@roba93 - I will be sure to try your method once I am back in the environment to do so.
Pyroshox said:
@LennARTpas - I am trying this on a separate computer, but I am getting errors that my device is not supported and that the S/N is incorrect even though I have typed it in several times. Any assistance would be greatly appreciated.
@roba93 - I will be sure to try your method once I am back in the environment to do so.
Click to expand...
Click to collapse
here!
@LennARTpas - I tried your method, however, the same issue occurred. I got several recurring errors telling me that my device was not recognized by Kies, and when I attempted to submit the S/N, it told me it was incorrect.
@roba93 - I tried your method as well, however, SamMobile does not offer firmware for SM-G935A, so I tried the unlocked version, SM-G935U, and it gave me this log below. If I did not use the correct firmware, if you could point me in the direction of which to use that would be greatly appreciated. I feel as though I'm coming off like a needy n00b, and I don't mean to in any way for future reference.
<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..
<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> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: @*Detection* - I tried your method where I didn't use the BL in ODIN, and I got this log.
<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> 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..
<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> Removed!!
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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)
Pyroshox said:
@LennARTpas - I tried your method, however, the same issue occurred. I got several recurring errors telling me that my device was not recognized by Kies, and when I attempted to submit the S/N, it told me it was incorrect.
@roba93 - I tried your method as well, however, SamMobile does not offer firmware for SM-G935A, so I tried the unlocked version, SM-G935U, and it gave me this log below. If I did not use the correct firmware, if you could point me in the direction of which to use that would be greatly appreciated. I feel as though I'm coming off like a needy n00b, and I don't mean to in any way for future reference.
<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..
<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> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: @*Detection* - I tried your method where I didn't use the BL in ODIN, and I got this log.
<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> 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..
<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> Removed!!
<ID:0/003> Added!!
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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)
Click to expand...
Click to collapse
You said that you are using the G935A.
Please try the following firmware: http://downloadmirror.co/1Ksx/G935AUCS4API2.zip
Hope this helps
roba93 said:
You said that you are using the G935A.
Please try the following firmware: http://downloadmirror.co/1Ksx/G935AUCS4API2.zip
Hope this helps
Click to expand...
Click to collapse
I love you so much right now.
I tried this firmware on a separate computer, and didn't try it on my main PC because it wasn't necessary, however, it worked. It went through and flashed correctly, and my phone booted into recovery mode. I had to wipe the cache, and it began setting up the phone like normal.
THANK YOU SO MUCH!
Pyroshox said:
I love you so much right now.
I tried this firmware on a separate computer, and didn't try it on my main PC because it wasn't necessary, however, it worked. It went through and flashed correctly, and my phone booted into recovery mode. I had to wipe the cache, and it began setting up the phone like normal.
THANK YOU SO MUCH!
Click to expand...
Click to collapse
No problem mate
Glad it worked
roba93 said:
No problem mate
Glad it worked
Click to expand...
Click to collapse
Yay it unbricked my phone too!
it is hard to find a guide with all the phone versions/updates, just specific solutions. Well this one magically worked, thank you.
I have a sm-g935a (att) - It would bootloop, after several attempts to recover by flashing various files the phone would give all sorts of errors depending on the version flashed, stop at recovery mode and not go any further, although let me wipe it. hope this helps if you have a similar porblem

Trying to get from SM-G935p to G935T REV Check Fail

Alright so I am trying to convert my sprint phone to work on tmobile my phone was upgraded to 7.0 so I downloaded SM-G935TUVS4QB1 software to flash it to tmobile, however I get SW REV CHECK FAIL : {aboot]Fused 5 > Binary 4. I am using Odin 3.12 and I see this error a lot with people trying to downgrade, but the phone is on 7.0. This is a copy of the odin log any help is appreciated.
<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> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
LeeFerio said:
Alright so I am trying to convert my sprint phone to work on tmobile my phone was upgraded to 7.0 so I downloaded SM-G935TUVS4QB1 software to flash it to tmobile, however I get SW REV CHECK FAIL : {aboot]Fused 5 > Binary 4. I am using Odin 3.12 and I see this error a lot with people trying to downgrade, but the phone is on 7.0. This is a copy of the odin log any help is appreciated.
<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> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It looks like you are trying to flash a firmware with bootloader version 4 over version 5. look at the 5th digit from the right in the firmware version and thats the bootloader version. Im afraid you are stuck on the Sprint firmware because tmobile versions are all bootloader 4 and you cant downgrade bootloader versions.
bsharp8 said:
It looks like you are trying to flash a firmware with bootloader version 4 over version 5. look at the 5th digit from the right in the firmware version and thats the bootloader version. Im afraid you are stuck on the Sprint firmware because tmobile versions are all bootloader 4 and you cant downgrade bootloader versions.
Click to expand...
Click to collapse
Interesting that makes sense. Thank you for the response I appreciate that.
No problem

Categories

Resources