Help me installing cm13. - Wileyfox Storm

Hi. Can someone write down below with all links and info how to install official cm13 nightly on our Storm?
btw recovery says this device is crackling, rom is for kipper.
AFAIK crackling is swift and kipper is storm.
Can someone Help me?

OK cm13 installed, but i have problem with issufient storage when trying to install g-apps or c-apps anybody help me?

And how to revert back to COS 12.1.1?

i have to say i have no idea xD. i recently droped my lg g3 in a bucket of water. got it out stripped it, and hopefully it be okay xD. but if not i been looking at a wileyfox
aaanyway, reverting back! (im guessing here) you have your self twrp? or something installed on the device in order to flash gapps. i cant say as i dont have a phone if TWRP is something installable on the phone. but i would have suggested making a backup before you flashed p: AAAAANNNYWAY!
i would suggest doing a factory reset, swipe to wipe , and then flashing Cos 12 and its respected files to go back.

Flash stock recovery or nightly cm12.1 recovery
Wipe and flash stock rom from cyangogen os support site

bobslesbricoleurs said:
Flash stock recovery or nightly cm12.1 recovery
Wipe and flash stock rom from cyangogen os support site
Click to expand...
Click to collapse
Have a look at:
http://forum.cyanogenmod.org/forum/1212-wileyfox-storm-kipper/

Use a smaller set of GAPPS. Mini or less. as long as you can get the store working you can install any missing ones you want.

Related

N910C Bootloop

I flashed CM ROM today to try and see what progress has been made. I decided to return to the stock ROM. Flashed the stock ROM and wiped everything except system partition. Rebooted the phone and it is resetting itself at the first logo now. The second stage of boot (animated logo) doesn't initiate.
Download and Recovery modes work. Flashing the stock firmware with both Odin and Smart Switch didn't fix the problem. I tried PIT file and NAND Erase with a no go. Any help would be appreciated.
Edit: After spending some time trying, I realized I can only boot CM. Maybe CM caused this problem or the Gapps package I have been using. I am not sure. I'll be happy if anyone can help me fix this problem.
just flash cm12.1 (clean install without gapps ) do not let device boot just flash and then flash any rom you like it (dirty flash )
sorry for bad english
osamaAlrogi said:
just flash cm12.1 (clean install without gapps ) do not let device boot just flash and then flash any rom you like it (dirty flash )
sorry for bad english
Click to expand...
Click to collapse
this doesnt work mate

Lg g2 black screen after flashing cm 13

Hi ,after installed in my d800 32 gig snapshot cm 13,the phone became with ablack screen, try to flash nigtly cm 13,same problem.only when i flash to cm 12.1 work ok
What shold i do? Also the device keeps makes random resets. Please help me
bennnnnn said:
Hi ,after installed in my d800 32 gig snapshot cm 13,the phone became with ablack screen, try to flash nigtly cm 13,same problem.only when i flash to cm 12.1 work ok
What shold i do? Also the device keeps makes random resets. Please help me
Click to expand...
Click to collapse
flash hibryd... http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
wipe again all wipes
flash in twrp/ go back to main menu reboot into recovery again to take effect of bootstacks.. once in recovvery again proceed to flash rom gapps.
hi - thanks a lot for your answer.
now I have cm 12.1 snapshot on my lg,
in the link it says that I need bump recovery?and karnels? how do I install it?and what are the steps please?
bennnnnn said:
hi - thanks a lot for your answer.
now I have cm 12.1 snapshot on my lg,
in the link it says that I need bump recovery?and karnels? how do I install it?and what are the steps please?
Click to expand...
Click to collapse
bumped recovery is blastagators thermal twrp. here
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
kernel?? rom has kernel..
sometimes when you flash and no boot you need the hybrid bootstacks..
in this process... flash recovery reboot into recovery..... then flash hybrids first link i gave you.. then go back to main menu reboot/ to recovery from recovery again to take effect. then once in recovery .. flash rom and gapps.

G900F Bricked after update: cm-14.1-20161219-NIGHTLY-klte.zip

Hello all.
I have a Galaxy S5 running cyanogen 13 ( cm-13.0-20161013-SNAPSHOT-ZNH5YAO21L-klte.zip ). Last night I updated it with the cyanogen tool, as usual, thinking that I was just getting a more updated version of cyanogen 13, but apparently I got it working with android 7.1.
As gapps were not working, I downloaded both 7.1 gapps, and cm-13 to try to install gapps or comeback to cm-13 if it did not work.
The problem is that I had no chance to test it. I rebooted the phone with the option "recovery reboot" and after it turned off it showed something like "no command", then it got to the first screen (recovey booting... in blue, samsung galaxy s5 white logo...) and freezed there.
I've tried every key combination and it does change nothing. I've read in another forum an user having the same issue so I advice you to not install this update. At least not from CM13. I will update when I get more details from the other users or if one of us success while trying to unbrick.
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
LGaljo said:
I suggest you to install twrp with Odin so you are sure that you have working recovery. Then backup what left of this not working ROM and download cm 13 and gapps for it. Then wipe system partition and install those two. By some chance you will end up with working ROM. If it works, I suggest you to backup all data with titanium backup and clean flash cm 13 to be sure that you got rid of all the issues... If cm 13 doesn't boot also wipe data and start on new.
I hope it helps you
Click to expand...
Click to collapse
Hello!
Thank you very much, as I found the problem was the recovery I've re installed TRWP. CM14 was replacing it each time I installed it by ODIN so i had to start it just directly after flashing it (without letting the phone boot) and i've installed last CM14 klte file and 7.1 GAPPs
Now all is working , I hope it can help others with the same problem
Thank you!

[GUIDE] How to get CM 14.1 working.

Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989
-Reserved-
Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings
If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!
kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.
Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.
shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...
Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!
Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

Can't get ANY Nougat rom working.

i'm on a g900f and every Nougat rom i've installed(RR, CM/LOS, CRDroid) , it just freezes and puts my into a bootloop. BUT, this only happens when i flash gApps (2/02/17 7.1.1 nano)
I'm now back on CM13 and i just hope Android 8 will work properly.
anyone know how to fix?
nialloshea said:
i'm on a g900f and every Nougat rom i've installed(RR, CM/LOS, CRDroid) , it just freezes and puts my into a bootloop. BUT, this only happens when i flash gApps (2/02/17 7.1.1 nano)
I'm now back on CM13 and i just hope Android 8 will work properly.
anyone know how to fix?
I had same issue took 2 days to discover gapps was doing it. Boot into recovery, wipe Data,System,Cache, Delvik Cache. Install whatever Version Nougat 7.1.1 rom. Install Mini_Dynamic_GApps-7.1.x-20170121.zip. (Find download link on xda or Google it.) Do factory reset and reboot. I never had any problems after that. Once i put all my apps back anf settings, it was like it never happened. Good luck.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
-Flash rom
-Flash latest opengapps
-Flash su if u need it
-Flash this fix ( https://www.androidfilehost.com/?w=files&flid=150763 )
-Done enjoy....
for the next lineage build all freezes in setup has been fixed
So if you cant wait for the next build just flash the fix file..
Flash img?
Hi
I am using custom roms since a while and I also got into this freezing problem. Now I see this .img here. Just that I don't do anything wrong. How to flash and .img? Need Odin or is it possible in recovery mode? Sorry for the numb question here but could not find an answer hot to do on my Galaxy S5

Categories

Resources