Database Info

ADB USB Driver

the USB driver for windows is available at:
http://dl.google.com/android/android_usb_windows.zip
It seems to work... I will update this thread with what I find.

Thanks for posting the driver!
I've tried a few things with adb, and so far I can't get an install to work over usb. I tried the following command.
C:\...\android-sdk-windows-1.0_r1\tools>adb install OperaMini.apk
579 KB/s (0 bytes in 278155.000s)
pkg: /data/local/tmp/OperaMini.apk
Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED]
Click to expand...
Click to collapse
http://www.android-freeware.org/tutorial/how-to-install-apk-files-on-android-device-emulator Had some basic info about the emulator, not sure what would be different for the G1.
The "adb shell" option allows you to access a shell on the phone over USB, which is really great but it appears you don't have root privileges. Any ideas on how to obtain root priveleges? Also, is there a command to install from the android shell? When i cd to /sbin i get access denied. I'm trying to figure out some kind of way to invoke an install either from the device or over USB.

I have the same problem... working on it now...

I don't know about the USB installs, but it seems to be something with the APK as well. I also have the OperaMini.apk and it does nothing. I downloaded the iTunes remote via the G1 and it installed just fine without getting a PC involved.

It looks like you have to put the phone into a "Debug on USB" mode to use ADB. It's working for me now.
http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware

So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on

Thank you dagentooboy!

Can someone explain this for this not so savvy person?

chrimage said:
So you were able to install the opera mini apk through adb with no trouble? I got the error listed above and did have debug mode on
Click to expand...
Click to collapse
I think that is caused by an issue with the the AndroidManifest.xml file within the APK having to do with going from "beta" to "live" Android. The same reason most of the apps were pulled from the store. I don't believe it takes a major change to make it compatible, but it's fully compiled so, unless you have a decompiler, I think we may be out of luck on that particular one. I have installed other apk's successfully using the same method.

Mikey1022 said:
Can someone explain this for this not so savvy person?
Click to expand...
Click to collapse
ADB is the Android Debug Bridge that comes as a part of the SKD. I don't think it was really intended as an end user tool. It has to be called from a command line. I know people have built basic UI's for it for file manipulation when the SDK was the only thing out there. If a better solution isn't found shortly I think we'll see one be made, or else I'll make one myself. In the end it seem to make a big difference of what you're trying to install some things work and some don't, there are some differences between the beta SDK and the G1.

For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?

Valicore said:
For any developers out there, you can also access the ADB/DDMS feature through the Eclipse IDE, it provides a somewhat simpler graphic interface and is a really easy way to get screenshots. Has anyone tried just typing su through the ADB command prompt to see if it will switch you to # ?
Click to expand...
Click to collapse
the su command and sudo su returns "no permission" or "access denied" or something like that. That is also the same message i get when typing arbitrary commands that shouldn't be anything. And like i said earlier, /sbin along with many other directories are inaccessible. Hopefully someone will find a way to access the root account on the G1 pretty soon.

yes... must... have.... root...
Also a normal shell would be helpful esp when looking thru /proc/ for information.

Please help (ahhhhhh)
Okay So I am pulling my hair out here... I just booted android on my Vogue for the first time, everything works great, voice calls and sms.. But I can get a Inet connection but I am using Cricket not sprint so I added the username and password lines in default.txt and can connect, but Cricket uses a proxy for all http connections. So I found this article http://fggarcia.blogspot.com/2007/11/setting-up-proxy-for-android-emulator.html , which basicly says to use the adp app that comes in the sdk to add some lines to make the proxy. NOW, here is my problem... I can not for the life of me get my come (in windows or linux) to see my vogue while its in android..
In windows it does not appear ANYWHERE in the device manager... So I cannot install the driver, and in Linux it doesnt make a blip in dmesg..... USB debugging is marked and so is use adb....
It does charge when plugged in to the comp running linux.....
Can anyone please help me... And thanks to DZO and everyone else for there hard work on this project..

check too make sure your Android isnt listed under usb mass storage devices in device manager.

Ya USB isn't possible on Vogue yet, I just extracted data.img and added the proxy that way, but it still doesn't work. My Problem is I need all connection to use the proxy wap.mycricket.com:8080. I am not trying to be cheap or anything like the tzones thing for tmobile. Its just the only data plan cricket have use this proxy. So any Ideas would be greatly appreciated.

my computer already had a driver installed and when i try to update it with this one it says there is no better match for my hardware
anyone got a solution for this

Im really sorry to bump this old thread up but i need the r3 drivers and i dont know why they are nowhere to be found on the official page... i think its a region lock thing...

adb driver for linux cli

Anyone know what driver I need to mess with to get the 'adb' tool to connect to device (sprint mogul) via linux PC?

Setting up udev rules
kkruse said:
Anyone know what driver I need to mess with to get the 'adb' tool to connect to device (sprint mogul) via linux PC?
Click to expand...
Click to collapse
Check out http://developer.android.com/guide/developing/device.html. I am not sure about the Sprint Mogul though? Try lsusb and get the Vendor code ie. 0bb4.

boulderjams said:
Check out http://developer.android.com/guide/developing/device.html. I am not sure about the Sprint Mogul though? Try lsusb and get the Vendor code ie. 0bb4.
Click to expand...
Click to collapse
Since the Mogul is an HTC device it should be 0bb4.
Manufacturer-USB Vendor ID
Acer-0502
HTC-0bb4
Huawei-12d1
LG-1004
Motorola-22b8
Samsung-04e8
Sony Ericsson-0fce

boulderjams said:
Check out http://developer.android.com/guide/developing/device.html. I am not sure about the Sprint Mogul though? Try lsusb and get the Vendor code ie. 0bb4.
Click to expand...
Click to collapse
yea it is the issue really was something in centos and the kernel this time. I upgraded it to fedora core and it worked with the same adb bin.

kkruse said:
yea it is the issue really was something in centos and the kernel this time. I upgraded it to fedora core and it worked with the same adb bin.
Click to expand...
Click to collapse
I wrote up a post this afternoon on getting the SDK fully working on my blog...
I am using Ubuntu, but should be easy to translate to other distro's...
HERE
Hope this helps others out.

LG EVE adb access on ubuntu
I'm currently using an LG Eve(GW620R) and have had no luck getting adb to see the device on Ubuntu Karmic Koala. I used to have an HTC Magic, and adb would recognize the Magic without any issues whatsoever, but I cannot seem to get the Eve to play nicely. Adb is properly set up, since I had full access to my Magic when I had it. I've edited my rules file to add in support for LG devices, but it still won't pick it up. I've tried changing the rules file to 51-android.rules, and I've also tried 70-android.rules, but neither one seems to want to work. I've rebooted my system, reloaded udev, changed the rules file to read every kind of device, regardless of manufacturer, but I still have had zero luck. I thought that linux was supposed to require next to no effort to set up adb, but I've been trying for 3 days now, and I've still gotten no farther then when I started. If I run lsusb while the phone is plugged in normally, it sees it, but adb does not, if I put the phone into emergency mode or fastboot, it shows a different device ID, but even adding in those IDs to my rules file, I still get nowhere. Any suggestions?

still not working
alright, so I've tried editing the rules files in all kinds of ways, I've tried running adb as root, I've got debugging enabled on my phone, I've followed every instruction I've found to the t, and I still have had no luck getting this phone to connect to adb. Can anyone give me any advice, or at least point me in the right direction? I've read a bunch of stuff about different kernels having issues with different phones, but I can't see my kernel being the issue if I could get my HTC Magic to work just fine. I'm hitting brick walls at every turn, and I've had no luck getting it any further than two weeks ago now. I'm running 9.10, Karmic Koala, I've got the newest sdk (which I think might be the issue since the Eve runs 1.5, but doesn't the newest sdk include all the old drivers as well?), and I've tried changing the rules file to be a higher number then any other rules file in my /etc/udev. Any advice or information that anyone could provide would be incredibly helpful. I really want to get rid of all this Rogers crapware that I'm stuck with. I'm open to pretty well anything anyone can suggest, and I'm more than willing to provide any further information that anyone might want to try and help me work this out. Thanks in advance

[Q] Help! Cannot get adb to connect to G1

1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks

Shame you didn't spend some of that two days reading the site rules and the fact that not only is there Q&A section but also try posting in the ADB threads that are littered around these forums.
Catch me on irc, link in sig and I'll see what can be done.

I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.

dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.

dalek1999 said:
I have read the Q&A and plenty of guides on how to setup adb including those on here. My problem seems a bit dfifferent from most others in that i have tried all the usual suggestions and they have not worked - Why I else would I bother posting detailed info here?
If you some links to threads which address problem please post them.
Click to expand...
Click to collapse
So what does helping you get adb setup help android G1 Developmet?
Sent from my HTC Dream using XDA App

lolmensch said:
he offered help via irc, so you should think about accepting it.
anyway he ment that this has (almost) NOTHING to do with development and should have been posted in Q&A.
concerning your problem: i have no idea try if you can connect to fastboot.
Click to expand...
Click to collapse
fastboot uses fastboot.exe, not adb.exe. Adb works while in recovery or while booted.

[Q] USB WWAN - How To On Wifi Xoom?

Hello, I Know there are correct wifi usb dongles drivers in Tiamat Kernels, i have tried everything possible to get the Mobile Settings option in the Wireless setting of android with no luck, Can anybody point me to the correct procedures on how to do it? btw i have tried the methods of doing that on Acer and Asus and it didn't work, i had to flash new kernels to boot again in some cases. Thanks

Why those drivers are present but nobody want to write dialer script and instruction?

Launchpad kernel for Xoom!
Alright, Forget about Tiamat kernel, i have Team Tiamat Moray Rom on my Wifi only Xoom with the launchpad kernel from this post :
http://www.xoomforums.com/forum/lau...nel-launchpad-1-2-2-new-6-11-11-3-1-only.html
you will find in the addons (WWAN USB Addon) which is used on the launchpad to show the Mobile Menu and enable tethering as the kernel should have everything required, so why when i use it on the Xoom it doesn't work? BTW i have also disabled the Zero-CD option on the USB stick to make sure it reads as a modem when connected to usb port, i made sure that my 3g stick is compatible with the operation.
Its really interesting when i see 153 views and only one reply

You can try this http://forum.xda-developers.com/showthread.php?t=1118639
And I will try with CDMA modem I found one non-english article.
But just yesterday I got trouble with OTG connections, all devices are with error:
usb 2-1: new low speed USB device using tegra-ehci and address 6
usb 2-1: device not accepting address 6, error -71
hub 2-1: unable to enumerate device on port 1
It was working last night. Wtf? Do you know how to fix this? I tried to restart tablet with no luck, otg cable not working anymore.
Update 1: Nevermind, cable was broken. Fixed.
Update 2: I tried that method on link I gave you - zore result, reflashed.
P.S: Just tried your launchpad kernel - too bad that 3.1 only. I'm using Rogue now. By the way usb_wwan can be installed everywhere.

I found also this universal installer for Huawei modems attached below.
Dunno how to "dance" with this. After installing just nothing happend or I doing wrong.

thanks for you effort, OTG cables are horrible, most of the time when you get failures its caused by cables or adapters anyway,
i downloaded the attached archive and pushed all modules to my Xoom with MORAY Rom and Odachi Kernel, rebooted and nothing happened too no Mobile Settings menu, will keep trying and keep you posted

Actually I'm not sure if there should appear some menu. After this you have to see in dmesg you modem to be recognized like GSM converter but I don't. So it looks like option.ko isn't loaded. Maybe this file has to be in defferent place instead of /system/lib on Xoom? I also tried to put it in /system/lib/modules/ , also nothing happend after.
Maybe it works on older versions of ROMs? I'm using 3.2.2 stock rooted with rogue kernel + usb_wwan

Maybe, i have tried it with many roms, even the 3.1 but no luck, i think Team Tiamat would be the right ppl who would clarify everything to us, i have tried setting the kernel to launch all the modules on boot but nothing happened,we need somebody experienced in those things to help us out

Hmm... as you see there is nobody who want to help with this. Because they have 3G models or expencive portable hotspots and nobody need this.
Anyway. Did you try to put option.ko and usb_wwan.ko in system/library/modules folder and right after that set up "modules on boot"? Restart tablet, connect modem and see in dmesg. I don't have this option in my rom, so try to do that.

:s
I've tried placing the modules and loading them on boot, but it didn't work too, its not about money, actually i have 3G portable wifi router and my other android devices have the built-in wifi hotspot ,but its about doing the thing...its about the concept, why it's not working while we have everything in place, thats the weird thing, i think we will have to wait until somebody feels sorry for us then decide to help us! :s

Problem definitely in /system/build.prop it should be edited somehow, according to manual for A500 tablet.

Neolo said:
I found also this universal installer for Huawei modems attached below.
Dunno how to "dance" with this. After installing just nothing happend or I doing wrong.
Click to expand...
Click to collapse
hi, where to put this module pack? i mean how to install?

How to connect manually using Huawei 3G dongle:
You need:
- rooted xoom with Tiamat kernel (or any other which has usb_wwan.ko and option.ko attached)
- 3g dongle
1. Backup files from /etc/ppp in case when this solution don't work
2. Download attached zip and extract to /etc/ppp
3. edit /etc/ppp/gprs-connect-chat in line
Code:
'' AT+CGDCONT=1,"IP","internet"
replace 'internet' with APN name for your network
4. Now run terminal (Terminal Emulator) and type
Code:
su
stop ril-daemon
insmod /system/lib/modules/usb_wwan.ko
insmod /system/lib/modules/option.ko
pppd call gprs
Now you should have working connection (Xoom doesn't show this, but if you run browser it should work).
For me it works on Verizon Xoom with Huawei e1750, but i'm living in area where only edge is avaliable, so this is very slow connection - i need to check connection speed in other location this weekend.
For Xoom Wifi owners: this should also work for you, but with small change - after inserting modules you should check on dmesg which port(s) is using your dongle and change port number in first line of /etc/ppp/peers/gprs . It's probably /dev/ttyUSB0 but you must check.

Porzeczek said:
How to connect manually using Huawei 3G dongle:
You need:
- rooted xoom with Tiamat kernel (or any other which has usb_wwan.ko and option.ko attached)
- 3g dongle
1. Backup files from /etc/ppp in case when this solution don't work
2. Download attached zip and extract to /etc/ppp
3. edit /etc/ppp/gprs-connect-chat in line
Code:
'' AT+CGDCONT=1,"IP","internet"
replace 'internet' with APN name for your network
4. Now run terminal (Terminal Emulator) and type
Code:
su
stop ril-daemon
insmod /system/lib/modules/usb_wwan.ko
insmod /system/lib/modules/option.ko
pppd call gprs
Now you should have working connection (Xoom doesn't show this, but if you run browser it should work).
For me it works on Verizon Xoom with Huawei e1750, but i'm living in area where only edge is avaliable, so this is very slow connection - i need to check connection speed in other location this weekend.
For Xoom Wifi owners: this should also work for you, but with small change - after inserting modules you should check on dmesg which port(s) is using your dongle and change port number in first line of /etc/ppp/peers/gprs . It's probably /dev/ttyUSB0 but you must check.
Click to expand...
Click to collapse
bro,
how can we connect any other company's usb modem? it is same as huawei modem or new driver files to be downloaded?

raihankabir_1 said:
bro,
how can we connect any other company's usb modem? it is same as huawei modem or new driver files to be downloaded?
Click to expand...
Click to collapse
What modem you have?

Porzeczek said:
What modem you have?
Click to expand...
Click to collapse
i was successful with huawei 3g modem according to the tutorial. i have an wimax usb modem and i didnt find any tutorial related to wimax usb modem on xoom

raihankabir_1 said:
i was successful with huawei 3g modem according to the tutorial. i have an wimax usb modem and i didnt find any tutorial related to wimax usb modem on xoom
Click to expand...
Click to collapse
Ask google for linux support for this wimax modem. If it works on linux it also should work in android. And most of linux tutorials are saying which driver is needed.

I also have different modem need to use, because gprs is slow and expencive.
I have Cmotech U300 (Dual mode - WiMax + CDMA Rev.A) branded for Sprint. Have no idea where to get a driver for xoom.
Looks like my modem is working under Linux, http://jebus.nu/tech-corner/sprint-u300 Dut generally I have no idea how to make it for Xoom.

My Huawei is recognized well. I set APN name, but what about APN username and password. Where are setted?

Are there any updated ppp files for the xoom on jelly bean as it does not seem to work with my one....... Also try something called "ppp widget" which seems to be easier to do but still its not worked for me on my xoom...... HELP

Question Can't connect Pixel 7 Pro to PC (Windows 11) [SOLVED]

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?