Database Users

[Q] Galaxy S4 (SGH-I337) Soft-bricked after extensive research

A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!

AhellHound said:
A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!
Click to expand...
Click to collapse
Use Odin 3.07 Download the MF3 Firmware from https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE And put all the extracted files in the correct spot

compucanton said:
Use Odin 3.07 Download the MF3 Firmware from (your link) And put all the extracted files in the correct spot
Click to expand...
Click to collapse
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<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> 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> 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/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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

AhellHound said:
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<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> 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> 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/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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone's status on the top right when in download mode is as followed:
Code:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURSRT MODE enabled

I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.

Nurmi_CEO said:
I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.
Click to expand...
Click to collapse
No

For future reference as posted in both the SS development thread and QA Thread OPs, Cyanogen and the like is not compatible with SS
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Also, if you are unable to restore with Odin and the MF3 files, I suggest mobitechvideos. They can possibly J-tag it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

HELP NEEDED! soft brick at&T s4 i337
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!

gtrijoe said:
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!
Click to expand...
Click to collapse
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Dude, you totally saved me. I soft bricked my galaxy s4 and tried everything to get it back up. couldnt get anything to take on it. Until I found this and I pushed it through via Odin 3.07 in the PDA slot. It took and I am back up. Much thanks my man

Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?

morphius2036 said:
Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?
Click to expand...
Click to collapse
There's a nb1 tar file in the general forum. Use that.
Sent from my Nexus 5 using XDA Free mobile app

Stuck in a boot loop even after flashing to stock from odin.

I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.

I'm in the same situation exactly. At the moment I'm trying to download UK 5.1 to play with odin once again.

did you manage to fix it?

BettlePimp said:
I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.
Click to expand...
Click to collapse
It looks like your problem is that you forgot to turn off the samsung activation lock before flashing. If you forgot what that is see this I have not used this feature on my phone; however, I would suggest wiping with odin then flash the official stock ROM for your phone that you previously had on it when it did work, hopefully it will boot then login to you samsung account when it asks you about the reactivation lock. There are some activation lock bypass methods out there if you do a quick google search. Hopefully this will point you in the right direction.

The reactivation lock is indeed on. "Reactivation Lock(KK): On"
I have no way of turning it off since I'm stuck in a boot loop no matter what firmware I flash through Odin.
Any other suggestions?

I have same problem on my SM-910H
This problem was after updating 5.1.1 and isntallind micro-sd card (128gb)
In 4-5 days after this, bootloop began.
I deisntalled micro sd, checked it in computer for mistakes, fixed it and after this phone worked fine.
Today same problem, but when I deisntall micro-sd my problem does not go away.
I downgraded phone to 4.4 - does not help
Data wipe, cache wipe etc - does not help...
Waiting for solution from proffesionals (
update^
I've found 4 file Factory firware and tried to falsh it
What does Odin say:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Do this, it worked for me. In ODIN, just AP/PDA Autoroot md5 file. It will not be successful and you will get "FAILED" message. Disconnect the phone from PC, pull out battery. Reinsert the battery and boot.

The same happened to me.

To all with this problem. My history:
1. Suddenly my stock device go in bootloop
2. Tried to flash it with official software it does not help
3. Tried to flash it with 3 or 4 file service firmware - did not help
4. Service center (not official, that was service center of my internet market) falshed it with some firmware and sad do not update it. It helped for 2 days.
5. They replaced the motherboard. Only this can help.
So, if you have bootloop in your stock device - try to falsh it with firmware if it does not help - take it to service center and say that they do not spent their and your time and change device or mother board.
Now its ok, working fine.
Wrote it because I spent a lot of time to repair it and maby it will help to some one.

I screwed up flashing with odin. Plz halp!

SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.

T1geR086 said:
SO, I made a stupid mistake and along with AP CSC and CP flashed BL to my Verizon S7. I tried to go back and do the steps correctly, but the odin flash's are failing now over and over. Get the "software update failed, use verizon repair assist." screen. Issue is in this state I can't get it in software install mode to use said repair assistant. Please tell me someone can help me fix my screw up!? I have googled and tried to solve this, but I came up empty.
Click to expand...
Click to collapse
What did you flash, firmware wise? What are you trying to flash?

I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.

T1geR086 said:
I was going from the newly updated PH1 (OTA) to Samsung_G930x_QC_Rooted_BOOT.TAR I was just not paying attention ...lol singing and goofing off but yeah I flashed BL AP CP and CSC.
ps. Then I did try to go back and flash the right things, but not surprisingly it was unsuccessful. I after that found a stock tar to try to redo the whole thing (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip) and that was also failed.
Click to expand...
Click to collapse
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app

ickedmel said:
I was having flashing issues before. I was doing it on my laptop. What I did was deleted the firmware files and re-downloaded it and was able to flash.
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried re downloading:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.tar
HEROQLTE_USA_VZW.pit Tried several more times.
Errors:
"re-partition operation has failed" nearly immediately after start of ODIN flash every time.
On boot attempts it does "erase" and "System Update", reboots and comes up in Android Recovery with "Supported API: 3" and "dm-verity verification failed..."
If someone could point me I don't mind learning and figuring it out, but yeah....tad frusterated so I'm gonna smoke some cancer lol brb.

Are you using the modified odin? The original one wont work. The modified one is in the root guide.

Do what he suggests. Use the modified Odin. If that does not work try swapping cables, computers, etc...

craazy82013 said:
Are you using the modified odin? The original one wont work. The modified one is in the root guide.
Click to expand...
Click to collapse
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Will try again.
Flash BL AP CP CSC, or BL AP CP CSC +pit or AP CP CSC?
Want to make sure I at least get this right.

T1geR086 said:
PrinceComsy version and the ? non PrinceComsy version linked in http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Neither worked. Everything failed the same way as described previously (re-partition op. failed, and on recovery dm-vert failure)
Click to expand...
Click to collapse
Does the phone even boot? USB debugging on?

craazy82013 said:
Does the phone even boot? USB debugging on?
Click to expand...
Click to collapse
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.

T1geR086 said:
It powers on. then go's to recovery, I have turned on USB debugging while trying to figure out wtf I did last night through maintence boot or not sure what its called but it has the option to enable debugging.
Click to expand...
Click to collapse
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.

craazy82013 said:
Check for usb debugging in maintenance mode. Power off device hold volume down and power at same time till maintenance mode shows up.
Click to expand...
Click to collapse
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.

T1geR086 said:
Does it stay enabled or do I need to do it every so often. I will do it again, but I had already last night.
Click to expand...
Click to collapse
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother

craazy82013 said:
I would think it would stay. I know you did some of this. Im not a dev. Just trying to help. Redownload everything. Try a different computer. Different usb cable. Try everything. Gotta get back to it but ill hit up a dev and see what he thinks. Sorry if im no help brother
Click to expand...
Click to collapse
Not trying to be short. Sorry if it came off that way. I appreciate hitting up a dev. I've been rather fixated on fixing this...*phone detox itch*

New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<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..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> 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)
Auth error instead of re-partition failure.

T1geR086 said:
New error (or first I noticed it) when attempting to flash:
BL_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
AP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CP_G935VVRS4APH1_CL8875708_QB10880117_REV02_user_l ow_ship_MULTI_CERT.tar
CSC_VZW_G935VVZW4APH1_CL8875708_QB10880117_REV02_u ser_low_ship_MULTI_CERT.tar
<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..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> 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)
Auth error instead of re-partition failure.
Click to expand...
Click to collapse
What version of Odin are you using?

Illogi.xbone said:
What version of Odin are you using?
Click to expand...
Click to collapse
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)

Try using Odin 3.14

T1geR086 said:
3.12 Princecomsy
I am DLing APE1 zip from sammobile because that's the version that shows up in recovery. heh have 2hrs left on that DL (non premium throttling)
Click to expand...
Click to collapse
Dont think you can downgrade ph1. Bootloader supposedly changed. There is a faster download in the forum. Way faster. http://downloadmirror.co/29Uj/G930VVRU2APE1_G930VVZW2APE1_VZW.zip<br />

Illogi.xbone said:
Try using Odin 3.14
Click to expand...
Click to collapse
Ty will try. Best place to find that? Odin downloader lists odin3 3.11.2 as latest? Didn't see any 14 ending versions.

Galaxy a5 2017 odin fails at cm.bin tried 2 lots fmware

Hi, tried to flash my a5 sm-a520f from 7.0 to 6.0.1 everything seems fine then it fails after cm.bin i've tried using A520FXXU1APLL VOD United Kingdom (Vodafone). and A520FXXU2AQF5 XEU United Kingdom.
I've searched but can't find a definitive answer. Tried as others suggested by changing ports several times and downloaded a second lot of firmware both for my phone and get the same.
Any help please?
Thanks
Below is log from the last time.
<ID:0/006> 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..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> Home Binary Download
<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> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.

So no one can help me?
I found out it's the bootloader and found posts about taking all the .bin files out before flashing but that would leave the whole of the BL file out which is like 4gb the bulk of the whole thing. I've tried 5 different UK roms. Tried using CSC instead of home_CSC and that time after sboot.bin in place of cm.bin there's param.bin and no cm. The phone does say odin mode at the top.
Found loads of posts saying because 7 has a different bootloader than 6 it can't be done but many people have done it successfully without a problem. Is there a way to flash it a different bootloader to downgrade to 6.0.1.
I have done a lot of searching about 15 hours worth but can't find the right solution.
I can't get into the phones settings because like a prat i did a factory reset without knowing the password for the email address. Bought the phone, got the login passwords/pattern so was able to use it but it still had sellers gmail and couldn't get in touch with the seller, still can't. Decided to do an frp unlock which i've done many times for people but never on android 7.0. Found out after trying all other methods i had to downgrade which brings me to this problem.
The phone never had/has the the usual startup logos for service providers so i don't know if that means it came without bloatware. I bought it network unlocked, he had it on o2. I've tried stock 6.0.1 firmware for o2, Voda, EE, XEU & BTU.
Please help, already receding don't want to make it worse!
Thanks

Hi. I guess you're on either A520FXXU3 or A520FXXU4 firmware., and that's why you won't be able to downgrade to any lower binary version. Normally it works fine to downgrade without the .bin files as you would still use the updated sboot and baseband ,but with older system files without any problems. All good for daily use, but not for frp reset.
Problem is that it won't help you to bypass frp because you still have the updated binary version.
What you need is a factory combination firmware with the same binary version that you have installed.
That would make it possible to flash it, enable oem unlock to remove the frp protection, then flash a full 4-file firmware with factory reset.

Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks

skg76 said:
Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks
Click to expand...
Click to collapse
Yes, afaik it should work.
Sent from my Moto G5 using Tapatalk

Did you manage to get this working? I can't find any decent links anywhere for the A520FXXU4ARA4 combination file, found one on pakfirmware but md5 was invalid and wouldnt accept in odin..

Sorry mate just seen your message. Yes it did work was a pain though, took a week. I think i found a link on boxwares.
link is here. clicking download leads to a fast google download.
https://shell.boxwares.com/Download.aspx?L=4474
If link is gone just google the combi and look for shell.boxwares link.
Afterwards i just used any u4 stock rom and it worked. Done like 30 phones with this method since.

Odin fail
Help!!
I have the same problem..i've tried everything even turned the anti virus off and nothing works..if i flash a different costum rom would it fix the problem or should i downgrade the firmware to nougat couse last version i had installed was oreo..

Bricked S7 Edge? AT&T

Hey folks, not quite sure where to turn from here or if this phone just goes to the dump...I was looking originally to unlock the AT&T S7 Edge I have and give it to a coworker who is on Verizon. Come to find this is a much larger task than I anticipated.
Device info: Galaxy S7 Edge AT&T SM-G935A
I attempted to follow the guide which started here: https://forum.xda-developers.com/verizon-s7-edge/how-to/odin-stock-nougat-firmware-t3570156
I downloaded the Samsung drivers, Odin v3.12.3 Patched, and the corresponding VZW firmware which I was under the impression was correct, from https://updato.com
I loaded Odin and the phone, ran the installer, and it looked kosher. The device passed, and it began to reboot. However, after that, it got stuck in the nightmare of recurring boot. I entered recovery mode, cleared cache and tried doing a factory reset, to no avail. Device keeps rebooting. Tried re-flashing firmware, no luck.
Where I got to:
On the downloading screen on the Edge:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-6935U <- (this seems wrong given it was AT&T, but I could be misinterpreting as I requested to have the device unlocked from AT&T and the person attempted activating on Verizon before all this)
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B8(2,1,1,1,1) K8 K8
SECURE DOWNLOAD: ENABLE
If I attempted to rerun any of the dozen or so firmware versions I've tried, I always got the following two errors:
In Odin:
<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/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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the device:
SW REV CHECK FAIL : [aboot] Fused 8 > Binary 4
After several hours I managed to get the phone semi-working.
I installed the G935UUEU8CRJ2 firmware from the web. It's the only one it would take as far as I can tell.
However there are two issues:
1. The device keeps restarting after 1-2 minutes of being powered on.
2. The firmware seems to be somehow Sprint? That doesn't make sense...
Android version: 9.0.0
Samsung Experience version: 9.0
Baseband version: G935UUEU8CRJ2
Kernel version: 3.18.71-13710210
Build number: R16NW.G935UUEU8CRJ2
Knox version: 3.1
I've tried running the factory reset from the GUI, but that didn't fix the restarting. Using the reset cache and factory wipe also did not fix the issue. Furthermore when booting into recovery mode initially it attempts to do a system update, then up pops the dead android with x's for eyes and the notorious yellow triangle, yet I can still access recovery mode after a few seconds.
Any suggestions?

Try this: https://www.mediafire.com/file/bzgzxqwafgpsk4c/G935AUCS8CRJ2_StockROM.zip/file

Leone/kyleproxx said:
Try this
Click to expand...
Click to collapse
There's a password on the file.

Update: I found the password. The ROM worked. It's back to AT&T. That solves my softbricking issue, but the original idea to switch it to Verizon is still at hand.
Is there any way to successfully do this?

Leomacomp said:
Update: I found the password. The ROM worked. It's back to AT&T. That solves my softbricking issue, but the original idea to switch it to Verizon is still at hand.
Is there any way to successfully do this?
Click to expand...
Click to collapse
I dont know what to do to switch to verizon

Leone/kyleproxx said:
I dont know what to do to switch to verizon
Click to expand...
Click to collapse
No worries. I actually found the correct VZW ROM (For any of those looking in the future it's: G935VVRU8CRJ3-StockROM-G935V-(-BIT
I loaded this using "Odin 3.13.1 Patched" (The SHA256 bypass). It installed successfully and works now on Verizon's network.
Thanks for the assist!

Leomacomp said:
No worries. I actually found the correct VZW ROM (For any of those looking in the future it's: G935VVRU8CRJ3-StockROM-G935V-(-BIT
I loaded this using "Odin 3.13.1 Patched" (The SHA256 bypass). It installed successfully and works now on Verizon's network.
Thanks for the assist!
Click to expand...
Click to collapse
Your Welcome :good:

Leomacomp said:
There's a password on the file.
Click to expand...
Click to collapse
Hello mate can you plz post the file pass TIA :good:

fabian108 said:
Hello mate can you plz post the file pass TIA :good:
Click to expand...
Click to collapse
The password is www.samkey.org/forum
Ps: and yes the actual website name is the password.

Thanks for solving my issue
I found this thread searching for a way to restore my AT&T branded Samsung Galaxy S7 Edge(SM-G935A), which I thought I might have bricked since it was stuck in a boot loop. Using the stock rom I found on this thread, I was able to get the phone going again. I spent many hours searching and trying different roms, and this was the only one I could get to work. It was FRP locked, but I knew the password. Just could not get past the loop to enter it.
Thus, I wish to say thank you for posting this thread, without it I would still be looking at a boot loop!

friends will have one for bynario 9 I have the same problem please