yashsingh1/xdaforums huggingface dataset:
[Wileyfox Storm] nsam1:
Hi Bobs...

Yes, the back light looks like its a hardware issue I guess. Mine still flashes occasionally, but is very rarely on as usual.

I have thought about trying to get the phone replaced because of this, but then I would have to put the stock ROM back on, and re-lock the bootloader (if that's possible)? I'm just not sure it is worth it for something that isn't really that important.

I am noticing more issues to do with sound though - some times when I am called, the ringtone will just suddenly stop, even though the phone is still ringing. This is a pain because it means I've missed a few calls.

I hope today I will update to the latest nightly kipper build - maybe these issues might be addressed there.

Cheers guys,

Nsam
[Wileyfox Storm] RastHacker:
I'm on stock and no backlight but no issues
[Wileyfox Storm] ijaz1976:
Wileyfox storm custom recovery

Thanks for custom recovery.

Method worked on my Wileyfox Storm.

Good work. Keep it up :good:
[Wileyfox Storm] RastHacker:
Thks
[Wileyfox Storm] Arslan Dhillo:
Hi

My wileyfox back button light is blinking and sometime Off please guide how to fix it
[Wileyfox Storm] RastHacker:
There is no fix my button has stopped working at 29/11 and never back... Sorry
[Wileyfox Storm] syedshakeeb:
heating issue

hello guys i am using a brand new wileyfox storm phone and on usage it gets heated up to 45 c is a there a way to solve this problem.
[Wileyfox Storm] zaccheo:
Hlo guys, I'm zaccheo how to root a mobile I'm using moto g2
[Wileyfox Storm] RastHacker:
Search on internet "how to root moto g2" and follow tutorial
[Wileyfox Storm] FearlessCoconut:
I have a problem, when I flash the UPDATE-SuperSU-v2.46-signed zip file i get an error saying signature verification failed. Any help?
[Wileyfox Storm] RastHacker:
Try to flash nightly recovery via fastboot and re flash super su

Or my port and flash super su
[Wileyfox Storm] FearlessCoconut:
Did not work when I flash do I have to do the oem reset thing again?
[Wileyfox Storm] RastHacker:
Oem unlock
[Wileyfox Storm] FearlessCoconut:
Got it. Obliviously I knew that ??
[Wileyfox Storm] RastHacker:
Okay ^^
[Wileyfox Storm] FearlessCoconut:
How does this one work? Could you provide a guide because I've tried all I can and followed this guide word for word and I still do not have root access
[Wileyfox Storm] steveharman:
This worked perfectly, many thanks.

On a related note I'm interested in experimenting with "Project dark Booster" (http://xdaforums.com/android/software-hacking/tweak-arkaynine-boost-script-v3-0-t3120404). But flashing it with the CM Recovery linked to in this thread always complains about being unable to verify the signature.

That wouldn't normally be an issue, just switch off signature verification... except the CM Recovery used as part of rooting doesn't seem to have that option?

Is there a recovery for the WF Storm which does allow signature verification to be skipped?

Thanks again - great work.

Steve
[Wileyfox Storm] luckyna1:
--> go to Developer options, check advance reboot, OEM unlocking, and android debugging

--> reboot ur phone to bootloader (fastboot mode)

--> open CMD, type fastboot devices -> type fastboot oem unlock -> type fastboot reboot

--> go to Developer options. uncheck update cyanogen recovery

--> reboot ur phone to bootloader (fastboot mode)

--> open CMD, type fastboot devices -> type fastboot flash recovery (drag ur kipper-recovery.img or nighty build recovery file here)

--> after flashing finish, remove usb cable from ur phone and immediately hold volume down + power (recovery mode)

--> on recovery mode go to apply update -> choose from internal storage (or micro sd, for me i put supersu file in micro sd)

--> flash supersu

--> finish.

( this is the steps i use to root my wileyfox storm, after i've failed so many time )

Big Thanks to bobslesbricoleurs & XDA-Dev for giving us an assist, sorry for my bad english
[Wileyfox Storm] backfire_12:
Have you guys tried cm-13.0-20160121-NIGHTLY-kipper yet? I having problem with the baseband being "unknown" and IMEI getting lost. I tried flashing back to stock then Cyanogenmod 12.1 again, I hope baseband get fixed on next nightly. Apart from the baseband CM13 seems promising, thanks guys for porting this dev to CM13.
[Wileyfox Storm] RastHacker:
No prob good tutorial ;D
[Wileyfox Storm] FearlessCoconut:
I'll try this one now
[Wileyfox Storm] FearlessCoconut:
Doesn't work. Keeps saying installation aborted
[Wileyfox Storm] luckyna1:
try wipe data/factory reset and wipe cache partition before applying update, don't wipe media

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

seem like they fixed it already because last night i install cm-13.0-20160125-nightly, and both baseband and imei are present, i want to upload the screenshot here but unfortunately xda won't let me upload picture from outside link because i'm still new here
[Wileyfox Storm] backfire_12:
Baseband seems to have been fixed since cm-13.0-20160122-NIGHTLY-kipper, but then another problem, sensors are getting offline after standby, I'm flashing cm-13.0-20160127-NIGHTLY-kipper as of this writing hopefully has the fix. I tried CM12.1 (mod) and stock are not having this issue, might be something with the Android Dose?...
[Wileyfox Storm] backfire_12:
cm-13.0-20160127-NIGHTLY-kipper has the same problem, I'm reverting back to CM-12.1-20160120-nightly-kipper. Losing vital sensors (i.e. proximity sensor lags during call) is just too much for a daily driver to missed. We'll let you guys know what's today's has to offer.
[Wileyfox Storm] syedshakeeb:
Stock firmware

hello guys can you provide me a link to flash the stock rom for my Wiley fox storm thanks in advance
[Wileyfox Storm] RastHacker:
Stock rom from cyanogen os official site : http://builds.cyngn.com/factory/kipper/cm-12.1-YOG7DAS2FI-kipper-signed-9b353dd59a.zip
[Wileyfox Storm] syedshakeeb:
Can you also provide instructions for flashing this on wileyfox storm
[Wileyfox Storm] RastHacker:
Just have to flash stock recovery or cm nightly recovery and flash this as zip
[Wileyfox Storm] syedshakeeb:
Guys are there any ROMs available to the wileyfox storm if so please post link to download them thanks in advance.
[Wileyfox Storm] backfire_12:
1. Download adb and fastboot

2. Download the fastboot version of the stock firmware

3. Turn off your phone, then boot to fastboot (press power and vol +, let go after the vibrate)

4. Follow extract then follow this commands:

fastboot flash aboot emmc_appsboot.mbn

fastboot flash abootbak emmc_appsboot.mbn

fastboot flash sbl1 sbl1.mbn

fastboot flash sbllbak sbl1.mbn

fastboot flash tz tz.mbn

fastboot flash tzbak tz.mbn

fastboot flash hyp hyp.mbn

fastboot flash hypbak hyp.mbn

fastboot flash rpm rpm.mbn

fastboot flash rpmbak rpm.mbn

fastboot flash modem NON-HLOS.bin

fastboot flash cache cache img

fastboot erase splash

fastboot flash splash splash.img

fastboot flash system system.img

fastboot flash recovery recovery.img

fastboot flash userdata userdata.img (This command completely clears the internal memory of the phone)

fastboot flash boot boot.img
[Wileyfox Storm] RastHacker:
What??? It's a flashable zip...
[Wileyfox Storm] luckyna1:
this what i do when i go back to stock rom

1. download fastboot_adb (1.0.32) http://xdaforums.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160 extract it to fastboot_adb

2. download stock rom for wileyfox storm (3 files, 2 zip and 1 img) and put cm-12.1-YOG7DAS2FI-kipper-signed-9b353dd59a.zip in the same fastboot_adb 1.0.32 file folder

3. reboot to bootloader (fastboot mode) and connect your wileyfox storm to pc/laptop

4. open CMD and type fastboot devices (just to make sure that ur phone detected)

5. on CMD type fastboot flash recovery C:\\cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img (or u can drag cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img file here)

6. on CMD type fastboot reboot, remove usb cable and go to recovey mode by holding volume down + power

7. on recovery mode wipe data/factory reset and wipe cache partition, and then go to apply update , select apply from adb

8. connect your phone to pc/laptop, open fastboot_adb 1.0.32 folder and press shift+right click select open command windows here

9. type on CMD adb devices (just to make sure ur pc can detect ur phone)

10. type adb sideload cm-12.1-YOG7DAS2FI-kipper-signed-9b353dd59a.zip ( for me i always drag the file when i do this so i don't have to type or searching where the location of the file) wait till finish, after finish reboot your phone

( i use this method every time when i wanna go back to stock rom and always succeed, i have done this three times already)
[Wileyfox Storm] RastHacker:
Noooo! Download cm-12.1 ROM

Copy in your phone as ZIP

Reboot recovery and wipe and flash
[Wileyfox Storm] syedshakeeb:
Is there any other way of flashing wileyfox storm other than using recovery.
[Wileyfox Storm] RastHacker:
Why ? It's the simplest
[Wileyfox Storm] syedshakeeb:
In case installing custom recovery failed then it would be a big mess out that's why.
[Wileyfox Storm] RastHacker:
Just flash stock recovery and flash the rom
[Wileyfox Storm] Awt67:
Followed the instructions unlocked oem but can't imstall SU signed or unsigned keep getting error message when i try ? any help please
[Wileyfox Storm] RastHacker:
you've not flashed recovery read carefully all steps
[Wileyfox Storm] Awt67:
Sorry should of said SU fails to install when I try to flash it in recovery, my bad
[Wileyfox Storm] RastHacker:
Yes but it is because you're un stock recovery so flash my recovery
[Wileyfox Storm] Awt67:
I have used your recovery
[Wileyfox Storm] RastHacker:
the write are little in recovery or normal
[Wileyfox Storm] image45:
Yes it's a real pain, it took me around 7 goes to get to the custom recovery, since the phone kept restoring the stock one. However once I had root and latest version of busy box installed I could use flash tools to change the recovery and this time it was not replaced on boot, not sure why!
[Wileyfox Storm] traxo:
I think I know why. When I tried flashing a new recovery, it always said "OKAY", but the new recovery wasn't actually flashed. After some searching I found some information in the CM wiki. You have to use fastboot with the vendor ID option like

fastboot -i 0x2970 flash recovery recovery.img

That did the trick for me. Not sure why none of the posts here on XDA mentions this. Maybe it's only necessary on a newer version of the phone.
[Wileyfox Storm] image45:
Interesting, I actually used the full vendor ID while unlocking the bootloader, however not while flashing the replacement CM recovery. After rooting, installing supersu pro and busybox stericson I used flashify to install twrp recovery and this has stayed as phones recovery. Rashr also made a permanent install into the storms recovery partition, again using a recovery.img on the internal memory.
[Wileyfox Storm] Fuzzra:
I suspect there's a crafty little script lurking somewhere in the image for the system partition - something dreadful happened to Play Services on mine during a routine update and the simplest (after fixing and re-breaking repeatedly to test) thing to do was to remove all GAPPS and reflash system while leaving everything else intact. Imagine my surprise when I no longer had TWRP...

The failsafe is to use the fastboot boot option to boot a custom recovery and install SuperSu without flashing. That way you can get yourself rooted without having to rely on the recovery taking and can use Flashify to get it in place even if you're at the pub* while finishing a fix.

* Voice of (pint of) bitter experience.
[Wileyfox Storm] Y0zcjan:
I had the same issue so i tried to flash the recovery using the vendor ID but it when i do that it gets stuck at:

< waiting for any device >
[Wileyfox Storm] image45:
You need to update your fastboot drivers for the device. I had to switch Eset security off for 10 minutes to allow Windows to find and update the device drivers for phone.
[Wileyfox Storm] BrainDad:
Confirmed

Thanks to Neon. Process is confirmed. Works great. Thanks!
[Wileyfox Storm] saikoa7a8a:
:angel::angel::angel::angel::angel:

hi plz i need video how do this root and recovery my phone wileyfox storm
[Wileyfox Storm] JulianVlassie:
Tried everything but stock recovery seems to overwrite the custom recovery every time I boot into recovery, so I get an error while flashing any zip (signature verification failed). How can I solve this? Read someting about changing recovery file name but phone is not rooted yet. Please help.
[Wileyfox Storm] FluffyTwit:
Hey, I've rooted my S6 before so decided to have a crack with my WileyFox Storm. I have got to CyanogenMod's 'Fastboot Mode' (power + volume up) but don't knwo where to go from here. I am a bit confused as to where you "Type "fastboot devices" and if it appear type "fastboot oem unlock" and press y".

Any help would be much appreciated. I tried on command prompt on my pc (which has Android SDK) but 'fastboot' is not a command.

Thanks :))
[Wileyfox Storm] RastHacker:
Install ADB and fastboot, open terminal and type fastboot devices.

You'll see a device if ok you continue else will not work.

After you type fastboot oem unlock an he will ask you yes or no, so you type y for yes en it's unlocked ;D
[Wileyfox Storm] FluffyTwit:
The terminal in ADB? :)

---------- Post added at 09:21 PM ---------- Previous post was at 09:09 PM ----------

Is xposed simple to install on the Storm. I understand you need to flash the zip; but my previous phone was an S6, so I had to use a custom framework. So:

- Can I use it with the Storm's stock OS?

- Is it the official xposed framework that I need to flash?

Thanks :)
[Wileyfox Storm] RastHacker:
You need to use xposed arm64 sdk22(5.1.1) or sdk23(6.0), stock ROM is cyanogen os so it's okay.

You don't know what is ADB?
[Wileyfox Storm] FluffyTwit:
I kind of know what it is but I have never had to use it :)

Anyway, thanks for your help! :)

---------- Post added at 01:26 PM ---------- Previous post was at 01:26 PM ----------

I kind of know what it is but I have never had to use it :)

Anyway, thanks for your help! :)
[Wileyfox Storm] FluffyTwit:
Help! My phone isn't booting!!!

I followed all of your steps and my phone is now taking ages to boot.

I did side track a bit from your steps though because I had to sideload SuperSU using ADB instead of from my phone, because no files appeared in my phone in the recovery. I now don't know what happened because my phone is stuck on the booting screen. I have tried rebooting and still to no avail.

I'm really worried because this is a new phone and my parents would murder me if I broke it. I have made a backup but not a nandroid backup (because I assumed you can't do one until your device is rooted).

What can I do, please help me :(
[Wileyfox Storm] RastHacker:
Flash stock boot.img from stock rom zip, reboot
[Wileyfox Storm] FluffyTwit:
I flashed the whole .zip file because I saw a tutorial on some website (this was before you replied). It fixed my phone but I still want to root it xD.

Maybe Ill give it a few months before I try it again. At least I have learnt my lesson.

Thanks for all your replies :)
[Wileyfox Storm] Blinkin89:
Hello, I was wondering if this still worked on the most recent official COS 13. You never know with recoveries.

Would anyone recommend using root with the official COS? Or should I flash CM? I have no idea if FOTA updates work when rooted, so any info about it is highly appreciated (I've done some reading the past 2 days but most info seems outdated or incomplete).

Edit: I'm an idiot. I tried following your steps and ended with a similar problem as FluffyTwit: boot looping. I should have known. :(

Could you be a bit more specific about how to flash the boot.img and where to get it from? I do have the zips from https://cyngn.com/support, but I'd like to have the specific instructions on how to solve this.

I'm afraid I'll make a typo or look up the wrong information and end in bricking the whole device.

Thank you in advance.

Edit 2: Seems like I already had read the solution but forgot about it. For anyone having the same problem and reading the solution is already mentioned here: http://xdaforums.com/showpost.php?p=65142058&postcount=55

Edit 3: So I tried the above mentioned solution with the new COS img and zip files and got to a new problem. I could flash cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img as a recovery but I couldn't boot into the recovery. It just kept booting into the ROM. So I tried the exact same img as mentioned in the tutorial which is cm-12.1-YOG7DAS2FI-kipper-boot-debuggable-a7322d8c3a.img but that gave me the same result. Booting into recovery didn't worked. So I flashed the Cyanogen recovery I had again with fastboot and I could boot into that one. Very weird...

I've followed all steps with this unofficial recovery and flashing the original ROM worked through ADB. On rebooting to ROM loading took a very very long time... I was ****ting my pants that it was still boot looping so I left it alone and walked away. After what felt like 10 minutes I got back expecting to see it still booting but it wasn't! It was busy building cache and it just literally finished. :D

Thanks!!! I got my Storm back up and running! :D
[Wileyfox Storm] FluffyTwit:
Hello again, apologies if my problems are p**sing some of you guys off now xD

So, my WileyFox Storm runs CyanogenOS 13.1.2-ZNH2KAS4YE-kipper and I want to root it. Previous attempts have been unsuccessful and I do not know why.

I have already unlocked the bootloader (I did that months ago in my previous attempts) and have downloaded Minimal ADB & Fastboot onto my PC. I have also enabled Android Debugging and Allow OEM Unlock in developer options on my phone.

I then reboot to bootloader and do "fastboot devices" if it appears type "fastboot flash recovery C:\..\kipper-custom-recovery.img" without out the quotes. All of the commands work with success.

I then reboot the phone to allow me to transfer the SuperSU .zip onto it. This is where it might have gone wrong. You see, my phone has an SD card, but it is formatted to my phone, to allow me to install apps onto it. So I cannot move the SuperSU "onto my SD card" because the internal storage is recognised as the same as the SD card storage.

So when it comes to rebooting into the recovery, my phone cannot find the file. This led me to sideload the SuperSU on instead from my computer (after wiping cache). This is where it went wrong multiple times, because when I rebooted, the phone stayed on the booting up screen for 20+ minutes. I tried restarting etc. but to no avail. Finally, I decided enough was enough, and just reinstalled the whole OS, which fixed it but meant it had no root.

So, how would I fix it? Should I try it with an unformatted SD card (I.e. one that is separate from the phone's internal storage)?

Cheers in advance :))
[Wileyfox Storm] image45:
You need to put UPDATE-SuperSU-v2.46.zip into the phones internal storage. When you go to recovery it should find this OK. Link below.

https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1

Are you not using TWRP recovery? If not why? Link below.

https://www.androidfilehost.com/?fid=24591000424963153
[Wileyfox Storm] FluffyTwit:
Hello,

Thanks for the answer but as it just so happens I managed to sort it out yesterday. I installed the Cyanogen custom recovery (not TWRP) then just used WinDroid Toolkit to sideload the latest version of SuperSU on. I don't know why this worked when ADB didn't but who knows...

The reason I don't use TWRP is because the custom one for the Storm is what I used in my previous attempts at rooting (which failed), therefore I decided to try using this custom recovery.

Thanks :))

-Adam
[Wileyfox Storm] image45:
OK well done on resolve. Have you not thought of moving onto new lineages ROM on Android 7.1.1 at all? Comes with system root!

https://xdaforums.com/wileyfox-storm/development/rom-test-build-lineageos-14-1-t3528016
[Wileyfox Storm] nelBest:
Drivers search

Hi guys help a bro out, am looking for wileyfox storm drivers .

Please post the link for downloading :D
[Wileyfox Storm] ftabashir:
stop at boot animation after installing custom recovery

Hello

SHORT STORY:

my device don't boot into android (stops at boot animation)

i locked oem (mistakenlly) after installing custom recovery, so when i try to boot in recovery it says "unsigned boot image can't boot on locked device. oem unlock or flash sigend boot image."

i just need my stock cyanogen os recovery, but i cant find it.

"cyngn.com/support" gives 404 error.

"download.cyanogenmod.org" gives 503 error

can you give me stock recovery for kipper?

LONG STORY:

one of users named "miSAKe" said that: " The above recovery image worked for me using fastboot boot xxx thus leaving the stock recovery intact."

because i didnt want to erase my data, so i tried to run this command: fastboot boot kipper-custom-recovery.img

it works and in custom recovery i tried to flash SU. but it dosent work and when i try to reboot to android it stops at boot animation.

after that i tried to flash custom recovery using: fastboot flash recovery kipper-custom-recovery.img (without oem unlock, i forgot it)

and then try again to flash SU. again didn't work.

then i tried to oem unlock, but it said it already unlocked. i thought that if i lock and again unlock it, maybe work. so i locked oem and then i tried o unlock it again it says that: FAILED (remote: oem unlock is not allowed)

and now if i try to boot in recovery it says: "unsigned boot image can't boot on locked device. oem unlock or flash sigend boot image."

what can i do? I'm confused.
[Wileyfox Storm] RastHacker:
try to go developer option and on top of page there is "enabled" toggle, turn it off and on again, then retoggle OEM unlock.

Now try fastboot flash command, and if error again try reunlock bootloader. or relock and then unlock
[Wileyfox Storm] FluffyTwit:
I had a problem a couple of week backs where the OS isn't available (its because Cyanogen is no more :( ). Luckily, I had two full copies of CM13 (as flashable .zips) for kipper on my PC, one for fastbooting and the other normal. I don't think its the most up to date CM13 but I dont really care because I'm planning on upgrading to Lineage14 when Xposed Nougat is released.

If you need the copies I can send them to you (don't know if there's a limit to file size on PMs or something) or you should be able to find them somewhere online.

Good luck,

~ Adam

EDIT: I've had problems with the custom Cyanogen recovery before (it was probably my fault) so I just run kipper's custom TWRP with the latest version of SuperSU (v78 i think?).