Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...
You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.
@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.
paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!
Related
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
swiftstrike763 said:
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
Click to expand...
Click to collapse
You have to flash nyankernel or just the twrp zip. And next time when you flash from twrp, you need to pick inject twrp if you don't want cwm.
Sent from my SPH-D700 using Tapatalk 2
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
altimuh said:
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
Click to expand...
Click to collapse
Try http://marcusant.com/android/epic/modem.bin
Sent from my SPH-D700 using Tapatalk 2
Hello guys I just wanna inform you that there is something happening with the CM 11 4.4+ based ROMS
they deleted my Baseband and IMEI
I restored through KIES and got my Baseband and IMEI back but this thing keeps happening and I cannot figure out why?
It's painful procedure because I did this more then 10 times
First I had to Reflash everything through KIES which makes my phone as DEFAULT
then I had to ROOT and install the ROOTED Original 4.3 then I had to install Clockwork Mod with MOBILE ODIN in order for me to install different ROMS
after that I do FULL WIPE ALWAYS
Cache / Dalvik / Data / System even Internal Storage
I installed CM11 whatever ROM u choose:
http://forum.xda-developers.com/showthread.php?t=2453586 (tried this one no success)
Tried this one:
http://forum.xda-developers.com/showthread.php?t=2565259 again the same thing Bad baseband
Also this one:
http://forum.xda-developers.com/showthread.php?t=2493905 OMNI Rom (first installed older version everything was fine but when It updated to the latest OMNI I got the same Unknown Baseband and no DATA whatsoever)
so what the heck is going on? Please help me?
recovery might be the issue
I just had this problem yesterday. You wouldn't happen to be using TWRP recovery would you? I found that if I was using TWRP and Kit Kat AOKP I would have no service and my APN list would be empty. If I used Philz Custom recovery or CWM it would work fine.
I tried going downloading the newest 2.6.3.1 version of TWRP and it made my phone unable to boot. I had to flash another recovery via Odin in order to get back into my phone.
Just a thought.
I've had this issue as well and for some reason the latest nightlies don't play nice with my phone and recovery I'm using the latest official twrp for t0lte. Not t0ltetmo. I recently tried fishing the last multi window and I lost my microphone use. I have since reverted to a homemade build from January.. It seems to be the only thing that works.
Sent from my SGH-T889
Guys I used both CWM and TWRP both the latest versions... and this thing happen during both tries... I don't think it's the Recovery!
I wiped the dust off my old S2 in hopes to get it running again. The last ROM I had on it was Jedi Mind Trick JB 4. I flashed sultanxda's CM11 ROM and it booted up fine(logged into google, installed some apps). I did a soft reboot and the phone never wanted to boot back up. It flashed the Samsung logo and then just sat at a black screen. I flashed CM11 again just to make sure it didn't get corrupted the first time, but it still did not want to come up after a reboot. Then I thought maybe it's the ROM/ZIP so I flashed ParanoidAndroid 4.6-beta5. Same issue, it boots up fine after the flash, but will not start up after a reboot.
I'm on CWM Recovery 6.0.2.7, and I wipe/format the usual before the flash. Also on radio UVMC6. Any ideas?
I'm having the same problem, did you find a fix ?
Rushaan™ said:
I'm having the same problem, did you find a fix ?
Click to expand...
Click to collapse
same issue, different roms .
You. Guys are using an out of date recovery. Get the newest version of twrp and you should. Be fine.
CWM: http://www.teamchopsticks.org/p/cm110-release-notes.html
TWRP: http://forum.xda-developers.com/showthread.php?t=1768742
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Hi,
I will have your thread moved to your device section.
Good luck!
Superbia Thema said:
Hi, new to flashing roms and this might be a noobie question, however, I can't find an answer online. Over this week I have tried to flash cyanogenmod to note 3 the tmobile variant. I have it rooted (thanks to CF-Auto-Root) and it has twrp 2.8 the newest version. I downloaded the newest cyanogenmod rom and gapps into my flash drive and used an adaptar when I tried to flash it to my phone. It successfully flashed and I was excited for the new rom. However, when my phone rebooted into the Samsung Galaxy note 3 boot up screen; the top left of the screen showed Kernel is not seandroid enforcing set warranty bit: kernel. And it just starts bootlooping. I've tried waiting for 30 minutes and that just kept happening. So i decided to boot into recovery and and restore my original rom with twrp. That went fine and now I have all my data back. However, how do I end the bootloop? I watch youtube videos and they all work fine, however, they dont get the bootloop. They even have the same phone with the same carrier. I know its not the bootloader because tmobile doesnt have locked boot loaders. Right now I'm running on 4.4.2 Kit Kat on my note 3. Also I have already went back into twrp after flashing the rom and wiping dalvik and cache. It still didnt work. After I went back in and formated system memory and it still didnt work, so I gave up and did a little research. However, I cant anything relavant online to help me.
Links that I already read: http://forum.xda-developers.com/showthread.php?t=2470599
http://forum.xda-developers.com/showthread.php?t=2609767
http://forum.xda-developers.com/showthread.php?t=2614787
Click to expand...
Click to collapse
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
I downloaded cyanogenmod and gapps from those websites, but I'll flash twrp again to give it another try. Yea I was goanna install android lollipop but the bootloop gets me every time...
Sent from my SM-N900T using XDA Free mobile app
bobbyphoenix said:
Make sure your getting the ROM from here: http://download.cyanogenmod.org/?device=hlte
Latest TWRP recovery is 2.8.4: http://www.techerrata.com/browse/twrp2/hlte
Gapps: http://wiki.cyanogenmod.org/w/Google_Apps
When in recovery do a factory reset as step 1. Then go into Advanced Wipe, and only leave SD card unchecked. Wipe everything else. Then Format the system. After all that Flash the ROM, then Gapps, and them reboot. If you want you can try CM12. It's been very stable even as a new nightly.
http://forum.xda-developers.com/note-3-tmobile/general/official-cm12-released-t2995099
Seeing: Kernel is not seandroid enforcing set warranty bit: kernel is normal for CM. Don't worry about that.
Hope it works for ya. Enjoy.
Click to expand...
Click to collapse
Welp I went ahead and flash another rom and it worked so I'm guessing I either have the wrong files or something is wrong with my phone. However, dompop works amazingly to thanks for the help!!!
Hi everyone,
Today I installed the new CM12 nightlies, after rebooting my HTC one m8 it showed me a popup message that google play services stopped working. I also couldnt launch particular apps. So after looking for a solution I tried reinstalling Gapps hoping this would solve the problem.
I downloaded the minimal Gapps ZIP file and flashed it using TWRP recovery, after I wiped the cache and dalvik cache. Once rebooted I started to get the anoying pop up notifications '' Gmail stopped working'' and ''youtube stopped working''. These two messages won't go away and makes my phone unusable. I think the reason why these messages keep popping up is because i flashed the minimal version of Gapps so I downloaded the normal version of Gapps on my computer since my phone isnt accesable because of the pop-up notifications that won't go away. What I did next was plug in my phone to my computer and moved Gapps L-3-14-15.zip to my SD card and installed it again. I also wiped the cache and dalvik cache. after I did a reboot and everything seemed fine for the first 20 seconds... It didnt last long. Im still having the same problem as before Gmail and youtube has stopped working. Do any of you know how to fix this without doing a system recovery?
Thanks in advance
HTC one m8
Cyanagonmod 12.1
Rooted
TWRP
S-on (don't know if this is relevant)
Copy important files to computer. Factory reset. Set it up as new device.
ikeny said:
Copy important files to computer. Factory reset. Set it up as new device.
Click to expand...
Click to collapse
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
I guess the minimal Gapps package that I first installed wasnt for 5.1
In order to get rid of the pop up notifications I started my phone in safe mode. This worked and I saw there was a new update for cm12.1 after the update finished and I booted up my phone the pop up notification werent there anymore but google play services was also uninstalled. What I did next was installing the newest google play services pack. After it was done I installed the 5.1 Gapps version on my phone and now everything seems working fine again. I did get some notifications that an app such as chrome stopped working but a simple reinstal of the app fixed the problem. Somehow the apps that I moved to my external SD card arent here anymore but im glad I didnt have to do a factory reset.
Thanks for your help
jcole20 said:
To me it sounds like you installed a gapps 5.0 package not a 5.1 package. With the CM Nightly you need to make sure you're using an updated gapps package designed for android 5.1+.
I always use a minimal gapps package but usually CM has a link available on their page. Double check that you're installing a gapps 5.1 package. I am currently running the 5.1 nightlies and they're great thus far... 4/20 and 4/19 are both confirmable as working on my end. Good luck.
To correct Wipe /data /system /cache and dalvik reinstall the nightly and flash a 5.1 gapps package.
Click to expand...
Click to collapse
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
decoction said:
every time i update my cm12 nightlies it has its own recovery (cyanogen recovery) but my zip files are not working with that recovery. (ex. cmzip.gapps, and kernels). for my device it works on PhilZ touch recovery. so the tendency is i have to flash fastboot boot.img(philz touch)again and again.
using Thunderzap kernel 4.15 im stock on bootloop.
running cm12.1 nightlies (4/20/15)
also gapps not compatible.
Click to expand...
Click to collapse
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Everything seemed working fine again until 30 min. ago...
I got the notification chrome has stopped working. (Haven't had this message all the morning and chrome worked just fine.)
I restarted my phone and the first thing I noticed was that some of my apps have disapeared from my home screen, they are still in the app tray tho. Also my keyboard input mode has been set back to AOSP while normaly I use Swiftkey keyboard as my standard input. Chrome was still pushing me not working notification so I reinstalled chrome and now it works fine again. Not sure for how many time...
Its kinda anoying but maybe tonights nightlies will solve the problem somehow. If not, do you have any sugestions how to fix this?
jcole20 said:
I use twrp and I've not had any issues with a cm recovery replacing twrp. On the 420 nightly I don't even see a recovery.img in the cm zip so I'm assuming you're updating via cm itself. I think there's a setting in there to choose to update cm recovery or not.
To flash Phillz recovery you're syntax would be "fastboot flash recovery recoveryimgname.img" the boot.img is your kernel. I'm not sure how many aosp 5.1 kernels the m8 has but I've not really been able to find any so I just use the cm one.
To correct your issues I would flash twrp 2.8.6 via fastboot flash recovery. Wipe everything from recovery (cache data dalvik system) and reinstall. If it was me I'd update cm via zip from now on if it was causing me these issues. Good luck
HTC One (M8) ViperOne + Hypernova
Click to expand...
Click to collapse
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
decoction said:
Thank you for that info. it really helps. by the way i got problems when i updated it to the cm12 4/21/15 update. got this message "trebuchet has stop working" so i decided to use cm resurrection remix.
Click to expand...
Click to collapse
Yeah I mean nightlys merge with code that it's being worked on and may break or fix certain things. Nightly builds may be perfect or they may not even boot. You kind of have to just flash them and see. Cm is very generic coding and depending on your carrier may not have the non open source vendor blobs necessary to make, say, your speakers work properly. It really depends. I don't believe Verizon had released their kernel source for lollipop so sometimes downgrading firmware to known source (ie 4.4.4) may help alleviate connectivity issues with Wi-Fi and things of that sort. Team UBs build and lollipop dream 5.0.2 have been my go tos as of late. The lollipop dream build is the smoothest running cm build I've ever used even on nexus devices. Very well made.
HTC One (M8) ViperOne + Hypernova