Odin for Samsung: download, versions and Odin mode

Odin is the Windows program that writes firmware to a Galaxy phone or tablet over USB. Samsung uses it in service centres and never released it publicly, which is why it is passed around in so many versions. This page covers which one to use, how to get the device into Odin mode and what the log is telling you when something fails.

Download Odin

Odin needs no installation: extract the ZIP to a folder and run the .exe, preferably as administrator.

VersionUse it forDownload
Odin3 v3.14.4Any current Galaxy device. Start with this one.Odin3-v3.14.4.zip (4.4 MB)
Odin3 v3.14.1The previous release, if 3.14.4 misbehaves on your PC.odin3_v3.14.1.zip (2.5 MB)
Odin3 v3.13.1A fallback if 3.14.4 does not detect an older device.Odin3_v3.13.1.zip (3.4 MB)
Odin3 v3.12.3Devices from around 2016 to 2018 with firmware that has no .lz4 files.Odin3_v3.12.3.zip (1.1 MB)
Odin v3.09 / v3.07Galaxy S3 to S5 era phones.Odin_v3.09.zip, Odin_v3.07.zip
Odin v1.85Only the first Galaxy S and S2 generation.Odin_v1.85.zip

You also need the Samsung USB driver for Windows. Without it Windows sees an unknown device and Odin never shows a COM port. Get it from Samsung's developer site, install it, and restart the PC once.

Which version to use

Newer is almost always the right answer. Since about 2019 Samsung packs the partition images inside the firmware as .img.lz4 files. Odin versions before 3.13 cannot unpack them and fail on the very first file, so an old Odin with a new firmware gives errors that look like a broken download.

The reverse is rarely a problem: v3.14.4 flashes old firmware fine. Reach for an older Odin only when a device from the KitKat or Lollipop years is not detected at all.

Skip anything called "Odin patched" or "3B patched". Those builds remove checks so that firmware for another model can be loaded, which is the quickest way to end up with a device that does not boot.

What Odin mode is and how to enter it

Odin mode and Download mode are the same thing. It is a small loader that runs before Android and waits for a PC to send firmware. The screen is blue or black with "Downloading... Do not turn off target", and on older phones a green Android robot.

Power the device off fully, then:

  • Most phones from 2019 on (no Home or Bixby button): hold Volume Up and Volume Down together and plug the USB cable into the PC.
  • Phones with a Bixby key (S8, S9, S10, Note 8, Note 9): hold Volume Down and Bixby, then press Power.
  • Older phones with a Home button: hold Volume Down, Home and Power.

A warning screen appears first. Press Volume Up once, briefly, to continue. Holding it longer on newer models opens the bootloader unlock screen, which you do not want.

To leave Odin mode without flashing, hold Volume Down and Power for about ten seconds.

The Odin window, briefly

  • ID:COM lights up blue or yellow with a port number when the device is connected. The log says "Added!!". No port means a driver or cable problem, not a firmware problem.
  • BL, AP, CP, CSC take the matching .tar.md5 files from the firmware ZIP. Use CSC for a clean install or HOME_CSC to keep data, never both.
  • Options: leave Auto Reboot and F. Reset Time ticked. Leave Re-Partition and Nand Erase alone unless you know why you need them.
  • Log: the useful part. When a flash fails, the last few lines say why.

The full procedure, with the meaning of each file, is in the step-by-step flashing guide.

Odin errors and what they mean

No COM port, Odin does not see the device

Reinstall the Samsung USB driver, close Smart Switch (it grabs the connection), use a different cable and a USB port on the back of the PC. Front panel ports and hubs cause more failures than anything else.

Stuck at "Initialization" or "SetupConnection"

Same cause as above in most cases: the link drops while Odin talks to the phone. Change the cable first, then the port.

"Invalid ext4 image" or the flash fails at system.img.lz4

Your Odin is too old for the firmware. Use v3.14.4.

"MD5 error! Binary is invalid"

The file is damaged, usually from an interrupted download or an extraction that ran out of disk space. Download the firmware again and extract it with 7-Zip.

"SW REV CHECK FAIL"

The firmware has a lower bootloader binary than the phone. This is a hardware rule and cannot be forced. See how to downgrade Samsung firmware for how to read the binary and pick a build that will install.

"Model mismatch" or "FAIL! (Auth)"

The firmware is for a different model number. SM-S918B and SM-S918U are both a Galaxy S23 Ultra but take different firmware. Check the model in Settings or on the Odin mode screen and download for that exact number.

Odin seems frozen after you pick the AP file

It is checking the MD5 of a file that can be over 8 GB. Wait; it can take a few minutes on a slow disk.

Odin on Mac, Linux or a phone

There is no official Odin for anything other than Windows. On macOS and Linux the usual option is Heimdall, an open source tool that speaks the same protocol, but it has not kept up with recent devices and fails on many current ones. In practice a Windows PC, or a Windows virtual machine with USB passthrough, is the reliable route. "Mobile Odin" apps need root and are useless for a phone that does not boot.

FAQ

Is Odin safe to use?

The tool itself is. The risk is in what you flash. Official firmware for your exact model number does not void Knox or unlock anything. Modified files or patched Odin builds do.

Does flashing with Odin delete my data?

With the CSC file, yes, everything. With HOME_CSC your apps and files normally stay, but back up anyway: a failed flash can still leave you needing a reset.

Where do I get the firmware?

Search for your model number on the models page, pick your region (CSC) and download the build. If you are not sure about the region code, see the list of Samsung CSC codes.

Related guides

Find firmware for your modelAll guides