yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
That basic integrity passes means that MagiskHide is working. In that case, CTS failing is usually because of using a custom ROM without a certified device fingerprint.

More on that here:

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

And here:

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

The update notification has been a little unreliable from time to time... It will always do a check when opening the Manager though.

Possibly:

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

In any case, logs would be needed...
[Magisk] secondhand2:
Installing Magisk from TWRP quirk on an LG V20

Hi

I haven't read the thread in too much detail so maybe I missed something...but maybe someone will find this useful. I thought Magisk needed to be installed with the ROM from TWRP before rebooting to system, but in this case it doesn't appear so...

I have the latest TWRP (TWRP 3.2.3-4: 2018-10-18) for the LG V20 US996 unlocked version and was reinstalling Oreo (version 20f) along with the 18.1 version of Magisk. Both Oreo and Magisk installed properly from TWRP - both saying done or completed without errors.

But booting back into system, Magisk Manager was not installed. I retried twice with the same results.

Previously I had installed Oreo (20F) with Magisk 18.0 and the mk2000 Kernel [STOCK] available on the LG v20 forum..

When reinstalling Oreo and Magisk 18.1 I had done a data format and a wipe of dalvik, data, cache...

Not wanting to reinstall a third time I installed the Magisk Manager apk to see if it would find the Magisk I installed from TWRP but although the Manager 7.0 installed it had a red x where Magisk 18.1 should have been listed in the Magisk Manager.

I went back into TWRP and only reinstalled Magisk 18.1 before rebooting into system. I was surprised to see that Magisk

Manager now listed Magisk 18.1 and Magisk Manager v7.0.0 both installed so I am assuming all is well.

Does Magisk 18.1 need to be installed at the same time as the ROM from TWRP before rebooting to system?

Thanks
[Magisk] generics01:
I updatep my magisk to the latest and after my phone hangs on the logo and stop e.

I updated my asus zenfone 3 max zc553kl to the latest magisk 18.o after it stops at the asus logo.. Its been almost 2 months now of looking some possible thread but cant find one
[Magisk] jcmm11:
No, you can boot to system and use the phone for days/weeks/months before installing Magisk. As long as you have a stock (meaning unrooted) boot image (or one rooted via Magisk) you can install Magisk.

Most people install Magisk at the same time they upgrade/install a ROM but it's not a requirement.
[Magisk] DroidJP:
I noticed in magisk 18.1 it no longer installs the magisk manager after flashing magisk.

This is the result of magisk.apk fails to copy from cache to data but copies the rest just fine though.

To get around this, simply extract the magisk apk from zip and install manually and you now have root.Hope this helps anyone running into this issue.
[Magisk] Rattor:
I have magisk installed on a tablet and I can't seem to find the button in magisk manager to actually update magisk. The only button is to update magisk manager, which if I do now tells me I can't open it because it's an the version of manager is not compatible with my installed version of magisk. Any help?
[Magisk] FlavioV:
This happened to me in older releases as well. I always keep the latest Magisk Manager APK saved just in case.

That's also mentioned in the installation instructions from the announcement thread:
[Magisk] 135Shadowsoul:
Hello every1,

i just tryed to install magisk on my very old Asus MeMoPad 10 (ME301T) with OmniRom (4.4.4), as magisk v18.1 should be compatible with android version down to 4.2. but installation failed :(

***
* Magisk v18.1 installer
***
- Mounting /system, /vendor
! Cannot mount /system
- Unmounting Partitions
E: Error executing updater binary in zip 'path_to.zip'
Error flashing zip 'path_to.zip'

Any1 an idea what the problem is and how to fix?

Thanks for any helpful answer :)
[Magisk] Didgeridoohan:
If that's from when trying to install through TWRP I would make a guess that the TWRP you have is too old and can't handle the installation scripts. If so, try using the patched boot image method instead.
[Magisk] 135Shadowsoul:
i think it should? its a version 2.8 TWRP i installed omnirom, gapps and superSU with (fully unrooted superSU before flashing magisk)

can you give me a short hint, how to use the menthod you mentioned?
[Magisk] guest4711:
Did you uncheck "mount /system" in TWRP before trying to flash?
[Magisk] 135Shadowsoul:
it was uncheckt by default... i checked it and installation worked. i hope tab will still run after installation :D
[Magisk] tinuthir:
Understood, and I've read up on that, but we're talking an official LineageOS build that always had a clean CTS bill of health. And I'm not aware of any changes to LineageOS regarding any device fingerprints.

That said, I'm working with changing the device fingerprint anyway - no stone left unturned =)
[Magisk] Didgeridoohan:
TWRP 2.8 might very well have issues with the Magisk installation scripts. If the device boots and everything is installed now that you mounted /system manually then things should be fine. I've seen reports of things not always being so fine when using older TWRP versions though...
[Magisk] X0LARIUM:
Here's my reply to your suggestions:

1) Eventually I will have to.

2) Tried it. Stuck in a boot loop. Had to uninstall SU through TWRP

3) I have done it already. My screenshots say it all don't they.

4) I have given up on Magisk. I don't want to repeat what I think it really is but you get the point.

Point number 3- I would love to, but like I said, it slows my phone to a halt where I can barely open one window. And I am tried of the endless cycles of refresh, remove and reboot.

If the log files are stored somewhere on the system when the app itself is uninstalled, do let me know. Will be more than happy to share it here.

As a polite member here suggested (unlike other A holes who think they rule the internet), I checked the 'Root Access' hidden somewhere dug deep in the endless Settings menu, but couldn't find this option.

I am using a Nexus 6P - Latest AOSP Android Pie ROM.

Edit 3: Oh and yes, it stops the playstore download at 99%. You are welcome.
[Magisk] Didgeridoohan:
Hm... If I remember correctly, official builds of LineageOS have a policy not to mess with SafetyNet. Can't say what changed...

Edit: Yup... https://www.lineageos.org/Safetynet/
[Magisk] tinuthir:
Yeah, but it used to just work with MagiskHide, that's all I needed. But no more...
[Magisk] Coumodo:
Didn't work...

also tried

- toggle hide Magisk Manager apk

- redone MagiskHide Props Config modul

- toggle Paypal/gpay hide options

all other typical magisk critical apps are ok.

only Gpay detect the rooted device and won't let me add payment methodes:(

last week Gpay worked flawless... :confused:

OOS 9.0.12

Magisk 18.1

Magisk Manager 7

MagiskHide Props Config modul v44

ctsProfile: true

basicIntegrity: true
[Magisk] 135Shadowsoul:
i checked /system as mount, and installation went through. but now im bootlooping :(
[Magisk] Didgeridoohan:
That's what I was afraid was going to happen... Try reflashing the stock boot image and if that doesn't work the system image or a dirty flash of the ROM (worst case a complete wipe). After that you can continue trying with the patched boot image method. It's described in the official docs: https://topjohnwu.github.io/Magisk/
[Magisk] simone.a:
Can't disable Core Only Mode

Hi, I have an issue. On my phone, Magisk is always in Core Only Mode: whenever I try to disable it from settings, after the reboot Magisk comes again with that on (and I think this is why I can't install any modules). What's the problem? :confused:
[Magisk] guest4711:
To get it working again you could flash the saved boot image (/data/stock_boot_...) or the magisk uninstaller (which does the same and a little bit more).

But to help development it would be good to have some logs...
[Magisk] Didgeridoohan:
[MENTION=5097461]X0LARIUM[/MENTION] A couple of pointers:

Screentshots aren't logs. Despite everything you seem like you actually do want help, and without logs it is going to be impossible for anyone to help.

I've tried to help you on several occasions and have in at least two posts linked you to my guide on how to provide details and logs. Don't know why you keep ignoring it...

You're still trying to insult those who have been trying to help you. I'm curious why you feel that this is a good strategy?

---------- Post added at 12:31 ---------- Previous post was at 12:26 ----------

Check in /cache for a file named .disable_magisk and delete it if it's there. Mind the leading dot, that means it's a hidden file so you'll have to activate the option to view hidden files in your file explorer.
[Magisk] 135Shadowsoul:
uninstaller did not work either.

i am no going to clean install a CM build i used before and try again and then try to use the link to magisk docs

im so sorry that im too late to get any logs. but if it fails again ill try to provide as much information as possible

edit: the flashable zip of the CM rom does only contain a "boot.blob" and no "boot.img"
[Magisk] tinuthir:
Eureka! It worked - changing the device fingerprint was exactly the missing link in the chain. I deleted Play Store data for good measure, and now everything is fine again.

1. Play Store says the device is certified

2. Play Store finds Netflix (always a good test)

3. cts Profile check passes

I'll try Google Pay at my soonest convenience, but I'm excited! Thanks for your help, [MENTION=4667597]Didgeridoohan[/MENTION] :)

I'll leave this here: The difference between a week ago and right now may be that now, for the first time, I have a device with a newer Security Patch Version that was ever officially available for my phone, bullhead (Nexus 5X) - that might have been the thing that triggered SafetyNet and made the Device Fingerprint necessary in the first place.

I love an active dev community :highfive:
[Magisk] wurstherpes:
Reset my phone today. Pushtan + Magisk 18.1 and it says the mobile phone is rooted.

Samsung S7 Edge LineageOS 16.

It worked properly until yesterday.
[Magisk] Didgeridoohan:
You have the app on the Hide list and have hidden the Magisk Manager? Usually that is all that is needed...

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

---------- Post added at 13:18 ---------- Previous post was at 13:14 ----------

With Gpay, some have had success by denying phone permissions to Google Play Services. You could give that a try...
[Magisk] wurstherpes:
Yes I have. It worked all the time. I don't think it's going on since the update 18.1.
[Magisk] Didgeridoohan:
And MagiskHide is actually working (that's always the first thing you should check)? If it doesn't, try toggling MagiskHide off and on. For more things to try, check the link I posted.
[Magisk] guest4711:
The newer images contain some dumps which are restored by installer, not single files. So I'd give it a try...
[Magisk] simone.a:
Nothing changed. I deleted .disable_magisk, rebooted, unchecked Core Mode Only and rebooted again. Magisk is still on Core Mode Only and I can't install any module yet.
[Magisk] Didgeridoohan:
All you need to do is to delete the file and reboot, nothing else. Do you have any module or boot script installed that could be creating the file on boot?
[Magisk] 135Shadowsoul:
sorry, i dont understand that.

i am currently on a clean installed, nearly nothing done CM11 rom on my tablet (see signature).

but as i said, there is no boot.img file in the install zip for rom, only the boot.blob
[Magisk] simone.a:
I've done it, but nothing changes, after these two steps the file is still there. No modules installed, I don't know about boot script (I don't neither know where to look for it). If it could be useful, I can share the install log of a sample module.
[Magisk] wurstherpes:
Apparently, Hide doesn't work properly. I'm done the checklist. The pushtan does not work.

At home I will reinstall my phone and see if it goes then.

I think but the same.
[Magisk] Didgeridoohan:
Check /data/adb/post-fs-data.d and service.d. If there are scripts there, open them up and see if there's anything about /cache/.disable_magisk in there. And I should have asked you this before, but you should also upload a Magisk log (preferably with a Canary build installed). Details here: https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] jcmm11:
It's probably the blob file renamed. No matter - I assume you have TWRP. Just backup the boot partition with TWRP then rename the backup that was created from a .win file to a .img file and you'll have a copy of the boot.img
[Magisk] guest4711:
Either you flash /data/stock_boot_*.img (the backup created by magisk) or flash your ROM, this should work always. And the ROM should contain a clean boot image. Probably boot.blob is a renamed boot.img, but I don't know.
[Magisk] 135Shadowsoul:
ill give it a try, thanks

edit: done, device booted up, but it seems magisk is still not installed :(

edit2: flashed "stock" boot img... im an idiot :D now i flashed the patched one. device is booted up, but magisk still not installed :(
[Magisk] wurstherpes:
Clean LineageOS installed.

Google Apps Installed.

Then the initial setup finished.

Back to TWRP and Magisk flashed.

Then Magisk Manager installed.

Hide the name from Magisk Manager and Hide the Pushtan and PlayStore then restart.

(SafetyNet Pass) (Two green hooks.)

Then start pushtan-App and root detected.

Again the same.

Sorry but adding a log/file will not work:

02-17 15:38:54.241 3456 3456 I Magisk : * Creating /sbin overlay

02-17 15:38:54.263 3459 3459 I Magisk : * Device API level: 28

02-17 15:38:54.263 3459 3459 I Magisk : Magisk v18.1(18100) daemon started

02-17 15:38:54.273 3459 3460 I Magisk : ** post-fs-data mode running

02-17 15:38:54.273 3459 3460 I Magisk : * Initializing Magisk environment

02-17 15:38:54.273 3459 3460 I Magisk : * Mounting mirrors

02-17 15:38:54.275 3459 3460 I Magisk : mount: /sbin/.magisk/mirror/system

02-17 15:38:54.275 3459 3460 I Magisk : link: /sbin/.magisk/mirror/vendor

02-17 15:38:54.275 3459 3460 I Magisk : bind_mount: /sbin/.magisk/mirror/bin

02-17 15:38:54.275 3459 3460 I Magisk : * Setting up internal busybox

02-17 15:38:54.299 3465 3465 I Magisk : Magisk v18.1(18100) logger started

02-17 15:38:54.330 3459 3460 I Magisk : * Running post-fs-data.d scripts

02-17 15:38:54.330 3459 3460 I Magisk : * Mounting /data/adb/magisk.img

02-17 15:38:54.421 3459 3460 I Magisk : * Running module post-fs-data scripts

02-17 15:38:54.421 3459 3460 I Magisk : * Loading modules

02-17 15:38:54.428 3459 3485 I Magisk : * Starting MagiskHide

02-17 15:38:54.428 3459 3485 I Magisk : hide_utils: Hiding sensitive props

02-17 15:38:54.428 3459 3485 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]

02-17 15:38:54.439 3459 3485 I Magisk : hide_list: [com.starfinanz.mobile.android.pushtan]

02-17 15:38:54.449 3459 3485 I Magisk : hide_list: [com.android.vending]

02-17 15:38:54.855 3459 3561 I Magisk : ** late_start service mode running

02-17 15:38:54.856 3459 3561 I Magisk : * Running service.d scripts

02-17 15:38:54.856 3459 3561 I Magisk : service.d: exec [11link2sd]

02-17 15:38:54.906 3459 3561 I Magisk : * Running module service scripts

02-17 15:39:11.678 3459 3485 I Magisk : proc_monitor: com.android.vending/com.google.android.finsky.setup.PlaySetupServiceV2 PID=[4726] ns=[4026535688]

02-17 15:39:22.255 3459 3485 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[6153] ns=[4026535729]

02-17 15:39:41.861 3459 3485 I Magisk : proc_monitor: com.starfinanz.mobile.android.pushtan/com.starfinanz.mobile.android.spushtan.SPushTan PID=[8084] ns=[4026535715]

02-17 15:39:50.557 3459 3485 I Magisk : proc_monitor: com.starfinanz.mobile.android.pushtan/com.google.android.gms.measurement.AppMeasurementInstallReferrerReceiver PID=[8731] ns=[4026535693]
[Magisk] simone.a:
The two folders are empty. Anyway, this is the Magisk log (sorry, no Canary build), found in /cache/magisk.log:

[LOG DELETED]

P.S.: I white-colored some app names.
[Magisk] jcmm11:
Try the latest Canary build, this problem should go away since magisk.img is gone. Before you start delete /data/adb/magisk_merge.img

If you really don't want to install Canary then still delete that file and try to install modules via TWRP.
[Magisk] simone.a:
Will canary build delete all my personal data?

I can't neither install modules via TWRP.
[Magisk] Didgeridoohan:
[MENTION=9724742]simone.a[/MENTION] A few things... First of all, please don't post a full log directly like that. It is hopeless to read and really clutter up the thread.

Second, if you want to use modules you're going to have to follow [MENTION=4487388]jcmm11[/MENTION]'s advice and use the latest Canary since the Magisk image can't mount on your system. That's why it's switching to Core Only Mode by default.

Third, your Hide list is way too big. You should only add apps that actually detect root and nothing else. You risk destabilising your system if you add too much...
[Magisk] simone.a:
I'm sorry, I don't know how to directly upload the log file.

Ok then, will this change delete all my personal data?

Ok, thank you.
[Magisk] Didgeridoohan:
It shouldn't, but since it's the Canary builds there's a greater risk of bugs and issues, so make sure you have backups. If you are uncertain it might be better to wait for the stable release, but that all depends on how desperate you are to get modules working.
[Magisk] simone.a:
It's not a priority, it was just to install Zirene, the speaker works well anyway. I'll wait, thank you everyone for your help. :o
[Magisk] jcmm11:
You may not have enough posts yet to add attachments to your posts. What you can do is post the log to a pastebin site and then post the link (until you have more posts you may need to "disguise" the link. Drop the https:// part of the link).

Once you do have enough posts to create attachments you can also consider zipping large logs before attaching them.
[Magisk] soder:
This is question about what could be possible to do with Magisk and root, or maybe if it's about Xposed.

Not being a fan of Apple, or should I say iPhone, I have to say their "Guided Access" worked very well for all units.

Three presses on the power button or home button starts a screen lock, or locks the app from being turned off, or even looks parts of the screen.

In Android there is the "pin mode", but that would work on my OP6T if I don't use it with navigation buttons.

There's also apps like Touch Lock, but I have to use it with the Android pin mode, because in some way my kids keeps pulling down the notification bar and leaves the video app or kid game.

Also it a bit of a challenge for me to first activate Touch Lock with some second delay, activate the Android pin mode and then start the video before Touch Lock actually locks the screen.

Is there some way, with root, Magisk and Xposed, giving me a better experience with handing my kids my phone?

If this post is in a compete wrong thread, I'm sorry, and please then help me move this post to where it belongs.

Thanks.

/Söder
[Magisk] Mangetsu:
Magisk 18.1 (also tried canary), Android 7.0, Samsung Note 4.

Manager doesn't list app (Samsung Pay watch plugin) in MagiskHide. Yes, "show system apps" checked. Nothing interesting in magisk log. What might be the cause?

---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------

Magisk 18.1 (also tried canary), Android 7.0, Samsung Note 4.

Manager doesn't list app (Samsung Pay watch plugin) in MagiskHide. Yes, "show system apps" checked. Nothing interesting in magisk log. What might be the cause?
[Magisk] batumulia:
Hi Didgeridoohan,

Thank you very much for your help! I wasn't able to test it earlier as I was out this weekend. I just fixed the issue. Thanks again!
[Magisk] Ch3vr0n:
It seems there's an issue with magisk and the pixel 3 xl? After flashing magisk, and the device is powered off, a charging battery icon appears. Device shortly powers on, then displays the power icon. So it's not really powered off. It seems this was fixed for some other devices? Are other fellow pixel 3 xl owners also experiencing this? What are thoughts on this, can/has/will this cause screen burn-in? Have/will you stop(ped) using magisk over it?

[MENTION=4470081]topjohnwu[/MENTION] anything that can be done to this. Device is updated to Feb patch.

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Magisk] Frankelvis97:
Trouble with Magisk Apk

i tried so many times with Magisk Apk to get the full access of the Android rooting process. But some features are missing in it. and i have to know how to enable the Magisk Hide feature? According to the magisk official web site it having some issues? is that true?
[Magisk] xunholyx:
There is no "official Magisk website". Everything is done through XDA or the Magisk Github

Here's a link to the official release/announcement thread. In the first post are links for both installation instructions and tutorials.

Good luck!
[Magisk] Frankelvis97:
Trouble with Magisk Apk

How to enable Magisk Hide?
[Magisk] Ch3vr0n:
Go to settings, swipe down, enable the switch next to it, reboot, done

Verstuurd vanaf mijn Nexus 6P met Tapatalk
[Magisk] Didgeridoohan:
You mean when the charger is connected, right? If so it's likely a variant of this (that can't be fixed by Magisk):

https://github.com/topjohnwu/Magisk/issues/906
[Magisk] mikek753:
S5 TMO can't install 18.1 zip in twrp

hi all,

I tried to install v18.1.zip, but got error

!Boot image patched by unsupported program

!Please restore stock boot image

Updater process ended with ERROR: 1

I'm on 6.0.1, sure it's modified, rooted

also, I have Xposed that I need for several things

I'm looking to pass SafetyNet, so Magisk to rescue

what I'm missing and what I can do to install the Magisk

thanks
[Magisk] chooks06:
If I'm not mistaken, having Xposed would make it impossible to pass safety net.
[Magisk] jcmm11:
As [MENTION=6323980]chooks06[/MENTION] stated Xposed means SafetyNet fails. If you still want to install Magisk you'll first have to remove your existing root and make sure you flash an unrooted boot image.
[Magisk] Didgeridoohan:
[MENTION=5455111]mikek753[/MENTION] You've already recieved some assistance, but I thought I'd drop this here anyway:

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

And:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
[Magisk] dpsi:
OP5 here, sticking with magisk 17.3 has been the only way for me to keep Google Pay working. On 18.1 it will pass safety net until you try to pay, where it will fail and then safety net won't pass until you reboot.
[Magisk] habylab:
Never had it fail like that, but give the latest canary a go. There's upgrades to Magisk Hide, and along with all the other improvements to 18+.
[Magisk] Shajirr:
How do I upgrade from Magisk v16 ?

Magisk Manager 7.0.0 doesn't even work, it just says that it doesn't support Magisk below 18 then closes

Magisk Manager 6.1.0 has no option to upgrade Magisk, it only offers upgrading itself to 7.0.0, which achieves the same result of not working afterwards.
[Magisk] Oswald Boelcke:
Did you already try to flash first the Uninstaller, and then immediately followed by a flash of Magisk v18.1, both done via TWRP?
[Magisk] Ch3vr0n:
Don't know, device does charge. That issue originally states not charging. If it's related, perhaps someone can write a module to replace that icon with the default animation (those expanding dots) or not show it at all, or a full black icon. I'd do it but I've got no clue how to do that.

Just wondering if anyone else with this device has it and what they've done/are doing about it and if I should be 'worried'. Brand new device, only setup. Waiting on case and glass protector to arrive before I start using it.

Either way, my device is hardly ever powered off completely so I doubt it's a very big issue.

Verstuurd vanaf mijn Nexus 6P met Tapatalk