yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] fathergweedo:
Well, the virgin Win10 pro x64 installation was an epic fail as far as drivers are concerned. Apparently the included Google drivers don't address everything. For each device that I connected, I had to install the vendor specific driver (LG, Motorola, Samsung for me). A simple "right-click/update driver" on the Sammy & Motorola in device manager found and installed the necessary files over the net. The LG required me to manually download & install those (this was a Verizon device, and I believe those are somewhat different for the VZW LG's). Note that I couldn't verify fastboot on the LG due to the LAF partition which prevents such access (unless zeroed out).

In retrospect, I just looked into my daily laptop driver installation(s) and I apparently added these in addition to the Google ones packaged with this installer. Memory isn't what it used to be - sorry :(

Good news is adb/fastboot installs perfectly (I used Global), and once the correct oem drivers are installed you can open a command prompt anywhere to use it. I see no conflicts with all of the above drivers installed and can switch between devices at will. All 3 co-exist just fine and are only loaded when the device is plugged in.

Using Linux is so much easier, but for Windows users this is still great ;)

Apologies for any incorrect information or controversial comments in my earlier postings.
[Android Software/Hacking General [Developers Only]] pittvandewitt:
I solved this by extracting the zip with 7-zip. Adb is able to launch in the \adb folder if you start cmd there (shift +right mouse). Hope this works for you too:good:

Edit: you have to run adb.exe and fastboot.exe before you start cmd
[Android Software/Hacking General [Developers Only]] Koysii:
With this package would I be able to perform what this user in quote has done in regards to tethering in UK Three on a Nexus 6P without root...?

I'm on three as well and just bought a Nexus 6P. I do not want to root it and have unlimited data plan. I used to use WiFi tether on my Note 3 but that app doesn't work on the 6P. Can you explain to me as simply as you can how you did this adb? What is adb is it an app on the playstore? I've searched and quite a few came up but most say the phone needs to be rooted.

If I create this apn and somehow get tethering to work on my unlimited data and not to take data off my allowed allowance of only 4GB/month. Would I be able to use data normally on the phone on a day to day basis on this new apn, or would I need to switch every time I want to tether and then switch back? And use the stock tether/hotspot method instead of these tethering apps?
[Android Software/Hacking General [Developers Only]] casual_kikoo:
Hi [MENTION=4638083]Snoop05[/MENTION], hi @ all

Got a problem trying to install v.1.4.3. At the end of the process, when trying to install the device drivers, got this error: "The system cannot find the file driver\DPInst_x64.": so fastboot and adb were not installed.

Any clue? Missing someting on my computer?

I'm on Windows 10 Pro 64 bits.

Thanks everyone, thanks mate very nice work by the way!
[Android Software/Hacking General [Developers Only]] M4M1K:
I have a doubt if anyone could answer it. My phone's screen is broken and is basically unusable. So I use Koush's Vysor to operate it. Previously I used adb for lots of things. First time when we connect the phone for usb debugging, it asks for confirmation about the computer. I have allowed it when the screen worked. My question is if I upgraded my windows (going from 7 to 10), would the phone ask for confirmation again? Because this time there is no way I can interact with the touchscreen.(or is there? that would be good to know) My phone is Galaxy S4 i9505.
[Android Software/Hacking General [Developers Only]] workdowg:
Just in case see this thread... http://xdaforums.com/showthread.php?t=2335799
[Android Software/Hacking General [Developers Only]] FrankieChen:
I'm using XP and have been unable to install the drivers despite having used every option I could find in the XDA forums. I have successfully previously installed the adb & fastboot drivers on a vista & windows 7 so I'm sure it is something to do with the XP drivers, not just me being an idiot. I no longer have access to the Windows 7 and Vista computers and don't have access to any other computer so I don't have any choice but to get it working on my XP.

When I run v1.43 I get a "0 files copied" for the ADB and Fastboot systemwide.

WHEN i RUN V1.3 I get "Nothing needs copying"

I get as far as the device manager opening and select Fire, which brings me to

Wecome to the Found New Hardwear Wizard, Can windows connect to Windows Update?

I select "no, not this time" and then "Install from list or specific location"

Then I select "Don't search, I will choose the driver to install" and

Android device

I then have a message saying "unable to find any drivers for this device" and select "Have disk".

I then locate my usb_driver folder and select android_winusb.inf.

I always get the message "The specified location does not contain information about your hardwear"

I've put the usb drivers folder on my desktop, on c:/ and d:/ but no luck in any location. My drivers are set to install unsigned and my profile is Administer (no right click option on XP Home to run as admin) .

There's no log (that I can find!)

Would hugely appreciate some advice.
[Android Software/Hacking General [Developers Only]] Trafalgar Square:
Very good

Hello,

I used the newest version of this Installer and everything worked fine!

It would be great, if you can fix this link:
[Android Software/Hacking General [Developers Only]] OrBy:
Love the idea of a quick and dirty installer with a minimal setup here but you REALLY need to learn a thing or two about error checking Snoop05.

adb-installer.log

"

WARNING: The data being saved is truncated to 1024 characters.

"

Oh sh*t...

Your install.bat can't deal with systems where the path statement exceeds 1kb.

So what does it do - it says screw it then deletes everything over 1kb. :mad::mad::mad::mad:

And it deletes the backup of the PATH.TMP after it's done. :mad::mad::mad::mad:

That's right - your install.bat does on some systems - delete users data and does not leaving them with no backup. :mad::mad::mad::mad:

It does not even echo the path to the log file. :mad::mad::mad::mad:

Sorry but not getting a thank you for this one...

PLEASE FIX THIS BEFORE IT SCREWS MORE PC'S UP !!! (or at least put a warning!!!)

Lucky for me I managed to figure out what it screwed up before I rebooted and extracted the uncut key from [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager\Environment] then restored it.

This can cause java failures, issues with video drivers, it can break compiler setups, hell if things are in a poor order in path it could lead to an unbootable system.
[Android Software/Hacking General [Developers Only]] RobbieRobski:
Does debug/usb storage have to be enabled on the device for this to be useful? Trying to recover pictures from a device with a shattered screen. devices -l lists nothing.
[Android Software/Hacking General [Developers Only]] Ohmster:
I am pretty sure you need USB debugging enabled to use ADB over USB. Can it be enabled through USB? That is a good question. I would normally use a shell to command the phone remotely, thus operating it in command line mode. Use "adb shell" to get a shell where you can use various Linux commands to view and copy data files such as "ls" or "ls -l" for the long listing. Then you can navigate the system with the cd commands to change directory, and I think adb pull <filename>" is the correct command to get the files to your PC. If you have to dig into system or restricted areas, create a root shell while in shell with the command "su" which will give you a root prompt to explore the system.

What you want to do is quite possible and not unheard of. Here is a really good post of how one fellow did his:

Broken screen while debug mode was disabled. How can I re-enable adb?

EDIT: I just tried using "adb devices" with USB debugging turned off. Does not show the phone at all and you are in a heap of trouble. Your best bet is the Google search outlined below this comment.

Also a good Google search of "can you enable debugging with adb usb" will help with this. The replies to the question are quite good, but rather complicated. However, they are "doable".

Cracked digitizers still work if they are not smashed to bits, meaning you may still be able to operate the phone by touching the broken screen and using either screencast or HDMI to see what you are touching.

With a functional phone and only the broken screen problem, adb can handle almost any need you have to interact with the phone. Brush up with a Google search of common adb commands. ;)

HTH! :)
[Android Software/Hacking General [Developers Only]] workdowg:
Also try this thread if you are able to get into twrp http://xdaforums.com/showthread.php?t=2335799
[Android Software/Hacking General [Developers Only]] mwake4goten:
I just want to wipe cache for htc one m8 for marshmallow (unrooted) will this work. I tried already but it said waiting for device...then nothing happened.. is this the right tool for htc one m8 or am I doing it wrong? Sorry, many thanks
[Android Software/Hacking General [Developers Only]] The-Droidster:
Great tool for nexuses. Easy fast and accurate! TY :)
[Android Software/Hacking General [Developers Only]] Ohmster:
Yes, this is the right tool but before you can use it, your adb USB drivers must be properly installed. This is a little tricky, for some reason, getting them to work in Windows has always been a hassle for me, but once installed properly, then it always works. This tool is exactly what you want, so long as it installs properly and works...

"Waiting for device" appears that the PC has found the phone and drivers are working .Double check by plugging in phone, USB Debugging enabled in Developer Options, and do a simple adb command, this one:

adb devices

The daemon should start and run, and return an ID number for your phone, looks like this when you get your drivers installed right:

C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb devices

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

List of devices attached

TA39400GKB device

C:\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>

See the word "device" with the strange TA ID number? THAT is my phone, adb has found it. If I unplug my phone and try that adb command again, there will be no ID number and adb will find, ...nothing.

I am really not sure how to wipe the cache and dalvik over adb, perhaps another member will jump in here with more help. But we need some information. What command did you type into your phone to try and wipe cache? What did you type in to get the message "waiting for device..."?

That message usually comes when running a script or issuing a reboot or fastboot command, the PC is waiting for the phone to get in the correct state so that it can continue, such as reboot to system or fastboot. What command did you use?

Common adb commands is all over Google, so finding them is not hard. How to wipe cache with it, I am not sure. Let's try a Google search for it, "how to clear cache via adb". As you can see, there are many results from this search. First result is for a Samsung Galaxy Note from XDA and I trust them, but they were unsuccessful. It really sounds like that chap has more wrong with his phone than he is telling. Even though he did get the right help, I still suggest the search for more input to you. This is as far as I can go right now, try the Google search to see if you get help there. Otherwise ask for more help. Can anyone tell us the correct adb commands to wipe the cache on an HTC ONE?

Tell us the commands you are using. If possible on PC, screencap the session and attach it to your post or copy and paste the text from command prompt into post so we can see. Good luck! :good:
[Android Software/Hacking General [Developers Only]] mwake4goten:
Thank-you for your detailed reply ohmster, will try when I get some time from work this week and report back ?.
[Android Software/Hacking General [Developers Only]] jmb995:
Hi there, since I upgraded to windows 10 I can't use fastboot since my computer doesn't recognize it, it works well with adb but when I reboot to use fastboot I get "Unknown Device (Device Failed Enumeration)" (Error Code 43), already search on the web and I couldn't find any fix, hope u can help

Using Htc Explorer
[Android Software/Hacking General [Developers Only]] Dirt_Bag:
I tried running your installation "adb-setup-1.4.3.exe" as administrator on my Win7 laptop, but it gives me the attached errors.
[Android Software/Hacking General [Developers Only]] feds64:
I was just wondering is the command to reboot into recovery when you are in the fastboot mode rather then to reboot to system?
[Android Software/Hacking General [Developers Only]] Ohmster:
It might depend on your phone. If you use an Xposed module like Gravity Box, there is a Power Menu tweak that gives you a "Reboot" option. Once tapped, you get options such as reboot, soft reboot, recovery, & bootloader. Custom roms like CyanogenMod give you "Advanced Power Menu" in Developer Options but not stock roms.

Normally you shut down the phone, power it back up while holding Power and Volume Down at same time. When screen blinks on, let go of Power, keep holding Volume down. Let go when screen lights and either boots you to bootloader where you scroll through choices to get to "Recovery", then press Power to Select and enter recovery. Or on some phones, you will enter recovery directly, as long as it is properly installed.

If you are already in fastboot mode, you have to shut off and power up as described above. Hold Power and Volume Down to power off or restart the device.
[Android Software/Hacking General [Developers Only]] feds64:
I am using Redmi Note 3, I am aware the combo keys are vol up + power key to go to recovery.

What I meant was once you are in the bootloader mode, eg. You type fastboot reboot to system.

But here I want it to reboot to recovery instead, without having to command it to

fastboot reboot

adb reboot recovery

That's what I am trying to find out, whether it is possible or not.

I seen ppl using adb shell command to do it from fastboot mode... Just that I am not to sure about it.
[Android Software/Hacking General [Developers Only]] Ohmster:
Oh excuse me, [MENTION=340154]feds64[/MENTION]. I didn't realize you were that advanced. Sounds like you are wanting to use this in a script or something, not just getting into recovery on the phone. That kind of question you should ask in a developer thread. You will get an answer a LOT faster there than in here. You need at least 10 posts to go into a dev thread and ask a question and you are already over that limit. The devs work with this stuff every day, we are just trying to help each other with the ADB tool or whatever questions we can help with. Any Android developer thread would be of great help you to my friend. Good luck! :fingers-crossed:
[Android Software/Hacking General [Developers Only]] GirishSharma:
Can you please complete steps, full file name, download links for my oneplus one rooted device which is running custom rom and kernel for windows xp pc?
[Android Software/Hacking General [Developers Only]] kojak1989:
How to Fix 'Error: Update Package Missing System.img' because i have it when i try to flash stock img and i must do this manual im on windows 10.
[Android Software/Hacking General [Developers Only]] Lord fiSh:
got the same problem, I just changed this "%USERPROFILE%\Desktop\adb-installer.log" to "%TEMP%\adb-installer.log" and it worked

Do you want to install ADB and Fastboot? (Y/N)y

Install ADB system-wide? (Y/N)y

Installing ADB and Fastboot ... (system-wide)

D:\_profile\Downloads\adb-setup-1.4.3
Press any key to continue . . .
1 File(s) copied
1 File(s) copied
1 File(s) copied

[MENTION=4245858]Ohmster[/MENTION] There are a few problems with your script:

(1) : I have no %USERPROFILE%\Desktop\ Dir, so most of the Script lines will fail. Just write the log to %~dp0 or to %TEMP% and open it after the script

(2) If I don't want to install ADB, then you goto :DRV and delete PATH.TMP, but it gets only written if you install adb, move the del command

(3) you can't install the drivers (windows 10 problem?), add .exe to DPInst_x64 and it works

(4) don't install to c:\adb, personly I hate Stuff in C:\
[Android Software/Hacking General [Developers Only]] Raffhell:
I can't make it work on win 10 x64

It installs correctly the adb driver (sony) but when I try to enter in fastboot (hold vol-up and then usb cable) the blue light is on for few seconds, I see the S1 driver but i can't install and then disappear from drivers.

Then phone starts in normal mode.
[Android Software/Hacking General [Developers Only]] kecskesajt:
Left a like, however, for me, it took 30 seconds.

Anyways, that's way faster than manual installation.

Thankd!
[Android Software/Hacking General [Developers Only]] :
Thanks for this op! I had adb and fastboot installed in seconds just like it says. Worked great on my laptop- windows 10. ?
[Android Software/Hacking General [Developers Only]] Almighty1:
I had v1.4.2 installed since Windows 7 x64 Home Premium which was upgraded to Windows 10 x64 Home Edition RTM 10240 and then 10586.14 and now 10586.36. v1.4.2 was working fine as of 5 minutes ago and I just ran the v1.4.3 installer and it works fine with my LG G4 Verizon VS986. The only thing with both v1.4.2 and v1.4.3 is that adb root doesn't work as that worked when I got adb about 6 years ago.

C:\WINDOWS\system32>adb root
adbd cannot run as root in production builds
[Android Software/Hacking General [Developers Only]] koen12333:
Virus in 1.4.2?

Edit:

Solved with version 1.4.3

Also VirusTotal suggests it's virus free
[MENTION=4638083]Snoop05[/MENTION]: thanks for the work

Original:

Google tells me that the 1.4.2 version on google Drive is infected with a virus.

See attachment.
[Android Software/Hacking General [Developers Only]] workdowg:
False positive. Read through this thread....
[Android Software/Hacking General [Developers Only]] digimancer:
lol Google drive detects this as a virus now.
[Android Software/Hacking General [Developers Only]] Snoop05:
Almost every antivirus marks self extracting archives as virus, maybe not if they are digitally signed, but mine is not.
[Android Software/Hacking General [Developers Only]] digimancer:
Yeah, it's not downloadable on Drive, maybe reupload as a zip?
[Android Software/Hacking General [Developers Only]] ramanvemman:
Seems to be false positive

Only these two identifies as VIRUS @ virustotal.com

https://www.virustotal.com/en-gb/fi...e429e6bc81eab291cba814aa196d2c4f419/analysis/

ClamAV	Win.Adware.Softpulse-215	20160117

Zillya	Adware.Eorezo.Win32.17659	20160116
[Android Software/Hacking General [Developers Only]] Almighty1:
Norton 2015 and 2016 does too.
[Android Software/Hacking General [Developers Only]] tedrogers61:
I got it from one of the other links...the Dropbox one was also down.
[Android Software/Hacking General [Developers Only]] jahman42:
Agreed windows 64 bit is a pain

I read though your post and was feeling your pain. I have a Nexus 5 and windows 7 home edition 64bit and was updating through NRG toolkit as normal. However, my root fail and the kit came at me with a screen saying to update my google drivers.... Unfortunately, after spending a few days trying to get windows and my mobile to play nice together; I gave up and did a system restore, so at least, my adb connetion would work.

I know the tool kit wug is for nexus devices, but I think the drivers can be installed through it. I had luck using the universe option with phone in PTP mode + usb debugging on. I sometimes think that google and windows just mess with us for the fun of it. Sincerely, Jah
[Android Software/Hacking General [Developers Only]] jmb995:
Hey there, thank you xD, but already lost days searching on the web and found no fix :/, I hoped that would someone might knew something more, but thanks anyway ^^, bummer Windows 10
[Android Software/Hacking General [Developers Only]] Almighty1:
Windows 10 works fine for me with both build 10240 and 10586.x.
[Android Software/Hacking General [Developers Only]] Ohmster:
[MENTION=2238888]jmb995[/MENTION] Almighty1 says he has Windows 10 and it works on his machine and his build of Windows. To see what build you have, right click Computer and choose Properties to see what you have. If it works for him, it will work for you. However, he might be more up to date than you are. Click on Windows Update and allow the updates to be installed. You may have to do this several times to get your PC up to date. This might give you the update you need to install the 15 second adb tool. If you get an error, save it with a screen capture or Windows Snipping Tool to capture the error and post it here for people to see so they can help you.
[Android Software/Hacking General [Developers Only]] jmb995:
thank you, [MENTION=4245858]Ohmster[/MENTION] willd do that, xD I have windows 10 pro. will do the updates and see if it works, will say something tomorrow
[Android Software/Hacking General [Developers Only]] Cizaquita:
Hi,

Thanks for the tool, i am trying to download the file, but Google Drive says that it is infected, why?

Grettings!
[Android Software/Hacking General [Developers Only]] ricarni:
With me it isn't there either

Verstuurd vanaf mijn SM-N920C met Tapatalk
[Android Software/Hacking General [Developers Only]] ikjadoon:
Anybody using the ADB driver here for the OnePlus One?

It doesn't work for me, but ADB & Fastboot installed perfectly. I guess it's not compatible with the OPO. Using Windows 8.1 x64 (that KB linked in the OP "wasn't suitable" for my system).

Using the howto-driver zip, I was able to get ADB recognize my OPO, but Fastboot is still dead in the water: "fastboot devices" is always blank.
[Android Software/Hacking General [Developers Only]] cellurl:
cant download from any of these sites at work.... Thanks for creating this Snoop05!
[Android Software/Hacking General [Developers Only]] mpyka91:
Everything seems to be working, but I can't figure out where I'm supposed to run CMD from to finish up the unlock process. There's no trace of any sort of ADB folder in my C: drive, but everything is showing up in Device Manager just fine. I did a system-wide install, so shouldn't it be C:/adb directory?
[Android Software/Hacking General [Developers Only]] daspazz:
This worked great for solving my T-Mobile S5 not being found by ADB after installing the "factory" Samsung driver package!!!!

I was trying to run G900T_OF6_Batch_Debloater_& App_Freezer (Customizable) and I couldn't get ADB to see my phone. After using your package everything worked great!!! :D
[Android Software/Hacking General [Developers Only]] rwleigh:
I've now tried 1.4.2 and 1.3 with no luck. New build Win10 64 just won't see my M9 in download mode so I can't flash firmware to update to MM.

Very frustrating, any suggestions?
[Android Software/Hacking General [Developers Only]] 5m4r7ph0n36uru:
Are you by chance talking about fastboot.exe? If so you could download htc_fastboot.exe from HTCDev and copy it to your adb/fastboot directory. As the fastboot of the sdk doesn't work in all cases on the HTC One M9 and other HTC devices, HTC released an own version of it. Instead of e.g. "fastboot getvar all" you then got to use "htc_fastboot getvar all".

In addition install HTC Sync and uninstall right away to make sure all HTC driver (coming with HTC Sync) are installed on your system and HTC Sync doesn't interfere with fastboot and adb commands.
[Android Software/Hacking General [Developers Only]] wulfie66:
ran the installer, all went well, issued an 'adb devices' command and says my phone is 'offline'. Ran adb.exe from a different download and it shows everything just fine. So someone tell me HOW to remove the files and paths that this little app installed! :(