yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
I think it is because you don't have enough posts yet to upload files. Hitting submit reply once should be sufficient. Even though it appears to fail, it usually doesn't, hence your multiple posts. I find going back to the previous page then forward again, it usually shows up the first time.

I wish that they would fix this.

Does anyone know why this happens?
[Magisk] scoobyjenkins:
I made a boot animation module that previously worked on Android 10 custom rom, now it doesn't seem to work but it's been a while since I tried. Has anything about the module template changed? I haven't been able to find anything yet, here's the log generated from Magisk:

- Copying zip to temp directory

- Installing validus10-wolf-bootanimation-magisk-module.zip

- Device is system-as-root

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

creating: common/

inflating: common/post-fs-data.sh

inflating: common/service.sh

inflating: common/system.prop

inflating: config.sh

inflating: module.prop

*******************************

Boot Animation

by

scoobyjenkins

*******************************

******************************

Powered by Magisk (@topjohnwu)

******************************

update-binary: line 101: mount_magisk_img: not found

- Extracting module files

Archive: /data/user/0/com.topjohnwu.magisk/cache/flash/install.zip

creating: system/

creating: system/media/

inflating: system/media/bootanimation.zip

touch: /dev/tmp/magisk_img/GZR/system/media/bootanimation.zip/.replace: Not a directory

update-binary: line 442: can't create /dev/tmp/magisk_img/GZR/system/media/bootanimation.zip/.replace: nonexistent directory

chmod: /dev/tmp/magisk_img/GZR/system/media/bootanimation.zip/.replace: Not a directory

- Setting permissions

update-binary: line 147: unmount_magisk_img: not found

- Done
[Magisk] Didgeridoohan:
Judging from this (from your log) you might be using a rather old template:

An image file hasn't been used by Magisk in a long time, and just the other day backwards compatibility was removed (so far only for the current Canary release, 20110):

https://github.com/topjohnwu/Magisk/commit/06c42d05c38a395a17147204ac721301adeb7c90

You should update your module to match the current module installer format... Take a look on the docs (always a good place to start):

https://topjohnwu.github.io/Magisk/guides.html
[Magisk] scoobyjenkins:
Ah, I'll take a look, thanks!
[Magisk] J.Michael:
In Developer Options on the tablet, subsection "Networking", I have "Disable absolute volume (Disables the Bluetooth absolute volume feature in case of volume issues with remote devices such as unacceptably loud volume or lack of control.)"

It sounds like it fixes the opposite of your problem, but I don't really understand what it's saying.

Android 9 (Pie) on Samsung Galaxy Tab A 8" (SM-T290)
[Magisk] EntropyAndDespair:
If anybody interested.

I 've found a way how to get magisk installed on my Cubot Mini.

1. Problems was with magisk it self. Patching boot.img didnt work properly. I changed it manually and it work. (Android was 32bit but somehow detected as 64bit).

2. Device IS system-as-root but when i used last version of magisk + changed boot.img BUT -> fastboot flashing unlock -> fastboot flash boot boot.img -> fastboot reboot -> gave me root.

Thank you all for your support.
[Magisk] viercp:
Tried all i could find there (incl. deinstalling Magist and install Canary build) - App still show that i am routed
[Magisk] Didgeridoohan:
If you've found something that needs fixing, how about creating a PR:

https://github.com/topjohnwu/Magisk/pulls

If you're talking about Raiffeisen ELBA-pay (https://play.google.com/store/apps/details?id=at.psa.app.raika), I had no issues opening it once I added it to MagiskHide.

Tested on a OnePlus 3T, Android Pie, Magisk Canary debug 20110 with hidden Manager 264.
[Magisk] viercp:
Very strange also that the "normal" Elba app is fully working and do not show any mssg after hide.

Can you pls give me some helping hands with how to set up the correct build and manager (i am not that familiar with Magisk and hae no idea what hidden Manager 264 means.)
[Magisk] warrencoakley:
Mmmm. I'll look into it. I think many custom kernals do something with the Bluetooth settings but unsure in how to fix them.
[Magisk] Didgeridoohan:
264 refers to the build number, in this case for the current Canary release. You'll see those next to the version info (within the parenthesis) in the main Manager window.

There are a number of variables the could cause full obfuscation to fail. Might be that the Android version/ROM you're using has limitations, etc.

First thing you can try is to uninstall the Magisk Manager and see if that makes any difference (with the app on the Hide list, of course). If that works we have a clue at least. Other than that, pretty much everything I've got can be found in the link you've already been given. More info about your setup might give some info...
[Magisk] viercp:
Checked both - latest version (20110 and 264 6)

I am on Evolution X - Android 10, latest build (4.14.160 - Immensity Kernel)

Deinstalled Mananger - unfortunately same result

Also thought about apps which require root but how to identify them ? I am not sure but dont think that i have installed some how requires ....

And what i also have seen in other threads - maybe i have to hide apps where Elba requires access (Telefon, Files ....) - might help ?
[Magisk] Didgeridoohan:
Your setup looks good enough and you've got the full force of MagiskHide at your disposal... And I did not need to add anything else than the app to the Hide list.

That leaves stuff outside of Magisk's control, such as other apps (Titanium Backup is a favourite, but there are many others), telling directories on your internal storage (like TWRP), or even your ROM if you're unlucky. Pretty much everything I've got is covered in the link you were given earlier.

That's gonna be practically impossible for me to help with though, but you might get help from other users of your ROM.

Good luck.
[Magisk] droople:
Thank you, I will have a try
[Magisk] chrcol:
Guys Seems I fail safetynet check now, did google update something to break it?
[Magisk] ktmom:
Have you tried toggling MagiskHide off and on?

https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
[Magisk] galih_ken:
Hi, noob question here. Is there magisk support for oreo 8.0? The latest version doesn't include oreo in the description of supported android version. I recently update firmware of my asus zc551kl marshmallow (old device) to oreo and I just want my phone to be safely rooted. Most of the tutorial out there is about marshmallow or noughat. I need help, I don't quite know what I'm doing
[Magisk] zgfg:
Maybe you are not reading Magisk documentation but some old forums from the time of MM and N, or related to MM and N devices/firmwares

Actually, I see most about P and Q (like A/B, SAR devices):

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

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

https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md

Also if you read the previous posts here (last month or two, or just like last 30 or 50 posts), you will see that vast majority of discussion is about P and Q - hence more appropriate question could be, does Magisk still support Oreo, but yes, it does :)
[Magisk] J.Michael:
SECURE CHECK FAIL: vbmeta

Does anyone know what "SECURE CHECK FAIL: vbmeta" (message on the tablet, in download mode, after trying to download set of four firmware files with Odin) is checking? What didn't match?

I'm trying to install Magisk on a Galaxy Tab A 8" (2019) Android 9 (Pie) (SM-T290). sammobile has nothing. samfrew has a lot. Originally, I had no idea of my country code, though I suspected it was *not* USA. I found a set of firmware files (i.e., a number of zip files) for T290 with the right date. I picked French because I thought I'd be able to bumble my way to changing the language. I tried installing Magisk and kept getting SECURE CHECK FAIL: vbmeta. My last attempt was with Magisk Canary and Odin Patched.

I found out that XAR was USA, and XAR is mentioned on the About screen (not specifically as a country code, just as one of the letter groups in "Service provider SW ver."). I found a firmware file identified as XAR, with the right date. I thought that would clear up the mismatch producing the SECURE CHECK FAIL.

After downloading the second firmware file, I found that, while one ZIP file is ten bytes longer than the other, the five files in one are identical to the five files in the other.

I'm out of ideas. Anybody?
[Magisk] seemebreakthis:
... So... No luck on using the app anymore?
[Magisk] Didgeridoohan:
The current version description states "Android 4.2+", so Oreo is definitely supported...

You've been given most of these links already, but it never hurts to post them again.

You'll find the official installation instructions in the Magisk documentation:

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

And if you've got issues you can find some information on the Magisk Troubleshooting guide:

https://didgeridoohan.com/magisk

And of course, your device's forum is also always a good place for info and help:

https://xdaforums.com/zenfone-3
[Magisk] Didgeridoohan:
I'm not very good with Samsung, but did you use the Canary release? That's the only tip I have at the moment...
[Magisk] coachmarino:
Screwed up OTA

So, Pixel 3, I've successfully updated Android in the past using Magisk patch...but this time after starting the process, the OTA failed, and when I rebooted I lost root.

Now I have a pending OTA and no root. Magisk is looking to be updated.

What is my best course of action?
[Magisk] ktmom:
You may get better help in the device forum. There have been issues reported with the December update.
[Magisk] hhrokarvi:
Hey guys,

Sorry if this has been discussed on the forum, I'm a maintainer for Nexus 6 (shamu) for crDroid. Just built Android 10 for it today. I installed ROM, GApps, and then magisk zips. The phone kept on rebooting on the logo screen. Without Magisk, it booted fine.

My device tree is from LineageOS github, and it uses SAR. I've followed the docs here and here and still can't install Magisk without not being able to get root or ending with the loop on the logo screen.

Can someone please guide me?
[Magisk] J.Michael:
Yes, Canary version of Magisk, 3B's Patched Odin.
[Magisk] Didgeridoohan:
Cool! As soon as I get an opportunity I'll fire that up on my old Shamu and give it a go.
[Magisk] hhrokarvi:
no idea what's wrong with Magisk not working? :D
[Magisk] Didgeridoohan:
No idea... Logs?
[Magisk] jcmm11:
I can tell you what I do (Pixel 3 XL) (short version)

Download factory image (not OTA) from https://developers.google.com/android/images

Extract the boot image (you'll find it in the inner zip)

Patch the boot image and copy it to your computer

Modify the flash-all.bat/sh file

In the last line of the file replace the -w with --skip-reboot

Run the flash-all file.

Apply the patched boot image

fastboot flash --slot all boot <patched boot image>

Reboot
[Magisk] foobar66:
Happy new year to all of you!

I have an issue with REPLACE of directories. In my install.sh file, I have:

REPLACE="
/system/product/priv-app/daxService
"

And then when I reboot my phone I can see:

> adb logcat | grep bind_ | grep product
01-05 22:45:07.087 796 797 I Magisk : bind_mount: /product/priv-app/daxService

But then the directory /system/product/priv-app/daxService still contains the original files:

> adb shell
$ su
# ls -l /product/priv-app/daxService
total 1752
1748 daxService.apk 4 oat/

I don't understand ... my intention is to "hide" the .apk file. I thought the REPLACE variable would do the trick but it does not seem to work. When I check the module on the phone, I see:

android@localhost[/sbin/.core/modules/test]# ls
total 44
8 module.prop 8 post-fs-data.sh 4 product@ 8 service.sh 8 system/ 8 system.prop

android@localhost[/sbin/.core/modules/test]# find
.
./system.prop
./module.prop
./post-fs-data.sh
./service.sh
./product
./system
./system/product
./system/product/priv-app
./system/product/priv-app/daxService
./system/product/priv-app/daxService/.replace

So as far as I can see everything looks fine to replace the directory daxService but it does not seem to work ...

Device: OnePlus 7T pro

Other stuff in my module (additional files) is working OK.

Any help would be appreciated. thanks.
[Magisk] ktmom:
I'm no expert, but I thought that when you define a directory, you get a mirror. To effectively remove a file, you must replace the file, not the directory.
[Magisk] nadeemakhtar1994:
In some android apps only camera can be used for photo selection. No gallery or file manager option

Any way to bypass this using a magisk module or anything?
[Magisk] jcmm11:
Directory replace should work. I'm replacing a bunch of directories, successfully. It effectively removes all the files in the directory. Quoting from https://topjohnwu.github.io/Magisk/guides.html#module-tricks

[MENTION=3463514]foobar66[/MENTION]

Try the latest Canary, debug version, and if it still doesn't work post the Magisk log. Include a pointer back to the original problem description as well. You can update to the latest template format while you're at it ? (although things should work with the format you're currently using)
[Magisk] martyfender:
Magisk stable, v20.2 and Magisk Manager Version: v7.5.0 has been released.

A new Canary build was released also:
[Magisk] J.Michael:
Does this supercede the current Canary build?

Do you think the new stable does anything yesterday's Canary did not?
[Magisk] martyfender:
The latest Canary was not yesterday but dated 6 days ago, so yes, there are some updates:

UPDATE: A new Canary build was released also.
[Magisk] Spookymyo:
What's the best method to update to magisk 20.2? I've updated magisk manager already.

Download zip only

Select and patch a file

Direct install

Or Install to inactive slot (after OTA)
[Magisk] Didgeridoohan:
Direct install (see first paragraph here: https://topjohnwu.github.io/Magisk/install.html).
[Magisk] rogers11:
On my device it shows:

...

Direct install (recommended)

...

...
[Magisk] originalul:
I have TGP_X96XX_v1.7.0_XXU4CSK N9 ported rom for my S9. I updated to the latest version of magisk and my phone Root is lost. I have reinstalled and uninstalled through TWRP several versions of magisk(the Magisk Canary Debug.zip build gave BootLoop) but without success. I reinstalled TGP kernel with CLEAN ROOT but without success again. The only solution I found was to install( Dirty method) again the TGP_X96XX_v1.7.0_XXU4CSK1 rom. I have "dmesg.log" and "recovery.log "files generated by TWRP but I don't know where to uplode it. Has anyone else suffered something like this on the Samsung S9?
[Magisk] frrancuz.:
Can anyone help me? I have NOTE 3 - stock. What type of kernel?
[Magisk] putridfoetus:
http://xdaforums.com/apps/magisk/magisk-discussion-thread-t3467229

That's a Samsung specific Magisk thread. You'd probalby have better luck there.

---------- Post added at 11:43 AM ---------- Previous post was at 11:35 AM ----------

What exact steps did you take? It will help us determine where/if something went wrong.

For example, did you:

1. flash ROM

2. COMPLETELY REMOVE ROOT

3. flash magisk v6

4. flash phh superuser v17 magisk version

5. anything else

6. install phh superuser app from playstore

7. install magisk manager app from op
[Magisk] angiest:
So I see others having a similar problem, but not exactly the same situation.

I just installed Magisk for the first time (brand new install of Noougies ROM on a Nexus 9). I have phh superuser for Magisk and it is working from everything I see so far. My issue is trying to disable root through Magisk Manager. I see it being granted root access, but the toggle doesn't stick. From what I have seen in this thread, this is usually do to a previously installed superuser program. That is not the case here. This ROM is unrooted and the recommendation is to install Magisk and phh. Therefore, I am at a loss.
[Magisk] Captain_Throwback:
Another possibility is a conflicting Busybox install. Does the ROM come with Busybox included? If so, try removing it.
[Magisk] angiest:
NO, it's not included.
[Magisk] Captain_Throwback:
Then the only advice I have for you is to wait for v7 and see if it fixes your issue.
[Magisk] crackers8199:
been trying to get help with this for a few days now and everyone seems to keep passing it by...does anyone have any idea what i might be doing wrong here? why can't i make a backup in TWRP without killing magisk?
[Magisk] angiest:
Maybe so. I did some more tests. It *is* unmounting root, and once I do that I have no way to remount it except to reboot. That's fine, it's a tablet, it's not like I carry it around for AP. ;) Even unrooted, though, I couldn't pass SafetyNet.
[Magisk] Captain_Throwback:
Not sure how those things can be at all related. Probably why no one has answered.
[Magisk] crackers8199:
yeah, you and me both...but i've done it twice with the same result. so it's seemingly not a random occurrence. every time i try to make a TWRP backup, magisk won't mount when i reboot. the only way i can get it to mount is by re-flashing magisk, then phh, then xposed...once i do that, everything is back to normal.
[Magisk] duowing:
Well you can always check and mount/unmount root through terminal emulator. You could even make a script so that it's even easier to run.

Check the Root Status:

$(getprop magisk.supath)/su -c "getprop magisk.root"

The output will tell you the status. 1 = Rooted | 0 = Unrooted

Change Root Status:

$(getprop magisk.supath/su -c "setprop magis.root x"

Then obviously use either 1 or 0 for x to Root or Un-mount Root

You could even make a text file with these lines and then all you would have to do is run something like

sh /sdcard/rootenable

sh /sdcard/rootdisable

sh /sdcard/rootcheck
[Magisk] tech_head:
Finally have it working on my Nexus 6P. The following worked for me YMMV.

1. I reinstalled the Stock Sept Security update (Nexus 6P).

2. Flashed ElementalX Kernel

3. Flashed MagiskV6

4. Flashed SuperSU 2.78 Systemless

5. Flashed Systemless Xposed 86.5

6. Flashed AdAway_systemless_hosts_V2

7. VERY IMPORTANT REBOOT HERE! (I tried not rebooting and flashing suhide here but got very strange results.)

Let the app optimization happen.

8. Install SuperSu, BusyBox, Magisk Manager, etc..

9. Start all the apps you want root for and get that all set up.

10. Reboot into recovery

11. Flash Suhide V53.

12. Reboot

Phone is stable. No rebooting so far.

If you install apps I suggest removing suhide for app optimization, then a reboot and flash suhide. YMMV
[Magisk] crackers8199:
i just did another backup and the same thing happened again. this is the third time, and i can reliably reproduce it (every time i make a backup, i lose root / magisk until i re-flash it). it sounds crazy and ridiculous, because like you said i can't see any way the two should be related...but it happens EVERY SINGLE TIME.

is there any kind of log file i can provide to try to figure this out? like i said, i'd like to stick with magisk just in case there's an update to make android pay work again w/ systemless xposed...but if i can't resolve this i'll probably just go back to system root.
[Magisk] rgawenda:
Or install Android Studio, MagiskManager source, and compile it.
[Magisk] james_rokr:
No man, I was talking about CyanogenMod all the time, Stock CM13 (without xposed, su and any other weird stuff)

also I don't know what's that "script to bump boot" I just did the things I told you on MY last comment and that's all :)
[Magisk] Captain_Throwback:
None that I can think of, which again, is probably why no one responded.
[Magisk] rtorres01:
I form this

1 - remove root custom rom

2 - recovery and wipe factery reset

3 - flash magisk

4 - flash phh super user

5 - reboot

6 - install phh super user from play store

7 - install magisk apk

8 - still without access root :chorando:

PS: also I tried use supeSu-v2.76-magiskzip but without success
[Magisk] mathy007:
What's the command I need to type in adb?
[Magisk] gozarudin:
Not working on my device

Hi topjohnwu,

Where i should send my boot.emcc.win to you?

I tried it on my sony Xperia m2 d2305 android 5.1.1

And get my device won't boot and just get blank screen when i restart my phone

Please help me

Regards,

Ghozali

sholehuddin.ghozali@gmail.com
[Magisk] ibrokemypie:
potentially stupid question but, is systemless xposed with phh support being worked on or is suhide with supersu and xposed 86.2 going to be a permanent solution to getting around safetynet without reboot?
[Magisk] kurtextrem:
Are you guys able to install modules using 20.2? If I flash or use the in-app method to "flash" the module zips, the flash is successful, but after a reboot the modules don't show up. The modules tab is just empty.

ArrowOS on Chiron, Q, SAR.

Edit: Also Magisk Hide turns off itself at every reboot for whatever reason lol
[Magisk] freeman_108:
I have the same issus

I am using SoLdieR9312s G96XCSK1 24 rom with TPG Kernel 2.12.4 I have the same problem, its happened since support pre-init sepolicy patch on canary build. Seems like only happen to S9 probably s9+.
[Magisk] Didgeridoohan:
No issues here. Sounds like a ROM/device issue... Module installation log and Magisk log might show something.
[Magisk] kurtextrem:
Logs attached. Can't find anything extra ordinary
[Magisk] lilian_ncy:
Hello,

I encountrered an issue due to the Magisk v20.2 installation on LG phones.

I own a LG G5 and LG G6 both patched with magisk v20.1. After installing Magisk v20.2 (update from Magisk manager direct install), when I restarted my phones, both phones were stuck on the fastboot mode and could not load their ROM.

I went to the recovery , I used magisk latest uninstaller but it did not solve the issue. My phones were still not able to load their ROM and got stucl on fastboot screenchoice.

I was able to flash back my ROM original boot.ibm to both phone tehn rebbot to recovery and apply Magisk v20.1 to solve the issue.

If a developper can have alook to my issue which seems to be related to LG phones.

Cheers
[Magisk] Minshter:
I am in the same boat as lilian_ncy, albeit on a LG V20 (h918).

Got manually back into TWRP. Not done anything further yet. Might dirty flash my A&O rom to see if it comes back to life, but waiting to see if this thread provides a better fix first.

lilian_ncy - Did you flash back the original boot.ibm by using restore in TWRP for only the boot option?

Thanks for any answers.
[Magisk] lilian_ncy:
You can get the original unmodified boot.ibm from your flashed ROM.zip file. Then you can flash the original boot.img directly from your PC.

See the tutorial below

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

Hope this help
[Magisk] mikeyb123:
G960F, Magisk. V20.2 working fine, wont work with TPG kernel, it's An TPG kernel issue .
[Magisk] Zachster96:
Had the same issue as you guys with my V20. I just flashed the boot.img file included with the A&O rom and it worked, but it gave me the classic v20 static screen on boot, which it never did before. I fixed that by flashing my kernel again, and then flashing magisk 20.1 again. Everything seems to be fixed now.
[Magisk] Crowbro:
Hi guys

Happy New Year

So there's this application, "My Vodafone" app, which is facing some issues while running. It detects root and when I use magisk hide it still gives an error " we are facing some technical issues". I think it is because of root and magisk. So I want to completely unroot my phone. When I tap on "uninstall" in magisk manager it shows 2 options: restore images and complete uninstall. I don't know which one to choose. I have seen some people discussing about boot.img file. I am running a custom rom.

Can anyone please tell me which option to select in magisk manager while uninstalling to unroot my phone completely? Or if there's any other method, can anyone please guide me through it?

Thank you