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.

NEED Help on ZuneUSBConnection.dll and ZuneWlanCfgSvc.exe

Dear Friend,
I seeking some help from you. I'm having touble to Sync my HTC DH7 with ZUNE.
My PC currently using Windows 7 64bit. I already install ZUNE for 64bit. unfortunately my phone was not recognize by my ZUNE software.
I've ran the Zune Device Utilities to determine the problem. and on the FILE tab, it shown that : ZuneUSBConnection.dll and ZuneWlanCfgSvc.exe was missing.
I already try to Google it... unfortunately not on my side.
Whoever have this file and dont mind to share, it would be pleasure to
say thanks so much for your help.
Regards.
Azman Ishak.

try uninstalling and reinstalling zune. maybe your anti virus deleted them thinking they're viruses?

The Gate Keeper said:
try uninstalling and reinstalling zune. maybe your anti virus deleted them thinking they're viruses?
Click to expand...
Click to collapse
Hi there... I already:-
1. Format my HTC HD7 sdCard - Done
2. Flash My HTC - Done
3. Change my OS from Windows 7 32bit to 64bit, vice versa - done.
4. Used the correct usb cable - Checked & Done
5. Soft Reset and Hard Reset the phone - Done
6. Restore to factory setting - Done
7. Remove and install ZUNE - Done
All has been done. But still failure..

anti virus? what are you using?

The Gate Keeper said:
anti virus? what are you using?
Click to expand...
Click to collapse
I'm not using any antivirus. and my pc is only used by me. quite tough for me to find the solution. the phone completely work with zune past few month. but now.. everything goes fakap. I was able to install any apps from market place without problem.. (which means, the sistem or the sdcard is good) but unable to be detected by ZUNE software.

only thing i can think of from here on is to completely wipe all memory of the phone from your pc and try again. in zune on the desktop > settings (top rightish) > phone tab > "forget this phone".
then connect the phone to the PC and start up device manager (start, type it into search). you should see your phone come up there. if it doesn't, try a different usb port. if it does, right click on it and uninstall. when uninstalling also delete the driver itself (should be a checkbox asking).
then restart PC and try to sync again.
if this doesn't work... my final 2 suggestions are wait till the update, or claim under warranty for a new device.

The Gate Keeper said:
only thing i can think of from here on is to completely wipe all memory of the phone from your pc and try again. in zune on the desktop > settings (top rightish) > phone tab > "forget this phone".
then connect the phone to the PC and start up device manager (start, type it into search). you should see your phone come up there. if it doesn't, try a different usb port. if it does, right click on it and uninstall. when uninstalling also delete the driver itself (should be a checkbox asking).
then restart PC and try to sync again.
if this doesn't work... my final 2 suggestions are wait till the update, or claim under warranty for a new device.
Click to expand...
Click to collapse
Hi there,
Thanks so much on your help and troubleshoot. I already followed your instruction. unfortunately still got the problem.
Here's some print screen for you.

[Q] Total Noob in Need of Lots of Help :(

I just got my SNS yesterday and it's my first android phone (was previously using an LG cookie) First thing I did was try to root it, and I seemingly succeeded, or so I thought. It looks like it's rooted and the superuser apps there but I can't install apps using any of the guides I find or even update to 2.3.2 (keep getting and error 7 msg). When I try to install using APKInstaller it tells me it can't find the device, which I think is the problem.
I think the problem is that someway or another windows 7 64 bit stopped recognizing my phone as a Nexus S and now recognizes it as a portable device in device manager (There's also an Android Phone, with an Android Composite ADB interface) I used the SDK to install all the updates available including the google usb driver rev. 4. I tried updating the Portable device driver using the google usb driver but windows keeps it as a WPD Filesystem Volume Driver. Also I noticed when I checked to see if adb gave me a serial number for the phone using the cmd prompt commands in the rooting guides it comes up blank.
I used usbdeview to delete everything seemingly related to Android, but everytime I reconnect the phone it, installs the drivers for the portable device.
I need help to make windows recognize the phone as a nexus s again so I can update and install apps and games etc. If anybody out there can help i'll really appreciate it. Explain the steps to me as if you were talking to a child, leaving nothing out plz. Thanks for any assistance.
I live outside the US (no android market) and would hate to think I messed up and expense phone purchase in just one day

Not quite sure where to start. But my intuition tells me its the Windows 7 64-bit and drivers that's not playing along. You might want to google if other users are having trouble with W7 64-bit with Android drivers. Otherwise, find another computer and repeat the steps. If not, flash a custom ROM to see if that eliminates the problem. You haven't damaged your phone. Don't worry.

just install directly from android market website
Sent from my Nexus S using XDA App

I assume you mean instal the update from the market (which I can't do because I don't have wifi)?
I managed to get the adb to list a device number after I installed java x32 & x64 bit. I still can't install apps or get the update to work, but I'll try unrooting and then rerooting my phone as see how that goes.
Oh, I haven't done the initial sign into gmail thing yet in case that makes any difference
Edit: god I feel stupid. I didn't realize that I had to upgrade from 2.3 to 2.3.1 and then to 2.3.2. I did that an everything upgrade without any problems. Now just got to figure out how to install apk's and I'm golden
Edit 2: Ok, I figured everything out and now i'm up to date with updates and I can install apps and games. Oh Happy Day Thx for all the help

Device not connected - Help, can't deploy apps anymore

Hi,
I have an unbranded HTC 7 Mozart T8696 Device running NoDo 7392.
It was chevron unlocked before I upgraded to NoDo and I was able to install apps aferwards. Currently sideloaded apps still work, so I assume the chevron unlock is still active. After about one month I wanted to sideload another app, but I always get an error telling me the device is not connected to the PC (I tried XAP Deploy and "Windows Phone Device Manager" even though Zune is running and showing the device as connected.
Any Ideas what might be wrong? I already tried uninstalling .net framework 4 and windows phone developer tools and re-installing, but it still shows "device not connected"

try this ... go to C\windows\system32\drivers\etc , open the file named "hosts" with notepad and delete any lines that say windowsphonedevelopement...

Hi,
thanks for your feedback. my hosts file is empty, still not working.
I am still using Zune 4.7 should I update to 4.8?

i had this same problem with my hd7 before and it worked after deleting that ... thats weird , yea 4.8 is now officially released u should update ..hopefully it will solve ur problem

still no luck, even with Zune 4.8

check this out ...
http://phone7.wordpress.com/2010/12/01/wp7-deployment-error-codes-explained/
http://msdn.microsoft.com/en-us/library/gg588381(v=vs.92).aspx

thanks, but this just doesn't help me
Failed to connect to the device. Ensure that the device is completely booted and is connected to the PC.
This can be caused by several reasons, including if the device is off. If the device is already connected, sometimes disconnecting and then reconnecting the device may fix the problem. Rebooting the device may also fix this problem.
This is what i tried multiple times. Rebooting the PC, rebooting the phone, re-installing .NET Framework 4, re-installing WP7 developer tools... all to no avail...

did u make sure the phones sync relationship with zune is not guest

Yes, I made sure it is. Nothing has changed on my PC really, except i switched routers. I am not sure what's happened...

hmmm maybe u can try going into device manager and uninstalling then reinstalling the phone drivers

I also went along and tried that. Still no luck.
EDIT: to clarify, I selected to uninstall the device and delete the driver files along with it. When I connected the phone it was re-installing the drivers.
tbh, i give up now. It's probably my phone and I can't be bothered to start from scratch again.

sorry i couldnt help u fix the problem

Instead of zune. Try using wpconnect.exe instead.
Thats all I use and its alot quicker that opening up zune and everything.
If you have Developer Tools 7.0 and the January Update wpconnect can be found here
C:\program files\microsoft sdk's\windows phone\v7.0\tools\wpconnect\
Restart your computer then connect your phone via usb wait for computer to recognize the phone. Then run wpconnect.exe... Dont run zune at all.

Hello,
thanks for your feedback, but wpconnect is giving me the same error as all deployment apps:
Failed to connect to the device.
It suggests i open zune and close it again. Zune itself recognises my phone and is able to sync data to it. WPconnect and deployment apps keep on telling me the phone is not connected...

*Bump* Anyone else have this problem?

could it be a pc registry problem ?

*bump* Still can't sideload

Hello !
Actually I've got the same problem.
Reparing .NET does nothing.
I've tried many things, as uninstalling programs that could interact on USB (VM Ware Workstation, Oracle VirtualBox, Kaspersky Internet Security 2012 and so on).
None of the XAP Deploy application works... And ChevronUnlocker is concerned to.
I don't know what to do.

Here I am too...same problem with my gf's optimus 7, no deplyment tool can connect to device, error 0x89731812, Zune works flawlessly.
Did you guys find the problem after warranty repair?

So, I seem to be running into this problem every 4 weeks... I am starting to hate this, I can never fix the issue aside from hard resetting my phone with a new ROM...
Anyone found a solution to this problem yet? I am currently on DFT v2 and I can't deploy xaps via PC. I can still deploy with the built in XAP deployer, but I have 2 xaps that I can't deploy using this method...

[Q] SK4G not being recognized on PC

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.