yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
Can I switch Magisk versions from Magisk Delta 26301 to Magisk Stable 26401 simply by putting a URL pointing to the URL for the Stable 26401 JSON file into the Custom Update Channel in the Magisk Delta Manager and performing the resulting update?

I know this would work if the original and updated versions would be the same Magisk release (i.e., both Stable or both Delta), but can I also count on this to work if I go from a starting point of Delta to a newer release of Stable?

Thank you in advance.
[Magisk] xcl1pse:
Umm.. I think not since magisk delta and normal magisk is quite different, you need fully uninstall magisk delta to switch to normal magisk. Also 26401 is canary, not stable
[Magisk] HippoMan:
OK, thank you! Yes, I meant "canary". I just said "Stable" to distinguish the Magisk version from Delta and Alpha.
[Magisk] sawdoctor:
There's a tutorial somewhere how to switch from any magsik version to another, try searching on xda. It was pretty straightforward from what I remember
[Magisk] HippoMan:
I was searching for it and couldn't find it, and that's why I posted here.

But I'll do more searching.
[Magisk] zgfg:
Modules should survive but you may have some troubles with DenyList

Open magisk.db for Magisk Delta and you will see inside (among others) Hidelist and SuList

All apps you select in Delta for Configure mount, Delta saves to Hidelist - not to DenyList.

Hence when you switch to official Magisk, official Magisk will ignore Delta's Hidelist and you will once again have to put those apps to DenyList

Even more troubles if you used Unmount modules by Default in Delta. Delta saves them to SuList but official Magisk does not care about that whitelist mode in Delta, hence again you will have to configure DenyList from scratch in official Magisk

And (as I answered you in Delta thread), Delta actually does not install magisk32, magisk64, magiskboot, etc to /data/adb/magisk but to /data/unencrypted/MAGISKBIN (and just links /data/adb/magisk to that MAGISKBIN folder).

Hence you will have dirt leftovers there upon 'updating' from Delta to official
[Magisk] HippoMan:
OK. Thank you! Yes, I'm already prepared to have to deal with the few dozen programs in my Delta whitelist. I know that I'll just have to bite the bullet with all that.
[Magisk] Linux4life2211:
Is there a way to extract the magisk mods from my previous phone into a the familiar .zip files that I can transfer to my new phone and then install from storage?
[Magisk] pndwal:
Probably what I wrote here:

https://xdaforums.com/t/discussion-magisk-alpha-public-released-fork-vvb2060.4424845/post-89112995

FWIW, I'll reproduce this with extra (embellished) details here...

For any wanting to downgrade, or change between Magisk forks from different Devs, or to CI builds from Magisk Actions etc:

1) You can use Direct Install to install official Debug App and Magisk which will bypass magisk.d daemon version and signature checks, then you'll be able to take Direct Install again to install older Magisk, official TJW, CI TJW/other test builds, Alpha or other forked builds etc...

Another simpler method to bypass these checks also using existing root for downgrading (or changing to any different build) is:

2) Rename older Magisk.apk to .zip and flash from App as a module... This allows downgrades and changes to differently signed builds by installing core Magisk (mask) including the down-dated and differently signed daemon (magisk.d) that performs App version/signature checks before installing the App...

To avoid unexpected issues, delete /data/adb/magisk.db file and /data/adb/magisk directory contents and reboot... Magisk configuration files will be rebuilt (modules will persist, but need to set up superuser apps, denylist etc fresh; alternatively, deleting everything in /data/adb will remove all configuration data incl. modules)...

Before opening, uninstall App and install older version...

Nb. I believe that method 2) cannot patch /recovery partitions so this will probably be of no use for devices requiring Recovery mode Magisk (Magisk in /recovery ramdisk), ie. Legacy SAR A-only devices w/ bootloaders incompatible with ramdisk in /boot partition like Samsung S10... It should work for all other devices (legacy ramdisk, A/B SAR, bootloader compatible A-only SAR and modern 2SI ramdisk boot-types) however.

🤠 PW
[Magisk] pndwal:
Copying and pasting the Install module configuration and overlay data to a different installation will be fraught but may work...

Unlike apps, module .zip installation archives aren't duplicated, so the basis answer is No... You should probably just save them yourself if you wish...

However someone else may know if/how third party Fox/Androcity or other module repo managers can maintain such files/module lists for your purposes... I don't use them personally...

🤠 PW
[Magisk] pndwal:
Aside from incompatible configuration, I imagine the modern anti-downgrade and signing checks would thwart you efforts since even with the correctly configured raw JSON set as URL, channel settings only update the Magisk App since 22.0 (you next update the Magisk mask, ie loaded binaries, itself) so running daemon will be certain to forcibly uninstall the App in this scenario... See my post above...

I personally think that these recent measures to protect Magisk users from themselves (largely from @vvb2060, "Nangong Xueshan"/"Shanshan") are overkill myself and have led to frustration in GitHub Magisk issues especially when users are asked to try CI builds w/ experimental fixes and find they cannot swap channels/builds etc as was previously possible... Anyway, there's always ways around problems like this... 😜 PW
[Magisk] pndwal:
Another interesting Magisk inclusion:

Add LSPosed launch test

topjohnwu committed yesterday

Well systemless XPosed was John's baby after all... Guess it's good current iteration and LSP development is getting tacit support. 👀 PW
[Magisk] HippoMan:
Thank you very much for this. It's definitely very useful information.

I'm not looking to downgrade per se, but rather, to switch from Magisk Delta 26301 to Magisk Official 26401, which looks like an upgrade to me, at least w/r/t version numbers. But given that they are two different Magisk forks, perhaps this would still need to be treated like a downgrade ... correct?
[Magisk] pndwal:
No, not a downgrade block (version check), rather a block for change of fork/build tree (app signing check), but while vv implemented two different 'protections', they both work in effectively the same way to forcibly remove 'invalid' Magisk Apps and the same bypass methods work as I indicated in bold... Ie updating the daemon, magisk.d, before the App prevents the checks from failing by changing anticipated app version and signing while using Debug builds as a bridge to change Magisk works as both checks are disabled in debug builds... In the latter approach you would use existing root to change builds by direct installing (or .zip install from recovery or as module etc) twice...

Signing checks and bypassing information (debug use) appeared in Magisk main page but has now been moved to build.md doc:

https://topjohnwu.github.io/Magisk/build.html#signing-and-distribution

The fact that the same method works for downgrading I just discovered by watching Magisk changes and trying... 😉 PW
[Magisk] HippoMan:
OK, thank you. I see.
[Magisk] Sanman99:
i got a boot.img for Derp ROM

and patched it...fastbooted and Magisk app not showing Direct Install

tried a few versions

i fastboot Flashed it

now Magisk app disappears no matter what version i install

phone is rooted, but no Magisk app

Magisk was crashing a lot, system ui crashing

but i rebooted and it seems ok besides Magisk app disappears (whoosh)

also on another computer, can't get USB drivers for Google Pixel installed in Device Manager

the Update Drivers just says 'the best drivers is already installed'
[Magisk] pndwal:
So you likely updated Magisk with App hidden as stub with custom name...

While Devs made fixes and said issues were resolved they're not, and Magisk often doesn't update hidden stub properly but tries to install full app, or you're trying, with hidden app still conflicting in the background... This is a primary reason for Magisk Installed = NA.

Locate you previously hidden Magisk App by its customised name ('Settings' is default) in device settings, Apps, and uninstall it and any other instances of Magisk App hidden or full... Then install version you flashed again...

This issues are avoided by taking Restore the Magisk app before reinstalling/updating Magisk, especially after ROM updates...

Please report if this was the issue... Usually is but could be other... 👍 PW
[Magisk] Sanman99:
Wow exactly

And yeah even Direct Install is appearing even though I did Fastboot Flash instead now

Not sure what you mean by Taking the Restore Magisk

But if it's to disable hidden or uninstall it, yeah this worked great

Thank you!
[Magisk] pndwal:
It will appear as long as App is able to detect existing Magisk root... Multiple apps cause the conflict..

... Well you must have taken "Hide the Magisk app" Magisk Settings option originally to use Magisk in obfuscated stub apps data... Taking the "Restore the Magisk app" option simply restores the full (unbidden) App, and updating/installing Magisk (core binaries/mask) generally works without issue from full App...

Welcome!... PW
[Magisk] J.Michael:
Does this mean that you originally patched a boot image, flashed it with fastboot, booted, opened Magisk app, and you noticed that "Direct Install" was not being offered -- even though you didn't really want Direct Install because you had already flashed the patched boot image?

And then you fastboot flashed again, and now the Magisk app keeps disappearing?

Does the Magisk app disappear while you watch; i.e., do you install Magisk app, use it, go about your business, and later notice that there is no Magisk app?

Or do you mean that when you boot, there is no Magisk app, even though there clearly was a Magisk app earlier because you used it to patch the boot image that you just flashed before the latest reboot?

I saw @pndwal's response, but I don't think he covered the possibility that what's happening is: You keep trying different Magisk versions. If you are piling up a bunch of patched boot images, maybe you are occasionally flashing a boot image that was patched with a later version of Magisk than the version of the app currently installed. @pndwal has described some kind of "safety" checking that I thought would actually delete the Magisk app if the Magisk felt it was not good enough.
[Magisk] Sanman99:
PW got it exactly

And well, I meant I Fastboot Booted.. That's what I meant by Fastbooted

I didn't flash it at first, no

I had an old hidden install and an OTA removed root

Magisk had no Direct Install option when Fastboot Boot to temproot

Then after flashing it I got lots of crashing system UI, still no Direct Install (since I had the hidden app still there it seems)

And then every time I click the Magisk app, it vanished. More and more it wouldn't even load. Just started disappearing completely each time I install, if I click it... Whoosh

So PW was accurate

I'm not sure about this other possibility you mention

I only Flashboot Flashed once

So uninstalling the Hidden fixed it and then I was able to do the menu it asked to reboot and fully install (it popped up asking to)

Thanks!
[Magisk] Ambivalent_0_o:
maybe you guys can help me. i was offered magisk 26.4 via the magisk app and did the update via direct method. then i updated all modules incl. play integrity fix v13, lsposed, knox patch etc. everything went smoothly.

everything went through without a hitch.

at some point during the restarts, all my ui customizations and app settings and permissions were gone and i was logged out everywhere.

since then it is no longer possible for me to log in to my google account, it always wants to verify my identity after I have entered my PW correctly, which then fails, whether by sms/call, backup code or otherwise. some google apps also tell me I have no internet connection or that authentication needs to be completed. see screenshot.

i don't know what to do anymore. can't find the problem on the net :-(
[Magisk] badabing2003:
Can you login from a desktop computer or any other device?

If the answer is no, then it has nothing to do with your phone and I'm afraid more likely that someone got into your Google account, logged you out from all devices and changed your password.
[Magisk] Ambivalent_0_o:
Yes, I can access everything normally on my desktop and even in Chrome on said android device it works fine. The problem is somehow the play services. even though I passed all the play integrity tests, I think my device somehow got flagged for play services or something

edit: i can log into my account on google.com using chrome, but i can't log into my account in chrome browser itself, if that makes sense.
[Magisk] pndwal:
The latest Stable Magisk is not actually stable for various Samsung, some MIUI (and other?) devices...

I mentioned the issue will file descriptor sanitization logic and linked app / UI related issues here originally:

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

here:

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

and

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

It was known but John's fix wasn't enough...

Canyie's latest fixes are now merged upstream:

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

Suggest you revert to 26.3 till next build arrives, which may be any tick of the clock... 🙃 PW
[Magisk] Ambivalent_0_o:
oh man, thanks for that information!

thought i'd have to factory reset at the end of the road, but i definitley i can make it a few days to the next build - too worried about the next hustle if anything fails while downgrading 😅
[Magisk] pndwal:
👍... If you do want to revert, see this:

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

🤠 PW
[Magisk] Ambivalent_0_o:
I have downgraded to 26.3 and now 26.2 with no success. I now get the authentication SMS and it auto fills the code but then says "error, please try again". And when google tries to send a prompt it shows my device as LG NEXUS 5? I have an S10
[Magisk] J.Michael:
Does not make sense.

What is the Chrome browser itself, if not the Chrome you used to successfully log into google.com?

I think you should flash an unpatched, stock, ROM and see if your problems go away. It might be a good idea to delete or at least rename the /data/adb directory first, so random module problems don't interfere when you later re-install Magisk.

I don't know if it has anything to do with your problem, but there used to be a warning in Odin (you don't say what device or Android, so why not?) to remove your "account" from your device before flashing.

Have you tried "Force stop" and "Clear cache" (and maybe "Clear storage") on problem apps / services / processes? (I have no idea how many apps before it works or you give up on this approach. Try one, then try a few, then decide if it's a sufficiently appealing approach that you want to blast everything.)
[Magisk] HippoMan:
Is there any way which *doesn't* require a factory reset which will allow me to delete the /data/adb stuff on a previously Magisk-rooted A13 device which is now un-rooted?

I screwed up one of the devices that I have been using for testing, and I don't want any such /data/adb remnants to get in the way of flashing other items (both Magisk-related and non-Magisk related), but at the same time, I want to avoid wiping everything that is already installed on my OS, if possible.

At worst case, I will bite the bullet and do the factory reset, but I prefer not to, if there is any way at all -- even something hacky and convoluted -- which will allow me get rid of the /data/adb stuff without wiping and without being on a rooted device.

Thank you in advance for any ideas and suggestions.
[Magisk] J.Michael:
Why reject being rooted? Install Magisk, boot to safe mode, boot back to Android, delete what you want.

Check PixelFlasher, it has an option to use a special version of Magisk that does not load modules.

Install TWRP. Pick one that has some file manipulation capability.
[Magisk] HippoMan:
Thank you very much!

Unfortunately, I can't install Magisk because of the way I hosed my device. Something is getting in the way of that working when I try to flash the image patched by Magisk, and I'm pretty sure it's the old /data/adb stuff.

Oh! ... but wait! I had previously installed OrangeFox on the device, which I forgot about. Your mention of TWRP reminded me. I just now went into Orange Fox, and I did indeed successfully get rid of /data/adb!

Anyway, PixelFlasher wouldn't have worked on this device, unfortunately, because it's a Nothing 2 device.

But no problem, because as I mentioned, OrangeFox saved the day!

Thank you again.
[Magisk] dcarvil:
Is your bootloader still unlocked? If so, you should be able to temporarily root by "fastboot boot magisk-patched.img" to remove /data/adb, then reboot back to non-rooted. I have not tried this, but I think it should work.
[Magisk] J.Michael:
Crap in /data/adb does not get in the way of flashing. It only gets in the way of booting. The Safe Mode followed by rebooting was supposed to bypass any modules causing problems. If the problem was the Magisk database, I don't know of any way to get around that.

The reference to PixelFlasher was just to give you a lead to a version of Magisk that doesn't load modules.

PixelFlasher may well work on a Nothing 2. I think the first question is whether you use fastboot to flash.
[Magisk] dimm0k:
does /data/magisk/resetprop --file replace or append to the current build.prop?
[Magisk] AnDroiDHackxr:
Here it is with advanced logging. And I'm not sure how to do that.
[Magisk] Henry1231:
Magisk wont start

Download and updated to the latest version of magisk and now it wont start. Just stays on the logo screen. Ive tired uninstalling it but still wont work. Any help
[Magisk] dimm0k:
[MENTION=1162986]Captain_Throwback[/MENTION] can you share a module or two of yours?? whenever I try to flash my own module via Modules > + > Flash Module Zip I keep getting the message "the zip is not a magisk module". I've even tried using the "Google_Assistant_Enabler-n" module with the same result.
[Magisk] jcrompton:
What would be the appropriate way to flash a custom kernel in a setup with working Magisk , superuser root, and passing SafetyNet ??

I'm currently running SIX ROM ( I believe a PN based ROM with a pretty much stock kernel). I would like to flash Blackbird kernel but when I do, I lose ability to pass SafetyNet.

For that matter, how do you dirty flash a ROM update with an existing Magisk install?
[Magisk] jackyaway:
There is a bug in magisk manager 2.5: default and dark theme have both the white background. To use dark background I have to install magisk manager 2.5 over 2.1.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Magisk] yochananmarqos:
Flash the kernel, then Magisk, then the phh superuser module. Both need to patch the kernel, so you'll have to flash both again. Same thing with a dirty flash except the ROM comes first.
[Magisk] photolarry:
I have not found that any kernel is working (I did not try total stock 91P from Nov build). I did wipe the device and installed a custom 7.1 rom without changing the kernel (since it has a sigma kernel as part of it). Flashed magisk 9 and phh magisk superuser 266-2 and enabled hide. But I fail safety net. Also added the xprop script which I believe still resets ro.boot.flash.locked to 1 (I checked in a terminal with getprop). So if that is not reason for failure, I am unsure if hide is functioning. I did try opening the HIDE tab and selecting Android Pay and Google Play Services and then rebooted. All that did is seem to lose the hide all together. Curious if [MENTION=4398101]topjonhuw[/MENTION] has any suggestions? Thanks.
[Magisk] chudy_85:
Magisk v9 and phh's root v2.66-2 work great on mate 7 with mm. I past safety net and can play Pogo
[Magisk] SimplyCity:
Well, great sugestion.

:)

To be honest, I did not find it erlier.

But looking into script, I have my doubts if it works with v9... Bc it does exactly as same thing as my method does (which is making folders inside system/priv-app PLUS moving already installed app from data/app...

My doubts are still with me thanks to entries which looks pretty same...

I have not tried App Systemizer, bc I just spend 20 hours fighting with my own method, got failure, as you know...

But I would like to try. Problem is that I just set up my system again, all aps, everything and have enough to fight with it for some time. Beside, if i get bootloop, I ussualy go to recovery, flash magisk-mounter and delete my mod folder from magisk. Problem is, that after that operation system goes unstable, google account is lost, sammy account loses its sesion cookie, few apps gets fc during startup... Once I got system ui fc and cant even get to my phone...

Just ask you kindly: has eny one tried to move any app with App Systemizer on Magisk v9? With success?

Another question is: why method that worked with v8 (which was very cool feature) now won't work? Something has changed and I would like to know how to make it work again, without semi-way, directly.

Thanks in advance.
[Magisk] smohanv:
I want to use SuperSU with magisk v9. The OP page of magisk page suggest as below. What does it mean saying flash SuperSU in systemless mode. If flashing any SuperSU BETA after 2.67, simple flashing should take care of systemless mode... i am confused..

If you choose to use SuperSU (only support Android 6.0+)

Download latest SuperSU

Flash SuperSU in "systemless mode" first

Then flash Magisk zip
[Magisk] Will_Xda:
Safetynet passed - Pogo and Android Pay confirmed working on Oneplus3 with Magisk hide enabled and phh's superuser. Nothing more nothing less :)
[Magisk] Tobi@s:
Have you hidden some apps explicitly in Magisk hide? As soon as I install v9 (with or without any modules(phh su)) Safetynet fails.. Even with Magisk hide enabled.

If I uninstall Magisk through the uninstaller, Safetynet check passes again
[Magisk] Will_Xda:
Only apps Magisk hidden are AP, Pogo, and play services and Safetynet passes fine. The kernel I am using has sultanxda's patch built in (not sure if relevant anymore)
[Magisk] android_htc:
Sorry, had no access to a computer to get a logcat. But, Safteynet now passes after using a different kernel for my galaxy note 4 :)
[Magisk] Hammerhead2502:
Anybody got it to pass Safetynet on Android 7.1?
[Magisk] olivercervera:
I had Magisk v8 installed, but did a clean install.

Magisk v9 + Magiskhide (using phh superuser) is working fine, but sometimes Magisk Manager (2.5) shows No Root access: functionality limited, and suddenly root access gets actually disabled, and no app can use root. I am using phh r266-2.

A reboot seems to fix the issue (temporarily). Using Android 7.1 on Nexus 5 (Nitrogen ROM, kernel from the rom)

Has anybody else seen root instability like this?

EDIT: I have found other people who have this issue, but is the developer aware? I couldn't find any answer.
[Magisk] Shemploo:
yea, i'm having same issues.

http://xdaforums.com/showpost.php?p=69638212&postcount=724
[Magisk] Captain_Throwback:
I've mentioned this too, but yes, [MENTION=4470081]topjohnwu[/MENTION] is aware of the "losing root" issue randomly after some time. Rebooting fixes it (until it happens again). Trust me, I've made sure he knows about this issue, but he currently doesn't have a way to fix it. The investigation is ongoing.

P.S. The issue is Magisk Hide (in case there was any doubt).