yashsingh1/xdaforums huggingface dataset:
[Magisk] jcmm11:
I'm feeling generous (via Google translate):

Me siento generoso (a través de Google Translate):

"Thanks to everyone beforehand ............

I have a Huawei P20 Lite android 8.0 with TWRP and Magisk 18.0 and I would like to know how I can install the latest version of OTA, that is, the officer who sends you the phone but I can not for fear of loading the system or root, the case is that I can not find any videos and in Xda Developers if you do not write anything in English and look to use the translator and destroy the phrases ... I do not know if you understand me

PLEASE Help and THANKS"

I can't help you with the OTA since I don't have a Huawei. In the future you can post in Spanish but you should include an English version even if you're afraid a translator will destroy the phrases. The translation above appears a little mangled but it's understandable.

No puedo ayudarte con la OTA ya que no tengo un Huawei. En el futuro, puede publicar en español, pero debe incluir una versión en inglés, incluso si tiene miedo de que un traductor destruya las frases. La traducción de arriba parece un poco destrozada pero es comprensible.
[Magisk] Hacker?pcs:
I'm on Xiaomi Redmi Note 6 Pro on stock MIUI (V10.0.5.0.OEKMIFH (MIUI10)). I unlocked the bootloader (and had the forced factory reset), flashed the DM-Verity, ForceEncrypt, Disk Quota Disablers and then flashed magisk via TWRP. I don't get any superuser rights even though I set it to auto grant permissions, apps like Root Verifier and Adaway from F-Droid halt a little when they're supposed to be granted su rights, they don't get them, I get the toast message that they were denied su rights, they're not listed in the Superuser in Manager but in the Log in Manager they are listed as denied. Log:

https://pastebin.com/RQLJBwrJ

I tried flashing the uninstaller then again flashing magisk without success. Also tried 17.3 without success too
[Magisk] ilkaayy:
I installed the v18 through TWRP yes.

Should i install the Magisk that I found on highonandroid for the Resurrection Remix Rom OVER this magisk through TWRP? Isn't that going to be an issue?
[Magisk] muttonhead411:
Hi everyone,

I have a question... if i install a custom kernel on my device (Pixel 3, non XL), will it break the simplified OTA update process described here?

Thanks in advance
[Magisk] bafforosso:
modules, not Magisk v18...
[Magisk] mayur.3.92:
Strangely magisk hide stopped working on v17.3 as well.
[Magisk] jcmm11:
Assuming you installed the custom kernel after installing Magisk then no. After you've applied the OTA and rebooted you'll have to apply the custom kernel again since you'll have a stock+Magisk kernel.

If you applied a custom kernel before initially applying Magisk then the OTA update, as described, won't work because when you restore images via Magisk (as per the instructions) the restored image will be the custom kernel (minus Magisk). That won't pass the OTA verification checks.
[Magisk] Nebrassy:
And that's why Magisk should allow you to pick the stock boot image to restore, because some kernels will break Magisk so you have to flash Magisk after flashing the kernel, and on a/b devices you need to flash twrp first
[Magisk] bafforosso:
As explained by [MENTION=4470081]topjohnwu[/MENTION] (Magisk lead dev) you should not flash TWRP on A/B device but only boot the image from a computer when you need to :

https://twitter.com/topjohnwu/status/1070029212428439553
[Magisk] Nebrassy:
I don't see a reason why I shouldn't flash twrp when I'm not facing any problems, why would I force myself to use a pc every time
[Magisk] bafforosso:
Could you please make the effort to read links before answering?

https://twitter.com/topjohnwu/status/1070032037870997504

And the practical example was the first tweet (just on top of the one in my last post) :

https://twitter.com/topjohnwu/status/1070028072181743618

But then you can do whatever the F* you want with your device, but please refrain from giving advice that could easily break other's.
[Magisk] jcmm11:
Or just don't bother flashing TWRP to the phone and just boot the image via flashboot as needed

https://mobile.twitter.com/topjohnwu/status/1070029212428439553

Edit: Lots of ninjas running around today ??
[Magisk] itylermartin:
Might be a silly question.

When you first clean install magisk. It asks you to install a module for something by default.

I just uninstalled all of my modules to troubleshoot an issue I was having.

Now I can't figure out what it was that magisk recommended I install on my first boot up.

What was it and do I need it?

I feel dumb BC I can't remember
[Magisk] psgbharathi:
I am in 17.3 version of magisk on Liquid remix android 9.0 max Pro m1 phone.

Systemless host option toggle/button is not showing in my version

I have deleted and flashed many times still issue not solved.

Any help?
[Magisk] bafforosso:
Probably "Systemless Hosts" if on v18?

If it is this one then it depends if you need to modify hosts file : if you are using any kind of adblocker then you probably do need it.
[Magisk] martyfender:
It is probably the new systemless hosts module. go to the Magisk Manager settings, click on the systemless host options and you should see a toast: "added systemless hosts module". Just like any other module install, you will need to reboot for it to be active.
[Magisk] Nebrassy:
I already saw those tweets, I follow him on Twitter, still, all those problems are easily avoidable, he wouldn't flash anything without a pc, that's up to him, you should respect devs' opinions, not worship them.

Even if you did so, such an option is needed in the case of a custom kernel that breaks Magisk, or if you wipe data while Magisk is installed, doesn't it it feel wrong to get an error message saying that stock backup doesn't exist and you can't select it when you can select a boot image to patch? (which is also backed up, presumably)
[Magisk] jcmm11:
You sure you're on 17.3 and not on 18? The attached image is from 18. The toggle is gone. Just click on 'Systemless Hosts'. Magisk now installs it as a module. You'll have to reboot to have it take effect.

Once installed it shows up in the module list like any other module.
[Magisk] martyfender:
Starting with Magisk v18, there is no longer a toggle for the systemless hosts option. You click on it in MM settings then you should see a toast: "added systemless hosts module". Just like any other module install, you will then need to reboot for the module to be active. To toggle it off, you would disable it in modules, then reboot for it to take effect.
[Magisk] psgbharathi:
Yeah am sure am on 17.3 and latest MM manager.

Yeah it gave a toast and installed the module but in terminal

If I enable any adblcok like energized it's showing please enable the systemless host module.

What should do ?

---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------

But it's not recognising it in terminal app.
[Magisk] jcmm11:
I have backups of boot images in my sdcard so if I can boot and have su available I can restore a different working image (I use FKM for that, EXKM is another option) or patch stock.

If I ever broke Magisk then I'd have to boot TWRP to fix it, or at least still use fastboot to install a patched (or backed up) boot image.
[Magisk] Nebrassy:
I have backups on SD too, I wasn't aware you could flash boot images with exkm, what I said was within the context of receiving ota with Magisk, it is easy enough to just flash stock boot with twrp, but there is an inbuilt option to do that within Magisk, it just doesn't work in many situations, I think my suggestion still holds up, it's a simple fix.
[Magisk] Bulbulz:
Helooo...

I have problem when install magisk18.

After flash magisk on twrp, my device always booting to recovery mode (TWRP).

Anyone can help me to solve my problem?

My device Xiaomi Mi Mix 2s.
[Magisk] jcmm11:
I'm making an assumption about EXKM. I know for sure you can with FKM.

Now the one thing I wish FKM would do that it doesn't is enable me to choose the inactive slot to flash to. That would come in handy for OTAs. Although to be honest at the moment I just download factory image, remove -w, then run flash-all etc.
[Magisk] Jaheen:
I have magiskhide issue with v18.0. Today Phonepe app became unusable, went back to magisk v17.3 and phonepe became active.

Could be magisk v18.0 still leaks in root detection.

Magisk has done a long way great support for all of our device.

Thank you Developer!!!

---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------

Try wiping dalvick cacher before system boot.
[Magisk] bafforosso:
Again, I couldn't care less about what you personally think or do with your own device(s). This is a public forum and you should stop thinking selfishly and start realizing that there are many users reading your posts with very diverse devices, configurations, backgrounds and technical knowledge. First step about respecting them and the devs (even more in their own software's help topic) is through posting the safest solution possible for a problem and not the most comfortable for your own specific use case.
[Magisk] Nebrassy:
Yeah I do the same, I've had enough of stupid fore encryption, still it would be useful to have it in Magisk

I've asked for a Magisk option that doesn't work as expected, I didn't recommend people to flash twrp, I said that I would like to have the OPTION to do that, yes, flashing twrp can cause problems, no, that doesn't mean the solution is not flashing twrp, it's to fix the problem with Magisk, because twrp is not the only thing that can cause this.
[Magisk] nmyshkin:
no root and no custom recovery option

I recently got a new tablet (Alcatel3T 8) free when I refilled my emergency phone for another year. Not such a bad deal!

I'd like to root it. I'm not a complete noob, having flashed many custom ROMs and even done some patching of jars, etc. But...this statement in the options for installing Magisk contains a world of aracana to me:

However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN

I've been doing a lot of searching and reading in the past couple of weeks. I know what a boot.img is, but have never extracted one myself. Nothing I've read so far makes me feel like I now know any better how to begin. So much of it seems focused on a specific device (or requires root--Catch 22). As far as the flashing goes, I've never used fastboot (successfully) before, although I have it with my adb, and while I'm generally up on my Norse mythology, I'm thinking ODIN is not that kind of reference. So...mystery there.

There are no firmware zips available for the device that I am aware of. It's just too new, so no extracting boot.img from that.

I can access the tablet via adb. I have selected the option to enable unlocking of the bootloader (Warning, Will Robinson! Danger!) but there must be more that is needed to be done there.

Can someone point me in the right direction? Like I said, I'm not a complete noob, but it would be nice to find a set of instructions rather than a "you need to..." with underlying assumptions that anyone should be able to fill in the blanks :(
[Magisk] ekowwillis:
Well I did the ff as suggested:

1. restored boot.img

2. temp boot to twrp

3. flashed Magisk v18.0(1800)

But the problem is still there.

The phone gets stuck on the charging screen when i put it off and I try charging.
[Magisk] breedmedaddy:
Hello

Seems like the boot.img from V18 is too big for my device's boot partition. V16 works just fine but am I technically barred from future updates because the new img are bloated?
[Magisk] theo2:
Problem with reinstall of magisj:

I deinstalled Magisk for same reason (i thought that torch was not running because of versionupdate to 18)

I deinstalled it and all other Apps for ex. Supersu deinstalled too.

I went to twrp to Flash Magisk again. But i get in twrp the failure message: "cannot Be installed - failure 1"

What can i do? I ve had Backup the whole Rom Same months ago? Can These Backup help me?
[Magisk] jcmm11:
ODIN is only relevant if you have a Samsung device.

I suspect you're out of luck until you can get some official images or TWRP is created for your device. Right now you're in a catch-22 situation. adb needs root to access the partition you'd need to copy to get a boot image. The command you would probably need (also assumes they're using standard Android by-name conventions) is

dd if=/dev/block/by-name/boot of=/sdcard/boot.img bs=1000000

if your device is a slot a/b device then the if file would be boot_a rather than just boot.

---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------

Copy and attach the install log from TWRP. Or restore stock boot image and try again.
[Magisk] estapagu:
After reading many post in several threads, I think there's something weird about the last update. We are a lot of people on the same boat, cannot be a coincidence. I started having SafetyNet pass for a few minutes and then fail afterwards since updated to magisk 18.0 / 6.1. The only workaround that solves the issue for me: Clean downgrade to 17.3 / 6.0.1

No more safetynet fails at the moment
[Magisk] nmyshkin:
Thank you. I was beginning to suspect I was SOL--at least for the time being. I came across the dd command earlier and bookmarked it. But as you say, Catch-22.

Whew. Now I can stop looking :)
[Magisk] Pkt_Lnt:
Probably true. However so much talk, NO logs...... nada, zip, zero, zilch
[Magisk] Hacker?pcs:
Regarding my problem

I can pass safetynet pass without a problem with v18 (clean install though)
[Magisk] Goobly:
Moto G1 "Your kernel doesn't support mount namespace :("

I'm using a Moto G1 falcon. I'd appreciate help fixing this not able to mount namespace please

Edit: Found the namespace change stuff but I'm in need or clearer directions of how to
[Magisk] zooorgie:
What I wanted was to replace SuperSu with Magisk. And I still want that. I dont have Supersu installed.

1/ I have Lineage 15.1 installed.

2/ I HAD TWRP installed, but every time Lineage wants to update, and I restart the phone, it removes TWRP.

So I dont have TWRP or Supersu, and root is gone.

So how do I now get Magisk and keep Lineage ?

And root
[Magisk] Nebrassy:
In this situation I think the only option is to capture an ota link and extract, but I doubt it's getting that many updates
[Magisk] jcmm11:
What's the device? If you posted it previously I don't feel like tracking it down
[Magisk] theo2:
Hopefully...
[Magisk] jcmm11:
That would work, and count as an official factory image. Apparently it's a new device just released in October or thereabouts.

---------- Post added at 11:05 PM ---------- Previous post was at 10:58 PM ----------

Did you get that log right after attempting an install? I don't see anything in there telling me it tried to install anything.
[Magisk] theo2:
Log from Magisk installer
[Magisk] villo88:
And it's working now. Really thanks, also automagisk is very good..

Inviato dal mio Redmi Note 2 utilizzando Tapatalk
[Magisk] SidneyD:
I restored my backup; unrooted via SuperSU; rebooted to recovery; mounted /system rw and removed /system/bin/su and /system/xbin/su; flash the following in order: Magisk-v6.zip, phh-superuser-17-magisk.zip; did NOT wipe cache/dalvik; reboot; (process list is nuts again because SELinux is permissive), install phh's SuperUser from Google Play Store, install Magisk_Manager_v1.2.apk; open Magisk Manager and try to toggle root off, and try to toggle SELinux to Enforcing; in both cases the toggle just bounces back after a second. I am never prompted to grant root to Magisk Manager. This is what happened the very first time so it seems that wiping cache/dalvik has nothing to do with the issue.

I have no idea why my SELinux is being set to Permissive. All I know is that Magisk v6 is what caused it to start in that mode. Do you know how to configure it to start SELinux in Enforcing mode?
[Magisk] kemz_a:
Question. Let's say I'm using a custom kernel. If it gets updates. Will it be ok to flash the updated kernel without having to go thru the same steps like I had to do with the initial install of magisk?
[Magisk] TheMysticle:
My fingerprint scanner stopped working after installing magisk

Hi!, I'm currently running cm13 on my telephone p9000 and as you may guess I need this to play pokemon go but there is an issue ever since I installed magisk my fingerprint sensor just dissapeared of the list as in its not even an option in security anymore. And yes I did check does it work with cm before installing magisk v6 I hope somebody could help me with this because the fingerprint sensor really did make my life easier in terms of security. I also uninstalled and reinstalled magisk and cm multiple times still nothing. Is there a way to fix this? Or will I have to pick between pokemon go and my fingerprint sensor.

Thanks,

Oliwier
[Magisk] TheSaiyan:
Thanks for answering. I'll post again if something goes wrong on v7.
[Magisk] juangcardoso:
Well... I'm facing the same issue...
[Magisk] Battery03:
I'm running Magisk and Xposed and Pokémon Go 0.37.1 is working. You can see at the top flat style bar indicator module running.
[Magisk] Dalamar666:
wow! latest versions?
[Magisk] aIeck:
Magisk & CM nightlies

Hi all, this has been a very helpful thread. I'm using Cyanogenmod nightlies with TWRP. When I flash a new nightly, do I also have to reflash Magisk, PHH SuperUser and Xposed?
[Magisk] Battery03:
Yes, Sir.
[Magisk] Dalamar666:
And pass safety net test?

Could you provide more information? Root Unmounted, systemless xposed enabled? :0

thanks!
[Magisk] Battery03:
Actually, I don't know how to do that test xD but I will search about that as soon as I can. About the other questions, yes root unmounted and yes systemless Xposed enabled.
[Magisk] Dalamar666:
the test is using this app ;)

https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

It's makes a request like the apps that are trying to detect root/xposed.

thanks again!
[Magisk] unknown00:
think you might be the only person in the world that has it working, unless you did something special?
[Magisk] Battery03:
Fail. It did not pass.
[Magisk] Battery03:
Mmm not really. I just did all the steps listed here. But I didn't pass the safetynet test. I don't know what's going on xD
[Magisk] Dalamar666:
haha incredible xD

The error is for xposed... but if you can play pogo... =O
[Magisk] unknown00:
exactly that's my point. fail safetynet test and still can play pogo? you are the only one in the world LOL
[Magisk] chris9000:
I'd love to know of a way to be able to run xPosed without it conflicting with PKGO's playability. It's a hassle to disable the framework and reboot the phone.
[Magisk] Dalamar666:
maybe the Safetynet update is like PoGo updates... 3/4/5 days to reach all the world o.o and the pogo still makes the old request
[Magisk] theo2:
Yes, i saved the log after try to Flash Magisk with twrp.

But Look at the Magisk installer log...
[Magisk] ktmom:
The Magisk log is saying the boot.img had already been modified. Did you restore a stock boot.img before trying to flash again? That's where you're at, restore a stock boot.img and do a clean install of Magisk. Save the recovery log before booting to system and post it if you still have problems.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
[Magisk] zooorgie:
Its a Samsung Galaxy S5 SMG900F
[Magisk] theo2:
I solved my Problem!

Just flash with fastboot

Fastboot flash boot boot.emmc.win

File "boot.emmc.win" found in twrp Rom Backup

Now i can Flash Magisk 17.1. And my first Problem with Magisk 18 solved too... Torch is running again.
[Magisk] MyStyle0714:
Did anyone using Pixel phone or Oneplus 6/6T face the problem that couldn't charge when power off? It will stuck at charging icon even when plug off the charger
[Magisk] jcmm11:
Unfortunately I don't do Samsung. But I think you have 2 options.

1) figure out how to get TWRP installed and stay installed. The TWRP thread for your device can probably help

https://xdaforums.com/showthread.php?t=2727406

2) get a clean boot image, patch it via Magisk Manager (choose Install, Install, patch boot image file) then install the patched boot image using Odin.

Even with TWRP you need to make sure that you have a clean boot image installed first, otherwise Magisk won't install.
[Magisk] xunholyx:
I think you mean fortunately. :D
[Magisk] ekowwillis:
Yep have that same issue even after removing twrp and temporarily booting to twrp to flash Magisk v18.0
[Magisk] jcmm11:
?It's not easy - being green ? ?
[Magisk] Bulbulz:
No work still looping to TWRP :(
[Magisk] LinoX:
patching a boot image does

NOT

work on magisk manager 6.1 I even posted the logs a few days ago.
[Magisk] aj_killer:
I am facing a problem with Whatsapp, It's breaking the SafetyNet and allowing all other apps to detect root. However, the moment I uninstall whatsapp, the safetynet check passes and everything works fine as before installing whatsapp. I hid whatsapp using Magiskhide even before its first run but it still detects a custom rom and thereby breaks the safetynet.

Anyone having similar issue?

(I don't know whether this thread is the place to ask this question or should I make a new thread for this?)
[Magisk] ce8866:
Redmi Note 4 MTK bootloop

Hello everyone. I was using Magisk v18.0 in my Redmi Note 4 MTK with MIUI 9 and it all was fine. But after upgrading to MIUI Global 10.1 Stable, and flashing Magisk v18.0 with TWRP my phone gets a bootloop, just as it happens with MIDO. Does anybody know if lazyflasher will solve this?. Thanks.
[Magisk] bafforosso:
If it loops to TWRP it means TWRP is indeed installed on your device. You may want to start from a clean base by restoring stock firmware then try to install Magisk by booting TWRP image (.img file) (and not flashing TWRP zip) :

1. In Bootloader mode : "fastboot boot /path/to/twrp.img"
2. Flash Magisk zip
3. Reboot
[Magisk] zooorgie:
I have only found one boot image for this particular phone that should work for Sweden.

So I thing I stick to that.

I dont know what defines a "clean" boot image anyway.

I have no problem installing TWRP, but I will ask at the link you shared about why its getting deleted.

The version there is 2.7 though, and the version I found before is newer 3.2.3

Why use an old one ?
[Magisk] kryshnakishore:
https://play.google.com/store/apps/details?id=com.infrasoft.uboi

Bank app, is there any fix to make it work, even tired on v17 too but as soon as I open hiding the app in magisk it says device rooted

OnePlus 6, android pie, oxygen 9.0.2
[Magisk] ktmom:
A "clean" boot.img means one that is completely unmodified from stock. The reason is, any previous modifications could interfere with the installation of root. Installing TWRP first, modifies the same boot.img that root must install into, potentially creating an unstable environment and contributing to Magisk install failures. This is why it's been encouraged to fastboot boot TWRP, instead of installing it.

In the case of a boot.img that is downloaded from any source that is not the original to a ROM, it's also possible other modifications have been made as well. This variability is the responsibility of the device owner.

Particularly for people who are having trouble, installing Magisk into a completely "clean"/ completely stock boot.img is the first step to identifying problems. The next step is to save logs from the installation and post those when asking for help.

As far as the TWRP in the provided link being older; determining which TWRP is suitable for your device/setup is a job for the device forum. *Usually*, there is only one thread for TWRP releases in a device forum and updates are followed within that thread.

"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini