yashsingh1/xdaforums huggingface dataset:
[Magisk] CrsMthw:
Thanks I reflashed my ROM and Magisk 10.2. Working perfectly now... I don't use phh superuser, I hate that. Also the safety net thing, yeah it's supposed to show fail because Magisk does not bypass safety net anymore after Magisk V8. So don't worry about that failed warning... :)
[Magisk] Magz Heaven:
I'm using the latest SU2.79 SR2. You? :)
[Magisk] mucha.k1994:
Well... Troll or just really don't know how to flash it properly? Magisk bypass safety net easy. But magisk hide must be enable in options in magisk manager. That's it.
[Magisk] htb2050:
Don't spread false information. Magisk doesn't fail safety net it's the only solution out there which allows ease of root while allowing safety net to pass. like that I am even seeing in this image?
[Magisk] mucha.k1994:
BTW - AFAIK pass safety net in a lot of apps and just truly PAID for smt in shop via android pay is a little difference. Someone in forum says they pass safety net, play POGO etc. but in shop when they close phone to reader nothing happen. So it's not a 10000% sure this will work.

Anyway, I pass SN and try pay in shop. Works like a charm :D

Now, I just have problem with v4a module on nougat :(
[Magisk] htb2050:
that is just one user that everyone is quoting around. maybe he didn't flash properly maybe he is just lying like the main stream media and pulling his sources out of thin air. ?
[Magisk] mucha.k1994:
Now I use word "maybe" ;)

Maybe you have right here, but I just told you what I hear. Anyway, I think if you correct flash everything it MUST work. pass = pass, so why I can't pass it in shop? summarizing - holy shiet - good work topjohnwu and other. Great work :)

by the way - in next hour I must go to shop. I will again try AP and post result here :)

And if someone else like this *troll* above will lie about not pass SN, I will make a video when I pay something via AP. Really. And them make a smt with root privileges.

Because people foolish sometimes scares me. :confused:
[Magisk] culiacanazo:
Just double checking...

You guys do know that topjohnwu, over at the official thread, mentioned something about some v10 problems, don't you?
[Magisk] oreo27:
What problems, exactly? I'm on 10.2 and it's working okay.
[Magisk] culiacanazo:
So am i, I'm just saying because i was reading that some ppl had some issues
[Magisk] culiacanazo:
I'm sorry about previous post, as usual, my screenshot attaching abilities suck.

Well, there it is, hope it helps
[Magisk] jadajada:
I wonder if anyone can help me? I am on Nougat 7.1.1 on Nexus 6P. I have newest Magisk 10.2 and newest phh superuser.

I am trying to install Viper4Android. I have tried all methods I know, but Viper cannot install its driver. It says that Busybox is not installed.

I have installed Busybox, and it is working. I have also checked to bind magisks own busybox in the settings. I have seen some tutorials saying that busybox needs to be installed in /su/bin, but I can't do that because busybox doesn't see systemless root.

Has anyone done a successfull install of Viper4Android with Magisk V10.2?
[Magisk] lululala:
Just flash the uninstall zip to remove magisk
[Magisk] oreo27:
Are you trying to install the V4A module or just plain V4A?
[Magisk] jadajada:
I have tried both. I have installed the V4A module through Magisk which needs the apk downloaded, which I have tried.

I have also tried to flash V4A directly and also the A.R.I.S.E-version. They all fail with the same: No working busybox or not rooted.
[Magisk] culiacanazo:
Any previous installs?

Well, it may not matter. Check this out.

V10.2 as well. Permissive
[Magisk] culiacanazo:
Edit: i forgot to mention, i checked magisk's busybox in settings
[Magisk] oreo27:
I only have experience with the magisk module. For this, you need to download the APK linked in the description of the module itself, not any other V4A APK. Otherwise, it won't work.
[Magisk] jadajada:
I have done exactly that. But this is what happens:
[Magisk] culiacanazo:
You're probably installing busybox to /system while v4a is looking for a systemless busybox, can you confirm?
[Magisk] frikakwa:
Try this BusyBox...

https://play.google.com/store/apps/details?id=me.timos.busyboxonrails

Working fine on my OP3.
[Magisk] jadajada:
Probably right. But how do I install busybox systemless?
[Magisk] jadajada:
Tried it now. No change.
[Magisk] culiacanazo:
You need to start quoting people because there are a few of us trying to help you, and i don't want to confuse you more.

If you're talking to me i would advise against busybox on rails as it is not compatible with some popular mods you might later want. I would uninstall stericssons (forget what viper said about only being compatible with it) restart (to be safe) and then just check magisk's

Edit: just so you know, binding is not the same as installing, so don't let that sway you, and please just acknowledge so i can know you're reading
[Magisk] jadajada:
OK. Uninstalled busybox, both stericssons and rails. Magisk busybox enabled. Still same error about missing busybox.
[Magisk] GatorsUF:
I asked a question here, hopefully some here can help. Trying to unlock/root my N6P again, but need to keep Safetynet. I know you get these questions all the time so I didn't want to clutter the thread with more of the same.
[Magisk] culiacanazo:
Was it successful? Sometimes it'll say that uninstall wasn't successful. And btw, the v4a version i caught i glimpse of in your screenshot is unknown to me, maybe, just maybe you need a different one

AND DON'T FORGET PERMISSIVE :)
[Magisk] yung40oz84:
So, I am trying to flash Magisk with DU, I flash unSU, and when I flash Magisk I get an error in TWRP and it is still detecting superSU I believe, I also tried booting, then going back recovery and doing it and same result, even though I made sure su was gone from system/bin and /xbin and cleaned out superSU........ please help, log link below.

http://pastebin.com/5Mt21xsR
[Magisk] culiacanazo:
I can't access your log but do you come from systemless supersu? (I read that you made sure to delete it from /system, but just double checking)... Usually it has to do with boot.img patching... If so, did you restore it? Any custom kernel? Did you manually delete the .img's from data?

I got nothing better to do in the meantime, but perhaps you might wanna wait for someone who can read your logs.
[Magisk] nixie2121:
So I had Magisk installed without Phh superuser. Using hide worked for Fios mobile so all was great. I updated to Magisk 10.2 and now when I choose to hide fios mobile and exit, the check mark does not work and disappears, so hide is not working for fios mobile. Any ideas? IF I wanted to switch to PHH Supersu, what are the steps? I am using Dirty Unicorns (Nexus6) with Supersu. Thanks so much in advance.
[Magisk] culiacanazo:
The steps are in the OP
[Magisk] oreo27:
I believe that the module already contains the driver. No need to install it from the application. Simply flash the module, install the APK and start using it.
[Magisk] Mr.Fearless:
I'm using magisk 10.2 with chainfire supersu cause the phh superuser (the latest ver) toggle module doesent remain selected after the reboot. I tryed disabling supersu app but it's the same.

Someone Can help me to enable pub superuser module?

Thanks

P.s. superuser.apk is installed
[Magisk] nixie2121:
Thanks, I was finally able to find it. Hide did not hold until I switched to PHH Superuser. All looking good now... Now I have never used Android Pay...might have to give it a try!

Thanks again
[Magisk] culiacanazo:
Right on! ;)
[Magisk] jadajada:
It does not work. The application keeps asking me for driver install at launch, every time. If I answer no, it simply does not work. It says Enabled NO.
[Magisk] teddy0209:
What version of the app do you have? Should be the same as the module you are using... As the other guy said, you can download the right app from the module description...
[Magisk] mucha.k1994:
AP work for sure - already tested and test in again today in shops in UK - worked.

But still this viper. I have annoying problem with viper too. Everything is YES in status drivers except PROCESSING, because it says NO.

Only way when it work is change to compatible in settings and disable SElinux. But I must disable it after every reboot. It's annoying so I search a better solution. Maybe change something in viper module? Some new files, commands?

GOD, why this nougat is so stupid.

PS - as above, I have 7.0 android stock on OP3.
[Magisk] jadajada:
The versions are the same. I have installed the apk from the module description. It simply does not work. I don't know if this is a 7.1.1 issue or a Magisk 10.2 issue. The last time I did this, was on a Samsung on Magisk 9. It worked then.
[Magisk] yung40oz84:
the log should be public......... ANyway, stock kernel, might use cutom, but was not when this happened, also did I restore what? the ROM> no, clean install, and I deleted su from /system/bin and /system/xbin, after running unSU, but it still detecting it, what else to delete from data exactly?
[Magisk] teddy0209:
Maybe it's on 7.1.1, I have it working on 6.0 with Magisk 10.2.
[Magisk] yung40oz84:
I just tried only data as f2fs today and still it will not root, on two different roms, crazy! Now, the regular phh superuser works without magisk, but when I use magisk, and even flash superuser after magisk I cannot get root, it does not show
[Magisk] dreinulldrei:
I have a very strange issue with the MyEE app (cell phone provider in the UK). As soon as I have Magisk installed (tried with and without root, Xposed etc.) it'll stop working and will crash when opening the app.

https://play.google.com/store/apps/details?id=uk.co.ee.myee

I found that when adding it to Magisk Hide, I'll see something in Xposed log.

Is this something that can be fixed?
[Magisk] IcyVeins:
Sadly, it is still not working with the most recent version on my Huawei Mate S:

- Repacking boot image
! Boot partition space insufficient
! Remove ramdisk backups and try again
! Boot partition size still too small
! Unable to install Magisk

The boot image is still uploaded (that´s why I quoted my post) . :crying:
[Magisk] andrew2432:
[MENTION=2393342]DAGr8[/MENTION]

Do you get a kernel warning on boot??

[MENTION=7182553]culiacanazo[/MENTION]

Are you on a custom kernel, rom, or just standard magisk 10.* phh, then the apks??
[Magisk] milesian:
It may not be a lie, just a misunderstanding. My manager shows all green but when I pay in store, AP cannot get past my Smart Lock security and keeps looping back for my unlock pattern. When I uninstall Magisk, my payments goes through after one unlock.

So even with Magisk all green and SN passing, there may be other issues sabotaging AP, maybe a kernel thing. Sigh... so close. Please enjoy your working AP enough for the rest of us still left out on the cold!
[Magisk] culiacanazo:
No warning, custom kernel, custom rom, v.10.2, latest phh, you lost me at "apks"
[Magisk] mucha.k1994:
Did you try unlock your phone before touch a reader? Well... Interesting. Because I never play like that, mean device locked. It's very interesting, tomorrow I go test it. But it is possible to pay without unlocked? Touch reader wake up my device and ask for password/fingerprint? omg, I never know it before!!! :D
[Magisk] HeNaFi:
I have a T-Mobile LG G5 supersu installed in systemless mode. I installed magisk 10.2 and the magisk.apk 3.0. In the app magisk install(green). Supersu(green). Ctf fails(red). I also tried phhsuperuser.

What seems to be the problem. Thanks in advance.
[Magisk] jhedfors:
At this point Android Pay generally won't work on custom ROMs based on nightlies with "test-keys".

If the ROM is based on a stable snapshot with "release-keys", it should work. I am on a CM13 snapshot ROM (Sultan's) for my OnePlus One), and it works great, but when on the Lineage14.1 ROM does not work (even though it passes safetynet).
[Magisk] waylo:
Completely uninstall supersu and use topjohnwu's phh r2 only.

Actually, you best uninstall magisk, flash a stock boot.img to remove all systemless root mods, and immediately install Magisk, skipping supersu altogether. Make sure magiskhide is checked in the manager.
[Magisk] HeNaFi:
I'll give that a try once I get home this afternoon. Thanks.
[Magisk] andrew2432:
Apk is my incorrect name for what you install from system, the gui application side: magisk manager and phhsu app side, not the zips.

What kernel/rom??
[Magisk] milesian:
The thing is, I use the Smart Lock feature to keep my phone unlocked when my smartwatch is connected, so with AP and its lockscreen requirement, it's at the point-of-sale when I'm asked for an unlock. With Magisk installed, that unlock mechanism fails. Anyway, as you suggested, Magisk+AP may well work for me if I disable Smart Lock, but that to me is too big a sacrifice. I still maintain the slim hope that my AP will work if Magisk worked with my stock Samsung kernel, but topjohnwu implied that may never happen because of a "namespace" Samsung kernel issue breaking Magisk Hide. Forever. Ugh.
[Magisk] jhedfors:
Not sure if you saw my other post, but Android Pay won't work if it sees that it is a nightly release. It must see that it has a "release-key" (e.g. stable, not test).
[Magisk] mucha.k1994:
Or just try a option, when you disable it for a while and then try pay with locked and unlocked little-before as I do it always. When you have 100% sure it is fail with smart lock feature.
[Magisk] Duo8:
This doesn't seem to work with Moto X 2014 on 6.0.

phh superuser creates a broken boot image so I used systemless supersu (had to force that). But magisk doesn't install, errors at "using sukernel to restore ramdisk": Unable to restore ramdisk.

There is no magisk.log in /cache

Here's the boot image with systemless supersu: https://my.mixtape.moe/dmkiew.win
[Magisk] culiacanazo:
Not sure what you're talking about, let me back trace

Edit: ok, I'm lost, as tapping on my quote takes me to a quote by andrew2432
[Magisk] jhedfors:
Sorry, it gets very confusing tracing the conversation. I thought you where trying to get Android Pay to work on a nightly release. If not, disregard!
[Magisk] Baconator724:
Hey, I can't disable the built-in busybox from showing in PATH. When I disable the config option and restart the app it's enabled again. I don't pass the SafetyNet check and I think this might be he cause of it.
[Magisk] culiacanazo:
Don't sweat it, it happens... :)
[Magisk] Artim_96:
Is anyone able to make a running module with the latest template for ARMv7 devices?

I just created a new module to remove AdAway installed as system app (since it normally won't really work) and to replace some ui sounds with empty files. Flashing it in TWRP gives me an ERROR 2, which I only found happening e.g. when trying to install GApps for the wrong platform.
[Magisk] Kal-El7:
Happy New Year folks,

Forgive me for asking here, but is the attached screenshot of a piece of [MENTION=4470081]topjohnwu[/MENTION] 's version 10 announcement refer to the MultiROM support that was once stated to be released in v.10 or is this something else which tries to do what MR does? Or did I misunderstand this section?

Thanks so much.
[Magisk] milesian:
Intriguing finding, thanks, though it may not apply to me since my ROM is pure stock Samsung TW, odexed/no mods. That said, I do use a custom Samsung-based kernel (in order for Magisk Hide to work), so if "release-keys" is something that the kernel affects, it could be the issue for me, as well. Any intel you can share on this theory?
[Magisk] Artim_96:
It is the official one. You can read the full announcement under the link in the first post here.

But I'd guess there will be a seperate thread for multi ROM (and of course one in the HTC forum for the Magisk powered ROM)
[Magisk] jhedfors:
The "release-keys" are how the ROM is built - I don't think it has anything to do with the kernel. However, the kernel does report the bootloader unlock status. If your bootloader is unlocked, and the kernel reports it as such Android Pay will not work. As you said you are using a custom kernel, I assume your bootloader is unlocked - has Android Pay worked for you before?
[Magisk] milesian:
I see, so I guess the "release-keys" isn't my issue, then.

Right, my bootloader is unlocked, but AP payments work for me in spite of that fact so long as I'm not rooted with Magisk or otherwise. Also, I recently read that Magisk now patches the bootloader reporting aspect of a kernel (dm-verity, right?) such that an unlocked bootloader is no longer an issue across the Magisk ecosystem. I could have misunderstood, though.
[Magisk] Kal-El7:
Thank you....yes, I had the opportunity to read the full announcement at first. I tried to re-read carefully the 'Custom ROM' section to see if I understood that correctly. I could have sworn I initially read some time ago TopJohnWu saying that MultiROM support would be introduced when Magisk v.10 would be released. Now that v.10 is released, I looked at the full announcement carefully to see if there was any mention of it, but I didn't see the word "MultiROM" mentioned. I did however see in the new release announcement the term Custom ROM and referencing the switching back & forth between a primary stock ROM & a custom rom. This made me curious if this was indeed an approach to something like MultiROM, but I was not very certain of the description I read & whether or not it pertained to MR or an alternative to MultiROM.

I will continue to be patient for MR. =)

Thanks again for chiming in. =)
[Magisk] Artim_96:
You're right, with both. SN shouldn't detect test-keys, but other detection methods do. And yes, Magisk doesn't let the kernel report the unlocked status anymore.
[Magisk] jhedfors:
I am very curious how this develops as well, and if it can be an alternative to MultiROM, or if ROMs have to be developed specifically for Magisk, which is really cool, but not quite as useful, if not broadly accepted.
[Magisk] Captain_Throwback:
That's not Magisk MultiROM.

That is literally just a systemless ROM, created as a Magisk module. I have 3 of such installed to my device, so I guess it's kind of like MultiROM in a manual sense. But that's not what [MENTION=4470081]topjohnwu[/MENTION] meant by MultiROM support. And I'm not sure where anyone said it would be ready by v10?
[Magisk] jhedfors:
Interesting. Can a systemless ROM be for different Android versions, such as Lineage 14.1 over CM13? Is there a guide to set one up?
[Magisk] Captain_Throwback:
You have to restore the ROM's stock boot.img. Otherwise Magisk will detect it as patched and not flash until you flash SuperSU again, since it sees a patched boot but no su.img in /data.
[Magisk] yung40oz84:
Yep I did that, got it to flash and back to same problem as yesterday, no root upon booting. Tried several options and variations
[Magisk] DAGr8:
Ok so quick update . By removing superSU from the rom.zip itself And manually flashing the original boot.img after the rom.

Then Magisk then phh.

I can successfully enable Magisk hide and I'm using phh superuser. Still failing profile mismatch but it's progress my kernel is permissive I'll try enforcing later
[Magisk] Captain_Throwback:
And you posted magisk log, logcat & boot.img already?
[Magisk] yung40oz84:
No, but I definitely will bro, been going wild flashing messing with all this today, lol
[Magisk] Apexpredator12:
Whenever I try to install anything through manager is says installation failed, how can I fix that?
[Magisk] yung40oz84:
Well the Magisk log is empty, probably because there is not root, I cannot get matlog cause no root and not by computer right now, but here is boot IMG. And also recovery log, and all flashed correctly
[Magisk] yung40oz84:
Sorry forgot boot IMG.

https://drive.google.com/file/d/0Bw-ARc6DtAVJY2hEOFY3cGJURGM/view?usp=drivesdk
[Magisk] culiacanazo:
Install it thru recovery
[Magisk] Apexpredator12:
I have tried with zips I download through manager it failes to install, but when I try to flash magisk it bricks my phone
[Magisk] culiacanazo:
It will not do that, it's not known to do that, if you "pull the thread" (no pun intended) you'll see that somewhere along the process you're overlooking something...

Search, because i can almost make an educated guess as to your "brick"; but it's been discussed... And as for us, we got nothing to go on from you :rolleyes:

I'mma go flashy flashy be back soon
[Magisk] Didgeridoohan:
SELinux have to be enforcing for Safety Net to pass.

You can find the Magisk log in the /cache folder with TWRP.
[Magisk] alego500:
I just have to say. I'm a poor ass student whose been into android mødding since I was 13 and after the v10 update I am left breathless. First ever donation! (only fair as i found out that you are a part of the Viper team, and Viper roms has been so good to my previous HTC devices)

Anyways, really exited for the future of Magisk. Also, why that name? Magisk means magical in Danish.? I'm rambling. Thank you so much.
[Magisk] babygau:
so magisk itself patch the kernel to unpermissive state?
[Magisk] culiacanazo:
Magical (system/systemless) mask perhaps?
[Magisk] Artim_96:
No, Magisk won't touch kernel. It only messes with the boot.img to be able to run and to hide unlocked bootloaders
[Magisk] yung40oz84:
No log there
[Magisk] Kal-El7:
This is my favorite thread at this particular time in my life. ❤️
[Magisk] edeg:
Removed for Boeing a retard wuestion
[Magisk] Alpine-:
Same deal, but gs6 edge. Multiple people having this issue and reporting it. Waiting for developments/info. I have the latest phh modified su installed.
[Magisk] culiacanazo:
?????

Please do tell more about this vision of yours
[Magisk] nixie2121:
quick question... when my rom gets a update, what's the best way to install? do I have to install rom which comes with chain fire su, uninstall magisk, unroot and reflash magisk and Phh su, or is there an easier way? thanks
[Magisk] culiacanazo:
What do you want ? Ccmt or phh's?

Either way it's in the op
[Magisk] vrgolin:
hi guys I just update the new Ver. from play store and I have the next message . thanks for your support. see pic.
[Magisk] Didgeridoohan:
I've no idea what you're asking for... Magisk Manager is letting you know your device does not pass Safety Net. Are you trying to pass SN? There are issues with Magisk Hide and stock Samsung kernels (stated in Official announcement thread under "Currently known issues")...
[Magisk] daneleo:
Any reason i can't install v10.2 on Galaxy s7 keep getting 'unable to restore ramdisk' then 'updater process ended with error 1' however i can install the older magisk's
[Magisk] culiacanazo:
Don't worry, I'm assuming you're in some Spanish speaking country, right? If so, you'll have a different device by the time the technology which you aren't "passing" right now starts being widely adopted.

Basically it's to let your phone accomplish things which would mean a security risk if it let you in its current rooted state (safety net would "guarantee" your phone hasn't been tampered with; of course, it has, and thus you assume responsibility)

Is that "Vergolin"?! ?
[Magisk] Alpine-:
Aside from this though, I'm having major issues with Magisk manager stability. It crashes a lot just using it and going through settings, etc., it doesn't display the modules installed correctly (shows none). Things just aren't working smoothly like v9. Not being critical, just reporting back what I'm seeing. I updated everything with the app from v9 straight to 10.2 along with manager 3.0. Do I need to like uninstsll and clean install magisk or something. It's also taken me from su to phh modified root, which is OK. I'll just uninstsll su I guess. A lot more is off than just no magisk hide working on Samsung device (s6 edge stock) though.

Update: forgot to install phh superuser manager after it switched me from cm su. That was causing issues.
[Magisk] vrgolin:
thanks . yes im in México spanish country speaking . then i dont have to worry.
[Magisk] culiacanazo:
So am I, cambio y fuera :)
[Magisk] yochananmarqos:
Enabling / disabling busybox in Magisk Manager requires a reboot to take effect. Whether you enable it or not will not affect passing SafetyNet.
[Magisk] danielcr12:
Mismatch, what does it means?
[Magisk] oreo27:
I'd like to know too. I have the same error.