yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
Interestingly, new Canary 22004 build has been out for some 22 hours now, and includes logfile writer update to fix 'deadlock and crashes'.

However, files (incl changelog/release notes) have not yet been hosted in magisk_files Canary branch... Normally they are immediately available. PW
[Magisk] pndwal:
Re Bug reports:

PW
[Magisk] Didgeridoohan:
That's because the files have now moved to the magisk-files repo. To get the 22004 update you need to be on 22003 (or download the 22004 apk manually), since any earlier app will look for updates in the magisk_files repo. John is doing some restructuring...
[Magisk] pndwal:
Thanks, I'd completely missed the new repo! 😑 PW
[Magisk] pndwal:
So it's late, but here's the new Changelog and release notes:

Magisk (43c1105d) (22004)

- Rewrite logfile writer from scratch, should resolve any crashes and deadlock

Diffs to v22.0

- [App] Prevent multiple installation sessions running in parallel

- [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images

- [General] Proper cgroup migration implementation

- [General] Rewrite log writer from scratch, should resolve any crashes and deadlock

- [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images

Working fine on my RN8T. 👍 PW
[Magisk] boxemall:
TY very much dear Sir!

i fllowed your advice by:

- extract boot.img from rom

- patched the boot.img from within the app with recovery option ticked off

- rebooted into fastboot ab flashed the patched boot.img

- rebooted into OS/ROM

since i already had some apps installed that need root, i was greeted with the "allow root" popup and immediately knew that all things worked out.

if there will be an update, will i have to rerun the whole process? i can't imagine magisk will update over the app, or will it?

one more question: magisk shows as installed but ramdiks is still "NO". i was a bit confused since you wrote " boot to fastboot and flash patchedboot.img (as for ramdisk= yes) " in your post. i'll leave it as is, as everything seems to be working. nevertheless a confirmation from your side would be nice, if you get some free time.

tx again!

regards
[Magisk] pndwal:
Not sure what you mean by 'over the app', but if you mean OTA update, you generally need to unroot to take it, then use this initial setup process again to restore root.

If you mean Magisk Update, generally you will only need to do direct Update from Magisk App (as you already have root permission; and never select 'recovery' option) and this should be seamless; all settings, modules and functions should be preserved.

Yes, flash patchedboot.img to boot partition as if ramdisk= yes.

Nb. ramdisk = no

won't change

despite Magisk having actually added basic ramdisk to boot image as I explained in posts I linked. - it is actually reporting that boot image has no FACTORY ramdisk, because only that is a reliable indication that Magisk in boot partition will work.

Devices with factory boot ramdisk will necessarily support Magisk in boot as they will have necessary bootloader support, but despite Magisk-added ramdisk, other devices (lacking factory ramdisk) usually lack bootloader support and won't work. So, since there is no means for Magisk to determine bootloader ramdisk compatibility, it is assumed it is lacking as it is not needed for OEM configuration, and so ramdisk = no remains (as John Wu clarified) because any indication other than factory configuration would be unreliable.

In our case, Xiaomi breaks the mould and has (inexplicably) left legacy ramdisk support in bootloader in 'type 3' devices despite not using it, so Magisk (manually) added ramdisk can actually work. Still, the only practical way to know if it will is to try it.

Hope it helps, PW
[Magisk] Homeboy76:
Please, post the link to download it manually.
[Magisk] Homeboy76:
Please, post the link to the new Changelog and release notes.

<edit>

Nevermind, @pndwal posted it.
[Magisk] pndwal:
Files all here:

https://github.com/topjohnwu/magisk-files/find/canary 🤠 PW
[Magisk] HungLu:
I try to flash Magisk 16.4 and other version, I got Error 1. No root. My Galaxy Tab A 10.1 SM-T580 running Android 8.1. TWRP can flash SuperSU 2.82 OK. Device is rooted but some app like Titanium Backup doesn't see root status.
[Magisk] ineedroot69:
SuperSU is obsolete the latest and last version is released back in 2016 also the SuperSU you can download from Google are provably malware infected ... Just use the Magisk built-in SuperSu
[Magisk] Lord Sithek:
Why Magisk 16?? It's so old know (actually the first Magisk version I ever flashed 😅)
[Magisk] ineedroot69:
i remember flashing SuperSu on my Samsung Galaxy Y back in my high school days 2000 era anime are the best 🙃
[Magisk] Didgeridoohan:
"Error 1" could mean anything. To know what's actually wrong you would need to post the recovery log.

Since you're messing with SuperSU as well, my first guess would be this:

https://www.didgeridoohan.com/magisk/Magisk#hn_Boot_image_patched_by_other_programs
[Magisk] HungLu:
What is the latest version of Magisk? Is zip file to be flash with TWRP? I saw there is Magisk v22.apk but I installed it didn't work. Thank you
[Magisk] HungLu:
How can I get the recovery log from TWRP? Thank you
[Magisk] Lord Sithek:
Release Magisk v22.0 · topjohnwu/Magisk (github.com)

Basically, you can rename the extension .apk to .zip and flash in TWRP. Like magic ;)
[Magisk] Didgeridoohan:
That's why I made the words "recovery log" in my post into a link that points to instructions on how to get that...
[Magisk] HungLu:
I did and it's installed no error. Now I bring Magisk app but so far no root yet. What I have to do next. Thank you.
[Magisk] Homeboy76:
Virus scanner, intermittently, detecting Magisk Canary: app-debug.apk and stub-release.apk as Malware. Anyone else seeing this?
[Magisk] HungLu:
I got it. Thank you
[Magisk] Didgeridoohan:
That's been reported from time to time and are always false positives, of course (as long as you use the official app).

Latest one I've seen reported (before this) is the hidden app being reported as a PUA, reason: downloader. Which is a bit funny, because that's the sole purpose of the hidden app, to download the main apk. So not really a false positive, but not malicious either...
[Magisk] Didgeridoohan:
Instead of making these small posts with single questions, that quickly will fill up the thread, take a close look at the official installation instructions:

https://topjohnwu.github.io/Magisk/install.html

If you've still got problems after that my troubleshooting guide have some tips that might help (you've already seen the page on how to ask for help):

https://www.didgeridoohan.com/magisk/HomePage

If you still have questions after all that, try to make them as detailed as possible so that it will be easier to answer and possibly give some help.
[Magisk] samhhmobil:
I expect, this fault is due to the new "scoped storage policy" forced by Google for Android-11.

Your possible workaround is to use LOS-17.1 (Android-10) instead. It's the latest Android, where you can handle your storage free as you want. With Android-11 it seems to be impossible.

samhhmobil

PS...

The alternative solution may be to format your external SDcard as "adoptable storage". With all restrictions. LOS 18.1 supports "adoptable storage":

Settings ==> Storage ==> "yourSDcard" ==> 'the three dots top right" ==> Storage Settings ==> Format as internal.

And after that, move your content to the adoptable storage. It works.

Other way... you can format only a part of your SDcard as "adoptable storage", when using "Root Essentials", the other part may be formatted as "external storage", i.e. exFat-Filesystem.
[Magisk] HungLu:
I have to downsize to Magisk v21.4 and Magisk Manager v8.0.7 to make it work. Now my device got rooted. Thank you for your help.
[Magisk] boxemall:
awesome explanation! now even i understand. lol

sry if i bothered you but some things go deeper under the hood than I'm used to. but this bit of information made me feel more comfortable. it's always nice to know about all the intel we get once you know how to look at it.

tx again and have a great week ahead!

regards
[Magisk] seanbaggey:
Nothing? Anyone? Specifically, the message I get when opening Magisk Manager is "Abnormal State - Running this app as a system app is not supported. Please revert the app to a user app."

I have no idea how it became a system app. I've successfully used magisk manager countless times on other devices and roms but this is the first time it somehow became a system app in the process and I don't know how to reverse it.
[Magisk] pndwal:
Yes, strange unless you systemised (/ systemized) it using an app designed for this or your ROM includes Magisk root. (Here's a Magisk module that does it too: https://xdaforums.com/t/module-terminal-app-systemizer-v17-3-1.3585851/ ).

If you're sure rom doesn't include root or Magisk app/manager, simply dirty flashing ROM should remove Magisk app (I recommend this approach as it should also fix/remove any OTHER /system mods you may have), or using Apps2SD's Systemiser utility (or other) will allow you to convert System apps to user apps (and vice versa).

I've used Apps2SD utility to merge system app updates (these are in /data) into /system in the past; of course, these are NOT systemless changes (and Magisk Installation as system app is no longer a systemless solution) and may cause problems with OTA updates etc. PW
[Magisk] Didgeridoohan:
The app doesn't just become a system app all by itself (and Magisk has no built-in feature to do this, neither from the app or the installer zip). The message you are seeing is shown if the Magisk app detects that it is installed to the device's system image, using a regular Android function to check this: https://developer.android.com/reference/android/content/pm/ApplicationInfo#FLAG_SYSTEM

If it's installed to /system you have to remove it from there manually (can be done through a root enabled file explorer, or in TWRP), or via an app that can do it for you (also root).
[Magisk] seanbaggey:
Only thing I can think of is possibly during the initial rom install, I may have flashed things out of order and "forgot" I already flashed magisk, and then flashing it again (the rom clean install instructions recommend several twrp reboots and a couple /data wipes).

In any event, as things currently stand, because of my failed attempt to uninstall by using the magisk app itself, along with flashing the apk (uninstall.zip) in twrp, my device is no longer rooted, which means I can't use one of the many root-required apps that change user apps to system apps and vice versa. Yet magisk manager still remains as a system app.

From this point, with a magisk manager that's a system app, but not rooted, what's the best way to proceed from here? Reroot (and if so, how) and try and remove it manually from /system? Or will a dirty flash of the ROM itself be the right first step?

WOrst case scenario, I can try a clean flash from the beginning with a /data wipe (press yes to continue) but I'm afraid I might accidentally repeat the same install steps that got me here in the first place.

Thanks for the help!

Edit: fixed xda link typo
[Magisk] dope77:
i've had a lot of issues with the magisk 22003,

but after uupgrading to 22004 the problems seems to be fixed, HOWEVER the manager is not working anymore,

as you can see in the images below, it's showing that magisk isn't installed (magisk is installed and modules are working properly)

and i can't access anything from the manager
[Magisk] DualJoe:
That's ok. I've copied /data/media/* to ext.sdcard. Logical view is the same in the end.

My ext.sdcard is formatted as ext4. 'vold' cannot handle that and gives up about ext.sdcard so '/mnt/media_rw' remains unused. But yes, probably not the best place. Leftover from fusefs times. I have several scripts expecting this folder and i'm too lazy to fix them atm.

I've had first success by changing some things. Modules and bind mounts are working now. I still need to pin that down exactly but its probably due to some other tmpfs overmounts in /data/data. Edit: No, gone again with the stable version... then its probably the Magisk canary build..

Edit2: I cannot replicate it again at all. Not sure what's going here. Maybe a race condition.

Thanks!
[Magisk] J.Michael:
Check whether you have more than one copy of Manager installed. Uninstall all of them. Maybe reboot before installing new copy of Manager.
[Magisk] Didgeridoohan:
There's an open Github issue about this:

https://github.com/topjohnwu/Magisk/issues/4005
[Magisk] pndwal:
You likely just need to remove BOTH newly installed Magisk app and any hidden Magisk app (seems you have) that are conflicting, then reinstall app. 👍 PW

Edit: If it's not hidden Manager conflict, there's likely a new bug/issue as mentioned above. 👍
[Magisk] pndwal:
I'd just dirty flash ROM again. You may need to setup Magisk (root) again if it doesn't survive this, but systemised Magisk app should be gone.

Just be aware this will also remove any other mods to system, but if all you mods are systemless they will be preserved unless you run Magisk 'Uninstall Magisk' option or uninstall.zip. PW
[Magisk] seanbaggey:
I just realized my xda link in my last post was bad and fixed now (just case you tried clicking for more info) but had I posted the link correctly the first time around you probably would've figured out the only "mods" I care about are flashing (1) RMM v3 bypass, and (2) dmverity & encryption patch. Both of those would be flashed right after flashing magisk.

I assume that doesn't change your analysis and I should be headed straight away to the dirty flash, correct?
[Magisk] pndwal:
If you have the system mods (zips) you need, try it (don't wipe data) then reflash those mods too... If it doesn't work for you, change Magisk system app to user app (or remove it) using Apps2SD or other... PW
[Magisk] dope77:
nope, i didn't hide magisk manager,

simply this happened after flashing 22004 and rebooting
[Magisk] Homeboy76:
@J.Michael

@HippoMan

This is the reason you

do not

use fastboot boot lineage17.1recovery...img on a

1st generation Pixel/Pixel XL

:

C:\android-sdk_windows\platform-tools_r31.0.0-windows>fastboot boot lineage-17.1-20210310-recovery-marlin.img

Sending 'boot.img' (31945 KB) OKAY [ 0.763s]

Booting

FAILED (remote: 'dtb not found')

fastboot: error: Command failed
[Magisk] pndwal:
Yep... But now I'm wondering if it does actually work w/ TWRP as indicated officially for marlin:

https://twrp.me/google/googlepixelxl.html

Or is this actually untested by @bigbiff or others?... Or is Lineage Recovery simply unique in this regard? PW

[Wow! We now have Search this Thread in XDA App! ... Shame it DOESN'T WORK. ☹️

... and new look update seems to have broken the working search function in browser view too, so for now we have NO working search on XDA. 😬 ]
[Magisk] zputnyq:
Del, it has been reported on github
[Magisk] andrea0807:
Why is there no longer the option in magisk manager to download only the zip file?
[Magisk] andrea0807:
Duplicate post
[Magisk] m0han:
'cos you can rename the .apk to .zip and thus get the zip file, i suppose. more here under 'custom recovery' section.
[Magisk] BrickL0rd:
my one+ 8t a11 completely locks down with latest magisk and using/toggling Magiskhide. can pass safetynet but no hiding from sensitive apps
[Magisk] dope77:
can you post the link for magisk 22003?
[Magisk] pndwal:
22004:

https://github.com/topjohnwu/magisk-files/find/bbb988177b606f6de1c4c8938b2f2a272535c63a

22003:

https://github.com/topjohnwu/magisk-files/find/9024bb13f92d3cec739e61e34b32b182721b02d8

Don't know what's going on with XDA. Edited last Post, and it duplicated it!...

Edit: Mod deleted duplicate; thanks.

PW
[Magisk] J.Michael:
What means "locks down"? Is that good for you?
[Magisk] HippoMan:
This XDA site has been particularly flaky for the past day.
[Magisk] BrickL0rd:
like apps don't open anymore, only rebooting helps. sometimes loss of mobilenetworking too.

oneh 8t android 11, latest firmware
[Magisk] DiamondJohn:
A little OT, but XDA hacve donw and upgrade and any bugs / flakey behaviour should be reported at https://xdaforums.com/t/xenforo-2-2-upgrade-post-bugs-issues-and-comments-here.4245677/

I know this because I just tried to search for my own posts on this thread (to find a specific response to a question), and it returned nothing.
[Magisk] RobbieRobski:
How does think or swim know that my device is rooted if I use magisk hide? I don't have any limitations using the app, I'm just wondering.
[Magisk] MattP410:
Anybody else having trouble hiding root from various apps since the latest version? Anything Amazon, Adobe and PayPal, as well as a few more won't work for me. I can reboot and log into most of them quickly after boot and use most of them, but some still won't work. I use Magiskhide for each individual one, and it worked on one device for about a week and then nothing again. It's kind of mind boggling that it would work for a while and then stop with the same Magisk version. Just wondering if I'm the only one, and if anybody has any suggestions. Thanks in advance for any replies!

Edit: By latest, I mean 22000. I'm reading that some have up to 22004. Is my manager not updating properly?
[Magisk] ineedroot69:
you have Xposed installed? you need to hide that too
[Magisk] ineedroot69:
change your update channel to canary to receive update 22004 in advance
[Magisk] MattP410:
I'll try this. Thank you for replying.
[Magisk] nowster:
Just a note of thanks. 22004 (with the change to logging) seems to be nice and stable. 76 hours uptime so far on Pixel3a using MVK kernel. It's been a long time since the phone's been running without reboot for long enough that it asked for a password instead of a fingerprint.
[Magisk] tramp20:
Hi.

all canaries until 22.003 were published at

GitHub - topjohnwu/magisk_files at canary

(Deprecated) Magisk File Host. Contribute to topjohnwu/magisk_files development by creating an account on GitHub.

github.com

since 22.004 here

GitHub - topjohnwu/magisk-files at canary

Magisk File Host. Contribute to topjohnwu/magisk-files development by creating an account on GitHub.

github.com

Does someone know why?
[Magisk] briandmiller:
Android 11 Galaxy Watch and Samsung Health

I just flashed my S20 with Android 11 Stock ROM and Magisk. I have everything working except the Wear connection to my Galaxy Watch3 and Samsung Health. I have MagiskHide Props Config v5.4.0-v122 and Universal SafetyNet Fix v1.1.1 modules installed. Does anyone have any suggestions for these 2 app? Also -I don't seem to be getting root access for any apps and not able to edit theProps Config
[Magisk] Didgeridoohan:
Because John is doing some spring cleaning.
[Magisk] Didgeridoohan:
I don't do Samsung, but doesn't Samsung Health rely on Knox, and as such it'll trigger as soon as you've modified your device?

Can't say anything about the watch, but maybe some of the apps that are used for the connection also use Knox or need to be on the Hide list...

I'm just guessing here though. I'm sure someone who actually knows what they're talking about will come along shortly.

Of course, you could also look through (use search) your devices' forums to see if there's any info there. I'm sure you're not the first to experience this...
[Magisk] Buzzcola3:
hey, for some reason magisk app does not give it self root after installation. is there a way to manually grant it the permission with adb or something ?

its like chicken and egg, i cant grant root to it without it having root :)

*same even if I use stable version
[Magisk] ineedroot69:
That is really strange since Magisk doesn't list itself on permitted app with superuser right ... Are you using rootallmtk exploit by diplomatic?
[Magisk] Didgeridoohan:
Take a look if this applies:

https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_app_was_denied_superuser_access
[Magisk] briandmiller:
I am very pleased to report that I got this all working. Started over making sure that I properly flashed the v11 stock rom and then flashed magisk and then followed the threads on using the patched S Health app and the Galaxy Watch bluetooth fix. Thanks to all of the contributors to these solutions. My advice to anyone in this situation is to not give up and don't overlook the possibility that you did something wrong in the process.
[Magisk] clambert11:
Anyone else having problems with the latest version of Company Portal? Seems like it's able to detect root now, even though it's hidden. I'm running Beta version 22.0 of Magisk.

In the meantime I've rolled back to the old version of Company Portal.
[Magisk] Buzzcola3:
thanks
[Magisk] mcdoe123:
@topjohnwu

are the complete snet reflective dex files sdownloaded to /data/data/com.topjohnwu.magisk/snet/oat?

I see this happening in line 99 here https://github.com/topjohnwu/Magisk...wu/magisk/ui/safetynet/CheckSafetyNetEvent.kt

If not how to snag and decompile the full snet.dex?
[Magisk] EliteChickenDev:
Two different devices, and questions for each:

1) Shield tv (2017)

Recently upgraded my shield tv (2017) to 8.2.2 (Android 9) from 8.0 using the dev image. After that I installed Magisk 22, patched the boot.img (even thought magisk reports no ramdisk), and everything seems to work except for an abnormal state message I receive when entering the app:

"An 'su' command that does not belong to magisk is detected. Please remove the other unsupported su."

Is this because the dev image from Nvidia is prerooted? Only have two apps that require superuser, and they've had no issues requesting it. Seems it may be a non issue however could there be an issue later on?

2) Umidigi S3 Pro (Came with Android 9, will not be getting 10 or 11 from Umidigi)

Without reading the message for v22, I unfortunately bricked my phone but was able to restore it. Took the opportunity to install ph's AOSP 11 GSI while installing TWRP 3.5.0 for my device (aubrey) however I could not seem to get magisk 22 to work. I've read a bit that Android 10 changed things, and I understood that it made it harder to root compared to Android 9. I've also read the installation instructions, even though there's no ramdisk, past versions of magisk I simply patched the boot.img with success, unfortunately this time round it didn't work. Tried patching the stock recovery, as well as twrp, both didn't work.

Is the reason the above two methods didn't work is that I'm patching a boot.img, and recovery.img that are meant for Android 9 instead of 11? If that's so, would that mean I need to go back to Android 9 if I want to use Magisk? Are there other root options for android 11 at the moment?
[Magisk] J.Michael:
ARE you patching Android 9 boot.img trying to install Magisk in Android 11?

From other posts, I think you should not try to install TWRP with Android 11. You can run TWRP with "fastboot boot TWRP.img" when you need it, but do not install it.
[Magisk] parisien99:
Hello

I need last version of the apk of magisk.

Where do i have to click on this page to get it?

Release Magisk v22.0 · topjohnwu/Magisk

RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN! Another major Magisk release! This time our focus is not the core Magisk implementation, but rather on improving the w...

github.com

Maybe i am stupid but i don't find.

Thank you
[Magisk] Xentiran:
Is it possible that there is an automatic backup generated or does it have to be done manually in TWRP?

Cause my Samsung 8 is stuck in the bootloop of "Downloading..." after the update was initiated and it rebooted the phone.

I would like to go back to my 21.4 version of Magisk and run that, but i've not been smart enough to do a manual backup before with a working version...

So do I have to start over from the beginning and is now doomed to run the seemingly unstable 22 Magisk or do I have a little chance to recover what it was before?

Edit: I forgot to mention that TWRP now complains that .zip files are an unsupported image to load, so I cant run the Magisk uninstaller.

I've found a magisk backup under /data. Im not sure if that does anything? It says "boot.img.gz"

I guess its worth to mention that I had SmaliPatcherModule installed aswell, it was installed via fastboot. So maybe that caused the issue?