Develop Bugs

[TUTORIAL] Flash CyanogenMod on TWRP

For CM11 Nightlies:
Find nightlies here:
http://download.cyanogenmod.com/?device=n1
If you're already on CM 10.2, just wipe cache and dalvik. Flash over your current build.
If you're coming from anything else, wipe cache, dalvik, data, and system. Then flash normally.
If you want gapps, you'll have to flash gapps as well.
No need for any modified files on nightlies. I assume that official stable builds will still be defaulted to flash on stock recovery though.
————————————————————————————————
CM 10.2 Information. Please do not use the following to flash CM11!
This is the method that I used to install CyanogenMod on TWRP.
I have tested this, and it is working perfectly on CM builds:
cm-10.2-WPPH47N-n1
cm-10.2-WPPH50O-n1
I will continue to test and update as new CM builds come out until CM flashes normally on TWRP
————————————————
First - Have TWRP as your recovery (2.6.3.1). Don't ask me how to do that.
Second - Backup your ROM! Just in-case something breaks, it's not my fault, and I'm not responsible.
————————————————
Now, we begin:
Download the newest CM build for the Oppo N1 from http://www.cyanogenmod.org/hardware/oppo-n1/#images
————————————————
After downloading your CM build from the above link, you'll need to follow these instructions to get setup for flashing in TWRP.
To modify your downloaded CM file, you can use either of the two methods below:
1: You can modify it yourself. It's actually very simple, just one line change.
2: I have attached an already modified updater-script to my post. You can use that and drop it into place (the file inside the zip, not the whole zip).[/b]
YOU ONLY NEED TO USE ONE OF THESE METHODS!
Method 1: To modify the file yourself:
First, open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Open the updater-script
Remove the first line only! You will remove:
Code:
assert(getprop("ro.product.device") == "N1" || getprop("ro.build.product") == "N1");
Do not remove anything else unless you know exactly what you're doing!
If you modified the file within the .zip, just save the file and it should save to the CM zip.
If you extracted the .zip, save the file and then go back and rebuild the zip.
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
——————————
Method 2: To download my pre-modified updater-script
Download my attached file (updater-script.zip)
Extract the file inside the zip (there's only one file)
Open your CM zip that you have downloaded.
Navigate to the folder: META-INF\com\google\android\
Simply copy your extracted updater-script from where you extracted it and drop it into the CM zip (It should save after)
Transfer over your newly modified CM.zip file to wherever you can find it on your phone (I drop it straight in the root folder).
————————————————
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
:victory:
I hope this all makes sense...
Basically you download the CM rom
Modify or copy the updater-script into the zip
Then you move the ROM to you phone
Then you go through the above area with wiping and flashing
* Pictures are attached
* Please let me know if there are any problems with this.
* Both versions of CM released so far have identical updater-script files. The .zip that I have attached will work on both builds.
* I will keep updating as needed
• Last updated: January 1, 2014

We're working on fixing TWRP so the asserts work properly.
https://github.com/omnirom/android_bionic/commit/4482d8513920d614e3799a214c5bad07b72580d2#diff-1 broke a lot of things.
https://github.com/omnirom/android_bionic/commit/ad76c85b9ca587084089d086f954158bc0eae905 allows flashing newer firmwares on older recoveries - but not the other way around.
The short-term fix is a TWRP build made from a 4.3 tree - this is 90% done.

@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img

Entropy512 said:
We're working on fixing TWRP so the asserts work properly.
Click to expand...
Click to collapse
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:

rayfin said:
@OP: Working with Entropy last night to squash this bug, I flashed his newly built TWRP and was able to go back to ColorOS or CM without issue. https://dl.dropboxusercontent.com/u/22964990/n1_twrp_43.img
Click to expand...
Click to collapse
BTW, I'd prefer that my personal dropbox not be directly linked. The same file is now an attachment to my post in the TWRP thread.

Harfainx said:
That's fantastic. I'm glad to hear that it's being work on/working. I suppose fixing TWRP trumps fixing the ROM :highfive:
Click to expand...
Click to collapse
i have some question can u help me :3
1. this download link is the file you already fix it right ?
https://www.4shared.com/download/UPP...N-N1_FIXED.zip - No wait - Direct download link - Full flashable ROM
Click to expand...
Click to collapse
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?

kenjilolip0p said:
so i just have to download and flash with TWRP. dont have to fix any else ?
2. This is CM10.2 rom official for N1 work with O-Touch in the back ?
Click to expand...
Click to collapse
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.

Harfainx said:
Correct, the very top link in the OP is the full ROM. You can download the full ROM and flash it in TWRP. It's already fixed and ready to go.
So far that has been the only ROM to come out from Oppo for CM. It contains most of the ColorOS features that work. "Knock" to wake (double-tap), screen off gestures, camera orientation, etc. I'm almost positive that the back touch-pad was working. I haven't been on CM in a little bit though. I'm still working on making changes to ColorOS, and updating as I go.
Click to expand...
Click to collapse
Camera orientation is handled by the camera HAL blobs.
CM does have back touchpad support but it's wonky (which is why omni hasn't merged it yet, we're still discussing whether to completely rearchitect it or just fix it.)

good work
Sent from my M045 using XDA Premium 4 mobile app

Except root it works
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.

fesar said:
Hi,
I tried everything and it works. But the root is not working well. I tried installing SuperSu.zip as well as apk nothing works. Any thoughts ?
Francis.
Click to expand...
Click to collapse
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?

nowy57 said:
I lost root as well
and superSU files insatlled into TWRP didnt work ...
any ideas how to back root acces ?
apart of it
I cannot instal via TWRP CM10.2 (4.3) cm-10.2-WPPH50O-n1-signed.zip
I v got error message
what you are latest build on ?
Click to expand...
Click to collapse
Go into SuperSU and remove it in the settings (unroot). That will get rid of all of the current SuperSU stuff.
Then flash SuperSU in TWRP.
To flash the unmodified CM, you can try the TWRP in post #3 of this thread HERE.
Or you'll have to remove the same line in the updater-script. The same method posted in the OP. Don't use the uploaded updater-script that I have there though. You'll need to change your own. It's a really simple fix. You don't have to extract all the files out. You can just modify the one file (I use Notepad++).
Sometime tomorrow I'll update the whole OP to include the newest CM version. I'm about to head out to our New Year's event, so I won't be available for the evening.
Enjoy the evening everyone. I wish you all the best! :good: :victory:

i have installed TWRP from #3 - not succes install CM newest version after this
i have unthick superSU and then install again via TWRP superSU.zip after that thick superSU on system android and no succes - root acces didnt come
happy new year
-------
I am a little dissapointed couse I downloaded CM ROM from OFFICIAL SITE http://www.cyanogenmod.org/hardware/oppo-n1/#images and I cannot install it SIMPLE on my device

OP updated! The newest release of CM has been added. I'll keep on top of it from now on, sorry about the delay.
I'm not going to host the CM builds anymore, since the modification is so small from the original CM build. Everyone flashing this should be capable of making the small change that's outlined in the OP.
:highfive:

@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy

nowy57 said:
@Harfainx
it is not a problem to me to delete first line from updater-script but what then ?
I have to zip ii normally or compile using special prgogram ?
why dedicated ROM from CM/OPPO site is not allow to simple install via TWRP ?
it shuld be so easy
Click to expand...
Click to collapse
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.

Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
okay , I will try it and confirm
I v got mac osx
under mac I unzip ROM , deleted first line from script then zip it , it doesent work .
but under windows - working good

Harfainx said:
Reboot into TWRP:
Advanced Wipe ->
Wipe Dalvik Cache, Cache, and Data. ***DO NOT WIPE SYSTEM***
Then install your modified CM file. Please, remember, DO NOTE WIPE SYSTEM.
Reboot system! Done!
Click to expand...
Click to collapse
What's wrong with wiping system?
You don't even wipe system if you go from ColorOS to CyanogenMod?
- Frank

cm11 nightlies are out and downloadable from cyanogenmod
Harfainx said:
After dropping the file in, just save the zip again. If you haven't extracted it, you shouldn't have to do anything special.
Also, CM can easily be installed on the stock recovery. Oppo doesn't control other recoveries.
Click to expand...
Click to collapse
Cm11 nightlies are out..
Do you think we can flash on twrp
If so what would you wipe...
I was thinking about using banks minimal.. 19 MB..
Please give the community tour thoughts and a step by step tutorial..
I would download the nightly from cyanogenmod and banks gapps.. Check md5 alla onmy phone
Reboot recovery and wipe all maybe even system except sdcard
Flash cyanogen then gapps then
Rewipe cache and dalvik
Reboot
I am on omni nightlies now.. Thanks in advance

where do you see nightlies for oppo n1 ?
edit:
ohhh I see
http://download.cyanogenmod.org/?device=n1
better later than never
I just lost hope for good support and sold my oppo n1
I didnt belive for good support having it from one month and non of help from CM team

Give me a hand will ya?

Currently running on AOKP OTA ver. 3.2
I would like to have someone who can guide me slowly step by step carefuly to whatever better option there is.
I been having lots of troubleshooting with phone not responding how it should and I have to keep rebooting to often.
I appreciate your help.
Thank you

Since you're running a custom rom, you could update your recovery to the latest CWM or TWRP and flash a different or updated rom.

Could you help me to do that?
Just guide me step by step.
Ok I already did a backup.

What custom recovery are you running? The first thing would be to get the latest img for your custom recovery and install it.
How did you root and install a custom recovery on your phone?

I am running AOKP OTA Ver. 3.2
That time I did it following a step by step guide with someone who was guiding me.
Hmm what else would you like to know?

That's the OS. What program did you use to backup your rom?

audit13 said:
That's the OS. What program did you use to backup your rom?
Click to expand...
Click to collapse
Oh…sure sure.
One I use is Team Win Recovery Project v2.4.1.0

You should update to the latest TWRP from here: http://teamw.in/project/twrp2/104
You can flash it using Odin. Make a full backup using the new TWRP. Find a rom you want to try, save it to the phone, and flash it using the ypdated TWRP. Don't forget to wipe the phone before changing ROMs.

audit13 said:
You should update to the latest TWRP from here: http://teamw.in/project/twrp2/104
You can flash it using Odin. Make a full backup using the new TWRP. Find a rom you want to try, save it to the phone, and flash it using the ypdated TWRP. Don't forget to wipe the phone before changing ROMs.
Click to expand...
Click to collapse
Ok So I delete the older TWRP get the new one.
Then back and wipe which of all the options?
And of course if I was using AOKP which I really liked, what will your recommend me?

Installing the latest version of TWRP will overwrite the version on your phone.
Install the newest version of TWRP, create a backup of your rom using the new version of TWRP, find a rom you like, copy the ROM to your phone, boot into TWRP, wipe cache, dalvik, data, flash the ROM, reboot.

audit13 said:
Installing the latest version of TWRP will overwrite the version on your phone.
Install the newest version of TWRP, create a backup of your rom using the new version of TWRP, find a rom you like, copy the ROM to your phone, boot into TWRP, wipe cache, dalvik, data, flash the ROM, reboot.
Click to expand...
Click to collapse
Ok perfect!
Thank you very much sir.
I will let you know when I'm done.

audit13 said:
Installing the latest version of TWRP will overwrite the version on your phone.
Install the newest version of TWRP, create a backup of your rom using the new version of TWRP, find a rom you like, copy the ROM to your phone, boot into TWRP, wipe cache, dalvik, data, flash the ROM, reboot.
Click to expand...
Click to collapse
Ok next is to find a nice rom, Any suggestions? (S3rx or SlimBean) keep in mind my device is an i747
Also do I use my computer to download the rom or should I use my phone directly?
I decided to go with Hyperdrive RLS16
Currently downloading it.
Will be flashing soon.

Harkadenn said:
Ok perfect!
Thank you very much sir.
I will let you know when I'm done.
Click to expand...
Click to collapse
Make sure to backup your apps with Titanium Backup.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

juanhbk1 said:
Make sure to backup your apps with Titanium Backup.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thank you for the warning.
Will do for the future.

Harkadenn said:
Ok next is to find a nice rom, Any suggestions? (S3rx or SlimBean) keep in mind my device is an i747
Also do I use my computer to download the rom or should I use my phone directly?
I decided to go with Hyperdrive RLS16
Currently downloading it.
Will be flashing soon.
Click to expand...
Click to collapse
You can download it directly to your computer and use Windows Explorer to copy it to a microSD card or directly to your phone. It's probably quicker to download a few to your computer and transfer them all at once so you can try different ones.
Have fun flashing ROMs.

audit13 said:
You can download it directly to your computer and use Windows Explorer to copy it to a microSD card or directly to your phone. It's probably quicker to download a few to your computer and transfer them all at once so you can try different ones.
Have fun flashing ROMs.
Click to expand...
Click to collapse
Ok as I extract the rom to my external sd card of my phone it's asking me many permissions such as:
"Do you want to copy Cesium.ogg to your device?
Your device might not be able play or view this file."
I said yes to skip all of the next warnings because every time i hit yes comes another warning.
Also strangely the rom took forever to download and the extraction is also taking way to long.
I didn't had to go through so much stuff by that time I downloaded AOKP rom. :/
Still extracting as I update this post... Something is not right...

I will have to cancel this.
It's stuck.

Do not extract the files. Just flash the zip.

audit13 said:
Do not extract the files. Just flash the zip.
Click to expand...
Click to collapse
Ah, to late I'm currently trying to find the right download link for Slim Bean rom.
Mind if you help me here?
My device is an I747.
UPDATE:
I believe is this one?
http://www.slimroms.net/index.php/d...o/6801-slim-d2att-4-3-build-2-2-official-1738
UPDATE!!
Yup it's done.
Thank you very much for your patience.
Quick question.
How do I restore all my phone data such as my contacts numbers and messages from the back up I did with the other rom?
Do I just restore the last backup and it should recognize the new rom?
UPDATE!
So it went back to where it was of course.
How should I back it all up and restore in the new rom?

Looks right. I have an i747m, not the i747.

cm11 glacier

Just built this on my computer was wondering if someone would test it out. Device tree and kernel I pulled from evervolv.
https://dl.dropboxusercontent.com/u/70782275/cm-11-glacier.2014.06.15.zip

adknight87 said:
Just built this on my computer was wondering if someone would test it out. Device tree and kernel I pulled from evervolv.
https://dl.dropboxusercontent.com/u/70782275/cm-11-glacier.2014.06.15.zip
Click to expand...
Click to collapse
Thanks for building a ROM :good:
However, I don't think I'll ever try to flash a new ROM with so little descriptions.. It only says cm11, pulled from evervolv's.
Maybe you can add a few more words about this build?

I get a dropbox error...

69gm said:
I get a dropbox error...
Click to expand...
Click to collapse
No worries it's just everything evervolv did I just used their device tree to build a CM version. So nothing really changed. Didn't install not sure why gave me a abort 7 probably the way asserts or something or older cwm recovery not supporting the update script.

Update to the TWRP build i just posted and reflash. CM source doesn't have the hacks for older recoveries.

Tried to full wipe + flash this one with latest 4ext recovery (update from June 20th) --> got stuck on logo screen.

jaibar said:
Tried to full wipe + flash this one with latest 4ext recovery (update from June 20th) --> got stuck on logo screen.
Click to expand...
Click to collapse
Yea I gave up on it since I don't know how to bring up a device tree. Stuck with evervolvs stuff since I finally got his thing to build on my laptop. Did a fastboot flashall but for some reason the data partition didn't wipe out so I ended up having my data still and a new android system.

[Q] PA 5.1 OTA issues

Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance

paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...

You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi

I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?

paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk

I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.

@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk

Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.

paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!

Cyanogen OS system upgrade

Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks

Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.

Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.

is a ZIP file available for flashing via TWRP?

Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver

mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI

Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464

mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated

Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!

seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).

Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.

seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.

mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?

seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.

Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?

seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success

Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.

seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.

Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.