OTA updates, nightlies, partitions... - ONE Q&A, Help & Troubleshooting

I'm no stranger to flashing CM nightlies as it is quite routine for me in our household. Yesterday I restored my CM11s rom so that I could do the new OTA update.
Someone posted that they had to replace their modified mixer paths xml file with the unmodified file in order for the update to work. I decided to do the same since I had modified mine too. All went well with the update...
Here is my question: Is there usually a difference in what partitions get flashed when there is a major update such as the CM11s update from yesterday compared to doing a CM nightly update?

Related

[Q] CM11S before OTA update?

Looked through both dev subsections and can not find an offical release of CM11S before the 4.4.4 OTA update. Was wondering if anyone knows where it can be downloaded to go back to before the update. Thank you.
This is the zip i used to flash trough stock recovery.
Its the official 25R version signed by CM
http://dist01.slc.cyngn.com/factory/...con-signed.zip
Note : When i flashed this over the 30o update my trebuchet crashed all the time to fix this simply factory reset after update !

[Q] How do you update the Bootloader to the Lollipop Version?

An official CM12 commit for tomorrow's nightly will ask for the bootloader to be updated.
One way would be to flash back to stock and take the LP OTA update.
Alternatively, you may be able to find an LP ROM that is compatible with your phone, extract the motoboot file, and flash it using fastboot, although the safest would be via an OTA update.
audit13 said:
One way would be to flash back to stock and take the LP OTA update.
Alternatively, you may be able to find an LP ROM that is compatible with your phone, extract the motoboot file, and flash it using fastboot, although the safest would be via an OTA update.
Click to expand...
Click to collapse
Strange, I've seen steps for flashing Lollipop on CDMA devices that makes you first flash the full GSM fastboot package then the radio files - doesn't this mean the bootloaders are actually interchangeable?
Also, I found a link for XT1031's lollipop OTA, but unpacking it reveals nothing related to the bootloader...
EDIT: Sh*t - I updated manually to the new bootloader, but the existing CM12 starts to exhibit screen flickering issues (shaking stripe moving vertically across the screen). It seems the new bootloader needs to be paired with the new CM build.
Sent from ARChon Runtime @ Chromium 42
Yeah, the flickering will also be fixed by flashing a stock LP ROM.
audit13 said:
Yeah, the flickering will also be fixed by flashing a stock LP ROM.
Click to expand...
Click to collapse
Stock ROM isn't necessary - the latest CM build has it fixed The recovery still flickers though (because it's built upon 4.4 blobs?).
Sent from Google Nexus 4 @ CM12
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
No flickering in stock lollipop recovery, only custom I think
The last cm12 deals with the flickering I believe, but earlier builds have it.

[Q] OTA Updates to Stock ROM w/ Non-Stock Kernel and Recovery

Hey everyone,
So for the past couple of days I've been getting the notification that 5.1.1 has been downloaded and is ready to install, but I'm running a rooted stock ROM with CWM and ElementalX kernel, so I wasn't sure what would happen if I accepted the update. So my question to you all is just that; what will happen if I OTA update? I would imagine I'll lose root access and have to re-root, but would the OTA also flash a stock kernel and get rid of CWM? Or will the update create a load of problems since I'm not completely stock?
Thanks in advance for your help.
The OTA update will fail.
As of Lollipop, you have to have everything completely stock (including the recovery) to take an OTA update. You're better off just flashing another pre-rooted ROM or custom ROM which has been updated to 5.1.1.
Elluel said:
The OTA update will fail.
As of Lollipop, you have to have everything completely stock (including the recovery) to take an OTA update. You're better off just flashing another pre-rooted ROM or custom ROM which has been updated to 5.1.1.
Click to expand...
Click to collapse
Thanks for the help!

How to update CM 12 OTA

I am running CM12 on D800. As the nightlies are being built I get OTA updates too and update is downloaded. But when I install it the phone just reboots into TWRP recovery and nothing else happens. How can I update it?

OnePlus One WiFi issue when phone ISN'T locked

I was on 12.0-YNG1TAS17L I was having some issues with SMS message not sending sometimes plus the stage-fright stuff was vulnerable in this build so I decided to try upgrading to PACMAN rom 5.1 and was receiving an error to execute the updater binary. I finally found the solution to the issue, and that was to update to the latest nightly of CM to upgrade some firmware? Maybe it was radio related? I flashed that and while I was still in recovery I did another wipe followed by a flash of the PACMAN rom, which then worked. After using the PACMAN rom for a few days I was noticing some lockup issues and the WiFi kept dropping while I was using the phone. (Phone wasn't sleeping). I decided that I would just go back to CM and install the latest version. I flashed the latest SNAPSHOT build from 9/1. The WiFi issues are still occurring so it isn't ROM specific. I am thinking that the new firmware that was flashed during the nightly flash that I did caused the problem.
So has anyone else had this problem? If so is there an easy fix? If I flash YNG1TAS17L will it back out the firmware update? Thanks.

Categories

Resources