Question about rooting and OTA updates - Google Pixel 2 Questions & Answers

This is the first phone where I don't plan to install a custom ROM, and I don't know how OTA updates work while rooted.
Can they still be downloaded/installed normally while rooted? If so do I need to re-apply root each update? Does updating while rooted, or reapplying root afterwords wipe apps/settings?
I'm not sure if these are questions that can even be answered now, before anything has shipped, but worth a shot.

I might be wrong but I believe once you root you have to side load any OTA updates that come along and you may have to reroot and no this won't wipe ur phone

Flash Fire will be the way to go....

On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.

me_droid said:
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
Click to expand...
Click to collapse
I started with full image and removing the w.
Then Google started releasing OTA So I used flashfire and it worked fine.
I tried sideloading and it worked also.
During the whole period, I never lost root or hotspot accept for the last update I lost hotspot because of an update changing Carrier entitlement. So I had to go about modding system file but. My hats off to developers. I suggest everyone donates to the people who make things available.
Thanks,

There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Nice tutorial. Is there a way to install magisk any easier if I don't care about OTA's? Can't I just flash magisk and carry on or do I still have to worry about the A/B partitions?

I did this and now I'm stuck in a bootloop!
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I followed this procedure and everything seemed to be fine until reboot. At first it would attempt to boot, get to the screen with the G logo, and then after a few seconds reboot again, showing the unlocked bootloader warning screen. i interrupted the loop with the power button, and now I get to the G logo with the small grey animated progress bar going back and forth, but it hangs there and never completes booting..

Related

Unlock/Root/TWRP OTA updates?

I've only had two phones prior to this but I have always unlocked the boot loader / rooted the device / installed a custom recovery / installed custom ROMS.
I believe with my MOTO X 1st gen this disabled the OTA updates.
Is that the case with the Honor 8? I'm wondering if it is worth it to install TWRP at this point as there seems to be so little in the way of kernels and ROMS.
Would I still be able to use SU or Xposed modules without Root?
What is the best move with this phone?
I have unlocked my bootloader as well as rooted my Honor 8. The only way to get SU and Xposed is by doing both of these procedures(root involves getting TWRP).
As for any Xposed modules, I tried amplify+greenify but instead of getting better battery life, my standby time decreased significantly. I am not sure why, but for some reason my Cell standby was showing to be eating a ton of my battery. Another big problem was that the dialer app would not let me call anyone, it kept crashing whenever I tried to. Both problems were fixed after I managed to get amplify+greenify uninstalled. Currently I am just running YouTube AdAway and MinMinGuard which seem to work fine.
So at this point, is it worth unlocking bootleader, installing TWRP, and rooting your phone? Well if there are certain Xposed modules that you really want then sure, and if there are certain apps you like that require root, then yes go ahead and root your phone. Note that if you try any OTA updates, you will have to remove TWRP as having your phone automatically restart and try to install the update wont work.
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
pairustwo said:
Imagine that the Honor 8 receives an update to say, Nougat, what is the pathway to update for someone who has rooted their phone. Will the OTA be able to be flashed if a .zip is provided here? Would we need to flash an entirely new ROM?
This is what I faced with my MOTO X. When Marshmallow came out there was talk... but no one was working on the at phone any longer so was never able to update.
Click to expand...
Click to collapse
It doesnt matter whether or not your phone is rooted. You will get updates the same way, through OTA. Of course you can find .zip files to flash(although personally I am struggling to get the latest update flashed through TWRP).
The real question is for how long will we be receiving updates? Nougat is pretty much guaranteed with the new EMUI update. Huawei/Honor has promised up to 2 years of updates from what I have heard, but who knows what that actually means. They have also have a "partnership" with XDA, and the phone is decently popular so I am sure there will be a few roms, just not as many as say a OP3.
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
pairustwo said:
Why are people trying to flash via TWRP if the OTA updates still work after rooting and unlocking the boot loader?
Click to expand...
Click to collapse
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Rakeen70210 said:
Okay so I just figured it out, but for the OTA update to work after rooting and having a non-stock recovery, you need to go to Settings->Updater->Menu(located on the bottom)->Download latest full package.
The full package is ~1.6GB and the regular update is ~280mb. The full package will work even if you have TWRP installed. But if you want the regular 280mb update, you need to get rid of TWRP and go back to a stock recovery.
Of course you will need to reinstall TWRP and root your phone again after doing this update.
Click to expand...
Click to collapse
I see the full package but I cant click on this, nothing is happened when I click on this.
Nas42O said:
I see the full package but I cant click on this, nothing is happened when I click on this.
Click to expand...
Click to collapse
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Rakeen70210 said:
I am not sure what you mean. Do you mean you can see the text "Download latest full package" but it is greyed out? If so please check to see if you arent currently at the latest version. If there is another problem, you might want to try to find a .zip of the full package and flash it that way.
Click to expand...
Click to collapse
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Nas42O said:
Yes , not greyed , but red color , and cant click on this .
I downloaded a full update of B31 about 1.77giga , just copy to the phone and flash it in twrp ?
Click to expand...
Click to collapse
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Rakeen70210 said:
The exact latest update that I currently have is FRD-L04C567B150. I am not sure where you got your update but I suggest you just flash back to a complete stock image and try to update again from there.
Click to expand...
Click to collapse
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Nas42O said:
its normal , you live in India no ?
i'm live in European country , so update are different .. Last update for us is FRD-L04C432B130
Click to expand...
Click to collapse
No I am in the US. I am not sure about the EU version, but yes if you can find a .zip update file just put it on your phone and go into TWRP to install it. Might wanna make a backup too and wipe cache too just in case.
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Palindrom87 said:
So if i download the full package in update and install it, bootloader will still be open? No full wipe? And later i only need to install twrp and root the phone again?
Click to expand...
Click to collapse
Updating or wiping your phone does not lock the Bootloader. The only way to lock the Bootloader again is by doing it manually yourself.
Yes after doing a full update you will need to reinstall TWRP as it will be replaced with the stock recovery and then re-root your phone again.
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
pairustwo said:
Rakeen70210, you sound really confident about doing full updates after rooting. Will these full updates also replace the kernel?
palendrome87 and NAS420 could you guys report back with any success or errors you have flashing full updates?
Where can one download full updates for Honor 8?
Click to expand...
Click to collapse
Seeing as how the full update package was ~1.65GB in size, I think its ok to assume that it replaces everything with the stock Honor 8 image. So yes it will replace the kernel too.
For downloading full updates, the only way I got mine was an OTA directly from the phone itself. Look at my previous comments to see how I got this update. If for some reason you cant update, check if your model is ready for an update. If it is and you cant update, try to flash back to a stock image. You should be able to find one on this site or anywhere else.
Flash stock recovery will lock boot loader ?
Nas42O said:
Flash stock recovery will lock boot loader ?
Click to expand...
Click to collapse
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Rakeen70210 said:
No, the only way to lock the bootloader is to manually lock it yourself using a similar operation to unlocking it.
Click to expand...
Click to collapse
I thought the same thing, but after taking the full OTA update my bootloader was locked again. If you want to update I would suggest first making a full backup to the external SD card in TWRP.
Then , its better to download à full update ( update.zip) ,copy to root of the phone , reboot in twrp and flash it ? Anyone already did it ?

LG G5 H830 10a will not update

So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
technocrat7 said:
So I'm having an issue with updating my phone.
I have tried reading all of the threads, but so many things are still a mystery and are confusing. I haven't been able to get a full understanding of all of this.
I have a LG G5 H830 10a T-Mobile variant.
I am running Android 6.0.1
I have a custom recovery of TWRP
My phone is rooted with SuperSU also.
All I want to do, is to update my phone to Nougat. What is the process I have to go through? After reading all about it, here is my assumption:
I download Flashfire and use DisableService to disable my root and SuperSu, then I run the OTA Nougat update...
That didn't work. I got an error from TWRP that said:
"unable to flash update.zip from cache/update.zip, update is meant for "h1" device, your device is an H830"
Or something along those lines.
I have a Nandroid backup, so I'm not worried if I brick or soft brick it.
Any help please?
Thanks!
Click to expand...
Click to collapse
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
jeffsga88 said:
You're not going to be able to update to Android N yet if you want to keep twrp and root. Only way to do it currently is if you have 100% stock phone and update via ota or using the zip file that was posted. If you don't care about root or twrp, update to 10j using the complete zip that autoprime posted and don't install SuperSU or dm-verity and let boot. You will have 100% stock and can take ota or use zip method. *** There is no current way to get root or twrp for t mobile version once on official android N yet *** So if root and twrp are important just wait until autoprime gets a chance to upload the flashable zip files for N to flash in twrp. You could also use cm or cm based Roms if you want android N, plus those are 7.1 stock is only 7.0, but if you want stock rooted just have to wait until it's released.
Click to expand...
Click to collapse
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
technocrat7 said:
Ohh okay, perfect thank you!
With that in mind, I had another question..
I have an LG V20 as well.
One thing I was thinking of doing was the following:
Unlocking the bootloader, putting a custom recovery like TWRP on it.
Make a Nandroid backup.
Then root it, and then go about my business. If something like this happens again and I want to update, I can simply do a Titanium Backup go to my Nandroid backup, restore it. Then update OTA, then reroot, run titanium backup restore, and then I'll be back where I left off.
will that work?
And one last question:
How would I go back to factory settings on my LG G5?
Click to expand...
Click to collapse
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
jeffsga88 said:
I'm not 100% sure but I don't think that would work as once you install twrp it modifies the recovery. IMG which would cause ota to fail. But on the other hand, you could most likely do the same method as the g5 to go back to official and take ota. Flashing the complete zip (if those are being created for the v20, haven't checked that thread as I don't own that device) and not re-installing the dm-verity or SuperSU will always reinstall the original boot.img and recovery.img and be 100% official stock. Hope this helps.
Click to expand...
Click to collapse
Thanks!
That helps a ton.
What is dm-verity though?
technocrat7 said:
Thanks!
That helps a ton.
What is dm-verity though?
Click to expand...
Click to collapse
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
jeffsga88 said:
The zip file we flash to disable force encryption (now this is part of the latest SuperSU zips).
Click to expand...
Click to collapse
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
carnivalrejectq said:
Can you link to the latest superuser? Just wanna have it on hand for when the H830 N zip drops
Click to expand...
Click to collapse
Here's the link to chainfires thread which will always have the latest beta supersu versions:
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Questions about OTA/Update to Nougat

Hello.
Just got the news about 7.0 being released for this phone, and thought I would give it a shot. However, I have a few questions before I update . These are not in any particular order and I would love any help people can provide, even if you can't answer all the questions.
Since I got this phone, I unlocked the bootloader (I bought the unlocked version) and got TWRP, then installed SuperSU binary in order to use a few root apps on my phone. Then along came an OTA update. When I went to install it, I got a message informing me that the update couldn't be installed due to my system being modified, which was fair enough as I had installed SuperSU. I stopped bothering with OTA updates.
Now it's been a while and the Nougat update is out and apparently available over OTA. Is there a way for me to return to normal system and get this OTA without losing all of my personal data already on the phone? I understand that I'd probably have to get TWRP again, and what is recommended for root now? Can I "re-lock" my bootloader in order to get the OTA?
Basically: How can I get Nougat without losing my data?
Cheers, and thanks for reading! Quick answers would be appreciated.
DuoDex said:
Basically: How can I get Nougat without losing my data?
Click to expand...
Click to collapse
backup your data and then flash a ruu, either the nougat version if its available for your version or flash the marshmallow ruu then take the ota update.
What is your "fastboot getvar all" ?
alray said:
backup your data and then flash a ruu, either the nougat version if its available for your version or flash the marshmallow ruu then take the ota update.
What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
I was able to get it by poking around in the forums, first got the RUU for 1.57, relocked bootloader, and am now OTAing the Nougat version (fingers crossed it all works). Thank you so much for replying!
Question: If I install TWRP (like I had before) and then Magisk, will I continue to be able to receive OTA updates? Backing up and reinstalling is such a pain and I'm afraid I will break something. Some people say you need to mount system read-only - how is this accomplished via TWRP exactly?
Thanks again!
DuoDex said:
I was able to get it by poking around in the forums, first got the RUU for 1.57, relocked bootloader, and am now OTAing the Nougat version (fingers crossed it all works). Thank you so much for replying!
Question: If I install TWRP (like I had before) and then Magisk, will I continue to be able to receive OTA updates? Backing up and reinstalling is such a pain and I'm afraid I will break something. Some people say you need to mount system read-only - how is this accomplished via TWRP exactly?
Thanks again!
Click to expand...
Click to collapse
I just went thru the process or putting magisk on nougat. You'll want to use twrp 3.0.3-4 for it. From what I understood from the user who clued me into it, magisk will let you take OTA's and use android pay since it won't mess with dm-verity, SELinux or safetyNet. I can definately confirm the Android pay part at least. I did notice however i had to turn on magisk hide in the settings to get it to pass the safetynet check.
as for mounting the system as read only, the first time i booted into twrp it asked me to either slide the lock to modify /system or check a box to mount it as read only and that was it.
txag2011 said:
I just went thru the process or putting magisk on nougat. You'll want to use twrp 3.0.3-4 for it. From what I understood from the user who clued me into it, magisk will let you take OTA's and use android pay since it won't mess with dm-verity, SELinux or safetyNet. I can definately confirm the Android pay part at least. I did notice however i had to turn on magisk hide in the settings to get it to pass the safetynet check.
as for mounting the system as read only, the first time i booted into twrp it asked me to either slide the lock to modify /system or check a box to mount it as read only and that was it.
Click to expand...
Click to collapse
I was mistaken, Magisk now patches dm-verity and forced encryption. You should be able to take an OTA by flashing the stock recovery though, and failing that by also restoring the system image backup you make in TWRP before modifying or mounting system.

Stop receving OTA updates for Pixel 3 after Root

2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
If you're rooted you can't take an ota directly. But follow this guide and you can get the ota, apply it, and root again. Pay attention to when you can reboot. https://topjohnwu.github.io/Magisk/tutorials.html
Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
That was discussed in several posts here recently: https://forum.xda-developers.com/app...32382/page3857
Apparently it has been going on for 3 years now. Some people are impacted, others are not. Luckily, I have not been impacted so far.
You can sideload the OTA. Instructions are at https://developers.google.com/android/ota You must re-root after sideloading.
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Nik0LaAs said:
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Click to expand...
Click to collapse
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
dcarvil said:
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
Click to expand...
Click to collapse
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Nik0LaAs said:
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Click to expand...
Click to collapse
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
dcarvil said:
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
Click to expand...
Click to collapse
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Nik0LaAs said:
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Click to expand...
Click to collapse
No other way to my knowledge. You can re-root after the update.

Pixel 4a Does Not Receive System Update Notification

The last System Update notification received was the Update from Android 11 to Android 12. It installed fine. Can keep up via sideload or a full manual flash, but why no notification of updates?
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a
Click to expand...
Click to collapse
Bootloader unlocked and rooted from Day 1. I was notified of the update from A11 to A12 and was able to use the system OTA. Otherwise I have sideloaded or flashed the Factory Image.
Even with auto update off in Dev Options, all I read says one shiuld still receive notification of the OTA. Guess I'll contune to sideload
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
Click to expand...
Click to collapse
How long after update release (usually 5th of the month or so) do they see their 4a updates?
I have a 4a, rooted and unlocked. When new updates come out (I check the https://developers.google.com/android/ota page), I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root. I believe it was Monday night April 3 when I did it last. If you don;t mind the hassle of all the reboots, I find it an easy enough way to keep updated and rooted.
amphi66 said:
How long after update release (usually 5th of the month or so) do they see their 4a updates?
Click to expand...
Click to collapse
It can vary a little (I think sometimes google stages the roll out?), but it's normally pretty soon after. The April update was already offered and installed.
augggg said:
I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root.
Click to expand...
Click to collapse
How do you get the new boot image for rooting after doing the OTA?
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
I do it by extracting/Magisk patching the boot.img from the Factory Image. Of course I had to sideload the OTA as it didn't show up in System updates.
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
For 4a, go to the latest factory image here, which is at the bottom of each phone's list of images: https://developers.google.com/android/images#sunfish
Download the factory image, then unzip the file. Go into the folder you get, then unzip the next zip file you see (starts with image-sunfish*), and look for the boot.img file. Should be 64mb
Thanks @augggg and @amphi66.
I use the factory image to upgrade each month. But since I have to download it, I see no value in doing an on-device OTA (ie. Uninstall Magisk, reboot, OTA, etc.)
@augggg mentioned uninstalling Magisk to OTA so I wondered if they had an alternative way of getting the boot image besides downloading the factory image or full OTA (which is a bit harder to unpack, but also includes the whole boot.img).
I suppose one could boot TWRP to extract the new boot.img from the phone and then use Magisk to patch that... But I feel like it'd end up being a lot more work than the few changed lines it takes to flash the factory image, and my download speeds aren't bad enough to make that faster
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
lbush said:
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
Click to expand...
Click to collapse
Exactly. Worked for me once, but have not seen an OTA nofication since
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
amphi66 said:
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
Click to expand...
Click to collapse
Gave up & sideloaded May OTA, followed by flashing the Magisk-patched boot.img to retain root. Still do not know why there was no OTA notification

Categories

Resources