Related
First I have to state: I've already searched the web and xda-developers forums. Tried all solutions found, none work.
I don't connect my HTC Touch Pro 2 to my computer (Vista 32bit) often; other than the first few days, when I was downloading a lot of softwares to my device, I don't connect them at all. But the point is I was able to connect to WMDC.
Yesterday I wanted to try out Pocket Diablo, so I had to connect my device in order to install .NET CF 2.0. But I found I can no longer sync:
- Before I connect the device, I can see WMDC's green tray icon
- After I plug in the device (using the cable from HTC), WMDC's tray icon disappeared.
- I checked Device Manager, and found "Windows Mobile Remote Adapter" cannot start, error code 10. There was no mobile device listed.
- I tried another USB port, same result. I tried uninstalling all USB hubs and root hubs, let them reinstall, reconnect device, same result.
- With device still plugged in, I uninstalled "Windows Mobile Remote Adapter" and deleted the driver too. Then I unplugged device, uninstall WMDC driver update and WMDC itself, reboot PC, download WMDC6.1 from Microsoft again, reinstall WMDC, reboot, still no tray icon, and reconnect device with same result.
- I tried the above together with giving Users group full control on the registry key "HKLM\Software\Microsoft\Windows NT\Current Version\Svchost\WindowsMobile", same result.
- If I uncheck "advanced connection" on my device, there is no "Windows Mobile Remote Adapter" in device manager, but there is a generic mobile device listed. In WMDC it still thinks there is no device connected, and I cannot access the device in Windows Explorer.
- If I connect the device as a disk (under device's USB connection settings), I can access the device through Windows Explorer.
- I even hard-reset my device, still same result.
- I tested my old O2mini, same result.
- I don't recall any big changes on my system since my last successful connection.
- I tested my HTC Touch Pro 2 in my office (Vista 32bit), and it can be connected successfully.
So it seems the problem is in my home computer; the Windows Mobile Remote Adapter (version matches WMDC6.1's version) refuses to work in all cases.
Other than taking the sync cable in my office back home tomorrow, I'm all out of ideas of what to try next.
Can anyone give me a helping hand?
Bump. Please help, I really need to solve this.
- I'm taking the cable in office home, but I highly doubt that is the reason because with the cable at home I can connect as a disk and can charge.
- I notice in office (the successful case), the remote adapter is named "Windows Mobile Remote Adapter #2". At home (the failure case) there is no #number, just "Windows Mobile Remote Adapter".
Tested and it is not the cable. Cable used to successfully sync in office has same effect at home - Windows Mobile Remote Adapter cannot start, code 10.
I tried enabling WMDC debug log, but there're none - looks like the process failed at the driver stage and WMDC is not even started.
Also, when I have the device connected with the non-functioning driver, it seems to wreck havoc on my real network driver. I often need to reconnect my network connection.
Can anyone help?
It's getting weirder and weirder...
- I reinstalled WMDC for the countless time, and suddenly I am able to connect to O2mini (which does not connect via a network adapter). O2mini shows up in WMDC (can setup a partnership) and explorer. But not HTC TP2.
- If I disable advanced connection on TP2, I can connect TP2 as a Mobile device, but there is no network adapter. WMDC detects no connection, and I cannot view TP2 in explorer.
- I tried connecting O2mini again after TP2's failure, and O2mini cannot connect too - device manager shows no problem, but in WMDC I get nothing but the red stop sign and a simple message: "Error". No entries in event viewer.
And is anyone even reading this thread?
I was having a similar deal. Sync works solid on XP at home, was working but then stopped on 2 laptops with Vista and giving me those error codes.
I did the same things as unistalling mobile center on vista to no avail.
What did work was going onto the device, Start/All Applications/ActiveSync. Then Menu/Options and delete on the laptop PC's.
Now when I sync my vista laptop to the device it shows up as an additional device. I can copy files to it, I'm not sure if it syncs any other info.
The active sync also has an option for connections where you can uncheck "same for all pc's". I didn't try that one, but it might do something.
Update the Driver?
shealine said:
I was having a similar deal. Sync works solid on XP at home, was working but then stopped on 2 laptops with Vista and giving me those error codes.
I did the same things as unistalling mobile center on vista to no avail.
What did work was going onto the device, Start/All Applications/ActiveSync. Then Menu/Options and delete on the laptop PC's.
Click to expand...
Click to collapse
You mean removing the partnerships? I already did that - I had hardreset my TP2 for nothing too.
yrreP said:
Update the Driver?
Click to expand...
Click to collapse
I tried, but Vista said I already have the latest version (6.1.6965.0). I tried uninstalling (and fill the checkbox to remove the driver) and reinstalling, no difference.
It has to be something not right on my computer's drivers.
I'm going to compare the driver files of my home and office computers and see if there are any difference...
I copied all files related to the Windows Mobile Remote Adapter home, and compared them to mine. They are all identical.
I also tried forcing Device Manager to show non-present devices (by setting two environment variables), removed the related ones and tried again. Same result.
I'm all out of ideas now.
I'm even considering moving up to Windows 7 (Ultimate 64-bit), hoping that will solve my problems.
-- but what? They leave me with a nasty bug and I consider paying them even more? Whiskey, tango, foxtrot?
Awesome, finally i found someone that has (i think) 100% my problem.
Let me ask you this, what is your computer specs? Because this happened to me after i got a new computer >.< .
Mine is
Asus p7p55d LE motherboard
i5 50?
Crucial Ballistix 2GB (2 x 1GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600)
I also have a HTC Touch pro2 (verizon) but i have testing my computer with a Samsung Omnia (verizon) to confirm my problem.
Edit: BTW this is on a Windows 7, just throwing it out there so that people can be even more mind boggled
Asus P7P55D Deluxe
Intel i7-860
2 sticks of Kingston 2Gb
I got my TP2 from Fortress (Hong Kong), they added a bunch of goodies in the ROM, like the radio cab, 1% battery driver, a business card scanner, etc.
You have the same problem on Windows 7? I am going to buy W7 tomorrow, I'm going 64-bit...
If I get the same problem in W7, then well, damn... at least I can connect TP2 as a driver and write data to it. But if I need to install anything from the PC-side, I'll need to rip the cab out of the installer.
holy crap then i think i know why its not working. Maybe its because of the new chipset p55? Doesnt support the drivers? or something
bornskilled200 said:
holy crap then i think i know why its not working. Maybe its because of the new chipset p55? Doesnt support the drivers? or something
Click to expand...
Click to collapse
Definitely not.
Plus I have sync'ed successfully before, and my TP2 plus cable can still sync in office, advanced connection on. It's a software problem.
I encountered the exact same error in Windows 7.
The Windows 7 is a fresh install, Windows updated, and installed 64-bit version of WMDC.
Darn.
First, sorry for my very bad english.
I had the same problem ( Error code 10 with Microsoft Mobile Remote Adapter) with p7p55d and Windows7.
It was a trouble with my asus p7p55d.
- I updated my bios to the 0711 version (this version does not appear on AsusUpdate, i found it on www.asus.com)
- I uninstall old Windows Mobile remote adapter
- I uninstall WMDC
- reboot
- simply plug my phone and let windows update do the job. This time it was good for me...
I have the same issue with ASUS P7P55D PRO and Windows 7 Ultimate 64bit, even with BIOS 0711. I tried all the ideas, nothing helps.
The same problem for me.
Windows 7 64bit,
Gigabyte P55M-UD2 Mainboard
I report great success with this problem!
Like suggested from a previous poster, i did update my bios to 605 (this is for p7p55d LE). But i noticed one thing, the setting for Plug and Play was set to that the bios handled it. I changed to so the that OS (?) handled it instead and tried everything again.
Happy to say (after some extra problems that does not pertain to this error) i finally got it to work. Hope my experience help others.
Encountered a similar issue yesterday.
WMDC could not sync. Although when selected as a disk drive, it connects fine.
What fixed it for me was to disable this setting in the device: Settings/connections/usb to pc/enable faster data synchronization.
Exit out, no reset required.
Good luck.
I have the same problem since my new gigabyte p55-ud5
i have windows 7 Ultimate. my htc diamond work fine for one week, then it stoped sync.
i think its somthing with the memory....
i tried to change the speed on my corsair DHX 2GB from 1600Mhz to 1333 and it worked for couple of days.
then it stoped sync.
tried to add voltage in bios but no good.
updated the bios - then it only worked with memory speed 1333 or 1066.
i shutdown my computer only once in a week.
then it started again. now no matter what i do - no SYNC.
i searched for this error alot and the common hardware is:
P55 + vista/win7 + HTC.
PLEASE HELP!!!!!!!!!!!!!!!!!!!!!!!!
Firm-up!
i have a good news!
Finally i got it after firm-up the bios.
Asus p7p55d turned out to got a problem installing 'Windows ... Adapter'
http://www.asus.com/product.aspx?P_ID=RBA8CzWoopUlYRFZ&templete=2
.
Description P7P55D 1002 BIOS
1. Fix PCI-E X16 may downgrade to X1 mode
2. Improve system stability
Good Luck!
Hi all!
I need your help to get this thing working, without necessarily
1: Install Ubuntu on one of my boxes
2: Debug through VirtualBox
I have been mucking about with getting ADB to recognise my Kaiser but it's been a long run uphill without any results. I'd like to ask you guys/gals if you have a fully working adb debugging environment with your Kaiser in Windows 7, 32 bit AND 64 bit. I'd like to know for three reasons
1: I have two boxes with either version of Windows 7
2: I have a Kaiser I'd like to be able to debug so I can help out as best I can
3: It would be a great addition to the wiki I'm authoring
So, if you have and/or know a debugging environment set up, please provide details on what to get, where to get it and how to install it.
I have been searching this forum up and down and used Google but this is seriously kicking my butt right now . Thank you all in advance!
Another option would be to make a dual-boot machine, although i'm not certain how this would work with Win7, only done it on XP, however I'm sure it's relatively simple.
In fact if it wasn't for the fact that I need my desktop as a file and print server it'd be dual-boot already.
I'm resurrecting an older laptop at the moment purely as a linux box to use as a dev environment, which is fun as anyone who has an acx100 wifi chipset will tell you (having to go back to Ubuntu 6.10, which is the last fully acx100 aware version I can find).
Dual booting involves either, repartitioning your hard drive, or installing another drive for Linux, I find having about 10GB is enough with maybe 1GB or so for swap, this is usually plenty for a decent dev environment with a lightweight GUI like Xfce or even Enlightenment, if you want bells and whistles, (Gnome or KDE), maybe as high as 20GB.
Some feedback
I've been trying to do this on two Windows boxes for a couple of hours and I have to say, it's pretty amazing that I can't seem to get this working in any other way that either installing Ubuntu or Windows XP.
I've been trying the drivers that came with the Android 2.x SDK because these should be working. Is there anything preventing these drivers from working on our Kaisers and should I in that case get other ones (please provide a link)?
I'll try using a Live CD of Ubuntu and boot up my 64-bit box and see if I can get that to behave. Will report back as soon as its done.
It may be something weird, because I connected my kais130 to my old armada 500 laptop yesterday, which is running an old 6.10 version of Ubuntu, and it connected in USB with not a care in the world, powered down, swapped drives to my XP drive, and rebooted, it too detected the kais, yet on my 1.6Ghz dual core netbook, not a flicker, even running the latest 9.10 ubunto on live cd, not a thing.
I'm starting to wonder if sometimes the lack of connectivity is down to hardware on the PC side?
My old laptop however hates even ubuntu 6.10, so I may have to go to another lighter distro, probably slackware based, in order to get decent speed without the damn memory hog of a gui ( gnome or kde ) and the ability to compile my acx100 module without all the ubuntu hand-holding sudo stuff getting in the way.
I just finished a guide on the wiki I'm authoring to get debugging up and running on Ubuntu 9.(Karmic Koala) and it worked on two of the machines I got around here. One of those machines is the one with 64-bit Windows 7 which I couldn't get to work before.
I threw in a Live CD of Karmic Koala and made a couple of changes to the udev rules and it worked from the first get-go. Same with the other computer, which is a laptop which just so happens had Ubuntu installed in it already. I followed the guide I wrote and it worked without a hitch.
My limited knowledge about drivers and hardware leads me to think there's something going on with either the driver having a problem realising there is an Android based device connected to it, or it is something else entirely.
I wish I had a it more knowledge about these things, if nothing else to be able to get some kind of log/dump/debugging info out of Windows that I could share with the rest of the people around here, which might make us nail down the culprit and get rid of these problems for good. Or until the next version of Windows gets released.
Anyways, it is now up and running on my Ubuntu-laptop, so now I can at least get some more info about what's going on in Android when it locks up, freezes or just FC's.
Ditch VirtualBox. USB support on it is pretty crappy.
I build all of my roms on Ubuntu sitting on VMware Player. Very seamless experience.
Hey all. Phone freakin rocks, and the OTA update to allow us to use WHAT SHOULD'VE BEEN THERE IN THE FIRST PLACE is great.
However, I'm having issues with getting the native USB tether to work.
I connected my phone to my Windows 7 Pro 32-bit netbook with USB debugging enabled. It said it needed drivers, so I had it install the necessary drivers. It was having problems with the ADB USB drivers so I found the solution on this forum and installed the fixed driver.
I go to the Settings menu in the phone, go to Tethering and enable USB tether. After a small delay, Windows 7 tells me there was some a problem installing the device driver, no driver found. Device Manager shows "Android Phone" under Other, and no matter what I point to the USB driver won't work.
I disconnect the phone, turn off USB debugging, and reconnect. Same problem.
I disconnect again, turn USB debugging back on, reconnect, and told it to turn on Mass Storage. Still no dice.
I'm puzzled here, as numerous reports state that It Just Works. Wonder why I'm having issues.
I haven't permrooted just yet - still using Visionary. Let me know if this is an issue.
Sent from my T-Mobile G2 using XDA App
USB Tethering
Here, I had this posted under USB Tethering. You just need an INF file.
You got the OTA update that enables wifi calling and usb/wireless tethering, right?
On your G2 Go to Settings, Wireless & networks, Tethering & portable hotspots, Help.
Under this help guide, go to the website link for USB listed there.
Go to this website and choose "USB Tethering with Windows XP"
Download the INF file "tetherxp.inf"
On your G2 check the "USB tethering" option, and connect your G2 via USB cable to your computer. Instead of using windows to automatically seach for drivers, direct the wizard to the "tetherxp.inf" file.
This will also work for Windows 7 if your having problems tethering there.
baquiller said:
Here, I had this posted under USB Tethering. You just need an INF file.
You got the OTA update that enables wifi calling and usb/wireless tethering, right?
On your G2 Go to Settings, Wireless & networks, Tethering & portable hotspots, Help.
Under this help guide, go to the website link for USB listed there.
Go to this website and choose "USB Tethering with Windows XP"
Download the INF file "tetherxp.inf"
On your G2 check the "USB tethering" option, and connect your G2 via USB cable to your computer. Instead of using windows to automatically seach for drivers, direct the wizard to the "tetherxp.inf" file.
This will also work for Windows 7 if your having problems tethering there.
Click to expand...
Click to collapse
Yeah, I saw that help link. I didn't think I needed it since I was on a Windows 7 machine. I'll go take a crack at it since at worst I'll just be back at square one.
Thanks for letting me know!
I used the driver for the HTC Hero for windows vista just google it. I have the vista drivers installed on windows 7 pro and it works great, its even faster then PDAnet which I used since my 1.6 phone days.
Sent from my T-Mobile 7 inch space banana
I have windows 7 and I installed pdanet because it has the drivers.
Sent from my T-Mobile G2 using XDA App
I am having same trouble to and I have Win7-64bit. The pdanet drivers only seems good for the adb functions. The tetherxp.inf is not being recognized at all for me.
Same issue
Hey guys, I can't tether my G2 / Vision to my Windows 7 64-bit machine either. Same issue as you all are having. The tetherxp.inf seems like it might work, but possibly only on 32-bit machines.
Is there a driver that will work on Windows 7 64-bit?
pcgeek86 said:
Hey guys, I can't tether my G2 / Vision to my Windows 7 64-bit machine either. Same issue as you all are having. The tetherxp.inf seems like it might work, but possibly only on 32-bit machines.
Is there a driver that will work on Windows 7 64-bit?
Click to expand...
Click to collapse
I got this working once using drivers downloaded from this forum. They worked.... S l o w l y. Maybe my laptop's usb sucks, but in any event it was enough to drive.me crazy.
I got MUCH better performance using wifi tethering. I just use the usb cable to keep the wifi & 3g radios from sucking the battery dry.
Sent from my T-Mobile G2 using Tapatalk
pcgeek86 said:
Hey guys, I can't tether my G2 / Vision to my Windows 7 64-bit machine either. Same issue as you all are having. The tetherxp.inf seems like it might work, but possibly only on 32-bit machines.
Is there a driver that will work on Windows 7 64-bit?
Click to expand...
Click to collapse
Im on a Windows 7 64bit machine and Tether(wireless and USB), ADB and Fastboot all work perfectly, I had to install HTC sync to my home computer to get the right drivers. The HTC sync program doesnt work with the Tmobile G2only with the Desire Z because it is Sense based, but it will install the right drivers for the G2, just install it from the following link and then hook up your G2 or Desire Z to your computer and it will install the right drivers for you:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1058&news_id=804
Just a side note make sure you are using the micro USB cable that shipped with the phone, some people were having problems using other micro USb cables.
WOW
You guys still haven't figured this out? I've been USB tethering on my XP/Vista/and 7 box since the day i got the new OTA. You need the proper drivers and also have to configure windows to use RNDIS.
It is truly that simple. I've walked many people through this already and have now started charging!
BTW
All of the methods described by the majority of the members on this site are just way too many steps. You don't have to do anything other than install 2 proper drivers. You don't need PDANet nor do you need HTC sync. You just need to be tech savvy enough, not fone savvy.
Stop trolling!
Android1126 said:
All of the methods described by the majority of the members on this site are just way too many steps. You don't have to do anything other than install 2 proper drivers. You don't need PDANet nor do you need HTC sync. You just need to be tech savvy enough, not fone savvy.
Click to expand...
Click to collapse
Seriously, I've seen u post the same thing in forum after forum without actually helping anyone... do that business or get the pot. Why on earth would you rather have people email u privately for your "wisdom" instead if just posing it?
Stop trolling.
here is the link to the driver for win7 and vista:
handheld.softpedia.com/progDownload/HTC-Hero-Drivers-Download-81097.html
here is where I found it at:
ozamora.com/2010/11/usb-tethering-htc-g2/ (the forum bot doesn't let me post a link with http:...etc. so you have to copy and paste the address yourself)
you can also search google for HTC_Driver_64.zip or HTC_Driver_32.zip
if the option to install doesn't come up automatically when you connect your G2 to your PC via USB do one of the following: hold down the windows key and hit the Pause/Break key OR click the start button (left lower corner of your screen), then find the word 'Computer' on the right of the start menu. Right click on it and click properties on the sub-menu that pups up. If you did it right you should be at "Control Panel\All Control Panel Items\System". In the left upper corner click on Device Manager. Find the device with the yellow triangle, it should say something like unknown Android device. Double click it and then click update driver. On the GIU that comes up do not select automatic, select browse my computer for driver software. Click browse and navigate to the folder where you saved and unzipped the HTC driver like "C:\Users\username.computername\Downloads\G2_HTC\HTC Driver". Be sure to check the option include subfolders. Click next, follow propts and you are done. You want to be smart about this for future use copy the uzipped driver folder to the SD card of your phone.
BTW Android1126 is a scamer, do not contact the f*&#er.
zero_0 said:
BTW Android1126 is a scamer, do not contact the f*&#er.
Click to expand...
Click to collapse
You may very well be retarded. You clowns sound like the guys from the HTC forum pertaining to this. Learn how to read. I've helped more people than I could even count with this particular problem, and what's a scamer? You really shouldn't be playing with your cell phone. Actually no, keep it up. HAHA.
"Wisdom", I'm not about to walk a million noob's (no offense, i am one too) through something so easy that they have made difficult for themselves. I'm not on the level of many of the guys on this site to be walking anyone through anything on a forum, though if I had to do it, I'd prefer an audience who would understand my direction. Both of you palsy stricken idiots definitely do not fall into that category, which is probably why you didn't receive my help previously. You can't post a definitive solution to a problem that could arise from a number of different scenarios, and even if you could, I never claimed to be up for it.
Hope you've both learned how to use Windows and your phones.
Guys.... The purpose of this thread is to help people, not alienate them.
Anyway, HTC sync may not be the *best* way to get the drivers on the phone, but it's certainly one of the easiest to explain. All that matters is getting the ndis drivers somewhere windoze will find them.
I said before in this thread that I got better performance using wifi tethering, but that's probably because the usb on my laptop has an attitude problem (adb issues even on a fresh windows install). Best part of that option is that the driver issue is avoided.
Sent from my T-Mobile G2 using Tapatalk
im coming from the incredible forums, im running Cyanogenmod 7 RC4, and im pretty sure its the same type of USB/Wifi tethering mechanism. ive searched everywhere, but i cant find the RNDIS drivers anywhere. if you seriously know how to hook up our devices to windows 7 (preferably 64bit lol) without using outside programs like pdanet, please post it here. thank you!
TheWizKid95 said:
im coming from the incredible forums, im running Cyanogenmod 7 RC4, and im pretty sure its the same type of USB/Wifi tethering mechanism. ive searched everywhere, but i cant find the RNDIS drivers anywhere. if you seriously know how to hook up our devices to windows 7 (preferably 64bit lol) without using outside programs like pdanet, please post it here. thank you!
Click to expand...
Click to collapse
(worked for me on Windows 7 32 bit, hope it helps you)
Dude, go to your device manager.
Find the Device with the little ? and then maybe a yellow !.
Right click that device and select Update Driver.
When the window pops up (on Windows 7 32bit), select, Browse My Computer for driver software, then on the next screen, click on the bottom that says, LET ME PICK.
Then it will ask you the device type.
Here you go down to Network Adapters.
Then when it asks you to select manufacturer, skip Microsoft and select Microsoft Corporation.
Then, select Remote NDIS based Internet Sharing Device.
Hit next, it will say it's not safe, etc etc, proceed to install it.
You should be set. I hope that helps.
Android1126 said:
(worked for me on Windows 7 32 bit, hope it helps you)
Dude, go to your device manager.
Find the Device with the little ? and then maybe a yellow !.
Right click that device and select Update Driver.
When the window pops up (on Windows 7 32bit), select, Browse My Computer for driver software, then on the next screen, click on the bottom that says, LET ME PICK.
Then it will ask you the device type.
Here you go down to Network Adapters.
Then when it asks you to select manufacturer, skip Microsoft and select Microsoft Corporation.
Then, select Remote NDIS based Internet Sharing Device.
Hit next, it will say it's not safe, etc etc, proceed to install it.
You should be set. I hope that helps.
Click to expand...
Click to collapse
P.S. btw you may have to remove other drivers you tried to install first. Good luck, let me know if it helped.
I had to do that twice, but I got it to work. Thanks, man.
Mmm at last, the thing was discovered, and just experimentation is needed, so we can test the syncing (Cheack Thread Page 3).
Old post text:
Code:
Mmm as I am far from a selfish guy, and have been asked about this, i think that i will share in an independent thread for anyone to see.
Note that this comes from my own ideas, not tested as i cannot use MTP protocol anymore.
[SIZE="5"]Responsability Disclaimer[/SIZE]
This may be agains DCMA or laws about reversing in your country. It's not probably being that way as is a development to interoperate with an unsupported OS (linux) and its one of the exceptions, but i'm not responsable for any liability you can have or imagine.
[SIZE="5"]What is this for?[/SIZE]
This is the procedure to follow before thinking in hacking the phone itself, trying to get to write and read files from the device.
It could faild and serve to no purpose or be gold, depending on the success of the tests.
In the best case, this will lead to the reading and writing of files at will to the device storage.
[SIZE="5"]USB protocol Pre-Knowledge (fast)[/SIZE]
I know you dont wanna know about it, and i am far from an expert but i must just express that USB devices support two operations:
[B]Bulk Transfers[/B] -> Big chunks of data, used mostly for the common data transfers up to 512Bytes per transmission (at a max/time).
[B]Interrupt Transfers[/B] -> Short chunks of data, used for changing settings on the device or short burst of information.
For your personal knowledge, MTP protocol instructions are bunch of hex codes and [U]they use bulk transfers for all of the MTP instructions[/U].
[SIZE="5"]Required items - Gathering[/SIZE]
- Working Kin
- Windows OS as host OS
- USB sniffer / monitor (I like Usblyzer, has trial for 30 days)
- CPU with virtualization capabilities (google how to check)
- Vmware
- Mac OSX image dvd (Snow leopard)
- Software & registration from MacSpace for Kin Media Sync
[SIZE="5"]Procedure[/SIZE]
- Unplug the kin & close all zune software opened.
- Install OSX in an vmware machine
- Install and setup Kin Media sync for mac
- Kill the process that launches zune when you plug the device ("ZuneLauncher.exe")
- Plug the kin now. Use a port where no other device is, so try to put it not together with other usb device like mouse/keyboard which could send packets and confuse the capture.
- Install and setup usb sniffer for windows.
--- Set it to sniff/capture at the USB port where the kin is (it's a tree view structure, so easy to see where to put the check). [U]Dont do it at the left of the KIN device!!![/U] do it on the bus/port as you will disconnect the kin later. Press start capture.
--- Open the zune software and visually check that the sniffer is capturing data (eeeeeeeeeeeeaaaaaaasssssyyyyyyy as it appears there). If it doesnt, you'r doing it wrong, probably cause the port/bus issue.
--- Close zune
--- Reset the capturing (stop, dont save, start).
- Open the virtual machine if it isnt.
- In the virtual machine you should have Kin Media Sync installed, which autolaunches if you have plugged the phone (virtually).
- In the virtual machine window bottom right (vmware border) you will see an item with usb icon. Hover over it and see if the tooltip says KIN. If there are more, look for the right one. Right-Click on it and pick "Connect (Disconnect from host".
- Hopefully, the usb sniffer on Windows would turn mad and begin capturing data, while Kin Media Sync is opening on the OSX virtual machine.
- I cant remember if it does put the label "Connected" at the Kin (you should remember that window from the Zune syncing :P). If it does, close Kin Media Sync and stop the capture on the windows usb sniffer. Else, do a sync before closing (doesnt matter what).
- Save the captured log as a file (in my case, Usblyzer file).
[SIZE="5"]Yeah, but why this is better than other software?[/SIZE]
Other users (and myself) have tried software that uses the MTP software which has some success on getting info from the device but fail when it comes to do reading or writing to the device.
I guess it's probably because the rest of the protocol, the private part that microsoft uses (MTPz) has some control values through the usb that turn on/off device properties, among ones is the one to write/read files.
My first idea was to understand this through the Zune software, but as i said many times, it uses DRM (Janus) to protect the songs (sigh!) and the mtp specification varies if using DRM protection, so i can never find out a way to solve it, without hacking the Zune software cryptography itself (not my intention at all) or became an old man finding how to bypass it. In any case, the Zune software does a RSA challenge-response handshake to the kin before calling to MTP-OpenSession, i can assure that, so its out of reach.
On the other hand Kin Media Studio for the OSX has no official DRM and it can just do easy syncing, so it's pretty much obvious for a dev guy (i am, haha) that its an easiest way to replicate. So i tried to go that way and i was correct, so it just does normal operations through usb and control interrupts.
The problem is that the native sniffers from OSX only capture 16 bytes of data through the usb bus, so messages over that cipher were not reachable for me at the moment. I contacted apple USB master guys about getting a bigger limit, and the resumed answer was something (just much more politely) like: "you'r screwed & stuck with 16 bytes".
So the only approach is to emulate Kin Media Sync in an OSX virtual machine under a windows os machine for the best sniffer software. Another bad point for the fruit logo machines.... (and i'm an owner... imagine a hater!). Here is why I stopped, as my normal working device (laptop) is kinda old and has no VMX/virtualization support, so i couldnt setup the virtual machine for OSX, stopping all the needed setup.
[SIZE="5"]From sniffed data to magic[/SIZE]
At this point, comes the complicate part. Understanding & testing the packets sent to the device to make things work. This is the part where i was going to operate with a new device or my current one if it wasnt bricked/stuck.
The problem appears with this structure (what is on the logged sniffed session):
- Plug the device
- Device <-> OS Handshake (Interrupt/Bulk transfers possible)
- Kin media sync queries (Interrupt transfers)
- Kin media write/read enable (Interrupt transfers)
- Kin media MTP Open session (Bulk transfer)
- Kin media MTP GetStorageInfo (Bulk transfer)
..... more MTP xxxxx (bulk transfer)
- Kin media MTP Close session (bulk transfer)
- Kin media write/read disable (Interrupt transfers)
- Kin media bye bye sync queries (Interrupt transfers)
(if unplugged, the ones below)
- Device <-> OS Goodbye (Interrupt/Bulk transfers possible)
- UnPlug the device
As some of you may realize, normal MTP software used didnt make the "read/write enable" cause the kin is not a standard device. So they fail. Once some person identifies which of this interrupt values make the kin "Connected" window shown and also enables it to be writable, profit comes.
So to test this and later make it published, you need a program to communicate with the device itself and do what some of you called "send hex codes to the kin" (which technically is "bulk and interrupt transfering values to the kin")
There seems to be none, so i code one from scratch and could polish it a bit and giveaway as a Netbeans C++ proyect.
I had some success and it works ok as i reused it(almost all the code) to operate my G15 on linux, iluminating keys and using the LCD pixels.
[SIZE="5"]This can brick my device?[/SIZE]
The short answer to this is NO. The long answer is no again, but cannot be sure of what happens enabling the the device settings while testing. It may become frozen and need to be restarted for example.
During the few test i made, mine refused to operate within my usb program and it was autosolved by libmtp-tools, which did a protocol reboot and it just work as is without doing nothing.
Anyway, i was aware that it was better than getting stuck with the phone "as is".
mmm All being said above, i just leave space for you guys to think what you wanna do with the info and questions that may appear.
Thanks but Hardware Virtualization came up as a no on my laptop.
I hope someone else tries.
I know I know I have to change my username as there are many similar and it gets confusing.
Thanks for taking the time for all the above text
I had a quick read-over what you put, but haven't looked at everything in detail. My wife had a baby yesterday morning, so I'm finding myself rather busy as of late.
Anyway, I'm more than happy to run some tests. Here's what I have access to right now (at home), with much more available when I get back to work in two weeks:
XPS m1530 laptop running x86 Windows 7 (dual-boot to Ubuntu 10.10 running as the Joli OS front). No Hardware Virtualization available for this system, though it can run VMWare for 32-bit Windows OS's.
Macbook Pro (Intel 64-bit archetecture) running 10.6.7 Snow Leopard. Can set up virtual machines if needed, using VMWare, but I'm not sure if that's necessary or not.
Powerbook G4 (PPC) running 10.5.x (latest 10.5 build). Can't run virtual machines, but can be used if another source is helpful to trace.
My personal KIN TWOm running the M OS build. Can technically be reverted back to the TWO (non-M) OS, but I'd rather not lose everything as it's my working phone.
My wife's TWOm, not activated. I can probably play with this more, as she isn't ready to use it yet, but I'd be in trouble if I bricked it.
At work, I have access to a number of different computers and OS's, as needed. I don't think this would be necessary, but they are still there.
John, can I ask where you're at? I've gotten the notion that you're not in the US, as you've said you don't have access to a CDMA network. Is there any way we can get your phone to a US Verizon store for assistance?
klamation said:
Macbook Pro (Intel 64-bit archetecture) running 10.6.7 Snow Leopard. Can set up virtual machines if needed, using VMWare, but I'm not sure if that's necessary or not.
Click to expand...
Click to collapse
This has hardware capabilities (VMX feature), but you should have to install XP (or 7) through bootcamp and then install the OSX there, as the host must be windows. Anyway, you'r "lucky" as 64 bit machines can get up to 32 bytes from the usb bus, so 2x my limitation (not enough but more).
klamation said:
John, can I ask where you're at? I've gotten the notion that you're not in the US, as you've said you don't have access to a CDMA network. Is there any way we can get your phone to a US Verizon store for assistance?
Click to expand...
Click to collapse
I'm from Europe, so most phone network is common GSM with some 3G implementations. I didn bought the phone from verizon, so have no relation to them and hence, no way to give them the phone expecting a working return (why should they in any case?).
johnkussack said:
This has hardware capabilities (VMX feature), but you should have to install XP (or 7) through bootcamp and then install the OSX there, as the host must be windows. Anyway, you'r "lucky" as 64 bit machines can get up to 32 bytes from the usb bus, so 2x my limitation (not enough but more).
Click to expand...
Click to collapse
After I read the details of what you want to do, I thought the same thing. I have 64-bit Windows 7 set up on a bootcamp partition (I actually use VMware Fusion to run it, most of the time, but can natively boot into it, if I need). I have never been successful at setting up an OSX VM though, as it's not officially supported. If you have any reference on how to do it, I'm all ears. I'll do more research into it after posting this.
johnkussack said:
I'm from Europe, so most phone network is common GSM with some 3G implementations. I didn bought the phone from verizon, so have no relation to them and hence, no way to give them the phone expecting a working return (why should they in any case?).
Click to expand...
Click to collapse
Considering the phone is less than a year old, it should still be under warranty. I know I've taken phones into their stores before and had them reimage them. I should try that with the KIN to see if they can do it (if the stores actually have the ability to reimage a KIN phone, indicating they have a ROM of it)
I could assist, I have a tri-boot of vista, 7, and OS X.
I doubt that there is a 128 bit processor emulator, let alone the OS...so wouldn't a solution be to use the same technique ,but "freeze" the process to collect data being transferred?
When I mean freezing, I mean slowing the USB data transfer speeds (using hardware underclocking, on the computer and/or phone)
@klamation
http://www.redmondpie.com/how-to-install-os-x-snow-leopard-in-vmware-windows-7-9140301/
Also, it could be a hackintosh image, i guess. At least if it is able to install the kin media sync software...
awesome71717 said:
...
Click to expand...
Click to collapse
i didnt understand anything beyond the 1st line.
there is no need to slow anything as it was a OSX kernel limitation thing, period.
John,
Why do we need 64bit vmx capability to capture messages when the Zune Software is successfully messaging with 32 bit on windows machines? Obviously I am missing something important.
Dave
kintwouser said:
....Dave
Click to expand...
Click to collapse
You'r missing a more detailed reading of the first post.
Quoteing myself:
My first idea was to understand this through the Zune software, but as i said many times, it uses DRM (Janus) to protect the songs (sigh!) and the mtp specification varies if using DRM protection, so i can never find out a way to solve it, without hacking the Zune software cryptography itself (not my intention at all) or became an old man finding how to bypass it. In any case, the Zune software does a RSA challenge-response handshake to the kin before calling to MTP-OpenSession, i can assure that, so its out of reach.
Click to expand...
Click to collapse
John, I was talking about halting the processor of the phone to allow the cache of data to be recorded and cleared. Once cleared, the processor will resume and the cycle can be repeated until the data is fully collected.
Anyway, has anyone found a jtag port on the board?
awesome71717 said:
John, I was talking about halting the processor of the phone to allow the cache of data to be recorded and cleared. Once cleared, the processor will resume and the cycle can be repeated until the data is fully collected.
Anyway, has anyone found a jtag port on the board?
Click to expand...
Click to collapse
I guess that it would be feasible in a parallel universe. And not mentioning that it's a host os "problem" (st#### OSx), not the phone fault.
Also please posting random ideas without thinking about what you say. A jtag? really?
And in the random case where you can plug one JTag cable/homemade adapter.... how the hell will you use it? with what program? with what known hardware specific schematics?
We cannot handle a USB writing... forget about other access...
Trying to start up Mac OSX 10.6 on a dell 630 laptop but keep getting a cpu has been disabled by the guest operating system error. Maybe I can get a newer copy of MAC that will work.
@ kintwouser
If you are having problems, look for kexts oriented around vmware or your own hardware if you're using hardware acceleration.
@John
Ah. Well then I'll just hop into my Delorean that I modified to travel to alternate dimensions, rather than just through time.
Ok ok I'll try to resist irking you any further.
I just reread the Kin Media Sync to asure it, and you can install it over a 10.5.6 Osx which is the labeled "Leopard" (as is), so i guess easier to get.
Maybe a little hackintosh image would do the same thing, as we dont really need compatibility... as long as the Media Sync works i wouldnt care about having audio on the virtual machine, or networking.. whatever.
On my own plain of existance, i tried to follow the url i posted and went till 95% of the installation, but Virtual machine didnt keep installing, so i had to turn the pc (was about 3 hours). I guess i will try with another different image or my official leopard dvd's.
It's kinda weird in my case, using a macbook with windows to vitualize a OSX... haha.
I've been trying to install SL for about 30 hrs now with no success. I've tried three different versions. VMware 7 is OK here but ACPI errors keeps disabling the CPU during osx install. I have edited the vmx file to no avail. Some suggested that I need kext files but I can't install them if osx isn't installed. I'll keep trying as it is a quest now.
don't know if i am breaking the agreements of this forum since i didn't read it (ala the latest south park episode) but here:
http://tehparadox.com/forum/f51/snow-leopard-10-6-6-vmware-hackintosh-newbies-1973493/
No editing needed. You just need to get VMware Workstation from the official site and use that custom vmware osx image. I have tested it and it works. Now if only I had the phone I could really do some testing.
zero2duo said:
don't know if i am breaking the agreements of this forum since i didn't read it (ala the latest south park episode) but here:
http://tehparadox.com/forum/f51/snow-leopard-10-6-6-vmware-hackintosh-newbies-1973493/
No editing needed. You just need to get VMware Workstation from the official site and use that custom vmware osx image. I have tested it and it works. Now if only I had the phone I could really do some testing.
Click to expand...
Click to collapse
Great find, i'm downloading it atm. Well, i think they could have chosen a (mega)better site but's ok. Queued downloads.
I will try the "installation" in my bootcamped windows XP plus vmware and then kin media sync.... Now I need a phone too, heehehehehe.
John,
I got a 10.6.7 VM running on my Win7 bootcamp partition. I followed the steps you mentioned and was able to capture some USB sniff/trace logs of browsing the device and copying a file. (inexperience during the initial sync missed the bulk of the sync).
You can find the file at www.kyleandelin.com/KIN - let me know if this helps or if you need something more?
Phew, i saw a little pack of problems hahaha (unexpected!)
While i stopped doing this, there was a new version released (2.0) and its format is not readable with 1.6 (version i have).
Installing 2.0 didnt solved the issue, as it says that was captured with a 64 bitOS version and it's not compatible with 32 bits version..... The 2.0 is the first one that included the support for 64 bits.
Man, this is all against us haha.
So... possible solutions:
- Install v1.6. May not work on 64bit os
- Install v2.0 as 32 bit verison. May not work on 64 bits or may be autoinstalled and set to 64bits.
So... what to do from here:
Please, confirm my theory before going further.
- Perform a capture from unplug state (needs to be from start). Must include the plugin till kin shows the connected status.
- Stop the capture session.
- Check the captured data in usblyzer.
- Look for the first "Request" column with "Bulk or Interrupt transfer" value.
--- If there is no suck column in all the capture session, the whole process is futile (no MTP protocol would have been transfered) and we should rethink our options.
--- If there is, please check that its column "Raw data" contains at least "10 00 00 00 01 00 02 10 ... " or a very close value.
If i'm right, and the column matches, it means that usblyzer has successfully captured the mtpz OpenSession request. Also, if it was that way, the "magic" instructions would be the before it.
If there are more than 1 and it's not the first one, please check for it .
I am finally gonna get a new (working) device, so i think that things are going to be a bit fun in some time.....
This time, just MTP, no Qualcomm random options testing.. (hahahahaha)
Hi guys,
I wonder if anyone can help with this problem?
,
I'm having trouble hooking it up to my PC which is running XP.
When I chose to connect as either "Media Device MTP" or "Camera PTP" I get an error message on the taskbar of my PC:
"USB device Not Recognised. One of the USB devices attached to this computer has malfunctioned , and Windos does not recognise it. For assistance in solving this problem, click this message."
I click the message and get taken to the list of USB devices with one in bold stating "Unknown device", I click on it and try to update the drivers etc but PC is unable to instal newer drivers.
I think I've narrowed this down to an MTP (Media Transfer Protocol) driver not being installed on the PC, so have installed Windows media player 11, Kies, Samsung PC Studio 7, tried searching the net for drivers, even tried installing Galaxy S2 drivers and none of them work.
Does anyone know what else I may be able to try, or can someone tell me where I could get the correct driver as this is starting to drive me nuts...
PS. I have hooked up the Nexus to my work PC (running Vista) and was recognised withing seconds, so is not a faulty phone
Thanks in advaance for you help!!
format c:/q
install Windows 7
Windows XP is 10 years old.
oscillik said:
format c:/q
install Windows 7
Windows XP is 10 years old.
Click to expand...
Click to collapse
Was really hoping it wouldn't come to that!!!
Is there no way I can get the drivers in XP?
oscillik said:
format c:/q
install Windows 7
Windows XP is 10 years old.
Click to expand...
Click to collapse
Hah, you posted what I managed to resist writing. I thought to myself 'someone's bound to bring that up'... Right on time!
Just get WiFi file explorer PRO and sync through wifi...but I'm quite sure that you can get MTP to work on winXP.
Can't really help you with the Galaxy Nexus since mine hasn't arrived yet but for my Galaxy Tab 10.1 I didn't install any driver (honeycomb also only understands MTP). I let windows install all the drives automatically, had to restart a couple of times but in the end I had a working connection with no Samsung crap like Kies installed.
gambiting said:
Just get WiFi file explorer PRO and sync through wifi...but I'm quite sure that you can get MTP to work on winXP.
Click to expand...
Click to collapse
I've got this as the work around at the moment, but finding it a bit laborious having to transfer one file at a time.
Finding that Samsung website is quite useless - only has the User guide as downloadable PDF.
Microsoft website is even less helpful...!
sw.monkey12 said:
I've got this as the work around at the moment, but finding it a bit laborious having to transfer one file at a time.
Finding that Samsung website is quite useless - only has the User guide as downloadable PDF.
Microsoft website is even less helpful...!
Click to expand...
Click to collapse
You can transfer as many files as you like....up.
And to be honest you can also try using an FTP server, it works very well and then you can browse your phone easily.
gokpog said:
Can't really help you with the Galaxy Nexus since mine hasn't arrived yet but for my Galaxy Tab 10.1 I didn't install any driver (honeycomb also only understands MTP). I let windows install all the drives automatically, had to restart a couple of times but in the end I had a working connection with no Samsung crap like Kies installed.
Click to expand...
Click to collapse
Is that with XP?
I thought I was getting there after installing WMP 11 as I got a message stating "Galaxy" when I connected the USB cable, but it still didn't work fully.
A couple of re-boots later it resorted back to "USB Device not Recognised"
Hope the Nexus conmects for you when it arrives
gambiting said:
You can transfer as many files as you like....up.
And to be honest you can also try using an FTP server, it works very well and then you can browse your phone easily.
Click to expand...
Click to collapse
Do you mean that you can upload multiple files in one go with Wireless file transfer Pro?
with music for eg. I'm having to do one track at a time?
Will look at the FTP servers now, any recommendations?
sw.monkey12 said:
Is that with XP?
I thought I was getting there after installing WMP 11 as I got a message stating "Galaxy" when I connected the USB cable, but it still didn't work fully.
A couple of re-boots later it resorted back to "USB Device not Recognised"
Hope the Nexus conmects for you when it arrives
Click to expand...
Click to collapse
Sorry no, it was something worse, Vista.
If you got xp to recognize it as "Galaxy" you should be on the right track. I remember that being the first device in Vista too. The auto update feature installed various Samsung updates, always after the device couldn't be started and almost all of them required a restart. But about five of these updates (and restarts...) later it connected correctly. No Samsung software necessary.
Don't know if that was dumb luck but I'm not complaining.
I have missing MTP driver on my WIndows XP laptop for work (I use Win 7 at home) is there any solution to this yet?
Try this.
It will install the Media Transfer Protocol Porting Kit (MTP drivers) on Windows xp and should allow the device to be recognised.
I uploaded the file (which I downloaded directly from Microsoft) so you dont have to validate first. Download it *HERE* and install.
Let me know if it works for Windows xp and I will add it to my fixes section im writing.
Mark.
Thanks, Mark,
I did find and download that file earlier but it didnt work. However, as my work laptop is subject to Group Policy, it may still work for others. I do have local admin rights on my machine so I wouldnt have thought it would be a problem but we always get quirks with our corporate builds.
I have found other references on the net to a file from Creative called "fixup.zip" which apparently includes the MTP drivers (tweaked to also allow recognition of creative devices) but I cant find anywhere to download it from.
after a little searching with Google i found the answer
so my laptop runs XP (because i shoot tethered to my Canon Camera and i know it works) and i use the laptop to sync my phones (also collects my e-mail etc) and i stumbled on this thread when i was searching for a solution as to why MTP failed to install with my new Nexus..
the solution is
to install Windows Media Player 10! once i did that, BAM! i can see my Nexus in the explorer window with the rest of my drives
oscillik said:
format c:/q
install Windows 7
Windows XP is 10 years old.
Click to expand...
Click to collapse
HAHAHAHHAHA made my day
Here you go. My work laptop is still xp(32bit) and i just installed this and works
http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW
Verizon_Wireless_I515_Galaxy_Nexus_USB_Driver_v1.4.6.0.exe
New "known issue" - samsung!
I had issues trying to get the device working on 3 computers yesterday (Win 7, Vista, XP) , with only interment luck.
I got to Samsung Level 2 support, at 2pm EST, I was his first G-Nex call. We tried the Samsung driver, updating WMP to v11 on XP. Best I got was it to open sometimes (best after a GNex Reboot or after almost shutting it down: ie. holding power button in ant hitting back arrow). It opens best on my Vista PC (one I hardly use...); Sometimes I open it and get no further than the device level (GALAXY NEXUS); if Internal Storage eventually shows up, you may be able to get in; then you MAY be able to transfer files to the folders.
I got a call back from SAMSUNG Level 2 today: "THERE IS A KNOW ISSUE IN THE MTP LAYER OF THE PHONE; THERE ARE ISOLATED CASES OF PROBLEMS LIKE YOURS; SAMSUNG & GOOGLE ARE WORKING TO RESOLVE AND ISSUE A MAINTENANCE RELEASE". (As close as I can quote this.) No, there was no estimate of WHEN this would be released, but I'm hoping soon, as it is a pain and major issue for us "isolated" cases - why me?
I found that MTP does not work correctly on winxp without Windows Media Player 11. It appears to work kinda with WMP10, but not the way you would expect.
Fix
I was pulling my hair out trying to get my new verizon galaxy nexus connected to my pc running windows xp to transfer files. Finally I figured out what the problem was for me.
MTP is tied to windows media player somehow and you need to have the new version of windows media player installed for it to work. Until I did this I was getting an error when a plugged in my phone about the required files not found in the INF file or something.
1. download new version of windows media player.
2. You need to download the samsung USB drivers from samsungs website...I would post the link but I am not allowed.
make sure you click the tab for software...it defaults to manuals and doesn;t look much like a tab at all. After that mine worked beautifully although the MTP transfers seem extremely slow compared to the USB mass storage connection my droid 2 had.
Hope this helps someone else out there!