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
Hi. Recently i've updated my Note 5 to Nougat and trying to root my phone. At first when i flashed TWRP is successful.
But after that my phone just bootloops endlessly. I tried flashing back to the stock but my device says SYSTEM REV. CHECK FAIL. DEVICE:1 BINARY: 0
please help me as im in need of my phone and all my important datas is inside my device :crying::crying::crying:
and here i include odin 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..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
<ID:0/004> 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/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that happened twice while trying to flash stock nougat firmware after some buggy custom roms.
smart switch from samsung for drivers on windows 10 installed, com 4 connected, whenever i try to flash the 4 parted firmware (cl, bl, ap,csc) it gives me a fail after some time with log above.
thanks for any help how to get back to stock
device wants me to use emergency recovery from smart switch but end of month small bandwith left i would have liked to prevent downloading another 4gb through smart switch as i have the nougat stock files on hdd.
thanks!
I need to make this SM-J530F work again in a day, I've tried installing supposedly OEM Stock, because all custom roms have had issues, either terrible sound issues, lock due to aosp and samsung payment app missing. random semi bricks. I don't need this ****e right now. I hope someone can recommend a rom which wouldn't have any bugs, or help me install the stock OEM rom, which i then hopefully can MicroG, and OpenGapps, supersu.
I've tried two different files now through odin and they both failed. I'm not sure what's wrong, device is wiped, put in download mode and connected to odin. Blue checks out it seems to start. But ultimately fails. The firmware files were zip files, I tried chaning it to .tar, and tried loading in AP alone, and AP, and all the others, alternating between two csc files which were included inside the .zip.
Re partitioning is not on.
Twrp 3.3
SM-J530F
Odin 3.13
Here's what happens when I first tried to just use the AP, and then all the files inside the OEM ROM file.
<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> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2909 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> __XmitData_Write
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:13130560/000> Odin engine v(ID:3.1301)..
<ID:13130560/000> send REBOOT_ODIN command (COM:6)
<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.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2983 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
second attempt
<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..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2909 M
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<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.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2983 M
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device purchased from Sweden.
ClownWorld said:
I need to make this SM-J530F work again in a day, I've tried installing supposedly OEM Stock, because all custom roms have had issues, either terrible sound issues, lock due to aosp and samsung payment app missing. random semi bricks. I don't need this ****e right now. I hope someone can recommend a rom which wouldn't have any bugs, or help me install the stock OEM rom, which i then hopefully can MicroG, and OpenGapps, supersu.
I've tried two different files now through odin and they both failed. I'm not sure what's wrong, device is wiped, put in download mode and connected to odin. Blue checks out it seems to start. But ultimately fails. The firmware files were zip files, I tried chaning it to .tar, and tried loading in AP alone, and AP, and all the others, alternating between two csc files which were included inside the .zip.
Re partitioning is not on.
Twrp 3.3
SM-J530F
Odin 3.13
Here's what happens when I first tried to just use the AP, and then all the files inside the OEM ROM file.
<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> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2909 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> __XmitData_Write
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:13130560/000> Odin engine v(ID:3.1301)..
<ID:13130560/000> send REBOOT_ODIN command (COM:6)
<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.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2983 M
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
second attempt
<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..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2909 M
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<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.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 2983 M
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device purchased from Sweden.
Click to expand...
Click to collapse
Did you start Download mode throught TWRP or button combination?
(It didn't work for me if I rebooted to download mode throught TWRP)
EDIT: Another thing that poped up in my mind is launching ODIN in administrator mode.
EDIT: You might have the wrong version of bootloader