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.
Related
So here's my question: How do you update your ROM?
Yes I am using the same ROM to update to.
Is it the same method as flashing it in the first place?
e.g.: Go into CWM and flash it?
Or is there a different way of doing it.
If you have an answer please explain it thoroughly.
Hi,
i have last week installed cyanogen 9
to update to the last build of yesterday, i have just installed it from CWM.
i didn't lose any data
heniki said:
Hi,
i have last week installed cyanogen 9
to update to the last build of yesterday, i have just installed it from CWM.
i didn't lose any data
Click to expand...
Click to collapse
So your saying just flash it again with no additional steps?
Just place the updated ROM file in the root of the sdcard and just flash away?
th3controller said:
So your saying just flash it again with no additional steps?
Just place the updated ROM file in the root of the sdcard and just flash away?
Click to expand...
Click to collapse
Yes
I've noticed that flashing ROMs without wiping data causes more problems than it helps you avoid.
Also, see:
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/AOKP_Frequently_Asked_Questions
It's always better to do a factory reset before a ROM install to avoid these issues, even when doing a direct upgrade from AOKP -> AOKP.
Click to expand...
Click to collapse
It wouldn't hurt to fix permissions after you flash if you don't wipe your data.
If FB said yes then cheers to that! Thanks FB!
And thanks for the advice guys, I'll make sure to wipe data before updating.
EDIT: Also what are gremlins? Do I need to remove these gremlins before I update my ROM? Or do I just clean gremlins IF I install a different ROM?
If so how do I remove gremlins? (A link provided is enough )
This thread should explain everything:
http://forum.xda-developers.com/showthread.php?t=1500427
I would recommend it only if you have flasheda bunch of stuff and are starting to see problems like poor performance, or extreme battery drain. It's also helpful if you just need to get back to stock+root quickly. Also, if you're having problems, try the other steps in the thread first. When I was having battery issues, the battery trick in the thread fixed it perfectly.
Wodensman said:
This thread should explain everything:
http://forum.xda-developers.com/showthread.php?t=1500427
I would recommend it only if you have flasheda bunch of stuff and are starting to see problems like poor performance, or extreme battery drain. It's also helpful if you just need to get back to stock+root quickly. Also, if you're having problems, try the other steps in the thread first. When I was having battery issues, the battery trick in the thread fixed it perfectly.
Click to expand...
Click to collapse
Thanks for that, I'll surely keep this bookmarked.
FBis251 said:
Yes
Click to expand...
Click to collapse
So by flash do you mean just putting the ROM into the phone and selecting it just like you would when you originally installed the ROM? How do you wipe the original ROM before flashing the update?
Certain ROMs now use the Aroma installer (FBis was responsible for much of the work to make that possible for SGS4G ROMs) which provide more options than a CW Recovery or TWRP "install zip" kind of install. The Aroma installer generally lets you save/restore or wipe.
Both CW Recovery and TWRP have options to wipe one or more of your partitions before you install. They are a little different and which one you have will depend on what you are flashing from.
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
UPDATE: I was able to make it work, see comment #12
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
timmaaa said:
You need to go back to being completely stock. Perform a full wipe (system/data/cache/dalvik cache) and flash the recovery flashable version of 33R from here, Then you can flash the update.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
rhaces said:
Thanks, but there has to be other way that would not require wiping data... that is not acceptable
Click to expand...
Click to collapse
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
timmaaa said:
I'm not talking about user data, I'm talking about your system data partition.
Transmitted via Bacon
Click to expand...
Click to collapse
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
rhaces said:
In your original post you mention "Perform a full wipe (system/data/cache/dalvik cache)", that will factory reset my phone (except /sdcard), that is what I want to avoid.
Click to expand...
Click to collapse
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
timmaaa said:
You don't really have a choice. Why is it an issue? Just use Titanium to backup your apps and restore them again once you've updated. The only thing you'll have to do again is your system settings.
Transmitted via Bacon
Click to expand...
Click to collapse
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
Follow vomer's guide here. It just bring your rom back to stock and leaves user data untouched. http://forum.xda-developers.com/showpost.php?p=55882576&postcount=229
rhaces said:
I've had plenty of issues throughout the years with Titanium, which makes me not to trust it fully, it will consume a lot of time to fully backup and fully restore, and, most important, I really hate that I need to wipe and re-flash stock if I'm in stock (with a few modifications which can be all undone)
Click to expand...
Click to collapse
There's nothing wrong with Titanium if you know how to use it. Unless you're restoring system data (which you shouldn't be) it's perfectly solid. And the thing is, you're not stock, those modifications you've made mean that you're not stock, so it's completely normal that you'd have issues with updating. You can moan about it all you like but it doesn't change the fact that you need to wipe.
Transmitted via Bacon
What he said.
You can't apply an OTA update if u have a custom kernel installed.
Just go back stock and apply updates until the latest version. If u use titanium properly you will not have any issue, just backup user apps without system settings.
Any other turnaround can cause havoc.
rhaces said:
Hey All, I got the OTA (I have it in /cache in my phone so no need to download anything) in my Stock 33R with root, franco 23R and TWRP. When trying to install the OTA, I'm getting a "Can't install this package on top of incompatible data. Please try another package or run a factory reset" error. I've followed Franco's post on how to install this OTA (https://plus.google.com/106873500108976028532/posts/ByvTAonR6mH) and I have even flashed the backed-up kernel and still same issue. One more thing I did was remove supersu.apk from /system/apps/ just to make sure that was not the case. I've read about the modified OTA, however not sure why I would need any modified so I want to see if this can be done with the unmodified 38R
Anyone can help?
Click to expand...
Click to collapse
Please check http://forum.xda-developers.com/showpost.php?p=55948892&postcount=16
@rhaces, just curious, could you PM me your /data/system/packages.xml file?
Well, It looks like you really don't need to wipe data (see, I told you it was ludicrous), I tried following both this and this, but did not helped (however both gave me ideas), here's what I did:
Fastboot flash boot system and recovery from 33R, boot into system, apply the OTA from the system (I'm now in an unrooted-unmodified stock 33R) and now that worked. Booted into newly installed 38R and everything worked ok, so went back to fastboot, flashed TWRP, went into TWRP and installed supersu and franco 24r and now things seem to be ok.
Thanks for all the help
Just don't complain when you start getting problems. Which you most likely will.
Transmitted via Bacon
This is the perfect storm....
Been running unofficial and official CM12 nightlies. Made the mistake of installing SuperSU (because it's my preference) and some how I've wrecked root access all around. My theory is that built in superuser and flashed supersu are breaking each other somehow:
To fix it I:
1. Tried to reflash UPDATE-SuperSU-v2.00.zip via TWRP. This does not work, supersu still can't get root access.
2. Tried disabling, enabling superuser in settings, no matter what supersu still can't get root access.
3. Dirty flashed the nightly agian (or the next days) to just use built in SuperUser. This does not work.
To make matters worst, I lost my TB backup so I can't do a clean install, without loosing everything.
Any ideas on how I can get root again, or maybe even how I can make new backups of my apps+data?
You need to clean flash the ROM again, and this time don't install SuperSU (root access is built into Privacy Guard on CM12). Unfortunately without root your can't backup your apps, don't you backup your backups to your PC or something?
Transmitted via Bacon
timmaaa said:
You need to clean flash the ROM again, and this time don't install SuperSU (root access is built into Privacy Guard on CM12). Unfortunately without root your can't backup your apps, don't you backup your backups to your PC or something?
Transmitted via Bacon
Click to expand...
Click to collapse
Hey thanks for your help. No, I don't have a backup on my PC.
I knew a clean flash would fix the issue, but as I said this is the perfect storm.
apollostees said:
Hey thanks for your help. No, I don't have a backup on my PC.
I knew a clean flash would fix the issue, but as I said this is the perfect storm.
Click to expand...
Click to collapse
Unfortunately I don't think you don't really have a choice. You could try entering the SuperSU menu and doing the full unroot, rebooting, and seeing if the built in root will work. This is why it pays to do your research before flashing.
Transmitted via Bacon
Didn't adb have a backup function? Something like adb backup -all
Thymo said:
Didn't adb have a backup function? Something like adb backup -all
Click to expand...
Click to collapse
I think so, but the parts he wants to backup require root access.
Transmitted via Bacon
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.
Hey everyone,
Thank you all for reading this...
Today, I wanted to update my phone from cm-12.1-20150429-NIGHTLY-bacon.zip to cm-12.1-20150502-NIGHTLY-bacon.zip and after optimizing all 199 applications the lock screen appeared and everything seemed fine. However a second later, a pop-up appeared delivering the crash of the google play services. After pressing on "ok" (the only option), the phone switched off and began optimizing the apps again and again, showing the boot sequence in-between. After a while, I tried to install the update again through TWRP and I failed again. Then I tried to restore my backup from the 19th April I had probably made with Nandroid Backup (not exactly sure) and I failed again. Now I have turned off my phone entirely so that it won´t get too hot.
Does anybody know how to fix this issue (preferably without wiping)? And do you think, should I stay with the nightlies or switch to Cyanogen OS 12 (how?)
Best regards from the android newbie,
George (ambach10)
Try reflashing slim's gapps package.
Edit: Link to thread: http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Follow this steps to first turn on your phone https://forums.oneplus.net/threads/guide-how-to-revert-back-to-cm11s-from-oxygen-guide.290605/
It's CM11S.
Easy way to revert back.
ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
I've had this issue before. To fix it, I used these gapps, did a full wipe, then flashed everything all over again and it was working without any problems.
Also, I ended up just switching over to COS12 and am still running that. If you want, you can get that here.
ambach10 said:
Thanks for helping me. I did, but it just continued to optimize. I also tried to install the newest cm12.1 update "cm-12.1-20150505-NIGHTLY-bacon.zip" by downloading it via a mac (is that a problem?) so that it would work with the newest gapps zip but I couldn´t even download the cm12.1 zip as it turned into a useless folder. Do you, or anyone else, know what to do know? I´m really frustrated that I cannot have access to my phone. I am also ready to wipe it, if necessary.
Click to expand...
Click to collapse
Also, make sure you are running latest version of TWRP recovery (or whatever recovery you are using)... there are compression incompatibilities with some of the older versions.
Thanks everybody!
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
ambach10 said:
Thank you all for helping me out:
@frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
@Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2766186 Here is the TWRP thread 2.8.6.0 is the latest. You can update using the TWRP Manager app available on the play store.
ambach10 said:
@The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Click to expand...
Click to collapse
I wiped everything other than Internal Storage, flashed the rom, flashed the gapps, and then rebooted and it booted just fine.
ambach10 said:
Thank you all for helping me out:
frieked I have twrp v2.8.5.1. Is that ok and if not how can i update that?
The_Symbiote should i install the apps before the full wipe and is there something not to wipe (USB_OTG)?
Mr hOaX does it also work for cm12.1 nightlies or only for oxygenos?
Click to expand...
Click to collapse
It works for all lollipop based ROMs.
I hope now your device is working fine.
Sorry for replying late.