ADB not seeing my Swift (retry)

finnfather

Member
May 21, 2014
28
1
0
Bordeaux
Hi all, posting here because my other thread hasn't been seen.

I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.

I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.

And yes, I've turned on developer options, etc.

I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...

B

Update: I have found that at the least I should be able to see my phone in the Other Devices list in the Device Manager but I've got nothing, just ADB Interface
 
Last edited:

yasteellutch

Senior Member
Aug 10, 2015
133
32
0
Johannesburg
Alright I see. I am assuming you are using stock COS. So when you enable developer options and enabled android debugging your computer did not want to pick it up. Unplug device and Try revoking USB Authoriztions in developer options. plug swift back in and look at the device. It should ask you for Authroization
 

jevtheboss

Senior Member
Jun 18, 2015
137
57
0
Manchester
Hi everyone,

@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the stock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,

Jev
 
Last edited:

ottischmidt

New member
Jan 13, 2016
2
0
0
I cound manage the get a workung adb connection, buy switching adb debugging off and on again on the device while the device was connected to the pc via USB. Then I opened the device manager in windows and klicked on update driver vor the unrecogniced device. After that the device prompted a dialog, I had to accept the connection. Now the device was visible in the adb device list. (@jevtheboss: So you do not have to reinstall the cm to make it work)
 
Last edited: