Hi,
I am looking for way to get ADB and fastboot working on the Pixel C. The goal ist to be able to debug and flash other Android devices using the Pixel C.
As far as I know Android used to be distributes with a full featured ADB binary (and maybe fastboot as well), but that doesn't seem to be the case for the Pixel C. I also couldn't find a recent version to download, so I would be very grateful for a download or instructions for how to compile the binaries from source, so that they are usable on the Pixel C.
I only found this one, but it's a bit out of date and doesn't seem to work for recent Android devices.
Thanks,
Niko
one way to get them is sdk manager
http://developer.android.com/tools/help/sdk-manager.html
you'll usually have the latest tools and drivers by installing it. you can select to just have tools and fastboot/adb/drivers are part of that. if you have android studio, usually it is installed as part of that.
dkryder said:
one way to get them is sdk manager
http://developer.android.com/tools/help/sdk-manager.html
you'll usually have the latest tools and drivers by installing it. you can select to just have tools and fastboot/adb/drivers are part of that. if you have android studio, usually it is installed as part of that.
Click to expand...
Click to collapse
That's not what I meant. I want to use the C as a PC replacement, connecting other Android devices to it and using it as the ADB host (as if it was the PC). That means I need ADB and fastboot binaries not for my PC, but for the Pixel C itself.
I know it used to be possible and I also found old ADB binaries that run on the Pixel C, but they don't work with current gen Android phones anymore (AFAIK).
ok, misread original post
http://www.droidviews.com/use-your-android-device-as-pc-for-fastboot-and-adb/
not sure, did not try, search of google produced two different sets, the filenames/filesizes
kadb 1,118KB
kfastboot 818KB
adb 107KB
fastboot 819KB
the second set was from the article posted with article date of june 2015 so it seems related to current phones.
do not understand difference in adb sizes.
dkryder said:
ok, misread original post
http://www.droidviews.com/use-your-android-device-as-pc-for-fastboot-and-adb/
not sure, did not try, search of google produced two different sets, the filenames/filesizes
kadb 1,118KB
kfastboot 818KB
adb 107KB
fastboot 819KB
the second set was from the article posted with article date of june 2015 so it seems related to current phones.
do not understand difference in adb sizes.
Click to expand...
Click to collapse
Thanks.
I tried them, but sadly ADB seems to have a missing library. I found another thread here on XDA that has statically linked binaries. Fastboot seems to work, but ADB shows my Nexus 5X as offline.
Related
The following links are to QtADB GUI Interface. It makes ADB easier to "see" and understand. Also it allows easy taking of screenshots, etc.
General Link
ADB Binaries Links:
Link to Windows ADB Binaries
Link to Linux ADB Binaries
Link to MAC ADB Binaries
If you have never installed ADB on windows. this is the most basic way of installing ADB without requiring the full Android SDK. Download the appropriate binaries above for your operating system. Extract them somewhere safe and remember the folder location.
QtADB Links:
Windows QtADB
Linux 32-Bit QtADB
Linux 64-Bit QtADB
Mac QtADB
QtADB is a GUI Interface for ADB. Download the appropriate file above for your operating system and extract it somewhere you can remember. Create a shortcut on your desktop to the QtADB.exe file in the recently extracted QtADB folder. Upon starting the program it will ask you to point it at your folder with ADB. Point it to the ADB binaries folder that you extracted at the beginning of this post
The rest will be history. Enjoy the easy to use ADB GUI QtADB and a streamlined version of the ADB Binaries.
Disclaimer:
I claim no ownership to any of these files. Nor do I claim to have created them. I have only linked to them to help out the development community. The real thanks should be given to the creator of QtADB for the extremely useful ADB GUI. If any thanks is given to me it should be solely for the guide on helping you set it up.
Hope this helps!
It's quite a nice app (I like the bounce effect!), but some of the sections are not functional on the KF probably due to it being a heavily customized ROM, and also it only lists 11 of my applications?!
I've only played with it for a short time, so there might be some settings that need to be tweaked.
I'll be plugging in my CM7'd Droid Inc shortly to see how that looks as a comparison!
Thanks for posting!
sl0ttedpig said:
It's quite a nice app (I like the bounce effect!), but some of the sections are not functional on the KF probably due to it being a heavily customized ROM, and also it only lists 11 of my applications?!
I've only played with it for a short time, so there might be some settings that need to be tweaked.
I'll be plugging in my CM7's Droid Inc shortly to see how that looks as a comparison!
Thanks for posting!
Click to expand...
Click to collapse
I think you have to enable it to show system apps to see more than the 11 you are seeing.
pyrostic said:
I think you have to enable it to show system apps to see more than the 11 you are seeing.
Click to expand...
Click to collapse
I just downloaded this today and am seeing the same problem. I think it is not used to the apps being located in the sd directory even though it isn't a true sd directory so it is not looking there.
Though I feel somewhat competent with regular ADB I would love for a fix for this program with regard to the Kindle fire app directory to come out. It's really neat, especially the large screenshot feature.
Can't get the Mac version working on my iMac (OS 10.6.8). When I launch QtADB I immediately get the attached error screen.
Works great for me and show's all my apps on CM7. Very cool. Thanks for heads up.
I do see "enter registration key". Is this some kind of trial or limited in some way?
Edit: Can't do much in the "Recovery" portion of the app. Just about everything is greyed out.
bradys said:
Can't get the Mac version working on my iMac (OS 10.6.8). When I launch QtADB I immediately get the attached error screen.
Click to expand...
Click to collapse
Same here on my Macbook Pro running 10.7.2
the the linux script doesnt even run on ubuntu
I didn't make it or maintain it. Maybe you can ask the developers at their website?
Sent from my SPH-D710 using xda premium
t3project said:
the the linux script doesnt even run on ubuntu
Click to expand...
Click to collapse
Install qtlibs from the repos first (or just install full kde -- it's better than gnome nowadays anyway at v4.8).
Hi there,
I got the latest version of adb and have installed the latest pc driver for Galaxy Nexus from samsung's website under device SCHI515
But "adb devices" is still not showing the device. I can see the device listed in My Computer. I have gone thru "Computer/Manage/update the device driver" routine as well
and yes, I have searched thru the forums and none of the suggestions have helped me
Any ideas?
You need the adb drivers from the SDK.
Sent from my DROID RAZR MAXX HD
I looked into that as well. Apparently I am supposed to have a google directory in the "adb/sdk/extras" but there isn't one. There is only an "android" directory.
spencer88 said:
You need the adb drivers from the SDK.
Sent from my DROID RAZR MAXX HD
Click to expand...
Click to collapse
mianbarray said:
Hi there,
I got the latest version of adb and have installed the latest pc driver for Galaxy Nexus from samsung's website under device SCHI515
But "adb devices" is still not showing the device. I can see the device listed in My Computer. I have gone thru "Computer/Manage/update the device driver" routine as well
and yes, I have searched thru the forums and none of the suggestions have helped me
Any ideas?
Click to expand...
Click to collapse
Which version of the SDK are you running? The 32 or 64.
do you have usb debugging turned on? sometimes an easy thing to skip over
mianbarray said:
I looked into that as well. Apparently I am supposed to have a google directory in the "adb/sdk/extras" but there isn't one. There is only an "android" directory.
Click to expand...
Click to collapse
1) get the "universal_naked_driver" from the GNEX forums
2) the fastboot/adb folder is sdk/platform-tools; rename the playform-tools folder into Android and move to the root of your C: drive
3) ???
4) profit
mianbarray said:
I looked into that as well. Apparently I am supposed to have a google directory in the "adb/sdk/extras" but there isn't one. There is only an "android" directory.
Click to expand...
Click to collapse
You need to launch the SDK manager and select the drivers from the list of things to download. After they download, they will be in that directory you listed.
Note: you need java installed in order to launch the sdk manager.
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
robopilot99 said:
Hey everyone. I just purchased a Asus ZenFone 2 (cheep model) and am attempting to root it/install a custom rom. However I have encountered difficulty with fastboot on my Ubuntu Linux machine. ADB works without any issues but fastboot does not always getting stuck on a endless <waiting for device> and my phone does not appear on the list of connect devices (fastboot devices). However my Nexus 7 (2013) works without any issues. I have tried running fastboot as root and didn't have any success. I was hoping that someone out here would have some idea why one device works but not the other. Thanks to anyone who can provide assistance.
Click to expand...
Click to collapse
I had the same issue. Tried it on windows (though I hate windows ) and it worked on windows. I am STILL trying to figure out how and why?
I had the same problem on Ubuntu 15.04, and I fixed it by uninstalling the outdated version of fastboot in Ubuntu's repositories and replacing it with the binary from the Android SDK platform tools.
The fastboot protocol may have changed slightly with Lollipop, and Ubuntu's fastboot and ADB packages say they're from 4.2. Remember to run fastboot as root unless you have the udev rules set up. Hope that helps!
yes i had a similar issue on ubuntu with the repo version. I actually got an error message saying i needed a newer version
Thanks. Using the version I got from the internet worked fine. I'm now getting and error about fingerprinting and stuff. Looks uke I'll have to wait for a way to unlock the bootloader on the latest version.
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
bhoth said:
Hi I am having the same issue but when I search, I get a lot of info about updating ADB but nothing on Fastboot. For those that have figured this out, would you mind posting a link?
Thank you!
Click to expand...
Click to collapse
You will want the Android SDK tools. Here is the download page:
https://developer.android.com/sdk/index.html#Other
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
joel.maxuel said:
You will want the Android SDK tools. Here is the download page:
It's a 300MB download, so it's a bit overkill for what you need, but it is there.
Also, if you need to download it again (update), can use the SDK Manager (included) to select/download "Platform-Tools" (at the very least - if you find yourself emulating Android on your PC, you may want more).
Click to expand...
Click to collapse
yeah that's what I ended up doing. It's a pain to find it in the huge download but it's kinda your only option.
im currently on the same problems as you too.. cant use fastboot on ubuntu 14.04 lts.. but i found this article online, didnt test it yet since im on my windows right now to use fastboot.. who knows this may help in updating to latest adb bin..
http://bernaerts.dyndns.org/linux/74-ubuntu/328-ubuntu-trusty-android-adb-fastboot-qtadb
Click to expand...
Click to collapse
wait i was wrong, the cmd there is to update adb to latest version and not for fastboot.. cant help anyway, unless download the whole android sdk as mentioned above..
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
illusion_insanity said:
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
Click to expand...
Click to collapse
Try rebooting. It could also be intentional behavior on Amazon's side (they won't let you change the default launcher, and they might prevent you from even opening another one).
Sent from my Amazon Jem using XDA Labs
thanks
i am no a pro at this but i think someone said its because it has a locked bootloader.
illusion_insanity said:
i am no a pro at this but i think someone said its because it has a locked bootloader.
Click to expand...
Click to collapse
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Thanks
monster1612 said:
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Click to expand...
Click to collapse
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
illusion_insanity said:
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
Click to expand...
Click to collapse
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
the thing is, I don't have the adb drivers to use kindle fire utility
illusion_insanity said:
the thing is, I don't have the adb drivers to use kindle fire utility
Click to expand...
Click to collapse
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
windows
monster1612 said:
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
Click to expand...
Click to collapse
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
illusion_insanity said:
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
Click to expand...
Click to collapse
The tutorials recommend you install the Android SDK, but unless you're planning on doing Android app development, most of the SDK will be useless. Instead of using the SDK (which is quite bulky), I'd recommend that you run the 15 second ADB installer, which can be downloaded here. Run the program as administrator, and when you're asked the questions, answer Yes/Y for the "install ADB and fastboot" and "install ADB system wide" questions, and No/N to the "Install device drivers" question. The reason we're not installing the drivers bundled with the installer is because the drivers are for Google devices, which will clearly not work with the Kindle.
Because of this, we're going to install the Kindle drivers separately. Go ahead and download the zip file in this thread, which contains installers for the Kindle drivers. Unzip the folder, run one of the executables as administrator, and install the drivers as prompted. You may get errors about installing unsigned drivers - continue anyway. Once the drivers successfully install, reboot your machine. Once you're rebooted, plug in your kindle (make sure it's booted into either recovery or a ROM). (NOTE: If you're booted into a ROM, you may get a prompt asking if you want to allow USB debugging. If you get this message, check the "Always allow from this computer" checkbox, and then OK.) Open a command prompt window and type adb devices. Below "list of devices attached", you should get a random string back (this is your device's ID) and either "unauthorized", "offline", or "device" next to it. If you don't see any text below "List of devices attached", then check to make sure ADB is enabled on your kindle (which it probably is if you rooted it ).
AWESOME
Have see it tried it yet but I will I gave ed up with sdk I have crap internet so it takes forever to download. I needed this thanks alot
Okay I got a problem I just got mine finally today in the mail. my Windows 10 recognizes it in ADB but as soon as I go to fastboot no matter what I do it's like it doesn't see the drivers anymore. Anybody have an idea how to get around this so I can unlock the bootloader?
Edit:. Nevermind I finally found a driver package that worked. What a deal
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Flippy125 said:
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
I finally figured it out. Found the right drivers. Took me forever
DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
mac796 said:
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
Click to expand...
Click to collapse
Please could you share the driver pack that worked for you?
Then just let us know which driver you installed so that the Pixel 6 was recognized. And a download link wouldn't be bad either - that helps others with the same problem.
Try Download Minimal ADB and Fastboot Tool it should work
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
After you install it ensure you update SDK Platform Tools the file name " ADB "
/c/adb
cd993 said:
Please could you share the driver pack that worked for you?
Click to expand...
Click to collapse
Yet Another Universal ADB Driver Package and adbupdater for Windows
I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before. While at it I added those two tools usually used, that is adb and fastboot. Based on batch scripts, so it's open source. Self Signed, not...
forum.xda-developers.com
Sorry took me a bit to find it again
mac796 said:
Sorry took me a bit to find it again
Click to expand...
Click to collapse
Thanks will give this a try later on!
On Windows 11 the official r13 Google USB Driver pack worked - but only after booting into an alternative mode that allows unsigned drivers. For some reason Google's drivers are not signed, and Win11, with TPM+SecureBoot refuses to load those drivers in normal mode.
cd993 said:
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Click to expand...
Click to collapse
It sounds like you're talking about accessing the phone's storage via MTP. When you plug the phone into the computer, you may need to choose the new notification regarding charging and switch it to the mode to be able to access the storage. Probably defaults to "Charging this device via USB", and you need to click on it and select something like "File transfer/ Android Auto". This won't require any new Windows drivers.
Please correct me if you're not talking about accessing the phone's storage.
mac796 said:
I finally figured it out. Found the right drivers. Took me forever
Click to expand...
Click to collapse
Would you mind saying WHICH drivers? Thanks...
wsalopek said:
Would you mind saying WHICH drivers? Thanks...
Click to expand...
Click to collapse
I posted it in this thread. Read it. There's a link
mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
OK...thanks...got it.
mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
wsalopek said:
OK...thanks...got it.
Click to expand...
Click to collapse
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).
My problem ended up being that my USB Hub went bad... Was getting Yellow Exclamation in Device Manager and an error when going into Fastboot. Once I plugged directly into the PC, no issues. New hub ordered!