yashsingh1/xdaforums huggingface dataset:
[Magisk] casouzaj:
Coinsider flashing the stock 291 ftf and, then, fastboot a TWRP which works for you to the FOTAkernel partition , and, from TWRP, install the new CR6.1 zip and Magisk v19.3.
[Magisk] Kockowan:
Hmmm, no other way to repair TWRP without new clean installation?

(After flashing TWRP with fastboot only, CR-6.1 is gone away...)

There are some device linked banking apps (pushtan a.s.o) installed. After new CR installation all of those apps must be newly authorizised, an extensive additional work for me and banker too...

Thx + regards
[Magisk] casouzaj:
Go to a previous CR6.1 config in which everything is working for you. Go to TWRP and back it up (at least the data partition), Then, start from scratch (ftft). When you achieve a state in which both TWRP and Magisk v19.3 are working , restore the data partition from the previous backup. You'll have to update Magisk Manager afterwards.
[Magisk] JudgeDread11:
Edit: see post below. (I'm still on Android 7)

If you use Titanium backup, it can restore the Android id.
[Magisk] BillGoss:
As of Oreo it is no longer possible to change the Android id with an app. This explains why TB can't change it.

See https://android-developers.googleblog.com/2017/04/changes-to-device-identifiers-in.html

You can get the current Android id using:

adb shell settings get secure android_id

But the value changes each time /data is wiped.
[Magisk] DragonFire1024:
Change the id in secure settings. You don't need an app to do that. Just ADB, unless the id is no longer available in secure settings then that's a different story.
[Magisk] jcmm11:
Doesn't matter. It's now a per app setting. Every app has its own Android ID.
[Magisk] Der Namenlose Held:
Hey, Magisk Hide doesn't work for a banking app I have to use. Magisk Manager is repackaged and the app is in the MagiskHide list, so it shouldn't detect that my phone is rooted. Any ideas on how to fix it? It used to work before I believe.

https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan
[Magisk] zgfg:
More hints can be found in the thread, as already discussed, and collected in the Guide on GitHub (link can be also found in the previous posts)
[Magisk] imska:
Another trick you can try is to disable and re-enable magisk hide in the magisk settings menu. Then try again your banking app. If it works, you still might need to do this again after every reboot.
[Magisk] MC_Ohr:
You have to hide magisk manager in settings and clean storage (ore even uninstall and reinstall) of pushtan app. Maybe it is also needed to restore boot.image and reinstall without reboot from manager app.

Gesendet von meinem HTC U11 life mit Tapatalk
[Magisk] hfam:
Pixel 2/Magisk 19.3/Pie 9 Aug update => Q10 Sept update/Canary 19.4 went flawlessly when using flashing full factory image (remove -w) method.

Update MM to latest Canary before flashing the Q update, flash factory image (remove -w from bat), then after flash and reboot, open MM and update Magisk using patch file method, flash the magisk_patched.img and reboot, good to go, all works solid.

Thanks to TJW, all the regs here, and everyone else who makes this forum so awesome. Wicked smart and helpful folks!
[Magisk] tukozaki:
Stuck with Magisk 19.1

Anyone having problems updating Magisk with Magisk manager?

Trying to update to Magisk 19.3 (19300) from version 19.1 (19100). When I update Magisk it downloads the zip, installs it till it asks me to reboot. Which I do. But after restart its on the same version as before.

In MM "Update" is on Stable. Also, same result after I disabled Magisk hide.

Any one have more details on this? Seems HavocR88 had similar issue on July 1st but he used Canary.

Using a Gemini PDA WiFi Android 8.1

Flashed with Magisk 19.1 (19100) stable

Magisk manager 7.3.2 build 224
[Magisk] shivamgosain89:
Magisk is not working on android Q for A only partition device.
[Magisk] palmbeach05:
Canary branch?
[Magisk] ecksdeeay:
[MENTION=4435364]tukozaki[/MENTION] Have you try?
[Magisk] JudgeDread11:
If you want advice we will need wayyyyy more information then that.
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] On the latest magisk Canary and unofficial builds, in a root terminal, has anyone else seen this strange behavior: (unreachable)?

Root does work, though. Screen shot is attached.
[Magisk] jcmm11:
That's partially correct. It's not working for A only devices on Android 10 that use 2nd stage init.

topjohn is most definitely aware but apparently it's going to be difficult to implement.

See this for more info

https://mobile.twitter.com/topjohnwu/status/1174392824625676288
[Magisk] guest4711:
No, it's working fine on armv7. Tested twice: using a permission already given and 2nd after deletion of the permission so MM asked again.
[Magisk] rfgamaral:
A few questions guys:

1) Every time I enable "Preserve force encryption" and reboot my phone, the option becomes disabled again. Why? What impact does this have?

2) What exactly is the new "Recovery Mode" option in the new Magisk Manager v7.3.4? Can't find any info on this besides a mention in the changelog.
[Magisk] JudgeDread11:
Afaik this option is only used when patching a boot.img with magisk manager. So enabling it only before patching your boot.img should be enough.
[Magisk] rfgamaral:
Were you referring to 1 or 2?
[Magisk] JudgeDread11:
Both, :)

I believe the recovery mode option is for if you use TWRP to flash your psyched boot image. If you flash through fastboot leave it disabled.

Please someone correct me if I'm wrong.
[Magisk] zgfg:
It switches off Preserve force encryption becsuse you are using installation where Preserve... was not checked in while patcjing the image (or Magisk was installed in TWRP with that option disabled)

If you want to have it, enable Preserve... and click on Install Magisk and patch the image (or let it directly update to your Boot/Ramdisk) with the Preserve... option enabled
[Magisk] rfgamaral:
Well, I don't even understand what's the benefit (if any) of having that option enabled...
[Magisk] zgfg:
If everything works for you fine, then don't bother (and better don't make changes in the winning team)
[Magisk] martyfender:
Yes, root appears to work fine for me also, other than that (unreachable) message after typing su in the terminal. [MENTION=4470081]topjohnwu[/MENTION] could not reproduce it, so I guess it is just some cosmetic error particular to my Nextbook Ares 8A, Intel x86, Android 6.0.1 devices.

However, I have never seen this ever with the many unofficial and Canary builds I have had on my devices in the last 2 years.
[Magisk] rfgamaral:
I know, but I like to understand how things work and all options so I don't screw things up and more importantly, when I do screw up, I like to understand what I'm doing wrong and why.
[Magisk] zgfg:
Please check Installation guide. AFAIK, you must use it if your device has encrypted Storage, but if you install/flash Magisk through MM, MM will automatically recognize and enable (eg., my Storage is encrypted and it always works like that)
[Magisk] rfgamaral:
My storage is also encrypted, but I installed Magisk through TWRP.
[Magisk] sdeft:
[MENTION=4470081]topjohnwu[/MENTION]

With the latest 19.4 release the mount point of system is changed and file managers can't delete files from eg. /system/etc (for example Root Explorer).

Seems the mount point is now /sbin/.magisk/mirror/system_root

Am I correct ?
[Magisk] pac213:
I can't see the update on the Magisk Manager.
[Magisk] Duck4Cover:
It's a beta you will have to download it manually and install. Best sticking with the current one until release.
[Magisk] zgfg:
You can update from MM if you change channel to Beta
[Magisk] palmbeach05:
One is on stable, one is on beta, and re-add canary branch via custom
[Magisk] Wolfcity:
For me the systemless access is the same as in 19.3:

sbin/.magisk/mirror/system
[Magisk] martyfender:
For some time Canary has had it's own channels in MM settings. There is no need to add it through the custom channel any more. There are settings for the release channel and the debug channel of Canary.
[Magisk] Didgeridoohan:
Only if you have the Canary Manager installed. Beta and Stable Managers do not have those options (only the custom option).
[Magisk] Kockowan:
There seems to be a solution, but how to apply it to broken system with CR-6.1 / Magisk-19.3 without access to TWRP recovery?

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

There is a known issue with Magisk 19.x.

Fixing should be possible by accessing init/init_main.cpp:

https://github.com/koron393/android...mmit/5be3e4b2723da9233f4f638ca4a5d0e515453442

But how to access/correct this file by adb.exe on phone or in TWRP-recovery.img or in Magisk-19.3 by editing?
[Magisk] ktmom:
I didn't see an answer that referenced the Magisk install docs (excuse me if I overlooked it).

From Magisk Installation - Boot Image Patching:

If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
[Magisk] palmbeach05:
But when you take today's update, you have stable, beta, and custom. No canary.
[Magisk] zgfg:
In the Stable or Beta MM, you don't have Canary channel.

Canary channels (Release and Debug) are only available from Canary MM

This was always the case, with all previous Stable, Beta and Canary releases as far as I remember
[Magisk] sharp3r:
After upgrading to magisk manager 7.3.4 with latest stable magisk and installing safety net and checked my apps in magisk hide. my bank app won't log in bcs the device is rooted. I uninstalled the manager and the app is working fine.

Any suggestions please?
[Magisk] jcmm11:
If all you had to do is uninstall the Manager then reinstall it and choose the option to "Hide Magisk Manager"in its settings.
[Magisk] sharp3r:
Exactly what i did, i tried clearing my apo's cache, reinstalled it but same issue, it looks like a bug in that version of magisk manager
[Magisk] ktmom:
Did you remove the banking app, and reinstall only after MM was hidden?
[Magisk] Fedroid:
Try with the option of renaming mm for hiding to other apps. My bank app only works this way
[Magisk] palmbeach05:
Oh ok, so i would have had to do what i did by adding it to custom channel to be able to see canary channel again. Got it.
[Magisk] sharp3r:
Renaming mm worked. Thank you [MENTION=3523999]Fedroid[/MENTION] :good:
[Magisk] Shotg1:
Latest magisk 19.4 doesn't allow to delete from root/system in n root explorer etc.
[Magisk] jcmm11:
You may want to read the notes

https://github.com/topjohnwu/magisk_files/blob/6510533d6a8bb751152539919f57bb616c2405af/notes.md
[Magisk] Bostwick:
updated to latest Magisk and Magisk Manager Canary on my Pixel XL just now and all of a sudden my ctsProfile fails/false in the safetynet check... hadnt made no changes, just checked safetynet 2 days ago before update and was fine... anyone else having this problem?

and a solution? how do i fix jt?
[Magisk] zgfg:
With a little patience and staying on Canary, today was released Canary MM v7.3.3 b236 plus Canary Magisk b19401 - with a short and self-explanatory Changelog:: Sync with public release.

So expecting also Stable Magisk v19.4 b19400 release soon.

This is all the usual habit
[Magisk] pac213:
My bad, I thought it was Stable.
[Magisk] DroidJP:
Hello

After updating to magisk 19.4. Link2sd no longer mounts sdext2 of my sdcard. I tried reinstalling, uninstall, reboot and then install again. whhen i have link2sd recreate mount scripts, it said that it was successful and then reboot, yet i see no sdext2 partition mounted.

I believe the problem lies that link2sd fails to create 11link2sd mount script in the following path: /data/adb/magisk/service.d

It used to create this file the moment i allow link2sd root access. I even restored the stock boot.img and reflashed and still, this folder is empty after allowing link2sd root access. Any idea what is going on?

Thanks.
[Magisk] TENlll423:
I noticed after updating to 19.4 I could no longer switch out different boot animations from system/media.. I went back to 19.3 and now I can..

Also it wouldn't let me change the read and write permissions for the boot animation zips on 19.4 either.. edit

I ended up fixing the issue by using total Commander it's an old app hasn't been updated in ages but It works... Delete boot animation zip from system / media then copy any bootanimation.zip you want to that destination and all is well...

Even works on A10 v10.3.0 Magisk 20.3.
[Magisk] Didgeridoohan:
Hi there and welcome to XDA.

That particluar issue you are facing are most likely fixed by simply toggling MagiskHide off and on again. That is sometimes necessary after an update (but usually quite rare). If you're really unlucky you might be experiencing a bug where the toggling off and on has to be done after every reboot, but since you have a Pixel device I don't think that's the case.

There are a few resources available to you when you have issues:

Most issues have already been covered in this and other threads here in the Magisk forum, so a search of either the forum or specific threads might give a solution. There is a large amount of information to sift through though, so sometimes it can be tricky to find the correcct search terms, especially if you are unfamiliar with how Magisk works.

A good source for information is the Magisk release thread. There you'll find a few tips, but most importantly links to other resources like the official documentation and my troubleshooting guide/FAQ.

If you have further issues and can't find any information about it in either the forum or documentation/FAQ, don't hesitate to post further questions.

That turned into a bit of an essay... :laugh:
[Magisk] wilsonhlacerda:
service.d scripts are not being run on new beta v19.4. At least not for me and seems also not for you.....

That's the root cause of some problems I had as soon as I've updated today (among other scripts, I'm also using Apps2SD just like your Link2SD fail).

Just to be sure I created 3 simple scripts to echo "ok" to some local files: the scripts under userinit and post-fs runs as expected, but the one under service.d does not.

Magisk log shows post-fs script being executed, but nothing about service.d.

scripts are fine and with execute permission. Something is broken on v19.4 update.

I'm running Lineage OS 16 (Android 9).

I'll try to better investigate, reinstall,..... But it seems is a BUG.

EDIT: by the way, the (annoying) bug that Magisk Hide only works after toggling after reboot is also present on v19.4 yet (just to remind it was fine to me till v19.2, then v19.3 introduced this bug).

And the worst part: I'm using an script on service.d to toggle it, but now as the scripts are not being run on v19.4 then this also fails.

I'm circumventing everything now by including all scripts under my userinit.sh main script.
[Magisk] DroidJP:
Well that explains it. Good to know now after couple of hours trying to figure out why it's not working. Unfortunately i did not make a backup of the script nor did i view the script to recreate manually.

I do have a backup plan (which btw, used this method before) to permanently mount sdext2 without needing link2sd or app2sd scripts. I simply unpacked the boot.img and edit the fstab and repack and flash. Now sdext2 is part of the phone's boot process with or without root.

The problem? Well, it's a little bit too perfect that the phone now expects sdext2 to be there on every reboot or the boot process halts if there is no 2nd partition, making your phone unusable should your micro sdcard fails or do a swap.

But hey, this method really works, bypassing mounting scripts altogether lol.
[Magisk] JudgeDread11:
For apps2sd you can set the path manually in settings to post-fs. And that should fix it.

Sure if you can set a path manually with link2sd.
[Magisk] DroidJP:
I had issues with app2sd. Link2sd does not give that option. It places the script in service.d automatically. Hopefully the next magisk update fixes this issue. Is there way to get this script manually?
[Magisk] Didgeridoohan:
[MENTION=4668495]wilsonhlacerda[/MENTION] [MENTION=5759902]DroidJP[/MENTION]

I cannot reproduce any possible bug that involves the service.d scripts. All the scripts on on my device runs just fine, and just to make sure I created a test script in service.d (just create a file in /cache) and that ran as expected.

Since this doesn't seem to be a general issue, more information will be needed. Debug build logs, etc...
[Magisk] DroidJP:
And the magisk logs you are referring to are in /cache? If so, i may have to repeat the issue since the last logs got deleted.
[Magisk] Didgeridoohan:
https://didgeridoohan.com/magisk/MagiskHelp
[Magisk] AndrzejDwo:
Successfully updated (with direct install) from 19.3 to 19.4 on my S8 running Hades v10. So far so good.

Thx,

Cheers
[Magisk] hfam:
Niiiice, thanks for the info! If the stable 19.4 is released in the next few weeks I'll coordinate the October Q10 update for my Pixel2 and switch from current Canary to stable 19.4 at that time.
[Magisk] palmbeach05:
19.4 update that was just released gas been merged into canary channel. Enjoy!
[Magisk] Dqnjel:
Installation fail in Magisk Manager fix by download Zip File from Magisk Manager flash Zip File in TWRP.
[Magisk] martyfender:
My Apps2sd custom service.d script runs fine now on my device.. However, after updating Magisk, the second ext partition did not mount. I recreated the mount script and on subsequent reboots all seems fine and I believe the service.d custom mount script is being run. In Apps2sd settings I have the path set in this setting:

set su.d/post-fs-data.d/service.d path:

/data/adb/service.d

I also have a UDSbypass script in service.d and it is also being ran, as usual, on the latest Magisk.

I tested this in Rootbeer Fresh.

---------- Post added at 09:29 AM ---------- Previous post was at 08:52 AM ----------

I'm not sure if it is still the case, but in the past I have had issues with the direct install method in MM, so now I always download the zip in MM and install it in TWRP.
[Magisk] jcmm11:
What's the exact error?
[Magisk] martyfender:
I'm not sure if it is still the case, but in the past I have had issues with the direct install method in MM, so now I always download the zip in MM and install it in TWRP.
[Magisk] JudgeDread11:
FYI with the new magisk version I believe the USD bypass script shouldn't be necessary anymore.
[Magisk] DroidJP:
Does this mean service.d is now disabled even though magisk still creates this folder?
[Magisk] Dqnjel:
Hm maybe it can better flash in recovery
[Magisk] JudgeDread11:
Sorry, no afaik the service.d should work.

I meant to say you shouldn't need to use the USD bypass script anymore. This was fixed in the magisk canary version and now in the new stable version. I'll edit my original post to make clear what I meant to say.
[Magisk] jcmm11:
And maybe you have other issues with the phone that you're not even aware of. What phone do you have? Version of Android?
[Magisk] martyfender:
It is not fixed for my devices. It does pass the the UDS part in a hidden Rootbeer Fresh app, but without that boot script RF detects a root management app. In both cases, Magisk Manager is hidden
[Magisk] r4yv3n:
Now i can use Samsung Pay (Watch Plug-in) Again.

But Galaxy Store detects root and cannot use card payment yet

Galaxy S8+

Regards
[Magisk] wilsonhlacerda:
service.d scripts BUG, not running after update to Magisk v19.4 (on Lineage OS 16, encrypted):

I've done some more tests and could narrow the root cause: Magisk v19.4 introduced some incompatibility with EdXposed v0.4.5.1_beta(4463) and as a result all service.d scripts do not run anymore.

With Magisk v19.3 and same EdXposed version there was NO problem. Everything used to work fine.

With Magisk v19.4 and EdXposed module disabled there is NO problem (don't need to uninstall; can even leave Riru module enabled), service.d scripts run as expected.

I've already tried to reinstall Magisk v19.4 from Magisk Manager and from TWRP. Also I have already tried to reinstall EdXposed, both YAHFA and Sandhook variants. Nothing helps to solve the introduced bug.

Unfortunately it's a new bug. I'll file the issue on both Magisk's and EdXposed's Github, but if some of you can help anyway (maybe you have close contact to developers!) I and lots of other users thanks in advance.

Magisk is a fantastic tool. EdXposed is another fantastic tool. Both together leverages Android experience to whole new level (and without triggering SafetyNet and Root detections!). They deserve to work fine together.

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

Are you using EdXposed (or maybe Xposed or Tai Chi)?

Check my findings above.
[Magisk] knpk13:
There's nothing written there about recovery mode, other than "synced with public release"
[Magisk] Didgeridoohan:
That is actually not a new issue at all... EdXposed has been known to break the Magisk boot process on some devices for at least 6 months now. And don't file an issue on Magisk Github for it, it's an EdXposed thing...

Of course, without seeing a Magisk log I'm just guessing.
[Magisk] wilsonhlacerda:
delete
[Magisk] DroidJP:
I finally came to the conclusion that magisk 19.4 service.d is not working. I gathered up the logs for magisk 19.3 and 19.4. It is quite a difference. Where should i send the logs?
[Magisk] jcmm11:
See 2 posts above yours. Make sure to read the quoted post as well.
[Magisk] DroidJP:
I am not. Just link2sd. I never had an issue with it up until now.
[Magisk] wilsonhlacerda:
So so, kind of: I've been running Android 7 + Magisk + Xposed (systemless) and then Android 9 + Magisk + EdXposed since a loooong time without issues.

Specifically till yesterday night I was with my current daily device + Android 9 + Magisk v19.3 + EdXposed....all fine. The only change I made was the update to Magisk v19.4, nothing else. Same device, same Android, same EdXposed. And then the bug showed up.

As you are writing sure may have some EdXposed bugs that affect (even old) Magisk on some devices, but what I'm observing is a complete new scenario. They may even be related, and the root cause may be EdXposed or Magisk, but what we can clearly see is that something that was working fine together does not work anymore after a change in only one of the pieces (Magisk in this case).

As both tools are valuable they do deserve both developers to take a look and try to revert to the previous good working together condition. Maybe even solve the old suspicious problems as a consequence.
[Magisk] ktmom:
Well no, not 10 days later with a new release. Now the information resides in the Magisk Installation docs Boot Image Patching section.
[Magisk] DroidJP:
I really do think magisk 19.4 is the issue. When i downgraded to 19.3. Link2sd is mounting again.

I included as much detail info along with a screenshot of mount warning.View attachment Magisk-logs-9-20-2019.zip
[Magisk] Dqnjel:
It makes no matter what phone or android i have maybe some have same problem install fail in MM and search for some soloution - download zip in mm but flash via twrp
[Magisk] DroidJP:
Yup and yup. Same thing with link2sd. All was fine and dandy until i updated to the latest version of magisk. The sdext2 partition was gone. What is interesting though that link2sd has a backup mount method which i did not know. It will eventually mount the sdext2 once the OS has finish loading everything. This must be legacy mounting method going back to kik-kat days.

Either downgrade back to 19.3 or see if there is a workaround regarding the 19.4 release. I have moved my apps back to the internal storage because this legacy mount not only screws up your home screen icon arrangements, but also their app data gets corrupted and app crashes.

Think for now, i am downgrading back to 19.3. the culprit of the issue is the magiskinit in the 19.4 magisk zip. It's in the logs provided, hopefully someone could compare these files.