Related
ADB Tools
Easily set how your Mobile is connected to ADB.
Supported Modes
ADB over USB
ADB over WiFi
Starting,Stopping and Restarting the ADB Daemon
Planned Features
Start service on Device Boot
Widget to Toggle Mode
ADB Tools 1.1 Test
Supported Modes
ADB over USB
ADB over WiFi
Starting,Stopping and Restarting the ADB Daemon
Start ADB in Wifi/USB Mode on Device Boot
Enable persistent Wifi Mode.
ADB Tools 1.1 Test 2
Changelog:
Wait for SU Persmission. Exit if SU permissions not Granted.
Improved SU Detection and App StartUp
Better info about what each option does.
Improved Boot Startup service.
Lot of Code Cleanup and Bug Fixes
Click to expand...
Click to collapse
NOTE: This app will not work without root permissions
Download
XDA:DevDB Information
ADB Tools,
Contributors
idragon81
Version Information
Status: Alpha
Created 2014-11-27
Last Updated 2014-11-27
Instructions of usage
ADB Over WiFi
1) Select the ADB Wifi Option and Apply
2) Note the IP Address that is given in the WiFi Info Field. (Usually 192.168.x.x)
3) Open CMD/Terminal and type adb connect 192.168.x.x
4) Voila!! Happy Programming
ADB Over USB
1) Select the ADB USB Option and Apply
2) Connect USB
3) And that's it. Happy Programming =)
great idea , and you thread is in portal , i will try it now, meanwhile where are the links?
Yeah, no download links.
yep no download links???
Sam_in_PGH said:
Yeah, no download links.
Click to expand...
Click to collapse
amit.tiger12 said:
yep no download links???
Click to expand...
Click to collapse
Ctrl + F -> type 'Downloads' !
Profit?
Profit!
Sam_in_PGH said:
Yeah, no download links.
Click to expand...
Click to collapse
amit.tiger12 said:
yep no download links???
Click to expand...
Click to collapse
CobraCommander said:
Ctrl + F -> type 'Downloads' !
Profit?
Profit!
Click to expand...
Click to collapse
DevDB is convoluted as hell to me, but obviously this is what I did.....never seen this crizzap before!:good:
CobraCommander said:
Ctrl + F -> type 'Downloads' !
Profit?
Profit!
Click to expand...
Click to collapse
amit.tiger12 said:
yep no download links???
Click to expand...
Click to collapse
Sam_in_PGH said:
Yeah, no download links.
Click to expand...
Click to collapse
ArjunrambZ said:
great idea , and you thread is in portal , i will try it now, meanwhile where are the links?
Click to expand...
Click to collapse
DOWNLOAD LINK
Winged_Panther said:
DOWNLOAD LINK
Click to expand...
Click to collapse
Please don't quote me again..
I found the link.
And for those who quoted me, when I replied there was no download section available.
As per that, I stroked my reply.
So don't quote me again.
Thank you.
Debug
How can I use this to run my application from IntelliJ (AndStudio)!
I have installed this. I have given it root access, I have applied Wifi mode, I have then tried to connect to the IP address in Wifi info but I just keep getting the message that it cannot connect. No problems with USB. Can anyone confirm that it works using wifi?
The question that strikes me is .. how is this different to other tools like adb wireless?
What I am looking for ist a tool that fixes my adb to wireless regardless of a reboot or of a wifi toggle and easily lets me set it back to permanent USB. Haven't found that yet. I can boot with adb wireless with an init.d script but there is not a real simple way to turn that off I want to go back to USB. Maybe that's sort of a brain teaser
Doesn't work!
Settings are dead.
Don't even try this crap, guys.
P.S.: Anyone took a look inside? May be it is some root trojan?
useless
Or you can just open terminal emulator and type:
Code:
su
setprop service.adb.tcp.port 5555
restart adbd
And you can disable it and return ADB to listening on USB with
Code:
su
setprop service.adb.tcp.port -1
restart adbd
PC side:
Code:
adb tcpip 5555
adb connect 192.168.x.x
y2k2r2d2 said:
How can I use this to run my application from IntelliJ (AndStudio)!
Click to expand...
Click to collapse
Android Studio keeps starting up its own instance of ADB. To use this with android studio you need to run adb kill-server and the the adb connect command.
MJD said:
I have installed this. I have given it root access, I have applied Wifi mode, I have then tried to connect to the IP address in Wifi info but I just keep getting the message that it cannot connect. No problems with USB. Can anyone confirm that it works using wifi?
Click to expand...
Click to collapse
Could you please provide more info on your PC OS and your handheld device? I'll look into it.
daniello8 said:
The question that strikes me is .. how is this different to other tools like adb wireless?
What I am looking for ist a tool that fixes my adb to wireless regardless of a reboot or of a wifi toggle and easily lets me set it back to permanent USB. Haven't found that yet. I can boot with adb wireless with an init.d script but there is not a real simple way to turn that off I want to go back to USB. Maybe that's sort of a brain teaser
Click to expand...
Click to collapse
Right now it isn't very different, but I got what you are saying, and that's next on my list.
Revertron said:
Doesn't work!
Settings are dead.
Don't even try this crap, guys.
P.S.: Anyone took a look inside? May be it is some root trojan?
Click to expand...
Click to collapse
Could you let me know what is not working?
valexi said:
Or you can just open terminal emulator and type:
Code:
su
setprop service.adb.tcp.port 5555
restart adbd
And you can disable it and return ADB to listening on USB with
Code:
su
setprop service.adb.tcp.port -1
restart adbd
PC side:
Code:
adb tcpip 5555
adb connect 192.168.x.x
Click to expand...
Click to collapse
It does work the way that you have mentioned, however i didn't find it very convenient to type in those commands everytime i had to develop. It works either way so choose whatever you are comfortable with.
idragon81 said:
Could you please provide more info on your PC OS and your handheld device? I'll look into it.
Click to expand...
Click to collapse
I am using:
GT-i9505
Paranoid Android 4.6-BETA5 (4.4.4)
OS X 10.10.1
Hi.. I'm trying to download the app from my S4 but I can't open the viglink link. Could you send me the original link?
MJD said:
I am using:
GT-i9505
Paranoid Android 4.6-BETA5 (4.4.4)
OS X 10.10.1
Click to expand...
Click to collapse
I'll look into it, I don't know how it works on Mac, can you try using root permissions on Mac if something like this is present,
I'll look into it as soon as my exams are over
peppe130 said:
Hi.. I'm trying to download the app from my S4 but I can't open the viglink link. Could you send me the original link?
Click to expand...
Click to collapse
Link for apk http://forum.xda-developers.com/devdb/project/dl/?id=9961&task=get
this is AWESOME....wireless everywhere=) yikes, can't wait to try it now=)
Hi,
was using this guide online to try to recover and move stuff around in my Nexus5 while it is broken as far as i know this is a LCD problem not a digitiser problem.
http://www.techlife.net/2014/09/access-your-android-device-after-breaking-your-screen.html/
http://forum.xda-developers.com/showthread.php?t=2786395
ran into a problem that I can't turn on USB Debugging on my phone without being able to see what i am pressing.
According to the end of the guide it told me to flash a kernel with USB debugging enabled by default but I am unsure of what this means.
Rooted: No (I dont mind if i have to)
Fastboot: No idea
Installed ADB on computer: Yes
The custom kernel will need to have USB debugging ON by default/on boot. Usually through a custom initrc.
If you manage to get rooted, you could try:
androidscreencast
- Flash TWRP if you haven't already
- boot to recovery
- adb shell
- mount system
- edit build.prop
- reboot
- figure out adbkey.pub stuff
I have gone the same way, but could not get a screen display. It was on my wife's Gnex though. The rest works.
Now to get debian or something installed...ultralow power wireless server.
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
OP, try this.
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
recoveries have adbd enabled by default. what we're doing here is making the OS have adbd enabled.
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
get a USB OTG cable and connect your mouse to your phone
Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh...
Even if display isn't coming on... You can 3bc to fastboot, press down twice (iirc) and press power. wait a few secs, custom recovery should be running.
`adb shell` .. out of android, adb running. profit.
I think the OP is not rooted, nor does he have a custom recovery.
In that case you will need boot temporarily into a custom recovery that will allow root ADB shell access.
Download the TWRP recovery image to you PC.
HERE
For simplicity, rename the file recovery.img
Place the renamed file in your \sdk\platform-tools folder on PC.
Turn off you phone and then hold volume up button while pressing power button to get into fastboot mode.
Then, open a command prompt from within the platform-tools folder and run the following command:
fastboot boot recovery.img
Your phone should reboot into TWRP recovery.
You can then run the ADB commands outlined in my first post to enable usb debugging:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Best of luck
Bubble-be said:
The two previous posts are forgetting you need usb debugging before you can adb shell.
Booting to recovery gives you access to your system and build.prop.
Click to expand...
Click to collapse
This is incorrect.
I do not need usb debugging enabled to run ADB shell in custom recovery.
Bubble-be said:
Yes, we're on the same page there.
You can't just adb to your device to enable adb, get it ?
You need a way to access build.prop out of android, so booting to recovery will allow you this.
Just dugg up the link for the adbkey as well. http://forum.xda-developers.com/showthread.php?t=2408802
Click to expand...
Click to collapse
Huh
My post clearly stated via recovery
---------- Post added at 06:31 PM ---------- Previous post was at 06:13 PM ----------
4n3ver said:
get a USB OTG cable and connect your mouse to your phone
Click to expand...
Click to collapse
I've never tried this, but think you need to be rooted and install some hacks to get a mouse
to work via OTG.
Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I can't upload images so i'm just gonna type what it says
Code:
C:\Users\blah> fastboot boot recovery.img
<waiting for device >
^C
C:\Users\blah> adb devices
List of devices attached
C:\Users\blah>
probably something to do with how my adb drivers are installed
Just to clarify my screen is impossible to use as its just coloured lines due to cracks in the LCD screen.
Hopefully all goes well and i'll be able to fastboot TWRP with the instructions you guys have given me.
fuzznuzz said:
Hello again,
Thanks for all the replies so far.
Unfortunately i'm still unable to enable USB debugging.
I'm getting stuck, I have managed to install adb and fast boot using the 15 second thing but am unable to get it to detect via "adb devices" and am currently troubleshooting this step
I
Click to expand...
Click to collapse
Your welcome.
It's probably just simple a driver issue. You will need to look in Device manager on PC while phone is connected.
Download the howto_driver.zip from the "15 seconds ADB Installer thread" and follow the picture tutorial contained in the zip file. This should fix your connectivity issues:good:
---------- Post added at 03:23 AM ---------- Previous post was at 02:58 AM ----------
If it helps, I don't have the "Android Bootloader Interface" driver option. So for me,
selecting "Android Composite ADB Interface" allows me to detect my Nexus5 in both ADB and Fastboot mode.
Keep in mind, my OS Win7 64bit and my 64 bit ADBdriver package may be entirely different than yours.
Okay i'm having some other problems now
can anyone help?
fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Your bootloader is locked.
Sent from my Nexus 5 using XDA Free mobile app
fuzznuzz said:
Okay i'm having some other problems now
can anyone help?
Click to expand...
Click to collapse
Locked bootloader
It is the first question I or anyone replying should have asked you.
Unfortunately, as far as I know, it's game over recovering any user data with
a busted non-viewable LCD, no USB debugging and a locked bootloader.
Unless, you can by some luck, miracle or Power of the Force, pull off using your touchscreen to enable USB debugging.
Then you could use Simple ADB Backup or Holo Backup to get your data.
If not and your data is important enough to you, then replacing the screen would be your last option.
Worth replacing IMHO because your Nexus 5 is still a really great phone with nice specs and plenty of power.
Found one HERE shipped from China for $46.76 or HERE from USA $69.99 from US on ebay.
didn't work
joegestes said:
You need to install ADB/Fastboot to your PC
GO HERE
Then you can
Enable usb debugging via recovery using the following ABD commands:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
Click to expand...
Click to collapse
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please
halo_95 said:
i followed all these steps and adb devices shows nothing while phone is in recovery mode
fastboot devices shows my phone when in fastboot mode
just adb not working
help asap please
Click to expand...
Click to collapse
Do you have a stock recovery or a custom one?
You'll need to boot a custom recovery, not the stock recovery.
Now that you don't have to install the custom recovery, just boot it.
Hi
I have a old nexus with broken touchscreen . I want to use it via mirror on pc.
unfortunatly USB debuggin wasn't enable so i can't install any app.
any tips?
thanks
PS: i saw many use usb adapter to connect a mouse but i don't have it
EDIT: right now i just need a rom/kernel with USB debugging mode enabled by default
the screen still works , only the touch screen is broken
power , and volume bottons still work
the device is rooted
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
nonameleft4me said:
If it's only installing apps you could install them via recovery. (as zip)
Or you could check for a cheap replacement touchscreen.
Click to expand...
Click to collapse
thanks for the answer!
sorry i forgot to mention that i need USB debuggin for make the app works correctly.
I'm trying now to find out what rom i have installed and maybe then find a kernel with OTG support . (yes i found a otg cable )
i'm not a expert of rooting
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
nonameleft4me said:
I think google has an app called voice control. Not sure how operational it is though. Supposedly you can control the entire system via voice.
Click to expand...
Click to collapse
i need to unlock the phone and tap on the widget "search" to start voice command .
I think the best way is to find a way to enable OTG and then use a usb mouse
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Itzabhaysingj said:
Boot into Recovery and mount*Data*partition.
Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace*~/*with home directory of your OS.
Open that file in a text editor and you would possibly see*mtp*written there. Change it to*mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using*adb pullbut doing:
adb shell echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the*echo*command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
Unmount*Data*and reboot into Android OS. USB Debugging would probably be enabled.
Sent from my Aqua Trend using Tapatalk
Click to expand...
Click to collapse
thanks!
i tryed
1) i went in recovery mode
2) i connect via usb the nexus4 to my pc
3)went in "mounts and storage"
4)then "mount /data"
5)in cmd i tryed your command "adb pull /data/property/persist.sys.usb.config" but i says i'm unauthorized
i checked via command "adb devices" and it return a alphanumerica string plus "unauthorized"
i tryed then to
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
adb shell reboot
but it still says error : device unauthorizated . please check the confirmation dialog on your device
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
hartman11 said:
i tryed also with a different version of adb and now gives me after "adb devices" an "offline" response
NB: if i connect the phone (not in recovery mode) via usb i can copy files in and out (i can explore onlyfew folders) , maybe this could help.
Click to expand...
Click to collapse
Sorry but this could not help... Now only thing you can do is connect any USB mouse to your phone via otg cable (as it is not costly also), and you can also try USB gamepad. I also have used USB gamepad before when my touchscreen was not working.
Second thing you can do is download any android device manager for your PC like mobogenie or mobilego they directly install any app from play store to you android device, through USB.And I don't think they need USB debugging option to be enabled.
Sent from my Aqua Trend using Tapatalk
my problem is not installing an app (i could do it in recovery mode with a .zip) but enabling the USB debuggin
I have a otg cable but not the "Y" type ( the one with power source ) , also i don't know if OTG is supported by my kernel . I would like to install maybe another kernel which has OTG support and usb debuggin mode enable by default but i don't know what kind of rom i have D:
right now i just need a rom/kernel with USB debugging mode enabled by default
up
Hello,
I have Oneplus One 64 gb variant, yesterday my nephew somehow changed my phone's lock pattern and now my phone is locked. USB debugging was disabled at that time. I am not able to get into my phone through any means. I have lot of important data in my phone and don't want to hard reset my device. I found a solution online to get usb debugging on through adb , but I am a ultra noob and don't understand how that has to be done. please dumb it down so that I can save my precious data and unlock my phone when debugging gets enabled. Also I don't have any custom recovery installed on my phone.
This is what is mentioned in the solution.
"Instructions
1. You should try your pattern-cracking software (or whatsoever the genre it has) from inside the Stock Recovery to see whether it works with the former's environment (ADB shell available there or not).
2.Since I would never try step 1., I would do the following:
-For Jellybean 4.2.1:
1. Boot into Recovery and mount Data partition.
2. Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace ~/ with home directory of your OS.
3. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using adb pull but doing:
adb shell
echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the echo command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
4. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled.
-For Lollipop 5.0:
JB 4.2.1 users can also follow this method if the previous one didn't work for them.
1. Boot into Recovery and mount Data partition.
2. Repeat step 2 and 3 used in JB 4.2.1 method.
3. We need to tweak some parameters in settings.db. Type:
adb pull /data/data/com.android.providers.settings/databases/settings.db ~/
4. Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX.
5. In the global table, change the value for:
adb_enabled to 1
development_settings_enabled to 1
6. Check that verifier_verify_adb_installs is set to 1 in the global table.
7. Check that as default, in the secure table:
adb_notify is 1
adb_port is -1
These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you.
8. Save the changes in settings.db and copy it back into Android by typing:
adb shell
rm /data/data/com.android.providers.settings/databases/settings.db
exit
adb push ~/settings.db /data/data/com.android.providers.settings/databases/
That delete (rm) command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind.
8. Unmount Data and reboot into Android OS. ADB probably would be enabled.
source:- https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock"
Please help me understand this code and be a life saver.
Thanks in advance..
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
jisoo said:
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
Click to expand...
Click to collapse
Is there any way I can create backup of the data in these conditions?
Dush123 said:
Is there any way I can create backup of the data in these conditions?
Click to expand...
Click to collapse
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
jisoo said:
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
Click to expand...
Click to collapse
Ohk. Then it seems I don't have any option but to hard reset my device.
Thanks anyways
HI! Is there anything I can do for my pattern locked Moto E4 Plus? Details I've posted in this thread.
https://forum.xda-developers.com/showthread.php?t=2620456&page=13
Hi,
I have a problem with my OPO, I have a broken display and can't use bottons to tap on "next".
I try to use this option:
Code:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
But the setup continues to be shown
is there another way to skip the setup?
Replace your screen first? Or connect a mouse to your phone.
DevSquad said:
Replace your screen first? Or connect a mouse to your phone.
Click to expand...
Click to collapse
I have Buy a new phone, i need itonly for few day.
If I connect a mouse via otg work?
Darkside01 said:
I have Buy a new phone, i need itonly for few day.
If I connect a mouse via otg work?
Click to expand...
Click to collapse
Yes.
just flash the rom without gapps....that should stop settings wizards from showing up on startup....you can flash gapps on the next reboot to recovery....