Most active commenters
  • johnisgood(7)

←back to thread

845 points the-anarchist | 11 comments | | HN request time: 1.448s | source | bottom
Show context
grishka ◴[] No.44334337[source]
The "unremovable" part is inaccurate. While you can't completely remove it because it resides on the system partition, you most probably can still disable it with an adb command:

    adb shell pm uninstall --user 0 com.package.name
This command is very powerful as it works for any app, even those that have "disable" greyed out in the settings. I disabled the Galaxy Store on my S9 this way for example.
replies(14): >>44334372 #>>44334377 #>>44334391 #>>44334708 #>>44334724 #>>44334999 #>>44335989 #>>44336280 #>>44336571 #>>44337223 #>>44338012 #>>44339617 #>>44339958 #>>44348889 #
johnisgood ◴[] No.44338012[source]
How would one go about using adb? Motorola, stock Android. Do I need to root my phone for this to work or what are the requirements, or how do I perform it?
replies(1): >>44338145 #
contingencies ◴[] No.44338145[source]
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.

replies(2): >>44338222 #>>44340676 #
1. johnisgood ◴[] No.44338222[source]
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.
replies(4): >>44339766 #>>44339916 #>>44341647 #>>44342275 #
2. Izkata ◴[] No.44339766[source]
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
replies(1): >>44339784 #
3. johnisgood ◴[] No.44339784[source]
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. :/
4. catlikesshrimp ◴[] No.44339916[source]
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

replies(1): >>44340343 #
5. johnisgood ◴[] No.44340343[source]
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.
6. homebrewer ◴[] No.44341647[source]
Have you tried 'sudo adb start-server' before running any adb commands?
replies(1): >>44341913 #
7. johnisgood ◴[] No.44341913[source]
No. Do I have to?
replies(1): >>44342607 #
8. heavyset_go ◴[] No.44342275[source]
Check your udev rules

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

replies(1): >>44349161 #
9. homebrewer ◴[] No.44342607{3}[source]
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.

replies(1): >>44346248 #
10. johnisgood ◴[] No.44346248{4}[source]
Thank you! Will keep it in mind! I have higher hopes now.
11. johnisgood ◴[] No.44349161[source]
Thanks!