yashsingh1/xdaforums huggingface dataset:
[Magisk] C5Longhorn:
Hi,

I need some help. I'm running Android 10 on a Pixel 3XL that is rooted with canary Dev Magisk version 19401 and Manager version 236.

How do I upgrade to the latest public beta build that was just released? Do I need to uninstall Magisk using the uninstaller, then install the new Manager, and then batch a bootloader file?

EDIT: I updated in the app and how have the file versions listed above.
[Magisk] wilsonhlacerda:
What is interesting is that in your case you are not using any kind of Xposed module.......but service.d bug showed up to you without it.

In my case the problem is Magisk v19.4 + EdXposed together. If I disable EdXposed the bug is gone and service.d runs fine (and thus Apps2SD in my case).

I myself right now did a workaround: manually moved my general service.d scripts (including the Apps2SD one) into the /data/local/userinit.sh (I'm running Lineage OS 16).

But this can be a problem for modules that need their own service.d (under their folders).....fortunatelly I have none.
[Magisk] DroidJP:
I have no magisk modules installed. Just what magisk comes with and link2sd. I try to keep things as basic as i can unless it is absolutely necessary. As far as app2sd goes. That app almost hard brick my phone when i was creating the 2nd partition.

Never again touching that app lol. I let either twrp or use my pc when it comes to partitioning. It has too many glitches and leaves files in system rom. I don't like that. It is a good app though. It just has dangerous tools bundled in one that was bothersome lol.
[Magisk] ktmom:
Yes, what you describe is what I would do. I would wipe cache before booting, which can be done in fastboot.

fastboot erase cache
[Magisk] jcmm11:
First of all the versions you have installed are identical to the beta versions. If you want to follow beta (or stable) from here on out just change the update channel within Magisk Manager and wait for the next update. No need to replace the existing files.

The next beta, or stable, will have version numbers > the current Canary so the update will get applied
[Magisk] Bostwick:
i tried it.. didnt work...
[Magisk] martyfender:
Why do you want to do that, as they are both in synch? They are therefore effectively the same version except for the fact that the Canary debug version has more verbose, debug logging. The release version of Canary, however, does not have this extra logging.

If you really want to go to the public beta, first download the latest Magisk Manager from here:

https://github.com/topjohnwu/Magisk/releases/download/manager-v7.3.4/MagiskManager-v7.3.4.apk

I believe it will be the same one as in the beta. Uninstall your current MM then install this new one. open it and go to settings and set all of your previously used settings, except set the update channel to the beta. On my test it was now set to the beta channel, by default. Now go back to the main page and swipe to refresh it.

Since I always install with TWRP, I chose to download the zip only, then reboot to TWRP and then I install the new zip.

I tested this on one of my tablets that has debug Canary and it works fine. The direct install or patch boot image methods I have not tested, as I don't use those methods, myself.

Upon re-reading your post, you stated that you are on Android 10, so you will have to use the direct install method or maybe the patched boot.img method, again. I am not certain about upgrading with the direct install method on 10, as I have not seen anyone do this yet to confirm that it works, as usual, on 10.

It is my hope that 10 users will clarify this.

My devices, by the way, are Android 6.0.1.
[Magisk] DroidJP:
Guess what? I finally got to the real issue of not just my issue but yours as well. (2 birds with one stone i suppose lol) So. here's is what's really going on.

So as it turns out, magisk version 19.4 is not as broken as we previously thought. It is only a particular part that is.

So this is what i mean and explains why your case is different than mines and now i know why that is. So here it goes:

.The service.d in it itself works perfectly fine just as it is in the 19.3. The issue is when it comes to creating upon requests and placing the newly scripts in the service.d directory by other apps (link2sd, app2sd, or other scripts creating scripts). When this happens, this is where you run into problems. Which explains my case why there was no 11link2sd script in the folder. Link2sd wasn't able to place this file on this folder.

.a true workaround is have your scripts ready and manually place the scripts in the service.d and every script in this folder will run upon reboot. I did exactly that with 11link2sd which was created in magisk 19.3 and flashed 19.4 after.

Now the sdext2 mounts upon boot every time on the latest version of magisk.

So in conclusion: scripts can still be executed from this folder just as long the script does not request to create.

Finally, problem solved an no longer losing my sanity over this! Lol.
[Magisk] C5Longhorn:
I don't think I do. I was confused and wanted to update to a later version and didn't realize they were the same. Thanks.

One follow up, we still aren't able to remove system apps correct?
[Magisk] jcmm11:
No, and that's not going to change. It's due to underlying changes that Google made. With system apps just freeze them.
[Magisk] martyfender:
One thing is certain, neither of these apps that we use, link2sd, app2sd have been updated recently for newer versions of Magisk, so part of the blame could potentially be in those apps, also.

As far as edexposed goes, it has been known to break on some devices. I would suggest posting issues for it here:

https://github.com/ElderDrivers/EdXposed/issues

You could also post on the issue area for Magisk, but you must post logs and be on the Canary debug build, or [MENTION=4470081]topjohnwu[/MENTION] will often close the issue right away. I am not clear if he accepts the beta build logs, there, as they will not be as verbose as the Canary debug builds. Today's Canary build is in synch with the current beta.

---------- Post added at 09:53 PM ---------- Previous post was at 09:35 PM ----------

Yes, I agree, you can no longer remove system apps in Android 10.

Since I don't have a device with Android 10, how does one freeze the app? Is this built into Android 10, or does one have to use an app, such as Titanium Backup to do this? I believe there are other apps that have this freeze feature, also.
[Magisk] DroidJP:
That is very true. App2sd was forced to not update anymore because of google therefore, app2sd is done for.

As for link2sd. Not sure why but there is a chance that it could be updated. Only time will tell though.
[Magisk] martyfender:
Yes, I agree, you can no longer remove system apps in Android 10.

Since I don't have a device with Android 10, how does one freeze the app? Is this built into Android 10, or does one have to use an app, such as Titanium Backup to do this? I believe there are other apps that have this freeze feature, also.
[Magisk] C5Longhorn:
I freeze them with Titanium Backup. Has anyone found an app they like better?
[Magisk] wilsonhlacerda:
Thanks for comments. I'll get Canary logs.

The bug I described is not caused byApps2SD or any other similar (but they also do suffer from it as a consequence).

The thing is simple:

Magisk v19.4 + EdXposed = no running service.d scripts. Any script. A simple correctly written and with correct permissions

echo "ok" > /cache/serviced.log

fails to run if EdXposed is enabled. On Magisk v19.3 (at least on my LOS16) it never fails.

---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------

Link2SD had development stopped much earlier than Apps2SD. And by the way the developer of Apps2sd plan to release a new version sooner (only on its support XDA thread probably).

Anyway, the link apps to SD feature of them works flawlessly till Android 9 at least, being Apps2SD more robust, with settings that let it very flexible to customize and evolve even without new releases (for instance I use it on a Chinese Android TV Box that has some stuff out of standards, just because I could play with its settings)
[Magisk] JudgeDread11:
If you would be able to provide logs (maybe both with and without script) I think it would be appreciated and help development.
[Magisk] jcmm11:
[MENTION=4412937]C5Longhorn[/MENTION]

In most cases, for system apps, there's a disable button if you look up the app under Settings|Apps &notifications

(See image). I usually 'uninstall all updates' (3 button menu, upper right) and delete data before disabling (which is the same as freezing).

If disable isn't available then you can use Titanium Backup, although personally I tend to use SD Maid. There are other apps available as well. Look up 'freeze apps' in the Play Store

Plus, if rooted, you can do it from the command line using the package manager

pm disable <package or component>
[Magisk] JudgeDread11:
Apps2sd has received updates a while back (but after the pro version was pulled from the play store) and Vicky (the developer) has announced at least one more update to come here on XDA. So for more info go to the apps2sd thread as it's off topic here.

You can also find help there on how to make it work with magisk.
[Magisk] Mikeligno:
With latest magisk 19.4 i check sub processs of some app or play services but magisk hide only check some option. Is it a bug or im doing something wrong? never happened with magisk 19.1, 19.2 and 19.3.
[Magisk] martyfender:
Yes, he did promise an update, but it never came in the time frame he mentioned and he has been quiet on that thread, so I have assumed that he had abandoned the project, or was too busy with his real life outside of xda.
[Magisk] zgfg:
Usually, system apps are not allowed to be disabled in Settings/Apps.

But even without root (!!!) you can disable or uninstall apps (for the current/default user) by using adb from PC

First, use some app like AppInspector or PackageManager (from Playstore) to find out package names corresponding to the apps you want to remove.

Eg:

Duo = com.google.android.apps.tachyon

Batch script with the adb commands:

ECHO OFF

adb devices
PAUSE

REM List packages
adb shell pm list packages
PAUSE

REM Disable Duo
adb shell pm disable-user com.google.android.apps.tachyon
PAUSE

REM List disabled packages
adb shell pm list packages -d
PAUSE

REM Re-enable Duo
adb shell pm enable com.google.android.apps.tachyon
PAUSE

REM Uninstall Duo
adb shell pm uninstall -k --user 0 com.google.android.apps.tachyon
PAUSE

REM Re-install Duo
adb shell cmd package install-existing com.google.android.apps.tachyon
PAUSE

For more, see:

https://xdaforums.com/mate-9/help/modding-removing-bloatware-blocking-ads-t3971297/post80526831

Source:

https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
[Magisk] Artim_96:
Since there was no updates in the mean time, yes.

The problem is the format the sing kernels do come in which is not supported yet for unpacking and repacking. The elf format they come in is common in Linux, but not in Android, so there might be a solution possible with what's left of Linux in Android, but otherwise you need to get a custom kernel in a different format (don't really know which is normally used), fur all I remember Advanced kernel was recommended.
[Magisk] Biges:
Thanks for the video! Please, what combination of Magisk, SuperSU and Pokemon Go version do you use? I'v recently installed a custom rom for my new Samsung S7 which contains some older version of SuperSU together with tailored Magisk, but Pokemon Go 0.39.1 refuses to authentificate :(
[Magisk] JudgeDread11:
It seems like I need to keep bumping this post. It's even easier now since magisk has its own sub forum. Subscribe to the magisk forum and post in the right thread.

---------- Post added at 01:27 AM ---------- Previous post was at 01:25 AM ----------

Please use search the same questions keep getting asked and the same answers keep getting given.
[Magisk] sanshinron:
When I boot up my phone I see a notification about an update to su binary. Can I click it and update?

Also, widget pleaseeeeeeeee :P
[Magisk] cubandanger05:
I went the SuperSU route. Installed SuperSU magisk version then installed SuperSU 2.78 systemlessly. My ROM supported systemless root so I didn't have to type the code in twrp terminal emulator to get supersu 2.78 to install systemlessly. Systemless Xposed 86.2.

I'm also running multirom and the secondary rom is the one with magisk installed which may or may not make a difference. Pokémon 0.39.0 is whats been working, I have not updated to 0.39.1 bcz it's not required. I am also not using the latest Android Pay which just updated recently. I'll test the new versions and report back.
[Magisk] kickthefreak:
hi, im completely install magisk v6 with phh superuser and xposed, it work perfectly,

do i need to flash magisk module template ?

and i cant switch root toggle to disable, any clue? im using mokee rom.

thanks.
[Magisk] untouchablejay:
I have Magisk v6 installed on my Nexus 6 and I can't get busybox to install. I tried the flashable zip, I tried installing in /su/bin and /su/xbin and it still says busybox was unsuccessful and just closes the app.
[Magisk] Citizen_Snips:
Did you try the flashable zip from here, http://xdaforums.com/showthread.php?t=2239421&page=86 ? If not, try that one and report back.
[Magisk] untouchablejay:
Yup, that's the one I tried.
[Magisk] kickthefreak:
im installing titanium backup without installing any busybox and it work perfectly
[Magisk] untouchablejay:
I want Viper4Audio to work so it needs busybox, don't know how to get busybox on here
[Magisk] cubandanger05:
I confirm the latest Android Pay and Pokémon Go are working without issues.
[Magisk] lil-devil:
I'm having problems with the systemless Xposed. Everytime I flash it pogo would stop working. What's your solution with it?
[Magisk] JuergenZ66:
Yes, I have used UPDATE-unSU.zip from osm0sis

http://xdaforums.com/showpost.php?p=63615067

Some people say they use both unrooting methods, first unroot within chainfires SuperSU app and afterwards unSU.zip in recovery.

To be sure you can check in TWRP filemanager if any su are left in /system/xbin/su, /data/su.img or /sbin/su and remove them manually before installing magisk.

see also matif525 post: http://xdaforums.com/member.php?u=4669975
[Magisk] Daedulus Minion:
Which version are you flashing? I think I read somewhere that 86.2 is the one that works. Not 86.5. Maybe I read it in OP
[Magisk] Didgeridoohan:
Systemless Xposed is no longer compatible with Safety Net. Uninstall or disable Xposed or use Chainfires suhide (where you currently need to use 86.2). Either way, this is the wrong thread for Pokemon Go questions, there's a dedicated Pokemon Magisk thread for that. Alternatively take it to the SuperSU forums and the suhide thread.

Good luck.
[Magisk] Daedulus Minion:
Haha thanks for the info. I had forgotten the suhide part. I don't play PoGo so had forgotten about this change.
[Magisk] Nexus11:
LG G3, android 7.0 (crdroid) everything is set fine but still can't access android pay or Pokémon. I may try again with a clean ROM install and edit if change.
[Magisk] EViollet:
Do you have Xposed?

If yes, then there's the culprit.

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[Magisk] knpk13:
Unless you've created it, there's no xposed for Nougat yet. ;)
[Magisk] C5Longhorn:
Thanks, I appreciate the follow-up. It turns out I can either disable or freeze with TiBu. It's the same. When I disable an app through settings, it shows it frozen in TiBu.
[Magisk] DroidJP:
I wasn't trying to go off of topic; in a way, it is still on-point because it so happens that apps like link2sd and app2sd relies on magisk to work. Otherwise, they be useless without magisk. Magisk 19.4 is what started it all in the first place.

Also to mention that you even brought up a good valid point that i did not realize. These 2 apps haven't been updated in almost a year and it seems to me that the development for these apps have ceased. Either the developers don't care anymore or not their main priority for these awesome apps at the moment.

When you now have devices with 64gb storage or more, could you blame these developers of not updating these 2 apps? I think the days of linking or even moving apps to sd are over. Could be wrong though.

Heck, i am not even sure what the future holds for magisk. Because as we all known. If you live in the U.S and wanting to upgrade your android phone to the next best thing. Good luck trying to find one with a unlockable bootloader.

For the life of me, can't figure out why is it a huge big deal to root nowadays here in the U.S?? Its your phone, you paid for it, why not?? Looks like my next phone will be international since my current phone is truly is the last U.S phone with it's bootloader being unlockable. It is the only reason why i have yet to upgrade.

This goes against what android is all about, even Google does not want us rooting anymore. Sure, maybe it has always been that way but were really quiet about it up until android 9 and especially 10.

Now i am reading that with Android 10, you won't be able to remove system apps even with root. Is this true?

But anyways, see how i brought up another issue (a good one at that) yet, still on topic as it relates to magisk.
[Magisk] Wolfcity:
OT: As TB is a really old app with some problems here and there (also the most ugly UI nowadays):

There is an app called Swift Backup (https://play.google.com/store/apps/details?id=org.swiftapps.swiftbackup) that can do

Backups (local and to different clouds) of systemapps, userapps and data, call logs, WiFi networks, SMS and app permissions in different ways, app downgrading and also deactivating (freezing)/uninstalling.On top it has a night mode/black theme. [MENTION=4487388]jcmm11[/MENTION] is right, SD Maid does a great job but if someone is looking for a successor of TiBu: Here you are.

btt.
[Magisk] FreeTheWeb:
I upgraded to ver 19.4 and both my bank aps: Barclays and Lloyds detected the root, with magisk hide enabled was working perfectly fine prior the update
[Magisk] Wolfcity:
Have you also magisk manager hidden?
[Magisk] Duck4Cover:
Natwest and Nationwide apps working fine, but you have to hide / rename the app in the manager settings.
[Magisk] JudgeDread11:
Times frame promised is November/December.

https://xdaforums.com/android/apps-...on-sd-card-link-apps-to-t3122919/post80036585
[Magisk] martyfender:
Thanks, I had not read every recent post there and missed that. last year,27th October 2018, he had stated:

https://xdaforums.com/showpost.php?p=77991248&postcount=5207

Real life probably got in the way. so he delayed it for a year, but it is good to hear that there might be an update.

Sorry, this is really OT here, so I will refrain from commenting any more.
[Magisk] 8lou:
Some apps start to crash, like play store and tinder, and I was suspecting of Swift Installer / Swift Dark. I did flash original firmware four times since yesterday. Now I suspect of MicroG module doing that. And I already removed it but nothing works. Could you help me?

Galaxy S8 SM-G950FD

Magisk 19.1

Magisdk Module 7.20

Same problem even on latest build after install MicroG module + YT Vanced

-09-22 01:09:09.639 3293 3324 I Magisk : * Starting MagiskHide
09-22 01:09:09.639 3293 3324 I Magisk : hide_utils: Hiding sensitive props
09-22 01:09:09.640 3293 3324 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms:snet]
09-22 01:09:09.646 3293 3324 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
09-22 01:09:09.651 3293 3324 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
09-22 01:09:09.655 3293 3324 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
09-22 01:09:09.659 3293 3324 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
09-22 01:09:10.248 3293 3466 I Magisk : ** late_start service mode running
09-22 01:09:10.248 3293 3466 I Magisk : * Running service.d scripts
09-22 01:09:10.249 3293 3466 I Magisk : * Running module service scripts
09-22 01:09:10.253 3293 3466 I Magisk : logcat: exec [service.sh]
--------- beginning of crash
09-22 01:09:23.189 3293 5047 I Magisk : ** boot_complete triggered
[Magisk] xunholyx:
You can check them with a logcat

Use ADB (there are tons of tutorials for that) or an app like Matlog. That seems to be the most popular one and works real good.

Personally, I usually use the Logcat Extreme app to grab a quick log, but use ADB when I want to go through them on my PC
[Magisk] molitar:
My Magisk Hide was no longer working after update. Found a solution though on Reddit it seems the random package name was lost on the update and had to be re selected.
[Magisk] JimZiii:
I just had some problems getting my play store certified but I solved it without any modules.

But I still can't find Netflix on the play store, am I doing something wrong?

I'm on 19.3 and play store certified
[Magisk] FreeTheWeb:
Can you tell me the steps.

For me i had restored the manager then re_hide magisk, tick the bank aps to be hidden and still doesn't work, for some reasons one of the aps keep uncheck the hidden box automatically, Barclays.
[Magisk] Josegames all:
Tried installing magiskhide props config?
[Magisk] keertikumar_ws:
I have an Pixel 3a XL and was rooted with Magisk and was in Pie. Switched to beta channel installed the v19.4 and followed instructions for OTA update. Got into a bootloop. Tried flashing full Q image of my device by removing -w flag and it's booting properly with the Data intact but without root. So tried boot path method to install Magisk and getting bootloop again. On googling, the issue I guess is that old magisk installation needs to be removed completely before installing the new one, have no way of doing so ? since there is no TWRP for Android Q in my device yet. Any idea how to do this without formatting data?

TL;DR Need a way to remove existing non working Magisk files without root and without TWRP and preserving data.
[Magisk] 8lou:
Hello folks,

I upgrade my S8 with official ROM (ZTO region without Google Pay) and rooted it with Magisk 19.1 – after that I get Safetynet fail.

I already tried toggle Magisk Hide, and edit fingerprint using MagiskHide Props, all that without success. What could be?

Using MagiskHide props I should use current fingerprint with different boot stage? default is device figerprint (default) security patch date (late_start service). I should use post-fs-data?

And whats difference to change it through Magisk Hide option (7) script settings?
[Magisk] Ch3vr0n:
Doesn't need to be removed. You need to use the canary manager, set the update channel to canary, then under advanced settings make sure 'keep encryption' AND 'keep dm-verity' are enabled. The 2nd one wasn't for me by default after updating to 10 and patching the boot image. This was causing the bootloop. Enabled both, patched boot image, loaded fine.
[Magisk] keertikumar_ws:
Thanks a lot for the response. Doesn't v19.4beta support Android 10? Also, tried checking both the checkboxes and then patching the boot image. Same issue :(

Attaching logcat
[Magisk] Didgeridoohan:
If your issue is caused by a Magisk module (possibly audio related from taking a quick peek at your log), you can use the new ADB command to uninstall all modules while the device is bootlooping.

Easiest thing would be to just start up terminal on your device, run the following command and then start up your device (with it hooked up to your computer through USB, of course):

Code:
adb wait-for-device shell "magisk --remove-modules"
[Magisk] Ch3vr0n:
19.4 does support 10 yes, works fine for me. Other than systemless hosts, I have 0 modules running
[Magisk] Tulsadiver:
Here's a core-only patched image you could use to boot into core-only mode with root.

fastboot boot image-new.img

https://mega.nz/#!JMJFwS4Z!nltRi59yFHB-vuVE6gqws2DQsE_5z-au1ChuUb0R6c4