ADB hack without a PC (Android 11+)

Dimlos

Well-known member
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
 

Attachments

  • Tap Pairing.jpg
    Tap Pairing.jpg
    266.8 KB · Views: 76
  • Tap Developer options.jpg
    Tap Developer options.jpg
    395 KB · Views: 74
  • Tap Pair device whith pairing code.jpg
    Tap Pair device whith pairing code.jpg
    212 KB · Views: 65
  • Enter pairing code.jpg
    Enter pairing code.jpg
    207.6 KB · Views: 67

Dimlos

Well-known member
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
 

Attachments

  • Tap Start.jpg
    Tap Start.jpg
    266.6 KB · Views: 49
  • Stop Shizuku.jpg
    Stop Shizuku.jpg
    260.6 KB · Views: 42
  • Tap manage authorized apps.jpg
    Tap manage authorized apps.jpg
    256.5 KB · Views: 45
  • Check aShell.jpg
    Check aShell.jpg
    106.6 KB · Views: 43

Dimlos

Well-known member
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

Well-known member
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?
 

Attachments

  • Screenshot_20230418-221939.png
    Screenshot_20230418-221939.png
    368.9 KB · Views: 31

dhj49er

Well-known member
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

Well-known member
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

Well-known member
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

Well-known member
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

New member
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!
 
Last edited:

Dimlos

Well-known member
@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

New member
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

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

If you want to do it easily using a paid application
 

Endercraft

Moderator (& bug finder :D)
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

Well-known member
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

New member
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

Active member
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

Well-known member
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.
 
Top