yashsingh1/xdaforums huggingface dataset:
[Magisk] DanGLES3:
Don't worry its a bug,magisk and some other apps checked safetynet using a now old method that google has blocked,its just a matter of magisk updating the safetynet checking api,don't worry about it,your device is likely passing safetynet its just that for now magisk can't tell you that until it updates to the newer api
[Magisk] xabier-bo:
root:root 666, like other devices I use
[Magisk] Didgeridoohan:
Not sure then. Some issue with sqlite3 on your device? Is it 64-bit ARM by the way? You could try installing the sqlite module in the Manager repo in that case and see if there's any difference. (No idea if it'll work, just throwing more or less useful ideas out there)

You say you've tried doing an uninstall and reinstall of Magisk, but how did you do it? By just flashing the uninstaller in TWRP and directly installing Magisk again? If so, try using the complete uninstall feature of the Manager and let the device boot up once before installing Magisk again.
[Magisk] mrspeccy:
There is only one user in "Settings - Users" and only one folder ("0") in the /data/user folder. However, Huawei's EMUI system seems to have something called "App Twin" (which I never used) that can create clones of an app. Not sure how it works internally (maybe it creates fake users) nor whether this App Twin has inadvertently been called my Magisk. However, at the moment this is the only feature that seems to be unique to Huawei phones and has something to do with app clones. I will try to investigate this further.
[Magisk] xabier-bo:
Yes, everything related with uninstalling an re-installing tried, with no success :(

AND right, it's ARM64. I'm not a developer... could you give me a more clear instruction of where should I download the sqlite3 module?
[Magisk] Han-Droid:
Hi

I used the search function but couldn't find an answer.

I realized that the date in my magisk logs is old ...only the last lines are with the correct date.

Log was cleared so it's not and old log.

Could this point to some problems I might run in to?

Apart from this I get force closes on several apps.

Deleting magisk app data helped but now it's like before. All this shaky behavior started with 16.7 . Before I used .4

Any thoughts?
[Magisk] jenslody:
It's normal if you have setup your device to automatically get the time via network (I guess that's the default on most roms), because during startup of the device the time/date is not correct and will be set when the device gets connected to the outside.
[Magisk] Didgeridoohan:
Magisk Manager - Downloads - Search for "sqlite" - install.
[Magisk] xabier-bo:
Thanks again but still not working...

As an outsider... if "everything" is working "properly" (apps get superuser grant and can be seen and managed under "superuser"), where is this information cached? Just to try to find out why is not stored into magisk.db
[Magisk] Didgeridoohan:
This kind or general troubleshooting is best kept in the General support thread, I'll answer you here...

Your log shows several modules and as far as the log shows they're properly installed. You'll need to be more detailed with your posts...

What do you mean be "none are there"? In the app drawer? In the Manager Modules section?

What's you device/ROM/Android version, etc?

Please help us help you... One line responses are seldom useful when trying to troubleshoot.

---------- Post added at 19:29 ---------- Previous post was at 19:26 ----------

It's supposed to be stored in the Magisk database... I think I've seen something similar a long time ago. Can't remember...

Have you tried asking other users of your device for aid?
[Magisk] sam00561:
Hi yes they show up as enabled in magisk. But none of them show in the app drawer. Rom renovate ice and android version 8.0. Other users of the rom have not been able to help.
[Magisk] xabier-bo:
I'll try but I found nothing...

I've done some testing with other different rooted device. This is what I've noticed:

* Failing one:

- magisk.db keeps the same timestamp from the begining of the session

- a magisk.db-shm file (I've read is a temporary file, and I guess it's where information is cached) appears at the directory

* Working one:

- magisk.db timestamp gets modified immediately afer any app is (un)granted

- no magisk.db-shm file at all.

Just to share information and in case it gives any clue if anybody ever finds in a similar situation
[Magisk] martyfender:
Most modules don't show up in the app drawer. There are some that do. look in the modules section of Magisk Manager (MM). Some modules have configuration options through the terminal such as Magisk Hide Props Config. Greenify4Magisk does show up in the app drawer. What modules do you have installed?
[Magisk] sam00561:
All the modules I use show up as proper apps usually in the drawer. YouTube black vanced, Greenify, viper. They are working now properly after I installed then again.
[Magisk] angelillom:
There is some way to update the Huawei P20 Lite software without losing the phone's ROOT

Is TWRP also lost?

THANK YOU
[Magisk] Pkt_Lnt:
Ask in the P20 Lite forums instead of all the Magisk forums. :rolleyes:
[Magisk] angelillom:
HUAWEI P 20 Lite ROOT

I ask here because what you lose "Supposedly" is the MAGISK, I do not lose the mobile system

Thank you and I'm sorry
[Magisk] benryu:
So flashfire doesn't work with magisk latest version. Heard it works only till 14.2. I'm trying to get a copy of 14.2 but can't seem to find any working link. If anyone has a copy could you please share with me.
[Magisk] yochananmarqos:
Flashfire will most likely never be updated again and Magisk 14 is no longer supported. Is TWRP available for your device?
[Magisk] benryu:
Yes I do have twrp
[Magisk] rexmako:
Why can't magisk be installed in my car headunit? I have tried severally to install magisk on my android 5.1 car stereo, it only shows the magisk user interface, saying "magisk is not installed". Can someone please help?
[Magisk] thelexxnow:
Is there some app available in the Play Store today, which already employs the new SafetyNet API and can check for Safety Net pass/fail as long as Magisk isn't updated?
[Magisk] :
https://play.google.com/store/apps/details?id=info.pvs.safetynet

?
[Magisk] zeroprobe:
Hi sorry for the delay, here is the module.

But my app will change the ID of the magisk module so there can be multiple versions of it, you would need to change the ID and make a few different versions of it.

https://www.androidfilehost.com/?fid=1322778262903980038
[Magisk] mrspeccy:
I made some progress on this issue and found a workaround. First of all, the Huawei AppTwin mentioned in my previous post was probably a dead end. What I did was:

With the original manager installed, I started a root shell and looked at the file "/data/adb/magisk.db". I regularly copied snapshots of this file to the "sd card" and investigated them with an sqlite viewer.

1. Before repackacking the manager, the file had several non-empty tables, in particular in the "policies" table that stores the apps granted su access.

2. Immediately after repackaging the manager (really immediately after the dialog "repackaging the manager" disappeared), the file contained an additional entry in the "strings" table, namely the random app name of the repackaged manager under the "requester" key!

3. A few (<=10) seconds later the magisk.db file was altered again. It turned out that all tables were cleared, except for android_metadata which contained my locale setting.

Items 2-3 are consistent with my observation that for a very short time span after repackaging the manager, su requests are still handled by the repackaged manager and open a requester window; but after some time has passed, all requests time out.

My workaround was to stop the repackaged manager and then to copy back the magisk.db file collected in Item 2 to /data/adb (which was possible since the root shell was still open). Now everything works as intended: no more double managers after a reboot, the su access rights are displayed in the repackaged manager, and new su requests are properly handled.

Fortunately, this workaround is needed only once after each update of the manager. However, it is a bit of a tedious procedure and it would be nice to understand why the magisk.db database is first altered correctly and then cleared. Can it have something to do with the fact that the original manager is not properly uninstalled (I had a strange error message of this kind in the logs, claiming that the manager was installed for several users)? Could the original manager be in some undefined state and try to re-establish its settings by writing an empty database to /data/adb? Finally, I noted that for a moment there were two Magisk Managers shown in the Settings->Apps menu of Android at the point where I stopped the repackaged manager. The second instances was not visible in the app drawer, though, and disappeared from the Apps menu shortly after.

Really weird.
[Magisk] Didgeridoohan:
There's absolutely nothing strange about your module... For fun, I even installed 12 versions of it on my device (slightly altered to not cause a bootloop), causing it to resize the Magisk image twice.

Looking back at your original report I see that you're using recovery to flash the module, right? Do you see the same behaviour if installing through the Manager? I tried both and had no issues...

Since you say that you have an app that is changing the module ID, what are your exact steps for installing the different versions of the module? And why do you need different versions of the module? There'll only be one of them that is mounting the files. All other modules that have the same file structure will do nothing...

I am still leaning towards the answer that it is your recovery that is causing this issue.

Interesting find. I'll pass it on to [MENTION=4470081]topjohnwu[/MENTION], but he's busy moving halfway around the world at the moment, so it might be a while.
[Magisk] cd993:
Can I ask, is this something that I can do or are we to patiently await an update? I looked at the API page but suspect (unless I'm wrong) this requires to be updated in the app and/or modifying the current one?
[Magisk] Yemble:
To add to this question...

IS this fixable in Magisk?

WILL it be fixed in the next (or a future) beta?
[Magisk] Didgeridoohan:
It needs an app update, so there's nothing you can do. Except to use a different app to check SafetyNet, one that's been updated. There are a couple around and it's been mentioned here and there in the forum in the last day or so.
[Magisk] guest4711:
If you really need to know wheter safety net is ok for your device (and if it is not enough for you that all apps needed by you are working fine) you should install another app for checking status of safetynet. The beta thread has a lot of useful hints... https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post77335769
[Magisk] Didgeridoohan:
Of course it is possible It might be possible (no idea if Google would block it, considering what Magisk does), but the question is if it's necessary. Being able to check SafetyNet in the Magisk Manager has no releavance on Magisk being able to hide from SafetyNet. It might not be worth the effort to update the app... But, that's ultimately up to [MENTION=4470081]topjohnwu[/MENTION].
[Magisk] cd993:
The difficulty I'm facing is that whilst Magisk and other apps fail to confirm passing safetynet ("call to safetynetApi.attest was not successful" and "response is invalid"), most importantly my Google Pay doesn't work anymore and so I can't use NFC to pay for things (learnt the hard way buying my morning coffee at work! Luckily she let me off for today :p)
[Magisk] Didgeridoohan:
Like I said, there are at least a couple of apps that have been updated for the latest API that you can use to check SN instead. Look through the threads...
[Magisk] cd993:
Thanks, my issue is not just apps telling me of safetynet issues, but my Google pay no longer working either :(
[Magisk] cd993:
Hmm I tried the martyfender-test.zip, installing the module via Magisk, and my system failed to boot. Flashed magisk uninstaller the reflashed the magisk 16.7 and system booted again.

Hmm...
[Magisk] Didgeridoohan:
Why are you posting here about my module? I have a support thread for a reason... And use the repo version please. That zip was a (surprise!) test, nothing else.

If you continue having issues, please post in the module thread and make sure to provide logs (installation logs, Magisk log, boot logcat, module logs, whether you can get your hands on).
[Magisk] sajanwfz:
safety net not work anymore ?
[Magisk] kantjer:
OMG :rolleyes:
[Magisk] cd993:
Apologies, will check the appropriate thread!

Thank you
[Magisk] rinaldi14:
Try using this apps guys..to check your safetynet..it's work on me..
[Magisk] rinaldi14:
Try using this apps guys..to get your safetynet status...it's work on me..
[Magisk] lnephyr:
SafetyNet

Hey guys, I'm having some trouble to play Pokémon go and watch Netflix.

Phone Nexus 6P

Resurrection Rom Oreo 8.1 latest version (August patch)

Latest Open GApps

Magisk 16.7

Both apps on MagiskHide

App repacked

I have installed the root checker posted above and it says: "Response Signature Validation : Fail (response payload validation fail)"

Anyway so can I fix it?
[Magisk] vandyman:
What can you tell use about the Google API

issue that everyone knows about? [emoji6]
[Magisk] zeroprobe:
Strange, I have an app that generates the magisk modules by changing the ID. It is to change camera bitrates and shutter speeds to save recompiling to have preset modules with different settings.
[Magisk] Chouiyekh:
hi guys i have installed magisk 16.7 zip

but why i get ???

latest version v16.0

installed version v16.7

i think i should get

latest version v16.7

installed version v16.7

and why i can't pass the safetynet, i always get : the response is invalid !

my phone is pixel 2 xl running android p the latest version, please help
[Magisk] MrPhilo:
Does not work, it seems Santander UK has found a way to know that if Magisk Hide is used on the app it force closes. When I remove it from Magisk Hide it just tells me it has detected root.

I have tried force closing, clearing data etc but seems the recent update they had has found away to detect Magisk hide.
[Magisk] jcmm11:
If you want it fixed I suggest you provide some logs so topjohnwu has some information about what's happening. Or you can just wait on the next update and hope that it's been fixed.
[Magisk] galapagos:
16 is the official version. 16.7 is a beta version.
[Magisk] Joyjo:
Please help me magisk hide don't work. Response not valid,on every rom and on every version of magisk. Proc.monitor gms unstable in event.Please help me i'am inexpert. Thanks in advance.my device is s7 edge
[Magisk] Nimueh:
You should really read back a few pages, this has been widely covered already and will probably get fixed in the next update.
[Magisk] Artim_96:
Try SafetyNet attest. It has just been updated to newest API and now works again. So Magisk manager just needs an update. The response is just invalid, not false since it's just a network error
[Magisk] DroidJP:
Hey guys,

Can anyone explain why the magisk uninstaller encrypts your data when removing magisk completely? I am basically trying to create a twrp boot backups that are in different states boot images for easy kernel swaps in case i run into an app that really detects root.

That way i can completely unroot without having to remove magisk by simply switching boot images and back lol.

Is there a flag in the uninstaller script to remove magisk but without it encrypting data?

Thanks.
[Magisk] Didgeridoohan:
When you flash Magisk, it can remove the forced encryption flag from your device. Whenever you uninstall Magisk it restores the stock boot image and the forced encryption flag will be activated again, thus enrypting your device on the next boot. If you want to avoid this you'll have to find a noencrypt zip for your device to flash after uninstalling Magisk. If you have a completely stock boot image, it will always encrypt your device (on any modern Android device).
[Magisk] DroidJP:
Yeah, about that. Kind of thought ahead on that one lol. When i flashed magisk in twrp, after it backed up the stock boot image. I deleted that backup so it would not restore it thereafter, thinking that no encryption on the next boot. Whelp, just how i thought one step ahead. It too was 2 steps ahead of me lol.

When i flashed the magisk uninstaller, to the point of restoring boot it said

"! Boot image backup unavailable Restoring ramdisk with internal backup"

And you guessed it. Data encrypted on the next reboot. So does this means that there is a backup of a backup?? What?? Lol.

I did find the noencrypt zip for my device and do what you stated instead lol.
[Magisk] Joyjo:
So that's why even other verification apps give me an invalid result so i have no problem?Thanks.
[Magisk] teddy0209:
No... It doesn't affect passing SN...
[Magisk] Joyjo:
It seemed strange to me because in the play store infact netflix pokemon go snapchat etc...were accessible still endless thanks for help ?.
[Magisk] sliding_billy:
Do you have a link?
[Magisk] Didgeridoohan:
It's called SafetyNet Helper Sample in the Play Store. You'll find it there...
[Magisk] guest4711:
You may try https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample which is just updated (and should contain neither trackers nor advertising).
[Magisk] sliding_billy:
Thank you both!
[Magisk] Cristi82:
Hi until now magisk worked fine but now an app that it was hidden by magisk auto-updated and i cant hide it anymore, if i hide it its show me an error that saiy that i have route on my phone
[Magisk] tliebeck:
Can't execute "pm" command on Android Pie due to SELinux restriction

I'm having some issues getting my root-enabled apps to work after Android Pie, they're not able to invoke the "pm" (package manager) command, even as root, due to SELinux violations. Even invoking "pm" with no arguments at all (which just displays help) fails with this SELinux violation, regardless of whether I'm running as a normal app user or as Magisk su:

type=1400 audit(0.0:82148): avc: denied { read write } for path="/dev/pts/2" dev="devpts" ino=5 scontext=u:r:system_server:s0 tcontext=u:object_r:untrusted_app_all_devpts:s0:c512,c768 tclass=chr_file permissive=0

Checking my current security context using /proc/self/attr/current...

As app user: u:r:untrusted_app_27:s0:c512,c768

As magisk su user: is u:r:magisk:s0:

Even when running as root, the security context in the log message is always listed as "u:r:system_server:s0", even though /proc/self/attr/current is showing magisk.

I also see a failure using the "am" (activity manager) command, but only when running as root (it will at least display its help info when running as a normal untrusted app user).

All of this can be replicated using Termux or a normal terminal, exactly the same way my apps fail.

Device is an Essential PH-1 on the current-and-presently-only stable release of Android Pie.

Setting SELinux to permissive mode solves all of this.

Everything else root-related in my apps seems to work just fine on Pie+Magisk, e.g, manipulating files, remounting filesystems, and reading /proc.

Thank you for any suggestions.
[Magisk] kkolokol:
In HTC U11 stock Oreo 2.42.617.6 , magisk 16.7, safetynet returns "invalid response" for now, but attest recent update from gmarket makes that standalone app working and returns green pass.

From the turn: gpay etc. All work just fine which only means: we need update to sleep well. :--))) Thanks.
[Magisk] tom.etc:
Just confirming that all magisk related stuff is working on 2013 moto x fw running aokp mm (droid ultra hw). Pokemon go and google pay work, even as google updated its api or whatever broke SN in magisk mgr
[Magisk] DroidJP:
Now that i know that having your device encrypted has nothing to do with Safety Net (which i thought that was one of the requirements for Safety Net lol)

I can ditch encryption altogether and finally be able to use twrp backup features.

Now the real true solution if there was a twrp that can mount encrypted data.

In any case, the latest safety net app now passes without any issues and google pay is working.
[Magisk] MetalIris:
Probably due to Google updating their api
[Magisk] armando_rod:
PSA latest Pokemon GO APK 115.2 doesn't work with Magisk root, we get an unauthorized device error message
[Magisk] SebaS-DG:
Same here, 115.2 comes with a loot of changes and soon will be forced to play.
[Magisk] dbr93:
Same here,is a overall problem,we pass safety net but not pokemon go security

Hope someone investigate on this and is able to find a solution
[Magisk] landwinwand:
Hi

Magisk don't want to work please help it give me this when I try to open

......

java.lang.StringIndexOutOfBoundsException length270 index-1 at java.lang.String.charAt(Native Method) at com.topjohnwu.sup.

Help fix bro

.bye

:)
[Magisk] LeMoise:
This is in regards to Pokemon Go not working on their apk 0.115.2

I attached a catlog to this post. I recorded the log of trying to log in with a dummy PTC account that is met with the error. I have no idea how to read through the thing or what to look for, maybe someone else can find it helpful or direct me to someone who could utilize it.

Edit: So I flashed a stock ROM, installed Magisk and tried again. Still didn't work. Something in the logs to be noted though is that there is a DetectedActivity with a confidence number attached to it. It was 100 in the first log file but is now only 62 on my fresh install. Maybe that has something to do with it? I've attached the new log also.

Edit2: Reflashed Stock ROM, did NOT install Magisk and it works. Bootloader Unlocked, No Root.

Edit 3: I'm an idiot
[Magisk] DrPhant0m:
I had an odd issue today. When I woke up, Titanium Backup reported it couldn't get root access (weird, since there were no changes to TiB). Later, AdAway reported it couldn't get root access. So I opened up Magisk. Magisk told me MAGISK couldn't get root access. There was no "root" options in Magisk.

I tried to reflash Magisk, and it wanted me to point it to a boot image. Don't have one.

I reinstalled Magisk from 16.0 version... everything was fine.

I attempted to update to Magisk 16.7... and it said it was unable to unpack the boot image. OK, so I tried in recovery. It said the same thing.

Now for the really weird part (well, weird to me. Some devs probably know why it happened)... my phone would not boot back to the OS. It would only boot to the fastboot screen (I have an LG V30).

I had to restore(flash) the boot partition from a recent TWRP backup to get the phone to boot to the OS. When it booted, I updated to 16.7, and now it works again.

Since we're "imminently" close to a stable release, I thought I'd mention this in case there are some extra bugs to work out.
[Magisk] peterlee928:
somewhat similar note - i have had magisk beta 1674 "randomly" stop working for me. unlike the scenario above, it started working again after a system reboot. unfortunately, i have not been able to capture logs because all my root apps that capture logs (including magisk) wouldnt work as root was lost.

google variant p2xl

stock rom 9.0

no custom roms/kernels

busybox pro stericson with ibuprofen binary installer tool

EDIT

ive only noticed this since upgrading to android p and magisk 1674.
[Magisk] diemadedrei:
Without me having changed anything Pokémon go stopped working now, when it worked an hour ago and Magisk returns something which translates to "invalid response" on the safetynet check. I'm on lineageOS 14.1 if that matters (I guess not)
[Magisk] fw85:
I would just like to point out that after seeing your post, I've gone through my older saved logcats (from last week), as I was trying to debug the Go+ connectivity back then, and I've also noticed a resultDetectedActivity originating from NianticActivityManager, but with various confidence levels ranging from as low as 20 to 100.

I'm not sure what this number means exactly, but since this was already captured back on 0.111.4, running a Magisk rooted Lineage 15.1, I'd say it may not have anything to do with this game update and the new unauthorized device error in particular...