I recently screwed up my S5 active and am desperate for help.
I only ever really occasionally screw with the OS, and I did a poor job of documenting what I did with this phone, so I will do my best to recollect exactly the state.
The phone is an AT&T Samsung Galaxy S5 active, model G870A
The recovery was some kind of robot icon that would show for maybe ~10 seconds at the start of boot (not a regular android, more square). I've tried searching for it to, as yet, no avail.
I'm fairly certain that the image I put on the device was KoolKit_S5_Active_V1.1.0.
I cannot recall if I used safestrap, towelroot, twrp, or some combination of these in order to get the above on the device. I have copies of each sitting in a folder I created for the phone.
The other day, SuperSU said it needed the binary updated. Me, being dumb, wanting the notification to go away, decided to appease it. It asked if I wanted to do so using recovery. I figured this would be easier, so I clicked "yes". And then my life got a lot more stressful.
When the phone boots now, it goes into ODIN mode and displays the message "android could not do normal boot. ODIN MODE".
I cannot get it to any other screen. Recovery, download mode, whatever. (I'm pretty sure this is download mode, but I cannot initiate any mode, it just goes into this).
I've been poking around on these forums. The first suggestion I thought might work was to use ODIN to (re?) flash towelroot. Or TWRP. I forget which one I tried, but it wound up resulting in a failure in ODIN, and a message on the screen stating something along the lines of "sys rev check fail no version".
I am very confused about what I need to be flashing using ODIN, but I have managed to cobble together that it has to be through ODIN.
I don't necessarily need links, I can find those, and I may already have the files. I'd really like to know which files it is that I need.
Do I need a firmware? What is the file format for that? tar.md5? etc.
Ideally I'd just like to get back to a regular run mode where my worst problem was a wonky USB port. I would deeply appreciate it if anyone could get me in that direction.
Thank you
It's working.
I plugged it in, tried to flash a PIT file. That failed. Apparently one does not flash those alone.
The screen said something like "check failed : PIT" ...
I went here:
http://forum.xda-developers.com/showthread.php?t=2799754
Followed the instructions. Got a failure. (This was, stupidly and fortunately, without restarting phone after pit failure).
Phone rebooted like nothing was ever wrong.
ODIN log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
Click to expand...
Click to collapse
P.S.: Previously unidentified robot was safestrap:
http://img.wonderhowto.com/img/96/6...hwiz-launcher-your-samsung-galaxy-s5.w654.jpg
Im glad you could fix it.
I also have a problem with a AT&T S5 active, the phone has horrible screen lag (even the booting screen is slow)
I tried doing a factory reset and also doing a downgrade to kit-kat using Odin, but the problem persists
Related
I have received a GT-i8190 which is messed up.
When I start the phone, it says something went wrong with firmware upgrade, and that I need to try installing again.
Tried to install new firmware I8190DXALL3_I8190OLBALL4 using Odin3 v3.07.
Have followed the instructions with PDA only, no re-partition etc...
When I press start in Odin, Firmware update starts, and I can follow progress bar in Odin3 as well as on the phone.
Unfortunately, the process hangs when it tries to write STE_boot2.img, and after waiting a long time I get a write fail.
Have tried with other firmware versions, but each version eventually hangs somewhere (not always with STE_boot2.img). Below an extract of what I get from Odin3.
Any suggestions anyone?
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190DXALL3_I8190OLBALL4_HOME.TAR.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> system.img
<ID:0/010> NAND Write Start!!
<ID:0/010> STE_boot2.img
Is your battery full, when you are trying to flash the firmwhere? Did you try another cable? Is your computer going to standby with some component or are you actively waiting moving the mouse cursor? If nothing helps, try to flash from another computer.
rarog said:
Is your battery full, when you are trying to flash the firmwhere? Did you try another cable? Is your computer going to standby with some component or are you actively waiting moving the mouse cursor? If nothing helps, try to flash from another computer.
Click to expand...
Click to collapse
First system I used was Vista; battery was full. System does not go on standby.
Have tried on different system (windows 7) with different cable. Now Odin does not hang as it did on the vista system, but Odin crashes at the same moment it hung on the vista system, with the message: Odin Downloader stopped working.
Have tried with Odin3 V3.07 and V1.85
Any other suggestions?
Try with firmware from here: http://forum.xda-developers.com/showthread.php?t=2157105.
Download "I8190 серв. укр.rar". It's made out of service firmware with additional files not included in official firmware.:good:
If that won't do it, then take it to samsung.
tys0n said:
Try with firmware from here: http://forum.xda-developers.com/showthread.php?t=2157105.
Download "I8190 серв. укр.rar". It's made out of service firmware with additional files not included in official firmware.:good:
If that won't do it, then take it to samsung.
Click to expand...
Click to collapse
Well, have used this service firmware following the instructions.
Everything went wel at firstl; could follow the progress in Odin, eventually the phone went down after 8 mins), I assumed for reboot but it did not restart.
Odin then finished stating everything passed (green), so disconnected the phone and tried to start up, unfortunately without success.
I thought that the battery was empty, but I have checked with another phone and it is still at 75%.
I guess the phone is now completely wasted, unless someone still has an idea to revive it?
Hey guys,
Last night I looked at my phone (which had been on charge for a while) and noticed that it was on the first S3 boot screen. So I assumed it had crashed and got stuck whilst rebooting, so I held the power button to reset it.
Problem is, it came back to the same screen, except this time the black background of the image was distorted - lots of red/green/blue dots on it. So I tried again, and it came back even worse... The third time, it settled on a completely distorted image and is now seemingly stuck like that.
The phone isn't booting, so far as I can tell. If I try to boot to recovery, I just see the same screen. If I boot into download mode, it actually works - the screen is no longer corrupt and it responds to button presses. (Although itnerestingly if I continue to hold Home + Vol Down + Power once the download screen appears, then it does distort).
I have tried plugging it into my PC. I don't see it as a MTP device (no suprises there), and ADB can't find it. It is however recognised by odin. I tried flashing a stock rom via odin, but it complained that there was no PIT found. (Which if I understand if something to do with the partitioning of the device.
Any ideas on how to solve this? Should I find a PIT image for my phone and flash that and the ROM together?
For background, my phone is a i9305 and was running paranoid android (4.2, IIRC).
Dont touch pit
First flash stock rom via Odin
JJEgan said:
Dont touch pit
First flash stock rom via Odin
Click to expand...
Click to collapse
When I try that, I get the following error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was why I was wondering about the PIT file.
I have also added some pictures (they're pretty low resolution, unfortunately). The first is what I see when I try to boot normally - lots of white and black bands (the yellow and purple you can see is just an artefact of my crappy webcam). The second image is download mode, where I continued to hold down the buttons after it loaded, causing it to reload with the corrupted image (again, this is a bit distorted by the webcam - the text and image aren't blurred).
no access to system and recovery,i doubt theonly way is download mode.just try an stock rom with pit files,agree that the issue have something to with the partition.if you have backup the whole system,even flash a new rom,youdata will be back easy and soon ,so nothing to worried and no way else to go,good luck.
Sent from my GT-I9305
As pit breaks more phones than it fixes its not recommended .
But your phone has no pit so you you have choices .
Warranty void so it would have to be a service repair .
Or you can try flashing a pit file yourself if it fails you will need to buy a new motherboard .
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Darkangel142 said:
I´ve had the same Problem on my S1.
I Flashed a whole Package from Samsung Stock Firmware ( PIT MODEM PDA ) in Odin.
After that it worked again, i´ve needed some try´s but after that everythin was normal.
Darkangel 142
Click to expand...
Click to collapse
Do you mean specifically that you had the same error in odin, or that your S1 had the distorted screen too?
Well, I tried flashing the i9305 pit file and had no luck. The re-partitioning failed to start at all, so it didn't ruin the motherboard, at least.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305EVRALI5_I9305BVALI5_HOME.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> FAIL!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Back to orange/samsung it is!
Thanks for your suggestions/help, everyone.
Any joy?
Hi,
I've posted about the same problem. Completely stuck on who to deal with and can fix it How weird to have happened so close and exactly same with black screen then stuck on white, Wonder if others are out there.
Link: http://forum.xda-developers.com/showthread.php?t=2526821
stuck screen
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
einjelhart said:
i have the same problem with my s3 and i couldn't do the download mode. im planning to restore on stock rom but i don't know how to fix this issues.
thanks,
Click to expand...
Click to collapse
Hi mate,
If you can't get in to Download Mode because of boot loop:
Try forcing it by holding all 3 buttons until it turns off, should come up.
Failing that, you can eBay Galaxy USB Jig that plugs in and forces Download Mode.
If you can get to Download Mode, I have written a solution to flash just the ROM.
You can read my solution by following the Link above your post
Have a great day!
-Shaz
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Debanshu bebartta said:
Same problem with my s3 ,but Odin doesn't recognise my device ,please help
Click to expand...
Click to collapse
I had these prob before; device not recognize in odin, distortion screen with colorful line, stuck at boot logo & splash screen.. I tried flash lot of thing possible to fix it but all fail. Suddenly everything working fine after changing new battery.. Lol. Or maybe im just lucky.
Sent from my GT-I9305 using XDA-Developers mobile app
Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Click to expand...
Click to collapse
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.
Unkiejay said:
Hi,
I've been searching the net and this forum for a fix, it seems like a few people have had the same issue as me, but either their post is unanswered or they say they've fixed it but never say how.
My phone one day went into a infinite loop of the Samsung Splash screen and I tried fixing it by googling the issue (Over 5 months ago) which may have caused more issues for my phone in the end. I remember entering recovery mode and wiping everything on the phone, then nothing I did could fix the thing.
So I just stopped touching it and left it to collect dust and used my old iPhone 3. My iPhone 3 is now broken and I've come back to my S3, so at the moment:
I can't enter recovery mode on my phone (It just won't start in recovery mode at all)
I CAN enter download mode
I've tried using ODIN (v3.09, 3.07, 1.85) and changing multiple USB ports and I was finally able to get my phone to show up on Odin.
I then downloaded the stock firmware from sammmobile website (It took forever to download) Which I made sure was the right model (GT-I9305) and Carrier (Optus, Australia)
Which is filename: I9305XXALI5_I9305OPSALI5_I9305XXALI5_HOME.tar.md5
I tried flashing that firmware with Odin (All 3 versions) [I reset the phone and Odin after every failed attempt]
and I would get this error:
That was WITHOUT having a PIT file included and also the only things ticked were 'Auto Reboot' and 'F. Reset Time'.
Then I searched all over the internet and came across this PIT Partition file
the filename is: m3xx_i9305.pit
which I then used in the PIT section of Odin WITH and WITHOUT the previously mentioned Firmware and I would then get this:
It would just sit on Get PIT for mapping for a very long time, longest I left it was an hour.
So I can't get it working that way, I also tried ADB Bootloading in the CMD prompt, but the device could never be found that way.
So after spending about 5 hours on this I'm resorting to just asking anyone on here for some help.
Thank you!
Phone Details:
Samsung Galaxy S3 GT-I9305
ODIN MODE:
Product Name: GT-I9305
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
Knox Warranty Void: 0
RP SWREV:
Computer Details:
Windows 8.1 Pro
Intel 2700k @ 3.5Ghz
16gb Ram
Samsung USB Drivers Installed
If there is any additional information required please let me know. This is my first time posting here, so If I did anything wrong please let me know.
Thank you.
Click to expand...
Click to collapse
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?
Wood Man said:
I've read you tried with different USB ports, OK, but did you try with a different USB cable when you use ODIN ? A brand new one ?
Click to expand...
Click to collapse
i am facing the same exact same probelm. i tried with different usb ports and cable results are the same . please someone help
:crying:
Hello everyone,
It seems I managed to soft-brick my i9000 today. I was checking out the list of firmware available here and chose the Gingerbread 2.3.6 MultiCSC ROM for Europe. I also wanted to re-partition the device and I used the s1_odin_20100803 file during the installation process.
With the Odin v1.82 version provided in the topic, I rebooted the phone in the Download mode and it was quickly recognized by Odin. I put each file in place and started the flashing process, and I received the following messages:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_XWJW5_Sbl.tar.md5 is valid.
<OSM> PHONE_XDJV1.tar.md5 is valid.
<OSM> CSC_OXXJVC.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I get the soft brick image when I turn on the phone, and now I have several details that might give you an easier time when providing solutions:
The phone still boots in Download mode and it gets warm while it's connected, so it should also charge.
The phone is still seen by Odin when I connect it in Download mode.
I already had the required USB drivers installed and I have also installed the Nexus S ones after the brick (I've read somewhere they could help).
I tried the OneClick UnBrick tool and I get the "Failed" message.
I tried flashing the s1_odin_20100512.pit file on its own, as I've seen in an unbricking guide here, with no results.
The phone was rooted and it was running a custom ROM, above 4.0.0, although I am not sure at the moment what ROM was installed.
I used an original cable, and tried all the ports on my laptop (the only device I have available), running Windows 10 64-bit.
What should I try now? Thank you all for your help.
----------
Edit 17:39:
The phone started, and I have done the following in order to achieve this, although I am not sure about the fact that I've done the right things:
I decided to go with this guide and performed the steps listed there. First time, i left the "kernel" uncapitalized and the cmd returned the "Partition "kernel" does not exist in the specified PIT. Ending session... Releasing device interface..." message. I discovered that "KERNEL" might be a solution and decided to go with it. This time, the cmd returned the "ERROR: Protocol initialisation failed!" Releasing device interface..."
I took the battery off in order to get rid of the Download mode, and just put it back in. Then, I connected the phone via USB and the charging image appeared. Then, the phone booted normally. I'm still not convinced about what solved this.
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Jeppe_77 said:
Hi folks,
I friend of mine have this phone that is stuck in Odin mode. The problem is that none of the "press and hold keys" commands work and the phone just reboots into Odin every time. She has "tons" of Pictures of her first born Child on the device, without any cloud backup! :crying:
Any suggestions what to try next?
What i have done so far:
Trying all the "press and hold keys"
Letting the battery drain out and the hook up the Power to it... When connecting Power the screen turns White for 15-20 minutes and then if i reboot it, it goes back to Odin/download mode...
Is it possible that opening the phone and removing the battery could work?
Click to expand...
Click to collapse
I am no expert, just going to suggest what I would try, hopefully someone may know what to do exactly.
You could try downloading stock filmware from Sammobile or updato (making sure to at least flash the same filmware build or higher, or Odin won't flash it) if you use the "home csc" csc file, it should not wipe the data on the phone, and what I hope may fix the phone not booting.
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Get a pit file and flash it though oden may work or not.......
yashthemw said:
First of all you should have mentioned the model no. Second, you can try flashing the stock firmware from sammobile. Now, the tricky part is, if prior to this soft brick the phone was on a custom rom or had been rooted, then flashing the firmware alone won't bring the device back to life, a factory reset will be needed after flashing stock firmware, which doesnt seems like a favorable option considering that the data on device is important. There can be other ways to fix this without losing the data but for that illl need to know the device details.
Oh and btw, opening the device and messing with the battery won't help at all. Don't do that.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Its an Galaxy Note 8 (SM-N950F)
The only thing i can see in the display is
https:// imgshare.io/image/odin-2.U7KCu
We dont know what firmware was beeing used Before this, it´s not custom or rooted tho. I assume its the latest official tho
I grabbed the latest from Sammobile, N950FXXU7DSJ1_N950FCKH7DSJ1_HTS
I could try the above suggestions but what about trying to flash the BL? Could it not be the BL that is cuppupt somehow?
I did try and flash the BL now but Odin software says:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 7 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems the partitions are gone, @stinka318. Next, where do i find PIT-files?
Found PIT file but it failed.
Also tried CSC flash but it fails (looks like Odin might not cennect to the device (ID:COM 0: [COM4])
<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.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 179 M
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Driver related? i have the Samsung USB drivers installed….
https://zfirmware.com/download-samsung-galaxy-note-8-pit-file/
Seems like it's a kernel problem, or maybe the phone IMEI reported stolen?
Have you tried installing custom binaries? TWRP maybe?
Or messing with OEM unlock found in Developer Options?
Most of the for solving such problem, you have to flash the exact same firmware found on phone before the problem.
Try rooting using odin and then twrp and thenflashing a custom firmware..... That could help..... Just a thought.... Wipe everything except internal storage
https://mega.nz/#!Lk8RiKQR!FiH50HLQp1aijVkRARSPtBN6M6wFphShHsm7i6u23lw
Try flashing this via odin through AP.
Sent from my SM-N950F using Tapatalk