I have a verizon pixel 2.
I have unlocked the bootloader and root with Magisk.
There are a few threads with different methods using factory and OTA images but I haven't been able to get it to work.
I'd like to update to the March update. Currently on Jan 5 build OPM1.171019.013
a quick run through would be helpful
Thanks
Related
Hello,
I'm guessing most of you already know that the android 5.0 or android lollipop updates started rolling out OTA. My nexus 5 is rooted and its running stock android 4.4.4 with the stock recovery. Also my boot loader is locked. Should I "un-root" my nexus 5 for the OTA update or should I try updating it with root on my phone?
Regards,
cyberusman
It should update with root but you'll lose it. You'll need to unlock your bootloader to root again though. I'd just unlock with boot unlocker and flash factory image personally.
rootSU said:
It should update with root but you'll lose it. You'll need to unlock your bootloader to root again though. I'd just unlock with boot unlocker and flash factory image personally.
Click to expand...
Click to collapse
I went onto my root app(superuser) and went to info and checked the box called OTA survival. After that ontroead the OTA update, it installed 1/4 of the way then just said error. What do i do?
Try other update methods. Root options available in my signature
rootSU said:
It should update with root but you'll lose it. You'll need to unlock your bootloader to root again though. I'd just unlock with boot unlocker and flash factory image personally.
Click to expand...
Click to collapse
I took the OTA with root and stock recovery. Updated, lost root, but the bootloader is still unlocked. My N5 is the Google play store edition if that makes a difference. Im I'm guessing carrier specific phones are relocking the bootloader.
Sent from my LGLS990 using XDA Free mobile app
MikeDroid said:
I took the OTA with root and stock recovery. Updated, lost root, but the bootloader is still unlocked. My N5 is the Google play store edition if that makes a difference. Im I'm guessing carrier specific phones are relocking the bootloader.
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
OTA doesn't lock the bootloader. All nexus 5's are created equal
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.
Hi all,
I unlocked the bootloader, rooted and dropped the purenexus 7.1.2 ROM on my Pixel back when it was all released. At the time people were saying that its about as good as its going to get and then when 8 came along ppl said a rooted Pixel can't be updated to the new OS while bootloader is unlocked and rooted.
Just wondering if someone can weigh in and tell me where we are currently at with Pixel in regards to rooting, bootloaders and OS updates? Can we have an unlocked bootloader, TWRP installed, rooted and run 8.1 with OTA updates now?
brettule said:
Hi all,
I unlocked the bootloader, rooted and dropped the purenexus 7.1.2 ROM on my Pixel back when it was all released. At the time people were saying that its about as good as its going to get and then when 8 came along ppl said a rooted Pixel can't be updated to the new OS while bootloader is unlocked and rooted.
Just wondering if someone can weigh in and tell me where we are currently at with Pixel in regards to rooting, bootloaders and OS updates? Can we have an unlocked bootloader, TWRP installed, rooted and run 8.1 with OTA updates now?
Click to expand...
Click to collapse
You can unlock your bootloader. TWRP and root your phone. You won't get OTA updates, but you can install them manually. Or unroot your phone.
pojr said:
You can unlock your bootloader. TWRP and root your phone. You won't get OTA updates, but you can install them manually. Or unroot your phone.
Click to expand...
Click to collapse
If I was to unroot but keep the bootloader unlocked would OTA updates work again?
Is the old bootloader unlock still valid or do I need to lock it and unlock it using current methods?
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.
Hello.
I have a bootloader locked Pixel 7 Pro with the April 2023 stock build.
I would like to downgrade to the October or November 2022 build.
Is there any way I can accomplish this?.
Thank you.
EDIT: Got an OTA build, but recovery is saying downgrades are not allowed.
Any other way?
Unless you unlock the bootloader, you cannot downgrade using an OTA. How you tried to flash the full firmware? Why are you trying to downgrade to a firmware that far behind anyways?
schmeggy929 said:
Unless you unlock the bootloader, you cannot downgrade using an OTA. How you tried to flash the full firmware? Why are you trying to downgrade to a firmware that far behind anyways?
Click to expand...
Click to collapse
Reason, because on Pixel 7 and 7 Pro, firmwares from October and November, deleting an app, you can carrier unlock them, so I am trying to do that. I did it already with a 7 Pro which had the October firmware, obviously, if there is a reset on the phone, it gets locked again, but at least it's something.
I tried using the flashme.bat script, PixelFlasher, used OTA and Full firmwares, Fastboot and Recovery, nothing.
You cannot downgrade to a lower security patch without wiping data. Unlocked bootloader has the same behaviour.
Lossyx said:
You cannot downgrade to a lower security patch without wiping data. Unlocked bootloader has the same behaviour.
Click to expand...
Click to collapse
The phone is clean, so no data on it.
SirRhor said:
The phone is clean, so no data on it.
Click to expand...
Click to collapse
Oh my bad. Then I am not so sure ,sorry. This is my first Pixel.