Thanks, my issue so far was with the 2nd step, as if my Linux did not recognize my device. I might have a go on Windows if Linux will not work again.

▲

heavyset_go 16 hours ago | parent | next [-]

Check your udev rules

https://wiki.archlinux.org/title/Android_Debug_Bridge#Add_ud...

▲

homebrewer 17 hours ago | parent | prev | next [-]

Have you tried 'sudo adb start-server' before running any adb commands?

▲

johnisgood 17 hours ago | parent [-]

No. Do I have to?

▲

homebrewer 15 hours ago | parent [-]

Using adb directly runs it under your user, which will probably be unable to access the necessary USB device.

Starting the server manually under a privileged user is the easiest way to circumvent those restrictions if you don't want to fiddle with udev rules, which is the recommended solution, but is more work.

	▲	johnisgood 5 hours ago \| parent [-]
		Thank you! Will keep it in mind! I have higher hopes now.

▲

Izkata a day ago | parent | prev | next [-]

It only works for me with one of my two USB ports, and my Kobo ereader has the same issue. Not sure why, best guess is one might be USB 2.0 and the other 3.0

	▲	johnisgood a day ago \| parent [-]
		That could very well be the issue. We will see. I think I only have 2.0 working right now. I hope it works with 2.0 too. :/

▲

catlikesshrimp a day ago | parent | prev [-]

Knoppix has an old android adb and drivers. Still recognizes Samsung A and chinese androids and is functional.

Other dristros surely offer the same support

	▲	johnisgood 21 hours ago \| parent [-]
		Not sure what the issue was, I did not debug it. I will try again and see if it works or not, and will debug it further if it does not work. Arch Linux or Void Linux definitely should offer the same or more (or better) support.