trying desperately for s-off. adb finds my device but says its offline. I'll follow any instructions cause ive tried everything and cant get it to be seen as online. please and thanks
zeer.row said:
trying desperately for s-off. adb finds my device but says its offline. I'll follow any instructions cause ive tried everything and cant get it to be seen as online. please and thanks
Click to expand...
Click to collapse
http://www.wugfresh.com/faq/7/
Have you already Tried this?
Sent from my ADR6300 using xda app-developers app
Tigerstown said:
http://www.wugfresh.com/faq/7/
Have you already Tried this?
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
just looked at it. yes i accepted the prompt already and i can see my device when i list, but its listed as offline.
zeer.row said:
just looked at it. yes i accepted the prompt already and i can see my device when i list, but its listed as offline.
Click to expand...
Click to collapse
I get this occasionally on a different device. But if I unplug and then plug it back in again, sometime takes more than once, it works
Sent from my Nexus 5
jd1639 said:
I get this occasionally on a different device. But if I unplug and then plug it back in again, sometime takes more than once, it works
Sent from my Nexus 5
Click to expand...
Click to collapse
ive been at it for 4 hours
heres a pic
zeer.row said:
ive been at it for 4 hours
Click to expand...
Click to collapse
Do you have usb debugging enabled?
Sent from my Nexus 5
jd1639 said:
Do you have usb debugging enabled?
Sent from my Nexus 5
Click to expand...
Click to collapse
yes, and unknown sources checked , and unchecked verify apps
zeer.row said:
yes, and unknown sources checked , and unchecked verify apps
Click to expand...
Click to collapse
And you're using the same cable that came with the phone? Also use usb 2.0 not 3.0 ports. These are the only things I can think of.
Sent from my Nexus 5
ADB
If you are trying to connect ADB for Weaksauce, you have to open apps folder,
run Weaksauce and accept prompt,
then run SU and accept prompt,
Then start giving your ADB commands.
just download drivers straight from htc thats all
I had the same problem at first. Then I installed Android SDK and copied the path to where the folder is on my C drive. Afterwards, Turned OFF USB Debugging, used the "revoke usb authorization" option, then Turned On USB Debugging on the phone again and the Key Verification window popped up on my phone and selected "ALWAYS" for adb to be used on the attached computer. Then tested with the command "adb devices" and now my m8 is all good and ready to go. No more offline or unauthorized.
has to be a driver situation thats stuck on my pc, used another laptop (different computer) downloaded latest sdk n it worked. this can be deleted. genuine thanks to everyone who gave input!!
michaelbsheldon said:
If you are trying to connect ADB for Weaksauce, you have to open apps folder,
run Weaksauce and accept prompt,
then run SU and accept prompt,
Then start giving your ADB commands.
Click to expand...
Click to collapse
I'm not using weaksauce because I wasn't sure if it worked on a Sprint phone. Does it?
thendyy said:
I'm not using weaksauce because I wasn't sure if it worked on a Sprint phone. Does it?
Click to expand...
Click to collapse
Just checked at the weaksauce website, and it says that it 'may' work for sprint.
If yours isn't running newest HTC releases for your phone, weaksauce could work.
I'd try it: worst thing that could happen is that you'd have a do a factory reset from hboot.
Best wishes -
mike
I got the offline message also and found out that i have to disable my USB 3 driver in Device manager.
When they are disabled i can use adb to my phone.
Related
"USB Device Not Recognized"
I have searched for so long trying to figure out what's wrong. I'm out of idea's on how to fix it, nothing will recognize my Evo.
Tried on 4 different computers, two of them running 7, one running xp, and last running vista, all say the same thing, computers not the problem.
Downloaded htc sync, disabled/enabled usb debugging, restarted the phone many times, restarted computers, and even changed the default usb connection to HDD and HTC sync.
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
b1indsided said:
Try downloading the auto sync app in market
And let me know what happens.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just tried that and still not recognizing it.
Which HTC Sync did you try? I think the latest is 2.0.40
http://www.htc.com/us/support/evo-sprint/downloads/
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
http://kenshinjeff.18jan.us/2009/06/12/adb-error-device-not-found-android-phone/
or here
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
stratman71 said:
Which HTC Sync did you try? I think the latest is 2.0.40
set the EVO connection type to HTC SYNC and USB DEBUGGING ENABLED.
Assuming you've used ADB, what response you you get from
ADB DEVICES at the command prompt?
you should get something like
C:\>adb devices
adb server is out of date
* daemon started successfully *
List of devices attached
HT05EHL10353 device
and we will know you have a good physical connection to the computers. If it doesnt show up, try a different USB cable....
also can try this helpful link...
Click to expand...
Click to collapse
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
guesswhatimevan said:
"USB Device Not Recognized"
I rooted using the idiot proof guide and used the Sprint Rom he linked in the guide. Would love some help. Thanks!
Click to expand...
Click to collapse
Did you do the 3 click method?
guesswhatimevan said:
Thanks for the help! I checked for my device in ADB and it does not list it, so i guess my cable is probably bad. I'll go out and buy another and hopefully that fixes the problem.
Click to expand...
Click to collapse
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Philosuffer said:
Probably not the cable, follow this guide before buying another cable.
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
Click to expand...
Click to collapse
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Sorry but bump, i relly need help with this.
It still says unknown device when i try to connect my phone in recovery mode.
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Mast3rpyr0 said:
Go into your computers device manager and uninstall the device and htc sync, then reinstall sync and make sure usb debugging is on then plug it in
Edit: sorry, go into the device manager with it plugged in. if its not there (should be a yellow or red triangle next to it or neat the to as a HID) them it could be your cable or phones port.
Sent from my Evo 4G via the XDA app
Click to expand...
Click to collapse
Just tried that and it's a no go, still the same problem, Also tried another cable today and that didn't help either.
I have light leakeage at the bottom of my phone, so i think i'm going to take it in for that and just get a replacement.
guesswhatimevan said:
When i connect my phone in recovery mode, it still just says device not recognized, so i can't really do that.
Click to expand...
Click to collapse
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Philosuffer said:
I think you need to pay closer attention to the guide, because this statement makes no sense in reference to the guide.
The guide is helping you install ADB drivers, you don't need to do anything in ADB while your phone is in recovery in that guide.
Could be wrong, but I'm still fairly certain that the guide will fix your issue, because I had the same problem.
It's as simple as you do not have the correct, or any ADB drivers, therefore your phone is not showing up as a device under ADB. Once you have the proper drivers installed, your device will show up.
Click to expand...
Click to collapse
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
guesswhatimevan said:
I followed the simple guide step by step.
When i boot into recovery mode i end up with this in the picture.
His recovery mode shows an Evo with a little exclamation mark next to it, i'm guessing what i got is still recovery mode. But still if i plug my phone in my computer still says unknown device, so i can't install ADB drivers.
Click to expand...
Click to collapse
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Philosuffer said:
You just have a different recovery. Once you are in recovery, you don't need to do anything else on your phone specifically.
Instead, connect your phone to your PC via USB if it isn't already and open up device manager on your PC and follow the rest of the guide.
Edit: Where does it say unknown device? In Device Manager?
Click to expand...
Click to collapse
It shows up in usb controllers instead of other devices as he shows in the guide. If i try to update the driver it just tells me it's already up to date.
>Sorry yea it does say unknown device in device manager.
Gotta bump, would really love to just fix this instead of driving 30 mins to a sprint store.
So i followed the guide for installing apb drivers, but even in recovery mode my phone still shows up as unknown device in device manager.
Ok, well I just ran into this myself on my secondary computer. Have you tried a different USB port on your PC?
My front ones were giving me unknown device, but as soon as I plugged it into one of the ports on the back of the mobo ADB showed right up in device manager.
Factory reset it and get it exchanged.I belief is the SD card failure issue.
Sent from my PC36100 using XDA App
I have the same problem and posted this question on 3 forums including the HTC support forum and nobody has been able to find the correct solution.
I know the cable and the port is good because I can connect my Samsung Moment to it and it works perfectly. On the Evo, I've downloaded the latest HTC Sync from the official HTC site, tried the one on the microsd card, checked and un-checked USB debugging, and still it doesn't connect.
The Evo won't connect to my Win 7 computer at home, Win XP at work, but it will connect to my daughters computer which is running Win XP also (all 32 bit).
I bought this Evo from Best Buy exactly 28 days ago today. Do they give you 30 days to return it, or is that only the Sprint store?
They do give u 30 day trial.go get it exchanged or...........
Sent from my PC36100 using XDA App
So I cracked my lcd and just received a replacement from insurance... it wont show a device so I can root it.
What's is there to check in order for the device to show? I have reinstalled the HTC drivers and restarted my system but nothing.
What is the best way to root 2.3.3?
Thanks!
[email protected] said:
So I cracked my lcd and just received a replacement from insurance... it wont show a device so I can root it.
What's is there to check in order for the device to show? I have reinstalled the HTC drivers and restarted my system but nothing.
What is the best way to root 2.3.3?
Thanks!
Click to expand...
Click to collapse
Check usb debugging on under settings -application- development and then try adb
theidlemonk said:
Check usb debugging on under settings -application- development and then try adb
Click to expand...
Click to collapse
already checked... i found this on another site, but am not sure what "Disk Mode" is
I type “adb devices” and get no serial number!
That means your drivers aren’t installed correctly or your phone isn’t in Disk Mode or USB debugging is not check on, please check those three and you should be good to go!
Click to expand...
Click to collapse
any other suggestions?
[email protected] said:
already checked... i found this on another site, but am not sure what "Disk Mode" is
any other suggestions?
Click to expand...
Click to collapse
When you connect to the computer, you should see the usb icon in the status bar. Make sure it says charge only for adb to work. Might also want to download HTC sync or get the android usb drivers from unrevoked.
used another computer... everything is great now
must be a driver issue on my laptop
thanks for the help though!
[email protected] said:
used another computer... everything is great now
must be a driver issue on my laptop
thanks for the help though!
Click to expand...
Click to collapse
Re-install the sdk, and make sure you have the two adb.dll files, as sometimes they are missing, and cause it not to work.
Hello folks, i am having trouble trying to get adb to recognize my device. Every time i try to do adb reboot, daemon starting etc... And then after it says device not found. I tried uninstalling and reinstalling the drivers for thehtc one m8 and yet it still doesnt work. Please help me as i want to gain s-off
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Are you using a pc running Windows 8. That was my problem. Worked fine on an old laptop running Windows 7
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BubooBear said:
Hello folks, i am having trouble trying to get adb to recognize my device. Every time i try to do adb reboot, daemon starting etc... And then after it says device not found. I tried uninstalling and reinstalling the drivers for thehtc one m8 and yet it still doesnt work. Please help me as i want to gain s-off
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
same happened with me. It turned out there was a prompt on my M8's screen asking for permission for my computer to use USB debugging. I gave it access and adb was working fine.
I had the same problem on windows 8. I installed HTC sync and everything worked fine.
Make sure USB debugging is enabled.
When you connect your phone and use the 'adb devices' command for the 1st time your phone will give an USB debugging RSA prompt. Click ok and you will be good to go in windows 7. Just run the 'adb devices' command again (or click on the UP arrow on the KB, this will replicate the last typed command) to check it sees it.
Windows 8 - No idea
grentuu said:
Make sure USB debugging is enabled.
When you connect your phone and use the 'adb devices' command for the 1st time your phone will give an USB debugging RSA prompt. Click ok and you will be good to go in windows 7. Just run the 'adb devices' command again (or click on the UP arrow on the KB, this will replicate the last typed command) to check it sees it.
Windows 8 - No idea
Click to expand...
Click to collapse
I must have missed that prompt, is there a way for me to do anything that will have that prompt show up one more time? I am running windows 7.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BubooBear said:
I must have missed that prompt, is there a way for me to do anything that will have that prompt show up one more time? I am running windows 7.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Turn off usb debugging. Give the phone a reboot.
Turn USB debugging on again and connect it to your PC again
Look at the phone It should come up again. Make sure it is set to 'always authorise'
Type adb devices = profit
grentuu said:
Turn off usb debugging. Give the phone a reboot.
Turn USB debugging on again and connect it to your PC again
Look at the phone It should come up again. Make sure it is set to 'always authorise'
Type adb devices = profit
Click to expand...
Click to collapse
I had the same issue on my Windows 8 pc.. I was able to rectify the adv device not found issue by going into device manager , clicking on the HTC one icon and manually installing the drivers by browsing through my computer and using my Nexus adb drivers and everything worked fine after that
Download htc sync, you'll need those drivers. Then follow grentuu's instructions.
umjammerlammy said:
Download htc sync, you'll need those drivers. Then follow grentuu's instructions.
Click to expand...
Click to collapse
Thanks a ton. I had just plugged my m8 in after a fresh win8.1 install and couldn't figure out why I could copy files but not see it under ADB after the adb google driver install.
Canadianreaper said:
Thanks a ton. I had just plugged my m8 in after a fresh win8.1 install and couldn't figure out why I could copy files but not see it under ADB after the adb google driver install.
Click to expand...
Click to collapse
Glad I could help!
I had the same problem using Windows 8.1. adb and fastboot were definitely installed correctly as I already used them for flashing other ROMs on my Nexus 7. The solution in my case was to download and install the HTC Sync Manager. After installing the hsm the adb and fastboot commands worked perfectly.
Best regards,
B.
I have got my device to be recognized by my PC but adb will not work ... Can anyone provide help on how to make it work?
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
dratsablive said:
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
Click to expand...
Click to collapse
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
canemaxx said:
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
Click to expand...
Click to collapse
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Lawlrus said:
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Click to expand...
Click to collapse
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
canemaxx said:
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
Click to expand...
Click to collapse
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computers fingerprint, meaning make alterations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Lawlrus said:
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computer fingerprint, meaning make altercations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Click to expand...
Click to collapse
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
canemaxx said:
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
Click to expand...
Click to collapse
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Try running adb devices and see if it will make the prompt show up
Lawlrus said:
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Click to expand...
Click to collapse
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
canemaxx said:
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
Click to expand...
Click to collapse
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Lawlrus said:
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Click to expand...
Click to collapse
I don't get what else I could do to make this work tho that's the problem....what am I missing
USB debugging enabled?
Heisenberg420 said:
USB debugging enabled?
Click to expand...
Click to collapse
Ues
canemaxx said:
Ues
Click to expand...
Click to collapse
Try running adb kill-server and then adb devices
Heisenberg420 said:
Try running adb kill-server and then adb devices
Click to expand...
Click to collapse
Bro thank you!!!! That worked
canemaxx said:
Bro thank you!!!! That worked
Click to expand...
Click to collapse
Yep
canemaxx said:
I don't get what else I could do to make this work tho that's the problem....what am I missing
Click to expand...
Click to collapse
Adb kill-server worked
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Yooperjusty said:
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Click to expand...
Click to collapse
You have to enable USB Debugging in settings in order to delete the unlock code. Unfortunately, you can't because he forgot it. You can try booting TWRP on the device using fastboot and see if you can delete the unlock code's key file using TWRP's file manager, but the reality here is that you likely will have to reset. Hope your friend didn't use a throwaway email address when setting up the device.
Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.
Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Have you recently updated and not re-authorized your phone?
sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.
Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.
sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.
Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.