yashsingh1/xdaforums huggingface dataset:
[Magisk] soder:
Because, I've many times flashed my rom's .zip since I started with Magisk, and after that I've still kept Magisk.

That's why I wonder...

/Söder
[Magisk] hgoldner:
My friend, you should be reading up some OP's and searching around the forums. You're asking the kinds of questions that indicate a certain lack of familiarity with the process that invariably ends with another post like "Help! I bricked my phone!"

This is a developer's forum. Do some homework; read; search; then come back with an intelligent question.
[Magisk] Captain_Throwback:
That's not even related to the original question I was answering, lol. Might help if you quote something relevant or at least mention what you're really asking about in the first place.
[Magisk] soder:
Boys! I asked how I flashed boot.img. You flash boot.img you said.

I then asked, if that wasn't flashed when I flash my rom.zip like I did when I wanted to restore my /system. Yes you said.

I then ask, why I kept Magisk during all the flashes I've done, if Magisk is in the boot partition and a flash of my rom zip should also flash boot.img.

I'm no developer, but I see my self as at least a couple steps above some POGO players in here in knowledge. You don't need to shoot me down when I ask some follow up questions..

/Söder
[Magisk] joshuaw84:
I think it's been hard following this exchange and this is why you've received the replies that you have... can you break it down? What I'm thinking I'm reading from this post is when you re-flash your rom you still have Magisk left overs? Can you elaborate? What Captain was originally implying is you don't have to reflash your rom and start over, technically you should only have to flash the boot.img from your rom. So more details would be vital in understanding the problem at hand.

Thanks!
[Magisk] hgoldner:
No, you didn't ask that (although now you are.) You said, "And that isn't flashed with flashing the .zip as normal?" Is that when you think you were asking about flashing /system? Again, all this is explained in the OP.

You flash your ROM (which includes /boot and /system), then follow the instructions in the OP. It's not that difficult and the OP really lays things out nicely.

So, yeah, your questions strongly suggest you haven't read the OP (hence my signature).

I know I should probably wait before posting this but I am repeatedly amazed with folks who think they can just drop in to xda, not search, not check threads, and assume that someone will just answer an easy question they are too lazy to look up for themselves. Maybe I'm just a grouchy old man, but it does tick me off.
[Magisk] soder:
I will try. =)

I've for many years been flashing rom's. I know it flashes /system, and if often let me keep my /data. Been using that for updates since I've been rooted with custom recovery and Xposed and OTA's doesn't work.

The latest weeks I've been using Magisk with sometimes cf's root, and sometimes phh's root. I know that systemless stuff like those "mods" use /boot (or boot.img or how you say it).

I know that I don't need to flash /system when updating or removing Magisk. I just said I've flash my full rom since I started using Magisk, and after that, still kept Magisk installed after boot up.

That's why I wonder how it should do if I WANT to remove Magisk from the /boot partition. Someone told me that if I flash my ROM, I would also replace my /boot. That what I wanted to know of, since as I wrote above, I've flashed my ROM and kept Magisk after that.

/Söder
[Magisk] joshuaw84:
So there's a Magisk Uninstaller Zip as well, if you're still seeing magisk installed (other than the manager this can be unistalled like an app.) this may be the rom zip not working correctly or you're just doing a dirty flash and it's just updating parts that it can. I don't know and cannot speculate. If you want to remove magisk and flashing your roms boot.img or rom itself aren't working out for you, you can try the uninstaller in the download section of the Magisk thread.
[Magisk] soder:
That was a follow up question, yes?

1. I asked about boot.img 2. Got an answer. 3. Asked if that is't flashed with you flash a rom .zip.

Sure, that's where I think I asked about it, if /boot wasn't flashed like the /system was when flashing a ROM's .zip.

English isn't my first language as you understand...

I have no problem with installing this. I had general questions about how the partitions works, and I hoped that someone in here could help me with it. It might have been wrong to ask a general question in a such specific thread as this...

I have, but not today, and I don't think it answer my general questions about how the partitions work? Sorry if it does...

I understand, but, I think that I'm not the worst kind at xda. I at least follow threads and read posts since I last was in. =) Also, I try to help others to, and not only let grouchy old men answer them. ;)

---------- Post added at 10:06 PM ---------- Previous post was at 10:01 PM ----------

Yeah, I know about the uninstaller. Like I said, I asked some general questions about android partitions, and I think I got pretty much misunderstand, and you guy's answered me like I had problems with Magisk.

My bad not clarifying that...

/Söder
[Magisk] Spartacus500:
On the new version, I can't hide the new process :( it works like this, I hide the process like in the screenshot below, then I exit Magisk manager and re-enter the hidden app and this process is disabled :( how to solve it ?
[Magisk] J_Force:
Don't know if it is allowed to ask here but I am looking to install Magisk and root my Samsung Note 20 ultra. Followed the samsung part of installation instructions from Magisk Github but did not result in the app to do additional setup. The tried the dr. Ketan guide multiple times. But still nothing happens when installing Magisk Manager after jumping through all the hoops. So I am back at square 1, with a unlocked bootloader and stock firmware. Hoping to find someone to show me the right way to install Magisk and root my new phone.

The Note20 Ultra is on the most recent firmware, so Android 11 en OneUI 3.0
[Magisk] zgfg:
Then it's not easy. You can find magisk zip 20.4 on Github and install from TWRP - if applicable to your device

Otherwise, I think you can still find the json for 20.4 on Github, then set the Update channel to that json, then it will install the that old 20.4.

(When I needed I did similarly for Canary, but it was more complicated since policy for Canary json is more complicated, I needed to create my own json and to upload to my Github place).

Sorry, if you are not familiar with Github, json, etc - I cannot support you further

Btw, you say you had previously flashed your boot.img with 20.4 - next time you will need to save your previously flashed img that you can simply flash the same again if needed - that's always the simplest way to downgrade
[Magisk] zgfg:
You can try from Terminal:

su

magiskgide add <pkg-name> <activity-name>

magiskhide lst

Check the Magisk docs on Github, Tools, Magiskhide
[Magisk] Lughnasadh:
FYI, Stable channel version is now 21.2.
[Magisk] Spartacus500:
I don't know the full name of the processes so I don't know how to do it. The question is why adding a new process doesn't work in the latest version of Magisk 21.2(21200) & Magisk Manager 8.05.4802(15) 😔🤔
[Magisk] zgfg:
Install e.g. Package Manager from Google Play, you can find for each app its package name and vice versa, as well as all other details about the installed apps

I did the same for another app that Manager did not even want to list, and it worked perfectly

Otherwise, you could report to Github, Issues (but the policy requires that issues must be reported only for Canary, not for Stable - sorry, that's the way)
[Magisk] aringler:
I'm stuck in a bootloop after flashing the patched boot.img (magisk_patched_li0Ey.img).

The problem might be caused, by an update through flashing new radio, bootloader, factory image, and patched boot.img while still having some modules active: Viper, systemless, BusyBox, Magisk Hide and maybe some other.

The log is created during the bootloop with adb. Did an adb logcat -c beforehand.

Here some more information:

Pixel 5

Android 11, RQ1A.210105.003, January Build

Stock ROM

Magisk version: 8.0.4 (4770),

Update Channel: Canary

Ramdisk: Yes

A/B: Yes

SAR: Yes

Crypto: File

Magisk Manager installed: N/A
[Magisk] zgfg:
In case of bootloops due to the errant modules:

- find out how to boot your phone to the Safe mode

- boot to Safe mode, then reboot normally

- upon that, Magisk Hide will be disabled (you must re-enable) and all modules will be disabled (no more causing the bootloop)

- then investigate modules one by one, which one to enable or uninstall
[Magisk] aringler:
I'm not able to enable or disable any modules anymore. See the attached image.
[Magisk] zgfg:
Yes, finally

You can see few posts back, already discussed with the same user
[Magisk] zgfg:
Your screenshot says: Magisk Installed N/A?!

Don't know if patching (or flashing Magisk, how you did, ended successfully)

Maybe you previously had your Magisk Manager hidden - see above, answered to somebody else earlier today. You should try by uninstslling Magisk Manager and also your previosly renamed Manager, then reinstalling the Manager again
[Magisk] HippoMan:
Thank you very much.

For now, I have disabled update checking in Magisk Manager, because I don't want to lose 20.4 (due to issues I have mentioned a day or so ago).

However, I notice that 8.0.5 Magisk Manager is now available. Has anyone seen any issues with that? If not, I will update.
[Magisk] tiger10000:
The latest magisk 21.2 when I install it xposed moudel is not working (activated in edexposed managet ) riru edxposed yahfa 0.4.6.4 4563 instaled . riru 21.3 as riru 23.1 causes that exposed moudel not working… . so I am back to magisk 20.4 working perfect any fix to instal the latest magisk my device redmi k20 pro premium edition miui 12.0.6 eu
[Magisk] HippoMan:
Which version of MagiskManager are you using? Recently, the latest version became 8.0.5. I have been using 8.0.4 and don't seem to have that problem (at least not with Magisk 20.4), and I am trying to decide whether to upgrade to 8.0.5.
[Magisk] IanWorthington:
Just updated my Asus zenfone 7 pro with the latest Magisk (or Manager? I didn't pay attention...) as prompted, and I'm now in boot loop. It flashes up a "Qualcom crashdump mode" screen with "Waiting for a flashing full ramdump..."message for an instant, then immediately resets. Rinse and repeat.

Is there any way out of this?
[Magisk] zgfg:
Since

- TJW said on Twitter that this will be the latest v21

- Magisk Stable was updated to 21200 (the same Beta was already, while Canary is on higher 21201)

- Magisk Manager Stable and Beta are updated to 8.0 5 (Canary is still on lower 8.0.4)

does it mean that Magisk Canary will soon go to 22?
[Magisk] wallace108:
Hi. I have an MTK device with Android 9.1.1.

I installed the latest magisk manager 21.2 (unchecking keep forced encryption).

Ramdisk No, A/B No, Sar yes, Crypto: Block.

When I patch the boot image, magisk finds that the boot image is signed with AVB 1.0.

Therefore I can't get root (the phone bootloops with a warning: Red State: your device has failed verification and may not work properly. Please download boot image with correct signature or disable verified boot.)

Do you have any recommendation on how to disable the verified boot? There used to be a way in an old version of Magisk manager, but it has bee removed.

Thank you

Mike

PS There is no vbmeta in this rom
[Magisk] zgfg:
If applicable to your device and the way how you previously installed Magisk 20.4, then you can just flash your old boot.img that was previously patched by 20.4, and voila

More about possible downgrading to 20.4 answered two hours ago to another user

But it could be also due to the no more compatible module. How to disable modules causing the bootloop, answered also an hour or two ago
[Magisk] HippoMan:
Good news! I managed to fix the problem.

I tried EdXposed instead of TaiChi, and all of a sudden, the GravityBox nav key remapping problem got fixed under 21.2. At first this didn't pass SafetyNet (which is why I have been using TaiChi, with which SafetyNet does pass), but then I tried the EdXposed "Pass SafetyNet" setting, and then, SafetyNet does indeed pass!

So, everything is now working for me with 21.2. Here are the particulars:

OnePlus 7 Pro (GM-1917) running OOS-10.3.7, TWRP 3.5.0_9-0, Magisk 21.2, MagiskManager 8.0.5, EdXposed Manager v4.5.7, EdXposed 93-v0.5.1.4_4655-master (YAHFA), GravityBox 10.1.0.
[Magisk] Zeuszoos:
Hi,

I updated to 21.2 and my LG (H910A) V20 would just crash to a gray screen (too tiny to read). So I used TWRP to restore to 20.4 I believe.

I saw an option that I never saw before when I went to update and I was wondering if my having failed to check that box when it gave me the choice is why it didn't work. The option was;

Preserve AVB 2.0/dm-verity

I don't know what that is, but could that be why it didn't work? Should I try checking that box?

Thanks!
[Magisk] Darkestnoir:
After update to 21.2, safteynet check takes ages and fails, so banking apps take ages to open/not working. Also hiding of new apps not working, after reopening the magiosk,the hidden apps are no longer hidden. OnePlus 3T, LOS 17.1
[Magisk] IanWorthington:
Thanks, Reinstalled 20.4 from TWRP and, after a bit of faffing around and the phone rebooting only to TWRP, got it rebooting to Android again. I've turned OFF "notify about updates" now.
[Magisk] pndwal:
Were you able to root this way previously successfully? Because, while this works on a number of devices without ramdisk in boot image (esp Xiaomi) as these have ramdisk compatible bootloader and Magisk adds ramdisk to image, a ramdisk = No result will otherwise (normally, w/ no bootloader compatibility) require Magisk in Recovery (ie. patch Recovery image) in any case. PW
[Magisk] jkeuclid:
Hi, I've been searching on this and today after I updated to Android 10 on my Moto G7 Power, installed TWRP and Magisk successfully but I keep failing Attestation, why is this happening? and should I be concerned? I do know that there's a new API or some such deal, but in any event is this fixable?
[Magisk] Lughnasadh:
Did you enable MagiskHide? Also.... https://didgeridoohan.com/magisk/MagiskHide#hn_CTS_profile_mismatch_vs_Basic_integrity
[Magisk] quyleanh:
Does this method still work?
[Magisk] jkeuclid:
I did enable for Google Play Services, is that what you're referring to? If so, it does nothing.

Check that, yes the slider is enabled.
[Magisk] pndwal:
Yes, his was the first no frills solution. Works by creating mismatch w/ model prop(s), but doesn't spoof a real model (value set to 'basic' or something, but any value will work).

MagiskHide Props Config solution is therefore better as it allows spoofing real models from same OEM (which still produces the mismatch - as long as you don't use your devices model prop value(s) - that causes fallback to basic key attestation), and this is much better if you want device/OEM specific functions (like Galaxy Store, high end camera functions etc) to keep working. PW
[Magisk] pndwal:
Guess that explains why he hasn't bothered aligning current Canary Magisk Manager either. 😃

Sammy users will be happy that John's been testing this on his:

And wait! ... There'll be more...

Release Notes

2020.12.28 Magisk v21.2

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

- [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-module command

- [General] Trim Windows newline when reading files

- [General] Directly log to file to prevent logcat weirdness

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

Magisk Manager Changelog

v8.0.5

- Fix sepolicy rule copying

PW
[Magisk] J_Force:
Is there anyone here that can help me out? I really like (aka "need" ;-) ) Magisk on my new Note20Ultra.
[Magisk] quyleanh:
Actually I have tried MagiskHide Props Config with some spoofed models. However the banking app still detects device's unlocked bootloader state.

I don't really understand how this app check unlocked state.
[Magisk] go vegan:
Just updated to Magisk Manager 8.0.5 (4802) and the "Request Timeout" (this affects the "Automatic Response" → "Prompt" setting) is not working.

I'm trying to set it to 20-30 seconds, and it's only giving me 3 seconds.
[Magisk] wallace108:
Thanks for your reply pndwal (y)

No, I never rooted this phone before. So as per your advice I patched the recovery and started the phone in recovery but alas got the same Red State message and 5 seconds later the phone rebooted to system. So now I'm stuck with AVB. No hints on how to disable it?

PS

I added the magisk install logs of boot and recovery for reference.
[Magisk] J.Michael:
I think that, before today, you needed the beta version of Magisk if your device was running Android 11.

I think @pndwal's note indicates that, as of today, stable is yesterday's beta.

So, if you did *not* use beta, try fresh patch and install. I'm not sure what controls which version of Magisk is used, so I would uninstall Manager and try to download the latest Manager from github.
[Magisk] Iustin_Theft-07:
I had a Huawei Y6 (2018) with qualcomm chipset rooted with magisk stable 20.4. Updated to 21.2 stable through manager stable with and without the option to preserve dmverity. Bootloop on the new 'stable' 21.2 for me...
[Magisk] JCDentonMale:
At first, updating from 20.4 to 21.2 did not work for me.

- Tried updating from the Magisk Manager app, no error, but root was lost after rebooting (Magisk was not even detected)

- Tried to flash Magisk 21.2 zip file from TWRP, same, no errors but Magisk was not detected after rebooting to system

- Tried to uninstall Magisk by flashing uninstaller zip, rebooted to system, uninstalled Magisk Manager remnant, then tried again flashing Magisk zip in TWRP. After rebooting, Magisk was detected and root was back!

I only had one module installed before trying to update, "MagiskHide Props Config". Once Magisk was detected again, I reinstalled it successfully and now can pass Safety Net.
[Magisk] J_Force:
If I understand correctly you say I just try again but with Magisk Manager 8.05 instead of 8.04 and that should fix it? So install the manager from github (I downloaded 8.0.4 before from github as well), patch the AP file with that and then I should work?
[Magisk] aringler:
I'm not able to boot my phone in safe mode, since it is stuck in a bootloop.

I need to press the volume down to get into safe mode during the boot animation, but it never gets out of the boot animation, so it does not boot into safe mode.

yes it was hidden. It was renamed to Manger, but right now I'm not able to find it in the installed app.

I just find the normal magisk manager, which I have deinstalled and installed again, several times.

I'm trying this all with the canary update channel. Is this the right way? Some other user suggested to use the new version 8.0.5. But is it compatible with Android 11?
[Magisk] zgfg:
As long as your renamed/hidden Magisk Manager remains instslled, your new MM will not be able to catch the Magisk, it will show that Magisk is not installed and you will not be able to manage the modules from

If you have proper TWRP for your device, you can try two things:

1) to delete /data/adb/db (Magisk database), AFAIK it should fix the problem with the old/hidden Manager.

You can also add empty files named: disable (exactly as that) to each subfolder under /data/adb/modules

That way you will disable those modules

2) Flash Magisk uninstaller zip (find from Magisk Github)

Otherwise but not popular, Factory reset (it wipes Data, hence Magisk db and modules, and the old hidden MM app - but not the Magisk itself)
[Magisk] aringler:
For Pixel 5 a proper TWRP does unfortunately not exist.

Question to 2)

Will it be a real factory reset? Or only magisk will be removed completely.

Rembering some time in the past, where flashing the uninstaller didn't wiped my data...
[Magisk] zgfg:
I've answered you about Factory reset in the cited answer but assuming that Factory reset wipes Data.

Since you don't have TWRP, you can only use your stock Recovery, I really don't know which partitions would it wipe but IMO, Factory/Hard reset should always wipe (at least) Storage hence Data (and Internal memory)
[Magisk] nowster:
Again, it looks like something's wrong.

My Pixel 3a worked for a couple more days with MHPC in Force Basic using a Nexus 5X.

Then overnight, there's a notification from Google that my device was no longer compatible with contactless payments and both basicIntegrity and ctsProfile are failing.

There's a deeper level check happening somewhere... or Magisk is crashing in such a way to fail a background check.

I've been able to uninstall the Force BASIC, reboot, reenable MagiskHide which mysteriously had turned itself off, apply Force Basic again, as a Nexus 6, and it's now giving two ticks.
[Magisk] Didgeridoohan:
There's your issue... MagiskHide has been known to turn itself off on a reboot in rare cases (on some devices, not so rare). If that keeps happening there's perhaps a new but introduced somewhere and you'll have to provide some more info about it: https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] pndwal:
As noted above, Stable is now the same as Beta, and Magisk itself is not updated; Manager has a minor selinux fix, so it's doubtful the update would fix it, but I'd say worth a try as it has changed.

More to the point, did you have Update Channel set to Beta (or Canary) when you tried previously? Because you need 21000 series Magisk for A11 compatibility, and stable channel would have used 20000 series (20.4) before today. (This was released in March 2020, way before A11!) Of course now any channel setting will do.

Other than this, as I've noted above, John Wu has himself got "Magisk running without a hitch on One UI 3.0", presumably on his shiny new Samsung Galaxy Z Fold 2, so I'd be rechecking official instructions for Samsung again carefully... Hope it helps, PW
[Magisk] zgfg:
PS:

Btw, look to the XDA Pixel subforums, probably Guides section. There were, for various Pixels, how-to guides to overcome Magisk bootloops (due to modules)

It was before this Safe Mode trick was implemented to Magisk and basically it was all about modiying the patched boot img to boot Magisk but with the modules disabled (since it was not possible to do it from the non-existing TWRP)

There is also a third way by ADB while booting, with the command:

adb wait-for-device shell magisk --remove-modules

but that did not work on some devices (Pixels included - don't know now for A11), hence the only way was with those modified patched images having hard-coded to not initialize the modules
[Magisk] dr4go:
Goddammit, it seems to have started...
[Magisk] bradical711:
If I wanted to downgrade magisk from 21.2 back to 20.4, could it be as simple as flashing the 20.4 magisk.zip file in twrp again like I did to update? Or do I need to flash my stock BL then use the 20.4 magisk zip in twrp.? I'm on pixel 4 xl android 10. I want to downgrade due my edxposed modules no longer working with magisk 21.2. I know why they aren't working and it's unfortunate because magisk 21.2 is amazing but I value edxposed more. I am also using Riru 21.3 and 4.6.4 (4563) yahfa the last stable versions of edxposed. I wanted to try the canary version (23.1 riru + .5.1.4 (4655) yahfa) but I don't know if that would fix my edxposed modules working with magisk 21.2 either.
[Magisk] J_Force:
started from scratch and now it seems to work. got the app available after flash and it did the additional setup. When I open the app I see it is installed. Let's see if I can get the modules running!
[Magisk] tiger10000:
Same problem here… any fix
[Magisk] pndwal:
Goodoh... So was channel set to Beta on previous attempts? Or Stable? PW
[Magisk] J_Force:
Stable and using 8.0.04