[Root]Wileyfox Swift

12 posts

Thanks Meter: 14

By , Junior Member on 1st December 2015, 05:49 PM

Post Reply Email Thread

Page 4 of 6 First 2 3 4 5 6

1st August 2016, 05:27 PM |#31

Junior Member

Thanks Meter: 5

Quote:

Originally Posted by grandmasterorge

I had a few problems doing this from Ubuntu 15.10.

1. ADB did not see the device although it worked fine on my Nexus 4 showing that adb/fastboot were configured correctly. I had to go to /home/.android and create the document 'adb_usb.ini' (right click, new document) which contains the text '0x2970'.

Once this was done I had to run the following commands

adb kill-server
adb start-server

This allowed ADB to see the device but it said that it was offline.

2. I had to create the file /etc/udev/rules.d/51-android.rules (type into terminal 'sudo nano /etc/udev/rules.d/51-android.rules') and paste in the following line, save it (ctrl+x, y, enter).

SUBSYSTEM=="usb", ATTR{idVendor}=="2970", ATTR{idProduct}=="2282", MODE="0666"

sudo service udev restart

After this ADB and fastboot recognized the device and allowed me to follow the directions posted above or on the cyanogenmod wiki.

Hope that is of some use to someone!!!

Thanks for this. For some reason I am not able to get the device to connect on Windows at all, so I will try Linux.

On Windows it tells me that the it is an Unknown USB Device (Device Descriptor not recognised. Error 43).

I have done the OTA update some suggested and this doesn't help, I get the same error. I have tried changing the cable (even though the Nexus works with the cable). The device is pretty much useless if I cannot connect it to a PC (never mind the ADB/Fastboot, I can't even see the internal or external SD cards). I have Windows 8, but I have turned off the driver signing and still no luck getting a driver installed for it. I have tried the Google ADB driver, the Naked ADB driver, the Samsung ADB driver and the Intel one and nothing at all..

Quick Reply Reply

2nd August 2016, 01:53 PM |#32

Junior Member

Thanks Meter: 5

Quote:

Originally Posted by Dior DNA

Did you use SuperSU-v2.65 ? or higher ? COS 13.0 is MM and needs systemless SuperSU

I can confirm that this fixed the problem I had which was as described by the other poster.

Very happy now!

Quick Reply Reply

16th September 2016, 04:01 PM |#33

Junior Member

Thanks Meter: 0

Problems here

Quote:

Originally Posted by olli_o

Hi all,
found out how to root this device!

Here the steps:

Make sure you have fastboot installed on your computer:
download supersu zip from here
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
```
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
```
download latest recovery image from here
to boot the custom recovery, on your computer type
Code:
```
fastboot boot <name_of_recovery>.img
```
OR
install recovery
Code:
```
fastboot flash recovery <name_of_recovery>.img
```
and reboot into recovery manually (remove and reinstall battery, hold volume down and power buttons.
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access

Thanks for this - seems to not work for me, however I initially installed SuperSU v2.46 and my wileyfox swift is running CM OS13 - seems I need SuperSU v2.65 or above. I tried again with v2.65 but during the install of SUPERSU zip I saw an error (but went too fast to catch the text of error)
Can you advise how to restore to original state to allow me to try this again with correct Super SU?

Also, an idiots guide to installing Mod rather than OS on wileyfox would be great.

Had 4EXT recovery on my rooted DesireHD, and found that useful, is there something similar for Wileyfox?

Apologies for all the Q's been a year or 2 since I last rooted and I'm afraid my memory isn't what it used to be!

Thanks all

Quick Reply Reply

17th September 2016, 12:56 PM |#34

Junior Member

Thanks Meter: 2

Quote:

Originally Posted by xander69

You just have to install the right SU .....(BETA-SuperSU-v2.77-20160827190633)
Dont have to restore to the original state.
To flash a ROM U just have to install the zip file using any custom recovery i.e after u have rooted ur device.

Quick Reply Reply

17th September 2016, 01:15 PM |#35

Junior Member

Thanks Meter: 0

Thanks, I'll give it a try - is that the recommended super su version or do any greater than 2.65 work?

Quick Reply Reply

17th September 2016, 03:23 PM |#36

Junior Member

Thanks Meter: 0

Quote:

Originally Posted by xander69

Thanks, I'll give it a try - is that the recommended super su version or do any greater than 2.65 work?

tried and was looking good.... until started Super SU installer - worked until "patching sepolitic...." step after that got a failure message and still unrooted

Any advice?

Quick Reply Reply

21st September 2016, 02:13 PM |#37

Junior Member

Thanks Meter: 2

Quote:

Originally Posted by xander69

tried and was looking good.... until started Super SU installer - worked until "patching sepolitic...." step after that got a failure message and still unrooted

Any advice?

Which SU did u use??
https://download.chainfire.eu/999/Su...0827190633.zip
Use this^^

Quick Reply Reply

The Following User Says Thank You to Joshua_JK For This Useful Post: [ View ] Gift Joshua_JK Ad-Free

21st September 2016, 02:43 PM |#38

Junior Member

Thanks Meter: 0

Used 2.65 but I'll download the version you suggest and give of a go, thanks

Quick Reply Reply

21st September 2016, 04:51 PM |#39

Junior Member

Thanks Meter: 0

still got problems here

Quote:

Originally Posted by Joshua_JK

Which SU did u use??
https://download.chainfire.eu/999/Su...0827190633.zip
Use this^^

Don't know if this is relevant:
output from "fastboot oem device-info"
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s

Quick Reply Reply

21st September 2016, 04:56 PM |#40

Junior Member

Thanks Meter: 2

Quote:

Originally Posted by xander69

Thanks for the link - it made no difference though, still seeing an error when installing SuperSU, begining to wonder if I'm doing the
fastboot flash recovery cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J0-crackling-recovery.img

step correctly, I run the command above, disconnect USB when it's finished, pull battery and re-insert, hold down volume down + power button, boot into recovery and apply update, ie navigating to SuperSU2.77 zip file and selecting it - each time I've tried there's some sort of error with the SuperSU install

Don't know if this is relevant:
output from "fastboot oem device-info"
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s

Your r not supposed to use cyanogen recovery!!
Thats what went wrong.
Flash TWRP 3.0.2.4..... " https://www.androidfilehost.com/?w=files&flid=48495 " -(Download the Zip file)
Then Root ur phone.

Quick Reply Reply

The Following User Says Thank You to Joshua_JK For This Useful Post: [ View ] Gift Joshua_JK Ad-Free

21st September 2016, 07:15 PM |#41

Junior Member

Thanks Meter: 0

Quote:

Originally Posted by Joshua_JK

Your r not supposed to use cyanogen recovery!!
Thats what went wrong.
Flash TWRP 3.0.2.4..... " https://www.androidfilehost.com/?w=files&flid=48495 " -(Download the Zip file)
Then Root ur phone.

excellent, SuperSU installed without any problem, got a rooted phone now, thanks

Quick Reply Reply

Post Reply

Page 4 of 6 First 2 3 4 5 6