yashsingh1/xdaforums huggingface dataset:
[Magisk] wikiuse:
Yes. I checked in Magisk Manager and TWRP but I didn't find module had been istalled.

---------- Post added at 11:22 AM ---------- Previous post was at 11:17 AM ----------

I did check in Magisk Manager and TWRP, but I cannot find module have been installed

My device: A50 SM-A505F

Android 9.0

Kernel 4.14.62

Module was installed: ART( Android Run Time) in XDA dev
[Magisk] wangdaning:
Many kernels block the FDE.AI module. That is why you cannot install it. If you must use it you will need to find a kernel that does not block it.
[Magisk] pndwal:
THANK YOU for checking and editing your duplicated posts! :)

You may want to note that FDE.AI module is one of the few reportedly now causing SafetyNet check basicIntegrity failure, so if you want SafetyNet pass you will want to look for alternatives unless module has been fixed. :)

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post82166469 Kind regards, PW
[Magisk] mcgyver83:
I tried also renaming the boot.emmc.win into boot.img but I still have the error in repackaging of boot.img. (attached)

I pushed the disk icon but nothing in download folder :(
[Magisk] cnjax:
Or better yet he can get the app on play, pay few bucks and support the dev.
[Magisk] GROOVYJOSHCLARK:
I finally got the hide working and to display as a menu, but I had to enable/disable/enable like 5 times and close the app, swipe from recents, re-open MAGISK app fresh and enable/disable more times, then it finally popped up and working with the latest. Its working great now and hiding everything I need, so IDK if it was a "ME" issue, or an app issue, or a device issue, or what, but it definitely didnt popup on its own once I enabled it, not until I did the steps above.
[Magisk] Wolfcity:
Just for your information:

FDE.AI tripps safety net, at least in the stable Magisk build.I had to uninstall it.
[Magisk] wikiuse:
FDE.AI

yes. my device is A50(SM-A505F), i did install FDE.AI in magisk, but it show" the kernel blocked this module, please get better kernel"

What should I do?
[Magisk] vermy:
Hi. I'm trying to update Magisk on my rooted Essential PH-1. I rooted it using a modified boot image created by Magisk. It tells me there's an update available, and I tried the "Recommended" method but failed. Is there something obvious I am missing you can see from this? Thanks.
[Magisk] guest4711:
Ask the developer of this module. Have a look for other kernels in your device forum.

And enjoy the holidays.
[Magisk] Didgeridoohan:
That seems to be an issue with Samsung 6.0.1v

https://github.com/topjohnwu/Magisk/issues/2609

Why? No idea and so far it seems like nobody's figured it out...

No idea why you can't have logs... Since you can select the file to patch the Manager should have storage permission, so that shouldn't be it. Can't currently think of anything else.

From the screenshot it does look like we can make a qualified guess that it is the same issue as when installing from TWRP.

Solution? Don't know unfortunately.

From the given information, no. Much better if you can provide the installation log. That it "fails" might mean a variety of things.
[Magisk] wangdaning:
As I said before, many kernels block this module as it is easy for it to cause issues which then get blamed on the kernel. Use a kernel that does not block it, that is the only solution.
[Magisk] wikiuse:
So where can I find kernels?

A50 (SM-A505F)

Android 9

Kernels v.4.14.62
[Magisk] pndwal:
You need to check threads for your ROM, or ask there! This is Magisk General Support / Discussion thread. PW
[Magisk] ardhani:
Sir how to fix cts check failed in latest magisk stable and security patch april
[Magisk] Soumy1234:
Check if it's any of your modules. Disable all modules and check if SafetyNet passes then enable a couple of modules at a time and reboot to see which one causes the issue.
[Magisk] Didgeridoohan:
Absolutely first thing to check is if MagiskHide is enabled at all (and toggle it off and on again if it is). Since Magisk v20.4 it'll be disabled by default (on clean installs).

After that it will be time to look at other possible sources of error. More tips and troubleshooting here:

https://didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] ardhani:
Yes i have check for the first time i clean flash and flash magisk no installed module, but no luck, are its related to April security patch from Google?

---------- Post added at 05:08 AM ---------- Previous post was at 05:04 AM ----------

Okey sir thanks for your information, i'll try

---------- Post added at 05:44 AM ---------- Previous post was at 05:08 AM ----------
[Magisk] pndwal:
As long as you have basicIntegrity pass with no modules active and MagiskHide is switched on (and you've tried suggestion to toggle it on and off), Magisk Hide Props module with appropriate device fingerprint set up will likely fix it (for the moment).

Please let us know what Device and ROM you have as these will make a difference.

(And thanks for removing your duplicate post above. :) )PW
[Magisk] NeverTooYoung:
You guys, especially Didgeridoohan, certainly are patient with all of us. For that, and more, we are grateful.
[Magisk] ipdev:
[MENTION=4686381]mcgyver83[/MENTION]

Could you give a download link to the CM13.zip and the TWRP bootimage backup you made?

I would like to check the CM zip you are using to see if the boot image is buried in it. Unless it's some kind of odd OTA or odd CM port, it should contain it's own boot image.

Also curious if the TWRP backup image can be unpacked and repacked properly.

If there is a problem with your recovery, it might also affect the boot image backup you made(?).

Just a few questions that ran through my head as I was catching up on posts in the tread.

Could you try patching the TWRP backup boot image you have using Magisk Manager on a different device, if so do you get the same errors?

Cheers. :cowboy:
[Magisk] ardhani:
Yes sir thanks, its working now
[Magisk] jcmm11:
Try renaming the file to boot.img

The TWRP backup of a boot file is actually an img file

Edit: never mind. I see you already tried this
[Magisk] mcgyver83:
CM13:CyanogenMod 13 di PolishVodka[S Advance]

Boot.emmc.win:boot.emmc.win

recovery.log: recovery.log

I'm going to try with a newer smartphone :)

UPDATE: same error also on a smartphone already root with magisk :(
[Magisk] Didgeridoohan:
I tested patching that file and it fails with a seg fault, so it's definitely the boot image that's incompatible. [MENTION=4544860]osm0sis[/MENTION] any idea why?
[Magisk] Kantilo:
Hello, I installed TWRP, then magisk.zip to make TWRP permanent, but once LOS is installed, in the magisk manager it tells me that magisk is not installed, is that normal?

To upgrade magisk you just need to flash the zip with twrp each time?
[Magisk] osm0sis:
That's not an Android format boot.img, looks like a raw kernel binary, which makes sense since it's an old Samsung device. No way to support it, unfortunately.
[Magisk] CoOlSlY:
Just wondering... If on the next OTA update I decide I do the OTA (it will uninstall Magisk when the new boot.img will be applied from the OTA), could I relock the bootloader and call it "the fun is ending" because of Magisk not passing Safety Net anymore and that I use my phone with Google Pay A LOT. No data loss and no brick phone?
[Magisk] mewbow1:
(Deleted Post)
[Magisk] pndwal:
But the fun hasn't ended yet! SafetyNet is still passing (for now), and SQLite method for G Pay is still working PW
[Magisk] CoOlSlY:
I've been out of the loop for a while but since my march update, Safety Net is not longer passing on my 4XL, any guidance on article or thread to have my Safety Net to pass again...?
[Magisk] zgfg:
Please read the posts during the last week. Makes no sense that others write/repeat same things that are already written, for everybody who was 'out of the loop'. TG, we are on XDA and not on Telegram

Make sure that Magisk Hide is enabled. Instead of SafetyPatch, use Magisk Hide Props Config. If SafetyNet still failing, disable all other modules and inspect one by one which is errant
[Magisk] CoOlSlY:
With all due respect, I read a few of the last pages, but my last page read at first was something like 2070 which was ~1700 pages out so while I read a few pages and also made a thread search, from my reading (and even on Twitter), it was "the fun ends" so thought it was over. Thank's for helping, i'll give a check on what you suggested.
[Magisk] zgfg:
Generally, stock ROMs with Gapps built in, hence being certified by Google, should all pass. You just need to make sure Magisk Hide is enabled (since being disabled in the latest Magisk Manager Canary build)

It means, SafetyNet will pass with all modules being disabled. Then enable one module by one, and if particular one causes SafetyNet to fail (e.g. Riru + EdXposed) ask in the module's thread, find an alternative module or live without

For custom ROMs (or stock ROMs without built-in Gapps - usually for devices sold only in China ), in addition to Magisk Hide, you need to use Magisk Hide Props Config module to fake the device fingerprint - to present them to Google as being the certified stock ones.

With that and all modules disabled, it should pass. Then investigatw one module by one...

If something is unclear you can search for, e.g. for Props Config,, SafetPatch or Riru if it was already discussed here
[Magisk] Tombab:
I'm running LOS 16 + Magisk v20.3 and I need to toggle magiskhide off and on each time my phone reboots due to bug or crash of some kind. For some reason phone crash disables Magisk and my banking app locks up because it detects root even if safetynet tests pass OK and everything should be peechy. Few times I have forgot to do this and then I have to clear banking app cache and set it up from scrach to get it working again, pain.
[Magisk] CoOlSlY:
Thank's a lot... As soon as I read your first message I went ahead and disabled everything and it worked... Brain fart... Basic stuff :| I had disabled everything except Riru and EdXposed ("beginer" mistake) and EdXposed .is the culprit, i'll check, Riru core works but as soon as I enable EdXposed it fails... I'll check this out, thanx again
[Magisk] pndwal:
In a nutshell:

Google introduced new hardware key attestation which fails CTS profile due to unlocked bootloader. No spoofing etc can bypass this, but after a few days they switched it off again, ostensibly to allow time for some OEMs to fix badly implemented key attestation, so CTS is passing for now, but the concesus is that Google will turn it on again to provide CTS that app developers can rely on "to know that their code runs in an unmodified environment, whose behavior is predictable."

Since then, Google introduced further SafetyNet checks, this time basicIntegrity failing due to several Magisk modules and Xposed framework. Solutions are found in recent pages for failures due to SafetyPatch module and EDXposed, and removing other mods fixes SafetyNet failure.

Make use of our 'borrowed time'! PW
[Magisk] mcgyver83:
Yes it is an old Samsung S advance i9070.

Thank you guys!
[Magisk] °Washy:
My magisk doesnt load his version, update, modules and anything regarding It. Root btw works well so it's very strange. I tryed to unistall It fully and dirty flash my rom before installing It again but with no success. I didn't find something similar to my issue so Im very bored. Any ideas?
[Magisk] demonoidmaster:
If he doesn't mind having MM get auto removed when opening the repacked one then he could do that, however if it detects at boot and does weird things then he should do the alternate thing i said, open the magisk zip in RAR app (available on play store) , go to common and delete the magisk apk, itll autorezip it, then whenever he needs to flash magisk it wont install the manager upon reboot. Best way to avoid having the default manager installed
[Magisk] wikiuse:
After uninstall Magisk and unroot

After uninstall Magisk, unroot and flash ROM A50(SM-A505F), so I opened Samsung Health it was blocked beacause: "it found Rom was change". What should I do?
[Magisk] bunklung:
Just an FYI: I restored images, and was able to pull the April security update!

I did NOT check for updates first. I restored the image, THEN i checked for the update. Normally I would do the other way around: Check, it breaks, I restore, I re-check, etc.

On my second phone, I did not have the restore image present. So I had to manually build it in /data/magisk_backup_55fcd5ec203b16ceb559848918a1fbc85853f434/boot.img.gz and /sbin/.magisk/config

https://xdaforums.com/showpost.php?p=81712377&postcount=38238

I am a bit jolly I don't have to manually patch the boot images and flash the entire image. It's so much more convenient and safer (opinion) to use the OTA process. I don't know how long this will last, but I suspect 20.4 might have fixed this OTA process.
[Magisk] Ch3vr0n:
Yeah I checked first, then restored and checked again. Didn't work. Guess I'll have to wait another couple of weeks [emoji4]. Not going to reflash March image just to test this. And no 20.4 didn't fix this procedure
[Magisk] Didgeridoohan:
I don't do Samsung, but I would strongly suspect that would be caused by the tripped Knox e-fuse. As far as I know there's nothing that can be done about that...
[Magisk] rpgdev:
Is there a good tutorial somewhere on how to make magisk modules? I need a little bit more than the official guide. More especifically, is there a particular way in which to zip the module? I made a very simple module (modified an existing one) but when I try to install it Magisk Manager complains that "this zip is not a magisk module" :/
[Magisk] Didgeridoohan:
Have you made sure to follow the instructions properly, with the correct update-binary and updater-script placed in the proper location in the zip? If you have, this might be your problem: https://didgeridoohan.com/magisk/Magisk#hn_Zip_is_not_a_Magisk_module
[Magisk] rpgdev:
I feel like an idiot now lol. Yeah that was it thanks! I was able to install it successfully (or so it seems) but I can't see it in the modules screen and it did not seem to have the expected effect, are they all supposed to show up in the modules screen?
[Magisk] Didgeridoohan:
If it's a Magisk module it would show up in the modules section. You sure it installed correctly? What does the install log show?
[Magisk] rpgdev:
Generic info messages and at the end "extracting module files\n setting permissions\n done"
[Magisk] Didgeridoohan:
Is that what's printed on the installation screen, or the info from the log that you save by pressing the disc icon?

Edit: posting the relevant logs is always a good idea...
[Magisk] rpgdev:
The actual log says something very different lol (attached). I kind of know what happened but, I put a path to a file in the REPLACE but it seems like it expects a directory (the module I modified pointed to a file). Not sure if putting the parent directory of this file would be appropriate.

- Copying zip to temp directory - Installing OREO_MAGISK_LGV35_Remove_Cliptray-3.zip update-binary: line 54: get_outfd: not found - Current boot slot: _a - Device is system-as-root Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip creating: common/ inflating: common/system.prop inflating: common/post-fs-data.sh inflating: common/service.sh inflating: config.sh inflating: module.prop ******************************* Disable LG ClipTray ******************************* ****************************** Powered by Magisk (@topjohnwu) ****************************** update-binary: line 101: mount_magisk_img: not found - Extracting module files Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip creating: system/ creating: system/etc/ creating: system/etc/permissions/ inflating: system/etc/permissions/com.lge.software.cliptray.xml touch: /dev/tmp/magisk_img/DisableLGClipTray/system/etc/permissions/com.lge.software.cliptray.xml/.replace: Not a directory update-binary: line 610: can't create /dev/tmp/magisk_img/DisableLGClipTray/system/etc/permissions/com.lge.software.cliptray.xml/.replace: nonexistent directory chmod: /dev/tmp/magisk_img/DisableLGClipTray/system/etc/permissions/com.lge.software.cliptray.xml/.replace: Not a directory - Setting permissions update-binary: line 147: unmount_magisk_img: not found - Done

Edit: XDA app didn't allow me to upload the log.
[Magisk] BillGoss:
Zip the file first and then you will be able to upload it.
[Magisk] Didgeridoohan:
I only had to scroll to this:

mount_magisk_img

To know that the module you're basing this on is very outdated and the update-binary from that module doesn't work with current Magisk releases. You might get away with simply replacing the update-binary with the current module_installer.sh (see the guide you linked earlier).
[Magisk] rpgdev:
This worked, thank you! And the module worked too. How can I get it into the repo? Have to post it here first I guess?
[Magisk] Didgeridoohan:
As it so happens, that information is also available in the guide you previously linked:

https://topjohnwu.github.io/Magisk/guides.html#submit-modules
[Magisk] wikiuse:
reply

Thank for replying! I did change value in build.prop from 0x1 to 0x0, rebooted and wipe data/ factory reset before unroot. How to fix Know forever?
[Magisk] physwizz:
Please help

I have a Samsung Galaxy A205YN and I'm not able to restore my system partition using TWRP.

Data and boot are fine but not system.

Also /system is ro from inside the Rom but rw from inside TWRP.

Does anyone know of a fix?
[Magisk] yannahzinha:
So it happens because Zenfone 2 needs a signed version of Magisk. Without it you end in a bootlooping. I have one and stopped on 17.3 version because it was the last version released by the dev of the ROM I used.

Never found info about how to sign it...
[Magisk] slayerking:
Wrong! Yes you need the verified boot signer, But! There was problem with x86 the new 20.4 fixes it. If you have a zenfone 2 don't use 20.2 or 20.3.
[Magisk] uudruid74:
Curious if anyone has problems with Netflix since updating to 20.4? It says my device is no longer compatible. It's a OnePlus 7 Pro.
[Magisk] kacarot:
Activate in settings "magisk hide" enter and you will see your list of apps, open 3-point menu and activate system apps, Netflix will appear in the list, mark it and update Netflix in the play store ...

Enviado desde mi GM1913 mediante Tapatalk
[Magisk] uudruid74:
Yeah I did all that. I even his Magisk from the stub and had it rename itself. Apparently, clearing storage won't help. I had to uninstall updates and then upgrade again. That finally did it. No idea. Thanks though
[Magisk] kacarot:
Yes, I also had to completely clean the memories of the apk, update and then dial in menu magisk hide .... there must be internal changes in magisk that conflict with Netflix as op7pro is an app embedded in system ...

Greetings

Enviado desde mi GM1913 mediante Tapatalk
[Magisk] Bringer1:
After flashing Magisk 20.4 to my oneplus7pro with Stock Rom, I have no gsm Signal (both sim cards). With 20.3 there is no problem.
[Magisk] kacarot:
Do you have twrp There is q update twrp for magisk 20.4 ...

Enviado desde mi GM1913 mediante Tapatalk
[Magisk] Didgeridoohan:
Like I said, as far as I know there's nothing to be done. Can't be reverted once tripped.

That doesn't sound like a Magisk issue. Magisk has nothing to do with TWRP... You should rather ask for assistance in your device's forum.

Have you made sure MagiskHide is enabled (and working, do you pass SafetyNet)? From v20.4 it'll be disabled by default.

Edit: nevermind. Just saw you had gotten it fixed... (Hadn't refreshed my browser).
[Magisk] physwizz:
When magisk roots the device should it make /system rw?
[Magisk] zgfg:
If you have SAR with read only System, you can only make systemless changes to /sxstem
[Magisk] physwizz:
How?
[Magisk] Bringer1:
Yes. Latest twrp is installed and i use it to Flash the Rom and magisk. Ok, I will have a Look for the Update twrp
[Magisk] guest4711:
Knox could not be fixed without replacing some hardware. If knox is triggered a fuse is blown away... It"s by design a point of no return.
[Magisk] ibrokemypie:
are you running either cf supersu with suhide or phh superuser with hidesu?
[Magisk] WeirdSoup:
Hey guys, which one is better(at present), supersu + suhide or phh + hidesu? (assume that xposed v86.6 is installed)
[Magisk] Didgeridoohan:
I had the same problem with bootloop and System UI FC on my Nexus 6.

Had to uninstall Magisk, flash system (for you it'd be vendor image as well) and boot image, wipe cache and boot a clean system before I could successfully flash Magisk and phh's superuser.
[Magisk] Tkbf:
Yes, you are right.

BTW as topjohnwu said a few posts before, he is currently working on magisk version hidesu which will be compatable with magisk manager 2.0.
[Magisk] ryaniskira:
Tried that already, flashed boot, vendor, and system, uninstalled Magisk, reflashed Magisk, and same issue. Luckily I make regular TWRP backups so not much of an issue, and I still have the working Magisk V6 zip and PHH on my PC so I reflashed those for now.
[Magisk] Didgeridoohan:
The key point for me was booting a clean system once before flashing Magisk. Until I did that nothing worked. You don't mention anything about that, so I just want to make sure...

I'm gonna set up my wife's 6P with Magisk in a couple of days, so if you haven't managed to solve it by then I might have something to report. :)
[Magisk] daleski75:
You don't need xposed but you need Magisk of course with phh root and make sure there are no su binaries under xbin, bin and bi SuperSU folders either or it will not work.
[Magisk] ibrokemypie:
If you are using 86.6 then you will not be able to pass safetynet without disabling xposed and rebooting first. If that is finethen either, otherwise try supersu + suhide + xxposed 86.2. currently gets around safetynet without anything needing disabling or any restarts.

[edit] sorry, mixed up, didnt realise 86.6 was the new one.

supersu + suhide is not opensource and not built for use with magisk, however phh + hidesu is both opensource and built for magisk, although hidesu is still very experimental.
[Magisk] WeirdSoup:
Please read topjohnwu's updated Xposed thread OP: (http://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268 )

Actually I didn't tried it yet, because now I'm using the phh. So my question is, can I use phh's hidesu for the same purpose, or should I move to supersu to hide root & xposed.
[Magisk] edale1:
Chainfire's suhide requires android 6 or better.

My LG K7 runs Android 5.11.

Does anyone know a working SaftyNet bypass for Android 5.11?
[Magisk] WeirdSoup:
Did you try the phh's hidesu?

http://xdaforums.com/showpost.php?p=68969947&postcount=1063
[Magisk] ibrokemypie:
afaict phh's hidesu does not hide xposed from safetynet, going back to chainfire for the moment
[Magisk] CrazyCypher:
I am geeting stuck because I mounted SystemUI through Magisk, now how can I disable this? In TWRP there is no magisk folder in root directory so I cannot delete it. What can I do? I cannot get to Magisk Manager to disable it
[Magisk] topjohnwu:
How about this, will this reduce the hate lately ;)?

Magisk hide based on phh's hide, it should hide all magisk mods, should be able to hide on both phh's root and SuperSU without additional configuration.

As I stated in the announcement, the old root toggle is depreciated, THIS IS the better solution.

(Xposed is still a no go, it requires Zygote proxying, and currently only suhide does it, sorry)
[Magisk] SpasilliumNexus:
Mount-Magisk: http://xdaforums.com/apps/magisk/collection-magisk-modules-t3445257
[Magisk] Turbopuschel:
I disabled the phh su module and rebooted. Now when I want to open Magisk Manager it force-closes itself instantly. Is there a way to enable the su module again?
[Magisk] Voltusss:
Can anybody help..

When i am flash magisk the proses success then flash super magisk the process error.

It say update process ended with error 1

Any solution?
[Magisk] CrazyCypher:
Thanks man! You saved my life! :)

EDIT: It mounts magisk folder, but there is no auto_mount file inside so I could delete it! :( What to do?
[Magisk] soder:
Am I blind? How do I turn of root in the new manager? I've update everything..

/Söder