Related
Systemless Root for Shield Tablet
Standard Disclaimer Applies:
Code:
You're responsible for everything that happens to your device.
If already rooted or have modified the system partition in any way. You must flash the stock system.img before following this guide.
Shield Tablet
SESuperuser Method:
Taken from the original thread.
Currently, three flavors of su are available:
- "eng" which puts "su" in permissive mode. This is the most compatible mode, but you should trust the apps you give root to. This does NOT put SELinux in permissive mode.
- "power" is meant to give all powers to su apps as well, but without setting permissive mode
- "user" is meant to give a safe su. su-apps won't be able to access to your Android Pay (for instance) informations, or keep persistent su access without your consent
Please note that power/user are in heavy development and aren't up to their promises at the moment.
Click to expand...
Click to collapse
Method 1:
The developer had kindly provided a build bot for the creation of these images and will be available there unless changes are made.
Go to, http://superuser.phh.me/nvidia/shieldtablet/ and download the version you want.
Flash the image via fastboot or TWRP
Let the device boot, it may loop a few times this is ok
Once the device is booted install the companion app https://play.google.com/store/apps/details?id=me.phh.superuser
Enjoy.
Method 2:
Download seSuperuser's superuser.zip from http://superuser.phh.me/
Flash superuser.zip in TWRP (use with other recoveries at your own risk)
Let the device boot, it may loop a few times this is ok
Once the device is booted install the companion app https://play.google.com/store/apps/details?id=me.phh.superuser
Enjoy.
To Unroot:
Download the stock boot image
Flash the stock boot image with fastboot or TWRP
Uninstall Superuser companion app
Reboot
You should now be unrooted
Note: If you are having trouble with a specific app or command with user/power try using eng. If that doesnt solve the issue file report the issue on the original thread. http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Chainfire SuperSU Method:
Systemless Root is now supposed to work with 5.1.x Reference post.
This method includes an automatic boot.img patcher to patch the boot.img durring flash to support the systemless root method. His automatic patch system will work on android versions 5.1.x and 6.0 The goal of systemless to make the root process more flexible and easier to take old-style and the newer block based OTAs on bootloader unlockable and non-unlockable devices.
Note: It is recommended that these steps are preformed on an android device using Root Explorer or Explorer from the same developer to ensure functionality.
Preparation Guide:
Download SuperSU-v2.60 from this thread
Navigate to and long press on the SuperSU-v2.60.zip file and select "Extract All" (if asked to go to extracted folder, do so.)
Navigate to SuperSU-v2.60/META-INF/com/google/android
Select "update-binary" and then "Text Editor"
Scroll down to the line that states the following
Code:
SAMSUNG=$(cat /system/build.prop | grep "ro.build.fingerprint=" | grep -i "samsung")
Change the line so it states nvidia instead of samsung
Code:
SAMSUNG=$(cat /system/build.prop | grep "ro.build.fingerprint=" | grep -i "nvidia")
Click the over flow button at the top and select "Save and Exit"
Delete the new file called "update-binary.bak"
Go back up the directory structure until the folder SuperSU-v2.60 is listed
Long press on the previously stated folder and select "Zip this folder"
The new zip will be located at /sdcard/SpeedSoftware/Archives/
Installation Guide:
An untouched boot.img is recommended.
Boot into TWRP and have it mount system as read only (If you suspect system was mounted at any point reflash the system.img)
Flash your modified SuperSU-v2.60.zip
The console should show "Systemless" and "Boot image patcher" at some point
If the console showed the previous items then it should have worked if not then it was not a systemless install
On boot after a successful Systemless root it will seem to boot loop, let it run for several loops and it should boot properly other wise the process must be started from the bigging.
Shield Tablet K1 - WIP
SESuperuser Method:
Taken from the original thread.
Currently, three flavors of su are available:
- "eng" which puts "su" in permissive mode. This is the most compatible mode, but you should trust the apps you give root to. This does NOT put SELinux in permissive mode.
- "power" is meant to give all powers to su apps as well, but without setting permissive mode
- "user" is meant to give a safe su. su-apps won't be able to access to your Android Pay (for instance) informations, or keep persistent su access without your consent
Please note that power/user are in heavy development and aren't up to their promises at the moment.
Click to expand...
Click to collapse
Method 1:
The developer had kindly provided a build bot for the creation of these images and will be available there unless changes are made.
Go to, http://superuser.phh.me/nvidia/shieldtablet/ and download the version you want.
Flash the image via fastboot or TWRP
Let the device boot, it may loop a few times this is ok
Once the device is booted install the companion app https://play.google.com/store/apps/details?id=me.phh.superuser
Enjoy.
Method 2:
Download seSuperuser's superuser.zip from http://superuser.phh.me/
Flash superuser.zip in TWRP (use with other recoveries at your own risk)
Let the device boot, it may loop a few times this is ok
Once the device is booted install the companion app https://play.google.com/store/apps/details?id=me.phh.superuser
Enjoy.
To Unroot:
Download the stock boot image
Flash the stock boot image with fastboot or TWRP
Uninstall Superuser companion app
Reboot
You should now be unrooted
Note: If you are having trouble with a specific app or command with user/power try using eng. If that doesnt solve the issue file report the issue on the original thread. http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Chainfire SuperSU Method:
Systemless Root is now supposed to work with 5.1.x Reference post.
This method includes an automatic boot.img patcher to patch the boot.img durring flash to support the systemless root method. His automatic patch system will work on android versions 5.1.x and 6.0 The goal of systemless to make the root process more flexible and easier to take old-style and the newer block based OTAs on bootloader unlockable and non-unlockable devices.
Note: It is recommended that these steps are preformed on an android device using Root Explorer or Explorer from the same developer to ensure functionality.
Preparation Guide:
Download SuperSU-v2.60 from this thread
Navigate to and long press on the SuperSU-v2.60.zip file and select "Extract All" (if asked to go to extracted folder, do so.)
Navigate to SuperSU-v2.60/META-INF/com/google/android
Select "update-binary" and then "Text Editor"
Scroll down to the line that states the following
Code:
SAMSUNG=$(cat /system/build.prop | grep "ro.build.fingerprint=" | grep -i "samsung")
Change the line so it states nvidia instead of samsung
Code:
SAMSUNG=$(cat /system/build.prop | grep "ro.build.fingerprint=" | grep -i "nvidia")
Click the over flow button at the top and select "Save and Exit"
Delete the new file called "update-binary.bak"
Go back up the directory structure until the folder SuperSU-v2.60 is listed
Long press on the previously stated folder and select "Zip this folder"
The new zip will be located at /sdcard/SpeedSoftware/Archives/
Installation Guide:
An untouched boot.img is recommended.
Boot into TWRP and have it mount system as read only (If you suspect system was mounted at any point reflash the system.img)
Flash your modified SuperSU-v2.60.zip
The console should show "Systemless" and "Boot image patcher" at some point
If the console showed the previous items then it should have worked if not then it was not a systemless install
On boot after a successful Systemless root it will seem to boot loop, let it run for several loops and it should boot properly other wise the process must be started from the bigging.
Old Guide:
Installation guide:
Download st8 systemless bootimg
Download shield tablet TWRP image
Download SuperSU-v2.60 from this thread
Unlock Bootloader
Flash stock system.img
Flash st8 systemless boot image
Flash TWRP
Prevent TWRP from mounting and modifying the system partition
Flash/Sideload SuperSU-v2.56 zip
Boot system and enjoy
After flashing the systemless root refrain from using any app or modification that touches the system partition for doing so defeats the purpose of this systemless root.
Take OTA:
Flash untouched boot image
Flash stock recovery
Flash/sideload OTA
Reinstall Systemless Root
Flashing can be done using TWRP's image flash method.
To unroot:
Delete all folders listed as /data/app/eu.chainfire.supersu.*
Delete /data/su.img
Delete /cache/su.img (if exists)
Flash stock unmodified boot.img
Flash system.img if at any point you suspect it has been modified
Reference thread
Downloads:
XDA-DB Download
Mirror
XDA:DevDB Information
[Root][Systemless] Shield Tablet Systemless Root, Tool/Utility for the Nvidia Shield Tablet
Contributors
Lrs121
Source Code: https://github.com/seSuperuser
Version Information
Status: Stable
Current Stable Version: v3.1.1
Stable Release Date: 2015-12-06
Current Beta Version: SuperSU-v2.60
Beta Release Date: 2015-12-05
Created 2015-12-01
Last Updated 2016-01-14
Important notes:
A modified boot image is not longer needed to achieve systemless root since the shieldtablet is compressed with gz. This op will be updated to reflect the changes necessary to achieve systemless root. old instructions will be left up for archival purposes.
Un-needed images remove, stock boot image is still available in the downloads.
Changelogs:
SESuperuser Changelog:
Code:
v3.1.1 - inital release.
Code:
holding txt
SuperSU Changelog:
Changelog:
Code:
SuperSU-v2.60 - New method with built in patcher available from Chainfire.
v3.1.1r2
Fixes: Fix init.environ.rc - remove double environment setup blocking proper /su/bin mounting
v3.1.1:
Inital release - based on stock boot.img with modifications for systemless root.
Code:
holding text
Finally did the 3.1.1 update tonight and tried the systemless root. AdFree and TWRP apps successfully requested root and worked perfectly.
durgis said:
Finally did the 3.1.1 update tonight and tried the systemless root. AdFree and TWRP apps successfully requested root and worked perfectly.
Click to expand...
Click to collapse
Adfree touches the hosts file in the system partition which ruins the point of this root method. http://adfree.odiousapps.com/about.php
Lrs121 said:
Adfree touches the hosts file in the system partition which ruins the point of this root method. http://adfree.odiousapps.com/about.php
Click to expand...
Click to collapse
I just discoverd this issue.
this method may not be working propperly anyway due to the way the nvidia mounts xbin on boot. root should still work but im going to have to figure out whats going on.
Lrs121 said:
I just discoverd this issue.
Click to expand...
Click to collapse
With this method SU still appears to be able to write to system. I'm not sure if it was meant to or not, but AdFree was still able to write /etc/hosts and symlink it to /data/hosts without issue.
durgis said:
With this method SU still appears to be able to write to system. I'm not sure if it was meant to or not, but AdFree was still able to write /etc/hosts and symlink it to /data/hosts without issue.
Click to expand...
Click to collapse
yes it doesnt prevent you from writing to system. thats to pont of having root, to have total control of your device. thats also why it states in the op to avoid using apps or mods that touch the system partition. when i get the issues fixed with mounting /su properly youll be able to use adaway and a su script to map the hosts to /su/etc/hosts without touching the system
found the line that is probably causing the problem. r2 will be posted when i get to work
update: Bah, this is far from ready for prime time, systemless currently has a min api level of 23 otherwise it does the old way. im still looking into getting it working propperly on 22 (current api of the shield tablet) but may not work until the marshmallow update is pushed.
Chainfire is thinking about getting systemless working for android 5.1.1 for samsung devices and should apply to many more. until either Nvidia pushes M out or until Chainfire feels like implementing backwards support.
Chainfire had updated his beta SuperSU to include support for 5.1.x versions of android. I will be testing soon.
It works people new guide and method is up!
Have you tested superuser.zip from http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ?
It works as-is on Shield TV, so I assume it should work on Shield Tablet.
You could even have this device supported by the buildbot so the root-ed boot.img would be directly available.
phhusson said:
Have you tested superuser.zip from http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 ?
It works as-is on Shield TV, so I assume it should work on Shield Tablet.
You could even have this device supported by the buildbot so the root-ed boot.img would be directly available.
Click to expand...
Click to collapse
I'd believe it might, however I have yet to test it. I have been following development, though I'm not quite certain how rooted boot images work. especially in relation as to allow easier ota updates such as the SuperSU systemless method does.
Lrs121 said:
I'd believe it might, however I have yet to test it. I have been following development, though I'm not quite certain how rooted boot images work. especially in relation as to allow easier ota updates such as the SuperSU systemless method does.
Click to expand...
Click to collapse
This SuperUser IS systemless.
phhusson said:
This SuperUser IS systemless.
Click to expand...
Click to collapse
So it doesnt touch the system at all?
Lrs121 said:
So it doesnt touch the system at all?
Click to expand...
Click to collapse
That's the idea, yes
phhusson said:
That's the idea, yes
Click to expand...
Click to collapse
Always the fan of opensource, I'm looking into it now.
OP changed to reflect new systemless root methods. Modified boot images are no longer required for the SuperSU method as a patcher is built in. Flashing the seSuperuser superuser.zip will do the the same as well without having to download a premodified boot image
There are many people looking to root the shieldtablet k1 Android m update. I'm away from my computer at the moment so an image won't be loaded to the db just yet. However they can be found here https://lrsservers.ddns.net/download/devices/nvidia/shieldtablet-k1/boot/ - sorry for not actually making a link I forgot the bbcode since I'm using the xda labs app. To download on Android use firefox and add a permanent exception, I'm still using a self signed certificate for HTTPS and haven't migrated to a public CA just yet. Like usual flash the image then install phh's superuser and you should be good to go.
The current version of TWRP will not accept your pin/password on 8.1. Until we get an update to TWRP there are a couple of work arounds.
One option is totally wipe your phone and root it before you set up a pin/password/fingerprint.
The other option is to get a thumb drive and a USB to C adapter from Best Buy or elsewhere. Put SU on the thumb drive, boot to TWRP img with fastboot as you normally do and then plug in the thumb drive to the phone. In twrp you will see an option to select storage, select the OTG USB Drive and you can install SU from there.
Edit. As of Jan 1 it looks like SU is no longer working. I have switched to Magisk without issue.
Good to know! Kudos
Which version of TWRP and SU did you use? Is it possible to install custom kernel on 8.1.?Thank you ?
veskostoev said:
Which version of TWRP and SU did you use? Is it possible to install custom kernel on 8.1.?Thank you ?
Click to expand...
Click to collapse
3.1.1.1 TWRP and 2.82 SR5 SU. The latest of both. So far I have not gotten EX to work, it boot loops. Going to try a couple of things after dinner but I expect it will fail.
Actually, you could use the old fastboot boot boot-to-root method used on 8.0 dev. It also works on 8.1 dev. Then you could use Flashfire to flash the latest SuperSU SR5 as the boot-to-root SuperSU version is an old one (SR1). Remember to choose Auto Mount option. Works for me, hope it helps you guys.
I tried flash fire but couldn't seem to get it to work. I just get a black screen. I know it says this is normal and it should come up after half a minute. I gave it a few minutes and never got anything other than the black screen. Did you get this screen? How long did it last?
EDIT- nevermind just did it with TWRP
TonikJDK said:
One option is totally wipe your phone and root it before you set up a pin/password/fingerprint.
Click to expand...
Click to collapse
I'm assuming after it is rooted, you can enable PIN/fingerprint? If so, what happens when the next dev build comes out, you will have to wipe again and setup without a pin/fingerprint and then add again, or hope TWRP is updated by then?
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
I just adb sideloaded the latest Magisk beta after the data decryption failed and I have root.
cleeezzz said:
I just adb sideloaded the latest Magisk beta after the data decryption failed and I have root.
Click to expand...
Click to collapse
How? It fails signature verification when I try
Rooted with SU and usb stick works perfectly. Thank you very much.
chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
where to find 14.3 zip? i found only version 14..or you mean to flash 14 and to update the app to v. 14.3?
chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
it works! thanks! :good:
galza said:
where to find 14.3 zip? i found only version 14..or you mean to flash 14 and to update the app to v. 14.3?
Click to expand...
Click to collapse
No, just flash Magisk the first time. No need to do any updates.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
Great method just did that and working flawless thanks mate
chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
I know this may sound stupid, but is there a more complete guide to this? I was able to root on 8.0, but I'm not sure I understand your method. Do I just type these commands into adb?
Juzman said:
I'm assuming after it is rooted, you can enable PIN/fingerprint? If so, what happens when the next dev build comes out, you will have to wipe again and setup without a pin/fingerprint and then add again, or hope TWRP is updated by then?
Click to expand...
Click to collapse
That would interest me also whether it is then possible to use fingerprint without the Twrp no longer goes.
DarthScabrous said:
I know this may sound stupid, but is there a more complete guide to this? I was able to root on 8.0, but I'm not sure I understand your method. Do I just type these commands into adb?
Click to expand...
Click to collapse
I might make a quick guide this afternoon. Got a few things I need to get done first. But I'll make another guide.
chevycam94 said:
Here is what I did to get root on 8.1:
1: Flash factory image of 8.1 WITH the "-w" (wipe) command
2: Boot up and set up the system (and updated apps while I was there)
3: Reboot into bootloader
4: fastboot BOOT TWRP 3.1.1-1
5: Flash TWRP 3.1.1-1
6: Reboot to recovery
7: Flash Magisk v14.3
8: Reboot to Android
I'm now running 8.1 with Magisk v14.3, and root it working as it should. I also have TWRP 3.1.1-1 installed, functional, and accessible via reboot without the need for a computer.
Click to expand...
Click to collapse
Worked perfect for me. Since I setup phone, fingerprint and pin before I installed TWRP and magisk, it bootlooped.
So, I re-flashed the 8.1, and then followed steps 3-8.
Thanks!
bradhoschar said:
Worked perfect for me. Since I setup phone, fingerprint and pin before I installed TWRP and magisk, it bootlooped.
So, I re-flashed the 8.1, and then followed steps 3-8.
Thanks!
Click to expand...
Click to collapse
Would deleting fingerprint / security, etc before rebooting resolve the TWRP lock issue?
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?
Hi guys,
I have gone thru the forum to install Magisk systemless root in S7 Edge running 8.0 but have few questions.
1. Is TWRP mandatory to install Magisk for systemless root?
2. If above point is yes, then will the device be eligible for OTA even with TWRP recovery?
3. Please provide steps to install Magisk systemless root in S7 Edge running 8.0 latest October patch
Thanks in advance.
mpadhu said:
Hi guys,
I have gone thru the forum to install Magisk systemless root in S7 Edge running 8.0 but have few questions.
1. Is TWRP mandatory to install Magisk for systemless root?
2. If above point is yes, then will the device be eligible for OTA even with TWRP recovery?
3. Please provide steps to install Magisk systemless root in S7 Edge running 8.0 latest October patch
Thanks in advance.
Click to expand...
Click to collapse
Go Here https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
1. U need TWRP for flashing Magisk.
2. When ur intentions are gaining root access, u should forgo OTA.
3. The above link has everything u need.
joeljose1001 said:
Go Here https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-root-android-8-0-oreo-t3840271
1. U need TWRP for flashing Magisk.
2. When ur intentions are gaining root access, u should forgo OTA.
3. The above link has everything u need.
Click to expand...
Click to collapse
Thank you for your time and response. There is something called systemless root which will hide the root from the system and also allows official OTA updates.
mpadhu said:
Thank you for your time and response. There is something called systemless root which will hide the root from the system and also allows official OTA updates.
Click to expand...
Click to collapse
From what I know, when you download an OTA and prompt your device to install it, your Android system performs a series of checksums to ensure that your /system, /boot, /recovery, and /vendor (or /OEM) partitions are unmodified from their original stock configuration.
The benefit of Magisk is that it does not modify the system partition, but while installing Magisk, the first thing it does is patch boot image. So you might have to restore the original boot image for the OTA to work.
Also, the OTA is designed to be installed via the stock recovery which has been overwritten with TWRP. So, I think u will face a problem there too.
I'm not saying that it's impossible to get an OTA update. It just might not be as easy as u r used to.
joeljose1001 said:
From what I know, when you download an OTA and prompt your device to install it, your Android system performs a series of checksums to ensure that your /system, /boot, /recovery, and /vendor (or /OEM) partitions are unmodified from their original stock configuration.
The benefit of Magisk is that it does not modify the system partition, but while installing Magisk, the first thing it does is patch boot image. So you might have to restore the original boot image for the OTA to work.
Also, the OTA is designed to be installed via the stock recovery which has been overwritten with TWRP. So, I think u will face a problem there too.
I'm not saying that it's impossible to get an OTA update. It just might not be as easy as u r used to.
Click to expand...
Click to collapse
Got your point. Thank you. I read that Magisk can be installed without root or even custom recovery.
The below is taken from the official Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
How to download or extract the stock boot image file from my official ROM?
"Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img"
I have installed latest android 10 stock rom. i tried using the magisk manager patch AP file method. i flashed the patched AP file CP BL and Twrp. tar in userdata on Odin.
TWRP 3.4.0.4 is installed but when i boot it gets stuck on samsung boot animation.
i tried flashing magisk zip from twrp and then it continuous bootloops to the Samsung bootloader image.
Do i root first stock and then install later TWRP?
Can anyone list out a short guide how to root Android 10 and aldo have TWRP with it.
I found the solution as
1. Install stock rom
2. follow root guide 1.0
3. Patch AP file with magisk manager
4. Download TWrRP App from playstore
4. Root stock rom
5 Install Twrp with the method in this link https://forum.xda-developers.com/tab-s5e/how-to/instal-twrp-p-c-galaxy-tab-s5e-sm-t720-t4072231.
6. Now I have stock rom rooted with latest twrp.
By the way also fixed device signature modified with magisk prop and busybox module and editing build prop to match device fingerprint error.
Moderators please kindly close this thread as solution found