Database Info

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"

[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire

The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk

Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S

USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.

It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S

I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.

maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.

No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance

dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...

dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance

Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help

jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.

windows 8 have a issue with ville fastboot... please make you sure you have a fix

zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic

..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...

Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!

Thank you very much bro. HTC One V good working.

Fastboot will not detect my device while rooting

I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.

Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.

under win10 environment，‘’fastboot devices‘’ command no response

enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks

hahaha1659 said:
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
Click to expand...
Click to collapse
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk

Droidriven said:
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.

hahaha1659 said:
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
Click to expand...
Click to collapse
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.

hahaha1659 said:
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
Click to expand...
Click to collapse
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.

hahaha1659 said:
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
Click to expand...
Click to collapse
It was created by a member of this forum, you should be able to find a safe version here somewhere.
Sent from my LGL84VL using Tapatalk

How can I wipe phone with nonfunctioning screen?

The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.

has it previously been paired with your computer via ADB ?

3mel said:
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb

nogods said:
yes - it shows up as a device with adb
Click to expand...
Click to collapse
hope this works for ya
Factory reset Android using ADB
I am trying to factory data reset my Oppo Neo 7 (Android 5.1) using ADB shell. Any way I can try and link to ADB shell?
android.stackexchange.com

nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse
try flashing the stock rom from adb/fastboot
nogods said:
The screen on my Pixel 4a died - google is sending a box to send it back for warranty repair. However, before I send it I want to wipe all the data - it is rooted with Magisk. How do I wipe the data given I can't operate the screen - can't even turn it off.
Click to expand...
Click to collapse

A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.

blackhawk said:
A hammer does a full wipe in seconds...
This is one reason why you use a SD card as your data drive. Simply pull it, set a new Google password, done.
Click to expand...
Click to collapse
the pixel 4a doesn't have an sd card

the ADB devices shows the phone's id with "unauthorized" next to it. All ADB commands return this:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

maoriboi said:
try flashing the stock rom from adb/fastboot
Click to expand...
Click to collapse
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
\

Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w

nogods said:
the pixel 4a doesn't have an sd card
Click to expand...
Click to collapse
Yes I know. Keep that in mind next time around as it makes life much easier.
All joking aside, sorry to hear about your issues.

AlexKarimov said:
Just to be clear: can you enter bootloader? If you're in ADB, type: adb reboot bootloader. If not, can you turn the phone off and then hold volume down while plugging the USB cable in?
Then commands will be fastboot erase userdata or fastboot -w
Click to expand...
Click to collapse
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set

nogods said:
Nope - adb devices shows id number and "unauthorized". Any other adb commands return the
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Click to expand...
Click to collapse
has it previously been paired with your computer via ADB ?
Click to expand...
Click to collapse
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...

AlexKarimov said:
yes - it shows up as a device with adb
So it looks like you never authorized it between the phone and the computer. When you enable USB debugging and then plug in a USB cable, a window will pop up with a check box and ask if you want to authorize/trust this device and you mark the box and click yes. I'm guessing you didn't do that? But what about turning it off and starting in fastboot mode. Forget ADB for the time being and start in fastboot mode. If that doesn't work, make sure you have the right drivers and try again. Otherwise, that's all I've got. I'm sorry...
Click to expand...
Click to collapse
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.

nogods said:
this phone was rooted on this computer using adb and fastboot. How do I start it in fastboot? The screen is off completely - I can hear the phone because I set a shortcut key for Talkback so I know it is turning on, telling me there is no sim, and then reading my lock screen with my name, phone numbers, and email.
Click to expand...
Click to collapse

Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"

nogods said:
Thank you for that info. So here is what happens.
1. I shut it down by pressing both power and down volume buttons while attaching it to a charger.
2. I start it in fastboot mode by holding down the down volume button while attaching it to the computer.
3. The computer notification says "preparing pixel 4a" and I heard the classic connected sound.
4. If I try "adb devices" I get back an empty list of devices (unlike when I just connected it without holding down the down volume button, so I think that means it is NOT in adb mode, right?)
5. But if I try "fastboot device" or any other fastboot command it merely says "waiting for any device"
Click to expand...
Click to collapse
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.

AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.

nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
nogods said:
Thank you, thank you, thank you. You were correct about the driver issue. I downloaded the official google driver, and now it shows as a device in fastboot. Thanks again.
Click to expand...
Click to collapse
O
AlexKarimov said:
That sounds like a driver issue. It's a different driver for each state the phone is in. If I remember right, the Google USB driver handles the ADB.
Here's the other one for fastboot
[TOOL][WINDOWS] 15 Seconds ADB Installer Reborn V2.0 - ADB/Fastboot, and Drivers.
15 Seconds ADB Installer Reborn V2.0 Introduction: We can all agree with the fact that the Android Debug Bridge (ADB) is one of the most important tools when it comes to developing for android, uninstalling bloatware, flashing recoveries...
forum.xda-developers.com
Once connected in fastboot mode, you'll have to assign the driver manually. Don't let the computer do it, it will almost always say you have the best one already. In device manager, right-click the phone(unknown android device, i think) and update driver. Then select 'browse my computer for drivers' and then 'let me pick from available drivers on my computer'.
Click to expand...
Click to collapse
yup - looks like it worked:
Erasing 'userdata' OKAY [ 15.171s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.158s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 15.797s
What nows "not automatically formating" mean?

nogods said:
O
yup - looks like it worked:
Click to expand...
Click to collapse
Awesome, thanks for the updates. I'm glad you got it going
nogods said:
What nows "not automatically formating" mean?
Click to expand...
Click to collapse
I'm not sure about this, I've never encountered that as far as I know. Did it say "can't determine partition type" after that?

Question PixelFlasher - what the heck am I doing wrong???

With some help from folks here, I have a working copy of PixelFlasher (V4.6.1.0 - the v4.8.1.0 was stopped by my AV product) and the proper Factory Image for my phone. Following the instruction here https://forum.xda-developers.com/t/...dating-rooting-managing-pixel-phones.4415453/, I got to Step 9 without any issues.
However, when I clicked the button 'Flash Pixel Phone', PixelFlasher indicated that it was rebooting my phone to bootloader mode - the phone was rebooted and the phone's display appeared appropriate. However, PixelFlasher then reported:
Waiting 10 seconds ...
2023-03-22 11:49:43 No Device is selected!
2023-03-22 11:49:43 ERROR: Unable to detect the device.
What the heck am I doing wrong???

groston said:
With some help from folks here, I have a working copy of PixelFlasher (V4.6.1.0 - the v4.8.1.0 was stopped by my AV product) and the proper Factory Image for my phone. Following the instruction here https://forum.xda-developers.com/t/...dating-rooting-managing-pixel-phones.4415453/, I got to Step 9 without any issues.
However, when I clicked the button 'Flash Pixel Phone', PixelFlasher indicated that it was rebooting my phone to bootloader mode - the phone was rebooted and the phone's display appeared appropriate. However, PixelFlasher then reported:
Waiting 10 seconds ...
2023-03-22 11:49:43 No Device is selected!
2023-03-22 11:49:43 ERROR: Unable to detect the device.
What the heck am I doing wrong???
Click to expand...
Click to collapse
May be best to head over the the Pixel Flasher thread and ask there. You may need to submit a support.zip so badabing can look at it.

You may need to install Google's official USB driver. Also, you might need to enable USB debugging on your phone depending on what you are using PixelFlasher for.
But, posting on the PixelFlasher thread that was mentioned on the previous comment would be your best bet =).

you're missing the Google USB driver for pixel
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
This
Install and check device manager, it should now say pixel 7 pro or something rather than a warning

The driver is already insatlled. I just looked at it in DevMgmt - it was the latest version, which I downloaded yesterday, but says V11.0.0.0. When I connect my phone, 'Android Composite ADB interface' appears, but I do not see the phone itself.

groston said:
The driver is already insatlled. I just looked at it in DevMgmt - it was the latest version, which I downloaded yesterday, but says V11.0.0.0. When I connect my phone, 'Android Composite ADB interface' appears, but I do not see the phone itself.
Click to expand...
Click to collapse
Reboot to bootloader and in cmd type " fastboot devices" if the driver is configured correctly it will show a list of attached devices.

There have been issues with Platform tools 34.0, if thats what you are using try using v33.0.3 for Windows or for Mac

if you could get into bootloader/fastboot mode (since we know the driver for adb is working, open a cmd, direct it to the platform-tools folder, and input the command adb reboot bootloader) you could run the command "fastboot devices" to see if there is a connection, and "fastboot --version" to see what version you are on.
In any case, when flashing, the driver should be identified as ""Android Bootloader Interface", vs. "Android Composite ADB interface" which is what's needed when you're loaded in the OS and/or running adb commands...

K1nsey6 said:
There have been issues with Platform tools 34.0, if thats what you are using try using v33.0.3 for Windows or for Mac
Click to expand...
Click to collapse
Thank you very much kind sir! The 33.0.3 release did the trick. Now I wonder why Google pulled all the March Factory images? Hmmmm...

Badger50 said:
Thank you very much kind sir! The 33.0.3 release did the trick. Now I wonder why Google pulled all the March Factory images? Hmmmm...
Click to expand...
Click to collapse
They didn't actually pull them. If you look at the English language download page they're all still there, but it appears on some of the non-English download pages they're not there. Thinks it's a problem with those pages.

Badger50 said:
Thank you very much kind sir! The 33.0.3 release did the trick. Now I wonder why Google pulled all the March Factory images? Hmmmm...
Click to expand...
Click to collapse
It's there if the language is set to English (the r34 issues and not finding the factory images in other languages are very well notorious at this point (prevalent in other Pixel 7 threads)....
EDIT: got ninja'd by @Lughnasadh

Lughnasadh said:
They didn't actually pull them. If you look at the English language download page they're all still there, but it appears on some of the non-English download pages they're not there. Thinks it's a problem with those pages.
Click to expand...
Click to collapse
simplepinoi177 said:
It's there if the language is set to English (the r34 issues and not finding the factory images in other languages are very well notorious at this point (prevalent in other Pixel 7 threads)....
EDIT: got ninja'd by @Lughnasadh
Click to expand...
Click to collapse
Well I'll be damned! The old dog learned something new today. Many thanks gents!