Develop Bugs

[Q] Help please

Hi,
Right, my A100 kept failing on auto update to new ICS with update failed. No ideas why so I manually updated using the update.zip method to ver 1.012. All working fine on ICS.
My two questions are :-
1) Is there a very easy way to update to ver 1.014 without losing anything on the tablet?
2) rooting. well, i'm following the method by zeronull (full root for a100 ics simple method) and it keeps failing at waiting for device. (the daemon method).
The tablet is accesible from windows fine so cables/drivers fine. The driver version is ver 1.000 as from acer website. I've followed all of the tips on the thread in developers forum. so.......
My tab details are :
Android - 4.0.3
Kernel - 2.6.39.4+
Image Version - Acer_AV041_A100_RV01RC01_WW_GEN1
Build number - Acer_AV041_A100_1.012.00_WW_GEN1
Image P/N - FM.S18A0.00D
Thanks

Download the stock ROM 1.014 from development section.
The method is the same (just put update.zip on the external_sd card), if you don't make factory data reset you will not loose your information.
For the rooting ... do you have 'check' on USB debugging?

yes, usb debugging is checked. (it sets it to that automatically tho)

ok, updated to version 1.014 all fine.
Now when I run 'runit-win' for ICS rooting i get :-
waiting for connect device
*daemon not running. starting it now on port 5037 *
*daemon started successfully*
Thats it..... now nothing.....

filking said:
Thats it..... now nothing.....
Click to expand...
Click to collapse
It's nothing because,the adb still waiting for device.Go through cmd to the ICS_rooting folder (from where you execute install-win.bat) and type : adb devices - You must see some number,if not you don't have the correct drivers or don't have USB debugging selected in settings.
Send from my A100

went thru cmd, the adb shows no devices at all.
debugging is def on. The drivers I am using are the ones from the uk and us acer site. redownloaded them and checked update drivers and the comp says the current driver is the latest.
But looking at the device when plugged in it says under driver details :-
Driver Provider - microsoft
driver date - 21/06/2006
Driver Version - 6.1.7600.16385
Now, assuming this is the wrong driver (it's the microsoft windows one), when i try to update driver it says the one i'm using is the best. Tried uninstall tablet, plug it back in, it automatically picks the windows one. grrr
I'm on Win 7 but also tried on vista.
Sorry for being a pain

Manually reload the acer USB driver
I had the same problem until I manually loaded the acer provided USB driver by running the acer driver setup

Sorry, but have you got a link for that Acer driver setup?

got it, thanks

thanks all, I now have up to date ICS and rooted. Thanks for all your help.

[ANSWERED] Unable to use ADB to connect CM10.1/driver issue

Hello,
I've been able to use ADB to install and test apps that I'm writing under the stock ROM for my Epic, as well as under CM9 (and I think an early CM10, not sure about that though). After installing the 20130101 build of CM10.1 (keeping the included kernel), I am having issues trying to deploy and debug apps from my any of my computer to the phone (all of which previously worked). I've verified that Android Debugging is still enabled on my phone.
In the device manager on my computer, "SAMSUNG Android USB Modem" and "Unknown Device" are both showing the "problem" icon. I've tried uninstalling and reinstalling various versions of the Samsung USB drivers, I've tried a few versions of Kies, and even a few third-party tweaked USB drivers. It doesn't seem like anything wants to recognize my phone now that is running CM10.1 (or CM10.1 in addition to something peculiar with my installation).
Additionally, if I have USB debugging enabled on my phone, even if I enable USB mounting, the computer won't recognize the mount until I disable debugging mode on the phone. Once I do that, then the volume will appear on my computer. Previously, when ADB debugging in general worked, I wouldn't have to disable debugging to get the USB mass storage mounting to work.
These problems happened at once on all three of my computers that I've been using for Android development, so I'm fairly convinced these issues are directly related to the ROM I'm running. I've attempted to search the forum and Google for others that may have had this issue and what the resolution/work-around might be, but so far I've not found anything. Surely other people are using CM10.1 and developing apps, which makes be believe it could be something unusual with my installations, but I've tried full wipe without a data restore and it didn't seem to have any impact. I've also tried searching to see if there were special drivers needed for CM10.1, and didn't find anything with that either. I know reverting back to an earlier ROM is an option to get ADB working, but I'm really hoping to get ADB working with CM10.1.
Does anyone have any suggestions on what I can check/do to get USB debugging working on CM10.1 (epicmtd)?
Thank you very much for your time
--James

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
I had the same problem, tried absolutely everything I could to get it to work and couldn't... had to roll back to a tw rom to get it to work (not a fan of the HUGE battery drain on cm9)
Edit- I know this doesn't help you, just wanted to point out you're not the only one with this problem....

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
jeffreyjicha said:
Locate the drivers for your phone on your computer and uninstall them. Then plug your phone in and let the computer reinstall the drivers. I had the same problem (although I wasn't making apps) and my suggestion above worked for me, so hopefully it'll work for you.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...

flastnoles11 said:
Tried this multiple times... it may have actually been a problem with my pc... get it back on Friday, so time will tell...
Click to expand...
Click to collapse
I've tried this with my previous uninstall/reinstall driver attempts, but tried it again anyway.
Unfortunately, it didn't' seem to have a positive impact. It looks like it reinstalled the mass USB storage driver, but it did not reinstall any other drivers (like the modem driver) so I'm still not able to do anything with ADB.

Re: [Q] Unable to use ADB to connect CM10.1/driver issue
Have you tried manually installing the drivers?
Here is the .exe that I used to install the drivers for my phone.
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
Have you tried manually installing the drivers?
Click to expand...
Click to collapse
Hello again. Yes. I've tried installing various versions of USB drivers floating around the net as well as Kies (after uninstalling and deleting current drivers to try to avoid conflicts). Other versions of Epic ROMs (Stock, CM9, etc.) worked with ADB using my installed drivers until I installed CM10.1 (maybe starting with CM10) on my Epic.
As an aside, using ADB requires some additional (special) drivers beyond the drivers required for mass storage support.
I'm hoping one of the CM10.1 developers will chime in with what they did and/or installed to have ADB working with CM10.1 on Windows 7.
Thanks!
--James

I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.

jeffreyjicha said:
I'm going to update to the most recent build of CM10.1 and see if ADB works for me. If it doesn't work, i'll try reinstalling drivers.
Click to expand...
Click to collapse
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.

samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
No problem.

samej71 said:
I don't know what I did differently in my search (I've been trying to find solutions for awhile now). I found this thread:
http://forum.xda-developers.com/showthread.php?t=1817954
I upgraded my Kies to 2.0, which includes the latest drivers from here:
http://www.samsung.com/us/kies/
I still had "Unknown Device" listed in my device manager. Based on that forum thread, I right-clicked on the "Unknown Device", selected "Update Driver", "Let me choose from software installed on computer" and then picked "ADB Interface". A list of a few Samsung ADB entries in it appeared, and I picked one (I had two with the same name, so not sure what the differences are between them) and after a few seconds I had no more alerts in the device manager and when I run "adb devices" I now see a device in the list. I fired up Eclipse to give it a real-world test and it worked: I'm now able to deploy and debug apps on my connected device.
Woot!
I'll be taking these actions on my other computers tonight.
Thank you very much for your assistance.
Click to expand...
Click to collapse
Activating through developer options doesnt help? just go to about phone --> tap build number 7 times

I just went to device manager, uninstalled the failed USB device, and then plugged the phone back to the computer via USB.
Boom, just like that, all was well.

i tried everything and could not connect to my htc rezound (w/ CM10.1) thru adb. then i tried the following:
1. download the android adk from google (i can't post links)
2. connect phone thru usb
3. on your computer's adk download folder, navigate to sdk\platform-tools\
4. press shift + right click on the window, open command window here
5. type "adb devices" in the command window w/o the quotes
6. there should be a window pop up on ur phone asking for USB debugging permission. say OK.
7. type "adb devices" again and you should see ur phone connected thru adb.

adb fastboot driver problem

Hi,
i tryed to get the Desire working with adb and everything works fine. I downloaded HTC Sync, installed only the drivers, and the adb interface worked with the Desire. But if i reboot in bootloader and use fastbootinterface it doesn't work.
fastboot devices get no result.
I downloaded unrevoke modified drivers, i also tryed to uninstall HTC driver and install only the modifed drivers. I also tryed to use this drivers:
http://forum.xda-developers.com/showthread.php?t=1161769
but always the same problem:
The device manager shows adb Intreface and there the HTC bootloader, but with and yellow !. properties of the Device shows me following error:
original Error log said:
Das Gerät kann nicht gestartet werden. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Translation in my own words: said:
The devices can not be startet (Code10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
And i installed the drivers correctly. So with settings, reboot and tha with deactivate the driver signature.
I hope you can help me

You should uninstall everything and start from the beginning. HTC sync clearly messed something up.
First, try to reinstall hboot drivers.

allready tryed but i get the same error.

google "the devices can not be started (code 10)"
happened to me before, its a windows problem. u have to delete something , cant remember what tho.

i uninstalled every thing desire also the not shown devices in devices manager. than i connected the desire in fastboot with pc and the pc gets the driver from alone. But with the error.
Thanks for the tip with the delete something. but the only results i find are something about reinstall the driver, update the driver, uninstall the driver, ask the support of the device -.-
Do you know maybe a link word what i need to delete? is it a file, an old driver,...??

http://www.google.com/url?sa=t&sour...9oGABg&usg=AFQjCNH1CYaPX1ZheHJ-vYr2Y3GDNFFvWw
try here, the thing that worked for me was deleting somthing in the registry.

thank you very much i'll try it

Just found the time to read the link.
One question? I looked for the Device Class GUID for USB. But there is no lowerfilter and upperfilter. What class is the desire?

I got a similar problem on my workstation, I got an Android Phone in device manager and nothing else, I'm not able to connect and mount desires SD Card. Windows 7 x64, on my laptop (same os) everthing works fine. My PC recognizes desire only with drivers from Android SDK software.

i think your problem is a bit diferent. Do you have a custom ROM installed?
If you did and it is an android 4.x ROM there are many Problems with USB mount. Try an app to mount the SD Card.
Back to my problem. I readed all of the site from up to down and than i deletet the Keys. After Reboot 2 times i got the bluescreen -.- after that the autorepair startet it selfs. the first couldn't repiar the system, and the second couldn't either. So i needed to reinstll windows
The good thing with this is There is difently no HTC on the PC anymore. So in what order i need to install which drivers to get the Desire in Fastboot connected?

A the moment I'm using CronMode 2.1 (previous CM 2.0, SpazeDog ICS, BravoBCM). On previous roms (all ICS based on CM9) got same problem. Laptop - ASUS S6F, Windows 7 Pro x64 - phone recognized, usb mount working fine. Desktop - Gigabyte P55-UD3, Windows 7 Pro x64 - just got Android Phone in device manager and that's all.
What app do you mean?

Try Usb mass storage toggle form the market.

Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).

nonline said:
Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).
Click to expand...
Click to collapse
You may have a usb brick. Try the "usb unbrick" option in recovery

abaaaabbbb63 said:
You may have a usb brick. Try the "usb unbrick" option in recovery
Click to expand...
Click to collapse
So why other PC/Laptopts recognize my phone proper?

nonline said:
So why other PC/Laptopts proper recognize my phone?
Click to expand...
Click to collapse
Ok then... reinstall your OS on the PC. If your tried everything, it's the last solution I can think of.

You can first try to reinstall the Driver.
Back to my problem in what order do i need to install the drivers for fastboot?

I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.

nonline said:
I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.
Click to expand...
Click to collapse
Some firms disable this ability and also SD card reading for security purposes. That can be only reason i can think of.
Sent from my HTC Desire

I'm also a sysadmin of this machine, so you can belive me, just a build-in firewall and security essentials as antivirus protection software.
My wife's Desire S shows the same problem. I think it is a driver issue. Can someone recommend a single "htc desire driver" for Windows 7 64bit?

[Q] my laptop doesn't recognize my phone (flash mode & fastboot mode)

my laptop does not recognize my phone in either flashmode or fastboot mode, i tried sing pc companion and flashtool drivers but it does not fix the problem. maybe im doing something wrong, can you guys help me in step by step?
Phone: Xperia Arc S
Version: 4.0.4
Build: 4.1.B.0.587
Computer
OS: Windows 8 (64bit)

http://forum.xda-developers.com/showthread.php?t=2044804

still not working for me

Do you see any error, installing the drivers? What was the the status in the flashtool?

Cibhin said:
Do you see any error, installing the drivers? What was the the status in the flashtool?
Click to expand...
Click to collapse
there's no error in installing the drivers, the status is "device not found"

Phone [Q] my laptop doesn't recognize my phone (flash mode & fastboot mode)
Try this:
(1) Go to device manager
(2) Plug phone in and look for any changes in your list of devices (maybe under other devices) should have a yellow box with exclamation mark
(3) Once found right click then click browse my computer for driver software (point to the folder where drivers are)
(4) Install from there make sure driver signature is off like instructions above :good:

Use this ( View attachment driver_androidusb.zip )... It will work for Arc S and Other
click Thanks if I Help

still not working...
here is the device status...
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.

try to uninstall any Android Emulator programs you have

Check also if both ends of the usb cable are properly connected and intact to phone and laptop.

Install Android SDK, open it, install all drivers with it. That should do the thing, if I remember correctly.
Sent from LT18i with custom firmware by myself.

Someguyfromhell said:
Install Android SDK, open it, install all drivers with it. That should do the thing, if I remember correctly.
Sent from LT18i with custom firmware by myself.
Click to expand...
Click to collapse
how do you install the drivers using android sdk?

If it's possible for you and not too painstaking, try and format your system, and then do a fresh install. Worked for me when I had a similar problem in the past.

MarcSinger said:
If it's possible for you and not too painstaking, try and format your system, and then do a fresh install. Worked for me when I had a similar problem in the past.
Click to expand...
Click to collapse
i think ill do that, i have tried almost everything but nothing works

so what now? working?
My laptop will not recognize flash mode.
Its not driver problem its keep usb not recognizing.

Help GNex has no OS and won't connect to a PC!

Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???

I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.

Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
stargazer127 said:
Windows 8.1; but had same problem with Windows 7 computer.
USB device not recognized
The last USB device you connected to this computer malfunctioned. And Windows does not recognize it.
Windows has stopped this device because it has reported
problems. (Code 43) A request for the USB device descriptor failed
Tried using WUGS Toolkit to install drivers, not happening.
The phone charges via usb port with no problems
On top of that, daughter wiped phone, there are no ROMS, or usable backups.
I can get into TWRP Recovery, but it can recover what isn't there. Tried factory
reset, still nothing. No matter what I do, I get No OS Installed! Are you
sure you wish to reboot? If I do reboot, just get GOOGLE screen with lock
symbol.
Without being able to get a computer to see the phone, I can't get a ROM to
load.
Maybe change USB port with cable? But I don't want to do that if the problem
is software related.
Any ideas what I can do???
Click to expand...
Click to collapse

isajoo said:
I just went through something similar like this last week, what a pain in the A$$.
Not entirely sure if this will fix your issue, but hopefully it'll help some how.
I ended up having to manually install galaxy nexus driver so I could sideload a ROM since I formatted my internal storage to test out this new F2FS BS... Anyways.
LOL
First you'll need to download and unzip "universal naked driver 0.72" Google it.
Now, without your GN connected open device manager and THEN when you plug in your GN to your PC you should see it pop up in the portable devices section.
AND also under other devices there should be "galaxy nexus" right click on it and click "update driver software"
Click "browse my computer for driver software" select the unzipped universal naked driver folder, click next and click "install this driver software anyway"
Now it should show "Google galaxy nexus ADB interface" in device manager under Samsung Android Phone.
Reboot GN into bootloader
OR
recovery (if you have a ADB supported recovery eg. TWRP 2.7.0.0, and enter ADB mode)
Now there are 2 ways to do flash an Android OS, some may find 1 easier then the other:
download/install "Wug's Nexus Root Toolkit aka NRT v1.8.3.sfx"
Google it.
Run NRT and it'll instruct and guide you through the steps required and whatever is needed to continue, eg. Select device, download TWRP 2.7.0.0...ETC.
Or
Download/install ADB setup 1.3
Google it.
I found this method a little more simpler.
Open the folder you have your ROM/gapps zip files saved on your PC, hold down shift key and right click on the folder, click "Open command window here"
Now in the command window type in "adb sideload XXXXX.zip"
XXXXX = COPY/PASTE the ROM file name. Eg. 20140615PA443RC2.zip
Press enter and now it'll flash the ROM onto your GN.
Repeat the same steps for gapps/kernel zip files.
Reboot your GN and enjoy.
BTW
I'm still loving running ParanoidAndroid Jellybean 4.1.2.
Click to expand...
Click to collapse
OK, downloaded universal naked driver 0.72, connected gnex, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, and will not allow install of of universal naked drivers, & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?

KingWickedd said:
Its like pain in the A** to install phone/adb drivers in win8/8.1
I had a similar issue with my gNex a while ago but i had the drivers installed in my pc so it wasn't that difficult.
Why don't you try to install this toolkit http://forum.xda-developers.com/gal.../gnex-toolkit-v11-1-0-drivers-backup-t1392310
When you run the toolkit, it may ask you to select your device, build number etc and also about installing device drivers.
Install the drivers through it and then connect the device in recovery (twrp) mode.
it should detect it and then you can push files/roms to sdcard (internalMemory) using adb push or the built in options in the toolkit.
then flash the rom and you're done
and i recommend using win7 or xp or vista for doing this because the driver installation in win8/8.1 is a bit difficult compared with other previous windows versions but there is still a way to install drivers in win8/8.1 its just a lengthy process
All the best :good:
Click to expand...
Click to collapse
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?

stargazer127 said:
OK, tried this too, but it only shows up under Universal Serial Bus controllers as Unknown USB Device (Device Descriptor Request Failed), not under Portable Devices, tried 1st way by installing drivers, then using PDA, cannot complete PDA driver installation because it can't see the phone. & yes I have toggled to allow win 8.1 to installed unsigned drivers. Since I cannot get phone to turn on to full android, it is not recognized. Any other suggestions?
Click to expand...
Click to collapse
You have to go to the device manager, double click on the "unknown usb..."
a dialog box may appear and then click on the 'driver' tab.
There u may find update/install driver button.
click on it and another window may open.
then select browse my computer for driver software and go to the respective folder where the drivers are.
then click next and it may install the drivers.
if you have installed the toolkit then you may find a folder in the toolkit's installation folder which has drivers in it.go through it if you want :good: