Related
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'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?
Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim
Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?
More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!
Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.
Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.
I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.
One thing I forgot. Do not unplug your device between uninstall and hardware scanning.
AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim
whenever I try and install the samsung usb drivers for my S3 the installer always fails with this message: "The MSS installation for SAMSUNG USB Driver for Mobile Phones V1.4.6.0 has failed."
I had the universal naked drivers installed on this PC before for my tbolt and transformer prime, but it wasn't compatible with the S3 yet. There is an updated universal naked drivers that supports the S3, but when I try and back up my IMEI and put the phone into RMNET+DM+MODEM mode, the naked drivers don't recognize my device. in the regular MTP+ADB the drivers work fine.
so I imagine I need the samsung drivers to install for this to work. does anyone have any ideas how I could get the samsung usb drivers to install properly? I've also tried the V1.5.5.0 version as well and the installer fails as well. I've removed the universal naked drivers and tried to install without it and I still get the error. same thing in windows safemode. I'm running Windows 7 Enterprise 64 bit.
has anyone else had trouble with this? and any idea how to get the installer to work? thanks
Lots of people have been having this issue. I'm having it on XP at the moment... until now.
Per another thread I read here (for the Dell Streak, thread here: http://forum.xda-developers.com/showthread.php?t=1291293) you can force Windows to use the generic driver instead of the Samsung one.
Basically, I edited a copy of the INF to match my device info, then entered the info into the [Generic] area of the INF. I then told Windows to allow me to manually select the driver, and pointed it to this INF file. Voila... I now have generic driver support for MTP in XP SP3. I imagine the same thing might work with other versions of Windows, since I'm not really using any non-Windows drivers.
jackmei2 said:
whenever I try and install the samsung usb drivers for my S3 the installer always fails with this message: "The MSS installation for SAMSUNG USB Driver for Mobile Phones V1.4.6.0 has failed."
I had the universal naked drivers installed on this PC before for my tbolt and transformer prime, but it wasn't compatible with the S3 yet. There is an updated universal naked drivers that supports the S3, but when I try and back up my IMEI and put the phone into RMNET+DM+MODEM mode, the naked drivers don't recognize my device. in the regular MTP+ADB the drivers work fine.
so I imagine I need the samsung drivers to install for this to work. does anyone have any ideas how I could get the samsung usb drivers to install properly? I've also tried the V1.5.5.0 version as well and the installer fails as well. I've removed the universal naked drivers and tried to install without it and I still get the error. same thing in windows safemode. I'm running Windows 7 Enterprise 64 bit.
has anyone else had trouble with this? and any idea how to get the installer to work? thanks
Click to expand...
Click to collapse
Download and install PDAnet app to your computer, this app will install the driver for you. You have to select "Samsung" during the install. Once done you can uninstall the app but the driver stay.
If PDA net doesn't work for you, go into device manager and select your phone, click on properties, advanced, and install the drivers manually.
So, I came across another way to get the drivers to load without any INF file hacking. If you simply tell Windows (XP in my case) to update the driver, then tell it you will manually point to it, you can find a suitable one in the folder C:\Program Files\SAMSUNG\USB Drivers\25_escape (after you install the MSS driver pack, of course).
Unfortunately, in my case, I use MediaMonkey to manage this, and it doesn't seem to notice the "difference" between my phone and my wife's (both SGS3s). That's their fault, though... they clearly have some bugs in there.
that's the problem... the MSS pack fails to install. I tried copying the samsung\USB Drivers folder from my desktop (which the driver install worked on) to my laptop and manually pointing to the folder, but it says it can't find a driver for it. kind of odd. I'll have to try the PDA net drivers to see if that will work. thanks for the help guys
Dawg5 said:
If PDA net doesn't work for you, go into device manager and select your phone, click on properties, advanced, and install the drivers manually.
Click to expand...
Click to collapse
Thanks this worked for me
Hi all !
This is so simple but it is driving me crazy.
I run Win 7 X64 and have a new [ network unlocked ] Samsung Focus 2 SGH-i667 phone.
No matter what I do, the PC will not fully recognise the phone when it is usb connected to the PC.
Zune *does* see it
Kies [ latest version ] does *not* see it.
Windows Phone 7 Developer Tools does *not* see it.
Windows *partially* does see it but it does not load the "Qualcomm CDMA MSM" drivers - as such,developer unlocking so as to side-load application XAP's is impossible.
I have tried numerous USB cables / numerous different USB ports / the *latest* Samsung USB drivers / forcing Windows Update / even a clean machine etc..... all to no avail.
I plug the phone in, it starts to load the driver and then it comes up with Device Driver not found - I let Windows Update do its thing, but still no go.
Please Help !
This is such a simple thing,
How can I make Win 7 X64 *see* my Samsung WP7 phone fully so that I can developer unlock it to side-load application XAP's ?
All help will be hugley appreciated.
Ben
I pl
my first suggestion would be to remove all the drivers you have installed and get it working correctly with zune, the best way I find to do that is use This program, it lists all USB devices, delete all the ones that maybe associated with WP, delete and uninstall!
then remove zune
install zune, restart then plug in your phone, see what happens then, for now, forget any other driver you may think you need,
dazza9075 said:
my first suggestion would be to remove all the drivers you have installed and get it working correctly with zune, the best way I find to do that is use This program, it lists all USB devices, delete all the ones that maybe associated with WP, delete and uninstall!
then remove zune
install zune, restart then plug in your phone, see what happens then, for now, forget any other driver you may think you need,
Click to expand...
Click to collapse
Hi RC
Genuinley - many thanks for helping out.
Did what you suggested - everythinhg is clean as a whistle - still the same issue - Zune sync's and see's the phone, but Win 7 X64 see's some of it but not enough for the developer unlock [ chevronwp7 ] to proceed - it jusy comes up with the error saying something like cant connect via usb - try re-opening zune etc.....
Please see the attached " devices.jpg " to see what my system is " seeing " .
My phone is a newer Focus 2 SGH-i667 WP7.5 phone - maybe its too " new " ?
Any help will be grealty appreciated.
Thanks again,
Ben
ben ifin said:
Hi RC
Genuinley - many thanks for helping out.
Did what you suggested - everythinhg is clean as a whistle - still the same issue - Zune sync's and see's the phone, but Win 7 X64 see's some of it but not enough for the developer unlock [ chevronwp7 ] to proceed - it jusy comes up with the error saying something like cant connect via usb - try re-opening zune etc.....
Please see the attached " devices.jpg " to see what my system is " seeing " .
My phone is a newer Focus 2 SGH-i667 WP7.5 phone - maybe its too " new " ?
Any help will be grealty appreciated.
Thanks again,
Ben
Click to expand...
Click to collapse
if its syncing with zune then your at least half way there, did you leave zune open when using the XAP deployer? did you install the full SDK? I know there are "smaller" packages out there but where theres doubt there are potential problems, we need to turn them in to real problems or rule the out so uninstall whatever SDK you used, make sure the full SDK is re installed.
Im actually about to try installing my Focus S on a brand new Win 8 x64 system So ill double check all the steps but I didn't think we needed the Samsung drivers to XAP install, I thought that was cab updates and QPST stuff.
Anyhow, make sure zune is running and is synced, make sure you remove and reinstall the full SDK and get back to me, ill check all the steps today
its connected to win 8 at the moment, no zune, no SDK and its installed as a portable device (Samsung SGH blar blar) im just getting the zune package, ill sync it, then ill install SDK and attempt some XAP deploying
dazza9075 said:
if its syncing with zune then your at least half way there, did you leave zune open when using the XAP deployer? did you install the full SDK? I know there are "smaller" packages out there but where theres doubt there are potential problems, we need to turn them in to real problems or rule the out so uninstall whatever SDK you used, make sure the full SDK is re installed.
Im actually about to try installing my Focus S on a brand new Win 8 x64 system So ill double check all the steps but I didn't think we needed the Samsung drivers to XAP install, I thought that was cab updates and QPST stuff.
Anyhow, make sure zune is running and is synced, make sure you remove and reinstall the full SDK and get back to me, ill check all the steps today
its connected to win 8 at the moment, no zune, no SDK and its installed as a portable device (Samsung SGH blar blar) im just getting the zune package, ill sync it, then ill install SDK and attempt some XAP deploying
Click to expand...
Click to collapse
Thanks - I'll do that and report back - look forward to hearing how you go at your end too.
Ben
ok, exact step by step - clean install of win 8
plug phone in (device manager lists it as a portable device - Samsung SGH-i937)
Download zune 4.8 and install, it will ask you to unplug the device so unplug it
plug in device and sync it properly
turn off zune
download and install the full 7.1 SDK note that it will throw up all sorts of errors, just install it anyway
don't restart
then download the SDK 7.1.1 patch, that will let it run on windows 8
don't restart
turn on zune and sync (note that device manager still lists it as a portable device - Samsung SGH-i937)
open up application deployment from the sdk and upload your XAPs (assuming you have it unlocked that is?)
the mere fact that is installing other drivers tells me its maybe conflicting, remove all traces of the drivers using USBDVIEW, also uninstall them, check the add remove programs in the CP and remove anything in there as well, the strange thing is I get those drivers installed when I mess about with the low level hardware using QPST, oh try a different USB port as well, not on the same bank, use a different set if you can.
dazza9075 said:
ok, exact step by step - clean install of win 8
plug phone in (device manager lists it as a portable device - Samsung SGH-i937)
Download zune 4.8 and install, it will ask you to unplug the device so unplug it
plug in device and sync it properly
turn off zune
download and install the full 7.1 SDK note that it will throw up all sorts of errors, just install it anyway
don't restart
then download the SDK 7.1.1 patch, that will let it run on windows 8
don't restart
turn on zune and sync (note that device manager still lists it as a portable device - Samsung SGH-i937)
open up application deployment from the sdk and upload your XAPs (assuming you have it unlocked that is?)
the mere fact that is installing other drivers tells me its maybe conflicting, remove all traces of the drivers using USBDVIEW, also uninstall them, check the add remove programs in the CP and remove anything in there as well, the strange thing is I get those drivers installed when I mess about with the low level hardware using QPST, oh try a different USB port as well, not on the same bank, use a different set if you can.
Click to expand...
Click to collapse
Hi dazza
In your Device Manager, do you get any " yellow flags " like I do with the .jpg I posted above ?
Ben
ben ifin said:
Hi dazza
In your Device Manager, do you get any " yellow flags " like I do with the .jpg I posted above ?
Ben
Click to expand...
Click to collapse
nope, I don't sorry.
have you played with the diagnostic tool at all? perhaps changed the USB mode?
Hi guys,
well, I try to explain my problem... I've installed windows phone application from microsoft and the relative driver ( i guess ). After that I' ve installed nokia care suite, attach my phone trough USB and nothing happens. :silly:
Also I've installed WinUsb driver in the driver folder of nokia care (i've read it on a guide), but even after that the suite is not connecting to the phone. My phone is regullary detected from Win 7 and windows phone application. I' ve tried also to disinstall all the driver installed previously and reinstall it but nothing changed.
Does anyone can help me please???
Look in the care suite folders in Program filesx86, make sure you have installed all the drivers in the Drivers folder, Open care suite then connect phone, If that fails check in device manager to see if the device is listed or has a yellow mark,
You may also need to restart PC.
AndyFZ1S said:
Look in the care suite folders in Program filesx86, make sure you have installed all the drivers in the Drivers folder, Open care suite then connect phone, If that fails check in device manager to see if the device is listed or has a yellow mark,
You may also need to restart PC.
Click to expand...
Click to collapse
I' ve tried also to install the driver in that folder, reboot the pc many times.....nothing helped... :crying:
in device manager, the device is correctly listed, no yellow mark...
kupo88 said:
I' ve tried also to install the driver in that folder, reboot the pc many times.....nothing helped... :crying:
in device manager, the device is correctly listed, no yellow mark...
Click to expand...
Click to collapse
Nokia Care Suite not supported by Windows Phone.
Right now there no way to connect with it.
I dont remember the exact url but when i bougt mine i had the same and i went to nokia support to get it know.
Sorry or my english.