[marmite] Official Wileyfox Swift 2+ Updates (also for root) - Repository

[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.

 

[bjlabuk]

Thanks, wish I had found this 2 hours earlier! I had been downloading the OTA update but it was failing to install. Spent ages searching my phone for the location of the download without success. Eventually connected my phone to my laptop and did 'adb logcat' - found the URL of the OTA File download "http:\/\/ota-files.wf.bsp.ninja\/marmite\/wf-marmite-8eec3af77b-to-0fcf4099d0-signed.zip". Changed 'User Agent' as described, put the URL in the address bar and hit enter and hey presto! Good to have a repository to refer to.

 

[Jack3volution]

Hi
I'm already on TOS163B. Can I just sideload the TOS208G OTA zip? Without reflashing the boot, recovery and system images from TOS163B?

The images from TOS208G are not available.?

 

[H2Oxide]

Thanks for this.

I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?

(... I dream about Lineage 14.1)

 

[image45]

Thanks for this.

(... I dream about Lineage 14.1)

We all do, I tried an unofficial build however no WiFi yet :crying:

Even with an official build we would still have the unlocked bootloader warning screen and the dm-verity screen that threatens to switch your phone off in 30 seconds if power not pressed. I am sure it only gave you 5 seconds then just continue to boot when running on the Cyanogen ROMs

I am sure there is some ADB the resolve this for the oneplusone phones.

After initial boot the ROM got stuck on the white splash screen. After I installed Magisk via TWRP flashable zip it worked so must need dm-verity switch off.

 

[quixoticduck]

I never updated back at the end of 2016 because I was unsure if it was a good idea but now I've become annoyed by it constantly asking me to (OTA UK). Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.

 

[image45]

Should I update to cm-marmite 460.6 MB like it's asking me to? And then I suppose it will pick up and ask me to install the updates since? Thanks.

It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.

I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.

However like I said at start of post what do you need from your phone/ android version?

 

[quixoticduck]

It needs to be what you want, I flashed the cm-13.1.4-ZNH2KAS5RM-marmite-signed-5175bd793a.zip then removed the cm updater to stop it prompting me to move to the next update as it would eventually have you on current build if you accept all the updates.

I flashed cm-13.1.4 as I found it the most stable Cyanogen Marshmallow 6.0.1 ROM and I wanted xposed framework.

Thanks, I see what you mean, about it being personal preference. The last couple years I've stepped away from rooting and flashing roms, so right now I suppose all I really want is a stable safe version. Back in 2016 I remember people being worried about the OTA update released right after Cyanogenmod's end, with people thinking the new update might be suspicious (why I never updated, and then stopped following things). So if it turned out that the OTA update was fine then I suppose the easiest and safest way to stop it bugging me about the update might just be to update xD as long as there's no risks (besides the basic risk that any update could bring). Probably makes it easier for any further updates too if any appear.

I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.

 

[image45]

I hadn't heard of the xposed framework, sounds interesting, I'll look into that just in case I want to use it.

You need an unlocked bootloader and custom recovery to install xposed framework. However I can jump between any of the Swift 2 ROMs when ever I wish of course.

 

[angstdasein]

Currently on the update right before that one, with TWRP and Magisk installed. I found the zip as instructed. Has anybody had success with Flashfire for a small OTA update like this or do you absolutely have to use adb sideload?

 

[bjlabuk]

Don't know whether I can post links to other sites but there are instruction on how to update to 7.1.2 using the OTA file for both rooted and non-rooted devices at

http://www.stechguide.com/install-android-7-1-2-nougat-on-wileyfox-swift-2/

 

[H2Oxide]

Thanks for this.

I managed to grab the TOD208G OTA. Flashing the zip in TWRP did not work though. I got an unexpected fingerprint error (6.0.1 instead of 7.1.2). I flashed the last available debloater on TOS163B (which worked fine), but that probably has got me in trouble now. Is there any way to fix this easily, without having to root and remove all the debloat stuff manually?

Any thoughts on this? Can I force a sideload or would that be unwise...

 

[mdosch]

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:

Sure that's fine.
I really appreciate you collected all the information and created this overview.

 

[Jack3volution]

Well I finally managed to try the adb sideload and this is what I got.

What's wrong here?

I'm using TOS163B (7.1.2) so I don't know why it says I have 6.0.1 test keys. I'm trying to sideload TOS208G

Any help is much appreciated

 

[mdosch]

What's wrong here?

You are using TWRP not stock recovery.

The OTA zips check your device for not being altered (like rooting or using custom recovery) this is why you have to go to a plain stock rom while flashing boot, recovery and system from the fastboot image (not the complete image as it will erase your data as well I assume).

After you have done this boot to stock recovery and adb sideload the first OTA zip then reboot and so on until you are on the latest.

Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).

 

[Jack3volution]

Thanks! my mistake. Yeah I still have stock recovery
Cheers

 

[image45]

Then you can boot twrp (I recommend booting instead of flashing as for me it complained about my device being altered when I flashed twrp) and root again (as root was lost during this update process).

What's the actual different between booting TWRP and flashing please?

 

[mdosch]

What's the actual different between booting TWRP and flashing please?

Booting means you boot TWRP temporarily without replacing your stock recovery. Flashing means you replace the stock recovery with TWRP.

 

[Jack3volution]

You are using TWRP not stock recovery.

Hmm it didn't work in stock recovery either

 

[mdosch]

Hmm it didn't work in stock recovery either

Did you apply the OTA zips in the correct order?
Did you alter your devices in any way like rooting or installing magisk?

You are on TOS163B you said. Did you start your device before booting to recovery? For me after sideloading the TOS163B, sideloading of TOS208G failed when I tried to install it instantly so I cleared the cache/dalvik cache booted to Android, then rebooted to (stock) recovery again and successfully sideloaded TOS208G.