yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Simply check if your device is SAR or not, look to the Magisk Wiki

If system is read-only, forget about giving write permissions by TWRP or root explorer or whatever - only systemless overlay by Magisk will work

But all this is nothing new, it's out for maybe two years, nothing mistycal, long ago explained in the guides and elswhere
[Magisk] DiamondJohn:
When you are trying to "delete a system app", I am assuming you are simply talking about stopping it from running, and not necessarily physically removing the files?

I normally Hibernate, Freeze and then Hide the app. All three are standard android methods. If you wish for a point-and-shoot UI, you can try the app I built: TeMeFI

You can find the feature under:

► Application Info / Manage
► State
▪► Hibernate-Freeze-Hide *

It also has the ability to de-systemise the app using Magisk. Requires a reboot, and this feature can be found under:

► Magisk
► Modules
► TeMeFI Hide System Apps
››► Add or Remove - Hide System Aps using a TeMeFI Module *

But I personally prefer the first method.

Let me know how you go.
[Magisk] str8str:
Which version should I be using on Android 10, 10.5? For stable
[Magisk] Wolfcity:
If I understand you correctly you're asking for the Magisk version you should use. Answer is: Always the latest (which is stable 20.4). If you run into any problems you may give the latest Canary build a shot.
[Magisk] dipstik:
is the safe mode stuff commited in may in the 20.4 stable? or should i use the canary?
[Magisk] Missy_X:
Can't install magisk module

hi

I can't install a modul on magisk 20.4 when i click on module and try to clik on the yellow button nothing happens, i can't download my module.

can anybody help me ?
[Magisk] JudgeDread11:
You'll need to provide more information then that.

It's the module updated to the latest Magisk template?

That's often the rain why (older) modules won't install.
[Magisk] Missy_X:
when i try to click on the button to download the module it seems like it's locked. I clicked several times

it's a module which worked until today with magisk 20.4, i've changed my rom and the twrp today et i can't use the module anymore
[Magisk] str8str:
Thanks
[Magisk] Missy_X:
thanks for your reply, do you have a link for magisk canary?
[Magisk] zgfg:
Change Update channel in Magisk Manager settings to Custom with this URL:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json

Or install Canary Magisk Manager:

https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk

Then update to Magisk Canary
[Magisk] Missy_X:
thanks
[Magisk] Palidino:
Mi Mix unlocked bootloader with the latest Pixel Experience installed. Installing Magisk 20.4 seems to have sent startup into a boot loop.
[Magisk] mrmrkmail:
just flashed latest gsi 11 (beta 2) and had no luck to delete files for example in root directory with the latest canary
[Magisk] zgfg:
You should know if your system is read only, if read only you cannot delete, no way (only systemless overlay will work)
[Magisk] varadinum:
Hi, how can I completely remove magisk root and restore original stock firmware? There is always something left. Samsung keeps saying "the system has been changed unauthorizedly"

SAMSUNG Galaxy A9 2018

Thanks in advance
[Magisk] J.Michael:
Have you tried burning the stock firmware?

Check your device forum to see if it is ever possible, once that message has been triggered, to remove that message.
[Magisk] pndwal:
OT here, but:

https://support.samsungknox.com/hc/...-a-Knox-Warranty-Bit-and-how-is-it-triggered- PW
[Magisk] M45s3rD0g3:
Magisk 20.4 Custom ROM stopped booting

I have edited some values with Magisk and my custom ROM does not boot. Is there a way to reset Magisk values to default in TWRP? Would an uninstall do this? Can I use the terminal in TWRP to access props again?
[Magisk] Didgeridoohan:
Did you change some prop values with MagiskHide Props Config? If so:

https://github.com/Magisk-Modules-R...README.md#device-issues-because-of-the-module
[Magisk] M45s3rD0g3:
Thankyou so much! The "Disable all Modules" section worked like a charm!
[Magisk] tom1807:
Lenovo M8 HD, Impossible to obtain root - Change my mind ;)

I consider myself as pretty good in root my mobiles, but this Lenovo M8 drives me nuts

First the specs:

Lenovo M8 HD (WiFi only)

Model: TB-8505F

Hardware: MT8166B (according to Lenovo Mobile Assistant) (AIDA and CPU-X report MT8766)

Platform: MT6761

Android: 9, latest update dated March 16, 2020 (TB-8505F_S100133_200316_BMP)

TWRP: not available

Bootloader: unlocked

Steps I did:

First step: Search internet, most feedback I read was, its pretty easy, just unlock the bootloader, patch the boot.img with Magisk Manager, so I downloaded v20.4.

Patched the Boot.img. Copied magisk_patched.img from my tab to PC, boot to fastboot, installed the patched boot.img, rebooted, Magisk Manager was gone, installed it again and Magisk Manager tells me "Magisk not installed"

Second step: Read everything on the Installation page of Magisk and made the recommended tests

ADB Shell

getprop ro.build.ab_update

No result

getprop ro.build.system_root_image

Result: True. So my Tab is using System-as-root

Third step: Patch the recovery image in Magisk Manager

Reboot to fastboot, type the command "fastboot flash recovery magisk_patched.img", the patched recovery is sent to the Tab, try to reboot and the tab stays in a bootloop. So flashed the original recovery, Tab boots normal.

Fourth Step: Tried Amazing Temp Root for MediaTek ARMv8.

Also not successful, but not sure whether this has something to with the Program "init.d" which requires to buy the software or to load an ad. Didn't buy it and Ad didn't show up. After a reboot, still nothing.

Fifth Step: Read everything (again) on Magisk and MagiskHide Installation and Troubleshooting guide. But this didn't help me a lot.

At this stage, I have the feeling either that Lenovo patched the Mediatek-su with the march update (which would be pretty fast) or I missed a critical step.

There is no log file available, so its gonna be probably tough to push me into the right direction.

Oh btw. Lenovo Mobile Assistant reports root, but this is probably caused by the unlocked bootloader.

Magisk only offers me to download the zip (after that nothing happens) or patch an Image.

I hope I didn't forget anything.

Cheers

Tom
[Magisk] mrmrkmail:
thanks for your reply. i really appreciate it.

i just was wondering, because with the previous beta (gsi 11, beta 1.5) i had no such proplems.
[Magisk] AndDiSa:
[MENTION=628957]tom1807[/MENTION] you booted into 'recovery' or you did a normal boot? Because you patched the recovery, you need to boot into recovery to start up the rooted system. Probably the 'normal' boot with a patched recovery does not work as the recovery partition changed ... just a guess.
[Magisk] Alxoom33:
Magisk v. 20419 works fine for me on 11 beta 2. Version 418 worked on 11 beta 1.5. I'm on Taimen.

---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------

There is a lot of users that don't know what they are doing. It's Magisk, not Magic. You need to do it right![emoji1628]

Mod Edit: Removed multiple repeats likely Xda glitch
[Magisk] Fry-kun:
My pixel 4 xl tripped into ctsProfile: false yesterday. From a cursory read, sounds like that check is now done in hardware, and there are no workarounds. Is that mostly right?
[Magisk] Lughnasadh:
I see you are on the Pixel 2 XL. I'm passing on that as well as stated in my earlier post. It is the Pixel 4 XL that I wasn't passing on. You made it sound like you were passing on the Pixel 4 XL. I haven't seen anyone passing on that as of a few weeks ago.

Only need to quote me once. You're making my notifications go beserk, lol :p
[Magisk] Alxoom33:
Mod Edit: Removed repeated posts likely Xda glitch

Sorry, Tapatalk issue. Not posting. Needed to resend a few times.

Where in my post did I make it sound like I had a Pixel 4? Problem is people don't read!
[Magisk] Lughnasadh:
[MENTION=4100646]Alxoom33[/MENTION]

My bad. Got you mixed up with someone else because you replied to a reply I was making to someone else. No need to be snotty about though. Honest mistake. And please, stop replying to me. You're still making my notifications go beserk.
[Magisk] Tianhe:
From of the look of it, yes. You can always check in logcat or Magisk Canary build to be sure but there is no workaround (atleast for now!)
[Magisk] zgfg:
Repeating is good for learning but you really didn't need to post it twenty-one time?
[Magisk] Alxoom33:
Sorry, Tapatalk issue. Not posting. Needed to resend a few times.

Where in my post did I make it sound like I had a Pixel 4? Problem is people don't read!

---------- Post added at 01:40 PM ---------- Previous post was at 01:38 PM ----------

Sorry, had a taptalk issue. Like your sense of humor [emoji6]
[Magisk] JudgeDread11:
As you can see, even though you get the message that the post failed, it actually didn't.

So please next time when you get that message just refresh your page or app before posting again.

Also it would be appreciated if you'd edit your posts to remove the duplicates.
[Magisk] Displax:
Temporary fix to avoiding hardware attestation on affected devices. This changed "ro.product.odm.model" to unknown value to reset checking from HARDWARE to BASIC.

Should work while google selectively activates verification on certain device models.

Magisk module:
[Magisk] tazcan:
sadly it didnt changed evalType to basic i also tried clearing the services cache but it didnt make any difference too
[Magisk] tom1807:
Valid Point, after flashing patching the boot.img or the recovery.img, I haven't found a key combination for booting into recovery. I can only boot into the fastboot mode again and thats it. I found an unofficial TWRP, but this is a generic one for MTK6761 hardware and frankly not so sure about the source.

Edit: I tested whether I can boot into recovery

ADB reboot recovery: works

Fastboot reboot recovery (or fastboot reboot-recovery) has no effect and the tab is rebooting normally.

Does this command still exist in adb/fastboot?

I am using ADB version: 1.0.41

Version: 30.0.0-6374843

Cheers

Tom
[Magisk] zgfg:
Did not work for me - tried also by MHPC and by removing ro.product.odm.model

EDIT: Thank you for your new extended module hardwareoff_1.1.zip, IT WORKS now but for ro.product.model, see:

https://xdaforums.com/showpost.php?p=83035713&postcount=40681
[Magisk] tazcan:
so as far as i understand custom roms aren't affected from the rollout yet. So if i install a custom rom after i got the hardware death penalty is it possible to get basic eval back?
[Magisk] ilal2ielli:
Noticed this after I updated to July update. I did use Google Pay today though with no issues. Have had my dg.db file read only since doing the manual fix way back when.
[Magisk] laiguana:
Hi, I can't remove apps I don't want, link2sd or system app remover doesn't work, I tried installing different versions of magic and I still can't, sorry for my bad English
[Magisk] JudgeDread11:
If your device is system as root (SAR) you won't be able to modify the system partition directly. Only systemless.
[Magisk] pndwal:
OP has as of June 11. Android beta 2 as of yesterday:

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

:) PW
[Magisk] curiousrom:
No. It depends on if your device was shipped with Android 7 or newer. In that case it has a hardware-backed keystore as required by Google.

No.

Read this XDA portal article for detailed explanations: SafetyNet’s dreaded hardware attestation is rolling out, making it much harder for Magisk to hide root.

***
[Magisk] :
Hide what exactly? play services?
[Magisk] Philnicolls89:
Don't hide any apps, magisk has a 'hide' button in settings. This will allow you to pass basic integrity checks and cts profile checks (you will only pass cts profile if ur decide uses basic and NOT hardware for its checks).
[Magisk] AndDiSa:
Unfortuately there is no "fastboot boot recovery" or "fastboot reboot-recovery" ... I have the same issues with my Huawai Mediapad. The only possibility is to press the correct button combination while booting and hopefully the device boots into recovery, or (as I am doing almost all the time): boot the device normally and then apply an "adb reboot recovery" (which still exists), but for that you need a working ROM ...

Edit: This page you know already I suppose?
[Magisk] BernGH:
Hello,I used tecno cm 7,pls I need app to root it,or reboot app
[Magisk] zzz2002:
Had to reinstall everything on my s7edge yesterday. Wiped everything, formatted data... install went as expected no gotchas.

Installed the latest Magisk debug/canary. No problems, until I tried hide Magisk Manager. which fails almost imediately.

I can find no logs, no error files, nothing.

However it appears magisk is unable to download a new/renamed version of itself.

Anything known, work arounds?
[Magisk] Lughnasadh:
As Philnicolls89 said. Magisk Hide is disabled by default now.
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
[Magisk] alex.do:
Not working :(
[Magisk] zzz2002:
Thank you didgeridoohan, that solved the problem.
[Magisk] swieder711:
Can the stable Magisk Manager 7.5.1 be used with the Canary build of Magisk, currently at 20419? I am currently on Magisk 20400 and need a fix that is is 20406 (xposed cant find modules.list).

For me, when I add the Canary path, https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json to Magisk Mgr 7.5.1, the app just spins while trying to get the version status.

I tried the Canary Magisk Manager, but was having issues with SU granting permissions to apps that needed root.
[Magisk] leviiis:
Samsung s10 Android 9, I changed it manual to Only "SM" and it works.
[Magisk] reYar:
Yes is working galaxy s10+ SM
[Magisk] Displax:
Update module to change all "model" props.

May work on more devices.
[Magisk] zgfg:
Thank you - it works now on my Xiaomi Mi 9T, MIUI 11, Android 10

Actually, off the five props you change now I found that only one is critical for me: ro.product.model - and I can also use Magisk Hide Props Config instead to just delete this prop

So I leave the other four intact (ro.product.system.model, ro.product.vendor.model and ro.product.odm.model are defined to Mi 9T, while ro.product.product.model is not even defined)

With that CTS Profile is using Basic attest again and SafetyNet check fully passes

The only potential issue I see is that Settings/About does no more display Model correctly (I have to see could it affect something like OTA or so, but I can always disable that redefinition of ro.product.model)

Upon deleting Cache and Data for Google Playstore and Services, I also got back Device is certified

Edit: Confirmed that it slso works on Xiaomi Mi 9T Pro, with the newest MIUI 12:

https://xdaforums.com/showpost.php?p=83059133&postcount=10
[Magisk] loadie:
Also working on pixel 4xl.

Thanks for the work.
[Magisk] Philnicolls89:
Working on s10+, thank you.
[Magisk] tom1807:
You mean this in generic or referring to those devices like your Huawei or my Lenovon Tab?

Pretty sure that I used above command to boot in to the recovery from fastboot with my old devices (HTC, Nexus, etc...)

I knew the website, was confusing for me first.

Well, 50% good news.

With the original recovery, it worked to boot into recovery with Method 1, after patching the recovery, not anymore :rolleyes:

Cheers

Tom
[Magisk] snovvman:
For Canary, is it possible to turn off debug? Thanks.
[Magisk] zgfg:
See:
[Magisk] jerrycbrowne:
I really appreciate your help. I suppose it's a philosophical question. I should be able to have anything I want on my phone and remove anything I don't want. I can, of course, 'freeze' the apps but there's still that nagging feeling that I'm being tracked/watched. (Plus, there's nothing Google offers that I want or need. I don't trust or like Google. (And I get the irony of having an android phone to get rid of Google!)
[Magisk] J.Michael:
When Magisk is not installed, is it hard to get to recovery? Is it important to release buttons at just the right time?

On my tablet (Samsung SM-T290), you can get to recovery by holding Power and Volume Up until you get to recovery. When Magisk is installed (in recovery), you have to let go of the buttons at the first sign of life to signal Magisk that you are trying to boot Android, not recovery. It is hard for me to get the timing right. But it is easy to get to recovery: I just keep holding the buttons. (Maybe I really have to let go of the Power button, but keep holding the Volume Up. I don't do it often.)

My point is: If you have Magisk installed in recovery, you have to hold the buttons longer to tell Magisk that you really want recovery.
[Magisk] Philnicolls89:
I guess the short answer is yes, you do need to do the right button combo/release at the right time. But it is device specific for the button combo. For example with my s10+, to boot to recovery I need to hold down power volume up and bixby for 5-10 seconds then release. But to get to twrp I need to do the same thing but release the bixby button and keep holding the other 2 until twrp logo appears.

I also use power menu apps that have reboot to recovery options so I only need to use the button combo when booting to twrp or powering off the device completely. To boot normally and not to rexovery i simply power on without a button combo. Im not sure about booting to recovery without magisk installed though as I have never tried, but again it would be device specific.
[Magisk] Didgeridoohan:
Do you have any Magisk module that is magic mounting an app? You might be trying to alter Magisk's systemless mask rather than the actual /system...

And of course, Android is making it more and more difficult to edit system partitions:

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
[Magisk] DiamondJohn:
There are some components and apps that are part of the system and should not be removed.

I would be cautious of freezing. A while back, I used to simply freeze apps, but one day I saw that a frozen app was actually still in memory:eek: And hence i created the hibernate-freeze-hide method in the above app.

The best way is to use a build of android specifically made to take google out of the picture. I forgot its name, but its out there.
[Magisk] guhvanoh:
I think you're referring to e.foundation.
[Magisk] DiamondJohn:
The one I was thinking of had "copper" somewhere in the name

https://en.wikipedia.org/wiki/CopperheadOS

Maybe its more security focused than explicitly removing google. But I would guess it would be removing the more questionable google components.

Edit: Their web site says its google free: https://copperhead.co/android/
[Magisk] Hafiz0091:
guys

im facing app cannot be opened after magisk hide turned on (still same even after its disabled)

latest magisk canary, and canary magisk manager

heres the log

https://del.dog/ijaqulykil
[Magisk] Didgeridoohan:
You mean this app?

I had no issues opening it once added to the Hide list and with the Manager repackaged with a random name. On Canary 20419.

If you have the app on the Hide list and the Magisk Manager repackaged but it's still complaining about root it might be detecting something else on your device. Take a look here for tips:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] bunklung:
Okay, how about this solution to SafetyNet HW attestation:

App Mirror.

App Mirror would allow you to configure apps which create shortcuts right on your phone that look just like real apps. Call them what you want with what ever icon you want. Lets use McDonald's as an example. Once your create a mirror app with icon, you then configure a remote phone that's not rooted. When you launch the newly created McDonald's shortcut it's really a remote view to the second phone's McDonald's app.

This would allow you to seamlessly use apps on your rooted local phone, because SafetyNet is passing on the remote phone. Ideally notifications would forward/respond like Pushbullet too.

This is a better solution than having two phones in your pocket and who doesn't have an extra old Android phone laying around. You could just leave it on at home, plugged in, and on WiFi.

The main hangup would be NFC, but perhaps your old android, is so old and not longer on monthly security updates that it's rooted via unpatched exploit with the bootloader still locked. I would think they you could get into some really cool NFC one way stuff? I just don't know enough. Sorry for the long post. Perhaps someone will do a better job of explaining/improving my idea or already knows of a solution similar or better.

*edit* games would be the main hangup due to latency and graphics/video encoding issues :(
[Magisk] knpk13:
That's weird, why is copperheadOS still up?

I thought that had been discontinued due to some legal complications and the founder left the organization. I remember he rebranded his work as GrapheneOS and it's primarily focused on hardening and security more than degoogling (which is a part of it). They have EXTREMELY limited device support (only a handful of pixel devices, which I don't own). Someone else, anupritaisno1 on XDA is working on GlassROM with similar goals, but trying to bring hardening features to more devices, OnePlus devices in particular. Projects whose main focus is degoogling are microg, the e foundation, and alternative mobile OS's (or app stores like fdroid) like ubuntu touch.

I am not sure if using these projects offers any specific benefits in degoogling over a "normal" less hardened custom ROM without gapps. I would do more research before using CopperheadOS over GrapheneOS, and find out why it's still up and who's behind it, because they tried to make it commercial and there were conflicts about the direction the project was heading in.

https://en.m.wikipedia.org/wiki/GrapheneOS
[Magisk] swieder711:
I am still struggling to get EdXposed working. It's log file shows:

07-10 08:44:28.997 1673 1673 E EdXposed-Bridge: Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found

07-10 08:44:29.287 1862 1862 E EdXposed: mmap failed, errno = Permission denied

When this problem appeared before. I saw that a change to Magisk with SEpolicy fixed it.

I just saw that there is no Magisk folder (with its sepolicy.rules) under /persist on my Pixel 3 XL running the July update of Android 10! I think this may be related to my "permission denied" issue.

Any suggestions on how to get Magisk to install its sepolicy.rules on my phone? I am running the Canary release of Magisk (20419) along with .4.6.2 of Riru-EdXposed and 21.3 of RiRu-Core

I submitted the issue about "permission denied" on the Magisk Github repository. [MENTION=4470081]topjohnwu[/MENTION] suggested that it is an EdXposed problem.

Today is my 60th birthday! If I can get this fixed, that would be a nice present from the XDA community!

Any suggestions?
[Magisk] DiamondJohn:
not a solution, but it may be informative to test if it works while running in permissive mode.

Also, running a logcat filtering just for the selinux denials may be helpful. If that's all it is, then writing your own selinux adjustments to run on boot may get you up and running while waiting for the actual fix.
[Magisk] Hafiz0091:
nono

i mean, all app that not in recent cannot be opened with magisk hide on, and still same after switching it off