Related
I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?
Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim
Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?
More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!
Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.
Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.
I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.
One thing I forgot. Do not unplug your device between uninstall and hardware scanning.
AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!
haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!
bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.
I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid
I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!
Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!
Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work
matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!
thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!
I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App
lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box
How to flash recovery.img via standalone adb?
and how to fix error in adb : `error: device not found`?
Windows 7 x64 , Motorola xoom 3g (Verizon)
Follow this thread for flashing recovery via ADB.
but what to do with error??
nothing changes
TechnoManiac97 said:
but what to do with error??
nothing changes
Click to expand...
Click to collapse
That error indicates that either you are missing the proper drivers from the Motodev site or usb debugging has been unchecked on your Xoom in settings. There may be other reasons but those seem to be most common.
emm..
Ive got everything
I forgot to write on the picture that usb debugging is on
so now you can see the picture how it looks like
using this drivers http://www.motorola.com/Support/US-EN/Support-Homepage/Software_and_Drivers/USB-and-PC-Charging-Drivers
in aplications|development I`ve got:
USB Debugging on
Stay Awake Off
Allow mock locations on
first off read....... and then follow the steps here
http://forum.xda-developers.com/showthread.php?t=1209341
and try to keep all your questions in one thread = makes your (and our)life easier and keeps unnecessary thread clutter down
Have you restarted your computer after you installed the Moto Drivers?? Sounds stupid, but I've had weird things like that happen before with HTC drivers... Worth a shot.
Dear cqms13,I don't understand where I have to find answer to my question(In that link)
That link doesn't make any sense(to my problem)
Maybe you can copy-paste Smth interesting and usefull?
Yes,Ive reboted my PC before I tryed to do Smth with adb
Sent from my Xoom using XDA App
I found that when my device is on I can do everythinf in adb, but when it is in fastboot I`ve got that error
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
The mystery: I cannot establish a USB connection between my Pixel 7 Pro (Android 13) and PC (Windows 11). When I try, the PC makes that characteristic "connected device" sound, but Windows Explorer doesn't discover the Pixel, nothing shows up anywhere in the Windows Device Manager, and the ADB command
.\fastboot device
returns nothing. The Pixel is similarly not discoverable as a bluetooth device to the PC, although it IS to other devices (like my earbuds).
This is the first task I have attempted since I performed a factory reset (and walked through the automated Pixel setup process) last night. I have spent the last three and a half hours reading Android forums, testing USB port-cable permutations, and installing and uninstalling drivers. There is no obvious solution to this problem within the first ten pages of Google search results. I would be beyond grateful for any possible insight, but please, take a moment to review what I have attempted already before you expend any effort helping me troubleshoot.
The Pixel CAN connect to an older laptop running Windows 10, appearing both in the Windows Device Manager (which says my drivers are up to date) and in File Explorer (where I can access the internal memory). But ADB similarly returns nothing on the ADB
.\fastboot devices
command. Also, my old phone (a Samsung Galaxy S20 FE 5G running Android 13) connects fine--both by USB and by bluetooth--to all three devices.
So the PC (Windows 11) connects to the Galaxy and the laptop (Windows 10) connects to the Pixel (kinda), which fairly well eliminates the possibility of an issue related to my hardware or USB cables. But the PC (Windows 11) won't connect to the Pixel--not anymore. Everything worked just fine when I unlocked the Pixel's bootloader a few weeks ago.
What I need now is to recover the functionality of the USB and bluetooth connectivities between the Pixel and the PC running Windows 11, especially for file transfers. For several reasons, WiFi reliant solutions are untenable for my situation. I also need to re-lock the bootloader by any method (not necessarily with the PC). As mentioned above, ADB has not succeeded in finding the device on either platform.
Finally, in case it's relevant: when I open the Pixel's USB Preferences menu, I cannot switch from "USB controlled by...This device" to "USB controlled by...Connected device"--in both cases, the Pixel returns a "couldn't switch" dialogue. And yes, I have of course enabled USB debugging.
If you took the time to comb through all those particulars, Thank you. I'm getting desperate for some thoughtful expertise, and while I'm open to retrying anything for the fifth or sixth time, (maybe I somehow missed the magic driver package), it is a special kind of tribulation to review the same tired list of perfunctory solutions to a different problem. I promise, the solution I need isn't one of the usual suspects.
I spent $800 on this device. That's a lot of money for me. It feels absurd and unfair that such a basic functionality--one that far more affordable devices have been delivering reliability for decades--should be missing from the Pixel 7 Pro. Please please please help me!
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
jaseman said:
Ummm, USB debugging is not only what is needed here. While you are in developer settings scroll down to "Default USB configuration" and tap on it directly. Then you will see a number of choices. I think the top one titled "File transfer / Android Auto" is the one you need. Or maybe try PTP???
Let us know if this helps.
Click to expand...
Click to collapse
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
GodieDan said:
Thanks for your speedy reply! I had File transfer / android Auto selected, but then switching to P2P allowed me to review the internal storage! I can't believe it. However I still need to figure a way to get ADB to find the device so I can lock the bootloader, and i still can't figure out how to solve the Bluetooth connectivity..
Click to expand...
Click to collapse
Have you tried putting in Fastboot mode and then connect to computer?
schmeggy929 said:
Have you tried putting in Fastboot mode and then connect to computer?
Click to expand...
Click to collapse
Putting what in fastboot mode?
GodieDan said:
Putting what in fastboot mode?
Click to expand...
Click to collapse
Your phone in Fastboot Mode aka bootloader Mode.
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
yurishouse said:
Uninstall any previous android USB driver you have installed, and install the official Google USB driver instead. You need to install it two times probably. First in Android mode and second in bootloader mode, after all that it should show up correctly. If not, check your cable and PC USB port
If possible, give a lsusb output on your PC, see if the phone's there or not
Click to expand...
Click to collapse
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Yeah, you probably just need to install the official USB driver from Google. That was a problem that numerous people had when the Pixel 7 series first released.
GodieDan said:
I'm sorry, i don't understand what you mean when you say install it in android mode or bootloader mode?
Click to expand...
Click to collapse
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
schmeggy929 said:
So you trying to unlock the Bootloader and you don't even know what Bootloader mode or Fastboot is? Maybe you should do some reading first. What do you mean by absurd that the Pixel doesn't have basic functionality? You said you have no problem with a Windows 10 computer, Windows 11 is the problem not the phone. Again I would do some reading on XDA, especially the guides on unlocking and rooting, because you don't seem to have a clue on what you are doing.
Click to expand...
Click to collapse
We'll I'm certainly not above learning new vocabulary but but in this case I don't think the issue is having read too little. Do you mean recovery mode? So far there is no custom recovery available for the Pixel 7 Pro, but yes I did try with the phone in the stock recovery
I have read every relevant article on XDA and three other forums and nothing has helped so far. I promise you I would not have posted if I could find the solution elsewhere.
Also the phone doesn't work fine on the windows 10 system. I was able to view my files but I couldn't read, write or execute ADB commands. I do consider USB file transfer to be a basic functionality, and windows 11 is backwards compatible with every storage device since punch cards.
Anyways I'm no pro, but I have had success with rooted devices in the past. For my benefit it would be helpful to be assiduous with language choice.
.
H
bobby janow said:
If you look at his second post (#3 of this thread) he says he wants to "lock" his bootloader not unlock it. Unless of course it was a typo. Maybe we should point him to the thread, Help I've bricked my device now what do I do".
Click to expand...
Click to collapse
I there, yes, my objectitve was to lock the bootloader, not unlock it. However I got that part figured out at least, by getting the phone replaced (i had fortunately splurged on the extra protection). But also I never bricked my device, and as best I can tell, the issue at hand isn't related to the rooting, or everything would be working again with the new phone. I wanted to re-lock the bootloader because everything was just getting to be so unstable. This was never a problem on my Nexus 6p, but that was two devices ago. Also, is it just me, or are there generally fewer benefits to rooting than there were in the teenies?
Hi there
simplepinoi177 said:
yeah...the "absurdity" doesn't fall on the Google Pixel in this case, but with Microsoft Windows...
So, the first thing you need to do is see what is the device being identified as in Device Manager -- it easily could be "Unknown Device" or even identified as something totally different & wrong (Samsung android device, MTP device, etc.). Regardless, it NEEDS to be identified as Android Composite ADB Interface (and Android Bootloader Interface when in Bootloader Mode). When this was happening to many members in the main rooting thread on this forum, it was determined that you can't simply just "Uninstall" it, but you also need to "delete device driver" as well (if option is available)! Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
GodieDan said:
Hi there
Howdy, thanks for this. I just wrote a long reply but I can't seem to find it now, so I'll go ahead and give you the upshot again.
In my device manager, i have located a driver called "Android ADB Interface" under the grouping of "LeMobile Android Device" (by itself), and sure enough, it has a yellow-triangle warning icon. Before I take any action, i want to be clear -- your advice is that I uninstall the driver AND delete it manually? The context menu gives me the option to update the driver (when I search automatically, windows tells me the best drivers are already installed), disable device and uninstall device. Do you suggest I choose uninstall and then download the correct driver? If so, please would you provide me with the right link? I know from recent experience that there are a lot of drivers out there which look pretty good, and obviously none of them have worked doe me
Click to expand...
Click to collapse
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
simplepinoi177 said:
...Most users are able to simply install the driver and sometimes just have to point it to the Google USB Windows Driver folder (that I hope you followed the suggestions of the other members in this thread and got it proper from the source from Google's developer's website), but I suggest going beyond it and pointing the device driver (Update, Browse My computer for drivers, Let me pick from a list, have disk, and choose the .inf file) to the exact .inf file.
Also, since it seems you aren't too experienced in all this, I really do suggest you use the official Google Android Flash Tool to re-lock your bootloader! There are countless members from the past 7 years that have HARD BRICKED their device because they have done things wrong -- the Android Flash Tool will do everything automatedly in the correct fashion as to not hard brick your device when re-locking the bootloader.
But you absolutely need to get your usb drivers correct in order for the tool to work...
Click to expand...
Click to collapse
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
simplepinoi177 said:
It might help to show what it states in the "Device status" in Properties.
But, regardless of what it says, YES uninstall the driver AND delete it manually. Windows automatically searching is usually wrong more often than not in my experience -- but especially in the case of special hardware connected to the computer.
Again, when reconnecting the device and after it installs the (most likely wrong) driver, please heed what I stated before:
You are correct that there are multiple sources for the drivers and adb/fastboot -- ultimately the best place to get them is direct from Google's android developers website. For Windows USB drivers; here is the link from this website: https://developer.android.com/studio/run/win-usb
Just extract the .zip to a folder, and refer to that folder when doing the aforementioned steps I laid out (in orange)...
hope this helps...!
Click to expand...
Click to collapse
Wow, thank you for the speedy reply!
1. Having splurged on the protection plan, yesterday i went to best buy and replaced my device, and I'm no longer interested in messing with the bootloader. So where ADB is concerned, I don't need it. What i DO need is the functionality of making file transfers between my PC and my phone. Do you still suggest I look for the ADB driver on the developer website, or is there something more basic (and hopefully reliable)?
2. The device status reads:
"
The device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
"
I spent a few minutes googling around about those errors, no luck yet.
3. It would be straightforward to uninstall (or disable) the device, but when I do, I worry it will be difficult to locate where the drivers are hiding (to delete manually). Under the "Driver" tab I clicked "Driver Details" and found the directories for three files, winusb.sys and two .dll files. Are these the culprits? Might there be others anywhere?