OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux

Search This thread

TheAirBlow

Member
May 7, 2021
40
32
Samsung's Odin on Linux is no longer a dream! This is an official version leaked from Samsung.

WARNING! Don't DM me stupid questions, I'm not tech support and I'm not going to teach you linux.


Here's the output you get from
Code:
odin -h
Code:
Usage : odin4 [args...]
Odin4 downloader. odin4 version 1.2.1-dc05e3ea
 -v        SHOW VERSION
 -w        Show License
 -b        Add Bootloader file
 -a        Add AP image file
 -c        Add CP image file
 -s        Add CSC file
 -u        Add UMS file
 -e        Set Nand erase option
 -V        Home binary validation check with pit file
 --reboot  Reboot into normal mode
 --redownload   Reboot into download mode if it possible (not working in normal case)
 -d        Set a device path (detect automatically without this option)
 -l        Show downloadable devices path

IMPORTANT : You must set up your system to detect your device on LINUX host.
 create this file: /etc/udev/rules.d/51-android.rules
 to add a line to the file:
 SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
   (http://developer.android.com/tools/device.html)
 And you maybe need to unload a module cdc_acm before downloading. (This is only needed for older kernels.)
   $sudo rmmod cdc_acm
 OR
   echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf

Example :
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
Example (Select One Device):
$odin4 -l
PATH_OF_DEVICE_A
PATH_OF_DEVICE_B
$odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A

Odin Community : http://mobilerndhub.sec.samsung.net/hub/site/odin/

You can even verify that's the real one by comparing it's code with the Windows Odin.
For some reason some method names were left unmodified.
Have a nice day!
 
Last edited:
OMFG! You are a godsend!!! I was skeptical at first when I saw this post, wondering how I never saw this before today... However, I just tried it out and it worked 100% and quickly!

I have tried every other linux solution and every last one came up bust until now. Thanks again!
Screenshot_2022-10-26_04-59-27.png
 
  • Like
  • Love
Reactions: BookCase and grm34

mark86v1

Member
Dec 12, 2022
8
0
OMFG! You are a godsend!!! I was skeptical at first when I saw this post, wondering how I never saw this before today... However, I just tried it out and it worked 100% and quickly!

I have tried every other linux solution and every last one came up bust until now. Thanks again!
View attachment 5743797
What is the command you executed before this? Please tell clearly. I want to flash TWRP.
 

mark86v1

Member
Dec 12, 2022
8
0
I somehow got rid of the above error and flashed BL, AP, CP, CSC files using Linux ODIN. Now can anyone guide me with the steps to install TWRP correctly, install lineage os and root my phone. It would be really helpful.
 

Top Liked Posts

  • 1
    When I try flash with Jodin3Casual I get this notifications:
    So Jodin3 seems to rely on having a pit file.
    Did you look for it inside CSC...tar.md5 as I wrote and there is none?
    Which stock are you trying to flash anyway?
    If you're having windows installed and there Odin doesn't work either (there it should for sure without pit) then I assume your device/USB-cable/-port is the problem.
  • 2
    I downloaded Odin. zip from the first page this theme. I extracted it. How I can install Odin on Linux? Command: odin -h not work for me.
    go to the directory you extracted it to. then run:
    chmod +x odin4

    then:
    ./odin4
    2
    I installed Jodin3Casual on Ubuntu. When I connect Phone with USB in Download Mode, it Connected. When I used AP, BL, CP and CSC and Start, Jodin Disconected. I need somthing for PIT.
    a pit file is imho only necessary when you want either to repartition the device (changing sizes aso) or your device as a wrong ROM flashed or is somehow corrupted.
    I usually flash with Odin without pit files.
    If you really need it it's often inside the CSC...tar.md5 file from where you have to extract it first.
    1
    go to the directory you extracted it to. then run:
    chmod +x odin4

    then:
    ./odin4
    What extracted? I pasted odin4 in /usr/local/bin. In bin I can't open Terminal.
    1
    What extracted? I pasted odin4 in /usr/local/bin. In bin I can't open Terminal.
    The terminal should be its own application. Try following these steps:
    First run the terminal,
    Then run this command:
    Bash:
    cd /usr/local/bin
    Next, run this command (it may need to be run with sudo):
    Bash:
    chmod +x odin4
    Finally, run this:
    Bash:
    ./odin4
    The first command changes the directory you are in, the second one changes the permissions to make the odin4 file executable, and the third runs odin4. Please let me know if you have any questions.
    1
    When I try flash with Jodin3Casual I get this notifications:
    So Jodin3 seems to rely on having a pit file.
    Did you look for it inside CSC...tar.md5 as I wrote and there is none?
    Which stock are you trying to flash anyway?
    If you're having windows installed and there Odin doesn't work either (there it should for sure without pit) then I assume your device/USB-cable/-port is the problem.
  • 19
    Samsung's Odin on Linux is no longer a dream! This is an official version leaked from Samsung.

    WARNING! Don't DM me stupid questions, I'm not tech support and I'm not going to teach you linux.


    Here's the output you get from
    Code:
    odin -h
    Code:
    Usage : odin4 [args...]
    Odin4 downloader. odin4 version 1.2.1-dc05e3ea
     -v        SHOW VERSION
     -w        Show License
     -b        Add Bootloader file
     -a        Add AP image file
     -c        Add CP image file
     -s        Add CSC file
     -u        Add UMS file
     -e        Set Nand erase option
     -V        Home binary validation check with pit file
     --reboot  Reboot into normal mode
     --redownload   Reboot into download mode if it possible (not working in normal case)
     -d        Set a device path (detect automatically without this option)
     -l        Show downloadable devices path
    
    IMPORTANT : You must set up your system to detect your device on LINUX host.
     create this file: /etc/udev/rules.d/51-android.rules
     to add a line to the file:
     SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
       (http://developer.android.com/tools/device.html)
     And you maybe need to unload a module cdc_acm before downloading. (This is only needed for older kernels.)
       $sudo rmmod cdc_acm
     OR
       echo "blacklist cdc_acm" > /etc/modprobe.d/cdc_acm-blacklist.conf
    
    Example :
    $odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5
    Example (Select One Device):
    $odin4 -l
    PATH_OF_DEVICE_A
    PATH_OF_DEVICE_B
    $odin4 -b BL_XXXX.tar.md5 -a AP_XXXX.tar.md5 -c CP_XXXX.tar.md5 -s CSC_XXXX.tar.md5 -d PATH_OF_DEVICE_A
    
    Odin Community : http://mobilerndhub.sec.samsung.net/hub/site/odin/

    You can even verify that's the real one by comparing it's code with the Windows Odin.
    For some reason some method names were left unmodified.
    Have a nice day!
    8
    It is in the archive attached. XDA doesn't allow for no-extension files to be uploaded.
    2
    OMFG! You are a godsend!!! I was skeptical at first when I saw this post, wondering how I never saw this before today... However, I just tried it out and it worked 100% and quickly!

    I have tried every other linux solution and every last one came up bust until now. Thanks again!
    Screenshot_2022-10-26_04-59-27.png
    2
    I successfully flashed lineage os recovery on Samsung a52q using that tool. I want to emphasize that rmmod cdc_acm was a mandatory step for me. Without it I got
    ioctl bulk read Fail : Connection timed out 110 error. That's quite strange, given the fact that module count usage was zero and /dev/ttyACM device was not created. But still the module interfered with the flashing process somehow.

    Also I decided not to mess with udev rules and just issued chown my_user /dev/bus/usb/xxx/yyy.
    Whats was enough.
    2
    Thanks a lot @TheAirBlow !

    I just tested, I was able to downgrade/update official firmware and flash my bootloader without problems. Really great, it was really annoying to have to use a VM for that.

    🙏