Develop Bugs

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.

Ota update for pixel 2 xl with magisk and twrp already installed

I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.

I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota

Thanks for your help. I will try that.

magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:

Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.

rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...

Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?

You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.

Root SM-G780F (Exynos)

Hi there,
I just dared to try and root my new S20 FE...and it worked.
I basically followed the steps in the S20 root Thread or the Link from the S10 root thread.
I didn't use vbmeta_disabled.tar, seems like it is not needed anymore.

Was also curious if we could just use TWRP from S20...but I ended up with a soft brick...so doesn't seem to be so easy :crying::crying:

danjac said:
Was also curious if we could just use TWRP from S20...but I ended up with a soft brick...so doesn't seem to be so easy :crying::crying:
Click to expand...
Click to collapse
what is the worst way you can brick it?

Sp8ky said:
what is the worst way you can brick it?
Click to expand...
Click to collapse
Hard brick where you are stuck with a phone that never boot again. Very hard to do though

I would attempt it but I couldn’t find an Australian firmware...

danjac said:
Hi there,
I just dared to try and root my new S20 FE...and it worked.
I basically followed the steps in the S20 root Thread or the Link from the S10 root thread.
I didn't use vbmeta_disabled.tar, seems like it is not needed anymore.
Click to expand...
Click to collapse
Just managed to root my 5G SD version as well following the S20 link. It’s even easier now using the latest magisk manager to directly install magisk rather than patching tar file.
Edit: I didn’t use vbmeta either.

tadasu said:
Just managed to root my 5G SD version as well following the S20 link. It’s even easier now using the latest magisk manager to directly install magisk rather than patching tar file.
Edit: I didn’t use vbmeta either.
Click to expand...
Click to collapse
Can you please summarize the steps performed?
Btw on the S20 forum section [RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon) a recovery is ready to test.

bognik said:
Can you please summarize the steps performed?
Btw on the S20 forum section [RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon) a recovery is ready to test.
Click to expand...
Click to collapse
As per the S20 link by OP, here's a very quick summary of what I did:
1. Unlocked my bootloader.
2. Skipped "Stage 3: Disable Android Verified Boot" in the link.
3. Searched and downloaded latest official firmware from sammobile specific for my australian model.
4. Used Odin to upgrade. I put CSC instead of HOME_CSC to erase all my data (not much data on my phone anyway) wanting a clean upgrade, and left "USERDATA" blank.
5. Skipped "Stage 5 and 6" in the link.
6. Downloaded and installed Magisk Manager from Magisk official website.
7. Installed Magisk in Magisk Manager using its "Direct Install (recommended)" option (can't remember the exact words).
And my phone was rooted.
Note I did not do any backup while rooting my phone because it's pretty new and nothing much was on it (and it's not my primary phone), so it's a high risk procedure if it's your primary phone and if something went very wrong.
Hope this helps.

Can I flash European firmware to.my hong Kong version?

So the the U.S. At&t Snapdragon version can't be rooted?

ı just twrp please

tadasu said:
As per the S20 link by OP, here's a very quick summary of what I did:
1. Unlocked my bootloader.
2. Skipped "Stage 3: Disable Android Verified Boot" in the link.
3. Searched and downloaded latest official firmware from sammobile specific for my australian model.
4. Used Odin to upgrade. I put CSC instead of HOME_CSC to erase all my data (not much data on my phone anyway) wanting a clean upgrade, and left "USERDATA" blank.
5. Skipped "Stage 5 and 6" in the link.
6. Downloaded and installed Magisk Manager from Magisk official website.
7. Installed Magisk in Magisk Manager using its "Direct Install (recommended)" option (can't remember the exact words).
Click to expand...
Click to collapse
I don't get how you were able to utilize direct install.
Direct install would only appear if you already had root access isn't it?
If I follow steps
1 - unlocked bootloader
2 - skip stage 3
3 - skip stage 4 (due to already being on latest firmware.)
4 - skip stagr 5, 6 (your step)
5 - install magisk
6 - no direct install option.
?-?

everlasting207 said:
I don't get how you were able to utilize direct install.
Direct install would only appear if you already had root access isn't it?
If I follow steps
1 - unlocked bootloader
2 - skip stage 3
3 - skip stage 4 (due to already being on latest firmware.)
4 - skip stagr 5, 6 (your step)
5 - install magisk
6 - no direct install option.
?-?
Click to expand...
Click to collapse
I'm not sure why I was able to do direct install on my unrooted phone, noob here just following guides

I haven't had a samsung phone before, if I root it am I going to have problerms with warranty later?

I was able to install magisk root using instructions here: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Used Frija for getting the FW.
edit: It seems magisk on this device breaks Tidal? Can anyone else confirm? Flashed back to stock, Tidal works, but with magisk patched tidal stops playback of all songs at 0:19.

I have some problems with rooting my device:
I tried to flash vbmeta_disabled.tar but ODIN fails to flash it
I used magisk to patch the boot.img and then flashed the image using ODIN, root works and I can access the system, but I can't change system to read-write, so I can't make any changes to files in system (or any other folder in root). Any apps I have get root access from magisk, but fail when attempting to make any changes to system files, so they are useless.
Does anyone else have these issues? Is there a step I should have done to be able to write to system/root?

So what's the process of root on Android 11?

cyyy said:
I have some problems with rooting my device:
I tried to flash vbmeta_disabled.tar but ODIN fails to flash it
I used magisk to patch the boot.img and then flashed the image using ODIN, root works and I can access the system, but I can't change system to read-write, so I can't make any changes to files in system (or any other folder in root). Any apps I have get root access from magisk, but fail when attempting to make any changes to system files, so they are useless.
Does anyone else have these issues? Is there a step I should have done to be able to write to system/root?
Click to expand...
Click to collapse
in my limited understanding android 10+ has a strictly read only system partition. any changes have to made via magisk overlays like systemless host files in adaway for example. EDIT: also there's ADB that can edit / write.

Has anyone got the full steps for rooting a new s20 fe? Lets say I buy the phone and upgrade using ota to Android 11 straight away...then what?

danjac said:
Hi there,
I just dared to try and root my new S20 FE...and it worked.
I basically followed the steps in the S20 root Thread or the Link from the S10 root thread.
I didn't use vbmeta_disabled.tar, seems like it is not needed anymore.
Click to expand...
Click to collapse
que al me podría indicar el proceso de instalación que usaste?
Translation: Could you tell me the installation process you used?

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

Question Update rooted Android 13

I just read the how to guide for this device.
Is there no easy way of updating the stock rom on a Magisk rooted phone?
I would have thought it should be possible to flash the full update in Android and tell Magisk to install to the inactive slot?
Especially there does not seem to be any opportunity without either using a computer or first uninstalling magisk (and for some reason all modules) and rebooting.
Best regards

TheColin21 said:
I just read the how to guide for this device.
Is there no easy way of updating the stock rom on a Magisk rooted phone?
I would have thought it should be possible to flash the full update in Android and tell Magisk to install to the inactive slot?
Especially there does not seem to be any opportunity without either using a computer or first uninstalling magisk (and for some reason all modules) and rebooting.
Best regards
Click to expand...
Click to collapse
You can do the "Install to inactive slot method", but it's been hit or miss for a lot of folks.

that's extremely weird. If it's a miss, can I still just flash the image through fastboot?

TheColin21 said:
that's extremely weird. If it's a miss, can I still just flash the image through fastboot?
Click to expand...
Click to collapse
Yes.
Several of our How To Guides in this section detail the full image method as well, which you can use if the OTA method fails. For that matter, you can also use the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
For what it's worth, for the last six years on my Pixels, I always use the (full) factory image, never the OTA method. I consider the factory image method easy. From what I read about people having trouble with the OTA method every few months (not due to their fault), I will likely never use the OTA method, but I understand why some people want to.

In that case I'll probably create a script which downloads the factory image, extracts it, patches boot.img, and then installs the rest through fastboot... Still a lot more complex than on my current device (hotdog), where I just flash the full image from Android, select install to inactive slot and reboot.... thanks a lot for the information.

TheColin21 said:
In that case I'll probably create a script which downloads the factory image, extracts it, patches boot.img, and then installs the rest through fastboot... Still a lot more complex than on my current device (hotdog), where I just flash the full image from Android, select install to inactive slot and reboot.... thanks a lot for the information.
Click to expand...
Click to collapse
As I've mentioned to @Lughnasadh before, I miss the days on my Pixel 1 when I could use Chainfire's [root] FlashFire app (last updated in 2017) to flash an update and re-root with SuperSU all directly from the device and in one step. A short but happy time.

No problems with this How To Guide

Lughnasadh said:
You can do the "Install to inactive slot method", but it's been hit or miss for a lot of folks.
Click to expand...
Click to collapse
dont do this this way.

roirraW edor ehT said:
As I've mentioned to @Lughnasadh before, I miss the days on my Pixel 1 when I could use Chainfire's [root] FlashFire app (last updated in 2017) to flash an update and re-root with SuperSU all directly from the device and in one step. A short but happy time.
Click to expand...
Click to collapse
RIP Flashfire