So, I have a Nexus 5x (32gb) which had the bootloop of death. I flashed the correct boot.img from the BLOD thread. I have done this a few times on 16gb versions with no issues. However in this instance the phone decided not to reboot.
All I'm left with is a device which can't load anything. No bootloader, no download mode, nada, nothing.
However, when I connect the phone to my computer, it recognises the device is connected. But it's not in adb or fastboot mode and the device manager only shows Unknown usb device (device descriptor request failed).
Any and all help appreciated, thanks
Related
Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end.
p.s. I have looked through other threads and even posted this message on one of the threads but recived no replies, hence the new post
Google splash screen = not bricked.
Power+DownVol from a power-off state...does this boot you into odin?
If so...flash an odin file.
You'll lose all of your data/sd contents =/ but at least it'll boot.
But the fact that you can boot into "fastboot" but not access it is bothersome to me.
Have you used fastboot before? (not a toolkit?)
It really SHOULD recognize...
In ODIN mode in shows the droid with a 'downloading...do not turn off target' message however i've left it in this state for hours and nothing happens, I cannot access it from my laptop either to push files to flash etc.
Data appears to be completely wiped from the handset
install the adb drivers http://pdanet.co/bin/PdaNetA302.exe (32bit win 7) or http://pdanet.co/bin/PdaNetA302x64.exe (64bit win 7)
and try fastboot devices after it has been installed.
I can't get into the device to activate USB debugging though?!
try this then.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Wait...
Are you just leaving it in odin mode?
You have to plug the phone in and use the program "ODIN" to flash a stock image.
Just making sure!
------------
the problem is solved i just don't know how to delete this thread
-----------
in fact the device is still not yet recognized under twrp but does work under bootloader mode, it's just it's not adb connection but fastboot connection that i got confused
for anyone who have a similar problem, you might find it helpful in the following links that i tried before i realized my stupidness...
http://sciologness.com/download/903...-configuration-descriptor-request-failed.html
http://adbdriver.com/downloads/
http://developer.samsung.com/technical-doc/view.do?v=T000000117 // this is the samsung page, but after installation you might find in your usb driver compatibility list something like "samsung adb interface" and that might do the trick
--------------original post-----------------
hey guys,
i just followed this page to root my device
http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
everything went fine until i flashed the xceed kernel.img for my stock rom...
and when booted into twrp and connect to pc meanwhile, the tablet it's not recognzied via usb anymore, and it says 'unknown usb device' error code 43. the tablet can either be rebooted into the system or recognized under the bootloader mode
i tried to install the google usb driver manually but it says
'This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)'
anyone please help
i don't think it's the problem of my cable or the connecting ports...
my os is win10 64
thanks all
G
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
I'm having trouble connecting my phone to my PC to transfer files. The phone never seems to register on windows, there are no "device inserted" sound at all and the phone is not listed in the device manager. On the phone, it is not even showing the little notification to change USB mode from Charging to File Transfert. Even in the settings directly, the option does nothing. Latest Google USB drivers are installed.
When the phone is in the bootloader, it shows up in the windows device manager with "Unknown usb device (device descriptor failed)".
I've tried multiple PC and cables, rebooting in safe mode, same thing!
I'm running TWRP recovery with stock ROM and ElementalX kernel, might that be an issue ? Thanks
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.