p5110 Unknown USB Device (Device Descriptor Request Failed) - Galaxy Tab 2 Q&A, Help & Troubleshooting

Hello.
So today i've decided to update firmware on my p5110.
It was already rooted and with cyan 10. I've installed TWRP 3.0.0.0 via CWM recovery and booted in TWRP. And then i chose Format data and it completely wiped out all of my files. I knew that, but i was thinking that i'll be able to flash ADB Sideload without a problem.
After that i've tried to boot into ADB Sideload, and nothing happened. My PC is not recognizing p5110. Sometimes it's showing notification "Unknown USB Device (Device Descriptor Request Failed)" in Device Manager, but most of the time it's not connected.
So, basically, now i have a tablet with working recovery, without any files on it and with no OS. I can't flash original firmware via Odin, and i can't flash it through ADB sideload, cause it's not recognized.
I reinstalled Samsung USB Drivers on my pc, installed ADB drivers and Android SDK, my other Samsung devices have no problems with USB connection, and the cable is fine.
Also, I have Windows 8.1 64 bit.
Is there any solution? Please, help.

I have exactly this same issue - running windows 10.
Following the CM installation instructions here:
https://wiki.cyanogenmod.org/w/Install_CM_for_espressowifi
Windows itself complains that the "device you connected to this computer malfunctioned and can not be recognised" and Zadig itself sees it as
"Unknown USB Device (Device desciptor request failed).
Any thoughts on this?
Cheers

cy80rg said:
I have exactly this same issue - running windows 10.
Following the CM installation instructions here:
https://wiki.cyanogenmod.org/w/Install_CM_for_espressowifi
Windows itself complains that the "device you connected to this computer malfunctioned and can not be recognised" and Zadig itself sees it as
"Unknown USB Device (Device desciptor request failed).
Any thoughts on this?
Cheers
Click to expand...
Click to collapse
install or re-install latest samsung driver from here
http://developer.samsung.com/technical-doc/view.do?v=T000000117

skyless_kingdom said:
Hello.
So today i've decided to update firmware on my p5110.
It was already rooted and with cyan 10. I've installed TWRP 3.0.0.0 via CWM recovery and booted in TWRP. And then i chose Format data and it completely wiped out all of my files. I knew that, but i was thinking that i'll be able to flash ADB Sideload without a problem.
After that i've tried to boot into ADB Sideload, and nothing happened. My PC is not recognizing p5110. Sometimes it's showing notification "Unknown USB Device (Device Descriptor Request Failed)" in Device Manager, but most of the time it's not connected.
So, basically, now i have a tablet with working recovery, without any files on it and with no OS. I can't flash original firmware via Odin, and i can't flash it through ADB sideload, cause it's not recognized.
I reinstalled Samsung USB Drivers on my pc, installed ADB drivers and Android SDK, my other Samsung devices have no problems with USB connection, and the cable is fine.
Also, I have Windows 8.1 64 bit.
Is there any solution? Please, help.
Click to expand...
Click to collapse
I found my old Samsung P5110 that i hard bricked a long time ago and i am having the same issue. It boots into download mode just fine, but i am getting the same error with the driver. Tried reinstalling the drivers but nothing seems to work.

Related

phone is only recongnized in bootloader and in system, but not in recovery

Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
david0916 said:
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
Click to expand...
Click to collapse
anyone?
david0916 said:
anyone?
Click to expand...
Click to collapse
There is no specific driver. Do you have usb debugging enabled?
I had to uninstall and reinstall drivers. Mine did the same thing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
david0916 said:
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
Click to expand...
Click to collapse
I have been having the exact same issue. Ive noticed that when I am in recovery and adb doesnt recognize the device, it seems like it is actually windows that doesnt recognize because i go into Device Manager and see Nexus 5 with an exclamation, and if I try to install the drivers for it, it says it cannot find the proper drivers in the same folder that i originally installed the drivers from!
I am very confused and this is pissing me off, because I should have the damn OTA already and I dont!!!!
david0916 said:
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
Click to expand...
Click to collapse
i am not rooted and do not have a custom recovery either. bur i had the same problem when i tried to side load update 4.4.1.
the problem for me was that the google usb driver that i installed did not have proper adb support for nexus 5. this is what worked for me. universal naked driver v. .73
downloaded and unzipped in a folder in desktop.
booted into recovery on the phone
windows chimed new hardware found, device manager showed nexus5 with an exclamation mark.
right clicked to update device software, pointed to unzipped folder, done.
this way after geting out of CMD phone is still recognized as MTP, so i can transfer files back and forth.
akmsr said:
i am not rooted and do not have a custom recovery either. bur i had the same problem when i tried to side load update 4.4.1.
the problem for me was that the google usb driver that i installed did not have proper adb support for nexus 5. this is what worked for me. universal naked driver v. .73
downloaded and unzipped in a folder in desktop.
booted into recovery on the phone
windows chimed new hardware found, device manager showed nexus5 with an exclamation mark.
right clicked to update device software, pointed to unzipped folder, done.
this way after geting out of CMD phone is still recognized as MTP, so i can transfer files back and forth.
Click to expand...
Click to collapse
just updated to 4.4.2 same way. except this time is was easier. no driver issue

tf700 not recognized by pc

I trying to flash my tf700 with a custom rom, since it's terribly slow and barely usable. I've unlocked the device with the asus tool. But when i'm trying to install trwp tablet isn't recognized.
I've installed sdk, naked usb drivers, asus drivers. But nothing works. Is there a way to flash a different rom with having to install a new bootloader?
Depending on what you have now, you may not have to install a different bootloader. But you do have to install a custom recovery and you need fastboot for that.
Driver issues in Windows are frustrating to solve, but don't give up.
1. Try a different USB port. I know, sounds lame, but it has worked for quite a few people.
2. Uninstall Asus Sync and all drivers you have tried so far. Also drivers for older phones/tablets you may still have
3. Try this cool little tool: http://forum.xda-developers.com/showthread.php?t=2588979
When I start the bootloader with powerbutton and volume down I see the following message, is this correct?
Key driver not found.. booting os
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.10-20130801" a03
Starting fastboot usb download protocol.
Yes, that is the bootloader screen and the tablet is in fastboot mode. Never mind the "key driver not found". That's also normal....
berndblb said:
Yes, that is the bootloader screen and the tablet is in fastboot mode. Never mind the "key driver not found". That's also normal....
Click to expand...
Click to collapse
I have tried several things, installed asus sync, sdk, google usb drivers and a different pc. Nothing works. Is there a different way to install a different rom?
UPDATE:
I did a new install of windows 7 and now my tablet is recognized by the pc. But when I try to install the twrp.blob file with the fastboot method, I get the error invalid argument and nothing happens. And again I'm having the problem that the tablet is not recognized by the pc.
UPDATE 2:
somehow I managed to flash twrp to the tablet after numerous invalid argument errors after using fastboot. I'm now running crombi kk.

SM-G920F - LCD broken - which boot mode?

ROM stock
Recovery TWRP
Hi all,
I would recover data from an s6 with broken lcd.
First time i connected it to pc via usb, it was recognized in recovery mode by adb.
I tried to access data with adb shell but no contents found in folder "data". I tought "no root permission?!"
So I installed TWRP recovery via Odin. Now, when i connect it to pc it's not recognized anymore by adb "no devices attached". I just can view "Samsung Mobile USB Composite Device" under device manager in windows and an error about MTP driver installation.
How I can determine in which boot mode is the telephone?
Could you suggest me a way to try to recover data, if present?
Thanks in advance.
additional info:
when i connect the phone to the pc trough usb, it takes about 15s being recognized by windows. next windows try to install MTP driver and it fails.
In Odin it appears "added" but if I try to flash a recovery it stucks on "setup connection"

Can't unlock bootloader, need help with drivers

I'm trying to unlock my bootloader to install a custom rom. "adb devices" command works fine but "fastboot devices" doesn't return anything. In windows device manager i haven't updated drivers because i dont know where to download them. Any help with drivers? I have an "android bootloader interface" option there but windows warns me that it might not be compatible and might break everything.
Download the Universal adb drivers from google
vuittion said:
Download the Universal adb drivers from google
Click to expand...
Click to collapse
I have done this, but it didn't help
enkerrohah said:
I have done this, but it didn't help
Click to expand...
Click to collapse
Download Tool all in one for flashing recovery and unlock bootloader. For One Plus 6. Check in XDA. Install necessary drivers. In developer option,usb debugging and file transfer for OTG.
sschacko said:
Download Tool all in one for flashing recovery and unlock bootloader. For One Plus 6. Check in XDA. Install necessary drivers. In developer option,usb debugging and file transfer for OTG.
Click to expand...
Click to collapse
Just downloading the adb drivers from google's own site made it work on another PC. I think my problem is that Windows has installed the wrong drivers for me. When i plug a device in for the first time, it says something like "setting up your device". I think during that point it installed wrong drivers on my own PC. On my brothers PC everything works like it's supposed to. Any idea how to get Windows to install the drivers again?
enkerrohah said:
Just downloading the adb drivers from google's own site made it work on another PC. I think my problem is that Windows has installed the wrong drivers for me. When i plug a device in for the first time, it says something like "setting up your device". I think during that point it installed wrong drivers on my own PC. On my brothers PC everything works like it's supposed to. Any idea how to get Windows to install the drivers again?
Click to expand...
Click to collapse
Problem persist when you try to install Drivers without valid signature in Windows 10.. Try to DIsable Driver Signature Enforcement..
Link to do it https://windowsreport.com/driver-signature-enforcement-windows-10/
Then try to install Drivers from this link :- https://drive.google.com/file/d/1L7EZGx5mgeQYXO19Vsp9FWu9GXhF45Qs/view
Let me know if that helps..
I have quit the same problem expected that i already have my bootloader unlock and usb debugging turn on...
im trying to flash twrp image, after failed yesterday to apply pixen os11. I had access to fasboot mode and to flash zip etc and my drivers was instaled but now my laptop didn't reconize my phone when plug in in fastboot and is on other devices in my devices manager. I tried to install updates manualy but nothing happened.
i dont know if it is related but i did update windows between my secon attempt to flash pixen os. Maybe the drivers were update in the same occasions ? Because a i have no others problems when my phone is boot normally and can acess to internal storage from my computer.

Install TWRP without USB

I have a Mi 9T Global 6/128GB running stock MIUI 12.0.7 Global with bootloader already unlocked. However the USB port has gone bad and only works for charging.
Is there a way for me to install TWRP without a USB connection?
Everything I've done and observed:
USB debugging enabled
USB tethering option greyed out - no USB connection detected
Default USB action set to MTP does not help
It charges but no prompt for USB mode when connected
Phone does not show up on PC
No new device detected in device manager
No problematic device detected in device manager in any mode
No device detected through ADB in any mode
No device detected through fastboot in fastboot mode
No device detected in miflash tool regardles of phone in system or fastboot
No device detected in miunlock tool regardless of phone in system or fastboot
No detected USB device on which I can attempt a driver update
USB drivers verified updated
Tried on my desktop and laptop, with multiple cables and ports
OTG with another Android device does not work
I was using RR Android Q when I realized this issue. At that time I was using TWRP and even in recovery with everything mounted and MTP enabled, the phone was still not detected on PC. I flashed the latest stable MIUI zip hoping it would be fixed bit no bueno.
I want to get TWRP back to install a custom rom because I refuse to use MIUI.
Any help will be greatly appreciated.
Because this phone doesnt have card slot my guess is you can't re-install TWRP.
Is your phone rooted? if it isn't then try rooting it with kingroot (I know it's bad, but you don't exaclty have any other option)
After rooting then follow this thread.
Briefly:
After rooting the device, install flashify.
Flash TWRP through flashify.
Do a factory reset to remove kingroot.
Download and flash your desired ROM.
I don't know if this method works and I recommend searching into it first before trying it.
If it actually works, don't forget to backup everything before flashing. Also once you flash there is no going back since Xiaomi devices has rollback protection.

Categories

Resources