Database Info

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]​
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.​
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!

Lucky Thirteen said:
...if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device.
Click to expand...
Click to collapse
Excellent tutorial... but I disagree with this line. No process is bulletproof and there is no way a tutorial can account for all the variables with Windows.
Which explains why I am now asking for help!
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed your tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
Please tell me you have a suggestion to help me fix this. I've tried using every combination of search terms I can think of and have had no luck for the past 36 hours.

Finally fixed my ADB problem using these steps in case anyone else runs into it.

This worked great for me after two days of trying to get my phone to connect. I had to uninstall everything related to java, android, and htc, and the link for the htc drivers was dead so I just reinstalled sync manager, but it all works now, much thanks. All this effort was just so I could put my music on the phone, and so that I could do a full backup to my pc without rooting.

[ Logcat or it didn't happen! ] How To Logcat (updated 9/6/13 - added 4.3 reqmnts)

Ok, so there's a lot of new people in the Blaze forums here on XDA, and that's great! That means we got more people buying a Blaze, which means more popularity, which hopefully means more support.
However, that also means the forums are getting choked up with "X isn't working, how do I fix?" on things that aren't known issues, and certainly are not the norm.
The first thing everybody should do BEFORE flashing a new ROM is to read all posts made by the OP, usually the top 2 or 3. Those contain critical information, directions, known bugs, fixes, downloads, etc.
Once you flash, if you run into a problem, what should you do? Ask about it in the dev forum?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Read the ENTIRE post. The whole thing, from page one to the last. If the post is more than 20 pages long and you've spent less than 35 minutes reading it, then FAIL.
Once you've read the entire forum post from front to back and you're 100% sure this hasn't been covered, then should you ask about it?
Not necessarily.
Logcats. Logcats are important. Logcats are Android's method of telling developers
instead of it being a functioning operating system.
Logcatting is easy. Its fun. It makes you feel important when you give the devs something to go off of instead of "duh, it aint workin', bossman!"
So here's how to logcat:
FIRST! You must have the latest version of ADB on your computer. The only surefire way to get ADB that hasn't been compromised or altered in a malicious way is to download it directly with the Android SDK >>>HERE<<<
For the minimalist, you can get ADB and Fastboot only. See @Romman0's post #6
There are installers for Windows, Linux, and OS X.
Prerequisites
You must have the Android SDK and/or ADB on your computer already set up
You must have your phone's drivers installed on your computer
Your phone must be able to boot past the loading screen
You must connect your phone to your computer with the supplied manufacturers USB data/charging cable
How to logcat: Linux, Windows, and OS X
WARNING! With Android 4.3 (CM 10.2 and 10.2-based ROMs), ADB version 1.0.31 is REQUIRED. You can find out your adb version by running:
Code:
~/.android/sdk/platform-tools$ adb version
C:/Android/SDK/platform-tools>adb version
You may also need to fully boot into Android and and accept Debugging from that computer (you will have to check the box marked always accept, or always trust, or something along those lines) and restart your phone to start the logcat
(Pictures coming soon guys, I'm tired lol)
Open up a terminal (Linux or OS X) or a command prompt (Windows).
Navigate to where the Android SDK is installed on. I always install at:
Code:
Linux: [email protected]: ~$: cd ~/.android/sdk/platform-tools
Windows: C:/Windows/System32> cd C:/Android/SDK/platform-tools
OS X: I dont know where, never done it on Android, but I will soon for the sake of this guide
Your location may be different!
type the following command to make sure ADB recognizes your device is connected. If it's not, Google "ADB wont connect to my device"
Code:
Linux: ~/.android/sdk/platform-tools$ adb devices
Windows: C:/Android/SDK/platform-tools>adb devices
If it is connected, power off your phone completely and type the following command:
Code:
Linux: ~/.android/sdk/platform-tools$ adb logcat > {name of logcat here}.log
Windows: C:/Android/SDK/platform-tools>adb logcat > {name of logcat here}.log
I normally name my logcats with a naming convention, example:
logcat-ROM-version-device-date_time_timezone_of_log.log
example:
CM10.1-20130729-UNOFFICIAL-t769-09AUG2013-2033EST.log
This way, when looking at my logcats, I know:
[LIST]
[*]The Rom
[*]The Build Number
[*]The Device
[*]The date and time the logcat was captured
[/LIST]
your terminal/command prompt will say "Waiting for device to connect...". THIS MESSAGE WILL NOT CHANGE! Just trust that the log cat is will start as soon as the adb service on the phone initiates.
Power on your phone as normal
Try to make the problem appear again
When you've catted as much log as you think you need, hit CTRL + C on Linux or Windows (It's probably CMD + C on OS X, as I said, I've never done this on Mac (yet), but I know how they like to be aggravatingly different so that when I'm using Synergy to share a Mouse and Keyboard between Linux, Windows, and OS X, I keep hitting the wrong keystrokes because I re-grew accustomed to whatever OS i'm using as the primary at the moment). Now hit dir.
Upload your logcat for developer review
Now, I know for a fact that Samsung USB Drivers and ADB communicate perfectly well with the Blaze using the following operating systems. I have tested them personally.
Ubuntu 12.04 x64
Ubuntu 12.10 x64
Ubuntu 13.04 x64
Fedora 17 x64
Fedora 18 x64
Fedora 19 x64
Windows 7 x64
Windows 8 x64
Windows 8.1 Developer Preview x64
I will test out OS X 10.8.4 tomorrow and make sure it works for certain-like
That's it. Any questions, comments, gripes, or complaints? Write your congressman!

Reserved: Because I Can!

I am so happy you did this.
Edit: You should ask a mod to pin this. This is really useful and should be on the top when needed.

Thank you so much for this. I've never been completely sure how to get a logcat, and always felt kind of worthless because of this. Thanks again!
Sent from a Paranoid Blaze

Very nice!
While Windows-specific, beyond this the next best reference I've found was this - just a nice link for sdk/logcat info.
Again, great job on getting this around. Stuff like this should be standard sticky/first post stuff for just about any forum

Here is a modified minimalist version of adb, if anybody wants it.......
http://forum.xda-developers.com/showthread.php?t=2317790

Pin request sent to a mod. here's hoping!
On an additional note, I dont exactly like how it looks and I've never been good with BBcode formatting... is HTML allowed on XDA???
---EDIT---
And we're pinned! Thanks, Naddict

I've read that terminal emulator can do a logcat as well, is that true? Is it the same as doing a logcat through this method?
Sent from a Paranoid Blaze

njstein said:
I've read that terminal emulator can do a logcat as well, is that true? Is it the same as doing a logcat through this method?
Sent from a Paranoid Blaze
Click to expand...
Click to collapse
yes, if running from terminal emulator:
Code:
logcat > /sdcard/logcat.log
That will place the logcat on the root of your SD Card.

jparnell8839 said:
yes, if running from terminal emulator:
Code:
adb logcat > /sdcard/logcat.log
That will place the logcat on the root of your SD Card.
Click to expand...
Click to collapse
Just thought I'd mention the adb shouldn't be there if running from terminal emulator

dwitherell said:
Just thought I'd mention the adb shouldn't be there if running from terminal emulator
Click to expand...
Click to collapse
thanks... dont know what I was thinking :silly:
BTW...
POST # 500!!!!

Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.

FroBreadCreamJellyPie said:
Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.
Click to expand...
Click to collapse
Yes. But adb is needed to debug booting issues. Catlog will work fine capturing logs for bugs on working roms.

Romman0 said:
Yes. But adb is needed to debug booting issues. Catlog will work fine capturing logs for bugs on working roms.
Click to expand...
Click to collapse
Awesome, thank you.

FroBreadCreamJellyPie said:
Okay, call me dumb if you want to but I have a question. As I do not have a manufacturers USB cord, I cannot use this method. However, I'm tired of being useless, can I use CatLog from the Play Store?
It appears to have the ability to record logs, but I honestly have no clue if it's the same thing.
Click to expand...
Click to collapse
a manufacturers cord is recommended because it's known and proven to work as is, however, I can tell you that I have yet to run across a MicroUSB cable that didn't work for strictly adb purposes, and I've only seen very few that wouldn't charge my phone.

jparnell8839 said:
a manufacturers cord is recommended because it's known and proven to work as is, however, I can tell you that I have yet to run across a MicroUSB cable that didn't work for strictly adb purposes, and I've only seen very few that wouldn't charge my phone.
Click to expand...
Click to collapse
Then in that case, I'm doing something terribly wrong, lol thanks anyways

Lol
Gửi từ GT-S5360 của tôi bằng cách sử dụng Tapatalk 2

Kali Linux (Chroot) on Galaxy S4 i9505/i9500 [Tutorial]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Install:
1. Download Linux Deploy from PlayStore
2. Open it and go to settings
3. Selection Distribution: Kali and leave everything else as default, except Disk Image Size, which you should use 7128mb instead of Automatic.
3a. Normally it automatically finds your resolution, but you can change it on this page. (One of the last items.)
4. Then select Install
4a. [IMPORTANT] Be sure to be connected to a Wi-Fi network, otherwise 1.4GB will be downloaded from your Mobile Network.
4b. The downloading time is quite long, and you can't lose connection through that, otherwise the .img will be corrupted.
5. Once you see <<< end: installation on the app, download your favorite VNC client and set-up the following configurations:
IP/Host: localhost or 127.0.0.1
Port: 5900
Password: changeme
Click to expand...
Click to collapse
6. You will notice that there's no tools avaliable, open LXTerminal (From the dropup icon of Kali) then type:
sudo apt-get update
Click to expand...
Click to collapse
and
sudo apt-get upgrade
Click to expand...
Click to collapse
Those are minor commands, to really install the tools see next step
7. Type
sudo apt-get install kali-linux -yq
Click to expand...
Click to collapse
And wait for the full installation to complete, after it's sucesfully done it's good to go!
Q&A:
Which VNC Client you recommend?
I personally like Touchpad mouse settings and a full-screen view, the best free app that does the work for me is bVNC Free.
PostgreSQL gave me an error on the end of installation, is that supposed to happen?
YES, to fix PostegreSQL on Kali Linux ARM you have to whitelist on your network. You can do that by simply typing:
sudo usermod -a -G aid_inet postgres
Click to expand...
Click to collapse
IceWeasel (Internet Browser) is not opening! What's wrong?
For some reason when you first install it, the browser is misconfigured. To solve that type:
sudo apt-get install iceweasel
Click to expand...
Click to collapse
Happy Hacking!

Thanks so much for this!!!
Kali Linux is one of the best pentesting Linux distro.
But, I've get one error triying to install Kali
When I try to install, in the part that sais "making new disk image" the App fails. I try it changing the directory install... but not working.
Thanks in advance!!!
EDIT:
I think the errors was produced by:
First, because I hadn't 7 GB of free space
Second, the filesystem of my external sdcard (fat32) can't support files bigger tan 4 GB.
Triying again!!!

i got the same issue on my Galaxy S4 let me know if u ever find a fix

Works brilliantly. For people having problems on install. You need the following.
1. A phone not running android 4.3
2. Root
3. Busybox
Sent from my GT-I9505 using xda app-developers app

In the last attempt, I lost all my data in the external sdcard.
I don't know what happend exactly, probably I change some option without being aware, and that is the result.
Backup your data before install this!!!!

GruberEXN said:
...
3. Selection Distribution: Kali and leave everything else as default, except Disk Image Size, which you should use 7128mb instead of Automatic.
...
Click to expand...
Click to collapse
Can anything lower than 7128 MB work? I don't have that amount of space free and anything else I try fails to make the image.

::

whats the use of this ?

If you don't know what this is you don't need it
Sent from my GT-I9505 using XDA Premium HD app

so with the s 4 hardware what is possible can it go in to mon mode and does it support packet injection

simkhovich said:
so with the s 4 hardware what is possible can it go in to mon mode and does it support packet injection
Click to expand...
Click to collapse
That's all I want to know before I Flash it
__________________________________
Sent from my M919 w/ Dualboot

Obagleyfreer said:
If you don't know what this is you don't need it
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Wow so you know it already when you first heard of it?
You came also from that point.
Why not help?
Sent from my GT-I9500

gdonanthony said:
whats the use of this ?
Click to expand...
Click to collapse
It's a pentest distribution, made for security profissionals or hobbyists who wants to have all hackers tools at hand for penetration testing at servers.
simkhovich said:
so with the s 4 hardware what is possible can it go in to mon mode and does it support packet injection
Click to expand...
Click to collapse
No, since it's a Chroot installation. It's in a jail, you can't use any connection outside from it apart the internet connection (3g/wifi/2g, etc).
ktetreault14 said:
That's all I want to know before I Flash it
__________________________________
Sent from my M919 w/ Dualboot
Click to expand...
Click to collapse
Sorry, there's no use then.
marc_ecko28 said:
Wow so you know it already when you first heard of it?
You came also from that point.
Why not help?
Sent from my GT-I9500
Click to expand...
Click to collapse
Sorry for the delay.

GruberEXN said:
How to Install:
1. Download Linux Deploy from PlayStore
2. Open it and go to settings
3. Selection Distribution: Kali and leave everything else as default, except Disk Image Size, which you should use 7128mb instead of Automatic.
3a. Normally it automatically finds your resolution, but you can change it on this page. (One of the last items.)
4. Then select Install
4a. [IMPORTANT] Be sure to be connected to a Wi-Fi network, otherwise 1.4GB will be downloaded from your Mobile Network.
4b. The downloading time is quite long, and you can't lose connection through that, otherwise the .img will be corrupted.
5. Once you see <<< end: installation on the app, download your favorite VNC client and set-up the following configurations:
6. You will notice that there's no tools avaliable, open LXTerminal (From the dropup icon of Kali) then type:
and
Those are minor commands, to really install the tools see next step
7. Type
And wait for the full installation to complete, after it's sucesfully done it's good to go!
Q&A:
Which VNC Client you recommend?
I personally like Touchpad mouse settings and a full-screen view, the best free app that does the work for me is bVNC Free.
PostgreSQL gave me an error on the end of installation, is that supposed to happen?
YES, to fix PostegreSQL on Kali Linux ARM you have to whitelist on your network. You can do that by simply typing:
IceWeasel (Internet Browser) is not opening! What's wrong?
For some reason when you first install it, the browser is misconfigured. To solve that type:
Happy Hacking!
Click to expand...
Click to collapse
I go into settings but I cant find distribution. some help please
Sent from my SGH-M919 using xda app-developers app

xda23 said:
I go into settings but I cant find distribution. some help please
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
This should be very simple, but anyway, I uploaded a short video showing how to select it.
It's pretty straightforward, really.
And please, don't quote the whole main post. (and edit this, please.)

There's a lot more to penetration testing then just wifi hacking.

hololight said:
There's a lot more to penetration testing then just wifi hacking.
Click to expand...
Click to collapse
You're actually right, but most of people don't get the whole idea of a penetrating testing operational system.
Can't blame them tho, server security don't interest most of them.

Hi. i have completed the installation everything is done and ready to start, but when I click the start button, it show done for the directories and other stuff, but when it comes down to SSH :22 and VNC :5900 it fails. I cannot connect it to the vnc or ssh.

Mount usb?
Sorry for my english.
I have installed kali successfully, but I need to mount a Tp-link WN722N or similar and I do not know how. Is this possible?
I would be very happy.

I'm having the same problem as tidu12 I've downloaded the distro successfully and I've downloaded the bvnc free, I enter in all the info given (127.0.0.1) port: 5900, and the password "changeme" it gives me this error "connection failed, connection to VNC server failed with reason:failed to connect to /127.0.0.1 (port 5900): connection failed: ECONNREFUSED (Connection refused)" I've also tried to enter in "localhost" for the host instead of the IP address and it gives me the same error.
Thanks in advance!!!

recover/repair a file ( not deleted)

Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you

what is the file format of the one file that didn't moved?

aiSanaul said:
what is the file format of the one file that didn't moved?
Click to expand...
Click to collapse
it is Mp4, and was a video taken by me with the camera app

METAL66 said:
it is Mp4, and was a video taken by me with the camera app
Click to expand...
Click to collapse
did you tried send it separately?
also is video size larder like 3-5gb ?
try creating an archive of it in phone and then try sending.

METAL66 said:
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
Click to expand...
Click to collapse
what tool used to tranfer?

the Microsoft MTP protocol is not implemented well. in case you faced the famous data loss on copy with Windows Explorer, the files are gone and can't be recovered.
you can copy existing files from adb. first, enable developer options by tapping the build number on the - about phone - screen (7x) seven times. in settings - developer options - enable usb-debugging. on PC download platform-tools and install the google usb driver. add the platform-tools path to environment variables.
open cmd.exe and navigate to the platform-tools directory. type adb devices and confirm the connection on phone screen. you are now ready to copy directories.
Code:
adb devices
adb pull -a /sdcard/DCIM/Camera

aiSanaul said:
did you tried send it separately?
also is video size larder like 3-5gb ?
try creating an archive of it in phone and then try sending.
Click to expand...
Click to collapse
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).

jwoegerbauer said:
what tool used to tranfer?
Click to expand...
Click to collapse
a normal copy paste from the phone "folder" on pc windows

alecxs said:
...
you can copy existing files from adb. first, enable developer options by tapping the build number on the - about phone - screen (7x) seven times. in settings - developer options - enable usb-debugging. on PC download platform-tools and install the google usb driver. add the platform-tools path to environment variables.
....
Click to expand...
Click to collapse
IMO a bad general recommendation, if phone isn't a Google device like Pixel or Nexus. One have always to use the ADB provided by device's OEM.

Right, Windows might complain "We couldn't find driver software for your device" even though you pointed it to the correct driver. But the driver is pretty generic and works for all devices, if you force install it.
Update Driver -> Browse my computer for driver software -> Let me pick from the list of device drivers on my computer -> Show all devices -> Have Disk -> android_winusb.inf -> Android ADB Interface
It may not work for every device (I remember once a Sony Xperia didn't work) but I can confirm for Huawei, Samsung, Xiaomi, Cubot and Blackview devices. For which phone/ tablet the Google USB driver did not work for you?
But right, you can always use the OEM usb drivers for adb. There the PID/VID is added in the android_winusb.inf and driver is properly signed, so these drivers can installed automatically when device is connected. But I am not that Windows expert.
METAL66 said:
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
Click to expand...
Click to collapse
Note that the MTP protocol is only a transfer protocol for copying files to/off the phone, it's not really a "drive" you can use like other disk drives from Explorer (for example editing files). It has issues with large files, I do not recommend that method. People have lost data trying to move directories from phone to PC due a serious bug.
adb is much more stable and faster, although it also cannot handle read errors in case of file system corruption on the phone itself. for this I recently wrote a shell script to pull files in smaller parts. But it requires Linux.

alecxs said:
Code:
adb devices
adb pull -a /sdcard/DCIM/Camera
Click to expand...
Click to collapse
Huh? Why the -a?
-a listen on all network interfaces, not just localhost
MTP is bogus, ADB is much better.
I have a Windows utility adbsync (in the sig) that's nice for syncing directories between device and desktop.
I set it up to sync reading materials to devices and photos/movies back to desktop.

the -a flag for adb pull preserves mtime of pictures.

alecxs said:
the -a flag for adb pull preserves mtime of pictures.
Click to expand...
Click to collapse
Oh! I learn something every day.
Still, that's wacky that there is the global -a and the pull-specific -a.
(adbsync preserves the modified times too!)

METAL66 said:
a normal copy paste from the phone "folder" on pc windows
Click to expand...
Click to collapse
If MTP doesn't work as expected, then instead of using ADB try FTP: Windows OS has it - you simply have to activate the FTP client, Android file explorers as https://apkpure.com/file-manager-file-explorer/com.alc.filemanager have it - the FTP server.

METAL66 said:
the file is 1GB, i will try to zip and extract, but would it help? because i need to repair it not just send it.
EDIT: i get this message when trying to zip/rar it:
Read error in the file.
Data error (cyclic redundancy check).
Click to expand...
Click to collapse
there is the problem system is unable to read the file... is that file in your phone's internal storage or in sd card, cuz maybe the card is read write protected and causing problems.
try providing read and write permissions for the file and then continue sending it to pc...

METAL66 said:
Hi,
i tried to cut and paste the files from my android to the pc, all went through, but one of them didn't seem to start, so i tried copying somewhere else, it wouldn't work either, is there a way to recover it from the phone itself or make it work/repair it in the pc?
Thank you
Click to expand...
Click to collapse
A file only can be read by system if both its start address and its end address ( there may be a chain of several start and end addresses if file is stored in chunks ) on the storage medium is known. The file's content hereby is irrelevant, it's not interesting the system what is to be read: that's only of interest when file's content should get viewed.
This should be clear to anybody. @alecxs has already pointed out that.
If a copy operation fails it should be obvious that the 1 file you mentioned couldn't get read by system, then it's corrupted for whatever reason.
You have no chance to get this fixed.
From the point of view of the computer reading and viewing a file are totally different things.

aiSanaul said:
there is the problem system is unable to read the file... is that file in your phone's internal storage or in sd card, cuz maybe the card is read write protected and causing problems.
try providing read and write permissions for the file and then continue sending it to pc...
Click to expand...
Click to collapse
If a SD-card is locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then you will not be able to modify or delete the contents on the memory card: READING a locked SD-card can't get prevented, never. If a SD-card isn't readable then it's corrupted. Point.

ADB no longer works with devices I have used for years

I originally posted in the "Ask ANY Question. Noob Friendly" thread but got no replies so am trying again in its own thread. I just find it hard to believe no one has seen a similar problem anywhere....
ILikeOldStuff said:
I've been using ADB for some years on several devices but recently ran into a snag. On the same machine (an older desktop running XP) where it has always worked before, I recently tried to use it but got an odd error message:
E:\platform-tools> adb version​Android Debug Bridge version 1.0.32​Revision 57224c5cff69-android​​E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​ADB server didn't ACK​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​I tried to google it but everything I found either assumed there was a problem with eclipse, with wifi, with not using correct cables, not installing drivers, etc. But NOTHING about a case where it used to work but for some reason no longer does.
I do not (and never did have) have eclipse, nor even the android SDK installed, just the much smaller platform-tools thing. The desktop box does not have any wifi radio hardware so I can rule those out. It also is not a usb port or cable issue as I can still transfer files through MTP.
It is not really a device issue as it suddenly started happening on ALL android devices including ones I used it on before. And it isn't a case where the device updated to change anything as these are older devices running FroYo, IceCreamSandwich, Jellybean, and Oreo, where updates stopped many years ago.
I don't think it is a device driver issue as all devices I tried do show up properly in device manager.
The last time it worked was 25Sep2022 when I adjusted some permissions on the BetterBatteryStats app. I did not need it again until recently when it started doing the above error message.
Has anyone seen anything similar or have an idea how to fix it?
Click to expand...
Click to collapse
I will add that I have tried disabling AV and adding extra permissions to the firewall (which were never needed before as the process was always local) to no avail. I have never had genymotion installed (another common culprit according to various google hits). There does not seem to be anything useful in system event logs either. And Task Manager does show the adb process is indeed running.
One question I have , is how to get more clues for solving this problem. I thought firewall logs might show if that was blocking anything, so set it to log all connection activity attempts but it is not showing up in firewall logs, which makes me think the problem is elsewhere.
I see that some apps can write things to system event logs, but ADB seemingly has not done this. Is there some setting to make it write event log entries, or any other way it can be made to write some debug logging details somewhere?
Any other thoughts of how to solve this?

To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com

Update ADB: dowmload latest version from here
Releases · K3V1991/ADB-and-FastbootPlusPlus
A small Application for Windows that allows you to install the latest Version of ADB and Fastboot Files on the Computer without installing the entire Android SDK Package + Toolkit & Commands - ...
github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ze7zez said:
To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
Click to expand...
Click to collapse
Sadly I can't do either of these. Platform tools R23 (that I have been using) is the last one that is compatible with Windows XP. And this desktop box is running on an old P4 processor, which is 32bit only, with no hardware support for virtualization either, so mAid does not look compatible.
xXx yYy said:
Update ADB: dowmload latest version from here
Click to expand...
Click to collapse
Again, that looks like too new of a version of platform_tools to be compatible with XP.
But thank you both for at least trying to help!
What bugs me, is that debugging mode USED to work, until recently when it didn't.

ILikeOldStuff said:
...
Again, that looks like too new of a version of platform_tools to be compatible with XP.
...
Click to expand...
Click to collapse
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too.

xXx yYy said:
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too
Click to expand...
Click to collapse
While it may be still 32 bit, it does not work anymore with Windows XP since it uses functions that are only available in Vista & up. It gives an error message:
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.​

Time to change OS version or update WS2_32.DLL ( read: WinSock 2 DLL - the system file that contains the Windows Sockets API, an important software that is used to run most network and internet applications ) .

Right, v23 is latest version working for Windows XP (and still works). delete the %userprofile%\.android folder and try again (do backup if necessary)

alecxs said:
delete the %userprofile%\.android folder and try again
Click to expand...
Click to collapse
This took a little longer before it eventually gave a similar error message :
E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​* daemon started sucessfully *​** daemon still not running​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.

what firewall? is that the cause? disable completely?

Comodo 3.14.130099.587
I don't really think it is the cause, it has been running on the machine since even before the first use of ADB and never caused an issue before, allowing ADB to work in the past. Also ADB has never showed up in the logs as having been blocked.
I might try disabling it later tonight when I get home.

do a search on whole disk for other adb.exe make sure you haven't running multiple instances.

ILikeOldStuff said:
...
​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.
Click to expand...
Click to collapse
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
ws2_32.dll free download | DLL‑files.com
Download ws2_32.dll free! Fix DLL missing error. Solve it yourself or get help using DLL‑files.com Client to fix DLL error automatically.
www.dll-files.com

xXx yYy said:
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
Click to expand...
Click to collapse
It is neither missing nor invalid. There is Ws2_32.dll version 5.1.2600.7074 present in \Windows\system32. This is the latest version for XP, from installing MS16-077 KB3161949 ; it just does not have (and was never intended to have) the WSAPoll function that was introduced in Vista.
This error message only happens if I try to run the latest version of ADB, which is no longer compatible with XP. I do not see this when I stay with the r23 version that is the last one compatible with XP.
xXx yYy said:
Time to change OS version or update WS2_32.DLL
Click to expand...
Click to collapse
Installing a newer Windows OS is not really an option for this older hardware; it just does not have the RAM nor CPU horsepower for anything beyond XP. There is also the lack of device drivers for older hardware, and I am not willing to do without such "frills" as a working video card, ethernet adapter, parallel printer port, and other items which I use on a daily basis but are not supported by W10.

alecxs said:
what firewall? is that the cause? disable completely?
Click to expand...
Click to collapse
ILikeOldStuff said:
Comodo 3.14.130099.587
I don't really think it is the cause . . .
I might try disabling it later tonight when I get home.
Click to expand...
Click to collapse
I finally got around to trying this, and it turns out you were right and I thought incorrectly. So thanks for the reminder to re-check the obvious.
alecxs said:
do a search on whole disk for other adb.exe make sure you haven't running multiple instances.
Click to expand...
Click to collapse
The only other copies of adb.exe that I have are inside the .zip files for other newer (no longer XP compatible) versions of platform-tools. I left them inside the .zip files and unzipped only the r23 version to prevent accidentally running the wrong ones.
Task Manager mostly only showed the one instance. The only time I could see multiple was when I disabled the firewall, started one, re-enabled the firewall, then did another "adb devices -l"; repeating this sequence several times would produce one additional instance for each repeat. Using task manager to kill the extras allowed the remaining one to work properly provided the firewall was disabled.
So I can still run the r23 version of ADB after all, although the workaround of disabling first the ethernet and then the firewall is inconvenient to say the least, and hardly ideal.
I am still confused why Comodo FW clearly is blocking this while not logging that action. And also why it is blocked at all when I am using only a USB cable and neither ethernet nor wifi networks. Even moreso why it USED to work with no need to disable the firewall but no longer does.
Looks like getting these other questions sorted will need some visits to the Comodo forums.

adb client communicates with adb server via TCP. here is list of ports you must whitelist in firewall.
https://developer.android.com/tools/adb