Database Develop

Nexus 6 boots into TWRP when trying to install system update?

I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!

You cannot apply Google OTA updates with a custom recovery. Replace your recovery with the stock version and try again.

Not just custom recovery - any system change such as root will stop the OTA. Depending on how you rooted, you might be able to unoot using the built-in SuperSU function (I'm guessing Supersu?) but more likely than not it still won't work.
The simplest thing to do is forget about the OTA entirely. Download the full ROM from Google, unzip it, unzip the zip inside the zip, and there you'll find system.img, which you can flash in Fastboot, then reroot. Done.

sonic2kk said:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
Click to expand...
Click to collapse
How did TWRP ended on your phone in the first place?

istperson said:
How did TWRP ended on your phone in the first place?
Click to expand...
Click to collapse
I installed TWRP.
Thanks for the suggestions everyone!

sonic2kk said:
I installed TWRP.
Thanks for the suggestions everyone!
Click to expand...
Click to collapse
Oh, then as other people said, if you want OTA then totally unroot it, then reflash system of the current version, and flash stock recovery. But it's much better when a new version arrives, just download it, flash system and boot, reroot it, clear cache and dalvik. This way you'll have your updated Android days or even weeks before the OTA.

Verizon Note 9 March security patch rolling out OTA

Just got a notification for update 6 on my VZW Note 9. This should be build 1CSC1 with the March security patch included. I haven't had a chance to update my phone yet.
Also, I sideloaded builds CSAA and the current CSB3 that I'm on now, via stock recovery and SD card and I'm receiving official OTA's from my carrier. I know some were worried they may not receive official OTA's if they sideloaded those builds. I'm just re-confirming what others such as Mr. Orange have said that you will be back on the official OTA train being on the sideloaded CSB3.

Thank you. I am waiting for an update since I sideloaded Pie last month.

CliftonFoster said:
Thank you. I am waiting for an update since I sideloaded Pie last month.
Click to expand...
Click to collapse
Yeah, no problem. Just wanted to get it up asap to let those who still worried about not getting official OTA's anymore because of sideloading, that they will still get official OTA's as long as they're on CSB3. Here's a screenshot of the about screen with the new build running, I didn't update till recently.

The big question is whether or not Substratum/Swift Installer is still working with this update.

Guyinlaca said:
The big question is whether or not Substratum/Swift Installer is still working with this update.
Click to expand...
Click to collapse
Still working on my end

tgee0907 said:
Still working on my end
Click to expand...
Click to collapse
Please help if anyone knows an answer to my issue. I have a Verizon note9 I updated from oreo to pie manually through recovery now I am no longer getting ota updates,even if I search for them. I was told that side loading pie would not effect later OTA's . Is there a way to fix it or I somewhere I can download the updates and install through recovery would be ok too. But can't find them anywhere.

Azag Thoth said:
Please help if anyone knows an answer to my issue. I have a Verizon note9 I updated from oreo to pie manually through recovery now I am no longer getting ota updates,even if I search for them. I was told that side loading pie would not effect later OTA's . Is there a way to fix it or I somewhere I can download the updates and install through recovery would be ok too. But can't find them anywhere.
Click to expand...
Click to collapse
Which version of pie are you still on? CSAA? If still on CSAA, you'll have to install the CSB3 pie build. The CSAA to CSB3 zip to put on your SD card and flashed through stock recovery can be found here within the Note 9 threads. Once you're on CSB3, you'll get OTA update notifications for the next couple OTA updates.

Justinphxaz said:
Which version of pie are you still on? CSAA? If still on CSAA, you'll have to install the CSB3 pie build. The CSAA to CSB3 zip to put on your SD card and flashed through stock recovery can be found here within the Note 9 threads. Once you're on CSB3, you'll get OTA update notifications for the next couple OTA updates.
Click to expand...
Click to collapse
Odin files for April CSD1 build are listed in another post.

Does anyone happen to have a link for that CSB3 zip

Azag Thoth said:
Does anyone happen to have a link for that CSB3 zip
Click to expand...
Click to collapse
Why Not Odin To Latest April Patch CSD1 build

Venom0642 said:
Why Not Odin To Latest April Patch CSD1 build
Click to expand...
Click to collapse
I do not have Odin setup and have never used it . Plus do not have access to a computer at this time. Also would just like to flash it off sd card and start getting my ota updates again. I have the file but it keeps aborting not sure what the issue is .my sd card is encrypted do I have to decrypt it before flashing the update?

Alright got the file (cbs3) and flashed from recovery, and then my ota updates started coming in so I am all updated and life is good. Now I'd I could just figure out why a week ago I stop being able to download apps or update installed apps from xda (from here) not sure what happen or why but when I try it starts to go through the motions ana them I get download failed. Any ideas would be greatly appreciated. I have tired all the usual fixes, clear cache and data uninstall and reinstall xda app,no help...

Unlocked EEA 10.2.22 will only download corrupted OTAs

Hello,
I found out that my EEA Mi 9 (128 if it matters), that I just unlocked and rooted on 10.2.17, wouldn't download proper zips when updated to 10.2.22
I'm explaining a bit more:
- Unlocked on 10.2.17
- Rooted via patched boot and fastboot the 10.2.17 boot.img
- Updated to 10.2.22
- Lost Root
- Used Mi settings to re-download the ZIP since the official MIUI site doesn't have the latest 10.2.22
- All zips are corrupted
I could update the boot.img thanks to this thread here, but I'm starting to believe that I will have, when the next update comes, download it, copy it before installing it...
Question 1
Has anyone experienced not being able to download 10.2.22 when "on 10.2.22"...?
Question 2
How do people "get" the OTA URL before miui.com ?
Thanks,
Edit : Sorry for the obnoxious editorial, but I already got 2 people postings random answers without reading the post.

Download full ota via pc then install

emprazol said:
Download full ota via pc then install
Click to expand...
Click to collapse
The official MIUI site doesn't have the latest 10.2.22 EEA
Check for yourself : https://en.miui.com/download-361.html#588
Since it doesn't go through the Android "Download Manager" I CANNOT magically guess the ZIP OTA URL like "http://bigota.d.miui.com/V10.2.22.0.PFAEUXM/miui_CEPHEUSEEAGlobal_V10.2.22.0.PFAEUXM_745a374eee_9.0.zip"
Someone with a usefull hint?

RedWave31 said:
The official MIUI site doesn't have the latest 10.2.22 EEA
Check for yourself : https://en.miui.com/download-361.html#588
Since it doesn't go through the Android "Download Manager" I CANNOT magically guess the ZIP OTA URL like "http://bigota.d.miui.com/V10.2.22.0.PFAEUXM/miui_CEPHEUSEEAGlobal_V10.2.22.0.PFAEUXM_745a374eee_9.0.zip"
Someone with a usefull hint?
Click to expand...
Click to collapse
https://forum.xda-developers.com/Mi-9/how-to/xiaomi-mi-9-firmware-twrp-recovery-root-t3922158:)

Kaeru Sapporo said:
https://forum.xda-developers.com/Mi-9/how-to/xiaomi-mi-9-firmware-twrp-recovery-root-t3922158:)
Click to expand...
Click to collapse
I don't accept your answer. I don't care about the OTA link. I already have it. You didn't read my post at all...
Questions are:
- Is someone else having corrupted ota zip problem
- How do you get the OTA URL without waiting for someone to post on XDA

How can I install an OTA update from downloaded file

I don't want to install the latest Android 12 OTA update. I have downloaded an OTA file for the Note 9 Android 11 update. How can I install this file? The phone currently runs 12.0.8.0 Global firmware with Android 10.

mars08 said:
I don't want to install the latest Android 12 OTA update. I have downloaded an OTA file for the Note 9 Android 11 update. How can I install this file? The phone currently runs 12.0.8.0 Global firmware with Android 10.
Click to expand...
Click to collapse
Go to the updater, 3 points at the top right, select an update file.

NOSS8 said:
Go to the updater, 3 points at the top right, select an update file.
Click to expand...
Click to collapse
Thanks for the quick reply. Would I use the OTA file or the recovery download? Does this process delete my current apps, settings and data?

mars08 said:
Thanks for the quick reply. Would I use the OTA file or the recovery download? Does this process delete my current apps, settings and data?
Click to expand...
Click to collapse
If the update was offered to you by OTA, use OTA.
With the recovery rom, you force the update, the installation can be refused or caused a bootloop.
The installation will not erase your data.
If the bootloader is unlocked in case of bootloop, you can recover your phone, if you lock it will be more complicated.

Thanks for your advice. I'm going to back up my apps and data just in case something goes wrong... then I'll go with the OTA update.

Question OTA Update Fails With "Installation Problem"

NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.

Maybe Oxygen Updater has full download link?

BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.

kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?

BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.

kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)

BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.

Did you flash stock recovery to both slots the last time?

g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?

BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.

g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.

BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.