Develop Bugs

Plenty of errors after updating

I have updated my rom to CM12 a while ago and after that my recovery (TWRP) stopped working. Yesterday, I finaly decided to fix it, so I flashed CWM (it worked!) and I tried to update my rom to the latest CM 12 nightly build. When it booted into the OS, I get a bunch of error for Text-to-speed, Google play service, UI System, etc. I tried to wipe, reflash, reinstall gapps... same thing. Then, I tried to only install the os : Wipe, install the rom, boot still get the errors.
Anyone, has any idea on how to fix this?
I have a SGH-M919 (Samsung galaxy S4 - T-Mobile), I downloaded the JFLTETMO version of CM12.

You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.

PanchoPlanet said:
You should start over.
Factory reset, reflash a stable version of cm12 and stay away from the nightlies.
Nightlies are experimental changes that are put out so you can try them on your phone. They don't always go well and your left with a phone that doesn't work.
If you need your phone to function properly you may consider stable CM11 or a stock rom.
Pp.
Click to expand...
Click to collapse
Thanks for the reply, I downloaded a Stable build of CM11 and flashed it, but my phone kept rebooting in Recovery. I noticed that the sdcard/ folder is empty like if nothing was installed in the phone. I decided to flash TWRP. And when i flash the rom I get an error:
"E: Unable to open zip file."
"Error flashing /sdcard/rom3.zip"
Edit : Forget about the error I think the file was corrupted during transfer. Still getting the boot into recovery thing.

Try removing your SDCARD from the phone.
Turn phone off, remove SD card and start over. This may allow you to flash without errors.
Afterwards if successful tryout phone and then reinsert SD card.
Pp.

Problems after installing CM12.1 nightlies

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

Recovery...super confused please help.

I love this phone but recently switched to a note 3 and love it as well. However, my wife is having problems with her phone and thought it time to factory reset to remedy the problem. However I figured i should put a custom rom on her E980 if I'm going to go through all that, I'd experiment with mine. Wow, what's with installing a custom recovery? I tried numerous ways after spending countless hours yesterday and nothing seemed stable. I had to "tot" back to stock 4.4 numerous times.
Could someone explain the procedure please as after I root how do I install custom recovery and what else I need to install and what order. Also, a good stable rom for my with based off of lollipop.

mikelets456 said:
I love this phone but recently switched to a note 3 and love it as well. However, my wife is having problems with her phone and thought it time to factory reset to remedy the problem. However I figured i should put a custom rom on her E980 if I'm going to go through all that, I'd experiment with mine. Wow, what's with installing a custom recovery? I tried numerous ways after spending countless hours yesterday and nothing seemed stable. I had to "tot" back to stock 4.4 numerous times.
Could someone explain the procedure please as after I root how do I install custom recovery and what else I need to install and what order. Also, a good stable rom for my with based off of lollipop.
Click to expand...
Click to collapse
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.

ShadySquirrel said:
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
Click to expand...
Click to collapse
i can't find anyway to root my phone neither i think if there is any recovery installed in my phone (idk if that's even possible) because it doesn't go to recovery at boot
I am already on stock lollipop for F240L but it have too much blootware.
edit: so it turns out recovery is installed on mobile but in an attempt to root i ran into another error. when the program(root software) it restarts Phone into recovery, i received this error. "NO command" and i cant push updates thorough ADB.
edit2: after pressing random keys it started working but when i try to push update through adb it say
"you need adb 1.0.32 or newer to sideload to this device." any help?

ShadySquirrel said:
From my personal experience, easiest 'path' would be to start from stock Jellybean, then to install recovery via Freegee after rooting, and then to update that recovery to latest TWRP (process I'm using for years now).
If you really want to start with KK as base, you should install GPRO_Recovery.apk and install a recovery from there, after you obtain root. After that, update that ancient recovery to TWRP and you're good to go.
For AOSP LP ROMs, you have to choose between 4 available ROMs (there are maybe more, but those mentioned should be updated more frequently) - CyanogenMod, BlissPop, Carbon and SlimLP. There are some builds of Resurrection Remix and AICP but I know nothing about them because I have never used them. Others are pretty much stable for everyday usage and should play nice on your e980s.
Start with one of four ROMs mentioned above and you won't have any troubles/issues.
Click to expand...
Click to collapse
Tayyab.Hasan said:
i can't find anyway to root my phone neither i think if there is any recovery installed in my phone (idk if that's even possible) because it doesn't go to recovery at boot
I am already on stock lollipop for F240L but it have too much blootware.
edit: so it turns out recovery is installed on mobile but in an attempt to root i ran into another error. when the program(root software) it restarts Phone into recovery, i received this error. "NO command" and i cant push updates thorough ADB.
edit2: after pressing random keys it started working but when i try to push update through adb it say
"you need adb 1.0.32 or newer to sideload to this device." any help?
Click to expand...
Click to collapse
I did it. went back to KK using download mode, rooted and now i will flash new ROM. Thanks.

Flashing ROM reboot issues, advice massively appreciated.

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

Nexus 7: Old CM builds won't install

For quite awhile now, I have had a nexus 7 (2013) wifi 16GB (flo). CM13 was my first custom rom. Since then, I have upgraded to the latest official Lineage 14.1 build. Now, I never use my old nexus.
Yesterday, I wanted to put together a little game station with it, centering around Wii remote support. I've read that the last android version to support the WiiMotes was 4.1. Unfortunately the N7 was launched with 4.3, so there is no official 4.1 build for the phone. I then read that CM used to have their own support for the controller. Can anyone verify if this is true? From the wayback machine, I downloaded and installed CM13, which worked fine, but while the WiiMote would "connect", it didn't actually do anything, and all for lights on the controller flashed indefinitely. Next, I went to the oldest stable build of CM available: CM10.2 (android 4.3). When I went into the latest version of TWRP to install it, I wiped everything except internal storage, and flashed the zip. I've tried this several times, and it always leads to one of 2 outcomes: either succeeds with the following output:
Code:
updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/cm-10.2.1-flo.zip'
Checking for digest file...
Skipping digest check: no Digest file found
updating partition details...
...done
This results in an unbootable system.
Usually successful OS flashes have a lot more output than this, right?
Other times it fails. (Using the exact same file)
I'm having trouble reproducing this error wile I write this, but it was something along the lines of
Checking symlinks...
some symlinks failed.
I know the file was downloaded correctly, because it matches the checksum on the backup of the site.
I would post a wayback machine link but XDA won't let me.
LineageOS and CM13 install just fine, so the tablet isn't bricked.
So, can anyone
-help me install this old build of CM10
-Tell me a way to use wiimotes with a newer OS
-direct me to some obscure build of android 4.1 or older (WiiMotes used to work perfectly in 4.1 for all devices) for flo (I doubt this exists but maybe)
Remember, my N7 is otherwise useless to me, so I don't really care what it takes to make this work.

rondnelson99 said:
For quite awhile now, I have had a nexus 7 (2013) wifi 16GB (flo). CM13 was my first custom rom. Since then, I have upgraded to the latest official Lineage 14.1 build. Now, I never use my old nexus.
Yesterday, I wanted to put together a little game station with it, centering around Wii remote support. I've read that the last android version to support the WiiMotes was 4.1. Unfortunately the N7 was launched with 4.3, so there is no official 4.1 build for the phone. I then read that CM used to have their own support for the controller. Can anyone verify if this is true? From the wayback machine, I downloaded and installed CM13, which worked fine, but while the WiiMote would "connect", it didn't actually do anything, and all for lights on the controller flashed indefinitely. Next, I went to the oldest stable build of CM available: CM10.2 (android 4.3). When I went into the latest version of TWRP to install it, I wiped everything except internal storage, and flashed the zip. I've tried this several times, and it always leads to one of 2 outcomes: either succeeds with the following output:
This results in an unbootable system.
Usually successful OS flashes have a lot more output than this, right?
Other times it fails. (Using the exact same file)
I'm having trouble reproducing this error wile I write this, but it was something along the lines of
Checking symlinks...
some symlinks failed.
I know the file was downloaded correctly, because it matches the checksum on the backup of the site.
I would post a wayback machine link but XDA won't let me.
LineageOS and CM13 install just fine, so the tablet isn't bricked.
So, can anyone
-help me install this old build of CM10
-Tell me a way to use wiimotes with a newer OS
-direct me to some obscure build of android 4.1 or older (WiiMotes used to work perfectly in 4.1 for all devices) for flo (I doubt this exists but maybe)
Remember, my N7 is otherwise useless to me, so I don't really care what it takes to make this work.
Click to expand...
Click to collapse
You have to wipe internal storage. To go back from anything 5.0 and up to anything lower.
Format data along with wiping internal storage.
So it looks like you tried everything except the actual solution... LoL.
Good luck

madbat99 said:
You have to wipe internal storage. To go back from anything 5.0 and up to anything lower.
Format data along with wiping internal storage.
So it looks like you tried everything except the actual solution... LoL.
Good luck
Click to expand...
Click to collapse
I didn't mention it, but I actually did wipe internal storage, and then transferred the zip from the computer via twrp.

rondnelson99 said:
I didn't mention it, but I actually did wipe internal storage, and then transferred the zip from the computer via twrp.
Click to expand...
Click to collapse
Format data (simple wipe usually isn't enough) and type yes in TWRP

madbat99 said:
Format data (simple wipe usually isn't enough) and type yes in TWRP
Click to expand...
Click to collapse
OK so I tried that, but it still doesn't work. Gets stuck on the Google screen when I reboot. I am supposed to wipe system first, right? Do I need to flash a 4.3 system image as well or something like that?
Thanks for all your help!

rondnelson99 said:
OK so I tried that, but it still doesn't work. Gets stuck on the Google screen when I reboot. I am supposed to wipe system first, right? Do I need to flash a 4.3 system image as well or something like that?
Thanks for all your help!
Click to expand...
Click to collapse
Wipe everything. Format data, and flash the ROM of choice. If it sits for a while on Google, force a reboot by holding power.
If that doesn't work try flashing a 4.3 factory image and then Boot it up then flash to CM10 ROM you want to use
make sure you haven't resized your partitions or anything crazy like that make sure your data is formatted to ext4 not f2fs. basically undo any changes you've done as you've been flashing ROMs for the life of this tablet

madbat99 said:
Wipe everything. Format data, and flash the ROM of choice. If it sits for a while on Google, force a reboot by holding power.
If that doesn't work try flashing a 4.3 factory image and then Boot it up then flash to CM10 ROM you want to use
make sure you haven't resized your partitions or anything crazy like that make sure your data is formatted to ext4 not f2fs. basically undo any changes you've done as you've been flashing ROMs for the life of this tablet
Click to expand...
Click to collapse
where can i get a copy of a 4.3 factory image ?

https://developers.google.com/android/images
Sent from my Asus P027 using XDA Labs