Database Info

[Q] Bricked my HTC One S

Hi all,
Got mine today, tried to install a ROM and it got stuck in bootloop.
I did a number of stupid things not to mention wiping the SD and im in serious trouble.
I can get into bootloader and CWM but thats it.
Ive heard restoring a RUU can cure it but I have a MAC and cant find anything to help.
Can anyone help? Im gutted....and fell like an idiot.
Ive got an S4 on the three network.
Thanks

Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app

blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hi,
It enters into bootloader but then what?

Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app

blackcell1 said:
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Its sent and wrote the recovery file but what now?

mikejasonsmith said:
Its sent and wrote the recovery file but what now?
Click to expand...
Click to collapse
Specifically you'll have to flash the ROM zip file from the recovery and then use fastboot flash boot boot.img.
You can find boot.img inside the ROM zip file

Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?

mikejasonsmith said:
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
Click to expand...
Click to collapse
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?

mikejasonsmith said:
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
Click to expand...
Click to collapse
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help

mikejasonsmith said:
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
Click to expand...
Click to collapse
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks

mikejasonsmith said:
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
Click to expand...
Click to collapse
so ive managed to get the h3g rom and flashed rom and boot.img.
locked bootloader and run RUU but i keep getting error 155???
Somebody please help me before this thing goes out of the window.....:crying:

Search adb push
Sent from my HTC One S using Tapatalk 2

danevianta said:
Search adb push
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Finally seem to have done it and managed to RUU
The phone is locked to 3 but as a noob I spent 2 days flashing a generic euro ROM.
When i realised i need a ROM to match CID i downloaded 1.53. Tried this a number of times with no joy.
Just tried 1.78 and it seems to be working
Thanks to everyone for your help - us noobs must be sooooooo annoying.

Htc One S bricked
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.

FaLLeN_BtB said:
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
Click to expand...
Click to collapse
Bootloop does not mean your bricked...means you need to fastboot flash boot.img
Sent from my HTC One S using xda premium

blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
This little post just pulled me out of missery. Love ya man!

all you guys getting sorted
make a nandroid and sdcard bu NOW and put them on pc,
obviously leave a copy of nandroid on phone also
makes it a lot easier if you get in trouble again
and you/we will

Mounts and Storage --> Format everything --> Now Mount USB Drive --> Put Gapps and ROM
Flash it, erase cache & and Dalvik...Blah blah blah. Flash boot.img in fastboot, and there you go.
Everybody, please remember this and there won't be noob q&a anymore...

TWRP v 2.2.2.1 I can't flash Jelly Bean 4.2.2 .zip on HTC one s (s3)
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........

mikebryant2807 said:
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Click to expand...
Click to collapse
See other reply.

[SOLVED] HELP PLease! Cannot go passed HTC ONE splash screen/ will not boot

I know you have seen this title a lot of times
I have looked for a thread that can help me with this but nothing helps...
Ok so here's what happened:
I had my HTC One X At&t version and everything was fine except i wasnt getting any updates. I was on version 1.73 so I decided to download the RUU for jellybean... it installed the new hboot 2.14 (the original one installed was 1.08). But the installation didnt go through after that.
Then I decided to download the other RUUs for Jellybean but some said that i wasnt charged enough even though i had 100% battery charge...
THEN I downloaded a stock deodexed image, Unlock the bootloader and installed TWRP and then flashed the stock deodexed image on my phone.
Now the phone will not go passed the HTC One splash screen :crying: I have tried wiping cache/ factory reset, and flashing the boot iimg from that deodexed zip
I can still get into fastboot and recovery i guess but not much after that! Can you guys please help me! This is the only phone I had ( just got rid of My nexus4)
Help please!

now my hboot fastboot screen says security warning!!!
I think Im screwed

gabo_e30 said:
now my hboot fastboot screen says security warning!!!
I think Im screwed
Click to expand...
Click to collapse
It says tampered cause u unlocked bootloader
Sent from my HTC One XL using xda premium

31ken31 said:
It says tampered cause u unlocked bootloader
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
yeah it said that before... but now theres also a third line that says security warning!!!

31ken31 said:
It says tampered cause u unlocked bootloader
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I have the same problem the phone will not go passed the HTC One splash screen and I can not copy the roomo into the phone becuase I have porblem to mount the phone.. can help me as well

gabo_e30 said:
yeah it said that before... but now theres also a third line that says security warning!!!
Click to expand...
Click to collapse
gabo_e30 can you send me the exactly "boot.img".. I can install the UrDroid_One_X_ATT_OTA_JB_Odex-evita-1.9 but the phone not pass the initial screen plese.. my phone is at&t version

loquillo711 said:
gabo_e30 can you send me the exactly "boot.img".. I can install the UrDroid_One_X_ATT_OTA_JB_Odex-evita-1.9 but the phone not pass the initial screen plese.. my phone is at&t version
Click to expand...
Click to collapse
I would bro.. except I have no idea what my problem is... I was reading in another thread that you should get into recovery and wipe system partition wipe dalvik/cache and re install rom using TWRP
http://forum.xda-developers.com/showthread.php?p=42364368&highlight=boot#post42364368
but I cant even get a working recovery now

gabo_e30 said:
I would bro.. except I have no idea what my problem is... I was reading in another thread that you should get into recovery and wipe system partition wipe dalvik/cache and re install rom using TWRP
http://forum.xda-developers.com/showthread.php?p=42364368&highlight=boot#post42364368
but I cant even get a working recovery now
Click to expand...
Click to collapse
Wipe all of those through fast boot, especially cache
-Sugardaddy

Could you be more specific... I can't get into any type of recovery or even flash one...

gabo_e30 said:
Could you be more specific... I can't get into any type of recovery or even flash one...
Click to expand...
Click to collapse
Wait, you can't even fastboot flash the recovery (i.e. TWRP)?

No
It says:
(boot loader) signature checking....
Failed...
When I try to flash a recovery or boot image... Doesn't matter if its TWRP or stock

Your bootloader is locked. Unlock it.
Sent from my HTC One X using xda app-developers app

SOLVED
Alright so i fixed it
http://forum.xda-developers.com/showthread.php?t=1891598
BAsically (Above post) is correct.
Here is what I did:
1) Unlock Bootloader
2) Flash TWRP 3.3.1
3)In TWRP, Wipe EVERYTHING (system, dalvik, cache, everything)
4) In TWRP mount as USB drive ( had to format it on Windows to be able to use it)
5) Move the ROM to your phone's storage
6)Wipe cache,dalvik cache, system, and factory reset (yes again)
7)Flash rom
From here on out i followed this thread's intructions because I was getting a bootloop: http://forum.xda-developers.com/showthread.php?t=2293032
8)If your're s-off or on hboot 1.09 then you can reboot to system. If your're not s-off and have hboot 1.14 or greater go to step 9
9)Reboot to bootloader and select fastboot
10)Open the rom.zip and copy the boot.img to your fastboot directory.
11)Plug phone into computer and verify connection (make sure it says Fastboot USB)
12)Flash boot.img with this command: fastboot flash boot boot.img
13Now you can reboot to system and enjoy the rom.
Now I have a fully stock HTC ONE X (unlocked) on At&t ...with 4.1.1 >>> but these instructions should work for any ROM
Thanks again for your help and concerns!
Thats what I love about XDA, people help you and you learn!

[Q] TWRP/NO OS - ROGERS - Searching forums and nothing!

I have been reading for the last couple weeks, thinking I have an answer and end up further into the hole.
Rogers HTC One X / EVITA / HBOOT 2.14. / 2.4 TWRP initially, now 2.6 / Unlocked boot loader / s-on
1. Started trying to flash AOKP 4.2.2. Flashed boot.img, then followed with TWRP recovery. All I could get was the language screen and then it stalled. Tried numerous iterations of this with various wipes and flash first and flash after.
2. Next tried Viper 3.2.7. All good till it gets to startup screen then it stops (I understand Viper has its boot.img installed to start not needing it flashed).
3. While trying various wipes to see if it would install completely I mistakenly did a factory reset! Now no OS! No Nandroid! No ROM.zip!
4. To get a ROM on SDCard tried ADB sideload thru TWRP. after running script it says unable to mount SDCARD! Suggests I reboot system! Now a little leery of rebooting for fear it will not.
5. Also tried to MOUNT HTV via TWRP on to laptop. Did not recognize said ti initialize. Formatted FAT 32 (via MAC). Now will not mount SD Card. I did drop Viper.zip into mount (cache and system OK) but can not find it using FILE MANAGER via TWRP
6. Now am in BOOTLOADER screen of Android. Thought I could flash a ROM but from what I read it does not look possible.
Can any one point me in the right direction to get this thing up and running. At this point, as much as I am learning all the time, it does me no good having my phone down for two weeks (sure glad I kept my Nexus One).
Any answer at this stage is a good answer and I appreciate all input!
Thanks
D

Sounds like you did a factory reset in bootloader which corrupts the sd card after unlocking the bootloader. You used to be able to just mount it on pc and format it but after the jb update I don't think that's possible due to the drive no longer being a mass storage device but an mtp device instead. There was a method to fix it developed by team nocturnal but it looks like the site is inaccessible right now. I'll see if there's a way to fix it and get back to you. Bear with me.
[/COLOR]By any chance have you tried wiping sd card in twrp 2.6?
Also, have done SuperCID yet?
Sent from my One X using xda app-developers app

exad said:
Sounds like you did a factory reset in bootloader which corrupts the sd card after unlocking the bootloader. You used to be able to just mount it on pc and format it but after the jb update I don't think that's possible due to the drive no longer being a mass storage device but an mtp device instead. There was a method to fix it developed by team nocturnal but it looks like the site is inaccessible right now. I'll see if there's a way to fix it and get back to you. Bear with me.
[/COLOR]By any chance have you tried wiping sd card in twrp 2.6?
Also, have done SuperCID yet?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
SuperCID has not been done. It is S-ON presently.
I wiped SD Card as suggested. Saw it set up partitions. And now TWRP shows up when I mount . Can I just drop a ROM in and flash via TWRP? Any suggestions for a ROM. Could not get AOKP 4.2.2 to run or Viper 3.2.7.
Thanks for the quick assist at getting it to MOUNT.

Flash a stock sense rom and then fastboot flash boot boot.img extracted from the rom. Then use jet to downgrade hboot and SuperCID and then s-off. It'll save you lots of headaches.
Sent from my One X using xda app-developers app

exad said:
Flash a stock sense rom and then fastboot flash boot boot.img extracted from the rom. Then use jet to downgrade hboot and SuperCID and then s-off. It'll save you lots of headaches.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
It all sounds simple when you say it.
I will find a stock sense ROM to install then follow with boot.img.
Is it necessary to wipe anything more then Dalvik and Cache?
Thanks again.
David

In twrp 2.6 the factory reset wipes everything except sd card and system. You don't have to wipe system but I always do when I'm flashing a new rom.
Sent from my One X using xda app-developers app

exad said:
In twrp 2.6 the factory reset wipes everything except sd card and system. You don't have to wipe system but I always do when I'm flashing a new rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Will wipe the system then.
Thanks again.
D

Anytime pip
Sent from my One X using xda app-developers app

[Q] Need help. Wiped OS with no backup

Hello, I was trying to flash slim bean to my phone, and when trying to wipe Davik, I wiped the os for the system without a backup. I can now only get to the htc quietly brilliant page. Please help me.

U should be able to boot from what I know.. from the powered off screen... Go to bootloader if. U can
Sent from my HTC One X using xda app-developers app

He won't boot if he wiped the OS.
Just go into recovery, mount usb storage, copy a ROM from pc, flash it.
Sent from my Evita

timmaaa said:
He won't boot if he wiped the OS.
Just go into recovery, mount usb storage, copy a ROM from pc, flash it.
Sent from my Evita
Click to expand...
Click to collapse
Okay, so if I re-lock the bootloader, will I be able to go back to a stock rom, if I use an RUU for my phone? Or should I leave it unlocked and try to flash. S is on by the way.

Thenerdy0ne said:
Okay, so if I re-lock the bootloader, will I be able to go back to a stock rom, if I use an RUU for my phone? Or should I leave it unlocked and try to flash. S is on by the way.
Click to expand...
Click to collapse
I'd leave it unlocked. Boot into recovery, use adb push to copy a rom and flash away.

I'd leave it unlocked. You don't need to use adb push. Just mount usb in recovery and copy ROM across. Then flash the ROM.
Sent from my Evita

fleabeard said:
I'd leave it unlocked. Boot into recovery, use adb push to copy a rom and flash away.
Click to expand...
Click to collapse
Ok, so do you know the script to push from adb? and what dp you think would be the best rom to flash in this case for ease.

Thenerdy0ne said:
Ok, so do you know the script to push from adb? and what dp you think would be the best rom to flash in this case for ease.
Click to expand...
Click to collapse
If you're already S-OFF, easiest would be to RUU and never root your phone again.

exad said:
If you're already S-OFF, easiest would be to RUU and never root your phone again.
Click to expand...
Click to collapse
The thing is I have S-on currently.

Thenerdy0ne said:
The thing is I have S-on currently.
Click to expand...
Click to collapse
What Hboot version?
It should say in bootloader.

exad said:
What Hboot version?
It should say in bootloader.
Click to expand...
Click to collapse
It's 2.14

Maybe you should just relock the bootloader and run the RUU.
Sent from my Evita

timmaaa said:
Maybe you should just relock the bootloader and run the RUU.
Sent from my Evita
Click to expand...
Click to collapse
That might brick him.
Best to just flash CleanRom or stock.

Yeah I guess there have been a couple cases.
Sent from my Evita

sdeUple Ganga
exad said:
That might brick him.
Best to just flash CleanRom or stock.
Click to expand...
Click to collapse
Ok, so I should flash clean rom. Any recommended way to do that? go through Adb? And how would I push the boot img with ADB

Thenerdy0ne said:
Ok, so I should flash clean rom. Any recommended way to do that? go through Adb? And how would I push the boot img with ADB
Click to expand...
Click to collapse
What is with you and ADB? With no OS, you can't use ADB.
Extract the boot.img from the rom zip file and put it in your fastboot folder
Mount USB through recovery, copy the rom zip file to your SDcard
wipe cache, dalvik, system
flash rom
reboot to your bootloader/fastboot
plug in your phone
fastboot flash boot boot.img
fastboot reboot
Should boot and work fine.

exad said:
What is with you and ADB? With no OS, you can't use ADB.
Extract the boot.img from the rom zip file and put it in your fastboot folder
Mount USB through recovery, copy the rom zip file to your SDcard
wipe cache, dalvik, system
flash rom
reboot to your bootloader/fastboot
plug in your phone
fastboot flash boot boot.img
fastboot reboot
Should boot and work fine.
Click to expand...
Click to collapse
Ok, I flashed the rom, and now I can't touch the screen and have it respond. It's strange because the touch screen will work in Recovery.

Which ROM did you end up flashing?
Sent from my Evita

timmaaa said:
Which ROM did you end up flashing?
Sent from my Evita
Click to expand...
Click to collapse
I flashed cyanogenmod 10.1
Is it common to have the touch screen problems after flashing it?

Which version of cm10.1? The other builds aren't compatible with the latest touchscreen firmware. You can either downgrade your ts firmware, or flash the latest cm build.
Sent from my Evita
---------- Post added at 12:26 PM ---------- Previous post was at 12:24 PM ----------
You probably should have stuck to Cleanrom. All of this stuff is super basic and you're still managing to get it wrong.
Sent from my Evita

Softbricked One Mini

so I've got a interesting situation. A friend managed to softbrick his Mini. I don't know how he got it in this state, but, it has TWRP installed, its copy of android does not boot, and it's S-ON. I played with RUUs for a few hours and couldn't get any of them to work. If I can get any working copy of android on it I can then get S-OFF and fix it. As far as I see there's two routes to fix this.
-Get S-OFF without using android
-Get a android ROM on there without S-OFF.
I pretty much have access to fastboot and twrp that can't flash Roms because of s on. Recoveries also have errors about mounting /system or /cache.
Any help in fixing this would be appreciated.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Adding abit more information, I tried using a RUU but get errors because of firmware version. When I get the rom.zip out of the RUU and try to use fastboot to flash it, on windows I get a error about header errors (error 32). On Linux I get errors about the file is too large.
Also, nomatter what recovery I can try, neither can mount either /system or /cache unless you format them, then after a reboot they cant be mounted again.

I had an issue where my os was completely wiped after a botched update attempt. Lol I went through every possible I could think of or find until I see something about using an external drive. So what I did was use fastboot to flash a recovery, which you already have which is good. And then from there I used an OTG cable, and connected my USB drive to it, which had a ROM zip on it and flashed it. It worked. I am bootloader unlocked but not s-off. But as long as you have a recovery you can do this. I actually wasn't even rooted.
Sent from my One Mini using XDA Premium 4 mobile app

dizzyman1180 said:
I had an issue where my os was completely wiped after a botched update attempt. Lol I went through every possible I could think of or find until I see something about using an external drive. So what I did was use fastboot to flash a recovery, which you already have which is good. And then from there I used an OTG cable, and connected my USB drive to it, which had a ROM zip on it and flashed it. It worked. I am bootloader unlocked but not s-off. But as long as you have a recovery you can do this. I actually wasn't even rooted.
Sent from my One Mini using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm still worried about the failing to mount /system and /cache errors. Did you have those as well?
Sent from my HTC6525LVW using XDA Premium 4 mobile app

polaric said:
I pretty much have access to fastboot and twrp that can't flash Roms because of s on.
Click to expand...
Click to collapse
You don't need S-OFF to flash roms. As long as you unlocked the bootloader you can fastboot-flash boot, system and recovery. And so you can flash ROMs when in recovery mode.
polaric said:
I'm still worried about the failing to mount /system and /cache errors. Did you have those as well?
Click to expand...
Click to collapse
What HBOOT version do you have?

morschesholz said:
You don't need S-OFF to flash roms. As long as you unlocked the bootloader you can fastboot-flash boot, system and recovery. And so you can flash ROMs when in recovery mode.
What HBOOT version do you have?
Click to expand...
Click to collapse
HBOOT is 2.22
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Well, then it looks like the same issue as in the thread next to this one. So please go over there and perhaps you'll try my next steps written down there: http://forum.xda-developers.com/showthread.php?p=51737651

morschesholz said:
Well, then it looks like the same issue as in the thread next to this one. So please go over there and perhaps you'll try my next steps written down there: http://forum.xda-developers.com/showthread.php?p=51737651
Click to expand...
Click to collapse
I followed that and it got me a working recovery, but both twrp versions and the cwm version won't flash the cm zip, regardless if its modified, if I modify it myself or use a attached update-script. Both recoveries simply say "Failed to flash zip".
Sent from my HTC6525LVW using XDA Premium 4 mobile app

Then you should repeat the flashing and have a look at the recovery log right after it. At TWRP it's located at /tmp/recovery.log (don't know for CWM).
Either do a
Code:
adb shell cat /tmp/recovery.log
or pull it to your pc:
Code:
adb pull /tmp/recovery.log

morschesholz said:
Then you should repeat the flashing and have a look at the recovery log right after it. At TWRP it's located at /tmp/recovery.log (don't know for CWM).
Either do a
Code:
adb shell cat /tmp/recovery.log
or pull it to your pc:
Code:
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
Already tried multiple times, of course. I looked at the log and didnt see anything of value though. I can post it if you like.
Sent from my HTC6525LVW using XDA Premium 4 mobile app

That's what I recommended in another post:
morschesholz said:
Meanwhile you could try flashing CM11. There is an edited updater-script and boot.img over here: http://forum.xda-developers.com/showthread.php?p=51613028
I used it with cm-11-20140403-NIGHTLY-m4 successfully. Maybe the edited script works with newer versions of the CM nightlies as well, but I didn't test that yet.
Click to expand...
Click to collapse

This is the 0403 CM11 nightly I modified to match the new partition layout: https://dl.dropboxusercontent.com/u/5035075/m4kk/cm-11-20140403-NIGHTLY-m4kk.zip
You should be able to flash it with the modified version of TWRP 2.7.0.5