Laptop refuses to recognize MTP - 7" Kindle Fire HD Q&A, Help & Troubleshooting

For some reason, my laptop refuses to recognize the kindle fire MTP portion. I know its suppose to show under portable devices and it did on my desktop. It shows up as a composite ADB interface under kindle fire.
With that said, i also cannot access it to transfer files over, which i feel plays a huge role here somehow.
Running windows 7 64 bit
Any ideas? I believe ive tried removing all the drivers and reinstalling a million times, doesnt seem to work at all
edit: desktop looks like its using windows drivers of some sort, my laptop has all the files needed so i think i have some service disabled or something.

Coderedpl said:
For some reason, my laptop refuses to recognize the kindle fire MTP portion. I know its suppose to show under portable devices and it did on my desktop. It shows up as a composite ADB interface under kindle fire.
With that said, i also cannot access it to transfer files over, which i feel plays a huge role here somehow.
Running windows 7 64 bit
Any ideas? I believe ive tried removing all the drivers and reinstalling a million times, doesnt seem to work at all
edit: desktop looks like its using windows drivers of some sort, my laptop has all the files needed so i think i have some service disabled or something.
Click to expand...
Click to collapse
same boat here adb is fine. device worked before on the laptop but not anymore i have done everything except reinstall windows(not going to do that), desktop works fine and both are x64. even mtp on ubuntu works fine also x64.
tried using manual ids, tried remove reinstalling google or amazon drivers, removed and reinstalled usb drivers and tried it with AV software disabled and admin modes... safe for me to say im pissed

Coderedpl said:
For some reason, my laptop refuses to recognize the kindle fire MTP portion. I know its suppose to show under portable devices and it did on my desktop. It shows up as a composite ADB interface under kindle fire.
With that said, i also cannot access it to transfer files over, which i feel plays a huge role here somehow.
Running windows 7 64 bit
Any ideas? I believe ive tried removing all the drivers and reinstalling a million times, doesnt seem to work at all
edit: desktop looks like its using windows drivers of some sort, my laptop has all the files needed so i think i have some service disabled or something.
Click to expand...
Click to collapse
You actually can push files to it still with ADB or you could just turn USB debugging off to make it appear as an MTP device again.
Sent from my KFTT using xda app-developers app

i have the same problem...i have 2 PCs running Win 7 x64...one PC recognized my rooted Kindle, automatically installed the necessary drivers, and had the Kindle accessible through Windows Explorer immediately, but the other PC did not...keep getting MTP Driver Not Found/Installed error messages....i searched online everywhere, and tried every bit of advice i found, but still nothing...i even re-installed Win 7 on a brand new HDD, and still nothing....ADB does work after installing the ADB drivers though...i eventually gave up trying to get the Kindle recognized as a USB storage device on that PC, and am just using WiFi transfer apps to transfer media/files

Related

ADB device offline

I've been using ADB the last couple of days to install apps on my Captivate and all of the sudden it stopped working today.
When I type 'adb devices' the phone comes up right away, but it shows offline.
I have tried reinstalling the drivers and Android SDK, but no luck. I've searched around and found some others with this issue, but haven't really found a fix that works for me.
Any idea why ADB would just stop working like that? I even performed a factory reset of the phone and put everything back to defaults.
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Man, I really thought I was going crazy.
wimbet said:
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Click to expand...
Click to collapse
What the hell is that about!? I wish all these companies would stop trying to break from standards by proprietizing common cables.
I can't get the drivers to work. Where did you get yours?
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Man, I really thought I was going crazy.
Click to expand...
Click to collapse
Yeah I buy that, I couldn't even get the thing to try and connect at all with out switching usb connections on my computer.
stock cable works. I just rooted and ran into that problem. In order to get around it if you cant get a diff cable, make sure that b4 you connect your phone to your pc you turn off your internet so it doesnt auto dl the drivers. b4 u connect, dl the drivers for your phone from the root thread. Plug your phone into ur comp with the internet off and close any pop ups. Go to device manager look for the notification labled usb or captivateand right click and select update. Select search from file on disk or select file (something like that, i forget) and scroll and select the folder where you extracted the usb drivers. Make sure the checkbox that says search subfolders is checked and click next to install. two more drivers will pop up in device manager after u install the first one. Repeat the same procedure for both of them and then you should be able to use adb just fine to root.
Just wanted to further confirm that using a different microusb cable works! I keep reinstalling the drivers but it kept showing the device was offline. Then I tried my old Nokia N85 cable and it worked like charm! So weird how usb cables aren't made equally, unless Samsung designed the cable to prevent using adb?
I had this issue for a little while, but I installed the Samsung Kies software (which contains drivers) and uninstalled the ADB drivers I had originally downloaded. It's worked like a charm since then.
Go to SamsungApps.com and then use the canada site, as the software isn't really available in the US yet.
I have had no problems using the stock cable on my Laptop and work PC, both are Win 7 32bit. The same cannot be said for my my main home PC which is Win 7 64bit. Neither the stock cable nor an after market cable worked with ADB.
For the 32bit OSes I installed the Kies software and the usb device gets installed correctly. for the 64bit OS, I installed the Kies software but could get the phone to connect correctly. I then tried to install the 64bit drivers that are floating around the web. The 64 bit drivers worked enough to get the phone connected to the PC but when I tried to query "adb devices" the phone would always appear as offline. I've tried several things: install/uninstall drivers and software on the PC, restart the PC and Phone, change cables. Nothing seems to help on Win 7 64bit.
It seems to me that there might be a bug in the 64bit driver, though I have no proof of a bug.
I am going to keep playing with the 64bit OS until i figure it out or get so annoyed a that I just give up.
I'll be using my Win 7 32 bit laptop until I get the 64bit PC to work.
TimF said:
I have had no problems using the stock cable on my Laptop and work PC, both are Win 7 32bit. The same cannot be said for my my main home PC which is Win 7 64bit. Neither the stock cable nor an after market cable worked with ADB.
For the 32bit OSes I installed the Kies software and the usb device gets installed correctly. for the 64bit OS, I installed the Kies software but could get the phone to connect correctly. I then tried to install the 64bit drivers that are floating around the web. The 64 bit drivers worked enough to get the phone connected to the PC but when I tried to query "adb devices" the phone would always appear as offline. I've tried several things: install/uninstall drivers and software on the PC, restart the PC and Phone, change cables. Nothing seems to help on Win 7 64bit.
It seems to me that there might be a bug in the 64bit driver, though I have no proof of a bug.
I am going to keep playing with the 64bit OS until i figure it out or get so annoyed a that I just give up.
I'll be using my Win 7 32 bit laptop until I get the 64bit PC to work.
Click to expand...
Click to collapse
i've been able to install .apk's with my win7 64-bit ADB :O
all i did was install Samsung Kies.
i don't think i've ever had a problem...?
EDIT: i'm using the cable that came with it and no problems yet.
I'm running win 7 x64 and Kies did the trick for me. I haven't had a single issue connecting my phone since I did that.
Sent from my SAMSUNG-SGH-I897 using XDA App
Justa dding to the anecdotes.
I was having problems with the included cable using the front USB. It would show as Device Offline, also the charging wasn't very strong.
I switched to the onboard USB at the back of the case, and adb worked fine with the included cable.
Looks like I'll be picking up a couple extra USB cables so I won't have to continuously do the desk dive everytime I need to use it somewhere else.
1. I installed the kies drivers first and it would say offline when i checked the device through the cmd prompt.
2. I then installed the adb drivers and it then said the device was online.
3. i then rooted the phone and went on my way. i then tried it a second time and it said device offline.
4. nothing changed during this time except that i turned off debug mode, changed it to mass storage and plugged it back into the usb to transfer some files.
5. on returning to debug mode it no longer tells me the device is online. i have tried different USB ports as well.
6. i deleted the drivers, and reinstalled and it still says offline.
very frustrating.
wow. i forgot to try plugging it into another USB port. that worked. sorry about previous post.
I am running Windows 7 Home Premium 64bit on my laptop,
I installed the samsung 64bit drivers, it was an installer i found on the web, not the kies installer packaged driver one.
i changed my setting on my captivate to Mass Storage.
I mounted usb and everything works, by that I mean i was able to ADB like no tomorrow without any issues.
Then I made the mistake of installing Samsung Kies and that messed up my previous drivers and I wasnt able to ADB to my phone. I had to uninstall Samsung Kies and my phone still wasnt being found I still couldnt ADB.
my solution to fixing was restarted my phone and computer, without my phone connected to USB i re-installed the Samsung 64bit Driver Package, then hooked up my phone made sure Mass Storage was selected and Mounted USB and bam was able to ADB again.
hope this helps! also i have been doing videos helping people with issues with samsung's captivate on youtube, youtube.com/johnnyzappone if anyone wants to check em out, if anyone has any suggestions please let me know and id be happy to release a video!
I resolved my issues, I plugged the stock cable into one of the rear usb ports and the device is now available on my main PC Win 7 64 bit.
wimbet said:
Ok I almost pulled my hair out, but I found the problem.
For some reason, ADB does not work with the Samsung USB cable that came with the Captivate.
I switched to another USB cable and it works just fine.
Click to expand...
Click to collapse
Confirmed this made my device stop appearing as offline with adb.
How it is even possible that the cable prevents (only) adb access on the PC, I have no idea.
I have windows 7 and mac osx and I can use adb with both using the stock USB.
i have debugging active.
lol @ the samsung cable.
i've 2 indentic cables here, one doesn't work. plugged in the other one and this one works...
maby its just a strange issue on windows, next time try to pull out the cable and put in back in then connect your device again this should work.... :s
because earlier the cable just worked fine and now it doesn't.. so good luck xD
joelpt said:
Confirmed this made my device stop appearing as offline with adb.
How it is even possible that the cable prevents (only) adb access on the PC, I have no idea.
Click to expand...
Click to collapse
also can confirm PITA

windows 7 and diamond touch

hey people,
I know I am writing about a known topic since I have been looking on the internet for hours, however I'm absolutely not finding the answer, it is so frustrating. Hope someone can help.
I connect my diamond touch (WM 6.1 pro, thanx to xda dev) to my freshly installed windows 7 utlimate on my iMac 27". It simply doesn't connect. I managed to install windows mobile device center, but it does not recognize my phone. I can connect mounting the phone as disk, but I want to sync. When I use active sync the computer sees it either as a generic RNDIS device (fast transfer checked on in pc-usb connection) or as unknown device (fast transfer checked off). For both it cannot find a proper driver when windows start looking for it! I have tried everything so far. Reinstalling WMDC, restarts, reboots, change usb ports. I don't know what to do anymore, please help me.
Best regards,
Barbet
Win7 mobile center, need install a driver.
drvupdate-x86.exe
you can search this file. I don't know why I can not put in the link.
Hmmm
Did that driver thing work? I didn't have any problems connecting from a PC. Are you using a VM or have you installed windows 7 on your mac? Try using a virtual machine.
Windows 7 by default do not recognise a lot of phone, you need mobile center to make it work, on microsoft.com -slash- windowsmobile -slash- en-us -slash- downloads -slash- microsoft -slash- device-center-download.mspx
thanx so much for your replies, however my problem is still not solved. I really don't want to use any viritual windows versions on my mac, it was a cramp to install it via bootcamp. I made sure all drivers were correct and all my hardware is working. Still problem is not solved. I have installed media pack, i have installed and reinstalled WMDC multiple times, i have installed any updates possible, i have tried different settings on my cell. Either i get: generic RNDIS driver not availible or i get generic serial driver not availible (serial doesn't even make sense, it is a usb connection). Anyways, i really really really want a solution.
btw, drvupdate-x86.exe is for 32 bit, i have 64 bit, i used drvupdate-amd64. It is properly installed.
Ow and i tried to deinstall WMDC update to reinstall it, but it was not possible to deinstall it!!! It deinstalls to 99% and then the process bar runs BACKWARDS. I didn't even know it was possible running these bars backwards. It certainly confirms why I prefer mac.
This will sound really dumb - but make sure you try it with the USB cable the phone came with. I was having problems for days until I tried a different USB cable... and there you go.
i will try again, but i remember trying similar things, also switching usb port, i tried didn't work
edit:
i did as you said and doesn't work
it does appear properly as disk if, but the moment you select 'active sync' it doesn't appear anymore,
i hear the sound that confirms the connection, and in the devicemanager i can see the device but with a warning that the driver is not installed
i have to edit first post, i am running wm 6.5, sorry, maybe this gives an anwer?
i think a solution can be in the WMDC driver update
i think i should uninstall it and reinstall it with my htc pluged in
however i can't uninstall it as i said before
i read that 'undocumented service' is necessary, however can find what it is
uninstalling via 'remove programs' doesn't work, neither normal or in safemode
someone help me further?

Unable to use N1 with Windows 7 64 Bit

I tried to do a search for this, and nothing came up for me. I recently purchased a new Laptop, running Windows 7 64 bit. My Nexus One will not install any of the drivers on such. I have downloaded the drivers from the Android Development, yet I am unable to actually use my Nexus One for ADB or for even Disk Mode. It keeps stating it is unable to install the drivers. I haven't ever tried to use my N1 with any 64 bit OS before this (except linux and mac, but that just seems to work) and my 32 bit OS's seem to work perfectly fine. Anyone else having this issue? Or possible solution?
I had the same problem when i went to root mine. I tried every tweak and hack and fix an update nothing worked.. but send someone at android community.com had it..
If you can wait a few hours i will post it when i get home..
Please don't even think of putting windows mobile on your nexus one. That is against Android law!
Sent from my CM6 Nexus One using XDA App
Keep trying and make sure you install the correct drivers. Try from another download source and don't let windows install the defaults.
naturefreak85 said:
I tried to do a search for this, and nothing came up for me. I recently purchased a new Laptop, running Windows 7 64 bit. My Nexus One will not install any of the drivers on such. I have downloaded the drivers from the Android Development, yet I am unable to actually use my Nexus One for ADB or for even Disk Mode. It keeps stating it is unable to install the drivers. I haven't ever tried to use my N1 with any 64 bit OS before this (except linux and mac, but that just seems to work) and my 32 bit OS's seem to work perfectly fine. Anyone else having this issue? Or possible solution?
Click to expand...
Click to collapse
I had the same problem. After hours trying things and searching for solutions in Google, finally MY solution was activate the USB Debug Mode
I hope this works for you too!
WaPeR32 said:
I had the same problem. After hours trying things and searching for solutions in Google, finally MY solutions was activate the USB Debug Mode
I hope this works for you too!
Click to expand...
Click to collapse
Same with me. USB Debug mode fixed it.
Im on Windows 7 x64 Pro. I havent had any problems getting ADB to work with my machine. I downloaded the SDK from the website and ran the sdk setup.exe. It will fail the first time, you have to close it and go to settings and FORCE HTTPS. once that is done. reopen it and reject everything except Device Drivers. This will download the drivers. When I connect my phone with debug mode on windows auto picks up the drivers and installs it.
I got it running on my machine ..windows64bit .. took a lil while but like someone said but it can be done ..or if all else fails install droid explorer ..and use its sdk directory
I had the same problem. In my case it was because I was plugging it into a usb port that was built into a card reader in my tower. As it turned out the usb port was not putting out enough power, so I decided to try some ports that are on the bottom of my case and the problem went away.
Each usb hub has to share power, so if you have several usb devices that pull some juice workin on the same hub you can try to get onto another hub via another port.
Win7 64 bit
I had the same problem. For me the solution was to use a legacy/older USB port on my laptop and not a highspeed one.
i am having this issue as well.
i have looked everywhere, and tried many solutions. i am lost.
my windows 7 32bit laptop sees the N1 is connected but cannot install or even find any drivers for it. i have USB debugging mode checked. i have tried ADK, using the USB drivers it provides, no luck there.
my N1 isn't rooted yet, and i'd like to trick it out. but i have to get access to it first. any help y'all can provide would be amazing.
it may be possible this is a windows 7 issue, with drivers and such. but i've been looking around for a while and can't find a solution anywhere.

[Q] windows will not recognize touchpad

I am not sure when this started. I have used windows to install cymod several times but i went to download a update and install it and my computer will not recognize the touchpad. it says the device driver was not installed properly
i have tried on two different units.
one has web os only and the other has android
it goes through the steps of looking for the device and then nothing.
i get a tone on the touchpad and then nothing on the computer
I do have the correct setting in the storage settings so i have no idea what to do
did you run novacom again?
x000x said:
did you run novacom again?
Click to expand...
Click to collapse
no i didnt see a point because Windows wont find the touchpad in explorer
Now i forgot to mention this was a fresh windows install too
dyson77 said:
I am not sure when this started. I have used windows to install cymod several times but i went to download a update and install it and my computer will not recognize the touchpad. it says the device driver was not installed properly
i have tried on two different units.
one has web os only and the other has android
it goes through the steps of looking for the device and then nothing.
i get a tone on the touchpad and then nothing on the computer
I do have the correct setting in the storage settings so i have no idea what to do
Click to expand...
Click to collapse
It sounds like driver problem to me. Search for HP touchpad driver and download and install the latest version you find, that should do it.. I'm assuming you have the MTP box checked in storage > settings > USB computer connection. Also, reboot both the tablet and the computer after installing the new driver.
Good luck.
I have two different devices one only has web os and the other has android.
on the android I have the MTp checked and have accessed it in the past but i upgraded to windows 8
that being said i had the same issue with windows 7 i just thought a fresh install would fix the issue and it has not
I have downloaded what i thought was teh latest drivers.
I have installed novacom
and rebooted my system.
and I get the same error message Windows does not recognize the device.
i get the connected tone on my computer but I don't get any response on the touchpads
did you put the tablet in usb mode?
i did on the android not on touchpad forgot how to honestly
dyson77 said:
i did on the android not on touchpad forgot how to honestly
Click to expand...
Click to collapse
In webos when you plug in the USB it will come up with a prompt. Remember to safely eject before disconnecting.
sstar said:
In webos when you plug in the USB it will come up with a prompt. Remember to safely eject before disconnecting.
Click to expand...
Click to collapse
it doesn't do anything when i plug in the usb. i get the tone on the computer but nothing on the touch-pad at all
i ried through the usb ports on the computer and the ones on the case just to be sure
dyson77 said:
it doesn't do anything when i plug in the usb. i get the tone on the computer but nothing on the touch-pad at all
i ried through the usb ports on the computer and the ones on the case just to be sure
Click to expand...
Click to collapse
Try using a different USB lead and plugging into different USB sockets on your PC sometimes I find my PC will recognize it with one socket but not another same thing occasionally happens with my USB sticks. Otherwise I would suggest trying a different PC if you still have a problem that would suggest a fault with the USB socket on your touchpad which I have had to have replaced once.
Fingers crossed that isn't your problem.
dyson77 said:
i did on the android not on touchpad forgot how to honestly
Click to expand...
Click to collapse
This will let TP be recognized on the PC
"If you want to transfer files back and forth from the CM9 touchpad you might have difficulty figuring out how exactly to do it.Here's how you pull it off:
First, tap on your app drawer in the top right of the screen (the little checkerboard). Now, select the "settings" icon.
Now tap on storage on the left-hand pane.
Finally, the tricky part - tap on the 3 squares at the VERY top right of your screen. It will bring down a little drop-down menu for USB computer connection. Tap it and put a checkmark in the "Media Device MTP" box.
Now you can plug your touchpad into the computer at will and transfer files back and forth from it. Easy as pie, I'm not sure why this isn't activated by default, but it's a simple fix if you know what to do."
Sorry I copied this from XDA a couple of weeks ago, so I can not take credit for this but it works great
that is already done on my android, and the touch-pad should auto connect. but neither are it says device not recognized
dyson77 said:
that is already done on my android, and the touch-pad should auto connect. but neither are it says device not recognized
Click to expand...
Click to collapse
Did you check my second suggestion/try it on another PC to find out whether you have a faulty USB socket on your Touchpad as they can go wrong?
yes i did and i tried 4 usb ports, but that would be rather unusual for it to go bad on two devices right?
dyson77 said:
yes i did and i tried 4 usb ports, but that would be rather unusual for it to go bad on two devices right?
Click to expand...
Click to collapse
i also just tried it on my galaxy s3 using a usb port and it gave me the same unknown device error
im not sure i read that you put TP into usb mode from webos..if not, google the how to.. really simple..
also, install the novacom again.. iirc, it has the drivers too
to me, this screams missing drivers for both devices.
it wouldnt hurt to go to youtube and watch some reverendkjr vids
amkaos said:
im not sure i read that you put TP into usb mode from webos..if not, google the how to.. really simple..
also, install the novacom again.. iirc, it has the drivers too
to me, this screams missing drivers for both devices.
it wouldnt hurt to go to youtube and watch some reverendkjr vids
Click to expand...
Click to collapse
Novacom shouldn't make a difference, I have just installed windows 8 on my laptop and haven't installed anything yet , just plugged in the Touchpad and it was recognized straight away
Sounds like either windows is messed up or the USB connector of the Touchpad has gone .
same error on TP + his galaxy??
dam the luck..busted ports on both devices at the same time..
right after a fresh format of windows ; what a coinkadink
if on your very longest shot that win needs new drivers, the palm / novacom etc
process installs them and TP will get recognized and picked up..
he said he does not know how to root his TP to put into usb mode..
i know from recent experience that even when android is in mtp mode, my PC would not connect play w/ it until i had new drivers..
same experience w/ my new nexus 7 during the process of rooting it..
amkaos said:
same error on TP + his galaxy??
dam the luck..busted ports on both devices at the same time..
right after a fresh format of windows ; what a coinkadink
if on your very longest shot that win needs new drivers, the palm / novacom etc
process installs them and TP will get recognized and picked up..
he said he does not know how to root his TP to put into usb mode..
i know from recent experience that even when android is in mtp mode, my PC would not connect play w/ it until i had new drivers..
same experience w/ my new nexus 7 during the process of rooting it..
Click to expand...
Click to collapse
Ok lets get a few things right
I do know how to root my device I did it a while ago and honestly haven't done it in a while so I am rusty
but that being said if you cant access the device at all even in usb mode then you cant root.
And yes now my galaxy s3 wont recognize either.
every time i try it tells me that there was a device error and windows doesn't recognize the device.
i formatted the cpu again and put windows 7 and no help
I have tried two diffrent touchpads one android and one web os
and my phone
to get things right you have to start at the beginning. Windows will not recognize TP w/o the drivers first. It's obvious you have been avoiding that step. you need to go back and do the whole nova com thing to install them before you attach TP to it.. look at the you tube videos. you will be finished in a few minutes. .

[Q] Z1 ADB driver woes

Has anyone else had any issues here? I've been unable to connect to the adb on my home PC, curiously on my work PC it's been fine.
It's displaying as a "C6903", with hardware Ids:
Code:
USB\VID_0FCE&PID_519E&REV_0232
USB\VID_0FCE&PID_519E
Which don't even seem to show up in Sony's official drivers.
Absolutely baffled. All I can think is the hardware ID was coming up as something different on the work PC. I've tried forcing the android_winusb.inf drivers on it, by adding the ID to the list and adding the vendor ID to the file in the home directory.
I've had quite a mash of Android devices on this machine, I'd really really not format to clear it up though.
Any ideas? Thanks!
I've just tried another machine, and interestingly the above is actually a standard "USB Composite Interface", quite why it can't figure it out I have no idea.
Edit: Wow, after more digging around, I realized the stock USB Composite drivers were missing from the machine (usb.inf). I restored a version into C:/Windows/INF, it detected and installed. Everything else appeared straight after.

Categories

Resources