Develop Bugs

Magisk on Nexus 5x

Is anyone using magisk and have Android pay working with root on the 5x ? I've been looking for a thread and can't find how to do it.
Unlock bootloader
Flash stock image
Flash TWRP
Reboot
Download magisk Manager and zip
Reboot ?
Will root apps work now with Android pay?

mikeprius said:
Is anyone using magisk and have Android pay working with root on the 5x ? I've been looking for a thread and can't find how to do it.
Unlock bootloader
Flash stock image
Flash TWRP
Reboot
Download magisk Manager and zip
Reboot ?
Will root apps work now with Android pay?
Click to expand...
Click to collapse
Make sure Magisk hide is on in magisk manager and that it passes the safety net check.

Keithn said:
Make sure Magisk hide is on in magisk manager and that it passes the safety net check.
Click to expand...
Click to collapse
Do I need to flash SU or just magisk

Got it working. Shows Superuser PHH's not the SU by chainfire. Some apps are not working as well with superuser vs SU, but at least everything seems to be working. Every now and then Magisk Manager bug and it shows loss of root. I'll try Android pay sometime today if I can

Could you make a quick guide on how you got magisk installed correctly?
I had some trouble when i tried it after updating to 7.1.2 yesterday and ended up flashing supersu instead. thx
mikeprius said:
Got it working. Shows Superuser PHH's not the SU by chainfire. Some apps are not working as well with superuser vs SU, but at least everything seems to be working. Every now and then Magisk Manager bug and it shows loss of root. I'll try Android pay sometime today if I can
Click to expand...
Click to collapse

mikeprius said:
Do I need to flash SU or just magisk
Click to expand...
Click to collapse
Magisk zip include SU binary (MagiskSU)
---------- Post added at 02:12 PM ---------- Previous post was at 02:09 PM ----------
robotzki said:
Could you make a quick guide on how you got magisk installed correctly?
I had some trouble when i tried it after updating to 7.1.2 yesterday and ended up flashing supersu instead. thx
Click to expand...
Click to collapse
If you have custom kernel, flash the stock one or that came with the Rom from recovery. Then flash Magisk 12 zip file from Magisk Thread and flash it via recovery. Then reboot and download Magisk manager ....

Is there any reason why Magisk wouldn't work with a custom jkernel? I've installed Magisk on top of pure nexus ROM with ElementalX kernel without issues before.

I'm running SAOSP with Magisk and Franco Kernel and I have root and Android Pay works. That's all I flashed. It had a hard time passing Safety Net when SuperSU was installed. So just flash Magisk without SuperSU. And I guess Android Pay can detect if you have an unlocked bootloader so Franco Kernel is used because it hides that.

I tried Android Pay twice. First time didn't go through, said on the vending machine failed. Second time worked. I checked Android Pay and see 2 charges, does the one that didn't go through just drop off eventually ? Also both charges are much higher than what the actual price was, but I assume this is just a temp charge.
I have elemental X kernel. Works fine. I decided not to mess with SU. My other apps work, plus I've tried asking Chainfire before questions about his apps he's made and he never responded. Not cool, I did buy his apps too, not just freebies.

mikeprius said:
I tried Android Pay twice. First time didn't go through, said on the vending machine failed. Second time worked. I checked Android Pay and see 2 charges, does the one that didn't go through just drop off eventually ? Also both charges are much higher than what the actual price was, but I assume this is just a temp charge.
I have elemental X kernel. Works fine. I decided not to mess with SU. My other apps work, plus I've tried asking Chainfire before questions about his apps he's made and he never responded. Not cool, I did buy his apps too, not just freebies.
Click to expand...
Click to collapse
All of my Android Pay charges initially show up as a $1.00 pending charge. After a while, they post as transactions for the full value of the purchase.

Lost Root

I was using SR3-SuperSU-v2.79 and flashed SuperSU v2.82 but
phone wouldnt boot up , so I reflashed SR3-SuperSU-v2.79 and
phone now boots ok but I dont have root,
I'm using TWRP blu-spark 3.1.0 v26

Petesky said:
I was using SR3-SuperSU-v2.79 and flashed SuperSU v2.82 but
phone wouldnt boot up , so I reflashed SR3-SuperSU-v2.79 and
phone now boots ok but I dont have root,
I'm using TWRP blu-spark 3.1.0 v26
Click to expand...
Click to collapse
Flash your rom then supersu, Magisk is also a nice option.

Puddi_Puddin said:
Flash your rom then supersu, Magisk is also a nice option.
Click to expand...
Click to collapse
I thought I might have to do that , is there a link to the latest SuperSU that works
on oneplus 3

Petesky said:
I thought I might have to do that , is there a link to the latest SuperSU that works
on oneplus 3
Click to expand...
Click to collapse
Well you already have the version number.. Not too hard to search is it?
http://lmgtfy.com/?iie=1&q=latest+stable+supersu

Well that was clever
I already did that and tried 2 that didnt work ,
SuperSU282 and SuperSU-v2.82-SYSTEMMODE , I asked for one that worked on the oneplus 3,
But done a fresh install of 4.1.3 , flashed SR3-SuperSU-v2.79 again and its working good, updated binaries and no DM_verity error

Petesky said:
Well that was clever
I already did that and tried 2 that didnt work ,
SuperSU282 and SuperSU-v2.82-SYSTEMMODE , I asked for one that worked on the oneplus 3,
But done a fresh install of 4.1.3 , flashed SR3-SuperSU-v2.79 again and its working good, updated binaries and no DM_verity error
Click to expand...
Click to collapse
Well there is no Supersu that specially works for the Oneplus 3. That is why I always recommend to try things yourself. Take a backup of system and boot and you basically can keep trying things without risking that your phone doesn't boot or you loose data.

Good point

just update the 2.79 via playstore to 2.82

Magisk and Magisk Modules

I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??

blake .l said:
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
Click to expand...
Click to collapse
I had a similar problem. It took multiple reinstalls of magisk to get it working, hang in there you'll get it working. That's just one of the issues with how this phone handles many different things. T-Mobile has had to issue updates to fix updates and that has potential to turn people away from an otherwise great piece of hardware. Hang in there you'll figure this phone out.
Sent from my Moto Z (2) using XDA Labs

blake .l said:
I have Magisk installed and decided to try out some of the modules for it but could never get them to update it said on all that they would update on next reboot, well after several reboots nothing. I clicked on the little garbage can to delete and they wouldn't delete?? I ended up having to uninstall magisk to get rid of them and had to reinstall magisk to get root back.. Any one else have any problems with the modules??
Click to expand...
Click to collapse
Out of curiosity, did you go through the full TWRP installation, or just use it to boot and install Magisk?

dismembered3po said:
Out of curiosity, did you go through the full TWRP installation, or just use it to boot and install Magisk?
Click to expand...
Click to collapse
Did the full TWRP install them installed Magisk

Anyone get Viper4Android to Work on Q?

Before I go back to 9.0.0, i figured i would ask....
Anyone get Viper4Android to install properly on Q?
I tried the latest Viper Magisk Module v1.4.2 i think... Magisk completed the installation but after reboot, Viper is requiring Drivers to be installed. So i install the Drivers, which took longer then normal, reboot and BAM! Viper needs to install Drivers on your device.
So Q doesnt seem to wanna play well with the Viper drivers.
And i tried installing Busybox for ****s and giggles and install fails in Magisk....
Thanks in advance for any assistance and/or **** head comments,
T

HACK3DANDR0ID said:
Before I go back to 9.0.0, i figured i would ask....
Anyone get Viper4Android to install properly on Q?
I tried the latest Viper Magisk Module v1.4.2 i think... Magisk completed the installation but after reboot, Viper is requiring Drivers to be installed. So i install the Drivers, which took longer then normal, reboot and BAM! Viper needs to install Drivers on your device.
So Q doesnt seem to wanna play well with the Viper drivers.
And i tried installing Busybox for ****s and giggles and install fails in Magisk....
Thanks in advance for any assistance and/or **** head comments,
T
Click to expand...
Click to collapse
Try using this viper apk, it generates a magisk module when you reboot the phone. In the latest update post, OP says:
The compatibility mode switch has been added back. This seems to be mandatory for car mode and some android q builds.
Click to expand...
Click to collapse
Worth a try

TENN3R said:
Try using this viper apk, it generates a magisk module when you reboot the phone. In the latest update post, OP says:
Worth a try
Click to expand...
Click to collapse
Yea thanks for trying but no go. The apk did install the Magisk Module, Drivers took 2-3 times but finally took. Driver Status is all NOs and Unsupported Sometime soon i'm sure...

Question Magisk Update doesn't run very well :(

Hello guys.
Unfortunately the today Magsik Update doesn't run very well on my Device. I did update to the available slot then reboot but the bootsplash now runs since 1H without being able to land on OOS. I'm on 11.2.5.5.LE15 BA + Omega Kernel latest build
Fastboot mode doesn't report any bootloader version nor baseband version.
What's the best way to repair that ? What was the mistake I did to prevent further error while I'm updating magisk or the Kernel ?

Ty @avid_droid but that's what I tried first. It leads me to the exact same type of Boot where nothing happens for 30 minutes excepts the bootsplash logo animation.
I did try to boot from the vanilla boot.img ... but that sent me directly to crashdump mode.
I then boot one last time to magisk_boot.img and .... it worked.
For some reasons everything was wiped on the device even if I never wipe anything from fastboot but no matter ... I'm now back in OOs and try to set it up completly

It's not Magisk, I updated to version 23 with no issues at all.
Also flashed the new Omega kernel afterward, no issues with that either, Magisk was still retained.
I would see if you can get into recovery, if you can then do a system reset and see if the phone will let you set it up again.

For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^

Fre$h said:
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Click to expand...
Click to collapse
I did it the other way round, updated Magisk app, then Magisk itself, rebooted the phone. Installed the latest kernel using EX Kernel manager, it noted that Magisk was there so re-applied it on the new kernel, then rebooted and it was fine after that.
I'm not using any Magisk modules though, not going to risk that until we have a good recovery.

avid_droid said:
Same here. I keep magisk modules to a minimum. I am however playing with substratum and we know how that usually ends up haha. Giving it a go. Trying to remember the signal icons I used to use
Click to expand...
Click to collapse
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either

djsubterrain said:
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
Click to expand...
Click to collapse
Liv dark works now on op9pro OS11.. I'm using several different themes from livDark now

All I need to do here just hit "install"?
Ive never done it before so I just don't want to screw up.

First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update

Fre$h said:
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Click to expand...
Click to collapse
Thx bro...all good

This is particularly here we miss TWRP to flash magisk uninstaller properly. I like the way we can temporary boot from rooted boot.img but the disadventage is that we need a computer just near us to do that.
Hope everything is now fixed