OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
- Thread starter TheAirBlow
- Start date
It says that it can't find the device. unplug the phone, reboot to download again and then plug the cable. Or check that you do have data cable. some cables are charging only
I'm also in the same boat as you while trying to flash stock ROM for my SM-A528B Galaxy A52s 5G. I get the same error ioctl bulk read Fail : Connection timed out 110. I have setup the correct udev rules and verified no interference from cdc_acm. I'm still trying to figure where the problem might be, or that it could be that the flasher binary is at fault and would need an update or bugfix should a workaround may not be found.
You have to unload one kernel module. Also applies to sharing usb over KVM to a VM. Sometimes required before flashing on Linux as well:
Bash:
$ sudo modprobe -r cdc_acmThen try again. If you'll reconnect the cable, you need to unload the module again, or black list it throug /etc/modules.d/
Thanks but if you have read the quoted reply and it's quoted reply before it, then you would know cdc_acm has been unloaded/blacklisted.
I believe blacklisting and/or passing custom options to modules are done in /etc/modprobe.d. Loading modules on the otherhand go in /etc/modules.d (or /etc/modules-load.d, depending on the distro).
I used the same cable on Windows and it worked. I don't know if I entered everything correctly in Terminal.
You must set up your system to detect your device on LINUX host.Create this file: /etc/udev/rules.d/51-android.rules. How create this?
I didn't type md5.
Attachments
I created file 51-android.rules wit this command:
sudo touch /etc/udev/rules.d/51-android.rules
Did this in Terminal and the problem remained the same.
I think this is how it should be for me.
sudo touch /etc/udev/rules.d/51-android.rules
Did this in Terminal and the problem remained the same.
I think this is how it should be for me.
Attachments
Last edited:
Worked like a dream and saved me many hours of trying to get (windows) odin working. Many thanks
Just creating the file is not enough. I do use Ubuntu and I didn't have to create any udev file. what 'sudo dmesg | tail' prints, after connecting the usb with phone in download mode? Debian is know for refusing to install proprietary drivers and software until directly told to.
The problem is that I don't know how to tell him. I searched on the Internet, but without success.
I installed JOdin3Casual and it open, but it is Disconnected. Odin4 not work for me.
If you really can't get this or JOdin3 working I would follow my tutorial on using Odin on Linux here. It still uses Windows, but as a VM (Virtual Machine) inside of Linux, so you don't have to shutdown your Linux computer just to use Odin. I tried to make the instructions easy enough so that even those new to Linux (like you) can still follow them. Of course, if you have any problems or questions just let me know. (Nice work switching to Linux, BTW.)
I have installation package for Windows 11 x64 Pro. Can I it use instead of Windows 10?
I installed VM. When I right clicked on the extension and clicked open with, i selected VM and it crashes.
Last edited:
I want to install Ubuntu. I don't know which one to install. Ubuntu 22.04.2 LTS or Ubuntu 23.04.
I would just use Windows 10. I doubt Windows 11 would work, at the very least I would have to try it myself and change the tutorial accordingly.
On FydeOS + Debian 11 I can't launch Virtual Box, VLC and some other application. I'll install Ubuntu 22.04.2 LTS. I think that I can install Virtual Box in this Ubuntu.
Ubuntu LTS stands for Long Term Support.
Yes, it should definitely work with Ubuntu. Just make sure you download the Ubuntu 22.04 version of VirtualBox when you follow the tutorial.
I tried install Virtual Box on Ubuntu 22.04.2 LTS and I get notification: Unable to install virtualbok-7.0: The following packages have unmet dependencies.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Can you be more specific please, I can't help you if you don't say what you're trying to do.1
Userdata is probably encrypted. Have you provided PIT? Try booting to stock recovery, and doing Factory Reset/Wipe. Format Data as well.
Then try again. Make sure that you do provide vbmeta image as well to the Odin, or package it to existing tarball and flash along. Basically it tells you that you're not authorized to overwrite data image/part of the phone.1
Usually when you're not certain in which state the phone is, make sure to download latest genuine FW for given phone model, and either flash with Odin3 (Windows), or odin4 (Linux) with re-partition ticket/defined. You'll need PIT file as well (it is available in the firmware tarball, just extract it).
That would wipe the phone, and reset it to factory settings, overwriting all content. Then follow the procedure to get it rooted and TWRP flashed, before moving forward with any firmware reflash.1
I don't understand nothing, I'm new l8nex user I know nothing about commands and boot and things like that. I just want to install a custom rom to my samsung a21s.1
I wanted to Flash twrp so I can install lineage os https://lineageos.org/ -
23
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in this leaked tool: F. Reset Time, NAND Erase All (aka just erase userdata), EFS Clear and bootloader update.
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 fromCode:odin -hCode: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!10It is in the archive attached. XDA doesn't allow for no-extension files to be uploaded.2OMFG! 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!
2I 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.2Thanks 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.
