Hello since some day, I have the following issue on my phone :
At some point, randomly, the phone freeze and reboot (it may boot loop one or two time)
No freeze nor reboot while charging
The phone is not recognized anymore when trying to connect thru USB (I tried with two different USB cable and with three different PC, one on windows 7, one on Archlinux and another on Unbuntu studio)
No USB access in system, bootloader (via fastboot) or in recovery (TWRP)
Code:
device descriptor read/64, error -71
So I suspect an hardware issue. If so, is someone already have this ? Can I fix it by myself ?
The phone runs ResurrectionRemix v5.8.3 with ElementalX kernel.
Thanks in advance for your help
Related
Hi,
So I got fairly sick of HTC's Android 6 update (Crazy amount of bugs) and decided to install CM-13.
A problem arose then when I tried to unlock my bootloader, the computer wouldn't detect my the one m8 in fastboot mode even with android studio and usb drivers installed or standard mode.
I installed HTC sync manager and still no good.
I tried different cables and different computers (one win 10 the other win 7).
When the phone is in standard mode and connected to the computer the usb symbol comes up and says charging only,
if i click on this and select file transfer mode the screen just greys out and stays like that until i click home/back.
This option comes up only once (I need to reboot to get it again).
I found another thread that says to install "AndroidHtcsync2.apk" I tried this and it didn't work.
Thanks
Maybe, like me, you have a broken USB port that will still allow charging but no data connection
assetttt said:
Maybe, like me, you have a broken USB port that will still allow charging but no data connection
Click to expand...
Click to collapse
That might be it, only thing is i was able to send files no problem a month or two ago before the update.
You need to be in bootloader-fastboot mode for fastboot commands; they won't work booted in OS or in bootloader (I think one of those is what you mean by "standard mode"?).
Other than that, Win7 is more reliable. And USB 3.0 is known to cause issues with USB connectivity on this phone, as well.
Sorry that wasn't clear. I was actually in fastboot mode when sending the commands.
The windows 7 computer I tried it in had USB 3.0 ports as well so that might be it.
However I wiped the phone after failing to flash CM and it fixed most of the bugs I was having trouble with so I might just leave it this way.
Thanks for the help
Guys my friend gave me his nexus 5x stuck in bootloop, tried to factory reset in recovery. Now the recovery is corrupted and device isnt being recognized by any pc, desktop, mac or linux in fastboot. In Windows it shows up as unknown usb device (device descriptor request failed). Can anyone suggest me a work around for this. Thanks in advance guys
Dug my old 2013 wifi 7 out to use on a project. Running a stock ROM, not sure of the version, rooted and unlocked bootloader. I screwed up something installing a new ROM and ended up wiping the system and data partitions. I'm trying to get a ROM onto the device so I can flash it. I can boot into fastboot and TWRP 2.8.6.0. Of course with no system it showed up as an unknown device. While doing the driver uninstall/install dance trying to get the naked driver set to work the tablet just stopped showing as connected to my windows 10 pc. Not like "unknown device" etc, no devices connected at all. Nothing shows on usbdview either. Tried plugging into a windows 7 pc, same thing, even tried a ubuntu live cd boot, nothing. Tried toggling MPT in TWRP on all these attempts. I can't mount USB OTG from TWRP I think its too old of a version. The tablet will charge so I don't think the usb port died. I'm out of ideas. Any suggestions before throwing in the towel?
Get the stable ROM for Flo. Stick Ubuntu on a decent laptop. Get a USB cable that's good for data and look at this instruction: https://itsfoss.com/restore-android-factory-nexus-7-2013-linux/
You want to Root look at this one and follow exactly: https://itsfoss.com/root-nexus-7-2013-ubuntu-linux/
Hi, I got this bugger for way too big price (40 bucks for non-working piece of garbage), but I needed it because nobody helped me with reflashing original Nexus 7 I botched up while flashing (can't even get to fastboot mode).
I need to resurrect it from death. Apparently, somebody was tinkering inside, one antenne lead is broken, USB port seems replaced with very wrong one (it fits, it sits, but clearly it is not original) and the main, biggest problem is that the OS is corrupted.
All I keep getting is Google logo, can't boot into normal mode, can't boot into recovery mode. Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)". When I try to manually install Universal Naked Driver, it keeps *****ing about wrong driver version or not compatible hardware. What I have to do to get it working except sending it to Asus and pay 5 times the tablet's price to get it fixed?
It was going to be replacement for that botched Nexus 7, but now it seems that it will cost way more...
Have you not tried the Nexus Root Toolkit by Wugfresh? I reckon you should give it a try good luck.
Yeah, that came around my mind too, but there is one problem. USB debugging was never turned on and now when I plug in the tablet, it shows in device manager as Unknown USB device (device descriptor request failed). And because there is no working communication (it doesn't show up as tablet), I cannot ADB DEVICES it, returns me empty list.
krivulak said:
Can get to fastboot interface though. But there is one problem - the USB debugging was never activated, so when I plug it into computer in fastboot mode, all I get is "Unknown USB device (device descriptor request failed)"
Click to expand...
Click to collapse
USB debugging on/off is relevant only in ADB mode and has no impact whatsoever in fastboot mode. Please boot it in fastboot mode, connect to PC and quote USB device descriptor number from device manager.
If it is 18D1:4EE0 then you have to resolve driver issues on your PC
If it is 0000:000x then you have to fix hardware problem in your Nexus
I posted more info in this and this thread.
USB Device Tree Viewer shows it as vid_0000&pid_0002, so there is hardware problem with the tablet.
So, if I understand it correctly, it can be caused either by badly seated cable or bad USB port. Sice the one that is there is clearly changed for the wrong one, I will try to order proper one and see what will it do.
By the way, I already tried to reseat the ribbon cable, no luck there.
Hi Team,
Asking you'r help regarding an issue im experiencing, i currently received a hand me down mi mix 2 from my cousin,
she is not techy and have not yet tried plugging it to a desktop/laptop, when i tried plugging it in on my laptop / desktop im receiving USB device not recognized
-charge function is working
on device manager it shows
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
I have a colleuge who has a mi mix 2 and on his it works fine.
so here are my troubleshooting that ive done
- Update driver of pc
-download fastboot and adb same thing
- tried 4 different usb cables (1 official cable, 3 3rd party)
- install miu suite (same error)
- check the USB health via some apps on android
-ampere
= usb host diagnostics shows no issue on hardware port
- Factory reset
- in settings - tried still did not works
- wipe data on recovery mode
- tried usb debugging same thing
-i even tried installing android auto then uninstalling it, (read it somewhere) but still failed.
- hope this is not a hardware issue
Have you tried on a different pc?