I recently bought the POCO X4 Pro 5G, but the device isn't detected by my computer, which runs Arch Linux.
When connected via USB to the computer, nothing pops up on the device, and it just charges. On the computer, nothing indicates that the device is detected either : nothing in the lsusb menu, and of course, no device detected by adb.
I enabled USB Debugging/OEM unlocking, installed the abd/fastboot tools, tried using the XiaomiTool v2 software, without success.
I also used different USB cable, including one which supports data transfer.
Does anyone know why this happen, and maybe how to fix it ?
It works fine on my computer running Manjaro Linux (which is based on Arch). Maybe faulty usb port on phone? I am just guessing.
EDIT: And you can try rebooting phone first, same thing happened on my another phone before.
Related
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
Hi, I have a problem here, I bough a very, VERY cheap D820 to a guy I met a few days ago, he told me that he was trying to root the phone and he somehow bricked it so he was selling it half priced, anyway, the problem is that I cannot get the phone to be recognized by any PC running Windows OS or Linux based OS. Linux does nothing at all, and windows says "Unknown Device" every time I connect the device.
I downloaded Google drivers, Android SDK Drivers, Universal Naked Drivers and had no luck at all, windows says the best fitting driver is installed allready (Unknown Device). Also there's no OTG detection either. I can only charge the phone but there's no data transfer of any kind, I've even tried with different usb cables with no luck.
I noticed that the device have installed TWRP 3.0.2-0, the OS instaled was Official 4.4.2 and there wasn't any SMS app installed, not even Google Play or any file explorer app so I went to my other phone, downloaded NitrogenOS along with Pico GAPPS, did a full wipe (DATA, DALVIK, CACHE, SYSTEM) and flashed the ROM and GAPPS. The phone booted just fine, there's no issue with the OS, WiFi works very well, also LTE and H+, bluetooth, I mean everything, yet, the problem persist, I cannot get the device to be recognized by any PC.
Can anyone help me? I don't know what to do next.
PS: I can access bootloader and recovery without any issue yet, adb and fastboot doesn't recognize the device even with debugging turned on.
Sounds like the USB flex cable in the phone is damaged.
Tried different USB cables and USB ports?
audit13 said:
Sounds like the USB flex cable in the phone is damaged.
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yeah, I tried 4 different fully working USB cables (tested them on my Motorola Moto G xt1032), I think the micro USB port on the Nexus its ok because I can charge the phone normally without any problem at all, the issue comes when I try to connect the device to any PC or OTG adapter to transfer files and such.
Sent from my Moto G using XDA-Developers mobile app
I believe It's possible that the phone USB flex cable is damaged even though it charges but will not transfer data.
Agree, most likely the USB port. Not a difficult or expensive part to replace.
I have searched for 2 days now and tried countless fixes for this issue, even fixes that have nothing to do with the phone. When I plug my 7 pro into my Windows 10 desktop it is instantly recognized and I can access files. When I plug in my 8T I get "USB device not recognized."
It's actually more complicated than that though. I tried using a different cable, it worked for a bit. It loaded and I could access it. Cool. Went to the MSM tool to flash the global rom and right as it started going the phone disconnected and the "USB device not recognized" error popped up. Now the phone is bricked. Black screen, doesn't vibrate when I plug it in. Can't unbrick it with the MSM tool as it's not a recognized USB device and isn't connecting with the computer.
Tried connecting it to my Samsung Galaxy Book 2. Same thing. 7 pro is fine, 8T isn't recognized.
I have tried removing and reinstalling drivers. I have tried unplugging the computer and all cables. Tried several other things. Searched youtube, google, duckduckgo, this forum, oneplus forums, and asked at r/oneplus and got no reply from anyone.
Can this be saved?
Update: Connected another OnePlus 8T to my computer and it popped up an option to install drivers from a cd that doesn't exist. It seemed to think the phone attempting to install drivers was coming from a CD. Never could get it to work, used the .exe file I already had and installed drivers and now that phone is recognized and I can access the files. This never happened with the other phone. It was errors from the start.
Hi there... I am struggling with my zte axon A2020G Pro running android 11. The problem is i can only connect it to my Windows 10 PC in charging mode. No fastboot or adb connection. Bootloader locked.
When trying to connect with usb cable i get the message Unown usb device. It charges only. I have tried changing cables, changing computer, Wireless adb, Rooting without PC. I have tried software upgrade/downgrade from sdcard.
I have read this problem can arise when flashing wrong uppgrade but as the booloader is locked i dont think this is the problem.
Everything else i working perfect and the phone is looing like new. Bought it from Tradera so no service support available in Sweden.
My main goal is to get it working with my PC so i can get it bootloader unlocked and transfer files.
Any ideas or suggestions?
Brief: Having issues with USB in Windows 11 and my Le2115. Right now, Windows sees the device, and adb devices returns a serial number (with debugging on); however, the phone is not seeing that it is plugged in at all. It is not charging, no transfer options, nothing.
History: So, it all starting sometime after trying to get rid of OS13 and returning to stock, I bricked my phone pretty good. Ended up using MSM and loaded an india version, went back to a Global version, lost touchscreen after updating to v12, used MSM to go back to a different rom (OS-11.2.4.4.LE25AA... don't remember the previous ones) and then updated to C65.
After rebooting to C65, I plugged by phone it that I got no response from either Windows 11 or from my phone. Swapped cables, swapped ports, rebooting both devices, uninstalled Oneplus drivers, rebooted and reinstalled them... nothing worked. Plugged in my LG V60 and Windows would see it fine. Put the phone into Recovery and tested with fastboot devices and the phone showed up fine. Reset the phone to factory... no change; Window would not need see it.
Reflashed the phone to the OS-11.2.4.4.LE25AA ROM via MSM. Booted up the first time and Windows saw the phone just fine and the phone gave me the connection type notification and began charging. Successfully tested file transfer and adb devices. Ran the first update... tested it and everything worked fine. Turned on Debugging to make sure that adb and fastboot worked... they did. Ran the C48 OTA update.
After rebooting, when I plugged in the USB-C Warp cable, Windows defects the phone as an MTP device (sm8350-mtp in device manager), but the phone did not see that it was plugged in (no charging, no notification). Turning on Default USB Configuration allows me to change it to other modes when plugging it in (File Transfer will even let me browse the phone via Explorer), and the phone will show in device manager as a Oneplus 9 G5, but the phone never indicates that it is plugged in and will not charge at all. Plugging the phone into a USB 2 or 3 port seems to do the same thing. Fastboot in recovery works fine. Turning of Default USB Configuration causes it to either detect as a generic USB Composite Device or as an MTP device (not sure how/when/what causes it to change). Charging and warp charging on a power brick works fine and it does show up in the phone.
Seems I am going in circles now and not sure how to get out of this cycle. Any suggestions would be most appreciated!
[TMO To Global] [No Dual-SIM Bug]
Requirements:- * Unlock Token * T-Mobile MSM Tool * OOS 11.2.10.10 and OOS 12 C.48 Global * Fastboot Enhance Instructions:- 1) MSM back to TMobile OOS11 and unlock bootloader through unlock token 2) Extract the payload file from...
forum.xda-developers.com
That will basically fix your problem. Just use le2115aa