yashsingh1/xdaforums huggingface dataset:
[Magisk] hyborian:
Maybe try MagiskHide props Config module's Hide feature ... with a previous Magisk like 17.3, as it is having problems now with latest Magisk
[Magisk] Murrfk:
Can't get V.18 to install - Bootloops

I have been working at this for a week.

I have a HTC M8 with viperRom installed. I had a heck of a time getting Magisk to work, as I had problems finding a stock boot.img and understanding what I needed to do, but I finally was successful and got it working fine with Magisk 16.

However, I CANNOT figure out how to upgrade to v18. I initially had to upgrade TWRP to the latest version as the install would fail. With the latest TWRP it no longer fails, but the phone will go into bootloops.

I can install TWRP backups and get everything working, but I cannot get v18 installed and have the phone boot.

I seem to recall that I saw a post that might have mentioned problems with Aroma installer, which ViperRom uses?

I have used the magisk uninstaller, flashed a stock boot image from an old TWRP backup, wiped Cache, flashed v18 from twrp and I get bootloops. I will attach a recovery log from my phone in a subsequent post, when I find where it was stored. I hope I have provided enough information, but please let me know if there is something else needed.
[Magisk] strangeFace:
Hi, is there any chance for analysis by one of the developers? I think it's quite serious bug affecting many games.
[Magisk] Dims_Camper:
Sounds promising to me, I only tried using the module on v18 this far. Might try someday, thanks for the suggestion.
[Magisk] Murrfk:
Here is the log. I had to redo things and this did not lead to a bootloop but I had to reinstall viperom. When it installed magisk manager was missing.
[Magisk] hawki:
"Note 9 SM-N960

How to install Magisk on a Note 9 SM-N960W
[Magisk] martyfender:
Do you have twrp available for your device? If so, I would guess that would be the best way to install it. If you don't have twrp, then the patched boot.img may be the best, flashed in Odin.

I don't however have any Samsung devices to know for certain, though.
[Magisk] y2kbugleung:
With MagiskHide, these two banking apps can still detect my Pixel 3 XL is rooted:

https://play.google.com/store/apps/details?id=com.scb.breezebanking.hk

https://play.google.com/store/apps/details?id=com.hangseng.rbmobile

Excuse me, but should I report the problem here?

---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------

With MagiskHide, these two banking apps can still detect my Pixel 3 XL is rooted:

https://play.google.com/store/apps/details?id=com.scb.breezebanking.hk

https://play.google.com/store/apps/details?id=com.hangseng.rbmobile

Excuse me, but should I report the problem here?
[Magisk] firozpatel:
im on v18 and everything hides fine, i know this because some apps detect root but when hidden they start to work, only issue i have had is google pay not working, also one other app which is my car insurance app.

is it because i have magisk.zip file on my phone, and maybe the apps search for the name magisk?
[Magisk] y2kbugleung:
I have tried deleting all "magisk" related files, but the banking apps can still detect root.

Enabling "core only mode", the banking apps work.

Disabling "core only mode", even with no module installed, the banking apps don't work.
[Magisk] Didgeridoohan:
And have you tried installing the Manager apk manually (you'll find it on GitHub or in the Magisk zip)?

I was bored so I tested both of those apps. They both look for and detect root, yes. But... With the Magisk Manager hidden and the apps on the Hide list neither of them detected root on my device.

In other words: There's no general issue, it's something about your setup. It could of course be that your device is affected by the intermittent failures of MagiskHide that some are experiencing on Magisk v18. For that there's currently no fix (except downgrading Magisk).

---------- Post added at 10:34 ---------- Previous post was at 10:32 ----------

Posting the Canary debug Magisk logs from both of those variations could be interesting. Please do.
[Magisk] y2kbugleung:
Okay I have installed the latest development build.

With modules:

https://pastebin.com/e8K7e73U

Core-only mode:

https://pastebin.com/h17aW6wD

Thanks.
[Magisk] andersjohansson81:
Magisk hide doesn't work on the app carpay from playstore. Linage Oreo microG

Edit : started working again of itself...
[Magisk] Yeyo117:
You must download from the manufacturer site a customized firmware made specially for the tool, is a zip with various files with .fls extension.
[Magisk] Legza:
Hi all. I'm using Magisk 18.0 on TMO Z2 Force with stock Oreo rom.

The problem is that every 2-3 pays via GPay, it (GPay) stops working with the message like "you cannot use gpay for pay anymore" or smth like that. But magisk tells that safetynet is still passed, the GPay app itself opens normally and does not warn that phone is rooted etc. I stop GPay and clear its data - and it continues to work for 2-3 times more.

Can this be connected with Magisk or some other problem? How can i figure that out?

I have already tried: adding/removing GPay to hide list, disable root for all apps separately that ask to, and fully disable root access from magisk settings - and that made no sense, sometimes i could make 5-10 pays, but every time i get back gpay disallowing me to use it.
[Magisk] Suryo75:
Now, you dont even could logging in the app if you update the newest of app.
[Magisk] Dims_Camper:
that's sucks, really. I hope the devs could find workaround any time soon.
[Magisk] Murrfk:
I hadn't, so I redid everything and then installed MagiskManager.apk. The recovery log for this next attempt is attached. When I rebooted and opened the app, it said that Magisk was not installed.

I then tried again to install Magisk 18, but got an install error asking me to use a stock boot.img.
[Magisk] :
Any Permanent fix for gpay passing safetynet other than denying phone permission for Google play services? [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] andersjohansson81:
Hide started working on carpay again by itself ?
[Magisk] Didgeridoohan:
Doesn't show anything special unfortunately.

There was no need to post that twice...

And MagiskHide works perfectly for the app (I just tested it).

Edit: See my post from earlier today for possible issues with hiding root.

The recovery log with the error might have been more interesting...
[Magisk] Murrfk:
So I then tried to patch a stock Boot image, with Magisk 18. It worked and said it completed. I downloaded the stock backup and patched the stock boot.emmc.win file. Magisk log from today attached. I flashed the patched boot image. However, when I tried to boot, while it did not go into a repeated bootloop, the phone would not go past the HTC startup logo. I left it for over an hour and there was no change. So I rebooted into recovery, flashed just an old boot backup that has Magisk 16 installed, and the phone started after optimizing the apps.
[Magisk] Didgeridoohan:
When you say "stock" boot image, are you talking about the one that comes from your current ROM or the stock HTC ROM? From your previous posts I got the impression you might be using the wrong file, so I just wanted to make sure...

To clarify: by "stock boot image" we just mean a previously untouched boot.img file from the ROM you're currently using.
[Magisk] GoJo ^^:
Hi there, i've got a device on KK 4.4.4 and it can't be upgraded. How can i get magisk to work on it?
[Magisk] Badger50:
If I'm not mistaken, I think magisk only works on LP 5.0 and above.
[Magisk] Didgeridoohan:
The current Canary build should work down to Android 4.2 (with some restrictions), so it should just be a matter of following the instructions in the release thread. Of course: YMMV...
[Magisk] Badger50:
Yeah...I spoke to soon I think. As usual .

https://consumingtech.com/magisk-supersu-and-manager-for-android-4-4-4-kitkat/
[Magisk] GoJo ^^:
Thanks for letting me know, i'll try.. I guess? This is for a dual boot android/windows tablet, it'd be extremely complicated to restore, so.. feeling a bit unsafe about it ^^ Which restrictions?
[Magisk] sdamark:
I have to ask, Viper ROM has the option in aroma to select Magisk as the root method. Why not just reinstall the ROM? After you can just update through the Magisk app. I have an HTC10 and I've never had to patch a boot image to get Magisk working. Maybe I'm missing something? Just trying to help.
[Magisk] Max litcher:
Hello everyone I have a very strange problem it's about magisk modules when I installed them & reboot my phone they work properly but when I reboot my device a second time I don't find them like they're deleted so is this a root problem because I did uninstall magisk & reinstall it but it didn't work or it's about the rom and I need to reinstall the rom I am on AICP 14
[Magisk] Mycroft2046:
Feature Request

It would be really helpful if we had the option to enable magisk hide for all installed apps by default. Rather, we choose the apps that are exposed to Magisk superuser feature.
[Magisk] jenslody:
If you hide Magisk for more apps than necessary, you might make your system unstable or even break it completely.

Only very few apps need to be on the list.
[Magisk] meangreenie:
Installed latest magisk, 18 i think, from the magisk manager. Rebooting it wouldn't get past the boot logo.

Went into recovery and magisk uninstaller just gave error -1 i think, couldn't install either. Luckily had a backup of the stock boot image and installed v17.1 sucessfuly and the phone booted.

Leeco le pro 3, sd821, lollipop v23

Cheers.
[Magisk] tag68:
If I may translate the suggestion which seems you did not understand.

It should be possible to change the operating mode of Magisk from "Default is root, hidden is exception" to the opposite "Default is no root (hidden), apps that have root access are exception". Then it would be the effort of Magisk to prepare the system in the way that root is available, and the "root list" which would replace the "Hide List" in the "default-hidden-mode" should be kept small to avoid the unstable system. It should not be reversed for all users, it could be made an option whether root is default (current situation) or hidden is default (new option).

I have no idea how much effort this would make, but the idea is nice.
[Magisk] Paschfire:
Magisk/Magisk Manger version?

Magisk modules?

Logs?

Logcat?

Magisk logs?

Recovery logs?

ROM/Android version?

Any other useful information regarding your device setup?

Have you looked through the Announcement thread Link within the OP for possible troubleshooting?

Why report an issue at all, if you're not going to provide any useful information or logs to help the developer in solving such issues.

Follow the rules for submitting a proper bug report.
[Magisk] Mycroft2046:
Well, if I hide Magisk from an app, shouldn't it just act as if the system is unrooted? Why would hiding Magisk from an app break it?
[Magisk] martyfender:
You should only be hiding apps that detect root and therefore will not run because of that. The author of Magisk, [MENTION=4470081]topjohnwu[/MENTION] has stated not to do that also. Here is what he said on twitter:
[Magisk] tag68:
Magisk does a great effort hiding the su functionality from the system when a context switch to that app where Magisk gets hidden occurs, and reverts this when the context switch away from the app happens. If you hide too many apps, Magisk is always busy managing the context switches. The CPU load increases with the count of the apps in the Hide list. There is some CPU load level where the system gets unstable, and before it may get slow.
[Magisk] Didgeridoohan:
That's not quite what that user is asking for... The user is asking for a way to add all apps on the device to the Hide list, something that's not good and will likely cause system instabilities and break stuff. What you are talking about is a complete remake of how Magisk and MagiskHide currently works...

It's got to do with how MagiskHide works (currently, this might change of course but not in any near future). Here's kind of how it works...

Whenever you add an app to the Hide list it means that every time that app is started (either in foreground or background) MagiskHide will quickly kill the app (meaning it's a very bad idea to add system processes to the Hide list), unmount everything that is related to Magisk (/sbin and any Magisk modules), and then let the app start. If you have every app on your device on the Hide list there will be a lot of process killing and unmounting of a (possibly) large number of files and folders, leading to all sorts of weird behaviour and various failures.

So, don't add unnecessary stuff to the Hide list.
[Magisk] Jaymin.0.1910:
Slight correction: The apps aren't killed when they launch, instead their execution is stopped. Apps are killed only when MagiskHide itself launches and initializes hidelist.
[Magisk] Didgeridoohan:
True... Thank you, I'll see about correcting that for any future reference.
[Magisk] Mycroft2046:
Well, obviously, adding system apps to Magisk Hide list would spell disaster. Well, then how about a modification that, whenever a new app is installed, it will automatically prompt me whether I would like to add it to Magisk Hide list. Problem is, some of the stubborn banking apps check if Magisk is installed the moment it is installed. Once it detects Magisk, it will block the user from accessing the app, even if the app is added to Magisk Hide list. That poses a problem.
[Magisk] TacoShow:
I've got the exact same problem as this user I quoted. When I let Magisk Manager install the setup zip, I also get the message "setup failed", and I honestly don't know what I need to do to resolve it. It's been frustrating me for days. Would anyone please help me out in resolving it?

After flashing Magisk via TWRP and I reboot back into system, I open Magisk Manager, and Magisk Manager asks "Do you want to install Magisk-v18(18000).zip now?", at which I select "no thanks" (as I just flashed Magisk). So Magisk Manager doesn't initially detect that Magisk has already been flashed. Then I refresh Magisk Manager, after which Magisk Manager then detects Magisk, after which I get the message "Requires Additional Setup" to download the Magisk setup zip. I select "Yes", Magisk Manager starts to process, and then after a few seconds states "setup failed".

This is how the "setup failed" message looks like: https://drive.google.com/file/d/1fdMvHGUUc9oKSq7qFKflsNibUguILmFd/view?usp=sharing

My ROM is also LOS 16, my phone is the Motorola Moto G Titan, and I'm using emulated storage.

What I've done so far is:

- Repair the file system from within TWRP.

- Flash my ROM's boot.img file from within TWRP.

- Removing Magisk several times with unSu and the Magisk Remover zip, and reflashing Magisk afterwards.

And that's it. I hope that someone can help. The most frustrating part is that I can't figure out why Magisk Manager can't complete the setup. There's no error code given, and I've got no idea if there's some log it spits out.

To note: I've also got a Motorola Moto G Falcon, but getting Magisk to work on that has been without issue.
[Magisk] Didgeridoohan:
If that were true it would not make any difference with a prompt to add the app to the Hide list when it's installed. The app would already have detected Magisk by the time you had added it to the Hide list...

What banking app would that be, by the way?
[Magisk] TacoShow:
Just wanted to say that I've had a look at your troubleshooting guiding pertaining Magisk, but I didn't find anything about the problem I'm facing that I mentioned in the reply above yours.

Would you happen to be familiar with the "setup failed" problem in Magisk Manager that I described, and would you want to help me resolve it?
[Magisk] FlavioV:
A quick search suggests that the issue is on Magisk Manager itself. Try installing the latest version from here (it's the same link from the main thread). If you get an "App not installed" error uninstall the current Magisk Manager and launch the APK from your Downloads folder.

Once it's installed launch Magisk Manager and check for updates. If it doesn't help grab a log as mentioned in [MENTION=4667597]Didgeridoohan[/MENTION]'s troubleshoot guide and post it here.
[Magisk] GrayJack:
Any idea how to detect Lineage and Lineage-based (like AICP) ROMS using getprop?

Maybe using ro.build.software.version value or something like that?

Could you please give the parameter and value - need to block them all in a module.
[Magisk] Ps24u:
Nintendo Switch Online crashes at startup, always.

Even after hiding it with Magisk hide, clearing data, rebooting, etc. Any tip ?

SafetyNet passed ok, android 7.1.1, Magisk 18.0, Manager renamed.. Halp xD
[Magisk] varadinum:
Hi,I extracted it ( boot.img.lz4) tried to patch with Magisk, without success. Why is it? From stock firmware I have extracted the boot.img. Samsung Galaxy SM-A920F. Bootloader is unlocked.

Is not that the right file? Why can not this be unpacked ? Can someone help me? THANKS
[Magisk] heynando:
safetynet inconsistency, it passes and I can access bank applications just fine, but after an INDEFINITE period, let's just say 12 hours for example, safetynet fails and I have to reboot the system, after a simple reboot it starts working again, how can I pinpoint the thing that's making it fail after a while?

same happens with MAGISK HIDE, it stops working after a while, no definitive period, just a couple of hours after boot it simply stops hiding root from selected apps, then I have to uncheck & recheck the specific app to have Magisk hidden from it. And other times, unchecking & rechecking isn't enough, it only works after a system reboot.

anyone else?
[Magisk] Didgeridoohan:
The Magisk installation isn't complete, possibly because your recovery doesn't have access to /data.

Don't know what would cause it to fail though... Logcat?

Tested and MagiskHide works for the app. You might be experiencing the intermittent Hide failures, or there's something else about your setup that triggers the app.

Try extracting the file from lz4.

Known (but currently no fix):

https://github.com/topjohnwu/Magisk/issues/907
[Magisk] Ps24u:
Thanks for your reply. Did you test with the latest version of the app? Version 1.1.2 works flawlessly on the same setup. Only the latest (but mandatory) version 1.4.1 won't run here, with crash at startup. I'm starting to wonder if my device/ip or something else isn't blacklisted.
[Magisk] Didgeridoohan:
I used whatever version is currently in the Play store. Before adding it to the Hide list it did crash on start, but with the app on the list it opened without complaints.
[Magisk] GoJo ^^:
Nobody answered this post yet, please do.
[Magisk] habylab:
I have the same. I've rolled back to Magisk 17.3 and still get ctsProfile false, basicIntegrity true. Have you managed to fix it?
[Magisk] vikingalle:
The new updated DNB app (bank) detects root on my OnePlus 6. Any ideas how to make it work?
[Magisk] exquisite.nish:
Need Help Guys.

After successful updation of magisk to latest stable version while installing "AML", screen got freezed for more than 5 min so i had to shutdown forcefully. But after restart i lost all installed apps and everything., from everything i mean bot internal and external got formated. But that's not only the case. My device Mi A1 keep restarting automatically after few min of starting (it's not bootloop as device restarts to homescreen but freezes and restarts after few sec.). I tried to flash rom and kernal but got no luck. As "MTP" isn't working currently on my device (which i will get it repaired in a few days), is there any way to get device to working condition. I can provide logcat only after few days ('coz neither phone stay on for long to run any app nor mine charging port functioning properly).

Why this happened afterall? i thought Magisk work systemlessly still my whole system got formated. :(
[Magisk] Didgeridoohan:
The restrictions I was talking about is that on Android 4.2 you will only get root, not any of the other parts of Magisk (MagiskHide, modules and so on). Can't remember right now if that also applies to 4.4.4...

The only way to know for sure if it'll work on your dual boot setup is to try, but I would make sure to have a backup of anything important and be prepared for failure...
[Magisk] GoJo ^^:
It's too dangerous in my case. Hopefully somebody using another device with 4.4.4 can try. I want to switch to magisk for modules mostly.
[Magisk] Paresh18shah:
Magisk 18 problem..!l??

After installing any module need to reboot 2 time on

After 1st reboot all modules are gone

After 2nd reboot all modules are back but all settings are wiped?

I m frustrated of this

Any solution..!!
[Magisk] Ps24u:
Thanks for these extra details.

I used CatLog to check what could be wrong. The Nintendo app is looking for an existing:

/data/su.img

Which *IS* present on my system. After I renamed it, the app launched without issues, yaye!

Now my question is, is it normal to have this /data/su.img file on a Magisk install ?

I doubt it a lot, but please confirm. It might be remnants of when I had SuperSU installed..
[Magisk] jenslody:
It's definitely not part of the Magisk installation.

Edit:

corrected my statement, I should not write in car (not driving myself, but anyway).

I meant of course, that it is not part of Magisk.

Sorry for that.
[Magisk] guest4711:
Are you sure? I've never seen /data/su.img on any Magisk installation.

jfltexx:/ $ su
jfltexx:/ # ls -la /data/*.im*
-rw-r--r-- 1 root root 7517559 2018-10-25 23:08 /data/stock_boot_26fd4f8a0fb97ca321d2de885ecbb46c330f354c.img.gz
jfltexx:/ #
[Magisk] jenslody:
No, it's definitely not a part of Magisk (tha's what I wanted to write).

Don't know how that could happen, really sorry for that.

I corrected my original post.
[Magisk] guest4711:
Errare humanum est.

(Human beeings may be wrong, sometimes.) ;)
[Magisk] vikingalle:
Anyone?
[Magisk] Ps24u:
Thanks for confirming /data/su.img is NOT part of Magisk.

Could you check if data/stock_boot[md5].img.gz is, though?

While it seems harmless to leave it there, even if it was created by SuperSU, I'd like to know.
[Magisk] SHOOK1337:
here on huawei p10 lite my phone restarts all the time after installing magisk how to fix this
[Magisk] jenslody:
It's Magisks backup of the stock bootimage.
[Magisk] Ps24u:
Are you sure?

It has the same timestamp as my su.img had...

And didgeridoohan says on his site "If you're trying to find a stock boot image because you're moving from SuperSU to Magisk, there might be a backup of the stock boot image in /data (compressed) that you can use."

So I wonder if that isn't really remnant of SuperSU too (in which case where is Magisk backup stored..)
[Magisk] guest4711:
You did not describe what you have tried to get it working... Did you try

1. Hide root from it (MM->settings->Magisk Hide)?

2. Use MagiskHide Props Conf module (MM->settings->Downloads)

3. Hide MM itself (MM->settings->Repack MM)

Step 2 requires a reboot. Before testing each step you should clear cache (and probably data) of your banking app.

If this does not solve your problem, have a look at [MENTION=4667597]Didgeridoohan[/MENTION]'s fine FAQ:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] jenslody:
Yes, I'm sure, see the screenshot.

I never had SuperSU installed on this rom (and I know a little bit about Magisk internals, not much but ...).

By the way, it's not md5, but sha1 since several versions, if I remember correctly.
[Magisk] vikingalle:
Sorry about that!

I have tried 1 and 3 with no luck.

Can you explain how to do option 2?
[Magisk] guest4711:
Install the module in MagiskManager and reboot. Afterward you may fine tune it via terminal (entering su and then props) - see the description of the module in Download section of MagiskManager (and reboot after tuning).
[Magisk] vikingalle:
Thanks.

From what i have read, i need to do something in the option "improved hiding". But it says its disabled. When i try to select it, it says "Prop file modification currently disabled, since all relevant file values are "safe".