I installed a nightly build, but now some important features of my phone don't work: it boot-loops, or can't make calls, or can't use mobile data, or something like that. What can I do about it?

N.B. This is a "canonical question" for all similar questions, because questions about specific bugs in one particular nightly build of a ROM are way too specific to have any long-term value. See this meta question to learn why this question was created, and why your particular question about nightly builds might have been closed as a duplicate of this one.

3 Answers 3


As our tag wiki explains:

Nightly builds are created each day, and represent a snapshot of development, with minimal testing and quality control. They often have missing features or critical defects, changing from one day to the next, and are not recommended for everyday use. If you ask a question here about unusual behaviour in a nightly CM build, we'll probably suggest you switch to a more stable ROM. Experimental builds are the same as nightlies, but are one-off special builds outside of the nightly routine.

That quote had a lot of words, so let's repeat the crucial bit.

If you want to use your phone, do not install a nightly build.

If you already ignored that recommendation and installed a nightly build, and your phone doesn't work, stop using the nightly build. Reinstall the latest stable, release candidate, or milestone build for your phone, or the stock ROM for your phone. If that means going to an older Android version, you probably need to wipe userdata (i.e. factory reset) at the same time.

If you don't know where to find a stable version of the custom ROM, or the stock ROM, check out Where can I find stock or custom ROMs for my Android device? The exact steps to install a ROM are different for each phone, but if you already installed a custom ROM, you probably already know how to do it for your phone. If not, just search this site with your phone model, and you'll probably find step-by-step instructions.

You should probably also report the bug to the developers. They might not be interested if it really is a nightly build. ROM developers don't expect the nightly build to work. But if it's an experimental, unstable, milestone, or release candidate build they probably will want to know. If the ROM in question is an official LineageOS port, you can report a bug using their Jira bug tracker. More information about their bug reporting process can be found on the LineageOS wiki. If it's an unofficial Lineage port, or different custom ROM, you probably need to contact the developer directly, or check the forum post you got it from.

In particular, if you installed a nightly build and it broke something, this site is not a good source of help. Generally, the only fix for the problem is to install a different (working) ROM build, so that's all we'll ever tell you to do. If there's some workaround for the bug, maybe only the ROM developer knows it, and the best place to get their advice is by the means above: the bug tracker, or whatever forum they hang out at.

Maybe you installed the nightly and it actually broke your phone hardware, or installed a new bootloader that can't flash images any more. If that happened, tough cookies. You played the lottery, you lost. Nightly builds can do all these things to brick your phone, and more. That's why even the ROM developers advise you not to install them unless you're willing to take that risk.

If there's only a nightly or unstable build for your device, you might read Why isn't there a Cyanogenmod stable ROM for my device? to learn about why porting ROMs is hard, and what you can do to help accelerate development of a stable, usable ROM for your device. But until then, you'll have to either stick with a different ROM, or just take the lottery of not knowing whether tonight's upgrade will finally be the one that bricks it.


What I normally do before I choose which ROM to use on my phone is, make a list of all the functionality I want to use or that the phone has and read up on the ROM and check change lists to see what is working on that ROM or not. From there you can make and pick of you can do without certain functionality or not. Next i would check the apps that I use, do they work on that ROM. I once had a ROM I would have loved to test out, but skype voice was not working on that ROM. So I waited until they sorted that out before I flashed to that ROM.

I use a custom ROM on my daily driver. And works great. Before updates I check the change log then from there decide. I think it is not a bad idea to flash so long as you are informed. If you do end up in a bit of a spot try flash it to an older working version that you knew was working, else wipe and reflash original ROM. Always my last option that.


  • 1
    This is good advice in general, but it's not really relevant to nightly builds. There typically isn't a published changelog, and even if there is, it won't tell you everything that broke. (If it could, there wouldn't need to be a nightly build in the first place!)
    – Dan Hulme
    Jun 9, 2016 at 12:08
  • @DanHulme With cyanogen there is usually a changelog. Plus if you google enough around forums you will surely come to a list of "not workings". But I do understand where you are coming from.
    – Kwekuq
    Jun 9, 2016 at 19:54

I did the same once.

Download the original rom from the vendor for your phone. Then do the same procedure to install this rom instead of the modded one.

If you copied the rom to the phone internal memory (and now because of the loop-reboot you cant access), it would be nice to have an external memory. Copy the rom in the external memory and install the new rom from there.



1) Download the rom for your phone from :


2) Copy it to external memory and put it into the cell.

3) Reboot cell in recovery mode ( up + power + home )

4) Install or format your phone with new rom.

  • 2
    Note: Community Wiki questions im this case have a canonical single answer, which is supposed to be edited to include new data,new answers aren't supposed to be added. I'll flag your post, as it is wrong (you normally can't flash manufacturer ROMs like custom ones, i.e., through recovery),and of no additional value to the question and the canonical answer Jun 9, 2016 at 0:46
  • 3
    In fairness to ctutte though, at the time I write this the supposed "canonical single answer" doesn't actually answer the question. The question boils down to "I've done something to my phone, how do I fix it" and the answer is effectively "don't do it in the first place". To be useful, the answer needs to contain some generic steps talking a moderately technical user through the process of obtaining a stable image for their phone & restoring it.
    – mcottle
    Jun 9, 2016 at 7:37

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .