yashsingh1/xdaforums huggingface dataset:
[Magisk] Soooperstar:
When you tried it, did 13_10 work? Also are you using the latest magisk manager apk 5.1.0 in goodwin's folder?

---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------

He said it was fixed in the b1 zip but not for a fresh flash. I haven't had any crashes. Had to flash over 13_10
[Magisk] WyldOne91:
I did them back to back so I'm not sure. As for the apk, I'm using the one pushed by the app itself. I didn't realize there was any difference with the ones in Goodwin's folder. I assumed they were just there for convenience.
[Magisk] Soooperstar:
Make sure 13_10 is working and use his apk
[Magisk] KingJ50:
Have you rebooted since installing b1? I noticed that SafetyNet will pass after the first boot after installing magisk but will fail after subsequent boots.

So that said. I'm also failing SafetyNet with b1. Resetting magiskhide didn't fix the issue.
[Magisk] Soooperstar:
I haven't rebooted but I will try now an report back

Edit: Did 2 reboots and still passing. Also using core only mode fyi
[Magisk] WyldOne91:
I now have no root and failing safetynet. I'm going back to where I was with root at least.
[Magisk] ohioDroid:
I have installed Magisk-v13.3-Pixel-b1 and the MagiskManager-5_1_0.apk from Goodwin, but SafetyNet checks in Core mode still fail for me.
[Magisk] Soooperstar:
Not sure what else to suggest but mine is still passing
[Magisk] Bloodgod:
Ok so I read the instructions a couple of times before installing just to make sure I did things properly, installed over previous magisk versions safety net check still fails. I do not have core only mode checked, but I did turn magisk hide off and on again but did not pass. Last version failed as well. Still rooted but kinda stuck.

Current ROM: PureNexus 7.1.2 2017509-official

Current Kernel: ElementalX p-14

Current build: N2G47O
[Magisk] pcriz:
So flashing the file you are asking about, yourself, would NOT solve the issue of not knowing if it works or not?
[Magisk] MArtyChubbs:
I don't understand what was just written.

To recap: I am asking the thread if someone had tried something before in order to prevent the duplication of effort towards a failure.

All I am looking for.
[Magisk] chazall1:
It is much easier to try new things. Then Report what the outcome is. That is how you learn.
[Magisk] kylepsp:
Anyone running on Android O now we have TWRP support? I've flashed magisk, but it's showing as not installed on the manager, tried clearing data and reflashing
[Magisk] pcriz:
Do you have a custom kernel?
[Magisk] ItWasAllIntended:
This really isn't the place to ask but has anyone get the Xposed Nougat Magisk modules to work on Pixel yet? Either the PurifyOS version of the Blacksoulxx version?
[Magisk] MArtyChubbs:
Oh no he didn't!
[Magisk] taz1458:
Having issues getting this thing to keep root. I flash the b4 file. Have root for a few hours then lose it. I'm wiping data on the manager and everything and the pos won't stay. Any ideas?
[Magisk] MArtyChubbs:
I think you need to have magisk manager not optimized in battery settings
[Magisk] taz1458:
I flashed the 13.4 b2 to try that. So far it looks like it may have worked. Fingers crossed.
[Magisk] Ezrem:
I never set optimization for Magisk Manager and my Pixel was able to keep root for days, but it would occasionally lose root. Guess maybe I was lucky. Definitely trying this for a fix for that occasional loss.
[Magisk] pcriz:
By that logic SuperSU would need to be optimized. I don't lose root intermittently and I never optimize the Magisk app. SU actions are pushed to the su manager in real time when they are requested. That means even if the app is dozed, it would wake to say yes said app is GTG or no it needs to be given permission.
[Magisk] MArtyChubbs:
Hi Buddy, I completely understand where you are coming from, however, SuperSU and MagiskSU are not the same thing.

Furthermore, before I answer, I try and make sure I know what I am talking about. My go-to is documentation.

Like this:

Randomly losing root

Some devices seem to have issues with memory management where the Magisk Manager will not be kept in memory and as a result root management is lost. This can sometimes be fixed by clearing the Manager from memory (swipe it away from recent apps list) and opening it again. Make sure the Manager is removed from any battery optimisation.

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828/page1

Bam!
[Magisk] pcriz:
Few things. Doze in android doesn't "remove things from memory".

SuperSU and Magisk are different, that's obvious. What's the same is they both are subject to the same doze rules in android and both are required to answer SU requests. By the logic of doze killed it, then it should essentially wake back up when the device is moved (while trying to do something that handles root).

Again, I'm not new to Magisk and doze hasn't killed my root ever. But hey it's nothing for him to remove the optimizations and see what happens.

The context is that it's talking about memory managers that actually kill applications. Huge difference, that being that even dozed applications can still provide notifications, still reside in the memory, and are only dozed when the device isn't being used/moving

That being said I've been on magisk since the initial release by Goodwin and never had to undoze a thing and I don't lose root.
[Magisk] Gooch4130:
Just installed magisk 13.3 on a Pixel running 7.1.2 (August update) and everything appears to be good. Noticed an issue, however, when trying to download/install apps (Root Explorer and ES File Explorer for example). The download completes, but the install won't start until I go into magisk manager and check the the box to hide the play store. Oddly, I have to do this each time I want to install something. Does that seem right?

UPDATE: Installed apps are not updating either and the 'certified' status in the Play Store says 'uncertified'. Does that have something to do with this?
[Magisk] MArtyChubbs:
Well said. I read that op back on 12 before I installed magisk. I just did it.

I'm interested to know if that does help anybody if not maybe I just skip that step next time.
[Magisk] Gooch4130:
Just installed magisk 13.3 on a Pixel running 7.1.2 (August update) and everything appears to be good. Noticed an issue, however, when trying to download/install apps (Root Explorer and ES File Explorer for example). The download completes, but the install won't start until I go into magisk manager and check the the box to hide the play store. Oddly, I have to do this each time I want to install something. Does that seem right?

UPDATE: Installed apps are not updating either and the 'certified' status in the Play Store says 'uncertified'. Does that have something to do with this?

UPDATE 2: Had to go into "Magisk Manager"->"Magisk Hide" and select "Package installer (com.google.android.packageinstaller)" to be hidden. Is that expected?

UPDATE 3: Per pcriz's suggestion below - I cleared the data for the app and then the phone showed 'certified'. I was also able to go back and uncheck the 'Package Installer' box from hidden and things are working again. Posting in case someone else hits this.
[Magisk] pcriz:
I mean it doesn't hurt and who knows until the other person responds back with a yay or nay. I am curious as well.

---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------

Try clearing data on the play store. I am rooted with the newest pixel Magisk but my play store is showing certified. I can even download Netflix. I'm using pure Nexus though.
[Magisk] Gooch4130:
That did it. Thank you for the reply!
[Magisk] kylepsp:
No I don't, wasn't aware it was a prerequisite. Are there any available for O?
[Magisk] taz1458:
I have Un optimized magisk to see if that works. Root was gone yet again this morning. ???
[Magisk] pcriz:
Not at the moment
[Magisk] MArtyChubbs:
Thanks for the update
[Magisk] taz1458:
Didn't work. Just got the notification that magisk had closed and used root checker and lost root again. What the hell can honestly be causing this stupid thing.
[Magisk] pcriz:
Use the uninstaller zip, reboot recovery, install zip again
[Magisk] EstiR86:
Reinstall Magisk and make sure your using the latest version
[Magisk] pcriz:
I'd also reinstall the apk and wipe data after flashing the zip again
[Magisk] EstiR86:
Anyone know how to get substratum to stick? I install with no errors, give root, reboot but no changes are observed. I'm on stock 7.1.2 July secruity patch.
[Magisk] pcriz:
Stock or rom?
[Magisk] EstiR86:
Stock ROM
[Magisk] piccit:
You have to use a theme that's compatible with your ROM. Substratum doesn't use root anymore, so this has nothing to do with Magisk

Edit: just saw you said you gave root, what exactly are you trying to do, boot animation or font or something?
[Magisk] EstiR86:
Trying to install Swift Black Theme so I shouldn't give it root premission?
[Magisk] hokiealumnus:
Other than boot animations, Substratum does not need root, assuming whatever ROM you are on has the proper Substratum commits, and any that are close to up to date should.
[Magisk] pcriz:
They are on stock though
[Magisk] hokiealumnus:
OH...missed that, sorry. I'll crawl back in my hole now.

:angel:
[Magisk] EstiR86:
All good does substratum but work with stock?
[Magisk] piccit:
IIRC it uses 'legacy mode' when on stock. Which, IIRC, is going to try to copy the dlls into /system/vendor/overlays

So it's likely the whole 'most apps can't mount /system r/w' issue. You can try manually mounting /system r/w in one of the explorer apps that can do that (I use Root Explorer) and try to apply the overlays again
[Magisk] EstiR86:
Ahhh that probably would of solved it I'm just gonna go and give PureNexus a shot as I've heard ARISE works better there anyways.

---------- Post added at 07:26 PM ---------- Previous post was at 07:11 PM ----------

Just curious to return device to stock so I'm able to flash a rom all I need to is factory reset and flash the magisk uninstaller zip correct?
[Magisk] hokiealumnus:
You don't need to return the device to stock if you're flashing a ROM; just wipe cache, system and data. Then follow the ROM's install instructions (don't forget to flash TWRP after flashing any ROM or you'll lose it!).
[Magisk] krazekid7:
Guys, Android pay works on dp4 with root using suhide lite. Also able to pass safety net
[Magisk] EstiR86:
Interesting wonder if it will work for official O release I guess we'll find out tomorrow.
[Magisk] JakeDHS07:
Should
[Magisk] 640k:
i'm going to be this guy, but there are quite a few pages of back and forth in this thread and no real "clear/official" install instructions on the first post.

can we get OP to update the first post and/or get the ideal set of instructions re-posted with the "best" version?

still running v12 and running the script/command line after each reboot.
[Magisk] pcriz:
Well for one you need to be on the newest build

What's this script you run after each reboot?

After a clean flash (or just not previously rooted):

Boot into twrp (if you just flashed a ROM reboot at least once)

Flash magisk zip (most current from Goodwin_c afh)

Reboot into system

Install magisk apk (most current from Goodwin_c afh)

Wipe data on magisk apk

Enable magisk hide

?????????

Profit
[Magisk] Jdban:
Anyone tested on official O yet?
[Magisk] Soooperstar:
I was wondering the same. Looks like they have the modded twrp and supersu working
[Magisk] pcriz:
But is there a custom kernel??
[Magisk] Pøîñtßlåñk:
Point us into these threads if you don't mind.
[Magisk] pcriz:
Twrp - https://xdaforums.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896

The newest SU should work fine. It's a fast bootable image. No flashable zip yet.
[Magisk] Soooperstar:
Both confirmed working on final release

https://xdaforums.com/showthread.php?t=3651574

https://xdaforums.com/showthread.php?t=3652044
[Magisk] Juzman:
I tried the modded TWRP and booted fine with O final.

Flashed Magisk-v13.4-Pixel-beta2-build1 but have no Magisk installed.
[Magisk] TheUndertaker21:
this needs to update for offiical O since it flashed fine but didn't install
[Magisk] EstiR86:
It has been mentioned the Magisk needs a custom kernel to work so unless there is a custom kernel for O already you won't get Magisk running.
[Magisk] EstiR86:
Also to note official Magisk support will be coming soon read latest update on official Magisk thread ! Until then I think we all owe [MENTION=2461994]goodwin_c[/MENTION] a huge thanks for all his work ! Thanks a lot man!
[Magisk] daddylonglegs:
Is it on your Pixel? If so, did you have to install it in a special manner?
[Magisk] Soooperstar:
That was over a month ago and many versions back. Old post. There's a new version now
[Magisk] daddylonglegs:
Does the newest version work on the Pixel? Or do we need to download a separate special Pixel version still?
[Magisk] Soooperstar:
Of course it does. This thread is for Pixel. I use it everyday
[Magisk] daddylonglegs:
When I did this like 2 months ago there was a separate build of Magisk just to get it to work on the Pixel. I am glad that is not the case any longer!
[Magisk] Soooperstar:
Yea that was before this Pixel thread existed. There should be an official version coming soon being that the developer now has a Pixel, but this one by goodwin works perfectly
[Magisk] abuttino:
That doesn't look like soon. He said he didn't have time
[Magisk] pcriz:
This is the fork you are talking about, thats why its called the Pixel family support and labelled unofficial
[Magisk] daddylonglegs:
Thank you very much!

Sorry if this is a dumb question but it works OK with Oreo 8.0 that was released yesterday right?
[Magisk] pcriz:
For the lazy

---------- Post added at 07:37 AM ---------- Previous post was at 07:36 AM ----------

You need a custom kernel
[Magisk] daddylonglegs:
Thank you. I noticed that after installing EX Kernel Manager I can no longer view any live video streams such as the one from my Ring doorbell or video calling. It does not matter if I use the Facebook Messanger video calling app, or the Duo app. It cuts out immediately.

Does EX Kernel Manager do anything to the "kernels" that are different than the Google ones? Or are they just the Google ones, but "modifiable"? I remember back a few years ago that custom kernels would result in things like people not being able to hear me clearly, crappy audio, bluetooth not working right, stuff like that. Is the EX Kernel for the Pixel that "different" than the one provided by Google? Sorry if this is a really dumb question. I am having trouble explaining what I mean.
[Magisk] EstiR86:
I'm confused by your question but I'll try to answer what I can. From what I know there is not a custom kernel for Android O as of yet and I highly doubt Flar2 would release a kernel this fast knowing how he takes stability to be very important. It sounds like your running the Ex Kernel manager app which is just an app that allows the user to modify aspects of the Kernel, however you have to be rooted for this to work.

Are you sure Kernel manager is the cause of the live stream crashes? I am still running a Custom rom and probably won't flash Oreo until a reliable TWRP is in place and a custom kernel is out for uses such as Magisk.

Custom kernels are what they sound like Custom each kernel is a little different some focus on features while others stability, reliability, and performance. Most of the time kernels are upstreamed versions that are slightly modified for audio enchantments and such goodies. I've never had a custom kernel cause any real problems to my devices actually almost every single kernel has in a way improved battery life or performance! When EX kernel comes it will be ready and be reliable like always but I'm more interested in FrancoKernel because of the magic he does to make idle drain so low!
[Magisk] daddylonglegs:
Thanks so much for the helpful reply! I guess what I am asking is are the custom kernels like the ones found in EX Kernel slightly modified from the ones Google provided for the exact phone? Or is it something where they basically build it from the ground up?

I know my video streaming issue is weird. If I try to receive or place any type of video call, it immediately hangs up on my end. If I try to view my Ring doorbell live-stream, it hardlocks my phone. My wife has the Pixel XL and has none of these problems. I have the Pixel and the only difference is that mine is modded. I can't imagine what it could be.
[Magisk] joemossjr:
I know this is the pixel device forum but the Moto z2 force owners are in the same boat with the a and b partitioning and we are trying to get magisk made boot img and we can only do it without recovery becuase ... Well we don't have one. If anyone can help that would be awesome
[Magisk] pcriz:
I don't think you can flash it right now without recovery
[Magisk] EstiR86:
The kernels are pretty stock like with features added. I would suggest trying a different custom kernel like Kirisakura or Franco Kernel then try again. Also are you on Android O by any chance or are you still on Nougat?
[Magisk] joemossjr:
theres a way to flash now wihtout a recovery building using adb
[Magisk] pcriz:
Care to share?
[Magisk] joemossjr:
It's in the official magisk post how to install without root or twrp
[Magisk] pcriz:
The method for 13.6? Aren't we on 13.4?
[Magisk] joemossjr:
The 13.6 is the beta
[Magisk] pcriz:
Yes I understand that. But if there isn't a 13.6 for the pixel then the installation without twrp method is useless to us and also to the guy asking about the Motorola with the a/b slot layout.

That's if I am understanding the post where the magisk dev says 13.6+ next to the instructions.

Have you installed it without twrp on the pixel?
[Magisk] joemossjr:
No sadly I only have the Moto z2 force to test I'm able to patch the boot image and fastboot boot it and it boots up but magisk doesn't work sadly
[Magisk] pcriz:
Sorry for some reason I thought you were someone else. So no we don't have 13.6 yet on the pixel. We are on a beta of 13.4. So the twrp free method won't work for us I am assuming.
[Magisk] joemossjr:
Dang :( that sucks
[Magisk] Evo_Shift:
Just thought I would let you know I have the Arlo Pro security cameras and I can view them fine with elemental X and whatever the stock settings for the kernel are.
[Magisk] jeremy.wang:
Is it compatible with Android O?
[Magisk] kartikb:
You need a custom kernel with Android O for this to work.. I've switched to SuperSU with SUhide for the time being..

You may want to check it out.
[Magisk] taz1458:
Really doesn't matter what you do with magisk, it refuses to stay rooted. I've tried everything. The Uninstaller, uninstall in the apk, reflashing it all then reinstalling the apk, Clearing data, nothing works.
[Magisk] pcriz:
I really don't think that is the case with everyone. I've ran it since Goodwin's first release until chainfire released su hide lite. There were hiccups in the beginning but was completely stable since 12.

Now I'm not saying you arent having issues. What I'm saying is the files currently offered work.

So just through process of elimination it's not a matter of magisk for the pixel not working.
[Magisk] hokiealumnus:
Another +1. I can't recall ever losing root with Goodwin's magisk, and I've used it all since he first released it.
[Magisk] taz1458:
Well now I'm really baffled. I did nothing but reboot it this time, and the root came back. I think this thing hates me lol.
[Magisk] Soooperstar:
I've had it happen 3 times since the early versions and all it took was a reboot but again that was during months of usage
[Magisk] taz1458:
Mines been about the last 2 weeks. So weird. I'm getting the Note 8 since this phone was a place holder from the Note 7 to the IPhone 7plus that I hated.
[Magisk] EstiR86:
+1
[Magisk] trips555:
Have you tried looking at other apps/tweaks you might have that could screw with it? I'm pretty positive Aggressive Doze in Greenify's settings screws it up, even though regular doze doesn't. I unticked that and my Magisk has been running smooth for like two straight days, after losing root and needing a reboot every few hours.
[Magisk] taz1458:
I had not. I just unchecked aggressive doze. See what it does.
[Magisk] TENN3R:
ElementalX for Oreo is out for Pixel & Pixel XL, if someone feels lucky with magisk can give it a try.
[Magisk] Playe:
Didn't work for me
[Magisk] Veid71:
i am trying to instal 13.4 on 7.1.1 and it goes well ill flash that twrp and the bootsigner and it restarts to a black screen with green text saying ramdump writing to ext4: press vol up+vol down to stop the ramdump process then it trys to boot up after a few seconds and it just keeps going through the cycle until i put it into BL and do a flash-all and boot back into twrp and flash the pure nexus rom.
[Magisk] EstiR86:
Are you flashing a custom kernel? A custom kernel is needed for Magisk if not your going to have boot related issues
[Magisk] Veid71:
Yeah I've been flashing elemental x
[Magisk] EstiR86:
Flash uninstaller zip first, then flash whatever kernel (twice) so flash ex then immediately after that flash ex again, flash magisk, and then flash twrp and bootsigner
[Magisk] Veid71:
still doing the same thing :/
[Magisk] EstiR86:
Hmm try flashing SuperSu then boot and see if that takes you to Pure Nexus if that works then go back to recovery and flash the un supersu zip, uninstaller for Magisk and repeat the steps above.

Edit: I've never tried with ElementalX I use Franco so maybe give that a shot
[Magisk] Veid71:
alright thanks do you have the download links for them?
[Magisk] EstiR86:
SuperSu:

http://www.supersu.com/download

UnSu:

https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page244

Franco Kernel:

https://xdaforums.com/pixel-xl/development/kernel-franco-kernel-r1-31th-october-t3491377/page105

I suggest just trying with Franco Kernel remember to flash kernel twice tho then proceeded with the installation of Magisk if that doesn't work try seeing if you can even boot with root (SuperSu) first then we can try making some progress.
[Magisk] pcriz:
Are you flashing on 7.1.1 and if so what version of elemental are you using.

Also if you are on 7.1.1 did you upgrade your bootloader to 7.1.2 may because that's the only one that needs the bootsigner.
[Magisk] wpbear:
Why flash kernal twice?
[Magisk] Veid71:
yes i am flashing on 7.1.1 and im using 1.15 of elemental and im not sure if my bootloader is upgraded i used to have 7.1.2 but then i switched to 7.1.1 is there a way i can check? and so should i not flash the boot signer?
[Magisk] Veid71:
no booting with supersu doesnt seem to be working either when i boot with su it boots up but it knocks me into the other slot without it so let me make sure im doing the steps right...

first i flash the ex kernal, then i flash pure nexus, then i flash super su-v2.82-201705271822, then i flash twrp and boot
[Magisk] EstiR86:
Yeah these steps should work. Try flashing the ROM then kernel and see if that makes a difference also try different kernels like Franco and Kirisakura.
[Magisk] pcriz:
So if you are on 7.1.1 you shouldn't be flashing 1.15 elemental. Also shouldn't flash the latest Franco kernel.

You also shouldn't be flashing the bootsigner, or rather you don't need to.

All these odds and ends with version numbers makes it super hard to help you. That and simply not reading the op of the files you are downloading.
[Magisk] pcriz:
Kernel version is specific to Android version.
[Magisk] Veid71:
no luck with either magisk or super su :/ i tried kirsaki and the franco one for 7.1.1 doesnt download as a .zip so i cant use it also i looked in the settings under about phone and it still says the kernel version is purenexus even when i do ex it says pure nexus
[Magisk] EstiR86:
Look at what [MENTION=1164081]pcriz[/MENTION] said I think he has you a solution.
[Magisk] veez21:
HEY PIXEL USERS ?[B\]

I'm a module developer (debloater/systemizer).

I'm here to ask if anyone can provide some info about the slot based partitioning. I'm kinda confused on how its structured and want anyone to help me to support this thing on my modules ?

Contact me through PM

/Thanks/
[Magisk] Veid71:
So its because all of these versions are different?