[Wileyfox Storm] Blinkin89:
Hi all,

I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.

After updating I followed this guide: http://xdaforums.com/wileyfox-storm/general/root-wileyfox-storm-t3250992

And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper

Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.

I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).

When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:

<bootloader> Device already : unlocked !

OKAY [ 0.000s]

finished. total time : 0.000s

Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...

I continued to start rooting it, but not before testing if I could still boot but everything was fine.

I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.

I checked if everything still was ok and it was. I could boot and everything.

So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.

I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.

I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.

This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.

I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.

I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).

So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.

I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.

And now the rom is in a boot loop.

I already tried a full factory reset but it's still boot looping.

I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.

The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".

But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?

I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..

Thank you in advance.

Edit: I've found my solution and had to change something.

You can read it here starting from Edit 2. :)

http://xdaforums.com/showpost.php?p=68632922&postcount=84