yashsingh1/xdaforums huggingface dataset:
[Magisk] jasonmerc:
So the Blade A3 Prime is too new to work with mtk-su. It only seems to work on things that are And. 9 and older, and this phone shipped with 10. As for your last point, we can't simply do that because of two reasons: one the vbmeta keeps the phone from booting (we had to modify that), and two the boot image doesnt support ramdisk booting (we had to patch that in with an oss patcher). If we don't do those two things, the phone will refuse to boot at all.

What doesn't help either is the Blade A3 Prime is an A/B phone so we can't just flash over TWRP or something to /recovery to mess around that way. Even dirty ports of TWRP are almost impossible because most phones with this MTK6761 chipset are x64, and this one's 32 bit

We did not think to try canary Magisk though, we will give that a shot shortly
[Magisk] saoudien07:
I am facing the same issue, after trying to update to v.22!!

I fresh installed Rom Marshmallow 6.0.1 on an old Tab. + installed TWRP + old Magisk 21.4. And when I update the Manager to v.22. It is like Magisk/ Root is no more present, and when I try direct Install no help. Same with Canary Manager >> Same Error

Magisk_install_log

- Target image: /dev/block/

- Device platform: armeabi-v7a

- Installing: 66e30a77 (22006)

! Unable to check signature

! Installation failed

Any help please on how to update the manager/ Magisk Root to v.22 ??

Manager before update and after update to v.22
[Magisk] pndwal:
You should try Canary. Seems a major issue with vbmeta on MTK was fixed 29 days ago, so not even in latest v22 stable:

https://github.com/topjohnwu/Magisk/issues/3727#issuecomment-803316566

Also, as long as bootloader is compatible w/ boot ramdisk, Magisk general should work as it actually adds basic ramdisk even when wholly missing (eg, for type III Ramdisk=no devices). This was fixed for SAR non A/B, but will likely help in other cases too:

https://github.com/topjohnwu/Magisk/commit/e72c6685edf81706617a3444575c4500b9b8fe6c

If normal method still doesn't work w/ latest Canary, simply creating a Magisk issue (following John's template inc. Logcat, logs etc) will likely result in an official solution / support for you (and others w/ similar devices), and negate need for 3rd party (temporary root, etc) solutions. I'd strongly recommend this approach. 👍 PW
[Magisk] pndwal:
Did you unhide / restore old 'Manager' before updating app as per Release Notes?:

https://topjohnwu.github.io/Magisk/releases/22000.html

It's a MANAGER/APP hiding incompatibility, not Magisk in ramdisk

I suspect you have a hidden version of manager Installed, and you only need to find/remember the name you chose, remove BOTH this and current app (normal app uninstalls), and reinstall app to fix conflicts. Nb. module /setting data witll be unaffected as it is in /data/adb.

PS. Not sure this applies as I don't know if you even had this option on Marshmallow! 🙁... You may have another issue...you didn't have Recovery mode selected did you? PW
[Magisk] poonyakon12:
Can Magisk still fake Knox to 0x0 to make Samsung Health work?
[Magisk] saoudien07:
Thx for the help.

And no, it is not related to Magisk Hide.

I mean the Rom is just freshly installed yesterday. I did not tweak any settings yet, as Magisk Hide or else.

Just Flash Fresh Stock Marshmallow + TWRP + Magisk 21.4.zip, and hope when I try to update to v.22, he crazy issue happen. And is jsut install v.21.4 , Root ang Magisk is functional as should, so for now more more updating to v.22 for me!

What is more crazy is that before to clean flash 2 days ago, the device was running v.22 fine.

I think it is related to Marshmallow and v.22 as I found other post peoples having this issue with Marshmallow and old device...
[Magisk] pndwal:
Yes.

I didn't mean MagiskHide, but 'Hide the Magisk Manager / app' in Settings, which is different, but I suspect you didn't see this w/ marshmallow before 22000 series Magisk anyway.

Others have indeed had similar issues with Android 6 on arm devices, and there may be a regression connected with recent changes, but it seems no-one has provided sufficient info / logs to help fix. Eg:

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

You could try supplying needed info / logs (follow John's issue template).

You may want to watch this issue which may be related / the same ('No root installed magisk N/A on all versions since 2200 on... Android 6.0.1', although the user has Intel x86 device):

https://github.com/topjohnwu/Magisk/issues/4103 PW
[Magisk] pndwal:
Not sure about need to fake knox, but I'm not a Sammy user.

I believe you may need test version of Universal SafetyNet Fix module for biometrics and other functions:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84693353

Others seem to have this working (I don't have details re. how). Eg:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84656377 PW
[Magisk] saoudien07:
yes I checked both MagiskHide, and 'Hide the Magisk Manager / app' in Settings, which is repacking of Magisk Manager with another Name for it to dont be detected... But as said the issue happen even on fresh Rom install, so I used an old backup TWRP for now... I even though the backup was kind of buggy, so I said lets go with fresh install from zero, and hop Magisk issue...

Right that issue Github (https://github.com/topjohnwu/Magisk/issues/4107) that is exactly what I was refering to. I mean I came around it yesterday during my search...

I will keep an eye on it, and for now I ll stick with v.21.4, because it works flowless...

Thx very much for the support ))
[Magisk] pndwal:
Yes, I know you said fresh install, but you said you installed 21.4, then updated to 22 I think... So, as long as you DIDN'T set app / Manager to 'hidden' before updating it should have worked...

I see you responded to that issue (are you a doctor?)... But this won't get attention as it's already been closed. You'd have to open new issue for arm device to get attention. The other issue is still open / active however. PW
[Magisk] saoudien07:
yes I did not tick hide, no MagiskHide , and no HideMagisk ( the one which repack the app). Actually I do not use any of them, never got need of them

Thx for the info above the closed issue. Newbie mistake :p

And u right,I am a doc
[Magisk] ipcammm:
I have the exact same problem with my old tablet (SM-T550):

Same root method with TWRP.

Same error logs when trying to update from Magisk 21.4.

Same language: french.

Same Device platform: armeabi-v7a.

But with Android 7.1.1 !
[Magisk] saoudien07:
Kind of nice to see, I am not only one facing this issue!! lol

Additionally to that I am facing TWRP Restore problem:

I restored an Backup with TWRP ( Data + System + Boot), and it takes forever on Splash "Samsung" boot. And it never boot!!

I suspected the Backup to be guilty, so went with Fresh Rom flash + TWRP install + Magisk v.21.4.

Then made a Backup, it ended fine without errors, and then go Restore Part. Again it stays on Splash Boot forever!!! Device never booting to System!! Sometime it restart after a while, and again stucks on Splash Boot "Samsung".

So no way to try risky things on the device if needed, as TWRP Backup restore is not available.

I even try to unRoot Magisk right after the Restore of the Backup, without any change. Still Stucking on Splash...

Also I tried reinstalling Magisk, same stuck... I read somewhere it fixes stuck on Splash Boot...

Did you recently try a Nandroid Restore on your Tab ??
[Magisk] J.Michael:
Maybe Backup more partitions? (vbmeta, recovery)

Try Fresh ROM + TWRP, then Backup, Restore.
[Magisk] saoudien07:
No vbmeta disponible, If I am not wrong it is not for Samaung devices....

I tried all possible combination, when I do the backup, I usually Backup everything, exept Cache. Just in case, always possible to choose what everyone want to restore later...

Then when I restore, I restore: System + Data + Boot. I read System Image is no need, I even tried 3 of them:

Restore with System only, stuck on Splash

Restore with System IMAGE , stuck on Splash

Restore with both ticked, also stuck

Currently I am testing Fresh Rom + TWRP + SuperSU Root (old Root), then Backup and sees if the Restore works...

I already installed SuperSU Root ...

If still Restore pb, I ll go with Fresh Rom + TWRP, only, without any Root of anyKind...

Update:

Magisk is guilty of all my headache!!!!

As I said I tried Fresh Rom + TWRP +SuRoot (old Root method).

Then I backuped, clean everything in TWRP + reboot to TWRP, and restore the Backup just made, and it works flowlessly!!

It seems Magisk is not really going well with old arm device, only assumption here, I am no dev.
[Magisk] RheinPirat:
We, the user off "Postfinace" (PF) https://play.google.com/store/apps/details?id=ch.postfinance.android&hl=de_CH&gl=US in Switzerland have a huge problem. The devs of the app implemented a function to detect magisk and i dont know how.

So i flashed a Mi9T (K20) with the latest HavocOS ROM with Android 11 (same on Android 10). The bootloader is also unlocked. I can now install the PF app und it works.

But after I installed Magisk, Hide Magisk Manager and added PF to Magisk Hide, the app doesn't start anymore.

And the strange thing is, if I uninstall Magik via the app, PF wont start anymore. I have to wipe the device and reinstall the OS.

Any idea?
[Magisk] saoudien07:
Did you try to force close this app + clean all its data, follow by a reboot??

Then check if I re-works again...

If so do, do not open it before Magisk hide +MagiskHide (from Maisk settings= Repacking).

Apply all hide stuff of Magisk hiding, only then open back the app.

Some apps, like Banky app, once Root detected, keep a trace of that detecting...

you need to make said app forget its data.....
[Magisk] RheinPirat:
I started the app after hiding manager and the app itself. Never had such issues with an app and root like now with PF
[Magisk] J.Michael:
Magisk and MagiskHide Installation and Troubleshooting guide by @Didgeridoohan
[Magisk] zgfg:
What if you only clear Data (maybe just Cache) for the given app, or ununstall and reinstall that app - after the fully uninstalling Magisk (instesd of wiping device)
[Magisk] RheinPirat:
Thank You. I read a lot there. And i tried "Shelter" from F-Droid. PF is working now xD

False Alarm. The app detects now root again

I tried that, but didn't helped. I think the app write a file somewhere and find it again after reinstalling.
[Magisk] pndwal:
With root, do you have full SafetyNet pass as well as Play Protect "Device is Certified" in PlayStore Settings? PW
[Magisk] RheinPirat:
Yes.

Basicintegrity - Check

ctsProfile - Check

evalType - BASIC

Play Protect certification - Device is certified
[Magisk] saoudien07:
Solution:

Found out kind of Magisk to be guilty:

I tried a restore of a Backup: Rom + Magisk + Marshmallow, and it stuck on Boot forever, I decribed about it above...

Finally it was not related to Partition being Restored. Tried a Restore of Backup ( Rom + SuperSU + Marshmallow) and it works fine. then tried to restore problem giving Backup, and after restore flash Stock Boot of Marshmallow Rom (Obtained from Stock Rom), and if booted fine to OS.

I even tried Restore + unRoot with Magisk Uninstaller 17.01.2021, and it do not help, should be with Stock Boot !!

So my recommendation for this old device/arm/Marshmallow is, to unRoot the device before to do a Backup!!

At least when you will to restore that made backup, you wont have problem to restore it, as I had, please re-Root, is also an additional flash.....
[Magisk] saoudien07:
that is what I usually do, start over everything ? from zero. And it is sometime a good idea to run a cleaner, in my case I use SD Maid
[Magisk] ID#:
TL;DR: When updating the manager from 8.0.7 to 22.0, the app won't open after update. How can I solve this?

I am on a OnePlus 7pro with 10.0.11.GM21BA build.The magisk manager tells me that I have version 8.0.7 of the manager installed and magisk 21.4. When I try to update the manager, it downloads the new app and installs it, but whenever I try to open it, it force-closes immediately. I tried rebooting after install and I tried disabling magisk hide and rebooting before the update, updating, and rebooting again. The outcome is the same: fc.

How can I perform the update?

Thanks in advance!
[Magisk] ineedroot69:
read changelog
[Magisk] ID#:
Well, I did, and because it says "RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!" I did toggle off magisk hide. But I just realised that I probably should use the "Restore Magisk Manager" Button in the manager.

Now it is working. Thx.
[Magisk] ineedroot69:
i have question let say i have TWRP.img and i patch it via Magisk would flashing the result TWRP_patched.img work as intended?

Can i have TWRP and be rooted with Magisk at the same time?
[Magisk] pndwal:
Yes, but as Instructions say "... you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app." PW
[Magisk] ineedroot69:
so it's a yes and a no at the same time? sound acceptable 🙃
[Magisk] bemyfrnd:
I am using lineage os without gapps. I had rooted my device and whenever I used to open magisk , it had 4 buttons (iirc) to access magisk hide, logs, module. But when I opened magisk now, the buttons were gone and when I checked if device was rooted, it wasnt. how is this possible? what should I do? I did update my os yesterday
[Magisk] ineedroot69:
magisk got uninstalled i assume since you update your os?
[Magisk] bemyfrnd:
so every time the os updates, i have to re flash magisk?
[Magisk] ineedroot69:
https://www.reddit.com/r/LineageOS/comments/hynl52
[Magisk] booneb50:
Update: I flashed the original boot.img file to my table to remove Magisk. I uninstalled the Manager app. I verified there were no other Manager apps listed in the app drawer. My tablet is no longer Rooted.

I followed the installation guide, installed Magisk v22, rebooted after installation. I ran the Manager it shows v22 installed, Magisk shows NA, Ramdisk = Yes. I selected Magisk Install, Preserve force encryption is checked, Preserve AVB 2.0/dm-verity is unchecked, selected Next, Select and patch a File is the only option. Selected my boot.img file.

The process failed with the following message:

Device platform: x86_64

Installing: 22.0 (22000)

Copying image to cache

Boot image is signed with AVB 1.0

Installation failed

I tried this several times with v22 but each attempt has failed. Previous versions of Magisk have worked fine on this tablet.
[Magisk] 0purple:
> Preserve AVB 2.0/dm-verity is unchecked

> Boot image is signed with AVB 1.0

I don't think I need to explain
[Magisk] PYCON:
From a couple of months of updates, I cannot find anymore a way to download only the Magisk ZIP file, from Magisk Manager. There's a way to do this nowadays?
[Magisk] zputnyq:
Magisk is no longer as a zip but you can rename its apk extension to zip in order to be able to flash it.

For zip you can stil download it but only limited to some older version before v 21 point something (not including canary & beta before v 21) by adding its .json file address in custom channel. Or you can also download it from github
[Magisk] J.Michael:
How can it be that "... you CANNOT use custom recoveries to install/upgrade Magisk!"? How do you flash the magisk.apk-renamed-to-zip if not with TWRP?
[Magisk] pndwal:
Well, that's the point John is making; You WON'T be able to use zip Installation method (ie. flash using custom recovery) AT ALL in this case.

You CAN patch TWRP recovery image with Magisk using Magisk app (Recovery mode selected), then flash using fastboot (as prescribed), and be able to use SOME TWRP features on type III devices. (Will work on other devices too, but why would you?)

However, you CANNOT Install or update Magisk in recovery partition boot image (not to be confused with boot.img in boot partition) via zip inslaller as installer scripts will only patch a BOOT boot image, not a recovery boot image.

There is therefore NO way to use zip installer on type III devices where installing or updating Magisk in recovery partition. (Nb. It CAN however be used on SOME type III devices - Xiaomi etc - where Magisk can still be installed to boot partition and booted.)

This is the same whether you install Magisk in stock recovery OR custom recovery boot image in any case. (Ie. you can't even fastboot boot TWRP and use zip to install or update Magisk in stock recovery.) You will always need patch/flash or direct install from app to install/update Magisk:

Nb. Re. 'It will be aware of your device state': Recovery mode is automatically selected in Magisk app where Ramdisk = no, so app will then patch recovery (boot) image properly since boot ramdisk and recovery ramdisk configurations differ. Interestingly, where user de-selects Recovery mode, app subsequently remembers this also and thereafter assumes a boot ramdisk configuration when patching. PW
[Magisk] pndwal:
Actually, this has now been reported / seems to be a know issue on x86 platforms:

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

This is being addressed, and seems to be a recent regression. Colaborator here indicates it 'may' be fixed w/ this pull request (14h ago) when merged (in next Canary):

https://github.com/topjohnwu/Magisk/pull/4142 😋 PW
[Magisk] pndwal:
Well, yes with caveat(s). This was the short answer. If its still as clear as mud, please see long answer above:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84772755 😬 👍 PW
[Magisk] pojhe:
Hi all. Currently I use pixel experience plus android 10 last version on my pocophone. I install magisk v22 and hide all banking app in magisk hide. Everything is working fine, banking app not detecting root until I install magisk module (bens thermal module), banking app started detect root even magiskhide still enable. Any help please?
[Magisk] pndwal:
Perhaps that broke SafetyNet. Do you have full SafetyNet pass in Magisk app (Check SafetyNet) as well as Play Protect "Device is Certified" in PlayStore Settings? PW
[Magisk] Drake008:
How to use Magisk?

It is installed and what now?
[Magisk] Philnicolls89:
Magisk is simply a method to root your phone. Once it's installed correctly you don't need to 'do' anything, your phone should be successfully rooted.

Or do you mean that you have downloaded and installed the apk and now want to know how to root your phone? If that's the case then it varies from device to device so we will need more info.
[Magisk] Drake008:
The phone (Galaxy S4) is rooted via MAgisk. The problem is that my Bankingapp tells me the device is rooted. I thought Magisk hides itself.
[Magisk] Didgeridoohan:
If you enable MagiskHide, repackage the app with a random name and add the banking app to the Hide list it might not detect Magisk any longer.

More:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Drake008:
I dont have a Hide list only the magisk hide option in the settings is there
[Magisk] Didgeridoohan:
Bottom navigation bar - the shield, then "MagiskHide".
[Magisk] ahb83:
Why is the download zip option removed when upgrading magisk thru the app? I always downloaded the latest before updating my rom me flashed it right after.

Now, i have to update rom, install older rev or magisk zip, boot, update magisk, and reboot.

Something simple is made tedious now. Where can I download the latest zips?
[Magisk] Homeboy76:
I think you can rename the apk to zip and flash it. Take a look at Custom Recovery in this thread.
[Magisk] ahb83:
Right, but the apk file is still older compared to the canary updates
[Magisk] ineedroot69:
you are confuse ... magisk is composed of 2 component the Magisk App(the apk)(previously known as Magisk Manager)and when installing update from canary server only Magisk is updated the Magisk App remain the same
[Magisk] martyfender:
Yes, that link does not work, but if you read, or keep up on topjohn's documentation, it tells you this. I am amazed at the number of people who try to use Magisk without even reading one section of the documentation? wtf?
[Magisk] Homeboy76:
Yup! Fixed the link to the thread.
[Magisk] pndwal:
"You don't say much friend, but when you do it's to the point, and I salute you for it."

Big Dan Teague (Bible salesman)

O Brother, Where Art Thou?

And here's a blatant misquote:

'John helps those who help themselves'. 🙄 PW
[Magisk] pndwal:
Just out of curiosity, what device do you want to try this on? And have you? ... I'm interested in observations on TWRP functionality. PW
[Magisk] pndwal:
All later Magisk builds are a Stand Alone (no need for internet connection / json files to downgrade), single package solution, both debug (Canary) builds (from 22402):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84354959

and public (Stable/Beta) from 22.0:

https://topjohnwu.github.io/Magisk/releases/22000.html

John's Installation Instructions outline general use, ie Patching Image method using APK package (unnamed) is recommended for modern devices. Zip package installation compatibility is retained for LEGACY support only, ie. custom recovery flashing, both as Installation package (change .apk extension only to .zip), and as uninstaller (rename Magiskxxx.apk to uninstall.zip).

PW
[Magisk] HippoMan:
Some banking apps do extra checks on the device beyond SafetyNet, and they will detect root, even if Magisk is running. For example, my Chase banking app does this.

In my opinion, this is ridiculous. These same banks allow us to access them from our desktop computers, and all desktop computers are rooted. Banks don't require us to limit our desktop computers' capabilities in order to use our computers to access their web sites, simply because there are ways to run any application as "root" (or as "Administrator" in the case of Windows) on our computers.

I don't expect any banks to change their policies about any of this.

Because of this, the way that I get around these banking app restrictions on my Android device is to install a browser on my device and (1) configure it so that it returns a desktop User Agent string; (2) configure it so that it has the bank's web page as its home page; (3) change its icon and displayed app name via my launcher so that it has the same icon as the standard Chase app and a similar name, thereby causing it to appear next to the standard Chase app in my launcher.

If I want to use the Chase banking app for a function that it doesn't support because it detects root on my device, I run that browser-based "Chase" app, log in from there to my bank's web site, and then perform the function that I want to perform.

For example, the Chase Android app will not let us add new Zelle recipients on rooted devices, although it will indeed allow us to send money to existing Zelle recipients. So if I want to add a new Zelle recipient via my Android device, I just go to that extra "Chase" browser on my device, log in, and add that recipient.

I don't know whether this is feasible with all banks whose Android apps detect root, but it's at least worth a try, in my opinion.

PS: Steps 2 and 3, above, aren't necessary. They are just things I did to make the procedure a little easier for myself.