Does Root Stay after Update? - OnePlus 7 Pro Questions & Answers

Does root stay after an ota update with oneplus or will I have to re-root?
I had to reroute my Nexus 6p after an update

Of course. You will have to root again. Doing an update will install the stick kernel for that Fournette, hence removing the patched boot partition changes. You will have a stock boot partition and kernel.
Also, for OTA, won't work with a modified boot partition. You need the full ROM to flash in system update>local upgrade or in TWRP if you have that installed

Related

How can install OTA on rooted device?

Hi, my nexus 5 is root and use TWRP recovery. every month i get security patch notification but the installation failed.
should i unroot my device or revert to stock recovery or both?
You would need to do both in order to install OTA updates. Alternatively, you could manually flash each partition but leave userdata alone.

Updating Security Patch, rooting and using TWRP

I'm currently on November's NDE63V with root and twrp installed. I updated to SR5 root when it was released using TWRP and it boot looped. I assumed it was because I didn't flash the stock boot.img(both slots?), boot to TWRP, flash TWRP then install root. Is this correct? Does that method need to be followed every time there's an update?
I want to update to 7.1.1, December's OTA -> I want stock ROM on one slot and WETA on the other. Both with root. Of course either Franco or ElementalX. Can someone outline the steps, as I don't want to boot loop again, setting everything up is a PITA!
http://forum.xda-developers.com/showpost.php?p=69834495&postcount=2
This should help you with dual booting.
Haven't read through it all yet as I'd like to dual boot as well. But all I did to update is download all the files Weta has when you go to download the rom (boot, bootloader, radio and vendor.)
I Fastboot flashed bootloader, radio and vendor rebooted to bootloader and flashed weta, elementalx and SuperSU sr5.

Update 6.0 to 6.0.1 OTA: unroot, recovery, howto?

I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Quark^2 said:
I have a rooted (SuperSU, xposed) MotoG3 with custom recovery (TWRP) running 6.0.
I just got the notification that an update is ready for my phone, which I assume is 6.0.1.
Now, I know that that OTA update is going to fail because of root & modified recovery.
What is the easiest way to update to 6.0.1, while keeping or reinstalling root, xposed and TWRP.
Can I just unroot, reflash stock recovery and update?
Click to expand...
Click to collapse
It's just a simple security patch, not an version upgrade, it can be safely ignored. That said, if you really want it you need to be pure, unmodified stock... Restore your pre-root Nandroid or flash the current factory image with fastboot.

Full steps on how to take OTA updates when rooted with Magisk, TWRP & Custom Kernel?

Full steps on how to take OTA updates when rooted with Magisk, TWRP & Custom Kernel?
I tried to take the 5.1.6 OTA by using these steps: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md but it didn't work properly.
Could someone give me a list of the full steps that will keep Magisk, TWRP and Blu Spark Kernel installed? When I did the steps above it kept Magisk after rebooting, but didn't keep the custom kernel, so I rebooted to recovery to reinstall the kernel. However it was replaced with OxygenOS Recovery and it automatically wiped my device.
There is no way for you to take OTA with twrp and kernel persisted.
You need to understand how update works. Apparently, the update replaces your boot partition and your kernel is exactly implemented in the boot partition.
The changes will get overwritten. Thus, you will need to reinstall the kernel by yourself.
And as what I just mentioned, there is no specific recovery partition on A/B partitioning method. When boot partition get overwritten, the twrp will also be replaced by the stock recovery.

Custom ROM

Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Uxlewl said:
Hello, will it be possible to return from custom firmware to the original one and continue to receive OTA update ?
Click to expand...
Click to collapse
Yes, if you used TWRP to create a backup of your stock ROM before you flashed a custom ROM, you just use TWRP to restore the backup of stock ROM.
Or, if you didn't use TWRP to backup your stock ROM, you can flash your device's stock firmware using the flashtool designed to be used with devices made by your device's manufacturer.
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Uxlewl said:
But to install TWRP you need Root, and if you get it, then OTA updates stop coming or am I wrong?
Click to expand...
Click to collapse
No, installing TWRP does not require root. Yes, TWRP and root prevent the installation of OTA updates.
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Uxlewl said:
That is, to make a backup copy of the original firmware, you need TWRP, but if you install it, you lose the ability to receive OTA updates, and if you restore the original after the custom firmware, there will be no updates? Or can TWRP be removed and OTA updates will come again? I'm sorry I do not understand.
Click to expand...
Click to collapse
To be more specific, installing TWRP does not necessarily prevent a device from actually receiving/downloading OTA updates, it prevents the actual installation of OTA updates because part of the OTA update includes automatically booting into stock recovery to apply the update. If you have TWRP installed, the OTA update can possibly be downloaded to the device but when the device automatically tries to reboot into recovery, it is trying to boot into stock recovery but if you have TWRP installed, it can't boot into stock recovery to apply the update and when it tries to boot into TWRP, it will try to apply the update but it will fail, resulting in a bricked device and the device will have to be restored.
When it comes to OTA updates, all that is required is an unmodified stock system partition(meaning, no root or any other kind of modifications to the system partition), stock recovery(meaning, no TWRP) and the update has to be offered by your carrier if they offer the update for your specific device.
If a device is rooted, has other system modifications and/or has TWRP installed and you want to apply a stock OTA update, you have to remove root and any other system modifications and you must replace TWRP with the original stock recovery before you can apply the update. If you have TWRP and or root and you remove them to apply an OTA update, you can root the device again and install TWRP again after the update, provided that the OTA does not come with a locked bootloader that can not be unlocked, in this case, you will not be able to reinstall TWRP or root because the bootloader will be locked, which prevents you from installing TWRP again. Sometimes, users remove root and TWRP to apply OTA updates with the intention of rooting and/or installing TWRP again after the update but then get stuck in a position where they can no longer root the device or install TWRP because the bootloader gets locked during the update and there is no way to unlock the newly updated bootloader, from then on, they are stuck with stock with no way to get root, TWRP and custom ROMs reapplied to the device because they were not aware that the update came with a locked bootloader that can not be unlocked by any means.

Categories

Resources