36

OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux

 1 year ago
source link: https://forum.xda-developers.com/t/official-samsung-odin-v4-1-2-1-dc05e3ea-for-linux.4453423/page-7#post-88606103
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea

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.

I'm posting an update regarding this issue. I can only describe what happened as surprising, but I successfully flashed the Galaxy A52s 5G when I was ready to do some more troubleshooting with it using strace. Here is the console log:

Code: 
strace -o trace.log odin4 -b BL_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5 -a AP_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5 -c CP_A528BXXU3EWE1_CP24186417_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5 -s HOME_CSC_OLM_A528BOLM3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5
Check file : CP_A528BXXU3EWE1_CP24186417_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
Check file : HOME_CSC_OLM_A528BOLM3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
meta-data/download-list.txt
/dev/bus/usb/001/010
/dev/bus/usb/001/010
Setup Connection
initializeConnection
Receive PIT Info
success getpit
Upload Binaries
abl.elf.lz4
xbl.elf.lz4
xbl_config.elf.lz4
tz.mbn.lz4
hypvm.mbn.lz4
devcfg.mbn.lz4
tz_iccc.mbn.lz4
aop.mbn.lz4
km41.mbn.lz4
qupv3fw.elf.lz4
storsec.mbn.lz4
NON-HLOS.bin.lz4
dspso.bin.lz4
shrm.elf.lz4
cpucp.elf.lz4
uefi_sec.mbn.lz4
imagefv.elf.lz4
sec.elf.lz4
bksecapp.mbn.lz4
apdp.mbn.lz4
vbmeta.img.lz4
vaultkeeper.mbn.lz4
tz_kg.mbn.lz4
tz_hdm.mbn.lz4
boot.img.lz4
recovery.img.lz4
vendor_boot.img.lz4
dtbo.img.lz4
super.img.lz4
vbmeta.img.lz4
vbmeta_system.img.lz4
modem.bin.lz4
cache.img.lz4
prism.img.lz4
optics.img.lz4
Close Connection
As you can see, I was quite surprised when it started flashing. I was expecting to see the ioctl bulk read Fail : Connection timed out 110 error and get the trace log to know more. The setup remained the same phone unit, same USB cable used, same USB port connected to, same machine used for flashing.

I don't know what changed for the flashing to push through, save for the strace prepended before the odin4 command. Perhaps this changed some execution condition that doesn't result to the ioctl bulk read fail. I guess it would be good to repeat flashing the unit again normally, without strace, and see if it results in the error coming back but that would be for some other time.
Last edited: Yesterday at 5:39 AM

ZmisiS

Senior Member
Dec 23, 2011 3,244 Livno
I'm posting an update regarding this issue. I can only describe what happened as surprising, but I successfully flashed the Galaxy A52s 5G when I was ready to do some more troubleshooting with it using strace. Here is the console log:
Code: 
strace -o trace.log odin4 -b BL_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5 -a AP_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5 -c CP_A528BXXU3EWE1_CP24186417_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5 -s HOME_CSC_OLM_A528BOLM3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_A528BXXU3EWE1_A528BXXU3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar.md5
Check file : CP_A528BXXU3EWE1_CP24186417_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
Check file : HOME_CSC_OLM_A528BOLM3EWE1_MQB64984945_REV00_user_low_ship_MULTI_CERT.tar.md5
meta-data/download-list.txt
/dev/bus/usb/001/010
/dev/bus/usb/001/010
Setup Connection
initializeConnection
Receive PIT Info
success getpit
Upload Binaries
abl.elf.lz4
xbl.elf.lz4
xbl_config.elf.lz4
tz.mbn.lz4
hypvm.mbn.lz4
devcfg.mbn.lz4
tz_iccc.mbn.lz4
aop.mbn.lz4
km41.mbn.lz4
qupv3fw.elf.lz4
storsec.mbn.lz4
NON-HLOS.bin.lz4
dspso.bin.lz4
shrm.elf.lz4
cpucp.elf.lz4
uefi_sec.mbn.lz4
imagefv.elf.lz4
sec.elf.lz4
bksecapp.mbn.lz4
apdp.mbn.lz4
vbmeta.img.lz4
vaultkeeper.mbn.lz4
tz_kg.mbn.lz4
tz_hdm.mbn.lz4
boot.img.lz4
recovery.img.lz4
vendor_boot.img.lz4
dtbo.img.lz4
super.img.lz4
vbmeta.img.lz4
vbmeta_system.img.lz4
modem.bin.lz4
cache.img.lz4
prism.img.lz4
optics.img.lz4
Close Connection
As you can see, I was quite surprised when it started flashing. I was expecting to see the ioctl bulk read Fail : Connection timed out 110 error and get the trace log to know more. The setup remained the same phone unit, same USB cable used, same USB port connected to, same machine used for flashing.

I don't know what changed for the flashing to push through, save for the strace prepended before the odin4 command. Perhaps this changed some execution condition that doesn't result to the ioctl bulk read fail. I guess it would be good to repeat flashing the unit again normally, without strace, and see if it results in the error coming back but that would be for some other time.

I tried strace and it not work for me. I installed strace with Terminal. Comman apt-get install strace -y.

Can you be a little more precise and write what you typed in Terminal when you used strace? What should be done to start the strace?


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK