yashsingh1/xdaforums huggingface dataset:
[Magisk] panchogg:
Ok, but i am not using Magisk Hide, i dont need it

Just need fews Magisk Modules

Example: Dolby Atmos....

How can i fix it?
[Magisk] Artim_96:
Since it's always on and at least hiding from SafetyNet and Google pay, I doubt it can be installed on older kernel versions.

And if so, you most likely can't do anything about that. If there is a kernel new enough for your device you're lucky, but since I would bet your device shipped with a much older kernel I doubt a newer is possible. Because then you'd need drivers that are compatible with the newer kernel and I very much doubt that Samsung will ever share enough information to achieve that
[Magisk] panchogg:
Maybe i must wait for a developer that creating a Kernel for i9300 with treble...

I dont remember his name but i am following developer status

Thanks for help
[Magisk] aznsensazn29:
Turns out Snapchat wasn't working either, so I cleared data for both Play Store and Play services. Afterwards both Google Pay and Snapchat work, so that's nice. Thanks anyway!
[Magisk] Artim_96:
That has nothing to do with trebble. You said yourself, the problem is mount namespace.

But you are lucky, with just a minute of searching the the Galaxy S3 development section I found a kernel backporting that feature. This could work: https://xdaforums.com/galaxy-s3/development/kernel-koffee-t3728423
[Magisk] StuttgartKiwi:
I don't use TWRP - I have the stock recovery on my phone. No modifications at all, apart from using Magisk. But yes, per the instructions at https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md it's definitely not necessary to uninstall root or twrp first. That's supposed to be one of the advantages of the Pixel's A/B partitions - you can do the OTA updates while keeping Magisk in place. Except that it's not working.

Any more ideas about why this is the case?
[Magisk] Didgeridoohan:
That doesn't work since you're creating a backup of your current boot image, that has the SuperSU patch that's causing the issue in the first place.

Everything worked out this time. Now you need to flash the patched boot image to your device. Can be done with TWRP, fastboot, etc. When you use the Manager you have to do things more manual.

And a tip for the future: please use HIDE tags when posting logs, or better yet, attach the file to your post.

The persist.magisk.hide thing is normal. Take a look here for the rest:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Mount namespace shouldn't be an issue, that's just MagiskHide, and you've already been given that information.

I've no idea what could be your issue, but I think the best place to find help is in your device's forum. Grabbing a logcat when the issue appears might help figuring it out.

You can't use just any boot image! It has you match your current ROM... Otherwise, as you've found, you'll end up in a bootloop.

If you take a look in the release thread you'll find that the link you provided is no longer used for the Manager downloads. Someone might have hijacked the old link... Don't use it.

---------- Post added at 00:26 ---------- Previous post was at 00:23 ----------

It seems like the A/B device OTA instructions might actually need a bit of an update to work... It's under investigation.
[Magisk] StuttgartKiwi:
Okay thanks for the update on that! I'll check the instructions again next month and hopefully you might have been able to solve it. Thanks again!
[Magisk] jcmm11:
Did you install the patched boot image? You need to replace the existing boot image with the patched one (TWRP, flash IMG)
[Magisk] metropical:
Installed. Thanks for bearing with me.
[Magisk] andrew2432:
You should also boot into your ROM once before flashing magisk usually
[Magisk] wogooo:
Ja i realised later i was on debloated rom. Although its still Samsung original rom, but stripped? Ja i have no clue how this all works.

But the boot image I found in debloated rom also didn't work..

I root and flash custom roms for 7 yeara but I guess im still too noobish for this :(
[Magisk] martyfender:
Did you flash that patched boot.img to your device with fastboot for most devices, or I think Odin for Samsung devices? Magisk only patches it in your case, it does not flash it to your device.
[Magisk] Vishal P:
[MENTION=4470081]topjohnwu[/MENTION] Magisk is still crashing on my phone after opening. Have reinstalled it, but still. Attaching Log.

OS version: 8.1.0

Device: Redmi note 3
[Magisk] wogooo:
i think i found a correct boot.img now...but it is indeed a .lz4 file. On Google i cant find a tool to decompress it. Do you know one? Im on Win 10
[Magisk] jenslody:
Try to patch it with MagiskManager on your device.

If I remember correctly, Magisk can handle lz4, but I'm not sure, and I can not look into the sources at the moment (at work).
[Magisk] wogooo:
so i install boot.img with Magisk in Android? :eek: Im confused now

Is this the right file for uninstall SU? https://xdaforums.com/showpost.php?p=63615067&postcount=2459
[Magisk] Pkt_Lnt:
Yes it is, that is the one you want to use, then patch the boot image.
[Magisk] wogooo:
i can flash it in Android? So no twrp needed?
[Magisk] Pkt_Lnt:
I'm not certain, as I stated, I know nothing about your device. Best to wait for [MENTION=8340552]jenslody[/MENTION] to investigate later when he can. :good:
[Magisk] EstiR86:
I didn't uninstall root or twrp when I took the DP4 OTA.
[Magisk] leonzon:
Hi, I have searched and cant find an answer to this. I am using magisk 16.4, i flash through TWRP. all is good for a while but then it dissapears and i am prompted to re install. when i go into the app, it says magisk is not installed.

also, im not sure if this is relevant, magisk when it does work is in the sbin folder and not the typical root magisk folder.

can anyone advise. thanks
[Magisk] StuttgartKiwi:
Which device do you have? A Pixel or something else?
[Magisk] wogooo:
Im in Magisk Manager now. I pressed Install -> Install - Patch boot image. But the patch needs to be in .img or .img.tar

Why its all so complicated :laugh:
[Magisk] Artim_96:
It would just make the process much more complicated and the app bigger to support other formats. And in most cases you have the image as img in your ROM archive. .img.tar is just for Samsung devices since those files can be directly flashed through ODIN... And Samsung just has the market share
[Magisk] metropical:
a few posts back.

https://xdaforums.com/showpost.php?p=76980632&postcount=25580

thanks for your help too Marty. Flashed with TWRP and everything came together.

and I installed the Xposed module that works with TextAid.
[Magisk] skiely666:
I've clean flashed DP4 3 times now & still CTS & basic fail + playstore is uncertified. John Wu said on twitter that it was fixed, what am I doing wrong?

Pixel XL

DP4

16.4
[Magisk] Pkt_Lnt:
Posts in this thread and others on XDA state to clear Play Store cache and data to solve it, Have you tried that?
[Magisk] skiely666:
About 100 times now..

---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------

I've even registered my gsf on the site.
[Magisk] andrew2432:
Dp3/4 aren't certified and don't pass safety net, needs fixed on googles end.

Edit: twitter says its fixed, idk then my bad

---------- Post added at 02:57 PM ---------- Previous post was at 02:55 PM ----------

Which magisk version, does it always crash? Mine randomly crashes on my 8.1 but it hasn't affected anything root related.

---------- Post added at 03:01 PM ---------- Previous post was at 02:57 PM ----------

You can usually extract the boot image with 7zip on your comp. Then flash it like anything
[Magisk] wogooo:
nope 7zip doesnt recognize .lz4 files
[Magisk] ZehWallace:
Hello, i have recently installed LineageOS 14.1 with magisk on my moto g4 plus. Initially it worked fine, and SafetyNet passed, but suddenly it stopped working, and I cannot download apps such as netflix from playstore. When I try to check safetyNet it displays "Due to some changes in Google Play Services, it is not possible to check SafetyNet on repackaged Magisk Manager".

Does anyone know how to fix this?
[Magisk] martyfender:
When the Magisk Manager is hidden, the SafetyNet check in the Magisk Manager will not work correctly, the way I understand it.
[Magisk] ZehWallace:
But magisk doesn't hide either, it is still detected :/

I guess i will try re-flashing everything
[Magisk] teddy0209:
Use other app to see if you pass safetynet... Or restore the manager so you can check...
[Magisk] skiely666:
Just an update to my problem a few comments back: I cleared play services data & playstore data & BOOM everything passes including playstore certified ?
[Magisk] Pkt_Lnt:
So 101 times is the charm?!?! :cyclops:
[Magisk] ianmacd:
It's best to obtain lz4 at source, where there are binaries for a huge number of platforms: https://lz4.github.io/lz4/
[Magisk] wogooo:
when i scroll down to 7zip with Lz4 i get this: https://github.com/mcmilk/7-Zip-zstd

my god this drives me crazy.

Clicked some other one but that is abracadabra to me
[Magisk] ZehWallace:
I wiped the phone using twrp and installed magisk again. Now everything is working. Thanks for the help:)
[Magisk] ianmacd:
Seems that someone had a repo with lz4 included in 7zip, but that repo no longer exists.

Try this: https://github.com/lz4/lz4/releases

There are Win32 and Win64 binaries here.
[Magisk] Artim_96:
https://xdaforums.com/showpost.php?p=76267065&postcount=8

Try this and just leave out the ext4 part, that might work
[Magisk] jcmm11:
Zarchiver does https://play.google.com/store/apps/details?id=ru.zdevs.zarchiver
[Magisk] panchogg:
same issue
[Magisk] jenslody:
I just tested it with mixplorer on my device. It handles lz4 with mixarchive installed, both are available on xda.

To flash the patched boot-image you need either (twrp most likely not possible, or you would be able to flash magusk directly) fastboot or odin. Odin needs a boot.img.tar file (the format can be chosen in manager settings).
[Magisk] panchogg:
Hey man, its works :good:

Issue solved installing kernel Koffee 91 (27.06) (no addons), no more hangs with data mobile activated, or phone charging.

Magisk 16 working correctly, no more error Magisk's log.

tips:

* BusyBox

.- Kernel Koffee 91 (27.06) included BusyBox version 1.28.1-LordBoeffla.

.- I installed BusyBox version 1.28.3-YDS but it show 1.28.1-LordBoeffla version again.

* Xposed (used only for Greenify - greenify's xposed settings )

.- if install Xposed version 89 wipe cache and dalvik (Necessary). I see Greenify working fine.

.- Xposed after installed reboot or hangs phone (this is another story).

.- apk BootManager doesnt detect Xposed correctly (with rom RROS works fine). Tested with SuperSu and BootManager doesnt detect Xposed correctly too. ROM issue maybe.

thanks a lot.
[Magisk] Rodrigo_Neves:
I have an infinity s one I can not install the magisk and I do not have access to his ROM for installation. Does anyone help me?
[Magisk] xunholyx:
So that's why I'm getting "Magisk General Support" in my Participated threads.

I didn't post off topic, and it's too late now (general support as participated will always be there), but that's okay I suppose.

I do know that another user responded with asking for advice for help since G Pay worked for me and not for him, but I never answered and went off topic, so.....

Oh well, guess I need to do some general support now. lol:D
[Magisk] wogooo:
Installed Mixplorer and Mixarchive. When i press on boot.img.lz4 the app says i need to install the addon. :rolleyes:

When i long click on the fill and press 'extract' it says 'operation failed'

---------- Post added at 12:30 PM ---------- Previous post was at 12:24 PM ----------

it opens and closes immediately

---------- Post added at 12:30 PM ---------- Previous post was at 12:30 PM ----------

it opens and closes immediately

---------- Post added at 12:33 PM ---------- Previous post was at 12:30 PM ----------

Thanks man, finally it worked...lol :laugh:
[Magisk] ianmacd:
Those are command-line tools. If you open them in a non-interactive shell, they'll display a message, exit and the shell that spawned them will close.
[Magisk] hunky-d:
iBird Pro app doesn't seem to work with Magisk. iBird Pro is a birding app that has a database that is downloaded separately so the app works in the service-less outback. The app has not recognized the downloaded database.

So working with their tech support, I finally got this:

I did try hiding iBird Pro in Magisk Manager and, after rebooting, it did not seem to help any at all. If there is a work-around or fix, I would be most grateful. Otherwise, perhaps I can help someone else searching for the issue by posting this here, somehow.
[Magisk] jcmm11:
Did you try hiding Magisk Manager? Also, where are the
[Magisk] hunky-d:
Thanks for reply! I did not try hiding Magisk Manager, didn't know that was a thing. Did try hiding the app within the Manager to no avail. As for logs, I'll research how to provide those and get back. At work now, so later.
[Magisk] Didgeridoohan:
I really doubt your issue has anything to do with hiding root from the app. If anything, it's probably Magisk's lookback mounting that could be a culprit (if it is Magisk causing it).

What you'd need (for starters) is a logcat captured when the app is trying, and failing, to access the database.

Where does the app store the database?

You could try enabling Magisk's Core Only Mode. That way you'll only have MagiskSU and MagiskHide active, everything else with modules and systemless modifications will be disabled.
[Magisk] edensites:
Im sorry, they Said i cant use linka Under 10posts. I maybe send it twice :D
[Magisk] Äptiva:
CM13 USERS SEE HERE:

The su binary is placed in 2 locations. /system/xbin and /system/bin. You

must

remove both of these or Magisk will not work.
[Magisk] rollerce:
Reboot kills SU?

After rebooting, Magisk reports "Su imporoperly installed" and I have to go back into recovery and reinstall SU (using phh's version). Any ideas on how to fix this?
[Magisk] Äptiva:
Did you install the phh's Superuser app from play store?
[Magisk] rollerce:
Yes.

Nexus 6 running CM 13. Trying to do the whole Magisk/PhhSU thing in order to be able to play pokemon again >.<
[Magisk] JudgeDread11:
That issue gets covered very early on on this thread.
[Magisk] Äptiva:
Try this:

Using any root file explorer, check to see if there is a SU binary in either of these locations:

/system/bin

/system/xbin

If so you will need to remove these. It's easiest to do in recovery via the following command:

adb shell rm -f /system/bin/su

or

adb shell rm -f /system/xbin/su

or both if in both locations.

I suggest clearing cache and dalvik and reinstalling Magisk as usual and try again.
[Magisk] JudgeDread11:
Yes, unlock your bootloader.
[Magisk] rollerce:
Well, when I say I do a clean install, I go into twrp and format every partition except external storage in order to avoid those very issues.

As a random aside, using PHH's SU, is there a way to set SELinux persistently to permissive at boot?
[Magisk] Äptiva:
Should boot with whatever it was set to prior to reboot.

Clean flashing or dirty flashing doesn't matter. CM puts it in both locations when you install it I believe. Still better to check

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

Depends on the device. What are you using and we may give you a yes or no.
[Magisk] Xebazzztian:
Moto G 2014

Turbo ROM (AOSP)

Kernel CM13 extended UV

Should work on my phone ?
[Magisk] rollerce:
Not with CM 13 on Nexus 6. Unless you do a complicated thing, it will set SELinux to enforcing on every reboot.
[Magisk] alroger:
Again modding things before Magisk...
[Magisk] SpasilliumNexus:
You and the others that keep saying "Moto devices" need to be specific. Because its working on the 2015 Moto X Pure and Style just fine.
[Magisk] Musa95:
Its not working on 2014 and 2013 moto X
[Magisk] rosekiller:
Thanks for reply.

i just find , but no su in system/bin or xbin folder.

what should i do?
[Magisk] Emisand:
About Moto Devices, it doesn't work with mine.

I have posted a Bug report, I copy that here:

Device: Motorola Moto Maxx (aka: Droid Turbo, Moto Turbo)

Hardware name: quark

Android version: 6.0.1 (Build MPG24.107-70.2)

TWRP Version: 3.0.2-0-quark

Steps to reproduce:

1- Flashed a clean stock rom with unlocked bootloader

2- Rebooted and let Android initialize

3- Flashed the latest official version of TWRP for this phone model

4- Flashed Magisk v6

5- Rebooted

6- Phone got stuck at bootloader screen, does not boot

7- I got to boot again by flashing the stock boot image again.

NOTE: No magisk.log found

I have uploaded to the Stock boot image and the Magisk patched boot image that does not work, both backed up with TWRP:

https://drive.google.com/file/d/0B0LxOeDbUjw5SHBFWVF4dnJ5WGc/view?usp=sharing
[Magisk] rollerce:
Didn't say I was doing that while trying to install magisk. I'm thinking of switching TO magisk from my current setup, which involves that complicated process to persistently set SELinux permissive.

I'm looking for other options, but the SELinux thing is important because apps restored from backups won't even load when SELinux is enforcing.
[Magisk] Äptiva:
I'm going to ask just because it's not in your post. Is your bootloader unlocked or is there another method to get TWRP running?
[Magisk] Emisand:
Yes, the bootloader is unlocked.

I was on cyanogenmod before flashing the stock rom
[Magisk] DenyDarko:
https://github.com/topjohnwu/MagiskManager/commit/831112abd2d7fd3df0b1680d1c73c458512e7745

Apparently I'm gonna need to install custom recovery to preserve root after OTA or patch boot manually as it seems [MENTION=4470081]topjohnwu[/MENTION] removed A/B installation for next version.

It was the most convenient option for my OnrPlus 6.

I wonder, Is there any way I can still do a/b installation from command line as the option only got removed from manager ?
[Magisk] EstiR86:
A Pixel 2 XL
[Magisk] Didgeridoohan:
It's not permanently gone... It'll be back and updated, hopefully in the next stable release (if not sooner).
[Magisk] martyfender:
"Where does the app store the database?"

That is the same question I would ask. As far as I can tell it is not even a root app, or one that has any reason to detect a rooted device. Maybe it stores it's database in a non-standard location? But what do I know, I am only speculating at this point.
[Magisk] hunky-d:
The database is usually stored in (apologies if these are just links) /Android/data/com.whatbird.pro/files . Otherwise, the app tech support gave me a link to download it manually, and the app will find it if it is in sdcard/Downloads .(I don't have an actual sdcard - must be a partition. This is a Oneplus 3 phone). I can open the app, navigate to the settings/More/Local Databases and it then shows the database with a "Mount" button. When I push the button it clicks like it recognizes the action, but the app never mounts the database. I'll do a logcat as soon as my computer is up and running. Had a crash and now doing an update via shell terminal and it is taking forever compiling (Gentoo).
[Magisk] jcmm11:
Alternate for logcat - use an app https://play.google.com/store/apps/details?id=com.pluscubed.matlog
[Magisk] EvanVanVan:
Can I patch a boot image using Magisk Manager on a different device than target one?

I'm looking to root my ShieldTV. It would be easier to grab the boot.img from the ShieldTV recovery files and patch it on my phone rather than navigating around the ShieldTV trying to patch it on there...

Thanks
[Magisk] pankozin:
Samsung Tab s3 lags with magisk

Hello, I'm on Samsung galaxy tab s3 t825. When flashing in twrp latest magisk on oreo stock BRE2(latest), and then booting, the overall system performance drops like hell (lags). Sometimes tab even hardly responds to touches, and system process loads cpu to max.

I tried clean flash with Odin, using verity patch and force encr disabler.

Had anyone experienced the same and maybe knows how to solve this?
[Magisk] GryphonBR:
Hi, I've been having a really funny situation lately. I'm running BoomBox on my LG V30 (a streamlined, debloated version of its original ROM) and every so often Magisk seems to stop working and I have to reboot my phone. I know LG has a process that constantly searches for rooting solutions, but this process is entirely disabled on my phone. What's kind of log could I collect to try and figure out what's happening with my phone?

---------- Post added at 11:50 AM ---------- Previous post was at 11:46 AM ----------

Sure, just grab the boot.img from your ShieldTV, drop it on a already rooted device, then select option Patch boot image from the Magisk Manager's installation menu. A patched image will be generated and stored in the /sdcard/MagiskManager folder on your device, flash it to your ShieldTV and you're good to go.
[Magisk] Didgeridoohan:
Should work. One thing that could cause issues is that there won't be a stock boot image backup available on the ShieldTV, in case you want to uninstall Magisk.

Logs?

Are you talking about root suddenly not working and the Manager reporting that Magisk isn't installed? If so, that's a known issue that is being very actively worked on.
[Magisk] GryphonBR:
Yes, that's exactly my issue. Is this an Oreo issue? Because I recall this happening a couple of times on a P10 Plus I have, but since updating to 16.4 I can't recall it happening again - my V30 is also on 16.4, by the way.

---------- Post added at 01:24 PM ---------- Previous post was at 01:20 PM ----------

Regarding [MENTION=1861966]EvanVanVan[/MENTION]'s question, he could simply have the original boot.img somewhere on his ShieldTV, and upon removal of Magisk flash the original image back, right?
[Magisk] Didgeridoohan:
Can't remember if it's an Oreo issue, but it's been an issue for a long, long time. And it's quite random... Should hopefully be fixed soon.

Correct.
[Magisk] Jaymin.0.1910:
Hello,

This issue is not Oreo related. It turns out to be an issue with multuple zygote processes running on the Android. Which I think is already been fixed in the latest sources, but not yet been released. You might try some community-built snapshots.

Regards from JayminSuthar.
[Magisk] martyfender:
That only fixes the root loss issue for some devices, Samsung, or similar, specifically.

Many of us are still experiencing root loss with the latest community builds, also.
[MENTION=3306843]kantjer[/MENTION] build 180626 has the invincible mode added back into it, and seems to solve the root loss for many of us, until a better fix is released by [MENTION=4470081]topjohnwu[/MENTION]. Results may vary though with different devices.

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

https://github.com/kantjer/MagiskFiles

cutom update channel to add to Magisk Manager, settings, update channel, custom:

https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json

If you try this, you must first uninstall your current Magisk Manager,

only

, as community builds are signed with a different key and will fail to install if you don't remove the beta or stable manager first.

Same holds true if you switch to any of the other community builds such as [MENTION=7187684]ianmacd[/MENTION] 's 64 bit builds. I believe his latest doesn't have invincible mode back in it though.

https://github.com/ianmacd/MagiskBuilds
[Magisk] Didgeridoohan:
That's because that code isn't quite finished...
[Magisk] Jaymin.0.1910:
Yes, that's what I'd suggest, too. [MENTION=8126387]martyfender[/MENTION]
[Magisk] hunky-d:
I grabbed a logcat for the iBird Pro database issue. I navigated to the app mount option and the app crashed.

https://drive.google.com/file/d/1HK2CT7sr0gQ-4LgiqzPzhW5AkRYtjPI7/view?usp=sharing

---------- Post added at 08:53 AM ---------- Previous post was at 08:41 AM ----------

I tried the Core Only Mode and it didn't seem to make any difference. I did a logcat at https://drive.google.com/file/d/1HK2CT7sr0gQ-4LgiqzPzhW5AkRYtjPI7/view?usp=sharing and next I will try uninstalling Magisk to actually see if it is creating the issue or not.

thanks, JD
[Magisk] jenslody:
The backup should be in /data/user_de/0/com.topjohnwu.magisk/install".