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
Related
I just got the KRT16S OTA update, how can I update keeping root? Would root keeper do the trick?
You'll lose root, but you can root it again by installing supersu binary from recovery mode or custom recovery.
Sent from my Nexus 7
Worked. Thanks
I received the OTA update (SRT16S) this evening. I was previously rooted with SuperSU 1.69 and TWRP.
When I boot into recovery, it comes up and says "No command" -- how do I re-install SuperSU?
My Nexus 7 works fine otherwise, just no root.
ncshawng said:
I received the OTA update (SRT16S) this evening. I was previously rooted with SuperSU 1.69 and TWRP.
When I boot into recovery, it comes up and says "No command" -- how do I re-install SuperSU?
Click to expand...
Click to collapse
Same way you installed the first time.
boot to bootloader
fastboot boot twrp.img
choose install
select supersu update.zip
sfhub said:
Same way you installed the first time.
boot to bootloader
fastboot boot twrp.img
choose install
select supersu update.zip
Click to expand...
Click to collapse
Ok, thanks -- that's what I figured it would have to be but wanted a confirmation.
I updated TWRP in TWRP via zip flashing and now whenever I try to reboot my phone, it only boots back into TWRP.
Previously, I was unlocked bootloader and rooted on stock.
Would appreciate any help. Thanks
I've never installed TWRP on this phone, but here is one thread Google returns that seems to be similar.
https://forum.xda-developers.com/pixel-xl/how-to/twrp-bootloop-flashing-twrp-t3533765
One relevant thing that has changed since the time of that discussion is that the May and newer bootloaders require a signed boot image. When I installed the May update with SuperSU without signing the boot image my phone simply ended up switching to the other slot, but again I didn't have TWRP installed. There is a zip for signing the boot image and further discussion here.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Thanks for the response. Looks like I have to flash factory image and then the verified boot signer. I'll give it a shot and report back.
Fixed this rather easily using the June factory images. Flashed using flash-all.bat (and removed the -w) and things are updated and back to square one. Interestingly, I didn't need to sign the boot image.
Thanks for the help.
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
TonikJDK said:
facted;72562818 Interestingly said:
You don't need to sign unless you root or flash a custom kernel that isnt signed.
Click to expand...
Click to collapse
Do you need to use the signed boot image file if you are flashing an unrooted custom Rom? I thought you needed to use it when flashing anything that changed the boot image from stock, including flashing TWRP if it's going to be installed on the phone.
Actually now that I thought about it the signed boot image is SuperSu specific, isn't it?
Click to expand...
Click to collapse
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
alluringreality said:
My understanding is that at the last step before restarting the phone the boot image needs to be signed, if the bootloader has been updated to May or later. The stock image is signed, and I've read that ElementalX will also sign the boot image. If you install anything else at this time, such as TWRP or SuperSU or Magisk, then I think as the last step it's necessary to also sign the image. Now that you've updated the bootloader, my understanding is that you will need to sign the boot image if you install TWRP again.
Click to expand...
Click to collapse
yeah i am stock rooted with twrp on june 7.1.2. I had to flash the verifiedbootsigner-v8 when rooting with magisk and twrp. I did NOT have to flash it when flashing elementaX 1.12
We're can I download v8?
Sent from my Pixel XL using Tapatalk
The first post from the following link has the latest version of the Verified Boot Signer attached.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
335Deezl said:
We're can I download v8?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
cognitivedissonance said:
So, I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is Pixel XL forum.
Slowclap
Phalanx7621 said:
Slowclap
Click to expand...
Click to collapse
I have a Pixel C, rooted using the Nexus Rootkit, TWRP and SuperSU.
All was fine and was on build N2G48C.
I had an OTA notification for Oreo, so I downloaded the OPR6.170623.010 Oreo OTA file, and used FlashFire to apply this.
Now everytime it reboots it goes past the Google logo, then to the "waiting for fastboot command" screen. I've tried rebooting to Recovery and I get the same thing!
Google didn't seem to help, so please can anyone else help?
I was manually flashing rather then using flashfire, but I was getting the same problem. First, flash just the stock room (no root or TWRP) and check that it boots. Mine would, but every time I tried to flash TWRP, it would bootloop to fastboot.
You may want to download the full rom, not just the ota. You can modify the flash batch file to not wipe the tablet, or just flash the components.
What was finally successful for me was to flash TWRP and NOT let it finalize. It should ask if you want to mount R/W so it can keep the rom from overwriting the recovery. I told it no, then flashed the Magisk zip for root. I haven't tested SuperSU, but just replace it here to try. This got me a proper boot to Oreo, with Magisk working correctly.
If I understand it right, and I haven't booted to recovery to check, the rom will likely have overwritten TWRP. Worst case, I have to reflash recovery whenever I want to do a backup or update my rom, but that isn't something I do often on this tablet.
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
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
mkhcb said:
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
Click to expand...
Click to collapse
Since you are having problems with updating via OTA, suggest either using flash-all method or Android Flash Tool to update to March build. Then patch boot image using either Canary 24301 or Stable 24.3. Make sure to disable mods before rooting.
No such thing as a match update
mkhcb said:
So I had Magisk. I uninstalled it via the app, preformed a system update, then avoided the reboot, installed Magisk on the OTA partition and rebooted. This got me into fastboot mode multiple times until my phone booted. Now I booted up and I am in the Feb update partition with no Magisk. How do I root and update without losing my data?
Click to expand...
Click to collapse
I would use the Android flashtool and download the factory image , patch the boot image then flash it in fastboot. No loss of data, just make sure you don't check any of the boxes like 'wipe device' or 'lock bootloader' in flashtool settings
I just flashed March. Used all old school flashed with latest adb and fastboot
Disabled all the magisk modules just in case.
Patched March update boot file in Magisk
Had the update for Magisk and did not do it at this point, as I had heard people having issues with that.
booted into bootloader Flashall.bat removing -w
booted into phone, waited for update to finish in the notifications.
booted phone back into bootloader, installed magisk boot image
Booted phone back up
enabled all magisk modules
Updated magiskapp, then updated root via direct install
Rebooted phone
And all good