OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux

Search This thread

akamaus

New member
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.
 
  • Like
Reactions: NielDK and Mates11

uluruman

Senior Member
Oct 23, 2021
244
40
Hello! Can you to public source code? And port Odin for Linux for ARM. It's only for x86
If you want something open-source there is a working version of Heimdall from amo13. For simplified flashing of separate image files (or any other files) or the whole stock firmware using Heimdall there are my scripts, theoretically they should work with any Samsung phone (except for the main repacksuper.sh which is for Treble-enabled phones only).
 

NielDK

Inactive Recognized Developer
Jul 13, 2008
540
141
Farum
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.
Interrestingly this is the error I get , when trying to flash my SM-G991B (Galaxy S21 5G/ EU). So far I have not been able to finish the flashing on this device, with this tool.
 
Jan 27, 2023
5
0
Fist, many thanks for all the information on this forum and the Odin tool for linux!
I just registered to post here. i am new to android modding but I have already educated myself somewhat. I want to flash TWRP to my A8 to get started but I run into a problem I cannot resolve after researching for many hours. I use ubuntu 20.04.
FRP unlocked
OEM unlocked
KG state checking (not prenormal)

When trying to flash twrp, I get the lines:
Fail request receive -1
FAIL close
Fail Close Connection
Upon rebooting I get this screen (kinda soft brick?)
1674814804011.png

I can fix and restart the phone by flashing the stock AP file with this odin here.
Thanks for any advice.

Terminal screenshot attached
 

Attachments

  • Screenshot from 2023-01-27 11-30-52.png
    Screenshot from 2023-01-27 11-30-52.png
    242.2 KB · Views: 137
Last edited:

PalmerBE

Member
Nov 11, 2021
18
3
Hi,
I am in the same situation.

How do I flash the vbmeta ?

I tried with :
"odin4 -a A528BXXU1CVG7_patched_vbmeta.tar -d /dev/bus/usb/003/17 "

But I got :

/dev/bus/usb/003/017
Setup Connection
initializeConnection
Receive PIT Info
success getpit
Upload Binaries
vbmeta.img
Close Connection
Fail request receive -5
FAIL close
Fail Close Connection

Cheers
 

Virnik0

Senior Member
Sep 14, 2010
1,928
429
Prague
blog.nutcracker.cz
Heimdall didn't work with S22 and Android 13. Windows inside KVM with USB forwarded and Samsung USB drivers installed didn't work too (although ADB works over forwarded USB port just fine). I do not intend to prep live Windows USB to do this from, so I was slowly loosing hope. But this binary works. I tested it with S7, S10+, S20+ and S22, no problem at all. I would welcome GUI, but CLI works as well for me. That said - thanks a lot!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    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. I'm here just provide the executable.
    All of this is REALLY annoying, so please refrain from DM'ing me.


    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!
    4
    It is in the archive attached. XDA doesn't allow for no-extension files to be uploaded.
    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.
    1
    When trying to flash twrp
    I guess you didn't flash the vbmeta.
    1
    How do I flash the vbmeta ?

    Guys, regarding the vbmeta questions, you'd better consult the device-specific forums.
    Those often contain explicit lists what to do after what.