Related
I tried to upgrade my rom but the process crashed. The utility mtty doesn't work because when I connect the universal, boatloader mode by the cable, to the pc, it says "USB not recognized" (sometimes when I connect the computer is frozen till I disconnect the cable of the universal)
Please, I tried to have some solutions in the forum but all the posts indicates is needed previously the usb connection.
Do you know if should be possible to run the flash of the rom in other way, for example using a serial cable connected into the miniusb of the universal, because the boatloader screen says "Serie, v.1.01"
I apprecite what you can say please, I'm really in a hole.
Try this...
Try taking out the battery for a few minutes (10-30mins) and reboot your PC then repeat upgrade process. Hope that helps. Good luck!!!
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
The only thing I found that worked was to try a different PC, then it was fine...
Click to expand...
Click to collapse
In my case it still happening in other computers. Conclussion: some piece of the software in the universal has been lost. The screen shows "Serial" that means on some way that is opened to comunication but not USB.
My questions are:
- should be possible to put some starting software in SD and do the universal boot on it.
- do you know how to connect to the computer COM! port from the usb miniport of the Universal.
I appreciate, I was not planning to replace now the Universal...
beginner said:
sl9 said:
I have the same problem on my PC at work, it's caused by a poor USB chipset in the PC, or trying to connect through a USB hub.
Now works.... I still thinking windows is so stupid software made for distroy our mind ....
Solved after install drivers for a converter usb -rs232 ( I was looking for the way to connect from rs232 the universal)
I'm happy again and I promise don't try to change rom again (at least for a while)
If some person is interested in what brand of software/hardware I installed, send me a mail...
Thanks hearing me ...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
zedino said:
i have the same problem with my friend's uni
does it mean that you don't have to own any adapter, just have to install drivers for USB to RS232 adapter
if yes, where to find it?
thanx
respectfully
ZeD
Click to expand...
Click to collapse
I want to say that is running after doing some things and obviously some of it solved my problems. I made:
- unistall last version of activesync and go back to version 4.0
- delete all the applications using ports usb.
due the connection still not running (windows message: device not recognized) and because in the screen of universal I saw: "COMM1" I tried to connect from computer port rs232. By that I purchased some special cable, name: hama brand, rs232 serial, 9 pin - usb.
As you can imagine all the steps I followed were followed by the typical restart of windows. In this sense is important to say that the universal, after connect, need to do a soft reset each time (again windows....)
Other comment is that I unmark the option to connect by usb in activesync and mark the connection by com1.
and after all was done, connecting by usb the unniversal, kill wcescomm, windows said "NEw usb device, sync device". I started mtty and now appears the USB option, great! same time the screen in universal changed from comm1 to usb, more great....
and that's all.
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
zedino said:
does it mean you solve your problem using special USB 2 RS232 connector?
ZeD
PS: it was my first idea , but i still believe i can solve the problem using USB port
Click to expand...
Click to collapse
I think my english wording was not fine. I mean I solved my problem after install the sofware -drivers- of the rs232 connector, but connecting to the universal by usb as on standard way I was syncronizing previous the crack with activesync.
OK, where to get this driver?
thanx
?????????? NOTHING ?????????????
zedino said:
OK, where to get this driver?
thanx
Click to expand...
Click to collapse
Try here.
http://www.hama.de/portal/type*3/action*1026/searchMode*1/q*039703
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
shrubbery said:
I have had the same problem several times now (search the forum for the thread).
I tried three different PC's/laptops and three different USB cables all with the same error as yourself.
Eventually I got a connection but the laborious process of trying - failing, restarting windows and soft resetting the phone, trying - failing........... until it finally worked. I did nothing differently the time that it worked but the strange thing is that it has worked every time since! Maybe the USB driver the phone has a bug in it that causes it to get 'stuck' in a mode where it will no longer correctly operate but once you have managed to 'kick' it into action it seems toi then carry on working.
It was also a ROM upgrade that caused my USB phone driver to stop functioning. Maybe the fact that the phone has a slightly diffferent software configuration after the upgrade but exactly the same hardware fingerprint causes the driver to fail.
Every time that I have had this problem it is after an upgrade but once I have gotten it to work once with the new ROM, it always continues to function - until the next upgrade.
Click to expand...
Click to collapse
not works, probably is this device lost forever, i have restarted device and PC almost hundred times, still the same result, uni stuck in Bootloader screen top of page "Serial" bottom of page "v1.00"
nothing changed, even if i connect to USB port
if someone have some solution to this s*it pls let me know
thanx
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
no, my problem persist, hundred times i tried to recover friends device using upgrade by original shipped ROM but the device is not recognized by system so there is allways connection error, so this kind of reliving this UNI is not usable
anyway, thanx for raply and suggestion
ZeD
mrijnvis said:
i have had the same. my device wast recognized by my pc, bur i used maupgradeno_id and installed a other rom, even installed the original rom from qtek (latest) then after i was finished it started then i tried the other rom and it was working. ( pc did see a unknown device ) hope you have the same and its working also.
good luck
Click to expand...
Click to collapse
If you're stuck in bootloader mode only, visit www.buzzdev.netand look for ExitBootloader utility written by the great Buzz. Just follow his instructions or scroll thru' Universal's forum here and there for problems relating to "stuck in bootloader"
hope this helps
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
i had the same problem with the QTEK of my principal after I upgraded his ROMs.
(after the hard reset, the pocket remained in bootloader mode).
you can solve this problem in a very simple way:
you have to launch the bootloader installation (BL1.01_RUU_UNI_V.1.2.EXE) from the PC (still connected with the PPC through USB) while the PPC is in bootloader mode (on your display you see "USB > Serial 1.01" or something like that).
then you do a SOFT reset and the pocket boot normally.
very simple.
i hope to be helpful to someone.
zedino said:
no device is not recognized by PC so any trying to use exitbl is not available, anyway this option was one of the first what i have tried
thanx anyway
ZeD
Click to expand...
Click to collapse
I had some problem. After uninstall all usb applications in the pc and install the software for cable usb -rs 232, doing some softreset in the pda connected, it turned the screen message "Com" by "Usb"
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Try this it shld work
hdubli said:
This is based on my experience with two UNis..one Exec and other JASJAR..both had same problem...this is how I solved :
-Put yr device in bootloader Mode
-Disable USB in Active Sync
-Now connect woth USB cable and open mtty utility
-Select the "WESUSB... " port
-You shall see a blank white screen..press Enter to get "USB>"
-Then type ( as BUzz has informed) set 14 0
(here I wud like to inform that after doing the above I did not get success so I typed set 14 10,then set 14 9 for two three times)
-Then I ran the ROM Upgrade directly(After enbabling the USB)
-I then followed the procedure as informed on the COngratulations Screen that is hold the two "-" buttons and soft reset and then pressed 0
-I got them back to normal..
I hope this helps to all my friends...Pls feel free..pls do not trouble our Buzz..he might be busy in inventing something more to our devices
Click to expand...
Click to collapse
Guru Meditation said:
I have a problem. My Exec is stuck on the bootloader screen. All I see is Serial at the top, and v1.00 at the bottom.
When I connect my exec via USB, the screen continues to say Serial (rather than switching to USB) and the PC I connect to 'installs' the device as 'unknown device' in device manager.
I've seen mention of the problem elsewhere on the site, but the only solution I can find seems to be to keep trying, and eventually it's recognised. So far, after three days of trying, it has not been recognised.
I am aware of Buzz tool to get the device out of bootloader mode, but that required a connection to be established, which at the moment, I can't do.
Has anyone got any experience of this, or any ideas as to what's causing this, or how this can be fixed? I have tried uninstalling the 'unknown device' from device manger, restarting the PC (and hard reset of the Exec) then reconnecting, but the same thing happens every time.
Just noticed your user name, I was a big Amiga fan a few years back, still fire up Amiga forever occasionally on my PC when I feel the need.
Any ideas would be appreciated, as I'm currently staring at a rather expensive paper weight.
Click to expand...
Click to collapse
Try it with a different USB cable or in a different USB port (don't go through a hub and if you've been using a laptop then try it on a desktop PC since some laptops have hubs built into them). If that doesn't work then you're out of luck as your Universal isn't detecting that you've connected to your PC and its time to send it in for repair.
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
i am stuck on the same problem and wondering the forum for almost 3 days now with no luck.... please help my device is in boot loader mood but not turning the serial to USB ......... please HELP.......
solution
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Please follow the steps:
1. Plug in ur usb cable in bootloader mode while it is showing 'serial' and version 'x.xx'.
2. Soft reset by pressing Backlight+power+reset pin WHILE KEEPING THE USB CABLE CONNECTED
3. your phone will now reboot into 'usb' mode. Don't remove the usb cable yet.
4. Remove the Memory card while keeping the usb cable still connected and VOILA,your pc starts recognising your phone as Microsoft usb sync.
5. Do whatever you want to do now (upgrade)
Hope it solves the problem now.
Press thanks if it does.
Something else to try
Having had a few issues with my G3 Uni, I've been through my fare share of Uni bootloader issues. When I find that I can't get the 'serial' to go to 'USB', I normally find it's because I haven't taken the memory card or the SIM card out (usually the memory card).
Make sure your memory card is out, then try to enter the bootloader and see if this cures it. If it does, then use mtty and the command 'set 14 0'
This tells it to reboot on reset. if you were to use 'set 14 1' it would go back to the bootloader on reset.
my Htc hd2 t-mobile won't recognize usb on boot-loader mode
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
kaleb2954 said:
hey guys i have a big problem!!!! my Htc hd2 t-mobile won't recognize usb on boot-loader mode. Here is the story my phone was running android 2.3.7 cyanogen 7 but i wanted to update it to ics android 4.0.4, So to do that i restarted my phone while holding down the down volume button and the boot-loader with the three colors came-on saying serial but when i connect my usb cable it won't show usb. even when i tried to run the dft.exe it shows an error saying usb connection failed. BY the way it lets me access the sd card using the usb cable on my pc, so i don't know what the problem is. PLEAS HEALP i am begging u guys pleas!!!!!!!!!!!!!!
Click to expand...
Click to collapse
you have the wrong forum friends! This Htc Universal section
to update Android on HTC HD2, you can use the Clock Work Mod Recovery !! for more details should refer to this thread http://forum.xda-developers.com/showthread.php?t=1021837
I-MATE JASJAR hung
Guru Meditation said:
Thanks Niketkumar - unfortunately it's the step before your suggestion kicks in thats the problem - the device won't connect to the PC, so when using mtty WESUSB..... isn't an option, only COM1 and COM2.
Shuflie, I've tried with three separate USB cables on a laptop and desktop (neither through a hub, and the same device has worked fine on both laptop and desktop before).
I fear a trip to the doctors is in order ...
Very frustrating because the PC sees a device, but installs it as unknown device. Anyone know if theres a Windows CE device driver that I could try and install as an overide (i.e. in device manager on the PC go to update driver and browse to a WinCE.inf or equivalent?)
Failing this, has anyone got any clue what needs to be fixed? Or how much it might cost?
Click to expand...
Click to collapse
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
bechir2013 said:
Hi every one,
i have a serious problem with my HTC I-MATE JASJAR what's blocked in white screen (Serial / USB) and i cannot do anything on it, no boot, no reset soft, no reset Hard, no upgrade.
The issue is related to:
I tried to upgrade Radio ROM from 1.09.00 to 1.12 and i'm using Windows 7 Pro and when starting Flash, my PC shutdown because an electrical issue and since that, i cannot boot my device, i cannot flash or reset, my device is hung on white screen with Serial when no USB cable bluged in the PC and USB when Cable is pluged.
I Tried many times to boot it but no response, it's still hung and nothing can move on it.
I Just have one detail: when i plug the USB cable in my PC, the device is reconised but when starting upgrade or flash, i have error 101, no connexion.
Plz someone help me
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=5456317&postcount=6
the first point...
A lot easier than to root this device
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
:::Edited:::
Try killing any adb running in the background first
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Another option is to use updated flasher attached. I found it on russian forum.
hlvl said:
I'm not sure it is somehow connected with Android or ADB since when HD2 is in flasher mode it is not runnung Android. The device is detected like HTC Usb Sync or something like this.
Click to expand...
Click to collapse
Meh... I can't read. For some reason I read that you were talking about connecting your phone to the PC, i.e. within android, for USB mass storage etc....
Even the topic of the thread says otherwise. I'll go get my eyes tested...
Sometimes it's because ADB still in your PC memery, just force close it and everything will be fine.
As I said I tried to reboot PC but it didn't help. I doubt ADB start with Windows but rather only when you start using it.
hlvl said:
Another option is to use updated flasher attached. I found it on russian forum.
Click to expand...
Click to collapse
Do you mean that this is MAGLDR 1.13!?!?
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Thanks man. I was already freaking out because of this.
I'm going to try this on my desktop, that's why I stopped using it lol
Sent from my HD2 using xda premium
Thanks! It worked very well!!
PG
Really thank you, you saved my phone
Mine has always done that. I just have to wait until the flasher program gets to the Looking for USB step and disconnect/reconnect the USB cable.
Or get a new cable. I had the same issue but even this guide didnt work. My cable needed replacing, luckily I had a spare in my closet. Tried it and bingo all the drivers installed. If it just wont find it, get a new USB cable.
I have the same problem but in bootloader my usb connection works...when i try to flash recovery with usb flasher mode in magdlr doesnt.
Wait for usb............and is stuck like that.So its not the cable..i tried to install new driver..i tried with command prompt....im freaking out!!
Installing WMDC 6.1 worked for me
hlvl said:
Let me share one solution that I developed recently.
At some point, after numerous reinstallation of Android, my HD2 become undiscoverable for MAGLDR as well as for Android flasher via USB Flasher. I wasn't able to flash anything. "Waiting for USB connection" was displayed until timed out. I did reset phone, removed battery, rebooted PC - nothing happened. I started to think about replacing USB cable.
Here is what helped at the end:
- Disconnect phone from PC
- Open Command Prompt
- Type "set devmgr_show_nonpresent_devices=1", Enter.
- Type "start Devmgmt.msc", Enter.
- Two commands above should be entered in the same command prompt window or it won't have an effect.
- When Device Manager opens select View->Show Hidden Devices
- Expand all nodes and remove all inactive devices - and icon of such device is grayed out
Here is an article about it http://support.microsoft.com/kb/241257
After that when I connected phone with USB cable system reinstalled drivers from scratch and I was able to flash.
Click to expand...
Click to collapse
Had same problem getting PC to recognize HD2 in order to Task29, etc...
I downloaded/installed WMDC 6.1 (for Vista, but works with W7) and walla... fixed! Link HERE.
USB cable only charges the phone when connected to computer. Tried the following
1. Using 2 different cables which previously worked for data but phone only shows charging.
2. Using pc and Mac and both does not see phone. Looked in device manager of windows but it nothing shows up. Both computer previously used for data transfer on this phone
3. Looking inside usb-c port but no lint or dirt. Although just before update to September security patch my phone has some water on the screen which I wiped off. And the phone does not show sign of problem other than no data transfer to computer
4. Factory reset phone and same thing
5. No notification shown for changing charging only to file transfer
6. Computer doesn't Bing when connected.
What else can I try? Anyone can help or confirm if their usb-c works after September update so I can narrow down to hard ware problem.
Anyone diagnosed this hardware problem before?
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
jd1639 said:
Do you have developer options enabled in settings? If you do go into networking/usb configuration and change that. If you don't you can enable it by going into about phone in settings and tapping the build number 7 times.
Click to expand...
Click to collapse
I tried changing the options to MTP, PTP, midi, charge only, etc but non of them make any difference to the computer, nothing pops up and does not show as new item connected in device manager
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
jd1639 said:
did you try changing from charging to mpt, and maybe back and forth, while the phone was connected to the pc? I have the same update on my 5x and mine is working fine.
Click to expand...
Click to collapse
Tried changing when USB connected and when not. Doesn't seem to make a difference.
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
jd1639 said:
I'm not sure what to tell you. You could try flashing the firmware package prior to the sept update. You'll have to re-set up your phone, but if you've already done a factory reset it won't be worse than that. That could tell you if it's software or hardware
Click to expand...
Click to collapse
I don't know how I can flash a previous firmware if I don't have USB access.. it's really frustrating. Looking from ifixit. It does not seem there is any chip near usb-c other than voltage control.
Can't seem to find how I can look at logs to know if USB has been engaged or if there is any error message. It's all dead end and my phone seem to be the unique case.
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
jd1639 said:
Are you rooted and do you have chainfire's flashfire?
---------- Post added at 01:22 PM ---------- Previous post was at 01:07 PM ----------
I should have asked if USB was working before the sept update? I had a problem where the PC would recognize the device but couldn't run fastboot. This solved that problem but it sounds different than your issue
https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4
Click to expand...
Click to collapse
USB worked fine, I am using it for Android studio, and transfered music across as well. Looked at the post and it seemed that has to do with device manager. Problem is mine does not show up any changes to device manager. I.e . No ADB or other device. Seemed like no data is exchanged and windows treating it like a battery or something
Any fix for this?
I've hit the same issue and wondering if anybody has a fix for this yet?
I'm using linux and seeing no usb activity at all from my nexus 5x after sep 17 update.
I've tried multiple cables. Cleaned the usb port on the phone. Multiple PCs.
I've connected to the phone using adb over tcpip and seeing nothing in logcat except battery logs when the usb cable is plugged in and out.
Turned usb debugging off and on.
I've set usb mode in developer options to mtp (it was on 'charging') and restarted the phone. Then find the option is forced back to 'charging.'
Logcat entries during boot show no failures in regards to usb connectivity.
Charging works fine but no data connectivity via usb at all.
Anyone got any other ideas?
Hello world.
I had the same issue.
To solve the problem :
- unlock developer mode
- switch on debug usb
regards
J.
I had this problem too- did not have to enable USB debugging though, just enabling the developer options fixed it for me. Which is odd because I definitely had them enabled previously... I guess a recent update reset that and for some reason all the USB data options are tied to developer mode now.
I've got 790 (american, as i know). The same issue, no response from service, guarantee, doesn't help, pc shows it as unknown device. some other bugs, mobile data fails, no sim detected after a few seconds, violet camera with no focus, but nice when the distance ia ok, so matrix works ok, but no stabilisation.
Then, bad battery, it seems that the bank ia ok, but controller works bad. it charges enough time to think that the capacity is not degraded. I suppose that usb controller (pc connection and fsat discharging) are nearby problems.
None of the above posts worked for me on my N5x (8.1.0 March), but searched some more and found this to work for me:
https://productforums.google.com/forum/#!topic/phone-by-google/DfpqXN1UfWY
Hello everyone. I'm just resurrecting this old thread so I can provide the solutions I have found to this problem. It appears this symptom has multiple causes, and there are different solutions depending on the cause. I have seen this problem twice now on my Nexus 5x (stock, no custom ROM) and solved it both times.
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
2. SOLUTION #2 - ClockworldMod USB Driver was installed. Replace with Google driver
The second time I encountered this issue, the Solution #1 above did not work. Surprisingly, the adb devices command successfully detected the Nexus 5x. It's just that the phone wasn't showing up in the Windows 10 File Explorer interface.
The root cause of this problem was that I had installed the ClockWorldMod USB Driver because I was playing around with their Vysor App (on a different phone.)
BTW, I think the Vysor tool is really nifty for screen mirroring purposes!
To resolve the problem, I replaced the ClockWorldMod driver with the regular Google USB Driver.
(Sorry, XDA is not letting me post links because of my low post count. The link is:
h++ps://developer.android.com/studio/run/oem-usb.html )
The procedure is:
- Download the Google USB Driver from the link above and extract the ZIP.
- Enter the Windows Device manager
- Find 'Android ADB Composite Interface'
- Open the properties of 'Android ADB Composite Interface' and you will see it is from ClockWorldMod.
- Right click on this Interface and Select 'Update Driver'
- Click on 'Browse My Computer for Driver Software'
- Click on 'Let me pick from a list of available drivers on my computer'
- Click on 'Have Disk'
- Browse to the Google USB Driver you downloaded.
- Select that driver and load it on top of the ClockWorldMod driver. (Windows may claim that you've got the best driver already installed, but ignore that.)
After re-installing the Google driver, the Nexus 5x appeared immediately in the Windows 10 interface for file transfers.
Cheers, I hope this helps someone out!
I have the same problem with LineageOS 15.1, I am not sure since when, because I don't use USB that often, but I it must have been after the second update for 15.1. ADB and FASTBOOT don't work.
None of the suggested methods work. I am on Linux, but I also tested the USB driver solution on a windows PC.
The problem is, my phone does not trigger any response from the system I connect it to.
On Linux an lsusb/dmesg shows nothing, and on windows it doesn't make the classic "ding" when I connect something to the USB port.
It is like my phone isn't even there.
In the developer options under networking and USB, USB was set to charging only. I changed that to MTP, but it didn't help.
Now I can't change it back (not that I want to, but just saying). No matter what I press on this menu, it always stays on MTP.
I am here because of adb not connecting tho, MTP is not my concern anyways.
I am not sure what to do, format data, and wipe system etc. and go for a clean install? The problem is, when I boot into recovery, ADB and FASTBOOT don't work either, i.e. my computers don't see an USB connection. So will a wipe even help? I am scared I wipe my phone, and then I can't connect via ADB in TWRP.
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
tantalfr said:
Hello @ufopaper
Did you try to cleanup usb connector with a toothbrush and/or a soft plastic tool ?
Did you try different usb wire ? On multiple computers ?
Click to expand...
Click to collapse
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
ufopaper said:
I even bought a new cable, however, I didn't think about the toothbrush .. and yes, that was it
Thank you VERY much!
Click to expand...
Click to collapse
Never underestimate the power of a toothbrush
Bamboo-Toolkit said:
1. SOLUTION #1 - Messing with USB Configuration in Android
First time I encountered this problem, I did the following:
- USB Debugging was already enabled
- Enter USB Debugging menu
- Scroll down to "Select USB Configuration"
- Open this and select MTP, even if MTP was already selected. On my 5x, MTP was already selected, but selecting it again fixed whatever was broken, and the phone was immediately visible again in the Windows 10 interface when connected via USB.
Click to expand...
Click to collapse
Amazing, this solved my problem. Thanks!
my a2 lite does not connet to my pc, I have installed drivers, put it on usb debug, but my pc does not recognize de phone, I have tried different usb ports and cables with no success, it does charge eventually with some cables, but I don't know if this is hardware problem or there is any setting I am missing, it does not give me any choice of chosing the usb kind of conection
it is a new phone just prepped for everyday use, not hacked or modded in any way
USB OTG is working but only reading, I cannot write in external usb drive with es file explorer, or the includer file aplication, it says unsupported operation
any help?
Set hardware id in the adb_usb.ini file perhaps
cpu004 said:
Set hardware id in the adb_usb.ini file perhaps
Click to expand...
Click to collapse
thank you, but I cannot acces from adb as there is absolutely no conection from my computer, it only starts charging but as if it were just a charger, there is no usb mode options avalaible y my phone, and the pc does not recognize anything conected
I have tried to connect with another computer with the same results, it only gets power, but no data comunication whatsoever
as nobody gives any clue or info about some hidden setting, I must assume this is another case of bad quality control in xiaomi products, I will check with the seller
Did you specifically set file transfer mode via the notification drawer or left it on charge only?
cpu004 said:
Did you specifically set file transfer mode via the notification drawer or left it on charge only?
Click to expand...
Click to collapse
the phone does not detect either that it is connected to a computer, so the notification to select the mode of connection does not even show
I have tried usb otg and I can read fine but I cannot write at all in a pendrive
I have installed also an sd card as internal memory and have storage errors all the time so I have removed it
I have tried also conection in fastboot mode but the computer still does not recognize anything connected
I have uses several cables, usb ports and even 2 different pc with same results
My only guess is that there were some hidden config setting that is messing with the phone, that's the reason I am asking before going to the seller.
Seems like a broken USB pin then
cpu004 said:
Seems like a broken USB pin then
Click to expand...
Click to collapse
an usb pin should not affect internal sd memory, and usb does not work like water pipes, one pin data in one pin data out, they need both data pins for reading also, so as it can read from pendrive the problem is somewhere else, not in the connector.
This could be a hardware problem. Have you tried to connect it to another computer?
I have already tried on 3 diferent computers with same results. The only diference so far is that it actually does not read either the content of a pendrive connected through OTG, the first day it read it, now it only detects but reads nothing.
Also when sd is configured as internal memory, instead of reading internal memory, that seems to be the normal result, I can read only the sd card with android file explorers
I have the same problem.
No connection data with pc/mac, it only charges.
I'm italian and like many other italians, I've also the problem with Sim slot 2 with no connect..
robiox said:
I have the same problem.
No connection data with pc/mac, it only charges.
I'm italian and like many other italians, I've also the problem with Sim slot 2 with no connect..
Click to expand...
Click to collapse
It is good to know I am not the only one.
F**k, this phone starts to look like a piece of garbage I dont connect to USB, I dont use SD not 2nd sim, so I did not experience these issues, but, f**k again..
Have you tried rebooting? Press the power button for 15secs. to power it off. Use another cable, use another PC, make sure the cable is plugged in properly... bla bla bla. Oh, have you tried placing the phone into a dry rice bowl? Haha (sorry, I had to). I'm sure you've tried it all.
So, I have not much to say. Only that I had a similar problem with a Moto G after I flashed a LineageOS ROM. It worked fine before, but with the new ROM, the USB didn't work at all (it could only read OTG). It was stuck in the "charging" mode. No notification nor option to turn it to file transfer. The PC didn't recognise it at all, either.
Solution? Initially, I turned on USB debuging option and the PC saw the phone (on windows device manager, it was there, but not on MyPc). It was some advance. I can't remember if adb detected it.
Final solution? Luckily my phone was rooted and had a custom recovery, so I could easily flash the same ROM from the TWRP recovery and everything works fine now.
You might try using Xiaomi's flash tool to try to flash the orginal ROM again IF the phone is recognised by the tool (try if it can see the phone) http://en.miui.com/download-354.html
And I suggest contacting Xiaomi for a warranty claim if needed, 'cause it looks like a harware problem (a pin the the microUSB port issue). But be ready to answer the questions posted above several times haha.
Good luck!
adriakus said:
Have you tried rebooting? Press the power button for 15secs. to power it off. Use another cable, use another PC, make sure the cable is plugged in properly... bla bla bla. Oh, have you tried placing the phone into a dry rice bowl? Haha (sorry, I had to). I'm sure you've tried it all.
So, I have not much to say. Only that I had a similar problem with a Moto G after I flashed a LineageOS ROM. It worked fine before, but with the new ROM, the USB didn't work at all (it could only read OTG). It was stuck in the "charging" mode. No notification nor option to turn it to file transfer. The PC didn't recognise it at all, either.
Solution? Initially, I turned on USB debuging option and the PC saw the phone (on windows device manager, it was there, but not on MyPc). It was some advance. I can't remember if adb detected it.
Final solution? Luckily my phone was rooted and had a custom recovery, so I could easily flash the same ROM from the TWRP recovery and everything works fine now.
You might try using Xiaomi's flash tool to try to flash the orginal ROM again IF the phone is recognised by the tool (try if it can see the phone) http://en.miui.com/download-354.html
And I suggest contacting Xiaomi for a warranty claim if needed, 'cause it looks like a harware problem (a pin the the microUSB port issue). But be ready to answer the questions posted above several times haha.
Good luck!
Click to expand...
Click to collapse
I have done all your sugestions previously, even reseting phone with a new gmail account so no config setting from other phone could interfere, I have also tried fastboot, but although phones goes to fast boot mode the pc does not recognize connection either
it is not an usb pin issue, tried 6 cables, 4 computers, 10 or more usb 2 an 3 ports, I am negotianting in aliexpress a refund, we'll see
If I go into recovery mode with power vol+ a broken android appears.
elsita said:
I have done all your sugestions previously, even reseting phone with a new gmail account so no config setting from other phone could interfere, I have also tried fastboot, but although phones goes to fast boot mode the pc does not recognize connection either
it is not an usb pin issue, tried 6 cables, 4 computers, 10 or more usb 2 an 3 ports, I am negotianting in aliexpress a refund, we'll see
If I go into recovery mode with power vol+ a broken android appears.
Click to expand...
Click to collapse
I don't know if you already did this, but try using a PC with Linux (you can use Ubuntu without installing it on the PC, then install the fastboot package).
Hi,
I had no problem with fastboot and adb with Mac!
Phone recognized by the machine and do transfer boot.img for magisk...
Now I Win!
I can see the internal memory with Android File Transfer (Trasferimento File Android in italian!) - this is the link https://www.android.com/filetransfer/.
My version of Build is V.9.6.8.0.
Solution:
- Connect the phone to pc/mac;
- Go to: Settings -> System -> Developer Options -> Select USB Configuration -> select first "Charge" and then "MTP" (Media Transfer Protocol)
- The system recognize the phone!
[for italian, like me, andare su Impostazioni -> Opzioni Sviluppatore -> Seleziona Configurazione USB -> scegliere "Ricarica" e poi "MTP" (Media Transfer Protocol) ]
robiox said:
Hi,
I had no problem with fastboot and adb with Mac!
Phone recognized by the machine and do transfer boot.img for magisk...
Now I Win!
I can see the internal memory with Android File Transfer (Trasferimento File Android in italian!) - this is the link https://www.android.com/filetransfer/.
My version of Build is V.9.6.8.0.
Solution:
- Connect the phone to pc/mac;
- Go to: Settings -> System -> Developer Options -> Select USB Configuration -> select first "Charge" and then "MTP" (Media Transfer Protocol)
- The system recognize the phone!
[for italian, like me, andare su Impostazioni -> Opzioni Sviluppatore -> Seleziona Configurazione USB -> scegliere "Ricarica" e poi "MTP" (Media Transfer Protocol) ]
Click to expand...
Click to collapse
somehow i was able to connect through fastboot with the help os some advanced users, I unlocked boot and managed to flash original firmware using fastboot mode, the result: no usb connection, no pendrive otg, sd card as internal memory gives storage errors all the time ...
so the phone is faulty, now I am at aliexpress hands claiming for a refund and send back phone
elsita said:
somehow i was able to connect through fastboot with the help os some advanced users, I unlocked boot and managed to flash original firmware using fastboot mode, the result: no usb connection, no pendrive otg, sd card as internal memory gives storage errors all the time ...
so the phone is faulty, now I am at aliexpress hands claiming for a refund and send back phone
Click to expand...
Click to collapse
Where are you from? Where did did you purchase the phone (the actual store, is it in China)? Depending on where are you from and what country did you buy the phone from, by law, you'll get manufacturer warranty. So, any "official" distributor in your country will have to provide a warranty solution for you. If Ali Express is unable to provide you with a solution, look into that.
Let us know how it work out for you
adriakus said:
Where are you from? Where did did you purchase the phone (the actual store, is it in China)? Depending on where are you from and what country did you buy the phone from, by law, you'll get manufacturer warranty. So, any "official" distributor in your country will have to provide a warranty solution for you. If Ali Express is unable to provide you with a solution, look into that.
Let us know how it work out for you
Click to expand...
Click to collapse
I am from Spain, and the aliexpress seller has store in Spain, but you know how chinese vendors act ... no agreement so far, and now aliexpress decides, whenever they turn back to work, because China as you may know is a whole year vacation place for workers ...