Now do you root a HTC 10. Will you still be able to download system updates.
Osakpa said:
Now do you root a HTC 10. Will you still be able to download system updates.
Click to expand...
Click to collapse
Rooting doesn't affect your ability to take OTAs. It's what you do AFTER you root that will impact OTA. Any modifications to System partition will break OTA. The modification can be as simple as just mounting system as read-write, as opposed to leaving it read-only.
Modifying system partition while using the unmodified stock kernel (we think) will also trip verity mode logging which will cause the you to get an error that system is corrupt when you go to check for OTA.
The TWRP FAQ (second post) has all the info you need regarding root and restoring your ability to ota.
Additional information regarding how to fix verity mode logging can be found here
Obviously, if you root and use only systemless exploits and never mount system as read-write, you should never break your ability to OTA. But, that's a lot easier said than done.
jollywhitefoot said:
Obviously, if you root and use only systemless exploits and never mount system as read-write, you should never break your ability to OTA. But, that's a lot easier said than done.
Click to expand...
Click to collapse
Magisk makes it super simple.
I have magisk'd phhh super-su, xposed, and now Dolby Atmos (that I converted to magisk), all still playing well enough together to so that at least android pay works. I won't know about OTA's until the next dev/unlocked one which could possibly just be N.
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
I was looking at rooting instructions on another site and it indicated that you may not be able to get OS updates from Google if you root your device. Is there any truth to that if you only root the device? and would it matter if you keep encryption on or off?
ecko19 said:
I was looking at rooting instructions on another site and it indicated that you may not be able to get OS updates from Google if you root your device. Is there any truth to that if you only root the device? and would it matter if you keep encryption on or off?
Click to expand...
Click to collapse
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
nitinvaid said:
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
Click to expand...
Click to collapse
If you modify the flash-all file to remove the flag -w it will not wipe the data from the device.
Is that because when rooting the phone the stock recovery partition is flash over with TWRP and when OTAs are updated they use the recovery stock recovery partition to update the system partition? or does the OTA update process do some check to see if anything was tampered with? or something else?
nitinvaid said:
if you root it then there are no more OTA for device but you can flash the factory images when update comes but that will wipe all the data of the device.
Click to expand...
Click to collapse
Well, I've seen in here that you can install superSU by booting into twrp but without having to flash anything to the drive - meaning everything is stock.. Shouldn't that still allow the OTA updates?
paul_one said:
Well, I've seen in here that you can install superSU by booting into twrp but without having to flash anything to the drive - meaning everything is stock.. Shouldn't that still allow the OTA updates?
Click to expand...
Click to collapse
No. Because rooting modifies the system partition (superuser apk and all related libraries are placed on different locations on the system partition), so the verification done by OTAs fail. Also, so far, the only way to achieve root is to modify the boot image and turn off dm-verity, which will also likely cause OTAs to fail.
craigacgomez said:
No. Because rooting modifies the system partition (superuser apk and all related libraries are placed on different locations on the system partition), so the verification done by OTAs fail. Also, so far, the only way to achieve root is to modify the boot image and turn off dm-verity, which will also likely cause OTAs to fail.
Click to expand...
Click to collapse
Actually, there is a better way to provide root access that we are working on.
At present, I have prebuilt boot images for Nexus 5, 6, 9. I do NOT have prebuilt boot images for 5x or 6p *yet* due to lack of device tree source code on google's git (hopefully they will fill that in soon).
You can read over the thread about it here;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
We are also working on a way to inject the changes into an existing binary sepolicy, but that process is in a very very alpha state currently.
There are two options currently that I can see for providing root access to a 5x or 6p;
1) try using a 6's sepolicy and related files and hope for the best, probably won't work,
2) generate a permissive sepolicy
Once the device tree source is provided and we can generate boot images from source, this will, of course, change -- we will be able to build the proper policy from source.
Summary of this approach;
The system image is *NOT* impacted in ANY way. All of the differences are added to the boot ramdisk.
doitright said:
Actually, there is a better way to provide root access that we are working on.
At present, I have prebuilt boot images for Nexus 5, 6, 9. I do NOT have prebuilt boot images for 5x or 6p *yet* due to lack of device tree source code on google's git (hopefully they will fill that in soon).
You can read over the thread about it here;
http://forum.xda-developers.com/nexus-6/general/root-t3231211
We are also working on a way to inject the changes into an existing binary sepolicy, but that process is in a very very alpha state currently.
There are two options currently that I can see for providing root access to a 5x or 6p;
1) try using a 6's sepolicy and related files and hope for the best, probably won't work,
2) generate a permissive sepolicy
Once the device tree source is provided and we can generate boot images from source, this will, of course, change -- we will be able to build the proper policy from source.
Summary of this approach;
The system image is *NOT* impacted in ANY way. All of the differences are added to the boot ramdisk.
Click to expand...
Click to collapse
So you do not have an su binary or Superuser apk installed in /system?
Sent from my Nexus 5X
craigacgomez said:
So you do not have an su binary or Superuser apk installed in /system?
Click to expand...
Click to collapse
Go read the thread.
doitright said:
Go read the thread.
Click to expand...
Click to collapse
I get an invalid thread message.
Sent from my Nexus 6P using Tapatalk
doitright said:
Go read the thread.
Click to expand...
Click to collapse
@doitright, very nice!! Love it!
Hi everyone
I want to root my nexus 5x to have xposed but the main issue is that I wouldn't be able to install otas even if I rooted with systemless root because xposed misses up system partition , so systemless root becomes pointless .
My question is if I rooted with systemless root and installed xposed , if I wanted to install any new ota if i just removed xposed will this be enough to return system to unmodified status and I can now install the ota , or my system will become modified untill I reinstall the whole binary image ??
Hope I made my question clear as possible and sorry for my bad English
Thanks in advance ...
Or, instead of worrying about OTAs, you could just get the images from the Google website since this is a Nexus device, we are supported for something like 3 years I think I read, with security updates persisting 1.5 years after that.
https://developers.google.com/android/nexus/images
(you would use fastboot flash to accomplish this)
I know , but I don't want to flash everytime the whole binary image if I just can install a ~< 10 mb OTA .
If i can Just uninstall xposed then install the ota that will be much easier ...
I don't think you can take ota updates with a custom recovery and without a custom recovery you would have to flash a system image to get it back to stock in order to take the ota
flashing updates manually via TWRP is very easy once youre used to doing it.
No I can install OTAs using flash fire if the system partition is unmodified , so that's why I'm asking if uninstalling xposed return system partition to unmodified status ?
@2x4 installing updates is very easy with chainfire's flashfire only if you have unmodified system partition , and I want to install xposed but at the same time I want to know if I just uninstalled xposed will that make my system unmodified again ...
Running the xposed uninstalled will undo any changes to the system partition. So to answer your question, yes.
@t-r-e you're coming from the angle of keeping your system partition intact for the SOLE purpose of OTAs (you've said nothing about android pay). Given that, it's easier to just update manually via TWRP instead of doing OTAs, so you won't have to worry about xposed or any other mods.
I've been reading on the forums and is there anyway to achieve system root on the n5x because i assume flashing SuperSu in twrp just gives you systemless root, I've read something about a modified boot.img, can anyone clarify this? and is system root possible on 7.0 NRD90S?
niklus101 said:
I've been reading on the forums and is there anyway to achieve system root on the n5x because i assume flashing SuperSu in twrp just gives you systemless root, I've read something about a modified boot.img, can anyone clarify this? and is system root possible on 7.0 NRD90S?
Click to expand...
Click to collapse
It is possible to have systen root.
You still need to have boot.img that has dm-verity disabled.
There are flags that you can set for SuperSU install that force it to do system install, but i don't recall if it will disable dm-verity in that case. If not, flash the modified kernel that is on the main thread.