yashsingh1/xdaforums huggingface dataset:
[Wileyfox Swift] Fonzie!:
Cannot unlock OEM

How do you guys even get this far?!

I can't even get past "fastboot oem unlock"!!

What I'm using:

CMD.exe with Admin privileges from Windows 10 to use adb and fastboot. They're in C:\AndroidRoot\platform-tools

Wileyfox Swift with CyanogenOS 13.1.5-ZNH2KAS7EB-crackling (Android 6.0.1)

The Swift's CyanogenMod API level is "Elderberry (5)" and its Android Security Patch is "1 December 2016", if that helps?

What I did:

Activate Developer Options

Turn on Advanced Reboot

Turn on OEM unlocking

Turn on Update Cyanogen Recovery

Turn on Android Debugging (ADB) and its notification

Download the platform tools on my Windows

Put the SuperSU zip on an SD card (in the main directory), inserted that into the phone, backed up some files from the phone onto a separate folder in the SD card as well.

Powered down the phone

Hold Volume Up and then at the same time the power button until it went into Fastboot mode (I think).

Connected via USB

Ran CMD with admin privileges (just to be sure) and ran the following code (with output):

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd ..\..\AndroidRoot\platform-tools

C:\AndroidRoot\platform-tools>adb devices
List of devices attached

C:\AndroidRoot\platform-tools>fastboot devices
5c63c60c fastboot

C:\AndroidRoot\platform-tools>fastboot oem unlock
...
(bootloader) Warning: unlock will wipe all user data
(bootloader) Please confirm

Here its stuck.

I've tried hitting Enter, Space and Ctrl.

I've tried Y for "Yes", J for "Ja" since it's a Dutch Windows installation (I dunno?!?!), and even Ctrl+Y and Ctrl+J.

The phone's Fastboot mode shows a black screen with the Cyanogen-logo, the title "FASTBOOT MODE", and the following options in blue:

Reboot to Android (grey background)

Reboot to Recovery

Reboot to Bootloader

Power down

About the Phone

Reboot to EDL

I tried tapping on the options, swiping, two-finger tapping, double tapping, tap-and-holding... Nothing, it doesn't seem touch-responsive (which I didn't expect but give me a break I'm desperate)

After waiting several minutes I gave up and aborted the command with Ctrl+C, then continued as follows:

^C
C:\AndroidRoot\platform-tools>
C:\AndroidRoot\platform-tools>
C:\AndroidRoot\platform-tools>
C:\AndroidRoot\platform-tools>
C:\AndroidRoot\platform-tools>
C:\AndroidRoot\platform-tools>
C:\AndroidRoot\platform-tools fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: -0.000s

C:\AndroidRoot\platform-tools>fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
C:\AndroidRoot\platform-tools>fastboot oem unlock-go
...
FAILED (command write failed (No error))
finished. total time: 0.000s

C:\AndroidRoot\platform-tools>fastboot -i Wileyfons-Swift oem unlock-go
error: invalid vendor id 'Wileyfons-Swift'

(the phones Device Name was set to "Wileyfons-Swift" for better recognition while developing)

Does anybody know what to do here?

Please help?
[Wileyfox Swift] robin0800:
I am not certain but believe you need a space between unlock and -go
[Wileyfox Swift] Fonzie!:
First off, I noticed that to "confirm" fastboot oem unlock, I have to press the power button on my phone... Ok?

The phone then simply boots up all the way back into CyanogenOS.

"fastboot oem unlock -go" results in "C:\AndroidRoot\platform-tools\fastboot.exe: unknown option -- g"

Any ideas?
[Wileyfox Swift] robin0800:
Do" fastboot devices"

Try "fastboot -i 0x2970 oem unlock-go"

You should not touch the phone until the fastboot commands have finished use the computer return key to execute the fastboot commands.
[Wileyfox Swift] M.A.K:
As you were asked for confirmation, you obviously got it right first time.

Like most people, I've only done this once so I don't remember the details. But if there's no prompt in the cmd window then look at your phone. It should be intuitive as I don't remember having any trouble.
[Wileyfox Swift] OneNot:
I can't flash the recovery

I can't seem to be able to flash the recovery...

When I try I get this error:

FAILED (data transfer failure (Unknown error))

OEM unlocked just fine.

I should mention the link (download.cyanogenmod[dot]org/?device=crackling) didn't work (Over Quota), so I was using TWRP 3.1

Downloaded from here: dl.twrp[dot]me/crackling/

UPDATE:

I used another USB cable and it worked.

Now I have another problem though...

First of all my phone doesn't react in any way to flashing a new recovery. Should it?

First I just flashed the new recovery: seemingly succeeded, but after rebooting to recovery the old one was still there.

After that, I first erased the recovery and THEN flashed the TWRP one and then when I booted to recovery it was TWRP.

I thought that flashing it was supposed to replace the old one in any case, but whatever.

Well, after installing the supersu from there I rebooted to the OS and nope. No root.

After that, the recovery got magically replaced with the old one again.

Every time I boot into the OS, the recovery gets replaced and I have to flash it again to get the TWRP recovery.

It says "No OS detected" in TWRP btw...

Also, when installing the supersu it throws errors. "failed to mount '/system' (no such device)"

That doesn't seem good. It does say everything else succeeds though...

I'm really confused.

Help!?
[Wileyfox Swift] wileyfail:
Experience Share:

Following the steps in the initial post, I naively wiped everything before installing SuperSU, as I wanted to install LineageOS afterwards. But then my phone did not start SuperSU or anything, just kept going back to Bootloader no matter what.

Solution: Install the normal Android from Google (7.1.1 Nougat in my case), then install SuperSU, let it boot into the normal android, then go back to recovery, only THEN wipe everything and install Lineage OS instead, succeed, party hard:)

BTW: As cyanogen went down the initial post's recovery image link is dead; I used the TWRP recovery image instead from <noobs cant post links but you will find out by yourself>

After Wileyfox's pure Android Update softbricked my phone I am now root&roll-ing with LineageOS, thank you so much guys:cool:
[Wileyfox Swift] StigR21:
Hi,

I had my first attempt at rooting my Swift over the weekend and it did not go to plan.

After getting TWRP onto my phone though ADB I was unable to mount the system as has been mentioned above. I watched a video on possible work around to be able to mount the system and one such way was to change the file system so that there was data. The problem was that I forgot to change the file system back to what it was before I tried to flash SuperSU.

I am now stuck in a boot loop. I can get into bootloader and I can also get into the default recovery but TWRP does not seem to be on the device anymore.

I've tried wiping the data and wiping the cache partition but those don't remove it from the boot loop.

My device will connect with my computer using the ABD Sideload, however when I try to send something it fails with the following message:

e: footer is wrong

e: signature verification failed

e: error: 21

Does anybody know anyway in which i can sort it.

Any help is appreciated

Thanks!!
[Wileyfox Swift] wileyfail:
If you can get to bootloader then stay there and flash TWRP again with fastboot:

fastboot flash recovery <TWRP-Imagefile>
[Wileyfox Swift] StigR21:
Thanks for your advice, I tried what u suggested but when i'm in bootloader I can't connect to the ADB. :( I can only seem to connect to the ADB on my computer through the default recovery when i select apply update from ADB and i tries via sideload. But when I try to reboot bootloader from there I just get error: closed
[Wileyfox Swift] wileyfail:
Adb and fastboot are two different tools, at least for me as linux ubuntu user. Which OS is your computer? How / what toolchain did you install?
[Wileyfox Swift] Dior DNA:
just guessing from OP

- enable OEM unlock in the developer options settings on the device.

- use '-i 0x2970' for fastboot
[Wileyfox Swift] StigR21:
I've now got my phone back to how it was before it was stuck in the bootloop but I have the exact same problem when I try to root.
[Wileyfox Swift] guriinii:
Where do you get the original img file? I'm stuck in a the fastboot menu. Help, haha. I need to restore it before trying again.
[Wileyfox Swift] eg789123:
ok so I got to this stage:

(bootloader) device was already unlocked

OKAY [ 0.002s]

finished. total time: 0.014s

now what?

how does one install the TWRP itself from here, the main site says something about copying the twrp files into adb folder?

where is this on PC or phone?

where do I go from here to flash TWRP, main app isnt much help either, as where does that download to?

Im using a swift with the nougat update 7.1.1/n6f26y/5506d7d322user release-keys
[Wileyfox Swift] robin0800:
In bootloader mode

fastboot flash recovery "name of recovery file"
[Wileyfox Swift] eg789123:
read a bit further, no luck keeps saying cant find file, and did copy the file into ADB folder on C drive in windows,

is the latest TWRP working on the swift with the latest update? maybe I need to try a different version?

anybody managed to get it to work correctly inside the latest wileyfox? what needs to be done differently?
[Wileyfox Swift] eg789123:
ok, so here is my progress so far on this project,

ITS NOT POSSIBLE to ROOT!!!!!

at least with the latest update, (TOS111B-N6F26Y)

tried multiple times to install TWRP, flashes successfully latest version and older versions,

did unlock bootloader (paid the price of admission by reset to factory settings:))

does not work, takes me back to stock recovery and stock bootloader,

tried kingroot to flash, no joy, not possible to flash,

tried windroid toolkit, no joy same issue, does not see phone,

even tried towelroot, not possible with this phone......

tried to go back to earlier CM 13 version, does not proceed to flash keeps saying error 21 signature verification failed,

tried CRdroid latest same issue as before,

anybody got any suggestions?

jevtheboss has been helpful, but no TWRP is possible, BEdroid no reply.

Ill repeat the important information in the hopes somebody got something that works........:o

Wileyfox swift version 1, original phone NOT the 2 or 2 Plus

latest nougat update installed, (TOS111B-N6F26Y).

android version: 7.1.1

security patch level: 1 may 2017

kernel version:

3.10.49-g3521c11

jenkins@bob #1

fri apr 21 13:18:42 west 2017
[Wileyfox Swift] stevo38:
Hi,

I have a Swift 2 Plus, just updated to Android 7.1.1 and found the same issue, TWRP for Swift 2 Plus is for Marmite not Nougat.

Build Number, (TOS118C-N6F26Y).

android version: 7.1.1

security patch level: 1 may 2017

kernel version:

3.18.31-g22136f6

jenkins@bob #1

fri apr 28 14:10:42 west 2017
[Wileyfox Swift] mocrole:
Hi,

I have the same issue. Stock in a boot loop of bootloader and the recovery and have not found a way out or even to enter fastboot.

It’s a Swift 2 Plus with latest android 7.1

Can anyone help?
[Wileyfox Swift] johnaaronrose1:
adb devices does not show my phone

2 points:

1. The 'Install ADB and fastboot on Windows with Minimal ADB and Fastboot' procedure does not allow specifying where adb & fastboot are installed. They actually install to c:/adb folder.

2. 'adb devices' does not show my Wileyfox Swift phone.
[Wileyfox Swift] robin0800:
Have you android debugging enabled and authorised on your phone the former is required for detection and the latter to enable communication?
[Wileyfox Swift] johnaaronrose:
[MENTION=4453551]robin0800[/MENTION]

I have both android debugging enabled and authorised on my phone. I have tried connecting my phone both to Ubuntu and to Windows on different computers with the same result. I think that the problem is due to Android Nougat 7.1.1 on my Wileyfox Swift. I have noticed that I get a popup of "Unfortunately, the process android.process.media has stopped" Media Storage has stopped" on my phone (with the only option being to close the app) when I select MTP for the "USB for file transfer" notification on my phone. Simultaneously, I get a popup on my computers of about not being able to mount the phone for MTP. I have googled "process android.process.media" with stop and the best one seems to be https://www.techjunkie.com/unfortunately-the-process-android-process-media-has-stopped/. I've tried the steps on that site but am baffled by the one saying that find an app within Apps for Settings as I have no such app on my phone. I think that the problem is Nougat 7.1.1 on my phone which replaced CyanogenMod recently as "adb devices" used to work before that happened. I've noticed that LineageOS has been recommended by some people instead of Wileyfox's Nougat: one of the reasons being that the Truecaller Dialer then reverts to Google's Dialer. I've also noticed that the Here We Go app no longer works. If you think that LineageOS is better than Wileyfox' Nougat, could you point me to an accurate guide for the installation of LineageOS? The one at https://wiki.lineageos.org/devices/crackling/install is useless since it requires fastboot to work and it doesn't for me as I can't get a proper connection between my computer and my phone. I couldn't even ask a question on the subreddit for that site as there seems to be no mechanism to do so!
[Wileyfox Swift] Dior DNA:
Does 'lsusb' on Ubuntu show the device?

I guess fastboot connection capability should not necessarily depend on Android OS installed.

Do you have a TWRP backup of CyanogenMod?

If so, and if you want to try LineageOS, you can restore from to a situation when everything still worked.
[Wileyfox Swift] robin0800:
Would suggest you get a reliable connection between your computer and phone first both in adb and fastboot. Fastboot is easier and does not rely on adb or debugging to work.

You need to be in bootloader mode and if using linux need sudo fastboot.
[Wileyfox Swift] johnaaronrose:
I have no TWRP backup of CyanogenMod.

---------- Post added at 07:35 AM ---------- Previous post was at 07:33 AM ----------

I forgot to state that lsusb does show the phone:

john@Barebones:~$ lsusb

Bus 001 Device 020: ID 2970:2282

---------- Post added at 07:42 AM ---------- Previous post was at 07:35 AM ----------

I do have reliable usb cables between my computers & phone. I use the same cables successfully between my computers & Android tablet. fastboot (to my phone) does not work:

john@Barebones:~$ fastboot oem unlock

< waiting for device >

As I previously said, I think that the problem is Wileyfox's Nougat 7.1.1 and I would like to install LineageOS but can't as it requires fastboot to work.
[Wileyfox Swift] robin0800:
I find it hard to believe that you think wiley fox's 7.1.1 stops you getting into the bootloader have you read this from here

"Download: With the device powered down, hold the Volume Up and connect USB"

https://wiki.lineageos.org/devices/crackling
[Wileyfox Swift] johnaaronrose:
Bootloader unlocked

The instruction you quote (Download: With the device powered down, hold the Volume Up and connect USB.) is from https://wiki.lineageos.org/devices/crackling. Unfortunately this instruction does nothing on my phone except briefly show the power status as a set of vertical blocks with a number (e.g. 100%). On the other hand, if I do 'With the device powered down, hold the Volume Down and Power buttons.' (from the same webpage), it goes into an 'Android Recovery' screen. This allows me amongst other options to go into the Recovery mode or Restart Bootloader screen which both show that the bootloader is locked. Thus, as the webpage giving instructions on installing LineageOS https://wiki.lineageos.org/devices/crackling/install implies, the bootloader must be unlocked first.
[Wileyfox Swift] robin0800:
If you can get to the bootloader screen which they call Download you can unlock the bootloader from there provided you have allow "OEM unlocking" ticked in developer options on the phone.

"Download: With the device powered down, hold the Volume Up and connect USB" This works on my phone!
[Wileyfox Swift] johnaaronrose:
I've now done what I wanted, namely to get rid of Nougat 7.1.1 as supplied by Wileyfox. I've now installed LineageOS 7.1.2. The "Here We Go" app now works. Also, the phone used to think for a few seconds before taking a photo: with LineageOS, it photographs instantly. Rooting was so easy (which I never managed with Marshmallow or Nougat 7.1.1) i.e done through developer options.
[Wileyfox Swift] twt131:
Gerät startet nur in den Fastboot Modus

Hallo,

danke erst einmal für die gute Anleitung.Ich hatte es schon so oft anders versucht,ohne Erfolg.Mein Problem ist jetzt nur,das das Handy immer nur in den Fastboot Modus neustartet.Mit TWRP und dem Installieren eines Custom Roms hat es wunderbar geklappt.Vielleicht hast Du eine Idee.

Vielen Dank,twt131
[Wileyfox Swift] johnaaronrose:
German

[MENTION=1407986]twt[/MENTION] 131 I do not know German. Please post in English.
[Wileyfox Swift] twt131:
Hello,first thank you for your good guide.It worked properly for me.I installed TWRP and a custom rom,-but then,when I tried to reboot,it alaways stopps in the fastboot modus.I reinstalled everything,but it is the same.Perhaps you can help me.

Thank you,twt131
[Wileyfox Swift] johnaaronrose:
The following web links give details on installing LineageOS which is the successor to Cyananogen and is based on Android Nougat 7.1.1. Please note the procedures will wipe your apps & associated data:

https://wiki.lineageos.org/devices/crackling/install Instructions state to use Volume Down & Power buttons (not Volume Up which did nothing on my Swift)

https://download.lineageos.org/crackling Use latest

https://www.androidfilehost.com/?fid=673368273298980888 To download Foxy kernel

https://wiki.lineageos.org/gapps.html Select LineageOS 71, Arm64, 7.1, Mini

I then powered up the phone, provided my gmail id etc & installed all my apps - if I remember correctly it took a few minutes for the first boot (subsequent boots take about a minute to fully finish). Rooting is done with Settings (no need to download any app). Phone is much improved: Wileyfox's provided Nougat update had messed up my phone e.g. Here We Go crashed, Camera didn't always work and had a few seconds delay. I had never been able to root my phone on either Wileyfox provided Marshmallow or Nougat. After installing my apps, I installed the Official TWRP app and did a backup recovery.

BTW I use Ubuntu on my PC, but I should imagine that everything will be Ok on Windows: I used https://xdaforums.com/showthread.php?t=2588979 to install adb & fastboot. Interestingly, lsusb shows the phone (when plugged in by usb to my PC) with a blank name (unlike all my other usb devices) so that "adb devices" never shows the phone.
[Wileyfox Swift] johnaaronrose:
I've just installed an update (new version ?) of some part of LineageOS as a result of acceding to a notification. I was first notified about this update approx a month ago, but it hung on the update. This update screws the phone up and leaves it in 'Recovery' mode. To correct this reinstall the Foxy kernel from https://www.androidfilehost.com/?fid=673368273298980888
[Wileyfox Swift] twt131:
support

Hello johnaaronrose,-thank you for your continuously support! Best wishes from Germany,twt131
[Wileyfox Swift] DarkStar66601:
Hmm.... Whot install twrp?I'm use adb "Unlock bootloadera"is ok delete data,and user command "fastboot flash *.img",a have info "whaite for devce"?. Whot wrong?Sorry is my bad English.

Wysłane z mojego Wileyfox Swift przy użyciu Tapatalka
[Wileyfox Swift] whowantstwoknow:
Hi all,

I'd like to move to a custom ROM, but I'd like to root the wileyfox ROM 1st and take a backup of it without losing any user data. Is this possible?. I'd really like to go back to the original setup if I run into any problems along the way?

Thanks

W.
[Wileyfox Swift] Cappucinto:
Hey everyone,

I bought a Swift on Amazon and wanted to unlock the bootloader, install TWRP and a Custom ROM.

Unlocking the bootloader was working fine but the phone won't boot anymore after trying to install TWRP. It's still showing the "Wileyfox" Logo with "powered by Android".

Flashing TWRP did not work, I used the Boot version and everytime I try to install a custom Rom the installation is fine but the phone did still not boot.

The phone has Cyanogen13 installed when I did this.

Can anyone help me please?

Thank You!
[Wileyfox Swift] r25txe:
Can you clarify what you mean by "I used the Boot version"?

Did you install TWRP to the bootloader?

---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------

If you are still bootloader locked unlocking will wipe your /data (and maybe internal media, too)

You could try to save your /data using ADB or use Helium backup Pro by Koush which uses your PC for a no-root backup.

A lot of apps have their own backup/export/sync solution and don't forget you can leverage Google backup for your Google settings and many apps.
[Wileyfox Swift] Cappucinto:
[MENTION=3748537]r25txe[/MENTION]: Thank You. The Problem for me was the TWRP I was using. Everything exept TWRP 3.0.1 did not work!

Now I'm happy with my Swift :)
[Wileyfox Swift] DarkStar66601:
Please help!

Who past this command?

fastboot oem unlock

fastboot -i 0x2970 oem unlock-go

fastboot oem unlock-go

1.I'm insaid command ADB,first command past[Enter]

2.In fone info Yes/No,Yes fone restart deleting data.End operation choice language

3.Pleasa (Screen Shoot)in ADB terminal,who past next command

Please help I'm new user Android,I'm Big Problem...

Update:

Keine Problem....Read this is...

https://android-hubo.de/thread/4509-bootloader-crackling-bootloader-unlock/

Wysłane z mojego Wileyfox Swift przy użyciu Tapatalka
[Wileyfox Swift] whowantstwoknow:
Phone wont reboot

Hi All,

I've unlocked the bootloader, installed TWRP, and installed the custom ROM, but the phone wont reboot, stuck in:

[IMG="Stuck here"]https://preview.ibb.co/mf3yNG/phone.png[/IMG]

Any help would be much appreciated..

Thanks

W.
[Wileyfox Swift] Cappucinto:
Hey whowantstoknow,

- download TWRP 3.1.1.0.img. Put one copy on your desktop-computer and one copy to your sd-card which you put in to your phone.

- try to boot twrp (from windows-desktop): fastboot boot <name_and_path_of_recovery>.img

- make a factory reset, turn down phone, go into bootloader again and then again: fastboot boot <name_and_path_of_recovery>.img

- in twrp: sideload the rom you want to install: adb sideload "C:\path_to_rom"

- do the same with gapps

- DO NOT REBOOT

- in twrp go to install and then, "install from image"

- install the twrp.img you had put to your sd-card before

- clean cache & dalvik

This worked for me, when I got massive problems with installing twrp and a custom rom
[Wileyfox Swift] whowantstwoknow:
[MENTION=7489663]Cappucinto[/MENTION] Thanks for that, think I got to follow all your steps but when I go to reboot, end up in the same place :crying:

Before that screen displays (from my original reply), I see flash up the message "wileyfox fastboot mode", any help?

Also I was going to say when in recovery mode, that the boot folder on the internal storage was empty but since the last effort, all I'm seeing on the internal storage from my windows box is these directories:

Open-GApps

TWRP

Can I/should I recreate the system partition perhaps.

Thanks

W.

PS: sorry when I use the TWRP file manager I see a filesystem with the empty boot folder. The above dirs are in the /sdcard folder
[Wileyfox Swift] whowantstwoknow:
I'm trying to install lineageos 15 onto the swift, but searching online I see many others installing 14.1 seem to have had this constant boot problem too...