yashsingh1/xdaforums huggingface dataset:
[Magisk] p-walker:
I don't want to be rude and I appreciate you trying to help. However everything you said didn't help me at all :-/ Yes the A2s are A/B devices. Yes any Custom Recovery will break OTA updating for the simple fact that the recovery lies inside the boot.img for A/B devices. You cannot have custom recovery without modifying your boot partition, thus breaking OTA.

Againg, it's nice that you try to help here but I was actually looking for someone that actually knows how the android update-engine works and why OTA updating isn't breaking if I for example edit the hosts file which should be part of the system partition and should also be detected by OTA updates in theory.
[Magisk] chooks06:
Understood mate!

And, no you're not being rude. I wasn't really able to help, just trying to get a better idea of your situation..

Thanks for the clarification! I'm hoping to learn something too!

Cheers!
[Magisk] jcmm11:
[MENTION=6323980]chooks06[/MENTION]

First off I don't have Xiaomi (I have Pixel), so I'm generalizing about OTAs, but (especially if your phone runs basically stock Android) everything I'm saying should be accurate.

What exactly does modify system mean? This one is fairly simple. You'll probably fail an OTA check if you've even mounted system (or vendor) as rw - even if you didn't actually change anything. Any actual change (even if later reverted) will definitely cause a failure.

AdAway, if you've activated systemless hosts in Magisk and are running AdAway in systemless mode, does not actually modify system. Magisk creates a copy of the hosts file, which it then mounts on top of the existing file. This hides the original file and all changes are applied to the copy. So it only appears that you're modifying a system file. In reality the "real" system file is untouched.

This same method, basically, is how Magisk works with any system files.

As far as removing vendor apps like camera it depends on where they are and how you remove them. If you can remove them using normal uninstall methods you're fine - they were installed in the data partition.

Unlocked bootloader is not an issue, Magisk will hide the fact that your bootloader is unlocked so the OTA can proceed.

You do not have to remove Magisk in order to apply an OTA.

If you're running a custom kernel that will prevent am OTA from applying.

If you've installed TWRP to the phone that may (probably will, but not 100% sure on this one) prevent an OTA from applying.

See also https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Hopefully this answers your questions
[Magisk] skinnykhalida:
"Magisk not installed" after update 18.1

Alright so I was using:

ROM: The Galaxy Project for Galaxy S7; Version 2.5.1; Firmware Base: 8.0.0 Oreo G935FXXS3ERI1; TGPKernel Base: 6.10.3

Baseband Version: G930W8VLS5CRJ1

Kernel Version: 3.18.124-TGPKernel.S7.6.10.3

But I had a lot of troubles getting YT Vanced to work because it suddenly disappeared, so i decided to upgrade my Rom to the newest version 2.7.0.

Everything was all good except of course i had to update Magisk. So i used the regular installer in Magisk Manager flashed it in TWRP and upgraded to Magisk 18.1 and Manager 7.0.0.

Now it says "Magisk not installed" and said there's another update, so i installed the zip and installed 18.1 (18100).

I am still getting the error saying Magisk is not installed BUT the weird thing is apps still request root access and the prompt comes up just fine and works.

:good:I ensured that Magisk is ignored by Greenify and any other battery optimization apps.

:good:I did NOT hide Magisk from itself in MagiskHide.

:good:I reinstalled Magisk using the zip in TWRP like 100 times (both 18.1 and 18.1(18100)).

:good:I used the uninstaller and tried reinstalling.

:good:I checked the FAQ and tried to follow the method with installing the boot.img but after waiting forever unzipping the TGP Rom package there is no such file in there and any .img file i try does not work

:good:Even tried unzipping the Magisk installer zip and tried patching the magiskboot.img under the folders labelled 'arm' and 'x86' but I got an interesting error:

Now I would read up on this Bootbridge method but I do not have a Sony device so I don't know why it's saying that.

I'm enjoying being rooted but I'd like to use my modules as well. Does anyone have a solution to this?

My Device:

Samsung Galaxy S7 G930W8

ROM:

The Galaxy Project for Galaxy S7 version 2.7.0

Thanks in advance!
[Magisk] Didgeridoohan:
From the size of that file it indeed looks to be smaller. Unfortunately XDA is acting up and I can't download the attachment. Will try later...

If you had the Manager repackaged when updating that will be the reason. There's a bug in the previous release so it can't update the Manager properly when hidden. Uninstall any and all Managers (there might be two) and reinstall it manually. That might work...
[Magisk] dvhttn:
Works fine for me. Stock based Oreo rom on an S7 running Magisk 17.3. Have you searched about Lloyds and Santander apps and blocking various websites? I used AdAway to block these:

# This hosts file contains exported entries from AdAway.

127.0.0.1 cem.lloydsbank.co.uk

127.0.0.1 mupdates.trusteer.com

127.0.0.1 trusteer.com

127.0.0.1 fins.trusteer.com

127.0.0.1 dyknreymc91ut.cloudfront.net

Just add them to AdAway's 'Your Blacklist'.
[Magisk] chooks06:
Thank you for the insight!
[Magisk] p-walker:
Thank you that helped me a lot. However I wasn't even aware of the systemless host feature and had not enabled it. I assume it was not enabled by default, thus adaway was altering the real hosts file. However my OTA updates still worked without problem. How could that be? Is it possible that the vendor disables certain block checks, for example if Xiaomi doesn't really care about altered real hosts files.

Which also leads me to another question.

Do root apps have a way of recognizing that they are using the "fake" system?

On the other hand would any other root app even care that they are not using the real system files.

I assume Magisk does only fake certain system files that's the reason why I have to manually enable the systemless hosts module, correct?

Does a passing safety net check equal to OTA update installation won't fail? Or is it possible that the update-enginge does some checks on top of what safety net is doing to check for root? Or is it not related at all and it is possible that some vendors don't even use safety net checks befor OTA installation?

(currently my safety net is failing after my OTA update from yesterday, but maybe it was already failing before, I haven't checked)
[Magisk] TacoShow:
Btw, I forgot to ask (this question is for anyone reading): why does MM install itself on SD card when using portable adoptable storage, while it is known that MM can't manage Magisk SU when installed on SD? Does not make a lot of sense.

I posted later that for me the issue was portable adoptable storage. Using portable adoptable storage, MM installed itself on SD, which I did not know, and MM may not be installed on SD in order to manage Magisk SU, which I also did not know until I did.
[Magisk] pa.pn2:
guys i uninstalled magisk in twrp using uninstaller zip

i flashed kernel and latest magisk 18.1 zip in twrp but now i cant install the damn magisk manager anymore.

never had issues before.any idea what to do?

there seems to be a manager app installed,but i cant see root in file manager anymore because i think i lost root somehow...

im on pixel 2 xl

mhh it seems even if i flash magisk zip in twrp i dont get root anymore.its weird...
[Magisk] guest4711:
AdAway runs systemless when "Systemless Hosts" is enabled in MM. (The option in AdAway 3.x is grayed out). So your real host file is not touched.
[Magisk] fredfox_uk:
Thank you, and thanks, and much appreciated, and thank you - I'm most appreciative. This worked for me :D
[Magisk] guest4711:
They could iterate the list of mountpoints to check wether the path they are eorking on is an overlay of /system.

Magisk does not protect /system in any way. But it gives us the option to mount some files (or directories) on /system so everyone can use these. This does not alter the content of the /system partition, so their checksum is not altered. The OTA engine uses the checksum to ensure it may patch the ROM without trouble.
[Magisk] zputnyq:
Hello everyone,

I have a problem with the latest magisk stable. I used to flash it using twrp. Installation for v18.1 is succeed based on twrp's log but Its MM doesn't appear on my device. I checked it using flashable SUmount script by, its files & folders are exist. I thought it was kernel problem, so I decided to change my device kernel but it's the same. However, previous version v18.0 has no problem.

Any solution for this? Or probably someone could point me safe link to download magisk v18.0?

I don't have a backup for v18.0

My device is Xperia M4 stoxk 6.0.1
[Magisk] hammerhead2:
Of course I used systemless xposed. I might be wrong I'f course, but AFAIK it's pointless (corrected myself) to use other xposed than systemless with magisk.

I am on stock. Currently with twrp and magisk with phh's root and no xposed installed. Used adb to boot to twrp after I flashed it with Odin, since when booting to recovery with homepowervolume it got overwritten every time.

To prove it...
[Magisk] KyeWalker:
So, our beloved friend "Google" has updated Safety Net to detect "Systemless Xposed" there for Android Pay, Pokémon can not be used on custom devices.............. Again!!!!!

Using GT-I9195 running CM13
[Magisk] pharmdeon:
no, only if using systemless xposed. If you turn it off, all work fine (at least pokemon cause i am not having a problem)
[Magisk] thenewnazy:
when selinux enabled in aggressive mode the root is lost. any suggestions?

SuperSU -> automatically loses

phh súper user -> the root is lost when restarting

Galaxy S3 I9300

Cyanogenmod 13

(sorry for my bad English)
[Magisk] FxSxKx:
How to turn off systemless-xposed?
[Magisk] tslim2696:
So how to turn off the systemless xposed framework without uninstalling it?
[Magisk] FxSxKx:
Same here, somebody?
[Magisk] esrvR:
In xposed
[Magisk] kemp7:
Seriously? Keep Root Toggle On inside Magisk, then go to Xposed Installer, in the Framework tab there will be a Toggle called Xposed Status to turn it off, then click on the 3dots Icon on the superior right side and select soft reboot, you'll lose all functionalities from modules, open Magisk, turn root toggle Off, open game, GG.
[Magisk] tslim2696:
Lol? That is useless, nearly as same as uninstalling it. I am looking for a way to disable it without rebooting.
[Magisk] kemp7:
You can only disable it by rebooting, I didn't found any other way, framework must be up and running to the modules work.
[Magisk] alroger:
LOL!

It modifies the whole UI framework, how do you think you can disable it? Soft Reboot only restarts the GUI.
[Magisk] tslim2696:
I am looking to disable the framework without uninstalling or disabling the framework WITHOUT the need of rebooting. Rebooting every time you need to play the game is to frustrating.....I guess I gonna use my old phone for Pokémon only..........until OP discover a fix.
[Magisk] kemp7:
do you understand that actually theres no way to do what you want? you can still play the game, just do a SOFT reboot before and just activate Xposed Framework when you stop your PoGO session, then go cry to the Niantic Devs about their decision.
[Magisk] pharmdeon:
I dont use it so cant tell u exactly but look around post 3047 ... the thread was talking about it there

http://xdaforums.com/showthread.php?t=3432382
[Magisk] Heisenberg:
[size=+1]Thread cleaned.

1. Whether or not people should be using cheats with PokeMon Go is not a valid topic. If you don't like people using it, just ignore their posts, you don't need to go all "moral police" on them. Just move on.

2. I have created a separate Magisk + PokeMon Go thread here:

[Discussion] PokeMon Go Magisk Discussion Thread

This has been created to reduce the amount of clutter in this main Magisk thread. Please direct all PokeMon Go discussion there.[/size]
[Magisk] JudgeDread11:
Deleted
[Magisk] BIGWORM:
https://i.ytimg.com/vi/jmNU8blUwms/maxresdefault.jpg

Stay out of my territory.
[Magisk] ftarules:
Phh Superuser thread lists version 242. The link in the OP of this thread with Magisk compatible version of phh Superuser lists v17? Could someone clarify for me? I think phh had released a better Superuser version. How do I make it work with Magisk.
[Magisk] Didgeridoohan:
Fun fact: The Magisk Manager is actually set up to

not

install to SD... But apparently that means nothing to Android.

https://github.com/topjohnwu/Magisk...06cc6a3b/app/src/main/AndroidManifest.xml#L13

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
[Magisk] pa.pn2:
have the same issue.

uninstalled 18.1 via uninstaller zip in twrp

flashed kernel+latest 18.1 zip but no MM anymore

even with 17.1,18.0 no success

have no idea what to do. at least i will do a factory reset but maybe some has a fix....there seems to be a installation somewhere..

---------- Post added at 21:50 ---------- Previous post was at 21:48 ----------

that did the trick

your my life saver lol.thxxxxxxxxxxxx
[Magisk] jenslody:
Check if MagiskManager is installed in external/adoptable storage, if yes, move it to internal.
[Magisk] tommo1982:
Does the new 7.0 Magisk Manager require boot.img to install the latest Magisk 18.1? Even though I have ver. 6 and it never asked me for it since I rooted the device.
[Magisk] Badger50:
Depending on your device, you may need it, then again, you may not. Usually you can just update to both from within the magisk manager app.
[Magisk] martyfender:
If you are truly using portable storage, vs. adoptable storage, it should not install on the external SD card. Are you perhaps confusing adoptable storage with portable? That is of course, you don't mean, the internal sd card, or emulated storage. I believe the external storage also uses emulated storage, with the fuse file system. If I have this wrong, please elaborate and educate us all.

Thanks
[Magisk] TacoShow:
Goddamnit... I meant to say adoptable storage. My mind thought adoptable, but for some reason my fingers wrote portable.
[Magisk] martyfender:
Thanks for clarifying that. I have never used adoptable storage, so I have never had that issue. I, however, do use Apps2Sd. My external SD card has 2 partitions, the first, is formatted as FAT32, the second partition is formatted as EXT2. I have some apps moved to this external SD, but I only move apps such as big game apps to this partition. In settings, I could have all apps moved to the External SD, but I do not have that option set, in settings. I do not want to be locked to adoptable storage.

When you use adoptable storage, does it not give you the option as to where to install your apps?
[Magisk] soder:
Sorry for not reading all the posts, but even though I've updated both Magisk and Magisk manager to latest version on my OP6T I'm being notified about a new version of the Magisk Manager.

What shall I do to get it right?

/Söder

/Söder
[Magisk] Didgeridoohan:
Could be this:

https://www.didgeridoohan.com/magisk/Magisk#hn_Updating_from_v18.0_to_v18.1
[Magisk] soder:
But it looks like I only got one version installed?

Also, I can't find that option about renaming the Magisk Manager. Where is that option? I know I just it before, so it ight be related to my problem now.

/Söder

/Söder
[Magisk] Didgeridoohan:
I actually added a new bit of info about that to the guide right before your post... The new Manager isn't recognised by Magisk so it'll be automatically uninstalled by the old Manager.

You'll find the option to hide/unhide the app in the Manager settings.
[Magisk] soder:
Thanks. I now saw that I still was on version 6. Now I uninstalled it, and kept v 7. But that version ask about some extra download and that setup will fail.

/Söder

/Söder
[Magisk] soder:
Also there's a lot less options in this version?

/Söder

Edit: a reboot worked...

/Söder
[Magisk] tag68:
This was discussed in the Moto Z Play forum, in TWRP thread.

Please read the last pages of the thread, and follow up there if necessary.
[Magisk] chinchulin01:
Thanks a lot for your answer. I added the hosts to AdAway, rebooted, deleted the storage of the app, registered or using the 4 digit password and the phone call and got it to work... once. I could use it going through that process (minus the host file) before, so not much of an improvement.

https://imgur.com/a/aNf0VLC

Some other apps are able to see Magisk even after selecting them in the Hide menu.

I'm using Samsung's Android 8 and the most updated version of Magisk.
[Magisk] guest4711:
So try hiding MagiskManager by repacking it to random name (settings-> Hide MM) and load "MagiskHide Props Config" module. Reboot. Configure the module using terminal shell (su -c props). Reboot. Clear cache of your banking app. Start the app and report.
[Magisk] jackagria:
i think you just need install mm apk :)
[Magisk] badabing2003:
I also have a similar issue.

To be thorough here are the full details:

Before updating to the latest firmware (Pixel XL PQ2A.190205.003, Feb 2019) I was on magisk 18.0 but with the latest manager 7.0 and things were working fine.

Magisk Manager was not hidden. (I had problems with hiding in the past and since then I never hide anymore)

I first flashed the magisk uninstaller (20190402) in twrp (without actually uninstalling the Magisk manager) and proceeded to flash the firmware and then eventually magisk 18.1

On first boot to system, Magisk Manager was not automatically installed and root was not detected.

On second boot, Magisk Manager got installed and root was detected (not sure why that happened)

However right after that, Magisk manager started reporting that Magisk was not installed.

Each time I rebooted, it first detects Magisk, but then afterwards (if I kill the manager and start again, or wait a little) it reports that it is not installed.

Root is always working.

Steps I have taken to remedy the situation

- Reflash Magisk

- Uninstall Magisk Manager and install the apk (after a reboot)

Here's another tidbit that might be relevant.

As I said , each time I reboot, Magisk is detected by the manager if I open the app right after reboot.

However if I check for Safetynet, it fails both tests.

If I keep on checking for Safetynet it eventually passes both tests, it looks like after a reboot it takes a while before Safetynet detection protection kicks in.

As stated, if I kill the manager and restart or wait a while, Magisk is no longer detected by the manager but root is still working.

Before re-flashing the ROM and starting all fresh to see if that fixes the issue, is there any information I could provide that could help shed more light at this issue?

Thanks

BB
[Magisk] zputnyq:
I had done it but it can't be installed.

I decided to roll back to previous version & MM appears
[Magisk] Didgeridoohan:
The Magisk log (but for it to show anything you'd have to be on the Canary channel and since that is causing devices to not boot at the moment you'd he to wait for a release of build 18103) or a logcat when you kill and then open the Manager (to reproduce they issue while recording the log) Those might show something...

Details about grabbing logs can be found here:

https://www.didgeridoohan.com/magisk/MagiskHelp

---------- Post added at 16:09 ---------- Previous post was at 16:08 ----------

https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
[Magisk] zputnyq:
Thank you,

I tried updating from magisk manager & it solve this issue on my device :)
[Magisk] Blooddrunked:
hello. i have a question. i wanted to try the installation from magisk with the patched_boot.img on my pixel 2 xl. i try it because i read, that this is possible a try when you have trouble, that magisk lost root after 24 hours or something like that. the problem, when you only must to reboot.

when i install the patched_boot.img from magisk in twrp, the magisk root is working, but twrp is away. so i decided to install the twrp zip and now the root is away. i think, i do a little (big) mistake, but i dont know what is the mistake...

thank you!
[Magisk] Dash95:
Hello, does Magisk support Alcatel 1x (2018, 5059A)? The section is dead.

It's possible to backup this phone ROM?
[Magisk] Tecalote:
[MENTION=4667597]Didgeridoohan[/MENTION]

Phone

: HUAWEI Mate 9 (MHA-L29)

System

: Android 8 - Oreo

Firmware

: European b376

Installed Magisk Version:

Magisk v18.1

clean installed - Magisk Manager hidden

Issue

: ctsProfile and basicIntegrity is switching between true and false

Details

:

After restarting the device, the safetynet is mostly true, but sometimes false. If safety is true, after some time (can be some minutes, can be some hours) safetynet is false.

Installed modules: Busybox for Android NDK by [MENTION=4544860]osm0sis[/MENTION] - nothing else. I guess it has nothing to do with this busybox module. However, install log of the module shows an error: mount: can't read '/etc/fstab': No such file or directory.

But the issue with Magisk is also without Busybox module - even if I do not have installed any module.

Logs

(attached):

I tried to make some. It was not easy, because sometimes, when I restarted the device and safetynet was true, I started to grab Log with Logcat Extreme App. But when I looked several times with Magisk Manager, safetynet was all the time true :) But a little bit later, when I finished to grab Log, safetynet was false...

The three Logs in the zip file are from a time when safetynet was changing from true to false → I do not know if there is something to see related to the issue, please check. Thanks!

Huawei uses a Power Management System for saving battery and forcing Apps to close, if they are not used for a while. It is possible to change this in settings and I did.

I included Magisk Manager in the exception list to be excluded from battery optimization. Also, I've changed in "Settings / Battery / Startup" (= Startup Manager) for Magisk Manager from "Automatic" to "Manual: to force "Auto-launch, Secondary launch, and run in the background" → Without this setting, Magisk Manager does not respond to root permission requests in a timely manner.

I suspect that Magisk processes will be killed by EMUI in between, and that's why switching from safetynet true to false will happen. But that's just a guess. Interestingly, the problem does not occur with Magisk 17.1 - only since version 18 and 18.1
[Magisk] darwinmach:
Worked like a charm for me!
[Magisk] clambert11:
I'm going nuts here. I can't get Magisk to install properly on a Pixel device.

1) Pixel XL (non-Verizon and unlocked)

2) OS - Stock Android 9.0 / Feb. 2019 - System Image just installed fresh

3) TWRP 3.2.3.1 loaded image via fastboot

4) Magisk version 18.1 installed

Issue: Device stuck at Can't load Android system. The only way to fix it is to install the Magisk uninstaller but then I still don't have root.

I tried removing my pin (read that in the thread) and the issue still persists.

Am I doing something wrong?
[Magisk] tommo1982:
I think it was because both versions were installed simultaneously. I used the option to hide with the old Manager, so maybe the new one couldn't locate installation dir and did a clean install. Dunno. When I removed ver. 6 I could update Magisk to 18.1. There is a third option to update directly which wasn't shown before.
[Magisk] clambert11:
Just an update to this. I installed Magisk Manager and tried patching / installing the boot.img file as well. My result seems to be the same. Kinda crazy.
[Magisk] varadinum:
odin fail

Hi,odin can not flash patched_boot.img. With magisk the patched_boot.img created. Odin launched -AP selected-patched selected-start-fail. Why does not work? can someone help me?

Thanks

Samsung A9 2018 A920F Bootloader unlocked

Edit: the mobile phone must be switched on or be off in download mode?