Android ADB 7.4 plugin: Installation instructions??

[mcthomas]

Is there any Installation Instructions?

I installed the app.. Have the latest TC installed..
Went into Network Neighborhood, clicked on the ADB,
Got two options: Login to device and Options..

I got my IP on my phone 192.168.0.153, but, guess I need a port number..

Is there anything else I am missing?

What is the port number or anything else I need to know..
I didn't see any installation instructions.

Thanks

[iana]

you need to go in your phone's developer options and turn on usb debugging, then when android asks you weather you want to allow your pc to connect select yes, you might need to restart the plugin (or total commander as tc cashes plugins) to get the usb confirmation from your phone.
if you install this apk
https://play.google.com/store/apps/details?id=com.ttxapps.wifiadb&hl=en
you can connect wireless, you still need usb debugging on and active.

[mcthomas]

Ok.. I have turned on usb debugging and restarted total commander.
I went back into the Network Neighborhood, clicked on the adb, and came up with the options again.
Connect to Device
and Options..

My phone IP: 192.168.1.40
My Computer IP: 192.168.1.31

When I select "Connect to Device", I am prompted for the IP address. I enter the phone's IP: 192.168.1.40 and hit enter.. Nothing.. Goes back to the two selections.
If I enter 192.168.1.40:8080, it creates a folder showing the same.

When I click to go into the folder. Nothing is there. (No Files)
I assume, I am still missing something..
Sorry to be a pain..

My phone is not rooted, so, the WiFi Debug over Air,, I did not install.

[mcthomas]

Is there a particular port number??

Or, is there something that needs to be loaded on the android phone?

I think I have missed something..

[iana]

are you doing it with a usb connection or wireless?

as I never get an IP when I connect with the usb
a few things I might have forgot to mention so I'll go thru it steb by step
go to your phone settings -> developer options -> activate usb debugging;
connect your phone to your pc, in usb options select usb storage device or media transfer device (do not select charge only);
start tc, start the adb plugin;
a popup window on your phone will ask you do you want to allow your pc debugging access select yes and check remember this pc (this is done on the phone and if your pc does not get access you will not be able to connect) if you do not get this window remove the usb cable wait a few seconds and try again.

If you can connect with the usb install the wireless debug apk and you will be able to connect with wifi

[lebans]

Is there a particular port number??

Or, is there something that needs to be loaded on the android phone?

I think I have missed something..

Port 5555 In your case: 192.168.1.40:5555

Edited: Think also about your firewall (PC)

[lebans]

Port 5555 In your case: 192.168.1.40:5555

Edited: Think also about your firewall (PC)

Change listing mode in options to native instead of busybox,
I have tried this with my HTC One X unrooted phone. Only
thing I have done was turning on USB-debugmode.

[iana]

when connected with the usb port the ip/port/firewall are meaningless they are only used when connecting with wi-fi
again with pictures
enable usb debugging
http://imgur.com/Kr0IuXD

conect it to your pc's usb and select media device (or storage device) this is done on the phone and I think this is where you're stuck
http://imgur.com/FsLB6Jl

start tc and the adb plugin you will see your phone as a new folder
http://imgur.com/lE7gqjD
the connect to device item is for wi-fi only

now you can browse/backup/do things to your droid
http://imgur.com/VUkJezZ

[mcthomas]

Ok.. Phone connected to PC.. Can use the Windows explorer to browse to verify the connection is good.

Everything is on a local network.. 192.168.0.
Laptop and Phone are both connected to an MBR95 wireless router.
Both have access to the Internet, etc..

Phone is not rooted, and is connected USB to PC..
I guess it seems strange to be connecting to the phone using an IP address and port number of 5555, since it is a USB connection.. Hmm..
Maybe missing something here.

The phone is connected as a MTP Media Device
I start TC,, but, I am not specifically starting the plugin..
I just start TC.. I go into Network Neighborhood and see the green Android Icon with [Adb] next to it..
I click it, then get the two options
Connect to Device and Options..

Options.. I have tried both Native Settings..
I also went back and tried the "busbox".. No difference..

I am using the phone's IP: 192.168.1.40:5555 when I select Connect to Device..
I am assuming that in the picture, where I see your PVD device and the Connect to Device and Options, that you have already used "Connect to Device" with your IP:5555 and made a successful connection, and the device showed up after..

When I try the Connect to Device, it pauses about 1 Full Second, and the screen comes back to "Connect and Options" screen again..
It does not really try very hard to connect..

Just to verify.. We are connecting through a USB cable? But, using the IP for something else? Seems like we would be just going through the USB cable and no IP needed.. Just saying because mine is not working, and I'm a bit confused...

But, thanks for your effort and pictures, etc..
I'm up to the point, that I should see the device folder..
Should it be there before using the "Connect to Device",, Stupid, I know, just asking to verify that it is connect and then see the device..

[Hacker]

mcthomas,

The phone is connected as a MTP Media Device
I start TC,, but, I am not specifically starting the plugin..
I just start TC.. I go into Network Neighborhood and see the green Android Icon with [Adb] next to it..
I click it, then get the two options
Connect to Device and Options..

MTP is OK.
"Connect To Device" with IP and port is only used for WiFi ADB connections. For USB cable ADB connections a new (third) directory appears inside the plugin folder automagically with a funny name like "CB5A1PD7S1" which you simply enter.

Do you have the proper ADB drivers installed for your phone? From ADB plugin's readme:

Requirements:
- Enabled "Android debugging" on your device
- Device connected to USB with proper drivers (an ADB device must be listed in Windows Devices)

Roman

[iana]

from the sound of things you have not authorized your pc, follow instructions above when you get to #3 (after starting tc and the adb plugin) you should get this confirmation box on your phone
https://imgur.com/6arbjMX

after removing the previous authorizations I had to reboot my phone to get a new debugging authorization request

The option you are selecting that is giving you an IP and port is for wi-fi connection only, you do not need to do that when connecting with the USB, USB connection does not need root either, my phone is not rooted, as you can see I have a vanilla kit-kat.

as Hacker pointed out you need an adb driver too, the universal adb driver should do
http://adbdriver.com/downloads/
http://adbdriver.com/upload/adbdriver.zip
plug-in your phone then start the driver installer

[mcthomas]

OK.. Thanks guys...
I have it now.. I would never have gotten this without you guys..
I found the plugin here:
http://totalcmd.net/plugring/android_adb.html
No Install.txt, readme.txt, etc..
I never did find the website:www.adbdriver.com
I thought I was missing something... Ha... Ok,, makes much more sense now..
I had to load the Samsung Drivers before the Adb drivers to get it to work on my Samsung S5... But, all is well..
Can't thank you guys enough.. Been looking for this for Quite some time now.. Really.. Thanks a bunch...

I wrote an install document, in case I ever needed to do this again on another phone/pc, etc.. Maybe you guys could post it as a sticky, for "Installation Instructions for Android Adb..

Thanks Iana for taking the time to capture the screens and post them.. Much appreciated..
I'll post my Installation notes next..

[mcthomas]

How to Install Android ADB (To access your Phone from your Computer:

1) On your Phone/Android Device.
Enable USB Debugging in the Developer Options on your Android Device
Go to the settings menu on your GS5.
Scroll down to the "System section and tap "About Device."
Now scroll down to "Build number."
Tap the "Build number" section seven times. ...
Now back out to the main settings menu, and you'll see "Developer options" listed.
Enable USB debugging in the Developer Options..


2) DOWNLOAD The ADB Driver to your Computer and Install.
http://adbdriver.com/downloads/
I had a Samsung Galaxy S5. Had to use the Samsung Official Android USB Driver First.
Install the Samsung Galaxy USB Driver.
Then, install the ADB Driver Installer.


3) Install the ADB Plugin to the Total Commander.
Download the Plugin from here:
http://totalcmd.net/plugring/android_adb.html
Either Install it with the installer, or, unzip it, and let TC install it for you.
TC install: Configuration/Options/Plugins/
Click Configure on .WFX files, and Add, and point to the unzipped Adb plugin.

Now, go into Network neighborhood and click on the ADB icon.
You should see an Adb icon in a Numeric fashion.
There are options for the working of the program, and Connect to device..
Connect to Device is for Rooting the phone and connecting Wirelessly to the device.
At this point of the install, you can click the Numeric Icon, and begin to access your Android

device..

Thanks to Iana, Lebans, and Hacker for the help getting this installed..
I figured I would document this, in case I need to install it again.
Hope this helps someone else get this fantastic program installed...
I love accessing my Galaxy S5 with Total Commander..

[mcthomas]

Feel free to edit/correct/modify/add, or ask why I did something...

I had to load the Samsung drivers first, before the Adb Drivers.. I still could not see the device, until I loaded both.. Not sure if that was necessary.. But, it was either that, or unloading the plugin and reloading it that made it show up.. Forgot to step by step that part..

Thanks again guys.. Really.. I have been using TC for a very long time.. Would hate to ever have to live without it.. And, the phone just became a pleasure to use.. Finally..

[algol]

Hello Android folks,

I guess, I'm a bit late to the party, but as another Samsung user (Note-4) I felt like adding my experiences with ADB-transfer to the discussion.

Let me begin with once more emphasizing, that it is NOT SUFFICIENT to download the latest USB-driver-pack for Samsung phones to resolve any issues with the ADB-plugin and the intended data-transfer in USB-developer-mode on newer (KitKat & later) Samsung models.

On my older Note-1 (Android 3.6 "Gingerbread") the latest Samsung USB-driver-pack did the trick and all worked like a charm so USB over ADB became my primary way of communication between phone and PC. This was such a "winning team" that I waited with an upgrade until the Note 4.

The first major setback came when, after USB connecting the new phone, I only found a new "odd-numbered" folder in my "network-neighborhood"/ADB-folder - but it was empty within. It took me over a week of researching the Internet (this forum didn't help much at that time either) to find out the cause. ADB drivers were installed from the beginning, updating them to the latest Samsung driver-pack didn't help at all, I then found a hint in the forum that, since KitKat, there was a new "security"-barrier where, upon USB-connect, a message would pop up on the phone to allow USB-debugging from a certain PC. Only thing was, that message did never show up. I had learned to 7-times tap on "build number" and enable developer mode first and USB-debugging was on, still - no success.

Somewhere I read a hint, that the really absolutely latest drivers were necessary and they could be found in the latest SDK (developer kit). So I finally installed that giant bloatware-package (from the point of a non-developer) - and with the google-ADB-drivers therein installed, it finally did the trick! Suddenly the pop-up message on the phone really popped up and after allowing the connection my ADB folder was again filled to the top with the root-access file system of my (already rooted) phone.

But today I thought I should report on some new Android-blunder I've stumbled upon last week. It wasn't until then that I updated my Note4 to the latest 5.1.1-Lollipop OS since it took even an Android-genius like "chainfire" until last Christmas, to update his famous CF-Auto-Root package to accommodate Lollipop-5.1.1 on the Note4 (and many other models).

https://autoroot.chainfire.eu/

As usual with those quality-packages the update and rooting-procedure was done in less than 5 minutes and worked without a single hick-up or other nerve-stretching issue.

The next time I tried to transfer files to the external SD-card of my newly updated phone all went well - except one larger file that failed with an error message at the very end. So I began to experiment a little. Same error on transfer to the internal storage (SD-card), but, as it soon turned out, only for all kinds of files larger than ca. 10MB. Strange!

To make a long story short at one point I felt like looking into the "ADB-Options"-page and one particular entry there immediately caught my eye:

Code: Select all

Threshold to use SD-Card for copying large files to device (MB):

as the value in there said "10MB". I did nothing, didn't even know it was there - so it presumably had been there as a default value all the time and all had worked well with that setting until (and including) Android 5.0.1.

Unfortunately I could not find any detailed documentation on this ADB-plugin so my guess is as good as everyone's what that option _exactly_ means and what the possible settings are. Setting this value to "0" means that no data transfer to the mobile is possible at all any more, setting it to, say, "400" means that a larger file with 300MB could be transferred successfully. So far I have tried to set the value to "-1" and this has resulted in no further error-messages so far even for larger file-transfers up to ca. 1GB, the largest I have tried up until now.

My working theory now is that "-1" hopefully will turn that option off altogether and that this has become necessary because the update from Lollipop 5.0.1 to 5.1.1 has somehow completely disabled any direct write operation to the external SD-card.

Does anybody know specifics? Can that behavior be fine-tuned/tweaked in Android 5.1.1? Does the ADB-plugin need any update here? Or shall we assume that development/support for this is dead?

greetings
algol