So I've received my X5 Pro today. After installing everything, I've wanted to move some backups on to the phone. So I've connected the USB cable to my PC, but the connection gets cut every like 2-3 seconds. It always recovers itself, but it only lasts another 2-3 seconds and this loops.
After installing drivers from "https://xiaomidriver.com/poco-x5-pro" it still does not work.
Same issue.
Also, when I keep the phone locked, so it should only charge the device, the same thing is happening.
==
Also, looks like the fingerprint reader is not very responsive after the phone has not been moved for some amount of time. It is not recognizing my finger at all, and I have to use the Pin to unlock it. When it is unlocked, it works just fine. This is only happening after a longer (2-5 minutes) of downtime, I guess.
UPDATE: After some time and adding multiple fingerprints again, it seems to work fine now. I am not sure if it was the re-adding of the fingerprint, or it just needed some time, but ye. Looks like it is working fine now.
Did anybody experience something similar?
gmbhneo said:
So I've received my X5 Pro today. After installing everything I've wanted to move some backups on to the phone. So I've connected the USB cable to my PC, but the connection gets cut every like 2-3 seconds. It always recovers itself, but it only lasts another 2-3 seconds and this loops.
Also, looks like the fingerprint reader is not very responsive after the phone has not been moved for some amount of time. It is not recognizing my finger at all, and I have to use the Pin to unlock it. When it is unlocked, it works just fine. This is only happening after a longer (2-5 minutes) of downtime, I guess.
Did anybody experience something similar?
Click to expand...
Click to collapse
Did you try installing the usb driver on your pc?
Legitimate_ process 99 said:
Did you try installing the usb driver on your pc?
Click to expand...
Click to collapse
Are there any device specific ones?
After installing drivers from "https://xiaomidriver.com/poco-x5-pro" it still does not work.
Same issue.
I had the same kind of issue with my X3 Pro and now my X5 5G, took me a good amount of Googling to solve it... Windows10 is the cause of those troubles.
You'll need to :
1) disable USB power saving on EACH root hub and port in "Device Manager"
see https://www.hamoperator.com/Fusion/FusionFiles/K9EQ-Fusion-PDF-0023.pdf
2) disable driver signing mode (but first you'll most likely need to turn off Secure Boot in your BIOS/UEFI, or the commands will return a "permission denied" error)
see https://windowsreport.com/driver-signature-enforcement-windows-10/
Worked like a charm for me. Sadly, the second procedure has to be repeated often, as Windows reactivates it stealthily and without even asking for your opinion...
Ok so at least, the USB Port is working fine on my Linux Notebook. So it has to be my PC or Windows ... good news in terms of the device.
gmbhneo said:
Ok so at least, the USB Port is working fine on my Linux Notebook. So it has to be my PC or Windows ... good news in terms of the device.
Click to expand...
Click to collapse
This is consistent, since as far as I'm aware the Linux kernel does not enforce any driver signing onto its users : it leaves the task of ensuring the drivers that the user chooses to add to the system have been verified as safe by the user beforehand (maybe it's placing a bit too much trust into the user's skills or discipline, but this is a completely different discussion)...
Thank heavens, that practice of driver signature enforcement is limited to and specific to Microsoft...
Just in case...
I had similar issues with another Xiaomi device, and reason was that I didn't use the device's USB cable to connect to the PC, but I used an older USB-C cable. Once I used the USB-C cable with the red USB connection it worked.
Thought of sharing this info in the rare case this is the issue.
Kalaoras said:
Just in case...
I had similar issues with another Xiaomi device, and reason was that I didn't use the device's USB cable to connect to the PC, but I used an older USB-C cable. Once I used the USB-C cable with the red USB connection it worked.
Thought of sharing this info in the rare case this is the issue.
Click to expand...
Click to collapse
I've tested this before. It is still not working with the cable coming in the box. I've tested around 4-5 cables, I guess. So it really seems to be an OS related issue.
I have the same issue of fingerprint scanner nor working on my Poco X5. Deleted the fingerprint and re-added it. Still not working.
EDIT: just stumbled on a post while googling for a solution. It's Nova7 that caused the issue. Now the fingerprint scanner is working.
Well then I'd advise using a totally different computer...
I just had the issue on my main laptop (Win10, but it's become very cluttered over time. I need to do a clean reinstall -and an upgrade to Win11 while I'm at it- as soon as I get a 1/2 day of spare time) : the device isn't picked up when plugged in.
Switching to my ultra-light notebook (Dell Latitude 7280, Win11) solved the issue, it's being recognized at once.
As a sidenote : if your computer features USB3 ports (as many computers of less than 4 years of age do), I'd strongly recommend getting a USB2 hub to plug your phone in, and most importantly to flash anything on it, because (according to the infos I've gathered here and there anyway) USB3 is apparently known for being pretty unreliable -sometimes even treacherous- for flashing purposes with Xiaomi devices... This might apply to other Qualcomm-powered devices as well, but I don't own any such devices that are recent enough to be able to confirm it, although my Galaxy Note3 (Intl QC version) never complained about it in the past.
gmbhneo said:
So I've received my X5 Pro today. After installing everything, I've wanted to move some backups on to the phone. So I've connected the USB cable to my PC, but the connection gets cut every like 2-3 seconds. It always recovers itself, but it only lasts another 2-3 seconds and this loops.
After installing drivers from "https://xiaomidriver.com/poco-x5-pro" it still does not work.
Same issue.
Also, when I keep the phone locked, so it should only charge the device, the same thing is happening.
==
Also, looks like the fingerprint reader is not very responsive after the phone has not been moved for some amount of time. It is not recognizing my finger at all, and I have to use the Pin to unlock it. When it is unlocked, it works just fine. This is only happening after a longer (2-5 minutes) of downtime, I guess.
UPDATE: After some time and adding multiple fingerprints again, it seems to work fine now. I am not sure if it was the re-adding of the fingerprint, or it just needed some time, but ye. Looks like it is working fine now.
Did anybody experience something similar?
Click to expand...
Click to collapse
Xiaomi side mounted fingerprint reader has already known as not so reliable. Even older device with back cover fingerprint has lower rate of failure on recognising thumbprint. Either go for back cover fingerprint reader or an under display one. My guess is because they have larger area to recognise thus lowered the failure rates.
Bonjour, je viens de recevoir mon Poco X5 Pro, je suis passé au Miui 14 et je n'ai aucun problème comme vous le décrivez. le lecteur d'empreintes parfait et je n'ai aucune déconnexion avec l'USB lors des transferts de fichiers !
Snakeforhire said:
Well then I'd advise using a totally different computer...
I just had the issue on my main laptop (Win10, but it's become very cluttered over time. I need to do a clean reinstall -and an upgrade to Win11 while I'm at it- as soon as I get a 1/2 day of spare time) : the device isn't picked up when plugged in.
Switching to my ultra-light notebook (Dell Latitude 7280, Win11) solved the issue, it's being recognized at once.
As a sidenote : if your computer features USB3 ports (as many computers of less than 4 years of age do), I'd strongly recommend getting a USB2 hub to plug your phone in, and most importantly to flash anything on it, because (according to the infos I've gathered here and there anyway) USB3 is apparently known for being pretty unreliable -sometimes even treacherous- for flashing purposes with Xiaomi devices... This might apply to other Qualcomm-powered devices as well, but I don't own any such devices that are recent enough to be able to confirm it, although my Galaxy Note3 (Intl QC version) never complained about it in the past.
Click to expand...
Click to collapse
This is quite true but mostly for Chinese OEMs who are still primarily using usb 2.0 on their phones. I've noticed it happen more on win 11 though, compared to win 10. But you seemed to have the opposite experience so I'm not sure if there's a trend correlating to windows. Haven't had issues with older OnePlus devices and Motorola.
I've got a problem regarding Poco X5 Pro 5G, when my phone is off and I put the charger....it chargest to %95 without any problem and gets stuck at %95. Doesn't matter how long I wait it doesn't help at all. But if I start up my phone then the charging continues to %100. Does anybody know what's causing this behavior?
Related
Alright this is gonna sound stupid, but I've done my looking around already. It's the same ol' Windows 7 USB issue that many people have had. I plug my phone in and I get an error message regarding it not being recognized etc...
The thing is...I've been using this computer for my dev'ing for like 6 months now without a single issue after the original driver work around. Haven't loaded any roms or anything for a couple months. ****, havent even plugged my phone into my computer at all. Nevertheless, it doesn't work anymore and I've done all the steps to try to fix it. Removed all drivers, downloaded latest driver (64 bit), updated, manually updated, etc... I've pretty much tried everything.
I saw a post regarding a bad power/date cord and that being an issue. My cord is sorta frayed at the usb connector, but seems to work fine so I really don't think that is it.
The only other thing I've seen is editing my registry. It's not that I'm worried about doing it, it just says it's a bit time consuming and I'm not positive it's the answer I'm looking for.
All I want to do is update to stupid CM 6 and sure enough my computer is laughing in my face. So annoying.
Any advice or help is much appreciated.
Try deleting all HTC drivers and reinstall them. I'm running Win7 Home Premium 64-bit and have never had this issue. Hope this helps!
Sent from my CricKet Hero using XDA App
Try other usb port or replace the usb cable
Sent from my HERO200 using XDA App
Why not just dl on your phone and flash via recovery? It's not the fastest option, but it is faster than a pc that won't recognize your hero.
Sent from my CDMA Hero. I got some hot Froyo on Hero action here!
I'd definitely cover the bases with the USB cord, I've had 3 of the stock cords, all have gotten "frayed" at the USB connector and have stopped working for me numerous times.
edIT: Also, try removing other USB devices or switching ports. It may not be receiving enough power.
Shots in the dark, but have proven to be the cause of the problem enough times to warrant an extra 5 minutes troubleshooting.
I had a hassle getting the Hero connected to Windows 7. I did so many things that I can't remember exactly what made it work in the end.
These are among the things I tried:
Switching USB ports. (Plug directly into machine.)
Installing and running sync (HTC provided Outlook sync).
Uninstalling android device (especially the unknowns) and updating drivers from Device Manager.
Googling the web for different versions of the USB driver.
On my system, when I plug the HERO to the computer, it shows up in three places under Device Manager:
Android USB Devices (HTC.Corp 6/10/2009 2.0.7.1 driver)
Disk Drives (microsoft driver)
Portable Devices (microsoft driver)
I hope some of this helps!
thesubliminaljuggalo said:
I'd definitely cover the bases with the USB cord, I've had 3 of the stock cords, all have gotten "frayed" at the USB connector and have stopped working for me numerous times.
edIT: Also, try removing other USB devices or switching ports. It may not be receiving enough power.
Shots in the dark, but have proven to be the cause of the problem enough times to warrant an extra 5 minutes troubleshooting.
Click to expand...
Click to collapse
dynamicpda said:
I had a hassle getting the Hero connected to Windows 7. I did so many things that I can't remember exactly what made it work in the end.
These are among the things I tried:
Switching USB ports. (Plug directly into machine.)
Installing and running sync (HTC provided Outlook sync).
Uninstalling android device and updating drives from Device Manager.
Googling the web for different versions of the USB driver.
Click to expand...
Click to collapse
That reminds me... When I first got Win7, I had trouble getting it to recognize my Hero as well. After some googling, I remember doing something like downloading both the Win7 and the WinVista drivers and replacing some of the Win7 drivers with a few of the WinVista drivers and then rebooting and that got my computer to recognize my Hero.
Not sure if you could find the same thing, but worth a shot.
Try the advice in this thread, the part about installing HTC Sync and getting it working:
http://forum.xda-developers.com/archive/index.php/t-659888.html
I hate to be the bad one but this is in the wrong section..belongs in Q&A section
Sent from my HERO200 using XDA App
Sorry!
I actually thought about that immediately after posting. Was browsing mulitple forums and just slipped my mind. If admin wants to move it, it's not a problem.
I'll investigate the usb ports. Shortly after discovering it was magically not recognizing my phone, a bunch of my usb peripherals stopped working. And upon reboot, actually reinstalled some of them.
I guess it could def still be the cord, too. Although, it charges fine.
And if it comes down to it, I'll just do it ota. Haven't really looked into it, but apparently it's possible. And at this point this usb crap is so annoying, it sounds like a great idea.
I've removed all drivers, all anything htc, and still can't even install the driver. Even if I point directly to it via "have disk", it gives some error about having the correct driver. I've downloaded mulitple drivers from multiple places, as well.
Thanks for the advice. I'll try a few more things and be in touch.
If you can, try it on another computer. It could definitely be the USB cable if it has been working and now isn't. It can still charge but not have data work because they use different parts of the cable
Current info on it - Android 4.1.1 and stock build - epad-10.4.4.23-20121127
I was rooted for about 2 months and had the tracking cilents frozen in titanium. About 2 weeks ago I saw a thread about the update for .23 firmware. I went and unfroze the clients and did a reboot with no problem getting the OTA update and restoring root. Before this I was able to hook up my tablet to a pc and transfer files. I didn't have need to use this function until last night when I discovered that it will no longer recognize being attached to the pc.
Essentially nothing happens. There is no sound and notification icon on the pc that a device was attached. Nothing shows up in device manager. The tablet doesn't show the USB connection icon. To make sure the usb port was good i connected my cell phone to it, bluetooth dongle, and a thumb drive. It works fine. This system runs XP with the drivers previously installed and working. I tried my laptop that runs Vista and worked fine previously when connected. Again I get the same issue. Even their Asus sync software on the pc shows no device attached. Just now I tried hooked up the tablet to my work pc and no change. That makes 3 pc's that I've attempted.
I can only think it was the firmware update. That was the only change I made to the system. Last night I did a factory reset of stock to see if a setting got messed up somewhere but there is still no connection. I probably lost root in that process and since it won't connect to the a pc, I doubt I can get that back. That is the least of my concerns though. I fear that something physical with the connector went bad that tells the OS a pc connection is occurring. Would that even be possible to happen yet work fine for charging the tablet?
Thanks for any suggestions or comments.
Yes, it is the JB update if your PC is running XP (not sure about Vista, but it's probably the same). You probably noticed that the options for USB connection in JB are limited to Media and Camera? Under JB the tablet sadly does not connect as an external drive to a XP PC anymore.
The Infinity does shows up under Windows 7 as an external device. I looked high and low, but there does not seem to be a fix for XP.
My work-around for anything I do not want in my Dropbox (which is by far the smoothest way to get something from your PC to your tablet) is using Airdroid from the play store. That app uses your WiFi network to transfer files. Works great! And no cables!
Larger files, like movies, I transfer via SD card. Truth be told - I do not really miss the USB connection anymore.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
It's odd that it won't recognise a connection at all. Have you tried reflashing the full stock firmware?
Under JellyBean, XP, Vista, 7 and 8 recognise it as a Portable Media Device. My main PC runs XP SP3, so no, it's not an XP-issue.
With ICS it used to be an external drive, but sadly that ended with JB. (Which is a feature I thoroughly detest on every device including my sgs3, but alas.) Originally they deleted the feature in ICS to begin with, but for some reason it continued to work on some TF700's. Not all of them, though.
I miss UMS.... MTP drives me insane on any device. It keeps whining about literally every file format that it "is not natively compatible with the device [insert 16 more lines of text I have stopped reading because it is actually longer than the dialogue window...]" . Even .jpgs.... Which is ridiculous, as stock gallery recognises .jpgs just fine.
I mailed the tablet in for RMA and they, well someone at the center, signed for it on Friday. I tried doing the wipes and even downloaded the firmware from Asus and reinstalled it from the sd card. Nothing happens when it's connected. I got it working originally under XP following a guide somewhere on here. You have to update windows media player or something like that to end the failed driver update error. It will install the MTP support or proper drivers that are not included in XP. But yeah, now in Vista or my XP machines nothing happens and I can only assume it's hardware with the connector not recognizing a pc signal. It was working fine with JB installed before.
When I called into support their answer was RMA anyway. I had already done everything the support person was going to ask; reboot, factory reset, try different pc, make sure the usb ports work. Aside form a little screen bleed the tablet has worked without a problem until this last firmware update. There other ways for getting media to the device and that didn't concern me. It is the inability to connect the device to the pc for actions such as rooting, unlocking, or other similar functions that bother me. I had it rooted (lost now that I kept trying different wipes etc) but feared something going wrong later if I unlocked it and lost warranty. Once warrant is up this device is fair game and going unlocked for sure.
In case anyone else encounters the same problem, apparently the connector went bad on the tablet. They replaced the part under warranty. Took about 10 days in total and so far the only issues I see with the tablet is bent metal where the connector and one of the prong holes for the dock is and the screen. I assume the bent metal is from the tools used to pry open the case. The glass over the screen seems mushy and a bit popped up now on the edges. Don't know if that is something I should worry about or just expect since it was opened.
It did come back with 10.4.4.16 firmware. I was real tempted before to unlock and really let the tablet shine but hesitant now. They may not have covered the warranty repair if I did and I don't have another $500 to drop if something else goes bad that isn't minor.
No pc recgnized
I had this happen a few days ago after rom-ing ..... In win 7......
2 thoughts
1. Check in settings mk sure pc sync / connect to pc is enabled...
2. Install asus sync on ur pc
good luck
---------- Post added at 02:33 PM ---------- Previous post was at 02:24 PM ----------
Here in the usa most states have warranty laws that void their claim that unlocking it voids the warranty...and last year the supreme court ruled that jailbreaking was legal in all 50 states, this claim by asus is clearly seen for what it is....a veiled attempt to not have to honor warranty on zillions of devices...to save their scamming butts alot of money
on std warranty repairs. Its a scam, they know it.....and now u know it....
If u unlock, your state warranty laws will in most cases still enforce your warranty...
If u threaten to file a class action suit agianst them for it, they will back down and honor your warranty....or they loose bigtime......
Asus corporate is not...your friend
Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?
graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730
OK, will do. Thanks!
try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Has anyone had the problem of USB no longer working? It charges the device, but PC will not recognize the device - no icon or ability to see it as a drive in the PC. I've tried different cables and laptops, but same problem. (And the old cables & laptops work fine with my other USB devices). The phone & USB worked flawlessly the first 4 days I've had it - no problems transferring files from PC to phone & back.
Bone stock Galaxy S6 128 GB on Verizon.
Win 8.1 on Yoga 13 and Win 7 on Latitude 6400.
Thanks for any guidance.
Check to make sure the drivers are on the computer and try a different USB ports
stantaur said:
Has anyone had the problem of USB no longer working? It charges the device, but PC will not recognize the device - no icon or ability to see it as a drive in the PC. I've tried different cables and laptops, but same problem. (And the old cables & laptops work fine with my other USB devices). The phone & USB worked flawlessly the first 4 days I've had it - no problems transferring files from PC to phone & back.
Bone stock Galaxy S6 128 GB on Verizon.
Win 8.1 on Yoga 13 and Win 7 on Latitude 6400.
Thanks for any guidance.
Click to expand...
Click to collapse
Make sure USB debugging is checked. Go to about phone. Go to "build". Tap on it rapidly until it says you now are a developer. Back out of about phone and go into the new option "Developer Options" and check USB debugging. When you hook up your phone you may get a popup that asks if you want to trust this computer. Say yes. On your notification page, it might say you are connected as an installer. Change it to media. Sometimes you need to toggle back and forth from camera and media.
Tulsadiver said:
Make sure USB debugging is checked. Go to about phone. Go to "build". Tap on it rapidly until it says you now are a developer. Back out of about phone and go into the new option "Developer Options" and check USB debugging. When you hook up your phone you may get a popup that asks if you want to trust this computer. Say yes. On your notification page, it might say you are connected as an installer. Change it to media. Sometimes you need to toggle back and forth from camera and media.
Click to expand...
Click to collapse
Thank you. Yes, tried Dev mode and USB debugging, but no luck. Phone double-beeps when I connect the USB to it (and begins to charge), but no pop-ups on either phone or laptop in relation to storage / ability to manage files. No drive shown for the phone (whereas Thurs-Fri the phone showed up as an extra drive when I plugged it in.)
I also did a Factory Reset, just to see if going all the way back to square one would help. No luck there either. Phone still won't recognize laptop, laptop doesn't recognize phone.
That leads me to think something died in the hardware, firmware or something. This Win8.1 laptop works great with all my other devices.
I'm in the 10 day trial/return period (and coming from 2 yrs of flawless-except-****ty-camera HTC One M7 experience) - so if this is the "crap" quality people say is endemic to Samsung (srsly, 3 days and the phone does this? WTH), please let me know so I can get a G4 or Nexus 6 (can't go back to HTC M9 since the M7's camera was a 2 year prison sentence).
stantaur said:
Thank you. Yes, tried Dev mode and USB debugging, but no luck. Phone double-beeps when I connect the USB to it (and begins to charge), but no pop-ups on either phone or laptop in relation to storage / ability to manage files. No drive shown for the phone (whereas Thurs-Fri the phone showed up as an extra drive when I plugged it in.)
I also did a Factory Reset, just to see if going all the way back to square one would help. No luck there either. Phone still won't recognize laptop, laptop doesn't recognize phone.
That leads me to think something died in the hardware, firmware or something. This Win8.1 laptop works great with all my other devices.
I'm in the 10 day trial/return period (and coming from 2 yrs of flawless-except-****ty-camera HTC One M7 experience) - so if this is the "crap" quality people say is endemic to Samsung (srsly, 3 days and the phone does this? WTH), please let me know so I can get a G4 or Nexus 6 (can't go back to HTC M9 since the M7's camera was a 2 year prison sentence).
Click to expand...
Click to collapse
I've read some horror stories but I love mine. I have two and no problems at all. See if you can get a new one with another trial period.
Tulsadiver said:
I've read some horror stories but I love mine. I have two and no problems at all. See if you can get a new one with another trial period.
Click to expand...
Click to collapse
Been on the line with Verizon Tech Support for 2 hours as of this writing. Re-did all the diags, reset, Kies, etc. that I did Sunday from the VZN and Sammy websites. Combined with the re-setting of folders, Peel remote, TouchDown, etc. I'd done on the first phone, I'll have wasted a full day just fixing the phone.
Wish the HTC M9 had a better camera, G4 had better battery life or Nexus 6 had a better audio chip. If they send me a new GS6 and it flops again, does anyone have a recommended fallback phone to get as a placeholder until something better makes it to market (M9+ with fingerprint reader, better CPU, better camera)?
stantaur said:
Been on the line with Verizon Tech Support for 2 hours as of this writing. Re-did all the diags, reset, Kies, etc. that I did Sunday from the VZN and Sammy websites. Combined with the re-setting of folders, Peel remote, TouchDown, etc. I'd done on the first phone, I'll have wasted a full day just fixing the phone.
Wish the HTC M9 had a better camera, G4 had better battery life or Nexus 6 had a better audio chip. If they send me a new GS6 and it flops again, does anyone have a recommended fallback phone to get as a placeholder until something better makes it to market (M9+ with fingerprint reader, better CPU, better camera)?
Click to expand...
Click to collapse
NO HELP FROM VERIZON "TECH SUPPORT" OR "WARRANTY" having spent 3 hours on tech support with Verizon...
Our Samsung GS6 failed Saturday (USB won't connect to any laptops using any cables) and I spent Sunday doing Verizon's online fixes (including safe mode, factory reset, Kies, etc.) and 3 hours with Verizon tech support this morning with no resolution.
Verizon is calling Samsung and "will get back with me later this week" if and when they find or make sense of other field failures that match my phone. (Really? And how would Zappos, Amazon and other customer service benchmarks handle it? Yep, overnight a new one after 5 min call and issue RMA for the defective item to be overnighted for tear-down / fault analysis). And by the way, my wife and I are paying for "next day" replacement and within the 14-day trial period...
So one would think Verizon would overnight ship a new GS6 out to me immediately and have me ship the defective GS6 to Samsung for tear-down analysis.
That's not the case. How Verizon is handling this frankly has us spooked that Verizon does not in fact stand behind either their products or "warranty" services.
I'd hope that our 14-day return-policy time-clock be reset and a new GS6 black 128GB be overnighted to me, or find some way of extending the return window (since the device, and its "warranty" and the customer "service" have all failed within 2 days of receiving the phone).
Think I'm going to be stuck with the LG G4 or maybe even swapping carriers.
Go to a store. If they can't do anything ask for a refund.
stantaur said:
Has anyone had the problem of USB no longer working? It charges the device, but PC will not recognize the device - no icon or ability to see it as a drive in the PC. I've tried different cables and laptops, but same problem. (And the old cables & laptops work fine with my other USB devices). The phone & USB worked flawlessly the first 4 days I've had it - no problems transferring files from PC to phone & back.
Bone stock Galaxy S6 128 GB on Verizon.
Win 8.1 on Yoga 13 and Win 7 on Latitude 6400.
Thanks for any guidance.
Click to expand...
Click to collapse
It's not a work/corporate PC, is it? I had a similar issue, and turns out that USB storage devices were disabled by Windows policy.
Have you tried to use ADB with the phone? If you install ADB drivers, you could verify that you can at least connect...
VZN and Samsung tech support / customer service FTL
jimbobtexas said:
It's not a work/corporate PC, is it? I had a similar issue, and turns out that USB storage devices were disabled by Windows policy.
Have you tried to use ADB with the phone? If you install ADB drivers, you could verify that you can at least connect...
Click to expand...
Click to collapse
One of my laptops is personal Win 8.1, the other is corporate Win 7. Neither laptop recognized the Samsung GS6 after day 2, but worked flawlessly up until that time.
Still nothing back from Tech Support / Samsung "researching" the problem. Total WTF with those yaboes.
Monday I engaged the team who originally sold us the GS6 at our local store, and they're saying my new phone (replacement) will be in the store by Sat 6/27. 5+ days without a phone, but if this replacement doesn't suffer any issues, great.
Have you solved this issue? My wife's meet the same issue. And we did a lot ..... But it still no work.
This happened to me today. Computer would not recognize device. I toggled USB to camera mode then back to media device in phone settings and my pc recognized it again.
Hi all,
I've been running my Xtrons unit for a while now, with Malay v2 Android 8 for a few months. Everything used to work great, but since last week (without changing anything) my USB connection works crappy. My USB with music and DAB are connected directly through the two USB connections at the rear with an extension. They both stopped working suddenly, but the USB stick I have connected still has its power LED on. So there is power to it.
A few reboots later it worked again, but the next day it was gone again. I then checked the MCU settings and disabled PVR USB (I believe), and it worked again after a reboot. When it works, it works great by the way. The next day it still worked, so I was thinking I solved it.
However, the same afternoon same issue... Few minutes later (without a reboot) it worked again... Tried to disconnect everything and plug in either the DAB or the USB stick, but same result.
I strongly think its a software issue since I can 'solve' it with rebooting it sometimes. Anyone ever had something like this?
No one? Same problem today. Started my car and no USB whatsoever. 10 minutes later without doing anything everything worked fine for the remaining part of my journey to work.
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
It's a GS unit. Not sure if they're the same perhaps. Weird that it suddenly appeared.
I have the same issue.
when I connect USB/64GB and 3G dongle USB constantly reconnects. I'm on dasaita px5/4GB
1st up and not to be one of the thread patrol guys we seem to have running round the Android auto forums..
But general help questions like this should be in the QA area..
Maybe mods should shift it..
But to answer the question with a bit of experience lately..
In my USB thread on SSD's and the USB M2 casing I have used.. I found a similar thing going on with the USB ports..
As reported there.. plug in the M2 SSD (which of course is plugged into the controller in the housing)
And it's seemily pulling too much power as it affected the ability for a GPS lock..
Unplug it and GPS works..
My thinking there is as said..to me it is like it is either a software glitch and or power interruption. I am leaning more towards the power theory.
There is a bit of reading around on USB port burn out on some of the boards.. so it's almost like a case of being careful on actually plugging in to much to ...
In my case 3 USB ports..
This does bring up another point that has been bothering me the last few days as I hunt for a better storage situation..
My reading on 128g USBs via the comments section is showing up extremely hot usb's.. thus it's something to think about . As in these things in a glove compartment could end up being a fire hazard..
And or even in the case here, causing sort of interference back through the system..
Some of the more electronically minded techies with the right testing equipment would be able to have more input.. and I can bet you that the engineers in the factories making these things are not talking or reporting back to their bosses anything along these lines.. as they will be all about protecting thier jobs.. and no one is going to want to put thier hand up and say.. hey..I think we have a problem..
tw39515 said:
Is it a "XRC" units (MTCE_XRC_...) i think were having issues woth the usb controller.
https://forum.xda-developers.com/an...icane-px5-oreo-wifi-bluetooth-waking-t3852206
Click to expand...
Click to collapse
Tried the 'fix' from here, which should restart the usb hub, but all it does it restart the wifi, as can be seen in the code. The problem is that USB worked fine for me now twice while testing. So couldn't test if the 'fix' actually does help.
I can't seem to get Tasker to run with root... It says that my device is not rooted, although other apps give the SuperSU pop-up that ask for root access...
Tried the .sh file in the other tried, and an app to reset the USB hub, but no luck. Rebooting a few minutes later worked.
I have the same issue. I figured out that it is temperature related. When the outside temperature is ABOVE 11-12°C the USB works fine. When its colder It constantly reconnect every 20(?) Seconds. When the Car Heat Up enough the Error is gone again.
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Bose321 said:
Still no solution for my issue. Also have it in the nice (12-14 degrees C) weather in the past few days. What else can I try before I bin it and go to another HU?
edit: Oh, and how can I get this to hardware?
Click to expand...
Click to collapse
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
EDGN said:
We need to replace the USB Controller Chip GL850 to GL852. You can get the Chip in AliExpress.
€ 3,47 11%OFF | 5 stücke GL852 GL852G USB hauptsteuerspan SSOP-28 SMD
https://s.click.aliexpress.com/e/cPrldP21
Click to expand...
Click to collapse
Yeah I've seen that, but it's too small for me to try. I'm not that great in soldering, so don't want to ruin my unit haha.
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Ati_gangster said:
Install the Hal9k Rom, where you can restart the internal USB hub on startup and then USB devices will work again.
Click to expand...
Click to collapse
Already tried that, and I have the Malaysk ROM which also has the 'fix'. Also tried to run it manually. Also have a USB Controller app that can do this.
Worked a few times but doesn't anymore now.
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
mahtew said:
check this thread
https://forum.xda-developers.com/an...x5-mcte-low-temperature-fix-wifi-usb-t3868388
there are at least two solutions. one is mentioned before - to swap the GL850 chip. second is not checked yet.
Click to expand...
Click to collapse
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Bose321 said:
Already tried the second 'solution'. Didn't work for me.
My best bet now is the new chip. I've ordered 5 of them, gonna check if I can solder it, or let it be soldered once it's arrived.
Click to expand...
Click to collapse
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
mahtew said:
It's good feedback (that second method doesn't work ). also ordered three chips and going for swap.
i have other issues though. when using USB dongle or copying files from usb to internal mem my screen is blinking (like darker-brighter in fast pace).
i hope that swap will help with this issue also
Click to expand...
Click to collapse
Sounds weird as well! Good luck.
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
karolp1993 said:
My unit disconnect USB with vibrations on the road. I also try replace USB chip.
Click to expand...
Click to collapse
I think you need to see very closely in where the usb cable is welded in the morherboard and try to find cold weldings. I had same problems with my pumpkin and when i completely dissasemble it i saw a ton of cold welding and i reweld everything and its rock solid now.