ADB can't see my Swift

), 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

Quick Reply Reply

9th December 2015, 08:12 AM |#2

OP Junior Member

Bordeaux

Thanks Meter: 1

Bump - anyone? Bueller? Bueller?

B

Quick Reply Reply

16th December 2015, 12:50 PM |#3

Junior Member

Thanks Meter: 1

Quote:

Originally Posted by finnfather

Bump - anyone? Bueller? Bueller?

B

If you're trying to root then see the method I added to the end of the ROOT thread (can't post link, new account).

In short, you can get directly into the flashed recovery without it going back to normal and getting over written first without needing to use ADB to send it back to recovery mode.

Just take the back off, then once you have flashed the crackling recovery: pull the battery.

Plug it back in with the volume down held and power the device on, holding volume down.

You'll get into the recovery and can install superSU.

Hope that helps.

Quick Reply Reply

18th December 2015, 06:04 PM |#4

Member

High Wycombe

Thanks Meter: 6

Quote:

Originally Posted by finnfather

Hi all,

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

I had the same problem on my Windows 10 that was upgraded from 8.1.

To fix it, I removed completely Android SDK and reinstalled it. For some reason this was the solution for me.
I tried the same things as you before that (except factory restore as it is a pain) and got the same results - no device listed.

As for Linux and OSX, the Swift got recognized without a problem.

Quick Reply Reply

9th January 2016, 02:27 PM |#5

Member

Manchester

Thanks Meter: 41

Quote:

Originally Posted by finnfather

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 atock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,

Jev

Quick Reply Reply

25th January 2016, 01:18 AM |#6

Senior Member

Thanks Meter: 41

Hi

Windows 10, android sdk installed and google drivers.

Fastboot shows 8bce440 fastboot when fastboot devices is tried in cmd (admin priv) and "waiting for any devices"

ADB list devices is also empty.

Any help appreciated.

Quick Reply Reply

25th January 2016, 02:47 PM |#7

Member

High Wycombe

Thanks Meter: 6

Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.

What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?

Quick Reply Reply

25th January 2016, 05:31 PM |#8

Senior Member

Thanks Meter: 41

Quote:

Originally Posted by Pak0St

Hi Cheers for replying.

I have now tried it on Win 10 (clean install) win 8.1 (clean install) and windows 7 (clean install)

Reinstalled sdk on 8.1 and 10 twice but no joy. I cant see anything under device manager for it (in fastboot)

Under devices and printers it shows Android

Any help appreciated.

---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------

adb_usb.ini could this help? I have tried creating a file manually. But no joy

Quick Reply Reply

25th January 2016, 06:48 PM |#9

Member

High Wycombe

Thanks Meter: 6

In fastboot mode, it should come up as Marshall London Bootloader Interface under Device Manager. From Devices and Printers you can check what driver is currently installed when it's displaying "Android".
Windows 8/10 is very insistent on using verified drivers. You could try to uninstall the current driver and re-connect the device so that Windows can try to find the verified ones.
For me it automatically installed the fastboot drivers, although it wasn't fast enough and the Swift rebooted before the drivers were finished with installation.

Quick Reply Reply