when I install driver, the windows find the ADB Interface as my driver
but the guide says it should be Android Bootloader Interface
so what's the difference?
will the ADB just be fine when I in fastboot?
Adb is available when you boot android...
Either Recovery or the ROM itself with USB Debugging enabled.
ADB = Android Debug Bridge.
ABI is to connect with HBOOT (similiar to PC BIOS) and not Android (the OS).
DoomFragger said:
Adb is available when you boot android...
Either Recovery or the ROM itself with USB Debugging enabled.
ADB = Android Debug Bridge.
ABI is to connect with HBOOT (similiar to PC BIOS) and not Android (the OS).
Click to expand...
Click to collapse
got it ,thx ~~~
proxylullaby said:
when I install driver, the windows find the ADB Interface as my driver
but the guide says it should be Android Bootloader Interface
so what's the difference?
will the ADB just be fine when I in fastboot?
Click to expand...
Click to collapse
When you see the ADB Interface as your driver, right-click on it and you will go through the process of selecting the new driver. If you are following Allgamer's guide, you can pick up around the step where he tells you to right click and select update driver software. HTH
Every time I try to update the drivers, I pick Android Bootloader Interface from the three options, it installs, and then says it has finished installing driver software Android ADB Interface, not ABI. No matter how many times I try it, I can't get ABI to show up.
I've tried USBDeview, but I'm not sure exactly what I should be doing in there to get this problem fixed.
Any help would be appreciated...
anonymou38 said:
Every time I try to update the drivers, I pick Android Bootloader Interface from the three options, it installs, and then says it has finished installing driver software Android ADB Interface, not ABI. No matter how many times I try it, I can't get ABI to show up.
I've tried USBDeview, but I'm not sure exactly what I should be doing in there to get this problem fixed.
Any help would be appreciated...
Click to expand...
Click to collapse
I did it anyways, even though it wasn't showing Android Bootloader Interface and it worked fine.
Related
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
I believe you need the android usb drivers supplied by google to get it to connect. They can be downloaded using the sdk package manager. Also I'm not sure it will work having the Samsung drivers installed and you may have to uninstall them first.
they are installed already since i installed the whole sdk manager pack
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
ringnutz said:
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
thx for answer but I already done that..any other suggestions?
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
What drivers are showing up when you plug in the device? If it says Samsung then you don't have the android drivers installed. And I believe you can't have both installed only one or the other as only one will load when you plug in the device not both.
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
tzacapaca said:
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
Click to expand...
Click to collapse
When you plug the device in, under Device Manager in Windows, there should be listed Android Composite ADB Interface under the device. If not the Google USB drivers were not installed properly.
yeah I dont think my theme is the culprit, there are many reasons why ADB wouldnt show devices. Also Heimdall>Zadig is good for drivers.
run sdk manager and install latest google drivers as well.
are you on Windows OS?
nope,not your theme its the culprit..cuz i didnt install it and i cant install it cuz of no adb connection which is required by a tool named AutoDEOTool1.0.3
I installed latest google driver via sdk manager too..
yes,on Win 7 64 bits
*pulling hair*
I didn't have my usb cable yesterday to check it out but adb actually works with the Samsung drivers. Device Manager>Android Phone>SAMSUNG Android ADB Interface. And when I type the command "adb devices" it shows up. This works both if you plug the tablet in wihtout powering it up and when its turned on so I'm not sure what your problem is. I do have Kies installed on the laptop too so yours should be working if you installed the sdk and drivers correctly.
Which Tab do you have? I have the 6210 unlocked wifi only, it could be other models work differently. Not sure if you have a locked bootloader that you can access the tab through adb.
GT P6200 European
and here is what i get on cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tavi>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Tavi>adb devices
List of devices attached
C:\Users\Tavi>
EDIT:SOLVED!
Thank you all for answers
How did you solve this?
I input in cmd adb fastboot reboot and suddenly the device got the command and then recognized my tab..(pretty strange i know)
make it done
tzacapaca said:
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
Click to expand...
Click to collapse
do this steps:
1) remove battery
2)insert battery
3) connect the phone via usb will turned off and leave it till usb android phone installed
4) turn ur android phone on
5) wait for full boot
6) install Motorola usb driver .zip attached down there
7)select charge only mode
8) then write the commands of tacoroot.bin
9) when all is done hit the thanx button
ADB wireless
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Unitedforlife said:
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Click to expand...
Click to collapse
What do u mean adb wireless?
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
keaukraine said:
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
Click to expand...
Click to collapse
Goto developer tools and enable usb debugging ADB on the ROM your using it should do the trick.........
There are no new ADB drivers the same drivers are used for all the ROMS.......:laugh:
keaukraine said:
I've installed PAC-Man ROM and now I can't use my device via ADB interface. I'm using Windows 7 x64.
It is just not listed in devices neither in Eclispe nor in Android Debug Monitor.
I've updated SDK to latest version but to no avail.
In Device Manager I have a device called 'Motorola USB Composite Device' and 'MB865' (this works, it is under 'Portable Devices'). I've tried updating driver pointing to Google drivers location but to no avail.
Stock ROM works just fine.
Click to expand...
Click to collapse
Make sure your Motorola drivers are up to date. Just go to:
https://motorola-global-en-roe.custhelp.com/app/answers/prod_answer_detail/a_id/89881
If I had a dollar for every time I said that, I'd be making money in a very weird way.
ADB, but not Fastboot, can see my phone. I have followed the same steps as with Windows 7, yet I can't get fastboot to see my device on this new machine. I see threads for other phones, but didn't see one for this for our phone. I need to reflash my recovery because this new CWN can't mount the sd card and I need to reflash root and busybox after OTA update (ota survival failed)
zomgitsanoob said:
ADB, but not Fastboot, can see my phone. I have followed the same steps as with Windows 7, yet I can't get fastboot to see my device on this new machine. I see threads for other phones, but didn't see one for this for our phone. I need to reflash my recovery because this new CWN can't mount the sd card and I need to reflash root and busybox after OTA update (ota survival failed)
Click to expand...
Click to collapse
OTA survival failed?
Did you pay for superSU pro?
It's worked for me since ICS
And about the fastboot on Windows 8.1......Good luck
EDIT#
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
TRY THIS
Windows has determined the driver software for your device is up to date.
I worked just fine on a Windows 7 machine
One more reason 8 is a POS
OTA survival was a partial success. Some apps can still get root, apparently, but others fail and
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed. (when in fastboot)
Warning if your intent is to Unlock the Bootloader.
At this time 24 Sept 2017
There are no Stock Firmware Images, No Custom Recovery, No Root Method.
Without any of those available Unlocking Bootloader has little Value, and lots of risks.
Official PH-1 windows drivers are up, with Official builds.
https://essential-live.herokuapp.com/developer/current-builds thanks for update @bmg1001 -14 Nov 2017
I haven't seen any Official Windows USB drivers (adb/fastboot) posted any where so i just used Google Pixel Drivers.
Official Google Drivers
Selecting correct drivers in Device manager
Adb seems to work with Windows default drivers, but i had to update ADB.exe version
SDK Platform-Tools for Windows ~3MB
If you have never used ADB
[Index] Setting up and Using ADB/Fastboot
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
Enabling Dev Options
See post #2
ADB Setup/ Troubleshooting
See post #3
Enable Dev Options..
Settings/About phone
Tap on Build number, until you see "You are now Developer"
Back up one screen (Main Settings Page)
tap Developer options
Optional
Toggle on Stay Awake (if you are new to this)
If you are plan on Unlocking Bootloader
Toggle On OEM unlocking
Select Enable (on popup window)
Required
Toggle On USB debugging
Watch for Allow USB debugging popup on Phone
recommended
check box Always allow from this computer
then OK
Testing ADB setup by booting to bootloader
Code:
adb reboot-bootloader
If that code doesn't work you may need to update adb
Fastboot setup
Fastboot commands only work with the device in Fastboot/Bootloader Mode
Boot the Device to Bootloader Options
Code:
adb reboot-bootloader
Power off, Hold Volume Down Button, Power On
Connect To PC via USB
Open PC Device Manager (Settings/Devices/Device Manager)
Look For Mata
Update Driver (Right Click on Mata)
Browse My Computer for Driver Software
Let Me Pick from a List of Available Drivers
Select your Device's Type: ADB
Select the Driver ypu want to Install
Manufacture: Google
Model: ADB Testing (there may be a better one)
Select: Next
PH-1/Mata should look like this
If You don't see adb drivers in available drivers
Try installing l Google Drivers in post #1
I'm using the minimal adb&fastboot, do you think that's the problem?
edit: see attached thumnail, I looked at your photos and followed the instructions. On my windows I get the following options. I tried the two "ADB testing interface" options and neither seem to allow me to perform fastboot commands. If I type fastboot devices nothing happens while the device is in fastboot mode. The ADB commands while the device is powered on do work though.
elsamuraiguapo said:
I'm using the minimal adb&fastboot, do you think that's the problem?
Click to expand...
Click to collapse
no, you need to select the correct driver in Device Manager
Looks like Minimal ADB and Fastboot hasn't been updated since 6th January 2017
So that could be an issue
Updated post #4
to explain images in post #1
sd_shadow said:
no, you need to select the correct driver in Device Manager
Click to expand...
Click to collapse
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Is yours the Sprint variant?
elsamuraiguapo said:
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Click to expand...
Click to collapse
Doesn't look like that has been updated since October 2016
i would use the ADB files direct from Google, link in post #1
Is yours the Sprint variant?
Click to expand...
Click to collapse
No, but if bootloader wasn't Unlockable, the OEM unlocking option in Settings should be Greyed out and unselectable
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05
adb-setup-1.4.3.exe
has adb version Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android
and fastboot commands didn't work for me with Mata
ADB version working for me is
Code:
adb version
adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
sd_shadow said:
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
Click to expand...
Click to collapse
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
elsamuraiguapo said:
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
Click to expand...
Click to collapse
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
sd_shadow said:
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
Click to expand...
Click to collapse
Well I uninstalled all the drivers I could find on my computer to start from scratch. Which should I install? I can't figure out how to install the google usb drivers referenced above
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
sd_shadow said:
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
Click to expand...
Click to collapse
Okay awesome, I think we're almost done. When I type in fastboot devices I can see the device now. Starts with PM1. What command did you use to unlock the bootloader? I tried fastboot oem unlock and "fastboot flashing unlock" and it failed. (remote: unknown command)
Edit: Never mind it worked now after a few attempts. Weird cause I typed the same command over and over and it kept failing. Anyway looks like it rebooted successfully after the factory reset. Thanks for your help mate. Now I can set up the device to my liking and just wait until we get customer recovery and root.
Hi guys, same issue here with OPENUS version of the MATA PH-1.
I have installed 15 seconds ADB driver 1.43 clean on laptop and can access the phone with ADB and reboot it into bootloader.
However, 'fastboot devices' gives me nothing. I've updated the Mata in device manager first with the options from the 15 seconds ADB, with are 'Android ADB Interface', 'Android Bootloader Interface' and 'Android Composite ADB Interface'. None of them give me any luck when trying 'fastboot devices', nothing found.
Then, uninstalled the ADB driver from device manager so that it showed Mata again, installed Google driver from 1st post, but same thing: version 11.0 of Google drivers (28/08/2014) with same choices, but none of them work.
Does this have to do with the USB A 3.0 --> USB C cable maybe? Or is it just a driver thing?
BTW reason for unlocking is so that I can root later without wiping the device, once root becomes available..
updated post 1 a bit
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.