yashsingh1/xdaforums huggingface dataset:
[Magisk] IzaacJ:
Latest Magisk still seems to be incompatible with the Lenovo Tab 3 710F (MediaTek MT8127 SoC).

Log below. Full log attached.

*****************************
Magisk v11.1 Boot Image Patcher
*****************************
- Mounting /system(ro), /cache, /data
- Device platform: arm
- Constructing environment
chcon: Could not label u:object_r:system_file:s0 with -h: No such file or directory
- 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
- Mounting /data/magisk.img to /magisk
- Found Boot Image: /dev/bootimg
- Unpacking boot image
Segmentation fault
! Unable to unpack boot image
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
Error installing zip file '/sdcard/Download/Magisk-v11.1.zip'
[Magisk] Gigobaito:
Just for future references: why Xposed triggers SafetyNet check? Ive managed to pass it by disabling Xposed, but just curious WHY that triggers it, even if systemless
[Magisk] Didgeridoohan:
Custom ROM here with SafetyNet passing... Nexus 6, Pure Nexus 7.1.1_r13 (01/21), Franco Kernel r64.

---------- Post added at 20:20 ---------- Previous post was at 20:19 ----------

There's been no work done on compatibility. I believe it's up next though...
[Magisk] ElenaPower:
I need to have it installed. But frozen is ok. So I think it's only that Tasker is somewhere looking for files it want's to see for thinking the S7 is rooted.

[MENTION=6168497]dcdruck1117[/MENTION]

If you uncheck the "Use Root" option in Tasker and Tasker is thinking there is no root you won't be able to tick it on again.
[Magisk] IzaacJ:
Well, some must've been, cause it has never gotten this far in the installation process before xD
[Magisk] Rennie-Boy:
I get what your saying and thanks for the tip. You're also right I didn't use it like. It was a last resort trying to fix my root problem as nothing else worked and it's driving me crazy. Since "that app" did nothing to help it's long gone!

I just want root so I can back up my apps properly and be able to play Pokemon Go. :(
[Magisk] Didgeridoohan:
Titanium Backup is working perfectly on my device with Magisk v11.1 and MagiskSU.

Edit: By the way; whats the message you get from Titanum Backup?
[Magisk] Captain_Throwback:
And you've actually made a purchase using Android Pay with your setup?
[Magisk] LazerL0rd:
I'm going to try it today, but if it doesn't work I'll add the card onto a Android Watch 2.0 then use that for payments. I'm guessing that would work.
[Magisk] Filip013:
Good to know. I already tested LOS 14.1 on my device. And it doesn't work. CTS profile is false. Basic Integrity is true. I only get CTS profile true on official Stable ROM, even the Development ROM issued by Xiaomi every week doesn't pass SafetyNet. I thought that a ROM has to be certified (by Google? by OEM?) to have a valid CTS profile.

Hmm... Come to think of it, in what way is Pure Nexus different from stock ROM? I gather it's closely based on the stock ROM. But that's just a guess.
[Magisk] Rennie-Boy:
So it can work! Did you have to do extra steps like mount system as RW? Tried that, is definitely mounted as RW but didn't work for TB.

The message I get is...

"You're SU binary (version "6:MagiskSU (topjohnwu)")" is functional but might not work reliably on some Android 4.3 roms. If you encounter any issues in TB try using SuperSU instead."

Don't get it though I'm on Android 6.0.1. :confused:
[Magisk] Didgeridoohan:
I've seen reports in this very thread of SafetyNet passing on LineageOS with Magisk Hide...
[Magisk] Filip013:
Then I guess that my device is just very picky :D

Edit: but I do want to get to the bottom of this. I've just started to search but it seems to me that Nexus phones, One PlusOne and Wileyfox (damn it, had to Google the spelling) pass SafetyNet with custom ROMs that are closely based on stock ROM. Will keep looking.
[Magisk] devilman30:
Did you update to the latest app?
[Magisk] chlap:
Yes I just installed new magisk from playstore. No previous version installed.
[Magisk] devilman30:
In magisk settings check disable magisk, reboot then enable and reboot again. Try this. If it doesn't work flash magisk via TWRP and try the same instructions again.
[Magisk] Trel:
I'm having an install problem with v11.

I did the following.

1. Used UnSu

2. Used latest Magisk Uninstaller

3. Flashed ROM

4. Flashed Boot.img again to be safe

5. From TWRP flashed Magisk-v11.1.zip (I should mention that during the install, it says that it's installing MagiskSU)

6. Rebooted to system

7. Ran MagiskManager app.

It reports that "Not rooted, Functionality greatly limited"

Additionally, none of the settings relating to MagiskSU are present in options.
[Magisk] de.er:
You need to flash unsu.zip after ROM, before magisk.
[Magisk] Trel:
I've just tried that too (the rom is NOT rooted by default either way).

Same exact issue. Magisk says I'm not rooted.

EDIT: May have found something that worked, will update in a while with status.
[Magisk] Link_of_Hyrule:
I'm still having my devices randomly say they are unrooted. I wiped system, unsued, unmagisked, installed newest magisk. Hopefully he gets this bug fixed.
[Magisk] bigknowz:
CTS profile mismatch

Clean flashed Dirty Unicorns 11.1 on N6P, and then Magisk 10.2, failing SafetyNet - CTS Profile Mismatch. Not sure the stock kernel has the proper patch. Should I flash a kernel with the patch and then Magisk? Not seeing anything in the log that helps.

https://www.dropbox.com/s/xezvq43actsrcsa/magisk_error_20170210_205101.log?dl=0
[Magisk] githyanki:
Why are you using old version of magisk?
[Magisk] bigknowz:
Because people are losing root and having problems with Tasker.
[Magisk] teddy0209:
All you need with magisk is a clean boot.img...
[Magisk] J_E_F_F:
Yup, SafetyNet Passes on my Oneplus One with the latest Lineage nightly and Magisk 11.1 and 4.1 manager.
[Magisk] yochananmarqos:
To get Tasker to detect root, all you have to do is install the phh superuser app. You don't even have to open it and can even freeze it with Titanium Backup. I haven't once lost root.

---------- Post added at 06:28 AM ---------- Previous post was at 06:21 AM ----------

Passive aggressive posts like these do not help. If you want a developer to fix "bugs," you need to post what devices you have along with what ROM and kernel you're using. In Magisk Manager, turn on advanced logging and post a log.
[Magisk] ABotelho23:
OnePlus 3, micro OpenGapps, DU 11.1, Magisk 11.1.

Magisk makes my ROM unbootable. Stays stuck on the 1+ splash screen, never reaches the DU boot animation. Nandroid restore let's me boot again, of course without Magisk.

Any ideas?
[Magisk] spacebar2011:
I posted this in the Wiki thread by mistake, so forgive me for that :P

My fellow Magiskers, I have a few questions here.

How does Magisk deal with encryption, specifically the new file based encryption in Nougat. I mean, is it possible to use Magisk while still having encryption on?

If i want to update my ROM (Oxygen OS 4.0.2 on a Oneplus 3), have Magisk installed (with MagiskSU), what's the best way to go about it without a full wipe.

Which version of TWRP is recommended for this? I mean, with all the decryption password, dm-verity issues and then the risk of the device getting fully wiped, which one is recommended? I'm using the blu_spark 3.0.2 v11 and it's been doing okay, at least till the last time I used it for Oxygen OS 4.0.2 installation.

I know the TWRP question might be out of place here, but, I guessed someone here might have an answer anyway.

Greatly appreciate any help with the above.. thanks!
[Magisk] Filip013:
When you run SafetyNet Helper, what result do you get? It would be best to post a screenshot.

I remain stubbornly convinced that I am right. :D But seriously, from what I understand OnePlus One comes with stock CyanogenOS so it makes sense that it has a certified CTS Profile and can fully pass SafetyNet.
[Magisk] Didgeridoohan:
Have you tried the findings of [MENTION=5530534]101_North[/MENTION] that he can get root back by removing the Manager from recent apps and opening it again?

https://xdaforums.com/showpost.php?p=70966512&postcount=8891

To me that sound like there's a battery saving feature (doze, Greenify, etc) causing issues with Magisk Manager. He's investigating...

---------- Post added at 08:49 ---------- Previous post was at 08:26 ----------

I actually think you're on to something as well... If the ROM on the device is to far from the original OS when the device was determined to be Android compatible you won't be able to get a true response to the CTS profile matching. Makes sense.

It'll be interesting to see if you find anything.
[Magisk] Artim_96:
Just disable busybox and maybe uninstall and reinstall Magisk, that fixes it (at least losing root)
[Magisk] rgawenda:
Then people uses search and find those damm lies.

I have root with MagiskSU. Tasker works. Period.

To be more constructive. I've had the losing root issue. Tried disabling busybox without success.

Turned of Magisk Hide two days ago. Root hasn't gone missing anymore. Ah, and surprise, I didn't suspect I could get these without Hide and with Xposed:
[Magisk] Didgeridoohan:
That's really interesting. And you're saying that you're not using the workaround for Tasker that's been discussed the past day or so (installing phh's superuser app). If so, you're the first person I've seen to get Tasker accepting MagiskSU out of the box. And just a clarification, Tasker works fine, but have trouble getting root access with latest MagiskSU.

And about SafetyNet: that's also very interesting. What's your complete setup? Are you using anything else besides Magisk?
[Magisk] rgawenda:
My setup is CyanogenOS 13 on Oneplus One. Dirty upgrade to Magisk 11 with phh's and removed the app after booting and facing the conflict.
[Magisk] Artim_96:
Well, at least the last part should be completely impossible. You have found some kind of workaround, or these results are just cached. Do they stay green after a reboot?
[Magisk] Filip013:
CTS profile match without Basic Integrity boggles my mind. What results do you get in SafetyNet Playground? Do apps that require SafetyNet work? It seems to me that you don't really pass SafetyNet, you just happen to get CTS profile match.

[MENTION=4667597]Didgeridoohan[/MENTION]

Well, I also got Tasker to use root without any modifications. (I guess I wasn't clear enough about that.)
[Magisk] Didgeridoohan:
What conflict?

Most people can't get Tasker in itself to recognise root. It can be done with some workarounds (shell commands and phh's superuser).

Maybe it's your dirty upgrade that does it... Again: interesting.

+1 on this.

And you can't get SafetyNet to pass... Could these be related? Could there be some kind of remnant of root on your system you've missed that works in conjunction with MagiskSU to get Tasker to recognise root? Pure and utter speculation from a sleep deprived mind...

Wait a minute... I just went back you check some of your previous posts and had an idea. You mentioned you can't get SN to pass on the development build from Xiaomi. What's your ro.build.type in build.prop set to? I can't quite remember, but I think I read something about conflicting build type values triggering SafetyNet.

Man, oh man... It hurts to think right now...
[Magisk] rgawenda:
The conflict of having phh's app trying to manage root. v11 upgrade removed the root module, but left the app. After removing and rebooting, the root was working for some amount of time and found no solution here (yes, I do read every post).

That's why I posted. Just forget SN for now (No, I don't have any other workaround). The thread is burned with the root issue. Just test yourselves for a while without Magisk Hide to get [MENTION=4470081]topjohnwu[/MENTION] to look there instead of the busybox thing.
[Magisk] LazerL0rd:
I was thinking... let's say someone creates a module for suhide... Especially when [MENTION=631273]Chainfire[/MENTION] fixes the November patch issue. Wouldn't that be great?
[Magisk] Mar-cel:
I'm rooted with SuperSU 2.79 and have installed Magisk 11.1 how can I activate now MagiskSU?
[Magisk] RandomPooka:
Delete the SuperSU app and the pro key. Reboot to recovery. Flash your stock boot.img (or the boot.img included in your ROM), and then flash magisk v11.1 after that. Reboot.

If you typically use a custom kernel, flash it before Magisk. But, you MUST start with the kernel supplied with your ROM or device
[Magisk] rgawenda:
Update: It seems I had activated the No Device Check xposed module. Again, I insist that I do loose root at some point unless MHide is disabled.
[Magisk] anonymous-bot:
I am running Dirty Unicorns 11.1 and Magisk 11.1 and I noticed that if I have USB debugging disabled I will pass SafetyNet but if it is enabled then I will fail. Is this expected behavior? How can I keep USB debugging enabled but pass SafetyNet?
[Magisk] Mar-cel:
Only delete SuperSU apk? Or should I select unroot in SuperSU settings?
[Magisk] Didgeridoohan:
Figured it was something like that...

Yes, there seems to be a bug in the latest release where root is lost at seemingly random intervals, for some users (I'm not affected yet and have both Hide and Busybox enabled). Several users are trying to figure out different things about it.

That's the expected behavior and the way Google wants it. Unless someone comes up with a way to hide it, as can be done with an unlocked bootloader and permissive SELinux, you'll have to keep it disabled and only enable when you need it.

To be sure you need to unroot as well, either through the app or with osm0si's unSU script.
[Magisk] RandomPooka:
Unrooting won't hurt. SuperSU systemless is an IMG file mounted as a file system, so it shouldn't leave any remnants that interfere with the magisk root operation any more than any other unused IMG file would.

But, if you're very OCD about unused files on your device, unroot like a boss. Osmosis zip is a good way to, as it doesn't require the supersu app to be present for self removal, and it can be done from recovery
[Magisk] bigknowz:
Genius! What made you think of trying that? Finally passing safetynet, thanks.
[Magisk] Filip013:
With regards to Tasker, there is 100% no other root on my system. If there was, I wouldn't be able to pass SafetyNet.

About build prop, I've heard that the value needs to be "user" and not "userdebug", which it is for all MIUI ROMs. I've tried experimenting with build prop, but it just caused me bootloops...
[Magisk] Didgeridoohan:
Don't mess with build.prop... You're using Magisk! Make a module and set the props with system.prop.
[Magisk] DarkLanternX:
I had managed to run magisk v11 on RR 5.8.0 Android N, but today I got an error from magisk all of a sudden and now I can't bypass the safetynet anymore, the safetynet tap is stuck on an endless loading, it was working fine till yesterday. I reflashed the whole thing still couldn't.
[Magisk] Nodens:
Can not install any version beyond 9 on S6 Edge+. No space in boot partition reported by Magisk installer flashed in recovery. Trying to update via manager just fails with the generic error message.
[Magisk] teddy0209:
That has been the case for custom roms lately... It's all over the magisk thread... ?
[Magisk] KaMyKaSii:
Question for who can answer me:

Is the folder /cache/magisk_mount created automatically when installing Magisk or only when installing a cache module or must it be created manually?
[Magisk] yochananmarqos:
Cache modules are no longer used. Read the release thread.
[Magisk] KaMyKaSii:
Thanks for the answer. But then could you help me to replace bootanimation systemless-ly?
[Magisk] ABotelho23:
Guys? Any ideas?
[Magisk] yung40oz84:
OK, so I was real excited to try this, and I flashed the latest Magisk 11.1 with its own root method on Dirty Unicorns for the OP3, Dirty Unicorns removed root completely so there is not need to remove root or clean it. I can flash Dirty Unicorns and then a custom kernel, and then Magisk, reboot and it gets stuck on 1+ logo, will not boot. Same affect when I only flash the ROM with stock kernel, flash Magisk, it gets stuck on 1+ logo and will not boot, I'd be willing to grab some logs or whatever is needed but I'm not sure what exactly I can get or you need when it won't boot. Kindly let me know, thank you!!!

---------- Post added at 06:10 PM ---------- Previous post was at 06:06 PM ----------

Ha, I didn't see this until after I posted mine, same issue my friend, hopefully they can look into this.
[Magisk] yochananmarqos:
The instructions are in the release thread, specifically this post.

.
[Magisk] ABotelho23:
it's certainly very strange. In 5 years of custom Roms I've yet to see it get stuck at the OEM splash screen lol
[Magisk] yung40oz84:
I've also tried several kernels thinking possibly it was a kernel issue or boot.img issue and that is not the case. It just will not boot at all.
[Magisk] Mar-cel:
Delete
[Magisk] Ncmt:
Hello, I would like to root my Huawei P8 and install MagiskSu to be able to continue to play Pokemon Go and I have some question :

- If I want to root my Phone, is that ok to use this tutorial ? :

1/ Download the Magisk zip file, uninstaller and the SuperSU files to your device.

2/ Reboot your device into recovery mode. You can just Google it if you don’t know how to get into recovery mode.

3/ Now you have two choices — root with MagiskSU or SuperSU.

- If you want to use SuperSU, flash the SuperSU in systemless mode. This works only for Android 6.0 or above Android versions. Now, flash the Magisk zip on your device.

- If you want to go with much integrated MagiskSU, just flash the Magisk zip.

4/ Reboot your device.

5/ After the device is up, download the latest Magisk Manager from the Google Play Store link below.

Also the way of rooting on Huawei P8 seems similar but I need to tap this command before flashing the supersu, or I'll get a bootloop :

echo SYSTEMLESS=true>>/data/.supersu

Do you know if I need to do the same with MagiskSu or something similar

Thanks for helping.
[Magisk] githyanki:
Try using the integrated MagiskSU first and see if it meets your needs.
[Magisk] Lumince:
Im currently on my LG V20 and it just fails to install Magisk. Already rooted and decrypted my phone. I have SU installed so I am unsure what is wrong
[Magisk] Artim_96:
At least for a few, not working on EmotionOS though. ADB is disabled, but in Magisk manager the test just keeps showing a spinning wheel (for all I know because play services crashes but I don't know how to keep it from crashing) and SafetyNet playground fails.

Magisk hide is enabled of course
[Magisk] teddy0209:
No... All you need is flash the latest magisk version... It's better to start clean....

---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------

Yup, that's not the case for all...

Some reports say they flash a different gapps, if the clearing of data for play services did not work...

---------- Post added at 01:15 AM ---------- Previous post was at 01:13 AM ----------

If you have supersu, remove that before flashing magisk if what you want to achieve is pass safetynet... Better yet start from cleam rom...
[Magisk] Lumince:
So just do a full unroot? Or would moving to phhsupersu help me even more? I have supersu but its already systemless. So i didnt think that would break it tbh.
[Magisk] Artim_96:
And which would that be?

PS: I don't know how exactly that hiding of SELinux permissive works, but maybe it only works reliably on permissive kernels, not if it gets switched to permissive.

Because for my ROM I have to use the built-in switch since an app requires permissive (and I have no idea how to manipulate SELinux in the way Magisk and supersu do) and there is no compatible permissive kernel or even ROM yet.

So after a restart dev settings will show enforcing, then the switch kicks in, I get a toast for the changed move and dev settings says permissive. Maybe that lets play services crash. Then (maybe only after running a SN check), dev settings say enforcing again
[Magisk] teddy0209:
Full unroot... Sometimes it does if magisk can't find a backup boot.img or if the boot.img was pre-patched for supersu...

---------- Post added at 01:59 AM ---------- Previous post was at 01:54 AM ----------

Someone posted it here, i don't remember exactly, I think it's the nano version...

Hiding of permissive selinux works even if it's switched... I only tested on stock rom though...
[Magisk] ABotelho23:
It's gotta be something with boot.img. Because I tried wiping caches . And I doubt the data partition could prevent booting?

I dunno, either way it seems like people are completely ignoring our posts so it doesn't look like anybody here knows either.
[Magisk] yung40oz84:
Ya I know, I tried several kernel as well, none work
[Magisk] LucentBirch:
Still getting reboots and loss of root on 11.1. No other mods or anything installed. Here's last_kmsg. Not sure if it's the right one because I had to reflash magisk zip to get root back.
[Magisk] [Alien]:
Is it possible to have /data encrypted with Magisk on Xiaomi Redmi Note 3 Pro? What about TWRP, will it work? Xiaomi.eu ROM, Android 6
[Magisk] teddy0209:
Recovery log will help...
[Magisk] githyanki:
Don't have that phone, but I am using latest TWRP (3.0.3-0) and encrypted and enforcing Selinux. I can pass safety net and use Android Pay.

Unless your phone has some issue with Magisk, everything should work.
[Magisk] spacebar2011:
No one? :|
[Magisk] mkhcb:
[MENTION=4470081]topjohnwu[/MENTION] may you consider allowing us to specify the defualt download location and name of future updates, downloaded via the Magisk Manager? I would like future updates to be downloaded to my CyanDelta folder. That way, I can always flash the most up-to-date Magisk without having to manually move each update and reconfigure CyanDelta's settings.
[Magisk] ABotelho23:
What will the recovery log give?

Magisk flashes without errors. It just doesn't boot after. Would the recovery log log that?
[Magisk] teddy0209:
With or without error, it will still log... If there's nothing there, then a logcat maybe... The boot.img after the flash... That would be better than nothing at all...

---------- Post added at 06:27 AM ---------- Previous post was at 06:23 AM ----------

I think that depends on twrp if it can decrypt your device... Not sure about it though, i don't encrypt and haven't updated to 7...
[Magisk] koko115:
What about magisk init.d ? For now unsupported ?
[Magisk] teddy0209:
Do you see in the phh superuser that magisk manager has been granted root? If not, try to reflash magisk (just dirty flash) and see if it works for you...
[Magisk] Captain_Throwback:
Use the mod tempate ;).

The instructions are in the update-binary. You specifically want to pay attention to the post-fs-data.sh section ;).
[Magisk] KAsp3rd:
I originally posted the instruction when I was on v1. The attached zip was created with the newest mod template and should work with v5 & v6 I verified working with v6
[Magisk] adrman:
I'm curious to compare our work to see if I understood the template properly. I wrote a module for v5 yesterday, but didn't flash it yet, since v6 dropped before I had a chance.
[Magisk] KAsp3rd:
I think the only items I removed were some unneeded script files and a few lines from the update-binary. That was only due to the fact that all we are doing with this module is adding an app to to priv-app
[Magisk] stratonz:
Thanks, but magisk manager is correctly granted andòl I've already reflashed it (dirty and from scratch). Moreover I've the same problem with phh or supersu (magisk version). If it could help, the problem appear after a module installation.

Inviato dal mio GT-I9305 utilizzando Tapatalk
[Magisk] jtk_:
Tried to look for it but is there a uninstaller for Viper4android as it doesn't seem to work at all and it breaks my system EQ. Can I use the uninstaller from the official thread or do I have to reinstall my rom to get rid of it? I'm on Galaxy s5 6.0.1 stock rom if it makes any change.

Lähetetty minun SM-G900F laitteesta Tapatalkilla