yashsingh1/xdaforums huggingface dataset:
[Magisk] DiamondJohn:
My experience has been that the UNlocking of the bootloader wipes / hard resets, but locking does not. And that makes sense. If you find/steal a phone, yuo would UNlock to get at the data. Locking the bootloader does not help nefarious access to your personal data.
[Magisk] zgfg:
It heavily depends on the phone/manufacturer.

I did relocking two phones.and I was warned, and indeed relocking triggered hard reset just like unlocking.

For Huawei phones (when I had, up to Oreo) I know for many users bricked them if they didn't remove TWRP (recovery partition) and Magisk (ramdisk) before going to relock, because of hard-resetting triggered by relocking Bootloader failing at half of the job when it did not find stock recovery and ramdisk

Why did yoy cut my original post - I clearly commented/recommended the guy to consult forum for his phone, since such policies, proceedres, consequences/troubles depend on the phone/manufacturer

Hence I warned the guy about possible consequences.

If you want to be responsible if he bricks his phone when attempting to relock Bootloader while keeping custom ROM, Magisk, etc - then please help him to recover

In that case, problem is that Bootloader would already be re-locked, hence he could not easily flash something to fix the brick (only Test point methods may work).

And if the phone is still under guarantee, official services usualy refuse to fix such bricks, hence it could cause a significant cost to get help from somebody with an authorized EDL account or so, needed to proceed with the Test point (even if it doesn't need like an authorized EDL account, just opening the phone and short-cutting Test-point pins on the motherboard is beyound the expertize for most of Magisk and custom ROM users).

Possible more troubles: to find drivers needed for low-level flashing for Test point methods (needed tools could be sometimes downloaded only from siites requiring paid subscriptions), some tools may work only with old Windows versions or even from Linux, etc
[Magisk] flroots:
Magisk newbie here. I've installed Magisk and obtained root without issues. However, when I run Check SafetyNet, I get the result shown in the screenshot. Did I do something wrong and if so, what are the consequences? Is there a way to fix it?
[Magisk] zgfg:
Enable Magisk hide in Manager's settings
[Magisk] dongvatm:
Hello everyone. I want to use the banking app on a rooted device. Is there any way to not be detected as root?
[Magisk] zgfg:
Magisk Wiki on Github, the whole chapter about
[Magisk] pndwal:
Well you haven't given much away, but seems you've installed Magisk correctly, nothing wrong.

Consequences of failed ctsProfile is same as for uncertified (Chinese etc) ROMs, simply Playstore Settings will say Device is not certified, and some apps like Netflix, banking apps etc, will not show in Playstore or run.

To fix may be as simple as toggling on MagiskHide in Magisk Manager Settings, or, if you've done this, spoofing a certified device by setting a certified device fingerprint in props. This assumes you are using an uncertified (Chinese etc) stock ROM, or a custom ROM which doesn't use device fingerprint spoofing such as official LOS builds. Method: flash MagiskHide Props Config Magisk module, install a Terminal Emulator and follow MagiskHide Props Config setup instructions to configure a certified fingerprint, and reboot.

If you are using a certified stock ROM, you have another issue; please give more details about your device setup. 👍 PW
[Magisk] pndwal:
If you're lucky, it will work simply by toggling hide root from that App in MagiskHide list (and, of course, toggling on MagiskHide in Magisk Manager Settings), then clearing the bank app's data and rebooting.

My bank app works out-of-the-box this way, but many (that don't simply rely on SafetyNet attestation because it's clearly unreliable) don't because they employ their own custom root / custom mod detection method(s). In this event the Wiki will be your best bet to circumvent these measures. PW
[Magisk] flroots:
Thanks for the comprehensive response. Yes, I am running the latest stock ROM (QPR30.80-58-8-3) for my XT2043-4 phone.
[Magisk] dongvatm:
Oh Thank you so much.

I tried to try using magisk hide but it doesn't work. I will try the wiki.
[Magisk] mooms:
Thanks, but I don't use Twitter.

Indeed, its stated here.
[Magisk] svendsvin:
After updating manager to 8.04 all my installed mods are also visible in the Online section aka not installed. Everything is working it seems, but it's kind of strange.

I'm on Magisk 20.4. Xiaomi Redmi Note 7 stock rom.
[Magisk] zgfg:
Installed section lists installed mods. Online all mods available online (installed or not). In case of available updates there will be third section on top.

That's how it works (you may need to get accustomed)
[Magisk] dope77:
My device fails safetynet and it's not certified and i can use and install everything without problems (Netflix, Disney+, banking apps...)
[Magisk] pkgnex:
I was about to flash the January factory image for my Pixel 4xl but when I took the boot image and patched it in magisk, instead of outputting magisk_patched.img it outputs magisk_patched_xyZSH.img or something. Is this expected with the latest version? I've never seen it before.

Thanks.
[Magisk] martyfender:
Yes, which effectively produces backups, as the previously patched version is not overwritten. In the past, I was manually renaming my last patched version as a backup if a new build had problems.
[Magisk] zgfg:
Random suffix for the patched image names is a useful feature (previously every new patch overwrote the previous one in Download folder if you didn't rename that older file yourself), and it's been already commented earlier:
[Magisk] nowster:
Heads up that Jan 2021 security update has updates which cause both basicIntegrity and ctsProfile fails, showing evalType HARDWARE.

This is a Pixel 3a with a Magisk 21201 with MagiskHide enabled and Manager (hidden) 15 using the stock image (RQ1A.210105.002).
[Magisk] Slim2none4u:
I'm still passing on my Pixel 3xl
[Magisk] nowster:
I've just reflashed Magisk, and it's still failing all SafetyNet checks. I think it's because evalType is now HARDWARE.
[Magisk] kadyt:
I bootlooped two phones trying to uninstall Magisk from Magisk Manager. Either uninstalling Magisk from Magisk manager is broken (lol), or, there must be something that I have done in the two phones, that now I can't simply uninstall from Magisk Manager but I have to do "something more". And I can't imagine what it was that is causing the problem or what should I do to fix it. Maybe someone can give me a clue on what could be causing these issues

- LG G7 Thinq with Android 10. My intention was to take an OTA so I first tried selecting to restore the stock boot only. It seems to be done OK but no, reboot and bootloop.

To fix it I rebooted to bootloader and flashed again the patched boot.

Once the phone is on, I try to uninstall Magisk again but now I choose to uninstall Magisk completely and this time it says there does not exist backup stock boot and I can't uninstall it.

After that, I just reboot thinking that I haven't done anything then and Magisk continues installed and, the robot down with the red triangle. The system seems to be down. I had to flash a kdz (then after all was updated I installed Magisk again from scratch).

- Xiaomi Redmi Note 5 with Miui 11 / Android 9. From the previous experience this time I chose uninstall compaletely. Same result, bootloop.

I Fixed it booting to Orangefox recovery from fastboot and installing Magisk from the Orangefox addon. Then the phone booted. After that I dirty flashed the complete OTA from Orangefox

Both where using Magisk 20.4 & Magisk Manager 8.4.

Putting these two scenarios together, does anybody have any idea of what could it be going on?
[Magisk] Slim2none4u:
Instead of uninstalling magisk to take an ota, just flash the stock boot.img in fastbbot. There's no reason to uninstall it.
[Magisk] update.freak:
Why is v20.4 displayed as the current version in Magisk Manager 8.0.4.

I thought it is v21.2?
[Magisk] dcarvil:
v21.2 is the current Beta version.

v20.4 is the current Stable version.
[Magisk] garylawwd:
Latest beta is 21.2

Latest stable is 20.4

You more than likely have update channel set to stable.

Also, quick side note, 20.4 does not work on Android 11, for magisk on a11 use latest beta release
[Magisk] zgfg:
It has been asked the same and snswered yestrrday - guys, please follow discussion before asking

Also, on Magisk Manager you have link to the Magisk Github and there you can check everything (Chabgellgs, links to the latest versions per channels)
[Magisk] zgfg:
There is s problem since Basic Integrity fails for you.

It could fail due to certain modules (Xposed and so)

Once Basic Integrity would be passing, you can simply force Basic CTS eval type (to pass CTS) by the corresponding feature in MHPC

Basic Integrity does not depend on CTS eval type Basic or Hardware
[Magisk] nowster:
The only modules active are ACC, GPay SQLite Fix and Systemless Hosts.

Toggling MagiskHide off, closing Manager, then toggling it on again seems to have fixed Basic.

ctsProfile has been failing for some weeks.

What's MHPC?

EDIT: Magisk Hide Props Config module.
[Magisk] zgfg:
Now, if Basic Integrity is passing and CTS fails with Hardware, use MHPC to force Basic (exactly that option, not fingerprints)
[Magisk] J.Michael:
According to OTA instructions on github, some OTA processes will balk if some partitions have been modified. @kadyt can try it your way, but it might not work.
[Magisk] zgfg:
Magisk patches to Boot (,or Recovery) only, and saves it its settings to Data.

Msgisk will not male any changes to System, Vendor, etc. Systemless Magisk modules also do not affect partitions - they only dynamically mount the changes when Magisk boot

Therefore, there will be no changes to System, Vendor, etc, unless (System is not read only and) user has used some old school root applications that don't follow systemless approach but instead they make hard changes to System, Vendor and so

Putting simply, once you boot with the original (not patched) Boot partition, Magisk will not initialize, hence there will be no changes in System, Vendor, Product, and so on, hence no problem for OTA

Once again, I assume that user should not have used not-systemless root apps, that user did not debloat his System through TWRP, that user did not flash custom ROM or Kernel, or similar

If user did such changes, he/she must restore affected partitions before OTA - but this is not part of Magisk considerations
[Magisk] nowster:
Well, actually it does it by setting a fingerprint of a basic model. My Pixel 3a now thinks that it's a Nexus 5... and passes CTS.
[Magisk] Didgeridoohan:
Nope. It's the model property that's changed, not the fingerprint. And if you want a device model that's closer to yours you can pick one from the list (as long as you pick a device that's different from your own).
[Magisk] zgfg:
Give the exact name of the prop you changed to see is it fingerprint as you said or not:

- go to /data/adb/modules/MagiskHidePropsConf

-open (textual file) system.prop and please copy here its content (props names and values you changed by using MHPC)

Options Force Basic and Device simulation do not mess up with fingerprints.

Only Edit device fingerprint or Edit custom props (if you pick up the fingerprint prop)

And to force Basic eval type you don't need to change device fingerprint:

ro.build.fingerprint

but product model:

ro.product.model

Btw, use also Terminal app and execute:

getprop ro.product.model

getprop ro.build.fingerprint
[Magisk] alc112:
Hello! I'm not able to install Addons because I don't see the 3 lines icons to access those menus.

This is a Samsung S6 Edge (SMG925i)., Tried with 2 different custom ROMS. Everything is updated.

I also get this error when trying to aply smali patcher: !!! ERROR: High volume warning class not found. Beacuase of that I wanted to try the TaiChi method to spoof location and I need to add it via MagisK manager.

Can someone help me, please?
[Magisk] HippoMan:
Scroll down a little bit, and you will see 4 icons at the bottom. When you click on the fourth one (the rightmost one which looks like a puzzle piece), the screen that lets you install modules will show up.

The older version of Magisk Manager had the 3 lines at the upper left. However, the newer version doesn't have that 3-line icon any more, and it uses those icons at the bottom of the screen to navigate to different sections of the app.
[Magisk] Slim2none4u:
Sorry I rushed this little photo edit to put labels on the icons to help. Maybe a good idea for future update? I misspelled superSU but you get the idea.

Home. SuperSU. Logs. Modules.

In that order from left to right.
[Magisk] alc112:
Thanks!

As you can see in the picture I posted, the screen of my phone is damaged and I couldn't see the options. Now I was able to enter the option I needed. Thanks!
[Magisk] J.Michael:
boot and recovery are partitions. If it doesn't matter if they have been modified, why is it necessary to uninstall Magisk? (Or to boot an un-Magisked image, so Magisk is not running when the OTA update is requested.)`
[Magisk] jamesta:
Hi,

Quick question, I just got the Huawei Nova 5T and want to get the Viper4Android FX Module installed, do I need an unlocked bootloader to install Magisk Manager and/or modules?

Thanks,

Jay
[Magisk] Micha_Btz:
Hi,

I use the latest beta 21.2 on AEX rom Android 11 for my Xiaomi MI 9SE grus device

and it worked fine with the standard (private profile).

I have the settings multiuser mode point to each user have it's own rules, but my work profile can't get root access.

I know some permissions have changed in Android 11, is there a way to get it working?

Micha
[Magisk] zgfg:
I didn't say that boot and recovery don't matter - just the opposite. I said that before OTA, you must revert to the original boot and recovery

Please carefully read what I wrote.

It was a long post and I absolutely don't have time to write about all those things once again.

Generally, this is Magisk thread here. Installation of Magisk depends on device and firmware; OTA depends too.

Generally, OTA must be discussed in the context of particular device, and hence on the corresponding device forum

Thrre is another thread on XDA for V4A

However, to install any Magisk module you must first install Magisk.

To be able to install Magisk you must unlock Bootloader

Please first read:

- from its thread about V4A

- from Magisk Github about Magisk installation

- from your device forum about unlocking your device (for Huawei it can be tricky and expensive, depending on your HiSilicon model and EMUI version/Bootloader version, etc).

Btw, it was long ago, I had Huawei P9 and V4A worked excellent on Nougat, but once I upgraded to Oreo, V4A was no more possible to install (it was, but only by flashing the whole modified EMUI ROM with the V4A built-in)

Hence read/ask also about V4A installation (which version, is it possible and how) on your device forum
[Magisk] pndwal:
Perhaps a bit OT, but relevant to Magisk compatibility, and at least a great ending for 2020!:

TWRP 3.5.0 Released

Dec 31, 2020

...AND ITS GOT DYNAMIC/LOGICAL PARTITION SUPPORT!

Many improvements for Android 9, seems we have proper support for Android 10 Launch Version devices (Pixel 4 etc), and an Android 11 branch on GitHub is up (as of 5th Jan) as well! (Pixel 5 coming... sometime 😃 )

New supported Android Version suffix will help avoid compatibility issues too!

Thanks for the tireless support of CaptainThrowback, Mauronofrio, AndroiableDroid, Noah Jacobson, bigbiff, Dees_Troy and a considerable number of others. 👍 @bigbiff, this announcement made my day!

https://twrp.me/site/update/2020/12/31/twrp-3.5.0-released.html#

Well done guys! PW
[Magisk] Slim2none4u:
Could you drop a link to this?

I could seem to find it anywhere.
[Magisk] zgfg:
Yes, using 3.5.0_9 on Xiaomi Mi 9T since Dec 28

It decrypts now for my A11 both with pin and pattern but still only for user 0 (hence data for dual apps cannot be backed up)
[Magisk] zgfg:
Go to official site and look if it was released for your device:

Devices

This is the Team Win website and the official home of TWRP! Here you will find the list of officially supported devices and instructions for installing TWRP on those devices.

twrp.me
[Magisk] jamesta:
Thank you very much for the information!
[Magisk] HippoMan:
Forgive me, but I have several devices and have done multiple downloads, module reloads, flashes, etc. over the past few weeks, and I have gotten a bit confused and my memory is hazy. I'm running TWRP 3.4.0, and in order to upgrade to 3.5.0, do I need to run the TWRP installer, or will simply flashing the 3.5.0 .img file via Install->Install Image from within TWRP be sufficient?

PS: This is on my OnePlus 7Pro (GM-1917) running Android 10 (OOS 10.3.7).

Thank you in advance.
[Magisk] zgfg:
As always, you have to flash TWRP img to Recovery partition either by Fastboot or from the already installed TWRP (or another custom Recovery)
[Magisk] HippoMan:
Thank you. I just now did that, and although the new 3.5.0_09 TWRP came up fine after rebooting to recovery, TWRP also now starts coming up when I try to boot to System.

But I'm now restoring my latest system backup, and hopefully, that will get my device back to a bootable System.

I'll report my results.
[Magisk] HippoMan:
Yes, after the restore of my backup, I am now able to successfully boot back into my System.

And when I boot to recovery, I'm back in my 3.4.0 version of TWRP, which is no surprise. I'll stick with 3.4.0 for now, until I find out how to actually get the 3.5.0_09 install to work.
[Magisk] zgfg:
You can try by flashing from Fastboot (although, if previous TWRP was fully compatible, it should be the same as flashing from that old TWRP)

And you don't need to restore full nandroid backup, just flash previous TWRP
[Magisk] HippoMan:
There is no way to install TWRP via fastboot on this A/B device (OnePlus 7 Pro). It has to be installed via Install->Install Image->Install Recovery Ramdisk. However, when I do that, I always get sent back to TWRP whenever I try to reboot to System. This is the case even if I try to re-install the older version of TWRP (3.4.0).
[Magisk] HippoMan:
So ... I installed the following via a normal Install from TWRP: twrp-installer-3.5.0_9-0-guacamole.zip

That installed TWRP and it lets me boot into System, but it also un-rooted me. So, I reinstalled Magisk 20.4, and now everything seems to be back to normal, as well as my having TWRP 3.5.0_09.
[Magisk] zgfg:
Btw, why do you stick with the old Magisk 20.4, did you encounter some problems with 21, particularly with 21.2?
[Magisk] HippoMan:
I want to move very slowly about updating Magisk, given all of the issues that have been reported here.

Even a supposedly simple TWRP upgrade turned out to be not so simple, after all, and as you know, this caused me problems today. Therefore, I want to be 100-percent sure that I'm not going to have to deal with more unexpected issues with a 20.4-to-21.2 Magisk upgrade.

Unless I am missing something, 21.2 is still beta. Once it gets into the "stable" category, I will try it.
[Magisk] zgfg:
It is 'beta' but the old 20.4 does not support A11 and even if you don't have A11 it has improvements for A10 (and earlier), for SAR devices, A/B, etc.

Only 21.2 can install now to some devices/chipsets

Problems you observed now when installing new TWRP could be even related to your old Magisk
[Magisk] HippoMan:
I understand. But lately I use my device for my work in addition to for my personal life, and I don't have the luxury of going without it for an extended period of time for the purpose of doing an un-brick or any kind of major software installation, in case anything goes wrong.

And anyway, I do not plan to use A11 in the foreseeable future. I have seen even more issues and problems coming up for people who are trying to run rooted devices in the A11 world, and I don't want to be one of those people.

I don't see anything about A11 which makes it any more desirable to me than A10, which has been working fine for me.
[Magisk] HippoMan:
Oh ... one more thing: I seem to recall reading somewhere that the "TWRP A/B retention script" will no longer work if I use 21.2. Or am I mistaken? Perhaps that had to do with A11 and not 21.2 ... ???

When I do A10 system upgrades, that A/B retention script makes the process much easier and more straightforward than any alternative that I know of.
[Magisk] nitramus:
Uninstall question.

Preparing to update pixel 3 xl to latest update.

Currently on Canary

Planning on installing latest Magisk Beta.

If I remember properly I need to uninstall Canary first but How do I do it with the .zip without TWRP?

I presume using a fastboot.

1 - just do "fastboot.exe Magisk-uninstaller-20201228.zip" and that's it?

or

2 - just restore image in Magisk and reboot to uninstall?
[Magisk] jenslody:
Normally it works by just switching to the beta-update channel and update Magisk.

At the moment canary and beta re the same, just other version-umbers.
[Magisk] J.Michael:
I don't think you do anything with "the .zip" without TWRP.
[Magisk] Slim2none4u:
Just patch your stock boot.img from your current firmware with magisk and flash it with fastboot.

Install the update and then root as normal. Normal being, pull the stock boot.img from the latest firmware. Transfer it to your phone. Patch it with Magisk. Transfer it to your PC. Flash it with fastboot.

fastboot flash boot magisk_patched.img
[Magisk] nitramus:
That I get no problem. The question was changing magisk from canary to beta.
[Magisk] Slim2none4u:
So when you patch the boot image, make sure you are on the channel that you want to use be it stable, beta, or canary.
[Magisk] nitramus:
So I don't need to uninstall only change channel (at proper time)?
[Magisk] Slim2none4u:
That's what I've done in the past. Can only speak on my experience and divide.
[Magisk] nitramus:
Thank you. Restored image. OTA then changed channel and patched new boot.

Worked and is fine.
[Magisk] M1ster1:
Hi there,

I spent 4h yesterday (uninstalling, reinstalling, via recovery, changing recovery from orangefox to twrp, via direct install etc.) trying to understand why Magisk was working fine but was still displaying "install" buttons on the home screen.

Finally I discovered that it's just an UX problem of clarity :

Why are "Install" buttons shown in Magisk Manager home screen always? · Issue #1186 · topjohnwu/Magisk

This is more of a UX issue than anything else. When Magisk root processes and everything else are up and running, opening up the Magisk Manager app will show huge "Install" buttons on it's home scr...

github.com

I guess i am not the only one that has been confused and think that modifying "install" to "reinstall" should be implemented.

My 2 cents,

Thanks :)
[Magisk] zgfg:
MM displays Installed - so you can see that you alreday have Magisk installed and which version

By using Install you can also patch a boot or recovery img (not even for your phone), regardless of do you have Magisk installed or not), and by changing the Update channel you can control which Magisk version shall it use for

But the name Install might be misleading for somebody installing Magisk for the first time
[Magisk] kadyt:
Actually that was my first idea and that's why I chose restore the stock boot only in the first place. Maybe I'm wrong but that's what I thought it would do (to restore the stock boot.img only)

As it failed, then it was when I tried to uninstall magisk completely the next time, only to fail again and then the rest of the story

Really, I would love if someone could have a clue, putting together the two scenarios, just out of curiosity
[Magisk] Vixian:
Hi, I have a rather beginner question...

Am I correct in understanding that Magisk effectively halves your storage?

It seems all my files / partitions (/data, /system) are also mounted (symlinked?) under /sbin/.magisk/mirror ... This way all my files are "counted" / "reported" as double what it actually is, therefore halving the available storage.

Is this a bug or a characteristic of the implementation?

Is there any way around it?

Thank you!