Running
like you already have shows you how to use the command. What exactly are you trying to do with it? (Flash, etc.) Let me know and I'll help you achieve the desired result.
Bash:
odin4 -h
odin4 -h
It could be started from any directory, even your home dir.What extracted? I pasted odin4 in /usr/local/bin. In bin I can't open Terminal.
According to his screenshots, it appears that @ZmisiS has already installed odin4, and is simply unsure of how to use it.
to me, it looks like he cant execute the binary, for which my advice was to make it executable firstAccording to his screenshots, it appears that @ZmisiS has already installed odin4, and is simply unsure of how to use it.
to me, it looks like he cant execute the binary, for which my advice was to make it executable first
ah, my bad. I overlooked this postView attachment 5920401
That's what I originally thought too, but after looking more in-depth at his screenshot I saw that he had been able to run "odin4 -h" successfully.
Well, so did I!
I don't know how to use this. For example when I want to install ROM, TWRP, etc.View attachment 5920401
That's what I originally thought too, but after looking more in-depth at his screenshot I saw that he had been able to run "odin4 -h" successfully.
run odin4 -hI don't know how to use this. For example when I want to install ROM, TWRP, etc.
My English is not good. I use translator. I can't really understand everything.run odin4 -h
will give you help. only thing it takes is to read
I see the marks -d; -l; -v; and the like. I see the marks for AP, BL, CSC... I get: command not found. Phone is in Download mode.are you telling me that the help the binary provides isn't clear?
I know for extract. I did that on Windows. AP_G973FXXSGHWA3_CL25257816_QB61057831_REV01_user_low_ship_meta_OS12.tar. I'm not going to write all this down, am I?Extract the firmware zip, which will produce AP, BL, CP, CSC tarballs. (tar archives).
then call:
odin4 -a APtarball -b BLtarball....
again, it is printed in your terminal as help. Just read it. I am quite surprised that you managed toinstall and configure your desktop, when you have a problem with this
For example, I want to install Stock ROM. I open the phone in Download Mode. I want to select AP, BL, CP and CSC. No matter what I type in the Terminal, it doesn't work. I get the message Command not found. If I were to type, what should I do to start the ROM installation? I need a description of how to do it.understood, but you also fail to explain what are you trying to do and what doesn't work
Yes, because while you've put the binary to a directory (I think it was /usr/local/bin, right?), you have to either provide full path to the binary (so you'll flash by running /usr/local/bin/odin4), or export /usr/local/bin to your PATH variable.For example, I want to install Stock ROM. I open the phone in Download Mode. I want to select AP, BL, CP and CSC. No matter what I type in the Terminal, it doesn't work. I get the message Command not found. If I were to type, what should I do to start the ROM installation? I need a description of how to do it.
virnik@Mainframe:~/Práce/GalaxyS7$ which odin4
/usr/local/bin/odin4
virnik@Mainframe:~/Práce/GalaxyS7$ echo $PATH
/home/virnik/.bin:/opt/wine-git/bin:/home/virnik/.bin:/opt/wine-git/bin:/home/virnik/.bin:/opt/wine-git/bin:/opt/wine-git/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/virnik/.dotnet/tools
virnik@Mainframe:~/Práce/GalaxyS7$
tee -a ~/.profile > /dev/null <<EOT
# set PATH so it includes /usr/local/bin
if [ -d "/usr/local/bin" ] ; then
PATH="/usr/local/bin:$PATH"
fi
EOT
. ~/.profile
cd ~/
which odin4
(should print: /usr/local/bin/odin4)
odin4 -b BL_G930FXXU8EVG3_CL19497840_QB54396082_REV00_user_low_ship.tar -a AP_G930FXXU8EVG3_CL19497840_QB54396082_REV00_user_low_ship_meta.tar -c CP_G930FXXU8ETI2_CP16784499_CL19497840_QB34227861_REV00_user_low_ship.tar -s CSC_ETL_G930FETL8ETI3_CL19818482_QB34666376_REV00_user_low_ship.tar
It is this:Yes, because while you've put the binary to a directory (I think it was /usr/local/bin, right?), you have to either provide full path to the binary (so you'll flash by running /usr/local/bin/odin4), or export /usr/local/bin to your PATH variable.
So, let's assume your odin4 binary is in /usr/local/bin, where I also put it on my system:
Bash:virnik@Mainframe:~/Práce/GalaxyS7$ which odin4 /usr/local/bin/odin4 virnik@Mainframe:~/Práce/GalaxyS7$ echo $PATH /home/virnik/.bin:/opt/wine-git/bin:/home/virnik/.bin:/opt/wine-git/bin:/home/virnik/.bin:/opt/wine-git/bin:/opt/wine-git/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/virnik/.dotnet/tools virnik@Mainframe:~/Práce/GalaxyS7$
As you can see, my odin4 is in /usr/local/bin, and I Have exported /usr/local/bin to my PATH. You can do it too. Run this:
This will add path of /usr/local/bin to your PATH variable. I am using ~/.profile file, which is loaded first time you logon. Now you can either logoff, or just 'source' the file, so the change become effective. This is one command! Copy everything starting by 'tee' and ending by last EOT, and paste to your terminal. Then run this:Bash:tee -a ~/.profile > /dev/null <<EOT # set PATH so it includes /usr/local/bin if [ -d "/usr/local/bin" ] ; then PATH="/usr/local/bin:$PATH" fi EOT
The dot at the beginning is important! It will load this change to your profile.Code:. ~/.profile
Now, you should be able to use odin4 regardless of your current directory. Try it:
Bash:cd ~/ which odin4 (should print: /usr/local/bin/odin4)
OK, so now you should be able to use odin4, so try to use it to flash the phone. Connect your phone over USB in Download mode, and enter the directory where you've extracted firmware tarballs. I am not certain whether odin4 understands *.md5 files being just tarballs, if not, rename your firmware files to remove md5 suffix (leaving just .tar), and flash. Bellow example is from flashing Galaxy S7, but the principle is the same (I used it on Galaxy S10+, Galaxy S20, Galaxy S22):
Bash:odin4 -b BL_G930FXXU8EVG3_CL19497840_QB54396082_REV00_user_low_ship.tar -a AP_G930FXXU8EVG3_CL19497840_QB54396082_REV00_user_low_ship_meta.tar -c CP_G930FXXU8ETI2_CP16784499_CL19497840_QB34227861_REV00_user_low_ship.tar -s CSC_ETL_G930FETL8ETI3_CL19818482_QB34666376_REV00_user_low_ship.tar
Can you be more specific please, I can't help you if you don't say what you're trying to do.
Userdata is probably encrypted. Have you provided PIT? Try booting to stock recovery, and doing Factory Reset/Wipe. Format Data as well.Hello guys ... I am trying to flash A34 5G. ANDROID 13 .. BUT I GET ERROR MESSAGE
Fail request received 0
FAIL!(Erase)
Fail receive PIT info
Then on phone it says
MDM MODE. CAN'T ERASE USERDATA
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).Very good stuff, just a remark from France, I've just refund my Samsung M20 (turk version) with android 10 with your soft : quiet good! before, i've made a mistake with a release of his old Android 9 with e/OS (to ungoogle it) wich is make for android 10 ... all broken... But, odin4 is strong, odin4 is full, you know, with odin4, this is freedom for release ;-)))))) If you want some screenshots of my upgrade , I could send them. thank you. Sylvain. (Linux Devuan4)
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.Can you be more specific please, I can't help you if you don't say what you're trying to do.
I wanted to Flash twrp so I can install lineage os https://lineageos.org/
odin -h
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/