Database Info

Fastboot not working with windows 7 beta

I recently crashed my vista hard drive and decided to give windows 7 a try, its working wonders right now. The only problem is that I'm trying to put Nandroid back up on my computer again. I am at the step of trying to get the fastboot loader. It worked on Vista, but now it is saying that the "Driver is not intended for this platform." Is that due to windows 7? Is there a work around for this? Any help would be amazing, thanks.

I used Fastboot on Win7 7100 build yesterday, and it worked fine. Did you set everything up according to this post:
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
This is all that I did, and everything worked flawlessly. Good luck.

hmm..yeah, i did do everything according to the tutorial exactly, do you have email, aim, gmail, etc? could you help me?

use the newest driver in this SDK..
http://developer.android.com/sdk/1.5_r1/index.html
If you dont see the ADB Device or whatever its called in the device manager you need to delete a generic volume and scan for hardware changes.... HTC talks about it here. I had to do it also...
http://www.htc.com/www/support/android/adp.html
Troubleshooting
fastboot.exe (on Windows) doesn't detect the ADP device properly
In some cases, Windows detects the ADP1 bootloader as a USB mass storage device, preventing fastboot.exe from accessing it. To resolve the issue, you can dissociate the USB Mass Storage driver from your ADP1 on your Windows machine and install the proper driver instead, as described in the steps below:
1. Boot the device into fastboot mode, as described above, and connect the device to your machine over USB.
2. Navigate to Start > Control Panel > System > Hardware > Device Manager > Universal Serial Bus Controllers. Observe that the ADP device is listed as a USB Mass Storage Device.
3. Right-click USB Mass Storage Device and select Uninstall. Windows then prompts you with a "New Hardware Found Wizard" message. If Windows doesn't prompt you, you can manually re-detect devices by selecting Action > Scan for hardware changes.
4. Install the USB driver included in the Android SDK, as described in Setting up a Device for Development on the Android Developers site.

thanks southsko, i'll try this and let you guys know how it works.

I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?

When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?

i had the same problem earlier tonight, i figured since i was running win7 i might as well try using the virtual xp out. I started the VM up and the attached the phone using the drop downs and it worked flawlessly.

yup .. it's working fine for me too.. if you are using 64 bit version ... u need to use the 64 bit usb driver too... u can get it here
http://forum.xda-developers.com/showthread.php?t=446274
Also you may have trouble installing it in Windows 7 unless you turn off driver signing at boot menu. Hit F8 and select no driver signing and you should be able to install it no problem... u will also have to disable driver signing each time you plan on using adb/fastbboot

foxlin said:
I tried your method Southsko, but it didnt work for me. I think the problem is that windows 7 refuses to install the driver for the htc dream, because its not "intended for this platform" is there a way to force it to install the driver? or manually install the driver?
Click to expand...
Click to collapse
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.

trmacdonal said:
When I wrote that tutorial it was using Windows 7 beta. I have also used it since I upgraded to Win7 RC, so I know that it can work. Did you make sure to install driver when the phone is connected and booted to the boot loader screen? Windows sees the phone as a different device when connected normally and at the boot loader. When I installed the driver It popped up with the message that it was for a different version, but it gave me an option to install it anyway. Are you logged in to Windows with admin rights?
Click to expand...
Click to collapse
I am in bootloader mode, and I am an admin. It didn't give me the option to install it anyways. That is interesting. I am currently still using the windows 7 beta. I have tried manually selecting the specific driver files. It is still not working, any other ideas?

I finally got it! thanks everyone. The solution was instead of having it search through the files, there is actually an option below it to pick the driver from a list, the list wasnt the right one originally, then i manually changed the directory and it worked. Thanks for the help everyone!

billc.cn said:
When choosing the driver software, make sure you select the "x86" folder instead of usb_driver or any parent folder. This is because the wizard search sub directories in alphabetical order, and will stop when it find the driver for x86-64(amd64). Then it will simply tell you "not intended for this platform" without looking in the x86 folder.
Also, you do not have to disable driver signing for this to work.
Click to expand...
Click to collapse
How come when I installed this on Beta I got the message that I could not install a non-digitally signed driver? I was not able to install it myself until I disabled it at boot... maybe the 32 bit version is signed.

I just need a little help

I currently have a mytouch 3g and am running a slide rom on it, problem is there is no keyboard, how do I manually install an apk file preferrably from the computers console such as swype or astro both of which apk files are currently on my sd card. Any help is much appreciated, I started using this forum in 2008 but have never once posted, sad really. ive been trying to install it via adb commands but I keep getting device not recognized errors, feel free to flame my noobishness

Once you have a file explorer you can just click on APKs to install them. If you don't have access to the market to get a file explorer you will have to install them using the ADB method. I found a forum post that gives some rough instructions, but it sounds like you don't have ADB set up correctly. Also I believe the path used with the adb install command is the location of the apk on the PC.
http://androidcommunity.com/forums/f4/how-to-install-apps-using-adb-4482/
The following is a response to someone having a similar problem on another site:
http://www.androidkit.com/steps-to-install-and-uninstall-apk-file-on-android-g1-device
The message is coming because the drivers for the G1 Android device are not properly installed.
If you are running windows, Check so:
Right click on My Computer, and click Manage, then go to the device manager
If you see an “ADB Interface” category at/near the top, with “HTC Dream” under it, then you’re good to go.
Else, you need to install the drivers by pointing to the driver location to the usb_driver folder under the android sdk folder installed by you, while the device is connected, and the system prompts for it.
Click to expand...
Click to collapse

Allwinner A10 Livesuite Install the driver fail error

I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.

Thank you!!
dm871 said:
I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Click to expand...
Click to collapse
thank you sooooo much, my sons Eken T10 crashed and was in a boot lock months ago and i had gone through every thread i could find on the web over the livesuite not working unyil i read this!!! Worked a treat

It's alive!
dm871, thank you so much!
I would just add, I had already unpacked version and this was ruining all installation process; I didn't know, where to find that LiveSuitPack_version_1.09_20111101.exe package.
Thats why I'm posting packed version here, it's from Ritmix site. May be someone can't find proper file too.
Windows 7 Pro SP1 x64, now all works well.

Thanks for the directions on how to install the driver on windows 8, I was having lots of issues, because windows 8 does not tell me that is blocking the install of the drivers. I didn't know that windows 8 had the option to reboot into a mode where It would accept unsigned drivers. (This is actually really helpful for me, because it seems I have plenty of other instances where I need to be installing unsigned drivers at work also for lesser known random devices.)

Thank you everyone!
My fault Ainol Novo 7 Legend finally recovered.
doz10us said:
dm871, thank you so much!
I would just add, I had already unpacked version and this was ruining all installation process; I didn't know, where to find that LiveSuitPack_version_1.09_20111101.exe package.
Thats why I'm posting packed version here, it's from Ritmix site. May be someone can't find proper file too.
Windows 7 Pro SP1 x64, now all works well.
Click to expand...
Click to collapse

Thanks!
dm871 said:
I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Click to expand...
Click to collapse
Thank you!!!
My GoClever is alive now! Thanks!

Tank you muchly
dm871 said:
I have had endless issues with 'Install the driver fail!' errors on numerous machines, this occurs when trying to launch livesuit.exe in order to flash many types of A10 tablet. This is a fix which worked for me on several platforms.
You will find something like LiveSuitPack_version_1.09_20111101 in the unpacked livesuite folder (I used version 1.09, it is similar for 1.07 which is the other version commonly found).
You should run this as administrator and it will install the relevant drivers and then you will be able to run the livesuite executable.
Under Windows 7 simply right click and choose 'Run as administrator', you will be prompted to allow the installation of an unsigned driver, to which you should say yes.
Under Windows 8 this will still fail with a similar message. This is because, by default Windows 8 does not allow the installation of unsigned drivers. To overcome this, you need to use CTRL-ALT-DELETE to get to the screen with the restart/shut down/log off button in the bottom right corner.
Hold SHIFT and click on restart.
This will take you though a series of screens. Choose Troubleshoot, Advanced Options, then Startup Settings. The machine will now reboot. On startup you will be taken to a new maneu screen, where you can choose option 7 to allow the installation of unsugned drivers.
Now you can run the LiveSuitPack_version_1.09_20111101 as administrator, and all should be well.
Enjoy.
Click to expand...
Click to collapse
Thank you so much for the heads up on win8 foibles. I have now managed to get my Scroll Extreme into a 'usable' state

i have done that and the device appeared in device manager but it giving error "code 10 cant start the device "
i am on windows 7 32bit .

My keyboard does not respond when I get to startup settings screen. I tried a command with command prompt and did not help

[TUTORIAL][ADB][WINDOWS 8]Connect HTC explorer to windows 8 and use adb

Hello friends,
This is my first tutorial on this forum and wishing to help my buddies overcome a simple issue I've been facing for many days after coming to windows 8... I am a regular Android App developer and when i started using Windows 8, I observed that the default adb interface couldnt detect my phone.
After a lot of searching here and there, I realized, that there is something missing. So here comes the way to connect our baby droid to the all new windows 8 -
THINGS YOU NEED -
HTC Sync latest 3.21.1
ADT - you can download this from android site.
and this file
NOW HERE COMES THE PROCESS -
1. Download and install HTC sync.
2. Unzip the ADT and add the platform tools folder to your environment path
3. Unzip the file downloaded from link above. Basically its the google usb driver.
4. Now go to device manager and see your phone should be listed as an unknown device.
5. Now find "Android Phone" with a yellow error sign in front. It will be expanded by default.
6. Right click on it and select update driver.
7. Select browse my computer.
8. Link to the folder where you extracted the google usb drivers in step 3. Check the subfolder.
9. Click next. It'll display a warning. Select Install anyway.
10. Completed.
11. You may now download SDK and ADB.
Hope this would be helpful in someway or other.... :highfive::highfive::good:

Is it necessary?
Do we really need HTC sync if we are on a custom rom?

Idea of htc sync is to have htc drivers, it is even recommended to stop htc sync when doing something with adb

shortyoko said:
Idea of htc sync is to have htc drivers, it is even recommended to stop htc sync when doing something with adb
Click to expand...
Click to collapse
Yes htc sync is not needed, but sometimes I see that if my phone is not being detected on adb and i turn on htc sync and keep it aside, my phone gets detected. So I am also a bit confused if this is at all needed or not...

just update htc sync (in case if it is not ) cuz i did the same and my phone got detected in windows 8

[FIX] USB Tethering lags/freezes on windows 8.1

Everytime i tried to use USB Tethering with my Xperia U on my Windows 8.1 (Bing's single language Edition [Genuine Licence]) have always lags or even freeze the taskbar and some other tool settings on my operating system. After some testing and googling a little bit i found a solution for this Microsoft Issue: Update your NDIS 5 Driver to NDIS 6.x.
Verify if your device is using RNDIS 5 driver (1):
Open Device Manager from Control Panel and expand “Network Adapters.”
Plug in your device and enable USB Tethering so that the device is detected as Remote NDIS based device.
This should now create a Network Adapter named as “ [Your Device Name] Remote NDIS based [internet Sharing/network] Device.”
Right-click the Adapter and select Properties.
Select the Driver tab and then click Driver Details.
You can see the driver files if the files are named usb8023x.sys and rndismpx.sys you are using RNDIS 5 Driver.
Updating your driver:
Option 1: Update your driver NDIS driver manually by selecting the driver's list option on windows wizard driver's update. Unselect show all compatible hardware option, you will get a Microsoft's driver list. You should seek for a RNDIS 6 USB device and click next. This should work on 32bits or 64bits edition.
Option 2 (64 bits only)(2): Just Download and update your NDIS driver from the attachment below. On Driver's Wizard installation must go through selecting the driver from a list.
Sources:
http://support.microsoft.com/kb/2923775 (1)
http://www.driverscape.com/download/remote-ndis-compatible-device (2)
https://msdn.microsoft.com/en-us/library/windows/hardware/dn449742%28v=vs.85%29.aspx. Microsoft says NDIS 6.4 is included on Windows 8.1, don't know why windows chooses RNDIS 5 over RNDIS 6 on my laptop.

Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards

MHP2013 said:
Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards
Click to expand...
Click to collapse
Try this before installing the NDIS 6 driver:
http://www.tomshardware.com/faq/id-2165451/dont-windows-windows-automatically-download-device-drivers-icons.html
If above didn't work try to disable driver signature verification:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/

Perfect, Thanks for this fix! Didn't need the driver as RNDIS6 driver is already included in Windows 8.1
NDIS Compatible works without huge driver lockups, but RNDIS6 USB Adapter also works like a charm. (Nexus 5)

Facing the same problem, here.
Tried both options, still facing the same problem..
Any ideas?

I am having the same issue in Windows 10 64-Bit.

Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.

Ano59 said:
Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.
Click to expand...
Click to collapse
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?

DubleJayJ said:
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?
Click to expand...
Click to collapse
As OP said, manually select the proper driver.

Windows 10 best solution: rename the RNDIS5 .inf file
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver

Something is not logical in this tutorial :
The content of the inf file in the attachment is rndiscmp.inf; but this file is already in Win8.1 system (C:\Windows\Inf). Hash are similar
This could explain why windows refuses to install it again and says "the last drivers is already installed"
Renaming extension of wceisvista.inf doesn't work for me in Win 8.1
Maybe you could tell us the name of driver files when using RNDIS 6 Driver ...

This thread is also important for resolving playability issues with the game XCOM 2, so thank you very much for the fix to a problem completely unrelated to Android You guys are awesome!

Thanks, worked for my Galaxy S6.

You can use one of the below drivers from that list. One of them may work, try them all:
USB RNDIS Adapter
USB RNDIS6 Adapter
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device > this was the one that worked for me

inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank You :good:

Thx! Worked!! Windows 10 64 bit.

Hi guys, i get some issues here where it looks like i have only NDIS 5 on my windows 10.
I tried manually select driver, but i can only see this one : Remote NDIS based Internet Sharing Device
i tried inkaine's method, usb8023x.sys is still there but rndismpx.sys is missing. So i think i'm still using this annoying NDIS 5.
I don't understand why it's so hard to update this driver.. :silly:

inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank you so much. This issue has been bothering me for years and your solution along with OP's solution helped me. Thanks

Hey ive been having this issue for a while now and im using a htc one m8 to tether with but for me it wont let me manually update the drivers or modify the wceisvista.inf im using windows 10 pro as well.

Windows 10 fix - Worked for me
Hello all,
None of the steps worked for me, however i followed one more set on steps that i found on the net (unable to post links yet )
anyways, the steps are
Open Device Manager (right click on Computer > Manage > on the left side, under System Tools choose Device Manager)
Choose the problematic device in Network Adapters (for me it's called HTC Remote NDIS based device)
Right click on it and choose Update Driver Software...
Click Browse my computer for driver software
Click Let me pick from a list of device drivers
Uncheck the box Show compatible hardware
For the manufacturer, choose Microsoft Corporation
Now you will have two options:
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device
I chose the second one and it solved the problem, but if it doesn't work you could try the other one. In my case, the driver that was being used was neither of these, but a special driver from Android SDK ADT bundle.
Pick one and click Next.
If a dialog comes up, confirm by clicking Yes.
Wait a few seconds for the connection to restart. If it doesn't work, try disabling and reenabling USB tethering on the phone, or reconnect the USB cable.
PS: Microsoft Corporation or Microsoft Inc. or Microsoft might be present in manufacturer. search among the three