yashsingh1/xdaforums huggingface dataset:
[Magisk] JensGoro:
If i had the Problem from OP:

(NOTE: Stock Samsung kernels do not support permissive, so the app won't let you toggle if Samsung rom detected!)

What i must do now? Flash a custom Kernel or what i have to do now?
[Magisk] borntobehappy:
LG G D855

Hello,

I can't install Magisk on my LG G3 D855 after unroot. It's always turning on boot then LED light is blue, then red. I can only turn on recovery

I Tried : Wipe, install phh’s SuperUser but it doesn't works. So I'll restaure cyanogen and wait for your help.

I use TWRP
[Magisk] Hjicons:
Tested Magisk with TD Pay (Canada). It's not working. Verified it working ok with fully unrooted phone. I am on stock 6.0.1, Nexus 6. Also Tangerine banking app gives warning about "unauthorized phone modifications".

I installed Magisk, Phh Magisk version from recovery, booted, installed Phh app from store and Magisk manager. Verified root and sellinux permission toggles off before testing.
[Magisk] Artim_96:
When you want to change SELinux to permissive, yes, you have to
[Magisk] keplenk:
Just need a few clarifications - are you saying you can use Android Pay with CM and you recently tried it with the latest version of Android Pay? The reason why I asked is that the instructions specifically said go to stock (Nexus 6p).

Also, are you saying that in CM - when you go to the Xposed installer (XposedInstaller_by_dvdandroid.apk) and by simply toggling on/off of the framework switch - you DO NOT need to reboot to take effect?
[Magisk] Chaud227:
I also get "unable to detect boot image" "error:1" when trying to flash Magisk v6 in TWRP. I'm on the Verizon Note 3 running 5.0 of1. I have tried it with both TWRP 3.0.2-1-hlte and TWRP 3.0.2-0-hltevzw-4.4. Bootloader on the Verizon Note 3 comes locked but I unlocked it prior to installing TWRP.

Figured I would give share my experience as well in the hopes of a solution being found.
[Magisk] goodtimes50:
I mentioned this before but didn't see any responses. Magisk breaks native gestures (double tap screen to wake, etc.) on the HTC 10. Just wondering if the devs are aware of this and have any idea how to fix it?
[Magisk] martyfender:
---------- Post added at 01:12 PM ---------- Previous post was at 01:08 PM ----------

[/COLOR]

Why are you hiding SafetyNet "Attest? For me it has no root check, just the SafetyNet check.
[Magisk] Eazart:
Can't install my other downloaded modules when I click Magisk just return to home screen and that's all latest manager 7 zip 18.1
[Magisk] garylawwd:
Is magisk manager installed to your external storage?

If yes make sure it is in internal storage
[Magisk] francwalter:
Did you ever solve this?

I got the same issue and asked it in that Mi A1 thread but yet without any answer.

I have the boot.img somewhere, but where to put it?

---------- Post added at 23:57 ---------- Previous post was at 23:20 ----------

I have the same issue and found your post here.

No backup was done it seems. But I cannot patch again the boot.img because there is no command for it in Magisk Manager (18.1) anymore when already patched.

What could I do?

I still have the boot.img and I could gzip it and put the hash in the filename, would that do the trick?
[Magisk] jcmm11:
The following assumes that:

You have an unrooted (stock) boot image currently named boot.img

You have busybox installed

You have a terminal emulator installed

Copy the boot.img to /data/local/ so you now have /data/local/boot.img

In the terminal emulator run the following, as root:

cd /data/local
mv boot.img stock_boot_$(sha1sum boot.img|cut -b-40).img
gzip -9 <file you just created with the mv command>

You should be left with a file named stock_boot_<sha1 string>.img.gz

Take that file and move it to /data/ so you have /data/stock_boot_<sha1 string>.img.gz

It should be owned by root:root and have permissions of 644 (rw- r-- r--)

Magisk should be able to find the backup now.
[Magisk] Rabbit308:
Hi all,

If I check logcat I see massive amounts of errors related to Magisk. I've spent a lot of time removing, reinstalling, researching etc. but I can't resolve the issues. Is there somewhere I can send a logcat to get some help?
[Magisk] Didgeridoohan:
You've been given a solution already, but I just wanted to address this. What do you mean? The option to patch a boot image is always there. Just press the "Install" button next to "Magisk is up to date", click "Install", and voila.

---------- Post added at 02:41 ---------- Previous post was at 02:38 ----------

Just attach it to a post here and I'm sure someone will take a look at it. Attach, mind you, not copy-paste...
[Magisk] Rabbit308:
Hi all,

I would be extremely grateful if anyone could help me sort out why my attached logcat is so full of warnings/errors related to magisk
[Magisk] DKWxda:
Magisk not installing module system apps

Hi guys, i have installed magisk 18.1 and im on pixle experience rom (pie) on redmi note 5.... When i install viper4android, it dosent show up in the app drawer and when i installed gboard themes mod, the themes dosent show up.... How ever when i installd sony music mod the app shows up and working properly... Please help....
[Magisk] Curious-Guy:
Magisk Hide not working

I have used MagiskHide on all apps except the two apps that I installed Magisk for (Battery charge limit & Camera Error fix). I even hid Magisk manager by re-installation and the cts profile & basic integrity check always return "True". But still, for some reason apps like Paytm are able to detect that my phone is rooted. What do I do now? :confused:
[Magisk] martyfender:
It is just plain crazy to hide all apps, as it can lead to system instability and break a lot of things. You should only be hiding apps that detect root and do not work because of it, such as Paytm.

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] heynando:
I didn't know about the trick "HIDE MAGISK MANAGER". That actually worked and the issue has been resolved. I finally have access to my bank account again. Thank you so much. So the miserable devs of the bank app (br.com.bradesco.next) have tuned the app to trigger root detection if an apk with an URL identical as the one used by Magisk-Manager is installed.

As a general rule of thing, Downgrading is, in most situations, the last card to play, because it has the potential to cause disruptive havoc and quite a high chance of actually being worse than just waiting for a patch it manual fix. I would have gone to Canary first.

Is there Xposed on 8.0? Well I'm not using it. Thought it died in Android 7. What's left of it is the magisk module but I never installed it and I'm not very informed about the subject because I can get by day-to-day tasks using the very old simple root.

Regarding the bank itself, I work in the business I'm a stockbroker and I have accounts of literally all of those mentioned by you. I agree Next's service is beyond horrible, their GUI is so poorly designed it looks deliberately made to be an internal joke cause I would be ashamed to be part of such a Dev team. The reason I still used them is because they were the first to accept Google Pay in Brazil. And I've been using G Pay since it's very infant days only because of them so let's give credit where it is due. Fortunately, they're no longer the only player and Google pay has different options. I already have a different account that accepts Google pay. I should say though that Considering this last episode, I've decide to no longer be their customer and cancel my account with them entirely.
[Magisk] Zico 10:
Thanks - tried the uninstall and reinstall route and I noticed an error in TWRP.

The error said it “failed to mount /system (structure needs cleaning)”.

I hadn’t noticed this when upgrading via the app.

Solution was to clean the /system partition using the e2fsck command (using the -f flag) in adb shell whilst in recovery.

Thanks for indirectly assisting!
[Magisk] dimscor:
Hello! Could you tell me how to do a clean flash?
[Magisk] Curious-Guy:
Ok so, it's working fine for Paytm but still not for MPL Pro, which is the app that made me go nuts in the first place by detecting root no matter what I did. Now, I even tried uninstalling all root apps and only keeping Magisk manager, but it still doesn't work. Also, I use no modules and don't even have BusyBox installed. So, my magisk installation is as clean as it can be. But that dang app is still able to identify root. Help please :(
[Magisk] guest4711:
0. Have a look into your device's forum and into the forum for your ROM.

1. Backup your current installation just in case something goes wrong.

2. Make sure you know all your account information/passwords

3. Boot into recovery

4. Wipe system, cache, dalvik/art, data (you will loose all your app settings and data!)

5. Flash your ROM

6. Flash g-apps if necessary for you

7. Flash Magisk

8. If not told otherwise wipe cache and dalvik/art again

9. On some ROMs it could be a good idea to perform the 1. start without sim card and wifi. So power down and eject the sim card.

10. Reboot. You should be greeted by setup screen.
[Magisk] pankozin:
Same bug with charging screen on 18.1 op6
[Magisk] habylab:
The charging screen issues have nothing to do with magisk, and are OnePlus' doing. It was fixed in 9.0.3 for the OP6, and OP broke it again in 9.0.4.
[Magisk] tezukaryoma:
On magisk 17.3 , dual apps/ parallel space apps can successfully hide and both the same app can work after hide. However all build after 17.3 the tricks wont work anymore, either one of the app cant hide, only 1 of the dual app can hide. Any solution? tried change other rom and try still same result.

Latest canary build solve this! kudos! Thank you!!
[Magisk] francwalter:
I really appreciate your help! Thanks.

But unfortunately this didnt change the error-toast. Still the backup seems missing.

With your commands I created this file (root.root, 644):

/data/stock_boot_547ec94e42ddd402657b4487efc7d6695130d369.img.gz
[Magisk] martyfender:
Have you tried rebooting after creating that file at the root of the /data/ folder?

I may be wrong, but I think Magisk detects the presence of that file at boot up.
[Magisk] OMeliante:
It still does not work. Used The command line adb uninstall com.topjohnwu.magisk and nothing...

Mi mix 3 here is only accepting magisk 17.3 with magisk manager 6.1.0...
[Magisk] jcmm11:
Need a copy of the full install Log to hopefully get a clue about what's happening.
[Magisk] kathynw:
unable to enable MAGSIK on Galaxy S4 (sprint SPH-L720)

SPH-L720 (Sprint U.S. Galaxy S4)

Here is the log from the magisk install fail (rooted with SuperSU):

Unable to install magisk v18 either through recommended (zip file) flashing via the Magisk manager or patching the boot.img file which was extracted from the lollipop 5.0.1 ROM used to flash the phone. When I had magisk flash the boot image file and re-flashed it back using ODIN it bootlooped. When I tried enabling Magisk manager using latest zip recommended option (rooted) it simply doesn't work (see log). I was rooted using SuperSU. [Also in addition, I have reinstalled android stock rom 4.4 and 5.0.1. about 10 times now with all the fails and now and now I am unable to enable boot to a custom bootloader TWRP, Philz, etc.... even via ADB. commands won't make custom boots start anymore. Don't know why. It worked before but now it stopped. ]

I'm sort of new doing all this stuff so if any one has any ideas, please explain clearly for a newb. thanks!
[Magisk] jcmm11:
First of all if you're rooted with SuperSU you will NOT be able to install Magisk untill you completely remove SuperSU. (I recommend osm0sis' unsu zip, followed by flashing a stock (unrooted) boot image)

Next, I'm not sure that's the entire log. If using TWRP go to Advanced|Save Log (it'll place the log into /sdcard/)

If using Magisk Manager there's an option to save the log before you exit or reboot.

The bad news is I don't do Samsung so I don't know the details of using Odin etc. Based on some things you said you may be better off just reflashing the entire OS (hopefully you either have a backup of your personal data or there's a way to flash it without losing your personal data, but again - I don't do Samsung)

Maybe just wait for someone more familiar with Samsung to weigh in before going any further.
[Magisk] DrLitte:
I was able to use Gpay for long time with Magisk. Thank you. Just 2 days ago Gpay detected my phone is rooted or modified. I have checked the safetynet and they are both green. I am using Android pie LOS 16.0 on mi5s. Anyone else having the same issue?
[Magisk] ryandanger:
I tried countless things and I think maybe the fix is to uninstall Google Pay and reinstall it and that may work
[Magisk] Pablo.x:
Had the same problem a week ago and I was able to solve it by updating to lastest magisk canary (there are some posts related to this, so use search if you need more info :good:) :highfive:
[Magisk] asmen5:
Some of mybangking Apps run well on canary build, after hiding magisk Manager in setting...

---------- Post added at 15:42 ---------- Previous post was at 15:39 ----------

This App still detracted root, while hiding magisk Manager in setting.... So strange..
[Magisk] francwalter:
Yes, I rebooted, no change. Still i get:

"Kein Original Backup vorhanden!"

The log in Magisk (in the Magisk menu) is empty after the attempt. I don't know where i could find another log file where there is logged that error.

---------- Post added at 09:59 ---------- Previous post was at 09:58 ----------

Where to find that?
[Magisk] daanishmodi:
I'm on Oreo 8.1.0. After flashing Magisk 18.1, the Magisk hide feature is not working. I even downgraded to Magisk 18.0, but even this is not working anymore. Nougat + Magisk 18.0 with Magisk Hide used to work flawless for me. Also, I tried flashing 17.3 (last stable update before 18.0) and now I have a weird problem where Magisk app is not available after I reboot. And now, no matter even if I am trying to flash 18.0/18.1 it is just not available in my app list.

I did not encountered any errors anytime while flashing different versions of Magisk via TRWP.

At the moment I'm without root on Oreo, but any help would be appreciated.

P.S: After flashing each Magisk version, I also flashed Magisk uninstaller before flashing to a different Magisk version. But however, for all the versions I flashed the latest 18.1 uninstaller. Can this cause such a problem? It worked couple of times, but since Magisk Hide was not working I thought to downgrade the version.
[Magisk] habylab:
Try latest Canary, as has been discussed a few times. It is stable for most and Magisk Hide is much improved.
[Magisk] nowster:
Just for information, what's the recommended way to obtain the logcat of a system crash when I'm driving the car and the phone reboots? (This is, of course, the only situation where it happens.)
[Magisk] Didgeridoohan:
There might be other things than Magisk that triggers the app:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

The installation log has to be saved just after installing. If you didn't, it's lost...

Try:

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager

Check /sys/fs/pstore/console-ramoops. It might show why it reboots.
[Magisk] daanishmodi:
Thank you [MENTION=4667597]Didgeridoohan[/MENTION] for pointing out the adb command (adb uninstall com.topjohnwu.magisk). I will look into it. Also someone just made a mention of Canary build, which I'm hearing for the first time, for enhanced Magisk Hide. I will give it a try because at the moment I'm unable to use few apps with Magisk 18.1 on Oreo 8.1.0.
[Magisk] RintSo:
working perfect on indonesia e-banking with magisk manager hiding
[Magisk] francwalter:
I investigated the code a bit by searching the error message and found: restore_fail in UninstallDialog.java then I found restore_imgs in utils.sh where I read that the SHA1 is read from /sbin/.magisk/config

I opened that file on my phone and found f71efd2d6133a1fd5fb91f739897171b06d6ba3b which is another sha1 than I build with these commands.

So I renamed that boot.img to stock_boot_f71efd2d6133a1fd5fb91f739897171b06d6ba3b.img.gz and now I am tempted to try again.

But I don't know if there is a risk now. If something went wrong and I built a img.gz from a wrong boot.img and let Magisk restore that, will it break my phone or will Magisk check it double before writing it back?

I fear that a bit (from utils.sh):

if [ -f $STOCKBOOT -a -b "$BOOTIMAGE" ]; then
flash_image $STOCKBOOT $BOOTIMAGE
return 0
fi
[Magisk] jenslody:
The TWRP logs are copied to /cache/recovery on reboot from recivery (at least on my device).

So there is a good chance the log is available after a reboot.

Last two logs are kept as far as I remember.
[Magisk] c3k:
did zip installer disable dm-verity and encryption by default?

for what I read, yes, but in TWRP for Samsung S8 exynos install guide installing a separate disabler zip it's a

required

step and I don't know why
[Magisk] FMXP:
New update for Fate/Grand Order (1.26.0 NA) seems to detect Magisk again. Running 18.1. Anyone else can confirm this?
[Magisk] martyfender:
Maybe try the latest Canary build released today?
[Magisk] jcmm11:
Rather than renaming the file (which means the sha1 string no longer corresponds to the boot image) I'd change the data in the config file.

Can't answer if you have the correct boot image or not. I'd assume that the string that Magisk has in the config file is probably from an older version of the boot file, which would explain the difference. Just triple check to make sure you have the correct image.
[Magisk] ang3l:
I recently updated my Xiaomi Mi Mix 2 to 10.2.2 via OTA which unrooted my device. I rooted it again and installed Magisk as usual, SafetyNet check is successful, however Google Pay won't work.

Any ideas what could be preventing the use of Google Pay?
[Magisk] FMXP:
False alarm! Strangely enough, rebooting the phone solved it. Not sure what happened, but it looks like for now 8.1 stable still hides from FGO. Might need to reboot the phone every time the app updates though.
[Magisk] martyfender:
Have you opened Magisk Manager settings and hid the Magisk Manager, then delete the app cache and data for Google Pay, or uninstall it and reinstall it, hide it in Magisk Hide, then launch it and set it up again?

I'm not sure, but MagiskHide Props Config Module could be useful also, to hide sensitive properties,

but the module author, [MENTION=4667597]Didgeridoohan[/MENTION] would be able to give a better answer than me, as I don't use, or need gpay on my tablets.
[Magisk] daanishmodi:
[MENTION=4667597]Didgeridoohan[/MENTION] The adb command perfectly worked and I'm again back on Magisk 18.1. This time I'm on latest Canary build, but still my company apps detect root and I'm unable to run them.

Should I use MagiskHide Props Module as well?

By the way, I'm on stock Oreo 8.1.0.
[Magisk] Didgeridoohan:
I don't use Gpay either, so I can't give any good advice on that, unfortunately... Some users have reported success by denying phone and sms permissions to Play Services, but that may cause a whole bunch of other issues.

There are a lot of users that have started having issues with Gpay even though they pass SafetyNet, so it is likely that something has been updated on Big-G's side. Someone just have to figure out what...

That's likely the intermittent MagiskHide failure bug in Magisk v18.0 and v18.1. MagiskHide has been comletely rewritten since, so the current Canary builds (right now, 18109) might work more reliably (with MagiskHide that is, there may be other bugs).

There are many different things that an app or service can look for and determine that your device is "compromised". Using MagiskHide and hiding the Magisk Manager are just two parts of that. If you haven't already, take a look here:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] francwalter:
I think the reason I have a different sha in the config is because the rooting did not success in the first try, when i did it.

I had to try several times till it worked, i just found in my notes that i made that time.

I changed the config file now, put the sha to the right one (547ec94e42ddd402657b4487efc7d6695130d369).

I hope this will work, will try later.

First a backup with TWRP.

By the way, a basic question:

Will TWRP be still present after the system update?

Thanks, frank
[Magisk] martyfender:
One thing I forgot to ask you to check, does your device show it is certified in the playstore, under playstore settings , about, play protection certification? It should say that the device is certified. Sometimes, for this to show certified, you must delete playstore cache and data and reboot. Then it can take some time for it to show up as certified.

I was able to force this a few weeks ago by uninstalling playstore updates, going back to the original for the device, then letting it update itself. Then that device showed it was certified. This is, of course, assuming you are passing safetynet as you stated.
[Magisk] Animesh Singh:
Can anybody guide me through this problem i have?

I had installed a broken magisk module which made my phone to be in a serious bootloop. I flashed the magisk Uninstaller from TWRP. Now no matter what, i cannot install magisk anymore. The installation is successful on TWRP but when I reboot to system i cannot see magisk. I also installed Magisk Manager apk to see if it is installed. But no luck. Any help would be appreciated. Thank you.
[Magisk] francwalter:
OK, I dared it after I did a TWRP backup.

I changed the config file to match the real sha1 hash from the boot.img and hit the button.

It worked that far. Magisk seemed to write back the boot.img.

Next thing (without reboot of course) I did was to try the system update, but this still failed :(

It downloads well, then it says it installs, but then it says it failed.

So I thougt I have to put back the patched_boot.img and ran it in Magisk:

Install Magisk > write the patched_boot.img to system and did a reboot.

Bang! Bootloop.

And TWRP is gone too :(

I could boot into TWRP with the version from CosmicDan and then from TWRP I installed the TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip, but since 10 minutes I can only see the androidone screen. Nothing happens anymore.

What doing?

EDIT: doing a fastboot boot patched_boot.img did it. The system is as before, nothing lost. Even I didnt need to restore the backup :)

OK, I lost TWRP, but I could reinstall it again (the version from CosmicDan 3.2.3-0)

The funny thing is, if I do now the Uninstall in Magisk and hit restore system, there is no error message. I have now the right stock_boot_f71efd...img.gz file with SHA1 as in the /sbin/.magisk/config. But this img.gz file is 21.8 MB and the img inside the gz is 64.0 MB! But my original boot.img is only 15.6 MB. So here is somehow something wrong.

And when I try to Update system, still it doesnt work and I have to do the same stuff (above) again to get working again.

I stop my attempts now for a later and maybe major system update...
[Magisk] c3k:
seems that:

KEEPVERITY try to be on

KEEPFORCEENCRYPT follow current status (no access to data => true)

someone can confirm?
[Magisk] Valeryan24:
Hi, to try solving my problem, I uninstalled both Magisk and Magisk Manager (through Manager and TWRP), so smartphone was set as unrooted with Root Verifier.

Then reinstalled the last Canary version of both : Manager 7.0.0 (189) + Magisk 18.2 (18109)

+ modules Busybox from osmOsis and MagiskHihe Props Config from Didgeridoohan

+ Hide Google Play Store, PokemonGo and Ingress Prime - no other app.

Test SafetyNet successful (both ctsProfile and basicIntegrity), test Root also (root undetected if I hide Root Verifier).

But both PokemonGo and Ingress still detect something and tell that my device is not compatible. I have no GPS modification nor spoofing app installed, I well cleared cache and datas for these apps. Normally no file nor folder named magisk in my storage.

Could it still remain some traces of old Magisk Manager 6, or is Magisk still not hiding enough because of PoGo progress to find it, or do I have another settings to modify - what logs could I send to help ? Thanks again :confused: