yashsingh1/xdaforums huggingface dataset:
[Magisk] zuelber:
Hi guys. Some guidance needed here. My phone (Mi9 Lite) have received an OTA update, I tried to install and the installation failed. Totally forgot about root/magisk.

Then I´ve followed some instructions to uninstall Magisk restoring images option, tried to apply the OTA and the phone rebooted and after that I am stuck on fastboot. Not sure what to do now.

Please help.
[Magisk] J.Michael:
I don't think you should rename boot.img.lz4 -- if that's what's in the AP.tar, just point Magisk at that to patch image.

I think Magisk can handle lz4. I don't know if it keys off the filename, or can recognize lz4 by the content.

I have a Samsung tablet. I made a new .tar file containing boot.img, recovery.img, and vbmeta.img. I let Magisk patch the mini-AP.tar file to install Magisk in recovery. I don't have TWRP.
[Magisk] Harlock1978:
Hello I updated my P8lite to the latest version of Magisk ap and installer, but now most of my apps start and exit and everytime I turn the phone on I'm asked to install Magisk manager even if it is installed.

What can I do?
[Magisk] tramp20:
You are my last hope :)

Thank you very much.
[Magisk] pndwal:
If you have TWRP you could 'fastboot boot recovery_img' from PC, then run Magisk-uninstaller zip from here:

Releases · topjohnwu/Magisk

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

and reboot to see if full uninstall fixes issues (corrupt ramdisk, etc)

Otherwise, try selecting latest Fastboot MI 9 Lite ROM from here:

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com

and flash using MI Flash Tool w/ 'save user data' selected. PW
[Magisk] zuelber:
Tried several methods and the only one that actually worked was MiTools V2. (using device bricked option)

Fastboot was returning this message: \$fastboot -s .* lock

Not sure what happened
[Magisk] theGeekyLad:
Thankfully my Pixel 2 shows an evaluationType as BASIC only. I'm on it's last EOL security patch with an unlocked bootloader and no root. I stumbled upon a post by someone here who penned that the evaluationType on their Redmi unexpectedly turned from BASIC to HARDWARE_BACKED.

Does it mean that SafetyNet in my Pixel 2 "already" sends keystore certificates but it's just the SafetyNet servers that don't pay heed to it yet hence BASIC type? Or is it that whenever Google intends to bring HARDWARE_BACKED into my Pixel, they'd roll out a covert Play Services update (which would then send the keystore certfs.) that would screw my happiness?
[Magisk] MECH_TECH:
Oh I was looking on his github site installation instructions. I downloaded the zip file and installed it through TWRP and it worked. Thanks
[Magisk] pndwal:
Apparently error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done is normal w/ MI Flash Tool if 'clean all and lock' (bootloader) option is not selected, but ROM is still actually flashed fine according to users.

You seem to be up and running again in any case. 👍 PW
[Magisk] pndwal:
Yes, seems Google frequently play with triggers for their selected devices for Hardware Key Attestation, and some are even exempted after bootloader unlock that were HARDWARE before!

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

Seems Google selection does not rely on any Play Services build; it is REALLY Hardware Key Attestation, and once implemented across the board we don't expect to be able to subvert it - presently it is easy as a simple model prop mismatch causes fallback to basic on any device.

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

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

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

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

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

So Fun's not (quite) over yet... But no knowing how long reprieve will last... PW
[Magisk] pndwal:
Good show... But John does state there:

Samsung (System-as-root)

If your device is NOT launched with Android 9.0 or higher, you are reading the wrong section.

... didn't Galaxy S9 launch w/ 8.0 Oreo? 😉

Must admit, best option choices are not particularly clear there. PW
[Magisk] GuyInDogSuit:
I've tried to root my OnePlus 7T on Android 11 multiple times now, with no success, and I'm at my wit's end here.

The process can either be done through TWRP or through manually patching the boot.img. Neither has worked for me so far.

On Pixel Experience, it straight up crashdumped no matter how I did it.

On YAAP, it booted the patched boot.img, and I was able to flash the Magisk zip successfully. However, once I rebooted, root was gone. Every time afterwards it wouldn't even root at all, regardless of what version of Magisk or TWRP I tried (Magisk 21.1 beta, canary, Chinese TWRP, etc).

Someone suggested trying a different kernel. Got the crashdump there, as well.

I have no clue what to do at this point. While others have run into a similar issue, they have all resolved it somehow, while mine just... fails every time.

UPDATE: Decided to wipe and try again, finally rooted, again, and I hope it sticks after a reboot this time. But currently waiting on the "hiding Magisk Manager," sitting there with a spinning circle, doing nothing, for ten minutes now. Did this the first time I flashed YAAP and rooted it, and I stopped MM, tried again, and it failed, so I rebooted, which led to..... the above, regarding YAAP, all over again. I'm guessing it's not gonna happen this attempt, either.

Someone please tell me what I'm doing wrong....

UPDATE 2: So, like before, I waited, and waited, and waited.... and Magisk Manager never succeeded in hiding itself. I ended up closing the app, and any attempt to launch it or even uninstall it, failed. So I rebooted... and lo and behold, no root, again. So once again, gonna start all over, and fail, again, and again, and again, because I have clearly lost my mind and I don't know any other alternative than to just keep trying.

UPDATE 3: SUCCESS!!!

WOW! I am so glad I thought of this. So, on a whim, before I tried wiping and starting fresh again, I decided to uninstall MM from adb, with the command

adb uninstall com.topjohnwu.magisk

The command returned "success" so I checked my app drawer, and "Manager" was now there, but had an android icon. I launched it, and it asked to install the "full version" as it does when flashing it. It then asked me to manually relaunch the app, and voila! It was not only "hidden" but still had root active and up to date (canary, anyway). I rebooted it, tested SafetyNet, and success!!

Whew. That was an ordeal. And the best part is, this ROM I've been using (YAAP), has not had any crashdumps since I flashed the full thing (it did once or twice when I flashed the extracted YAAP boot.img I patched with MM, though).

Anyway, sorry for the long rant. Hope this helps out anyone else who might have run into this wall.
[Magisk] MECH_TECH:
Yes this phone came with 8.0. Guess i missed that section.

More problems, I put my google account in so I could get all my apps on it but it will not allow me to add my Samsung account i keep getting failed error. I tried both with the email I'd I have and with google option but both fail. Is there something I'm missing? Is this related to Magisk or something else and do i need to post in a different forum?
[Magisk] zgfg:
Updated to the to-be Canary Manager 316 (31x number is now omitted, hence 4766 or 15) and Magisk 21103, all ok (Xiaomi Mi 9T, Xiaomi.eu beta A11)
[Magisk] J.Michael:
Is there web access to a Samsung account? Maybe from a browser you can check access, reset password, get a hint about which e-mail address you used.
[Magisk] pndwal:
Latest Canary Changelogs:

Magisk (b51b884f) (21103)

Unblock signals before executing commands

Fix module installation in recovery

Magisk Manager (b51b884f) (4766)

More minor changes

PW
[Magisk] tazcan:
hello, when trying to hide magisk manager it just hangs it creates an app but if i try t start it just says app is constantly stopping what can ı do to hide magisk manager succesfully, btw i am trying on a MIUI and usb install is enabled, play protect disabled

edit: after i uninstall it via adb and try again it worked
[Magisk] tramp20:
My problems are gone since the last Magisk canary before v21.2 (release notes: Fix module installation in recovery )..

Thank you for your interest :-)
[Magisk] Val81:
Hello,

I'm using magisk since 2016 without problems, but now it's installed but have lost root permissions...

Tried to install it again on twrp but no success 🙁.

I need your help to solve my problem!

Thanks
[Magisk] abhinitagrawal:
Did all steps 4-5 times and with extreme focus but still can't pass SafetyNet
[Magisk] abhinitagrawal:
SafetyNet Check Result

Attestation Failed

basicIntegrity OK

CTSProfile Fail

EvalType BASIC
[Magisk] pndwal:
Is your Android 10 Custom or Stock? PW
[Magisk] abhinitagrawal:
Stock Android 10 with December 1, 2020 Security Patch
[Magisk] Mervingio:
Latest Magisk App update have issues Not found Magisk WTF happened OP7 PRO
[Magisk] pndwal:
Any mods other than Magisk on phone? Any modules? PW
[Magisk] pndwal:
Release Notes:

2020.12.28 Magisk v21.2 (Beta)

- v21.2 is a maintenance update, mostly addressing bugs, and expanding device compatibility. Checkout the full v21.0 release notes if coming from older releases.

Magisk Changelog

v21.2 (Beta)

- [MagiskInit] Detect 2SI after mounting system_root on legacy SAR devices

- [General] Make sure post-fs-data scripts cannot block more than 35 seconds

- [General] Fix the magisk --install-modulecommand

- [General] Trim Windows newline when reading files

-[General] Directly log to file to prevent logcatweirdness

- [MagiskBoot] Fix header dump/load for header v3 images

(6d88d8ad) (21201) (Canary)

- Sync with public release

Magisk Manager Changelog

v8.0.4 (Stable)

- A lot of stability changes and minor bug fixes

- Collect device properties, app logcat, and Magisk logs when saving logs in the logs menu

(6d88d8ad) (4770) (Canary)

- Sync with public release

PW
[Magisk] pndwal:
John Wu, 14h

New update: Magisk v21.2 (beta), along with Magisk Manager v8.0.4!

This should hopefully be the last release for v21. If everything went well, v21.2 will be promoted to the stable channel.

John Wu, 13h

I finally set up an issue template on GitHub stating clear requirements for a valid bug report. If you cannot provide the required info or cannot understand how to do it, don't even bother because I will just close your issue without explanation

This is the only way I can keep sane when reading the issue tracker. If it is still very bad, I'll just shutdown issues altogether. I really only need feedback from developers, or someone that "really" knows what they are doing

John Wu, 4h

Due to popular demand, I had open sourced the stub APK used when hiding Magisk Manager on Android 9.0+. You can now have your own end-to-end setup by using custom channels pointing to your self-built binaries, include hiding the app!

Open source stub APK loader · topjohnwu/Magisk@41a644a

Close #3537

github.com

Please note that I had removed all obfuscation logic that is actually used for building the release stub APK (due to the same concern as why I originally closed source the whole thing). You can of course always come up with your own obfuscation tricks

PW
[Magisk] scottyrick2:
Moto E6 (T-Mobile version/ Magisk in Recovery) upgraded from 20.4 to 21.2 perfectly. First time any 21 series Magisk worked. Thank you!
[Magisk] tramp20:
This command does not work on my Sony Z1c with lineage 17.1 Android 10 and Magisk 21.2:

F:\FastBoot>adb devices

List of devices attached

CB5A1YLE1H device

F:\FastBoot>adb uninstall com.topjohnwu.magisk

Failure [DELETE_FAILED_INTERNAL_ERROR]

F:\FastBoot>

What is the cause?
[Magisk] tramp20:
@ didgeridoohan ,

sorry, the bug has not disappeared:

if I flash the same ROM or an ROM update over my running system then Magisk shows again N/A and root is lost.

The same happens if I make a factory wipe and install the ROM again and then a Magisk version > 20.4.

I could only somehow (luck ?) update Magisk from 20.4 to 21.2 with this Magisk update :-(
[Magisk] Herbie_2005:
Hi!

Using a Samsung Galaxy Note 10.1 (2014) [SM-P605] with Lineage 14.1 (Android 7.1.2), the tablet does not boot anymore with Magisk 21.2 beta, but it does with 21.1 beta. Tried several times from scratch.

Magisk 20.4 is not a problem.

Any ideas?
[Magisk] zgfg:
Better try with:

adb shell pm uninstall -k --user 0 ...

but be aware this 'uninstallation' is not like properly uninstalling the (user) app from Settings/Apps.

You can always reinstall then the same (still existing!!!) app by:

adb shell cmd package install-existing ...

Btw, one of the reasons I prefere to install Magisk Manager apk myself, then patch the image and flash it - instead of flashing the Magisk zip that automatically installs the Manager apk (once I also had problems to remove the Manager app while keeping the Magisk)
[Magisk] tramp20:
On my Z1c (from 2014, factory reset and then flashed Lineage 18.1 and BitGAPPS) I am not able to flash the magisk 21.2 in TWRP:

1. No errors during flashing but neither magisk nor Magisk Manager are installed.

All necessary files are written to /data/adb.

2. After I installed manually the MM I patched the original boot.img from the Lineage zip without errors and flashed it with fastboot to my device with the same result in MM: Magisk N/A :-(

I repeated this many times.

How can I see if the boot.img is really successful patched?

In Lineage 17.1 and AICP 15 (both Android 10) there is the same problem with all Magisk versions > 20.4, but after installing 20.4 I can at least update to 21.2 with the MM.

Magisk 20.4 cannot be installed in Android 11 so this way is closed.
[Magisk] zgfg:
Since you have TWRP, you can take Magisk log (check Magisk Github docs and Wiki) and open an issue at Magisk Github

You can additionally capture a screenshot from Manager when patching and/or screenshot can be also taken in TWRP when flashing the Magisk zip
[Magisk] tramp20:
Thanks, I will do my best if I have the time for this :-)
[Magisk] abhinitagrawal:
Thanks a lot. The latest Magisk update fixed it all
[Magisk] redplate:
Hi, for some reason

- I can't control superuser access or my installed modules anymore.

Usually there are 4 symbols at the bottom.

- Another thing is the missing option "hide Magisk" in the settings.

I'm using the latest Magisk Manger 8.04

Root is still given.

I've attached some screenshots.

Can anyone help me and tell me what's "wrong" here?

Thanks in advance

Edit: updated to latest version 21.2. Still same behavior.
[Magisk] MECH_TECH:
I did web access, logged in to the samsung account and reset the samsung account password using the email that i setup a long time ago with ms S6 phone. I can login with the browser but if i try to add the samsung account on this phone from settings it gets process failed. The camera is not working also. The camera app opens with a black screen for a couple seconds the i get warning camera failed OK.

If i want to start all over again should i remove the samsung account from the phone? then uninstall magisk using the manager? then can i just flash the stock S9 android 9 usinng Odin that i downloaded? and start over.
[Magisk] redplate:
Thx, but that's the problem. There are no symbols or floating icons.

What does this means "swipe down to homescreen"?

I can swipe as much as I want, but there are no icons.

I know how it should look like
[Magisk] Didgeridoohan:
Your screenshot tells you exactly what's going on...

"Installed: N/A"

Most likely either your installation is broken, or you've ended up with two Managers installed somehow (one hidden, one not). Since you say that root still works, I'd go for the second situation.

Solution (if that's the case):

Uninstall the Magisk Manager and use the app named "Manager" (or whatever your named it when hiding), the one with the generic Android icon. If that one also doesn't work, uninstall it as well and install the Manager apk manually (download from the Magisk Github repo).
[Magisk] redplate:
It was the second situiaton. Don't ask me how I did this.

Thanks a bunch! :)
[Magisk] ivivaitylin:
Got a pixel 2 XL (So it has ramdisk), finally decided to update to android 11, and do a spring clean at the same time so grabbed the factory image and ran flash-all.bat . Got it mostly set up, got the magisk manager installed, extracted the boot.img from the factory image zip, plugged that into the manager to get the patched img. installed that through fastboot no problem (it was written to boot_b if that matters), but on rebooting I got a 'device is corrupt' warning and it wouldn't boot. Tried flashing the original boot.img back but this got sent to boot_a and still got the corrupt warning

Not had problems before, though this is the first time I've had to do it this way, last time I had to install magisk from scratch was back when you had to do it through TWRP and there wasn't any need to mess around with your own boot.img. Still, I don't see what I could have done wrong since the instructions are pretty clear, so I'm stumped. About to flash-all and try again from the beginning in case something went wrong along the way, but on the offchance it's something else I figured I'd ask here.

Edit: Nevermind, realised you can still flash the zip through custom recovery, got it working like that.
[Magisk] pendgy:
Since two years ago I have LG V20 H990DS. Oreo stock ROM rooted with Magisk 20.4 and latest Magisk Manager. TWRP also installed. Today I switched to Magisk beta update channel and decided to flash latest Magisk beta 21.2. After reboot the result was crash dump. No way to boot to TWRP. Attempting booting to recovery leads to stock recovery dialog inviting me to reset to factory. No access via adb. The phone can be booted to fastboot mode and the most worrying think is that it shows as US996 instead as H990DS.

Any advice how to solve the problem are much appreciated. Please help!
[Magisk] rackid1:
Hi,

I have trouble with the Magisk installation. I have a Gigaset GS4 phone, of which I unlocked the bootloader, but didn't try to flash a custom recovery. Gigaset does not provide the stock ROM, so I'm a little bit cautious to experiment too much (I'm not experienced).

I was able to extract the boot.img from an OTA update. When I flash the patched boot.img from fastboot, the device gets stuck in a bootloop. I can't grab anything from logcat as it reboots before the adb daemon has started. Flashing the stock boot.img makes the device bootable again. I use the Magisk Manager apk version 8.0.4 and tried both Magisk from the stable (20.4) and beta (21.2) channel.

Spoiler content hidden.

Spoiler content hidden.

Any help is appreciated. Thanks in advance!
[Magisk] redplate:
You might run into the same error as me. It's on this and the previous page.

Problem seems that I can't reinstall the Magisk hide. It seems that it does nothing when switching from on to off for hiding Magisk.
[Magisk] mooms:
Hi,

which version is the latest stable version ?

I can see 21.2 on Github, but the manager only shows 20.4 as the latest :
[Magisk] Lughnasadh:
20.4 is the latest Stable version. 21.2 is the latest Beta version. If you want to use Beta, change your update channel in Magisk Manager to Beta.
[Magisk] zgfg:
Yes, half and more year old v20.4 is still the latest Stable.

You have 21.2 Beta installed, stick with that (if everything is ok for you), specially if you have Android 11 - it is not supported by 20.4
[Magisk] mooms:
Thanks to both of you. It's not clearly stated, at least not on Github.
[Magisk] jenslody:
See the Magisk changelog on github: 21.0 is the first version, that says it has Android 11 support.

Not that easy to find, I know.
[Magisk] mooms:
And where is it stated that it's a beta ? because that was my point.

I'm on Oreo by the way.
[Magisk] Didgeridoohan:
For those kind of announcements, follow @topjohnwu's Twitter.
[Magisk] Homeboy76:
I found that information here:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

Under downloads.
[Magisk] juankar7:
Hello I've installed stable and beta version in Xiaomi Mi with a clean install Android 11 miui eu 20.12 28.

In both cases phone turns into bootloop .

If someone can help me I will appreciate, thanks
[Magisk] zgfg:
You must not use Stable because it's too old, it does not support A11

Extract boot.img from your 20.12.28 zip file

Install Canary (or Beta) Magisk Manager,

make sure you select the appropriate Update Channel (Canary or Beta),

patch the extracted boot.img (if not familiar with patching, please read Magisk Github docs and Wiki),

flash (by Fastboot) your patched boot img

At the end, enable Magisk hide in Manager Settings
[Magisk] rackid1:
Well, not exactly. I don't even manage to get it installed in the first place.

Is there any way to capture logs during the boot process (before adb daemon starts) when the phone is not rooted?
[Magisk] sachaweb:
I did see the navigation bar but since there wasn't much to see in each screen and I couldn't see green check marks I thought something was missing.

Meanwhile I understood from the links you provided that I had to enable MagiskHide in the settings. After that I passed the SafetyNet check. That instruction was missing from the official XDA Magisk page:

How to Install Magisk on your Android Phone

Magisk is a powerful tool that can help you customize some aspects of your phone or even grant you root access. Here's how you can install it!

www.xda-developers.com

Thanks a lot for your help and sorry to respond so late. It's been a long and arduous journey trying to install a custom ROM for (almost) the first time, but I have a fully functioning unofficial LineageOS 16 on my phone now, and I can stop cursing the gods for my fate.

I'm still a bit worried about having an unlocked bootloader. How can I minimize the risks associated with that, aside from not letting geeky thieves take hold of my device?
[Magisk] zgfg:
On most devices (for most manufacturers), relocking Bootloader triggers hard reset, that would either wipe Magisk (and your custom ROM) or even worse, (soft) brick your device (if you don't reflash original images beforehand) - consult the forum for your device

In short, unlocked Bootloader (and its warning while booting) is the price you have to pay. Who doesn't like, did not need to unlock at the first place 😷
[Magisk] Didgeridoohan:
Unfortunately that article is seriously outdated and should probably not be used by anyone... All the official and up-to-date instructions are found on the Magisk Github repo:

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Magisk] HippoMan:
Yes, and in any case, the main purpose for locking the bootloader is to prevent the use of custom ROMs and custom modules. You can't have it both ways in most (all?) cases: you either have custom ROM/modules or you have a locked bootloader with a pristine, factory-level ROM.

This bootloader locking is not all that useful for preventing hacking. Its main purpose is to lock you into standard, non-custom software. If you have a problem with your device and you go back to the manufacturer, they will probably not fix it if they see that the bootloader is unlocked, because that means you are likely to not be using their standardized software, and they don't take responsibility for anyone else's OS or modules.
[Magisk] biglo:
Can someone tell me how to disable magisk logging please?
[Magisk] Homeboy76:
True the article is outdated with the exception of the download section.