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 !
Related
Hi,
Has any one been able to connect to samsung galaxy I5801 using adb? Running adb devices is not listing the device for me. I have installed samsung kies.
thanks, srb.
srbose said:
Hi,
Has any one been able to connect to samsung galaxy I5801 using adb? Running adb devices is not listing the device for me. I have installed samsung kies.
thanks, srb.
Click to expand...
Click to collapse
Have you put USB in debug mode?
Ciao
Hi Slumpolo,
Yeah, i have enabled the usb debugging option and rebooted the phone.
Before doing that I also went to Settings>About Phone>USB settings, and selected "mass storage" . This options gets disabled when USB debugging is on, but I did it just to be on the safe side.
Windows device manager shows that all the drivers are installed correctly.
i also did adb kill-server and adb devices multiple times.
Oh boy....its much deeper than that. Search YouTube "how to Android adb devices"...its kinda tricky.
sent from the current baddest cell phone on the planet.....the HTC Evo 4G
Hi StaraSkola,
I went over all the videos I could find and I believe I am doing everything right. To verify my setup, I connected by friends Galaxy S I9000 and I was able to see it in adb devices.
I did the same with my GT-I5801, and it does not get listed in adb devices. I made sure I was in USB debugging mode.
One difference I noticed in device manager was this:
When I connected I9000, a device called "Samsung Android Composite USB device" showed up in the USB devices.
But when I connect the GT-I5801, I get a device called "Samsung Composite USB device" ... there is no android mentioned any where.
I have tried reinstalling the driver but Windows insists it cant find a better match.
Does this help in root causing the issue?
thanks,
srb.
I finally managed to connect to my GT-I5801, both via Samsung Kies as well adb. yay!
I will note down all the steps that I did, in case any one finds it useful.
1. I re-installed Samsung Kies and then I reinstalled the Samsung drivers. This can be done using the "Driver Recovery" option available in the top left drop down menu in the Kies window. Its a button called Kies. I did this as I had messed around with my devices and drivers trying to discover my phone. But this did not solve my problem.
2. I unmounted the SD card and re-formatted it. The SD card had a few mp3 files in it and Samsung Kies is known to have issues with some types of MP3 files. This did not solve my issue. Phone was still undiscovered.
3. My most drastic step: I went to settings > reset to default. This erased all my settings and all my installed apps and I lost all my notes etc ( .. But, after I connected my phone back to the laptop, everything came up just fine. I was able to browse the phone using Kies and then connect to ADB shell after enabling USB debugging mode. So the problem was with one of my installed apps. I dont know which but I suspect it could be a modded Navigation app (BRUT mod) , that I had installed. But I am not sure.
4. When connected using Kies, there is an option in Kies to eject the phone. If I use this, then Kies does NOT connect back to the phone when I plug it back in. I have to reboot the phone. The workaround is, never use the eject option. Always remove the phone by simply unplugging the USB cable. Then Kies discovers it on connecting back and even adb is able to connect to it. I dont know if other other Galaxy models suffer from the same problem but folks can try out this work around.
Thanks,
srb.
Apologies if this is already posted, each time I search the forum it says search is unavailable.
OK, I'm on Win 7, trying to restore some stuff from my N4 using Helium, this requires you to connect to a PC with USB debugging on (done) and PTP as opposed to MTP (set on the phone).
My problem is that Windows will not install the drivers in PTP mode, I have removed all traces of Android/ADB/Nexus 5 from Device manager (uninstalled and removed drivers where available).
I've downloaded the latest SDK and installed the drivers from there.
Still not happening. It installs fine in MTP mode so I can access the storage.
Can anyone help?
thanks
mmace said:
Apologies if this is already posted, each time I search the forum it says search is unavailable.
OK, I'm on Win 7, trying to restore some stuff from my N4 using Helium, this requires you to connect to a PC with USB debugging on (done) and PTP as opposed to MTP (set on the phone).
My problem is that Windows will not install the drivers in PTP mode, I have removed all traces of Android/ADB/Nexus 5 from Device manager (uninstalled and removed drivers where available).
I've downloaded the latest SDK and installed the drivers from there.
Still not happening. It installs fine in MTP mode so I can access the storage.
Can anyone help?
thanks
Click to expand...
Click to collapse
Try installing these drivers http://forum.xda-developers.com/showthread.php?t=1514942, don`t know for sure if it will work but i think it will.
gee2012 said:
Try installing these drivers http://forum.xda-developers.com/showthread.php?t=1514942, don`t know for sure if it will work but i think it will.
Click to expand...
Click to collapse
worked perfectly, thank you!
mmace said:
worked perfectly, thank you!
Click to expand...
Click to collapse
Worked great for me, though didn't have to go through all the motions, uninstalled the ADB driver that windows was automatically assigning. extracted the driver pack, then plugged the N5 back in and hey presto, windows recognised the device as something i can navigate.
Time to put my music and photos back on it now.
Cheers.
Hi all.
I have installed MyMobiler on my PC (Win7 x64) and followed the instrusctions on this website. http://mymobiler.com/android-setup-start.html
But i cant connect with USB! The device manager shows a conflict icon with the one.
USB Debugging is turned on.
Can enyone help me with that? I would likely use my phone over the PC.
You probably have an incorrect ADB driver installed, try manually selecting the Google/Nexus driver.
yeah youre right!
i solved it like here: http://forum.xda-developers.com/showthread.php?t=2782721
but now i am not rly excited of "mymobiler"
can any one suggest a good remote controler for android! (PC controls Android)
want to type messages and full control the device like it is in my hand
pls only free suggestions.. dont want to pay 8EUR for tightvnc!
Just attach your device with pc and click my mobiler see android settings in this there is install and uninstall press install my mobiler will automatically install it's app in your mobile.
But i am not sure if this function needs root or not because it wanted permission in rooted device and i can't test on not rooted not having correct adb drivers. Can anyone help me adb drivers for karbonn a12 star it is a phone with dead display i will use it with my pc thank you.
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
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.