yashsingh1/xdaforums huggingface dataset:
[Magisk] ruky87:
I have the same proble on Huawei P8 Lite 2017 (PRA-LX1). LOG enabled, phone can't unlock after reboot (dark screen). The other features work, if I enable Hide it works. The problem is only after reboot.... So I think there is a problem with the initialization script. Probably is a small thing to change... I checked the log before rebooting, unmounts are present

Please help, I really need this feature to get bank apps working

EDIT: I uninstalled Magisk (uninstall zip) and then installed again. Now I am unable to reinstall a clean Magisk (the above problem persist). How can I reset the initialization settings? It seems that the uninstall zip didn't uninstall everything...
[Magisk] ItzShadowz:
Is your bootloader unlocked?

Also, is dm-verity the thing which basically tells it that your bootloader is unlocked? So if you keep dm-verity disabled in Magisk Manager then no bootloader unlocked issue when buying things?
[Magisk] Didgeridoohan:
There seems to be quite a few issues with Magisk and Huawei devices... Try clearing data for, or reinstall the Magisk Manager as well.

Have you tried an unofficial beta snapshot, to see if the issue persists with the current code?

Not quite. Verity checks your device for tampering and can actually keep it from booting if to much has been altered. It also warns about your bootloader being unlocked. It's still possible for the system to see if your bootloader is unlocked (a custom kernel can hide it). You should keep dm-verity disabled though.

You'll need to enable Magisk Hide for it to mask the unlocked bootloader.
[Magisk] DodoGTA:
Yes, almost yes (https://source.android.com/security/verifiedboot/verified-boot) and yes
[Magisk] ruky87:
I will try the new version! Is there a way to disable the Hide feature at boot, and enable it after the unlock?
[Magisk] Pkt_Lnt:
Yes, yes, no
[Magisk] DodoGTA:
If it works properly, then there's no need to worry about that problem: https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Didgeridoohan:
Run the enable script manually in terminal emulator:

su
cd /magisk/.core/magiskhide
sh disable
sh enable

It'll probably show that the file can't be created in the first place. Might be that the Magisk image gets mounted read-only (or something along those lines). You'll have to fix that first...
[Magisk] Didgeridoohan:
You can mount the Magisk image in TWRP with the Mount Magisk script here: https://xdaforums.com/apps/magisk/collection-magisk-modules-v2-t3575758

Edit: But I don't know if that'll fix your issue...
[Magisk] Didgeridoohan:
Yeah... That's what I meant with the edit to my last post.

You can also run chmod as su in a terminal emulator... If you ever get it figured out, please report back. It'd be a handy thing to add to that guide you got linked to earler.
[Magisk] gregfrankenstein:
I'm guessing if I use this with LineageOS, I'd have to use a third-party access manager like SuperSU? Or could I still use the built-in Privacy Guard for granting root?
[Magisk] Artim_96:
Well, how good it would work with that one is unknown. To have the best result remove that with osmosis unsu.zip, flash the ROMs boot image and then flash Magisk. It has its own root stuff.

And better not activate busybox in Magisk settings, it only causes problems on LOS ROMs
[Magisk] gregfrankenstein:
Woah. I was under the impression that there was, at most, an unofficial Magisk module for controlling permissions. That was the impression I got from the Play Store page, anyway. But sure enough, the built-in control in Magisk Manger works wonderfully.
[Magisk] teddy0209:
[MENTION=4667597]Didgeridoohan[/MENTION]

Here is the new log...http://cloud.tapatalk.com/s/5923b03c18dfd/magisk.log.txt
[Magisk] Artim_96:
No, the Magisk manager itself controls permissions. Nobody ever said anything about an unofficial module
[Magisk] jerryshaw12:
Why my titanium backup can't ask superuser with magisk? (Xbin)
[Magisk] teddy0209:
Why not? ???

Edit: Remove other su app...
[Magisk] jerryshaw12:
Already did that, tb only recognize SuperSU for me :/
[Magisk] teddy0209:
Did you check the manager if root is activated for apps?
[Magisk] Didgeridoohan:
Man... I guess I'm gonna have to flash a snapshot on my Nexus 6. It's just too hard to read the new log without getting to know it first. :D I wonder why the log is repeated 4 times?

Curiosity: What's up with the "(Xbin)"? Do you mean that's where TiBu is looking for root? Do other root apps work?
[Magisk] alessio89g:
I'm planning to replace SuperSU with MagiskSU, because Play Store starting to classify my device as "Uncertified", but before I would like to ask for clarification, since I'm new on Magisk World.

Is it necessary use MagiskSU instead of SuperSU for pass SafetyNet/Device certification?

I use some recovery zips that remove some system apps, edit system/media (sounds and Bootanimation) and theme my Bootloader; can these mods affect SafetyNet/Device certification?

I use Unlegacy ROM 7.1.2, a vanilla AOSP Nougat ROM, with its stock Kernel on a Nexus 5.
[Magisk] DodoGTA:
Yes and no (but I recommend to make most of these mods systemless because we're using a systemless interface)
[Magisk] alessio89g:
Thanks for this clarification, but about the systemless mods, I don't think there are modules for them. :(
[Magisk] joelh:
delete
[Magisk] SvenSSSvensson:
Hey Guys!

So by mistake I deactivated Superuser rights under Settings -> Security in the Superuser app.

Now when I try to activate it again by choosing "Apps and ADB" in the drop down nothing happens and it just states Deactivated.

Which means I have root. But my apps cannot get root access through Superuser

Is this a bug?

Edit: Found the settings in the Magisk Manager. Never mind me!
[Magisk] alessio89g:
Just for curiosity, the mods that I apply in Recovery (excluding SuperSU), don't affect SafetyNet/Device certification thanks to Magisk, or don't affect it in any case?
[Magisk] DodoGTA:
Some /system mods might break SafetyNet in any case
[Magisk] xAnubiSx1:
I'm having trouble running the MagiskHide. I have a Xiaomi My Note Pro with ROM Weekly 7.5.19 Android 7.0.

I see that the folders are not being unmounted at the end

Log: https://pastebin.com/q0Xix9Nm

Already check from the post: Https://xdaforums.com/showpost.php?p=71154562&postcount=4

* Restarting the Magisk Hide daemon

* Starting Magisk Hide manually

* Kernel logcat support

* Systemless hosts

* Busybox conflict (I have no idea if I already have it installed)

Can anybody help me?
[Magisk] Artim_96:
Do you have activated busybox in Magisk manager?

Is your ROM pre-rooted?
[Magisk] Chocklety Boyee:
There is a magisk module to fix this issue..
[Magisk] xAnubiSx1:
Could you tell me what the module is?

I try It, enabled and disabled.

And It is not pre root

Enviado desde mi MI NOTE Pro mediante Tapatalk
[Magisk] Chocklety Boyee:
Xaom8 safety net fix 1.8.1.zip..google.it..
[Magisk] xAnubiSx1:
I came to this thread, because dont work the fix for the safetynet and it's because the magiskhide is not actually working

Enviado desde mi MI NOTE Pro mediante Tapatalk

I've been reviewing the Busybox issue, if I activate it in Magisk Manager and run

leo:/system/xbin # ls -la
ls -la
total 368
lrwxrwxrwx 1 root root 20 2017-05-23 19:43 acpid -> /data/magisk/busybox
lrwxrwxrwx 1 root root 20 2017-05-23 19:43 add-shell -> /data/magisk/busybox
lrwxrwxrwx 1 root root 20 2017-05-23 19:43 addgroup -> /data/magisk/busybox
lrwxrwxrwx 1 root root 20 2017-05-23 19:43 adduser -> /data/magisk/busybox
lrwxrwxrwx 1 root root 20 2017-05-23 19:43 arp -> /data/magisk/busybox

but

leo:/system/bin # ls -la
lrwxr-xr-x 1 root shell 6 1969-12-31 21:00 chcon -> toybox
lrwxr-xr-x 1 root shell 6 1969-12-31 21:00 chgrp -> toybox
lrwxr-xr-x 1 root shell 6 1969-12-31 21:00 chmod -> toybox
lrwxr-xr-x 1 root shell 6 1969-12-31 21:00 chown -> toybox
lrwxr-xr-x 1 root shell 6 1969-12-31 21:00 chroot -> toybox
lrwxr-xr-x 1 root shell 6 1969-12-31 21:00 cksum -> toybox
[Magisk] Artim_96:
I think that's exactly what it should show. So that means it was not activated when you got your error.

But are you sure Magisk hide doesn't work? Install RootBeer Sample, App it to hide (maybe deactivate and activate in servings), reboot and then run it and report back which points are not passing (you might need to disable busybox since at least for me it's always detected
[Magisk] xAnubiSx1:
What do you mean by disable busybox? Disable busybox from Magisk Manager? Or rom (I do not know how disable from rom)
[Magisk] Ibuprophen:
I was just wondering if anyone (or even [MENTION=4470081]topjohnwu[/MENTION], though, he is probably aware of it already) had noticed the following LineageOS Biweekly Review from May 15th?

If you go to the following, direct link, and scroll down a bit, you'll see a title "Kernel su-hide to address an important vulnerabilty".

LineageOS' Biweekly Review #9 - Gello, Jelly and a security advisory {15 May 2017}

I posted it here as it does pertain to the devices SU file and what they had done.

I just wanted to provide a little friendly FYI...

Thanks!

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Magisk] teddy0209:
That, I don't know... I enabled advance logging and the log grew like that... MIUI is really interesting, lol... ???... Don't have any problem on my M9...

---------- Post added at 05:44 AM ---------- Previous post was at 05:40 AM ----------

Magiskhide is not working, like any other miui rom... Manually restart magiskhide via terminal, or apply su -c fix on the enable script... If you decide to edit the enable script, do not use modules that activates magiskhide at boot, it will just cause a conflict...

Edit: Try this, restore your boot.img and remove magisk first...

Edit: Sorry I can't attached the file, must be data limitation...
[Magisk] bundysoat:
Buddies!

I have a problem, I installed the zip but not work, yesterday appears as the same, but install the zip and works, today not work, what is the problem?

Thanks
[Magisk] Chocklety Boyee:
But i tried and magisk hide worked with that module...just enable magisk hide option..but fix should be activated ..then hide all google component and safetynet app too ..then u ll pass safety net even on dev rom ..i have tried personally ..but i lost root ..only magisk installed with safetynet ...i got that result on official magisk not on Snapshot build ...
[Magisk] Artim_96:
Manager of course. For your ROM you'd need s removal zip for recovery
[Magisk] teddy0209:
On MIUI it's almost certain that you will lose root if magiskhide is activated with su... If ever you lose root, remove and reinstall.. keep modules to minimal, just props module, and don't add anything to hidelist, just a rootchecker app to check if magiskhide is working properly...
[Magisk] ilya142536:
good afternoon friends.

I apologize in advance if I made a mistake with the topic, but I have difficulties with magisk.

I install magisk, through twrp install v12. Everything goes well. Instead of supersu, magisksu becomes, two green ticks appear. But unfortunately, the profile check is not suitable.

So that's what you need to do to successfully start working Magisk and hide the root from ap?

This is the data of the phone at the moment. Already several times rolled the backup

[b]Телефон[/b]
Кодовое имя: [color=blue]m7[/color]
Модель: [color=blue]HTC One[/color]
Версия загрузчика: [color=blue]1.61.0000[/color]
CID: [color=blue]HTC__102[/color]
MID: [color=blue]PN0710000[/color]
Радио: [color=blue]4T.35.3218.16_10.33Q.1718.01L[/color]
Прошивка: [color=blue]M7_UL_L50_SENSE60_MR[/color]

[b]Подробнее о телефоне[/b]
Security Flag: [color=blue]S-OFF[/color]
Bootloader: [color=blue]**UNLOCKED**[/color]
Recovery: [color=blue]n/a[/color]
SuperUser: [color=blue]SuperSU v2.79[/color]
BusyBox: [color=blue]BusyBox v1.25.1-meefik[/color]
Ядро: [color=blue]Linux version 3.4.10-g8195b49[/color]

[b]Подробнее о прошивке[/b]
Версия Андроид: [color=blue]5.0.2[/color]
HTC Sense: [color=blue]7.0[/color]
Версия SDK: [color=blue]21[/color]
База: [color=blue]7.19.401.51 CL482424 release-keys[/color]
Имя прошивки: [color=blue]InsertCoin 7.1.3[/color]
[Magisk] dahawthorne:
Have you ticked MagiskHide in Settings?
[Magisk] teddy0209:
You probably have a leftover...

Remove all remnants of root, also remove the busybox you installed... Then. Reinstall magisk...
[Magisk] SvenSSSvensson:
Before I switched to Magisk I flashed SuperSU.

Now I get these annoying "Su binary out of date" messages.

Is it safe to use "Cleanup for permanent unroot" in the SuperSu app and keep root from Magisk?
[Magisk] dahawthorne:
I found that the built-in SuperSU unroot didn't fully work. Try Osmosis' Unsu - https://xdaforums.com/showpost.php?p=63615067
[Magisk] Didgeridoohan:
I had time to do some testing this morning. The log grows like that on every logging event. I suspect a bug with verbose logging in the current code... Gonna do more testing tonight.

That information shows that you're still using SuperSU. Magisk works with systemless SuperSU, but Magisk Hide can't hide it. That's why SafetyNet is triggering.

As already suggested, you'll need to do a full unroot and reflash Magisk.

Permanent unroot should work fine. Just make sure to restore the stock boot image. You'll also have to reflash Magisk to install MagiskSU.

---------- Post added at 11:22 ---------- Previous post was at 11:20 ----------

I've used the built-in full unroot for SuperSU several times without issues. If course: YMMV.

The unSU script is brilliant though. :good:
[Magisk] teddy0209:
Cool, thanks!!! I've been trying, but I'm not good with codes, just not my forte... ???
[Magisk] gsser:
i tried to port a rom dirty way and changed boot.img etc etc.

then flashed it and flashmode nor fastboot was dead.

so (my eng is not very good) will it install like a rom with boot.img or just a regular zip like init.d's or music mods? (i used BETA-SuperSU-v2.52.zip for root)
[Magisk] JudgeDread11:
It will patch the boot image, like SuperSU. To install you'll need to uninstall SuperSU first.
[Magisk] gsser:
so there is no risk getting it hard bricked like flashing another phones rom?

---------- Post added at 09:27 PM ---------- Previous post was at 09:06 PM ----------

well, flashed it on recovery and reboot. its been five minutes and its still at sony logo. seems like it doesnt support.
[Magisk] swent:
Still need this? I'll upload a stock boot img of the SM-N930F version if you want.
[Magisk] moriel5:
It does, you just need reflash boot.img first.

Reflash your kernel (boot.img), and then flash Magisk.
[Magisk] patch_Adams:
Hello!

I am building pure aosp N for shamu (nexus 6). Is it possible to sync this into the build?

Thanks!
[Magisk] rebretz000:
Thank you very much for this amazing app/tool. I just updated my LG Nexus 5X to the latest monthly security build without wiping anything. Everything work perfectly.
[Magisk] putridfoetus:
Viper does not show the option to uninstall. There is a folder in /data/app, but not /data/data/.
[Magisk] Mao04:
Thanks for this. Yeah, I've read the OP (multiple times) and even modified a couple modules to install apps systemless, but I'm still not too clear on exactly what it is I'm doing (especially with cache). Looking though your mod will help me understand. So thanks again.
[Magisk] CrazyCypher:
Hy guys, I have a few mods running through Magisk, but I have to ask because I dont know - Do I have to disable magisk to successfully perform OTA update?

Or can I leave it enabled and OTA will still be achieved? I know it does not modify the system, but I dont know either if OTA check sees the mask or real system situation?

THank you :)
[Magisk] topjohnwu:
Is it the Exynos version that is unlockable? Of yes, then please upload one :)

Thanks
[Magisk] swent:
Yes, sent you a PM yesterday with the link, have no clue how that vanished.

Anyway, here is the zip containing the backed up boot image + its md5:

https://drive.google.com/open?id=0B0JC5t2OfDUwaHJmdTYxb0Q5d2s

To be precise its the SM-N930F model, if you have anything I could help with or test (debug/testversion), just let me know.

I'd be happy to help out (since I can't wait for systemless mods to work on the Note7).

Thanks for the great work!
[Magisk] Fedroid:
In most cases you need stock recovery to receive Ota. In other cases you need also to toggle root off before installing it.

At this moment is enough...
[Magisk] hotcell:
Let's say we have stock recovery and root toggled off. What would be the steps to re-enable everything back after performing OTA install? What are the chances to survive OTA that way?
[Magisk] FLYER37:
It's amazing! But if i used chainfire's suhide, Magisk can work, SafeNet can't be passed, Android Pay can't used.
[Magisk] JudgeDread11:
Hi guys,

I need some help.

I have created a mod to set C-locker as a privileged system app. (I want to try if it will solve/reduce the lag for C-locker start)

The mod works, in the sense that C-locker appears in the priv-app directory. But it doesn't appear in my launcher or the app list in settings.

When looking at the difference between the folder containing C-locker and other priv-app apps in FX explorer the first obvious difference is the text color of the folder name.

Unfortunately i can't find which color stand for what in FX explorer :(

An other difference is that in details the "containing filesystem" for C-locker is /system/priv-app while for other apps is the app folder itself.

Can anybody explain me what is going on and how I can solve this?
[Magisk] JudgeDread11:
I forgot some screenshots of what I am talking about. :)
[Magisk] Nomelas:
Doesn't modifying the system partition defeat the purpose of magisk?
[Magisk] soder:
I guess he's talking about the dummy version of /system.

/Söder
[Magisk] ilya142536:
Oh sure. I have included this item
[Magisk] dahawthorne:
As [MENTION=4667597]Didgeridoohan[/MENTION] & [MENTION=3615867]teddy0209[/MENTION] said, you need to do a full unroot of SuperSU. If the built-in uninstaller works, good, otherwise use Osmosis' Unsu to make sure. Once you've done that, you should flash your boot image again - I would guess, I'm not sure, that SuperSU restores the original backup which it took during installation, but if you want to be 100% certain a boot image flash from your original ROM is best. This is because (if I've read the installation logs correctly) Magisk does quite a bit of work on the boot image before it installs it, and you don't want to risk installing a changed image of an already-changed boot image.
[Magisk] SvenSSSvensson:
Cool! Does this also restore the boot image mentioned in the post below?

I'm using a custom ROM (Maximus). That ROM actually installed Magisk for me.

So I guess I could just dirty flash the ROM if I need to install it again.

Edit: I'm not sure how to flash the boot image again. Do you think the Maximus Aroma Installer takes care of that?

I'm really not in this game anymore. Lost most info I once knew.
[Magisk] teddy0209:
No it doesn't... It is inside the rom zip... Reflashing the rom should also take care of it...
[Magisk] Slomies:
I can't get Solid Explorer to work with Magisk. It works with Titanium Backup and other apps that require root. If I try to created a folder in /system/app then I get the error message saying it cannot create the folder. Any ideas?

EDIT: I'm using a Google Pixel
[Magisk] Kloosek:
@up, I use Magisk (v13) and Solid Explorer works great.

Wysłane z mojego LG-H850 przy użyciu Tapatalka
[Magisk] Mistercraft38:
Hi, I have an issue with magisk and my Moto G4... When I try to install magisk, at the system reboot, it's just don't boot: I haven't the advertisement about my unlocked bootloader and the screen stay black (I already try, it stay more than 10 minutes)...

All partitions​ are stock, except the recovery (TWRP)

Motorola moto G4 Build: NPJS25.93-14-4

Thanks for help
[Magisk] Chucknorris1975:
Keep loosing root. Running Crdroid 3.2. Was working with previous version of CrDroid.

Can't seem to attach log file.
[Magisk] DevShekhawat7:
Tasker is not prompting for root access
[Magisk] RandomPooka:
Known issue. Look under [MENTION=4667597]Didgeridoohan[/MENTION] signature for THIS LINK to fix
[Magisk] 13680201:
HI

Why show not rooted?.what's I can solved it.

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] buffer overflow:
Try to reflash Magisk.
[Magisk] Artim_96:
Your screenshot only shows that you can view files in /system, the question was to get r/w permissions

---------- Post added at 09:26 AM ---------- Previous post was at 09:23 AM ----------

I hope you know that you are supposed to use Magisk for that kind of stuff? Using Magisk and then trying to mount /system r/w completely defeats the sense of Magisk. It basically exists just to manipulate /system without having to write to it and breaking stuff that way
[Magisk] dahawthorne:
The bottom item in the screenshot is a folder called "Created using Magisk".

Edit: And I've just done the same myself. I'm on Magisk v12, Solid Explorer Pro, and I created a folder in root as easily as in internal storage.
[Magisk] Artim_96:
Have you disabled busybox in the manager?

And if XDA fails to upload files, rename .log files and files without any suffix to .txt. otherwise copy its text to pastebin.com and post the link

---------- Post added at 09:30 AM ---------- Previous post was at 09:29 AM ----------

I would read "created using Magisk" as created by making a module for it... And that's how it's supposed to be, that's the main reason Magisk exists
[Magisk] dahawthorne:
I don't know what this comment means, but I take your point that it's a bit absurd to corrupt /system by manually creating folders in it.
[Magisk] Aulin86:
Thx to magisk I can use Androidpay, thx guys

Inviato dal mio MI 5 utilizzando Tapatalk
[Magisk] markurt30:
hi guys. i'm search for a solution to remove supersu, for install magisk. does anyone link me the discussion page? thank you
[Magisk] Artim_96:
Osmosis unsu.zip as already posted about a thousand times. Or just what supersu offers you in its app plus maybe flashing your ROMs boot.img just to be sure. But this will only help if it's not prerooted. If the boot.img itself contains root, you'll need a different ROM or at least a kernel with its own ramdisk not containing root
[Magisk] markurt30:
i have slimm rom, preerooted with 3.4.0 elitev3 kernel. i have had some problems with supersu, i would like changing with magisk. i think won't be easy
[Magisk] Didgeridoohan:
If it's pre-rooted you might have difficulties. The boot image is probably patched for SuperSU and because of that the Magisk installer will fail. If you can find a clean boot image to match your ROM, flash the unSU script and then the clean boot image. After that you can flash the Magisk zip in recovery and you're done.

Or, change to a ROM that doesn't come pre-rooted.
[Magisk] markurt30:
yes, it's a preeroted rom. i'm waiting for lineage or carbon, thank you for all the informations, anyway
[Magisk] Artim_96:
Depends on how it is prerooted. CM/LOS based ROMs have their own root stuff, not supersu, there unrooting if no problem. Then there are ROMs only including the supersu zip and just automatically install it systemlessly after the ROM Installation is finished (there you should see the supersu zip in the ROM zip), unrooting them is even easier, it's basically just flash the boot.img even though it won't delete stuff like the su.img in /data. But then there are ROMs having it included into the boot.img, there you'll find no supersu zip but supersu is installed in a fresh installation. Getting rid of that the only way is to either use a different ROM or a different kernel that has its own ramdisk so it would fully replace the changes made to let supersu run systmlessly
[Magisk] xAnubiSx1:
* Manually restart, didn't work.

* su -c fix, didn't work.

* Restore boot.img (dirty flash rom) + Magisk, didn't work
[Magisk] DodoGTA:
Your device's kernel doesn't have setns support for the mount namespace
[Magisk] Kloosek:
Look at the last folder on screenshot, it was created not by Magisk, it was created by Solid Explorer using Magisk SU.

Wysłane z mojego LG-H850 przy użyciu Tapatalka
[Magisk] dahawthorne:
As I said four hours ago... :)

https://xdaforums.com/showpost.php?p=72422895&postcount=13830