3 ms·

1. Install android SDK / android studio on your computer. 2. Plug phone in to computer using USBC cable. 3. Answer prompt on phone granting permission to comp

1. Install android SDK / android studio on your computer. 2. Plug phone in to computer using USBC cable. 3. Answer prompt on phone granting permission to computer. 4. Run adb commands.

microtonal 1y ago
You also have to enable developer options (tap the Android build number N times) and then enable USB debugging. You can disable USB debugging and the developer options afterwards (keeping USB debugging on is insecure). The universal android debloater makes uninstalling packages easier, it has descriptions and categorizes packages by how safe they are to uninstall.
johnisgood 1y ago
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.
- Izkata 1y ago
  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 1y ago
    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 1y ago
  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 1y ago
    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.
- homebrewer 1y ago
  Have you tried 'sudo adb start-server' before running any adb commands?
  - johnisgood 1y ago
    No. Do I have to?
    - homebrewer 1y ago
      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 1y ago
        Thank you! Will keep it in mind! I have higher hopes now.
- heavyset_go 1y ago
  Check your udev rules https://wiki.archlinux.org/title/Android_Debug_Bridge#Add_udev_rules https://wiki.archlinux.org/title/Android_Debug_Bridge#Add_ud...
  - johnisgood 1y ago
    Thanks!

1. Install android SDK / android studio on your computer. 2. Plug phone in to computer using USBC cable. 3. Answer prompt on phone granting permission to computer. 4. Run adb commands.

microtonal 1y ago

You also have to enable developer options (tap the Android build number N times) and then enable USB debugging. You can disable USB debugging and the developer options afterwards (keeping USB debugging on is insecure). The universal android debloater makes uninstalling packages easier, it has descriptions and categorizes packages by how safe they are to uninstall.

johnisgood 1y ago

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.

Izkata 1y ago
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 1y ago
  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 1y ago
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 1y ago
  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.
homebrewer 1y ago
Have you tried 'sudo adb start-server' before running any adb commands?
- johnisgood 1y ago
  No. Do I have to?
  - homebrewer 1y ago
    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 1y ago
      Thank you! Will keep it in mind! I have higher hopes now.
heavyset_go 1y ago
Check your udev rules https://wiki.archlinux.org/title/Android_Debug_Bridge#Add_udev_rules https://wiki.archlinux.org/title/Android_Debug_Bridge#Add_ud...
- johnisgood 1y ago
  Thanks!