Related
Hello,
I flashed one of the CM 10.1 that I found on CM website, and then I flashed GAPPS, but the version I downloaded has some bugs, so I want to choose a different CM version, but I don't know how to. I mean, what will happen with GAPPS? Do I need to follow same procedure as for installing CM for the first time i.e flashing CM, and then flashing GAPPS again?
Also, I have non-touch CWM recovery and I downloaded the touch version from CWM website, but I'm not sure how to do it, is it done with regular Odin via PC , or with something called "Mobile Odin"?
If you want to flash a newer nightly, you can either perform a clean flash or dirty flash. Clean flashing means you wile your data and flash cm along with Google apps again and start fresh. Dirty flashing means you just wipe your cache and dalvik cache and flash cm on top of the old cm which allows you to keep your data. Research both and decide what you prefer.
As for cwm, simply flash the new touch version in cwm and it'll overwrite the old cwm nontouch.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
If you want to flash a newer nightly, you can either perform a clean flash or dirty flash. Clean flashing means you wile your data and flash cm along with Google apps again and start fresh. Dirty flashing means you just wipe your cache and dalvik cache and flash cm on top of the old cm which allows you to keep your data. Research both and decide what you prefer.
As for cwm, simply flash the new touch version in cwm and it'll overwrite the old cwm nontouch.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks, I have last question regarding flashing new rom:
I flashed CM, but then I separately flashed GAPPS, so I dont know if GAPPS will be removed when installing new rom, or do I need to manually remove GAPPS before flashing new rom?
I hope you understand what I'm trying to ask :silly:
If you're dirty flashing, you don't need to reflash Google apps. However, if you're clean flashing then you are wiping everything so you'll need to reflash Google apps.
You don't need to remove it or anything before flashing the new rom. If you feel more comfortable flashing it, you can because it'll just overwrite your old Google apps.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
I am trying to use flash paranoid android and flashing this version of gapps along with it: pa_gapps-stock-4.4.2-20140412-signed. When I go to flash the ROM, it succeeds without issue, but when I go to flash gapps it says that it cant open the zip fie of gapps and than in parenthesis it says (bad). and than it says installation aborted. Please help!!!
maxell505 said:
I am trying to use flash paranoid android and flashing this version of gapps along with it: pa_gapps-stock-4.4.2-20140412-signed. When I go to flash the ROM, it succeeds without issue, but when I go to flash gapps it says that it cant open the zip fie of gapps and than in parenthesis it says (bad). and than it says installation aborted. Please help!!!
Click to expand...
Click to collapse
Have you tried re-downloading GAPPS? or from another mirror link? you could have a bad download.
GUGUITOMTG4 said:
Have you tried re-downloading GAPPS? or from another mirror link? you could have a bad download.
Click to expand...
Click to collapse
I have tried from several places with the same gapps version. Can I try to install a older version of gapps and than just let them automatically update once I have booted?
maxell505 said:
I have tried from several places with the same gapps version. Can I try to install a older version of gapps and than just let them automatically update once I have booted?
Click to expand...
Click to collapse
Yep, that works as well.
GUGUITOMTG4 said:
Yep, that works as well.
Click to expand...
Click to collapse
So I can flash this version right: gapps-kk-20140105-signed.zip
maxell505 said:
So I can flash this version right: gapps-kk-20140105-signed.zip
Click to expand...
Click to collapse
There are some not that old like 04-05 http://goo.im/devs/paranoidandroid/...ions/pa_gapps-stock-4.4.2-20140405-signed.zip
GUGUITOMTG4 said:
There are some not that old like 04-05 http://goo.im/devs/paranoidandroid/...ions/pa_gapps-stock-4.4.2-20140405-signed.zip
Click to expand...
Click to collapse
I already started flashing the the version of gapps that I posted and it worked! Paranoid Android gave me an update to the latest gapps and now it is updating. Thank you for your help. Also, what should I do if I want to switch to OmniROM later on. Can I just flash the OmniROM zip and the gapps zip or do I have to do something extra?
maxell505 said:
I already started flashing the the version of gapps that I posted and it worked! Paranoid Android gave me an update to the latest gapps and now it is updating. Thank you for your help. Also, what should I do if I want to switch to OmniROM later on. Can I just flash the OmniROM zip and the gapps zip or do I have to do something extra?
Click to expand...
Click to collapse
Comming from paranoid, I suggest first to back up apps data and wipe caches before the flashing the Rom .
You should not have any issues there after but if any, the wipe data and flash Rom and pa gapps
GUGUITOMTG4 said:
Comming from paranoid, I suggest first to back up apps data and wipe caches before the flashing the Rom .
You should not have any issues there after but if any, the wipe data and flash Rom and pa gapps
Click to expand...
Click to collapse
So do the same process as when I was flashing paranoid. All I have to do is wipe data, wipe cache, wipe dalvik chache, and flash the rom and the gapps?
maxell505 said:
So do the same process as when I was flashing paranoid. All I have to do is wipe data, wipe cache, wipe dalvik chache, and flash the rom and the gapps?
Click to expand...
Click to collapse
Yep, that's pretty much what's recommended for changing Roms. I personally don't clean anything when flashing similar Roms but PA is a bit complex imo and you already had issues with it. so, wipe.
GUGUITOMTG4 said:
Yep, that's pretty much what's recommended for changing Roms. I personally don't clean anything when flashing similar Roms but PA is a bit complex imo and you already had issues with it. so, wipe.
Click to expand...
Click to collapse
Ok for some reason, gapps updated and then it said that it has to install so it rebooted me into recovery and it started to install but it said that there was an error in the rom manager script or something like that. So I just got fed up and restored my backup that I had. So now I am back on stock. I want to install OmniROM though tomorrow.
maxell505 said:
Ok for some reason, gapps updated and then it said that it has to install so it rebooted me into recovery and it started to install but it said that there was an error in the rom manager script or something like that. So I just got fed up and restored my backup that I had. So now I am back on stock. I want to install OmniROM though tomorrow.
Click to expand...
Click to collapse
Because the Paranoid OTA cannot use CWM. Use twrp instead.
Sent from my Nexus 5
Pirateghost said:
Because the Paranoid OTA cannot use CWM. Use twrp instead.
Sent from my Nexus 5
Click to expand...
Click to collapse
So lets say that I just want to install OmniROM. Will OmniROM work with CWM?
Also will I be able to automatically update gapps once OmniROM boots because for some reason I cannot flash the latest version of gapps so I have to use an older version?
You can also get gapps from goo manager and the online version.
Sent from my LG-D800 using xda app-developers app
maxell505 said:
So lets say that I just want to install OmniROM. Will OmniROM work with CWM?
Also will I be able to automatically update gapps once OmniROM boots because for some reason I cannot flash the latest version of gapps so I have to use an older version?
Click to expand...
Click to collapse
It's not that PA doesn't work with CWM, just the ota app.
OmniROM requires twrp or CWM-based recovery. Not CWM itself if I recall.
You also have zero reason to install those gapps updates on either rom..
Gapps are updated automatically through the play store.
Sent from my Nexus 5
Pirateghost said:
It's not that PA doesn't work with CWM, just the ota app.
OmniROM requires twrp or CWM-based recovery. Not CWM itself if I recall.
You also have zero reason to install those gapps updates on either rom..
Gapps are updated automatically through the play store.
Sent from my Nexus 5
Click to expand...
Click to collapse
ok. Sorry if I am asking too many unnecessary questions. So since I have ClockWorkMod Recovery, I can easily install OmniROM by just flashing it and than installing gapps after that right?
maxell505 said:
ok. Sorry if I am asking too many unnecessary questions. So since I have ClockWorkMod Recovery, I can easily install OmniROM by just flashing it and than installing gapps after that right?
Click to expand...
Click to collapse
Yes. You can do the same thing with ParanoidAndroid also. You DO NOT need to update gapps through the ota app
Sent from my Nexus 5
I was trying to flash Exodus-Vanir on my OnePlus One. But it gives me error on
Code:
Comparing TZ version TZ.BF.2.0-2.0.0109 to TZ.BF.2.0-2.0.0096
assert failed: oppo.verify_trustzone("TZ.BF.2.0-2.0.0109") == "1"
E: Error executing updater binary in zip '/sdcard/Vanir ROM/exodus-vanir_bacon_5.0.2.031015.zip
I'm not sure about what to do in this case. I have tried to remove the line from the updater script but figured I need to get some ideas beforehand. Anybody got a workaround for this?
I know you need to update the firmware but EVERY SINGLE LINK I FIND IS DEAD! Someone, please give me a working link to the CM12 firmware.
You need the updated firmware and modem.
Firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFczZZTTZ0X2dzbEE/edit?usp=docslist_api
Modem:
https://docs.google.com/file/d/0B98G0KTJwnBFMThZUjhndGJlc1U/edit?usp=docslist_api
Transmitted via Bacon
Hi. How can we update them? Just flash them the through recovery?
Also, is there available a beginner guide how to install Exouds/Vanir Rom? Im currently on Liquidsmooth 5.0 and I want to switch to Vanir rom, but im not 100% sure what I have to do...
Thanks.
edzalv said:
Hi. How can we update them? Just flash them the through recovery?
Also, is there available a beginner guide how to install Exouds/Vanir Rom? Im currently on Liquidsmooth 5.0 and I want to switch to Vanir rom, but im not 100% sure what I have to do...
Thanks.
Click to expand...
Click to collapse
Just flash them in recovery. Flashing any ROM is the same, I have a guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Thank you very much for your quick reply. Ill give it a try now.
Ohh, one last thing. I have to Flash firmware and mode after I flashed new Vanir Rom, or I have to do it on my current Rom?
edzalv said:
Thank you very much for your quick reply. Ill give it a try now.
Ohh, one last thing. I have to Flash firmware and mode after I flashed new Vanir Rom, or I have to do it on my current Rom?
Click to expand...
Click to collapse
Perform a full wipe (system, data, cache, dalvik cache), flash firmware and modem, go to reboot menu and reboot to recovery, flash ROM + gapps, reboot phone into new ROM.
Transmitted via Bacon
timmaaa said:
Perform a full wipe (system, data, cache, dalvik cache), flash firmware and modem, go to reboot menu and reboot to recovery, flash ROM + gapps, reboot phone into new ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
Luv ya'
I have smillar problem,i flashed firmware update and modem files without problem.But there is no signal , checked 4634,sometimes it finds the signal but no network registration ,sometimes the signal is 0.Imei,baseband are okay.I can use it with 44s modem and sensor file.Any suggestion?
Please help me how to back from Oxygen to CM11s or CM12 ? Oxygen is't better. i've root my Oneplus and have twr
I HAVE NOT TRIED THIS MYSELF:
I would say make a back up, wipe all partitions except for your internal storage, and then try flashing cm12 via twrp.
I went from oxygen back to stock rooted CM11s no problem. I heard Oxygen installs a modified TWRP, though, so you could reinstall the latest version just to be safe before re-flashing CM.
Edit: I didn't have to reinstall the recovery.
The hard is if you got no partition backups. If that is the case you will have to download stock cm11s XNPH05Q latest signed build. Unzip put OPO into fastboot mode. Find the file flash-radio.sh open it and manual flash every command that starts with fastboot. Then flash boot,cache,system, and depending on which data amount you have flash userdata images. Don't worry with the recovery you have twrp. Be ready to start over. Remember friends don't let friends flash CO2 OS. Good luck.
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
andrewwright said:
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
Click to expand...
Click to collapse
The oxygenOS zip installs a boot loader version that doesn't play well with CM11. If a person were to attempt to flash CM11 or restore a CM11 nandroid with that boot loader present it could cause serious complications.
To go back using recover one would need to flash a file that contained a good firmware/bootloader. CM12 from the CM website contains such a configuration. There are other files around that also apply non-bricking firmware. Fastboot flashing CM11S also would work if the device isn't bricked yet.
Once "bricked", recovery is possible but problematic and frustrating.
Flashing via TWRP straight from OxygenOS is not a good idea without preparation.
Hastily spouted for your befuddlement
xdoncam said:
Please help me how to back from Oxygen to CM11s or CM12 ? Oxygen is't better. i've root my Oneplus and have twr
Click to expand...
Click to collapse
You need to flash the right firmware and modem first and then you can flash whatever you like.
andrewwright said:
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
Click to expand...
Click to collapse
Not the same at all. Oxygen uses completely different firmware, if you fail to flash the right firmware before going back to CM you'll fail dismally.
Transmitted via Bacon
If you want oxygen you use cm12 firmware
For cm11 you use cm11 firmware
For cm12 you use cm12 firmware.
Formatting system and data and not using tb would help to. I did state this in my first post. Also the bootloader...turns first boot screen red....it works OK on cm12. Had no problems booting
Sent from my A0001
---------- Post added at 01:28 AM ---------- Previous post was at 01:23 AM ----------
But I did get what you two are saying but people on xda should know this already really. Flashing is easy...fixing is not
Sent from my A0001
andrewwright said:
If you want oxygen you use cm12 firmware
Click to expand...
Click to collapse
Oxygen doesn't use CM12 firmware, it uses firmware specific to Oxygen. This is why there are countless posts from people (who tried flashing CM12 after Oxygen without first flashing the right firmware) complaining that CM won't flash and their ROM won't boot, or that they're bricked.
Transmitted via Bacon
SAFE way move back from oxygenos to CM11s
For those who havnt shifted back to cm11s.(and still on oxygenos) and want to move back to CM11s ofcourse not hardbricked your phone. THIS GUIDE Is FOR ONEPLUS ONE 64GB VARIANT . (ALSO VALID FOR INDIAN USERS)
This guide will happily and SAFELY get you back to cm11s(XNPH05Q. OTA Safe).
people have hardbricked their phone by simply flashing cm11s through fastboot, which ofcourse is not the appropriate procedure.
NOTE: MY PHONE WAS NOT ROOTED BUT I WAS RUNNING OXYGENOS WITH TWRP RECOVERY INSTALLED(BUT I PREFERRED FASTBOOT METHOD). ONLY DRAWBACK IS YOU NEED TO TAKE BACKUP FIRST . ELSE THIS METHOD IS SAFE.
You need to have the following files:
1. mediafire.com/download/78r7kes21exsnbh/Calkulin's_Stock_OPO_XNPH05Q_ROM_v1.0.zip
2. mediafire.com/download/94o0lb0pzdg1drw/XNPH05Q_Extras.zip
-Extract the first zip. Again extract the zip from the extracted folder.
-Extract the XNPH05Q in the same folder where the all above files were extracted .
-The folder should have fastboot cmd. and you should have fastboot drivers installed .
-put your device in fastboot mode by turning the phone off and pressing volume up+power key simultaneously .
-open cmd in the folder where all of the above files were extracted . press shift and right click in the flder and open command prompt .
- look whether your device is detected by fastboot. type fastboot devices
-You need to have unlocked bootloader.(if not, type fastboot oem unlock)
-TYPE THE FOLLOWING COMMANDS IN THE COMMANDS IN THE ORDER AS GIVEN :
IMP: DONT REBOOT IN BETWEEN COMMANDS
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
You are all done. Sit back and relax.
Lock the bootloader again. After you are done with setting up. type fastboot oem lock
timmaaa said:
Oxygen doesn't use CM12 firmware, it uses firmware specific to Oxygen. This is why there are countless posts from people (who tried flashing CM12 after Oxygen without first flashing the right firmware) complaining that CM won't flash and their ROM won't boot, or that they're bricked.
Transmitted via Bacon
Click to expand...
Click to collapse
People are getting "stuck" not a hardbrick. because they won't wipe system and data. That's my only thought here as oxygen bootloader boots cm12. Also cm12 bootloader flashes/boots oxygen without issue my end...but I formatted system/data. If people want to mess about with fastboot when recovery does the same thing is up to them. People just need to use recovery in the right way for a successful flash.
Sent from my A0001
andrewwright said:
People are getting "stuck" not a hardbrick. because they won't wipe system and data. That's my only thought here as oxygen bootloader boots cm12. Also cm12 bootloader flashes/boots oxygen without issue my end...but I formatted system/data. If people want to mess about with fastboot when recovery does the same thing is up to them. People just need to use recovery in the right way for a successful flash.
Sent from my A0001
Click to expand...
Click to collapse
CM boots because the firmware is built in to the ROM zip, so it overwrites the firmware that Oxygen previously flashed. You're not booting CM with the Oxygen firmware, that's impossible. The Oxygen firmware is being overwritten. For every ROM other than CM you need to first flash the right firmware zip because the firmware isn't built into those ROM zips. Not one did I mention fastboot either, it isn't needed. I'm talking about the recovery flashable firmware zip.
And of course you should wipe system and data (along with cache and dalvik cache) when flashing a ROM, that's standard procedure for any ROM flash.
Where can I obtain the needed flashable zip files to revert back to cm11s?
Sent from my A0001 using XDA Free mobile app
Here:
https://mega.co.nz/#F!ooViWJYB!DWSVZpEJRQb-zpurGyM-mg
Both cm11 and 12 are in there. Flash in recovery then reboot recovery then flash ROM/gapps
Sent from my A0001
andrewwright said:
Here:
https://mega.co.nz/#F!ooViWJYB!DWSVZpEJRQb-zpurGyM-mg
Both cm11 and 12 are in there. Flash in recovery then reboot recovery then flash ROM/gapps
Sent from my A0001
Click to expand...
Click to collapse
I actually had it done already by the time I saw this but very much appreciated. I am sure it will come in handy for others.
timmaaa said:
CM boots because the firmware is built in to the ROM zip, so it overwrites the firmware that Oxygen previously flashed. You're not booting CM with the Oxygen firmware, that's impossible. The Oxygen firmware is being overwritten. For every ROM other than CM you need to first flash the right firmware zip because the firmware isn't built into those ROM zips. Not one did I mention fastboot either, it isn't needed. I'm talking about the recovery flashable firmware zip.
And of course you should wipe system and data (along with cache and dalvik cache) when flashing a ROM, that's standard procedure for any ROM flash.
Click to expand...
Click to collapse
Just to clear this up I had to find out why this is happening. Okay so my home brew cm12 builds don't compile firmware file's. I didn't know this but now I do. So this must have been the reason why I was able to keep oxygen bootloader on cm.
Sent from my A0001
somehow I could just revert to cm12.1
FYI,
In case it helps someone, I tried out OxygenOS last night and while it is stable I dislike many things (email client, text client) and the biggest beef of all is neither text nor email show on my Mazda.
Soooo this is a nono I believe, but I could restore CM12.1.
I just did a backup in TWRP of OxygenOS> then I did a clean wipe> then was able to restore CM12.1 nightlies from June1 I think it was and it seems just fine.
I believe it is because the modem etc in 12.1 is the same as OxygenOS had all along?
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
6andro said:
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
Click to expand...
Click to collapse
Just follow this...
STEPS:
1. Download http://builds.cyngn.com/cyanogen-os...263178b74/cm-12.0-YNG1TAS0YL-bacon-signed.zip
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Shankar9822 said:
Just follow this...
STEPS:
1. Download [lurl]
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Click to expand...
Click to collapse
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Update twrp first then flash. You will not loose personal data when doing the wipe.
Sent from my A0001 using XDA Free mobile app
6andro said:
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Click to expand...
Click to collapse
I think you are using the wrong version of TWRP.
http://dl.twrp.me/bacon/
Use the above link, download the latest version 2.8.6.0-bacon.img and flash it...
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
striker280 said:
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
Click to expand...
Click to collapse
It's normal for the stock recovery to be flashed during an OTA update. Yes you can flash it again. No it won't relock your bootloader.
Transmitted via Bacon