About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
Install via ClockworkMod (do not use ROMManager for initial install):
1.Make sure you're running a rooted device.
2.Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
3.Do a Nandroid backup!
4.WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
5.Install the ROM from internal sdcard using ClockworkMod Recovery.
6.Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
7.Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
8.Reboot
9.Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Seconding the question as well as noting that it also occurs with Arif-Ali's nightly compiles.
did you wipe cache and dalvik cache after flashing cm7?
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
No, you dont need.
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
I did. I tried "messing" with CWM any which way and even flashed a stock rom in odin (and appropriate CF root). Nothing short of flashing Siyah (and probably any other kernel that supports CM7 except the one in the update zip) lets CM7 boot.
Net.silb said:
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Click to expand...
Click to collapse
I fixed it.
This is how:
1. Make a CWM Backup.
2. Use Odin to flash I9100XXKI3, including the PIT (re-partition)
3. Flash this kernel (PDA section) and the old Bootloader (Bootloader section) with Odin.
4. Boot into CWM recovery and flash cm7+gapps.
5. Use Advance Restore in CWM to restore your /data partition if you want to.
I'm 90% certain that the problem was ICS's partition layout (PIT file).
Related
Hi,
Currently using latest firmware KI3 with root.
I'm able to use CWM, backup, install zips, everything.
However, if i install a ROM trough a ZIP, i get a boot loop.
Only way to get back the phone, it's to install via ODIN with latest KI3.
Even tried with Litening Rom, and got the boot loop.
Any ideas ?
I was very keen to return to CM7.
Tx in advance.
Did you exactly what's mentioned here?
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
Did you try flashing a old stock ROM like KH3, root it then try from this base?
I went from Villain ROM 2.3.5 to CyanogenMOD without any problems.
It's essential that you flash CyanogenMOD !TWICE! in a row when you're coming from a stock ROM.
Thanks.
Gonna check, as soon as i'm @ 127.0.0.1
Same behaviour, back to boot loop.
Tanx anyway!
I had a similar problem so here goes my help.
Cf root kernel uses a modified version of CWM that isn't compatible with CM7 or something like that. So what I did was flash this kernel http://forum.xda-developers.com/showthread.php?t=1118693. Get the kernel with CWM 5.x.y.z With that I got a compatible version of CWM and from there I flashed CM7. It is important that you do a full wipe, wipe cache, wipe dalvik cache, format \system, everything so you don't get any trouble. THen you flash the CM7 zip file, when tha t is done, flash the zip again for a second time (don't reboot just do it after the first flash). After that reboot. That worked for me at least.
A tip: If you can't reboot your phone and you have no ROM zip file to flash via CWM you can mount usb storage from CWM for putting the ROM in sd card and flash with CWM. That way you don't have to use ODIN to recover.
Tanx Tomas.
Tried with CWM 5.x.y.z and upon "WIPE" always got an error for mounting partitions.
Could't mount CACHE, SDCARD .....
Tx anyway.
Back to ODIN, back to stock 2.3.5
PS : I have to get a JIG to reset ...
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
i have the exact same problem!
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I tried and got the samething. I also tried a different cm nightly and got the same results.
InFa_ReD_1 said:
I tried and got the samething. I also tried a different cm nightly and got the same results.
Click to expand...
Click to collapse
me2 only stock roms work for me =(
I think there was an issue with the version of CWM used on the CF-roots since it's been modified by CF and because it's an older version.
After you've rooted with CF, try flashing a kernel on there with a newer version of CWM on there (I used codeworkx's kernel from the Cyanogenmod wiki I've attached below with CWM 4.0.1.4).
Once this kernel is on there, then try flashing the CM7 ROM as per this thread. I prefer flashing from recovery myself, but it's your call.
Make sure you flash it twice in a row if you're having issues.
The problem, as stated above is that cf root kernel installs a modified version of CWM that won't work with CM7. Another thing is you have to flash a stock KH3 because KI3 has the new bootloader (unless you flashed KI3 with the old bootloaders). Then, you have to flash the codeworkx kernel so you get a compatible version of CWM. Once in CWM clear data factory reset + clear cache partition + clear dalvik cache (from advanced).
THIS IS IMPORTANT: Flash the ROM from sd card and when finish do not reboot device, just flash it again without wiping anything in between, just 2 consecutives "install from sd card". When this is done you can reboot the system and then enter again to CWM to flash the google apps .zip file that you can download from the CM7 thread.
Hope this helped. When I flashed CM7 i had exactly the same problem and went back to stock cause it was a pain in the ass to flash it fr the first time. But once you get in CM7, everything becomes great and easy, and you can update the nighlies directly from ROM manager without doing any wiping. You just can't use ROM manager when getting to CM7 for the first time.
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
droidphile said:
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
Click to expand...
Click to collapse
Thanks. Can i flash the orginal CWM over top the CF CWM?
InFa_ReD_1 said:
Thanks. Can i flash the orginal CWM over top the CF CWM?
Click to expand...
Click to collapse
I did it and didn't have any problems, just follow the steps as I posted above.
tomascunill said:
I did it and didn't have any problems, just follow the steps as I posted above.
Click to expand...
Click to collapse
Great thanks for the help it worked I'm now running CM7. One thing though I can make calls but have lost my network connection. Can someone help me with this? Sorry for all the questions I'm new to the whole smartphone business. Thanks.
Ok all fixed up thanks for all your help.
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
SynGates said:
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
Click to expand...
Click to collapse
Follow this:
-boot to CWM recovery
-wipe data /factory reset
-wipe dalvik cache (under advanced)
-format /system (under mount and storage)
-flash ROM
-flash Gapps (for jelly bean)
-fix permissions
-reboot phone
Done
Swyped from my Samsung Galaxy SII
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
Nope
Swyped from my Samsung Galaxy SII
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
which kernel u were into while flashing the JB rom?
Use siyah or dorimanx kernel it works fine for me must be your kernel
Sun90 said:
which kernel u were into while flashing the JB rom?
Click to expand...
Click to collapse
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
SynGates said:
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
Click to expand...
Click to collapse
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Sun90 said:
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Click to expand...
Click to collapse
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
SynGates said:
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
Click to expand...
Click to collapse
Use a newer version of siyah or dorimanx, they should work fine
Sent from my GT-I9100 using xda app-developers app
I have tried three versions of syiah, including 4.1.4 but I will try dorimanx and report with the results.
edit: dorimax kernel is the same.
One thing I noticed tough is whenever I wipe dalvik cache the system reports "unknown volume for /ext-sd blablabla" - maybe this is connected to my problem?
I am at a complete stop...
No JB kernels seem to work whatsoever. Is there any wit to flash the bootloader? Or is that even possible?
I really would like to get JB working on my device.
There must be something about the previous state of my phone, some files or folders that are in the way or are missing or somewhat. Is there any way to completely reset the phone? Not just factory resetting it since that is not working.
edit: Progress! These are my steps:
- Downloaded fresh stock Samsung ROM and another version of CF-root.
- Flashed stock ROM and then CF-root kernel.
- Booted into recovery and did the whole wipe.
- Flashed .zip twice (don't know if that did the trick or what)
- Wipe dalvik cache and fix permissions.
After that the phone booted normally and I'm now running ResurrectionRemix with Android 4.1.1, hoping it wil be awesome as ****.
Hi, I'm getting stuck at the black screen just before the boot animation (the one that says "samsung galaxy SIII gt-i9300"), after flashing custom rom via CWM. Maybe I'm a complete noob but I think something is wrong in my phone.
I had installed MIUI official before, then removed it to get warranty back and sent phone to samsung service to fix the my broken simcard compartment.
After getting my phone back, I tried to install MIUI again and got stuck.
The strange thing is how fast ROM is installed in CWM, less than 10 seconds...
No error message and says install is complete
have retried 7 times now, using this:
- Odin 3.04
- CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=1957273)
- CF-Root 6.4 - SuperSU+CWM5.5+CWMManager (http://forum.xda-developers.com/showthread.php?t=1695238)
- ClockworkMod Touch 6.0.3.2 (http://forum.xda-developers.com/showthread.php?t=1719744)
- ClockworkMod 6.0.3.6 - Touch and Non-Touch (http://forum.xda-developers.com/showthread.php?t=2200501)
ROMs:
- MIUI Official 3.8.16
- MIUI Official 3.7.12
- CyanogenMod 9.1.0 (stable)
what I do:
- boot to bootloader
- flash CF root with Odin (Auto reboot and F.reset Time are checked)
- reboot, then shutdown
- boot to bootloader
- flash CWM with Odin (Auto reboot and F.reset Time are checked) also tried to install with ROM manager
- reboot, then shutdown
- boot to recovery
- wipe data/ factory
- wipe cache
- wipe dalvik
- install zip from sdcard (internal) <-- strange thing here is how fast it is installed, less than 10 seconds...
- wipe data/ factory, cache, dalvik again
- reboot
- got stuck.
- flash samsung stock ROM I9300UBALE6_I9300ZTOALE7_ZTO (brazilian 4.0.4, phone was in that version when installed MIUI first time)
Don't know what to do now, please help!
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
rootSU said:
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
Click to expand...
Click to collapse
yes, it boot with stock rom.
I just copy/paste files from windows, always done that, but now that you say, md5 is diferent...
I'll check stock ROM and file copy.
Thanks!
It was the file copy messing with the zip...
used adb push and all OK now!
Thanks again!
Hi guys,
I successfully followed the advice on this thread (http://forum.xda-developers.com/galaxy-s2/help/to-mod-s2-t3189884) and I have installed CM12.1 's nightly from 29/8.
I boot in once, no problem. But on the second boot the phone bricks. The only way I can get into the system again is to load Philz kernel again and reinstall. But after the second boot the phone bricks again.
Any ideas? It may be the nightly, but even updating to the latest (31/8) didn't fix this.
I can get the CM10.1 stable to work fine, but that drain my battery faster than I can charge it.
I'd like to use 12.1, though: am I just doing something wrong that causes the bricking?
thanks,
blahsum said:
Hi guys,
I successfully followed the advice on this thread (http://forum.xda-developers.com/galaxy-s2/help/to-mod-s2-t3189884) and I have installed CM12.1 's nightly from 29/8.
I boot in once, no problem. But on the second boot the phone bricks. The only way I can get into the system again is to load Philz kernel again and reinstall. But after the second boot the phone bricks again.
Any ideas? It may be the nightly, but even updating to the latest (31/8) didn't fix this.
I can get the CM10.1 stable to work fine, but that drain my battery faster than I can charge it.
I'd like to use 12.1, though: am I just doing something wrong that causes the bricking?
thanks,
Click to expand...
Click to collapse
Clean install the rom!!
1.At first Flash stock rom
2.flash philz kernel
3.Reboot to recovery
4.Wipe Cache Partition and Dalvik/ART Cache
5.Now click on Clean to Install New ROM
6.Install the rom
7.Reboot system
Don't forget to hit the thanks button
Sureshtuty said:
Clean install the rom!!
1.At first Flash stock rom
2.flash philz kernel
3.Reboot to recovery
4.Wipe Cache Partition and Dalvik/ART Cache
5.Now click on Clean to Install New ROM
6.Install the rom
7.Reboot system
Don't forget to hit the thanks button
Click to expand...
Click to collapse
When you say I should flash the rom, do you mean I should unzip the stock and push it with Heimdall/Odin?
blahsum said:
When you say I should flash the rom, do you mean I should unzip the stock and push it with Heimdall/Odin?
Click to expand...
Click to collapse
I mean before flashing any custom rom flash stock rom then flash that rom which u want.
1.download stock firmware flash it with odin
2.then flash philz kernel
3.Reboot to recovery
4.Wipe Cache Partition and Dalvik/ART Cache
5.Now click on Clean to Install New ROM
6.Install the rom
7.Reboot system
Don't forget to hit the thanks button
Excellent, thank you!
A few tips to anyone looking this up:
First, I used Heimdall - but apparently Odin is quite similar.
I had to unpack the stock rom and then individually flash the factoryfs and zimage files.
I then unpacked the Phils mod and flashed the zimage again.
That was all in download mode
After that I flashed CM12 in recovery mode.