yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
I'm. Not sure, but on the recent Canary builds, it is on by default. Disabling Android device administrators, temporarily, could help, because that helps to be able to go back to the factory version of google play sevices, so it may help you. Settings, security, device administrators.

UPDATE: I almost forgot about this, It comes from topjohnwu's documentation, but I used it last week You need to run these commands as root in a terminal app (type su, enter, first):

In Magisk versions newer than 18.1 (Canary or unoffical builds, some of the commands have changed slightly. You can see the new commands just by typing magiskhide, enter, into the root terminal. I used this to remove an app from the hide list by using the apps package name. You would need the actual package name for google play services, on your device

For example, on one of my devices it is: com.google.android.gms-1. On another, identical device, it is: com.google.android.gms-2. You can find the actual package name on your device in /data/app/ .
[Magisk] RandomPooka:
Isn't SafetyNet part of Google play services? I'm pretty sure it is.

If that's the case, you would ALWAYS want to hide Magisk from that, so disabling it is not a good plan.
[Magisk] martyfender:
In newer versions of Canary, it is enabled by default. By going to the upper right, 3 dot menu, you can enable: show system apps and then you are able to hide individual components of Play Services, such as snet, but as far as I know, there is no documentation yet on how to use this feature.

So potentially, one could hide everyone, with the exception of snet, to allow safetynet to work. However, it may be more complicated than that.

UPDATE: the one hidden is the one that has always been hidden by Magisk Hide:

com.google.android.gms.unstable.

Can someone clarify what the difference is from the above and:

com.google.android.gms?

Thanks
[Magisk] PokemonTotalWar:
gms.unstable is just the Beta
[Magisk] martyfender:
Yes, I am a beta tester on my 5 devices, does that also show up for those on stable versions in the magisk.log? I have been on the beta for the last couple of years, so I forgot about that. For those on the stable version, does it show up in the magisk.log as com.google.android.gms ?
[Magisk] PokemonTotalWar:
Yep, they just append .unstable to the beta, people not on the beta just get com.google.android.gms
[Magisk] Didgeridoohan:
com.google.android.gms.unstable is just the name of the part of Google Play Services that has to do with SafetyNet (got nothing to do with beta or not). It's always been automatically added to the Hide list, the only difference is that in the current code base it shows in the list (where previously it would be on the list but hidden) but can't be unchecked.
[Magisk] jenslody:
Just for the record and to avoid more complaints, microG's droidguard-helper is now (in recent canary builds) also hidden automatically and can not be removed from hidelist via ui.
[Magisk] BakaPhoenix:
I'm having a little problem with magisk hide, is working fine but sometimes stop to work and need to reboot phone to make it work again. having this issues on both my nvidia shiel tablet using stock rom (android 7) and my poco using nitrogen os (android 9) on magisk 18 stable
[Magisk] Didgeridoohan:
That's a known bug with both v18.0 and v18.1. You shouldn't have to reboot, it should be enough to just go to the Manager settings and toggle MagiskHide off and on again. It's been fixed upstream and the next release will take care of it.
[Magisk] Adnan008:
on op5t ob26; magisk 18.1 doesnt work at all (magisk not installed, even with 2 installs) and latest canary 116 phone opens completely fine but after a few seconds it reboots to recovery
[Magisk] dvhttn:
That explains exactly what I'm seeing then. Many thanks.

Basically I'm just checking things as I'd like to get GP working again but if I add a payment it just sits there spinning .......
[Magisk] dope77:
Can't enable/disable or delete modules. Nothing happen if i press delete or enable. Even after restarting phone, problem persists. Any ideas?
[Magisk] sidhrth89:
I cant install magisk..i try 5 time and also tried patch boot img..can anybpdy help??

Redmi 4 indian santoni, pixel experience 9.0 CAF sdition.
[Magisk] Pkt_Lnt:
First thing is logs are an absolute necessity to see why it will not install. Here is the guide to get the

full recovery log

.

https://www.didgeridoohan.com/magisk/MagiskHelp

Attach here (please to NOT copy & paste) or zip it attached here or upload to to pastebin.com or hastebin.com and provide a link here.
[Magisk] kotuamoalt:
Why are you questioning his perfectly legitimate answer? You are adding completely unnecessary steps. If you don't like the answer, you probably shouldn't ask the question.

---------- Post added at 12:19 AM ---------- Previous post was at 12:16 AM ----------

Modules are updated by the individual developers, at their leisure. There is usually contact info, so maybe you can ask about your specific module.
[Magisk] papatzis:
Hi to all again, with your help I managed to get magisk running on my xiaomi smartphone, now I try to install it on my old Cube UT65 10'' tablet. I patched the stock boot image, magisk is running root is working, but I have problem with magisk hide.

If I enable it from settings I see it but when I close manager and run it again it is not on, and if I check some apps in magisk hide there are not still checked after the reboot.

I had read the FAQ and I have a old kernel My kernel was from 2014 the tablet came with 4.4 Android, and know I had installed RR rom android 6.0 I have no other problems.

I have in magisk log "proc_monitor: Your kernel doesn't support mount namespace", so it is kernel problem . Latest kernel doen' t exist.

To add support to the existing kernel like this page https://lore.kernel.org/patchwork/patch/217023/ I think it is difficult for me I can pack repack the boot.img can you give me a little help ( If possible ) in what file to add the code to support namespace in the existing kernel? ( But I don't think it is easy to do myself ).

Thank you very much in advance.
[Magisk] moloko01:
Hi, I am now over to Lineage OS 16 official on my sm-t813, with a clean installation after whiping everything.

When I install latest Magisk, I got a bootloop after each reboot of the system.

I have to use the 3 button method to get into TWRP and clean dalvik cache manually to boot right into the then working system.

With alternate LOS-SU there are no problems with rebooting. So I think it is not rom related. Why isn't Magisk cleaning dalvik-cache at reboot?

Any suggestions/solutions? Thank you.
[Magisk] tyler19820201:
I was updating to LOS 16.0 20190312 nightly plus micro gapps on my OP3T. I did CLEAN install not dirty as goggle services were disabled to work... After clean install everything was working. Magisk 18.0 and adguard i am using. Every banking apps run well and GPay works no issue so far. Everything has been wiped off before install (exc. SD card)
[Magisk] TheUndertaker21:
will magisk work with Q beta ?
[Magisk] Ch3vr0n:
Who knows, it's not even out yet. Let's cross that bridge when it comes to that shall we? And if it doesn't, it'll probably get updated so that it does work with it

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Magisk] Didgeridoohan:
https://twitter.com/topjohnwu/status/1102152024232263680?s=20
[Magisk] dope77:
hi everyone,i rooted my phone a couple of months ago after i bought it,everything was just fine till yesterday when magisk stopped working properly (didnt allow me to remove/disable modules). and today all apps granted supersu permission disappeared from magisk and magisk didnt give me an option to give them root permission again. i rebooted my phone a couple of minutes ago and now it's stuck in bootloop (continous restarts during boot at logo),tried reflashing magisk from twrp but im gettting this error (Failed to repack boot image Updater process ended with ERROR: 1)

any idea what caused this?

-didnt make any changes to my device

-using same modules since i rooted my device and non were updated recently

currently installed modules:

xposed sdk 27

youtube vanced

magisk manager for recovery

viper4android
[Magisk] Pkt_Lnt:
Au contraire, mon ami. :D

https://www.xda-developers.com/android-q-dp1-google-pixel-2-google-pixel-3/

https://developer.android.com/preview/download
[Magisk] martyfender:
Flash the latest magisk uninstaller, followed by your stock boot.img, just to be safe and then flash magisk again.
[Magisk] kingbri:
Bad news for android Q people

https://twitter.com/topjohnwu/status/1105947979679191041
[Magisk] TheUndertaker21:
Yeah I'll pass on Q for now.
[Magisk] coolbeans2016:
Magisk not hiding from Google pay

I just finished installing latest security patch for nougat 7.0., fresh install, (3-1-2019) from LG. After flashing Magisk it did not show installed even after putting manager on. Magisk manager downloaded 18.1 zip I rebooted to TWRP flashed it and then all was well. Until I tried setting up Google pay. It detects root...

Not sure if this has happened to anyone else OR where is it the right place to report this...

zach
[Magisk] coolbeans2016:
Log file
[Magisk] prot-:
Does android pay work for anyone currently?
[Magisk] martyfender:
There is a thread dedicated to Google Pay:

https://xdaforums.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
[Magisk] dope77:
still same problem,flashed magisk latest uninstaller then boot.img ,when trying to flash magisk i got same error and phone still wont boot
[Magisk] stanguay:
Google pay not work for me even if the safetynet pass. Magisk 17.3

Envoyé de mon SM-G935F en utilisant Tapatalk
[Magisk] J.L.C.:
Anyone else having issues with Magisk Manager 7? I have Magisk 18.1 and everything works fine with Manager 6.1. But when I update to Manager 7, it shows Magisk isn't installed...But everything is still fine in Manager 6.1
[Magisk] kotuamoalt:
If it were me, I would run the magisk uninstaller in TWRP, then reinstall magisk, and then the new manager.
[Magisk] martyfender:
deleted, becauses [MENTION=4667597]Didgeridoohan[/MENTION] already posted the link from his excellent guide.

Thanks, [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] vukis:
Hi.

OnePlus 6t stock rom rooted with latest stable magisk. Call recorder and youtube vanced modules.

Having one banking app which complains about phone being rooted. SS attached. Banking app: https://play.google.com/store/apps/details?id=lt.swedbank.mobile.v2. Can provide apk if it's not accessible. Root detection happens when first launching app after clearing data.

This app complained trowed errors before rooting (with unlocked bootloader). Haven't tried before unlocking bootloader

Tried root hiding from app via magisk hide (also hide phone and google play store). Also tried hiding magisk manager.

Even tried MagiskHide Props config spoofing my phone as 1st pixel fingerprint with device simulation (was thinking about if this app checks device + DRM Widevice Security level L3)

Play store reports device as certified and SafetyNet test passes.
[Magisk] martyfender:
People seem to be resistant to try the Canary build. I would suggest you try that. I believe Magisk Hide is much improved in that version, with the disclaimer that there can be new bugs. so a good backup is prudent, of course.

Did you delete the apps data before all of the hiding and relaunching?

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot

https://www.didgeridoohan.com/magisk/MagiskHideMore
[Magisk] xamxixixo:
Hello, I am using android x86 on a Surface pro 3 and it seems fine. I managed to install magisk on it. With the new kernel and ramdisk.img replaced, the device run like it's on fire (the fan screams) and for a short time of using, the OS stopped working. And when I replaced the old kernel and ramdisk.img (stock files of android x86) it was fine again. How to fix it? Thank you
[Magisk] tyler19820201:
Do a clean install wipe everything. After installing the os make sure to disable automatic update of the os. I am using LOS 16.0 and lineage updater is disabled to avoid unwanted updates. It might happen your phone downloaded some updates for your os and this can lead to crash your magisk and could make a bootlop also. That is my personal experience.

---------- Post added at 10:56 AM ---------- Previous post was at 10:46 AM ----------

1.Remove magisk from twrp and do clean chache and dalvik

2 remove your banking app and restart your phone.

3. Install your banking app and register with your device. Log in at least once to make sure works well. When you log out make sure to do forced stopping!! Settings/apps

4. I am using adguard. Install it on your phone.

5. Install magisk from twrp and set up magisk hide. Do not worry about modules it should work without them. When you do the magisk configurating make sure the banking app not running on the background!! (Forced stopping enabled)

6. Restart your phone and enable adguard

7. Try to log in banking app
[Magisk] ashyx:
Agreed. Canary fixed detection of MBNA app.

However I had to use the uninstaller to do a clean install and then it worked a treat.
[Magisk] vukis:
3 step it is not working well. As I described in my initial post it is not working since unlocked bootloader.

Tried canary build (magisk-release.zip) from https://github.com/topjohnwu/magisk_files/tree/master/canary_builds With same negative result. And I cleared app data in between every step.
[Magisk] Didgeridoohan:
Have you tried disabling USB debugging and/or Developer options?
[Magisk] ashyx:
Like I said clearing app data wasn't enough, clean install of Magisk was needed.
[Magisk] J.L.C.:
Uninstalling magisk and re installing did the trick. Thanks!
[Magisk] martyfender:
Yes, I should have mentioned using the uninstaller.zip. I've had to use it a couple of times myself, recently, when in the past I only had to flash the new magisk.zip.
[Magisk] vukis:
Hmmm no I didn't. It was working alright with an old galaxy s7 with developer options on. I know how to enable them, but will need to google how to disable them :)

Magisk was uninstalled before installing canary build
[Magisk] kingbri:
Topjohnwu's Twitter says that that magisk now works for Q on pxl and p2xl and their respective counterparts. Will this be in the next canary?
[Magisk] H4X0R46:
Quick question, the canary build is self explanatory, a manager apk, and a flashable zip... What is snet.apk for? Anything I as an end user need to worry about? Thanks.
[Magisk] tyler19820201:
Did you try bricktool? This is for bricked phones and will restore the bootloader as factory settings (locked bootloader). Then try to unlock again and start from step 1.
[Magisk] vukis:
You saying that locking bootloader and unlocking it again could solve this issue?

Does this app report as rooted for you too?
[Magisk] nowster:
I think it's the SafetyNet check it downloads.
[Magisk] tyler19820201:
Try it and will know. You have nothing to lose.

I have 6 banking app on my phone. Only barclays was not working after clean install of LoS 16.0. it was detecting rooted phone... However my phone was unrooted but because LoS is not the official ROM it does detect as "unsecure device". The rest of banking apps works well before installing magisk. However after magisk installation all the banking apps has been thick in magsik hide and even barclays was launching with no issue. I was using the same installation method mentioned the previous post.
[Magisk] vukis:
I would lose half day of unlocked and relocked bootloader data wipe cleaning up. And it does not look very promising as that app was not working with non rooted bootloader unlocked stock rom :(

That's why I was asking to try that app with your device. Its root detection results are quick and straightforward: it would show root warning on first screen upon first app launch
[Magisk] martyfender:
It is not yet ready for Q and one person who did try to flash it has bricked his phone and can't get any PC's to recognize it to restore. He posted in the Canary thread.

Read all of topjohnwu's recent tweets to see this.
[Magisk] pogo-airsupport:
I think you're confused.

His recent tweets demonstrate he was able to root both OG Pixel and Pixel 2.

The person in canary build flashed a 18.1 canary build, which is NOT 18.2 as seen in John's twitter

I believe John is probably trying to see if mounting a logical drive is something he can accomplish in a few days, and if so he'll just release everything at the same time
[Magisk] martyfender:
Nope, [MENTION=5005867]Mayex[/MENTION] stated he flashed the latest Canary build, which is an 18.2 version, ecf3d303.
[Magisk] pogo-airsupport:
Well I mean John was able to do it, so possibly his changes have not yet been pushed to github
[Magisk] kingbri:
I have the OG pixel XL. On further investigation, I saw that the latest canary (which I flashed. I'm not gonna flash 18.1), makes the system not boot. He may have not pushed as of yet just like pogo-airsupport said. Thanks for the clarification. I'll use my in-kernel su builds for now
[Magisk] tyler19820201:
Wich banking app is that?
[Magisk] guest4711:
To quote [MENTION=2553561]vukis[/MENTION]' post:

Banking app: https://play.google.com/store/apps/details?id=lt.swedbank.mobile.v2.

Unfortunately it is not available in my region so I cannot check it.
[Magisk] Quinny899:
His changes have been pushed, you can see it in this tweet. b7e2e972 is this commit, so when the canary build is updated to that or beyond (it is not currently), it will work on 1st and 2nd gen pixels presumably.
[Magisk] tyler19820201:
Unfortunatelly the link does not work for me. I can se it is swedbank but lot of different version are on Gplaystore. Anyway i have never try this app before.
[Magisk] martyfender:
I am in the United States and I was able to install, add to Magisk Hide list and the app launched fine without any warning on one of my devices with Canary 18118. I do not have the Magisk Manager hidden either. The device passes safetynet and shows as certified in the playstore. I also have MagiskHide Props config installed, but don't have any other fingerprints set or have device spoofing enable. My devices default fingerprint is certified.

Of course, I do not have an account with that bank, so I can't go any further than this. I removed it from Magisk Hide, deleted data and it still does not detect anything.

Swedbank 2019 Lietuva is the app I downloaded, v80, is that correct? I do see multiple ones listed.

Nextbook Ares 8A, x86, Android 6.0.1 tablet.

I would suggest testing the Canary build, with a good backup, of course. I recommend you use the Magisk uninstaller first, before flashing Canary.

I have never tried the stable 18.1 build of Magisk, with the exception of Canary and unofficial builds, when they were at the same commit level as the stable.

Magisk Hide has been totally rewritten since the stable build was released.

If I turn off Magisk Hide and delete the app data, it still does not detect root. Also, on that one device I still have the now deprecated folder, MagiskManager, which many apps detect now.

I did not reboot after unticking Magisk Hide.
[Magisk] bigknowz:
Donate

Just sent [MENTION=4470081]topjohnwu[/MENTION] a token of appreciation for his hard work and deciding immediately to do what it takes to get root on Q, Who's with me? (if you can spare it, of course).
[Magisk] Badger50:
Just did the same myself. TJW is a beast, and I for one am happy to donate to his hard work and determination. Thanks again TJW :good::good::cool:
[Magisk] bheeshmpita:
[Issue] Unable to get root access despite installation of magisk manager

The magisk manager despite being successfully installed through zip file flashing in recovery mode, my device doesn't get rooted, even though the magisk manager app gets installed on my device. I am using a custom ROM on my device

I'm sharing the related info below

device details

[moto e(condor)

android ver 6.0.1 M0B30Z

MIUI 8 02.20161129.234431 Beta

kernel ver 3.4.112-g1eaf2cb]

magisk ver 18.1

magisk log text

01-01 19:10:42.017 227 227 I Magisk : * Creating /sbin overlay

01-01 19:10:42.088 233 233 I Magisk : * Device API level: 23

01-01 19:10:42.088 233 233 I Magisk : Magisk v18.1(18100) daemon started

01-01 19:10:42.099 233 234 I Magisk : ** post-fs-data mode running

01-01 19:10:42.099 233 234 I Magisk : * Initializing Magisk environment

01-01 19:10:42.102 233 234 I Magisk : * Mounting mirrors

01-01 19:10:42.103 233 234 I Magisk : mount: /sbin/.magisk/mirror/system

01-01 19:10:42.104 233 234 I Magisk : link: /sbin/.magisk/mirror/vendor

01-01 19:10:42.104 233 234 I Magisk : bind_mount: /sbin/.magisk/mirror/bin

01-01 19:10:42.104 233 234 I Magisk : * Setting up internal busybox

01-01 19:10:42.167 243 243 I Magisk : Magisk v18.1(18100) logger started

01-01 19:10:42.239 233 234 I Magisk : * Running post-fs-data.d scripts

01-01 19:10:42.239 233 234 I Magisk : Create /data/adb/magisk.img with size 64M

01-01 19:10:42.295 233 234 I Magisk : * Mounting /data/adb/magisk.img

01-01 19:10:43.269 233 234 I Magisk : * Running module post-fs-data scripts

01-01 19:10:43.269 233 234 I Magisk : * Loading modules

01-01 19:10:43.365 233 272 I Magisk : * Starting MagiskHide

01-01 19:10:43.365 233 272 I Magisk : hide_utils: Hiding sensitive props

01-01 19:10:43.366 233 272 I Magisk : hide_list add: [com.google.android.gms/.droidguard.DroidGuardService]

01-01 19:10:44.936 233 539 I Magisk : ** late_start service mode running

01-01 19:10:44.947 233 539 I Magisk : * Running service.d scripts

01-01 19:10:44.956 233 539 I Magisk : * Running module service scripts

03-15 03:28:21.248 233 272 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[4295] ns=[4026539712]

03-15 03:43:32.819 8953 8953 W Magisk : su: request rejected (10081->0)

03-15 03:43:57.114 10521 10521 W Magisk : su: request rejected (10081->0)

03-15 03:56:41.636 233 272 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[29476] ns=[4026539722]

03-15 03:57:07.515 233 272 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[29856] ns=[4026539660]

please note that I am an amateur in the rooting process, so while providing help please use easy to understand terminology

Any kind of help would be appreciated
[Magisk] martyfender:
You may have better luck with the latest Canary 18118. Make sure you have good backups though and know how to recover from problems that could occur.