yashsingh1/xdaforums huggingface dataset:
[Magisk] hsiehboss:
Mod Edit - Link Removed

我從使用 Tapatalk 的 Nexus 6P 發送
[Magisk] Darke5tShad0w:
Please Link directly to the creators work so the user can give thanks and be sure they are downloading the original and not a tainted copy.

Here it is:

https://xdaforums.com/showpost.php?p=63615067
[Magisk] Pkt_Lnt:
Thank you. To add to this, the devs have download counters to see if a file is useful and whether to keep it, improve it, or remove it.
[Magisk] masri1987:
so i've been using this also,

I have tried ROm > Kernel > unsupersu zip > Magisk and i get the same supersu patched boot error telling me to flash supersu first
[Magisk] Darke5tShad0w:
Sorry, I should have said this to you earlier but it only removes all file traces, nothing in the boot image.

To get a non modified kernel you are either going to have to change to a different one or ask your developer if he can provide one or provide you a non supersu boot image.
[Magisk] Bad--Dog:
Did the 12.0 update today cause it keep popping up now my Android pay doesn't work any more still dings and vibrates but won't complete the transaction... How can I go back to previous version
[Magisk] mobileman88:
Still works for me on my 6p. What device are you on?
[Magisk] SDMU:
Can I convert Magisk Manager to a system app ? If yes , which app can I use ? I tried using Titanium , but it has been showing "processing" for quite some time .
[Magisk] karthik km:
Link2sd

It can
[Magisk] SDMU:
Any reason why Titanium cannot ?
[Magisk] karthik km:
Titanium is converting by installing app into directly to the system and app directly goes to /system/app it won't get classified

But Link2sd

Just copy the app to the system and with apps proper libs and it ask for a reboot

Here app and its data properly classified
[Magisk] Venats:
I seem to be stuck on Magisk 12.0 getting root permissions?

I fresh flashed Axon 7 to 7.1.1 and installed Magisk 12.0 but later it says "Rooted but no root permission, not allowed?" not sure what I am doing wrong? Worked fine when I had previously been using SuperSU but I want to use Magisk Hide and that requires removal of SuperSU as I understood.

Everything seemed to install correctly, just seemingly limited/no root permissions?
[Magisk] Bad--Dog:
Nexus 6
[Magisk] alb.boy:
Sorry, one quick question. I have flashed an custom rom on my S7 and i have Magist v11.1 installed from the rom, now i receive an update what to do, can i directly type from in the application "Download&Install" but my question is do i have to check those to lines into the advanced setting? Thanks in advance :D
[Magisk] Didgeridoohan:
Have you tried keeping the Busybox toggle in Manager settings disabled?

---------- Post added at 08:45 ---------- Previous post was at 08:42 ----------

Have you made sure Magisk Hide is starting properly after updating/rebooting? Check the logs. Might take a couple of reboots after an update for it to work properly.
[Magisk] Venats:
Due to the lack of seemingly any root permissions showing up for Magisk (from MagiskSU), I don't even get to be able to see Busybox. Right now, Magisk Manager looks as if I had installed it on an unrooted devices where Settings is all of like 5 options.

Standard checks, and Magisk Manager itself, say the device has root but Manager says no permissions. Somethings not right with MagiskSU, maybe its an Axon 7.1.1/Nougat problem.

Edit: Actually, testing with Root Checker seems to suggest its ~not~ rooted. So I have conflicting information, seemingly something is not working with MagiskSU installing. Could it be a formating issue? My device is ext4.
[Magisk] Didgeridoohan:
If you don't know what they are, probably not. That's why they're called "advanced settings".

---------- Post added at 08:50 ---------- Previous post was at 08:48 ----------

Ah... From your post it sounded like you lost root after using it for a while. This is something else than the usual "losing root"-issue.

Might be a compatibility issue...

Do you have a recovery log from the installation. There's a slight chance it might show something.

Edit: compatibility issue with your device's boot image that is, not ext4...

---------- Post added at 08:52 ---------- Previous post was at 08:50 ----------

Why?
[Magisk] Venats:
Sorry for not being super clear, hah.

I think its compatibility with MagiskSU with the current Axon 7 7.1.1 boot image, because SuperSU works perfectly fine (but obviously won't allow for MagiskHide) so long as its installed in ext4. Magisk Manager also works "fine" with SuperSU (aside from the obvious loss of Hide functionality). So process of elimination says its the boot image having a conflict with MagiskSU.

I didn't save a log, unfortunately, had not anticipated the issue. If I do it again (and don't just give up and return to SuperSU), I'll save a log.
[Magisk] SDMU:
It was a trivial issue :) , I use ADM downloader , whenever I download a Magisk ,Xposed module , ADM intercepts it and I will have to probably flash it manually . I stumbled upon the Download Redirection module , which has an option to prevent ADM from intercepting download processes by system app . As Xposed was installed as a system application , I had no further issues with it . However Magisk was still an user application and all the updates and downloads (both for Magisk and the modules) were intercepted by ADM . Hence I wanted to make Magisk a system application :laugh:
[Magisk] Didgeridoohan:
Cool... Nice to see someone with a real need for something like that, for a change. :p

To keep it nice and systemless (you're using Magisk :D ), you could adapt the App Systemizer by [MENTION=2226076]stangri[/MENTION] to do it for you.

Edit: Or probably use the app included with the Systemizer nowadays... Note to self: try to keep up. :)

Edit2: Or maybe not... I just tested and couldn't quite get the app to work for me. Editing appslist.conf worked fine though.
[Magisk] Pumpino:
I've just switched from SuperSU to Magisk on my wife's Xiaomi Redmi 4, as she wants to use an app called Qkr! with MasterPass to make payments to our daughter's school. The app won't work when the phone is rooted.

I'm a bit confused by what I need to do. Do I need to somehow change a setting for Qkr! within Magisk Manager that means it will work every time?

Also, I've installed Magisk on four devices and they all say SafetyNet Failed: CTS profile mismatch. What does this mean and how do I fix it?
[Magisk] karthik km:
Saftynet failed : CTS profile mismatch

This problem always be there with the Google's latest security patch

You are requested to use Magisk Hide option to hide root from your payment app

Or

for Saftynet issue

Just go back to the previous post in this thread

Because this question asked and answered so many times
[Magisk] WorD ZerO:
Hi, I just updated to Magisk v12.0 and lost root there after. Should I uninstall using the uninstaller zip in the op and reinstall using the v12 zip file to check if I get back root? Will I lose my module settings?
[Magisk] RDDraco:
Try to reboot your phone 1 or 2 times. For some reason Magisks randomly loses root. (Or just might be an Samsung isuse)
[Magisk] Kloosek:
I have a similar problem on my LG G5 (Fulmics 2.0 + Asgard_v3 kernel). However, there is no solution for me. Only back to version 11.6, then everything works fine.
[Magisk] BootloopedMillennials:
Its not only a Samsung issue. Have it on my Moto X. Everytime a reboot regains root.
[Magisk] Pumpino:
So, rather than being able to permanently hide root from certain apps, I would need to go into Magisk Manager to hide root, use the payment app, and then unhide root in Magisk Manager once finished?
[Magisk] WorD ZerO:
I did try rebooting but it didn't turn out to be successful in restoring root. Oh I am sorry, I should've mentioned the environment. I am running Magisk on OnePlus 2 with Oxygen OS 3.5.8 and stock kernel (If that matters).
[Magisk] dahawthorne:
Why "break" the app by unhiding it again? Why not just leave it hidden?
[Magisk] culiacanazo:
[MENTION=4667597]Didgeridoohan[/MENTION], [MENTION=4470081]topjohnwu[/MENTION], to whom it may concern, do you happen to know if this by any chance would happen to be a bug?
[Magisk] culiacanazo:
Because the more you check the more unstable magisk becomes. It's in the op. Got read? :D
[Magisk] Didgeridoohan:
Ha! Took a few second to see what you're talking about. Is Hide not enable at all or just not showing up in the Manager? What's in the Magisk log?
[Magisk] culiacanazo:
When that did happen to me (usually after flashing whatever.zip/started noticing a pattern) i simply installed it (Magisk) right over its old self, and that got rid of that.

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

I disabled it earlier and then i just got home and checked to see how Googie (intendedly spelled) was doing, and everything was as good as usual.

Then, i went on to check on every tab as i routinely do, and that's when i noticed/remembered that it was disabled
[Magisk] culiacanazo:
The only thing fun might be here because before that nothing but skeletons, after that nothing but magisk hide...

What do we call this "problem"? :confused:
[Magisk] Citizen_Snips:
Eh, OP says it's known to happen on certain custom ROMs like LoS, when Magisk busybox is enabled.

This isn't an issue on my Nexus 6P. I have a stock based ROM with latest security patches. Magisk v12, I've enabled busybox, hide & systemless hosts and I've not had a single issue losing root or failing SafetyNet leaving those enabled 100% of the time. Not once. AP works (I don't play any games on my phone except for PS4 remote play, thanks again magisk!).

Using it a lot or leaving it checked doesn't automatically make it unstable, it depends on phone and ROM combination. I got reads! :laugh:

Edit: hmmm, FAQ also says if your ROM doesn't pass SafetyNet itself, Magisk can't help. Older versions of the ROM I am on did not pass by itself, but flashing Magisk and enabling hide worked and it passed. I added my cards to AP no issue.. The version I am on now can pass by itself since a new update, but the older one couldn't and Magisk fixed it. Weird.
[Magisk] WorD ZerO:
Thank you. I shall try this and report.
[Magisk] sysbus6:
Installed nougat venom rom on my phone. Magisk is built in. Now, Root Explorer tells me i'm not rooted. I know my phone is rooted. Does anyone have a fix?
[Magisk] culiacanazo:
Maybe, just maybe, rom thread?? Since they implemented it. Didge might have a better answer tho
[Magisk] aer0zer0:
What does magisk manager tell you?
[Magisk] sysbus6:
Posted same msg in their forum, just thought I would also ask here.........
[Magisk] Newmanl:
HELLO guys, was wondering how it's Magisk going with Samsung galaxy S7 edge???
[Magisk] sysbus6:
magisk v10.2 installed, properly rooted, 17 me.phh.superuser cm-su subind suinit
[Magisk] aer0zer0:
Which phone, sounds like you need to really update magisk. 10.2 is pretty old
[Magisk] sysbus6:
HTC One M9.
[Magisk] teddy0209:
I have no issues on my M9... Root Explorer properly detects root... Did you try asking on the rom thread?

---------- Post added at 02:59 PM ---------- Previous post was at 02:54 PM ----------

Yup, it's totally device and setup dependent... I have evething enabled, never turn them off, never had issues... ?
[Magisk] aer0zer0:
try the latest magisk 11.6 and see if it helps
[Magisk] Captain_Throwback:
You mean v12?
[Magisk] tofu:
I have Oneplus One.

Tried flashing latest Magisk v12 after clean flashing OmniROM, but once I reboot and try to open the Magisk manager, I get a message saying "now available on Play Store" or something similar. I don't use GAPPS, so I don't have play store access. But why should I install anything from play store anyway since I have just flashed the Magisk v12? Root isn't working either.

Tried Magisk also after clean flashing NuclearROM, but again: "Install on Play store, Magisk MAnager is now on Play store! Please Download from Play Store for future updates!" and then only option is "Go to play store". If I click that, the Manager force closes.

So what am I doing wrong?
[Magisk] Captain_Throwback:
If you don't have Play Store access, then you have to download Magisk Manager from the official thread. Magisk won't work without the Manager; what's in the zip is just a stub that tells you to install it and links you to the Play Store link for it.
[Magisk] Krunk_Kracker:
In case someone else has this issue, I ended up dirty flashing my rom, running unsu, and v12 installed fine with Magisksu.
[Magisk] sysbus6:
Upgraded via Magisk Manager to v 12. Phone is rooted on all apps, even passed sn.

Thanks for tips all the info!!

Happy trails, team..... we'll talk again!!!
[Magisk] aer0zer0:
you mean v13 snapshot?

lol, yeah
[Magisk] s0r00t:
On my Redmi Note 4, Magisk (v11.6 AND v12) breaks the Basic integrity SafetyNet test, with or without Magisk Hide.

(NOTE : Xiaomi ROMs do not follow the CTS requirements, so CTS always fail. However, I do not care about this test, so it's not important for me)

Before installing Magisk, the basic integrity test passes, therefore I can freely use apps such as Super Mario Run.

After installing Magisk (nothing else than flashing Magisk through TWRP, no additional modules, no Xposed), the test fails.

I've opened an issue on GitHub (#147), but topjohnwu closed it, claiming that it wasn't Magisk's fault.

I don't know what to do, should I toggle Hide on specific apps?
[Magisk] Captain_Throwback:
If the dev already said it's not the fault of Magisk, then why are you posting here?
[Magisk] s0r00t:
Because that's Magisk who trips the Basic integrity, or I cannot see what else it could be.

Even on a stock ROM, Magisk installation trips the basic integrity.

I might be totally wrong, but I have no idea where else it could come from.
[Magisk] usflightboy:
Now this does NOT work on the US versions of the Galaxy S7/S7e correct?
[Magisk] Rush94:
Why is systemless host automatically re toggles himself (off all time ) this bug was persistent since i started using magisk from v11.1

device Condor Moto E (1gen)

rom : RR 7.1.1 r9

Kernel : clarity Reborn 1.7

Current Magisk : v12 core only mode
[Magisk] Jedgina:
Sm-g920f

Galaxy s6. Thank you.
[Magisk] HeroCC:
I want to use Magisk, Root, XPosed, and Android Pay / SafetyNet. I got safetynet to not trigger with rooted / magisk, but when I install systemless xposed it says 'CTS profile mismatch'. Any idea how to fix it?
[Magisk] Captain_Throwback:
This question should be banned.
[Magisk] siri21:
Easy... Remove xposed

Magisk hide couldn't hide xposed bro. It just hide core magisk function. Read well before asking. This question shouldn't be in this thread...
[Magisk] espresso70:
Hello,

I recently upgraded from v11.6 to v12.0 and RBC Wallet force closes every single time. This was the behaviour in some versions of Magisk where it would fail the root check or be forced closed (sorry, I didn't keep track of the versions). When I last tried RBC Wallet on v11.6, I was pleasantly surprised that it was working again so I re-installed v11.6 and RBC Wallet works again.

Is there something I can do to help you debug this? Thanks.
[Magisk] stormxbijuu:
Reboot and root gone

when I install magisk (galaxy s4 5.0.1)

it works for a bit

but after a little the screen freezes then reboots, vibrating twice and then I lose root

I need help because I cant even use magisk :(
[Magisk] aaubets:
Hello!

I have a Kobo ARC 10HD with Cyanogenmod 12 rooted with SuperSu. I installed Magisk Manager from Google Play and then installs Magisk v12 in Magisk Manager. After reboot, SuperSu was deleted and I lose root privileges.

I tryed flashing Magisk v12 in TWRP, flashing SuperSu again in TWRP, and a lot of diferent combinations. Nothing works... Always i finishing losing root privileges or without modules installed.

In one of my attempts, I can access to install Modules (Magisk Manager with Magiskv12+SuperSu working together) but after flash some module (in Magisk Manager) and reboot, I lose SuperSu again or I can't view modules installed on Magisk (I tried a lot of times and different combinations).

I also tryed with phh's superuser but it don't root my device.

What I'm doing bad? Some incompatibility with CM12 or SuperSu? Can be a problem of my device?

Thank you very much! And excuse me for my bad english :)
[Magisk] korxil:
Can anyone help me resolve this "Error executing updater binary in zip" message when trying to flash Magisk v12? TWRP Log is attached. Let me know if you need anymore info. Thanks.

HTC Desire 610, Cyanogen 12.1, TWRP 2.8.0.1
[Magisk] M4rt1n94:
Pls Update your TWRP to 3.1.0-0 ---> https://dl.twrp.me/a3ul/

This is the important Part

After Updating the TWRP try to reflash :)
[Magisk] Karls0:
I also had random reboots on S4, but it was on 6.0 based rom. Since I'm on 7.1, I don't have this issue. Only maybe once I temporary lost root access, but reboot fixed it.
[Magisk] Pumpino:
Let me put it this way - the app currently doesn't work because it reports that the device is rooted. What do I need to do in Magisk Manager to get the app to function?
[Magisk] _alexndr:
Hello [MENTION=4470081]topjohnwu[/MENTION]

Thanks for v12 update. Finally works well with my Samsung N910F

I have one problem:

I'm working on systemless solution (a complete set of modifications designed exclusively for Samsung devices) - not dependend on root solution (of course - we know that there are only 2 choices - SuperSU & MagiskSU). This systemless modification uses script that need to be run in post-fs-data and it uses bind mounts.

This script works well in case of SuperSU (as su.d script, without Magisk)

Unfortunately, in case of placing it in /magisk/.core/post-fs-data.d it does not work as it should. Bind mounts seem to work well, but seems like commands were run to late because modded files (e.g. apks and xmls in /system/csc/...) do not work - there is no expected effect.

Could you fix your post-fs-data.d to let bind mounts triggered from post-fs-data.d script works well, as in case of SuperSU's "su.d" ??

At this moment it is the only reason why MagiskSU is not main root solution in case of my work (custom ROMs and systemless MODs combo for Samsung devices)
[Magisk] :
Had problems with constant crashing of NFC, wifi and others with magisk 12. However the safety net check passes on 12 where as it didn't on 11.6
[Magisk] Thelgow:
Am I missing something with this in regards to VZ Galaxy S7? I had root on it, installed Magisk, it offered to install v12, now I get "Start up failed".

Now I have to go back to stock it looks like.
[Magisk] korxil:
After flashing TWRP 3.1.0.0, I've entered a bootloop when trying to enter TWRP. I had this problem before when I first tried to get TWRP on my phone, but I forgot how I fixed it. I can access bootloader after my phone battery dies. What do I do to access TWRP?
[Magisk] pogs24ever:
I don't know if this was mentioned before

FYI.. If ever you want to encrypt and decrypt your phone make sure to uninstal it first.. Possibly due to bootimage modification.

Other than that.. This is superb! Using m8 stock rom
[Magisk] mchapa489:
How do I enable magisk hide? Sorry I'm new to magisk
[Magisk] teddy0209:
In settings?

---------- Post added at 01:04 AM ---------- Previous post was at 01:02 AM ----------

Did you try to start clean? This usually eliminate most issues...
[Magisk] sonysingh1983:
Settings, should be a box there for magisk hide, tick it.

Then go back to main magisk screen, Click on three line button at top left, then u should c a section for magisk hide along with modules, downloads, etc. Then just tick whichever app u wanna hide. Restart magisk.
[Magisk] digitalhigh:
I refuse to accept your retirement. It would be amazing to see you and [MENTION=631273]Chainfire[/MENTION] working together on this - I personally think that allowing root to run while Pay is active is *not* the proper solution, and will eventually piss off the bear that we are continuing to poke. It would be much better to to see you guys collaborate and work on a method of disabling root when necessary, thus potentially keeping the banking powers-that-be somewhat complacent and accepting of us keeping root.

Here's hoping to see everybody work as a team...Magisk is an awesome concept, and SuperSU is absolutely the best. It would be a pity to see a disagreement such as this affect the entire community.
[Magisk] Captain_Throwback:
First off I want to say that I appreciate all the work you've done on Magisk. Since I was someone with an outlier case with SuperSU v2.76 not working properly on my device, you took it upon yourself to develop a working solution. At the same time that solution became what I feel is an amazing framework for applying mods systemlessly, regardless of root, Xposed, or anything else. I would hate to see all of your great work go to waste over a disagreement/misunderstanding.

I, like [MENTION=3400685]digitalhigh[/MENTION] hope that you and [MENTION=631273]Chainfire[/MENTION] (and maybe even [MENTION=1915408]phhusson[/MENTION]) can work together on a solution that makes everyone happy. The whole idea behind Android and open-source is for people to help out each other. I understand that SuperSU is closed source, but hopefully [MENTION=631273]Chainfire[/MENTION] can help you apply the concepts involved for an open-source solution that also works? Even if not, I'd say you should keep moving forward with Magisk. If you remove the root component, it doesn't change the functioning of Magisk, so maybe that is the best way to move forward. I know that will mean that some devices can't be supported (read: Samsung), but if that's what it takes to keep this going, I say, do it. And then maybe some other developer with a Samsung device and the knowledge/ability/willingness to help will step up and make it work.

So keep your head up! You've done great work here, and it shouldn't be taken lightly.
[Magisk] bumpaneer:
[MENTION=4470081]topjohnwu[/MENTION]

I would like to agree with the above sentiments, and express my gratitude to you for this project. I think the Magisk framework has amazing potential and I hope you continue development. If you decide not to, please understand that the community appreciates all the time and effort you put into getting this project off the ground and functioning for the majority of users who've tried it.
[Magisk] ianmacd:
I know you're upset at the moment, but this statement seems absurd. Samsung have arguably done a great deal to further the cause and popularity of Android. Creating devices that are a pain in the arse to root doesn't equate with being malignant for the whole operating system. At the same time, I recognise that you personally have been caused a great deal of frustration with them over the last few weeks.

I know we're off-topic here, but since you raised it in your own thread, I wanted to provide an opposing opinion.

You know what, for the life of me, I can't understand why people are so eager to use Android Pay, anyway. Why would anyone want to use their phone to make a purchase, when electronic devices can fail in so many ways? It's a poor solution to a problem that no longer even exists.

We already carry in our wallets wafer-thin debit cards with NFC chips. They can't crash and they don't need a power source. Just hold the card up to the terminal in the shop and enjoy the ease of a contactless payments. Yet, here comes Android Pay to replace a robust system with something dependent on hardware, software and enough electrical current. Why?

It's like someone inventing fax technology and trying to replace e-mail with it, or proclaiming teletext to be the successor of the WWW. A bad case of The Emperor's New Clothes.

Anyway, I want to conclude this by saying that I don't believe your hard work these last few weeks has been in vain. Apart from the learning experience you've had (however much it might sting right now), you've made some great leaps with Magisk and I'm sure others will build on that in the future. I hope you will continue to as well.

I'm not (yet) a Magisk user myself, as I've been waiting for development to slow down and stabilise, but I'm very grateful for all of your hard work on both this and systemless Xposed. I'm sure there are hundreds, if not thousands who are equally grateful to you. That's certainly something to be proud of.