Database Users

PHH's Root Disappeared

Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.

apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me

[Q] Magisk Root

Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?

There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Sent from my VS995 using Tapatalk

mrtruckincowboy said:
There Is no root method for variants that don't have a unlocked bootloader. You would know this if you read the forums before asking
Click to expand...
Click to collapse
So, quite frankly, if you read, another user has it working. Further more, with the TMO variant, I do have an unlocked bootloader. Root application works with magisk, however the APK itself fc's.

I thought cowboys were polite ; )

I misread your post thought you were the typical person asking for a update on root I apologize.
Sent from my VS995 using Tapatalk

Thats what you get for not reading posts Cowboy... Smh...

I have the H918/tmo and I was able to get magisk running with phh's superuser. I'm kinda iffy on magisk-hide, as i had issues with it initially ( random reboots with it enabled). I turned off magisk hide for about a week, then turned it back on last night with no reboots since.. but haven't tested it with apps.
After running the easy recowvery + root script, i got rid of SuperSU. I believe all i did was a Full Unroot in the options, with no changes to the recovery. (I also may have done a format /data when rebooting to recovery again, but i dont recall fully, so take that into consideration if it didnt work at first (followed by the no-verity-opt-encrypt zip).)
After getting rid of SuperSU/su binary, what i remember doing was:
1 ) Flash magisk v9.zip -> reboot to system to make sure it boots, then adb reboot recovery.
2 ) Flash phh's superuser r266-2.zip -> reboot to system
3 ) install magisk manager via apk, and phh's superuser via playstore.
4 ) test out root.

has anyone been able to get Phh's superuser to work on the Sprint v20 / LS997 ?? If so, how? Thanks in advance.

If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.

HiddenKnight said:
Has anyone been able to get magisk to work appropriately? I attempted and the magisk apk kept fc'ing. I read about LG devices needing a boot.img "bump". Is this true or has anyone got it working in their own way?
Click to expand...
Click to collapse
ive got 1 working and 1 in testing that uses magisk and phh.
the phh superuser seems to be casusing the systemui to force close often when in hide mode and the random reboots and loss of service, otherwise it was working fine.
but yeah, just flash version 10.2 on your current rom and see what happens!
btw this was on DEC sec patch, on oct builds i never tried it, but this is latest DEC sofware, didnt even use rootswitch

slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179

remix435 said:
Is this the App you used?
https://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
Click to expand...
Click to collapse
I am using the one from this rom thread;
https://forum.xda-developers.com/v20/development/h819-nrd90m-modded-stock-rom-t3503658
Just follow the directions in the OP and you'll be g2g.

slayerh4x said:
If you can't get this working there is an app called RootSwitch. It can successfully hide root on the V20 with a toggle.
Click to expand...
Click to collapse
Tried RootSwitch w/ SuperSU. Didn't pass SafetyNet if that's what you were referring to.
Tried it again last night. Had the 1st 3 options turned on. Soon as I opened Android Pay my phone hot booted and got stuck on the VZW splash screen. Had to pull the battery. Won't try that again with supersu.

I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access. Now I tried to uninstall supersu threw the app and I got a failed message. I tried going into recovery and flashing the supersu unistaller and that would fail. I tried flash magisk v12.0 and keep getting error message. I got stock in twrp recovery several times and used LGUP and flash either VS99512A KDZ or the VS99513A KDZ. Am not a developer but it seemed as if the boot.img won't take by the magisk zip. Those where my failed attempts for about a week or two. Now on to the success story
Performed Dirty Santa on software version VS99513A. I decide to flash modstock kernaI update v1.1 because it seem to work well with a stock rooted VS995. I flashed busy box in recovery and downloaded the app and also downloaded quick reboot so I could reboot into recovery easier. After reading @poixninja thread on modstock kernal - stocked with goodies he mention flash a boot.img that was patched with magisk. So I but the phone into fastboot mode and flashed his boot.img onto the phone with cmd (command prompt). I think I might have tried to uninstall supersu threw the app and I think it didn't work after flash the boot.img. So I put the phone into recovery mode the to wipe and then to advance wipe and clear dalvik and cache. After that I went to install and flashed the supersu unistaller and it took. After flashing I wipe the cache that twrp ask after most flashes. I then rebooted into recovery to make sure my twrp was not affected because I had and issue with that in previous supersu unistaller attempts. Rebooted ito twrp recovery then rebooted into system. I think whenever I flashed the verzion logo stayed up longer than normal but the phone fully started up. I clicked on supersu and it said no root access. Turned of the phone and did the steps to get to recovery mode. Once in I first wiped dalvik and cache. Then I flashed magisk unistaller and it went threw with no issue. I wiped dalvik and cache then rebooted into recovery. After getting into recovery I rebooted to system.
Sidenote: I recommend after wiping supersu and flashing magisk unistaller. Once you boot up install magisk apk. I didn't install the apk until after I flashed the magisk v12.0 in recovery. I noticed when I reboot the magisk icon was on the phone but when I clicked it it said go to playstore to download. I had the magisk manager apk on my SD card so I just installed it. The install to longer than normal I think it was because I didn't install it prior to flash the zip in recovery. I didn't get a chance to verify it yet.
Once the phone boot and I installed the magisk app manager I open it up and got green checks for installed magisk v12 and properly rooted. I went to setting and turned on enable busy box, magisk hide, and systemless. But when I clicked safetynet I got cts mismatch. Did some research and read on other XDA magisk thread that it maybe because of custom roms, modified kernals and possible supersu somewhere on the system. The only root accessible apps I had installed during this process was busybox and quick reboot. I did notice the first time I ran quick reboot after getting magisk it did give it root access then it did after I opened it again.
I decide to uninstall quick reboot and busy box. I uninstalled both apps. I rebooted into recovery mode the manual way. First thing I did was wipe dalvik and cache. Then I flashed busy box uninstaller. When the flash was running I say in the command lines that it found supersu. Which I thought was odd so I also flashed supersu unistaller. I rebooted into recovery wipe dalvik and cache and flashed uninstall magisk. Then reboot into recovery. I ran busy box uninstaller one more time to see if it would pick up supersu again and the command lines did not mention it. I flashed back magisk v12.0 rebooted into recovery. Then rebooted into system
Opened magisk went to setting to turn on enable busy box, magisk hide and systemless. Check safetnet and failed I found a magisk XDA thread that talks about common issue. It said I had to check magisk core only mode. Once I did that he requested a reboot which I did. Once back up I first cleared in app manager under show system I cleared all data for google play store, google play service for instant app, google play services. I opened magisk clicked safetynet check and I passed it. I went to search for netflix in play store and it pop up I installed it and it working fine so far. I tried logging into snapchat and I got threw.
Hope this maybe help full to anyone having issues
https://forum.xda-developers.com/v20/development/kernel-modstock-kernel-stock-goodies-t3563887 (boot img and modstock v1.1)
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4 (Magisk common issues)

Easier than that...?
sentra10550 said:
I have a VS995 this is how I got my phone to finally take magisk and pass the safetynet check. I'm running software version VS99513A I performed dirty santa to get unlocked bootloader and root access...
...
...Hope this maybe help full to anyone having issues
Click to expand...
Click to collapse
If I may be so bold, I played around with the rooting process on mine (I have a VS995 on 13A, too), and found a much easier (and possibly cleaner?) way to do this. Of course, the way I'm about to suggest would require a full KDZ to stock and a factory reset...
Here's mine:
Follow this thread:
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Note: For noobs: After step 13, it's a bit misleading, because it doesn't boot DIRECTLY into TWRP, but boots to the white-screen "stock" recovery. The trick is to tell it "Yes" to both reset prompts. (It doesn't actually reset your stuff.) After this, it will take you to the TWRP menu.
When you get to step 14E, DO NOT FLASH SuperSU!
Instead, flash the ReStock zip.
After flashing ReStock, follow step 14G, and then flash Magisk 13.3 (latest stable, haven't tested others) from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I tried this out of order a couple of other times and ended up either having Magisk not following through with install, or developing issues installing certain apps. (Either getting a -504 error from Play Store, or having valid APKs reply that they were "corrupt" when directly installing.)
Of course, all of the stereotypical disclaimers apply-- YMMV, and I'm not responsible if you brick your device, yadda yadda...
No offense, intended, sentra10550. While I'm glad you managed to get things working, the directions were a bit convoluted and I hope my humble findings might help yourself, in the future(?), and any others that may have a VS995.
Good luck, everybody!
)O( NeoHiPPy )O(

Think I'll wait until an easier method comes out for the VS995 to run Magisk lol..

I was UNABLE to do full unroot on my V20 from SuperSu settings menu. It would say "uninstallation failed"
I tried running UPDATE-unSU.zip from TWRP and it did not help. Magisk keeps on complaining about modified boot file.
I am unlocking boot loader, trying to flash Magisk in TWRP instead of SuperSu as per DirtyStanta root method instructions.
I will also flash restock 1.3 right after to stop static and vibration issue.
If it works, ill update my post.
---------- Post added 21st February 2018 at 12:28 AM ---------- Previous post was 20th February 2018 at 11:48 PM ----------
Ok i got it working. It was easier then i thought it would be.
These are the steps i did the very first time i got into TWRP after bootloaded unlock process as per DirtySanta rooting instructions.
Entered TWRP
DID NOT format data>yes
Installed Restock1.3 and Magisk.zip
Wipe cache and dalvik. Says Failed to wipe Dalvik (dont know why but what ever)
Reboot.
Result: Asking for unlock password 9 attempts left. So i have to Format Data>Yes
Re-entered TWRP
Format Data>yes
Reboot.
Root works. No SuperSu needed.
Conclusion:
You have to format DATA not for the root to work, but to be able to get into the phone. If there was a way to bypass that, there would be no need to factory reset to root. Root method would not require you to wipe the phone.
How ever, some apps that i use still do not support systemless root. They fail to do their work such as removing system apps. I cant remove any of my system apps for some reasons. I get "failed" messageevery time.
I was told i need modules for Magisk, but i have yet understood what that even means.
Other apps that use root, work fine. Such as AdAway.org

Magisk and S7 edge Int. On nougat

Hello Guys,
I'm a Noob to Magisk. I really don't understand that What is Magisk and What is does? I'm eager to install it. So I'm very new to this. Let me tell I have Galaxy S7 edge (SM-935FD) model on Nougat 7.0 Rooted with Super Su and Twrp newest Version installed. Plus I have also flashed Superstock Kernel on it. As I searched on Xda magisk but I still didn't get it. If anyone can tell me in a Noob friendly way. That would be appreciated. Thanks.

Anybody replying?

SjDU said:
Hello Guys,
I'm a Noob to Magisk. I really don't understand that What is Magisk and What is does? I'm eager to install it. So I'm very new to this. Let me tell I have Galaxy S7 edge (SM-935FD) model on Nougat 7.0 Rooted with Super Su and Twrp newest Version installed. Plus I have also flashed Superstock Kernel on it. As I searched on Xda magisk but I still didn't get it. If anyone can tell me in a Noob friendly way. That would be appreciated. Thanks.
Click to expand...
Click to collapse
Magisk is basically another root manager like supersu, but instead it can be toggled on and off on the go, so that apps that check for root binaries, would work again. But if you don't have such apps installed, then there is no point of installing magisk, because you already have supersu installed.

TheSproker said:
Magisk is basically another root manager like supersu, but instead it can be toggled on and off on the go, so that apps that check for root binaries, would work again. But if you don't have such apps installed, then there is no point of installing magisk, because you already have supersu installed.
Click to expand...
Click to collapse
I want to use Magisk. So what will I have to do?

SjDU said:
I want to use Magisk. So what will I have to do?
Click to expand...
Click to collapse
First uninstall supersu by going into the app and selecting the complete removal of root. Then download phh's superuser and flash Magisk in the recovery and that's it.

Need help with Magisk v12 installation
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.
---------- Post added at 11:51 AM ---------- Previous post was at 11:48 AM ----------
TheSproker said:
First uninstall supersu by going into the app and selecting the complete removal of root. Then download phh's superuser and flash Magisk in the recovery and that's it.
Click to expand...
Click to collapse
It says that phh super user is obselete when directed to the download page.

Sandiramogan said:
Hi guys,
I have been trying to flash Magisk v12 on my S7 edge (SM-G935FD) without super su, in hopes of using Magisk Su but I keep receiving ERROR: 1 in TWRP when it is trying to mount SU.
I am using a stock Rom and have performed a clean wipe in TWRP, but still cannot get Magisk v12 zip to install without the error 1 message. Appreciate if someone can enlighten me on how to over come this issue.
---------- Post added at 11:51 AM ---------- Previous post was at 11:48 AM ----------
It says that phh super user is obselete when directed to the download page.
Click to expand...
Click to collapse
Then try to download it from the Google playstore

magisk 12 has super user incorporated into it.
first make sure that you back up your phone using smart switch as you will be dealing the data on your phone as part of the installation process.
1. you need to make sure that you have flashed a stock and cleaned boot image to your phone.
2. enter TWRP and wipe data
3. while still in TWRP flash the magisk 12 zi[p which you have stored on phone or sd card
4. reboot and magisk and root should be on your phone.
5. reintsall your data only from the back up you made.
total time needed depending on how mich data you have could take up to 20 minutes.

Cosmic Blue said:
magisk 12 has super user incorporated into it.
first make sure that you back up your phone using smart switch as you will be dealing the data on your phone as part of the installation process.
1. you need to make sure that you have flashed a stock and cleaned boot image to your phone.
2. enter TWRP and wipe data
3. while still in TWRP flash the magisk 12 zi[p which you have stored on phone or sd card
4. reboot and magisk and root should be on your phone.
5. reintsall your data only from the back up you made.
total time needed depending on how mich data you have could take up to 20 minutes.
Click to expand...
Click to collapse
Thank you for your reply and step by step instructions. I followed and everything is working flawlessly. I'm now trying to figure out how to fake Knox 0x0 as mentioned in the changelog, so I can use Samsung Pay and other banking services. If you do have any idea, please do share and let me know.
Cheers and have a great weekend.

SuperSU error: SU Binaries occupied

SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165

I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.

evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.

evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
I am also having the same problem...
Now what to do...?

ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks

ashesall said:
Got this error too after installing 2.82. What I did was to Reinstall ("Cleanup to reinstall from Google Play" option in Settings) and then installed the 2.79 apk I have as backup. Got a prompt that SU binaries needed to be updated and so I did. Update was successful and seemed to do the trick since I'm not receiving the error and still have root.
Click to expand...
Click to collapse
No... It doesnt work... Failed to update binaries... And asks to update the app...

yashasvi.malik said:
No... It doesnt work... Failed to update binaries... And asks to update the app...
Click to expand...
Click to collapse
The last SuperSU version I had before updating to 2.82 was 2.79. I was lucky I turned off automatic updates because the next SuperSU versions after 2.79 were buggy based on reviews. I updated to 2.82 because I thought bugs were already ironed out. It was a bad decision because I started having "SU Binaries occupied" error popping up. I solved this by reinstalling the 2.79 apk I had as backup.
Maybe you updated from a different SuperSU version that's why it didn't work. Make sure that you reinstalled the SuperSU apk version you were using before you upgraded to 2.82.
I've been reading the reviews and the most common reply by support is to flash the SuperSU binaries that corresponds to version 2.82. You can try that. Visit the XDA thread of SuperSU for the flashable zip.
If all things fail with SuperSU, you can try phh's Superuser as an alternative.
---------- Post added at 05:55 PM ---------- Previous post was at 05:32 PM ----------
JGene1983 said:
I have staright talk stylo 2 lgl82vl 5.1.1 lollipop think thats issue? I cant really find info on my stylo 2 version.. Rooted phone with kingroot 4.6 and reboots itself and losses root within minutes of completing root. Any help for this rookie tech. Guy...thanks
Click to expand...
Click to collapse
Sorry, I'm not an expert with these kinds of things. However, you can try visiting the XDA thread of SuperSU and ask for help there.
And also, I'll stay away from Kingroot if I were you. Search for "Kingroot malware/adware" on XDA for more information.
You can try 'phh's Superuser' as an alternative. You can also ask help there.

Install SuperSU 2.65 and update binary, then reboot, and update from Play Store, then update binary again (using "normal" option).

evildog1 said:
I had the same problem as well after SuperSU binary update
SuperSU 2.82 no loger have ability to replace Kingoroot and now it says "SU Binaries occupied". Really Chainfire?
SuperSU 2.79 was the best version.
Click to expand...
Click to collapse
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!

lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
this solved for me, thanks a lot!

For me root works, but SuperSU SU Binaries are still "occupied" Device: Huawei y540

for me it helped to:
* install version 2.79
* run it and follow instructions
* update to 2.82
* reboot
* 2.82 works!

delete this please

super su binaries occupied
wptski said:
SuperSU updated yesterday like normal, required updating binaries and I used TRWP. I updated the app with my Titanium Backup. Another app updated today but when I tried to back it up Titanium had lost root. Opened SuperSU and got SU Binaries occupied. Later today, I powered up again, SuperSU and Titanium both had new updates. I thought the problem was reported and fixed but it still does the same thing! :crying: Anybody??
EDIT: A known issue, https://forum.xda-developers.com/ap...6-09-01supersu-v2-78-release-t3452703/page165
Click to expand...
Click to collapse
this worked for me. https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1. I installed the update zip from the sd card

lucasgabmoreno said:
This works for me:
1° Root using Kingoroot
2° Install Supersu
2° Install link2sd
3° open link2sd and found in the list Supersu, press continuolsy (not simple click) and Click "convert to system app"
4° Remove Kingoroot supersu and Kingoroot
5° Reset device
6° Open Supersu and apply binaires!
Click to expand...
Click to collapse
do we need to unroot the device for this first?????

akshayrrrb said:
do we need to unroot the device for this first?????
Click to expand...
Click to collapse
No.
You need to root your mobile first. Kingroot works for me.

[Mini Guide] How to root 8.1

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.

Our phones came with a USB a - c adapter in the box... Unless you bought it used or lose it... You shouldn't need to buy one unless you lose it

two_cents said:
Our phones came with a USB a - c adapter in the box... Unless you bought it used or lose it... You shouldn't need to buy one unless you lose it
Click to expand...
Click to collapse
Lol, you are right. Forgot all about that. Now I have two.

Fyi, just took the ota to Android 8.1 beta on my stock Pixel and Magisk 14.3 survived. Now have 8.1 rooted and all my modules up and running:laugh::good
Sent from my Google Pixel using XDA Labs

Guys I just bought a new pixel which turned out to be Verizon, anyway I'm just wondering if 8.1 has any major bugs or bugs at all ? Since the bootloader is looked and I will not be able to flash factory images if anything goes wrong with this beta.. help appreciated.

Alaadragonfire said:
Guys I just bought a new pixel which turned out to be Verizon, anyway I'm just wondering if 8.1 has any major bugs or bugs at all ? Since the bootloader is looked and I will not be able to flash factory images if anything goes wrong with this beta.. help appreciated.
Click to expand...
Click to collapse
I seems rock solid to me, and not seeing any major complaints.

Before I update can anyone confirm if ARISE will run on this?

quinejh said:
Before I update can anyone confirm if ARISE will run on this?
Click to expand...
Click to collapse
NVM I figured it out!! Lol

What i did to root the 8.1 Dev Preview was
1. As i didn't get the OTA Notification, i used the factory image, deleted the -w command
2. flashed the Factory Image
3. done, reboot back to bootloader
4. boot into the official twrp using the fastboot boot command
5. adb sideload magisk
6. Profit?
Well still can't flash anything but it's better to have root, and my previously installed modules are still there as well.

mflow said:
What i did to root the 8.1 Dev Preview was
1. As i didn't get the OTA Notification, i used the factory image, deleted the -w command
2. flashed the Factory Image
3. done, reboot back to bootloader
4. boot into the official twrp using the fastboot boot command
5. adb sideload magisk
6. Profit?
Well still can't flash anything but it's better to have root, and my previously installed modules are still there as well.
Click to expand...
Click to collapse
What version of Magisk are you using? I'm on 14.0 rather than 14.3.

ss4rob said:
What version of Magisk are you using? I'm on 14.0 rather than 14.3.
Click to expand...
Click to collapse
i'm on 14.3 now, i haven't tried 14.0 yet but i got problems with 14.0 on Android 8.0, so i moved to the beta channel.

Black crush
Would anyone be willing to do a test for me?
Can you restore the stock boot image, boot to system then look at the top right corner of this wallpaper with brightness on high, and in a dim room. You should see banding like the middle phone in this picture.
Then root with SR5-SuperSU-v2.82-SR5-20171001224502.zip and look at the same wallpaper. Let me know if the banding is gone and the transition is as smooth as the right phone in the picture.
You have to do the steps exactly as laid out, though. Having a modified boot image before flashing SuperSU does not produce this result, and neither does being on 8.0 or 7.1.2. It only happened in 8.1, and only after I flashed this SuperSU over the stock boot image...Magisk did not do the same thing.

Will it be necessary to wipe my phone or flash with -w command?
I have a card reader which is type c port. But I dirty flash SuperSU zips using different TWRP images. One is TWRP 3.1.1-0 from this forum, and another one is 3.2.0 from TWRP official website. SuperSU zips are 2.8 stable and 2.82 RC5. Any zip installed by TWRP 3.2.0 was failed, stable on 3.1.1-0 shows successful but not getting root after boot into system, RC5 shows patching sepolicy failed and gets the same result after boot.
I don't want to wipe actually, because I have lot of important data especially game data on it. It's easy to copy and paste personal files but since I can't use Titanium Backup I hate getting clean wipe.
Should I get a Magisk for completeing this one?

bbs3223474 said:
Will it be necessary to wipe my phone or flash with -w command?
I have a card reader which is type c port. But I dirty flash SuperSU zips using different TWRP images. One is TWRP 3.1.1-0 from this forum, and another one is 3.2.0 from TWRP official website. SuperSU zips are 2.8 stable and 2.82 RC5. Any zip installed by TWRP 3.2.0 was failed, stable on 3.1.1-0 shows successful but not getting root after boot into system, RC5 shows patching sepolicy failed and gets the same result after boot.
I don't want to wipe actually, because I have lot of important data especially game data on it. It's easy to copy and paste personal files but since I can't use Titanium Backup I hate getting clean wipe.
Should I get a Magisk for completeing this one?
Click to expand...
Click to collapse
The sepolicy abort is happening to others. I don't think keeping the -w in place is going to help.
https://forum.xda-developers.com/pixel/how-to/platform-tools-windows-zip-12-5-2017-t3715120/page2
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101

sliding_billy said:
The sepolicy abort is happening to others. I don't think keeping the -w in place is going to help.
https://forum.xda-developers.com/pixel/how-to/platform-tools-windows-zip-12-5-2017-t3715120/page2
https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page101
Click to expand...
Click to collapse
Yeah, and after boot I even don't got any supersu app, manually install from play store and it will tell me my phone isn't rooted
---------- Post added at 03:27 PM ---------- Previous post was at 03:07 PM ----------
Finally, I've successfully rooted by following steps from here: https://forum.xda-developers.com/pixel-xl/how-to/how-to-root-android-8-1-devpreview-1-t3696278
But notice we don't have to keep -w command to do a clean wipe, just boot into TWRP and flash TWRP installer, then flash magisk it will be done.
Shortcoming is I cannot use SuperSU anymore instead of Magisk, but it also doing things great.

I used Magisk 14.5 (1456) to root the Pixel with no issues. I left SuperSU on the XL, and might put it back on the Pixel when the issue is resolved.
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
bbs3223474 said:
Yeah, and after boot I even don't got any supersu app, manually install from play store and it will tell me my phone isn't rooted
---------- Post added at 03:27 PM ---------- Previous post was at 03:07 PM ----------
Finally, I've successfully rooted by following steps from here: https://forum.xda-developers.com/pixel-xl/how-to/how-to-root-android-8-1-devpreview-1-t3696278
But notice we don't have to keep -w command to do a clean wipe, just boot into TWRP and flash TWRP installer, then flash magisk it will be done.
Shortcoming is I cannot use SuperSU anymore instead of Magisk, but it also doing things great.
Click to expand...
Click to collapse
Try Magisk.

I've successfully rooted 8.1 by following steps:
1. boot into TWRP 3.1.1-1
2. install the latest Magisk 14.5 zip from external storage (DOK)
without wipe and/or installing twrp installer

Really wish we could get SuperSU to work. Rooting with Magisk doesn't allow me to use Titanium backup to get rid of Google bloat. Is there some other way to achieve this using Magisk? My understanding is that rooting through Magisk will not allow one to modify the System partition in any way?

pavanmaverick said:
Really wish we could get SuperSU to work. Rooting with Magisk doesn't allow me to use Titanium backup to get rid of Google bloat. Is there some other way to achieve this using Magisk? My understanding is that rooting through Magisk will not allow one to modify the System partition in any way?
Click to expand...
Click to collapse
I removed approximately 500 MB of bloat via Titanium Backup. I'm rooted with Magisk 14.5. Flashed Magisk 14.5 via TWRP using usb-otg. No issues except the contacts sync issue.

phaino00 said:
I removed approximately 500 MB of bloat via Titanium Backup. I'm rooted with Magisk 14.5. Flashed Magisk 14.5 via TWRP using usb-otg. No issues except the contacts sync issue.
Click to expand...
Click to collapse
Huh! It didn't work for me when I tried it. It seemed to uninstall, but on rebooting, all the apps were still there. Is that not the case for you? Also, do you have a list of the apps you uninstalled?
Thanks.