Hi,
I have a Umidigi One phone (not the pro although I doubt it matter for this question). Been trying to back it up - I used to use Titanium Backup, but rooting caused me so many issues with Uber, Paypal etc, that I'm no longer going to bother on my main phone, which rules out Titanium.
I came across Helium and have attempted to use this.
I initially installed both Helium Desktop and Helium App - I followed the instructions in the APp and enabled USB debugging. I then connected the phone to the Pc with the App running. I got the message unable to connect - you may need to install ADB drivers.
I disconnected the phone, installed ADB drivers from the link in Helium, rebooted and reconnected the phone. I still get the "unable to connect" message.
Note, my Pc itself recognises my phone - when I plug it in, I get the message that driver software is being installed and it shows up correctly as "One".
In device manager I have two entries - Portable Devices/One and Ports(Com & LPT)/MediaTek USB VCOM (Android) (COM4)
What could be the issue here and how can I fix it?
I'm running WIndows 7 x64 - Virus and Firewall were disabled while I attempted the above.
Related
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
thats nice but it doesnt exactly do anything for my problem
Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app
This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.
I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..
I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything
I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2
Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck
I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS
Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:
Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps
Hi,
I have a very serious problem with my OnePlusOne (64GB) after updating to version YOG4PAS3JL. Since the update, ADB no longer recognizes my phone.
It doesn't depend on the computer I'm using, I have tried to use my phone on 3 different computers (Windows) that I use on a regular basis and none shows my phone with the command adb devices.
Connecting via MTP is no problem, but when I enable Android debugging with USB, my phone will not show up in Windows Explorer.
I have also attached a Samsung Galaxy Note 4 and a HTC phone, both are recognized by ADB.
If I change the mode to MTP, it will show up as portable device called A0001 in the windows device manager. If I switch to Android Debugging, it will simply disappear and not show up
as "other device" or usb device without driver. So I can't even reinstall Android ADB Interface, it also doesn't show up in the Device Manager any longer. If I try to install a driver for my OnePlus One when it is in MTP mode, it will also only allow me to install MTP drivers (no possibility to install the previously so fine working Samsung USB drivers).
I have literally tried every solution out there I have found, from unplugging and restarting my phone, using different USB ports, using different USB cables, reinstalling Samsung USB drivers (didn't help as phone did not show up as unrecognizes device any longer), uninstalling Google USB driver, adding OnePlusOne to the .inf usb driver file myself (which mostly resulted in an "no compatible driver was found in this folder"-error), installing fastboot (didn't change anything), universal adb driver setup, pdanet, using USDBDeview, removing drivers with the bacon root toolkit to removing mtp files from the inf folder of windows to prevent MTP driver installation, but nothing worked
I would prefer to go back to the version before YOG4PAS3JL, where ADB worked fine or install a different ROM, but I have seen that every guide states that you need to have ADB to install a new ROM. As my phone is not rooted and I can no longer use ADB with my phone, I'm basically pretty stuck and don't know what to do I'm pretty desperate after two days of trying to solve this problem without success and would be so thankful for any suggestion what I could do.
Same situation...let me know if you find any solution.
Same situation here. Anf I guess this might have a link with my lack of internet connection while tethering.
Did any of you tried the USB or wifi tether? Does it work?
Sent from my A0001 using XDA Free mobile app
Hey,
I have an ASUS X55A Laptop with Windows 10 and I can't connect any phone with it. USB Sticks etc work normally so I think it is a MTP related problem. My device right now is a Moto G. I connect it with the USB port and my pc detects it, but I can't get access to the data on the phone. I installed the motorola drivers manually, but it didn't work either.
When I am in the windows "device manager" I can see my phone, but I am not able to install the MTP drivers properly. There is a small warning triangle next to my device name.
I tried many things, but I can not find a solution. If it is really MTP/PTP related, how can I install the drivers properly and working?
Thx for your help.
Edit: When I connect the phone without any drivers installed it says "Device is being installed" and the bar is ca. 5% filled and is stuck there. So the MTP won't install automatically.
Solved:
I installed the "Windows 10 Media Feature Pack" and now it works. I had the N Version of Win10, so it was not preinstalled.
Thanks for your feedback
Thread closed.
I've been trying to root my OPO for two days now and I've continued to have this issue. After installing Android Studio + the SDK, as well as downloading the Google USB Driver, when I connect my phone to my computer it shows up as an MTP device under unknown devices. If I allow it to automatically download drivers, it becomes a portable device instead. But I need it as an ADB device. I've already started USB debugging on the phone, as well as switched between all the different USB options on the phone (charging, MPT, PTP, MIDI, etc.) and still no good
When I try to update the driver for the "MTP" device, the Google USB drivers don't show up, and if I try to browse manually, it comes up with the error message saying how "the folder you specified doesn't contain a compatible driver." What do I do?
Thanks!
tli said:
I've been trying to root my OPO for two days now and I've continued to have this issue. After installing Android Studio + the SDK, as well as downloading the Google USB Driver, when I connect my phone to my computer it shows up as an MTP device under unknown devices. If I allow it to automatically download drivers, it becomes a portable device instead. But I need it as an ADB device. I've already started USB debugging on the phone, as well as switched between all the different USB options on the phone (charging, MPT, PTP, MIDI, etc.) and still no good
When I try to update the driver for the "MTP" device, the Google USB drivers don't show up, and if I try to browse manually, it comes up with the error message saying how "the folder you specified doesn't contain a compatible driver." What do I do?
Thanks!
Click to expand...
Click to collapse
Just want root? No custom recovery or rom?
Then use kingoroot or kingroot app on phone and get root without pc
Make sure you've fast net connection.
Mr.Ak said:
Just want root? No custom recovery or rom?
Then use kingoroot or kingroot app on phone and get root without pc
Make sure you've fast net connection.
Click to expand...
Click to collapse
Don't exactly want to use them due to the risks / IMEI debacle.
I have exactly the same issue.
I managed to get root by flashing SuperSU (only on a system less basis)
This just got the rooting side sorted but I'd still want to be able to get ADB working again on the phone.
I tried with three different laptops and the issue is persistent. I am running Cyanogen 13.1 coated beautifully with a Boeffla kernel and a slimlined build.prop (have to boast because everyone can agree, the Oneplus One is a revolution on its own)
tli said:
Don't exactly want to use them due to the risks / IMEI debacle.
Click to expand...
Click to collapse
Trsut me,there are no risks involved.
hello i have a samsung s7 vodafone-Italy. I have a problem with connection with helium backup, i have a version 6 of android.
Well I install helium backup on smartphone, i have install some drivers (maybe not good??) i have installa application helium for chrome, and i try on windows 7 and windows 8.
I open helium on smartphone, connect cable, ask for PTP mode, i go to set up, i set PTP
but smartphone ask me again select and enable PTP again.
With samsung tool program i backup smartphone...and i have no problem, but is not usefull.
Best regards.
Did you solve this? I have same problem with Helium and PTP-mode. (I have selected PTP mode, but Helium still asks me to change to PTP)
Helium worked fine when I backed up my old Moto X Force (and worked with Galaxy S4 too).
Now I have Samsung Galaxy A5 (2017).
EDIT: I found solution myself. I uninstalled old adb drivers, and then I installed universal adb drivers from here: https://www.clockworkmod.com/
For anyone still having a problem with this I found the solution. You need to be running adb on your PC (this is literally written on the bottom of the helium desktop app, I can't believe I missed it). So all you have to do is make sure adb server is running by going into CMD and typing "adb devices".
These are the steps:
1- Install ADB drivers on your PC (just google it and download the setup and install, simple as pie)
2- Open any command prompt and type "adb devices"
Installed the ClockworkMod universal Adb driver.
Manually updated driver in Windows Device Manager.
"adb devices" works for both MTP and PTP.
Helium still doesn't recognize PTP.
Update: Problem solved.
Installed Helium Desktop for Windows.
Run this desktop version instead of Chrome version!
After downloading the tariffs from the site, it still doesn't work.
I fixed that by replacing the adb files inside Helium\win32 by new recent ones.
Hi ! For other ppl experiencing same problem like I had myself too
I figured out that was the usb cable doing this problem and i tryed another one and it works fine ! Hope it help next ppl having same ptp issue !