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.
Has anyone else using XP had any issues installing the USB Driver for the Magic? I've tried every possible method to get it to work and it just will not install. A method that appears to work for some is in this link-
http://www.mail-archive.com/[email protected]/msg09692.html
Although this did not work for me. There was also a suggestion of copying the inf file and renaming certain strings by one digit. Any suggestions?
I used the latest SDK with the included driver. Set the environment paths. Nobody has any other suggestions?
renaming the inf file solve the prob for me.
radonsg said:
renaming the inf file solve the prob for me.
Click to expand...
Click to collapse
What did you rename it to? I renamed it to android_usb_Magic.inf like the linked post said.
Hi Gimpeh
This worked perfectly for me. The issue was once it installed the Windows drivers there was no way back. However, follow this
So you plugged your Android phone into your Windows machine having forgotten to switch on USB debugging…
Menu > Settings > Applications > Development > USB debugging
Then Windows detected your device as a USB-Mass storage device and won’t change the settings, regardless of how many times you uninstalled the device. Thread on it here.
This solution worked for me and didn’t require editing the registry settings (I don’t know if the reboot is unnecessary).
(1) Plugin phone
(2) Uninstall any drivers that mention “HTC Android Mobile USB Device”
(3) Unplug phone and restart
(4) Install and run USBDeview
http://www.nirsoft.net/utils/usb_devices_view.html
(5) Using USBDeview find the Android device (for some reason Windows hides uninstalled drivers instead of deleting them), right click on it and uninstall.
(6) Follow the official instructions to the letter this time.
http://developer.android.com/guide/developing/device.html
Click to expand...
Click to collapse
http://blog.zedray.com/2009/06/16/when-adb-won’t-detect-your-android-phone…/
Good luck!
This is pretty close to the instructions I followed earlier. No resolution. All HTC device drivers have been removed. Although there is a composite USB device installed (not labeled HTC). I know sometimes if windows does not recognize a device it will show it as a composite.
Install HTC Hotsync - http://www.htc.com/sea/SupportViewNews.aspx?dl_id=573&news_id=169
Have your phone plugged in first then install the app. You don't need the additional drivers it list. Just the Hotsync program.
That did the trick for me.
edit the inf file under the x86 folder inside the usb driver.
replace the vid_0bb4&pid_0c02 with vid_0bb4&pid_0c03
cos somehow my htc is recongnise as vid_0bb4&pid_0c03 instead of vid_0bb4&pid_0c02.
Hotsync didn't work and neither did replacing the string from 02 to 03. I got it to recognize at work on a Vista machine but since then it will not recognize on my home XP or any other Vista machine. When I select Have Disk and select the INF file it says something to the effect of There is no driver information for this device.
Additional Note: Although the device was recognized on that one vista machine, it would not recognize when it was in HBOOT mode.
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
radonsg said:
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
Click to expand...
Click to collapse
CTRL+F Put in that key and found nothing.
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Cheesebaron said:
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Click to expand...
Click to collapse
How would you go about flashing the recovery.img in Ubuntu. I didn't see any drivers for linux.
Driver
http://developer.android.com/sdk/1.5_r2/index.html
Additional work for linux(add rules)
http://developer.android.com/guide/developing/device.html
I finally figured the damn thing out. For some reason windows recognized the ION as a Video device and installed it as such. I figured it out after I got irritated and just uninstalled everything that wasen't plugged in.
woa.
TT is strange. Which version of windows? vista or xp?
Its XP Home on a HP Mini. I'm glad I finally have it figured out. I've probably spent 20 hours on this issue alone. I even went to Ubuntu since Windows was being...well windows.
I originally posted this inside the Glorious Overdose V2 thread, but decided to post here as well.
For some reason my computer won't recognize my Sidekick when I plug it in via usb. I do have the samsung drivers installed and it will read my friends Samsung Droid Charge just fine, but when I plug my Sidekick in it comes up saying "USB Device Not Recognized". So far I've tried uninstalling and reinstalling the drivers from the device manager to no avail. Wondering if anyone has an idea as to what it could be. I've also tried googling the solution and everyone says to just uninstall and reinstall the drivers and it should work. Now the phone is not plugged into a USB Hub, extender, or case, it is plugged directly into a usb port on the mother board.
PC Specs just in case:
Motherboard - Gigabyte GA-970A-D3
OS - Windows 7 Ultimate x64
CPU - AMD FX-4100
Memory - 8GB DDR3 1066
Phone:
T-Mobile Sidekick 4G running Glorious Overdose V2
Nothing added just the rom and some apps/games.
I have tried with USB Debugging on and off, either way does not work.
Update: I have since tried Kies mini, as well as the drivers found on Softpedia. Neither of those worked, so I just got done reformatting and reinstalling Windows hoping that would work. At first it did not, right now I am running windows update to see if that was the issue, I'll update of what the outcome is.
Update: After installing all available Windows updates it's still not recognizing the phone. Now no matter what it's saying it's an Unknown Device. Even after I try and do a manual driver update and tell it to look in the folder with the driver files from Softpedia. I'm at a complete loss now.
If anyone has any idea's please let me know.
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Jax184 said:
What mode do you have the phone in? Settings->Applications->USB Settings. It should be in Mass Storage if you want to access its SD Card.
Click to expand...
Click to collapse
It's set to USB Debugging. But even then, it should read as something else other then Unknown Device when I plug it in. I have tried plugging it in and selecting Mass Storage, still comes up as Unknown Device.
HewettBR said:
Maybe put another rom on the sd card and flash something else, I don't think it would be a rom issue but it would be worth a try?
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
I've thought about that, and from everything I can see it's either the ROM or the drivers. So we'll see...I'll probably try a different ROM and see what happens.
I suggest turning USB debugging off and mass storage on, for how you'll be using it. And recall that you have to change this stuff with the USB cable unplugged.
I've tried that, and after talking with the T2 Technical Support from Samsung for 45min today, the only option left is to send the phone in to get worked on. Though, I'm going into the T-Mobile store and see if they can't replace the phone or give me a loner while this one is out getting repaired.
More info request.
Can you provide us with the names and links to the drivers you have tried?
DuctTapedGoat said:
Can you provide us with the names and links to the drivers you have tried?
Click to expand...
Click to collapse
Kies Mini - http://www.samsung.com/us/support/owners/product/SGH-T839HABTMB
Softpedia - http://drivers.softpedia.com/get/MOBILES/Samsung/SAMSUNG-USB-Driver-1480.shtml
As well as the Samsung Vibrant drivers from both of those sites.
Samsung SideKick 4G Drivers
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
DuctTapedGoat said:
www DOT filedropper DOT com FWSLASH sk4gx64drivers
This is the exact drivers I pulled off of my own machine, I ran into massive issues with those same driver packages, especially in getting the initial root to take with a few different utilities designed to grant sudo/su/root access, and these are the drivers I have running currently, just pulled off my own machine. I run Windows 7 x64, but as well, there should be no reason why these drivers wouldn't work on a x86 machine and/or OS.
NOTE : I apologize it's not a proper link, but I'm unable to post a raw link until I hit my 8th post. I will come back and fix this after I hit that 8th post, but until then it will be ghetto-bypass HTML.
Click to expand...
Click to collapse
Thank you, I tried unpacking them to a folder on C:\ went into Device Manager, right clicked on the Unknown Device, Update Driver Software..., Browse My Computer for Driver Software, Set the search to C:\, and still saying Unknown Device is the best driver software for it. No idea why it's doing this.
Proper Driver Update
What is going on is that Windows is seeing a more recent signature file attached to the SK4G drivers on your computer (I don't believe anything at all is wrong with your device) than the working ones there.
First, in Add/Remove Programs, uninstall the Samsung Kies and Samsung Driver pack you installed earlier. Now...
Go into on your PC:
://windows/system32
And locate the same file names, cut them all, and paste them in a temporary folder you create, preferably on the desktop or something similar. You may not find every file, and that's okay, just the ones you can find. Next, you will be wanting to paste the driver files from the package I uploaded. Now, turn off Automatic Updates, so it doesn't automatically install drivers upon connection. Reboot the computer, double check and make sure Automatic Upates are off when you log back on. Now, connect the device and see if it gives you the same results. By removing the old drivers which don't work, you'll be able to force it to the ones we know work, and you /should/ have success. As well - USB data debugging active and activating connection for data transfer via the notification pulldown menu would be the best way to do this initially.
Would I be looking in c:\windows\system32\drivers for the same file names as the ones you packed up?
Ok, so the only one I could find in the drivers folder was modem.sys. But it will not let me move/replace the one that's already in there. It's telling me access is denied, same thing when I try and set the permissions it will not let me. I am logged in as an Administrator, as well it says it when I log in as THE Administrator account. So yeah...
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
DuctTapedGoat said:
Cool - modem.sys is a stock one that is shared with the device, so that's fine.
With the other two programs uninstalled, the old drivers uninstalled, and forcing it into those by pasting them into //win/sys32/drivers you should be in business. Hmm. You can try UnlockRoot.com's device rooter - I know they have an auto driver detector in their program. As well, you can try SuperOneClick, but I don't remember if they do or no. What about going in from the Recovery menu and toggling USB? Anything wierd going on in the /mounts? What about ADB shell access from the Android SDK on Windows?
Click to expand...
Click to collapse
I tried plugging the phone in, still showing up as Unknown Device. Tried UnlockRoot.com's program, no change. Installing the Android SDK right now, as well as I tried deleting the INFCACHE.1 file, and no change with that either. Once I'm done installing the Android SDK I'll redelete the INFCACHE.1 file and restart and try the phone again.
I did go in and check the mounts in recovery and they were set to:
UNMOUNT CACHE
MOUNT DATA
UNMOUNT SDCARD
UNMOUNT SYSTEM
Thank you for your help so far.
UPDATE: So after installing the Android SDK, deleting the INFCACHE.1 file, restarting, and then plugging the phone in, comes up and says the USB Device is Not Recognized. Then goes to search the preconfigured driver folders, and fails to install the driver for Unknown Device. And ADB Devices shows no devices as well(didn't think it would, but yeah).
UPDATE: So after using my friends phone as a conduit to throw the Stock Odexed KJ2 w/ Root(http://forum.xda-developers.com/showthread.php?t=1328698) onto my SDCard and flashing that the phone seemed to go into a soft brick at pre-boot screen(where it says SAMSUNG T-Mobile blah blah blah). Mind you this would freeze before it was even able to get into recovery. So I took it into T-Mobile and they are doing a manufacturer warranty replacement. So hopefully this next phone will be able to connect to the computer and be read correctly.
When I plug my phone in I have no way to transfer files to and from the Nexus 5. Nothing comes up. Tried updating the drivers, but nothing works. Please help.
I haven't been able to do this either, anyone wanna help?
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Sent from my Nexus 5 using xda app-developers app
n7of9 said:
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Click to expand...
Click to collapse
Nope, still nothing. My Razr HD comes up fine, but not the Nexus 5. Think it's a conflict in drivers?
Tweaken said:
Think it's a conflict in drivers?
Click to expand...
Click to collapse
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Tweaken said:
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Click to expand...
Click to collapse
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thank you n7of9 the link you provided worked for me.
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
This worked and also fixed another popular issue
Not only does this fix the MTP connection issue to move folders to root folder. But it also now allows me to see the preview thumbnails of my media! This was a huge problem on my other phones and many many people including me were never able to fix that. All the ideas to get around or create USB Mass Storage instead of MTP after 4.1 were fails.
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Worked perfect, thanks
what worked for me
In windows 8.1
I plugged in my nexus and browsed to device manager in control panel
I uninstalled the device (and deleted the driver)
I unplugged the nexus 5
I plugged it back in
Windows recognized it as a proper MTP device
I think the problem was something to do with windows recognizing it as an ADB device (I had installed the toolkit before etc)
This fixed it for me
openlatedotorg said:
Worked perfect, thanks
Click to expand...
Click to collapse
Hi,
I did all the steps mentioned, and ran the driver test - everything works fine, success.
However, I still cant see my device in "This PC"...
What is even more weird, that it only disappeared couple of days ago, and I didnt do anything to my computer at all....
Any other way to get devices to show? (Nexus 10 or Nexus 4 stopped showing too).....
Maybe problem is that it is being shows as ACER ADB Interface? But i cant change that to MTP anyway..
Installed drivers a few times. Win 10 shows my 6 as windows phone. Didn't before I reloaded windows.
When you plug the phone, be sure to activate the transfer mode in the phone settings.
Drivers are included in a folder as a mounted device in "computer"
Yeah
I did that I can see the files on the phone but shows as win phone in devices and shows windows driver
A OK.
Is that a problem?
Yes
b4bass said:
A OK.
Is that a problem?
Click to expand...
Click to collapse
*Win 10 no longer sees the phone period. Under file explorer or in devices. Tried reloading phone and usb drivers numerous times.
Kinda sucks as I can't transfer files, root, twtp etc
So it used to work but now it isn't?
It won't solve your problem but if you need to transfer files you can still use a ftp (numerous apps on the store). Just mount it as a network folder using the local ip the app gives you
I give for now