ADB hack without a PC (Android 11+)

[Dimlos]

This section describes how to perform ADB hacks on Android 11+ devices using Shizuku and aShell.

1.Install Shizuku from the Play Store
2.Tap Pairing
3.Tap Developer options
4.Tap Wireless debugging
5.Tap Pair device whith pairing code
6.Enter pairing code

 

[Dimlos]

7.Tap Start
8.Install aShell from the F-Droid
9.Stop Shizuku
10.Start Shizuku
11.Tap manage authorized apps
12.Check aShell
13.Stop Shizuku
14.Start Shizuku

 

[Dimlos]

15.Launch aShell
16.Input ADB command in Command Box

 

[Dimlos]

Isn't this the easiest way to do the ADB hack for free?
Unfortunately, aShell does not seem to be able to run adb tcpip 5555.

 

[dhj49er]

Isn't this the easiest way to do the ADB hack for free?
Unfortunately, aShell does not seem to be able to run adb tcpip 5555.

Free?
The ashell on the Play store isn't free - see attached screenshot.
Could you replace ashell with LABD, as that is able to run ADB tcpip 5555?

 

[Dimlos]

It's free if you install it from F-Droid; LADB has a lot of literature on the net, and there is the hassle of screen splitting.

aShell | F-Droid - Free and Open Source Android App Repository

aShell: A local ADB shell for Shizuku powered android devices

f-droid.org

 

[dhj49er]

if it's hassle its worth it....as running ADB tcpip 5555 is essential if you use ADB shell commands and with LABD it can be done without a PC - very useful as it needs to be done on every reboot.

 

[Dimlos]

Yes, I recommended LADB in another thread as a way to run ADB tcpip 5555.
I'm a little pressed for time right now (I'm running late), but I'm going to contact the author of aShell and see if I can't get ADB tcpip 5555 to run.

 

[dhj49er]

Yes, I recommended LADB in another thread as a way to run ADB tcpip 5555.
I'm a little pressed for time right now (I'm running late), but I'm going to contact the author of aShell and see if I can't get ADB tcpip 5555 to run.

That would be good.

 

[Dimlos]

I received a reply from the author of aShell. Unfortunately, adb tcpip 5555 is not feasible with Shizuku alone.

Since this thread was mainly about how to do a simple ADB hack, I am not going to pursue it in depth since not all users need adb tcpip 5555.

 

[kkhh2]

I received a reply from the author of aShell. Unfortunately, adb tcpip 5555 is not feasible with Shizuku alone.

Since this thread was mainly about how to do a simple ADB hack, I am not going to pursue it in depth since not all users need adb tcpip 5555.

Can you help me with the isuue of adroid revokes the accessibility permission by itself of the app in Android 13 even after ADB hack. Why it's happening?
I have to enable it again every time, whenever I leave the device locked for more than 5 minutes!
Thanks!

 

[Dimlos]

@kkhh2
Is this only happening when you do the ADB hack using the method I described?
If not, I think you should start a separate thread.

 

[crloslm]

Any way to run adb tcpip 5555 from the smartphone itself without using a pc. Even create a macro that when starting the smartphone will execute the command.

 

[Dimlos]

If you want to do it for free with background processing, even if it takes a lot of time and effort

Wifi ADB debug mode lost on restart?

oh that was it , sorry, i just search only the digits .-) thanks so much @MacroDroidDev I wish we could search just the numbers

www.macrodroidforum.com

If you want to do it easily using a paid application

Wifi ADB debug mode lost on restart?

@Christoph First, run it from Termux and get it working before moving on to the next step. I will upload an image of the successful result. I have tried just the bash shell from Termux and here is the result: I am very surprised by the outcome: why does the first ./,nmap.sh show No output...

www.macrodroidforum.com

 

[Dimlos]

Please write in the linked thread about automating adb tcpip 5555.

 

[Endercraft]

I received a reply from the author of aShell. Unfortunately, adb tcpip 5555 is not feasible with Shizuku alone.

I don't understand that, is Shizuku running its commands via adb shell ?
If I launch a terminal from my laptop, connect via wireless debugging, I can easily turn on/off tcpip. But if I enter adb shell some of these connection related command will just say for example '/system/bin/sh: tcpip: inaccessible or not found'.
Am I missing something here ?

 

[Dimlos]

I'm not sure what's going on, but it seems that I can't access the tcpip command at the moment.
I told him that LADB can do it, but he said he doesn't want to use the libraries used in LADB because it would spoil the light operation of aShell.
In fact, LADB is so unstable and slow that I think it is better to give up tcpip command in aShell.

 

[pures]

Thanx for this method! I was failed with ladb but this method with ashell I can finally have adb commands to grant permissions on my Galaxy s22 ultra Android 13!!! Thanxxxx

 

[chaoscreater]

You can run adb tcpip using Termux. Check one of my comments in another thread. I automated this without using the need of a PC.

 

[Dimlos]

This thread is mainly for newbies who want to do ADB hacks with as little hassle as possible.
Not everyone needs adb tcpip 5555, but I already pointed you to that thread.

Although it is not published in the forum, in cooperation with @Endercraft, we have also managed to automate adb tcpip 5555 by connecting two devices running Android 11 or lower that cannot be debugged wireless with a USB cable.

I think the ADB hack and adb tcpip 5555 should be considered separately.