Database Users

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.

Switch to Magisk from Super SU

Hey guys,
I apologize in advance if this is somewhere on the forum (I coukdn't find anything on it.)
So last evening I decided to do the fllowing: unlock, install twrp, root and install a custom rom. I'm comeing from a Note 3 so just getting familar with everything for Nexus.
I completed the unlock, twrp install and root (supersu) with the nexus root toolkit and made a backup as well (not through twrp), and flashed the latest pure nexus rom (stock kernal).
I would like to switch over to magisk so I can get the benefits of using it. How would I go about doing so ?
Thanks !

rich6619 said:
Hey guys,
I apologize in advance if this is somewhere on the forum (I coukdn't find anything on it.)
So last evening I decided to do the fllowing: unlock, install twrp, root and install a custom rom. I'm comeing from a Note 3 so just getting familar with everything for Nexus.
I completed the unlock, twrp install and root (supersu) with the nexus root toolkit and made a backup as well (not through twrp), and flashed the latest pure nexus rom (stock kernal).
I would like to switch over to magisk so I can get the benefits of using it. How would I go about doing so ?
Thanks !
Click to expand...
Click to collapse
If you want magisk then dirty flash your rom to get rid of magisk. After that flash the magisk zip from recovery then reboot and go to play store to update app. Why do you want magisk btw? I used it but drooped it for supersu as it made the splash screen (boot logo that said Google) stay for a while making boot time take a long time.

Ok so if I did the following would I be in the clear:
Full Wipe
Flash rom
Gapps
Elementalx kernal (want to try this kernal)
Magisk 12.0
Reboot
Install magisk manager
I'd like to have magisk to hide root, for things like netflix.
Also would it make any sense to run unsu while flashing everything else ?

rich6619 said:
Ok so if I did the following would I be in the clear:
Full Wipe
Flash rom
Gapps
Elementalx kernal (want to try this kernal)
Magisk 12.0
Reboot
Install magisk manager
I'd like to have magisk to hide root, for things like netflix.
Also would it make any sense to run unsu while flashing everything else ?
Click to expand...
Click to collapse
No need to flash unsu. If Netflix is the only reason you are using magisk then you could just use apkmirror. Also, I heard that the app detects unlocked bootloaders. You should be good to wipe the rom and flash all the stuff you said.

I'll look into apkmirror. Forgot to mentioned I'd like to used android pay as well. Can apkmirror help with that ?

rich6619 said:
I'll look into apkmirror. Forgot to mentioned I'd like to used android pay as well. Can apkmirror help with that ?
Click to expand...
Click to collapse
If you want android pay then you need magisk and need to hide magisk from it aswell as using the hide root settings. You also need to pass the SafetyNet check if you want to use android pay.

Ok thanks. So I will do everything I mentioned in the list as well as set magisk to hide in magisk manager settings ?

rich6619 said:
Ok thanks. So I will do everything I mentioned in the list as well as set magisk to hide in magisk manager settings ?
Click to expand...
Click to collapse
Yes, make sure to run a SafetyNet check.

Will do. Thanks for all the help !

rich6619 said:
Will do. Thanks for all the help !
Click to expand...
Click to collapse
You're welcome, hopefully all goes well?.
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
rich6619 said:
Will do. Thanks for all the help !
Click to expand...
Click to collapse
Also, make sure to check out my thread for better idle drain by blocking wakelocks if you haven't already seen it. I've built a version for pure nexus.
https://forum.xda-developers.com/nexus-6p/general/taking-wakeblock-requests-t3583397

I will for sure check it out. Thanks again !

DEVILOPS 007 said:
You're welcome, hopefully all goes well.
---------- Post added at 09:33 PM ---------- Previous post was at 09:32 PM ----------
Also, make sure to check out my thread for better idle drain by blocking wakelocks if you haven't already seen it. I've built a version for pure nexus.
https://forum.xda-developers.com/nexus-6p/general/taking-wakeblock-requests-t3583397
Click to expand...
Click to collapse
So just an update. Did the following :
flashed
Rom
Gapps
Magisk
ElementalX Kernal
Reboot
Installed Magisk Manager, enabled magisk hide and systemless host (for adaway) and rebooted. Safetynet passes in magisk manager. Went to play store, checked settings device certification and it's certified. Searched netflix, still not available. I'm guessing this has to do with the bootloader being unlocked ? Is there a way around this or will I have to just download the latest apk from apk mirror ?
Going to test the phone out for a few days to see what battery life is like with elementalx (I was averaging around 4.5 hrs ost with stock). If I don't get any better I will def test out your wakeblock.

I would like to hijack this thread a little bit as it is on the same topic as well with slight differences, sorry!
I got a stock 6P with unlocked bootloader and rooted with systemless SuperSU. Fiddled around with Magisk manager before, it will fail SafetyNet check.
How do I switch to phh superuser and using magisk? Will this pass SafetyNet check? The bootloader will still be unlocked....
My main intent is to be able to use Android Pay.

This thread is right up my alley. I just got a Nexus 6 ( XT1103 ) unlocked bootloader, rooted using a Windows toolkit (don't remember the name) and have twrp installed. I read about Magisk after trying to use Android pay without any luck. I would like to use Android pay and believe Magisk would let me be able to do so with still having use of root apps.
Is it possible to go from root to Magisk without loosing my data?

how to keep magisk from uninstalling during a reboot!!!!!!???!!!!!!
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM if also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know

[Guide] Stock 8.0.0 with root and SafetyNet OK (Android Pay working)

Hi all,
With the activation of Android Pay in Canada, I was looking for a solution that pass the safety net with open bootloader, root, and modified host file. The information about was very partial at best, so I thought writing a guide is a good idea. Here we go:
1) Download all the needed files:
Official factory image: https://developers.google.com/android/images#marlin
TWRP boot image: https://dl.twrp.me/marlin/
TWRP install zip (on the phone): https://dl.twrp.me/marlin/
Official Magisk Uninstaller: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Official Magisk Beta v14.3 version for Pixel: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[*]Last version of ElementalX kernel: http://elementalx.org/devices/pixel/ [or any patched kernel for verified boot, See post #45]
Last beta version of Magisk Manager: http://www.apkmirror.com/apk/topjohnwu/magisk-manager// or on the XDA Thread
2) Install last factory image
Unzip the factory image
Edit flash-all.bat or flash-all.sh (Mac, Linux), and remove the "-w" on the last line
Reboot into bootloader: adb reboot bootloader
Flash factory image: flash-all.bat or flash-all.sh
3) Install TWRP
Boot into recovery: fastboot boot twrp-3.1.1-1-fastboot-marlin
In TWRP, flash TWRP twrp-pixel-installer-marlin-3.1.1-1.zip
Reboot into TWRP
4) If coming from prior version of Magisk, flash Magisk-uninstaller-20170928.zip
*) If you want, flash a compatible custom kernel, like ElementalX-P-2.02.zip
5) Flash Magisk into TWRP: Magisk-v14.3(1437).zip
6) Reboot into system (and tap on Do Not Install)
7) Install Magisk Manager if missing: com.topjohnwu.magisk.apk
8) In Magisk Manager settings, enable Magisk Hide, and Systemless Hosts
9) Reboot
10) In Magisk Manager, in Magisk Hide, select your bank app, Play Store, and GSF (Android Pay should be already selected).
11) Reboot
Here we go, you should be able to add your card in Android Pay, use AdAway and download Netflix.
I did not make a factory reset.
Works with 8.0.0 (OPR3.170623.008, Oct 2017) and latest October safetynet
Also works with Pure Nexus ROM
Enjoy!

You don't need the April factory image. Use Chainfire's bootsigner.

Cares said:
You don't need the April factory image. Use Chainfire's bootsigner.
Click to expand...
Click to collapse
This. Stop with the "use the old bootloader" stuff. Use the boot signer. You need it with ElementalX anyway, at least until it's incorporated into his kernel process (it might be already; I haven't looked in a few weeks)
---------- Post added at 02:13 PM ---------- Previous post was at 02:13 PM ----------
firewave said:
Hi all,
With the activation of Android Pay in Canada, I was looking for a solution that pass the safety net with open bootloader, root, and modified host file. The information about was very partial at best, so I thought writing a guide is a good idea. Here we go:
1) Download all the needed files:
Click to expand...
Click to collapse
Do not directly link to files. Link to file sources, such as the ElementalX thread for example.

Cares said:
You don't need the April factory image. Use Chainfire's bootsigner.
Click to expand...
Click to collapse
It's why I put "or sign your boot partition".

khaytsus said:
Do not directly link to files. Link to file sources, such as the ElementalX thread for example.
Click to expand...
Click to collapse
You're right. It should be better now.

Not a big deal for me, however Magisk Hide and Systemless hosts options are missing.

Oh, and apk mirrors? Why? There is a link in the Magisk thead to the manager.. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Do you need to unlock your bootloader before following these instructions? Also will it wipe my (currently stock) device?

Hello,
May be a bit OT but wondering if you are having any issues losing root or passing SaftyNet on June patch and reboots? I assume if Android Pay is working you show certified for PlayStore? I so want to move over after the last SU binary thing...but need reliable root.
Cheers & thanks!

planetgong said:
Do you need to unlock your bootloader before following these instructions? Also will it wipe my (currently stock) device?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is required for this process, and unlocking the bootloader wipes the device.

jschill31 said:
Hello,
May be a bit OT but wondering if you are having any issues losing root or passing SaftyNet on June patch and reboots? I assume if Android Pay is working you show certified for PlayStore? I so want to move over after the last SU binary thing...but need reliable root.
Cheers & thanks!
Click to expand...
Click to collapse
Do you have busy box enabled?

pcriz said:
Do you have busy box enabled?
Click to expand...
Click to collapse
No on BB, my Nexus 6 would just lose root even with core enabled on V12. Had to go back to 11.4 for reliable root. I am more curious as to members results on the modified v12 on our Pixel's...that is my DD. I am still using root 2.79 and April patch for reliability.
Cheers
Sent from my Pixel XL using Tapatalk

jschill31 said:
No on BB, my Nexus 6 would just lose root even with core enabled on V12. Had to go back to 11.4 for reliable root. I am more curious as to members results on the modified v12 on our Pixel's...that is my DD. I am still using root 2.79 and April patch for reliability.
Cheers
Click to expand...
Click to collapse
I'm on 12 for the pixel. Only magisk and it's been stable for me

khaytsus said:
This. Stop with the "use the old bootloader" stuff. Use the boot signer. You need it with ElementalX anyway, at least until it's incorporated into his kernel process (it might be already; I haven't looked in a few weeks)
---------- Post added at 02:13 PM ---------- Previous post was at 02:13 PM ----------
Do not directly link to files. Link to file sources, such as the ElementalX thread for example.
Click to expand...
Click to collapse
Well, I used the boot signer, but when on the newer bootloaders and boot signer I cannot ever restore a backup. It always gets stuck with an error, went back to april and backups work flawlessly

HI, thanks for putting this together.
I followed the steps to the tee, and I'm failing to get Android pay to work. In Magisk v12.0 when I launch the manager and tap to start SafetyNet check I am getting the following error "SafetyNet Failed: CTS profile mismatch".
Any suggestions? I know you just gathered this information and put it all together here but thought I'd give ya a shout and see.
Thanks again!

pcriz said:
I'm on 12 for the pixel. Only magisk and it's been stable for me
Click to expand...
Click to collapse
Hello, are you on April or the new June patch and what kernel?
Thanks

ko0ky said:
HI, thanks for putting this together.
I followed the steps to the tee, and I'm failing to get Android pay to work. In Magisk v12.0 when I launch the manager and tap to start SafetyNet check I am getting the following error "SafetyNet Failed: CTS profile mismatch".
Any suggestions? I know you just gathered this information and put it all together here but thought I'd give ya a shout and see.
Thanks again!
Click to expand...
Click to collapse
Did you turn on magisk hide in the settings.
---------- Post added at 06:00 AM ---------- Previous post was at 05:59 AM ----------
jschill31 said:
Hello, are you on April or the new June patch and what kernel?
Thanks
Click to expand...
Click to collapse
April bootloader

I'm using June stock btw. (Att user not that it matters but I grabbed the correct ROM).
Yes, I enabled magisk hide. Android pay was already selected like you said, I found Google play and checked marked that. Rebooted.
I downloaded root checker and blocked it using magisk hide and hide does appear to be working. Still having issues with safetynet . Looks like others too, I tried a few things like disabling USB debugging, installer busy box, Several reboots. Nodda.
I'm old school custom ROM installer but don't mess much with kernels. How do I know if the kernel is installed correctly? I haven't seen anything after the initial install. Seems when I have in the past I had a way of cusomtizing it. Feel like that might be my problem I can try to reflash it. But looked good during install.

ko0ky said:
I downloaded root checker and blocked it using magisk hide and hide does appear to be working. Still having issues with safetynet . Looks like others too, I tried a few things like disabling USB debugging, installer busy box, Several reboots. Nodda.
I'm old school custom ROM installer but don't mess much with kernels. How do I know if the kernel is installed correctly? I haven't seen anything after the initial install. Seems when I have in the past I had a way of cusomtizing it. Feel like that might be my problem I can try to reflash it. But looked good during install.
Click to expand...
Click to collapse
Hello,
This was one of the issues I had with V12 on my N6. Only difference was both root & SaftyNet were hit or miss(binding Busy Box can cause root issues). As far as the kernel goes I believe the stock kernel will not work so you would need to flash Elemental or other custom. If you did do this, you can try clearing cache in TWRP then reboot and check SaftyNet again.
Cheers

followed the steps exactly (coming from stock, unrooted june update) and after the final reboot into system, i check Magisk Manager and it says magisk is not installed.
edit ran through again, but did not flash twrp again after flashing elementalx, and that did the trick. also don't think boot signer is needed on the latest 1.12 elementalX, it said it was already patched.

[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.

how to root android p

Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version

Ss

joeeboogz said:
Ss
Click to expand...
Click to collapse
Too late , topjohnwu released magisk v16.1 here https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 Magisk manager isn't flashing for some reason so you have to go into the actual file path inside the zip. /common/magisk.apk and install it manually. The module devs need to update their code, but mine should still work.

Just noticed well If u need apk still it's in my drive along with zip

How do access your drive? I tried to go the Magisk route and it hung on the Google boot screen with the loading bar and eventually rebooted itself

can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....

Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
I did the same thing. I couldn't get it to boot back to my phone but I could boot back into TWRP. So I just wiped then restored a backup I had. Try that. Or worse case scenario just boot to bootloader and flash the factory.img again. That should over write anything you have on there now and allow you to boot successfully.

Alekos said:
can someone just provide the few steps in installing latest magisk?
I booted, then flashed latest twrp-3.2.1-2-marlin.img (making sure no security on phone)
then flashed latest magisk 1610
and didn't boot
now I'm stuck....
Click to expand...
Click to collapse
This may be a little late, but go back into twrp and flash the magisk uninstaller located in the official forum. Then reboot. Then reinstall magisk again

This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?

petiolarissean said:
This so simple even newbie like me did it.
Flash 16.1 magisk threw twrp and reboot.Use official Magisk.That easy!I was rooted!
---------- Post added at 01:27 PM ---------- Previous post was at 01:23 PM ----------
I was able to install xposed Oreo and read as following
Android P 8.1 SDK 27 so rebooted but stuck on G logo updating,Any ideas get around it.By theory should work correct?
Click to expand...
Click to collapse
You need to use Xposed for P, which isn't even the roadmap I'm sure lol

If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?

x31234 said:
If I flash to Android P would j be able to root my pixel 2 xl even if it's a Verizon varient?
Click to expand...
Click to collapse
No.

are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*

AlPoo said:
are we fastboot flashing twrp after the beta OTA, or should that custom recovery still be intact?
loading magisk using the manager, or SU, or what have you?
finally, list of the files i should have on hand if things go wrong? have the may image if i need to re load that. ill try to find the P-DP2 image available as well, but I'm not sure of all the root files I'll need.
*yes i could wait for a comprehensive guide, but im here in the meantime*
Click to expand...
Click to collapse
Also waiting for this. Just searched for it but it seems the full image files are not online yet. And I don't know if twrp or the ability to root will still be there if I just uninstall magisk via the uninstaller zip in twrp, and then install the OTA from today?
EDIT:
fastboot the full dp2 image
do set-up process (don't set a PIN)
fastboot twrp 3.2.1.2 img
install twrp 3.2.1.2 zip
reboot recovery
install magisk 16.4 (16.0 won't work)
done
Tested with adaway and it works fine. I expected it to be harder to be honest but I'll take it.

joeeboogz said:
Simple quick guide to rooting Android p
Download both files from my drive
Go to twrp and flash zip and reboot. (Here's the pain in the butt part)
When u get to boot animation it will freeze
After like 2 minutes hold volume down and power to reboot to bootloader
Reboot. I personally turn off then manually turn device back on by holding power button.
When device starts back up install apk as it won't show after flashing zip.
For now su hide don't work App is 5.6.2 the latest version
Click to expand...
Click to collapse
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.

Jerreth said:
i simply booted to twrp 3.2.0.0, installed twrp 3.2.1-2 from a usb otg as 3.2.0.0 wont decrypt, rebooted to twrp, flashed magisk 16.4 and booted android and was rooted.
Click to expand...
Click to collapse
I did the same but booted to 3.2.1-2 and it worked as well

I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot

madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
sometimes it takes a second or more reboots to get into the OS.

madsurgeon said:
I must be doing something wrong, DP2 just refuses to boot after flashing Magisk 16.4, keep having to flash stock boot.img to get it to boot
Click to expand...
Click to collapse
Same here

Try flashing boot.img to both slots and redo the process
Sent from my Pixel XL using Tapatalk