forked from tytydraco/LADB
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'tytydraco:main' into main
- Loading branch information
Showing
25 changed files
with
404 additions
and
270 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,35 +1,44 @@ | ||
# LADB | ||
|
||
A local ADB shell for Android! | ||
|
||
# How does it work? | ||
LADB bundles an ADB server within the app libraries. Normally, this server cannot connect to the local device because it requires an active USB connection. However, Android's Wireless ADB Debugging feature allows the server and the client to speak to each other locally. | ||
|
||
# Initial Setup: | ||
1. About -> Build Number -> Click 7 times | ||
2. Developer Settings -> Wireless ADB Debugging -> On | ||
3. Developer Settings -> ADB Debugging -> On | ||
|
||
# Troubleshooting: | ||
If you encounter "device unauthorized" or "multiple devices connected", try this: | ||
1. Enable Airplane Mode | ||
2. Disconnect any USB devices | ||
3. Kill and restart LADB | ||
|
||
Still not working? Try this: | ||
1. Close LADB completely | ||
2. Developer Settings -> Wireless ADB Debugging -> Off | ||
3. Developer Settings -> ADB Debugging -> Off | ||
4. Developer Settings -> Revoke authorizations | ||
5. Reboot | ||
6. Developer Settings -> Wireless ADB Debugging -> On | ||
7. Developer Settings -> ADB Debugging -> On | ||
8. Enable Airplane Mode | ||
9. Open LADB | ||
|
||
# Credit | ||
Thanks to Surge1223 for compiling ADB for the ARM/ARM64 architecture. | ||
|
||
LADB bundles an ADB server within the app libraries. Normally, this server cannot connect to the local device because it | ||
requires an active USB connection. However, Android's Wireless ADB Debugging feature allows the server and the client to | ||
speak to each other locally. | ||
|
||
# Initial Setup | ||
|
||
Use split-screen more or a pop-out window with LADB and Settings at the same time. This is because Android will | ||
invalidate the pairing information if the dialog gets dismissed. Add a Wireless Debugging connection, and copy the | ||
pairing code and port into LADB. Keep both windows open until the Settings dialog dismisses itself. | ||
|
||
Here is a nice tutorial from XDA on how to do it: [link](https://www.xda-developers.com/debloat-your-phone-run-adb-shell-commands-no-root-no-pc/). | ||
|
||
Here is a video tutorial: [link](https://www.youtube.com/shorts/v7hT6rMYqh4). | ||
|
||
# Issues | ||
|
||
LADB is sadly incompatible with Shizuku at the current moment. That means that if you have Shiuzuku installed, LADB will | ||
usually fail to connect properly. You must uninstall it and reboot to use LADB. | ||
|
||
# Troubleshooting | ||
|
||
Most errors can be fixed by clearing the app data for LADB, removing all Wireless Debugging connections from Settings, | ||
and rebooting. | ||
|
||
# License | ||
While this project is GPLv3 licensed, I would like to add an additional parameter: please do not publish unofficial (user) LADB builds to the Google Play Store. | ||
|
||
Still confused? Email me at tylernij@gmail.com. | ||
While this project is GPLv3 licensed, I would like to add a parameter: please do not publish unofficial (user) LADB | ||
builds to the Google Play Store. | ||
|
||
# Support | ||
|
||
Still confused? Email me at tylernij+LADB@gmail.com. | ||
|
||
We also have a Telegram server here: https://t.me/ladb_support. | ||
|
||
# Privacy Policy | ||
|
||
LADB does not send any device data outside of the app. Your data is not collected or processed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.