hello everyone: D
*
I would like to install the rom lollipop but I have to first install a recovery ...
*
For this I have to go and do a fastboot command but this is where it stops: s
*
It makes me that
*
{
"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"
}
*
Yet I installed the drivers 2 times (and reboot the pc), I use the usb cable I originally tried several USB ports and when it is on, it is recognized ..
*
What to do?
*
thank you
Let's try the obvious...
USB 3.0 vs USB 2.0 ports and, not saying you're stupid or anything but your device is actually in bootloader mode yes? adb reboot bootloader <<< I assume you manually booted into bootloader mode on the phone hence why you didn't use that command in the screenshot? The command won't work from within the running OS it needs to be in bootloader mode.
Of course it should say in fastboot mode that the USB is connected.
Another solution for the drivers that seem to work is to uninstall all the HTC drivers and HTC Sync. Connect the device to the computer, cancel/close the prompt to install drivers. Got to Device Manager, find the device and select the option to manually select drivers thenpick the Generic MTP Android device drivers. @redpoint73 usually recommends this for device driver issues, seems to work out most of the time.
Thank you for your reply! I uninstalled the drivers etc as you say
For cons, I do not really understand the beginning of your paragraph
To get in fastboot mode, I switch off the mobile, then I turned still pressing volume down and power at the same time and press fastboot
My bootloader is unlocked if that's what you want to know
I confess I'm a bit noob with Roma with HTC and I have a little trouble with English (I use an internet translator)
nobody?
BerndM14 said:
Another solution for the drivers that seem to work is to uninstall all the HTC drivers and HTC Sync. Connect the device to the computer, cancel/close the prompt to install drivers. Got to Device Manager, find the device and select the option to manually select drivers thenpick the Generic MTP Android device drivers. @redpoint73 usually recommends this for device driver issues, seems to work out most of the time.
Click to expand...
Click to collapse
I'm not sure about "most of the time" but it worked for me, and some other folks I've given this step to.
OP hasn't stated whether he tried this or not.
Other possible solutions are to try different USB ports or even another PC (he stated that other USB cables were already attempted); re-install HTC Sync; and verify whether the ports are USB 3.0 (which often does not play well with this device).
I had the same problem and couldn't find a solution Its a combination issue of Windows 8.x and USB 3.0 drivers. I tore my hair out trying to fix it and gave up, I just do my Android tinkering on a Windows 7 PC now.
fabidesca said:
hello everyone: D
*
I would like to install the rom lollipop but I have to first install a recovery ...
*
For this I have to go and do a fastboot command but this is where it stops: s
*
It makes me that
*
*
Yet I installed the drivers 2 times (and reboot the pc), I use the usb cable I originally tried several USB ports and when it is on, it is recognized ..
*
What to do?
*
thank you
Click to expand...
Click to collapse
redpoint73 said:
I'm not sure about "most of the time" but it worked for me, and some other folks I've given this step to.
OP hasn't stated whether he tried this or not.
Other possible solutions are to try different USB ports or even another PC (he stated that other USB cables were already attempted); re-install HTC Sync; and verify whether the ports are USB 3.0 (which often does not play well with this device).
Click to expand...
Click to collapse
Yeah I also saw it working for some of the members you advised to do this...If 10 guys followed it and it succeeded for 6 of them then it's surely "most of them" Won't know about those that don't report back...
I am having the same problem. It all worked fine with my Turbo. Odd it is not working for me now. I am on Windows 10.
Everything works for me on win10 and M8. Strange issue imo
xunholyx said:
Everything works for me on win10 and M8. Strange issue imo
Click to expand...
Click to collapse
I can confirm that
No issues on win 10
Sent from my HTC M8 using XDA Labs
xunholyx said:
Everything works for me on win10 and M8. Strange issue imo
Click to expand...
Click to collapse
ahmed.ismael said:
I can confirm that
No issues on win 10
Click to expand...
Click to collapse
It was before, I fixed it with a reg file (still have it dated Oct 28, 2014 )
... now with updated HTC USB drivers and also microsoft updated drivers, no more problem, no need any fix.
xunholyx said:
Everything works for me on win10 and M8. Strange issue imo
Click to expand...
Click to collapse
ckpv5 explained it. But I don't find it so strange (for it to work for one person, and not another). Consider the endless combinations of possible PC hardware, plus differences in software, such as the mentioned updated Windows drivers which may or may not be installed. USB 3.0 (versus 2.0) alone has cause a lot of folks trouble with getting fastboot/RUU to work on the M8.
Point in case, fastboot and adb have always worked fine with this phone on my work laptop. But on my home desktop PC, I often have to manually select generic MTP drivers to get adb to work. Both run Win7.
I will try my wife's HTC cable.i used the Motorola cable.
hello,
i use htc desire 820 dual sim , my phone is not recognized in the fastboot usb mode. can you please help me out?
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.51015
OS-
eMMC-boot2048MB
hanubhargava said:
hello,
i use htc desire 820 dual sim , my phone is not recognized in the fastboot usb mode. can you please help me out?
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.01.010_U10305041_08.01.51015
OS-
eMMC-boot2048MB
Click to expand...
Click to collapse
Re-install HTC Sync, try a different USB port, a different cable.
Also, on the PC (assuming Windows) one thing that works for me, is that I have to go into Device Manager, find the phone, and pick the option to manually select a driver, then select the generic "Android MTP device" (or some name like that - can't remember exactly). This method may or may not work. I have to sometimes do it on my home PC to see my phone on fastboot/adb, but don't need to do this on my work laptop PC. Its not consistent.
Other than that (general fastboot tips for HTC devices), I can't offer much more advice. This is the M8 device forum, and I have no experience with your specific device.
Related
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
BonzTM said:
Hey All,
Been rooted/unlocked since launch and the only time I've flashed a ROM to this device was when the IMM76K leak hit. After flashing I lost CWM and root. Didn't worry too much at the time, but the past couple days I've been attempting to get it back.
I cannot, for the life of me, get the Fastboot drivers to work. I've tried every driver I could think of and I constantly get a "Device cannot start (error 10)". I've tried every USB port, multiple cables and even different machines. Everytime I plug the device in while in the bootloader I get the Windows popup that says my device can perform faster if I plug it into a USB 2.0 port.
When I did the update, does the new bootloader now require a different driver? Everything else works. MTP, ADB etc. Just not fastboot.
I'll include the specs at the bootloader screen.
Fastboot Mode
Product Name - tuna
Variant - toro 32GB
HW Version - 9
Bootloader Version PRIMELA03
Baseband Version - I515.FC05 CDMA - I515.FC04
Carrier Info - None
Serial Number
Signing - production
Lock State - Unlock
Has anybody had this problem since flashing to the latest update? Does anybody have any suggestions or advice?
Click to expand...
Click to collapse
No, there should not be any issue. I suggest to re-install the fastboot driver. Use 1wayjonny's drivers here.
I've seriously never had any issues whatsoever in any way with the drivers I'm using, and I got them from the knives & forks package. Check my sig.
Well I don't know what's your case but as I do stuff with Nexus, Galaxy tab and lg o2x on my computer sometimes one of the drivers gets messed for randoms reasons.. So I re install drivers and that's it... Try that suggestions
Sent from my Galaxy Nexus using xda premium
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
{
"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"
}
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
rmagruder said:
I just spent the last hour in the hell where everything is great when Android is booted up, but no ADB in fastboot mode.
After trying anything and everything, I got it to work:
1. Installing the Samsung Drivers while Android was up and running.
2. Reboot device to Fastboot (adb reboot bootloader)
Windows 7 now identified the device as "Android 1.0" with a yellow triangle
3. Right click | Update Drivers | Select Device
From list selected Android Phone
The dialog now showed two possible devices : Google and Samsung. Clicking Samsung showed 3 different drivers. Picked the newest.
Accepted warning about unsigned drivers, it installed it. Voila...I now see no more errors.
Click to expand...
Click to collapse
I must've done this a million times. Where are the newest drivers? I've downloaded 1.4.6.0 from Samsung's website. If you or somebody has these "newest" drivers, could I please get a link?
I've used the ones from Samsung's website, the Universal Naked drivers, Google's drivers from SDK, Drivers from Galaxy Nexus Toolkit v7, drivers from Galaxy Nexus Root Toolkit 1.4 by WugFresh. I get the same issue with all of them.
BonzTM said:
No matter what I do I get this error message.
No matter what driver I use. Even the Universal Naked Drivers.
Click to expand...
Click to collapse
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Theshawty said:
Uninstall all drivers related to the Galaxy Nexus using Driver Sweeper, then check my signature and give knives & forks a go.
Click to expand...
Click to collapse
Did one even better. Went to a brand new machine that had never seen an Android phone to be sure I was getting a clean experience.
Firstly, when I plugged the phone in (Android on), immediately said that the device could perform faster if I plugged it into a USB 2.0 port. Problem is, it was a 2.0 port. Got all the drivers installed etc. MTP, PTP, ADB works; granted very slowly because it's only going at 1.1 instead of 2.0.
Rebooted into Fastboot, same problem as before. Device failed to start (error code 10).
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
BonzTM said:
[snip]
I've done just about everything I can think of to do. It's gotta be something wrong with the hardware itself to be doing this. Problem is, how do I send it back if I can't even un-root it and re-lock it.
Click to expand...
Click to collapse
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
efrant said:
Have you checked your USB port on your device? Is it dirty/bent/etc? I doubt there is anything wrong with your phone besides that.
And yes, there is no way to re-lock the bootloader if you can't plug into a computer OR if you don't have root.
Click to expand...
Click to collapse
It seems to be fine. :crying:
BonzTM said:
It seems to be fine. :crying:
Click to expand...
Click to collapse
Try using a different cable. I just went through the exact same experience. Hours of not being able to get fastboot drivers to work (ADB would though!).
I have a small desk dock that I got off of E-Bay, and I too was getting the USB 1.1 speed warnings when using it. Never really thought much about it until this particular problem.
I've un-installed, re-installed drivers and done everything short of standing on my head in a corner
Unplugged it from the 'Dock' and used a regular USB2.0 compatible cable, and fastboot fired right up.
Yesterday I plugged my phone with usb to the pc but it didn't recognize it, When I tried with another cable , One of the devices you connected was not recognized" this message popped, the phone was recognized day before yesterday and before that but suddenly it's unrecognized by the system. How do I fix this? I tried plugging my phone to my friend's pc but still it gives the same error,
Jexbox said:
Yesterday I plugged my phone with usb to the pc but it didn't recognize it, When I tried with another cable , One of the devices you connected was not recognized" this message popped, the phone was recognized day before yesterday and before that but suddenly it's unrecognized by the system. How do I fix this? I tried plugging my phone to my friend's pc but still it gives the same error,
Click to expand...
Click to collapse
Do you have HTC sync installed? Or have you ever had the right drivers installed on this PC? If so you can try go into device manager on windows, select the malfunction device and manually change its driver to the HTC drivers and see if that works
Sent from my HTC Desire S using Tapatalk
heavy_metal_man said:
Do you have HTC sync installed? Or have you ever had the right drivers installed on this PC? If so you can try go into device manager on windows, select the malfunction device and manually change its driver to the HTC drivers and see if that works
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
Yea It used to detect my phone earlier but suddenly it has stopped, with the stock usb cable nothing gets detected, and when I try with others it pops the message that it is unrecognized.
Jexbox said:
Yea It used to detect my phone earlier but suddenly it has stopped, with the stock usb cable nothing gets detected, and when I try with others it pops the message that it is unrecognized.
Click to expand...
Click to collapse
Have you tried
Code:
adb devices
?
What does it say?
mcgi5sr2 said:
Have you tried
Code:
adb devices
?
What does it say?
Click to expand...
Click to collapse
It returns nothing
{
"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"
}
even tried to run fastboot in bootloader, It doesn't detect the phone which it used to detect previously, the phone is still in warranty but I can't give it because I can't even restore my stock backup as I won't be able to flash the stock kernel again is there any other way to return to stock?
Jexbox said:
It returns nothing
even tried to run fastboot in bootloader, It doesn't detect the phone which it used to detect previously, the phone is still in warranty but I can't give it because I can't even restore my stock backup as I won't be able to flash the stock kernel again is there any other way to return to stock?
Click to expand...
Click to collapse
OK panic not.
First see if you can test it on another computer. The HOV doesn't agree with USB3.0 so if you have any usb ports that aren't that, then try it there. Is the phone S-OFF? If so you could try and flash by putting the rom.zips on your sd-card then rebooting into recovery.
Also can you check adb with the other cables as well?
mcgi5sr2 said:
OK panic not.
First see if you can test it on another computer. The HOV doesn't agree with USB3.0 so if you have any usb ports that aren't that, then try it there. Is the phone S-OFF? If so you could try and flash by putting the rom.zips on your sd-card then rebooting into recovery.
Also can you check adb with the other cables as well?
Click to expand...
Click to collapse
I tested it on other 2 computers with 3 different cables, Adb doesn't detect my phone, The phone is S-ON, I tested it on all ports still no recognition, The phone charges through the USB but it is not recognized, I also looked at the HTC Dumlock method as I have TWRP installed, should I try that ?
Jexbox said:
I tested it on other 2 computers with 3 different cables, Adb doesn't detect my phone, The phone is S-ON, I tested it on all ports still no recognition, The phone charges through the USB but it is not recognized, I also looked at the HTC Dumlock method as I have TWRP installed, should I try that ?
Click to expand...
Click to collapse
That is very strange indeed, if it charges then it should be recognised by ADB. Are you sure your running adb from a folder it works from, are the drivers installed on the computers you tested it on?
I don't know anything about the Dumlock method so really can't advise
mcgi5sr2 said:
That is very strange indeed, if it charges then it should be recognised by ADB. Are you sure your running adb from a folder it works from, are the drivers installed on the computers you tested it on?
I don't know anything about the Dumlock method so really can't advise
Click to expand...
Click to collapse
Yea, it is strange, I was running adb for a long time on my pc and it was working and this thing has just started recently, I've read many similar posts with this strange problem but none of them give an solution to it.
Jexbox said:
Yea, it is strange, I was running adb for a long time on my pc and it was working and this thing has just started recently, I've read many similar posts with this strange problem but none of them give an solution to it.
Click to expand...
Click to collapse
Could you try it without your SD card in?
mcgi5sr2 said:
Could you try it without your SD card in?
Click to expand...
Click to collapse
Tried. still not working
Jexbox said:
Tried. still not working
Click to expand...
Click to collapse
It might be worth trying with different usb cables. If this wont help the hOV micro usb socket could be physically broken. :\
kvestas said:
It might be worth trying with different usb cables. If this wont help the hOV micro usb socket could be physically broken. :\
Click to expand...
Click to collapse
Can't tell cause the phone gets charged but it's not detected, tried at least 5-6 wires on different computers still the same
Ok another idea you could try is flashing a different rom. I am plucking at straws here though, as all our 4.2.2 roms are currently based on 1ceb0xs one anyway. Have you tried re-installing the rom from recovery?
mcgi5sr2 said:
Ok another idea you could try is flashing a different rom. I am plucking at straws here though, as all our 4.2.2 roms are currently based on 1ceb0xs one anyway. Have you tried re-installing the rom from recovery?
Click to expand...
Click to collapse
Will give it a try and report back.
Accidental full wipe of my Nexus 7 has left me with a no OS paper weight.
Fastboot indicates it's locked but I can boot into TWRP, but can't get it to be recognized by any PC and it won't recognize my OTG-USB (which has been recognized by others).
Any ideas as to how to get her up and running would be greatly appreciated.
{
"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"
}
Did you mount the OTG usb in TWRP or just looked for it to auto detect?
Btw, this belongs in the Q & A section, so ask a mod to move it
I am unable to select/check mount the OTG while in TWRP. The OTG is formatted correctly as the OTG is readable on other devices, but it seems like it just isn't being found by the N7. I'm baffled.
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Tried it on a full battery, still no luck.
tried to get it to work, any suggestions fellow XDAers? I'm in a real jam here
Check this thread: http://forum.xda-developers.com/show....php?t=3064562
Click to expand...
Click to collapse
Thanks, but I can't get the tablet to be recognized. I've tried it in multiple windows computers with both USB 2 and 3.
Have you tried adb/fastboot?
Have you tried adb/fastboot?
Click to expand...
Click to collapse
I am able to fastboot, but still can't get the pc to recognize that it's connected. The tablet takes a charge, but the pc never acknowledges that a device is connected, device manager never indicates a device is connected.
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
CrazyJ36 said:
-If you don't have any Roms on internal storage, that's no good since you have TWRP.
-Try A different USB cable.
-Definitly make sure you have installed Google USB drivers.
-Have you tried ADB Sideload in twrp? Maybe TWRPs' adb will work better.
It looks like you need to update your bootloader as well, go with the latest factory images.
If you need to know where to find the above things I can point you to them. You must eventually get the PC to recognise it in fastboot though.
Click to expand...
Click to collapse
Thanks. Everything hinges on the PC being able to recognize that I'm attempting to connect the tablet (or for the tablet to recognize that I've attached the OTG).
I have tried multiple USB cables and ensured that the drivers are installed on the multiple PCs I've attached to.
I have tried to ADB sideload in TWRP, but since none of the PCs recognize that the tablet is connected to the PC, ADB won't work.
Again, it's not that the drivers are not installed, but rather the PC not recognizing that I have attached a device through the USB (no sound, no pop-up, nothing in the device manager). It is extremely frustrating, especially since the device charges via the USB from the PC.
DorianX said:
Check this thread: http://forum.xda-developers.com/showthread.php?t=3064562
Click to expand...
Click to collapse
CrazyJ36 said:
Have you tried adb/fastboot?
Click to expand...
Click to collapse
Still no luck, any other recommendations?
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
CrazyJ36 said:
Device Manager doesn't even show something like "qualcomm_qloader"? That's seems worse than any other hard brick I've seen.
-OTG should be FAT32 formated (probably is).
-We're you using Lollipop with that 4.02 bootloader? I believe that was A prerequisite for installing Lollipop which may have cause the tablet to not show on the PC.
- Nexus Root Toolkit has different methods for installing drivers http://www.wugfresh.com/faqs/
-Found this thread http://forum.xda-developers.com/showthread.php?t=2404297&page=1
Shows holding power for A minute got theres' to start doing stuff. It' A different recovery issue though.
Hate to be A downer, I hard bricked A galaxy s4 I had for only 5 days last month. That never turned on again. It's not fun.
Click to expand...
Click to collapse
Nothing shows in the device manager. I was using KitKat on the tablet.
Turns on without an issue, opens TWRP with no issue.
when connected to the PC nothing occurs, not when it's on the Google screen, not when it's in TWRP, not in Fastboot, not when it's restarting. Nothing.
if it was the driver being missing, I'd at least see the device attached, just not communicating properly
sorry to hear about your GS4
The Apostle said:
I had the same issue. The only way I could fix was a full adb restore. I tried several other ways and none worked.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
if you truly had the same exact problem, how were you able to use ADB if your device wasn't recognized on a PC or OTG?
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
The Apostle said:
Welp, that would be my fault for not completely reading. My apologies.
sent from my Hyperdrive powered G Note 10.1
Click to expand...
Click to collapse
it's alright, thanks for the thought.
I'm just hoping since I can get into TWRP someone has an idea of how I can get it to recognize the OTG or the PC to see it and I can get into ADB.
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
zandgreen said:
Corrupted usb port on the tablet? Maybe broken pin. Try to examine it. It can happen that it is being charged but not identified by the pc because of a faulty port. Try live install of ubuntu to chech if it sees the device.
Click to expand...
Click to collapse
the port looks perfectly fine, I was thinking the same thing, but there doesn't seem to be any damage. I almost wish it was damaged so I could at least assume that's the problem and just trash the thing.
Hello everyone,
Since few days, I have a really enoying issue with my Pixel 2 XL.
Android Auto is not working anymore.
after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode
Does anyone have the same issue ?
What can I do ?
thank you for your help !
PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo
MrMoi said:
Hello everyone, Since few days, I have a really enoying issue with my Pixel 2 XL. Android Auto is not working anymore. after differents diagnostic test, USB data is not working at all. I tried different USB cable, different Android Auto car and different Computer. I have only USB charge.. not data. Even if I enable USB debbug or if I try in safe mode Does anyone have the same issue ? What can I do ? thank you for your help ! PS: https://productforums.google.com/forum/#!topic/nexus/PP_MDA4y0kU;context-place=forum/Nexus this issue looks like the same as me. but even if I enable or disable usb debbug. it doesn't work. and I am with 8.1 Oreo
Click to expand...
Click to collapse
Have you tried revoking USB debugging authorizations and then re-enabling? It is the option just below the USB debugging toggle. Taking AA completely out of the equation, if after you have tried more than one USB-A to USB-C cables on more than one PC and cannot get MTP working you probably need to do a factory data reset. This will confirm whether you have a hardware issue or not. It is also the first step Google will require you to do prior to allowing an RMA.
Edit: You can also test if fastboot is working in bootloader mode, and if adb is working in recovery mode.
thank you for your help..
I've tried adb, fastboot and factory reset...:crying:
MrMoi said:
thank you for your help.. I've tried adb, fastboot and factory reset...:crying:
Click to expand...
Click to collapse
I'm not sure you understood... my suggestion was to test the phone in bootloader mode and send fastboot commands to it from your PC (eg. fastboot devices) -and- while in recovery mode (eg. adb devices). This is of course with adb debugging enabled. You also didn't answer my question about revoking adb in Developer Settings and then re-authorizing it? I still suspect you have a cable/pc driver issue.
Oups sorry my answer is not really clear.
Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.
I can't see the device in my w10 computer in device manager
MrMoi said:
Oups sorry my answer is not really clear. Yes I revoke all ADB computer in developer setting . I try to boot in fastboot mode and recovery mode but ADB devices and fastboot device command doesn't work.I can't see the device in my w10 computer in device manager
Click to expand...
Click to collapse
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?
v12xke said:
Use THIS tool to view and remove any Google related USB drivers and try again. Don't worry about removing any drivers, they will re-install. Make sure you get them all out, REBOOT the PC and then plug your device back in. Are there any conflicts in your Device Manager in the USB section?
Click to expand...
Click to collapse
no conflicts in my device manager, nothing change after removing all my drivers
{
"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"
}
MrMoi said:
no conflicts in my device manager, nothing change after removing all my drivers
Click to expand...
Click to collapse
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked
wkJason said:
I had the same problem with my Nexus 5x (now dead) and recently pixel 2xl where there is no charging options or USB debugging mode in all different modes(recovery, fast boot) like yours.
What I did before it was installing Andromeda. Not sure if your case was the same.
Anyway, I fixed mine by going to safe mode. Plugging usbA to C, and connecting to mac. Tried changing usbc between the orientation while trying "adb devices" in the terminal on mac. After a while plugging in in each orientation. It came back to work. Not sure why..
Try it on your windows machine if it worked
Click to expand...
Click to collapse
thank you, but still not working
Did you ever get this problem resolved? I am having the same issue on my XL 2
I experience this problm as well but I just try different USB ports then it magically works. Quite annoying.
Boiler_81 said:
Did you ever get this problem resolved? I am having the same issue on my XL 2
Click to expand...
Click to collapse
Hello,
I had to send it back to the Google store. I never knew what the problem was.
Thank You
MrMoi said:
Hello,
I had to send it back to the Google store. I never knew what the problem was.
Click to expand...
Click to collapse
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Hyoretsu said:
Assuming you did find the correct OTA to go from OPP28-85-13 to OPP28-85-16, you'd have to go to fastboot, and I doubt those options matter then. Also if you didn't sign up for soak test you wouldn't be able to go from a soak to official version through OTA. Check if your PC recognizes your phone in fastboot.
Click to expand...
Click to collapse
it does not work in fastboot mode, in fact it is as if the cell phone was dead, it stopped working on the computer, it only loads, I already installed drivers, everything ... but no use, I already tried to use rsd lite but it does not recognize!
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Hyoretsu said:
Kinda dumb but you're using fastboot command right? Last time that happened to me I was using adb devices and it never showed up
Click to expand...
Click to collapse
to recognize in fastboot mode, the cell phone does not need to be recognized on the pc first? I connect the USB cable and it's the same as nothing, besides that, debugging usb also does not work to proceed in fastboot
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Hyoretsu said:
Nope. If it's in fastboot, it won't get recognized as an actual device, you'll just hear the plugging sound and be able to interact with it via commands
Click to expand...
Click to collapse
{
"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"
}
Does not recognize, neither in fastboot nor in normal mode
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Chekm8Qc said:
@kolple
Hey I know you said you installed drivers and all.. But maybe you should uninstall them and try again. This really sounds like a driver problem honestly.
You could try looking up for UsbDeview on google. It's a pc app which lets you see installed devices.. You could uninstall everything related to your Moto g5.. Then reinstall official Motorola drivers.
Click to expand...
Click to collapse
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
kolple said:
I already tested it on other computers, and the same thing happens, does not install anything, nor does the device manager appear. It is as if the cell phone was no longer receiving data through the cable ... I do not know, it could be an android bug or the faulty usb port, some solution to that?
Click to expand...
Click to collapse
This is odd for sure. I wish I could help more honestly. Trying USB 2.0 or 3.0 ports doesn't change anything right? Probably not.
kolple said:
Does not recognize, neither in fastboot nor in normal mode
Click to expand...
Click to collapse
I would say update your adb/fastboot
I never use minimal adb/fastboot but always the package that comes with the full android sdk
Also try a different USB cable
And you can try cmd as admin instead of the windows power shell not that it should make a difference
kolple said:
So, after upgrading to Android 8.1 OPP28-85-13 . somehow I could not upgrade to version OPP28-85-16 (OFFICIAL VERSION) and so I tried to update the computer, but the same did not recognizes the cell phone.
I already installed the drivers of the motorola 5x, I changed PC, cable, I activated USB debugging, I already changed that MTP option and nothing! The cell phone does not live on the PC, the only thing that happens is that it carries, nothing else! Does anyone have a solution to this? I'm stuck in a version that still has bugs and I can not update anymore ... I've tried everything!
Excuse my English, I'm from Brazil and I can not find anyone here to solve this.
Click to expand...
Click to collapse
Try using Moto lenovo smart assistant it will flash the latest firmware.
riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
Really? I didn't even know that.
riyan65 said:
Try using Moto lenovo smart assistant it will flash the latest firmware.
Click to expand...
Click to collapse
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
kolple said:
No application that will connect USB will not work, nor with debugging, no use! My salvation would be if there was an application that does these methods over wifi.
Click to expand...
Click to collapse
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Chekm8Qc said:
Man this is so weird.. In your screenshot the bootloader screen actually detects the phone being connected to usb.
Click to expand...
Click to collapse
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
kolple said:
Exactly! But it does not recognize on the system, on any computer. In fastboot it appears that it recognized, but without signal ... With the cellphone turned on normal, also nothing appears in the computer, even with usb debugging
Click to expand...
Click to collapse
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Chekm8Qc said:
Have you tried in device manager to scan for hardware changes when the phone is connected? And of course you selected mtp right? Have you selected mtp in developer options? You should try to revoke USB debugging authorizations ( right under USB debugging) this will reset the adb permission you first allowed. You should get prompt for permission again when you type adb devices under cmd ( if phone is seen by pc)
When you check your installed programs on pc do you have other USB drivers installed at the same time as the Motorola ones? If so that might cause some issues.
Click to expand...
Click to collapse
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
kolple said:
I've already changed all these options, I already installed and reinstalled the motorola drivers and nothing works for me
Click to expand...
Click to collapse
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Chekm8Qc said:
There seems to be quite a few cases like yours if you Google the problem.
Mind looking at this to start with?
https://www.google.ca/amp/s/forum.x...p-problems-8-1-official-windows-t3715171/amp/
Click to expand...
Click to collapse
did not work, even changing the options MPT, PTP, loading, the device manager did not appear anything either!
@edit
USB HOST DIAGNOSTIC