Related
Hey guys,
When I bought my Omnia 2 with WM 6.1 on it, it worked great but when I went and installed the stupid PC studio software that came with the phone I tryed to update and now my phone has either a thing saying
"DOWNLOAD MODE!
Do not turn off.
It takes about 10 minuites."
or it will have a symbol of a phone connecting to a "!" next to a computer symbol.
I can no longer use this phone if anyone can help me it would be very much appreciated.
Thanks.
hahaha to funny bricked means it no longer turns on meaning you don't even get the download mode. its just like a useless brick. But anyways to the problem at hand, there is only one way to brick the omnia and that is if you flash the eboot which you have not done since it still works and turns on.
Unplug from USB cable and turn it of and/or take out the battery. Put the battery back in and plug it into your PC and try to update it with PC studio and see if it works it should not have an issue. Repeat the steps if it fails but this time start PC studio first and then plug in the omnia and see if that works.
If all else fails you need to get OCTANS and download the official firmware for your region or a custom firmware if you want. I'm assuming you have a I8000 which OCTANS is used to flash don't know if that is the case with other omnia 2 as well. Visit this site and look for OCTANS and all the firmware you need. Since you are flashing anyways i would recommend you flash JD3 ROMS so you have the latest. Either go official ROM or go Lite i myself am using tw2 lite ROM.
I went to that site and nothing on there says anything about "OCTANS" so could you possibly give me a link of some sort to what I need.
I've tried running PC Studio on XP and Vista with no luck on getting the computer to even see the phone anymore so I've just about given up on the whole thing.
heavywater said:
I went to that site and nothing on there says anything about "OCTANS" so could you possibly give me a link of some sort to what I need.
I've tried running PC Studio on XP and Vista with no luck on getting the computer to even see the phone anymore so I've just about given up on the whole thing.
Click to expand...
Click to collapse
Here is the Octans Downloader's latest version. Just run it (If you are using Windows Vista or 7, set compatibility mode to Windows XP SP2), select the appropriate parts in various slots, click Detect Device and then turn off and plug your phone into usb cable. It will detect the phone, then just press Start and wait for the process to complete.
In addition to these steps, you might also need to update activesync drivers and install Samsung CDMA Modem drivers if you are using Windows 7 or Vista. For more details, see this thread :
http://www.modaco.com/content/b7610-omnia-pro-b7610-modaco-com/299070/tut-flashing-rom-using-octans/
I hope you get back your phone soon!
Good luck and Cheers!
same problem - cannot flash: the phone is stuck with an image of a mobile device, a pc, and a (!) sign in between.
unable to hard reset, unabe to flash - octan does not detect the phone...
any chance to save my phone?
1. get the ROMs from modaco site.
2. Start Octans and follow the ROM update guide in modao.
3. Click detect in Octans.
4. Power off phone (remove battery and insert back in ur case).
5. connect phone to PC/laptop (do not use any usb hub).
6. u shd see the download button becomes ungrey. click it to flash.
the download button remains grey......
what OS are u using?
If it's vista or win 7 and whether it is 32bit or 64bit.
The solutions are at modaco.
i read modaco.
the device is stuck: when i turn it on, the screen shows only one image:
an image of a mobiel device, a pc, and in between a (!) sign.
cannot hard reset device, cannot do anything.
am using vista, and followed all protocol from modaco (first time was able to flash - thats how the device got bricked).
octans (or the pc) does not detect the device when i connect it to the - that is the problem...
OK I now have installed the CDMA drivers and i'm running OCTANS in XP SP2 mode what OS should I download to use with the phone and how big will it be?
Thanks so much for the help guys.
And btw is there any versions that will keep the samsung virtual keypad and things like that (not the damn cube though)?
like i menchioned get a lite ROM I use tw2 ROM's Garys are good to. I like tw2 ROM because they are totally stipped ROMS except for samsung dialer and SMS and he gives cabs of all the apps so people can restore what they use. Garys is also very nice lite ROM with the basic apps that mainly everyone uses. Its your choice really what you want you can install the JD3 stock ROM as well, but why? when these lite ROM's giuve you more RAM.
As for drivers you may need to search on the site i don't have the links because there are new updated drivers for windows 7 which should work on vista too. When using octans make sure to hit detect and then plug in the phone (phone must be off) then click start. You only need to flash the PDA unless other parts messed up during the update, you won't know till you flash.
Driver installation:
1.) Turn off Phone
2.) Plug into PC
3.) Let it install the default drivers
4.) Go into device manager
5.) Go under the phone menu
6.) Update drivers and follow the steps and when asked which location point to the driver you just downloaded.
flash i8000
PROBLEM-HEPL pls..
cannot flash: the phone is stuck with an image of a mobile device, a pc, and a (!) sign in between!
unable to hard reset, unabe to flash - octan does detect the phone, but flash phone image and error (the end)
octan write: [Setup:0] PDA Device removed.
[Setup] Windows XP
[Setup] Download Ram Size :41777920 bytes,(39 MB)
OnDeviceChange \\?\USB#VID_04E8&PID_6619#5&ed04620&0&4#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
[Down] CSC Image.
[Down] MoviNAND Image.
[Down] Phone Image.
[CSC:0] Download start 0x0
[CSC:0] ----------------- Information of Multi CSC Image ------------------
[CSC:0] Verision:[I8000ATOIJ8]
[CSC:0] SalesCode:[ATO]
[CSC:0] Priority:[0x1]
[PDA:0] LANG_ID:[7][0405]
[Phone:0] Download to 0x0
[Phone:0] StartOffset: 0
[Phone:0] EndOffset: 16777216
[MOVINAND:0] Download start 0x0 and all!! :-(
I have win 7 32bit..driver install from modaco..octans (setting XP service pack3), restart..but cannot flash..HELP please? Soory, my bad english...
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Hi,
standard HTC driver works fine for me on windows8 64bit.
Adb, fastboot, no problems, what is the difference to this driver?
Cheers
starbase64
Gesendet von meinem HTC One mit Tapatalk 2
This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
backfromthestorm said:
This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices.
Click to expand...
Click to collapse
^^^^^^ This =)
1wayjonny said:
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
Click to expand...
Click to collapse
Does this version include support for the ASUS TF300 and TF700?
Thanks!
I hopes nexus 7 is added as well
Sent from my Nexus 7 using Tapatalk 2
yiwsg said:
I hopes nexus 7 is added as well
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes at the moment this works with over 250+ devices. Adding more when I can.
I can't get this installed for my HTC One.
I uninstalled every USB driver I had installed. Plugged my Galaxy 8 back in, and updated one of the drivers to use these after downloading.
I tried ADB on My Galaxy 8 and it worked.
No matter what I try to remove, and install, or update the drivers for the HTC one I can't get it to go.
It says "the folder you specified doesn't contain a compatible software driver for your device. if the folder contains a driver, make sure it is designed to work with windows for x64-based systems.
Any advice?
Thanks
I just manually install the appropriate driver (adb and fastboot for the respective devices dected in each mode) from the android SDK and ignore the warnings about it not being designed for this device. It works perfectly. I've done this with every android phone I've owned. Are there any benefits to doing this vs that?
--Matt
mkosem said:
I just manually install the appropriate driver (adb and fastboot for the respective devices dected in each mode) from the android SDK and ignore the warnings about it not being designed for this device. It works perfectly. I've done this with every android phone I've owned. Are there any benefits to doing this vs that?
--Matt
Click to expand...
Click to collapse
That will work too, Universal Naked Driver helps with a few aspects:
1) East to find and download
2) SDK Drivers will not work with APX Tegra devices, these do!
2) Works with over 250+ devices
3) Nothing needs to be installed ever such as *.exe's or even the SDK.
4) These are becoming a standard on Windows as they are integrated in most root / tool kits as well, racking in well over a million downloads
Most people will not even want to install the SDK, then Java, etc...
Hope this helps
mkosem said:
I just manually install the appropriate driver (adb and fastboot for the respective devices dected in each mode) from the android SDK and ignore the warnings about it not being designed for this device. It works perfectly. I've done this with every android phone I've owned. Are there any benefits to doing this vs that?
--Matt
Click to expand...
Click to collapse
I'm going to try this, seeing as how this universal driver did not work, and no one replied to my message. :good:
1username4thisforum said:
I'm going to try this, seeing as how this universal driver did not work, and no one replied to my message. :good:
Click to expand...
Click to collapse
I've never had it not work, even on the tegra2/3 devices I've owned. Just make sure you pick the right driver when the phone is in each mode, and it'll remember it the next time you connect it and/or the next time you're in that mode.
--Matt
mkosem said:
I've never had it not work, even on the tegra2/3 devices I've owned. Just make sure you pick the right driver when the phone is in each mode, and it'll remember it the next time you connect it and/or the next time you're in that mode.
--Matt
Click to expand...
Click to collapse
i get under adb shell device not found debugging is enabled
AllusionPDX said:
i get under adb shell device not found debugging is enabled
Click to expand...
Click to collapse
And you see the device without any issues in in device manager? Is USB debugging enabled? Do you have the latest version of the SDK's driver?
I've used this method on every android device I've owned, this one included (on aosp and sense ROMs) without any issues.
-Matt
Thanks for posting this OP
I added it to my FAQ Guide Q26
bigdaddy619 said:
Thanks for posting this OP
I added it to my FAQ Guide Q26
Click to expand...
Click to collapse
Your welcome!
don't work on win 8.1 Pro x64
starbase64 said:
don't work on win 8.1 Pro x64
Click to expand...
Click to collapse
Same hete, PC wont detect my HTC ONE. Is there any solution found yet?
new driver on HTC page works with Windows 8.1, but not in fastboot
It doesn't work in fastboot mode for Windows 8.1 Pro. Saddd!!
Hi there
I have seen some posts where users are having difficulty connecting Xperia to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone to the PC and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
Sony Xperia Drivers for ADB.
DOWNLOAD FROM HERE
reserved
it works on win 8.1?
jatinrungta said:
it works on win 8.1?
Click to expand...
Click to collapse
No,I dont know who reads this tutorials anyway wnen there already 10 of them for this particular issue.
Sent from my Xperia U using Tapatalk
XperianPro said:
No,I dont know who reads this tutorials anyway wnen there already 10 of them for this particular issue.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
true that, thought it would work beacuse it is posted this week
XperianPro said:
No,I dont know who reads this tutorials anyway wnen there already 10 of them for this particular issue.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
jatinrungta said:
true that, thought it would work beacuse it is posted this week
Click to expand...
Click to collapse
These drivers are seem to work perfectly on Windows 7 and it should work just fine on any other windows!
Hnk1 said:
These drivers are seem to work perfectly on Windows 7 and it should work just fine on any other windows!
Click to expand...
Click to collapse
nope, windows 8+ is different
I'm getting a lot of problems with drivers for this device, seems Sony's guys did it just to say:
"Ok, now this device got some drivers, lets play poker :"
It's serious. To get ADB driver working was a lot of work, just got it working because our friend Ashu1307 posted this link for me ( maybe it can work for ya= http://forum.xda-developers.com/showthread.php?t=2552505)
Ok, that's nice since it was the only driver that's not working on windows 7.
I said windows 7
Now I'm on windows XP, tryied 2 machines already, and this goddam piece of **** don't have any driver working. Nothing, neither MTP, nor fastboot nor ADB nor flashmode (mass storage works, the ones I've quoted are detected, but don't work)
PC companion is another thing I'm hating. First I have to download the Web Installer, 27MB of nothing, since after the download it has to update because the sony's website offers outdated file. THen I download support zone, which detects phone but not the model.
What do I do? I'm going weird just about to break this phone on the wall, I never had so much problems on motorola's or samsung's or enen old sony ericsson's devices.
Before,my PC used to display an error whenever I tried to transfer files from my pc to my Xperia Sola.But after changing the kernel,I could transfer files with ease.So,do you think the problem in the kernel is related to this error?
I never had problem with drivers.
Trying another computer, still having the problems, I use the DoomKernel, do you think it has to do with it ?
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hello. I've got A700 and I'm trying to root it but I've got a problem. I tried it with every key combination (power, volume up & down) I found on the internet but they don't work.
I also tried it when using the USB port but my PC and my laptop won't recognise the tablet. I've downloaded the drivers from Acer but when I install them my PC asks to install NET frameworks 2.0.5727. This version is no longer available but Frameworks 3 also worked according to Microsoft. After this installation the drivers from Acer still don't want to install. Then I tried it with Android USB driver but the same problem keeps coming back.
When I plug the tablet on my PC and look in the windows device manager there is a yellow triangle on the USB port with an error code 43. I've got the same problem and errors on my laptop. They both work on Windows 8.1. Could it be that the problem is on my tablet's USB? There is no problem when charging.
Does anyone have a similar problem or maybe a solution?
I have this problem too for my Acer a700. When I connect the tablet, i can't see the folders on the tablet via the pc anymore. I can't put files on it, and I can't transfer files from the tablet to the pc.
I contacted Acer and they said that windows 8.1 uses a new way to deal with usb drivers.
I will translate (google translate) from dutch to english
Dear customer,
*
Unfortunately, Windows 8.1 handles the USB drivers differently than Windows 7/8. So there are specific drivers for Windows 8.1 required that we can not supply at this time.
We have made a request to check whether these drivers are still going to be mad.e At this moment we can not specify the period within which we as a reaction to get going.
Until then you might try to work with the following generic driver: http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Note that they are not specifically designed for the Acer tablet and we can not provide support for the things that are discussed there.
Following the instructions is at your own risk.
*
As soon as we have more information about the Windows 8.1 driver, we will inform you about it.
*
Hoping this provides you with sufficient information and we apologize for the inconvenience
Any update. I have same problem running window 10.
alan0923 said:
Any update. I have same problem running window 10.
Click to expand...
Click to collapse
got it to work in windows 10. Driver issue. Just have to select driver in the device manager.