yashsingh1/xdaforums huggingface dataset:
[Magisk] bassmannate:
No solution here but I just wanted to add that I'm running into the same issue. Would rather not have to re-root after every monthly update.
[Magisk] chooks06:
So far, my experience with MTK devices with unlocked bootloader boots with stock ROM, with or without root.

There was once, idk what happened, but instead of getting the orange state warning pre boot, I saw a red state warning - that didn't boot.
[Magisk] dcarvil:
Looks like re-root is the only solution for the time being.

https://github.com/topjohnwu/Magisk/issues/3256
[Magisk] chooks06:
In any case, if it didn't stick i could easily restore my previous image. I always do a backup before installing betas - a just in case habit..

Cheers! Stay safe mate!
[Magisk] Philnicolls89:
Weird, my manager does not require or ask for any permissions when hiding/repacking itself and all functions related to magisk and magisk manager work perfectly. Must be rom related?:confused:
[Magisk] pndwal:
Have a feeling most SafetyNet apps require GApps. I think even MM used to, but may now work for micro g.

I don't know if MM check is actually reflecting a full pass. I don't know how that works, and it may now contain fixes needed for MicroG.

If it isn't and doesn't, you may need an OS supporting signature spoofing (LOS doesn't :( )

May also need Magisk systemizer module (executed in terminal), a GmsCore, DroidGuard and modified playstore

I found this solution for Xiaomi Mi A2:

https://xdaforums.com/mi-a2/help/microg-pie-safetynet-t3914624

Nb: I have no practical experience with full MicroG system, but I'd love to hear method to utilize MagiskHide and fully pass SafetyNet w/ MicroG if you are successful! PW
[Magisk] Incognito777:
Thank you for replying mate, I have installed app systemizer too, as u said I had read LOS does support spoofing, all this while I thought it did, on second thoughts any suggestion on a custom Rom that supports Spoofing and microG. I even have installed Magisk props. 3rd party app shows spoofing disabled.
[Magisk] pndwal:
Sorry, post got truncated by Labs app. :( More above now.

LOS have strict policy not to break Google's / others licencing, or circumvent their Security model(s), therefore they never package GApps, or Include spoofing solutions.

Havoc and many other OS's have no such scruples... PW
[Magisk] Superwitschi:
Flashed it and all ok but i can't make any changes or add anything in system. Can somone explain why?
[Magisk] zgfg:
Maybe you are new to the systemless concept - for how and WHY, please read the Magisk docs on GiTHub, search back in the thread (every week or so somebody asks the same), google...

In short, if your device is e.g. SAR read only, you CAN NOT change your system files - instead, by help of Magisk, you mount your new or changed file or folder over the original one
[Magisk] debprosad:
Rooting problem with magisk

I have nokia 2.2 TA 1188 model. When i went to root it with latest magisk manager by patching boot image and fastboot command ,it failed to root..The following output received..

writing boot_b failed

download for partition boot_b is not allowed....what should i do? pls help

---------- Post added at 07:30 AM ---------- Previous post was at 07:21 AM ----------

I have nokia 2.2 TA 1188 model.When i went to root it with magisk manager by patching boot image and fastboot command, it failed to root...The output is as such

writing boot_b failed ( remote: download for partition boot_b is not allowed)

there is currently no TWRP for my device,so this is the only way i tried but failed...is rooting possible for this device?pls help
[Magisk] Didgeridoohan:
The Manager shouldn't need storage permission to hide... Might be something else going on. A common issue for hiding the Manager is Play Protect, so it might work if you temporarily disable that.

I've just been testing things, and the Manager (303) actually doesn't seem to need storage permissions at all to download stuff. There seems to be a bug with installation doesn't starting automatically after downloading a module from the repo though... Might be what you're seeing [MENTION=7341800]ausren07[/MENTION]. Scratch that... I just did a reboot and now I can install modules without any issues. Temporary glitch...

I don't follow MicroG stuff, but previously it has not been possible to pass SafetyNet with MicroG. No idea if that has changed. Do you have any other mods installed, like the HiddenCore Xposed module? That you can pass SN in the Manager suggests that you are using a spoofing mod like that. They are mainly cosmetical in nature and don't fool a proper SN check.

You've already been given a reply above, but I wanted to also add this:

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files

That sounds like you haven't unlocked your bootloader. That is a necessity for being able to install Magisk...
[Magisk] Superwitschi:
Look i cant change to R/O

Superwitschi Designs
[Magisk] Didgeridoohan:
Yes, you said so already. And I replied... Did you read the info from the link I posted?
[Magisk] Superwitschi:
Yes i did, will try it later

Superwitschi Designs
[Magisk] robuser007:
In the latest version setting for magiskhide for certain apps disappeared, does it work by default now (for banking apps) ?
[Magisk] Didgeridoohan:
Nope, it's still there. Open the "Shield" icon in the navbar and you'll find it.
[Magisk] kari kimber:
problem and reboot new magisk v21

I used magisk 20.x success running call recorder. but magisk new version 21.x released and updated my phone then call recorder crash and reboot my phone. if call received (ringing) phone directly reboot.

I don't know its magisk or call recorder problem.
[Magisk] zgfg:
According to the official doc (link was re-posted couple of times in this thread):

https://developer.android.com/training/safetynet/attestation

an app asking for SafetyNet attestation, calls to SafetyNet API which is part of Google Play Services.

Google Play Services collects data, communicates to Google backend and provides its response back to the application.

I don't believe you can make MicroG or any GApps substitute to sit here instead of Google Play services, since the communication to the G server is supposed to be authenticated from both sides.

Instead, a GApps substitute could fake the process, without communicating to the G server and providing its own, fabricated (Pass) result

That could work for an app from a garage (believing to the fake attest from the fake GApps), but not for an official banking appplication because the SafetyNet scheme provides a mechanism how that originating, calling app should validate itself whether the 'response from server' (as submitted by API) was really obtained from the G server

The scheme even includes a protection against reverse engineering that calling application locally on the phone - it is required that the fail/pass logic (and implications) are offloaded to the application's own server

Therefore, you could have different Pass or Fail SafetyNet results, depending on how serious is that app calling for the attest

On the other side, it is a mice and cat game. Some tricks may work for some time, then no more, until a new trick is found, and so on

Btw, our trick for stock firmwares with the official GApps (spoofing ro.product.model for SafetyNet to think that CPU is not ready for hardware-backed CTS profile attestation) will not last forever. In their shows I would try something like

- to read relevant props early at boot, before Magisk overlay (MHCP is based on) takes place

- to circumvent Magisk overlay and read directly from the stock prop table(s)

- to ignore props and try hardware-based attestation anyway

(just the ideas, not sure about their feasibilities and their possible, corresponding, catches twenty-something)
[Magisk] shadavis08:
Does anyone know if magisk version 21 is going to auto update through the app or do I have to manually download?
[Magisk] zgfg:
You also tested by MM Canary 303 - I did couple of times (investigating something else) but I always observed a small glitch:

- Canary 303 installed, Canary channel selected

- upon hiding=repackaging (the whole thing is not only in renaming the app [or changing the icon?!], but primarily in renaming the packages), it shows version 302 and asks for an update

- after the update it shows 303 again

- upon un-hiding/

restoring it remains 303 but upon the next repackaging it goes back to 302 and asks for the update

It was also captured in my screenrecording (sorry, large file but you could play directly from Mega):

https://mega.nz/file/V0sVkCxY#RDOpE0sLAx9Z1zNUjHcFm2wHGOWPOAMBq-4Us9ZSjCM

that I was only asked for Install over USB.

And yes, I had to manually continue the process upon installing the stub.

Btw, I was noted to disable Play Protect only first time (hence not while repeating and screenrecording), but it worked for me without disabling the Play Protect

PS: Just updated to Canary MM 305
[Magisk] argumantive:
Hello guys,

I have encountered a problem after upgrading to Android 11, previously all was working fluently with magisk 20.4 on android 10.

I have removed magisk modules, unrooted, and then updated via OTA, all worked as intended, I downloaded the magisk manager, and patched the boot file from the latest factory image (Coral for pixel 4 xl, october patch). After which, when I tried to flash it via fastboot, I only receive an error:

"Unknown Partition 'magisk_patched.img'

fastboot: error: cannot determine image filename for 'magisk_patched.img' "

Any idea what might cause this? I have tried to flash the factory image, after which was the same result. I have tried a factory reset, which still gave the same result.

Thanks in advance.
[Magisk] zgfg:
Discussed for days here that old 20.4 is not for A11 - please check the posts how the others went througj the upgrade.

Use Magisk Beta or Canary update chammels
[Magisk] andrea0807:
Now also the beta version of magisk (21) is compatible with andrid 11?

Currently i'm using the canary version on my poco F2 Pro with rom xiaomi.eu weekley (Android 11)

Inviato dal mio lmi utilizzando Tapatalk
[Magisk] argumantive:
I have used the 21 after the upgrade to android 11, the error was given when using magisk 21, with manager 8.0.1. I apologize if I was not clear! :X
[Magisk] Spartacus500:
New version :highfive:
[Magisk] dcarvil:
What Magisk channel are you on? If you are on stable, the current version is still 20.4. Once 21 moves to stable, it should auto update through the app. If you want 21 before then, switch to the beta channel.
[Magisk] zgfg:
In the very latest Canary MM build 305 and Magisk 21001 there are some fixes for padding the patched images for Pixels. IDK would it help you
[Magisk] shadavis08:
Yeah I just realized I was on Canary build Channel and that the new magisk is on the beta Channel. Thank you for your response
[Magisk] Didgeridoohan:
Thanks for the reminder, I've observed the same thing but forgot to let John know about it. Build 305 has the same issue, but reports 304 after repackaging. Probably just a faulty link/variable somewhere.
[Magisk] sdeft:
I am a bit confused about the install instructions as per below

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

"Pay special attention to the Ramdisk info. If the result is Yes, congratulations, your device is perfect for installing Magisk! However, if the result is No, this means your device’s boot partition does NOT include ramdisk, and unfortunately you would have to go through some hoops to make Magisk work properly." Then you need to follow https://topjohnwu.github.io/Magisk/install.html#patching-images eg. for Xiaomi phones.

In my phone the result is No but phone is rooted even without following the "PatchingImages" section. Am I missing something ?
[Magisk] JudgeDread11:
Sorry if I'm completely off, I'm kinda making a guess here, but are you specifying the destination partition?

It sounds like it's trying to get the destination partition from the filename. Magisk_patched obviously isn't an existing partition.

I'm that case change the image name to match the partition name (boot.img I guess)

Or specify the destination partition in your fastboot command line.
[Magisk] argumantive:
I am not specifying.

After rebooting into bootloader I simply go "Fastboot Flash Magisk_Patched.img" As I did before, the patched file is in the platform tools folder and I am running the command line from there.

I will try renaming, thanks for the input!
[Magisk] dcarvil:
That should be "fastboot flash boot magisk_patched.img".
[Magisk] argumantive:
Thank you, I am a moron... It worked flawlessly. :X
[Magisk] bobbyp1086:
I'm sorry if wrong place to ask. But did core only mode go away? Just had an update. To magisk 21 and manager 8.0.1. Core only mode is vital to me I can't not have that feature it's what allows a certain app to run even when magisk hide is working. Please a speedy response would be awesome.
[Magisk] Didgeridoohan:
Core Only Mode has been replaced by Safe Mode. Boot into your devices Safe Mode (search the web for the button combo, but it's usually something like power + volume down) and all your modules will be disabled. Reboot back to normal Android and all the modules will remain disabled.

That is not at all what you want though... If it is important to you, you could try opening a feature request GitHub issue about bringing it back, but I wouldn't hold my breath. If you've got good enough arguments though, who knows?
[Magisk] monicaONxda:
How to backup Magisk (incl. all modules / EdXposed & settings) without TWRP?

... Is there a way such as a "Nandroid Backup" with other apps that work on Android 10 (Busybox, Flashfire?)

I assume Titanium Backup can't backup whole Magisk incl. modules and settings in modules...

Thanks for any help!
[Magisk] jakelewis:
Thanks for your instruction. In the end I just allowed the OTA to reboot, which switched the active slot, then went thru the usual fastboot method of re-rooting.
[Magisk] bobbyp1086:
So boot into safe mode, reboot again and it's core only/safe mode? I don't have any modules downloaded, I just need su permissions for the things I do.

So there is this game, kart rider rush+, Mario kart in the new day, crashes if it's not in core only mode, I will try it if not I still have previous version magisk, every one of them actually I never delete lol. Thanks tho I'll update after rebooting twice.
[Magisk] Chris334:
With latest Magisk canary patches OTA on Pixel with Android 11 seems to work without issue, at least on my Pixel 3a. I used

# resetprop ro.product.brand aaaaa

to trick Magisk Manager to display OTA update option. I was able to apply Oct. 5 OTA with this.
[Magisk] zgfg:
Missing information which phone, firmware
[Magisk] Didgeridoohan:
No. It will

not

boot into Core Only Mode. Like I said, that is gone. All it will do is disable all your modules (if you have any installed). That's it.
[Magisk] zgfg:
Btw, better use systemless Busyybox NDK Magisk midule (e.g. to be able to hide it alongside Magisk)

Some vendors (Huawei - very good backup, Xiaomi - I don't like their backup but it is provided, Samsung - not familiar with) provide pretty good backup solutions

Brwy things generallydepend on the phone (info missing), I have A10 but also the fully working TWRP to make the full nandroid backup
[Magisk] Gleniu:
Hello, I'm on Magisk Manager 8 since yesterday. Am I'm missing something or now it doesn't show modules updates? In Manager 7.X the modules with available update was on the top of the list. Now the only way to know there is a module update waiting is to manually find and install it. I experienced it with MagiskHide Props Config - I accidentally found there was an update today when I was scrolling through all the modules in repo. Any help on that? Thanks ?
[Magisk] zgfg:
Apollo 13, we have a procedure for you ?

First of all, I reproduced your case (as suspected) by disabling Developer options/Install from USB (you don't have that option to turn it on).

Upon that, hiding Magisk Manager just failed.

Before it failed, I chose the name Manager (we'll come back to that later)

Now, I continued and hid/repackaged it manually:

- Went by MiXPlorer to

/data/data/com.topjohnwu.magisk/cache

- You should find two apks there, stub.apk and patched.apk

- Click on patched.apk (that one, not stub.apk) to install it

- It asked me and I had to disable Play Protect

- After that I successfully installed Manager (name I gave it earlier, before the regular procedure failed)

- It asked me to manually open the newely installed Manager and to continue installation (as for the regular procedure), I followed, it downloaded and completed installation

- At the end I manually uninstalled my original, not-hidden Magisk Manager (probably I could have to uninstall it earlier, too)

As a result I got fully working hidden/repackaged Manager, everything was just like previously when I was doing repackaging the 'regular' way - ugly icon, adding shortcut, Magisk hide, SuperUser apps, modules...

Btw, once that manual installation was finished, it automatically deleted /data/data/com.topjohnwu.magisk folder - like for the regular procedure

After couple of hours of testing and using the phone and modules, I successfully restored Magisk Manager (regular way - not manually, even with still disabled Install from USB option), everything worked as usual

---

How and why I came to manually installing that apk in that folder:

/data/data/com.topjohnwu.magisk/cache/patched.apk

Not by chance, but by following the know-how (you can also find all info in that ticket) revealed from TJW while helping him for:

https://github.com/topjohnwu/Magisk/issues/3147
[Magisk] Gleniu:
(deleted)
[Magisk] Didgeridoohan:
There was no update to the MagiskHide Props Config module. I only updated the fingerprint file and readme, which will make the date in the module list show that there was a change in the Github repo. If there had been an update it would have shown up at the top of the list.

Edit: and there's no need to keep trying to post, even if there's an error. First check if your post has actually been posted, which it had.
[Magisk] Gleniu:
Thank you for that. I was fooled by v104 and v105 description in module version - I thought that technically it is an update.

Edit: I'm using a smartphone right now (which I hate for the purpose of using a forum) and my browser hung and crashed. Twice. I checked if that was posted, but there was a long post just after my first post, so I missed it. Sorry for that. Tapatalk seems to work better.
[Magisk] bobbyp1086:
Thanks again, I understand it is gone, I was just saying core mode as in it's function. I'm using moto g stylus, all moto phones have had issues with magisk, don't know if it's known or just me, I'm a little stuck in past times I still miss supersu, half the modules won't work half the times and the other half they just miraculously work. Like the exposed modules, edxposed?, One day it said not installed open it up a few days later it's up and running then not again, I gave up in modules just give me root permissions and I'm good enough to get what I need going. I just disabled them all let me see if I get the same issue.... Yup I need core only mode, that sucks I have no idea how to downgrade to older version without complete wipe, reflashing modified boot img I have will not work it's older. Any suggestions
[Magisk] J.Michael:
What was "Core Only Mode", other than "(almost) all modules disabled"?
[Magisk] zgfg:
Atter that Safe mode (Android reboot), all modules will be disabled and Magisk Hide will be also disabled - don't forget to re-enable Magisk Hide (apps configured for Magisk Hide will be remembered). I.e., Magisk will boot with only the root
[Magisk] Syoenth:
if using Banking apps don't upgrade to Magisk 21 beta, for some reason my banking app (Santander) detected root after I upgrade to Magisk 21 beta, so I had to downgrade to Magisk 20.4 to get working that app again
[Magisk] Superwitschi:
Does not work, can't add system with my Xiaomi Mi 10. No R/O

Superwitschi Designs
[Magisk] Didgeridoohan:
I'm not entirely clear on the details, but from that I remember basically Core Only Mode didn't load modules at all, while Safe Mode just disables modules using the "disable" file in the module directory. If you want details you can check the code on GitHub.

There's been a few reports of the opposite recently, so you might he experiencing a fluke. Maybe MagiskHide failed to initialise (usually fixed by toggling it off and on again).

If mounting the root directory ("/") rw didn't work it's likely that your only option is to use Magisk modules to make your desired system modifications.
[Magisk] Superwitschi:
Which module i have to take?

Superwitschi Designs
[Magisk] sdeft:
Xiaomi Redmi Note 8

Firmware is 12.0.2.0 with LOS 17.1 and/or Havoc 3.9.
[Magisk] zgfg:
Disabled module is not loaded. And otherwise, this Safe Mode booting would not help for bootloops caused by a module (culprit module would be still loaded, and again causing the bootloop)
[Magisk] Syoenth:
i did that and didn't work, i forgot to say that I'm using my banking app on Island
[Magisk] guest4711:
(deleted)
[Magisk] guest4711:
Thanks, I'll give it a try.

But after trying to hide MM all folders are empty...

So I went this way:

1. Unhide MM.

2. Uninstall MM

3. Install magisk.apk 7.4.1 (2.6.2]

4. Verify update path is set to custom or canary

5. Rehide MM.

But the problem persist, no downloads of MM or modules from inside MM possible anymore.

I think, that problem depends on the missing permission for storage. MM tries to download to 'download path' which is /storage/emulated/0/Download by default (having permissions 770)
[Magisk] Didgeridoohan:
On the contrary, that's exactly what the Safe Mode is intended for:

https://github.com/topjohnwu/Magisk...led-a-module-and-it-bootlooped-my-device-help

If modules are again enabled for you when you reboot back to normal mode you might want to file a bug report for that.
[Magisk] Didgeridoohan:
What app are we talking about?
[Magisk] Syoenth:
Santander (MX)
[Magisk] Didgeridoohan:
That entirely depends on what you want to do...
[Magisk] Superwitschi:
Add some ringtones in system media

Superwitschi Designs
[Magisk] Didgeridoohan:
You mean SuperMóvil? If so, I can hide Magisk from it just fine in v21 (Canary 21001 actually, but they're basically the same). Without adding the app to MagiskHide it refuses to start, with it on the list it starts just fine and I can log in or register (can't test further than that, obviously).

What I'm trying to say is that MagiskHide generally works fine on Magisk v21. There are off course things Magisk can't hide and there are differences between ROMs and devices, but the basic functionality is there and working.
[Magisk] Didgeridoohan:
That's a very simple module. All you need is to create the module directory under /data/adb/modules and then create a module.prop file so that the Manager will recognise what you have. Your ringtones you add to a system directory in your module folder, with the same path that they would be in if you were editing /system directly. Example:

/data/adb/modules/MyAwesomeRingtones/system/media/audio/ringtones

Take a look in the Magisk docs for more details and for how you need to setup the module.prop file:

https://topjohnwu.github.io/Magisk/guides.html#magisk-modules

When everything's as you want it, reboot and you should be good to go.
[Magisk] guest4711:
Why not simply put them into /storage/emulated/0/Ringtones folder?
[Magisk] Syoenth:
I'm using Miui 11 global, idk then why isn't working, i have to use Island to clone and then run it, even in Magisk 20.4 when I opened the app it close
[Magisk] zgfg:
I was also confused (ago, when got my Mi 9T and started to root - now, after v21 release docs are updated, will look into) but I had no problems with installing Magisk over the whole 2020 (each and every Canary build) to all my eea MIUI 10, 11, 12 (Android 9, 10) firmwares.

I always patch Boot image (Recovery mode option disabled) and it patched with no issue - screenshot attached.

I did but only few times installed via TWRP, but I prefer patch+flash since that way I can keep images patched by older versions and revert back in case of issues with the new (Canary) release