Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH
Related
I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?
timal said:
I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?
Click to expand...
Click to collapse
You should ask this in the thread that already exists.
If you follow every step listed, that won't happen. Do not skip any steps.
Do not skip any steps
1. Boot the device in fastboot mode, hold down the back button while powering on.
2. Connect via USB.
3. "fastboot boot recovery-RAv1.1.1H.img"
It will reboot into the custom fastboot with a black background. Then you'll be set to do these commands:
adb shell mount -a
Ignore the the errors...
adb push recovery-RAv1.1.1H.img /system/recovery.img
adb push recovery-RAv1.1.1H.img /sdcard/recovery-RAv1.1.1H.img
adb shell flash_image recovery /sdcard/recovery-RAv1.1.1H.img
adb shell reboot
I would have tried all that except the adb drivers are not working with the magic on windows vista. Device manager only shows Android 1.0
timal said:
I would have tried all that except the adb drivers are not working with the magic on windows vista.
Click to expand...
Click to collapse
they work fine, you just need to properly install them.
k4r1m said:
they work fine, you just need to properly install them.
Click to expand...
Click to collapse
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.
timal said:
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.
Click to expand...
Click to collapse
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.
Amon_RA said:
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.
Click to expand...
Click to collapse
Thank you I tried all the above. Long story short brick, no power dead . This hobbie is getting expensive.
I installed sdk android-sdk_r07-windows.zip and also tried with android-sdk_r06-windows.zip.
When I do "adb devices" the list of connected devices is empty. My phone is a Huawei U8230.
The USB debugging mode is enabled. I can also see the files inside the phone in a Windows Disk Drive.
Any sugestion on how to get the device listed?
A bit stupid... But your phone is running android ?
You can try to search your phone drivers if there were somes, didn't it ?
Fixed it.
1. First Installed the SDK (all components including usb drivers).
2. Then Enable USB debug mode on the phone.
3. Then connect the phone.
4. Then a CD Drive is detected -> run setup from that drive.
5. Last restart adb.
Fiuuuuuuuu that costed a lot!!!!!!
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Hoping it's okay to bump my thread after a month.
Does anyone know what to do in this situation?
Thanks!
jorge_quintanilha said:
Hello there,
I'm running CM11 20141223 NIGHTLY on my XT1033, and everything is working fine so far, with the exeception of USB communication. I develop my stuff on my desktop, which is running W7. Consider the following scenarios:
1) If I plug it in MTP mode (debugging deactivated), it won't find. Windows tries to install a USB Composite Device driver and fails.
2) If I plug it in PTP mode (debugging still deactivated), Windows installs a Moto G driver and access the DCIM camera folder normally (that's what I've been using to "push" files into it, and then move it with file manager with temp su access).
3) In both MTP and PTP mode, but with debugging activated, Windows detects it as a USB Composite Device. On Device Manager it shows up with the yellow triangle warning icon, but I can't seem to update it (tried with the extra Android drivers that comes with ADT).
4) Neither adb nor fastboot can detect the device. Which is weird because on my notebook, running windows 8.1, I got the same situation but adb (only, fastboot still can't) can detect it.
5) I also installed Koush universal ADB Drivers on both machines.
Does anyone have some insight on the matter? Should I get rid of Koush?
I don't intend on upgrading to CM12 anytime soon. In fact, I did it some weeks ago, but I'm more confortable with CM11 so I rolled back to it.
Click to expand...
Click to collapse
Have you tried Motorola's drivers? It installs separate drivers for adb, fastboot, mtp. https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
Okay, so, I am currently trying to root my Nvidia Shield Tablet, and my PC keeps registering the tablet with "Offline."
I am getting frustrated, and I want to really put a system-wide adblocker on the tablet.
I have done these following actions and haven't gotten a prompt to trust the computer.
1. Reboot the tablet.
2. Switch from FTP to PTP
3. Reboot my PC
4. Update all Android SDK drivers.
5. Uninstall Android SDK
6. Use all ports on my computer
7. Turn Debugging off and on.
8. Revoke USB debugging authorizations
9. Reboot my tablet into recovery mode/fastboot mode.
10. Reinstall ADB drivers.
11. Reinstall Java.
I cannot get my device to show it to be online. I really am desperate to root my tablet right now. I am in dire need of help. I cannot get a single reading of it being online. The ADB driver installer recognizes my device. But ADB doesn't recognize it as "Online."
Adb is working only with: normal turn on, recovery mode.
Reboot to bootloader, connect, and use fastboot.
Command "fastboot devices", if "no devices" - on tab select "fastboot protocol".
All you need(adb/drivers) is at nvidia developer site - go to "stock images".
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Unable to connect to usb
I installed Carbon-cr-5.1-moo-release-bacon-20180202-1444.
I am unable to get usb connection working and having tried many different things...
-I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
-In Android Studio SDK Tools I have installed Google USB Driver v12.
-I have developer options turned on and Android Debugging turned on.
-When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
- when I go into developer options and hit 'select usb configuration' my selection of mtp or whatever is always ignored and charging selectiomn remains
-Device Manager / Portable or Other devices does not have the phone beneathn it.
-When I run adb devices in cmd there are no devices attached.
-I cannot find a OnePlus One adb usb driver. I thought I found one but I have no way to verify and after installing it made no difference
I want to update to the latest rom in case this may be the cause, but after I download it to the phone and click flash
I just get the oneplus icon forever and the recover app twrp does not come up. It used to be there but then after I installed
the first rom after a couple of uses it disappeared for some reason or at least will not boot to it.
When I installed that first custom rom I folowed instructions for rooting and on completion it says to open up the installed
su app but when you open it it says there is a more up to date version but when you try to install that it fails.
Now all the apps that will not run if your app is rooted say it is rooted and all the apps that will not run unless it is rooted
say it is not rooted.
I think I need connection via usb in order to reinstall the twrp recovery app in order to install an up to date rom, hoping this may help
me solve the usb issue, but I cannot get the usb connection working as described above,
any hehlop would be appreciated.
Same Situation
hardya said:
I have latest Android Studio installed and Android Debug Bridge version 1.0.41.
In Android Studio SDK Tools I have installed Google USB Driver v12.
My ONePlus One has Carbonfibers ROM, has developer options turned on and Android Debugging turned on.
When I plug in OnePlous One I get no mobile notifications and nothing in Win 10 Pro.
Device Manager / Portable or Other devices does not have the phone beneathn it.
When I run adb devices in cmd there are no devices attached.
I cannot find a OnePlus One adb usb driver.
Any suggestions how to diagnose this problem and get my OnePlus One recognised by adb?
Click to expand...
Click to collapse
but my phone connects in edl mode just for 10 seconds and then automatic