Related
If you have a 2.73+ rom with the latest hboot you will need to follow This Post to boot the recovery image
1) restart into bootloader (switch on holding the back button)
2) Extract the latest GSM Hero recovery IMG into your android SDK/tools folder
(For SDK & CMD help reffer to Post 3 "The Basics" )
3) Download Superuser.zip and extract the contents to your SDK/tools folder.
4) Plug in USB
5) open a CMD prompt from the tools directory and type the following command> fastboot boot recovery-RA-hero-v1.5.2.img
(you should now enter a recovery console on the handset)
NOW PERFORM A NANDROID BACKUP from the recovery menu, once completre, continue..
6)then type the following commands in CMD exactly as they are here, hitting enter for a new line.
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
Congratulations you now have root access..
Download "Root Boot" from the app store (this will only work if you have root!)
Step 6 modified thanks to ENLIGHTENER, cheers, su whitelist working nicely now..
Recovery image updated to recovery-RA-hero-v1.5.2.img , thanks to Amon_RA
Please be carefull! I accept no liability!
FYI, To unroot you will have to either restore an earlier backup or flash a stock rom..... (reccomend the new official HTC Update via RUU to do a full reset)
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
The Basics
gaabrysz said:
OK i have a stupid question as i'm new to all that android thing. Where is the sdk folder? How do i open CMD? Maby u could do a tutorial for totaly new guys on *how to root your HERO* ??
Thanks
Click to expand...
Click to collapse
1) you need to download the android software development kit from Here and extract it to yourhard drive.
2) (check) fastboot and adb should be located in the tools folder.
3) in tools right click>new>shortcut when asked enter CMD.exe
4) right click on cmd.exe shortcut, go to properties and clear the "start in" box.
job done, follow as above.
*Edit*
FYI
Verify you have root, go to app store> download Root Booter and test its functions if this works, you have root!
The G2 is the HTC Hero on T-Mobile.
The SDK includes all the drivers needed.
once you have booted the img via fastboot you should enter a recovery console, at this point you need to follow the instructions exactly as typed for adb,
I am running windows 7 Ultimate, should be the same for all windows platforms,
Cheers
__________________
Thank you
Oh and one more question. Do i loose any data doing this??
gaabrysz said:
Thank you
Oh and one more question. Do i loose any data doing this??
Click to expand...
Click to collapse
No, you will not loose anything but be sure to do a Nandroid incase you need to go back to "Stock"
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
Use a program that requires root access.
MrHorus said:
I've followed the process and I never ran into any problems, but I'm new to Android having previously owned Win Mobile phones and now an iPhone.
I got my G2 today on a contract upgrade just so that I could play around with it and try some development work.
Now that I have followed the process, how do I verify that I now have root?
Is there anything I can do to test?
Click to expand...
Click to collapse
If by G2 you mean HTC Magic/Sapphire rather than HTC Hero you're in the wrong place...
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Just tried it and it works sweet... Took all of 5 minutes... Awesome work thank you
I now have root access on my Hero
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Have you installed the correct drivers? They are located in the SDK folders you downloaded.
If so try entering "adb devices" in the commmand prompt, Just incase the daemon didnt start.
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
gaabrysz said:
OK i have a problem when i do this:
4) open CMD prompt use> fastboot boot cm-hero-recovery.img
the phone reboots and then you have to do "adb shell" but when i do that it says "error: device not found", what now??
Click to expand...
Click to collapse
Having the exact same problem here.
gaabrysz said:
I think i did. i'm on win 7 x64 btw. ok i'll switch to vista 32bit and try there.
Ok i have checked and in the device manager there is a ADB device>HTC bootloader so i think drivers are correct.
Click to expand...
Click to collapse
try entering adb devices see if that makes any differences
btw, when i done mine the phone was in the recovery console..
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Ok so lets clear something. after i type in cmd: fastboot boot cm-hero-recovery.img my phone reboots and goes to recovery console where i have some otions.... so now i have to type in cmd: adb shell, yes??
still nothing and the adb devices didn't help.
Mienaikage said:
Never mind I got it, I'm on Win7 x64, had to switch the driver from:
HTC Dream Composite ADB Interface Version: 1.0.10.1 [25/06/09]
To:
HTC Dream Composite ADB Interface Version: 1.0.9.0
Click to expand...
Click to collapse
Can u share a link to the drivers?? Please
it sounds like a driver issue. Using the lastest SDK?
android-sdk-windows-1.5_r3
OK got it working. It is a driver issue. using latest sdk but i had to use older drivers just like Mienaikage sad.
gaabrysz said:
Can u share a link to the drivers?? Please
Click to expand...
Click to collapse
They came with the SDK I believe, in the android-sdk-windows-1.5_r3\usb_driver\amd64 folder.
If that's not it then it was this one: http://forum.xda-developers.com/showthread.php?t=446274
No ADB knowledge needed. Just follow instructions.
1. Download mini-adb Here
2. Extract that and put it on your desktop.
3. Go download HTC sync Official Page or HTC sync Direct Download and install it. If you are NOT HTC, then download whatever you need to get the drivers needed for your phone onto your PC (like samsung Kies)
4. Plug your phone into your computer and make sure debugging mode is on.
5. Now go to your mini-adb folder on your desktop and double click RunMe.bat
6. When the black command prompt window pops up, type the following:
adb devices
7. If it lists your Device, then you did it!
8. To push any file, make sure you place it in the same folder as your RunMe.bat, and the command will be
adb push WHATEVERTHEFILENAMEIS /WHEREEVERYOUWANTITTOGO
For example, to push a file called libSwypeCore.so into /system/lib/
Adb remount
adb push libSwypeCore.so /system/lib/
+1 Thanks if this worked for you!
P.S. Technically you have installed ADB by step 5. Step 5 and onwards just tells you how to use it.=P Title doesn't lie.
why not just install Android SDK from http://developer.android.com/sdk/index.html
and you got ADB right after the installation.
By the way if you wanna push something to /system, you have to "adb remount" first to set it "r/w"
When I click runme it opens for a split second and then disappears
I so wish i could of found this earlier to save me the 4 hours of WTF moments i was having.
Also beats not having to install the SDK of 31megs not counting install/setup as well.
jzhyok said:
why not just install Android SDK from http://developer.android.com/sdk/index.html
and you got ADB right after the installation.
By the way if you wanna push something to /system, you have to "adb remount" first to set it "r/w"
Click to expand...
Click to collapse
I almost gave up on adb cuz that way didn't work for me. And yes, I forgot to include adb remount.
this should be stickied for the nooblets.
Fantastic; this is definitely going to make getting CM6 my fiancée's G2 easier. Now, which of the 3 rooting processes below should be the one I use for her stock T-Mobile G2:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
http://forum.xda-developers.com/showthread.php?t=834228
http://forum.xda-developers.com/showthread.php?t=886023
Thanks!!
How do I flash a radio with this? Cause I don't see any "fastboot" folder, whatever that is.
BradBot said:
Fantastic; this is definitely going to make getting CM6 my fiancée's G2 easier. Now, which of the 3 rooting processes below should be the one I use for her stock T-Mobile G2:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
http://forum.xda-developers.com/showthread.php?t=834228
http://forum.xda-developers.com/showthread.php?t=886023
Thanks!!
Click to expand...
Click to collapse
I edited my post to answer ur Q
convolution said:
I almost gave up on adb cuz that way didn't work for me. And yes, I forgot to include adb remount.
Click to expand...
Click to collapse
Same boat..I saw your post on Jan 20th in the Guide for ADB thread, which is really nice..
But I got to the same point(you also outlined in that thread) of after uninstalling the previous Android usb drivers on my system, and trying to choose a specific location to look for a x86 driver, I was left with Windows not allowing me to click 'OK' to denote the USB driver folder from the Android SDK that I wanted to scan. Not sure what was up, but I was elated to see the link to this thread in your sig.
Thanks for the guide! My Evo 4g Shift thanks u as well
How do I install a Radio with this?
Broman400 said:
How do I install a Radio with this?
Click to expand...
Click to collapse
don't know.
I assume you find the apk, find the lib files, and push stuff to places?
LOL I wiped my laptop cause it had viruses and I forgot how to install ADB so I had to click my own link. LOLL
convolution said:
LOL I wiped my laptop cause it had viruses and I forgot how to install ADB so I had to click my own link. LOLL
Click to expand...
Click to collapse
hahaha
Broman400 said:
How do I install a Radio with this?
Click to expand...
Click to collapse
K I got it. You can only flash a radio if you have S-off.
Download the zip file for the radio. Put it into your SD card. Boot up in recovery. Choose flash zip file. Choose radio zip file. Done.
No adb required.
Gee, thanks past me! I would have forgotten how to get it if it weren't for my own sig!
From: Present Me.
convolution said:
No ADB knowledge needed. Just follow instructions.
1. Download mini-adb Here
2. Extract that and put it on your desktop.
3. Go download HTC sync Official Page or HTC sync Direct Download and install it. If you are NOT HTC, then download whatever you need to get the drivers needed for your phone onto your PC (like samsung Kies)
4. Plug your phone into your computer and make sure debugging mode is on.
5. Now go to your mini-adb folder on your desktop and double click RunMe.bat
6. When the black command prompt window pops up, type the following:
adb devices
7. If it lists your Device, then you did it!
8. To push any file, make sure you place it in the same folder as your RunMe.bat, and the command will be
adb push WHATEVERTHEFILENAMEIS /WHEREEVERYOUWANTITTOGO
For example, to push a file called libSwypeCore.so into /system/lib/
Adb remount
adb push libSwypeCore.so /system/lib/
+1 Thanks if this worked for you!
P.S. Technically you have installed ADB by step 5. Step 5 and onwards just tells you how to use it.=P Title doesn't lie.
Click to expand...
Click to collapse
This archive has some kind of weird ".exe" file. What is this, some kind of balmervirus?
This is an older thread but I'm hoping someone can help me. I had adb installed on my old win7 pc and I had the my nexus drivers installed and everything was good. A month ago I got a new pc that is running win8 and I've had nothing but trouble ever since. I cannot find nexus drivers that will install on windows 8. Is anybody else out there running windows 8 that can help me? The VZW driver exe file would not even install for me and I ran it as an administrator.
ba_hamilton said:
This is an older thread but I'm hoping someone can help me. I had adb installed on my old win7 pc and I had the my nexus drivers installed and everything was good. A month ago I got a new pc that is running win8 and I've had nothing but trouble ever since. I cannot find nexus drivers that will install on windows 8. Is anybody else out there running windows 8 that can help me? The VZW driver exe file would not even install for me and I ran it as an administrator.
Click to expand...
Click to collapse
Yeah... I also gave win8 a try...
I reverted back to win 7. Sorry, can't help you there bro. Have you tried downloading the nexus toolkit and installing gnex drivers using that toolkit?
AW: [GUIDE] Install Portable ADB In 5 Easy Steps
Try this: In Windows 8 install the drivers with Windows 7 Compatibility checked. This did the trick for me while testing adb and rooting a samsung galaxy tab on my windows 8 x64.
I found this tip on only one forum after trying many other tips and drivers around for more than one day and it worked. So all credits to this poster.
Sent from my HTC Desire Z using xda app-developers app
So, someone went and did something to my phone, I guess he deleted everything, and formatted the SD card, system folder, etc.
Now, I don't have any of my ROMS on my phone, and I'm stuck with just CWM. I cannot mount the USB storage using CWM, so I can't transfer any files over.
I'm using Windows 8.1, and I've tried installing the drivers using Flashtool. Installation of drivers was successful, but Windows still detects the phone as a "Xperia S" with an exclamation mark. Running Flashtool tells me I need to install the drivers from the driver folder. I installed the 3 drivers with Xperia S in its name, and the fastboot and adb drivers. Still doesn't work.
Any advice? Basically I just want to be able to copy a ROM over to the phone to install it, as I don't have any OS(?) on the phone right now.
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app
monivan said:
Actually window 8 can! U have to Disable driver enforcement setting through advance reboot in window 8
Sent from my SGP321 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.
pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks. I'll try and see if I can find a Windows 8 or 7 machine. Not possible to do this in Mac, I suppose? Would a virtual machine work, you think?
markiemice said:
I've done that. I installed the drivers, but the phone is still not recognised for some reason. Not entirely sure why, though I suspect it's got something to do with me using Windows 8.1.
Click to expand...
Click to collapse
Maybe u could try Sony Update Service, so that the fastboot driver might install properly through official software from sony.
Sent from my SGP321 using XDA Premium 4 mobile app
Is it save to assume that you have experience flashing ROM? Just asking coz sometimes we missed some obvious step.
Yes, I do. I've flashed using CWM. Mostly it's pretty easy, just copy the ROM onto the phone, and install it using CWM after clearing caches.
pattz said:
You can get into cwm? Then Transfer and install a Rom.ZIP with adb sideload. I believe the adb driver is working in Windows 8. Open up Windows terminal, browse to the folder where adb.exe and the custom Rom is saved (should be there). In cwm select adb sideload and write in the command line in windows "adb sideload Rom.ZIP". If thats Not working (what it does for me, im also using Windows 8, cant install any Rom on another way) install all the drivers and Software for flashing on a Windows 7 device and it should work just fine.
Click to expand...
Click to collapse
Thanks for the idea to do a sideload! I used a virtual Windows XP, and was able to install a ROM onto my phone!
Thanks very much.
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Digital signature of the driver or wrong drivers is the problem
joedoctor said:
I tried everything the internet could offer. Installed all the google and or OnePlus 5T drivers I found, many different ADB versions, enabled all the needed settings on the phone, yet when I type "fastboot devices" it comes up empty.
Followed many guides and videos, did all the steps. What could be the problem?
Click to expand...
Click to collapse
u are not saying mutch about how u are trying to enter fastboot
u do know the phone must be turn into fastboot right ?
...
same here, done everything i can...
mockneygeeza said:
same here, done everything i can...
Click to expand...
Click to collapse
to get fastboot to work u need to reboot the phone into fastboot
-fluffy- said:
to get fastboot to work u need to reboot the phone into fastboot
Click to expand...
Click to collapse
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
I'm going to try the above, it's never too late ?
moeq123 said:
Right, and (if you are a Windows user) after you put it into fastboot mode, you Need to overwrite the Drivers in the device Manager inside of Windows to the adb / fastboot Driver...
not just the "update Driver" Option.. you really Need to search und choose for the .inf file.
after that has been done, Windows should be able to find your device with the fastboot.exe
That should do the trick.
If you got any Problems Setting this up in Windows, and want some Support, I could help you remotely with TeamViewer application. (as far as our timezones allows us to do that)
Edit: Nevermind - probably to late.. this thread is from march.. lol
Click to expand...
Click to collapse
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
-fluffy- said:
well i just downloaded the adb folders an put my phone into fastboot connectet usb an it installed automatisk the drivers
Click to expand...
Click to collapse
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
moeq123 said:
Yes, it also did that for me after I plugged in my Device AFTER booting it into Fastboot.
BUT! since I'm on Windows 10 Education; 64 Bit, it somehow messed up the Drivers or something. Fact is, These automatically installed Drivers weren't working for fastboot (at least for me and probably for many others too).
the command "fastboot devices" wasn't able to detect my phone.
But if you download the needed adb / fastboot Drivers for that device and reconfigure the driver via device Manager on Windows
to choose the just downloaded adb /fastboot Drivers - it worked for me afterwards.
Click to expand...
Click to collapse
im on windows 10 also an my adb devices also show nothing but i can still flash recovery an all
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!