yashsingh1/xdaforums huggingface dataset:
[Magisk] Roll3r:
Man this is from the FAQ. I didn't write the SW (obviously), I'm just pointing out where the, contrary to your opinion, "ugly icon" was in fact intentional

But, I'll hold your hand because I'm super bored because we're all stuck at home on account of forest fires shooting up the AQI and covid and we can only watch CNN to check if the president's dead or not

This is from memory, but it should be close enough

In Magisk, go to "settings". , do you see "hide Magisk Manager" or similar? Tap it

It'll ask you for a name for the hidden app. Enter whatever you want

From the app drawer, click on the "ugly icon" named whatever you chose

It's gonna tell you it needs to "download the full version" or something. Do that

Open the "ugly icon" again

It's going to ask you "Do you want a pretty icon"? Say yes if you want

Is it super straight forward? Nope! But I wouldn't say it's "hard"
[Magisk] Philnicolls89:
The problem for me is that the 'pretty icon' app (that has been repacked and renamed) and the normal app both have the ugly android stub icon.
[Magisk] nri_tech1183:
New magisk has crap ui and drains battery.
[Magisk] 73sydney:
Theres nothing like constructive feedback

Please provide proof that it "drains battery"
[Magisk] Didgeridoohan:
The setting mentioned is for the shortcut. That's all you get... If you're unhappy with how it's phrased in the FAQ you can submit a PR with suggested changes.

If you want full obfuscation of the Manager you'll have to live with the "ugly" icon. As I've already mentioned it's quite easy to make it pretty again...
[Magisk] Didgeridoohan:
It is intentional. Since Canary can be unstable it shouldn't be too easy to switch to it.
[Magisk] zgfg:
Man, I have gone through the hiding and unhiding Magisk Manager ten times the last days, I'm not guessing "something" like this or that, etc

And I'm also bored of repeating what is the difference between that "shortcut" and the "icon" in this case (I have them one by another on my Home screen)

Thank you for such help - I also know to read FAQ but before I started to write a word about here I carefully tested mysellf (!) and then just pointed to the observed issue and to the discrepancy between the way how it works compared to how it was described.

In addition to previous screenshots, now also a link to screenrocording, showing the whole process of Hiding Magisk Manager:

https://mega.nz/file/V0sVkCxY#RDOpE0sLAx9Z1zNUjHcFm2wHGOWPOAMBq-4Us9ZSjCM

- Observe that I had Magisk Chanary channel, and already Magisk Manager 303

- Upon hiding the Magisk Manager, it dropped to 302, asking me to update again to 303 (no big deal but strange)

- There is no setting to change the icon but only to install the Shortcut

- Shortcut installed (already while hiding, when it popped-up and asked for), but then observe a difference with the long tap functionality between the icon ('ugly' or maybe very nice to somebody, on the left) and shortcut (standard Magisk icon look, on the right)

Take care and let's consider this 'closed', this discussion made no progress
[Magisk] andrea0807:
I updated my poco F2 Pro to Android 11 today but magisk canary does not pass safetynet check.

I have the ROM xiaomi.eu weekly

How can I solve?

Spoiler content hidden.

Inviato dal mio Redmi K30 Pro utilizzando Tapatalk
[Magisk] XtraWater:
The new UI is beautiful.
[Magisk] pndwal:
Some context regarding Magisk Manager:

"Diareuse is officially the main maintainer of Magisk Manager"!

https://medium.com/@topjohnwu/state-of-magisk-2020-21de32721d65

This is a great read from a talented, modest developer, and a basic history of MagiskSU evolution from Systemless Xposed AND Magisk SU in 2016, to 2020 Magisk building.

So many thanks to John for arranging all this. :good:

... AND many thanks to Viktor De Pasquale, [MENTION=9815783]diareuse[/MENTION], for his sterling (re)development of Magisk Manager! :good: :good: :good:

Kotlin code, edge2edge display support etc etc may mean more to others, but I'm liking it and appreciate that difficult decisions had to be made to boot!

So credit where credit is due! (And we shouldn't forget the huge contribution from Jorrit Jongma / [MENTION=631273]Chainfire[/MENTION], who continues to support John's MagiskSU, as well as those of Devs like [MENTION=5345056]DVDandroid[/MENTION] and [MENTION=3400685]digitalhigh[/MENTION], who John also acknowledges here. :good: :good: )

... I'm certainly glad the two of you "continue to enjoy the fun of hacking things around while it lasts"... Cos I do too! PW
[Magisk] dcarvil:
I did a reboot after the OTA, which makes the OTA update the current slot. This causes the loss of Magisk, which was not a big deal for me. Then I patched boot.img using Magisk 21, and flashed it to the boot partition. Reboot again, and back in business. There are probably other ways to do it, but this is what worked for me.
[Magisk] pndwal:
A heads-up:

PW
[Magisk] Spartacus500:
The new version of magisk manager 8.0.0 is amazing ? beautiful UI appearance, and most importantly, it hides the root beautifully for the app :highfive:
[Magisk] andrea0807:
Up!

Inviato dal mio Redmi K30 Pro utilizzando Tapatalk
[Magisk] justDave:
As I understand it, is still fine to use the OTA option on Pixel devices as long as you're still on Android 10 or earlier. I've been using this command to reenable that option so I can keep Magisk after a Lineage OTA (still on 17.1):

resetprop ro.product.brand goggle
​

It works for me. I can't say for sure if it'll work for you. If you get stuck in a boot loop after doing it, you have only yourself to blame.
[Magisk] Wolfcity:
Thanks a lot for these information, especially the content of this link:

https://medium.com/topjohnwu/state-of-magisk-2020-21de32721d65

These things should have been read by all the users of magisk and magisk manager, just to let them know how far this project has come over the years.

For many users magisk has become kind of normal but don't forget the amount of work that has been done to make magisk the one and only root solution nowadays.

Thanks a lot [MENTION=4470081]topjohnwu[/MENTION] and [MENTION=9815783]diareuse[/MENTION]!
[Magisk] J.Michael:
How long is your phone?
[Magisk] zgfg:
Article is excellent, just the @ simbol made a bad things to the URL?

Use:

https://medium.com/topjohnwu/state-of-magisk-2020-21de32721d65
[Magisk] zgfg:
It's a scrollshot
[Magisk] Wolfcity:
Thanks for the hint, edited my post (as the link is very important).
[Magisk] oo0:
How to fix missing bottom config buttons in latest update? Magisk works fine
[Magisk] DarkSJ1998:
That's not feasible on many devices as the device won't boot up (on Stock ROMs) when the BL is unlocked & Magisk isn't there.

Magisk makes the OS to not detect unlocked BLs & allows it to boot up.
[Magisk] pndwal:
Install Magisk! :D PW
[Magisk] oo0:
So it just doesn't install itself after successful recommended direct install and reboot on two test devices
[Magisk] pndwal:
Well, your Manager screen says it's not installed!

You haven't given any other information though...

Are these perhaps Mediatek devices?:https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83637693

Remember, Magisk 21.0 is still in Beta, even if your Manager is sourced from Stable channel, and your update channel is set to Beta.

2 options for you:

Change to Canary Manager (303) and try Canary Magisk (21001) to see if this is fixes it for you.

If you're on Android 10 or lower, just change channel to Stable, and try with v20.4 (20400)

Without details there are so many other possibilities! :) PW
[Magisk] chooks06:
I'm using a MTK device. UMIDIGI A5 Pro on Google Experience ROM (Hadenix), Android v10.

Magisk will not install via the Manager even though in recovery it says success. Same result after 3 attempts.

Decided on the usual manual method - uninstalled the Manager, uninstalled v20.4 using the uninstaller in TWRP. Then flashed v21.0 via TWRP.

Up and running after that.

Just sharing.
[Magisk] lividhen99:
Really? I've never heard of that before ?. Can someone confirm this? I feel like it's usually the other way around, but with locked bootloaders: boot checks for modded partitions. If modded, No boot!
[Magisk] pndwal:
Great! Just curious, do you now have v21000, or v21001?

Also, I see that device shipped w/ Android 9, so TWRP should still be compatible. (It isn't w/ devices shipping w/ Android 10 and up.) PW
[Magisk] ibrokemypie:
anyone know what's going on with the magisk modules repo? numerous modules have been made but are just being ignored, no input at all
[Magisk] mrceli:
Really need magisk to get root without being seen by sf^ckty net or rip her! Magisk alone is more than enough. :) it seems sf^ckty net really hates xposed.
[Magisk] heslo.rb26:
Great stuff mate! I know we all appreciate the effort you put in for this, amazing work!
[Magisk] ryex:
Is there some special way to make magisk 7 work with suhide and supersu2.78r-1?

Because re-going through the old install replacing magsik 6 with 7 and xposed systemless 86.6 seems to yeild no root ability.
[Magisk] Artim_96:
There is a Magisk module called suhide helper
[Magisk] Rhoban:
Not at the moment. He said in his statement that SafetyNet now looks for Xposed.

No Xposed No problem.
[Magisk] ryex:
So the new correct installation order is just to flash Super Su, then magisk 7?

Then use the magisk suhide helper module, correct?
[Magisk] Artim_96:
Don't know. I first flashed it the normal way (with phh's SuperUser), then I saw that module do I removed SuperUser from the Magisk manager, flashed SuperSU and suhide after I installed the suhide helper
[Magisk] Hostage XII:
Is there a mirror for v6?

Thanks.
[Magisk] wolfrules:
In magisk v6 was possible to set dm-verity and encryption,if it's possible to do so in v7,how?

That part of the tutorial disappeared with the new relase.

Thanks in advance
[Magisk] Droidphilev:
strange, i don't have a "suhide helper" in Magisk manager downloads
[Magisk] soder:
Please look at my screen below. Is that right if using SuperSU that Magisk then "imported"? Thinking of that the icon is blue, and there's two paths...

Also, my history of root and Magisk is like this.

1. Only SuperSU with Xposed for many year.

2. Tried early version of suhide (didn't work for me).

3. Found Magisk v6. Switched to phh's root. Used it with some mods.

4. Magisk v7 came. Updated manager, and Magisk inside that, also phh's root.

5. Uninstalled Magisk and then also the phh's root.

6. Rooted with SuperSU in TWRP, booted, flashed Magisk and Xposed, and suhide, and got everything working until latest version of SafetyNet (actually, I don't use AP or POGO (I'm an adult ;) )).

Now to my question. Would it be better for me to stay on phh's root, if there's where the upcoming changes to get complete hidden root (along with Xposed) to pass SafetyNet are?

Next question for me. I read that some of you say "restore boot.img". How do I do that? When I flash my COS13.1.2.zip from recovery, that at least restore my /system and keeps my /data, will that also keep my boot.img? How do I restore that, if I REALLY want to start with this from scratch?

Thanks for a "magisk" (magic in swedish) work!

/Söder
[Magisk] Rhoban:
There's no reason to pass SafetyNet if you are not using Android Pay or Pokémon GO. Those are the only 2 (that I know of) that use SafetyNet.

Anyway, SafetyNet has been updated again and can now detect Xposed.

You may be able to pass it with phh root and his own hidesu method, but it won't pass if you also have Xposed.
[Magisk] mat1jaca:
i had no problems with magisk v6. when i reverted everything back to stock and then tried installing magisk v7, my touchscreen started freezing up in the system. it works for 15 seconds and then freezes for 2 secs and continues working. only the touch input freezes, as i still get notifications about incoming messages etc while the input is frozen. after that i uninstalled magisk manager, wiped system, dalvik and cache; and then flashed back to stock, but the issue is still occuring. i had no problems prior to flashing magisk v7. whats happening? i have a SM-J320F
[Magisk] soder:
Well, yeah, Xposed are more important for me then AP (at least for now) and POGO. But I read that hidesu might be getting an update with Magisk future versions or something. Was just wondering if phh's root is a better was to stay on together with Magisk? I used it with v6 but switch back now with v7 (felt better with SuperSU) but... if the future is in phh's root then I might stick with that.

/Söder
[Magisk] ameel:
Does magisk pass safetynet?
[Magisk] steviemch:
Unfortunately, not anymore. At least until the next magisk update by the sound of it.

Nexus 6P
[Magisk] WeirdSoup:
I compared v7 to v6 so far, with Xposed installed. v7 can bypass the SafetyNet, but it can't bypass many other apps that can detect root & xposed. v6 cannot bypass the SafetyNet, but it can bypass many other apps, using the toggle function. If the toggle is turned off, most apps cannot detect root AND xposed.(Yes, there are a few exceptions, some banking apps still detect the xposed with v6. But still most apps cannot detect xposed if the toggle is turned off.) I personally started to use the Magisk for bypassing the xposed detection, so I think v6 is better fit for person like me. But if you need to bypass the SafetyNet, it'll be better to use v7.

Edit: I didn't know the safetynet has updated and v7 cannot bypass it anymore. Sorry.
[Magisk] Cristan:
How I can unmounted root now with Magisk Manager 2.0?
[Magisk] WeirdSoup:
BTW, v7 + SuperSU + suhide doesn't help me to bypass Xposed detection. It cannot hide the xposed, contrary to v6's toggle function. Moreover, most banking and game apps still can detect the SuperSU. The suhide can't hide SuperSU correctly from those apps.

---------- Post added at 10:33 AM ---------- Previous post was at 10:32 AM ----------

You can't. You should use the 1.2 to use that function.
[Magisk] chooks06:
Yes, it was shipped with Android 9. It's a MTK 6763v/v. I used the unofficial TWRP by Hadenix.

I'm currently on Magisk v21000.

I have set update channel to "Beta".

Thanks for the tip about MTK incompatibility with TWRP) Magisk.

Cheers!

Chooks
[Magisk] pndwal:
Well, that's TWRP incompatibility w/ devices shipped w/ Android 10 (upgraded to 10 are ok), and all devices on 11 it seems...

...And Magisk Beta version problem w/ MTK.

Magisk issue may be fixed in 21001, or in later Canary builds as John is aware of it, but happily you have found a way to make the buggy beta stick. :)

MTK problem may be confined to direct update, I don't know, but I guess any other issues will come out in the wash as MediaTek users report. PW
[Magisk] Didgeridoohan:
[MENTION=4228219]Frost90[/MENTION] Funny you posting this almost at the same time as this was posted on GitHub: https://github.com/topjohnwu/Magisk/issues/985#issuecomment-703535974

I also tested the app and can open it without problem using Magisk build 21001 and repackaged Manager 303(11). But if it is detecting root after that I can't test...

If you can't get it working, it might be something about your ROM (I'm just guessing, of course).
[Magisk] xunholyx:
No, you are correct. Having an unlocked bootloader without root won't cause your device not to boot up.

---------- Post added at 04:47 AM ---------- Previous post was at 04:44 AM ----------

I'm not sure where you got this information from, but it is 100% false. Unlocking your bootloader won't cause your phone to not boot if you don't have root.

If you have information that I'm not aware of, please list the "many devices" that this happens on.
[Magisk] DarkSJ1998:
I have a OnePlus 6T running OOS, and if I don't have Magisk installed, I cannot boot into the OS with an unlocked bootloader. I've tried it multiple times, it's due to "dm-verity" (I'm not a 100% sure).

I faced this exact thing on OnePlus 3/3T as well before...
[Magisk] Frost90:
[MENTION=4667597]Didgeridoohan[/MENTION] it's not me on GitHub, I see no use in double posting, most likely there are other users affected as well. It gives me a glimmer of hope that it works for you, but I'd like to avoid changing my ROM for now, and leave it as a last resort.
[Magisk] zgfg:
I have installed your app, started, got a screen telling ne something in Romanian, used Translator: This app cannot run on your config - unfortunately, app blocks taking the screenshots.

But it was my mistake, I forgot to check-box Magisk Hide for this banking app - see the screenshot

So did it, cleared Cache and Data for the app, restarted (probably not needed), then the app opens a different screen with the option to login - seems it is no more detecting root

Btw, I'm also passing SafetyNet and RootBeer (hance having Magisk Manager repackaged), with TWRP folder and root apps like AdAway, LogCat 4U, Termux, Root checker, Reboot, SesEdit, TeMeFl, Smart-Pack Kernel Manager, NetHunter App and Terminal, Viper4Android, Vanced Manager WiFi Pasdword Viewer, LiveBoot...
[Magisk] Homeboy76:
Something is definitely wrong with the installation: You are also missing the Uninstall button.

Try re-installing Magisk Manager, tap install and tap install.
[Magisk] pndwal:
Don't think he was suggesting it was you!

He pointed to a user of ING app who was able to BEAT detection using latest Magisk (21001/303, and coincidentally, in the last few hours), which suggests it may not be a problem with (latest) Canary Magisk. (Could be other settings or the ROM.) :good: PW
[Magisk] kamikaze702k:
Does the new ui sort by last update on modules? As there's no way to know what needs to be updated of that which is already installed
[Magisk] pndwal:
Correct, he didn't actually have Magisk installed... He assumed it was after direct install / reboot, but hadn't checked.

Proved to be known issue w/ MediaTek devices (at least with Beta Magisk build), and he's sorted it by uninstalling previous MagiskSU and flashing patched boot image from recovery. :) PW
[Magisk] Lughnasadh:
At the top of the modules page there will be a section called "Updates" that will let you know if any of your mods have an update. If that section is missing that means you don't have any updates pending.
[Magisk] bartleby999:
I'm screwed, right?

As far as I'm aware passing CTS isn't possible if you failed due to Hardware, correct?
[Magisk] dcarvil:
Install to Inactive Slot

For those looking for the "Install to Inactive Slot" option, see this GitHub ticket.

https://github.com/topjohnwu/Magisk/issues/3256
[Magisk] pndwal:
No... Not yet!:

https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83148385 :good:

Spoofing model using Basic Attestation works for now as it seems Google is using a server end list of devices to utilize Hardware TEE Attestation for verified boot.

Most here believe that this will be short lived, and is just a testing phase.

Hardware Attestation was actually switched on indiscriminately (for all devices with Hardware TEE) for a short period, and reports of false fails due to bad TEE implementation on some One Plus devices surfaced.

Google switched it off in short order, but switched it on again for certain devices only, seemingly to allow time for fixes to TEE etc to be made at least for some devices. Presumably, it will be on again for ALL devices with Hardware TEE at some point.

So enjoy spoofed Basic Attestation on Hardware TEE equipped devices while it lasts, but understand that no-one here knows how long that will be. PW
[Magisk] zgfg:
Install MHCP module, run props in terminal, take Force Basic option, follow its responses - many oosts here and in MHCP thread, just search if needed...
[Magisk] ausren07:
after updating magisk i cannot download modules and change package name of magisk.seems like storage permission is missing.
[Magisk] zgfg:
Settings/Apps, Magisk Manager - check and provide permissions if needed
[Magisk] sdeft:
I noticed that with new Magisk 21.0 phone is stuck at boot screen when I flash Magisk after fresh ROM install. If ROM boots for 1st time then I can go back to TWRP and flash Magisk and it will work. Is this normal ?

20.4 doesn't have this.

Above was tested with Android 10 roms (LOS, RR, etc.) on Xiaomi Redmi Note.
[Magisk] guhvanoh:
It does with 20.4 on Poco F1. That's why you're advised to boot the ROM after installing before flashing Magisk.
[Magisk] ausren07:
permission is grayed out so cannot check permission
[Magisk] rogers11:
So there is no way anymore to OTA a 11.0 Pixel without PC!?
[Magisk] zgfg:
Maybe somebody could help you if you provided any information about your phone, firmware, etc (you didn't give a word about but it's defintely not a common problem, actually nobody mentioned anything similar)
[Magisk] Incognito777:
Hey, guys, I am running lineage17.1 with micro g, can anyone of you guys help me pass cts, basic integrity test on third-party apps, I have passed these test on magisk manager, but when I try using a safety net app it fails, I have read about google's new hardware and bootloader checks, I just need to run Gpay and banking apps. Thanks in advance.
[Magisk] dcarvil:
You might be able to do it with a second Android device (tablet, or a second phone) instead of a pc. This article details one process - https://android.gadgethacks.com/how-to/use-adb-fastboot-commands-without-computer-0200838/

I believe the TWRP team is planning a TWRP version for Android 11, but I doubt it will be ready soon. I suspect [MENTION=4470081]topjohnwu[/MENTION] will find a way to bring the option back to Magisk before we have TWRP for Android 11. More info on that at https://twitter.com/topjohnwu/status/1303574238796808192
[Magisk] guest4711:
How to set if if Manager does not ask for it?

I'll try it from terminal (pm grant ...)

Last Manager which is able to hide itself on 3 devices (all are klte, arm32) was 765d5d97 | 283
[Magisk] guest4711:
Me and some others reported it 2 months ago, e.g. https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post83189355
[Magisk] Alxoom33:
Sure there is. You take a regular OTA on your phone with stock recovery. Reboot and you are updated with the lates Android 11 version. Now to root again you need your pc. :)
[Magisk] zgfg:
When I was repackaging (MIUI 12) it asked me to grant Installation over USB.

Try also with enabling Install over USB in Settings, Developer Options menu
[Magisk] bartleby999:
Thanks alot for the help guys. I did see MHCP earlier, but thought if you failed Hardware it wouldn't work so I didn't bother trying.

Safetynet all passed for now. So I appreciate it.
[Magisk] zgfg:
You need to report to GitHub, link is on the Magisk Manager front page.

Developers debug and fix the bugs from there, no more (since long ago) from XDA posts

E.g., I had a similar issue for Xiaomi, reported it and got it fixed ?

https://github.com/topjohnwu/Magisk/issues/3147
[Magisk] guest4711:
The only way to pack it was to install the old version as mentioned above (765d5d97 | 283) and then let it hide.

All phones in trouble are klte, one on Havoc 3.7 (Android 10), one on Havoc 3.5 (Android 10), one on Havoc 3.6 and one on Havoc 2.9 (Android 9).

It occurs even after wiping /system and /data and fresh installing the ROM and Magisk.

But all is ok when using older stable or canary builds (before 765d5d97 | 283).

BTW, I don't see any option to install over USB in developer options. Do you mean "ADB over network' or 'Verify apps over usb'?
[Magisk] zgfg:
Screenshot from my Xuaomi attached

Also, during repackaging, it popped me and asked again for the same, you can see in the first part of this screenrecording:

https://mega.nz/file/V0sVkCxY#RDOpE0sLAx9Z1zNUjHcFm2wHGOWPOAMBq-4Us9ZSjCM

But really don't know for your phone and custom ROMs

Edit: MM uses pm install command, and it needs that Install over USB permission (on some phones)
[Magisk] Frost90:
Thank you both for taking the time to test the app on your side. I will try with a different ROM.

Gotcha! Those said solutions didn't help unfortunately.
[Magisk] guest4711:
Thanks. If it does not start downloading, the permission of 'installing over usb' should not be the problem (and on my phones I don't see any settings like that). Probably it is the missing storage permission Magisk Manager does not ask for...