Hi
I'm running DP4 and installed TWRP and xceed kernel.
I tried to install DP5 with the automatic OTA update but when it rebooted, it booted on TWRP asking me if I want to keep the read mode only or allow modifications. I chose 'keep read only'. Then on the reboot, Android started normally but i'm still on DP4. Update check is saying i'm up to date...
How can I update to DP5 ?
How to do to keep TWRP and xceed kernel ?
Thanks a lot !
OTA updates won't work with a custom recovery. Download the zips from the Android development forums and manually flash them in TWRP, or fastboot the images which can be downloaded from google.
Sent from my Pixel C using Tapatalk
Related
I have a system update available, but whenever I try to flash it, it ends in an Error 7 in TWRP. The stock rom, I did a factory restore on it. But it was rooted with magisk, and phh superuser before I had to do the factory reset on it. Could it be some of the SuperSU stuff is left over and that is why it keeps throwing that error?
you've provided zero information about your current setup and what version you're updating from/to
you could be talking about OOS OTA updates or CM OTA updates or even a custom CM-based ROM OTA update for all we know.
Sorry, it is oxygen OS, version 3.2.4. I think it updating to version 3.2.5. I did a factory reset, and have not rooted or anything with the exception of flashing Twrp.
Flash patched TWRP via fastboot.
Tried to side load it, it still failed with error 7.
Edit: It looks like I am trying to go from 3.2.4, to 3.2.6. But still not sure what if stopping me from being able to install the update.
i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!
You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.
neeraj679 said:
You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.
Click to expand...
Click to collapse
should I flash any other rom or the oos 4.0...???
pranav_j619 said:
should I flash any other rom or the oos 4.0...???
Click to expand...
Click to collapse
which twrp version are you using? also do you have encryption issues in twrp? you might not need to reflash the rom butmay be reset the phone and install updated twrp. there are couple of threads. i myself saw this issue on my device
I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.
You can flash newest BluSpark TWRP and the the 4.0.2 Full ZIP, then it should work
This is the solution that worked for me
MM MaD said:
I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.
Click to expand...
Click to collapse
I had the same issue, flash the stock recovery 2.0 on the phone (the one that takes 64Mb) and then boot the phone. As mentioned it'll fail but then you get out of the loop and can flash whichever recovery and rom you feel like. And thanks for the people that mirrored the recovery while it was not on the official page, and to the people that suggested this, it was a pain to fix the first time.
pranav_j619 said:
i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Had this issue before, just look on your internal memory, there is a folder called ".OTAsomething", in there the OTA zip is stored, delete it and the phone will boot to Oxygen OS again.
Im running stock ROM 7.1.1 with Latest ElementalX Kernel and latest Magisk + MagiskSU. Also Running latest TWRP 3.1
I haven't updated yet. so I have the march patch, and this recent patch im behind on my 5x. I thought maybe i could just accept the OTA and just reflash magisk and the elementalX kernel afterwards. Oh, and likely would have to do TWRP as well. But accepting the update clicking to restart and install just rebooted me into TWRP. Flashfire doesn't work yet either been waiting a month on that. I get that failure during "uncrypting" error.
I'm slightly new back on the modding scene, until recently have been out of it for years. I did recently make a mistake with an audio mode and had to download the full image and use fastboot to throw that back on my device. Anyway with 7.1.2 out i really do want to update so i need to do it manually, and hopefully without losing my data. (or having to restore it from a backup if possible anyway)
I'd read somewhere that you can download the full images and extract the updated images you need and flash them to your device then your respective addons root kernel ect.. There seems to be lots of way to go about it, but little clear on how to do this so that's what brings me here to this post. What's the best way to manually update (add security patches) if im running Magisk and magiskSU.
Thanks in Advance.
https://elementalx.org/how-to-install-android-monthly-security-updates/
After you flash the /system /boot /vendor (I would also do bootloader and radio), reboot into TWRP and install kernel & Magisk.
Hi,
I have Stock Android 8.1.0 ROM from February installed and also Magisk.
I wanted to install March OTA-Update but it just throws "Error" while trying to install OTA-update and reboots back to previous ROM with the hint, that "update could not be confirmed".
Any ideas how to get OTA-Updates to work?
Regards
jsfgsdfhakjf said:
Hi,
I have Stock Android 8.1.0 ROM from February installed and also Magisk.
I wanted to install March OTA-Update but it just throws "Error" while trying to install OTA-update and reboots back to previous ROM with the hint, that "update could not be confirmed".
Any ideas how to get OTA-Updates to work?
Regards
Click to expand...
Click to collapse
OTA's won't work if you're rooted. Get Chainfire's flashfire and flash the ota there. They're are options to retain custom recovery and root.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
OTA's won't work if you're rooted. Get Chainfire's flashfire and flash the ota there. They're are options to retain custom recovery and root.
Click to expand...
Click to collapse
Hi,
but should it not be the reason of using Magisk, that OTA updates are functioning, because it doesn't change the system file system?!
Or does OTA system update also checks the boot loader integrity before updating?
At what state of changing device do OTA updates not work anymore?
Already after unlocking bootloader?
Is there no possibility to get root access and Google OTA updates beside Chainfire's Flashfire?
Magisk, as well as SuperSU, are both systemless root methods. But they also affect the boot image. You need the stock boot image for the ota to work. Magisk can revert the boot image to stock, but I'm much more familiar with using flashfire.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Magisk, as well as SuperSU, are both systemless root methods. But they also affect the boot image. You need the stock boot image for the ota to work. Magisk can revert the boot image to stock, but I'm much more familiar with using flashfire.
Click to expand...
Click to collapse
I restored boot image, tried flashfire but nothing worked for me on my phone.
OTA update still throwed the error after restored boot image.
flashfire throwed a black screen after rebooting and did nothing for a lot minutes. I did a hard reboot after some time.
Finally I did the update manually:
image backup with TWRP boot loaded by Fastboot only
download Google stock ROM from march
extracted ROM
disabled wipe parameter in flash batch file
flashed now
reinstalled current Magisk by TWRP boot loaded by Fastboot only
Finished. :silly:
Nexus 5x
I tried using flashfire myself and got the same results that you did. Thanks for the info. I guess we have to flash the entire ota zip from the google developer site and not just the update.zip.
jsfgsdfhakjf said:
I restored boot image, tried flashfire but nothing worked for me on my phone.
OTA update still throwed the error after restored boot image.
flashfire throwed a black screen after rebooting and did nothing for a lot minutes. I did a hard reboot after some time.
Finally I did the update manually:
image backup with TWRP boot loaded by Fastboot only
download Google stock ROM from march
extracted ROM
disabled wipe parameter in flash batch file
flashed now
reinstalled current Magisk by TWRP boot loaded by Fastboot only
Finished. :silly:
Click to expand...
Click to collapse
I did some searching, but could not see a guide for moving from Magisk rooted 8.1.0 to Magisk rooted 9.0. I believe I need to uninstall Magisk, then install the update, but not sure of the exact process. Also, is it better to wipe the data when going from 8.1.0 to 9.0 or doesn't matter?
Thanks in advance!
There's two ways you can do this.
One, you can sideload the OTA using ADB (if on stock recovery), or you can flash the OTA through TWRP.
Two, you can download the factory image, and manually flash the bootloader and radio, then update /system WITHOUT the -w flag, if you don't want to wipe data.
Any time you flash a software update, whether it's the OTA or the factory image, it WILL overwrite /boot, so you will lose Magisk and any custom kernel and recovery. Simply boot TWRP using fastboot, flash Magisk (and TWRP and kernel if desired), and you'll be good to go.
No need to wipe data. My process for installing OTAs and re-rooting has always been the same and it's no different with the 9.0 update other than one exception I encountered (patching the boot image AFTER updating).
I prefer the boot image patching method:
Download the latest platform-tools from Google
Download both the OTA and full factory images
Extract boot.img from the factory image
If already rooted prior to updating, re-flash current stock boot image
Sideload OTA
Patch the extracted boot image with Magisk (make sure you're on the latest version; 16.7 beta channel)
Flash patched boot image
Normally I patch the boot image prior to sideloading the OTA but it resulted in an endless boot after the 9.0 update.
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
machx1111 said:
Thanks guys. I actually found a thread I bookmarked previously on this topic. Do you think this would work well still? :
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
Also I saw some people mentioning trouble with Magisk after 9.0 update. Did you encounter that or anything special to consider there?
Click to expand...
Click to collapse
Here's a bit more specific guide for updating to 9.0
https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77269862