Hi, I have a problem in the connection between the fire and kindle mac.
I state, ADB I installed and working properly.
When I enable debug function, and I enter the command ./adb devices, the output gives me empty, ie not find the kindle. Yet he continues to appear on the desktop and connect as mass storage.
How can I do?
what rom do you have on the kf couse you are able to enable/disable usb debugging ?
may be you are able to find mac specific answers over the *FULL LIST*
maybe restart adb by "adb kill-server" and try again ...
b63 said:
what rom do you have on the kf couse you are able to enable/disable usb debugging ?
may be you are able to find mac specific answers over the *FULL LIST*
maybe restart adb by "adb kill-server" and try again ...
Click to expand...
Click to collapse
Is the stock rom: Current Version: 6.2.2_user_3205220
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
4K2K said:
My Win10 Insider Preview machine did not recognize the phone. Nothing happened when I connected the phone and I could not access storage of the phone.
Below is the solution for it:
Go to Control Panel - Device Manager - LeMobile Android Device (could be under a different name. Choose the one that is your phone) - Update Driver - Manually Install a Driver - Let me pick a list of available drivers on my computer - MTP USB .
Click to expand...
Click to collapse
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Alternative solution is to use KDE Connect app over Wifi. Bonus is that once set up, it is possible to push files from the phone to the PC without any interaction on the PC side - e.g. useful if the PC doubles as a file server.
losteagle said:
Uhm ... when you connected the phone to computer you changed the mode on phone from USB charging to MTP mode ?
In my Win10 x64 build 14392.447 not problem to see the phone in MTP mode after changing mode on phone.
Click to expand...
Click to collapse
Both of my home & works computer (Win10 14959) failed to detect it as MTP or PTP drive. Might have been due to those having previous phone's drivers.
But I faced same problem with fresh out of the box Win8 laptop.
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
ksj0823 said:
No issue with the MTP, however I can't seem to get adb to work. list of devices attached is showing empty.
Click to expand...
Click to collapse
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Citroon said:
I had the same issue, i reinstalled minimal ADB and removed the drivers from my pc, rebooted my pc. Plugged the phone into a different USB port and voilá ADB could see it
Click to expand...
Click to collapse
Wanted to add my voice here too that I did the same - I had to clean up previous drivers I had installed over time for varios phones and different ADB versions like the one from clockworkmod - once I cleaned that out and installed google drivers from SDK PTP worked and I was able to do Helium restores
I had issue on my Win10 PC, but I found that after I disabled USB debugging, it would work as MTP/PTP, but not for ADB of course. So apparently, I have to toggle USB debugging ON/OFF to switch back and forth from MTP and ADB.
Small pain in the butt.
Solution.
I had the same issue. Drove me NUTS for about an hour. In the end, simply unchecked the USB DEBUGING in developer settings. This will make it pop up immediately.
Update:
I clearly should have read the post above mine first.
Hi,
Since my phone is not yet rooted, I thought it might use Helium to perform an app backup, but I cannot get Helium to recognize the phone. ADB devices does indeed that the phone is connected. Any ideas?
Thanks
PH-1 ADB
How did you get ADB to recognize PH-1?
I have been unsuccessful in all attempts from all the web sources to get adb devices to recognize the PH-1, nor any device with the name Mata.
With usb file transfer set to MTP I can get Windows 10 x64 to read the PH-1, but adb and fastboot cannot find the device. I have tried Android ADB Interface, Android Bootloader Interface, & Android Composite ADB Interface for the Android Phone drivers with no luck. When I try to the PH-1 Driver under Portable Devices, I get an error message that the latest Google USB driver does not contain compatible software for the PH-1 for Windows 10 x64.
Any ideas?
Doug
[email protected] said:
How did you get ADB to recognize PH-1?
I have been unsuccessful in all attempts from all the web sources to get adb devices to recognize the PH-1, nor any device with the name Mata.
With usb file transfer set to MTP I can get Windows 10 x64 to read the PH-1, but adb and fastboot cannot find the device. I have tried Android ADB Interface, Android Bootloader Interface, & Android Composite ADB Interface for the Android Phone drivers with no luck. When I try to the PH-1 Driver under Portable Devices, I get an error message that the latest Google USB driver does not contain compatible software for the PH-1 for Windows 10 x64.
Any ideas?
Doug
Click to expand...
Click to collapse
I did nothing special. I assume you enabled USB debugging and the standard Android USB drivers are installed.
I got Helium to work after some fiddling including upgrading the desktop client. I switched between file transfer mode and PTP mode and then it just worked.
Any Luck?
[email protected] said:
How did you get ADB to recognize PH-1?
I have been unsuccessful in all attempts from all the web sources to get adb devices to recognize the PH-1, nor any device with the name Mata.
With usb file transfer set to MTP I can get Windows 10 x64 to read the PH-1, but adb and fastboot cannot find the device. I have tried Android ADB Interface, Android Bootloader Interface, & Android Composite ADB Interface for the Android Phone drivers with no luck. When I try to the PH-1 Driver under Portable Devices, I get an error message that the latest Google USB driver does not contain compatible software for the PH-1 for Windows 10 x64.
Any ideas?
Doug
Click to expand...
Click to collapse
Hi Doug I am having the same issue on Windows 10 64bit. I've uninstalled and reinstalled the Universal Drivers provided by Koush as well as the Helium desktop client. Have you had any luck?
Thanks,
-Blake
I see same issue with Windows 7x64, and PH1 (running oreo beta: I didn't try it with the Nougat release): Helium PC app doesn't find the client to enable it.
PC finds the phone and loads Essential ADB drivers, but Helium PC app never finds the client on phone to enable it. Whole setup worked just find to backup the Nexus 5x I am moving from.
I didn't try using the generic drivers provided on Helium site, I guess I can give that a shot.
Same issue on my Mac running Essential Oreo beta build. Phone recognizes it is plugged in to a computer but says waiting for the Helium Desktop application.
l0aded said:
Same issue on my Mac running Essential Oreo beta build. Phone recognizes it is plugged in to a computer but says waiting for the Helium Desktop application.
Click to expand...
Click to collapse
Thanks. I also tried the generic ADB drivers, same results. SO must be some incompatibility with Essential (and/or with the beta build).
Joe Kane said:
Thanks. I also tried the generic ADB drivers, same results. SO must be some incompatibility with Essential (and/or with the beta build).
Click to expand...
Click to collapse
On Mac and if you are using chrome Helium web app, the bundled adb binary is too old to recognize the PH-1. Swap it out and you are golden.
Sent from my PH-1 using Tapatalk
I finally got it to work by doing the following:
1. Removing all previous versions of ADB (including the one I downloaded from Clockworkmod)
2. Installed the PH-1 Windows driver directly from Essential from here: https: //storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe and installed it.
3. Opened Command Prompt as Administrator and navigated to C:\Program Files (x86)\Essential\ADB and typed the command "adb.exe start-server" then it confirmed the server had been started.
4. Opened Helium on my PC desktop, then plugged in my PH-1 to my USB port (using an Anker cable in case it matters) and it asked for permission for this specific computer to access USB debugging (make sure to enable USB debugging first) and then it connected to Helium Backup and I was able to Backup.
Hope this helps someone.
-Nikbone
i got helium working but is does not restore any app data. i have no idea, why
Dude
nikbone said:
I finally got it to work by doing the following:
1. Removing all previous versions of ADB (including the one I downloaded from Clockworkmod)
2. Installed the PH-1 Windows driver directly from Essential from here: https: //storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe and installed it.
3. Opened Command Prompt as Administrator and navigated to C:\Program Files (x86)\Essential\ADB and typed the command "adb.exe start-server" then it confirmed the server had been started.
4. Opened Helium on my PC desktop, then plugged in my PH-1 to my USB port (using an Anker cable in case it matters) and it asked for permission for this specific computer to access USB debugging (make sure to enable USB debugging first) and then it connected to Helium Backup and I was able to Backup.
Hope this helps someone.
-Nikbone
Click to expand...
Click to collapse
9 hours and 8 PCs later, with different versions of windows, and you saved my sanity with this. Worked flawlessly! Thank you, seriously. Awesome work
I had the same issues to run Helium backup on my PH-1, but now it works.
The Helium ADB driver kills the Essential ADB driver and starts its own.
It looks like this is not compatible with Essential. To avoid this I replaced the driver from Helium with the driver from Essential.
1. Install the Essential driver from the link mentioned above
2. Install Helium backup
3. Go to C:\Program Files (x86)\ClockworkMod\Helium\win32 and delete the files "adb.exe", "AdbWinApi.dll" and "AdbWinUsbApi.dll"
4. Copy the same three files from C:\Program Files (x86)\Essential\ADB to the Clockwork folder
Oliver
Thank you ever so much. It worked, although I reinstalled Helium on my laptop, then copied the 3 files from the Esseential folder in Program Files (x86) to the Clockwork Mod\Helium\Win 32 folder replacing those files in the CWM Helium\Win32 folder. Finally doing a Helium Backup after 8 months of having the PH-1.
Thanks to everyone for their creative solutions! None of them worked for me, I am on Windows 10 64bit. What finally worked for me was using the Chrome version of the Helium Desktop client. It's available on Clockworkmod's website and he even recommends it.
Once you have that app up and running, Powershell/Bash your way from the Essential Driver USB folder and start the adb server, until USB permissions are prompted for. On my phone for USB options, I had the PTP option work for me.
Good luck to everyone and thanks for this!
nikbone said:
I finally got it to work by doing the following:
1. Removing all previous ...
Click to expand...
Click to collapse
Super. Thanks!!!
I haven't been able to get data transfer to work when connected to computer since Color OS 6 update. Pop up warning says resetting USB Debugging is required. Actions already taken :
1. Turn usb debugging on/off
2. Turn developer options on/off
3. Revoke usb debugging (adb devices shows device ID)
4. Enable usb tethering
Any suggestions?
After days of no response and some efforts of painful google-searching , I finally find a solution using adb command which is
adb shell svc usb setfunctions mtp
That being said there should not be any issue with usb / adb driver whatsoever, because I can use file transfer on my LG V30+ just fine using the very same laptop. Also system security check showed usb transfer is being blocked (see attached pics)
I had previously connected my Asus X00TD to my laptop for transferring files. The phone doesn't connect to PC from yesterday. Only charging happens after connection, and device doesn't show up on the device manager(no change on list of devices after connection), and no notification sound of device being connected either. There is no notification in my phone as well. Here are the following workarounds I have tried, but failed:
Changing USB cable
Changing PC/laptop
Installing ADB and Qualcomm drivers and again uninstalling them(error code 10 on ADB Driver)
enabling and disabling USB debugging
changing connection mode(nothing works)
Going into safe mode
restarting and connecting multiple times
Kindly help me if possible, and your help will be kindly appreciated
I had a similar problem recently. What ended up working for me was to install some generic Android driver published by Google. I already had the ADB package installed, but without the generic Android driver published by Google, my phone could charge and transfer files, but I could not issue ADB commands through the Windows command prompt.
The package I needed was called "usb_driver_r13-windows.zip"