Following the video
youtube.com/watch?v=TrP-IBuAeN0
I tried installing custom ROM.
Everything went fine till flashing 'boot.img' using flash tool. After the flash tool showed me a successful message i unplugged my device from the laptop,but I didn't get the menu(recovery- shown in video) even after 30 min..now when i am connecting my device in fastboot mode to re-flash the device the usb driver is not being recognized
with error message in the ADBdriver details
"This device cannot start. (Code 10)
A request for the USB BOS descriptor failed"
I even tried installing the drivers provided in the SONY website, it is not getting updated .... its showing an error
plz help me in fixing drivers issue
thanks in advance
Windows 8 64-bit? Follow this: http://flashtool.net/disabledrivers.html
Related
Ok so here is what happend:
I wanted to root my phone and I did the root fine with stumproot. Then i used autorec to flash the recovery. When i went to boot into recovery it got stuck in fastboot mode without download mode. I finanly got download mode but now I can't get the phone to show up device manager. I was having a issue with the ports but I finanly got that to show up but now all it shows up is communications port with a error.
The error is "Windows cannot determine the settings for this device. Consult the documentation that came with this device and use the Resource tab to set the configuration. (Code 34)"
When I plug in the phone to the computer in download mode it comes up with three options under other devices.
CDC ECM- The drivers for this device are not installed. (Code 28)
CDC Serial- The drivers for this device are not installed. (Code 28)
LGE Android Phone- The drivers for this device are not installed (Code 28)
I have tried uninstalling and re-installing the drivers. I have tried lg's official drivers and koushes universal adb drivers. Nothing seems to make it show up. Can someone please help me. I'm trying to do the restore to factory with tot files since i have the sprint variation. I'm not having anything other issues other than the phone not showing up properly in device manager! i have googled and googled and found nothing that helps. Thanks!
I am trying to downgrade my LG G3 VS98512b so I can root it. I am running Windows 7 Professional Edition in a VM on an elementary OS host. I am following this guide: androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
I have gotten to step 19, but I cannot get past the "Waiting for connection" stage. The device manager tells me "This device cannot start. (Code 10)." It does this shortly after FlashTool starts waiting; before that, the device is working fine.
I believe I have correctly installed all of the drivers I need, and I am using the LG connector that came with my phone. I have no idea what the problem is. Please advise.
I had that problem when you get to waiting for connection unplug usb lead from phone then reconnect it and it detects it and finishes the job.....
Sadly, that isn't working. When I try unplugging/replugging the first time, I get the waiting message. If I try again while the message is up, some more messages flash by and FlashTool says "Download FAIL!! (0 sec)." The other messages are
Code:
PID: NULL
IMEI: NULL
Model :
DLL : VS985
BIN : VS98510B_03.TOT
SWV :
SWOV :
Model Information Check FAIL!
00000000
This all happens within about a second of unplugging my phone. I've tried using a different USB port on my computer, and I've tried waiting varying amounts of time between unplugging and replugging my phone. While this is happening, my phone doesn't change at all; it just keeps the "Firmware Update" screen. I'm also using VirtualBox version 4.3.26, if that makes any difference.
I have the same problem !
Did u fixe it ?
Hi,
I am a local repair shop for phones, tablets, iDevices, laptops, pc's etc and I have a customer's phone here Galaxy Note 2 GT-N7105 that am pretty sure they have tried to flash it with some dodgy ROM and hard-bricked it. It is stuck in a boot loop so I can not boot into the android system to change anything in there. When I put it into download mode and connect to the PC (any PC/Laptop), windows says "The device has malfunctioned and windows does not recognize it". I have tried going into device manager on the PC and uninstalling the UNKNOWN DEVICE, then pressing "Scan for hardware changes' and letting windows try to install the drivers again but it immediately comes up "Driver was not successfully installed' and goes straight back to being an unknown device, so using the cable and Odin seems to not be an option. I also have the Samsung USB drivers installed.
This is what I have also tried installing from the SD card in recovery, however I am getting the 'E:signature verification failed' error on all of them:
~ Installing the firmware
~ Installing Clockwork Recovery
~ SuperSU v2.46 (this also gives 2 'Failed to verify whole-file signature' errors as well as the normal 'signature verification failed' error)
~ TWRP 2.8.7.0
I tried CWM because in my searching, I saw that if I install that, I can disable the signature verification, however I can not install that because I get the 'E:signature verification failed' error.
I am pretty much at an end as to what to do now.
Again to sum up:
~ Can't boot into Android system (stuck in boot loop)
~ Can't use the cable and PC (device not recognized/device malfunctioned/unknown device)
~ E:signature verification failed' error with anything I try to install from recovery mode
Does anyone have any ideas ?
Hi all,
I am still on Android 4.3 and have previously rooted my device. Trying to connect on a Windows 8.1 PC.
Recently I did a factory reset and now I get errors when setting up - "Unfortunately, Setup Wizard has stopped" - after the device name.
I am trying to unroot my device and upgrade to 4.4.2 but I cannot get the device recognised in download mode (power + volume down + home).
I have tried different USB cables, different ports and different PCs and the only difference is that all but one USB port shows the "device descriptor request failed" error in device manager. On one port I can see it when powered on and connected, and it is recognised in Kies and Odin. As soon as I put it in download mode I get an error and the device won't start and I get the "This device cannot start. (Code 10)" error.
I have nothing I need to get off the device, so am happy to try anything to get the device recognised so I can re-flash some firmware!
Any help would be most appreciated...
Thanks
ForrieDave said:
Hi all,
I am still on Android 4.3 and have previously rooted my device. Trying to connect on a Windows 8.1 PC.
Recently I did a factory reset and now I get errors when setting up - "Unfortunately, Setup Wizard has stopped" - after the Dropbox offer.
I am trying to unroot my device and upgrade to 4.4.2 but I cannot get the device recognised in download mode (power + volume down + home).
I have tried different USB cables, different ports and different PCs and the only difference is that all but one USB port shows the "device descriptor request failed" error in device manager. On one port I can see it when powered on and connected, and it is recognised in Kies and Odin. As soon as I put it in download mode I get an error and the device won't start and I get the "This device cannot start. (Code 10)" error.
I have nothing I need to get off the device, so am happy to try anything to get the device recognised so I can re-flash some firmware!
Any help would be most appreciated...
Thanks
Click to expand...
Click to collapse
Check make sure USB debugging is checked in Developer options and unknown sources in Security settings are checked.
buhohitr said:
Check make sure USB debugging is checked in Developer options and unknown sources in Security settings are checked.
Click to expand...
Click to collapse
Thanks buhohitr, I made sure they were checked and same errors.
I was wondering if it possible to load new firmware via the recovery menu? Like load the firmware onto sdcard or something?
Just trying to think of a way to flash firmware without a PC. I found a mobile Odin by Chainfire but this device is not supported.
Any thoughts?
------------
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