yashsingh1/xdaforums huggingface dataset:
[Magisk] timmylog:
When i boot to recovery mode magisk says that its installed cause ive patched and flashed the recovery image and everything works fine there but the problem is that i dont use wifi but mobile data and in recovery magisk mode, theres no network access. So the recovery aspect is kinda obsolete for me cause i need to call, browse and do other stuffs with my phone rooted at that moment. Thats why i stated earlier on that the magisk developer added support for my type of devices in normal mode, instead of recovery. From the canary builds of v.18.2 normal mode of rooting works but it still doesnt root my phone in normal mode after flashing the zip file or patching and flashing boot img

---------- Post added at 07:16 PM ---------- Previous post was at 07:01 PM ----------

Actually, my phone REQUIRED patching to recovery. Theres nothing new about that, when i boot to recovery mode magisk says that its installed cause ive patched and flashed the recovery image and everything works fine there but the problem is that i dont use wifi but mobile data and in recovery magisk mode, theres no network access. So the recovery aspect is kinda obsolete for me cause i need to call, browse and do other stuffs with my phone rooted at that moment. Thats why i stated earlier on that the magisk developer added support for my type of devices in normal mode, instead of recovery. From the canary builds of v.18.2 , normal mode of rooting works but it still doesnt root my phone in normal mode after flashing the zip file or patching and flashing boot img. So theres definitely something wrong somewhere, or maybe i need to do sone rework to my boot img cause if they work for other a-only SAR devices, it should also work for mine too.

---------- Post added at 07:19 PM ---------- Previous post was at 07:16 PM ----------

Actually, my phone REQUIRED patching to recovery. Theres nothing new about that, when i boot to recovery mode magisk says that its installed cause ive patched and flashed the recovery image and everything works fine there but the problem is that i dont use wifi but mobile data and in recovery magisk mode, theres no network access. So the recovery aspect is kinda obsolete for me cause i need to call, browse and do other stuffs with my phone rooted at that moment. Thats why i stated earlier on that the magisk developer added support for my type of devices in normal mode, instead of recovery. From the canary builds of v.18.2 , normal mode of rooting works but it still doesnt root my phone in normal mode after flashing the zip file or patching and flashing boot img. So theres definitely something wrong somewhere, or maybe i need to do sone rework to my boot img cause if they work for other a-only SAR devices, it should also work for mine too.
[Magisk] zgfg:
So anyway, if it's a problem, to make it visible and to get it solved, you please need to report to TJW to GitHub:

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

We have to do that not only for us but also to help to others who may run to the same issue. The least we can do for community, compared to the efforts that developers put into the projects we all use ?
[Magisk] geminihc:
I'm on xiaomi.eu's miui 12 latest stable ROM and google pay works fine (and i have an unlocked bootloader).

If i flash magisk v20.4 , will my google pay stop working?
[Magisk] Philnicolls89:
Google pay workings fine for me on 20.4, Samsung Android 10 rom.

---------- Post added at 01:33 AM ---------- Previous post was at 01:17 AM ----------

That is very strange, it does sound like a problem with your device though.

My samsung s10+ is A only System As Root, and after patching my firmware and recovery img with magisk everything works fine.

I use button combo to boot to the recovery partition and there are no system issue such as mobile data not working.

I can also install a custom kernel which eliminates the need to boot to the recovery partition for root access.

I think as mention above, you may find more answers by opening a github issue or asking on one of your devices forum. Hopefully you can get it working as i agree that without mobile data etc the phone can not be used as a daily driver.
[Magisk] pndwal:
You may have noticed that latest Canary Manager shows not only SAR & A/B status, but presence of Ramdisk.

My device is SAR, Non A/B but has Ramdisk, and MagiskSU in boot.img works fine despite Official Installation Instruction indicating it shouldn't.

I guess SAR, Non A/B devices lacking Ramdisk specifically, are those that need patched recovery, and likely John assumed that they would all lack Ramdisk when this configuration first appeared.

Since SAR, Non A/B devices w/ Ramdisk started appearing, it seems John has simply deferred documentation updates for a while as new Stable Magisk has been the priority... Something had to give!

In any case, updated Official Installation Instruction that should clarify all this is imminent!... As is new Stable Magisk!... TONIGHT:

Many (Android 11 users etc) will no doubt want to migrate back to Stable... Don't all hit the GitHub server at once! PW
[Magisk] zgfg:
MIUI are SAR, non A/B, without Ramdisk but boot.img should be patched (and one can have both TWRP and Magisk)

Btw, 30x Canary Manager also shows a new Crypto info (File for me)

Thanks for the info - no new Stable yet.

But anyway, Canary would be also updated and leveled-up with the new Stable (maybe some hours later, as usual), hence no need for the massive escape to Stable
[Magisk] pndwal:
Mine is China MIUI MiPad 4 now w/ LOS 17.1, Android 10. Magisk Manager shows SAR Yes, A/B No, Ramdisk Yes, Crypto N/A

I do have later unmodded Redmi 8T w/ Global MIUI. Will unlock and root soon. Magisk Manager shows SAR Yes, A/B No, Ramdisk No, Crypto File (based).

Good to know I may not need to use SU in recovery for that. :good:

For me too. Didn't mention that as probably wasn't relavent.

On its way as we speak

That's as maybe, but some who needed Canary only for Android 11 compatibility will no doubt want to get off the bleeding edge, and avoid frequent updates / instabilities / challenges... Others here will relish the fight! (I doubt even Stable will be bug free, at least initially.) PW
[Magisk] pndwal:
Well, ITS HERE!

I've got MagiskSU 21.0 (21000) w/ Manager 8.0.0 (302) Running, and it looks like Canary... wings n all!

Sorry if I raised false hopes... may not (quite) be Stable yet:

Either change channel in Manager or download from GitHub. Stable manager link and Beta MagiskSU link and the documentation is now updated.

Happy reading -

- See link for release notes above. (Changelog is BIG this time, so I won't quote it, but included here. Take a look.)

- Magisk Homepage w/ updated documentation:

https://github.com/topjohnwu/Magisk

Great stuff John Wu! Many thanks, n hope you can get some sleep now... After the party. :D :good: PW
[Magisk] zgfg:
Beta 302/21000 available and Canary 303/21001

Stable followers will have to wait a little bit more?

Updated my Canary, got warning that I may need to disable Play Protect (last couple of times I updated without disabling and there was no problem, so probably still not needed)

Updated without restoring my hidden/repackaged Manager, no problem again

So far, so good, excellent?
[Magisk] timmylog:
Well, ive done exactly as you said but this is what happened after I stated my issue @ https://github.com/topjohnwu/Magisk/issues/3226

It got closed and i got the opposite of a like reaction. I don't know maybe it was something i said that TJW didn't like or maybe i didn't give enough info, but please if you see any part where i did wrong, please let me know
[Magisk] blinoff82:
Phone: OnePlus 6

Syberia OS on Android 11

The previously installed "Magisk modded" was removed, a new magisk 21 was flashed via TWRP. The result is a reboot into fastboot mode.
[Magisk] wallace108:
Phone: Oukitel WP5-PRO

Android 10

A/B = No

SAR = Yes

Ramdisk = Yes

I tried them both, Beta 302/21000 and Canary 303/21001. I flashed them with fastboot. No joy. Still Magisk Manager says N/A.
[Magisk] pndwal:
Well Manager 8.0.0 (302) is now latest Stable!

And Beta GitHub link now lists MagiskSU 21.0 (21000) in addition to Manager channel.

Today is the biggest day for Magisk since March 23!

John's just cleaned his whole GitHub, updated all documentation, seems to have moved old Canary builds (only new one shows presently), and upload new Stable and Canary Magisk Manager, Beta and Canary MagiskSU, and seems to be starting fresh with these!

Here's the listed Canary changes:

Magisk (21001)

-Fix Pixel C image padding

Magisk Manager (303)

-Sync with public beta

Re image padding:

Commits on Sep 29, 2020

-Skip image padding on Pixel C

So I doubt 'insufficient space' issue is fixed for other devices yet.

Re new documentation:

https://mobile.twitter.com/topjohnwu/status/1312345063033192449

Issues:

Don't think John's sleeping yet! PW
[Magisk] zgfg:
Sorry but I must admit that after all I don't (completely) understand your case. Let me summarize - please confirn with Yes or No and comment inline if needed

1) For your device, there is both boot.img and recovery.img?

2) You tried with various versions of Magisk, but you can never patch&flash Magisk to Boot partition?

If so, please upload a screenshot from Magisk Manager when you are trying to patch, also save (floppy disk icon top/right at least in Magisk Canary) and post the log.

If you are patching boot.img:

- Recovery mode option must be Off

- You must flash the patched image to Boot

3) You can patch&flash recovery.img?

With Magisk v18.2 it works fine for you but with newer Magisk versions you get wireless not working (abžnd/or mobile, please describe the issues)?

In that case you would have root, and you should be able to collect logcat when you are trying to e.g. attach to wireless or so.

Btw, make sure when testing with these new Magisk versions (where you have root but issues) to disable all Magisk modules (modules that worked for 18.2 may no more work fine with newer Magisk, but that is not a Magisk issue, modules should have been updated)

And generally, if Magisk reports an error while patching boot.img, its likely not Magisk fault but something specific to your phone - IMO, you can't open the issue for Magisk based on that.

There are also other devices with no Ramdisk in Boot, hence Magisk can't patch to Boot but must patch to Recovery - as a result those users have to live with that that booting to Magisk require the usage of key combination as for booting to Recovery

However, it's strange that with Magisk v18.2 it works fine, but that you have issues with WiFi (with newer Magisk versions or also old Magisk versions?) - for that you can open the issue in GitHub but only if you clearly describe that TJW could understand and by submitting logs, screenshots, as much material as you can, to help him to analyze

Ticket must also contain as much as possible other info, particularly Android version, maybe kernel version, etc

Ticket for some totally rare device, with no details about the firmware, no logs and no screenshots, not clear what was really claimed - he is somewhat tough but consider how many similar tickets he obtains, he has no device to try to reproduce and better understand what user wanted to say, he has no time to go in discussion with each user...
[Magisk] Iustin_Theft-07:
App icon doesn't look normal after hiding latest stable manager (8.0.0) on Android 9 and 10. It is an android logo on a green background. Is this normal ?
[Magisk] lividhen99:
I think it is. There an option to add a "prettier" shortcut to your home screen if you want it.
[Magisk] Iustin_Theft-07:
Omg it's so ugly I hope he can fix it soon
[Magisk] 73sydney:
Devils avocado, but i have to ask, because ive never hidden magisk manager ever

But why are you hiding magisk manager?

Do people think thats something you have to do?
[Magisk] MattP410:
How do I get to downloads and/or modules with this latest version?
[Magisk] Iustin_Theft-07:
my banking app scans my apps on android 9 and if it sees "Magisk Manager" it locks me out of my acc. Cant pay cant see my currency or do anything. safetynet still works for my phone. so i have to hide it(
[Magisk] chooks06:
There's the icon at the right hand of the bottom "menu" bar.
[Magisk] MattP410:
Thank you. I didn't even see that. I feel pretty stupid now.
[Magisk] chooks06:
You're welcome mate. It was a totally new manager UI to me.. So I just started poking around to see what's what..I couldn't recognise the icons initially..lol
[Magisk] Alxoom33:
Thank you! Seamelessly installed new Magisk Manager (303) and new Magisk 21001.zip using Direct Install method through MM on both my Pixel 2 XL running Android 11 and my Pixel C running Android 10 LOS 17.1.

Install and reboot were flawless and without incedent.

Thak you again [MENTION=4470081]topjohnwu[/MENTION] !
[Magisk] lividhen99:
I dont think there will be a "fix" because it is intentional. You could build from source and add your own icon though... Not sure the best way to go about that...
[Magisk] smartfaune:
Hi,

the display is different in the French version (Magis-k, Manag-er)

Probably comes from the length of the word "Installer" instead of "Install".

Pixel 3a/Android 9

Magisk 8.0.0
[Magisk] g000n:
How do I downgrade to the previous version of Magisk Manager, version 8.0.0 says that it doesn't support the older version of magisk I have and it's acting like it's not installed at all

I used an older version of magisk because newer version doesn't work properly on my phone (Galaxy Note 5)
[Magisk] Spartacus500:
What android version do you have on Note 5 ?

Delete new version magisk manager & try install Magisk manager 7.5.1
[Magisk] g000n:
Android 7
[Magisk] lividhen99:
Downgrade magisk manager. The previous releases should be on the github.
[Magisk] Kello12012:
Latest UI is op.
[Magisk] wilsonhlacerda:
Android 9 (LOS16)

Samsung S4 Active I9295

Encrypted

Was running Canary (one version before last one)

Magisk Manager was hidden

I switched to Stable channel and updated Magisk Manager without problems. All as expected. New manager got hidden automatically.

Then already on new manager switched to Beta channel and updated Magisk itself directly (as recommended) without problems. Rebooted and Magisk is working fine. Everything as expected.

Thanks TJW and all people that help us to have such a nice tool, guides, tips and support!
[Magisk] g000n:
This worked, thanks.
[Magisk] jakelewis:
OTA - Install to Active Slot option not shown

Pixel 4a Android 10 Magisk v20.4(20400), manager 8.00(302)(11).

I'm trying to install Android 11 via OTA while retaining root via method outlined https://xdaforums.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773

The OTA downloaded fine, and I didn't reboot, but when I went to 'install' via Magisk the Install to Active Slot option was not presented:

[IMG="Magisk Screengrab showing no Install to Active Slot option"]https://horologyobsession.com/tmp/Screenshot_20201003-150209.png[/IMG]

just:

Method

Download Zip Only

Select and Patch a File

Direct Install (Recommended)

and then a lengthy description about 2020.1.23 Magisk v20.4 as though it is this that I'm trying to install. This seems reasonable as I uninstalled magisk as per the instructions above.

Does Magisk not recogonize that an OTA has been downloaded and ready for installation?

I'm unsure how to proceed from here?
[Magisk] HippoMan:
Is that guacamole made with extra jalapeños?

I'm sorry. I know it's OT, but I couldn't resist.

.​
[Magisk] Syoenth:
I have a issue with my banking app, on Magisk Canary and this new beta one my banking app detect root, I cloned my app using Island and still it detect my device is rooted, I had to revert to Magisk 20.4 to get my banking app working again
[Magisk] dcarvil:
I believe the "Install to Inactive Slot" option has been removed from the new version of Magisk as it no longer appears in the updated Magisk documentation. You'll have to use the "Select and Patch a File" option to patch boot.img, then flash it with "fastboot flash boot magisk_patched.img".

However, you may encounter a problem doing this because you are still on Magisk version 20.4. I know the procedure works with Magisk 21. You can get 21 from the beta channel.
[Magisk] pawelmiernik:
New manager ui flashing animation obstructs module installation instructions for modules that use volume buttons for selection. This makes it difficult to see the choices especially the first ones that appear, because the log screen isn't filled enough to allow scrolling. Please move the animation back up above the installation log as it was in previous version, thank you.
[Magisk] Mysticblaze347:
New version look absolutely amazing, but few issues. I can't use magisk hide, it crashes apk. Also before in magisk hide I wasn't able to find Chrome in apk list to hide magisk from. Idk if can be fixed but would be cool if able.
[Magisk] zgfg:
That shortcut (with standard Magisk icon) cannot substitute the ugly icon

Real (ugly icon for the repackaged Manager) provides long tap functionality: you can directly access (without opening Manager) Modules, Magisk Hide and SuperUser

By long tapping the shortcut, you only get Remove option

And that ugly icon appeared with Canary Manager 299 or so. With Canary 294 or so, repackaged Manager still had the standard Magisk icon - hence I don't believe bit could be 'intentional'

---

Generally - some people are now surprised with the new UI redesign they see in Beta.

Howevet, this UI is present since early this year in all Magisk Canary versions, and it has benn polished over time.

What you see today as 'new' in Beta, that UI was more or less the same (only very minor UI changes) since the summer in Canary
[Magisk] kamikaze702k:
Sorry but version 7.5.1 is a much better ui than the latest, I don't know why the change is needed to spoil the ui and functionality. Almost more than always it's always a unnecessary update that kills a app......
[Magisk] jakelewis:
Thank you for your reply, but I'm a bit confused. The OTA is currently residing in the inactive slot, but the procedure you described here will effect the currently active slot will it not?

Maybe it would be easier to rollback my Magisk+Manager to a version that still supported "Install to Inactive Slot" as that seemed to take care of all this automatically.

What would you suggest ?

Jake
[Magisk] J.Michael:
Figure out which slot you are trying to modify. Use command to specify slot to be modified.

I've never done it. Google found someone saying

fastboot getvar all

find line "(bootloader) current-slot:b"

fastboot --set-active=a

or the other way around. (Assuming you're trying to modify the one that is *not* current.)
[Magisk] Vinayakn73:
Yeh I find it so unnecessary. They have made easy nice UI very complicated and less user friendly. Literally it took me whole 15 minutes to find where magisk hide for apps is.
[Magisk] 73sydney:
hehe i'll allow it :)

---------- Post added at 06:22 AM ---------- Previous post was at 06:18 AM ----------

Cheers for the clarification

I was half worried people were just doing it because they thought they "had to"

---------- Post added at 06:26 AM ---------- Previous post was at 06:22 AM ----------

Many of us have been using the newer gui for a while on canary builds

At first it was a bit challenged and plenty of us removed it, but then TJW took over design of it and its much better than the first iteration of the new gui, trust me

After TJW fixed it, i went back and have been using it for a while now

You get used to it pretty quickly
[Magisk] Roll3r:
From the FAQ (https://topjohnwu.github.io/Magisk/faq.html)

"Q: After I hidden Magisk Manager, the app icon is broken.

On devices running Android 9.0+, Magisk Manager will use a more advanced hiding method. It will install a “stub” APK that has nothing in it. The only functionality the stub app has is downloading the full Magisk Manager APK into its internal storage and dynamically load it. Due to the fact that the APK is literally empty, it does not contain the image resource for the app icon.

When you open the hidden Magisk Manager, it will offer you the option to create a shortcut in the homescreen (which has both the correct app name and icon) for your convenience. You can also manually ask the app to create the icon in Magisk Manager settings."
[Magisk] 73sydney:
The outrage will wane, take a breath :)
[Magisk] zgfg:
Then please a simple question, how/where to "ask the app to create the icon in Magisk Manager settings"?

Have you tried, where is that setting?

Screenshot from the repackaged Manager attached, there is only a setting to add shortcut but that is not the same as the proper icon for the app:
[Magisk] CatThief:
I just used the newly-redesigned Magisk Manager 8.0.0 to root my Pixel 4a with Magisk 21.0 and didn't have any trouble at all finding settings, etc, and I actually like the new UI. John did a darn good job, and I sure am happy to have my firewall and AdAway running again. Thank you John!
[Magisk] Didgeridoohan:
[MENTION=7786725]zgfg[/MENTION] That the repackaged Manager uses the default ("ugly") Android icon is by design (but I'm sure you've read the FAQ already).

If the created shortcut isn't enough for you, there are plenty of launchers that allow you to assign an icon of your choice to the app.
[Magisk] pndwal:
Great, cos he beat me to the punch...

Feature needed as bank etc app Devs don't trust SafetyNet (for obvious reasons) and employ their own means to detect root / modified environment including detection of root apps, TWRP folders etc, etc. Guess they would tell you you're rooted with nothing more than Manager installed unless hidden.

+1. I liked UI for its extra features (device configuration details, etc) after I got used to it some time ago.

Nb. Some features that might seem to be missing are actually now on an as-needed-for-device basis. With better 'smarts' they won't show unless supported / needed.

An observation: I Just moved back to Canary after trying new Stable Manager and Beta MagiskSU. I initially had Manager 8.0.0 (301) Beta, then updated to 8.0.0 (302) Stable. I noticed that while otherwise looking identical w/ same basic version number 8.0.0, the Beta (301) showed 4 update channels, Stable, Beta, Canary and Custom, but after updating to Stable (302), settings only shows 3 channels, Stable, Beta and Custom. Since I'd updated I had to download Canary from GitHub. In Canary, 4 channels show again.

This change necessitating migrating to Canary via GitHub download may be intentional. PW
[Magisk] Iustin_Theft-07:
Trying to update from Magisk stable 20.3 to Magisk stable 20.4 inside the stable manager 8.0.0 results in an installation failed error. Flashing the 20.4 zip manually from twrp renders my device unusable after 20 or so seconds. (It looks like it's crashing systemui).

Android 5.1.1 TouchWiz, arm7. Do I need to log anything else apart from the install log below ?

View attachment 5109465
[Magisk] zgfg:
Of course I have read the FAQ - please did you read my post where I cited the FAQ , posted the screenshot from the Manager settings and simply asked where is that setting mentioned in the FAQ to create the icon (shortcut is not the same)

https://xdaforums.com/showpost.php?p=83635161&postcount=41789

Btw, all who just point to FAQ and ask/comment like, have you read etc, did you try yourself first to be sure about?

Edit: Screenshot from the FAQ attached