I've had CM10.0 installed on my Verizon GNex since it was released. Just today, I decided to update to the newest experimental CM10.1. I was wary about an experimental, but it displayed as a stable release, so I figured I would give it a shot. After having the 10.1 experimental running for about 10 minutes, I decided to see if I could flash back to 10.0, because there was no option to add/sync my google account in 10.1 experimental. I saw that 10.0 was still able to be flashed from the updater within 10.1 experimental, so I started the installation. Everything seemed fine with the flash, but then when it rebooted, it just got stuck looping the CM boot screen.
I can still access the bootloader and get into ClockworkMod Recovery 6.0.1.5. What can/should I do to get CM10.0 booting? If it's not possible, how would I go back to stock firmware?
Thanks all!
All fixed now. Thank you! I used CWM Recovery to push the newest CM nightly and gapps to the sdcard, then just flashed them from within CWM and rebooted. All good now.
PHEW!
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
Q&A for [ROM] Candy5 Unofficial | 5.1.1 | 4.30.15
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Candy5 Unofficial | 5.1.1 | 4.30.15. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Awesome port
Brilliant job, man!! The ROM seems stable enough for a daily driver, even from a dirty flash from Hashcode's CM12 port. Just a few bugs:
1) When choosing to show the seconds for the time, the seconds show up after the PM/AM text. The attached screenshot demonstrates this (I used the CandyROM sweeteners for the Adventure Time themed navbar).
2) When I paired my Bluetooth keyboard, I was able to type the pairing code as prompted, but even though Android recognizes it as an input device, I'm not able to type with the keyboard. This issue didn't occur in CM11, but it was prominent in Hash's CM12 ports. Maybe it's a lollipop issue in general?
3) the navigation ring targets look awfully large (also shown in the screenshot). This issue appeared before (and after, as well) I customised the navigation ring targets, and it did not do this in Hashcode's port.
Otherwise, this ROM is excellent for a first port!
EDIT: Adding screenshot link: http://imgur.com/dubEMEH
Some games crash and can't be started. There is no not responding or force closed messages., they just crash and returns to home screen. Is it a rom problem or am I doing something wrong?
Does it work on the LTE version. Does the LTE work on it ? Thanks!
[ROM] Candy5 Unofficial | 5.1.1 | 4.30.15 checking connection has gone on for 3 hours
well like the title says i have just flashed this rom on my kindle and the i started it up and connected to wi-fi and it says checking connection for 3 hours now and i tried reboot several times now but nothing seems to get me past this screen???
Lynn472 said:
well like the title says i have just flashed this rom on my kindle and the i started it up and connected to wi-fi and it says checking connection for 3 hours now and i tried reboot several times now but nothing seems to get me past this screen???
Click to expand...
Click to collapse
Did you do a dirty flash from Hashcode's CM12 builds or CM11 nightlies? Try clearing dalvik and cache in TWRP and then reboot. If that fails, I would suggest doing an advanced wipe in TWRP (check all boxes, including system), rebooting into recovery again, and then re-flashing the ROM.
monster1612 said:
Did you do a dirty flash from Hashcode's CM12 builds or CM11 nightlies? Try clearing dalvik and cache in TWRP and then reboot. If that fails, I would suggest doing an advanced wipe in TWRP (check all boxes, including system), rebooting into recovery again, and then re-flashing the ROM.
Click to expand...
Click to collapse
umm no i just got a custom recovery installed but i dident wipe data or anything so ill go try that and re do it
Lynn472 said:
umm no i just got a custom recovery installed but i dident wipe data or anything so ill go try that and re do it
Click to expand...
Click to collapse
With that in mind, you must have come from stock - did you make backups in case you wanted to revert back to stock firmware? Generally speaking, if switching from Amazon's stock firmware to CM or CM to AOKP (differing ROM bases), you should make backups and then wipe system, data, and both caches (Dalvik and regular). Doing so ensures that no conflicts arise when using the new ROMs. If you do encounter problems, the backups ensure you have software to fall back on. If you're flashing an update to an existing ROM (like you're flashing a newer CM ROM on top of an older CM build), then it's OK to dirty flash (just flash the new ROM zip without clearing data or system. Also, make sure you have the latest TWRP release (you can flash that update just like any regular ROM zip, download here: http://forum.xda-developers.com/showthread.php?t=2218802). The reason why you would need Hashcode's port of TWRP 2.8.3.0 for the HD 8.9 is because 2.8.3.0 has support for Lollipop builds, and if you try to flash a TWRP build from TeamWin's website, you'll end up with a brick.
monster1612 said:
With that in mind, you must have come from stock - did you make backups in case you wanted to revert back to stock firmware? Generally speaking, if switching from Amazon's stock firmware to CM or CM to AOKP (differing ROM bases), you should make backups and then wipe system, data, and both caches (Dalvik and regular). Doing so ensures that no conflicts arise when using the new ROMs. If you do encounter problems, the backups ensure you have software to fall back on. If you're flashing an update to an existing ROM (like you're flashing a newer CM ROM on top of an older CM build), then it's OK to dirty flash (just flash the new ROM zip without clearing data or system. Also, make sure you have the latest TWRP release (you can flash that update just like any regular ROM zip, download here: http://forum.xda-developers.com/showthread.php?t=2218802). The reason why you would need Hashcode's port of TWRP 2.8.3.0 for the HD 8.9 is because 2.8.3.0 has support for Lollipop builds, and if you try to flash a TWRP build from TeamWin's website, you'll end up with a brick.
Click to expand...
Click to collapse
ive got this revovery not twrp
http://forum.xda-developers.com/showthread.php?t=2721761
Lynn472 said:
ive got this revovery not twrp
http://forum.xda-developers.com/showthread.php?t=2721761
Click to expand...
Click to collapse
OK, try clearing data, system, and both caches and then flashing the ROM from PhilZ Touch. If you get the same issue again, I would boot into fastboot mode on the Kindle and then flash the TWRP 2.8.3.0 recovery img file (https://goo.im/devs/Hashcode/jem/kfhd8-twrp-2.8.3.0-recovery.img) from there. Best of luck!
Is there a TV Out problem/lack of support?
Everything went perfectly until I tried to send kodi to TV, the app would stall/crash to home and at one point looked just like a broken TV with an interference pattern, requiring a hard shutdown.
Does the sweetener pack work on JEM? Does the pack get flashed or unzipped? What's in it?
Sent from my Amazon Jem using XDA Free mobile app
BobJayJr said:
Does the sweetener pack work on JEM? Does the pack get flashed or unzipped? What's in it?
Sent from my Amazon Jem using XDA Free mobile app
Click to expand...
Click to collapse
It worked for me. I changed the navigation bar icons with no problem. But with aroma on twrp it gets a little complicated.. It works though. See in the main rom thread. I tried to explain there.
Having the same problem with getting stuck on the "Checking connection..." screen. Coming from CM12, but I did a full wipe in TWRP 2.8.3.0 (checked all the boxes, rebooted back into recovery) then installed the ROM and the GAPPS from the link provided in the post.
Bluetooth got problem
Hi everybody,
I flashed the ROM candy5-release.v2.1.1-20150429-OFFICIAL-jem.zip on Kindle Fire HD 8.9 LTE version and got this error message:
Unfortunately, bluetooth share has stopped
Click to expand...
Click to collapse
Temporarily, I must move the folder Bluetooth in /system/app/ to another place and reboot the OS to disable Bluetooth.
Are there any Lollipop version for KFHD8.9 LTE?
Does anyone got this problem? Any idea?
Thanks.
Can't install "Google Play Games". Error on installation: -505
What's new in this one?
Anyone else having an issue with settings? Initially I dirty flashed Candy5 v2.8 over v2.5. I activated developer options but encountered a "settings stopped" error while trying to access developer options. The "Settings Stopped" issue continued after a clean install. I can't access root. Any suggestions/workaround?
Sent from my Amazon Jem using XDA Free mobile app
BobJayJr said:
Anyone else having an issue with settings? Initially I dirty flashed Candy5 v2.8 over v2.5. I activated developer options but encountered a "settings stopped" error while trying to access developer options. The "Settings Stopped" issue continued after a clean install. I can't access root. Any suggestions/workaround?
Sent from my Amazon Jem using XDA Free mobile app
Click to expand...
Click to collapse
Same problem - "settings stopped" on v.2.8. I went back to version v.2.5, it is more stable.
I'm also returning to 2.1. 2.8, though initially appearing stable, became increasing unstable. Messages like "Unfortunately settings has stopped", "Unfortunately Amazon has stopped", "Unfortunately Android has stopped" became more frequent even after reflashing (clean reflash) the system. Chrome browser also seemed to become more erratic - especially if there are multiple frames per page.
Sent from my KFAPWI using XDA Free mobile app
For some reason, my phone doesn't boot after updating my current rom or wiping and installing a new one.
After the install, the boot animation is displayed for about 1-2 seconds. It then reboots and gets stuck during the boot animation. I've let it sit for an hour, so I know I'm not just being impatient.
Funny thing is that I'm able to restore my nandroid without issue. I'm currently running CM 12.1. I've tried dirty flashing a newer version of 12.1, clean installing a newer version of 12.1 and also clean installing various other roms. The latest I tried was the newest android revolution HD. I'm running the latest TWRP (2.8.7.0).
Can anyone think of why this might be happening? Any troubleshooting tips are welcome.
Thanks.
Got it working with Viper One.
MaxGame said:
Got it working with Viper One.
Click to expand...
Click to collapse
I was gonna suggest.
I rooted my phone yesterday fine and made a backup of my oxygen OS (original rom).
I am definitely successfully unlocked and rooted, and TWRP newest version is running.
I have tried so much to get a new rom running correctly I have tried both resurrection remix official and unofficial:
https://forum.xda-developers.com/on...evelopment/op3-3t-resurrection-remix-t3754941
I have also tried official paranoid android, but every time it starts up I get two issues the first is the error saying "android.media has stopped" the more serious being the fact that no matter which rom I flash it always begins force restarting over and over again, I get into the OS fine, have a scroll around and around every 2 mins or so it just force reboots, then it comes back and is fine for 2 mins then same again.
It has happened with the official and unofficial versions of resurrection remix and also happens exactly the same with paranoid android. I have no idea what else to try at this point.
The process I have been using for flashing is this:
1. Boot into TWRP recovery
2. Wipe everything but internal storage.
3. Install my rom.
4. Reboot.
5. Starts up successfully and then falls back into the standard boot loop and the android.media error.
I have also tried it with GAPPS which was throwing some setup wizard has stopped error, so for now I am just attempting to get an actual rom running without constantly restarting.
Any help is massively appreciated, I am tech savvy, hence why this is annoying me even more.
Thanks,
Kieran
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
jeffrey268 said:
Have you tried going back to the latest official Oxygen OS (Stable or OB)?
Click to expand...
Click to collapse
My backup is the original oxygen and this restores fine and works fine just as soon as I try to flash a new rom it just keeps restarting every few minutes, I dont really know what else to try.
Also to add I sometimes see this issue when I attempt to flash certain roms..... 'assert failed: op3.verify_modem("2017-11-16") == 1'
Use the recommended firmware by the rom. Also you can't flash most roms without Gapps.
1. Flash proper firmware
2. Flash the rom
3. Flash Gapps or something similar.
4. Flash any additional kernel (optional).
5. Flash SuperSU or Magisk.
The assert failed littery tells you that you use using the wrong modem // firmware.
my first question which custom Rom you installed every Rom developer say it is stable but only few has been stable as rock . i tried everything but settled with AICP Rom. and then try to use GAPP as ARM64 android 8.1
u have first install Rom and then GAPP then magisk or Superuser anything which u refer
https://forum.xda-developers.com/on...e-development/wip-official-aicp-13-0-t3713637
this is the Rom which i use it . .they are stable and also update it weekly thrice ..
if u like it you can install this ROM