I was installing the most recent nightly update and after the phone restarted it began to flash on and off, I then rebooted it to try and fix the problem but this only made the phone stay of the cyanogenmod loading screen and will not boot after 20+ mins on this screen. How would I go about fixing this issue?
This is the update I installed: cm-12-20150116-NIGHTLY-bacon
What you need to understand is that "nightly" builds are highly experimental and far from stable. They are actually meant for developers if you ever dare to read the description of them.
Unfortunately you will not likely find much support for nightlies as they are updated daily for the most part. You're either going to have to flash a different rom or wait for the next nightly and try your luck.
Thank you
markbencze said:
What you need to understand is that "nightly" builds are highly experimental and far from stable. They are actually meant for developers if you ever dare to read the description of them.
Unfortunately you will not likely find much support for nightlies as they are updated daily for the most part. You're either going to have to flash a different rom or wait for the next nightly and try your luck.
Thank you
Click to expand...
Click to collapse
Ah okay I understood what I was getting into but here's the weird part, I was successful in adding a new ROM and trying to boot using a stable version of CyanogenMod which again was successful however when I rebooted the phone I got the same issue with it being stuck at the boot screen.
Thank you for your help.
Related
NOOB HERE!!!
My quick and hopefully simple question regards installing the CM updates that are available directly on my phone. I am running 10.2 with no issues. Nearly everyday I get the icon stating there is an up to CM10. I simply click on it and install. Again, so far so good but I would like to know if simply installing these updates this way is "endangering" my phone. Is there a better way I should be installing these? I am assuming not otherwise the updates would not be present and as simple to install. Thanks for your input!
kcoop99 said:
NOOB HERE!!!
My quick and hopefully simple question regards installing the CM updates that are available directly on my phone. I am running 10.2 with no issues. Nearly everyday I get the icon stating there is an up to CM10. I simply click on it and install. Again, so far so good but I would like to know if simply installing these updates this way is "endangering" my phone. Is there a better way I should be installing these? I am assuming not otherwise the updates would not be present and as simple to install. Thanks for your input!
Click to expand...
Click to collapse
It is perfectly safe to use the built in cmupdater every day. For piece of mind it may be a good idea to occasionally make a backup manually using your recovery of choice (either TWRP or CWM).
If you ever encounter a problem after upgrading to the latest nightly, and nightlies do sometimes break features, just boot into recovery and manually flash the previous day's file (located in the /cmupdater folder)...no need to wipe anything.
I've been dirty flashing cm nightlies since June. You're fine. A clean flash doesn't hurt once in awhile though!
Thanks! I appreciate it!
I dirty flashed for a year with no problem at all untill a few days ago. I went from the 8/16 to the 8/17 to the 8/14 and lost my imei and eri once the 8/14 booted. Ive been trying everything with no luck to get the eri back. make sure you do a full (not just imei) NV back up and do a normal rom/data backup like once ever week or two. Im regretting not doing a NV backup as the only tool to fix my problem has been removed from the site due to infringing the ToS.
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Have you tried deleting the telephone system app?
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
rickpref said:
I have a TF300T with the latest bootloader and twrp 2.6.3.1. I had been installing nightlies for CM11 and using Grimlock kernel and had zero problems until the first nightly after Snapshot M4. Ever since then, after flashing a kernel on any CM11 as soon as it reboots into android I get the message in the title line.
I have tried wiping everything and it still happens after installing a kernel. If I just install any copy of CM11 and GAPPS everything works perfectly fine. It's only when installing any of the aftermarket kernels. I even tried using the latest Philz Touch 6 and still get the same problems. I have searched on Google and find plenty of people asking for help on the same error message for different devices but nothing on how to fix it. Does anyone know what this can be?
Any help will be greatly appreciated. I like our tablet with CM11, but it is SO much better being able to overclock.
Thanks,
Rick
Click to expand...
Click to collapse
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
graphdarnell said:
Free gift from Grimlock. It's the kernel that restarts 3 times before fully booting, right? As soon as I took it off my system, the problem vanished. Comes with the package. You like Grimlock, must learn to live with it. I don't like it That much.
Click to expand...
Click to collapse
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
hardslog said:
Updates have come that fix that problem. Same with Geass, if it's not fixed yet it will be VERY soon.
Or you could file bug reports with the devs, and guess what? They found the problem and fixed it! Instead of slagging people who are trying to improve our tablets, you could help them by letting them know about the issues you have.
The "free gift" is the kernel that's posted for a community. If you don't like it and don't want to help, and would rather tell others bad things about it, then take your nonsense somewhere else.
Click to expand...
Click to collapse
I upgraded to the latest TWRP 2.7.0.1, deleted everything and started from scratch. Everything works great now and using new kernel that clocks to 1.8 is flying.
I just made the switch from BlackBerry to Android and the Relay seems like a good fit for me since I really can't stand touchscreen keyboards. I already unlocked the phone per the forum sticky since I'm on AT&T and it was a priority.
I *think* I want to install Cyanogenmod 10.2 (I'm a fan of using stable builds). When I look over the installation instructions, I'm a bit cornfused on step one:
There is an Important Note instructing users to install bootloader and radio firmware. How do I do that? The zip files it links to don't include any instructions or links to any instructions.
openletter said:
I just made the switch from BlackBerry to Android and the Relay seems like a good fit for me since I really can't stand touchscreen keyboards. I already unlocked the phone per the forum sticky since I'm on AT&T and it was a priority.
I *think* I want to install Cyanogenmod 10.2 (I'm a fan of using stable builds). When I look over the installation instructions, I'm a bit cornfused on step one:
There is an Important Note instructing users to install bootloader and radio firmware. How do I do that? The zip files it links to don't include any instructions or links to any instructions.
Click to expand...
Click to collapse
It pretty much means update to the latest ota available...which is T699UVBMC5 if you don't you'll have issues with signal and such...last I heard 10.2 had very rapid battery drain and stability issues but its possible they may be fixed but idk...most stable would be cm11 in terms of cyanogenmod but all my users say my latest carbon ROM is the most stable ROM available for relay as they go back to that if any issues arise in my other ROMs or teamapexq roms. Liquidsmooth ROM that I have has a lot of tweaks and mods and is fast and smooth...it gets updated the most as it is official and there is an ota within the ROM that whenever I release you can update it straight from phone without really having to do anything
REV3NT3CH said:
It pretty much means update to the latest ota available...which is T699UVBMC5 if you don't you'll have issues with signal and such...last I heard 10.2 had very rapid battery drain and stability issues but its possible they may be fixed but idk...most stable would be cm11 in terms of cyanogenmod but all my users say my latest carbon ROM is the most stable ROM available for relay as they go back to that if any issues arise in my other ROMs or teamapexq roms. Liquidsmooth ROM that I have has a lot of tweaks and mods and is fast and smooth...it gets updated the most as it is official and there is an ota within the ROM that whenever I release you can update it straight from phone without really having to do anything
Click to expand...
Click to collapse
I'm having a hard time finding an install guide for anything other than CM. For carbon, I'm guessing it's located at vp-zp.com/snuzzo/roms/carbonrom/apexqtmo/kk/ ? Even that I got from googling and then backtracking links from a blog post, as the carbon webpage doesn't seem to have a Relay ROM listed.
To be honest, as a total n00b at this, I'm having a hard time pulling all the pieces together to understand the various different abbreviations, projects, download sources, etc. My goal is simply a nice stable build that is maintained, updated to support major features, but without adding issues, such you as mentioned there may be battery life issues in CM.
openletter said:
I'm having a hard time finding an install guide for anything other than CM. For carbon, I'm guessing it's located at vp-zp.com/snuzzo/roms/carbonrom/apexqtmo/kk/ ? Even that I got from googling and then backtracking links from a blog post, as the carbon webpage doesn't seem to have a Relay ROM listed.
To be honest, as a total n00b at this, I'm having a hard time pulling all the pieces together to understand the various different abbreviations, projects, download sources, etc. My goal is simply a nice stable build that is maintained, updated to support major features, but without adding issues, such you as mentioned there may be battery life issues in CM.
Click to expand...
Click to collapse
i've been running the M7 snapshot of CM11 for about a month now. my only complaint about battery isn't really the rom's fault - if i'm watching a lot of netflix or youtube, the battery goes down faster. that's not really a surprise though.
i'm still pretty new to the relay though i've had a couple other androids before this one. but i suggest you use TWRP (Team Win Recovery Project) instead of CWM (clockworkmod) for your recovery. it's got a gui and is a bit easier to use when flashing roms and doing wipes and stuff.
bsically the process is to boot your phone into download mode, flash twrp, then reboot the phone into twrp, wipe everything, then flash CM and gapps (if you want google apps like gmail, play store, etc). then wipe cache/dalvik/factory reset (because some roms are unstable if you simply flash without doing the second wipe). no need to try to inject SU (superuser) or anything since pretty much all custom roms are already rooted. there are other posts that go into more detail but this should about cover it.
Gibson99 said:
i've been running the M7 snapshot of CM11 for about a month now. my only complaint about battery isn't really the rom's fault - if i'm watching a lot of netflix or youtube, the battery goes down faster. that's not really a surprise though.
i'm still pretty new to the relay though i've had a couple other androids before this one. but i suggest you use TWRP (Team Win Recovery Project) instead of CWM (clockworkmod) for your recovery. it's got a gui and is a bit easier to use when flashing roms and doing wipes and stuff.
bsically the process is to boot your phone into download mode, flash twrp, then reboot the phone into twrp, wipe everything, then flash CM and gapps (if you want google apps like gmail, play store, etc). then wipe cache/dalvik/factory reset (because some roms are unstable if you simply flash without doing the second wipe). no need to try to inject SU (superuser) or anything since pretty much all custom roms are already rooted. there are other posts that go into more detail but this should about cover it.
Click to expand...
Click to collapse
Where can I download TWRP for the Relay?
openletter said:
Where can I download TWRP for the Relay?
Click to expand...
Click to collapse
search for it in the relay forum - it has its own thread, i think in the dev sub-forum. instructions to install it are the same as cwm, just use the twrp file instead of cwm.
Gibson99 said:
search for it in the relay forum - it has its own thread, i think in the dev sub-forum. instructions to install it are the same as cwm, just use the twrp file instead of cwm.
Click to expand...
Click to collapse
Thanks - I was just discovering that forum when you replied. I had looked right passed it initially since there isn't usually anything for me in dev forums for other projects I use.
** Was not sure where to post this.
Today I was successful in building CM 12 for the first time using Docker on Ubuntu 14. The build went fine but when I try to flash my phone with the cm-12-2015-02-01.zip file the flashing goes fine without any errors but when I reboot the device it gets stuck on the Google boot screen and doesn't process to the CM boot screen. I have tried doing a full clean flash, as well as wiping cache(s).
This does not happen if I try flashing an official build from the CM site. This has something to do with my build but I cant figure out what because the build goes fine when I run it.
Thanks for the help in advance
Did you make sure you're building for hammerhead?
Lethargy said:
Did you make sure you're building for hammerhead?
Click to expand...
Click to collapse
Yes I definitely built for hammerhead.
waleed_k said:
Yes I definitely built for hammerhead.
Click to expand...
Click to collapse
Try running a repo sync and rebuild
Hi,
Did you figure it out? We are running into the same issue, build in plain Ubuntu is fine, but if we build in Docker container, then the phone stuck on boot screen.
waleed_k said:
** Was not sure where to post this.
Today I was successful in building CM 12 for the first time using Docker on Ubuntu 14. The build went fine but when I try to flash my phone with the cm-12-2015-02-01.zip file the flashing goes fine without any errors but when I reboot the device it gets stuck on the Google boot screen and doesn't process to the CM boot screen. I have tried doing a full clean flash, as well as wiping cache(s).
This does not happen if I try flashing an official build from the CM site. This has something to do with my build but I cant figure out what because the build goes fine when I run it.
Thanks for the help in advance
Click to expand...
Click to collapse
Still have not figured this out.
I think this is a generic issue about building Android in Virtual Environment (chroot, lxc, docker).
I know that someone else says that Android can be built in VE without any problems, in our company, we do have some Android projects which can be built in VE without any problems too, but somehow, some projects cannot, hope that someone knows Android and VE better can help on this.
waleed_k said:
Still have not figured this out.
Click to expand...
Click to collapse
Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
duratto said:
Hi guys, been off the scene for quite a while, so please forgive me if I'm not really up to date with the latest.
I own a OPO anad currently I have Cyanogen 12.0 installed. Lately my phone started to play up, not sure if I got some kind of malware but I thought it was a good occasion to update my ROM. Historically, I've always used CM but they seem to have disappeared completely (they used to have a nice website with all the phone models and the corresponding compatible ROMs, but I suppose that since when they went out of business things might have changed quite a bit). Can they be found somewhere? If not, I'd appreciate any advice on what ROM would be good to have - considering though that even my Teamwin Recovery needs updating as somehow it thinks I'm on an older version of android.
Cheers
Click to expand...
Click to collapse
Firstly,this should be in QnA..
Secondly,
For latest recovery,
https://forum.xda-developers.com/oneplus-one/development/recovery-twrp-3-0-3-k1-t3563692
Recommended rom- https://forum.xda-developers.com/on...m-kernel-unofficial-lineageos-14-1-3-t3626403
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
duratto said:
thanks, do I need to install the recovery first and then the ROM? Also, are there any instructions for the recovery here or should I have a look on the net?
thanks
Click to expand...
Click to collapse
Yes,to flash recovery the process is same as you did for the previous Twrp that is now on your device.