yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Since I don't think you've removed any of the install scripts (or how did you edit the module?), it could be an issue with the zip itself. Try creating it with a different app/program.
[Magisk] Gregbmil1:
I had to unzip the module and used Mixplorer to edit. Lol, now that I think about it, I'm sure it's the zip I made after I edited it. I have no clue how to make a flashable zip and I put very little effort into zipping it back up😁.
[Magisk] Didgeridoohan:
Unzipping the module, editing it and zipping it again should work. Sometimes I've seen issues with how some file explorers zip the file though, and Magisk can't read it. That's why I suggested trying a different app to rezip the file.

You can always upload the file here so that I or someone else can look at it.
[Magisk] zgfg:
When I play with TWRP and Magisk modules ZIP files with MiXplorer:

I always Extract zip to the folder, make changes there, save, then select all files and folders in that extracted folder and Archive them back to the new zip file.

(Making changes on the fly into the zip file may result with un-installable zip)
[Magisk] J.Michael:
I have seen instructions that emphasized the importance of a few files being the first to be inserted into a new archive.

I don't remember what I was playing with. It might have been an epub. It might not have been a zip. I assumed the target program was lazy or minimized, and needed the META-INF directory (or whatever it was) to be the first item in some table.

Maybe find the ZIP options that list the TOC in internal (not otherwise sorted) order. Then compare the original to the modified.
[Magisk] Cruzy12100:
For me these are the settings available for the magisk app. For the reboot app suggested by you, the magisk popup did not appear. I can confirm I have root as I again checked it with the root checker app on play store (One with the # symbol)
[Magisk] zgfg:
Sorry, don't know your ROM, launcher, device settings, but apparently something is preventing the Magisk app to popup

I can only recall that we similarly had another user and after few days and numerous posts he eventually found that he had other apps with screen overlay permission

IMO, it's not anything about the root or Magisk, but something similar
[Magisk] cheshyre:
OnePlust 8T, newly rooted with Magisk (but not TWRP)

Where do I place my hosts file for adblocking?
[Magisk] Cruzy12100:
Ok. I will try to find the solution for this. My device is OnePlus Nord with aex extended rom. Launcher is stock launcher provided by this rom . It's a combination of several different roms.
[Magisk] zgfg:
Enable Systemless hosts and reboot. Then use /data/adb/modules/hosts/system/etc/hosts

Upon reboot, content will be copied by Magisk to /system/etc/hosts
[Magisk] cheshyre:
Thank you

so

much.

I couldn't find that documented anywhere.

Browsing without my hosts file is so ad-laden as to be nearly unusable.
[Magisk] Gregbmil1:
So it can still be flashed if zipped with Mixplorer? Mixplorer is great isn't it, lol. A file browser is one thing I never search for anymore. Mixplorer does it all
[Magisk] Didgeridoohan:
In theory, yes. But like I posted earlier I've seen instances where a zip created with some apps won't work (I've never tested Mixplorer though). And also, easiest way to get help would probably be if you posted the zip that's giving you problems...
[Magisk] bmrz1981:
Mainly because as nerds we can :-) Just joking. You are right.

Usually I replace contact/gallery/music apps and edit hosts files. For me a device that can be reset any time but still preserve the modifications is a must.

But agree with your point.

PS: Finally I managed to find the offending app.

/system/priv-app/Velvet/Velvet.apk

After I deleted this by su - many google apps disappeared.
[Magisk] l3g0r:
hi is it posible to config magisk to boot root all the time?
[Magisk] zgfg:
What does it mean?

When you boot with Magisk, all apps granted root have root, Magisk modules are i initiated, etc
[Magisk] l3g0r:
allways , power on normal but with root.

Without recovery reset buton.
[Magisk] pndwal:
If you're meaning a Magisk in Recovery (type III device in document linked below) installation, and I assume you do since other devices always do this, it seems you may be able to reboot directly to Recovery to get System w/ Magisk root (I'm not sure about mechanism to get to rooted system in this case), but starting from power-off it does seem you'll always need use key combo and timed key release:

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Further, John says:

https://topjohnwu.github.io/Magisk/boot.html#piecing-things-together

Nb. There are exceptions to the requirement for Magisk in Recovery for type III devices; Xiaomi is a notable one.

Seems this is part of the limitation of the need to install Magisk to recovery partition, and apparently it has become even more inconvenient for users of some devices (eg Samsung) on Android 11 due to new requirement to have computer or headphone etc connected to USB in order to use special key combos for recovery, safe-mode etc.

😬 PW
[Magisk] zgfg:
Then, it's specific to your device where there is no Boot but Magisk installs to Recovery and sorry, you must boot through Recovery
[Magisk] J.Michael:
Did you try disabling Velvet?
[Magisk] ipdev:
Velvet is the Google app. ;)

package: name='com.google.android.googlequicksearchbox'​

Google - PlayStore - Link

Velvet is the apk file name used when GApps is bundled with the system.

or installed with a GApps install.

---

I use zgfg's module for debloating.

Magisk Module Systemless Debloater (REPLACE) - xdaThread - Link

It worked on every device, factory and custom rom I have tested it on. :)

Including stub-app(s). ;)

Magisk Module Systemless Debloater (REPLACE) - xdaThread

Post # 30 - Link | Post # 36 - Link

Cheers. :cowboy:
[Magisk] Mossgftygvhh:
Hi a I just want to say I'm new to rooting. I've tried all the appto root and what I can't get done is I can't get a bot.ing without a recovery not going to work I'm on a ZTE n9137 tempo x look for help with a recovery
[Magisk] zgfg:
Suppose that your ROM comes with YouTube pre-installed as system app (under /System, /Vendor, /Product, not under /Data/app), and with version 16.32.34 (or any version STRICTLY HIGHER than 16.29.39)

Suppose, you want to install YT Vanced, root. Currently, their latest patch is for YT 16.29.39, hence Vanced requires you (first step) to install YT (exactly) 16.29.39

But you cannot downgrade the preinstalled YT to the older version, and you cannot uninstall YT as the pre-installed system app.

Hence, you must first debloat YT to be able to continue with Vanced YT root installation

However, methods like:

1) adb shell pm disable-user com.google.android.youtube

or

2) adb shell pm uninstall -k --user 0 com.google.android.youtube

do not help here - in both cases the YT package com.google.android.youtube, pre-installed as the system app, remains on the system.

First command only disables the YT package, second command 'uninstalls' but only for user 0.

(Indeed, preinstalled YT package is still on the system, you can always simply revive YT by executing the 'opposite' command and you don't really need to install the YT apk again:

1) adb shell pm enable com.google.android.youtube

or

2) adb shell cmd package install-existing .com.google.android.youtube

respectively - pay attention to "enable" and 'install-existing")

Hence, when you try to install YT 16.29.35, installer will immediately find that newer package was still present on system, and its installation of the older YT version will fail

Hence, to install YT Vanced root, whose first step requires downgrading YT app to its official 16.29.35, you have to properly debloat the preinstalled YT and fot that you have two options:

3) (Hardly) delete the preinstalled YT app (from /system/app, /system/priv-app, /vendor/app, etc, wherever you find it).

But that's not possible for phones that were RELEASED with read-only SAR (then even TWRP cannot delete the YT folder/app from the /system partition)

4) Debloat by systemless manner, using Magisk. In that case Magisk will 'mask' the system preinstalled newer YT app every time when booting, by 'replacing' its folder (file) with an empty one (by using the Magisk mount mechanism).

After that, YT instsller will no more find the (system) preinstalled newer version of YT app. I.e, it will be able to install the YT 16.29.39 (split/bundled app version), which is the first step required for installation of the Vanced YT root (second and last step will be configuring Magisk to mount the YT base.apk, patched by Vanced team, over the official YT base.apk v16.29.39, in /data/app, on every boot)
[Magisk] DiamondJohn:
@zgzf never say never. One can always find the extreme cases for every situation. Nothing is absolute. However, for the most part, disabling and hiding works. It *MAY* even work to enable downgrading. I have not checked. Even though I have one of the latest pixel phones form google, and update every month to the latest firmware, I still have not personally had the issue of downgrading.

90-10 rule. I have the feeling you are just looking to catch me personally out.
[Magisk] iooxda:
Thank you, I am working on a phone install script, this is very helpful

Is it also possible to install a Magisk module from a local zip file by launching Magisk with this intent and supplying the file path as an argument?
[Magisk] ipdev:
@zgfg

@DiamondJohn

Hi. :)

I have been a ghost on xda for the last few weeks due to time restraint.

I hope my free time comes back soon. Lot of posts [few PM(s)] I need to respond to. 🙃

--

Just to note, Google does not include the most recent version of Google apps in the stock releases.

Pixel August 2021 build. rq3a.210805.001.a1

package: name='com.google.android.youtube' versionCode='1512439256' versionName='15.18.39' compileSdkVersion='30' compileSdkVersionCodename='11'

Google likes to control what is installed depending on your account.

A common version if you are not logged into your Google account.

In this case, YouTube v15.18.39 is the system install.

So Google can "update" YouTube to any version above v15.18.39.

If you manually install a version of YouTube above (or different variation) what Google thinks should be installed on your device.

Google will offer an "update" to the version that should be installed.

This could be the actual version or a variation like DPI resolution.​

Using Pixel for an example.

Google also uses stub-app(s).

The stub is installed in system and the full app is installed in userdata.

The stub allows it to be a system app without actually being installed in system.

This allows them to keep system smaller (Super and Virtual partition crap).​

---

It is very rare that the system installed version is equal to or above the common version available from PlayStore.

Regardless of device or system (ROM).​

---

I actually ran into the issue that zgfg described a year ago.

🤣 I did not realize Google has not updated YT in the stock Android 11 builds since Beta 3. 🤣

I made a quick module at the time as a work-a-round.

GitHub - Link

It was the only way I could install a version of YT older than 15.18.39.​

Cheers. :cowboy:
[Magisk] zgfg:
I chose the example with YT as something of potentially more interest for the broader auditorium.

And it was based on the real issues with one or two Vanced YT users from the corresponding XDA thread (a year ago or so)

I have personally experienced with some Xiaomi system apps I wanted to downgrade

Sorry for your feeling but to the contrary. I like your posts because they are unlike many other standard/repeating things and I want to follow-up discussion
[Magisk] Soumy1234:
Hello there. Your status bar caught my eye. Would you mind if I DM'd you about it?
[Magisk] JFDee:
Hi everyone,

info question here: I wanted to report an issue with Android 11 on Samsung Tab S6 on the Github site for Magisk, and it said:

"Only report issues with the Canary build"

Now I can't seem to find that Canary branch. Does anyone have information about it? Has development stalled perhaps?
[Magisk] Didgeridoohan:
Development on the official branch is currently stalled as we're waiting to see if John will manage to work something out with Google...

There is at least one forked branch being actively maintained, and you can find plenty info on that in this thread (check the most thanked section or search for Magisk alpha).

Regarding reporting bugs on the official GitHub you'll need the Canary release, yes, and you'll find that linked under "Downloads" on the main page of the Magisk GitHub repo.
[Magisk] JFDee:
Thanks a lot for the pointers! I'm more up-to-date now with respect to the general situation.

I hadn't even regarded the little badges under "Downloads" on Github before - shame on me!
[Magisk] pndwal:
Just a heads up FWIW.

LSPosed users may be interested that the

https://github.com/LSPosed/Magisk

branch has a number of sub branches (these seem to be deleted regularly after testing) w/ what are clearly test fixes.

These sub branches have @vv2060's Alpha commits merged also (he's a prolific contributor to

https://github.com/LSPosed/LSPosed

branch also), as well as many from @yujincheng08, and a few from.@canyie (also LSPosed contributors).

The merged commits in

https://github.com/vvb2060/Magisk/tree/alpha

itself also include those from these guys.

As there are apparently no published builds in

https://github.com/LSPosed/Magisk or sub branches, it appears these guys are all testing LSPosed with vv2060's Magisk with Alpha fixes. It also follows that Alpha Magisk changes will include some fixes for LSPosed compatibility. PW
[Magisk] yujincheng08:
vvb2060 is also one of LSPosed's devs.
[Magisk] pndwal:
Thanks, and yup, "prolific contributor"! (Didn't say Dev as members appear to be unlisted.)

Good to see you are present on XDA... So far we have not had an XDA point of contact for Alpha. 😜 ...

And MANY thanks for your contributions to an active Magisk fork especially! PW

PS I'll take the liberty of announcing imminent LSPosed 1.5.2 here for any watching...
[Magisk] pndwal:
... Speaking of OT, all OP does lately is post OT!... 😜

Some of its pretty funny though... And it's good that he can even agree with XDA editor-in-chief at least on twitter; ED posts more Xciting Delightful Anecdotes there too!

(In case you're worried, the following is relavant in so far as it pertains to obtaining / sharing open source code.)

www.twitter.com/topjohnwu/status/1428834837369028609

Anyone have a UMIDIGI (You, Me, Digi[tal]) phone?

Kinda wish I spoke Chinese now... Poor Ben... Naomi Wu certainly gives unique insight into Chinese corporate mentally / tactics (incl. 'developmental stage'). PW
[Magisk] Homeboy76:
New

The latest SDK Platform-Tools: r31.0.3
[Magisk] spiderjuka:
Hello.

Could someone describe step by step how to install Magisk alpha assuming that I currently have Magisk v23 installed?

Thank you
[Magisk] Homeboy76:
To get the latest information on Magisk alpha using the XDA app: Tap

Search this thread (at the top of the page)

, type

alpha on the Search line

, type

pndwal on the by: member line

then tap the Search button.

If you are having problems with Magisk Stable or Magisk Canary, try using Magisk Alpha (vvb2060 alpha). Read @zgfg post.
[Magisk] zgfg:
Please search back for Alpha in this thread, it was really discussed and described previously

Nothing special, install Magisk Alpha application (if it complains, uninstall your previous Stable/Canary application but not the Magisk itself), then install Magisk Alpha as you usually install Magiskk (through TWRP or by patching & flashing)

Also as a general rule (applicable for bigger Magisk upgrades):

Unhide Magisk App (former Manager) before upgrading (in this case, before switching to Alpha app), otherwise you will end up with the two apps/mngrs being in collision one to another.

In theory it should not happen, but in practice it had happened here to the tons of users (specially those upgrading from the ancient versions of Magisk, etc).

Then, it's always, why my Magisk app shows that Magisk is not installed (i e., it shows empty for the installed version), why I don't see any of the installed modules, why it doesn't ask for root grants, etc
[Magisk] pndwal:
More relavant OT / Heads-up 😜 :

Sammy users w/ unlocked bootloaders may want to defer OTA updates to avoid heartache if they like using cameras (especially on high-end devices).

Members may be aware of recent discovery re. Samsung Galaxy Z Fold 3 - unlocking-bootloader-will-disable-the-camera issue reported by @白い熊

https://xdaforums.com/t/unlocking-bootloader-will-disable-the-camera.4321957/post-85505605

- confirmed by @ianmacd

https://xdaforums.com/t/unlocking-bootloader-will-disable-the-camera.4321957/post-85522359

(I note his initial confidence regarding a fix being discovered using Magisk / root while acknowledging that this cannot be banked upon.)

- reported by XDA

https://www.xda-developers.com/samsung-galaxy-z-fold-3-unlock-bootloader-broken-camera/

- and commented on by John Wu

www.twitter.com/topjohnwu/status/1430233185036562437

It now appears this issue also affects other Samsung devices including Galaxy S20 after official updates:

https://xdaforums.com/t/unlocking-bootloader-will-disable-the-camera.4321957/post-85532367 PW
[Magisk] DavidWolfen:
Thank you so much because I had never noticed the badges either ^^Uu finally got Canary easily
[Magisk] SteveJames99:
NEED HELP:

Has anyone had issue when granting an app root permission causes phone to freeze then restart. (Only happens to certian root apps)?
[Magisk] zgfg:
It must be something specific to your app:

- you start the app and it wants to do 'something' that requires root

- the app asks for root and you grant it

- the app now goes to do that 'something' but it causes freeze and restart

You should investigate the logcat to find what happens just before restarting (supposidely, app did that 'something')

Also, now you did grant the root to your apo. Upon restarting, open Magisk, Superuser tab and check if your app now indeed has the root grant.

If so, then start the app again (this time it should not ask for root if it was previously granted) and check does it freeze again (trying to do that 'something')
[Magisk] SteveJames99:
It freezes and restarts as soon as i press grant, but when i go to check in magisk upon restart if root was granted, doesnt even show up, i have checked the logcat but doens't show any logs for that app. (The app in question is 'zANTI').
[Magisk] pndwal:
Like which? Which phone? ROM? Latest Magisk? PW
[Magisk] zgfg:
Hmm. For the other apps when you grant the root everything goes regularly (no freeze/reset and next time the root is granted)?

Check also in /cache magisk.log and magisk.log.back (anything there about the root granting to zANTI)?

Edit:

Despite the warnings (and indeed some suspicious permissions asking: Read phone status and identity, incl. phone number and remote phone number in a call), I installed zAnti (from zimperium), opened, granted root and let it scan my home WLAN. I had no freeze, no restart, no issue (Xiaomi Mi 9T, A11 Xiaomi.eu).
[Magisk] SteveJames99:
I have checked the cache magisk.log, .back and nothing shows for zANTI.

(Samaung galaxy s20 fe, A11, Oneui 3.1)
[Magisk] SteveJames99:
Samsung Galaxy S20 fe

Oneui 3.1

Magisk v23

A11
[Magisk] zgfg:
As said, I did install zAnti, ran, granted root, let it scan my home WLAN, no freeze or restart
[Magisk] SteveJames99:
Must have to do something with my device specific

Edit: The app works fine denying root permission when dialog pops up, but not useful without root as it needs it.
[Magisk] pndwal:
Interesting similar (old) issue reported here

https://xdaforums.com/t/sm-g930f-keeps-rebooting-root.3680103/

No obvious solution w/ Magisk however, but may give you a clue...

Also, what modules are you running?

If using Universal SafetyNet Fix especially (not test2 module) w/ OneUI, try with modules disabled.

Incidentally, are cameras working on your S20? PW
[Magisk] DiamondJohn:
if ir freeze and reboots then last kmsg is the place to look. Its the logcart before the reboot.
[Magisk] SteveJames99:
Here are the magisk modules i have installed.

And yes camera does work
[Magisk] SteveJames99:
Where do i find that?
[Magisk] SteveJames99:
So i just disabled all my magisk modules and it worked, now to firgure out which module is causing it.

Edit: So i re-enabled one by one to see which module was causing it to freeze on me, but eventually all was enabled agian and seems to work now, i have no idea why its working now.

Edit 1: I have now tired another root app ' kali nethunter' and seems to be doing the same thing, tried disabling and re-enabling each module one at a time but sitll causes phone to freeze.
[Magisk] pndwal:
Just a thought, if you needed Legacy mode for V4A, which method did you (originally) use to enable NEON driver (ie Normal operation)? PW
[Magisk] SteveJames99:
I installed V4A app which then installed the drivers and installed the magisk module for me, then enabled legacy mode in V4A settings for it to work.
[Magisk] pndwal:
Ah, so no special scripts / SELinux fiddling etc... good.

FWIW, I don't install app first; pasting my method:

I'm running Viper4Android FX 2.7.2.1 w/ 2.5.0.4 driver, just set up from Magisk repo, on stock MIUI Android 10, RN8T.

After installing and setting Legacy mode (Compatibility mode does nothing for me), Driver Status is Abnormal, but driver is always reset properly / working (for Legacy mode) simply by disabling module and rebooting, then enabling and rebooting again (2 reboots). PW
[Magisk] SteveJames99:
V4A works for me, i was able to get zANTI to work but another root app 'kali nethunter' is doing the same thing as before (freezing and rebooting my phone), disabling all magisk modules but still didnt work.
[Magisk] pndwal:
May need to analyze logs as suggested by others...

How To / log types:

https://www.didgeridoohan.com/magisk/MagiskHelp#

👍 PW
[Magisk] SteveJames99:
Here is the last_kmsg log, hopefully this will help find the problem.

Edit: im wondering if its got something to do with selinux being enforcing.
[Magisk] rudim12f:
Need help

I am in poco x 3 i used application name mobile jkn this apk not run even i just install magisk.apk

Attached ss before instal magisk.apk and the one after install magisk.apk(not yet root)

I am doing several time but no luck

But for the bank apllication no issue just only one apk i mention above

Thank you
[Magisk] pndwal:
Have you tried setting 'Hide the Magisk app' in Magisk settings? PW
[Magisk] rudim12f:
I am not setting anything as i wrote device not get root only install magisk manager
[Magisk] zgfg:
What is the purpose of installing Magisk mngr/app without Magisk?

If you need it as a SafetyNet checker, there are other checkers available
[Magisk] rudim12f:
Have you seen my ss before device got rooting just install magisk manager my purpose is just to prove that mobile jkn not running even just install magisk manager
[Magisk] zgfg:
But I don't understand why that app would not run "even if you install Magisk mngr"?

If that app does not run without Magisk apk - why would it run when you install Magisk mngr

If your app needs root then it needs Magisk itself in the first place

On the other side, there were some apps that used to wrongly guess that phone was rooted (and then they stopped working) just if they found Magisk apk (although Magisk was not installed).

Hence, they did run when Magisk apk was not installed, but did not run if Magisk apk was installed

Sorry, but I cannot imagine why would a particular apk need Magisk apk, without Magisk, to run

And then, I don't see how is that related to the Magisk topic here
[Magisk] shoey63:
Stay tuned folks

https://twitter.com/i/web/status/1431380423762841602
[Magisk] pndwal:
Ain't he a tease!...

Re Sammy Cameras

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85534107

XDA Editor-in-chief is a tease too:

www.twitter.com/MishaalRahman/status/1430946260383584257

A Magisk module "containing the patched camera provider libs" may be coming soon.

www.twitter.com/MishaalRahman/status/1430987219569872899 PW