Develop Bugs

[Q] PC wont register my Evo4g as ADB

I've searched to the best of my ability in these forums and cant seem to find an answer to my problem...
Ive been looking at a particular thread's information on how to replace my MMS file and default.xml in order to get my MMS functionality working on my Evo 4G flashed to Cricket. http://forum.xda-developers.com/showthread.php?t=793588
Ive installed the SDK, installed the USB driver package within, installed the repository for 2.3.3 (what my phone is running).
I uninstalled all drivers from my phone using USBDeview.
And STILL, after plugging my phone in while in recovery mode (Clockwork mod 2.3.3) my PC will not recognize it as ADB, only as an Android Phone.
I have everything i need setup to push the files to my phone and get back the functionality of my MMS, but I cant seem to figure otu how the heck to get my PC to see my hone as an ADB. Any suggestions?

Did you install the modified unrevoked usb drivers?

Use the original USB cable... had similar problem and that solved it...
Sent from my A500 using xda premium

"Did you install the modified unrevoked usb drivers?"
I don't know what that is... All tutorials I found instructed to just use the USB drivers provided byt he Google Repository built-in to the SDK. Would this solve my problem? If so, where can I find it?
And yes, I'm using the original USB cable.
Is there a way to push files to the /system directory without using ADB? I just want to put 2 files in my /system directory...

PhayzR said:
"Did you install the modified unrevoked usb drivers?"
I don't know what that is... All tutorials I found instructed to just use the USB drivers provided byt he Google Repository built-in to the SDK. Would this solve my problem? If so, where can I find it?
And yes, I'm using the original USB cable.
Is there a way to push files to the /system directory without using ADB? I just want to put 2 files in my /system directory...
Click to expand...
Click to collapse
Here > http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
And nope, because you'll need 'permission' to have r/w on the system directory.

PhayzR said:
I've searched to the best of my ability in these forums and cant seem to find an answer to my problem...
Ive been looking at a particular thread's information on how to replace my MMS file and default.xml in order to get my MMS functionality working on my Evo 4G flashed to Cricket. http://forum.xda-developers.com/showthread.php?t=793588
Ive installed the SDK, installed the USB driver package within, installed the repository for 2.3.3 (what my phone is running).
I uninstalled all drivers from my phone using USBDeview.
And STILL, after plugging my phone in while in recovery mode (Clockwork mod 2.3.3) my PC will not recognize it as ADB, only as an Android Phone.
I have everything i need setup to push the files to my phone and get back the functionality of my MMS, but I cant seem to figure otu how the heck to get my PC to see my hone as an ADB. Any suggestions?
Click to expand...
Click to collapse
teh roxxorz said:
And nope, because you'll need 'permission' to have r/w on the system directory.
Click to expand...
Click to collapse
If you can still mount your phone as a usb flash, or disk drive or even take the sd out use an adaptor and transfer the files to the sdcard, now you have 2 of many options but these I prefer
1) You can use Root explorer which I prefer this will give you the option to mount system read write rather easily, then you can just copy or move your files and drop them in where you need them
or
2) You can install terminal on your phone and manually transfer files using the commands
this one I am not positive which one is needed but they will work as long as you have root and busybox
# su
# busybox mount -o remount,rw /system -this will put your system directory into read/write
you may try leaving the busybox off if it doesnt work at first.at the prompt you can use either cp or mv for copy or move I would do copy
should look something like this.
#cp (source directory)/(file you wish to copy) /system/(destination of file add additional directories if needed)
Make note though this is all dependant on you having root and busybox installed. Otherwise this will not work but I would work on getting the usb drivers working.

Sounds funny but did you enable usb debugging in settings/applications?
Sent from my PC36100 using Tapatalk

Sure did. I ended up replacing the default.XML, apn.XML and mms.apk files, but still no luck... I tried using apn backup and restore to install the new apn but no luck there either. Aaaaand when I tried to restore deathsled's jiminy mod, it looks like it just defaults back to cm7 instead. Any idea how I can try running jiminy without deleting my cm7 incase it doesn't work out as planned?
Sent from my PC36100 using XDA App

Still no luck...
Turns out I can't do a full flash (which is apparently what I need to get my MMS and GPS on my Cricket Flashed Evo4G) using ES Explorer or Root explorer. I need to use ADB to do so, but I still can't get the drivers working...
Any ideas?

[Q] Can't Sync Windows 8 with DInc

I am trying to sync my DInc with Windows 8 Pro to unlock it through the HTC developer site. Unrevoked wont work due to the version of my baseband being 2.15.10.12.20. Software version 2.3.4.
I have USB debugging enabled, fastboot off, performed a factory reset, cleared cache through HBOOT, and the computer DOES reckognize the phone and I am able to select open files and do whatever I need to do with the phone... it just wont display on HTCSync so I can go through the process of rooting it and getting JB on it.
I have also tried running HTCSync in compatability mode. I have been working on getting this working for days now, and have searched this and many other forums for solutions to no avail.
Any ideas would be greatly appreciated, and any more information you need will be provided asap.

Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.

PonsAsinorem said:
Check the unrevoked site for the proper drivers of you haven't already. You don't need HTCSync to work, just adb.
Click to expand...
Click to collapse
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?

cyborggold said:
The baseband for this particullar device isn't supported by unrevoked, so I'm looking for other solutions. Ate there any other ways you know of to get jb on this phone?
Click to expand...
Click to collapse
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.

PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I can connect the phone and browse files through Windows explorer, I guess I'm just not familiar with adb yet, ill try to find more information on that and give it a try, thanks!

Still Lost
PonsAsinorem said:
I understand that unrevoked won't work, but you need your PC to connect to it as far as drivers go (most people use unrevoked drivers). You don't need HTCSync, just adb. If you can setup adb to work, and get it read when you issue
Code:
adb devices
then you should be good to.
Click to expand...
Click to collapse
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!

cyborggold said:
I've been looking for the adb tool you had mentioned, but the only reference I am finding is for ICS/JB. I'm currently running Gingerbread (2.3.4 to be exact) Your last comment mentioned using a command 'adb devices' which makes me think adb is actually a command in windows or a linux application... I'm sure something I've said already has made you laugh at me so I'll stop now and just ask... can you give me a link to the process I need to follow to get this resolved, because for whatever reason, I can't find what I think you were trying to direct me towards.
Thanks!
Click to expand...
Click to collapse
How To Set Up Android ADB & Fastboot On Windows [Tutorial]
The only note on this guide I'd make, is not to use the C:\ drive. It's always a bad idea to put stuff in your root directory. Myself, I installed the sdk (which installed itself to C:\Program Files) then I added that to the system path. Also, you might have to reboot (or at least log off and log back on) to reset your PATH.

Fastboot the Ouya and Windows 7

Hello I installed a new FW on my Ouya and it killed CWM recovery. Right now I'm stuck at the device manager and it list my Ouya as other device and fastboot is under that. I tried installing the drivers from OneClickOuyaRecovery.zip, but it doesn't work. What am I doing wrong?

Install the adb sdk then your going to want to install the Google drivers and add a line of code to the file under nexus to make It work with the ouya. Your going to have to Google it or maybe some one can file you in better on it. I'm at work and don't have access to a computer to give you a 100% detail on how to do it. Like I said just Google it that's how I found out how to make it work.
Sent from my SCH-R970 using Tapatalk

samt3 said:
Install the adb sdk then your going to want to install the Google drivers and add a line of code to the file under nexus to make It work with the ouya. Your going to have to Google it or maybe some one can file you in better on it. I'm at work and don't have access to a computer to give you a 100% detail on how to do it. Like I said just Google it that's how I found out how to make it work.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Yep I had the adb drivers installed, but not the fastboot drivers. I found them here: http://forum.xda-developers.com/showthread.php?t=1582554. CWM recovery installed and works fine.
Thanks

I am unsure how to install launchers read below

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

Question Pixel 6 pro drivers

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!