Thor: Error When Using `begin odin` Command.

When I Try To Do begin odin After Connecting To A Device It Says This:

Failed to bulk read: Connection timed out (110)

249108814-cd49c15f-346c-45e0-b6fb-cb4414357a0a

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 29 (17 by maintainers)

Commits related to this issue

Most upvoted comments

Also, hell naw, CPU should not be a problem…? I own a Ryzen 5 laptop.

I Got begin odin Once To Work (I Do Not Know What I Did To Make It Work, I Remember Flashing The Device With Odin4 For Once, Then Run sudo modprobe -r cdc_acm After It Gave Me The Timeout Error), But Trying To Do It Again Gives The Error! It Even Messed Up With Something That Made Odin4 Doesn’t Work Anymore And Gives The Same Timeout Error…

Bro… You can’t re-use the same USB connection multiple times, or disconnect and reconnect the cable. For that to work, you need to restart it into Download mode each time - it’s a quirk of bootloader’s USB implementation.

Can you test if leaked odin4 I published on XDA works in any way? I want a reference point. Additionally, the error code 62 can be just interpreted as a timeout. Also it fails at the handshake, which is really bad. Make sure you have a good connection, and if you disconnect a device from USB in Odin mode and connect it again without rebooting it nothing will work as it “grabs” on the first connection and ignores any further attempts.

Sadly, failed.

root@:/mnt/m/# cat  /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
root@ :/mnt/m/# ./odin4 -l
/dev/bus/usb/001/003
root@ :/mnt/m/# ./odin4 -a /mnt/j/PixelExperience_Plus_star2qltechn-12.1-20221101-1827-UNOFFICIAL/recovery.img -d /dev/bus/usb/001/003
/dev/bus/usb/001/003
Setup Connection
Fail Setup Connection

I have zero clue. I’ll leave this issue as help wanted