yashsingh1/xdaforums huggingface dataset:
[Magisk] Be4st187:
Install the canary build. That fixed it for me. Magisk was fine, but hidden Magisk caused the app to pop up when a root request was issued shortly after boot. Updating to canary build fixed this issue.
[Magisk] robrazil:
Device: Samsung Galaxy J1 Ace (SM-J110M)

Android: Lollipop 5.1.1.

Processor: arm-v7a

API level: 22

MAGISK MANAGER: 7.4.0

MAGISK: 18.0

After update to 20.1 version some system apps stopped to work and popup messages warned about that.

So, I back to 18.0 version and all working fine again.

EDIT:

After few days, many system app stopping to work including the launcher. I rebooted many times the smartphone but not solved.

So, I uninstalled the MAGISK and back to xposed + rootcloak.
[Magisk] 32bitTech:
I eventually figured it out ? Thanks for letting me know, though. Appreciate it.

I guess in the later versions, they changed it around a bit. I'm now in the process of making my own Magisk module to include all of the sound files I want (mostly from iOS).
[Magisk] topjohnwu:
OK here's a quick update.

I had planned to release tonight, so I tested the repo system, module in-app update, the template, the modules, the automatic Magisk installation, auto SuperSU module-lize...... all the new features are working fine.

However, at the last minute I tried it on my HTC 10..., and soon I found out that the root shell in Magisk Manager is not working consistently with some weird bugs....

The culprit seems to be the auto root stuffs that was added to the app, which I didn't participate the coding and contribution, and that might conflict with the changes I made recently.

Magisk will now stay away from all root management, I'll completely remove that part of the code from the app. You might know that phh's root has its own hide su program now, with features similar to suhide, why do I need to bother to do it again in Magisk?

So it might take a little more time before I clean up the Magisk Manager code........

I really want to deliver a full featured and well functioned update to all of you, so please stay tuned for further updates! :)
[Magisk] xu3sno:
Take your time dev!

We're not in a hurry! :D

Wish you luck!

Have a great day! :cool:
[Magisk] adrman:
I had not seen anything about this yet either here, the AP thread or phh's thread. Are you referring to AutoMagisk? Otherwise do you or anyone have a link?
[Magisk] cubandanger05:
You have to use SuperSU magisk version then flash SuperSU 2.78 systemlessly. Systemless xposed 86.2, Then Suhide version 53.
[Magisk] ELGeeRo:
[MENTION=4470081]topjohnwu[/MENTION]

What does "root management" include? Is it just the auto unroot etc. for specific apps that will be removed from Magisk or also the option to toggle root overall? Cause this would be missed severely by me, suhide doesnt have the same functionality, since it just hides the root status, and it wont be a permanent solution, cause the SaftyNet devs obviously cant just ignore it.

So pls dont remove this amazing feature of Magisk!
[Magisk] Captain_Throwback:
https://github.com/phhusson/super-bootimg/commit/3f51b03597ddee135517c6e82a3e06ffde8e1c8c
[Magisk] Artim_96:
At least restore stock boot.img and system partition.

Otherwise just start from scratch. Fish your whole ROM, Magisk and phh's SuperUser (and XPosed wanted) and restore your apps.

But try try run SafetyNet helper as often as possible in-between to find out what exactly happened between passing it and falling.
[Magisk] adrman:
Duh, the one place I didn't look. Thanks!
[Magisk] tech_head:
Doing that does work.

My Nexus 6P is also less stable. I'll see how often it reboots.

Startup is definitely slower.
[Magisk] topjohnwu:
It is on Github of phh's SuperBoot repo
[Magisk] chiwjiajun:
HELP!!!

Hey guys, need help here!!!

Followed the instructions here (http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/) but still failed to get boot version to reach Magisk v6. After flashing the magiskv6 i also get a "Boot verification failed, Secure boot error." message. Followed on, i also tried to flash phh superuser but still fail to get root access.

Currently on Fulmics 6.1, uninstalled root via supersu.

Thanks in advance!:)
[Magisk] dugapila:
Help/Request

Can you make a update-binary file for Wiko Pulp Fab 3G (or a whole Magisk-v6.zip)?

I alreay tried modifying where the boot img comes from - because in the normal update-binary file it can't even find my boot img due to the non-conventional way Wiko manufacturers assigned all the partitions. But even when I modifiy the file to recognize a boot img, either it says boot partition is too small and can't flash, or if it flashes (bacause I bypassed boot size verification) it just bricks the phone to the point where it takes several hours to get it working properly (after flashing to stock rom, it's usually stuck in booting to Factory Mode only, and belive me, it's a pain in the ass to deal).

PS: I'm flashing Magisk with FlashFire hence on a rooted phone (I never tried to flash a SuperSu uninstaller zip before the flash of Magisk and maybe that's why I can't flash?) because ofc this phone doesn't have a freaking custom recovery for it cause no one owns this crap xD

Thanks,

dugapila.
[Magisk] ken2802:
any way to tell if was succsesfull?
[Magisk] aerostride:
So i tried Magisk on Sony Xperia Z5, yet to no avail. Here are the steps i took:

Flashed AOSPA ROM

Booted up, did full unroot through SuperSU

Then in TWRP 3.0.2-0 i flashed osm0sis' unSU to remove the rest

Then Magisk V6 and phh's Superuser

Booted up, installed Magisk Manager using sideload

Installed phh's SuperUser from Play Store

Magisk Manager seemed to work, but even though root was off (according to the manager) i could not pass the SafetyNet check.

PS: No Xposed installed, su not found in /xbin or /bin (used root browser)

So i did the following (totally different approach)

Flashed Magisk uninstaller

unSU again

Then the newest SuperSU from Chainfire in Systemless mode

Reboot, Set Up SuperSU

In TWRP i flashed HideSU

Root worked, not to be found in /xbin or /bin, found it in /hidesu

But i still failed the safetynet check.

I have no idea what to do now, any help?
[Magisk] Turbopuschel:
I was able to install Magisk ony my Sony Xperia Z1 Compact with Stock ROM thanks to [MENTION=4099072]toshi127k[/MENTION] and [MENTION=7760226]QWEnter[/MENTION] and this post: http://xdaforums.com/showpost.php?p=68884579&postcount=3543

But I find the stock ROM to have quite a bit of bloatware and tried to uninstall that with Titanium Backup (already did that successfully in the past). But this time, after every reboot, the uninstalled system apps are back again. I suspect this is somehow due to the way Magisk works? Is there a way to still get rid of system apps?
[Magisk] QWEnter:
First of all glad to read that you have successfully installed Magisk v6.

Could you please write exact names of bloatware you mentioned in your post?

And another question - do you mean, you've deleted them from /system/app and they appeared again after reboot?
[Magisk] Switiz:
Hy guys.

I followed all the steps and I still can't play PokemonGo..

I flashed magick, the phh superuser and then installed Phh superuser from playstore. IT worked, but I wanted xposed as well, so I Installed systemless.. after that, PoGo won't start.

plz help :(
[Magisk] Didgeridoohan:
And there's your answer... Either disable Xposed or use the suhide method instead.

And: There's a specific Pokemon Magisk thread. Please use that for Pokemon questions.
[Magisk] Switiz:
srry for posting here..

I disabled xposed from installer, restarted and hale The same problem. I'll try to user Suhide. thank you
[Magisk] Turbopuschel:
I basically want to uninstall most of the apps from this list: http://xdaforums.com/showpost.php?p=60375059&postcount=1, for example AR effect, the Google Play stuff and the Xperia Social Engine stuff.

As I said, I used the uninstall feature of Titanium Backup which I think deletes the apps, be it from /system/app (like Account Manager, called "sneiaccountmanager" in the files) or /system/priv-app (like AR Effect, called ar-effect in the files). And I did that successfully in the past with the apps not returning after reboot. After reading your question I looked at the corresponding folders/files after uninstalling from Titanium Backup before rebooting and they were still there although gone from the Titanium Backup list (and system apps that were updated were only there as their unupdated versions, causing them to be updated again after reboot).

Now if I delete the files manually in some file explorer (and the folders of the apps, I guess? I am not that knowledgable about manually manipulating system files) the apps will probably be gone for good? But still why doesn't Titanium Backup uninstall work anymore? I still suspect the interaction with Magisk to be part of the cause somehow because that is the only thing different from when I uninstalled bloatware in the past.
[Magisk] BladeRunnerA2C:
I lost the original boot.img of a local source code less phone and installed SuperSU. I tried fully unroot then installed Magisk framework via recovery but it always fails
[Magisk] nugrahayoga:
Phone: Redmi Note 8 Pro (Begonia)

OS: MIUI 11 based on Android 9 (Indonesian version of official rom)

Magisk Manager: 7.4.0

Magisk: 20.1

Hello, I have a question why hide magisk manager always failed to hide. I've check the logs, it written that

Anyone has any idea how I can fix this problems?

Here's the full logs.
[Magisk] Didgeridoohan:
Try temporarily disabling Play Protect when hiding the Manager (and then enable it again afterwards).
[Magisk] nugrahayoga:
Google play protect is already disabled, but still the same error occurred. Any other workaround for this problems? Manually install repackaged magisk apk also failed, there's a toast notification that says setup failed.
[Magisk] onoakino:
Magisk 19.0 on Oreo 8.1.0 custom ROM and using MagiskProp Hide Module

Hi [MENTION=4667597]Didgeridoohan[/MENTION],

I'm on Oreo 8.1.0, Magisk 19.0, Magisk Manager 7.1.0. Hide Magisk Manager doesn't work. It keeps on returning "Hide Magisk Manager failed". My device's Play Protect is already disabled and it still fails.

I need to hide it because my banking app detects that I am rooted even though I already included it on the Magisk Hide list. This is the app https://play.google.com/store/apps/details?id=www.mobile.bdo.com.ph&hl=en

---------- Post added at 10:54 PM ---------- Previous post was at 10:48 PM ----------

Also, I noticed that Android 8 was skipped on the supported list of androids for Magisk 20.1. Android 7 and 9 were mentioned but 8 was left out. I tried reading the change logs but I cannot see any mention of about oreo being unsupported.
[Magisk] Cheako:
Nubia Z20(NX627J) V1.x(NON-EU): Contains links to boot/recovery images.

I fixed my phone. I was using V2.x files, but my phone is V1.x. The major version numbers are more like part of the model number than like a version indicator. Here is the full dump where I got the boot and recovery images, it's 2.2GB compressed

https://www.filehosting.org/file/details/835328/NX627J_NubiaEmergencyDownload_V103.7z

I'll try and post just the boot/recovery images here: https://mikemestnik.net/archives/

SHA256 (NX627J_NubiaEmergencyDownload_V103.7z) = bd412eeab191c001a4ee5b11bda8a2ec7273257ccd2e1d024e60e8c6a1bd174b
SHA256 (NX627J-stock-1_03.7z) = f53a120dc7e8029bf2bb0fb7a462d027376d63bb39e4b7f2ae2f55ae2bcba9ae

I attempted to patch both the boot and recovery images, not sure I did the recovery correctly. Either way neither booted, I got the same go.c/ABH error when I flashed the V2.x images.

Thanks!
[Magisk] Forever Alone:
It's almost 2020. World has moved to Artificial Intelligence. Here I cannot even get the "Restore Magisk Manager" button work properly from such a popular application. Stucks at Restoring notification. Applications are not getting root access properly. Android 10 ROM.

Edit: had to uninstall magisk completely and reinstall it. IK coding is very difficult and im sorry for the above message, but i never expected Magisk to crash, or at least like this.
[Magisk] Techguy777:
Do you guys know if TWRP has to be version 3 and up to work with Magisk? I got a fiio x5iii coming and TWRP 2.8.5 is all we have and I want magisk but someone said it wont work without twrp 3.0. Its only on lollipop.
[Magisk] andrew_yousry:
tried everything didn't work for me :(

actually it detected root only after installing modules, before that it was working fine
[Magisk] amg314:
Try do the following:

1. Repack the Magisk Manager with a random name thru Settings

2. Add the banking application to the hyde apps list, check the safetynet and clear the data (not cache) of your banking app.
[Magisk] stormy1777:
Hopefully someone can help :)

Got Android 9 on Redmi 7A , with Magisk 20.1/Manager 7.4, root working fine, but, only for fixed number of apps!

This is standard MIUI 10.2.5 ROM, no mods, with twrp 3.3.1.

In the SuperSu section of Magisk it has 2 apps, that were somehow granted (with pop up asking to approve), only these 2 apps get root, any NEW app does NOT get root, no pop up or anything.

Tried all things listed here: https://android.gadgethacks.com/how-to/root-apps-not-working-with-magisk-heres-what-do-0189903/

in addition, in Magisk setttings, set to GRANT by default, i.e. not prompt, still root checker app or anything else gets permission denied.

Tried to reinstall Magisk by patching in-place, and rebooting, no change, re-installed Magisk Manager, no change, only 2 apps have root :)

This phone is completely new, no old supersu or any other rooting apps installed.. just Magisk.

Also, disabled all modules, and tried Core-only, rebooting after each such change.

Disabled all un-hide in Magisk, did not help either.

when running logcat during a root request , this is shown in logcat:

12-02 12:32:29.975 1362 2917 I ActivityManager: START u0 {act=request flg=0x18000000 cmp=com.topjohnwu.magisk/a.m (has extras)} from uid 10154
12-02 12:32:29.975 1362 2917 D com.android.server.am.ExtraActivityManagerService: MIUILOG- Permission Denied Activity : Intent { act=request flg=0x18000000 cmp=com.topjohnwu.magisk/a.m (has extras) } pkg : com.topjohnwu.magisk uid : 10154 tuid : 10177
12-02 12:32:29.980 7670 7670 D AndroidRuntime: Shutting down VM

at final request/failure another mention like below:

12-02 12:32:53.825 1362 1728 I ActivityManager: START u0 {act=request flg=0x18000000 cmp=com.topjohnwu.magisk/a.m (has extras)} from uid 10154
12-02 12:32:53.825 1362 1728 D com.android.server.am.ExtraActivityManagerService: MIUILOG- Permission Denied Activity : Intent { act=request flg=0x18000000 cmp=com.topjohnwu.magisk/a.m (has extras) } pkg : com.topjohnwu.magisk uid : 10154 tuid : 10177
12-02 12:32:53.828 7761 7761 D AndroidRuntime: Shutting down VM

Attached more complete logcat..

The prompts to approve root worked only TWICE, afterwards, not sure what changed, getting no prompts, and so all requests are denied for some reason...

Any help much appreciated.

Stormy.
[Magisk] Didgeridoohan:
[MENTION=7274885]stormy1777[/MENTION] First thing to try is the Magisk Canary build. Sometimes there has been changes upstream that fix things on the stable release channel, so reporting about bugs should always happen on the Canary builds. And, use the debug build so that the Magisk log has more relevant information.
[Magisk] stormy1777:
[MENTION=4667597]Didgeridoohan[/MENTION] Thanks, was not aware of that.. Found the canary thread:

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

However, on my devices/phones (Xiaomi, Redmi 7A), I found the magisk installation to be tricky, the normal installations do not work for some reason. like: get stock boot.img, patch in manager 7.4 and flash using twrp, or flash from fastboot. These methods do NOT work , the only way I got get it to install is using a provided boot.img from the 7A thread, which has magisk 19.3, then update in-place from M/Manager.. So, I'm afraid going into the canary path might leave me without root/magisk at all, since the "install" patch stock boot.img does not work. Some of posts I've described that are here: https://xdaforums.com/redmi-7a/help/unable-to-root-redmi-7a-miui-11-0-6-t4011525

more specifically: https://xdaforums.com/showpost.php?p=80498891&postcount=179

and, since then, that boot.img (global 10.2.5) is no longer available to download (I've got a saved copy)..

Clearly Magisk was working fine, since pop ups did appear (phone 1 has only 2 apps, but phone 2 with similar setup has over 20 apps, but cannot get any NEW apps)..

If there's any further debug that can be done using the existing install appreciate it. Otherwise, will wait for other replies/ideas.

Thanks for your time and info. Stormy.
[Magisk] Didgeridoohan:
[MENTION=7274885]stormy1777[/MENTION] In-app upgrades work with the Canary builds as well. Just download the Canary Manager from the thread (the debug version) and change the update channel in the Manager settings to Canary (debug). Then you can update as normal.

Like I said, Canary builds are necessary when troubleshooting stuff like this. There's no use wasting time on issues that might already have been fixed...
[Magisk] nugrahayoga:
I finally manage to hide magisk manager by temporarily set selinux to permissive, hide manager, and set selinux back to enforced. I think this is miui problems that caused hiding magisk manager failed
[Magisk] stormy1777:
[MENTION=4667597]Didgeridoohan[/MENTION] HERO!!

Thanks so much for insisting and giving the needed confidence!! did as you said: Installed Magisk Manager Canary, then things started to work better, but not perfect, then installed in-place magisk canary (no debug), and it worked flawlessly.. so got 2 Redmi 7A phones on that, and it resolved all root/supersu issues, prompts pops up, etc!!

Thanks again, really appreciate it!! I'll stay on that until stable becomes more applicable to this device..

Thanks Thanks!!!

Stormy.
[Magisk] GryphonBR:
Ran into some really uncomfortable trouble here: installed a Magisk module developed by Mishal to enable Live Transcripts on my OnePlus 7T, but it seems to have brought my phone to a state where it can't finish booting up. Because 1+7T factory shipped with Android 10 already, it has the new recovery partition that's causing TWRP devs a lot of trouble; in the mean time, I'm stuck with, apparently, no alternative to remove the faulty module. Is there something that I could do, under these circumstances, to not lose root (or, worst case scenario, only lose it temporarily) while still being able to remove the faulty module?

Thanks in advance for any help!
[Magisk] smileguy91:
With the latest December security patches on Pixel 3 XL Android 10, when trying to boot with the patched Magisk boot image, I get error boot prepare. Anyone else with this problem?
[Magisk] rogers11:
No, on my Pixel 3a it worked like in the months before.
[Magisk] stormy1777:
Not sure if this is related to switching to Magisk/Canary (7.4.1-latest) + 20.2-latest, on Redmi 7A(android 9, MIUI stock ROM 10.2.5) , the safetynet checks are not passing, both:

ctsProfile: false
basicintegrity: false

I assume this is a FAQ? Found many suggestions online, just wondering what's best path to debug?
[Magisk] Ch3vr0n:
Afaik if you don't even pass basic integrity, it's not a magisk problem but a rom problem.
[Magisk] Didgeridoohan:
Try the remove-modules adb command. Details:

https://didgeridoohan.com/magisk/Magisk#hn_Disablinguninstalling_modules_manually

First thing to try is to toggle MagiskHide off and on again. That usually fixes things after an update. More stuff:

https://didgeridoohan.com/magisk/MagiskHide
[Magisk] Akaze:
Magisk rooting on S10+

How do I root my S10+?

I'm using Android 10 Beta Snapdragon U.S. Unlocked.
[Magisk] Tyakrish:
Recently I have been interested in this SAR debate with Magisk. After reading stuff about SAR, Android 10 etc, I have come to know that for A only SAR roms, magisk is installed to recovery... So to use magisk with them we would have to boot to recovery first then to system.

I thought all Android 10 ROMs were supposed to be SAR ROMs and I would have to boot to recovery everytime for the Android 10 roms which would release in future.

But when some non SAR Android 10 builds came up for my device (which is A only non SAR from the beginning), I was pleasantly surprised. It seems that these builds make use of ramdisk despite being Android 10.

So will Magisk install to ramdisk only as usual for these ROMs ?
[Magisk] ktmom:
I think this Twitter thread will help.
[Magisk] mimmmmiiii:
If I want a clean start to use Magisk without TWRP, does anyone know to proceed? Since TWRP is not supporting Android 10 now ...

Because after Android 10 December security patch, I couldn't boot with Magisk on my Pixel 2.

Many thanks. :)
[Magisk] Badger50:
Simple as patching the stock December boot.img and fastbooting it to both slots. Just did that very thing on my P2XL a couple hours ago :good:
[Magisk] mimmmmiiii:
Yeah, but it's not a clean start, right? A clean start should use Magisk-uninstaller-20191102 via TWRP, but TWRP isn't supporting Android 10 now ...

Still thanks.
[Magisk] -Jeka-:
I've just updated Google Pay to latest version, and it stopped working, saying the phone is rooted. I'm using Magisk hide, also tried to repack magisk manager with different name, but without success. I'm using Google Pixel with Android 10 and Magisk version is 20.1
[Magisk] Badger50:
Then just uninstall magisk from within magisk manager. Also, I used TWRP to remove a magisk module that didn't like the December update. You could use twrp file manager to remove all things magisk as well. You may get flashing errors in twrp, but that doesn't mean it doesn't work :good:
[Magisk] ktmom:
You should be able to use FK Kernel Manager. It's got a built in flasher (thank you very much [MENTION=4544860]osm0sis[/MENTION]). I've not tried unrooting this way, and flashing requires root, but that should all be set before the actual flash occurs.

Otherwise, remove modules from Magisk Manager. Then reboot. Remove Magisk Manager then shutdown and flash the unmodified boot.img from your ROM.
[Magisk] mimmmmiiii:
I already use the uninstall function in Magisk Manager to get back stock boot.img and reboot to receive December OTA.

After OTA, I want to install Magisk but get boot loop so I lost Magisk and root.

I wonder if a clean start would help me get Magisk and root back or not.

Anyway the point is, I can't use Magisk Manager to make a clean start because there's no uninstall option now. xD

TWRP file manager ... that's new to me.

Thank you for your reply.
[Magisk] ktmom:
Search this thread for the adb module uninstaller command. If you left modules installed, and they're not compatible, then after installing Magisk you will get a boot loop.
[Magisk] Badger50:
Ok. Then download the OTA or factory image on your pc, extract it, put the stock boot.img on your phone, patch it with magisk, then move the patched boot.img to your platform-tools folder on your pc, and fastboot it to both slots with...

fastboot flash boot magisk_patched.img --slot=all

Then boot up, and you should have root :good:
[Magisk] mimmmmiiii:
Thank you for the hint, I'll give it a try! :)

---------- Post added at 03:06 AM ---------- Previous post was at 03:02 AM ----------

So your P2XL with Magisk is good after December patch?

And TWRP 3.3.0 still function except flashing part?

Thank you!
[Magisk] Badger50:
Yep, twrp 3.3.0-0 still works on my P2XL with December update. Again, it will throw mounting errors, but it still should flash zips. I only fastbooted into twrp to use the file manager to remove a magisk module that wasn't compatible with the December update, then went back to bootloader mode to fastboot the patched boot.img to both slots, and all is well :good:
[Magisk] mimmmmiiii:
Many thanks to you and [MENTION=6617276]ktmom[/MENTION],

I use TWRP manager to remove all Magisk modules and then reinstall Magisk and modules one by one,

everything is working now! :)
[Magisk] Badger50:
Boda bing Boda boom! :good::cool:
[Magisk] Himansuaj:
Xposed frame work failed to install in my op5 with nitrogen os version Android 10

can any one help me