Develop Bugs

Does rooting only removes the ability for OTA updates?

Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.
Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
Sent from my Nexus 7 using Tapatalk 4

Mine is always rooted, and I get all OTAs.
Sent from my Nexus 7 using xda app-developers app

You just need to have the stock recovery to receive OTAs.

Username invalid said:
You just need to have the stock recovery to receive OTAs.
Click to expand...
Click to collapse
So if I have twrp installed, i won't receive them?
Sent from my Nexus 7 using Tapatalk 4

Takes 10 seconds to reflash the stock recovery.

UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is no longer necessary unless you are using an older version of SuperSU
This post also applies to JSS15Q update.
I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.
Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.
I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)
install UPDATE-SuperSU-v1.55.zip
install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)
reboot
You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.
Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.
If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.

Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Sent from my Nexus 7 using xda app-developers app

rmm200 said:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
Click to expand...
Click to collapse
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.
Thus it is safest to use stock recovery to flash OTAs.
I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.
I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.

Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?

It was common on other platforms I've used, but I don't know about here.

Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:
If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted
If you are running stock recovery, the update will install automatically as normal
If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use
If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs
Also:
You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)
You can flash factory images instead of the update, without losing data (see other threads for how)
If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it
The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong Hope this helps.

phazerorg said:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically).
Click to expand...
Click to collapse
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.
With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.
You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.

TheAltruistic said:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries?
Click to expand...
Click to collapse
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2

nolook said:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...
just keep in mind you need to keep your files stock otherwise it might not work
Sent from my Nexus 7 2
Click to expand...
Click to collapse
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
Titanium backup is an app, I assume with files he is targeting e. G. Config files.
Sent from my Nexus 7 (2013)

Mightym83 said:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
Click to expand...
Click to collapse
It means don't modify or delete any files in /system
Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)
Adding files is ok.

Alright, so here's my scenario. Hopefully someone can tell me what should happen:
I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.
So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?
Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?
(that last part is just my OCD talking)

phazerorg said:
:
[*]If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)
Click to expand...
Click to collapse
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?
So basically what you are saying is this, with my current set up:
1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?
2 - I can just wait for the download to be posted on here, and just install via twrp.
3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.
Correct?

Theoretically it could work. I believe the flash has worked with twrp.
Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.
On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.
Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.

If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?
Then go through and use it to recreate the root\custom recovery again?

[HELP!] Systemless Rooting on 6.0.1 Build MMB29P

Hi! So I'm looking to root my Nexus 5x following this guide. However, I can't find the modified boot.img for my build MMB29P. I have a brand new phone out of the box (my mic stopped working so this is a replacement) so I'd like to get this done in the next little while the phone has no data and I can wipe anything I need to without worry and use the restore afterwards. I also heard something about SuperSU being able to use stock boot.img or something of that nature, could someone clue me in? Thanks!

[GUIDE] Unlock/Root/Flash for Nexus 5X - Heisenberg's How-To Guide For Beginners
take a look at section 6
as an alternative there are some toolkits that may be more convenient to you (on-screen instructions and detailed faq/guides)

The latest version of SuperSU (v. 2.66 I believe) is automated for systems root. I actually used the SuperSU beta v. 2.62 to root. I just unlocked bootloader, flashed TWRP, and then flashed that version of SuperSU.
Sent from my Nexus 5X using Tapatalk

Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?

jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.

https://www.androidfilehost.com/?w=files&flid=43558

k.s.deviate said:
No, an official image cannot be flashed like that. If you fastboot flash an image you will lose recovery and root. Update officially with a factory image and root afterwards or flash a custom rom plus vendor.img.
Click to expand...
Click to collapse
Even with systemless root?

When it comes to upgrading, there are a couple of routes you can take. Both involve downloading the official factory image ZIP first. Extract the contents, reboot into bootloader, and then you have option:
1. Edit the flash-all script (.bat for windows and .sh for Linux/Mac) by removing the -w option. Removing this option will prevent the upgrade from wiping user data. Once the option is removed, simply run the script to upgrade.
2. Flash the images individually. Sometimes certain things don't change like bootloader.img or radio.img. You should always flash boot.img, system.img, and vendor.img when updating. This is the route I take.
After flashing the images, you will need to reboot into Recovery mode and flash SuperSU. Then wipe cache and dalvik and reboot into system. If you use a custom kernel, you will need to reflash that as well after updating.
Sent from my Nexus 5X using Tapatalk

Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.

jkingaround said:
Ah makes sense. So I just need to reroot. Where do you get the "official" factory image? Have a link handy so I can bookmark it? Thanks!
Also anyway to remove the "warning" about unlocked bootloader that comes up on boot? I heard you need a custom kernel but I don't know the point of installing what (aka the benefits). Sorry for noob questions, but all the info is so scattered and hard to figure out.
Click to expand...
Click to collapse
Google posts the official factory images on the developer site. Here is the link: https://developers.google.com/android/nexus/images
AFAIK the boot warning can't be removed, but I may be wrong. It's nothing to worry about though.
Having a custom kernel is not necessary, but there are benefits to using one. Custom kernels typically provide better battery life with same or improved performance. They can also make your device run cooler and use less memory. Custom kernels also allow for various tweaks such as change vibration intensty, screen DPI, headphone/speaker gain, etc. I personally use ElementalX with the Interactive Governor tweaks from the thread in the general forum, but I've read that Franco Kernel is very good as well and will probably try that out in the future.
Sent from my Nexus 5X using Tapatalk

jkingaround said:
Sweet! Officially, unlocked, TWRP'd, rooted, and supersu'd So as far as upgrading? I grab the file from google officially and flash it via TWRP?
Click to expand...
Click to collapse
Just pick a custom rom to try and follow OP instructions. Cataclysm seems to be a hit...

How to remove Root from Galaxy Tab S?

I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks

There is no update. 5.0.2 is the latest.

ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!

MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app

3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?

MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck

3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:

If you want to go back to stock just flash the latest firmware with odin.

Keep Magisk/Root and Take Updates?

On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?

wy1d said:
On OG Pixel XL, I used to be able to follow this guide to take OTA updates and retain Magisk/root:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
It was the BEST! Super quick, small delta file download, one reboot and DONE. No PC needed, no full system image (1.6GB) download required.
But it hasn't worked with Pixel 2 XL (or maybe it's Magisk 15.x that broke this process?). Now any time I try this I get boot loops and end up having to download the full system image, flash-all.bat (remove -w) and then copy the boot.img, patch it in Magisk, and reflash via fastboot. I'd really love a way to be able to take OTA updates without having to get to a PC.
Is there an easier way?
I should mention the ONLY reason I use Magisk is to hide the fact I have an unlocked bootloader and allow things like Android Pay/Samsung Pay (which is broken with latest update anyway - detects Magisk). Any recommendations?
Click to expand...
Click to collapse
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.

mac796 said:
I'm not sure about your way anymore cuz I always install it with TW RP but if you don't need root and you're just wanting to hide your unlocked Bootloader you can just flash a custom kernel and be done with it.
Click to expand...
Click to collapse
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk

wy1d said:
Hey! Thanks for the quick reply. Wouldn't flashing a custom kernel be the same cat and mouse since the OTA would flash a new kernel? I'd need to have a mechanism for flashing the kernel which I'm guessing means TWRP.
I always ran a custom recovery before Pixel so I'm familiar with TWRP but having a custom recovery means you can't take OTA. What is your process for flashing the updates in TWRP? I thought you had to have a flashable .zip file specifically meant to be flashed in a custom recovery. Are you now able to flash system images from there? Do you just reflash Magisk after each time? I'm guessing that means you have to download the full 1.6G image since Google doesn't post the delta file?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA

mac796 said:
I always Flash the factory image I don't take the OTA. And then I fastboot the TWRP boot image and then install the twrp zip. After that you'd Flash the magisk zip inside TWRP. But if you're just looking to hide the bootloader you can fastboot the custom kernel on stock with no root I Believe In The Flash thread he has both files the fastboot and the Zips for TWrp. But yeah every month you want to flash an updated kernel. Nate actually keeps up on the security updates so he has a new ones quite often.
Edit. Yes so if you wanted to take the OTA I believe you would have to flash the factory boot image to wipe out that kernel and then you could take the following months OTA
Click to expand...
Click to collapse
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk

wy1d said:
So you do the full download and flash it from your PC every month?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.

mac796 said:
Yeah that's how I do it I edit the flash all bat remove the - w
So it doesn't wipe your data. It's pretty much like taking the OTA the manual way. But if you don't want to do that. And just take the OTA and you installed TWRP or if you just installed a custom kernel with fastboot. You just fastboot Flash the boot image of the month you're on and then you should be able to take your new OTA. I'm fairly sure you can do it that way I haven't done it that way in a long time.
Click to expand...
Click to collapse
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk

wy1d said:
That really isn't any quicker than what I'm doing now. I was hoping for a way to do it without needing a PC and fastboot although it does sound like that might prevent having to download the whole factory image (assuming TWRP can extract / backup the stock boot image?).
Seems like Flashfire or something like that was able to do this before - flashing the new image without a PC.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it

mac796 said:
I've always been told never install an OTA with Flashfire or TWRP, especially if it has a new updated bootloader. Because if something goes wrong you're done. But I know people do it all the time
There's even a warning in Flash fires directions about it
Click to expand...
Click to collapse
Such a bummer the Magisk method doesn't work anymore. It's definitely the safest and most graceful.
Sent from my Pixel 2 XL using Tapatalk

Root magisk questions

Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.

Kape1234 said:
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Click to expand...
Click to collapse
Hello,
First off I would just let you know that typically questions like this go in the Q&A section.. This is S20/S20+/S20U Snapdragon Development thread which is usually reserved for people who develop things such as roms, twrp, mods etc. etc. so be sure to ready the rules and other stickied information when considering to post just to be sure you post in the right section.
So next thing I want to say is that in order to use TWRP or root or anything custom really on a usa Snapdragon model (U/U1/W Models) you have to use paid service to unlock the bootloader IF your device is eligible to be unlocked which means you haven't updated to the latest OS, if it is, then you are out of luck for now until new method is developed using new security.
If you are unlocked already, can unlock or just want to know I will try and answer your questions now.
1) TWRP is not necessary. Neither is patching the full ROM. All you need to do (if you don't want to use TWRP) is take the boot.img from the stock firmware, patch it using Magisk app and then flash it in ODIN. Device will wipe most likely if encryption and vbmeta etc. isn't disabled already. I do not know if "encryption" works while just rooted using Magisk patched boot.img or not as I usually disable all that stuff. My guess is that in some form it would be encrypted, just not sure if it's the same thing you are referring to or not.
2) If you are on an unlocked bootloader and complete stock i.e. no root or anything just clean full stock then you should get OTA updates. If you use anything "custom" i.e. Magisk patched boot.img or TWRP installed or vbmeta disabled etc. etc. then OTA updates will NOT work. And no, you don't have to revert to stock in ODIN each time there is a firmware update. It really depends on the update but you can typically use the odin tar with home csc and it should update without wiping but at the same time you would lose root or need to re-patch the new boot.img etc. etc. but wouldn't necessarily have to flash stock first then start over. There's also "safe" updates available some posted by jrkruse in development sections. If you had a usa unlocked device that was unlocked using paid service then you do NOT want to take OTA's because Samsung has changed the way tokens are verified when device boots up so new OS can't read them and most devices have incremented the bootloader so if you did take an OTA you likely would lost your unlock and no way to downgrade.
3) No. In order to do that you would need Samsung's private keys since there is no way to load your own custom key to use.. you can't just sign it with any key.. Also, if you relock your bootloader on a USA model that was unlocked using paid service then you will not be able to unlock again.. either way, it's not possible to use a custom signed firmware then relock the bootloader and have it boot.. not on Samsung anyway..
Hope that clears it up for you.
Thanks