From topjohnwu twitter
A few PSA:
1. Canary release builds are no longer provided. All Canary builds are now built in debug mode.
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:
But I personally prefer the first method.Code:
► Magisk ► Modules ► TeMeFI Hide System Apps ››► Add or Remove - Hide System Aps using a TeMeFI Module *
Let me know how you go.
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.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.
No matter what I try I can't delete any system app. Magisk is installed. I use the awesome Amaze file manager which neatly lists all system apps. However, after removing an app and 'Done' being displayed it remains there clearly still installed. I'm probably doing something wrong but I have no idea what. Preserve dm-verity is enabled. Any tips or tricks to try?
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 And hence i created the hibernate-freeze-hide method in the above app.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!)
The one I was thinking of had "copper" somewhere in the name
The one I was thinking of had "copper" somewhere in the name
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/
not a solution, but it may be informative to test if it works while running in permissive mode.
nonoYou 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:
I installed the SElinux switch and have it set to Permissive. No change. I will reinstall Magisk manager while set to permissive.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.
Okay, how about this solution to SafetyNet HW attestation:
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
I don't doubt it's working, but Magisk Hide is disabled by default as of 20.4 .That's really odd. Because on my device it's enabled and working with PayPal, My Transport app, and more.
So, I reject your reality and substitute my own
I enabled user independent in the settings of magiisk.
Not sure if that did the trick, but I assure you it's working on my Samsung A70 droid10 with a downgraded Google and Assistant. !!
regarding root switch, yeah once I've got magisk installed I turn it off which does reboot the box.Great! I was going to say sounded like nothing seemed wrong with Magisk mask itself, but likely reset corrupted Magisk data in /data/adb which should be fixed by reinstalling Magisk. (Sometimes needs deletion of files in /data/adb.)
Happy update worked; should be able to use latest 23.0 or 23001 now.
Do you need to restart after changing OEM root switch? Not sure what that enables exactly... guess you disabled after update. I was wondering about conflicting SU in boot ramdisk... I guess OEM could have used Magisk SU anyway... A root detection app may have given info.
In case you haven't read it, @Didgeridoohan has great (comprehensive) overview of issues / fixes here:
(Time to 'Updatefor Magisk v23.0(23000)'? ) PW
all is well now with @Didgeridoohan and @pndwal's help...
Great! I was going to say sounded like nothing seemed wrong with Magisk mask itself, but likely reset corrupted Magisk data in /data/adb which should be fixed by reinstalling Magisk. (Sometimes needs deletion of files in /data/adb.)all is well now with @Didgeridoohan and @pndwal's help...
I hadn't used magisk hide previously no. I managed to fix the issue by updating magisk manager.
first I tried to flash a magisk uninstall zip via Ex Kernel manager as that sounded safest if it didn't work.
it said it had completed the script with success but upon reboot the manager was showing 20.4 still installed.
I reactivated the OEM root switch and updated the manager app to v22.01 I think, then I updated magisk itself and that has worked completely. I have a couple of modules installed already...
many thanks gents
When you had Magisk 20.4 installed, did you use MagiskHide? Did you rename the Manager?@Didgeridoohan @pndwal thanks for the suggestions, just to be more clear on what happened...
I flashed magisk via magisk manager first time around because I had janky OEM root. after a recent reset most of what was flashed from v20.4 still remained. installing magisk manager showed 20.4 as installed and SU was working for granting apps permission but the module side was non functional. it would download modules and try to install them and then tell me I needed to flash 20.4...
some parts of that 1st manager flash survived the reset, others seemingly not so. trying to uninstall via the manager didn't take me back to a blank slate like I hoped (so I could repeat that 1st flash again). I'm in limbo, rooted for root access but not for magisk modules. every time I open the manager it asks for the download of additional setup files that never work. so I need to reflash somehow.
flashify installs and reviews say it still works for android 10 users but I've no idea how it would cope with a more complicated (presumably) script. I have Ex Kernel manager that has a script manager and a flasher. I just don't know if these are good gambles worth considering.
Just use Magisk/Canary button on Magisk GitHub home page to get app. OpensTried using https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk after it was already rooted with Magisk, but adb said [INSTALL_FAILED_VERSION_DOWNGRADE]
Wouldn't say no point however.