yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
The issue looks fine. The only thing I would have liked differently is to replace "latest Magisk" with the actual Magisk version (v11.1 in this case, if you look in the log). Very minor detail though and this is just me being extremely nitpicky.

There was a lot of compatibility issues worked on between v11.1 and v11.5. I'm gonna assume you've tried v11.6 and get the same result, or?

Other than possibly updating the issue with recovery log and boot image from a v11.6 installation there's nothing more to do than wait. It's there, it's been reported and [MENTION=4470081]topjohnwu[/MENTION] will look at it when he has the time.
[Magisk] sjknight413:
Does systemless viper4android work yet on 11.6 without causing a bootloop?
[Magisk] BootloopedMillennials:
Well I'll be damned v11.6 did install. Though it did mention

! System installed root detected, mount rw :(

The ROM I'm using doesn't package root in. Hence I couldn't find traces in /system/xbin and /system/bin. I'll have to figure that out but it went through with the install process. I haven't rebooted and tested it yet. It was just to test the install, I have to restore my old rom, and backup.
[Magisk] Didgeridoohan:
Awesome! There's a good reason to not write "using the latest" when reporting issues... You might trick people into believing there are still issues with the actual latest version, even though there might not be.

I'm not too familiar with the actual code behind it, but Magisk installer will look for any other root than MagiskSU and SuperSU and try to remove it if found. If it's a system installed root, /system will have to be mounted rw to remove it. I believe that's what that line is about.
[Magisk] BootloopedMillennials:
Thank you for the assistance. Also much thanks to [MENTION=4470081]topjohnwu[/MENTION].

The Github post wasn't created by me but like you said good reminder on including the version number.
[Magisk] Didgeridoohan:
No worries. I know it wasn't you... It was just a general statement. :D
[Magisk] kryzeK:
Anyone can run Mario Run with sucess?
[Magisk] EpicLPer:
Yep, no problems here.
[Magisk] chudy_85:
Yes it's work correctly
[Magisk] Genericxx:
It would be appreciated if someone could check if S-PushTAN works with latest Magisk and MagiskHide. I deeply rely on this app and wasn't able to make it work on Magisk Verisons prior to 11.6 although i pass Safetynet and even RootBeer shows nothing confidential. It usually crashes instantly when opened, redirecting to the website of my credit institute. So apparently MagiskHide wasn't able to hide root to this app. Oddly enough i am able to make this app work flawlessly by using lineageos-addon-su in combination with iSu to temporarily disable all root services. This is currently the only culprit that keeps me away from Magisk, so maybe someone just install it from PlayStore, check if it works and gives me a hint? :)
[Magisk] Newmanl:
Anyone have a link to a full game unlocked levels? obb data or something like that?

I had to hide su with magisk (using magisksu of course) and the apk finally works...also working with magisk and supersu..tried both
[Magisk] cr723:
Breaking root for Call Recorder

Hi,

Call recorder application is not working with Magisk.

Any permanent solution for this?

https://xdaforums.com/showthread.php?t=1441643
[Magisk] noooooo:
Is there a way to hide magisk app icon if my ROM displays it already in settings menu?
[Magisk] Didgeridoohan:
I can start it just fine with Magisk v11.6 installed. Besides adding it to the Hide list I also had to change ro.build.flavor to match "<device name>-user", in my case "shamu-user".

On another ROM (I recently changed) I also had to mess with ro.build.selinux (not even present on my current ROM) and couldn't open it without clearing data for the app and rebooting if it detected root once.

---------- Post added at 17:20 ---------- Previous post was at 17:16 ----------

That sounds an awful lot like you're requesting warez... Big no-no.

Without having looked at the app in question at all, it might be that the app needs to be updated to work with MagiskSU.
[Magisk] blue whale:
Guys, the file

Uninstaller (2017.3.20) (Support v1+)

is not available, can you re-upload it

---------- Post added at 05:57 PM ---------- Previous post was at 05:42 PM ----------

I installed magisk 11.6 on xiaomi redmi KATE with MIUI dev global 7.3.9, but I do not have root with it.

I installed phh-superuser-magisk-r266-2.zip but still no root. Also, I cannot download this file through the application mad by phh. I thought I could download phh-superuser-magisk-r266-2.zip through an app, but I had to go on xda and download it.

How do

---------- Post added at 06:18 PM ---------- Previous post was at 05:57 PM ----------

So i uninstalled magisk 11.6, installed magisk v9, because it is said to work and indeed I have root, but I have no ''enable magisk hide'' option and the SAFETY test fails too.

Then I update to magisk 11.6 and I have root+mgaisk hide

but still the safety check fails.

Also, the data connection fails to be ON at startup

-make DATA ON

-reboot

-data is on, there is a bit of data exchange, but then it is cut off, while ''data ícon is still on''
[Magisk] joshiameya:
I keep losing superuser after few hours, I am on lineage os, at first I refreshed 11.6 and su was available, now I checked again in magisk mgr and su is gone, is anybody experiencing this?
[Magisk] Genericxx:
Tried everything described here and over the Support-Thread this evening but there seem to be no way for me to get S-PushTAN to work with Magisk 11.6 on latest Resurrection Remix. Had to switch back to addonsu with iSu to make it work again.
[Magisk] Buffydamion:
Super Mario Run

Running Helios 7.9 with Magisk 11.1 and Mario Run ist crushing all the time while loading. Any ideas? Already turned MagiHide on for Mario
[Magisk] Januh:
Guys iam really sorry but, i have been searching so many in this forum about Magisk and tested so much on my OP3 i dont know what to do now...

I installed the 11.6 also installed the manager, when i go to manager it says root: supersu... how can i solve this to be root: magisk?

i installed again the 11.6 but still keep the same

Any help for this noob is someone dont mind explain?
[Magisk] Chichi.Lopez:
Hi, I'm new to Magisk but already read the "Magisk and Magisk Hide installation and troubleshooting tips and tricks (v11.6)" thread. My ROM ist latest "Official LineageOS 14.1 for GT-I9305". So far I couldn't pass the SafetyNet check, it shows me "CTS profile mismatch".

Last night I've installed the latest ROM version. After booting I'd a look at the Magisk Manager and it showed me "Magisk not installed" and "device not rooted" (meanwhile know, that I've to install again). I curiously pressed the safetyNet check and it became green. Afterwards I I flashed Magisk 11.6 version by using TWRP 3.1.0-0. After reboot the Mangager showed me "Magisk 11.6 installed" and "device rooted", but I couldn't pass SafetyNet. It again showed me "CTS profile mismatch". So far I tried almost everthing mentioned in the "installation and troubleshooting thread", but Magisk did not hide root. SELinux status: Moderat. I would very pleased if you give a noob a hind whatelse I could try. Thanks in advance!!!
[Magisk] gtpy:
You already checked the supersu settings? There you can fully unroot or clean for another superuser app.
[Magisk] Zer0t3ch:
Look, I'm sorry I worded it in a way that offended you, but it's not like I'm trying to hassle the guy. I'm merely curious....

1. If it works

2. If it's being worked on

3. If it's a priority

The answer to all three of those could be no and I wouldn't mind, I'm just curious.

As for the answer to #1, it can't be solved by "a simple search", because I did multiple searches, both in this thread and on google and saw no answer to it. (At least not when I asked the question, there's probably more info around by now)
[Magisk] ShadySquirrel:
Lineage user too, Huawei Honor 5X, Magisk 11.6. Root is restored after you force stop Magisk Manager and rerun it. Had this same issue on 11.1, but it stopped after I've disabled Magisk Hide. Now, no matter if I'm using Magisk Hide or not, I have to restart manager to keep root functional.
[Magisk] GHFear:
Easy fix, before you do anything, unZIP your custom rom, put the boot.img in a folder you remember, download unSU, restart to recovery, Wipe Dalvik/ART cache and Cache, Flash unSU in recovery to wipe ALL traces of ROOT. And then flash the original boot.img from the rom you are using. When you go to *Install* in TWRP recovery you can choose *Install img* or something similar down in the bottom right corner, and then locate the boot.img from the folder you put it in. Now start your phone and letters Everything load Up and update IF it has to, restart to recovery again, Install Magisk 11,1.zip. Restart phone and go to Magisk Manager, now it Will pass safety Net and you can update to 11.6 from the manager. :)
[Magisk] Ninja Potatoe:
After installing magisk 11.6 from the manager, I can't access my system and internal sdcard contents. I can actually see them just fine, but I can't open any files (EACCESS/permissions error). Tried to fix permissions in twrp and with the viper4arise script, no luck.
[Magisk] jhedfors:
I agree with everything, but I would flash osmOsis's unSU zip AFTER restoring boot (right before flashing Magisk). Some ROM's come with the boot.IMG pre-rooted with systemless root - this will make sure it gets unrooted as well.

https://xdaforums.com/showpost.php?p=63615067
[Magisk] GHFear:
True :) that is pretty uncommon tho... Mostly they just put supersu.zip in a folder in the rom.zip and add a script to Install it when you Install the rom. But yes because it is an OP3, probably with Cyanogen or something on it, I would do what you said. Flash unSU AFTER you restore the boot.img
[Magisk] bigknowz:
Uninstaller

Anyone have the new uninstaller, also not able to download.
[Magisk] Januh:
Guys iam so mad about this MagiskSU... i did everything i saw in xda and nothing went well in Magisk Manager, in root always says SuperSU and never does MagiskSU...

Can someone give or made a little tutorial on how to put this MagiskSU?

Thanks in advance for the person who help
[Magisk] ToHellWithGA:
Second attempt at OmniROM + Magisk on Nextbit Robin (ether) - version 11.6 this time. Still getting "CTS profile mismatch" error. Please advise.
[Magisk] Doc Franky B.:
http://cloud.tapatalk.com/s/58d46c92bb3af/Magisk-uninstaller-20170102.zip

This is what I have at the moment

Send from Note4 - 6.0.1
[Magisk] xslain_69:
Boot IMG full

Hey guys,

A noob here i kinda need help. When i try to install Magisk, it says that my boot.img is full (40MB). I have tired flashing back to stock using Odin to see if that will fix or reset the boot.img but that doesn't seem to have worked. Currently running a custom ROM (AMBASADII) and I have included the entire TWRP log in a link as i don't know where to include the file. Thanks.

LOG EXTRACT:

- Creating /data/magisk.img

Creating filesystem with parameters:

Size: 67108864

Block size: 4096

Blocks per group: 32768

Inodes per group: 4096

Inode size: 256

Journal blocks: 1024

Label:

Blocks: 16384

Block groups: 1

Reserved block group size: 7

Created filesystem with 11/4096 inodes and 1294/16384 blocks

losetup: /data/magisk.img

- Mounting /data/magisk.img to /magisk

Boot partition too small!

MagiskBoot (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/block/sda5]

IMG [AOSP]

KERNEL [34375952] @ 0x10008000

RAMDISK [4673599] @ 0x11000000

SECOND [0] @ 0x10f00000

DTB [956416] @ 0x10000100

PAGESIZE [2048]

OS_VERSION [7.0.0]

PATCH_LEVEL [2017-02]

NAME [SRPOI30A000KU]

CMDLINE []

COMPRESSION [gzip]

Repack to boot image: [new-boot.img]

Compressing to [ramdisk.cpio.gz]

KERNEL [34375952] @ 0x10008000

RAMDISK [9025825] @ 0x11000000

SECOND [0] @ 0x10f00000

DTB [956416] @ 0x10000100

PAGESIZE [2048]

OS_VERSION [7.0.0]

PATCH_LEVEL [2017-02]

NAME [SRPOI30A000KU]

CMDLINE []

COMPRESSION [gzip]

! Boot partition space insufficient

! Remove ramdisk backups and try again

MagiskBoot (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

Dump cpio: [ramdisk.cpio]

Boot partition too small!

MagiskBoot (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/block/sda5]

IMG [AOSP]

KERNEL [34375952] @ 0x10008000

RAMDISK [4673599] @ 0x11000000

SECOND [0] @ 0x10f00000

DTB [956416] @ 0x10000100

PAGESIZE [2048]

OS_VERSION [7.0.0]

PATCH_LEVEL [2017-02]

NAME [SRPOI30A000KU]

CMDLINE []

COMPRESSION [gzip]

Repack to boot image: [new-boot.img]

Compressing to [ramdisk.cpio.gz]

KERNEL [34375952] @ 0x10008000

RAMDISK [9026238] @ 0x11000000

SECOND [0] @ 0x10f00000

DTB [956416] @ 0x10000100

PAGESIZE [2048]

OS_VERSION [7.0.0]

PATCH_LEVEL [2017-02]

NAME [SRPOI30A000KU]

CMDLINE []

COMPRESSION [gzip]

! Boot partition size still too small...

! Unable to install Magisk

Updater process ended with ERROR: 1

I:Legacy property environment disabled.

I:Install took 9 second(s).

Error installing zip file '/sdcard/Download/Magisk-v11.6.zip'

Updating partition details...

I: Data backup size is 5720MB, free: 11092MB.

I: Unable to mount '/usb-otg'

I: Actual block device: '', current file system: 'vfat'

...done
[Magisk] bigknowz:
Thanks, but there is supposed to be a 17.3.20 version.
[Magisk] Doc Franky B.:
I had the same.

For me helps, install ver 11.1 via twrp and them update 11.6 via magisk Manager

Send from Note4 - 6.0.1
[Magisk] xslain_69:
But just wondering, is there a way to get the boot.img back to what it was originally? Like would flashing using SmartSwitch or some other method get it back? Since i mentioned that i tried Odin and the boot img is still full (at 40MB).
[Magisk] Taivotat2:
Hi everybody. Im having this issue trying to use AIKMobile module.

Device Samsung Galaxy J500M AOSPExtendedOfficialNougat

Magisk installs directly from ROM, I was used with SuperSu and I dont know how to make it work with Magisk, no crashing apps, apps gain root permission flawlessly. Only not working safenet and this module ...????
[Magisk] Taivotat2:
Is stock kernel? Did you try flashing boot.img from twrp? Pick boot.img from your nandroid backup...hope it help?
[Magisk] Dave_247:
Before posting I did a bunch of searching but wasn't able to find anything on the issue I am having.

I have a Sony Xperixa X running 7.0 with the December security patch. I was able to install Magisk and boot without issue, however upon starting Magisk Manager there seems to be a lot of things missing. The app shows Magisk as installed but not rooted, and the modules tab is missing in the side menu as well as other settings int he options menu.

I'm not sure if this has to do with how before installing Magisk, I used this tool to restore the phone's functionally you lose by unlocking it, as well as disabling dm-verity, Sony RIC and foce encryption as all of those things would get in the way of installing Magisk I would think. It does that though by patching the original kernel file which you then flash yourself, so I'm worried that might have interfered with the Magisk process which also needs to patch the boot image.

I did try flashing the original kernal.elf back to my device and then flashing Magisk again but it made no difference, so I'm not entirely convinced that this was the culprit.

I also tried using the latest beta version of Magisk and Manager Manager but again, it made no difference.
[Magisk] yochananmarqos:
It's also attached to the same post.

Uninstall Magisk and do a full unroot in SuperSU or use osm0sis' unSU ZIP. Then flash your ROM's boot image before you flash Magisk.
[Magisk] AntholifeV2:
When I install Xposed I do not bypass safety .. is normal? If I uninstall xposed it works without worries ! It's impossible to have xposed and safety in same time ?? .....

THANKS
[Magisk] yochananmarqos:
Yes and yes.
[Magisk] AntholifeV2:
Not a problem, I understood after the problem by rummaging in the files .. Google has updated its system again, it detects the framework despite magisk ... Do you think that an update of the side of xposed or Magisk can fix the problem? I've heard that topjohnwu is working on an update of the framework and the v12.0 of magisk who can solve the problem, you'd echoes?

Envoyé de mon SM-G928F en utilisant Tapatalk
[Magisk] yochananmarqos:
Not anytime soon if at all.
[Magisk] Rainbowtwinkies:
So i have a samsung sm-p580. I cant use magisk? When will a custom kernel be available?
[Magisk] HampTheToker:
Magisk 11.6 breaks things on OnePlus 3T (OxygenOS 4.1.0).

Users report error 1 while attempting to flash FrancoKernel and probably others. I tried uninstalling Magisk via Magisk Manager and also encounter the same error. The uninstaller zip worked fine, thankfully. I'm back on 11.1 for now. If you need logs just let me know.
[Magisk] Didgeridoohan:
Doublecheck with the getprop command in terminal that all the prop values Magisk Hide changes get set properly (you'll see which ones in the Magisk log). There's one exception though, in my experience. The prop ro.build.tags might not be set properly, even though getprop reports "release-keys". Use an app like Root Check to see if it reports "test-keys" or "release-keys" (scroll down on the main window). If it reports "test-keys" even though Hide is enabled, try toggling Hide off and on and rebooting.

Also, like I mentioned before, make sure that the prop ro.build.flavor doesn't report "xxxx-userdebug", but "xxxx-user".

Other than that, I don't know... The above is all I had to do to get it running.

Did a test and it seems like Mario Run doesn't check for root, but does crash if one or more of the prop values Magisk Hide changes by default isn't set to the expected value.

Check with an app like SafetyNet Playground or SafetyNet Helper if you can pass basic integrity. If that's the case there's some issue with your device/ROM and CTS certification and there's probably not much you can do on your end. If basic integrity doesn't pass, you can use a root checker app to see if you can hide root with Magisk Hide. If that works, Hide is functioning and you've got some other issue with SafetyNet you'll need to take care of (maybe check your device/ROM forum/thread).

No worries, no offence taken. Just wanted to add that the "if it works" question had been asked just the day before and I actually did a search for it right before posting my first response to you. Searched for "Android O" and clicked through the first few threads returned and voila, there it was. So yes, it could be answered by a "simple search" (and a few clicks).

That's a question for your device's forums.

That sounds like a device specific issue, since Franco Kernel works great with Magisk on my Nexus 6. Reporting "error 1" is not very helpful though. Post a recovery log instead...
[Magisk] Xennet:
Flashing magisk after Franco is possible

But flashing magisk and then Franco error shows up

But the way I know the kernel has to be flashed last

Unfortunately I don't have the logs as I reverted everything back
[Magisk] freeza:
Just tried to use this on my Axon 7 (7.1.1) and it's insanely laggy when enabling Magisk hide. Laggy to the point the screen turns off and i'm forced to hard reset.
[Magisk] xslain_69:
Thing is when i did my nandroid backup, it's also at 40MB... tried restoring to stock firmware again but still at 40MB (boot.img). No idea if this will affect anything or if i am able to get it back to the original.
[Magisk] Didgeridoohan:
I always flash FK before Magisk and haven't had any issues up until now...
[Magisk] Xennet:
That's it now the issue is clear

Been reporting it in Franco thread for long

The issue is flashing Franco after magisk

But since time it has always the golden rule to flash kernel as last after rooting..
[Magisk] Didgeridoohan:
Actually, early on [MENTION=4470081]topjohnwu[/MENTION] recommended flashing kernel before Magisk. Magisk is so much more than just a way of getting root access.
[Magisk] ManikandanGuru:
Sony framework modules doesn't seem to work.

Play store not showing any Sony apps for me.

Help needed please.
[Magisk] tamer7:
I have Phronesis Note7 ROM v5.1 on Samsung Note 3 (SM-N9005) passing safetynet in clean (fully-unrooted, stock boot image, no xposed, etc.) state.

i install magisk hide v11.1 or v11.6 , but magiskhide doesn't work at all, despite log looking ok, and despite toggling magiskhide off/on etc.

In Magisk Manager , safetynet doesn't pass.

SafetyNet Helper Sample / Attest listed in MagiskHide list, but still fails both basic integrity check and cts profile mistmatch.

I've been searching the forums, have read thoroughly all troubleshooting steps, looked at all open-issues on magisk in github, and opened a new github issue outlining all troubleshooting steps carried out so far.

Any help in further troubleshooting MagiskHide to help fix this in future release would be greatly appreciated! :fingers-crossed:

---------- Post added at 11:02 AM ---------- Previous post was at 10:43 AM ----------

it works, but according to Didgeridoohan , you need to make sure ro.build.selinux=0

v11.6 changes it to 1 , so you need to edit the /magisk/.core/magiskhide/enable script

see: https://xdaforums.com/apps/magisk/m...systemless-t3432382/post71524704#post71524704

see: https://github.com/topjohnwu/Magisk/issues/125
[Magisk] francyesco:
is this a normal behaviour for magiskhide (enabled on the rootbeer app)? is there a way to hide native root checking?

oviusly i'm on latest version 11.6, Mi 5 Global Stable 8.1.2.0
[Magisk] Taivotat2:
Flash kernel as topjohnwu said before Magisk. When installing Magisk it changes some things in boot.img like ramdisk. So first kernel, and after Magisk.☺?
[Magisk] aiola1982:
Same with Z5c.

Updating from 11.1 thru MagiskManager works, but flashing 11.6 on untouched Stock Kernel ends up without root
[Magisk] phoberus:
If I deactivate the extensive logging the safetynet check says the cts profile mismatch. If I activate the big logs its all good. Someone knows why?

Should I post my magisk logs?

edit:

MagiskHide enabled

only MagiskSU root files

usb debbuging disabled
[Magisk] Dave_247:
The problem for me though is that I can't use 11.1 as it causes my phone to bootloop after installing Magisk. The only way to recover it is to flash the uninstaller to remove it.
[Magisk] Didgeridoohan:
Wait, what? Are you talking about log settings in the Magisk Manager, "Enable advanced debug logging"? If it's disabled you get a CTS profile mismatch? That is... interesting...

Are you sure that's the only thing that changes between failed and passed SafetyNet? I have a theory...

Post a Magisk log before enabling verbose logging, with a CTS profile mismatch, and one after enabling verbose logging with passed SafetyNet.
[Magisk] BootloopedMillennials:
Magisk lost root overnight on my Moto X 2014 running LineageOS and Magisk v11.6. A reboot restored back root.

Nexus 6 use to have this issue and it was caused by Busybox being enabled in earlier Magisks. Busybox wasn't enabled on my Moto X though. I'm currently testing with it enabled to see if it will lose root.

Android log should pick up why it lost root correct? Without root there was no Magisk logging to check..
[Magisk] phoberus:
Tested it more know. I think it's completly random if it works or not. In like 2 from 3 starts safetynet passes and one not. But after a restart it works. Maybe something with the Hide deamon?
[Magisk] Didgeridoohan:
That was my theory, that it was simply the Magisk Hide daemon not starting correctly on a reboot. You can see in the logs if that's the case. Toggling Hide off and on again and/or rebooting usually fixes it.
[Magisk] phoberus:
Good, thanks for the help :good:
[Magisk] Genericxx:
I did that, Safetynet passes, every 3rd party app that checks cts profiles etc. passes also. Solely my PushTAN won't start, whereas there is no Problem with it if i'm using lineageos SU with iSu. Weird :confused:
[Magisk] tamer7:
After changing ro.build.selinux=0 in the magisk enable script, you need to reboot obviously.

Also you need to force stop S-PushTan, then clear the app's data, maybe even reboot... It keeps a record of finding root.