Userland: How do i run adb terminal

Created on 13 Mar 2019  路  8Comments  路  Source: CypherpunkArmory/UserLAnd

Can I run adb commands on UserLAnd

Do I need root permission to run ADB commands for control my device by Userland?

I haven't tried anything yet because I do not know if it will require root permission and , do will it work on Userland?

Describe how your task behaves in a regular Linux environment

As you know it behaves normally and has been tested by me on a Windows 10 operating system.

Most helpful comment

Are you asking about either:

  1. Running ADB inside UserLAnd?
  2. Running ADB from a computer to access UserLAnd files?

For 1:
I don't think you would need to be root to run ADB from inside UserLAnd if you could figure out how to get it installed. Normally ADB detects connections over USB however, which would not make sense in referencing the device it is running on. You also won't have access to USB drivers anyway I believe.

For 2:
You still don't need to root your device, but I believe ADB works best when APKs are installed by hand. This allows you to run the following commands:

$> adb shell
$> run-as tech.ula

which you can use to access your UserLAnd files

All 8 comments

I was on my way down this road..... I installed my setup like this http://www.tinyurl.com/donofriodexnote8 and I have adb installed in my ubuntu 18.04 would like to see if it network wise can connect because we're never going to get access to physical hardware (usb cables and the like) I want to code on this setup and I've yet to get time....

Are you asking about either:

  1. Running ADB inside UserLAnd?
  2. Running ADB from a computer to access UserLAnd files?

For 1:
I don't think you would need to be root to run ADB from inside UserLAnd if you could figure out how to get it installed. Normally ADB detects connections over USB however, which would not make sense in referencing the device it is running on. You also won't have access to USB drivers anyway I believe.

For 2:
You still don't need to root your device, but I believe ADB works best when APKs are installed by hand. This allows you to run the following commands:

$> adb shell
$> run-as tech.ula

which you can use to access your UserLAnd files

@MatthewTighe
You say聽that聽ADB聽detects the connection via a聽USB聽cable only, but is it possible to connect to it by creating a聽connection service as an example? You have linked the聽Nox Player聽emulator by with ADB so that it can be connect by the聽Android studio聽for running applications from with in.

Q: You say that ADB detects the connection via a USB cable only, but is it possible to connect to it by creating a connection service as an example?
A: We don't know how possible that is.

If I understand correctly Android Studio does not support arm, but I wouldn't be surprised if you could get the platform-tools, like ADB, working.

Q: You say that ADB detects the connection via a USB cable only, but is it possible to connect to it by creating a connection service as an example?
A: We don't know how possible that is.

If I understand correctly Android Studio does not support arm, but I wouldn't be surprised if you could get the platform-tools, like ADB, working.

Yeah... It could be possible.

@corbinlc Yes i believe I have had adb working in the past. The way to do it is to enable wireless adb, and then you can connect via localhost in userland 127.0.0.1.

Still it is a pain because you need to connect the phone to PC first to enable it.

Any update on this? I trying this too but without success.

Update:Bellow method works on x96 max+ (just checked using update/upgrade, localhost/standard port):

sudo apt update && sudo apt upgrade
sudo apt install -y net-tools android-sdk-platform-tools
adb connect localhost
adb -s localhost shell

Hi there.
Also spent some time on this - I think option 1 would be nice feature.
Installation of adb in UL/Ubuntu is quite simple:

sudo apt install android-sdk-platform-tools
adb devices

-> empty list

Then connected the phone to PC (standard ubuntu with adb installed) and switched phone to tcp debug mode:

adb tcpip 6555

(default port was causing problems)

disconnected phone

back to UL:
adb connect localhost:6555

displays "connected to localhost:6555" but adb server crashes

tried with ip:
adb connect 192.168.2.131:6555

_adb connect 192.168.2.131:6555
* daemon not running; starting now at tcp:5037
* daemon started successfully
connected to 192.168.2.131:6555_

and if You try:

adb shell

_* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found_

Android side is ok because I can connect from PC.
Tried also tunnelling to PC - same effect.
Currently have no spare android phone to check if I could connect to external machine.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

RonCan picture RonCan  路  7Comments

TechDossier picture TechDossier  路  3Comments

MaffSi picture MaffSi  路  9Comments

denomparkour picture denomparkour  路  4Comments

lewisdonofrio picture lewisdonofrio  路  4Comments