If I unlock bootloader and apply TeamWin Recovery Project will that disable the ability to receive OTA updates?
I really would like Viper4Android! Thanks
Yes TWRP disables OTA updates. All system partitions need to be @Stock for a successful update via OTA.
Our TWRP is quite crappy and at best a beta version anyways.
You can install V4A quite easy as a Magisk module. Just check a root guide in the Guides section. It's just a matter of seconds to disable root for taking an OTA and re-enabling it again afterwards.
Related
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Pickle_Jr;4f86 said:
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Click to expand...
Click to collapse
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
sfhub said:
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
Click to expand...
Click to collapse
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay? I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Pickle_Jr said:
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay?
Click to expand...
Click to collapse
Yes.
For example, if you freeze a stock app in titanium, that is ok, but if you remove a stock app, then an OTA will likely fail.
If you use stickmount, it modifies a system file and backs it up, then restores it when it is done, but sometimes that gets out of sync, in which case the OTA fails.
There are other examples.
Pickle_Jr said:
I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Click to expand...
Click to collapse
If you install root through the stock recovery, you'll lose root permissions (but the files will still be there). Just re-root using the existing procedure.
If you want to save a step, boot into TWRP to install the OTA (which you download manually) and then "chain" install the OTA, then the root install files.
This way, you lose root for half a second until the 2nd install file in the chain runs. Essentially you won't lose root (or won't notice losing root) because the first time you boot into 4.4, you'll have root.
I am new to the whole understanding of root on non-Nexus devices seeing how I had to root my Nexus 4 after each update and I had a fair bit of knowledge hacking/modding/rooting the Nexus.
Kedros over at oppoforums (http://www.oppoforums.com/threads/how-to-root-your-oppo-find-7a-w-oppo-recovery.11309/) provided a root method that is permanent. I have no plans to install custom ROMs nor do I feel the need to flash a custom recovery (ex. TWRP).
My question is:
1. Will I still receive OTA updates from Oppo after I root?
2. If no to step 1, will flashing ColorOS updates remove the "permanent" root?
Thanks.
Root and OTA
anwedr said:
I am new to the whole understanding of root on non-Nexus devices seeing how I had to root my Nexus 4 after each update and I had a fair bit of knowledge hacking/modding/rooting the Nexus.
Kedros over at oppoforums provided a root method that is permanent. I have no plans to install custom ROMs nor do I feel the need to flash a custom recovery (ex. TWRP).
My question is:
1. Will I still receive OTA updates from Oppo after I root?
2. If no to step 1, will flashing ColorOS updates remove the "permanent" root?
Thanks.
Click to expand...
Click to collapse
1. Yes. OTA updates will work so long as you're using stock recovery and haven't made drastic changes to the /system partition.
2. Flashing an incremental (OTA) update in recovery will have the same effect as tapping "install update" from the about phone menu. You will lose root. If you flash a complete dump of the /system you will lose root as well since you are replacing /system.
Losing root isn't a big deal. Just flash again from recovery. You could try the OTA survival option built into SuperSu. I didn't bother trying because it takes less than a minute to reboot to recovery and flash SuperSu/su binary. What might be a big deal with the OTA update is that it wipes /data. This is odd because the pop-up that appears prior to installing the update specifically states that you won't lose apps or data. Your custom ROM plans may change after you use ColorOS. I hate it. It's glitchy and has a huge memory footprint. I'd recommend trying the 2.0 beta. I haven't had my Find 7a for long, but I've had no bugs thus far with the 2.0 beta. It's available on the Oppo Forums.
-Sent from my Panasonic 3DO
Hello everyone,
I have purchased my OnePlus 5T, and I absolutely love it! I was just wondering whether I could root while retaining the stock ROM and recovery and still get the OTA updates in the usual way? I don't mind staying with OxygenOS and stock recovery I would just really like root access while keeping updates!
Would appreciate a quick answer,
Thankyou in advance,
Nathan.
I would unlock the bootloader and backup the default recovery. Then flash twrp and boot in to it and flash Magisk for root. Then flash the default recovery back.
Why? If you root your phone, then incremental OTA updates will more than likely get broken. That means, once you root, you will just need to apply the full update for each OTA. If you have TWRP installed, then you just download the fill update.zip file, and flash the update.zip and root.zip packages and be on your way.
when an update comes out just dirty flash the full zip once released, i thought u could still install OTA even with TWRP, u just can't with root and a modified system, can't u just uninstall magisk, then do the update then reinstall magisk?
Exactly. As soon as you modify the system (whole point of root), incremental OTAs will not work. Just dirty flash the full OTA via TWRP and profit.
This question has been asked before. You can read through all the answers here: https://forum.xda-developers.com/oneplus-5t/help/root-update-ota-t3712615
I would like to get to the point where I'm able to OTAs instead of manually flashing factory images but I'm not passing safety net when I uninstall magisk and reinstall it when the update reaches step 2. I'm not sure what is causing the update to fail. I recently switched from system root via supersu (obviously wouldn't pass safety net) to systemless root with magisk. I'm running 8.1 feb. security update with the following apps installed: adaway, busybox, CF. Lumen, greenify, magisk manager, & titanium backup. (rootless substratum & andromeda as well).
I do not have TWRP installed, I only boot to it to flash magisk and kept TWRP systemless. The purpose for this post I guess is to try understand which of the installed apps listed may affect the /system files. I was under the impression that since i now root systemlessly I would be able to accept OTAs. What am I missing here?
As far as I know you cannot be rooted and/or have a custom recovery. You can have a unlocked bootloader but you have to be stock in order to receive OTAs.
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
......... you can flash full OTAs from TWRP?? I knew I was missing something.
So download the full OTA to internal storage. flash in TWRP. then magisk and if i choose not to install TWRP (i usually only boot to it), I'm done?
onesolo said:
I really don't get the problem. Just flash full ota file via TWRP and then flash again magisk and twrp again.
With TWRP, flashing full OTA files is a breeze... I think incremental otas can be done in the same way, but better to flash full ota files...
Click to expand...
Click to collapse
Wait, doesn't flashing the full OTA get rid of TWRP?
Do you have instructions how to install full images without TWRP being uninstalled?
Also... How do you get ota to install if the original bootloader is replaced by twrp? I thought installing twrp permanently voids the possibility to install ota...!
I have a MiA2Lite with bootloader unlocked, magisk installed and update to Pie. If I wanted to receive OTA updates I should
a) remove magisk
b) re-lock the bootloader
c) both
which of the r options?
IO13 said:
I have a MiA2Lite with bootloader unlocked, magisk installed and update to Pie. If I wanted to receive OTA updates I should
a) remove magisk
b) re-lock the bootloader
c) both
which of the r options?
Click to expand...
Click to collapse
Do not relock bootloader, if you do you may not be able to recover later- without disassembling Device.
If you mess with the system partition other than a couple magisk modules, you may need to flash a stock image.. but very easy with bootloader unlocked, so again don't lock the bootloader.
There is a guide to temporarily uninstalling magisk for the OTA, and if you follow it will work. Upgrading to pie however you may need to flash the updated boot.img and patched_boot respectively through fastboot after the ota
Again emphasis on not relocking bootloader.
Use titanium backup to backup app data and move backup to external sd before flashing stock image to protect it or before trying the above for easier restoring.
IO13 said:
I have a MiA2Lite with bootloader unlocked, magisk installed and update to Pie. If I wanted to receive OTA updates I should
a) remove magisk
b) re-lock the bootloader
c) both
which of the r options?
Click to expand...
Click to collapse
To make it short: a)
I had recieve before we have november update while magisk is installed and bootloader is unlocked.