Question Guide to unroot, relock bootloader and to OTA updates

Search This thread

G5-User7080

Senior Member
May 31, 2018
183
53
you should be able to get in system OTA's even while being rooted so long as you didn't modify /system in any way.
If you want to do that you need to first restore the stock boot.img, typically done by going to magisk -> restore images, for details refer to the guide for the pixel 6, check the automatic OTA section.

Though it might be easier and safer to sideload the OTA instead, you can find details for that in the same guide under the sideload OTA section.
As far as I understood it doesn't matter if you still have modules installed and a rooted boot.img when you sideload, but if you want to be super safe you could always just disable all modules and flash stock boot.img

After sideloading OTA you have to re-root, so keep a magisk patched boot.img ready to boot from.

unroot is just as easy as flashing stock boot.img or uninstalling through magisk.
I'm not exactly sure what the difference between the "uninstall" and "restore images" option is in magisk.
"restore images" is supposed to restore your stock boot.img if you previously rooted by doing "direct install" in magisk.
And I suppose uninstall does the same but also removes all of magisk instead of only unrooting?

Don't take my word for it, it's just a guess.
Relocking bootloader requires you to be 100% stock, and iirc that also requires you to wipe your device, but not sure about that one.

I'd recommend you use pixel flasher for that as it leave little room for error, typos and the like.
In essence you just download the latest factory image from google, flash everything including wiping data and relock bootloader after that.
That said, using Pixel flasher or android flash tool with the wipe options checked do the same for you without needing to type out commands and navigate your downloaded archives.

Is it necessary to flash to both slots?
I don't know, hopefully someone else can answer that one.
 
  • Like
Reactions: juv3nal

juv3nal

Senior Member
you should be able to get in system OTA's even while being rooted so long as you didn't modify /system in any way.
If you want to do that you need to first restore the stock boot.img, typically done by going to magisk -> restore images, for details refer to the guide for the pixel 6, check the automatic OTA section.

Though it might be easier and safer to sideload the OTA instead, you can find details for that in the same guide under the sideload OTA section.
As far as I understood it doesn't matter if you still have modules installed and a rooted boot.img when you sideload, but if you want to be super safe you could always just disable all modules and flash stock boot.img

After sideloading OTA you have to re-root, so keep a magisk patched boot.img ready to boot from.

unroot is just as easy as flashing stock boot.img or uninstalling through magisk.
I'm not exactly sure what the difference between the "uninstall" and "restore images" option is in magisk.
"restore images" is supposed to restore your stock boot.img if you previously rooted by doing "direct install" in magisk.
And I suppose uninstall does the same but also removes all of magisk instead of only unrooting?

Don't take my word for it, it's just a guess.
Relocking bootloader requires you to be 100% stock, and iirc that also requires you to wipe your device, but not sure about that one.

I'd recommend you use pixel flasher for that as it leave little room for error, typos and the like.
In essence you just download the latest factory image from google, flash everything including wiping data and relock bootloader after that.
That said, using Pixel flasher or android flash tool with the wipe options checked do the same for you without needing to type out commands and navigate your downloaded archives.

Is it necessary to flash to both slots?
I don't know, hopefully someone else can answer that one.
Thank you for your answer and your time, very much appreciated! I'll have a look at that guide. Thanks!
 

juv3nal

Senior Member
I don't know if anyone is getting this error in PixelFlasher...

Active code page: 850
Sending 'bootloader_b' (11574 KB) OKAY [ 0.261s]
Writing 'bootloader_b' (bootloader) Flashing pack version bluejay-1.2-9288097
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
FAILED (Status read failed (Too many links))
Finished. Total time: 2.662s
 

Lughnasadh

Senior Member
Mar 23, 2015
6,174
7,673
Google Nexus 5
Huawei Nexus 6P
I don't know if anyone is getting this error in PixelFlasher...

Active code page: 850
Sending 'bootloader_b' (11574 KB) OKAY [ 0.261s]
Writing 'bootloader_b' (bootloader) Flashing pack version bluejay-1.2-9288097
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
FAILED (Status read failed (Too many links))
Finished. Total time: 2.662s
Best to go over to the Pixel Flasher thread and post your support.zip so the dev can take a look at it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    you should be able to get in system OTA's even while being rooted so long as you didn't modify /system in any way.
    If you want to do that you need to first restore the stock boot.img, typically done by going to magisk -> restore images, for details refer to the guide for the pixel 6, check the automatic OTA section.

    Though it might be easier and safer to sideload the OTA instead, you can find details for that in the same guide under the sideload OTA section.
    As far as I understood it doesn't matter if you still have modules installed and a rooted boot.img when you sideload, but if you want to be super safe you could always just disable all modules and flash stock boot.img

    After sideloading OTA you have to re-root, so keep a magisk patched boot.img ready to boot from.

    unroot is just as easy as flashing stock boot.img or uninstalling through magisk.
    I'm not exactly sure what the difference between the "uninstall" and "restore images" option is in magisk.
    "restore images" is supposed to restore your stock boot.img if you previously rooted by doing "direct install" in magisk.
    And I suppose uninstall does the same but also removes all of magisk instead of only unrooting?

    Don't take my word for it, it's just a guess.
    Relocking bootloader requires you to be 100% stock, and iirc that also requires you to wipe your device, but not sure about that one.

    I'd recommend you use pixel flasher for that as it leave little room for error, typos and the like.
    In essence you just download the latest factory image from google, flash everything including wiping data and relock bootloader after that.
    That said, using Pixel flasher or android flash tool with the wipe options checked do the same for you without needing to type out commands and navigate your downloaded archives.

    Is it necessary to flash to both slots?
    I don't know, hopefully someone else can answer that one.