I have read that we're supposed to get the CM12S this month but if I flash a nightly of CM12S now, will I have to format my data and wipe everything or can I just upgrade it later OTA?
And another thing, I'd my phone is rooted will I be able to get the CM12S?
Thanks!
Sent from my A0001 using XDA Free mobile app
ril2 said:
I have read that we're supposed to get the CM12S this month but if I flash a nightly of CM12S now, will I have to format my data and wipe everything or can I just upgrade it later OTA?
And another thing, I'd my phone is rooted will I be able to get the CM12S?
Thanks!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
If you flash a nightly you won't get the OTA for 12S, to get the OTA you need to be stock (you can have unlocked bootloader/custom recovery/root OK). If you're stock rooted, you should get the OTA no problem, you may lose root but you should be able to just flash a supersu via recovery to sort it. If you're rooted and have changed any files in /System the OTA will most likely fail, but you can just flash the factory images or even one of the stock flashable zips of 11S to sort that.
CM12S shouldnt be too far off now, hopefully here in a few weeks. If you really can't wait, just take a nandroid and flash a CM12 nightly and give it a go. You can always switch back and take the official OTA.
The nightlies aren't CM12S nightlies, but CM12 ones. Don't get confused.
If your confident enough to flash, then why bother waiting for the OTA? Or worrying about getting it?
The OTAs take so long to roll out. I actually flash the Original OTA directly.
IMO wait. CM12 is not very stable yet.
runderekrun said:
IMO wait. CM12 is not very stable yet.
Click to expand...
Click to collapse
I disagree, its been my daily driver for about a month now and I've experienced little to no problems. Plus, if you decide to get onto the CM12S release version just flash stock and you can get the OTA. For the time being, until the release comes in around 2-3 weeks, I would say that it's okay to switch to the nightlies.
served24 said:
I disagree, its been my daily driver for about a month now and I've experienced little to no problems. Plus, if you decide to get onto the CM12S release version just flash stock and you can get the OTA. For the time being, until the release comes in around 2-3 weeks, I would say that it's okay to switch to the nightlies.
Click to expand...
Click to collapse
You use bluetooth much? That is probably my chief complaint. It's borked for me and others. That and random wakelocks that will not let my phone deep sleep on Wi-Fi (not just me, multiple reports in nightly thread). Many people have reported overall worse battery life but I haven't been running CM12 long enough to comment on this (besides the wifi wakelocks).
I mean if you don't depend on your phone then maybe. Coming from a "flash a new rom every week" background, I don't mind it. But for someone that is used to stability on S roms, I wouldn't suggest it.
Titanium backup is your friend and you can restore all your personal data after clean flash.
Don't bother with CM12 nightlies, there are no compelling new features yet and many bugs to work out.
Android 5.1 is coming this week or next week. I'd wait to flash a rom until that is out.
alpha.shining said:
Titanium backup is your friend and you can restore all your personal data after clean flash.
Click to expand...
Click to collapse
Will I be able to restore the phone's settings such as accounts, themes, launcher pages layouts (icons and widgets) app data, etc.?
gsmyth said:
If you flash a nightly you won't get the OTA for 12S, to get the OTA you need to be stock (you can have unlocked bootloader/custom recovery/root OK). If you're stock rooted, you should get the OTA no problem, you may lose root but you should be able to just flash a supersu via recovery to sort it. If you're rooted and have changed any files in /System the OTA will most likely fail, but you can just flash the factory images or even one of the stock flashable zips of 11S to sort that.
CM12S shouldnt be too far off now, hopefully here in a few weeks. If you really can't wait, just take a nandroid and flash a CM12 nightly and give it a go. You can always switch back and take the official OTA.
Click to expand...
Click to collapse
If I have changed files in /system how can I get the OTA without erasing any data?
Thank you very much for your help!
Sent from my A0001 using XDA Free mobile app
ril2 said:
Will I be able to restore the phone's settings such as accounts, themes, launcher pages layouts (icons and widgets) app data, etc.?
If I have changed files in /system how can I get the OTA without erasing any data?
Thank you very much for your help!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Best bet is just to flash the below stock rooted ROM via recovery. Wipe cache and dalvik and you should be fine, its OTA safe as nothing has been touched, apart from root added.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033
gsmyth said:
Best bet is just to flash the below stock rooted ROM via recovery. Wipe cache and dalvik and you should be fine, its OTA safe as nothing has been touched, apart from root added.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033
Click to expand...
Click to collapse
What will it do? Will it erase or change anything?
Sent from my A0001 using XDA Free mobile app
ril2 said:
What will it do? Will it erase or change anything?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
If you just flash over the top, wiping cache and dalvik cache only it won't erase any data or settings, but will restore any modified/removed system files to stock, so you can take an OTA when it comes. As always, make a nandroid backup first just to be on the safe side, but all will be fine.
Related
I am loving this rom but I am nervous if and when the developer comes out with a new version.
When the newer version comes out how do I update to the newest version? Do I have to erase everything and start over again? Thanks so much!
well if you installed stock ROM, you will probably recieve an update without need to delete anything, but if you used custom ICS rom like CM than you will have to update it manually...
I believe i was clear!
thanks but I was talking about when the developer of the custom rom has a newer version. Wondering if there is an easy way to update.
download it, put it on phone, and just apply it using CW recovery, if its same rom but new versiom, for example CM9 v19 and you want to put CM9 v20 than in most cases you just apply it and it should work, but its always good practice to make backup before any ROM update...use titanium backup or something similar
so can I just wipe cache and dalvik cash then install?
Will my home screen be the same?
stu5797 said:
so can I just wipe cache and dalvik cash then install?
Will my home screen be the same?
Click to expand...
Click to collapse
In most cases, you can clear caches, and flash over. I went from 32 to 43 without wiping, and have no issues. In fact, it is my main fallback backup when testing new ROMs. By doing this, all previous settings will stay.
If there is a major overhaul, though, you will want to wipe if you run into force closes. So let's say Google releases 4.0.4 tomorrow and aosp releases a new ROM update based on it. In most cases, you will want to full wipe and clean install. This is where titanium backup pro is very useful.
Sent from my Nexus S 4G using xda premium
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk
Hi all!
First off, I apologize in advance if this is a dumb question. But basically, I'm running a rooted One and I've been waiting for the official nightly builds for CM12, but now that they're finally here, I can't seem to flash them. I keep getting random errors when I try. I'm currently running on the latest 11s update that was OTA with TWRP, and I've unlocked my bootloader and everything. Anyone have any input? I've read in some places that you can't update to the CM12 nightly from 11s, and if that's the case, what's the best way to go from 11s to 11 without losing any data?
Thanks in advance!
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
timmaaa said:
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
Click to expand...
Click to collapse
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
CaptainBlackbeard said:
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
Click to expand...
Click to collapse
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
timmaaa said:
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
Click to expand...
Click to collapse
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
I'd wipe even going from CM11 to CM12.
Transmitted via Bacon
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
No, can't, unless you wait for CM12s. But I guess you can backup everything with Ti Backup then restore it back, No harm doing that though.
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
dirty flash
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
dd2 said:
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
Click to expand...
Click to collapse
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
timmaaa said:
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
dd2 said:
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
Click to expand...
Click to collapse
If you're just updating the same ROM (flashing a newer build of the exact same ROM) you can usually dirty flash. Any other time you must clean flash.
timmaaa said:
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
CaptainBlackbeard said:
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
Click to expand...
Click to collapse
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
timmaaa said:
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
CaptainBlackbeard said:
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
Click to expand...
Click to collapse
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
CaptainBlackbeard said:
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
Click to expand...
Click to collapse
Did you read the second part of my post??
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
The new version you linked worked!
Now I'm attempting a restore through TItanium. How long does it usually take? It's been sitting at 0% on the first app for a little while now.
Like everyone else I got the 5Q update the other day. Something in the update was causing my battery to drain much faster than before and since there are no new features in 5Q that I care about I tried rolling back to 44s.
I used the flash-able version of 44s from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Now I am basically stuck in a boot loop. Android boots up but I keep getting com.android. phone has stopped working over and over.
Anyone know how to fix this?
I didn't back anything up thinking this would be a quick roll back to 44S so I want to avoid having to do a full factory reset.
If worst comes to worst, can I use fastboot to reflash 44S without losing pics/texts/files ect?
Edit: I jumped back to 5Q and I no longer get the continuous errors. So I guess the question becomes now how should I go about rolling back to 44S and avoid getting the errors I was getting?
Thanks!
skyliner99 said:
Like everyone else I got the 5Q update the other day. Something in the update was causing my battery to drain much faster than before and since there are no new features in 5Q that I care about I tried rolling back to 44s.
I used the flash-able version of 44s from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Now I am basically stuck in a boot loop. Android boots up but I keep getting com.android. phone has stopped working over and over.
Anyone know how to fix this?
I didn't back anything up thinking this would be a quick roll back to 44S so I want to avoid having to do a full factory reset.
If worst comes to worst, can I use fastboot to reflash 44S without losing pics/texts/files ect?
Edit: I jumped back to 5Q and I no longer get the continuous errors. So I guess the question becomes now how should I go about rolling back to 44S and avoid getting the errors I was getting?
Thanks!
Click to expand...
Click to collapse
When you went back to 44S did you clean flash or dirty flash? The errors suggest that you dirty flashed, which you shouldn't do when going backwards. So what you need to do is perform a full wipe (system/data/cache/dalvik cache) and then flash 44S. Backup your user apps (not system apps or settings though) with Titanium Backup first, then you can restore them after 44S boots up again.
Transmitted via Bacon
The easiest method to go back would be to back up using Titanium Backup (And nandroid if you want to revert to old ROM if any problems occur) and then Wipe data/cache and flash the signed zip you downloaded. The issues must be with additions to dialer app I guess.
But just one question, have you checked why there is battery drain in 5Q? I would suggest you to install 'Better Battery Stats' or WakeLock Detector and find out what is draining your battery.
Usually this is the main culprit,http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525/page3 .
You can also rely on Calkulin's Stock ROM's to enjoy stock+root. http://forum.xda-developers.com/oneplus-one/development/rom-calkulins-oneplus-one-v1-0-t2810365.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
timmaaa said:
When you went back to 44S did you clean flash or dirty flash? The errors suggest that you dirty flashed, which you shouldn't do when going backwards. So what you need to do is perform a full wipe (system/data/cache/dalvik cache) and then flash 44S. Backup your user apps (not system apps or settings though) with Titanium Backup first, then you can restore them after 44S boots up again.
Transmitted via Bacon
Click to expand...
Click to collapse
@timmaaa, you really are the fastest to help anyone in distress. Thank you. :good::laugh:
tr.supradeep said:
The easiest method to go back would be to back up using Titanium Backup (And nandroid if you want to revert to old ROM if any problems occur) and then Wipe data/cache and flash the signed zip you downloaded. The issues must be with additions to dialer app I guess.
Click to expand...
Click to collapse
System must be wiped too. Otherwise there's really no point in wiping anything.
Transmitted via Bacon
You are right, I missed that part, though I do it always. Always while changing ROMs and Downgrading. Upgrading using dirty flash has never caused me a problem.
OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.