Hi,
My Pixel 3a as an unlocked bootloader and is rooted.
Usually, when I update my system every month, I get the OTA update zip on google website to do the update and only patches the boot.img from the factory image with magisk to keep the root.
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
As I don't know why, can you explain me if it is or not dangerous or impossible, and eventually why I have to use the factory image to install this new system ?
I know that every time i made a wipe data (even if i know there's a way to delete the -w in the bat file but it's not recommended) it made me a day to restore all my apps and configurations... So if i can avoid this, I'd prefer.
Thanks in advance
oldbear3 said:
But this month, we get Android 12 and I saw on this thread : https://www.xda-developers.com/how-to-install-android-12/ that it was recommended not to use the OTA update for updating to Android 12 on unlocked bootloader.
Click to expand...
Click to collapse
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
a1291762 said:
I don't see this warning on that page?
The point of the full OTA sideload is that works with both locked and unlocked bootloaders.
The factory image only works with unlocked bootloaders.
I have a 4a with unlocked bootloader and just upgraded using the OTA and it was fine. I normally use the factory image (removing the -w arg) but found warnings on the internet that this would break when upgrading to Android 12 so I did the OTA instead.
I was even able to re-root with Magisk 23 as normal, which is apparently not possible for newer devices (eg. Pixel 5 guide: https://forum.xda-developers.com/t/guide-update-to-and-re-root-android-12.4345627/).
Click to expand...
Click to collapse
Great, thanks a lot. Made just right now and it works perfectly. The root also worked for me.
a1291762 said:
I don't see this warning on that page?
Click to expand...
Click to collapse
About this question, it's written for OTA Updates :
"To install the stable build, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader"(but as I re-read it, I see that it's written that it "also work" with locked bootloader"). For the full update, it's written "If you have an unlocked bootloader on a Google Pixel device, you need to flash the full factory image of the Android 12 via Fastboot"...so I thought it was the only option.
But you're right, it's not exactly what's written.
Related
First let me thank this community for the MANY years of great help pushing my devices to their limits. I've never register or posted because I've ALWAYS been able to find my answers with a simple search and really never have much to add.
This time I can't find a good answer. I hope this isn't too much of an amateur question.....
I purchased my Pixel via Verizon (I know....) and have unlocked the bootloader and rooted.
I really don't want to mess with custom ROM's for a while and I still want the latest stock version. How do I update to the latest version without losing recovery and root? Example: I updated to 7.1.1 the other day, then wiped, unlocked, installed recovery and rooted. I went back to 7.1 and don't know how to update to 7.1.1 again or other future versions. I hear that flashing stock rom from Google will wipe recovery and root. Is that correct?
Thanks again for all the years of sharing your experiences.
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
foolie said:
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
Click to expand...
Click to collapse
Thanks for the reply. Follow up question after scanning the toolkit description..... I'll look deeper into it in a bit.
This will retain root? Will using adb to sideload lose root?
I think so. You can just reflash SuperSU in recovery :good:
Farmer Tony said:
First let me thank this community for the MANY years of great help pushing my devices to their limits. I've never register or posted because I've ALWAYS been able to find my answers with a simple search and really never have much to add.
This time I can't find a good answer. I hope this isn't too much of an amateur question.....
I purchased my Pixel via Verizon (I know....) and have unlocked the bootloader and rooted.
I really don't want to mess with custom ROM's for a while and I still want the latest stock version. How do I update to the latest version without losing recovery and root? Example: I updated to 7.1.1 the other day, then wiped, unlocked, installed recovery and rooted. I went back to 7.1 and don't know how to update to 7.1.1 again or other future versions. I hear that flashing stock rom from Google will wipe recovery and root. Is that correct?
Thanks again for all the years of sharing your experiences.
Click to expand...
Click to collapse
That's not possible. If you installed the 7.1.1 update you wouldn't have been able to unlock the bootloader again. So you must have had it unlocked before the update.
aholeinthewor1d said:
That's not possible. If you installed the 7.1.1 update you wouldn't have been able to unlock the bootloader again. So you must have had it unlocked before the update.
Click to expand...
Click to collapse
I updated, then decided to root so I factory reset which brought me back to 7.1...... I didn't even know it wouldn't work on 7.1.1 so I guess I was lucky to have done so. I just thought it would be safer to start with a clean slate.
It wasn't until I noticed I could no longer double tap to see notifications that I realized that was only in 7.1.1 and noticed that I couldn't update to it anymore.
Edit: Maybe when I said "wiped" I should have said "factory reset".
foolie said:
I think so. You can just reflash SuperSU in recovery :good:
Click to expand...
Click to collapse
I figured I could do this as a last resort but would love to side load and just go about my day. Nice to know that there wouldn't be an issue, thanks.
I realize this isn't my thread, but... I flashed factory image to my Pixel but the recovery flashing failed. How can I get stock recovery back on so I can take the update?
Crowick said:
I realize this isn't my thread, but... I flashed factory image to my Pixel but the recovery flashing failed. How can I get stock recovery back on so I can take the update?
Click to expand...
Click to collapse
Use the skipsoft toolkit and try again with a new factory image download.
foolie said:
http://forum.xda-developers.com/pixel/development/tool-skipsoft-android-toolkit-google-t3482761 download that
https://developers.google.com/android/ota download OTA images
use the toolkit to sideload flash the OTA.
Click to expand...
Click to collapse
sorry I'm a total newb, where is the sideload option? I keep looking but don't see it
mrj0087 said:
sorry I'm a total newb, where is the sideload option? I keep looking but don't see it
Click to expand...
Click to collapse
There's a section 'Updating instructions' in the OTA page (linked above) with instructions. Not for the faint of heart if you're unfamiliar with ADB.
It's on the toolkit options after you select your device.
Do you mean you booted into recovery and reflashed because I've actually been wondering almost exactly what you have.
I have a VZW pixel that I unlocked and rooted via adb/fastboot and I've been wonder if accepting a Verizon OTA would unroot me, and relock the bootloader. The 2nd Verizon update as we know disabled depixel and grayed out the option in dev options but do current OTA updates (not images I downloaded myself) unroot and relock which would prevent me from unlocking and getting root again
I've looked all through the forums and haven't found a clear tutorial on how to do this, if it can even be done.
I have a Verizon bought, bootloader unlocked, Magisk rooted Pixel 2 with TWRP and a custom kernel (Flash 2.06) installed running 8.1.0 with the December security patch.
How would I go about updating to future monthly patches (e.g. January's)?
I'd prefer to not lose all data (i.e. OTA-like), but am willing to start clean. Definitely do not want to risk losing the unlocked bootloader.
Is it possible? Willing to try if there is a semi-reasonable assurance of success.
Thanks.
If you're familiar with fastboot you can pull out the image.zip from the factory image and fastboot it with the command
Code:
fastboot update whateverthelongassimagename.zip
Leaving out the -w in that command won't wipe anything. If not, you'll have to get the stock boot image and take the OTA. Either way you'll have to temp flash TWRP again, installer to keep it there and your kernel and Magisk.
When we get an update that requires a new bootloader, that will have to be via OTA or adb sideload. VZW seems to have blocked us from fastbooting that.
JRJ442 said:
When we get an update that requires a new bootloader, that will have to be via OTA or adb sideload. VZW seems to have blocked us from fastbooting that.
Click to expand...
Click to collapse
I'm guessing on Verizon you wouldn't want to update the bootloader anyways since that would likely fix the current method of unlocking those phones.
clcdev said:
I'm guessing on Verizon you wouldn't want to update the bootloader anyways since that would likely fix the current method of unlocking those phones.
Click to expand...
Click to collapse
They most likely will patch the unlock yes, but they're not going to send an update that will relock the bootloaders that have been unlocked. So I wouldn't see an issue with updating it. Unless for some reason you need to lock it back. The bootloader in this months security update is still the same as last months. Version number is the same.
I have a rooted One Plus 6 running on stock Oxygen OS 9.0 There is an OTA update available at the moment. I have used FlashFire on my previous phone (Nexus 6P) and it worked flawlessly in keeping the root and applying OTA updates without any steps required. All I had to do was launch the app, it detected the firmware, and I would let it install. I purchased the professional version of the app as the free version stopped working at some point.
When I launch the same app on my OP6 and select "Flash zip or OTA" option I get another screen that has three options to check:
1. Auto-mount: Mount common paths before running update. Rarely necessary. Enable for A/B device OTAs, disable for all other OTAs.
2. Mount / system read / write: Mount /system read / write by default, rather than read-only. Doing this only once may break the future OTAs, Enable when flashing custom firmwares.
3. Restore boot and recovery images: Attempt to restore boot and recovery images before flashing. May be required for some OTA. Disable for non-OTA updates.
What's confusing me is the third option as that is already checked. It sounds like this option would install a factory image back on the phone? Should I uncheck it and check #1 as the only option?
If your bl is unlocked then you can't use ota to update. You have to flash the full zip in twrp.
se7ensde said:
If your bl is unlocked then you can't use ota to update. You have to flash the full zip in twrp.
Click to expand...
Click to collapse
I just found the instructions for update in another thread. I will have to use the blu-spark twrp to update it. Since I have never done it before, my question is, is it going to leave all the data and the app data intact? Things like pictures, videos, messages from messaging apps? Because in my mind I always thought of flashing the full image the same way as reinstalling the OS on any desktop computer - it deletes everything.
I am guessing the answer is no?
Is your bl already unlocked?
se7ensde said:
Is your bl already unlocked?
Click to expand...
Click to collapse
BL is unlocked and the phone is rooted.
shagexpert said:
BL is unlocked and the phone is rooted.
Click to expand...
Click to collapse
okay so if you have it setup Google will backup your apps calls and network settings and you will be able to sign out to your Google account and choose to restore it. For photos.. If you have Google photos installed it will backup everything you have told it to. But you shouldn't have to worry about any of this if you are just dirty flashing the update. Everything will be the way it was is like an ota only difference is you manually flashing the full room zip in twrp. So if your just dirty flashing you shouldn't lose any data.
Thanks! I will give it a try sometime later this week.
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
ichigodango said:
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
Click to expand...
Click to collapse
You can downgrade to 9 but you'll need to do a full wipe. Instead download the full factory image for the latest update and edit the flash-all batch file you'll find in it to remove the -w. Then run the batch file. You'll need to copy the boot.img file in the factory image to your device and then patch it with magisk to root. That patched image will need to be flashed to your device using fastboot from your pc.
I ran into the same issue as you when trying to update with the ota.
ichigodango said:
I'm currently on stock Android 10, unlocked bootloader, rooted with Magisk. There's an available update (12.7 MB) but it always gives an error message of "Couldn't update / Installation problem". Uninstalling Magisk didn't fix the issue, so I'm assuming it's due to unlocked bootloader.
If I want to downgrade to 9, is it a simple case of flashing the factory image of Android 9, or does Android 10 need to be fully up to date first? Do I need to re-lock the bootloader?
Any advice much appreciated!
Click to expand...
Click to collapse
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
You should be able to flash the full factory image of either 9 or 10, but that will wipe your phone. Here is a link to a thread regarding downgrading from 10 to 9. That thread is for an XL, but it is still applicable.
https://forum.xda-developers.com/showpost.php?p=80206785&postcount=31
Complete flashing instructions are here: https://developers.google.com/android/images#instructions
You can flash the factory image without wiping your phone by editing flash-all.bat, and removing -w from the last line. That may not fix your problem, though. You may need a wipe to fix it.
Make sure to download the latest platform tools if you decide to flash. https://developer.android.com/studio/releases/platform-tools
I would not relock the bootloader. It may be impossible to recover from a bricked phone with a locked bootloader, and the relocking process may brick the phone. You must be on a stock image to relock the bootloader.
jd1639 said:
You can downgrade to 9 but you'll need to do a full wipe. Instead download the full factory image for the latest update and edit the flash-all batch file you'll find in it to remove the -w. Then run the batch file. You'll need to copy the boot.img file in the factory image to your device and then patch it with magisk to root. That patched image will need to be flashed to your device using fastboot from your pc.
I ran into the same issue as you when trying to update with the ota.
Click to expand...
Click to collapse
I managed to figure it out, updated ota and am now back on 9 with no problems I used flash-all without removing -w but didn't lose anything important so it's all good!
dcarvil said:
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
You should be able to flash the full factory image of either 9 or 10, but that will wipe your phone. Here is a link to a thread regarding downgrading from 10 to 9. That thread is for an XL, but it is still applicable.
https://forum.xda-developers.com/showpost.php?p=80206785&postcount=31
Complete flashing instructions are here: https://developers.google.com/android/images#instructions
You can flash the factory image without wiping your phone by editing flash-all.bat, and removing -w from the last line. That may not fix your problem, though. You may need a wipe to fix it.
Make sure to download the latest platform tools if you decide to flash. https://developer.android.com/studio/releases/platform-tools
I would not relock the bootloader. It may be impossible to recover from a bricked phone with a locked bootloader, and the relocking process may brick the phone. You must be on a stock image to relock the bootloader.
Click to expand...
Click to collapse
You're totally right that my problem had nothing to do with bootloader. I realised that by rooting with Magisk, the boot.img was modified, so I downloaded the image of the version that I had, extracted boot.img, flashed it to my phone, which got ota working.
I then updated ota to the latest Android 10 just in case, before flashing Android 9 followed by root - this was probabaly more complicated than necessary and I probabaly could have skipped the ota update, but everything is working as intended
dcarvil said:
Your problem is not due to an unlocked bootloader. I had no problems with that update following this procedure. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
You would have to reinstall Magisk to follow that procedure.
Click to expand...
Click to collapse
What's the difference between this method and simply flashing the phone with the stock boot.img? I just flashed stock boot.img, got ota working on 10, updated, before downgrading to 9. Will I run into any issues because I didn't use Magisk's restore image?
ichigodango said:
What's the difference between this method and simply flashing the phone with the stock boot.img? I just flashed stock boot.img, got ota working on 10, updated, before downgrading to 9. Will I run into any issues because I didn't use Magisk's restore image?
Click to expand...
Click to collapse
Flashing the stock boot image removes root, so you must re-root the phone after updating. This method removes root from the active slot, but preserves it on the alternate slot. After the OTA root is restored from the alternate slot.
The end result is the same for both cases, but following the OTA procedure is simpler and faster.
dcarvil said:
Flashing the stock boot image removes root, so you must re-root the phone after updating. This method removes root from the active slot, but preserves it on the alternate slot. After the OTA root is restored from the alternate slot.
The end result is the same for both cases, but following the OTA procedure is simpler and faster.
Click to expand...
Click to collapse
That makes sense, thanks!
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