yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
[MENTION=2903832]BruceElliott[/MENTION]

There's no such thing as a "SafetyNet infection". Your device either pass the SafetyNet check or it doesn't. The only thing that's stored is the device certification status in the Play Store, but that can easily be updated by clearing data for the Play Store.

There are many apps that "report" to Google, as in that they use a bunch of Google's APIs for the Play services and other stuff. But they won't "tell" on you. If your device doesn't pass SafetyNet, Google still let you easily change things so that you do. The official ways are:

Remove root, Xposed, and other apps that are seen as security issues.

Use an official, certified device/firmware.

Lock your bootloader.

With Magisk you don't have to do this, because it can help you hide the above,

except Xposed

.

You do not need to wipe your device... Unless you haven't unlocked your bootloader, because doing that will usually wipe it.
[Magisk] martyfender:
Revert to kantjer's 180520 build.
[Magisk] BruceElliott:
Ok, thank you Didgeridoohan. That is good to hear and I will give Magisk a shot without wiping /data. I flashed stock ROM, uninstalled SuperSU, cleared Play Store data and indeed was able to open Play Store and see my apps.

Over the past few days I have reflashed the stock ROM and/or installed old stock versions of Play Services and Play Store numerous times without uninstalling SuperSU. When I do that I immediately regain Play Store access. Play Store immediately auto-updates Google Services and the Play Store app. Then I begin locking things down with Titanium and Netguard, checking at each step by opening Play Store successfully. All seems well for awhile until SafetyNet figures out what is going on, at which time not only can I not access Play Store but my my phone get wonky and overheats, among other things. SafetyNet must be disabling or crippling Play Services for that to happen. Seems dangerous and borderline unlawful to me to punish a root user by physically damaging his phone.
[Magisk] roboprint:
Guys,

Has anyone managed to solve the way to install the polish bank IKO application?
[Magisk] BurnedDrake:
Failing SafetyNet does none of that, you have some other problems going on you need to figure out

Sent from my SM-N920T
[Magisk] eriknors:
I'm trying to reinstall magisk and I keep running into problems. My question is I guess do I need to flash the magisk uninstall zip in twrp or in adb? Cause some how I've f@#ked up something and no matter what I do I can't seem to reinstall magisk onto my essential PH-1.

Here's what I've done so far:

I installed a couple modules back to back without rebooting and when I did reboot I was stuck in bootloop. So I flashed the stockboot.img and everything was fine. Tried running the uninstall.zip in twrp with no luck. Everytime I try to flash magisk back onto my phone it freezes and goes into bootloop. I've done a full wipe back to stock. So far I've flashed back into twrp restored my data and still cannot flash magisk to get root. What am I doing wrong? I can get a log if necessary
[Magisk] Didgeridoohan:
Always assume it's necessary...
[Magisk] HemanthJabalpuri:
Sir [MENTION=4470081]topjohnwu[/MENTION] When patching boot.img it downloads magisk zip file to patch the boot.img but when again patching another boot.img it again downloads the magisk zip file, it does not uses the existing magisk zip file.....

Sir please add a feature to patch the boot.img in .pac extension also to get flashable files for spreadtrum devices also
[Magisk] xboxkiller88:
Is there a current issue with 16.4 and Pokemon go I am unable to login at all to the app it says unsupported device
[Magisk] ianmacd:
No need. I found the commit to native/jni/utils/img.c that broke module installation. If I revert that and recompile, everything's sound again.
[Magisk] jenslody:
What about sharing your solution ?
[Magisk] ianmacd:
Of course. Attached. Fixes the bug introduced in commit b436bce565f0878aacda7c9d8ad891116c72092f.
[Magisk] deepakdavidster@gmail.com:
Any fix available
[Magisk] Didgeridoohan:
The issue will probably go away if you disable MagiskHide. But other than that, all you can do is wait for [MENTION=4470081]topjohnwu[/MENTION] to have some time on his hands to investigate and maybe come up with a fix.
[Magisk] martyfender:
Do you have somewhere you can share the flashable zip with the fix, or should I wait for topjohnwu to release a fix? I have never set up a build environment as I have limited space running Linux Mint from a 32gb, persistent, casper-rw, USB thumb drive.

Also, Do you plan on doing what I think is a revision or pull request at [MENTION=4470081]topjohnwu[/MENTION] 's github page?

Thanks
[Magisk] ianmacd:
No problem.

I've attached a couple of ZIP files to this message. One is for S9 and S9+ devices (G965F), and the other is for everyone else.

Do make sure you have a boot.img back-up before you flash these, so that you can recover is anything unexpected happens. They work for me, though, on both an S9+ and a Tab S3 tablet.

My fork of [MENTION=4470081]topjohnwu[/MENTION]'s Magisk repo can be found here:

https://github.com/ianmacd/Magisk
[Magisk] martyfender:
Thank You,

I installed on one of my devices and then successfully installed a module.

And yes, I could have waited for a fix by topjohnwu and a new release by kantjer, but I like testing new builds, knowing I can easily recover if anything goes wrong.
[Magisk] ianmacd:
Hey, I'm glad to be of help. I just wish my understanding of the code was better, so that I could work on the sporadic root loss issue that many of us are seeing. I don't have a background in Android programming, and Magisk is a rather complex piece of code.
[Magisk] danielson2047:
Does magisk need to be reflashed after every wipe/new rom flash or no since its changing the boot.img?
[Magisk] Didgeridoohan:
[MENTION=4470081]topjohnwu[/MENTION] knows about the issue and will try to fix it. It's probably caused by MagiskHide sometimes failing to remount folders after hiding (/sbin in particular).

Yes your do. Unless your ROM has addon.d, in which case it'll take care of it for you.
[Magisk] BruceElliott:
With regard to hiding...

Magisk is a wonderful project; thank you!! I put off learning about it and installing for a long time, but finally bit the bullet and so glad.

FYI as to my experiments with the Manager hiding function: The process does not show up at all under developer options as a running process, so that is good. However, it shows up simply as "Magisk Manager" in Settings...Application manager, complete with icon. It also show up that way with the "Active Applications" widget. Under OS Monitor there are two cached entries named "Magisk Manager" and showing the icon, one for the manager and one for the su process. The hiding function may take a bit more work and may ultimately be limited by OS constraints.

Separate subject and question... I also show an entry in Settings...Application manager for SuperSU with the SuperSU pound sign logo, even though I selected "complete uninstall" from within the SuperSU manager and rebooted before installing Magisk. I assume that some components of the SuperSU manager survived the uninstall, because Titanium shows pre-Magisk backups for it. Also, I remember reading that Magisk stopped using SuperSU long ago. Could someone please confirm that this is not associated with Magisk, so that I can feel safe about uninstalling it? I don't want to mess up my Magisk installation, of course.

Thank you!
[Magisk] ianmacd:
Yeah, I know it's a known bug. It's just that [MENTION=4470081]topjohnwu[/MENTION] is stretched about 6 different ways at the moment, so I wish I could pitch in and help out.
[Magisk] BruceElliott:
Yes, I'm thinking that paranoia was beginning to set in after excessive late-night hours attempting to fix my phone. I must have locked down some system process with Titanium and/or Netguard. But my troubleshooting technique led me to the aforesaid conclusions.

Step-by-step I would lock down a process and then check for Play Store access. All would be good until an hour or two later when I noticed my phone hot and wonky in various ways, with no Playstore access. Settings... Google would blink the screen and return me to the same place; so I could not delete and restore my account. At that point, completely re-enabling all apps and processes from Titanium, disabling Netguard and rebooting numerous times would not fix the problem. However, I could get back to normal by deleting Play Store and Play Services data and by restoring those two services to Android 6.0.1 stock versions.

Now I am being much more conservative with Titanium freezes and Netguard network restrictions. With Magisk installed and conservative lockdown, I left my phone unplugged for 18 hours and battery went from 100% to 70%. That is more than good enough!
[Magisk] addas4:
Can anybody tell me if it is possible to enable/disable Magisk Module using a soft/hot reboot instead of full reboot?

I tried it & it didn't work for me :(

I want to enable & disable Xposed SDK 26 faster than a full reboot. I know I can install No Device Check to Pass CTS but this doesn't make Basic Integrity Passed :(

Thanks a lot in advance! Special thanks to [MENTION=4470081]topjohnwu[/MENTION] that saved our lives after Google implemented the stupid SafetyNet :(
[Magisk] martyfender:
A few builds back, I had the root loss issue, but I haven't had any root loss in recent weeks, with [MENTION=3306843]kantjer[/MENTION]'s recent builds.

again, thanks, it is working great, so far.
[Magisk] yochananmarqos:
You answered your own question. ;)
[Magisk] soder:
Sorry for writing a post like this, but I'm looking for a file like "magisk mount for recovery"? I had one like that before, that mounted the stuff to /magisk, where I could remove stuff when I had problem.

Now I only find Magisk Manager for recovery, and I don't get it to work.

The problem is that I got Magisk installed and working, but installed Xposed in Magisk and then some module called Android P-ify that seems to have done something not good to my phone.

I want to remove the Xposed module in Magisk, but can't boot the phone.

Please help. BIG thanks...

EDIT: I might had solved it with the Magisk Manager for recovery. It was that I had to press "enter" twice to disable the module.

/Söder
[Magisk] Didgeridoohan:
[MENTION=2438781]soder[/MENTION]

You'll find it here:

https://xdaforums.com/apps/magisk/collection-magisk-modules-v2-t3575758
[Magisk] John D J:
Hi I'm new to magisk therefore don't know much about this super su and there are over 2500 comments of which is a lot of reading. So please may I ask, and please don't be offended, if I root my s4 with magisk will I still be able to use my banking apps even though rooted. Will it hide the root from them please? Thanks for your patience and answers. :good:
[Magisk] teddy0209:
It depends on the bank app. So just try it. Add it to magisk hide, and probably hide also the manager, then hope it works.
[Magisk] Didgeridoohan:
That's correct. Magisk hasn't been compatible with SuperSU since v13.0.

Maybe. More on that here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] 123lisa:
Device: Oukitel K10 (MT 6763, arm 64)

Firmware: Stock 7.1.1

Security patch level: 5th december 2017

Bootloader: Unlocked (orange state)

Problem: Bootloops after flashing Magisk 16.4 or 16.0 (doesn´t matter if I use TWRP or fastboot to flash). Anyone have similiar problems? Or any ideas how to fix this?
[Magisk] Pkt_Lnt:
Check this -

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

Note these sections - (everything there is very useful, I suggest bookmarking it)

Installation Issues

Asking for help/reporting bugs
[Magisk] Flyview:
Reposting this...
[Magisk] Kylethedarkn:
I'm currently having a problem with Magisk 16.4 where installed modules are not showing up in the app drawer. I've tried installing them from the downloads section of Magisk Manager as well as flashing the zips with TWRP, but neither have worked. I've also tried installing the modules one at a time with the others uninstalled and that does not work either. Any help would be appreciated!

Samsung G920P

Nougat

Magisk 16.4 Beta
[Magisk] guest4711:
Most modules have no GUI so nothing will be shown in app drawer.

If a module is listed as active under "modules" it is recognized by Magisk and should work. Some of them have command line interfaces which you may call from terminal emulator / console. Have a look at the documentation of the module how to invoke it.
[Magisk] demonoidmaster:
Then use said custom kernel... Jfc, stock kernels usually suck anyways

---------- Post added at 09:19 PM ---------- Previous post was at 09:12 PM ----------

Deep sleep % is the indicator of how long your phone has been in deep sleep, it's not a battery drain indicator

All are percentages, but some listings are for how much something has been active and using battery while others are simply to list how long they've been active (like your wifi for example at 100%)

---------- Post added at 09:26 PM ---------- Previous post was at 09:19 PM ----------

>without magisk installed

>flashes magisk uninstaller

>do noy works , why?¿

Hmmm i wonder why...

---------- Post added at 09:40 PM ---------- Previous post was at 09:26 PM ----------

with MyAndroidTools app open it then go to service, system, play store

From there find "DailyHygiene$DailyHygieneService" and disable it, this disables the service the play store uses to check and update google play services, play store, etc

Also if i were you I'd keep ya gapps up to date (with opengapps or other choices) just saying
[Magisk] cmezh:
Good day everyone!

Currently I'm trying to find a way to install Magisk on AndyOS Android emulator (or better to say - virtual machine, since it's based on VMware). The problem is that it comes with no boot.img, but separated ext2 partition containing kernel, ramdisk and cmdline file. And, of course, no recovery mode.

I believe that it's still possible to get Magisk working on this emulator, but I need your ideas and advices where to digging to. Thanks!
[Magisk] sajjads24:
can not install magisk on lineage 14.1 ?

hi

i am can not install magisk on lineage 14.1 for i9100 ?

how fix this ERROR ?
[Magisk] xXxNeXuSxXx:
Today I received a notification that magisk update is available and since then my modules are not working... also there is no install update automatically option which was available earlier.... the weird thing is that now I am not able to see boot.img in Magisk folder as well....

So can I proceed further to update magisk?
[Magisk] yuri76:
I have a problem on galaxy s8 plus goes in bootloop. I tried to do full wipe and put supersu and that's fine

Inviato dal mio SM-G955F utilizzando Tapatalk
[Magisk] Didgeridoohan:
I would start by just rebooting your device.

There's a known issue where it seems like MagiskHide sometimes fail to remount everything after hiding, resulting in Magisk seemingly not being installed. It's under investigation...

---------- Post added at 11:27 ---------- Previous post was at 11:25 ----------

I guess you could start digging through the code to see what Magisk actually does to the boot image, and match that on your emulator.

https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh
[Magisk] xXxNeXuSxXx:
Super thanks... that worked!
[Magisk] guest4711:
i9100 is nit supported by magisk. The linuxkernel used for our beloved Sii is too old.
[Magisk] hshah:
I tried some of those newer builds and it didn't solve the problem for me. I ended up going back to v16.3 and currently haven't lost root in around 4 days. Previously it was mostly immediately after booting.
[Magisk] the steve:
I have a cheap chinese tablet called BMXC S10, in Windows explorer it is called S900. It runs android 7.0, has MT6797 decacore chipset (helio X20) and Mali-T720 GPU. There is no official manufacturer and no offical homepage to get the original firmware.

Can anyone help me get the boot.img from my stock rom? I only found tutorials using MTK Droid Tool to create a scatter file and then make a readback with SP Flash tool. Unforunately my tablet is not recognized by MTK Droid tools, so what can I do? Is there any other way to get this boot.img, or create a scatterfile for a readback? I tried to backup with adb, but I can't do anything with the backup-file.
[Magisk] 123lisa:
I literally tried everything from this thread with no success. I also tried to keep dm-verity and forceencrypt. It´s also not that it fails when I install it from TWRP (it says, it´s perfectly fine), it just doesn´t boot afterwards. Maybe my Oukitel has special keys that it needs to be signed with and the test keys don´t work? I might have to add that rooting with SuperSU seems to work without any issues (tried for testing purpose and properly unrooted after that with osmosis unSU script + flash of the clean boot.img), but I prefer Magisk due to it´s useful modules. Should I try to grab some logs and post them up?
[Magisk] Pkt_Lnt:
Logs are the

ONLY

way you can get help on this issue, recovery log for certain and probably a logcat.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] ro-mann:
Magisk isn't listed in my apps on my Samsung T580. Apps that require root just go on loading and won't start. I've flashed Magisk in TWRP and there whas no error message. But it doesn't show in my apps.
[Magisk] Didgeridoohan:
You could attempt to sign the boot image yourself after flashing Magisk:

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606

This can sometimes happen... Try to install the app manually. Download the apk from the release thread.
[Magisk] davidzam:
I have a question. Did you rooted your tablet?

Enviado desde mi SM-G550T1 mediante Tapatalk
[Magisk] the steve:
No, I could not find a working root method. That is why I want to use magisk. But I need the original boot.img for that....
[Magisk] davidzam:
Using mtkdroid tools can get you the temporal root you need tho get the firmware from your device?

Enviado desde mi SM-G550T1 mediante Tapatalk

---------- Post added at 03:00 PM ---------- Previous post was at 02:48 PM ----------

You should try out this method, read all the post and all the other post that X3non makes reference to

https://forum.hovatek.com/thread-21970.html

Let us know if at least you can get the boot file.

---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------

At least you would have your original firmware backup in case of any contingency.

---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------

Mediatek it's another world entirely. :)
[Magisk] the steve:
I can't use mtk droid tool because it doesn't find my device, so temporary root doesn't work either. On my research I already tried the wrr method. It creates some kind of partial scatter file according to the selected chipset but SP flashtool could not use the adresses to create a readback.
[Magisk] davidzam:
Well then I don't know how to help you out. Maybe there's a root method... In my experience using MTK devices you can use mtkdroid tools to root or use apps like kingoroot. Maybe it's what this means is that there's no root method yet for the firmware of your device. Or maybe more research is needed. MTK are popular in Asía and Russia. They had a lot of web forums working on such smartphones, but they write only on Chinese or Russian. I'll send you anything I can find from them if I can or maybe a link to the Rom itself. One note, MTK Droid tools gives you all the information you need to find the right firmware, sometimes, again from experience, one Rom that does not seem to be for your device, because it's from another brand, works just fine. They are almost all the same, if you know what I mean. But you have to test one by one. I did it because of my job selling this kind of devices an offering support for them on warranty issues, sometimes it worked sometimes it won't. Sorry I couldn't help.

Enviado desde mi SM-G550T1 mediante Tapatalk
[Magisk] adaa1262:
Delete

---------- Post added at 10:39 PM ---------- Previous post was at 10:38 PM ----------

You can find most China phones/tablets ROMs and custom recoveries on 4pda (with Google translate) & needrom
[Magisk] davidzam:
Exactly. Needrom, if it not there, an equivalent will be, if not, then...

Enviado desde mi SM-G550T1 mediante Tapatalk
[Magisk] the steve:
I hoped for a way to get a copy of boot.img out of my system like some adb pull command or something, but it seems this doesn't work with newer android versions.

Thank you anyway for trying to help. I guess this is a risk when buying cheap Chinese stuff. I would like to try different roms or at least recoveries but not without a complete backup of the stock firmware. I think I will have to wait until more people buy these tablets and work on custom stuff here on xda. Maybe there will be an update on mtk droid tools in the future so it will recognize these devices.

Thanks again!
[Magisk] davidzam:
Yes, but look on needrom. Also try to backup your firmware, if you can do that it will be a great advantage for you, and you can upload it on needrom, so possibly some devs start working on it. You are welcome.
[Magisk] Didgeridoohan:
[MENTION=5188219]observingman[/MENTION] First of all, please don't post logs in plain text like that... It gets quite annoying to browse the thread, especially on a mobile. Attach it to your post instead.

About Xposed, it's probably best to head over to the Xposed forum for that. But I wouldn't hold any high hopes... It's not that stable on many devices. And you didn't need to wipe your device: https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc

Your installation of V4A looks like it's attempting to do a system install rather than as a Magisk module. That means it can't detect Magisk on your system and there's probably something wrong. Trying to do a clean install of Magisk again might be a good idea. If nothing else providing a Magisk log or magisk_debug.log might shed more light on the issue (remember, attach the file :p).

And if you continue having issues with Magisk or MagiskHide (SafetyNet):

https://www.didgeridoohan.com/magisk
[Magisk] 123lisa:
I fetched the recovery log directly after trying to install Magisk via TWRP, using the 16.4 beta version. I unfortunatly was unable to grab a logcat, cause my computer doesn´t seem to be able to see my phone during boot in adb (says waiting for device). Recovery log is in attachment.
[Magisk] KevMetal:
if you have stock rom with encryption flash zip to disable force encrypt ..search for noverity.zip
[Magisk] Pkt_Lnt:
Thanks for the log! I don't find anything in there, but my Magisk troubleshooting skills are not well turned to anything but a Nexus 6. Hopefully others, [MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=8340552]jenslody[/MENTION] or other currently active Magisk contributors can find something? Thank you.

Here are the other posts from [MENTION=8874274]123lisa[/MENTION] for troubleshooting reference.

https://xdaforums.com/showpost.php?p=76698914&postcount=25072

https://xdaforums.com/showpost.php?p=76708006&postcount=25087

https://xdaforums.com/showpost.php?p=76719276&postcount=25102
[Magisk] dieGeist:
Any new issues on Nexus 6p? No longer have a verified device. I did a complete reinstall of stock as well.
[Magisk] yochananmarqos:
Nope. Do you mean you're not passing SafetyNet or the status on the Play Store shows Uncertified?
[Magisk] Didgeridoohan:
You could check in /data/adb if there's a magisk_debug.log. If your device gets far enough in the boot process, Magisk should take care of creating the boot log itself...

To me it just sounds like there's an incompatibility between your device and Magisk at the moment. Mediatek devices are special... If you can't get it figured out, providing the stock boot image together with that recovery log might help towards finding out what's wrong.

---------- Post added at 05:57 ---------- Previous post was at 05:51 ----------

https://xdaforums.com/search/forum/5903?query=mido
[Magisk] teddy0209:
Xposed does not support miui under oreo. You can just restore the unpatched boot.img if you face any problem. No need to use mi flash...