Database Info

Cannot install 9MB OTA update

Yesterday I tried sideloading the 30O update manually from Android Police, the sideloading of 30O kept failing so I used the modified version on the XDA forums which skips the errors and installs it anyway. After this being successful I woke up this morning to see another 9MB update, this is apparently a patch for the update.
I went to install this but it has the same error as the 30O install had,
assert failed: apply_patch_check("/system/framework/core.odex","numbers and letters here","numbers and letters here")
E:Error executing update binary un zip '/cache/cm-bacon-numbere-to-numbers-signed.zip'
Then it fails to flash.
Does anyone know how I can fix this? Wiping Cache and Dalvik Cache does not help.

oscarandjo said:
Yesterday I tried sideloading the 30O update manually from Android Police, the sideloading of 30O kept failing so I used the modified version on the XDA forums which skips the errors and installs it anyway. After this being successful I woke up this morning to see another 9MB update, this is apparently a patch for the update.
I went to install this but it has the same error as the 30O install had,
assert failed: apply_patch_check("/system/framework/core.odex","numbers and letters here","numbers and letters here")
E:Error executing update binary un zip '/cache/cm-bacon-numbere-to-numbers-signed.zip'
Then it fails to flash.
Does anyone know how I can fix this? Wiping Cache and Dalvik Cache does not help.
Click to expand...
Click to collapse
You have flashed some mod to your system, which prevents the update from applying.
The only solution is flashing the 25R system.img manually, then sideloading the 30O big update, followed by the small one.

Dzhedaj said:
You have flashed some mod to your system, which prevents the update from applying.
The only solution is flashing the 25R system.img manually, then sideloading the 30O big update, followed by the small one.
Click to expand...
Click to collapse
I don't think I've flashed any mods through recovery, but I have done stuff like installing busybox, xposed, root, I assume this could mess it up too?
One more question, I am currently successfully on 30O, surely flashing 25R would cause a softbrick as you cannot go back to older versions with CyanogenMod?
Should I just flash the system.img from 30O big update and then try to install the small one?
What do you think?

oscarandjo said:
I don't think I've flashed any mods through recovery, but I have done stuff like installing busybox, xposed, root, I assume this could mess it up too?
One more question, I am currently successfully on 30O, surely flashing 25R would cause a softbrick as you cannot go back to older versions with CyanogenMod?
Should I just flash the system.img from 30O big update and then try to install the small one?
What do you think?
Click to expand...
Click to collapse
Where does it say you can't go back to older versions? If you have a previous backup or something you can roll back no problems. You need to remove Xposed and start again.
Transmitted via Bacon

timmaaa said:
Where does it say you can't go back to older versions? If you have a previous backup or something you can roll back no problems. You need to remove Xposed and start again.
Transmitted via Bacon
Click to expand...
Click to collapse
I don't have any backups from that version. I was under this impression because in the CM nightlies if you ever flashed a nightly from before your current nightly it caused a softbrick.
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?

oscarandjo said:
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
Click to expand...
Click to collapse
It's probably something you installed from xposed. But your solution should work.

apristel said:
It's probably something you installed from xposed. But your solution should work.
Click to expand...
Click to collapse
I'm going to try uninstalling xposed and my modules before reflashing all of that.

oscarandjo said:
I'm going to try uninstalling xposed and my modules before reflashing all of that.
Click to expand...
Click to collapse
Removed Xposed and uninstalled all of my modules and I'm getting the same error as the beginning, I'm gonna try the flashing solution now.

oscarandjo said:
Removed Xposed and uninstalled all of my modules and I'm getting the same error as the beginning, I'm gonna try the flashing solution now.
Click to expand...
Click to collapse
You should always have a backup on your phone. Especially the original setup at least. when properly rooted or not you can go from 4.4.4 to 4.4.2 or whatever if you like. Let us know how the flashing goes and do yourself a favor and do more reading and less flashing at least till you fully know all you can and can't do.

playya said:
You should always have a backup on your phone. Especially the original setup at least. when properly rooted or not you can go from 4.4.4 to 4.4.2 or whatever if you like. Let us know how the flashing goes and do yourself a favor and do more reading and less flashing at least till you fully know all you can and can't do.
Click to expand...
Click to collapse
I haven't actually been flashing anything though, I just had Xposed and some minor modules like TabletMetrics and the Greenify module installed.
Anyway, I'll make sure to do backups through recovery every so often. I've got a lot of stuff backed up with TitaniumBackup

oscarandjo said:
I haven't actually been flashing anything though, I just had Xposed and some minor modules like TabletMetrics and the Greenify module installed.
Anyway, I'll make sure to do backups through recovery every so often. I've got a lot of stuff backed up with TitaniumBackup
Click to expand...
Click to collapse
nandroids are good for a lot of different reasons. TB are fine but there may be times where simply restoring your phone to a time when all worked fine may be highly necessary. Unstoppable FC's and unknown basebands have been times where a nandroid has helped out for some users

playya said:
nandroids are good for a lot of different reasons. TB are fine but there may be times where simply restoring your phone to a time when all worked fine may be highly necessary. Unstoppable FC's and unknown basebands have been times where a nandroid has helped out for some users
Click to expand...
Click to collapse
I see, thanks.

oscarandjo said:
I don't have any backups from that version. I was under this impression because in the CM nightlies if you ever flashed a nightly from before your current nightly it caused a softbrick.
So to clarify, I get the 25R system.IMG and flash it to my 30O device, once I've done this, complete the 30O OTA and then the mini update after that?
This will not cause any problems?
Click to expand...
Click to collapse
Flashing backwards may only cause problems if you're dirty flashing. So if you're ever moving backwards you must go clean. Anyway, it looks like you're all set judging by the other posts here now :good:
Transmitted via Bacon

Does anyone have a 25R mirror? Mega.co.nz would be best. Cyanogen's servers are being awfully slow.

timmaaa said:
Flashing backwards may only cause problems if you're dirty flashing. So if you're ever moving backwards you must go clean. Anyway, it looks like you're all set judging by the other posts here now :good:
Transmitted via Bacon
Click to expand...
Click to collapse
Oh. I didn't want to lose any data though...
Does this apply even if I'm just flashing 25R's system.img and will update to 30O again straight after?

oscarandjo said:
Oh. I didn't want to lose any data though...
Does this apply even if I'm just flashing 25R's system.img and will update to 30O again straight after?
Click to expand...
Click to collapse
Can I ask a question and anyone can answer this - Whats the big deal about setting your phone up from scratch knowing that doing it this way will have it bug free. Its about a half hour to reset a phone up lets say.
I will let you know of a program called APP2Zip its old but you can back all your stuff up in a flashable zip file. Its dirty and any issues like FC's you have to handle but it does work.
I prefer doing it all from scratch but at least I know I have a clean canvas

playya said:
Can I ask a question and anyone can answer this - Whats the big deal about setting your phone up from scratch knowing that doing it this way will have it bug free. Its about a half hour to reset a phone up lets say.
I will let you know of a program called APP2Zip its old but you can back all your stuff up in a flashable zip file. Its dirty and any issues like FC's you have to handle but it does work.
I prefer doing it all from scratch but at least I know I have a clean canvas
Click to expand...
Click to collapse
Because I've already had to do this before now, it's annoying to have to wipe it all over again after just setting it up.
I guess I'll have to do this...
Flash system.img of 25R, update to 30O and then the mini 30O patch. Then re-root using TWRP, then restore my stuff using Titanium Backup and set everything up as it was, wasting an hour or two. :/
Anyway, I understand this is the best way to do it, thanks for the help.

oscarandjo said:
Because I've already had to do this before now, it's annoying to have to wipe it all over again after just setting it up.
Click to expand...
Click to collapse
Ok, I guess doing it right is not so annoying to me... Enjoy and hope you find a suitable workaround to save your data :good:

playya said:
Ok, I guess doing it right is not so annoying to me... Enjoy and hope you find a suitable workaround to save your data :good:
Click to expand...
Click to collapse
Yeah, does Titanium Backup backup large sideloaded apps?

oscarandjo said:
Yeah, does Titanium Backup backup large sideloaded apps?
Click to expand...
Click to collapse
Pro version will restore all at one time. That's not recommended especially if you are restoring from a different version of android. Its all at your own risk. I been there and for me shortcuts were not worth it always for me at least...
1+1 Homie......

Cannot update to 30O

I have been holding off from updating to 30O since it came out because of battery issues, however now that 33R is rolling out im trying to install 30O in preparation but am unable to do so. Whenever I hit the "Download Update" button through settings nothing happens, I have tried restarts and cache wipes with no luck. Everything on the phone is still stock.
Any suggestions?

Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.

teh roxxorz said:
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
I am trying to update via ota not a custom recovery does that make a difference?

teh roxxorz said:
Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
I don't think that's possible; the OTAs are incremental.

Joe-Pk said:
I am trying to update via ota not a custom recovery does that make a difference?
Click to expand...
Click to collapse
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.

teh roxxorz said:
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
Click to expand...
Click to collapse
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.

dr3amsINdigital said:
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
Click to expand...
Click to collapse
Well yea. Sorry if my wording was a bit convoluted; but I just see it being a waste of time to overwrite the custom recovery. But also from my experience OTA just goes with stock recovery, so thank you for your input.

Joe-Pk said:
I have been holding off from updating to 30O since it came out because of battery issues, however now that 33R is rolling out im trying to install 30O in preparation but am unable to do so. Whenever I hit the "Download Update" button through settings nothing happens, I have tried restarts and cache wipes with no luck. Everything on the phone is still stock.
Any suggestions?
Click to expand...
Click to collapse
You can download the OTA updates from somewhere like Android Police and flash them manually.
teh roxxorz said:
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
This is irrelevant.
Joe-Pk said:
I am trying to update via ota not a custom recovery does that make a difference?
Click to expand...
Click to collapse
It makes zero difference.
dr3amsINdigital said:
I don't think that's possible; the OTAs are incremental.
Click to expand...
Click to collapse
It is possible by using the fastboot images from the cyngn site.
teh roxxorz said:
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
Click to expand...
Click to collapse
Not true.
dr3amsINdigital said:
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
Click to expand...
Click to collapse
Exactly.
teh roxxorz said:
Well yea. Sorry if my wording was a bit convoluted; but I just see it being a waste of time to overwrite the custom recovery. But also from my experience OTA just goes with stock recovery, so thank you for your input.
Click to expand...
Click to collapse
An OTA can be flashed by stock recovery or TWRP on this device.
Transmitted via Bacon

I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.

Joe-Pk said:
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Click to expand...
Click to collapse
You can manually flash updates while stock.

Joe-Pk said:
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Click to expand...
Click to collapse
dr3amsINdigital said:
You can manually flash updates while stock.
Click to expand...
Click to collapse
Yes you can. Rename file to update.zip and flash through stock recovery. Please make sure you give out accurate information if you're going to answer questions.
Transmitted via Bacon

timmaaa said:
Yes you can. Rename file to update.zip and flash through stock recovery. Please make sure you give out accurate information if you're going to answer questions.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm not sure if you read my post wrong or not, but I said you can manually flash updates while stock. If you did read it correctly and are just complaining that I didn't give a detailed answer with instructions, I wasn't exactly sure of the process, so I left that to someone else. Some helpful information is better than none.

dr3amsINdigital said:
I'm not sure if you read my post wrong or not, but I said you can manually flash updates while stock. If you did read it correctly and are just complaining that I didn't give a detailed answer with instructions, I wasn't exactly sure of the process, so I left that to someone else. Some helpful information is better than none.
Click to expand...
Click to collapse
My sincerest apologies! I completely misread your post.
Transmitted via Bacon

I ended up just flashing manually using files from android police and stock recovery, however the download update button still didnt work even when i was trying to go to 33R. If I get some time ill get around to factory resetting and trying again because as far as i can tell there is no reason for it not to work.

You could always sideload a OTA if you have the zipfile.
Code:
adb reboot recovery
in recovery choose "ADB Sideload"
Code:
adb sideload update.zip

[Q] Root and keep CM11S?

Hi, apologies if this is the wrong forum but I have just received my OnePlus One and want to root it before I really start using it. However, I don't want to miss out on CM11S. If I flash TWRP/CWM and flash a SU zip will I be able to update through the CM11S OTAs?
I couldn't see CM11S ROMs on get.cm so I'm a little confused.
Thanks in advance.

r0brimmer said:
Hi, apologies if this is the wrong forum but I have just received my OnePlus One and want to root it before I really start using it. However, I don't want to miss out on CM11S. If I flash TWRP/CWM and flash a SU zip will I be able to update through the CM11S OTAs?
I couldn't see CM11S ROMs on get.cm so I'm a little confused.
Thanks in advance.
Click to expand...
Click to collapse
So far, I haven't updated via OTA from OnePlus. I just manually flash because it is always faster than waiting for an update to get pushed to your specific device. However, with other devices in the past (Nexus 10), if I have kept the stock kernel, I have been notified of updates via OTA. If I were you, I would just root, flash Franco Kernel and update manually in the future. It is very easy to do once you get the hang of it and the great devs here post flashable updates very quickly.

Thanks
Sounds like it's not a huge hassle then. I'll flash TWRP now and then apply the SU zip file. I think I'll enjoy having CM11S for a little while. It will be interesting to see if root sticks after an OTA.
lr4life said:
So far, I haven't updated via OTA from OnePlus. I just manually flash because it is always faster than waiting for an update to get pushed to your specific device. However, with other devices in the past (Nexus 10), if I have kept the stock kernel, I have been notified of updates via OTA. If I were you, I would just root, flash Franco Kernel and update manually in the future. It is very easy to do once you get the hang of it and the great devs here post flashable updates very quickly.
Click to expand...
Click to collapse

r0brimmer said:
Sounds like it's not a huge hassle then. I'll flash TWRP now and then apply the SU zip file. I think I'll enjoy having CM11S for a little while. It will be interesting to see if root sticks after an OTA.
Click to expand...
Click to collapse
Well, if you look on XDA for an OTA based update, there are always versions of the update that keep root that you can flash that are supplied by various developers, so that shouldn't be an issue.

I had grief with some root apps (particularly Secure Settings) in 11s until I applied the fix described by crushingyen here: https://forums.oneplus.net/threads/root-access-in-developer-option.52874/page-2 Just FYI.

If you install TWRP and root the phone you can still pull updates from the Settings > About phone > System updates. I've done several on my OPO. One warning though. By default the updates will both remove root (expected) and will re-flash the recovery back to stock (unexpected). You can turn off the re-flashing of recovery by unchecking the Settings > Developer options > Update CM recovery option.

Dont go with CM11s!
1) Open your Bootloader
2) Root your OPO
3) Install CWM (best in my opinion)
4) Install/Flash and AOSP Rom (like crDroid Rom (BEST ROM EVER!!!))
5) Install/Flash GApps
6) Install/Flash AK-Kernel
7) Install/Flash UKM+Synapse
Got no Reboots, Lags, NOTHING!
I undervolted my OPO -150mV and deactivated the quad core to a dual core with 1,8GHZ!
Runs so smooth with the smartmax Governor impressive!

I also tryed Mahdi Rom+Cyanhacker but dont go with them, laggy and Random Reboots and no weekly updates :/

EasyGoingXD said:
I also tryed Mahdi Rom+Cyanhacker but dont go with them, laggy and Random Reboots and no weekly updates :/
Click to expand...
Click to collapse
Mahdi ROM isn't laggy. Its user error that is causing your phone to lag / reboot if you do encounter any.
Posts like this are not constructive, people don't make ROMs to have random reboots or lag. Instead of complaining about it, figure out why it does for you individually but not for others.

zephiK said:
Mahdi ROM isn't laggy. Its user error that is causing your phone to lag / reboot if you do encounter any.
Posts like this are not constructive, people don't make ROMs to have random reboots or lag. Instead of complaining about it, figure out why it does for you individually but not for others.
Click to expand...
Click to collapse
I mean the crDroid is smoother then Mahdi , btw i am used the same settings on both ROMs and yes....Mahdi lagged and got some ghost touches too :/

Just unthick update cm recovery in developer options and flash supersu zip after applying the update!
Inviato dal mio A0001 utilizzando Tapatalk

So root the original ROM on there and OTA over the top or should I root and flash a clean install of the latest ROM?

r0brimmer said:
So root the original ROM on there and OTA over the top or should I root and flash a clean install of the latest ROM?
Click to expand...
Click to collapse
Root your phone, flash a new Recovery, flash a new Rom+GAPPS

r0brimmer said:
So root the original ROM on there and OTA over the top or should I root and flash a clean install of the latest ROM?
Click to expand...
Click to collapse
What there saying is when your first get it unlock boot loader flash custom recovery and then root. Then go into developer options. Untick update cm recovery. Then when you get an ota you can run it. So it won't touch your custom recovery you will just lose root. So reflash su with custom recovery and your good to go

nathlynn22 said:
What there saying is when your first get it unlock boot loader flash custom recovery and then root. Then go into developer options. Untick update cm recovery. Then when you get an ota you can run it. So it won't touch your custom recovery you will just lose root. So reflash su with custom recovery and your good to go
Click to expand...
Click to collapse
Perfect. Thanks for clearing it up. Just awaiting a screen protector before I start.

r0brimmer said:
Perfect. Thanks for clearing it up. Just awaiting a screen protector before I start.
Click to expand...
Click to collapse
Lol i'm still waiting for my phone so your in front of me. Hoping mine will come next week along with my glass screen protector and case

So received phone today 2 days after order

nathlynn22 said:
So received phone today 2 days after order
Click to expand...
Click to collapse
They are quick! I got mine quickly too
Sent from my A0001 using XDA Free mobile app

Semi-bricked OPO, need help restoring

Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You

Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon

timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?

You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first

Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.

Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon

EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.

Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)

Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon

timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)

Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.

OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?

Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon

CM12 Bootloop Issue

I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.

Have you tried using CyanDelta?
https://play.google.com/store/apps/details?id=com.cyandelta
Transmitted via Bacon

Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk

timmaaa said:
Have you tried using CyanDelta?
Transmitted via Bacon
Click to expand...
Click to collapse
Tried that earlier today, didn't help anything.
gmac1990 said:
Its also possible there are firmware differences. I have read about some new firmware pushes in the nighties. I am currently on Bliss and we have to flash updated files to keep up with the cm commits. It could be that because your dirty flashing its causing an issue. Perhaps do a backup of data, install latest. And restore data is your best bet.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yeah, I think that might be my best bet. I guess it's better than nothing, haha. Thanks for you answers guys.

It probably is due to not having updated firmware. Which nightly? Wipe everything and flash the most recent nightly or go to blisspop thread and find the updated firmware zip it's around 30mb and flash that. It should fix your boot loop issues
Sent From Lollipopified Bacon Goodness!

The firmware can be found here:
http://www.vanir-exodus.net/exodus/bacon/
Transmitted via Bacon

Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.

Skizwack said:
Thanks for the help guys. That most likely would have been the issue. But, alas, I ended up soft bricking (still not sure how), and now I'm back to stock. I'll probably stick here until a more stable Lollipop ROM is out.
Click to expand...
Click to collapse
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon

timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
I suppose that may have been my problem all along. The main problems I was having were just little bugs (system UI very rarely crashing, and a couple other minor annoyances), but I guess those could have been caused by having the wrong firmware. Maybe I'll give it another go soon. Now that I'm all settled in to CM11S, haha. Thanks again!

Has anyone else had any issues with the automated download and install feature in the CM12 settings? Mine will download the night lies and even automatically boot into TWRP but it doesn't flash?

timmaaa said:
They are stable, all you needed to do was have the correct firmware on your device.
Transmitted via Bacon
Click to expand...
Click to collapse
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?

Skizwack said:
So, I'm still having this issue. I flashed the new firmware yesterday, and I went back and installed CM12 (the 1-28-15 nightly). Just now I tried updating it to the 1-29-15 nightly with CyanDelta, and it's doing the exact same thing again. Any other suggestions? Did I flash the firmware in the wrong order?
Click to expand...
Click to collapse
which recovery and version are you using?

playya said:
which recovery and version are you using?
Click to expand...
Click to collapse
TWRP 2.8.4.1

Skizwack said:
TWRP 2.8.4.1
Click to expand...
Click to collapse
What's the name of the firmware file you flashed?
Transmitted via Bacon

timmaaa said:
What's the name of the firmware file you flashed?
Transmitted via Bacon
Click to expand...
Click to collapse
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.

Skizwack said:
I've done some searching around, and can't really find anyone else that is having quite the same problem as me. So, I'm running CM12 Nightlies on my One. After I upgraded from stock, everything worked flawlessly. But now, whenever I try to update it to a new nightly, it gets stuck in a bootloop. The only way I've found to get it to update without the bootloop is to wipe the whole system. Which is getting a little annoying having to reinstall my apps and stuff every day. I've found a few work arounds, like making a backup through TWRP, updating, then restoring just the data of the backup. But I'd like to be able to just update it without having to go through all that trouble. I don't know if I'm the only one having this specific issue, or if it's a CM12 issue. Any help would be great.
Click to expand...
Click to collapse
have tried different version TWRP?

Skizwack said:
bacon_firmware_update_2015_01_16.zip, from that link you gave me before.
Click to expand...
Click to collapse
What about when you download the whole ROM zip from the CM site?
geowolf1000 said:
have tried different version TWRP?
Click to expand...
Click to collapse
The version he's on is fine.

timmaaa said:
What about when you download the whole ROM zip from the CM site?
Click to expand...
Click to collapse
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.

Skizwack said:
I think I tried that before. Even if I downloaded that and flashed it from recovery (without wiping anything first), it would do the same thing.
I know it's best to not dirty flash, but my main reason I want to figure this out is because I use Google Music All Access. And every time I wipe my system I have to re-download all my music.
Click to expand...
Click to collapse
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.

timmaaa said:
Dirty flashing should be fine if you're just updating the same ROM. Do you check the md5 when you download the file? They might be getting corrupt during the download.
Click to expand...
Click to collapse
If I remember right, I do. I'm on the latest version now though, so I can't really test it. When a new one comes out tomorrow I'll give it a go and see what happens.