yashsingh1/xdaforums huggingface dataset:
[Magisk] :
This is normal. The SafetyNet API in the official Magisk Manager is old and not working anymore, because SafetyNet API just got updated. Use another app like SafetyNet Helper Sample to check it.
[Magisk] bigw34:
Well I was already on 16.0 when it prompted me to install the "newer" version and safety net check was working before I flashed it a few minutes ago.
[Magisk] :
You are trapped by the timely coincidence: google has removed the support for the depricated old sf api. The current MagiskManager is using the old sf api. Since google has stoped answering old api queries, all old api requests are unanswered. This is not an issue of Magisk (no matter if 16.0 or 16.7) - so updating Magisk has nothing to do with with failed/working sf api queries, but MagiskManager needs to be updated to use the new sf api.

Use a sf api checker using the new api (like: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample) or change to one of the unofficial Magisk builds. I don't know for all, but [MENTION=7187684]ianmacd[/MENTION]'s build is updated and the sf api query is working.
[Magisk] bigw34:
Thanks for the explanation, I appreciate it. Thanks to [MENTION=6973536]bien2004[/MENTION] for the help aslo.
[Magisk] paolocorpo:
The API checker fails on my device

Where may I find the updated version of Magisk by ianmacd ??

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] Artim_96:
If you mean a different version than what topjohnwu creates you will not get any support here. And it's impolite to ask such things here
[Magisk] paolocorpo:
You are right ...

I faced a stupid question only pushed by my curiosity about the question discussed into post above

My bad

P

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] dboren:
Safetynet fail and root detection after magisk hide

Hello, I've developed a problem seemingly out of nowhere where magisk hide no longer works and safetynet fails (both cts and basicintegrity) and root is detected. I'm on a Pixel 2 Xl running Android P, no custom kernel, no custom rom and magisk v16.7. I've deleted all of my magisk mods except the props configuration. Also I have no Xposed mods installed. I've done everything I can think of including: repackaging the manager app, deleting files/folders with the name magisk in them, changing the fingerprint of the device through prop configuration (using the approved Pixel 2 Xl fingerprint), flashing a lower version (16.6), reflashing 16.7, clearing app data from the app (PoGo) that detects root and blocked its permission via the app App Ops (which seemed to not even attempt to block permission), download root checkers and use magisk hide to prevent detection of root (works 10% of the time), toggling magisk hide off and on in the app and manually through terminal emulator, toggling systemless hosts off, uninstalling the manager app and reinstalling multiple times, and countless reboots in between. I just got magisk hide to work for maybe 20 seconds and hide root and pass safetynet, but then after that time both are detected and failed respectively. It become quite a headache as it occurred out of nowhere and I had not downloaded any new mods or done anything new and unusual to my phone. Thank you for taking the time to read this long post and I appreciate your help, thank you.
[Magisk] guest4711:
Have a look in the unofficial thread: https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901/post77414965
[Magisk] paolocorpo:
Thanks a lot

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] b4karmenyan:
hai guys,

need some help installing magisk 16. so i have this lenovo a7000 plus with stock marshmellow and i want to root it using magisk. i flashed the magisk zip file trough TWRP and ended up bootloop. i've tried install it trough magisk manager, i patched the boot.img and flashed it trough TWRP but i got error message saying that the patched size is too big.

any of you have the solution for this please ????
[Magisk] martyfender:
I would suggest that you provide recovery logs for both attempts in TWRP. Hit the advanced button, copy log in TWRP and there will be an option to copy it to your internal sd card. You will have to rename one of them or it will be overwritten. You can do this by hitting advanced, file manager /sdcard/recovery.log, hit the rename file option, recovery1.log, for example. post them as attachments, not the full text in the post as mobile users especially, will have a hard time reading it. You may need to reflash your stock boot image to be able to boot back into Android to post your logs. If you can't boot back into Android, there may be a way to pull the logs through adb pull, to your computer, but that is beyond my knowledge, as I have never used adb pull.

I just did the rename operation myself, as I have never done it, I used: recovery.log and recovery1.log and upon booting back into Android and opening in a my file managers of choice: Total Commander and Mixplorer, I have those two logs on my internal SD card.

There could be a better way to do this, maybe someone else will elaborate?
[Magisk] Didgeridoohan:
[MENTION=5672992]dboren[/MENTION] What if you empty out that Hide list and try again? You only need to add those few apps that do detect root to the list, not every app on your device... I have no idea if it'll make a difference, but it can't hurt.
[Magisk] dboren:
Yeah all those apps are definitely overkill and I agree with you, I was suggested to hide from every Google app and that was the outcome. But hiding from only the apps I need to hide from and hiding from all those apps yielded no difference:/
[Magisk] Didgeridoohan:
That was a bad suggestion... :D

Unfortunately there's nothing in that Magisk log that shows anything not working as it should. Hard to say if it's something specific for you or if it's something that's changed for Pie. A logcat saved while you're trying to get MagiskHide to hide root, from root detectors and SafetyNet, might show something (if we're lucky).

---------- Post added at 07:21 ---------- Previous post was at 07:00 ----------

https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
[Magisk] RusherDude:
I tested v16.7 and I find something strange. Never used Magisk before so this may be logical:

- Brand new stock Oneplus 6 -> unlock bootloader -> boot then flash TWRP -> flash Magisk 16.0 -> Update to Magisk 16.7 with dm-verity so no manufacturer error appears.

In this status, Magisk as root works perfect, but MagiskHide is strange:

- In the own Magisk Manager application, the result is "This response is invalid".

- In the wiki, they say to try with a newer app with updated API, such as "SafetyNet Helper Sample". I tested with this app and it passes (green screen) even if I dont activate his toggle on the MagiskHide section, if I disable MagiskHide globally the app returns KO (red screen), so it appears to be working. However I find it strange that it is working without his special toggle on the MagiskHide section, is this normal?

- Also, the Play Store keeps showing "uncertified" even if I check its toggle on MagiskHide, but the app Netflix is downloadable, so it must pass SafetyNet right? (In all my other rooted devices, the app doesn't even appear on the store).

I find this strange. First safetynet seems to pass on the Safetynet Sample tool and on Google play store (Netflix is downloadable, but it says uncertified device?), but in the Magisk Manager app it says unvalid response. And every app seems to pass safetynet without toggling anything on the MagiskHide section, I tested and toggling/untoggling anything doesn't change anything at all.

PS: After a while, tried again and Netflix app didn't appear anymore. Added Play Store to the MagiskHide list, cleared Google Play and Play Services data, and now device appears as Certified, showing Netflix/Mario Run. The Magisk app still shows "invalid response" though. It seems that it was half broken before and somehow play services ended it on the background.
[Magisk] myzoneajay:
Facing the same issue. Magisk hide functionality does not works.

Device Oneplus 3t

Lineage OS 15.1

Apps are unable to get root privileges, unable to open the cloned Magisk APK. Have to uninstall that, then install original Magisk APK, then root works fine.
[MENTION=4470081]topjohnwu[/MENTION] please look into this.
[Magisk] Watanabe_You:
Thanks for the link. I checked them out and saw that

1. This was a clean install so there wasn't any leftover package

2. The two ROMs I tried did not have magisk packed in

This is probably a ROM error, since they all got commited from the same dev. Thanks anyway
[Magisk] :
If the official release and beta builds have a hickup, which will be fixed on the next release and someone is doing unofficial builds with the fix included in the very same forum, but in an other thread, mentioning this fixed build is not impolite but helpfull and just fair enough - especially when everybody knows that the next update is delayed due to [MENTION=4470081]topjohnwu[/MENTION]'s private situation...

@ianmacd's builds OP
[Magisk] paolocorpo:
Thanks a lot

I installed the beta build done by [MENTION=7187684]ianmacd[/MENTION]

Waiting for new coming from [MENTION=4470081]topjohnwu[/MENTION] ...

Paolo
[Magisk] jcmm11:
not sure which ”special toggle" you're referring to but everything sounds normal so far. Safety net test 'invalid response" is caused by Google changing API as of Aug 1 and will be fixed with next update. This error is only cosmetic and doesn't actually impact any functionality. Magisk Hide, by default, hides most of the things that you need hidden so you don't need to toggle anything (I haven't needed to even go into the Magisk Hide section of the manager)

As far as the Play Store being uncertified goes - you don't need to toggle it in Magisk Hide. All that it needed was to clear Play Store data.
[Magisk] robbayani:
i hope Magisk quickly update new API for fixing "the Response is Invalid".. because this problem my phone still detected as "rooted" if testing using Native Root Checker & RootBeer apps(i already including both apps in MagiskHide)..
[Magisk] teddy0209:
Lol... I missed the quote... You have busybox in system, that's why... You might also have the busybox installer app...
[Magisk] metropical:
back up issue

unable to back up a file since Magisk install. Perhaps it has something to do with the Xposed module?

The app is TextAide v9b3 and was previously run under Xposed v87/sdk23.

Magisk v16. 5.8.3(129)

LG G4 H811v20x MM.
[Magisk] robbayani:
yeah, busybox is included from my custom rom(Nitrogen OS aka NOS) :-s .. also my cusrom have root included(pHH Supersu).. but before install Magisk i unroot first by flashing NOS-UnRoot(from NOS rom developer)& UnSu-signed(by osm0sis)..

a month ago before new google API, RootBeer detecting my phone is "Not Rooted".. with Rootber checked in Magisk Hide + using module MagiskHide Props Config by Didgeridohan.. "Not Rooted" means my root apps & busybox(included from custom rom) not detected :D

#and then two days ago i clean flash with SAME CUSTOM ROM after new API and i get Response Invalid.. thats mean my root apps & busybox from rom still detected :( .. i'm also hiding RootBeer & using module MagiskHide Prop Config..

i think MagiskHide on Magisk not working because problem Response is Invalid..

are U using module to hide anything??

btw if using module "DOTMOD" in Xposed i'm also get "Not Rooted" on RootBeer & Native Root Checker apps :D

but i dont like that module
[Magisk] :
I highly doubt that: the "invalid response" is from a small piece of software, which is NOT included in Magisk it self (because it's not foss) and is just used for the sf check. Magisk and MagiskManger (including hide) is not relaying on this code. You can run Magisk, MagiskManager and MagiskHide without even downloading this.

"invalid response" doesn't mean sf api compatibility is broken - the opposite is true: sf api check still works (try a checker using the new api, like: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample).
[Magisk] RusherDude:
I see, thanks! Appreciated :good:
[Magisk] jenslody:
Recent rootbeer detects MagiskManager, you have to hide itself (from MM's settings).

Rom busybox can not be hidden by Magisk, because it's not systemless.
[Magisk] Didgeridoohan:
You've already got some explanations, but I just want chime in and say that everything you describe is perfectly normal.

You never need to add anything to the Hide list to pass SafetyNet, that's taken care of by default. And if the Play store at any point detects a failed SafetyNet check it'll report as uncertified until you clear data for it (as you already found). And "Invalid response" in the Magisk Manager has no impact on Magisk's ability to hide from SafetyNet.

You've already got your answer for Busybox. Magisk can only hide Busybox if it's installed as a Magisk module. The other two checks can probably be taken care of by hiding (repackaging) the Magisk Manager (in the Manager settings).

The fact that the apps can't find the su binary means MagiskHide is working just as it should...
[Magisk] RusherDude:
Yeah, but I found really strange that Magisk was updated to bypass last safetynet but the Magisk app was not updated to use the last API, which was like a WTF.. and then the toggles section being kinda useless was the definite wtf to post :P. Thanks!
[Magisk] madbat99:
Maybe read about what it takes to implement the API, and you will know why its still "coming in the next update". Also when the API requirement took affect.

That may help with your "WTF" moments.
[Magisk] jcmm11:
The API for testing it was updated, but not the way that SafetyNet itself works. Magisk wasn't "updated to bypass last SafetyNet", it just kept on doing what it's been doing prior to Aug 1. Like I stated previously - for our purposes it's strictly a cosmetic change that doesn't impact actual functionality.
[Magisk] martyfender:
[/COLOR]

[MENTION=4470081]topjohnwu[/MENTION] fixed the safetynet check in his recent commits, but has not released an official update yet. The unofficial builds have those fixes and more and are working great on many devices.

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

https://github.com/kantjer/MagiskFiles

https://github.com/ianmacd/MagiskBuilds/tree/master
[Magisk] dboren:
[MENTION=4667597]Didgeridoohan[/MENTION]

Here's the entire logcat a logcat app captured while I turned on magisk hide and then detected root through the root checker. I've never used logcat so I'm sorry if it does not show what you might be looking for. magisk might not pop up in a search so I believe it's repackaged as com.j.f6yJBgPKr.EWnc. Thank you for your help again
[Magisk] flex1911:
Thread cleaned. Lucky patcher is a piracy software and is strongly forbidden on XDA.
[Magisk] sk8223:
Is the Play Store detecting Magisk again, or is it my device? Probably just my device, though I'm pretty sure others with the same ROM and device are still managing to pass SafetyNet. I have no modules installed. Just base Magisk.

I have an LeEco Pro3 Elite (x722) on LineageOS 15.1. This phone was never released with Google apps. I don't know if it can even pass SafetyNet because of this, but I gave it a shot anyway.

After setting the phone up and installing some apps from the Play Store, I flashed Magisk 16.7 without issue, then cleared the Play Store's cache and force stopped it. Rebooted and the phone still shows up as uncertified in the Play Store. I managed to root the device with Magisk before on the same ROM and it managed to pass SafetyNet even though the phone showed up as uncertified in the Play Store app--I don't know how but it worked because I was able to see Netflix in the Play Store. Now I can't see Netflix, so the bypass isn't working anymore.

Checked SafetyNet status and get the error "response is invalid". That's the same error I had before on this device, but Magisk still let me see SafetyNet-dependent apps like Netflix in the Play Store.

EDIT: I got SafetyNet to "work" again. I still get the response invalid error in Magisk. And my device still shows up as uncertified in Play Store settings. But I can find and install Netflix from the Play Store again.

What on earth is going on.
[Magisk] martyfender:
Here is my response about 3 posts above yours. A simple thread search would have revealed many answers:

https://xdaforums.com/showpost.php?p=77440499&postcount=26615

I'm not sure in your case, but this could help, also:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md
[Magisk] metropical:
https://xdaforums.com/showpost.php?p=77435914&postcount=26606

now TextAide is broken since the last update of Magisk. Any ideas?
[Magisk] oscar1823:
Any fixes for Fate/Grand Order?
[Magisk] sk8223:
I'm using a custom build of Magisk 16.0 from June on my Redmi Note 4 (also LOS 15.1) and my device is certified. Is this only an issue with standard 16.7?

FGO JP and NA work fine. Just add either/both to Magisk Hide, and be sure to hide Magisk in Magisk settings. Clear FGO's cache and make sure Magisk isn't in your recents. I know FGO works with 16.7 even if you can't pass SafetyNet.
[Magisk] jcmm11:
Wipe data for play store, not just cache. Ignore the "response invalid". It's strictly a cosmetic error (or you can get an unofficial build with the latest patches). Or just get a safety net app from the play store that's already been updated (eg SafetyNet Helper Sample) and use that to check SafetyNet status.
[Magisk] Kimikz:
sadly fgo dont work on los 15.1 /treble roms on mido without magisk so weird...
[Magisk] AwesomeYash:
Supports Micromax Canvas 6.

Can anyone tell me whether magisk supports canvas 6 or not. I am a new user and I found the magisk modules extremely attractive. I want to use them but don't want to brick my phone. I don't have a custom recovery so pls suggest one for canvas 6 also. Thanks in advance.
[Magisk] yochananmarqos:
Text Aide is no longer in development. The developer pulled it from the Play Store last December due to the Accessibility service fiasco. The app doesn't use root, so I don't see how the error is Magisk related.
[Magisk] Killua96:
FGO doesn't work at all since the last update 1.20, that's why he asked, now there is only a temporary fix to skip the root check by changing the date, who knows how much it'll last...
[Magisk] AwesomeYash:
Someone help me pls.
[Magisk] -Happy Feet-:
Unlocked Bootloader?
[Magisk] Norbix1999:
Yes
[Magisk] -Happy Feet-:
Custom Kernel? With custom kernel I have also bootloops. The advanced stock kernel works.
[Magisk] Norbix1999:
Stock kernel sony

Please help me install Magisk on the Xperia M4 Aqua Andoid 6.0 unlocked bootloader and TWRP recovery

Phone after installing magiskv6.zip hangs constantly on the Sony logo (turn on and after a while) (flash sony logo and turns off)

I noticed that this is problem with boot.img

I would have uploaded these files from Magiska and super user to boot.img? This may work if

Please

Here a link to boot.img https://drive.google.com/file/d/0Bwfkh9Wew36kTGJlamI3enA1VDg

It is boot.img installed SuperSU version 2.76 so I had to delete it and route files magisk and superuser phh

I also tried on its original (including wgranym by flashtool) but there did not move (sony logo and reboot) and here even starts but does not work for me Magisk

Will load and like all ok but I can not switch the switch from the root of the root is always off

Help please
[Magisk] Ranomez:
This thing is working great on my Redmi Note 2 but could the SELinux toggle remember the state on reboot cause the ROM I am on comes with SELinux permissive and with it on enforcing the camera does not work right (and if I remember right other things as well related to Wi-Fi and Bluetooth)?
[Magisk] villo88:
Please describe what have you done.. :)
[Magisk] Depressed Man:
I was able to fix it by flashing a stock image. Then flashing magisk. Then letting Android boot up. And then flashing ph's su v17. Seems to work now and haven't gotten a message saying my su binary is out of date. Unfortunately the logs from when it wasn't working have been over-ridden. Oddly, flashing magisk and ph's su without a boot up of Android in between doesn't install the su binary.
[Magisk] xxspookyxx:
Is not working in moto Maxx, droid turbo ,can way method to fix?

This app have donate app in play store? I wanna help with cash, but i need this working.
[Magisk] shovelgrill:
Magisk Quick Toggle for Marshmallow

Hello, this is my first post on Xda.

I really wanted that nice toggle that [MENTION=3007198]bpear96[/MENTION] made for Nougat, but I am still at MM, so I made one for myself.

Also It should work on Lollipop, but not tested.

I dont have play store account and publish on aptoide

[MENTION=4470081]topjohnwu[/MENTION] Thanks for Magisk, it is exciting new way to use root.
[Magisk] Ranomez:
What exactly do you mean?

If you meant how I flashed it's a bit more complicated for me but basically I had xposed already installed so I downloaded the uninstaller zip, the unsu zip, the Magisk zip, the phh SU Magisk zip and the Xposed Magisk zip then I patched all of them to flash on the primary ROM in dual boot patcher (because I have a multiboot setup) and rebooted in recovery and flashed in this order:

Patched xposed uninstaller zip

Patched unsu zip

Patched Magisk zip

Patched phh su Magisk zip

Patched xposed Magisk zip

Then I wiped dalvik+cache for the primary ROM from the dual boot utilities zip and that's all, rebooted, waited for bootup, installed the phh SU app from play store and the Magisk Manager and good to go.
[Magisk] requiiiem:
I can use magisk for Android N?
[Magisk] Norbix1999:
Please help me install Magisk on the Xperia M4 Aqua Andoid 6.0 unlocked bootloader and TWRP recovery

Phone after installing magiskv6.zip hangs constantly on the Sony logo (turn on and after a while) (flash sony logo and turns off)

I noticed that this is problem with boot.img

I have Stock kernel sony

I would have uploaded these files from Magisk and super user to boot.img? This may work if

Please

Here a link to boot.img https://drive.google.com/file/d/0Bwf...GJlamI3enA1VDg

It is boot.img installed SuperSU version 2.76 so I had to delete it and route files magisk and superuser phh

I also tried on its original (including wgranym by flashtool) but there did not move (sony logo and reboot) and here even starts but does not work for me Magisk

Will load and like all ok but I can not switch the switch from the root of the root is always off

Help please
[Magisk] alroger:
You can use another app or xposed module for that.
[Magisk] Samuel Holland:
Thank you sincerely for sharing your work. Also thank you for the quick toggle.
[Magisk] JimZiii:
So i have a question. The selinux option says 'only turn off SELinux if necessary'

Yet it deactivates automatically from time to time.

So I'm just wondering why its turning off by itself and what this setting really does, if its safe to have it deactivate by itself
[Magisk] Rls4ever12:
Substratum is not working
[Magisk] aalemann:
Sony Xperia Z1 Compact, with a fresh CM12.1. Downloaded SuperSU to make a full and complete un-root (which worked).

Then booted into recovery and tried to flash Magisk, but it did not work, got the message: footer is wrong and signature validation error

Suggestions or experience if this is even possible on a Sony Xperia Z1 Compact...?
[Magisk] Xebazzztian:
That's Why I've updated my post some comments ago. Jeez ....
[Magisk] SpasilliumNexus:
After being called out on it. Nice try.
[Magisk] Norbix1999:
I have a problem

the root toggel just keeps turning back on

Help me please