[Root]Wileyfox Swift

12 posts

Thanks Meter: 14

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

Post Reply Email Thread

Page 3 of 6 1 2 3 4 5 Last

13th February 2016, 02:00 AM |#21

Senior Member

Thanks Meter: 195

Quote:

Originally Posted by TheRootPrince

Hey do we need to unlock a bootloader before installing the custom recovery on this device? Thanks.

From OP instructions (which I followed) it seems: yes.
I let others comment.
What is the concern?

Quick Reply Reply

13th February 2016, 02:16 AM |#22

Junior Member

Thanks Meter: 0

Quote:

Originally Posted by Dior DNA

From OP instructions (which I followed) it seems: yes.
I let others comment.
What is the concern?

Thanks. My mistake. I'm used to seeing the unlock bootloader at the beginning of a post.

Quick Reply Reply

12th March 2016, 12:43 AM |#23

Senior Member

Islamabad

Thanks Meter: 17

ON COMPUTER TYPE where on what? please tell the first step where to type these commands in?

Quick Reply Reply

12th April 2016, 12:32 PM |#24

Junior Member

Thanks Meter: 0

how to input the commands

How do you input the fastboot commands to the phone?

Quick Reply Reply

11th June 2016, 03:09 AM |#25

Senior Member

Thanks Meter: 195

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: https://wiki.cyanogenmod.org/w/Fastboot
download supersu zip from here
https://download.chainfire.eu/696/supersu/
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
http://download.cyanogenmod.org/?device=crackling
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

Has anyone tried this on swift COS 13.0 ?
I succeeded on COS 12.1 some time ago on a friend's phone.
But today, on another friend's phone, I tried after COS 13.0 upgrade,
and the boot stays on Cyanogen logo.
To recover, I reflashed stock partitions via fastboot.
All hints/comments welcome.
(see also thread 'Su binary')
update
systemless SuperSU-v2.65 is needed for COS 13.0 (Android 6 MM) ... then rooting succeeds.

Quick Reply Reply

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

13th June 2016, 08:40 PM |#26

Junior Member

Thanks Meter: 0

Phone no longer boots

I followed the instructions and up until the final step all was good, but after I installed SuperSU the phone gets stuck on the boot screen. Please help, I wish I hadn't done it now

Quick Reply Reply

14th June 2016, 12:15 AM |#27

Senior Member

Thanks Meter: 195

Quote:

Originally Posted by Kyt3

I followed the instructions and up until the final step all was good, but after I installed SuperSU the phone gets stuck on the boot screen. Please help, I wish I hadn't done it now

Did you use SuperSU-v2.65 ? or higher ? COS 13.0 is MM and needs systemless SuperSU
I had same issue, (using SuperSU-v2.46), but could always go back to stock with:

Code:

fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn

fastboot flash boot boot.img
fastboot flash cache cache.img 
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img

from unpacked cm-13.0-ZNH0EAS2NH-crackling-signed-fastboot-2306277a34.zip

Quick Reply Reply

20th June 2016, 09:19 AM |#28

Junior Member

Thanks Meter: 0

Hi,

I'm struggling with rooting.

booted the latest recovery from CM
Installed SuperSU v2.74 (beta) for with 'stable' the phone doesn't boot (official CMOS 13)
I have the /xbin/su binary but all the apps (i.e. TitaniumBackup) are missing root

I think, the keyword is 'systemless supersu'.
But what's a 'systemless' supersu and where can I download it?

Thanks!

Quote:

Originally Posted by Dior DNA

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

Quick Reply Reply

20th June 2016, 05:41 PM |#29

Senior Member

Thanks Meter: 195

Quote:

Originally Posted by Palmer.Blanquart

Hi,

I'm struggling with rooting.

booted the latest recovery from CM
Installed SuperSU v2.74 (beta) for with 'stable' the phone doesn't boot (official CMOS 13)
I have the /xbin/su binary but all the apps (i.e. TitaniumBackup) are missing root

I think, the keyword is 'systemless supersu'.
But what's a 'systemless' supersu and where can I download it?

Thanks!

'systemless supersu', as far as I notice, is one where su binary is placed in /su (sub)directory instead of /system one. I believe the installation also patches boot image (so each time you (re)flash boot you may need to reflash supersu). But do not take my words for expert. Rather double check on supersu forum. v2.65 is the first stable 'systemless' one AFAIK. just Google for "SuperSU-v2.65 ZIP". It worked for me after reflashing stock COS13 and from twrp-3.0.2-0 custom recovery. But other procedures and/or combinations might work equally well, of course.

Quick Reply Reply

28th July 2016, 07:29 AM |#30

Junior Member

Cambridge

Thanks Meter: 0

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: <link removed> success
download supersu zip from here
<link removed> success
save it to your external sdcard success
enable developer options (settings - about - click mutliple times on the build number). success
enable OEM unlock in the developer options settings on the device. success
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!!! success
on your computer type

Code:

fastboot oem unlock success
fastboot -i 0x2970 oem unlock-go <waiting for device>
fastboot oem unlock-go success

download latest recovery image from here
<link removed> success
to boot the custom recovery, on your computer type
Code:
```
fastboot boot <name_of_recovery>.img
```
success
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) install fails if I remove battery and go into recovery manually
reboot and enjoy root access **failed**

Hi, please see above where I have had trouble with certain steps to root.

I am only able to install supersu successfully if I do it immediatly after recovery has loaded after fastboot installed.

When I restart phone and check root, there are no changes to the phone?

PS. I also get <waiting for device> when I type "fastboot -i 0x2970 oem unlock-go"

Quick Reply Reply

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

Post Reply

Page 3 of 6 1 2 3 4 5 Last