Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!
youssefkr said:
Hey everyone, I have a pixel 2XL rooted with stock recovery (and stock firmware).
I was wondering if I can get OTA updates ? I thought I could receive them and install them (and then re-root of course), but I still haven't received the March OTA yet.
Thanks!
Click to expand...
Click to collapse
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:
Badger50 said:
You'll likely get the notification, and it might even download, however, it won't install. But no biggie, you can either fastboot the monthly updates, or flash the OTA zip in twrp. Either way, you'll still have root it again :good:
Click to expand...
Click to collapse
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.
youssefkr said:
Thanks, but I thought the whole point of keeping the stock recovery is that I could install OTA directly ?
In that case I should probably flash TWRP.
Click to expand...
Click to collapse
Stock recovery yes, however, root is the ota killer as well :good:
There was a moment that flashing twrp would brick the phone and that they made it where you couldn't flash twrp anymore
Looks like they found a work around
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Sent from my Pixel 2 XL using Tapatalk
Related
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Snowby123 said:
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Click to expand...
Click to collapse
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Batfink33 said:
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Click to expand...
Click to collapse
Thank you very much! I am glad that some one had an explanation!
How can I restore to stock recovery for LMY48L? There is no LMY48L factory image, so I can't just extract the recovery out of there. Is there any way I can manually apply the LMY48L OTA's recovery to the recovery image in the LMY47V factory image to get a "stock" LMY48L recovery?b
EDIT: Never mind, it looks very complicated. I ended up just flashing LMY47V recovery and system images, then re-updating to LMY48L, then finally updating to LMY48P. I didn't mean to hijack the OP's thread, but I asked here because it looked like he would run into the same issue as I did.
So some might remember me awhile back ago... https://forum.xda-developers.com/pixel-xl/help/unlocking-verizon-bootloader-t3557290
I got tired of not having a unlocked/rooted device since I just dropped so much money on a new phone for my 27th bday sooo I took it back to verizon and swapped it for a new one. I was having the battery problems where my phone would hit 30-15% and just die on me OR the screen would die on me but the phone stayed on no problems.. I'd be in a phone call and the screen would shut off and I couldnt get it to turn back on without plugging in a charger or battery bank.
I've got my new phone now and everything is working flawlessly.. It's unlocked, has twrp installed and rooted just fine..
Now I remember seeing something about once I unlock/root the device my OTA becomes disabled so where do I get the OTA update for the device so I can go to 7.1.1 or later this month 7.1.2? I found this https://developers.google.com/android/ota and I see the 7.1.1 update but it's 800mbs which means I'm guessing if I flash that i'd be completely reinstalling a new copy of android and lose all of my data and have to go through setting up my phone again etc..
How do I just get the update itself and flash that? When I use the OTA on my Pixel XL the download is only like 200MB it doesn't install though just says it failed. Still new to all of this but I'm learning and how else am I gonna learn if I don't ask questions
a point in the right direction would be great.
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
https://developers.google.com/android/images
Sent from my Pixel XL using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Point point
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
[QUOTE=
If you go to that link in the post above you can download the newest firmware. Unzip it and open the bat file with note editor or something like that and remove the -w and it will update without losing your data.
Dimmizer said:
These images are even bigger than the ones I linked.. the 7.1.1 update is 1.8GB? the file I'm downloading via my Phone is 282.1 MB?
Click to expand...
Click to collapse
You use your original link and sideload it with TWRP.
TonikJDK said:
You use your original link and sideload it with TWRP.
Click to expand...
Click to collapse
Thanks
Upper left corner Link to OTA's smaller
Sent from my Pixel XL using Tapatalk
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Dimmizer said:
Now one last question...
From official TWRP webpage it says
Never try official ota updates using TWRP. Its not recommended. should I wait to update to 7.1.1 or flash? any pros/cons?
Thanks for all the help and ansrewing of questions so far
Edit: should I unroot and try to OTA again and if it works just reroot the device?
Click to expand...
Click to collapse
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
You did not decrypt it. That isn't currently doable.
TonikJDK said:
You are unlocked, so the only danger here is that you bootloop and lose your data. Make sure your data is backed up and sideload the ota with the directions on googles ota page and re install TWRP.
That's the easiest way and pretty darn safe. I dont recall seeing anyone having trouble with that.
Click to expand...
Click to collapse
Doing what you said now
[
Dimmizer said:
Looking at unrooting my device so I can do OTA updates via the phone and then I'll just reroot again but during the unroot process it says
Attempt to restore stock boot image? This is require for OTA's to succeed. If you manually decrypted your device, note that this might prevent my device from booting.
How do I know if I manually decrypted it? I used depixel8 to unlock bootloader and used SuperSU to root so am I safe to proceed or should I not attempt to restore a stock boot image?
Click to expand...
Click to collapse
I wouldn't unroot with that, doesn't work all the time just flash the newest firmware and you will be unrooted. You are going to have a bad time if you do.
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Hit the link below, it explains it well and you will see it worked for others.
https://forum.xda-developers.com/pixel-xl/help/rooted-twrp-recovery-how-update-ota-t3524279
If you ever bootloop don't freak, its an unlocked google phone. Flashing back to stock is easy.
The only thing that was in question was the bootloader unlock, once its unlocked your safe. It wont relock unless you lock it. But, if you do lock it, its locked for good. Afaika
Sent from my Pixel XL using Tapatalk
Dimmizer said:
lol... I know this isn't that hard and I'm just being paranoid cause I don't wanna brick my phone etc. but also it's like ALLLL this work just so I can flash new android update to my phone... and this whole thing seems to be taking longer than it really needs to.
Click to expand...
Click to collapse
Dimmizer said:
mk so another question..
https://twrp.me/faq/officialota.html
twrp says NOT to flash ota with twrp? so should I flash back to a stock recovery or just use twrp? if so how? lol
https://developers.google.com/android/ota
The google site explains what to do but I'm assuming it's explaining things as if I had a stock recovery and I don't..
Click to expand...
Click to collapse
I flashed OTA with twrp on my buddy's pixel for the Feb update worked just fine. Just make sure it's the OTA and not the factory image. But the best way would be using fastboot
Most anything you flash (stock updates, custom roms, will overwrite recovery. But not a problem, you just re-boot it to flash it, or just boot it and flash su and reboot device.
Sent from my Pixel XL using Tapatalk
awesome , thanks again everyone for your time and the help, very much greatly appreciated.
Hi,
This guide is based in my first post about how to do it with the Moto G4: http://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
(Read it for full info).
Then, here the updated info for the Moto G5+:
1) If you are in NPN25.137-33 and like to apply the last OTA, but you have rooted and/or flashed a custom recovery (TWRP) + custom kernel, then you can.
2) Requirements: original SYSTEM and BOOT partitions. If you have flashed another version, then restore the originals. You can use any backups from you, or you can download from here: http://drive.google.com/open?id=0B6-Tz_7kDyxsZnVNa0pldnhndG8
(Thank you to GtrCraft: http://forum.xda-developers.com/showpost.php?p=72387571&postcount=15)
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Warning: Don't install this OTA if you don't have the exact version of the required firmware.
4) After install the OTA, reboot and check the new version. At that point the ROM isn't rooted. Then, you need to re-root.
That's all!
Tried flashing and it fails.
You need stock recovery to flash OTA's
GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
3) To apply the OTA download this ZIP and install it from the TWRP recovery (it's not required to have the TWRP flashed, you can start it from the fastboot util): http://www.sendspace.com/file/7w75rw
This file is the original OTA (shared by the user olive23) and patched by me to remove the check for the fingerprint of the running firmware. Then it can run over the TWRP.
Click to expand...
Click to collapse
bvsbutthd101 said:
Isn't that the point of this post? He said he patched the OTA update so it could be flashed with TWRP.
Click to expand...
Click to collapse
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
bvsbutthd101 said:
Tried flashing and it fails.
Click to expand...
Click to collapse
Because isn't for your device OR you have modified SYSTEM or BOOT.
GtrCraft said:
You need stock recovery to flash OTA's
Click to expand...
Click to collapse
FALSE!
GtrCraft said:
Well the OTA isn't meant for reteu firmware. So that will bring problems with it
Click to expand...
Click to collapse
TRUE! :silly:
manos78 said:
Because isn't for your device OR you have modified SYSTEM or BOOT.
Click to expand...
Click to collapse
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
bvsbutthd101 said:
Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
manos78 said:
Probably. This OTA is from user "olive23".
I don't have (still) received any OTA in my XT1685 (EU 3/32).
Click to expand...
Click to collapse
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
bvsbutthd101 said:
Installing TWRP and rooting doesn't change the SYSTEM or BOOT right? Must just not be for my device then. I have the US 4gb model (XT1687)
Click to expand...
Click to collapse
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
bvsbutthd101 said:
Here's the OTA for the US 4gb model if you're interested. :good:
https://drive.google.com/open?id=0BxqNotAWlwLUQ1Fzcjc2YXd4QzA
Click to expand...
Click to collapse
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Dahenjo said:
I have the same US model and this is supposed to be for it but it didn't work for me either, got errors during flash of OTA zip in TWRP that various partitions weren't accessible &/or verifiable. Even tried it a second time after a full restore to stock and had similar errors. I restored SYSTEM too (not sure that our rooting process works for systemless yet, meaning it would change SYSTEM), so that wasn't the problem in my case. Restored stock again and will wait to see if I get OTA normally.
So did you get this OTA normally as a system update, indicating that we should be receiving it now?
Click to expand...
Click to collapse
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
bvsbutthd101 said:
I got the update weeks ago. I've been postponing until someone makes it's flashable. I ripped it from my phone when I got it so yes, it's from my phone.
Click to expand...
Click to collapse
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Dahenjo said:
Thanks. I wonder why I haven't gotten anything and had phone since it came out on 3/31. I'm on NPN25.137-33 with a 4GB XT1687 from Amazon ($299 full-price without ads) on AT&T if carrier matters. Rooted or not we should still get the notifications as you have.
Click to expand...
Click to collapse
Yeah I got mine the day it came out from amazon, using on Verizon.
Here is a flashable stock zip based on reteu firmware:
https://drive.google.com/open?id=0B6-Tz_7kDyxsU2NlTERsSzZsalk
U have*67 files??
Same Here
US variant XT1687 4/64GB on Sprint but no OTA notification. Maybe I should just wait another week before flashing this. Not sure if there is something in the SIM the server notices and stops updates on some carriers. But maybe the SIM is how they decide, not sure what else they could go by other than IP to detect the carrier.
bvsbutthd101 said:
Yeah I got mine the day it came out from amazon, using on Verizon.
Click to expand...
Click to collapse
I also have XT1687 4/64G US on 25.137-33 + root & TWRP, and no OTA notification.
So, is there a way to go to -67 (flash over TWRP, restore back to -15 stock)?
I could not understand the right answer from all the thread on the subject.
Sorry for this noob question: I have just rooted a brand new phone. After the first login the OTA warning popped out so I downloaded it. When finished I got a loop on the recovery; I fastbooted boot and got my phone working again ... what do I have to do? Thanks.
Hi,
My upgraded guide: http://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
wy1d said:
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
Click to expand...
Click to collapse
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
mac796 said:
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
Click to expand...
Click to collapse
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
mac796 said:
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
Click to expand...
Click to collapse
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
mac796 said:
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
Click to expand...
Click to collapse
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
wy1d said:
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
mac796 said:
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
Click to expand...
Click to collapse
Such a bummer the Magisk method doesn't work anymore. It's definitely the safest and most graceful.
Sent from my Pixel 2 XL using Tapatalk
Currently running Oreo 8.1 with magisk root and TWRP installed. I have access to no other devices other than my pixel XL.
Is there a way to update to Stock 9.00 in this situation without losing TWRP or the ability to root with magisk?
Flash ota with twrp.
Then flash twrp and magisk and reboot.
Probably will want to wipe and start 9.0 clean.
Sent from my Pixel XL using Tapatalk
lafester said:
Flash ota with twrp.
Then flash twrp and magisk and reboot.
Probably will want to wipe and start 9.0 clean.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Maybe I am being dense, but how would he flash TWRP (after flashing the OTA with TWRP the 1st time) without a computer to then fastboot boot the twrp.img? The OTA will revert recovery to stock, so he won't be able to flash the twrp.zip and magisk.zip.
You are still in twrp, so just flash the zip.
Sent from my Pixel XL using Tapatalk
lafester said:
You are still in twrp, so just flash the zip.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I said I might be dense. I haven't flashed anything in TWRP without rebooting immediately in a long time since I remember folks having issues flashing Magisk after the TWRP.zip (or flashing anything after an OTA) without a reboot. Good call though. It's worth a try.
sliding_billy said:
Maybe I am being dense, but how would he flash TWRP (after flashing the OTA with TWRP the 1st time) without a computer to then fastboot boot the twrp.img? The OTA will revert recovery to stock, so he won't be able to flash the twrp.zip and magisk.zip.
Click to expand...
Click to collapse
he first would have to download Full OTA from google, not the incremental ota that he receives in the phone. He also could download the incremental ota, but that he would need to capture that incremental ota url. So, it's much easier to download the full ota because the links are publicly shared by google.
onesolo said:
he first would have to download Full OTA from google, not the incremental ota that he receives in the phone. He also could download the incremental ota, but that he would need to capture that incremental ota url. So, it's much easier to download the full ota because the links are publicly shared by google.
Click to expand...
Click to collapse
Gotcha. I have done the full OTA through TWRP (mostly just to see if it worked), but it has been well over a year since using OTA through TWRP quit working for at least one TWRP build. When that happened, I quit playing with it at all and have used nothing but the flash-all (minus the -w of course) since then. I just remember there being a bunch of errors if you continued to install in TWRP without doing a reboot device after an OTA (and even other zip installs).