It's been a while since I've touched my OPO since I've been using my OPT as my daily. I'm still on YNG1TAS2I3 on my OPO running stock everything. At the moment it is not rooted, with no custom recovery, but the bootloader IS unlocked. I also had xposed installed with some modules but I ran the xposed uninstaller arm.zip version in TWRP and removed the modules.
Is it possible to dirty flash YNG4PAS1N0 which is CM12.1 onto my OPO? I've tried installing TWRP and then fastbooting CM12.1 but it causes a bootloop. I had to re-fastboot flash CM12.0 to get out of it. I've tried it with TWRP 3.0.2.0 and TWRP 2.8.6.0. I also tried sideloading it but again-- bootloop. Reflashing CM12.0 causes CM recovery to rewrite TWRP even though I don't flash the recovery partition. So it took me a LONG time to get TWRP installed again for all these trials.
At this point is my only option to do a complete wipe and then flash? Even trying to run the OTA update for YNG4PAS1N0 causes a bootloop.
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
MZO said:
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
Click to expand...
Click to collapse
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
crazykidguy said:
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
Click to expand...
Click to collapse
Then
Instead of normal flashing you should fastboot erase <partition> and then flash it.
Transmitted via BACON
Related
Hi, i'm on cm11s 25r, rooted with towelroot and twrp installed. I'd like to install 30o and 33r but the ota is not working with twrp ("error, can't install on top of incompatible package"or something like that)
I prefer not too lose all my data, apps and photos. Is there a way to update ?
Thanks !
What recovery are you on? There are some problems going on with TWRP 2.8.0.0, where you may have to revert back to 2.7.1.1 in order to flash OTAs.
Your steps are to flash 30O OTA and then 33R OTA.
Alternatively, you can start from scratch and flash 30O via fastboot but then you lose all your data.
zephiK said:
What recovery are you on? There are some problems going on with TWRP 2.8.0.0, where you may have to revert back to 2.7.1.1 in order to flash OTAs.
Your steps are to flash 30O OTA and then 33R OTA.
Alternatively, you can start from scratch and flash 30O via fastboot but then you lose all your data.
Click to expand...
Click to collapse
... I just flashed 2.8.0.0 this afternoon it might be related. i think i'll end up backing up all my data, unlocking my bootloader properly and flashing latest rom (i was trying to avoid that because downloading game data and apps takes forever with my "slow" internet )
coc014 said:
... I just flashed 2.8.0.0 this afternoon it might be related. i think i'll end up backing up all my data, unlocking my bootloader properly and flashing latest rom (i was trying to avoid that because downloading game data and apps takes forever with my "slow" internet )
Click to expand...
Click to collapse
Thats understandable, I always recommend people to unlock their bootloaders so when they do decide to tinker with their phones they can flash a custom recovery as well as back up all their data.
When you are fully unlocked and whatnot, get Titanium Backup (Pro recommended) and then you can use that to back up all of your apps/data so they stick on rom changes.
i installed titanium backup, downloaded stock rooted 33r, installed it, restored my apps/data , installed franco kernel r18 and everything is working :good: :good:
So guys, I've been at this for days.
I was originally using AK's kernel, TWRP Recovery and the official 44S ROM, but had issues with logging being disabled, so I fugured I'd go for the cm12 nightlies. I installed the latest AK kernel (102), updated TWRP to 2.8.4.1 and tried to dirty flash the 20150130 nightly, just to find that I'm stuck on the boot screen. I then on found about a firmware update that I installed after I wiped everything clean. Installed cm12 again and I was stuck in the same bootloop. I've even tried cm11 with the intention to OTA to cm12, but that had the same issue. That went through many different ROM's I've tried. I am kind of fed up by now and I would appreciate any input.
Thanks.
So you initially tried to dirty flash CM12 over CM11S? And you did that after flashing the AK kernel? If so you've got one major problem there: never dirty flash when switching ROMs or Android versions, you did both in one hit. And the minor problem: you're meant to flash a kernel after flashing a ROM, if you do it the other way around the stock kernel from the ROM zip just overwrites the custom kernel.
Anyway, I think your best bet is to flash the stock images with fastboot, see section 8 of my guide thread .
Transmitted via Bacon
I can flash any 11S rom, but the problem is installing and booting into cm12. But I think I'll just wait for 12S as it should come up soon. Would be cool if I had access to nightlies though.
Well' you can't win them all.
There's no reason why you shouldn't be able to flash the nightlies? Did you update your firmware appropriately before flashing CM12?
Transmitted via Bacon
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
tetakpatak said:
@timmaaa I am also wondering why does he face bootloop issues every time. If there is no essential change in the latest OTA update (like updated bootloader) maybe his recovery doesn't wipe /system properly.
Hey, @BigWaxx, did you manually format /system in TWRP before flashing CM12? If yes, maybe give a try with PhilZ recovery.
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
It's definitely possible, the firmware is the most likely culprit at this stage though.
Transmitted via Bacon
I have updated the firmware properly before that. Also no other custom ROM runs - not only cm12. I've tried cm11, OmniROM, TGM, BlissPop and temarek.
I have also tried CWM, but not PhilZ. I made sure to format everything - even internal storage. I've tried both F2FS and EXT4 as filesystems for /system.
I will try PhilZ though.
Cheers.
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
I'm testing CM 12.1 and came from the official Kitkat rom. I had to flash CWM via fastboot (thread here) in order to install CM 12.1. It worked, but I was stuck with that Cyanogen recovery that comes with CM 12.1. I tried flashing CWM and TWRP, but my phone went into a boot loop. I was forced to reflash 12.1. I also tried installing a newer version of TWRP via XZRecovery, but it got stuck and never installed anything. Here are my problems:
Can't make nandroid backups
Unable to flash Xposed zip for Lollipop 5.1
Is it possible to run CM 12.1 and have a regular recovery like CWM/TWRP?
I do, so yeah definitely possible. But I don't use a "regular" recovery, but the FOTA Recovery version of TWRP. This recovery is installed in a partition of the system which won't get overwritten by the CM Recovery when upgrading. Just search for "FOTA TWRP Z3" via google or XDA and you should be good to go.
Omario-242 said:
I do, so yeah definitely possible. But I don't use a "regular" recovery, but the FOTA Recovery version of TWRP. This recovery is installed in a partition of the system which won't get overwritten by the CM Recovery when upgrading. Just search for "FOTA TWRP Z3" via google or XDA and you should be good to go.
Click to expand...
Click to collapse
I've been on Kitkat for about 4 months and have no idea how I missed that. I installed it and it works perfectly. Thank you!