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.
I can't able to flash xposed zip file via TWRP for oreo 8.1 so i used this magisk method and its working on 8.1 aosp rom.
Recognized Contributor @topjohnwu has modified the*Xposed*Framework (V.85.1) to work alongside Chainfire's*systemless*SuperSU in order to also run without modifying the*system*partition. This means that you can install*Xposed*modules on a rooted device running the stock ROM and continue to receive OTAs
And can pass safety net check so u can use any root app which interfere in system.
Video guide:
https://youtu.be/4mW16FJjCPU
Requirements :
1)MAGISK ROOT
2)SOME FLASHING KNOWLEDGE (for installing magisk only)
DOWNLOAD AND FLASH MAGISK v16 IN TWRP AND INSTALL MAGISK MANAGER APP 5.6.2
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445#login
AND FOLLOW ALL STEPS IN VIDEO
KEEP NANDROID BACKUP IF ANY CASE DEVICE DOESN'T BOOT
Working XPOSED modules list for OREO
https://forum.xda-developers.com/xposed/xposed-modules-oreo-t3732819
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3a.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3aRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
oh my gosh would you believe i desperately needed this on tuesday and, after several hours spent trying unsuccessfully to get magisk manager for recovery working, ended up reflashing and starting again from scratch! crazy timing. anyway thanks for this, will definitely come in handy as i am too stupid to learn from my mistakes, ever.
c_tho said:
oh my gosh would you believe i desperately needed this on tuesday and, after several hours spent trying unsuccessfully to get magisk manager for recovery working, ended up reflashing and starting again from scratch! crazy timing. anyway thanks for this, will definitely come in handy as i am too stupid to learn from my mistakes, ever.
Click to expand...
Click to collapse
Relatable. I've had to hard wipe twice as I'm not used to this a/b stuff without TWRP lol. I've learnt my lesson though and finally granted shell root access, so assuming the phone boots past the bootloader I can use adb to fix up my magisk install.
Sent from my Google Pixel 3a XL using XDA Labs
Thank you! I've been running the stock kernel for the past several days because of a borked Magisk module. I couldn't fix the problem through TWRP since I'm on Android 10. This boot image allowed me to get back root without wiping. So thanks again!
Do you mind explaining how you made the image? I saw on the Magisk website that such a thing was possible but was unable to actually find details on how to create a core only image.
benji said:
Thank you! I've been running the stock kernel for the past several days because of a borked Magisk module. I couldn't fix the problem through TWRP since I'm on Android 10. This boot image allowed me to get back root without wiping. So thanks again!
Do you mind explaining how you made the image? I saw on the Magisk website that such a thing was possible but was unable to actually find details on how to create a core only image.
Click to expand...
Click to collapse
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack a copy of your magisk_patched.img.
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
I definitely need to make sure I have this handy. A few questions, if you don't mind.
1. I would assume one should make a new version everytime they update to the latest security patch, correct? For example, I should not use a patched boot.ing from the December patch if I'm on the January, patch, correct?
2. Do your instructions assume that someone already put a .disable_magisk file in /cache, or does the boot.img itself do that job?
Bramton1 said:
I definitely need to make sure I have this handy. A few questions, if you don't mind.
1. I would assume one should make a new version everytime they update to the latest security patch, correct? For example, I should not use a patched boot.ing from the December patch if I'm on the January, patch, correct?
2. Do your instructions assume that someone already put a .disable_magisk file in /cache, or does the boot.img itself do that job?
Click to expand...
Click to collapse
To update boot would be best but you are just booting the image, not flashing. The old method required building a modded version of Magisk. The new method you just unpack the magisk_patched.img and drop in the overlay folder.
The boot image installs the .disable_magisk file for you.
March boot fix images uploaded.
Thank god for this one. I almost did a fullwipe because I couldn't get Magisk to work after flashing the March factory image in order to update. Turns out I forgot to remove your center clock/battery icon gone module. I didn't expect it to be the culprit, but it seems it was. Regardless, I'm back to working root after days of trying to find a fix
Is it possible to fastboot boot (not flash) the modified boot image for disabling modules and then install Magisk via Magisk Manager?
cucumbersmell said:
Is it possible to fastboot boot (not flash) the modified boot image for disabling modules and then install Magisk via Magisk Manager?
Click to expand...
Click to collapse
You should be able to boot with the modified image, but you don't "install" Magisk then - Magisk is already installed, just you booted with all the modules disabled
Just open Magisk Manager, go to Modules and mark to remove the module(s) causing bootloop.
Pay also attention to remove
.disable-magisk file from /cache
as described in OP post #1
Then reboot with your proper Magisk patched image (no more Core Only) and if you have removed the module in the previous step, this time you should be booted to Magisk with no bootloop and with your other modules re-enabled again
zgfg said:
You should be able to boot with the modified image, but you don't "install" Magisk then - Magisk is already installed, just you booted with all the modules disabled
Just open Magisk Manager, go to Modules and mark to remove the module(s) causing bootloop.
Pay also attention to remove
.disable-magisk file from /cache
as described in OP post #1
Then reboot with your proper Magisk patched image (no more Core Only) and if you have removed the module in the previous step, this time you should be booted to Magisk with no bootloop and with your other modules re-enabled again
Click to expand...
Click to collapse
I used Tulsadiver's core-only boot.img for the OP7T to root the phone by fastboot booting it and then using Magisk Manager to install to the active and inactive slots. Was hoping the boot.img for the 3a would work similarly. Was nice and simple and saved the time of having to download and patch the boot.img.
cucumbersmell said:
I used Tulsadiver's core-only boot.img for the OP7T to root the phone by fastboot booting it and then using Magisk Manager to install to the active and inactive slots. Was hoping the boot.img for the 3a would work similarly. Was nice and simple and saved the time of having to download and patch the boot.img.
Click to expand...
Click to collapse
It is based off of a magisk_patched.img so you might be able to use it like that. You would need to remove the .disable_magisk file from the cache folder though. This is a little different than the one I helped out with on the 7T forum.
cucumbersmell said:
I used Tulsadiver's core-only boot.img for the OP7T to root the phone by fastboot booting it and then using Magisk Manager to install to the active and inactive slots. Was hoping the boot.img for the 3a would work similarly. Was nice and simple and saved the time of having to download and patch the boot.img.
Click to expand...
Click to collapse
Edit: Sorry, seems I just missed the thread ?
I've been running custom roms since before android was a thing so I'm usually pretty good at this stuff.
I'm running 11.0.9.9 IN11AA
It refuses to root. I'm not sure if there is some step I'm missing that's so obvious nobody mentions it?
I was rooted, but when the new Magisk 23 came out without Magisk hide.. it was a big problem for me. I have corporate apps that will refuse to work on a rooted device. I restored the stock images (just like I do to get my OTA).. but then I uninstalled Magisk 23 and Installed 22.1. I then patched the bootloader (Dire3ct Install) and all was good, until I rebooted and had no root.
My bootloader is unlocked.
So I downloaded the full stock rom v11.0.9.9 IN11AA directly from Oneplus.
Extracted payload.bin
Used Payload dumper to get the proper boot.img.
Copied boot.img to my device and used magisk 22.1 to patch the file.
Downloaded the patched boot.img to my desktop.
Used ADB to flash it
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
Nothing. No Root.
I tried this over and over with different versions of magisk.
I tried downloading pre-patched version, and using fastboot boot patched_boot.img.
The device just hangs, and then boots using the stock image. No root.
I have no idea what could be wrong.
Ideas?
I just updated from v11.0.8.8 to v11.0.9.9 today on the EU variant.
Downloaded the update via Oxygen Updater, then used the built in updater with the local file downloaded.
Before restarting the device, opened up Magisk, then clicked "Install to inactive slot" since the new update gets put on the inactive slot. After it installed, rebooted the phone, and done. Updated to latest, and kept root. Didn't even turn off the modules, although I only have 1 installed.
This is my usual method to keep root while updating.
I'm not sure where you got your Magisk from, but i'm using v23.0 from the official github page (HERE), and it still has MagiskHide built-in, and currently using it for all of my banking apps, and it works.
Most likely the issue is that you have used the old Magisk version to patch the file.
Download the app from the link above, and use that to patch your boot.img file.
While the extracted file should work as flashed, I like to just boot from it rather than flash it and make it "permanent".
Use fastboot boot patched_boot.img to boot using the file once only.
After starting up, you should have Magisk installed in a couple of seconds. It might prompt you to restart the phone when opening it first time, but just ignore that and do not restart as you'll lose the root. Alternatively, you can install the app when you're not rooted yet, and when you boot using the patched boot.img, you won't need to restart.
When done, Magisk should tell that you have 23.0(23000) installed.
Then just use the built-in Install > Direct Install (Recommended) option within Magisk to install it to the current slot.
Do NOT install it to inactive slot. This option only to be used when updating via OTA.
Other option:
Download the Magisk app from the link above, and rename it to magisk.zip then copy it to your phone.
Download TWRP from HERE to your PC and use fastboot flash recovery twrp.img to flash this recovery.
Reboot to recovery. (Might take 2-3 mins to boot first time)
Flash the magisk.zip using recovery.
That's all you should need to be able to root.
I appreciate the help.
I was so hopeful you gave me what I needed, but it didn't work.
So, It wasn't an update issue... it was more of an attempt to downgrade Magisk.
I always OTA the same way as you and it always works.
I also always get Magisk from the official Github page.
What I got excited about was that I wasnt aware there was a working TWRP! So I thought.. THAT will fix it.
I didnt flash it, I just booted from it. I flashed Magisk that way, BUT... still not rooted.
Here is the interesting bit.. when flashing Magisk via TWRP, it detected that my boot.img was already Magisk patched and not stock (Which is right). It's like the boot.img is correctly patched, Magisk just isn't seeing it.
I'd be ok with a full wipe and factory reset at this point, but I'm not even sure that will fix it.
** Edit - I tried manually flashing the latest full OOS downloaded from Oneplus. It didnt help. I finally factory reset and it's working now.
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
ps000000 said:
This is my fav. root method.
[GUIDE] Easiest way to root/magisk Oneplus 8 Pro
This method will not flash any custom recovery or any custom boots. Caution: I don't take any responsibility. Proceed with your own risk and resilience in mind Prerequisites: Oxygen OS 11 (tested with 11, issues reported with 10) and a PC with...
forum.xda-developers.com
Click to expand...
Click to collapse
Agreed, this is a great method. I tried that too before I ended up doing a reset... no good. I somehow broke something with the rom outside of Magisk so that Magisk wouldnt work. Whatever it was, A full wipe fixed it..
Hello, I've done this update on my OP8Pro and forget to use the magisk app to keep my root so I've lost root. I'd like to root it again but i dont have the boot.img patched with magisk to do it; could you guys help me ?
thanks you
It's already been shared in the usual thread.
Thanks you. Its rooted again
Out of curiosity, why bothering with a patched boot image while flashing the Magisk zip works?
For future reference, if you have TWRP or other functional custom recoveries - all you do is flash magisk.zip and you will have temporary root. Afterwards, go into magisk.apk app in your OS and click direct installation for permanent root.