Hello!
Please advise, I really don't know what to do with it anymore ...
Every ROM with Android 10, including Crdroid, Pixel Experience etc ... as soon as I upload it to the Mi A1, then (after normal first start and boot) I connect the USB cable and choose "USB transfer files", so it just doesn't appear on a Windows PC and I cannot transfer anything. As if the phone was just unplugged, it's just charging USB tethering works. Direct selection of "USB file transfer" in the developer options won't help either. Where's the problem? Once I get back to Android 9 (Any... Stock and AOSP), everything is fine.
I flash the ROM normally. Starting from STOCK, unlock the original bootloader, load TWRP, delete DATA, SYSTEM, INTERNAL, DALVIK, flash ROM, then GAPPS (eventually) and then restart...
I really don't know where the problem is when nobody reports anything like that here
neobit78 said:
Hello!
Please advise, I really don't know what to do with it anymore ...
Every ROM with Android 10, including Crdroid, Pixel Experience etc ... as soon as I upload it to the Mi A1, then (after normal first start and boot) I connect the USB cable and choose "USB transfer files", so it just doesn't appear on a Windows PC and I cannot transfer anything. As if the phone was just unplugged, it's just charging USB tethering works. Direct selection of "USB file transfer" in the developer options won't help either. Where's the problem? Once I get back to Android 9 (Any... Stock and AOSP), everything is fine.
I flash the ROM normally. Starting from STOCK, unlock the original bootloader, load TWRP, delete DATA, SYSTEM, INTERNAL, DALVIK, flash ROM, then GAPPS (eventually) and then restart...
I really don't know where the problem is when nobody reports anything like that here
Click to expand...
Click to collapse
? Might be something to do with the usb driver(s) on your pc. Also if you can't get it to work then try FTP as that's an alternative. See if you can transfer files via usb when you boot into recovery (twrp etc). Have you tried Derpfest ROM? That ROM might work for it. Just a few possibilities lol
I don't assume that it would be a USB driver, because the same phone with Android 9 works normally. And to replace the direct connection via USB by FTP connection? I don't think about it for a second Maybe when I'm in a bit of a mood I'll try another ROM and maybe I'll be lucky...
I'm rather surprised that no one has a similar problem and I would just like to solve it
Anyway, thanks for trying to help me
Hi,
Try flashing latest firmware. For me personally, New USB Cable solved it
---------- Post added at 03:05 PM ---------- Previous post was at 03:04 PM ----------
On the other hand, you can always use something Like mixplorer with ftp or HTTP server
I'm calling off my problem!
It was really enough to completely remove the existing drivers and let Windows do its job and install them again.
I'm sorry, I'm sorry, I'm sorry!
This should happen to newbies only! Unfortunately, I made it very complicated IN MY HEAD and I didn't think clearly
I apologize to everyone!
It is a problem with the drivers, it does not matter what ROM you use or if you have Android 9 or 10. You have to enter the Windows task manager, put the mobile in file transfer mode and delete Google driver by uninstalling the device from the system, just delete that driver and re-target your Mi A1 to PC. Windows will install the correct driver.
In Windows 10,go to Device manager & uninstall Google nexus device.then plug your phone.Storage working well
dilupalakmal said:
In Windows 10,go to Device manager & uninstall Google nexus device.then plug your phone.Storage working well
Click to expand...
Click to collapse
I solved the problem with your directions. Thanks!
neobit78 said:
I'm calling off my problem!
It was really enough to completely remove the existing drivers and let Windows do its job and install them again.
I'm sorry, I'm sorry, I'm sorry!
This should happen to newbies only! Unfortunately, I made it very complicated IN MY HEAD and I didn't think clearly
I apologize to everyone!
Click to expand...
Click to collapse
Same trouble, can you send screenshoot device manager, i dont know what driver must be I update
Roober_4 said:
It is a problem with the drivers, it does not matter what ROM you use or if you have Android 9 or 10. You have to enter the Windows task manager, put the mobile in file transfer mode and delete Google driver by uninstalling the device from the system, just delete that driver and re-target your Mi A1 to PC. Windows will install the correct driver.
Click to expand...
Click to collapse
You are a life saver! I spent an entire night re-flashing ROM and troubleshooting but this solved the problem. Thanks!!!
dilupalakmal said:
In Windows 10,go to Device manager & uninstall Google nexus device.then plug your phone.Storage working well
Click to expand...
Click to collapse
You Are Awesome !! Your suggestion helped me too !!
Removed the Nexus in Device Manager and reconnected the USB cable .. This pushed my Google Pixel device into USB File Transfer mode.
Roober_4 said:
It is a problem with the drivers, it does not matter what ROM you use or if you have Android 9 or 10. You have to enter the Windows task manager, put the mobile in file transfer mode and delete Google driver by uninstalling the device from the system, just delete that driver and re-target your Mi A1 to PC. Windows will install the correct driver.
Click to expand...
Click to collapse
thanx for your suggestion thats really work , or there is no problem in pixel rom
Related
Hi!
Some day HTC-Sync (2033) could not find the phone (but it worked before!) so I uninstalled all HTC-software and drivers. Then I installed the HTC-Sync again but now the OS can not recognize the phone. I tried to install the drivers manually but it did not work too. When I try to select the driver manually, I always get the message 'No suitable driver found in this directory' or so... - 'Unknown Device' is all I can see in the device list.
I tried the same procedure on 3 computers running WinXP SP3, Win7 32bit and Win7 64bit - without success.
(an other android phone (t-mobile pulse) does not have problems with these PCs)
Does someone has an idea?
I also tried all drivers I could find in different forums (xda, modaco and some others), read hundreds of posts but nothing helped. I always used the original USB cable; the AV-software was inactive.
The phone is not rooted, it runs original the original HTC-firmware (Kernel 2.6.29-gf922713, Build 1.67.161.18).
please help... :-(
If you are using "Advanced Task Killer" (or something like that) you have to make sure that "PC-synchronisation" is added to the list of apps wich will NOT be killed by this program. Otherwise the "PC-synchronisation" software on you phone will not launch when you connect your phone to the computer.
If it isn't listed, try adding it to the list and then reboot your phone, so "PC-synchronisation" will launch again.
Hope it helped!
sam_cocha said:
If you are using "Advanced Task Killer" (or something like that) you have to make sure that "PC-synchronisation" is added to the list of apps wich will NOT be killed by this program. Otherwise the "PC-synchronisation" software on you phone will not launch when you connect your phone to the computer.
If it isn't listed, try adding it to the list and then reboot your phone, so "PC-synchronisation" will launch again.
Hope it helped!
Click to expand...
Click to collapse
no, I'm not using any task killer apps.
... I also have tried to use Ubuntu 10.4. The result was the same as on Windows-PC - no connection. The t-mobile pulse worked with Ubuntu fine.
Maybe the Tattoo is broken? or the USB cable? (I do not have another one).
Would a factory reset help? I do not want wipe the phone if it is unnecessary...
any idea?
ok, I've tried another USB-cable but it did not helped. The issue is still there and I always get the unknown device message...
Can you try to uninnstall pc sync and after that clean windows registry with some program like CCleaner or another and then install PC sync again ?
MPABKATA said:
Can you try to uninnstall pc sync and after that clean windows registry with some program like CCleaner or another and then install PC sync again ?
Click to expand...
Click to collapse
I tried that already several times, it did not help.
Is there someone that has found the answer why PC won't load a Tattoo?
win 7, 64bit,...
Thanks
petar17 said:
Is there someone that has found the answer why PC won't load a Tattoo?
win 7, 64bit,...
Thanks
Click to expand...
Click to collapse
Maybe , because you've got a 64 bit system or if you use a custom rom Htc sync does work
checks if htc tattoo driver are installed correctly
Maybe factory reset
Maybe factory reset will help becouse that is the problem I had before when I tried to install recovery and those shi%&. Then my screen went dead so I had to unroot my phone and factory reset it. Surprisingly, after that my phone worked with laptop.
I can send you that htc sync.apk or pc syncronisation if I find it on ICS.
Which rom do you have?
Problem was with a cable.
My phone was not rooted, until now, but the problem which made my PC not loading a Tattoo was, believe it or not, CABLE...
Now everything is ok, and I enjoy my Tattoo with GB ROM...
Thanks to all, appreciate it!
Anyway to manually get the drivers for it? I can't find them and I can't sync my device to my computer. Windows Mobile Device Center won't work at all, it doesn't recognize my HD2 and it says the driver installation fails.
Can someone help me out please? Thanks
Windows Mobile Device Centre was all I never needed on my win7 x64. I installed the program before inserting the HD2 though. Obviously make sure you have the program up and running before plugging in the HD2 and selecting activesync on it; It should load up. You could uninstall the driver (from device manager) and start again if all else fails.
What if it does not?
Started doing that "cant recognize" issue while installing NAND (at the radio installation process -r: 2.15., compatible)
Figured to go to stock WinMo with SDCard, but it still cant..
Faster data sync disabled, after that it tried to install the drivers again, but says it fails...
Gotta go to ms and install the updated win mob dev c. The one that ships needs updating.
Also, once you are into the android side of things you should open wmdc, connection settings, and turn off allow usb connections, and install the android usb drivers.
Thanks mate, but done everything, I mean everything. Now I'm totally stock, original SPL and original WWE ROM, everythings working like a charm, besides connecting to a PC. Also tried with another computer (XP) and another cable. I can say I've done everything I found on the net, but nothing helps. Uninstalling driver, uninstalling HTC Sync etc etc etc... It just cant recognize the USB..
thekillingroad said:
Thanks mate, but done everything, I mean everything. Now I'm totally stock, original SPL and original WWE ROM, everythings working like a charm, besides connecting to a PC. Also tried with another computer (XP) and another cable. I can say I've done everything I found on the net, but nothing helps. Uninstalling driver, uninstalling HTC Sync etc etc etc... It just cant recognize the USB..
Click to expand...
Click to collapse
Replace your USB Cable and Thats ALL !
i had the same problem....i am for now using windowx xp
aks777 said:
i had the same problem....i am for now using windowx xp
Click to expand...
Click to collapse
I have been using it win 7 64 bit since the beginning. and I never have a problem with the driver.
Try redownload and reinstall Windows Mobile Device Center from Microsoft website.
Only connect your device after the driver has been properly installed.
in device manager delete usb controller after software installation.
Thanks to ALL, but changing the USB cable, so sure that's ALL? =)
I'm not gonna mention that I've written that I've tried it with many computers and many cables. =)
The phone is sent to HTC and they told me that they ordered a new mainboard.
Hope doesn't take too much time. My Service Provider gave me a Galaxy 7500.. Cupcake, no market.. arrrgh!
Thinking of buying an iPhone and selling it after two weeks but that's gonna cost me $200 loss in two weeks. too much =)
As doing some thinking.. the device cannot "introduce" itself to the computer. I couldn't find a more sense making answer.
If you've tried hard-resetting, cable and PC changing, if it's still not working, then there should be a problem about the phone, mostly about the mainboard.
I suggest anyone having that problem go make your phone check at a service, of course if you have warranty. =)
Hi all,
Yesterday I stayed till 3 AM trying to flash the new firmware to my 9100, but KIES was so unstable that I decided to re-install.
We all know if we simply install Kies under XP, there is an issue with an Android MTP driver failing to install. No matter what you do, it won't install. This is the driver that Kies requires to work in order to sync contents and flash new firmwares.
After trying different options and settings, the solution is quite simple. Follow the steps (XP tested):
1.- Remove Kies entirely.
2.- Remove Samsung USB Drivers
3.- Reboot.
4.- Install latests .NET framework.
5.- Download and install latest Windows Media Player (ver 11 for XP). This is the key, since it installs a User mode driver framework used by Kies.
6.- Reboot
7.- Download and install latest Kies. Reboot.
6.- Plug in your phone. It will detect everything.
8.- Start Kies.
This should make it.
Hope it helps!
Cherni.
I had Rooted and Custom ROM-ed with AOSP GingerMOD.
Then when connected to PC via cable, W7 failed to install MTP driver.
Heres what worked.
Turn off USB Debugging on the phone. Reconnect via USB storage mode.
Voila!
Am not using Samsung Kies. so dont know whether it will work with the same trick.
cherni said:
5.- Download and install latest Windows Media Player (ver 11 for XP). This is the key, since it installs a User mode driver framework used by Kies.
Click to expand...
Click to collapse
What if you have XP?
ro-mann said:
What if you have XP?
Click to expand...
Click to collapse
He said version 11 for xp lol.
BTW, for those of you with windows 7 enterprise N - The "N" means no multimedia drivers, so media player would not be enough.
You need to download some 300+MB package which I don't remember the name. and then media player.
I meant W7!
Well I just tried this and it didn't work, am losing hope here...I already tried everything and nothing works
undertaker677 said:
Well I just tried this and it didn't work, am losing hope here...I already tried everything and nothing works
Click to expand...
Click to collapse
Is usb-debugging on?
Sent from my GT-I9100 using XDA App
I have tried it with or with out debugging
calexus1182 said:
Is usb-debugging on?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
All this started when I updated from version 2.3.3 to 2.3.4 through KIES
Hi, were you able to solve? I'm stuck at the same point, tried almost everything and i'm still getting the MFT driver error with my Galaxy S 2.
OS is WinXP 32bit, I tried before with Kies version 2.0.3.11082_152_2, then yesterday with 2.0.3.11082_152_4, no luck.
I tried the suggested Windows Media Player 11 procedure, i did the whole process as written in the 1st post (installed .net 4, then WMP11, then reboot, then Kies, then reboot again) and it didn't worked.
Before that i tried with USB debugging mode, i tried following what Kies says (connect device, got the error, disconnect the device then go to "tool -> the crap that should be supposed to repair drivers but that truly does nothing", then reconnect the device just to get the error again), I tried a tool i found somewhere on the internet while reading HUNDREDS of pages of users having the same error (Samsung engineers, that means that you really SUCK!) "FileSearcherforKiesFix" to find files with long extension on my SD, deleted some files (was only some thumbnails), NOPE, still getting the same F****n' error
So, were you able to solve in some way this error? How?
Thank you for your help, and sorry for my english (i'm Italian).
and if that doesn't work...try a different USB port on your computer. I have found that only one of the 4 on my t410 thinkpad plays nicely with the samsung usb drivers...
having said that, i have sworn off kies entirely and will only use Odin,
I'm on the Galaxy SII and was having similar problems. Went to the samsung website, DLed the USB driver, then to get the MTP to work: Turn off Debugging, go into "wireless and network", then into USB Utilities, unplug usb, click connect to PC, then plugged it back in, and bingo, we have a winner.
I didn't read the entire thread to see if this method was already posted, to f'ing tired!
Hopes this helps.
edit: looks like Kragusk did a similar (exactly the same?) install. So yeah, what he said....
the fix
This fix for windows XP was discovered by a chap named Dennis.
The problem is caused by some drivers from WMP11 failing to install correctly.
(WMP11 contains the MTP drivers, nothing to do with Samsung or USB drivers)
You just need to re/install them
rename C:\WINDOWS\system32\drivers\wudfrd.sys xxx_wudfrd.sys
rename C:\WINDOWS\system32\drivers\wudfpf.sys xxx_wudfpf.sys
rename C:\WINDOWS\system32\wudfhost.exe xxx_wudfhost.exe
rename C:\WINDOWS\system32\wudfsvc.dll xxx_wudfsvc.dll
rename C:\WINDOWS\system32\wudfx.dll xxx_wudfx.dll
rename C:\WINDOWS\system32\wudfplatform.dll xxx_wudfplatform.dll
rename C:\WINDOWS\system32\wudfcoinstaller.dll xxx_wudfcoinstaller.dll
Then run this file (umdf.exe) found inside the windows media player 11 install
(Hint: download then open in winrar to find the file)
Sorry as a new person I can't post a hotlink to a file.
wwwDOTmediafireDOTcomSLASH?2ak0f9n985ql00h
This not only cures Kies, but almost all other Media Player connection problems as well!
Kragusk said:
Go to Samsung Kies software, on top left of the window, click the menu > Driver recovery.
Let it reinstall drivers
After driver installation finished, go to your phone, Settings> Application > Development, tick USB debugging mode.
Under USB debugging mode connect your phone to the PC with USB.
It installs correctly!
Disconnect from PC
Untick USB debugging mode
Connect again
and it works!
Click to expand...
Click to collapse
This method really helped me. Thanks a lot man
wrong thread.....
Windows Media Player has the secret sauce! thx Cherni & pjclark1
5.- Download and install latest (ver 11 for XP). This is the key, since it installs a User mode driver framework used by Kies.
Cherni.
Worked for me, too. Didn't need to reboot.
XP sp3 captivate
I cant believe it that so many people are having this ****in problem! I will try post #1. Thanks
i tried post #1 but still doesnt work.
i tried installing a standalone Samsung USB drivers also doesnt work.
Anyone has a clue?
thank you v m~
It worked for me.
Thanks a lot.
Hello, i have a very weird problem. My nexus 4 cant connect to pc as mass storage device.. It worked fine like 4 days ago.. I dont know what happened or what else i can try.. Already tried: usb debugging on/off, factory reset, usb settings in storage menu, different usb port, NOTHING HELPED! There are another weird thing that i spoted is that it only charges through usb when i have nothing selected in storage>usb connections menu, as soon as i try to select mtp or camera it stops from charging and nothing happens. Same problem for AC charging it wont charge when theres mtp or camera selected, and only charges as USB... I'm confused.. Are there any ways to get it working again?
I'm having the same problem.. I've just installed Windows 7 64 bit but it sees my Nexus 4 like Unknown Device.. I uninstalling the drivers and re installing them using Nexus Root Toolkit but no result for now..:crying:
Do you have a ROM or anything installed? I know with PA its a problem at the moment at times. A little more info would be nice. I never had a problem with Windows 7. I'm on Windows 8 now and i had an issue at first with it not showing up at times. But it seems to be fine now.
Just go in
Settings,
Dev options (if you not have it go in phone informations and press many times in row the Build Number, this activate Dev options)
and Disable USB Debugging,
then reconnect your phone, and the computer will see it
USB debbuging isnt working. i have no ROMS, stock android 4.3. And yes, now im running WIN 8, previuosly had 7, the problem occured after installing 8 and trying to plug it in. Its not showing in my computer neither in device Manager. I doesnt make any difference with, or without it pluged in, the only difference is that it will start charging, but then again ONLY when i disable everyting in storage>usb connections.
bump
do you have a fast charge app installed? it sounds like it's an issue related to fast charging via USB. if it's enabled you can't access anything on the phone via usb, but i think that requires to at least be rooted.
I'm on last PA 3.99-Rc1 and I just found out that if I go in Setting-Memory the appilcation shutdown .-. Never had this issue before .-.
Matteo Mazzu said:
I'm on last PA 3.99-Rc1 and I just found out that if I go in Setting-Memory the appilcation shutdown .-. Never had this issue before .-.
Click to expand...
Click to collapse
Nothing, just read that it's a issue with PA while using last Franco Kernel nightly XD I'm going back to windows vista 32bit, so I believe the problem connecting my nexus 4 won't be any more an issue (Going back to Vista because for daily use it worked perfectly and every thing worked fine with the drivers, Windows 7 it's better, but too many issues with drivers bla bla bla XD) :laugh:
I have always used the Windows Driver from the Google SDK (Google USB Driver- As of today, Revision 8) for my Windows 7 64 bit computer and have never had a problem. More importantly there is an Update Manager that comes with the SDK, that when you run, notifies you of newer Windows drivers as they are released. That way as Google issues newer OS builds or Windows issues a new OS, I know that not only my driver but my platform tools aka fastboot/adb/etc. (As of today, Revision 18.0.1) will always be compatible. The problem with these toolkits and driver downloads all over the place on these forums is that you have know idea how old the internals are. The other obvious thing to check is a bad or intermittently bad USB cable. Also make sure "MTP" is checked in Settings > Storage >Settings > USB computer connection.
Hey, I'm sorry if it's against etiquette digging up an old post, but this part worked for me:
pjc123 said:
Also make sure "MTP" is checked in Settings > Storage >Settings > USB computer connection.
Click to expand...
Click to collapse
Thank you so much, I had this problem for a long time before I found this thread.
dunni88 said:
Hey, I'm sorry if it's against etiquette digging up an old post, but this part worked for me:
Thank you so much, I had this problem for a long time before I found this thread.
Click to expand...
Click to collapse
Glad I could help. That setting isn't exactly the easiest thing to find.
Fix usb
Go to device manager in windows 7/8/8.1 . Connect your mobile with usb. You will see android device or adb right click on it, select properties, click uninstall driver. NOTE: When you click this a small popup will appear saying remove software driver, tick on it and click uninstall.. there you go ..it will reinstall drivers and your phone will be finally connected.
im having the same problem . My phone shows as Unknown Device on Device Manager. Tried other cables and usb ports. I can tell that the cables and ports are not the problem since my Nexus 7 can connect without problem. Tried usb debuggin on/off, MTP on/off, PTP. Still no luck. Already tried to reinstall drivers but still the same problem. Hoping this is not a hardware issue. I already tried factory reset and flashing other ROMs
I'm having an issue with file transfer where my computer can't 'see' the phone when an AOSP ROM is installed.
File transfer is fine when mounting in recovery, also when I have OOS installed, so it isn't a hardware problem.
I've gone through the forum searching for a solution, and I have:
Changed the default USB configuration (under Developer options) to MTP
Uninstalled the phone from Device Manager on my computer
Tried installing OnePlus drivers to my computer
Tried installing Qualcomm drivers to my computer
Can anyone suggest a solution? I'm desperate to get this sorted as I can't tolerate OOS any longer, I just want a cleanish build of Android with no OnePlus rubbish in it!
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Hitman478™ said:
I join your quest man... Im looking for the solution for this problem since i have installed my first AOSP rom on OP5... Never find the solution, i'm curious for this too... Now im on PureFusion and MTP of course isnt working... so i use recovery for file transfer (which is annoying) or the WiFi server (which is slow and isnt "operations" friendly)
In the same time cant understand why my nexus 6p with PureNexus is fully working in MTP but the oneplus 5 nope
Click to expand...
Click to collapse
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
siankatabg said:
That's interesting. I'm transferring like 80% of my files trough MTP and it is and always was working fine, but I'm using Linux, so that might help you guys to solve it
Click to expand...
Click to collapse
I know it's windows fault because when it have too many drivers to manage for the same thing it goes crazy.. but even removing every single driver (ADB and Android related) it doesn't work.. I'm looking in a solution on the Linux build called "forget windows use Linux" since I can't completely remove windows 10
I had same issue in Linux
Typically, issue is not the ROM
1) check the phone get set to "file transfer" when connected, you generally have option to chose
2) plugging to a usb in chain to other switches it was not work, connected directly to a usb MB port, worked.