[Wileyfox Swift 2 Guides, News, & Discussion] der_dkw:
Hi!

As Wileyfox issued another OTA today and the last time I had a hard time to find the proper information, I thought I'd start a thread that contains the update information and links for ALL OTAs in one place right at the start.

But first of all: This would not be possible without linuxct and mdosch who delivered this information in a combined effort. I added only a few things, like the new updates and put everything in one place.

1. The official update links from Wileyfox (partially from here, here and myself):

TOS118C (Recovery Image)

TOS163B (Recovery Image) Deleted by Wileyfox

TOS208G (Recovery Image) Deleted by Wileyfox

TOS249H (Recovery Image)

TOS319I (Recovery Image) Deleted by Wileyfox

TOS373J missing

UOS224B missing

UOS273C (Recovery Image)

TOS118C (Fastboot Image) Deleted by Wileyfox

TOS163B (Fastboot Image) Deleted by Wileyfox

TOS208G (Fastboot Image) Deleted by Wileyfox

TOS249H (Fastboot Image)

TOS319I (Fastboot Image)

TOS373J (Fastboot Image)

UOS224B missing

UOS273C missing

TOS089A to TOS118C (OTA Update)

TOS118C to TOS163B (OTA Update)

TOS163B to TOS208G (OTA Update)

TOS208G to TOS249H (OTA Update)

TOS249H to TOS319I (OTA Update)

TOS319I to TOS373J (OTA Update)

TOS373J to UOS224B (OTA Update to OREO 1)

UOS224B to UOS273C (OTA Update)

TOS373J to UOS273C (OTA Update to OREO 2)

2. The instructions how to make the OTA links work (taken from here):

If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible. Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string. Now here's the thing: if you want to switch the UA you'll need an extension to do so. linuxct has used this one and on Firefox I used this one. As soon as it's installed, go to the Options of the extension and add it like here:

WILEYFOX rsotaua 1.0 Chrome Replace WF

Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.

As I just found out: The "User Agent Switcher" for Chrome works just as fine.

3. The instructions how to update a rooted phone (taken from here):

I'll write down what I did to get it finally work, but be aware you might brick your phone. I did this with Windows 7 and 10 successfully with fastboot and adb installed.

3.1. Download and unzip the fastboot image from point 1. Then switch to fastboot mode and flash boot, recovery and system.

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img

3.2. Boot to stock recovery and choose "apply update from adb". Then sideload the update.

adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip

This is, of course, an EXAMPLE! You have to put in the name of the actual update you want to do.

3.3. After successful install wipe cache and dalvik/arts cache and reboot to system. If you have issues with "dm verity" do it with the following command (I myself didn't need to do it):

adb reboot "dm-verity enforcing"

3.4. When the update is configured let the phone switched on for a while (I don't know why, but mdosch ended in a bootloop and had to start again when he instantly rebooted, I myself didn't need to wait). Here you can already put the SuperUser ZIP-file onto your phone via USB (or do it later via sideload).

3.5. Then boot to bootloader and BOOT (not flash) TWRP

fastboot boot twrp-3.1.1-0-marmite.img

3.6. If you have the SuperUser ZIP-file already on the phone flash it, otherwise go to "ADB -> Sideload" and install there

adb sideload superuser.zip

3.7. Wipe cache and dalvik/arts cache and finally reboot. Again, if you have issues with "dm verity" do it with the following command (I myself didn't need to do it)::

adb reboot "dm-verity enforcing"

This is how it worked for me in Windows 7 and 10 on my Wileyfox Swift 2 Plus. Neither did I brick my phone, nor did I loose ANY(!) data, neither from storage nor from any app. But as I don't know what you did with yours I won't issue any warranties here...

BTW: If you ever wondered, when you do the OTA the phone saves the zip here: data/data/com.android.providers.downloads/cache

So, linuxct and mdosch thank you very much again and I hope you don't mind about what I did with your input. :fingers-crossed:

And also thanks to image45 and DIMICH666 for getting hold of some more of the image links.