Develop Bugs

[Q] Nexus 7 (flo) not connecting to PC????

im not sure if ive been looking in the wrong places but i cant find an answer to my problem. so i rooted my nexus 7 about a week ago and installed twrp. everything was working fine until i accidentally pressed wipe data instead of factory reset. i deleted EVERYTHING on my tablet including my operating system, the only thing left was twrp :crying: today my otg usb cable came in and i installed that unofficial cyanogenmod build and now it wont connect to my pc. i have usb debugging on and everything. i go to device manager (on my pc) and it is listed as "Nexus 7" but when i try to install the usb drivers it says that they dont work for it. how can i get the usb drivers to work again?
Note: its not my pc cause my rooted s3 works just fine with my pc.
sorry for being a noob! and thanks for the help!

I actually have the same issue where my Windows won't let me navigate my N7 as a portable device. Tried a whackload of drivers and the like to no avail. To transfer files I just end up using ES Explorer. Funny enough, ADB in recovery works just fine.

If it is the same as PA and PAC, try Settings > Storage > Press Menu > USB > Check MTP
Sent from my Nexus 7 using Tapatalk 4

BigDaddySunshine said:
im not sure if ive been looking in the wrong places but i cant find an answer to my problem. so i rooted my nexus 7 about a week ago and installed twrp. everything was working fine until i accidentally pressed wipe data instead of factory reset. i deleted EVERYTHING on my tablet including my operating system, the only thing left was twrp :crying: today my otg usb cable came in and i installed that unofficial cyanogenmod build and now it wont connect to my pc. i have usb debugging on and everything. i go to device manager (on my pc) and it is listed as "Nexus 7" but when i try to install the usb drivers it says that they dont work for it. how can i get the usb drivers to work again?
Note: its not my pc cause my rooted s3 works just fine with my pc.
sorry for being a noob! and thanks for the help!
Click to expand...
Click to collapse
Were you on stock before you wiped? Trying going back to stock and see if you can get MTP working, then start introducing the parts until you figure out what broke.
The USB IDs for the MTP device change more often than you'd expect causing recognition problems.
For example, on stock, with USB debugging enabled, it advertises one USB ID and also sends out a MTP-compatible flag. When USB debugging is disabled, a different USB ID is sent, minus the MTP-compatible flag.
I helped someone on a different ROM force the MTP device drivers to associate, but then the drivers couldn't initialize the device. This might indicate there is a problem on the ROM side.
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
verkion said:
I actually have the same issue where my Windows won't let me navigate my N7 as a portable device. Tried a whackload of drivers and the like to no avail. To transfer files I just end up using ES Explorer. Funny enough, ADB in recovery works just fine.
Click to expand...
Click to collapse
If your ADB works in recovery then you must have installed some other adb device driver, other than Google's, at some point.
If you want I can try helping you get things recognized on this thread
http://forum.xda-developers.com/showthread.php?t=2391236

swagstr said:
If it is the same as PA and PAC, try Settings > Storage > Press Menu > USB > Check MTP
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
this

Adb not recognizing device on linux

Did anyone manage to get adb recognize the g3 on Linux and if how?
I'm using ubuntu gnome 14.04, udev rules are set up (including the 1004 vendor id). The device probably shows up at dmesg, but adb doesn't recognize it, also checked if Windows (as much as i hate it) works and there adb shows the device.
Mtp is working fine, just debugging doesn't, even the pop up to trust the pc isn't showing up.
Gesendet von meinem LG-D855 mit Tapatalk
Edit: I also tired to add the line
Code:
0x1004
to the adb_usb.ini within .android, but it didn't work out.
Edit2:
I've now also tried to add the udev rules with the proper product ids, still no sucess ...

Try in PTP mode, it worked for me in OS X

anod said:
Try in PTP mode, it worked for me in OS X
Click to expand...
Click to collapse
Damn it, why haven't i thought of that, tinkered around at the system, but missed that, works now, thanks

Can't enter fastboot + unusual screen - bricked?

Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.

MaRkuS_538 said:
Hello Guys,
yesterday I flashed AICP (6.0) from transi11 with opengapps... But needed root, so I downloaded the latest SuperSU2.65.zip and flashed it, how I've always done it.
I've got a JVT-Jem-Prod04.
But now it doesn't Boot anymore (idk why). First there's the normal KF screen and Athen another one with a grey bar on the top, Wtf?View attachment 3659595
So I tried a few tools like KFFirstAide, the system.img recovery tool and another one that said it worked even though I hadn't it plugged in xD
But in the better apps it says always that he's waiting for the device.. Always. Nothing happens on the kfhd 8.9...
Twrp is not bootable and Windows says that it can't recognize this device if I turn it on/into the bootloop.
Maybe I've got the drivers set up wrong? Or what could it be?
Thanks in advance.
Click to expand...
Click to collapse
I have that same line running down mine, looks like twrp.
hope someone chimes in...

It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.

r3t3ch said:
It seems that supersu is running amok on kindles lately. Not sure what that line is but it's probably harmless. It's easier to recover from this on jem as you don't need a factory cable to enter fastboot. I explained the gist of it here and how to recover here. It's a very simple fix, but if you want an even easier root solution, AICP and RR are both CM13 based and should have a "Root access" toggle in developer options you can enable without the need to flash anything.
Click to expand...
Click to collapse
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...

You have a driver problem. If it gets listed under anything, uninstall the drivers for it from device manager. It should show up as something like "jem-pvt-prod-04" under other devices with a yellow triangle. You can then try to install its driver as adb composite interface or try using the driver from this thread. If you don't see "Android Composite ADB Interface" when you try manually installing the driver, reinstall adb/fastboot.

MaRkuS_538 said:
Thanks for your advice... But it didn't work.
So I reinstalled the drivers and tried the getvar command, stucked at waiting for device.
Then I looked into the device manager and searched for the kindle.. No direct Entry for it, not und er portable device, neither under ADB (or how the category is called).
It only got detected as USB detected device (failed at requesting a device description), Windows wanted only to charge it and to overwrite the "device" with ADB drivers or anything didn't help :/
The next strange thing is that there's for every time I connect the kindle another Entry as USB detected device comes in, wtf?
And, Windows only knows it when the normal orange/white Logo is there, but no longer if there's this strange Logo (first post)
It seems that my kindle is finally bricked (to me), or is there any way to rescue it with fastboot, or did I only take the wrong drivers?
Hope somone may help...
Click to expand...
Click to collapse
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry

sullytrny said:
I fixed mine
I will try to post a solution later today or tonight, you need the android sdk and any of the restore tools with the recovery and boot img's
And you may need a fastboot cable
storm coming so I need to get to town, sorry
Click to expand...
Click to collapse
Hey hope all went well with the storm for you, now can u do a write up on how to fix the issue please.

Yeah, hopefully. But it would be very nice to tell what you've done exactly (especially driver setup)
Gesendet von meinem Nexus 6P mit Tapatalk

Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?

MaRkuS_538 said:
Update:
Today I tried it again. I used your explanation but it didn't work at all
And now it doesn't know the kindle any longer, as no device! So there's no entry for it, never.
Can I save it or is it too late?
Click to expand...
Click to collapse
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs

It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk

monster1612 said:
It's not bricked - we just need to get ADB and fastboot working to a point at which we can carry on from.
Are you using Windows 8/8.1/10? If so, you're going to have to disable driver signature enforcement before you install the kindle drivers. Make sure you do that, and also verify you have a working ADB install.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Can you tell me how you did this? I disabled driver signature enforcement (running windows 10), but I have no clue where to go from here.
---------- Post added at 02:30 PM ---------- Previous post was at 02:20 PM ----------
MaRkuS_538 said:
It finally worked! I'm booting!
I think the solution was to disable driver signatur enforcement, then anything wasn't hard anymore.
Thank you guys for your help
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
Can you by chance explain what you did? I've got mine stuck at that screen (no recovery or anything) and can't go anywhere.

I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk

MaRkuS_538 said:
I did everything people have told me to, with some reading in these linked posts. I have followed them, step by step.
Hardest thing was actually to time the pressing of the buttons and plugging in, so if your drivers are already on point just try out, often. If not, reinstall everything regarding adb and Kindle. If you're in fastboot, most of the deal is done.
Anyway, i can't remember everything 100%, but I hope that I helped you and that everything will run fine again soon.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?

kslonkey said:
So basically what I did was flashed stock OS over lineage 14.1 and stupidly rebooted before I wiped, so stock OS got rid of my recovery and fastboot (from what I've read).
I can't get device manager to populate the device before the device becomes unrecognizable. Now I'm stuck here, I uninstalled the drivers, downloaded the SRT, and android sdk, but in the process of reinstalling, but with no fastboot on the device I'm not sure where to go. Is it true that stock ROM doesn't have fastboot?
Click to expand...
Click to collapse
YES, i can help.
you need EITHER:
KFHD_SRTv1.3.5.zip 1.13 gig from here @ X-DA
OR
Minimal ADB and Fastboot (a few megs) from here @ X-DA
launch the app, and when it says "waiting on device" plug the usb cable into the ALREADY OFF tablet.
this is the only way i could get fastboot to work (and be "installed" in windows) on my 32 gig model. i have the "red screen of death" and these 2 apps are the only ones i could get to work. i WANT to try "kindle fire first aid" but ALL the links here for that app are DEAD.

Cannot detect in fastboot mode

I was trying to flash the factory images on the Nexus 5x through fastboot. When I kept typing fastboot devices the computer would not recognize the phone so I couldn't flash the images, however; when I go to TWRP it recognizes the phone. When I type fastboot devices it keeps saying "Waiting for device"
I'm using minimal ADB, not full SDK

yesterday i having the same issue .... when i flash last stock 7.1.1 and after that i return on PixelRom But my computer won't recognize my device normally and in fastboot mod
i have try to change bootloader , radio , vendor but same issue after download direclty on my device
i have read to change cable i have try another cable but same issue i have reinstalled 15 sec adb & fastboot and drivers and i retake my cable that I usually use and wow it's work now ......... how ?? why ?? i don't know
good luck

Renaf2 said:
yesterday i having the same issue .... when i flash last stock 7.1.1 and after that i return on PixelRom But my computer won't recognize my device normally and in fastboot mod
i have try to change bootloader , radio , vendor but same issue after download direclty on my device
i have read to change cable i have try another cable but same issue i have reinstalled 15 sec adb & fastboot and drivers and i retake my cable that I usually use and wow it's work now ......... how ?? why ?? i don't know
good luck
Click to expand...
Click to collapse
I'm not sure what the issue is but I have a feeling it has to do with Nougat. I just tried doing a bunch of the standard stuff and it's not working. I plugged in my old Nexus 6, everything is working no problem fastboot and adb. I have a feeling Google made some type of changes and possibly the fastboot/adb program that I am using is not compatible with whatever change Google has apparently made as of recent.
It's not my program since it is working fine on Marshmallow for the Nexus 6........so it makes me think that it's Nougat......I updated the LG driver which I initially thought it was and it shows no errors as well.

mikeprius said:
I was trying to flash the factory images on the Nexus 5x through fastboot. When I kept typing fastboot devices the computer would not recognize the phone so I couldn't flash the images, however; when I go to TWRP it recognizes the phone. When I type fastboot devices it keeps saying "Waiting for device"
I'm using minimal ADB, not full SDK
Click to expand...
Click to collapse
What OS do you have on your PC?
Inviato dal mio Nexus 5X utilizzando Tapatalk

i don't know if it's Nougat or not it's my first time with this issue ......... Yet it's been a while since I flash Nougat version without this issue ( and perhaps i can flash 5 Roms on one Day ) (I'm a crazy flasher XD ) .....
For me i'm on Windows ssshhiiittttyyy 10 drivers signed desactivated with settings on boot

sobe00 said:
What OS do you have on your PC?
Inviato dal mio Nexus 5X utilizzando Tapatalk
Click to expand...
Click to collapse
I have windows 7.

I'm using another laptop with Windows 7 as well, but it is currently working. The only difference between the 2 is that one is almost 5 years newer (working one) than the non-working one. Still works fine with Marshmallow Nexus 6, just not with this one right now.

Are the bootloader drivers installed? Look in the device manager.

mikeprius said:
I have windows 7.
Click to expand...
Click to collapse
Maybe you need to set fastboot driver manually in Device Management . Sorry for my not good English.
Inviato dal mio Nexus 5X utilizzando Tapatalk

sobe00 said:
Maybe you need to set fastboot driver manually in Device Management . Sorry for my not good English.
Inviato dal mio Nexus 5X utilizzando Tapatalk
Click to expand...
Click to collapse
How do you do this ? I tried setting up LG Mobile drivers for the Nexus 5x. The computer was scanning and auto found the adb driver, I still can't figure out what I am missing.

mikeprius said:
How do you do this ? I tried setting up LG Mobile drivers for the Nexus 5x. The computer was scanning and auto found the adb driver, I still can't figure out what I am missing.
Click to expand...
Click to collapse
in fastboot, hook your phone up to your computer. than go to your device manager and find your device, double click on it. right click on the second one that pops up and select update driver, select browse computer, than select pick from a list of drivers and manually install the driver for fastboot mode...hope this helps.

dominoeflux said:
in fastboot, hook your phone up to your computer. than go to your device manager and find your device, double click on it. right click on the second one that pops up and select update driver, select browse computer, than select pick from a list of drivers and manually install the driver for fastboot mode...hope this helps.
Click to expand...
Click to collapse
Huge thanks for your advice. Got the phone up and running. Fastboot now running. What you described was what was needed. :highfive: :highfive:

mikeprius said:
Huge thanks for your advice. Got the phone up and running. Fastboot now running. What you described was what was needed. :highfive: :highfive:
Click to expand...
Click to collapse
Your welcome bro and anytime. This was exactly what happened to me at one point until I figured out what the problem was. Good you get the phone up and running ?

mikeprius said:
How do you do this ? I tried setting up LG Mobile drivers for the Nexus 5x. The computer was scanning and auto found the adb driver, I still can't figure out what I am missing.
Click to expand...
Click to collapse
Plug your device in fastboot mode in your PC and open Windows's Devices Manager, now you should find your phone under "other devices" as "Android phone" or "android Devices" or something like that, right-click it and select "update driver softwere", then select "Browse my computer for driver software" and select "Let me pick from a list of device drivers on my computer" , now you should see in the menu a thing as "android bootloader interface", select it and then click next. Now you should be able to use your device in fastboot mode. Sorry if I answer only now, but this weekend I was aut for work.

Impossible to install Google usb and fastboot driver for Pixel C (Windows 10)

First, bit of background: I am not an Android developer or even a computer geek in any way but I can follow precise instructions to a positive result. I have for instance had in the past the following devices and managed to root every single one of them sometimes in 10 minutes, sometimes with a lot more difficulty: B&N Nook, Samsung Galaxy SII, Nexus 5, Nexus 7, Nexus 9, Sony Xperia Z3 Compact, Chuwi Hi10 Pro.
Now, I have just purchased a Pixel C and I have been tearing my hair out for the best part of 48 hours just trying to install the Google USB driver and fastboot bootloader driver on it. I previously had my Windows 10 PC set up with working ADB and fastboot (sdk tools only, no Android Strudio). As proof, I recently rooted my Nexus 9 on it. With the Pixel C I tried:
-Nexus root toolkit and every single method of driver installation possible
-I then downloaded Android studio - didn't change a thing
-I then try to unlock the bootloader the manual way (command prompt inside of platform-tools - fail since the driver won't install.)
-I even wiped out my Windows install and reinstalled it fresh with Android Strudio
- I do get the device seen as an mtp device
-I do get adb function (I can reboot the device to bootloader)
-Yes I did enable usb debug and 'oem bootloader unlock'
-when I try to install te Google driver to the tablet as mtp device in Device Manager I get the message "the best driver is already installed" (no matter what Google usb driver I use, the one downloaded by Android Studio or the one I downloaded separately)
-I have also always disabled driver signature enforcement in Windows before trying to update the driver.
I am extremely puzzled and feeling defeated. If someone can tell me of something that passed me by, please tell me. If the Pixel C can be rooted on a Windows 10 PC, please tell me something I don't know...
Please note: I made the possibly mistake of letting the Pixel C update to 7.1.2 before doing anything.
Please Help!

This may or may not be a helpful response. I had the same problem and never, ever solved it. I read a gazillion articles and all sorts of detailed instructions about how to remove and update drivers. I tried for days and nothing ever worked. That's not to say that it can't be done, but I had to give up.
Do you have access to a Windows 7 computer? That will get you through the unlocking process and initial installation of TWRP. After that you won't need your PC for anything except transferring files so the drivers won't be a big issue.

badwiring said:
This may or may not be a helpful response. I had the same problem and never, ever solved it. I read a gazillion articles and all sorts of detailed instructions about how to remove and update drivers. I tried for days and nothing ever worked. That's not to say that it can't be done, but I had to give up.
Do you have access to a Windows 7 computer? That will get you through the unlocking process and initial installation of TWRP. After that you won't need your PC for anything except transferring files so the drivers won't be a big issue.
Click to expand...
Click to collapse
Thanks, so it would be a problem with Windows 10? And you manage to solve it with Win7?
I don't have a Windows 7 PC but I tried to run a Win7 virtual machine, and it can't recognise the tablet as an mtp device. So, fail.
I can't believe we're the only 2 who've had that issue and that this is not generating more help and tips. Nevermind...

Try the skipsoft tool kit thread.
I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.

nexus root toolkit by wugfresh supports pixel c. good info on drivers found there.

https://www.vichaunter.org/como-se-hace/instalar-controladores-no-firmados-windows-10
Enviado desde mi SM-N9005 mediante Tapatalk

kjwaugh said:
I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.
Click to expand...
Click to collapse
Hi. Thanks. I have been reading about the issue across the Internet for 3 days now and keep seeing the same instructions which lead nowhere...

dkryder said:
nexus root toolkit by wugfresh supports pixel c. good info on drivers found there.
Click to expand...
Click to collapse
As said in the original post, I used (and always have) the Nexus root toolkit. I also tried every single driver installation method in it and out of it - several times each...

chinimen said:
https://www.vichaunter.org/como-se-hace/instalar-controladores-no-firmados-windows-10
Enviado desde mi SM-N9005 mediante Tapatalk
Click to expand...
Click to collapse
Thanks. Although my Spanish is no longer that good I believe it instructs how to disable driver signature in Windows. As I specified in my original post, I have done that.

fgaine said:
Thanks. Although my Spanish is no longer that good I believe it instructs how to disable driver signature in Windows. As I specified in my original post, I have done that.
Click to expand...
Click to collapse
Ok then you only have to install the drivers manually with the nexus root toolkit
Enviado desde mi SM-N9005 mediante Tapatalk

have you tried the legacy drivers install?

chinimen said:
Ok then you only have to install the drivers manually with the nexus root toolkit
Enviado desde mi SM-N9005 mediante Tapatalk
Click to expand...
Click to collapse
That's one of the very first things I did, mate If you have read my post. ,?

fgaine said:
That's one of the very first things I did, mate If you have read my post. ,[emoji16]
Click to expand...
Click to collapse
First you have to disable the use of unsigned drivers as indicated and then install the drivers manually from nexus root toolkit. If you read your message and I did it in that order. a greeting
Enviado desde mi SM-N9005 mediante Tapatalk

kjwaugh said:
I am not an expert, but the thread offers many insights into this problem. I got the drivers installed properly after some thorough failure too. Keep at it. I did it successfully about 9 months ago - long enough for me to completely forget how I did it. The answer will be there.
Click to expand...
Click to collapse
Hi. I didn't know about the Skipsdoft toolkit. Sounds good, I will give that a go. :good:

dkryder said:
have you tried the legacy drivers install?
Click to expand...
Click to collapse
Is that using the NRT?..

chinimen said:
First you have to disable the use of unsigned drivers as indicated and then install the drivers manually from nexus root toolkit. If you read your message and I did it in that order. a greeting
Enviado desde mi SM-N9005 mediante Tapatalk
Click to expand...
Click to collapse
Thanks again. But that's what I did. Didn't work...

I always have this problem, and it always comes down to me forgetting that the device needs a different driver in ADB mode than it does in fastboot mode. Or, at least, it needs the driver installed in each mode. If you haven't already, make sure you get it working in ADB, then go through the steps again while the device is in fastboot mode. Maybe you've already made sure of that, but the last time I needed to do it, after hours of pulling out my hair, I realized that I wasn't doing all the steps of removing drivers and then installing the correct ones while the Pixel was in fastboot.

when using device manager , left click on action then select add legacy hardware, then next, then install hardware i manually select from a list, then next, hopefully android device is at top of list, if not look for any adb/fastboot , like portable device but the point is to find a adb/fastboot early legacy device and select that, then next, then select the driver from the list and hit next. should be done.
let me ask you when you installed android studio, did you go to sdk manager and select usb drivers then install. then go to users/username/appdata/local/android/sdk/extras/google/usb_driver and right click .inf file and select install and let windows install the driver(s)?

dkryder said:
when using device manager , left click on action then select add legacy hardware, then next, then install hardware i manually select from a list, then next, hopefully android device is at top of list, if not look for any adb/fastboot , like portable device but the point is to find a adb/fastboot early legacy device and select that, then next, then select the driver from the list and hit next. should be done.
let me ask you when you installed android studio, did you go to sdk manager and select usb drivers then install. then go to users/username/appdata/local/android/sdk/extras/google/usb_driver and right click .inf file and select install and let windows install the driver(s)?
Click to expand...
Click to collapse
Hi. Yes I did but it keeps saying there are no suitable drivers in the folder. When I check myself there is indeed no .inf file in it.

I have had no luck. Using both the skipsoft and the wugfresh tool.
My pixel c is locked asking for a pin and I never put a pin lock into it. What a piece of $h!t this tablet has been.