Now I remember why I've always avoided using adb :-( I don't have a
Windows machine, I have a Macbook and a Raspberry Pi running Raspbian.
Here's what it looks like on the Pi:
mat@pi:~$ adb devices
List of devices attached
mat@pi:~$ adb devices
List of devices attached
???????????? device
mat@pi:~$ adb devices
List of devices attached
Last time I tried adb I found the problem was partly an unrecognised
manufacturer ID. I fixed this by editing adb_usb.ini. That file is
still there but isn't doing much for me now:
mat@pi:~$ cat .android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2a45
Does anyone know how to get adb talking to an MX4 without a Windows machine?
On 2016-04-07 16:27 , Marco Graziotti wrote:
Hi,
when I installed the firmware in one of my two MX4, I'm doing this
from Windows, because I have trouble to upload Flyme firmware from
Ubuntu Desktop.
So, you can find here:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
howto install ABD and fastboot on windows pc, you need this package to
permit at your computer to talk with your phone during "fastboot"
mode. You can find here a video that explain you howto use fastboot
and adb: https://www.youtube.com/watch?v=foLQCNxroHw
For installing the Flyme firmware you can find here a guide:
https://lists.launchpad.net/ubuntu-phone/msg13848.html but if you are
worried about the flashing process, I suggest you to ask (or search an
old threads) in "xda developers" forum to get help or find a guide for
flashing your device: http://forum.xda-developers.com/
Bye
