yashsingh1/xdaforums huggingface dataset:
[Magisk] dcarvil:
There are a lot of suggestions on @Didgeridoohan site at

Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide

www.didgeridoohan.com

I think booting into Safe Mode is your best bet. This site tells how to get into Safe Mode.

Two ways to enable Safe Mode on Google Pixel 3a

In this article, you will learn the two ways you can make your Google Pixel 3a start up into Safe mode to temporarily disable all third-party applications.

thedroidguy.com
[Magisk] andrew_yousry:
Dear @topjohnwu ,

I'm currently facing a problem. after updating the banking app, it started to show that the app is not supported on rooted device. Although I still can pass safetynet check and the app is checked in magisk hide, the magisk manager is hidden also.

I tried to troubleshoot the problem, I reinstalled the older version, it didn't show that message and worked fine. unfortunately they stopped the older version and now I have to use the new one.

Pleased help me

old app link

new app link

Screenshots attached
[Magisk] daddylonglegs:
Thanks. All the modules have been removed. Unfortunately, every time I flash the magisk boot image I get NO VALID SLOT TO BOOT

:(
[Magisk] raxeffect:
Hello all,

I have a Realme X2 Pro running C34 version of official rom on Unlocked bootloader with Magisk 20.4; I installed 21.4 through the recommended installation and it resulted in bootloop (very occasionally it goes further and there is error messaging saying android system is corrupted or something.)

I have tried reinstalling recovery - which allows going to recovery; I 've reinstalled vbmeta.img that also hasn't helped. I have cleared cache and system data and reinstalled. I've dirty flashed a ROM over it as well;

I am now trying to download firmwares to extract boot .img and see if that works.

ANy suggestions as to how to get this working again?
[Magisk] dcarvil:
Are you using the latest version (30.0.5) of platform tools? https://developer.android.com/studio/releases/platform-tools

Try a different USB cable and/or port.

There are lots of other potential solutions in this link.

pixel "no valid slot to boot" site:xda-developers.com - Google Search

www.google.com
[Magisk] daddylonglegs:
Yep, I am on the latest ADB. Tried a new cable, and even a new computer, and still the same thing every time I flash Magisk: NO VALID SLOT TO BOOT

:( :( :(
[Magisk] dcarvil:
Sorry, I am out of ideas. All I can suggest is go through the links in the google search in my last post.
[Magisk] DiamondJohn:
Sorry if you have sorted this out already, but your commands dont look right.

I used (return to stock in my example, but you get the idea)

You appear to be missing thge "FLASH" part of the command. 🤦‍♂️
[Magisk] daddylonglegs:
I appreciate the reply but my post was replying to someone who told me to try it that way, without the flash command.

Every time I try to flash Magisk on my Pixel 3a on Android 11, I get the error: NO VALID SLOT TO BOOT

I've used Magisk for years in the past, so it's not me being a noob. Every single time I try to flash the patched image I get NO VALID SLOT TO BOOT errors afterwards and have to re-install the OS to get it working again.

I would really like to get this solved. :(
[Magisk] wangdaning:
Flash it to both slots add "--slot all" in the command.
[Magisk] kevk60:
Maybe try fastboot boot magisk_patched_*****.img without the adb. I put the patched image in the platform tools folder, opened a power shell window and entered the command fastboot boot magisk_patched_****.img. It booted to the system then I went to magisk and did a direct install in magisk. All went well. This was on a one plus 8t with a/b partitions. I of course entered fastboot devices to make sure the phone was recognized and then entered the other command. This was done on a pc not a mac also. Hope you find a solution. It can be frustrating.
[Magisk] kevk60:
My previous post was supposed to be directed towards @daddylonglegs. Sorry for the confusion.

The command I used is...

C:\android-sdk\platform-tools> fastboot boot magisk_patched_****.img
[Magisk] DiamondJohn:
If you have the return to stock image from your manufacturer, and look inside the fash-all.bat, you can see exactly what the fastboot command should be like.

I have a Pixel 4a and it shows that flashing partitions explicitly name the partition after the command flash: eg:
[Magisk] pndwal:
Sorry, who could add it? PW
[Magisk] daddylonglegs:
Just tried this. I still get the NO VALID SLOT TO BOOT error

:(
[Magisk] daddylonglegs:
thanks so much for the reply. The MD5 for my fastboot.exe is: ffe96c8dfce2b88d98c30605d7566f6c

Also the command I have been using is:

fastboot flash boot magisk_patched_qfngE.img

which follows your method of having the type of flash named (boot).

I have no clue why I keep getting this NO VALID SLOT TO BOOT error every time I flash magisk's boot file. I've never had a problem with Magisk before and I have tried everything I can think of! :(
[Magisk] daddylonglegs:
Alright so huge update; everything now works! How did I do it?

I switched from using Command Prompt to PowerShell. I don't even know what made me figure out to give that a try, but it worked!

Mystery solved for anyone else that ever has this problem!
[Magisk] curiousrom:
Sorry, that part was addressed to an other user.

Post edited.

***
[Magisk] daddylonglegs:
Now that my phone is finally booting I have a completely new problem.

Only 3 modules installed. Systemless hosts, MagiskHide Props Config, and Universal SafetyNet Fix.

My phone will barely make it to the home screen and then it will just hard lock.

I am on a Pixel 3A, stock January 2021 Android 11 ROM, with the latest Magisk canary (f5593e05; 21401 for Magisk and ver 4835 15 for manager).

Any one have any ideas?
[Magisk] andrew_yousry:
no one replied me till now

please help
[Magisk] pndwal:
“Curiouser and curiouser!” Cried Alice 😁
[Magisk] garylawwd:
Maybe your banking app was updated to detect an unlocked bootloader in which case the only way around this is to revert to unrooted stock and lock the bootloader.

Personally I hate banking apps and just use a browser instead. This may also be an option for you perhaps?
[Magisk] WeirdSoup:
Just install v6 instead. It still works very well. For me, only v6 can hide xposed from some apps that can detect xposed. With v7, those apps can detect xposed. And the root toggle (& AutoMagisk) is the easiest and most effective way to temporary unroot & hide the entire root-related stuffs.
[Magisk] joshuaw84:
Modules, check out the downloads in the manager.

I can use xposed just fine with magisk 7 suhide latest and can pass safety net. No need for a toggle really...
[Magisk] Elmarigo:
Can someone help me please?

Why doesn't magisk work?

I tried placing a modified build.prop in .core/mirror/system but the system doesn't care at all about it!

Also I cannot write or modify the existing files in there.

How is this supposed to work? Or is it just disfunctional?
[Magisk] Dyspr0sium:
Can confirm that I am passing SafetyNet (PoGo) with suhide 0.54 + Magisk v7 + Xposed 86.6 on my OnePlus 3.
[Magisk] Darke5tShad0w:
It works fine nor is it disfunctional.

Please provide more info about phone etc, steps to install and whether it is a first flash on a clean boot image or if you have upgraded magisk.
[Magisk] WeirdSoup:
I dont need to bypass the safetynet. I mean the other apps that detect root and xposed itself using their own methods. Yes v7 might can bypass the safetynet, but in fact, there are only a few apps that are actually using it. Most apps still using their own ways to detect root and/or xposed, and until v6, magisk could hide xposed from those apps. But with v7, those apps start detecting xposed again, and there is no answer which can manage with that. Actually I totally dont care if it can bypass safetynet or not. That is the reason why I stick with the v6, and I mean, if there are other people who want to use magisk for the same purpose, It will be better to use the v6.
[Magisk] joshuaw84:
Are those apps detecting root or xposed? If it's root that's what suhide is now for. Still no toggle needed as its per app basis. Magisk wasn't meant to be a toggle it's a for modules, just so happens it could handle it before root solutions could. This is all new, go with the evolution of things, it's fun [emoji1]
[Magisk] Captain_Throwback:
You're doing it wrong.

You need to create a Magisk module - a Cache Mod, to be exact. Looks like you have some reading to do ;).

P.S. You shouldn't need to create a modified build.prop if all you want to do is set some props. A post-fs.sh cache module with some setprop commands should be able to handle that (depending on the props you're trying to set).

P.P.S. You shouldn't be touching anything in the core Magisk folder - that's just asking for trouble.
[Magisk] WeirdSoup:
I know. And I already tried the v7 and suhide(with the gui app + xposed 86.6), and yes, it can hide root from those apps which just simply call the "su" command. but if an app is using a little more complicated method to detect root(dont ask me what is it; I am not an expert so I dont know), It can detect root. It seems that many apps can find the SuperSU related stuffs no matter if I use suhide or not.(Don't tell me about reboot, I surely know that it needs to reboot to apply changes so I did it every times.) The fun fact is, most apps can't find the phh(If I turn off the toggle, or that apps don't call the su command) until now. But there is no toggle in v7, and no methods like suhide if I use the phh.

And also, many apps also can detect the xposed itself, and the suhide can't hide xposed. So many banking and mobile game apps can fine xposed, and with v6, most apps cannot find xposed until now.(Even if I don't turn off the toggle. Some apps just check if there are xposed and SuperSU or not, so I can use that apps without managing the toggle.) But they can detect if I use v7. I dont know why.
[Magisk] shinobi26:
Every time I try to install a module through the Downloads section in Magisk Manager I get "The zip is not a Magisk Module!!". Anyone know how to fix? I've tried using the Magisk Uninstaller and starting over and what not. I'm using phh's SuperUser for root.
[Magisk] Rude People:
i have noticed that with magisk v7 root, my phone's stock camera loses its modes feature (dual camera, panorama, etc) except for "Auto" and "Beauty Face", and with low light detection always on and greyed out. when i have magisk v7 root removed, i have all the modes and i am able to toggle low light detection on and off. i am running stock marshmallow 6.0.1 on my Galaxy S5 G900T. anyone know if this is a bug/cause from magisk?
[Magisk] JudgeDread11:
No the best way to get your issue fixed is to search and read. Your question has been answered many times.
[Magisk] ericotena:
Does safetynet only detects system and systemless root? Does it detect other flashed zips that modify system for example installed adaway or viper4android?
[Magisk] alexpower:
If we would know that, a patch is so much easier

Gesendet von meinem HTC 10 mit Tapatalk
[Magisk] Artim_96:
The toggle was removed because that functionality is now provided by the suhide versions for SuperUser and SuperSU.
[Magisk] spaxx24:
Is this supposed to work on Samsung ? When i press the button to "unroot" it just changes back after a few seconds. I see the message about "SELinux status" but I dont know what that is.
[Magisk] Elmarigo:
Thank, you very much, I think I got it kinda working now.

My intention is creating a module, that makes "Secure Settings" work again, with Magisk + phh-superuser259.

(It was working with Magisk v6, and phh-superuser V16., but it wouldn't accept root anymore, after updating to Magisk v7 and phh-superuser259.

I have read in many places, that Secures Settings searched for "su" in /sbin/su, /system/bin/su, and /system/xbin/su.

So, using my module, I created the path /magisk/maketaskerroot/system/.

In this path I created a symlink named "bin" to /magisk/phh/bin/ because there's "su" in there and this should make Secure Settings find su.

The result was, that it is kinda working. Secure Settings now found root.

But as a trade off, no other app accepted su anymore including phh supersu.

I thought that it was possibly some security related problem, probably caused by the more modern apps, that wouldn't like having su in /system/bin.

So I changed the link's name to /magisk/maketaskerroot/system/xbin.

I had to allow root for all desired apps again after rebooting.

It seems to be working now, for "Secure Settings" as for all the other root dependent apps.

But I'm still not fully convinced by what I did, for the main, because I' got these questions:

1.

Why exactly did all the other apps not work with the symlink to bin/su in /system? If they don't like having su in /system/binm they still could have used it from where they already where using it before - propably /magisk/.core/bin/su, as issuing "which su" in the terminal app tells me.

2. Why did Secure Settings work before, with Magisk v6, and why doesn't it work anymore with Magisk v7? Maybe this is a side effects of the efforts for trying to make su invisible because of that SafetyNet/Pokemon hype?
[Magisk] nk950357:
Miui 8 with Android 5.0 doesn't work with magical v7, it keeps FC

Miui 8., xiaomi 4i
[Magisk] neo_mat:
I got a lenovo a7-10.

And probably same arborescence as you A7-30.

tomorrow I will try to run the same commands.
[Magisk] Nekromantik:
hi all, I will be flashing a N ROM today and want to use Magisk with Phh for AP.

Do I flash magisk, supersu and then custom kernel? Or kernel first?

thanks
[Magisk] DiamondJohn:
Im happy to hear it all now works for you, however, thats the opposite of "mystery solved" as to why it wasnt working before. But it certainly is a path for others who end up in the same dead end as you. (y)
[Magisk] daddylonglegs:
Yep! Figured I would post the fix for anyone that ever has the problem.

The only issue now is when Magisk is enabled, my entire phone freezes shortly after booting into Android. I only have 3 modules installed. Universal Safetynet Fix module (v 1.1.1), Systemless Hosts and MagiskHide Props Config.

Any clue why this would be locking my phone up?
[Magisk] arkadius41:
Hi there. Could sb help with proper installation on my device Huawei Mediapad M3, LineageOS-17.1 & twrp-3.3.1-3. Just can't go any further and stop on that below
[Magisk] DiamondJohn:
First you question, I dont personally have a clue. Have you tried the magisk boot log?

And just to help others who have your problem, did you have to do the "fastboot flash boot boot_image..." or did the "fastboot flash boot_image.img" work (or whatever it was)?
[Magisk] daddylonglegs:
OK it seems as though my phone is locking up because Magisk somehow changed my active boot slot?

So when I flashed the patched magisk boot file, I used this command:

fastboot flash boot magisk_patched_qfngE.img --slot all

I did that because someone here recommended I try that.

After doing that, I noticed my phone now tries boot from slot A. It was previously always slot B.

I tried this command:

fastboot --set-active=b

which seemed to work, but when my phone reboots, it defaults back to slot A, which is where I get the constant hard lockups in Android.

Does anyone know what's up and what I can do to fix this?
[Magisk] Yahoo1:
Maybe wipe everything and start installation from scratch after all your mishaps. Btw the PowerShell use is pretty interesting solution of your previous problem. I mean why Command Prompt was not enough...
[Magisk] daddylonglegs:
I appreciate it but there's no way I am wiping my data. Too many important things; even just the way I have the phone set up would be a nightmare to re-do.

I think doing the fastboot flash boot magisk_patched_qfngE.img --slot all command is what screwed my phone up. "--slot all" installs Magisk to both slots and it for whatever reason changed my phone to always boot from slot A.

Is there a way to reverse this? Flash the January 2021 firmware to both slots maybe? How do I do that? Do I have to make each slot active and then run flash-all.bat ?
[Magisk] AndDiSa:
@daddylonglegs as I already tried to explain to you: the Pixel 3a has two boot slots for seamless updates, i.e.

- before the update it starts e.g. from slot A

- after the update slot B is activated and the phone tries to start from slot B

if for whatever reason the phone cannot boot, slot B will be marked as 'bad' and the phone will automatically start from slot A again.

Flashing to both slots in parallel is not needed / recommended as there is also a ramdisk / system / ... connected to slot B and if those are not compatible to the boot image you have just flashed it will mark automatically the slot as 'invalid' and will fall back to the other one ...
[Magisk] daddylonglegs:
OK thank you.

Maybe I should stop trying to install Magisk from ADB. I believe there is a way to boot to the patched image, and then install Magisk in the app? Is that correct? If so is there a link on how to install that way instead of flashing the patched boot?
[Magisk] AndDiSa:
@daddylonglegs no, you need to upload the original boot.img (which is exactly matching the OS you are running) to a running phone where Magisk-Manager is installed. Then you need to patch that image, get it back to your PC and flash it into the currently active slot (e.g. flashing without any --slot parameter). After that you can boot your phone and it's rooted with Magisk.
[Magisk] daddylonglegs:
That's what I am doing. My phone hard locks whenever it boots and Magisk is installed. Flashing the original boot.img file, my phone works fine. Flashing the Magisk one makes my phone freeze up about a minute into being inside Android 11.
[Magisk] AndDiSa:
Most likely it's related to Systemless hosts. I had this freezing from time to time, too, but since about two weeks it's working fine (even with systemless hosts enabled). Try to run without systemless hosts (at least for some time) and see whether this fixes your issues.
[Magisk] daddylonglegs:
Will my Adblocker still work OK?
[Magisk] Homeboy76:
Using a windows computer, try:

- unhide magisk

- uninstall Magisk --> Restore Images

- opening File Explorer

- click the platform-tools folder

- click the folder (left side of address bar) to highlight the address

- type cmd and press enter.

- at the prompt type:

- fastboot flash boot magisk_patched_xxxx.img
[Magisk] zgfg:
If your system is read-only (e g. A11), AdAway will not work without Systemless hosts

To disable, open Magisk Manager, modules tab, find Systemless hosts, disable its button and reboot

You can also disable by some root explorer like MiXplorer or from TWRP by putting an empty file named disable (exactly as that) to the folder:

/data/adb/modules/hosts

(always reboot)

Disabling through Magisk Manager does the same, putting that disable file.

Enabling just removes the disable file
[Magisk] daddylonglegs:
Update: phone locks up with only Universal Safetynet Fix module (v 1.1.1) installed. FML.
[Magisk] Yahoo1:
So try no modules first. And did you make sure to patch boot.img from correct factory zip file? Is it the same version you have on your phone now? I know it probably is, I am just running out of ideas here...
[Magisk] zgfg:
If you have TWRP, you can disable as was described for Systemless hosts.

This time you put disable file to the folder:

/data/adb/modules/safetynet-fix (not sure about the exact folder name but you will see)

Or disable all modules by booting to Safe Android mode, then to normal mode (you will also have to re-enable Magisk hide)

Or remove all modules by adb command - everything is described in Magisk Wiki on Github, pls read and learn 👍
[Magisk] daddylonglegs:
First I want to say thank you so much to you and all the other strangers that have been trying to help me. You have no idea how much I appreciate it. I try to pay it forward in my everyday life. :)

I definitely am using the proper boot file from the latest firmware. I checked and redownloaded a half dozen times just to make sure.

With no modules, my phone works fine. I just installed Systemless Hosts and Riru, and rebooted and no lockups. This says to me the issue is Universal Safetynet Fix module (v 1.1.1) .

This is very unfortunate because passing SafetyNet is really important to me. I can live without it for a bit and maybe the next version of Universal Safetynet Fix will not lock up my phone. But what if it does? Is there any way to just remove a single module instead of removing them all with that ADB command?

Unless I am missing something I thought TWRP hasn't worked in forever? Since like, Android 9 or something?
[Magisk] zgfg:
The adb command:

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

uninstalls all modules - but you can easily reinstall what you need

Or use Android Safe mode, then normal boot, then remove or enable modules from your Magisk Manager (you must also enable Magisk hide)

For TWRP it depends if it was ported to your device

Latest official TWRP 3.5 supports A11 but again, must be ported to your device - check on your device forum and on https://dl.twrp.me

For SafetyNet Fix google, search on XDA or scroll back for few days in this thread to find its XDA thread.

Ask there why your phone bootloops with or if there is some special test version you could try for your phone
[Magisk] Lughnasadh:
Have you tried the SafetyNet mod without Riru, just Systemless Hosts and the Universal SafetyNet Fix mods?
[Magisk] daddylonglegs:
I just installed Gravitybox and my phone is hard locking again without SafetyNet mod installed :(

I'm at my wit's end here.
[Magisk] Lughnasadh:
Maybe try an earlier version of the mod?
[Magisk] daddylonglegs:
I will try that but how do I disable individual modules? A few said to enter safe mode and then uninstall the modules in safe mode. I'm in safe mode right now and can't access any file browsers or the Magisk Manager because they are all disabled in safe mode??
[Magisk] Lughnasadh:
After you are in safe mode, reboot normally and your mods will be disabled and you can uninstall them.
[Magisk] Didgeridoohan:
@daddylonglegs Your device freezing up is very likely a known f2fs bug that Magisk (and other stuff) triggers, although it's not directly related to Magisk. You'll need a kernel that fixes it.

Details here:

https://github.com/topjohnwu/Magisk/issues/3171
[Magisk] Lughnasadh:
Ah, I thought the issue was fixed in 21.3. I guess not for all phones or al scenarios.
[Magisk] zgfg:
I described you in two posts, boot to Safe mode, then to normal

Then manage your modules in Magisk Manager - and don't forget to re-enable Magisk hide

All is described in Magisk Wiki - link to Github from Magisk Manager
[Magisk] Didgeridoohan:
Some f2fs stuff was fixed in v21.3, but this is a driver bug that Magisk can't fix (described in the linked issue).
[Magisk] daddylonglegs:
Holy crap you are a genius and savior! Thank you so much!!

I just checked to see if Elemental X would be good enough for a new kernel but apparently it's not? What kernel am I supposed to flash to my phone?
[Magisk] Didgeridoohan:
That info you'll find a lot easier in your device's forum...

Edit: if nothing else you can always point the kernel developer to the issue I linked so that they'll know how to fix it.
[Magisk] Lughnasadh:
See if Kirisakura is available for your phone. freak07, the developer, is mentioned by John Wu in that issue Didgeridoohan pointed out and I believe he's implemented a fix in his kernels for this issue.
[Magisk] shorbah:
any assistance please !
[Magisk] nigol:
Hello, I wanted to install Magisk-v21.1 version on my Xiaomi MI 9T Pro with MIUI Global 12.0.4 Stable (QFKINXM) using both OrangeFox-R11.0_1-Stable-raphael, and TWRP-3.5.0_9-0-raphael.

Well, when you restart, instead of restarting in System, it restarts in Recovery. how to solve wanting to use the smartphone in ROOT mode?

Thanks

nigol