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.

Android and ADB under Windows 7 x64

I'm trying to connect my device under Android and I'm having problems.
Windows 7 actually detects it and I select the right x64 drivers, but when it is installing them, the progress bar keeps going forever while it says "Installing the driver software...".
The only way to close that window is to unplug the device. Then, the driver appears to be installed, but it's not.
What up with the driver?

Have you tried modify driver from G1 post for example, I remember i used modify version.

imfloflo said:
Have you tried modify driver from G1 post for example, I remember i used modify version.
Click to expand...
Click to collapse
After days of trying a lot I'm almost crazy because of this issue!
I don't know what the problem is, but I discovered that the my Polaris, when it's connected under Android, prevents the system from shutting down! I mean, if I choose to shut down my Windows 7 x64, it doesn't shut down until I disconnect my Polaris.
It happens the same when I boot my computer: it I have my Polaris connected, it doesn't boot. When I remove it, it boots as usual.
I switched the USB cable, the USB socket, and it's the same. But under Windows Mobile, it works like a charm
My Android OS is this one: http://forum.xda-developers.com/showthread.php?t=591104 (updated yesterday).
So, the problem is not the drivers, it's Android itself!

Hi
have you tried installing "PdaNet for Android" just (follow those steps)

[Q] Can't deploy XAPs anymore

I have a Samsung Focus (rev 1.3) which is interop-unlocked using Jaxbot's WindowBreak.
Everyt
My desktop (Windows 7 x64) was able to:
1. Connect and sync via Zune
2. Deploy XAPs
3. Create backups using the Easy_Backup tool
4. Connect to Cab_sender
While it is still able to do 1, 3, & 4, it just cannot deploy XAPs anymore. It's not a problem with the phone as I can still deploy xaps from my laptop.
Every XAP deployer I use returns the following error:
"Failed to connect to device. The specific module cannot be found"
I've tried re-installing Zune, my .NET is upated. I even tried installing the full WP7.1 SDK but it didn't help.
Googling the error hasn't turned up much.
What could be the problem here?

I had the same problem, but I didnt want to reinstall the whole wp7 sdk. Uninstall the wp7 sdk(only if you dont need it) and then try W.I.N.C.O´s wp7 mini sdk. That one worked well for me
http://forum.xda-developers.com/showthread.php?t=1265846

freddx said:
I had the same problem, but I didnt want to reinstall the whole wp7 sdk. Uninstall the wp7 sdk(only if you dont need it) and then try W.I.N.C.O´s wp7 mini sdk. That one worked well for me
http://forum.xda-developers.com/showthread.php?t=1265846
Click to expand...
Click to collapse
Unfortunately, this doesn't work. I had this installed prior to the start of the problem. I installed the full SDK only later.
I tried this again, but the installer just disappears moments after it executes.

Samsung MTP Mobile Device Failed

For the life of me I cannot get my Desktop - Gigabyte Mobo (Windows 7 pro 64 bit SP1 with all windows updates) to install the mtp driver for my Galaxy S III (VZW). So far I have tried installing and uninstalling, rebooting, installing drivers both from Samsung website as well as through Kies. The error code I get for the Samsung Mobile MTP Device is
"This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"
(looking at device manager)
As a sidenote, I tried installing Universal_Naked_Driver_0.7 from this forum and while it does install without error the phone still doesn't show up in any way on the computer (I.E. My computer/as a storage device).
What is strange is that using the Samsung driver that I tried first (on the desktop) I was able to get the phone to install and work perfectly on my Windows 7 64 bit sp1 home premium (Dell laptop).
Any thoughts or suggestions as not even Samsung chat was able to remedy the issue.
*I am new to the forum but I did my best to (beforehand) search for solutions (which I have yet to find).

I couldn't get the MTP drivers to load on XP, due to the well known problems there. I got the built-in Windows drivers to work, and it seems to be working relatively well. I will be testing a longer upload to my wife's phone later today, but for the few songs I tried on my SGS3, it's working well.
I posted my hack here: http://forum.xda-developers.com/showthread.php?t=1851547

Nextbook NXW8QC16G Windows 10

Hi there,
There was a previous discussion on installing other systems on the Nextbook NXW8QC16G (http://forum.xda-developers.com/showthread.php?t=2956409)
This is specifically installing Windows 10 on this unit.
The latest build of Windows 10 build 10041 works great.
I backed up drivers from Windows 8 using Double Drive 4.1.
I created a system restore disk on a USB stick.
Used Rufus to format usb stick, to FAT32 , for the Windows 10 install, but had to avoid adding the image to the rufus tool as it kept changing the format of the USB stick to NTFS(the UEFI boot doesn't seem to be able to boot from). Manually copied the contents of the ISO to the memory stick and installed Windows 10.
Once in Windows 10, I installed all drivers except the display and network drivers (when I did on previous installs, i would end up with an endless boot).
Rebooted, attached a usb Wifi dongle, ran Windows updates, rebooted, and all, including touch and built in wifi work perfectly.
I am willing to do a driver dump of the current setup if anyone wants to avoid the Windows updates, or doesn't have a USB dongle to get the drivers updated.
Everything seems to be working brilliantly

I would love to have a driver dump for this device.. my friend has 2 of them and her sons have wrecked them.. I got windows reinstalled and was able to get everything but the touchscreen working again

I would also LOVE a dump as my daughter bought 2 of these for my grand-kids for Xmas, and they have ruined them! Thanks!!!

YaBoyRobD said:
I would also LOVE a dump as my daughter bought 2 of these for my grand-kids for Xmas, and they have ruined them! Thanks!!!
Click to expand...
Click to collapse
I have found that the drivers for the HP stream 7 seem to work for these devices. as well

awesome sir, I shall look for them now, and thanks in advance for you assistance!

rancidbob said:
Hi there,
There was a previous discussion on installing other systems on the Nextbook NXW8QC16G (http://forum.xda-developers.com/showthread.php?t=2956409)
This is specifically installing Windows 10 on this unit.
The latest build of Windows 10 build 10041 works great.
I backed up drivers from Windows 8 using Double Drive 4.1.
I created a system restore disk on a USB stick.
Used Rufus to format usb stick, to FAT32 , for the Windows 10 install, but had to avoid adding the image to the rufus tool as it kept changing the format of the USB stick to NTFS(the UEFI boot doesn't seem to be able to boot from). Manually copied the contents of the ISO to the memory stick and installed Windows 10.
Once in Windows 10, I installed all drivers except the display and network drivers (when I did on previous installs, i would end up with an endless boot).
Rebooted, attached a usb Wifi dongle, ran Windows updates, rebooted, and all, including touch and built in wifi work perfectly.
I am willing to do a driver dump of the current setup if anyone wants to avoid the Windows updates, or doesn't have a USB dongle to get the drivers updated.
Everything seems to be working brilliantly
Click to expand...
Click to collapse
Good day.
Have you tried this with the latest insider preview build? Do you know if the drivers work out of the box yet?
Also, can you please provide a driver dump for me?
Regards,
Ganralf

I have successfully installed Windows 10 build 10074 on my 8" 16GB Nextbook tablet, model NXW8QC16G
You can find the drivers and some other tips on this thread: answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/installing-windows-10-on-the-nextbook-101-that-is/18a49db3-ad1e-4232-aa44-547409a27518
I posted the following information for what I had to change to get it working on my tablet:
The only problem was that the orientation was off by 90 degrees (display would be portrait while tablet is in landscape mode)
I found a small change int he registry file fixed it for me:
"Orientation"=hex:01,01,00,00,01,01,02
Note the order of the numbers.
Hope this helps people that want to install Win10 on their 8" tablets
Click to expand...
Click to collapse

does any one have a bios bin for this nextbook