yashsingh1/xdaforums huggingface dataset:
[Magisk] duowing:
I pulled the getprop log as suggested by Captain Throwback and didn't find anything different. I think it's something to do with the way Magisk is modifying the boot.img and probably related to the way Huawei codes. Even in the logcat it looks like everything initializes and then it just errors out. I just used the Charles app method to flash the latest N beta, so I'll unlock bootloader and try flashing Magisk on that to see if it works on N.
[Magisk] Demax55:
This is incredibly annoying. I come back home just to sleep and I don't have to time to play around and see how to make it work again.

Could someone explain me how to unroot ( I have magisk v10.2 + phh superuser) so I can install magisk v9 that used to work? I have Honor 8 and Android 6. When unrooted I'll also update the phone ( Not to android 7)
[Magisk] andrew2432:
Still flash the uninstaller? It locates your stock boot, used to, and installs it
[Magisk] anuraag.neo:
[MENTION=4470081]topjohnwu[/MENTION] [MENTION=4683552]maxwen[/MENTION]

Do you know why SafetyNet check loops over infinitely on OMNI 7 ROM? Device Oneplus One.
[Magisk] kerbiii:
how to pass the safetynet?
[Magisk] teddy0209:
What do you mean by that?

Start by going to first page and read. All you need to know are properly documented.
[Magisk] kerbiii:
this one, how to fix this?
[Magisk] Captain_Throwback:
Play Services crashed. Reboot.
[Magisk] vampire_8_7:
Hi guys, so no one having a similar issue or got a suggestion on this one?
[Magisk] anuraag.neo:
Didn't work.
[Magisk] yochananmarqos:
Your Magisk log is normal. FYI, hiding a SafetyNet check app will not help you pass the check. :eek: I'm guessing you did not remove your ROM's built-in root before you started.
[Magisk] Artim_96:
Then it's not compatible as most custom ROMs
[Magisk] vampire_8_7:
Cheers mate for replying, I know it looks so normal but fails to pass the safetynet, also I made sure that root was completely removed from my rom, went through all supersu folders and su files from the file manager of twrp under system/bin and system/xbin, booted the device and checked wasnt rootrled. Then flashed magisk with phhs but no look.

The rom I am using has the privacy guard of CM, I dont know if this will make any difference or not since I completely removed root.
[Magisk] Filip013:
I'm curious. Do you fail SafetyNet entirely or just get CTS mismatch? What result do you get in SafetyNet Helper app from Play Store? Is it blue or red? For example, I've never been able to get full SafetyNet pass on my phone, I always get red but that is still a pass and Pokemon Go works.
[Magisk] teddy0209:
Are you passing safetynet after removing su/ before flashing magisk?
[Magisk] Wesley_NL:
guys, i want to install magisk but in app or twrp i keep getting a error,

i use audax v13 on s6 edge+ sm-g928f, i removed super su and installed it systemless with latests super su from chainfire that was linked in one of the treaths of xda

i hope someone can tell me howto slove this problem , pm perfered to keep tread clean
[Magisk] vampire_8_7:
I get it blue response validation: fail

When I try safetynet after removing su safetynet fails and it's also blue, which is making me think this is the real issue not Magisk itself, but am not sure how it fails even after removing su.
[Magisk] teddy0209:
Restore your boot.img and redo the flashing, see if it will work.
[Magisk] Biz92k:
Guys anyone else is getting error 1 when flashing v10.2 in TWRP 3.0.2-2? v9 is working fine...

Moto g 2013, Idcrisis6 1.5c, kaminarikernel r7
[Magisk] olivercervera:
[MENTION=1162986]Captain_Throwback[/MENTION] already replied, I hope he helped you!

PS: AirWatch Agent is still working since the last Safetynet patch done last year :D Apparently as long as SafetyNet will be passed, AirWatch will work too.
[Magisk] Valiante:
I can't seem to find a list of supported devices, does any such list exist or am I just a clown?
[Magisk] oreo27:
Hey. Were you able to try this? I've read some problems with the Mate 9's system partition and was wondering if Magisk is able to overcome them.
[Magisk] Wesley_NL:
restore boot.img ?! care to explain a little ?,

do you mean revert to stock firmware ota?
[Magisk] morfinrider:
Thank you! Yes [MENTION=1162986]Captain_Throwback[/MENTION] did reply and I followed his instructions. Managed to get an all okay in Airwatch (Doesn't show as compromised) and I can access email only in Airwatch Inbox. But unable to use Nine for emails or connect to corporate Wifi. I can get emails on Airwatch Inbox app though! SafetyNet check still fails :(
[Magisk] Hakem:
For all S7 edge Exynos users: I've got Magisk working with following setup:

[ROM][DPLT] STOCK Official Android 7.0 (dirty flashed)

[KERNEL][STABLE][TW][7.0][DPLT][16.01.2017][SM-G935F/FD/W8] SuperStock-Kernel V2.0

:good:
[Magisk] joelh:
Edit: How was I ever this dumb
[Magisk] Biz92k:
I have the same error, even starting from clean flash of the rom (which works without problems with v9, only v10.x gives problems).

The issue we are experiencing is on two different hardwares, so should be magisk related... Right?
[Magisk] Scherzengel:
What kind of error do you get? With this little information you can't expect help from anyone.
[Magisk] Biz92k:
Alright, now should be more clear... :)
[Magisk] Scherzengel:
Still no error code that ist given by the App or TWRP
[Magisk] Biz92k:
It gives error 1 in TWRP (as stated in the last post quoted above) and just a generic "installation error" in the app :confused:
[Magisk] Scherzengel:
Okay. Thought is was a Typo. Error 1 typically stands for a full system partition. So there is not enough space.

Check if this is true. If it is, try using a smaler gapps pack for example.
[Magisk] Biz92k:
My /system has 312 MB free... Should be enough?

https://s27.postimg.org/c0tauds03/image.png
[Magisk] Hakem:
I edited the post thank you.
[Magisk] Scherzengel:
Maybe post a detailed TWRP log. Could be helpful.
[Magisk] Biz92k:
Sure, there you are. Thank you btw :)
[Magisk] Didgeridoohan:
The installer can't find the stock boot image backup SuperSU creates when you flash it. Try flashing a clean boot image from your factory image/ROM and flash SuperSU again. Then try installing Magisk and see if it works better.
[Magisk] olivercervera:
If SafetyNet is still failing, it means you haven't flashed a kernel that patches blootloader state check.
[Magisk] Didgeridoohan:
Magisk hides the bootloader state. It's more likely that SN is triggered by remnants of previous root or SELinux being set to permissive.
[Magisk] morfinrider:
Thanks! I used SELinuxModeChanger to change SELinux to Enforcing. Let's see if that works.

I am using CM's inbuild kernel, and not a custom kernel. Any recos on kernel that sets SELinux to Enforcing?

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

I am using CM's in-built kernel, and not a custom kernel. Any recos on kernel that sets SELinux to Enforcing?
[Magisk] me7tarfeek:
I tried it but did not work.... Error during installation.
[Magisk] Wesley_NL:
ok as requested a log, took some time to figure out but here it is, hope you guys can assist me beter now,

i like to know why magisk dont wanna install
[Magisk] Scherzengel:
Same Deal as with Biz92k. Installer can't find the backup the SuperSu Installer should have made. Flash the stock boot image of your ROM and try again.
[Magisk] Captain_Throwback:
That's a folder in recovery, not the ROM. It has nothing to do with any of this.
[Magisk] Captain_Throwback:
I just told you, lol.

CM doesn't include supersu, so why would there be a SuperSU folder?
[Magisk] Captain_Throwback:
It's not a version of SuperSU. SuperSU is closed source software, now owned by CCMT. Does that sound like something CM/LOS would be including in their ROMs?
[Magisk] Captain_Throwback:
It's part of the recovery ramdisk - it's for automatically installing SuperSU for root on pre-Marshmallow devices. It only exists in recovery. If you want to delete it, you'll have to unpack your recovery image and delete it manually, or rebuild TWRP from source for your device with the SuperSU option disabled. Is it really that serious? It's not as if it installs anything to your device just because it's there...:rolleyes:
[Magisk] Biz92k:
So, I tried again restoring my stock boot.img and then flashing SuperSU SR3 and Magisk 10.2, with the same results as before.

I attached the log of the test, if that could help.
[Magisk] Artim_96:
Maybe don't flash SuperSU next time?
[Magisk] Biz92k:
Man, Magisk OP says that in the instructions, so I followed them. You think that is the culprit?

Btw I tried flashing magisk right after the stock boot.img, no luck.
[Magisk] jhedfors:
I think the point here is to limit the variables. Can you restate the issue you are having? It is hard to trace your conversation as you did not quote any post.
[Magisk] Wesley_NL:
Stock boot image? Like I asked before is that official bloated Samsung ROM , or stock kernel of Samsung?

Because I run audax 13 and I don't know if he have made a stock boot image or something
[Magisk] Biz92k:
Sure.

My issue (but I'm not alone) is that if I try to install magisk v10.2 from the app it gives me "installation error", and tells me to install from recovery.

In TWRP 3.0.2-2 I keep on getting error 1, and installs fails.

I'm able to install v9 without issues.

I'm on moto g 2013, IDcrisis6 1.5c, kaminarikernel, but I tried various permutation of stock kernels without luck.
[Magisk] Didgeridoohan:
I'm guessing your ROM comes with SuperSU built in. The flashing of SuperSU 2.79 SR3 also failed, for the same reason as Magisk. Your boot image is already patched and the installer aborts when it can't find a clean backup. When you then proceed to flash Magisk nothing has changed and you'll get the same error message.
[Magisk] Artim_96:
Well, then it's most likely a device specific problem and can't be solved here. You need to ask in your devices forum since some Motorola devices are already known to be incompatible
[Magisk] Biz92k:
That's right, gonna give a try to the unrooted variant of my rom. Thank you for the suggestions till now, Ill' let you know if I manage to install v10.2.
[Magisk] jhedfors:
Not sure if this will help, but you could try this:

1. Dirty flash current ROM

2. Without rebooting, flash unSu script by osmOsis

3. Without rebooting, flash Magisk v10.2

4. Reboot

Might be worth a try.
[Magisk] Biz92k:
Thanks for the idea, but didn't work. Nice one btw
[Magisk] Biz92k:
I flashed the unrooted version of my rom and got the same exact behavior as before. No clues anymore, gonna stick on v9 until a solution comes out (or another update of magisk will install). Thank you btw! :)
[Magisk] kewlpanda:
anyone having a problem with magisk passing safety net and i get up to the part when android pay verifys card and that then it says i cant use android pay because of being rooted
[Magisk] designori:
did you enabled 'magisk hide' feature? you can find it @ in-app settings section.
[Magisk] Wesley_NL:
so let me ask again, i need a stock rom with root to get this working? but what good will it be to not able to run a custom rom? , people root to go custom and optimized rom no? , or arleast thats what i could find out with " stock boot image" unless i am wrong
[Magisk] Didgeridoohan:
People have been successful with Magisk on custom ROM's, so it's not a prerequisite to be stock. It's easier on a stock system though. You don't need to be rooted prior to installing Magisk, it'll root for you.

Stock boot image means you need an unmodified one...

And there are many reasons to root, not only to have a custom ROM. It's not even necessary to root to install custom ROM's. I root mainly for Magisk, AdAway, Titanium Backup and my custom kernel app.
[Magisk] Wesley_NL:
and yeas i know magisk root for me, but then again if magisk root for me why do we need supersu ?!?

also i am unable to get it working with audax 13, witch is the only modified rom there is for my device, the rest is dead no more updates,

i rooted because i wanted a optimized rom, and a beter battery life that was my main reason for rooting, ofc the air message and the note ux stuff is great to along with viper+dolby atmos, but if i have to go stock this all would be lost,

i tried asking them for help to get it working on audax but no replies on this mather,

sofar i was able to systemless rooting by removing it and reinstall with the systemless command in twrp but on magisk no luck it keep failing

also i beleve the custom kernel of audax have root inside so that probaly wont work right ?

if i had to go stock this device won't even last 12 hours on its battery, mind you its 1.3 years old device so its pretty used up all the time
[Magisk] Didgeridoohan:
You don't need SuperSU. You have a choice to use either or.
[Magisk] Wesley_NL:
o i see so the audax kernel might work then , then whats left the rom itself how to slove that, i know howto install viper and dolby though but the note ux not
[Magisk] kewlpanda:
Already done that with Android pay and banking app
[Magisk] olivercervera:
Since when? I thought that kernel patch was still needed!
[Magisk] teddy0209:
Restore your boot.img/ the boot.img of the rom you are using/ also called kernel. After that, flash magisk, if successful it should root your device, then install any mod that you want the usual way you install them. By the way, there is magisk module version of V4A if that's what you are referring to with viper. I hope I'm clear enough.

---------- Post added at 11:53 AM ---------- Previous post was at 11:49 AM ----------

Since V9, the so called resetprop if I'm not mistaken.?
[Magisk] Wesley_NL:
uhm i did a clean install of audax, full phone wipe, and still it didn't slove it , thats why i came to here, and i don't know if pierdebeer made a clean kernel/boot

oh so v4a also have a magisk version, damn so i can't use stock v4a ?, its getting more complicated the more answeres i get

i don't even know where to start now, i mean i don't know where i can find a stock clean kernel of my rom

so i guess i have to flash offical bloated samsung rom?
[Magisk] teddy0209:
What exact steps?

1. Full wipe and install your preferred rom

2. Remove root included in the rom if any

3. Flash magisk via twrp

The boot.img that I'm referring to is the one included in your preferred rom/ rom you are using. If you install systemless supersu it modifies that boot.img, same with magisk, so if something goes wrong just restore the boot.img prior to flashing.
[Magisk] Wesley_NL:
uh wait, i did a full phone wipe, i installed audax 13, i removed super su with the option "switch superuser app" because full unroot dont work, ,and i folowed some guide on xda to install systemless su

this worked, without fails and the file is there in /data/.supersu and then i flashed magisk after that but no luck, unless i do it wrong , it seems magisk instaleld some files , see attachment
[Magisk] teddy0209:
Disregard supersu, you don't need it prior to installing magisk. Install just magisk to see if it works.
[Magisk] Wesley_NL:
nope dont work, i even removed the old files .supersu and magisk that where in /data/ before i installed magisk

btw where is v4a magisk version ?

also , if i revert back to offical rom, do i hve to follow this to reroot again in order to install magisk ?

1- Put Rom in your device

2- Enable Developers options in your phone

Go to Settings / About Device / Software Info and tap on Build Number 10 times to enable Developers Options.

Then Go to Settings / Developers Options and Make enable "USB Debugging" and "OEM Unlock".

3- Make a backup of you internal SDcard and your data.

4- Power off your device

5- Reboot into Download Mode

(Press and Hold Volume Down + Home + Power button)

6- Open Odin 3.10.7

7- Put BOOTLOADER for G928F in BL

8- Put MODEM for G928F in CP

(For other G928 variant please search, download and flash your Marshmallow Firmware with Odin in AP)

9- Put TWRP RECOVERY in AP

10- Connect device to PC and it added in Odin

11- Go in options tab and uncheck autoreboot (check only F. Reset Time).

12- Click on Start to Flash the files

13- Once it's completed and you see "PASS" in a green box, disconnect device and long press Volume Down + Power

14- Once screen turns off, immediately press Volume Up + Power + Home to reboot to recovery manually.

15- Once in Recovery, install Audax Rom and in Aroma installer select WIPE DATA.

16- When device reboot seems like a Bootloop but is normal. Than start Samsung bootanimation. Complete reboot ends after 7/8 minutes.

copied from audax page
[Magisk] morfinrider:
Thanks! So maybe I need to figure out how to get the SuperSU within CM/Lineage OS to be hidden from SafetyNet.
[Magisk] Wesley_NL:
[MENTION=1584835]morfin[/MENTION]ride

enable develop mode in cm and there will be root option, that i know from cm 14.1 on lg g3 d855

cm itself have root already as far as i know, but it is not visible untill enable develop option

i like to have cm for sm-g928f to but it died rather fast on cm 13, so yeah audax is all that there is left
[Magisk] teddy0209:
As we have said to you, no need to root your device prior to flashing magisk. No need to do those steps again if you have already unlocked your device and installed twrp.

Edit: you can find v4a in the magisk managers download tab.
[Magisk] Wesley_NL:
that is not what i mean, if i install offical bloated samsung rom i have to redo all these steps again right ? i can't get it to work with audax 13 and i like to have it to work , as i can not find any good guide howto install magisk on custom roms, it looks simple if it works that is, but if it dont it get more difficult and i want to slove that, that is why i asked some support

if i install offical rom twrp is gone to so i have to boot into download mode and install twrp/bootloader/modem again, from what i remember
[Magisk] teddy0209:
Then you need to redo all that if that's the case. I thought you just restored stock rom, not recovery and bootloader.

Edit:

After you install TWRP make a backup, so you can easily restore and start over.
[Magisk] Wesley_NL:
i see, so you guys can not asist me any further ? because i dont know where i can find this boot.img file you mentioned
[Magisk] teddy0209:
Almost every rom comes with a boot.img inside the package. You can extract it from there.
[Magisk] Wesley_NL:
good to know another thing learned,

and that image i have to flash trough odin right ? i don't know if twrp can do it but i know it from odin

so i need to exctact it from audax rom or samsung offical rom ?
[Magisk] teddy0209:
TWRP can do that... It can also backup all partitions boot, system, data, recovery, and some additions depending on the device you use.

Edit: If you are using audax then use the boot.img that comes with it, same with samsung official use the boot.img that comes with it.
[Magisk] jjhaohao:
WARNING: Samsung S7 930F not booting after Magisk 10.2 install. Stuck in Samsung logo and random vibrations. Has to reinstall Magisk v9 from TWRP for booting again.
[Magisk] spida_singh:
Tested LinageOS 14.1 with the Kernel commit to allow SafetyNet to pass, and performed 2 successful Android Pay transactions earlier today

https://xdaforums.com/showpost.php?p=70625893&postcount=324
[Magisk] Wesley_NL:
gotcha, imma try it now ,

no luck

1. i removed super su and booted into recovery

2. i installed the boot.img with option "boot"

3. rebooted phone again into recovery

4. installed magisk

5. same old error popped up

---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------

have you wiped cache/dalvik cache ? that might work after you installed it
[Magisk] topjohnwu:
So it works on all your other devices, but not working on your Samsung S4?

Did your download the updated modules? All previous modules are NOT compatible!

Yes you are :), please take a look at post #4, you will need to meet the module structure
[Magisk] TheManii:
Correct
[Magisk] topjohnwu:
I just tested your boot image, it seems that my sepolicy-injection doesn't work properly lol

It seems to patch too much so that the sepolicy file is crazy big. Will investigate.
[Magisk] FPSUsername:
App doesn't work at all. It used to do selinux first for me, but v1.2 broke it. It doesn't ask for root either
[Magisk] anagramgenius:
Guys, phh's superuser is in the 2nd post of this thread and not in another thread. Took me a while to figure it out. Install it and you're good to go.
[Magisk] stangri:
I've tried to read up on that, but couldn't find the answer. What are the consequences and benefits of patching vs not-patching verity and force-encrypt?
[Magisk] Droidphilev:
Hi,

Tried again with a custom rom on Nexus 6 which seems to work!!!

I have a question (i have read OP!)

I want to hide xposed apk Do i put it in /magisk/dummy/system/app or in /magisk/mirror/system/app? I don't realy understand the difference

I want to hide the apk when i disable/unmount in Magisk Manager

(i need this for an app that doesn't like root but also doesn't like the xposed apk)

Thanks for all!!!!
[Magisk] topjohnwu:
Magisk v5 is a hotfix for older Android versions.

For everyone complaining that root is not working, root zips are in post #2, both SuperSU and phh is updated for the new API (Magisk v4 and newer). Please make sure to flash the latest one.

Also, I added a troubleshoot for Magisk Manager installation failures in FAQ. I signed it properly in this release, so older versions are not upgradable.

This will not happen in the future.

May you test v5? If it still complains boot partition size too small and unable to install, I'm afraid it's impossible to install Magisk

Unless you know what they mean, you should let them be patched. It won't do any harm to your device, neither will change the encryption status of your device

You need to create an Magisk mod for that. Do not touch the files/folders in the .core folder. They are for internal use.

However, you want to hide the Xposed Installer at runtime? I'm afraid it is not possible.
[Magisk] rgawenda:
Can we dirty flash v5 over v4 without further steps?
[Magisk] topjohnwu:
Yes :)
[Magisk] Droidphilev:
Ah ok. Quite difficult how to make such mod for dummies. I will reread. Well.. my intention was to disable xposed in materialised installer amnd then hide the apk using Magisk. Is this not possible?
[Magisk] ThePurpleK:
Would it be possible to think about using semver (http://semver.org/), following v[major].[minor].[hotfix]? Versioning is really up to the developer, but lots of developers have adopted semver and it's great because you can see whether a new version brings breaking API changes at a single glance. For a hotfix to v4, the new version would be v4.0.1 because the API doesn't change. It's quite intuitive and it'd be great if you could take a look!
[Magisk] devilloki:
thanks!v4 can work on huawei honor7
[Magisk] KPOCAB4EG:
this not working with a F2FS on Samsung (g930f) devices. fix in future?

with ext4 working fine(
[Magisk] tikizondo94:
V4 working great for me. Running on n6 with chroma. Using v4 with, phh and Xposed. Love it! Awesome work devs. Thank you for this and all your hard work. Much appreciated.
[Magisk] ThePurpleK:
To get it to work on LG G2 or LG G3 (due to secure booting error), flash this directly after the Magisk installer to bump the modified image: http://xdaforums.com/lg-g2/development/cbump-bump-current-boot-image-t3325186
[Magisk] Skuggo:
Is it just me or is the download link for magisk gone?
[Magisk] KaMyKaSii:
The folder "magisk" in cache must be created manually now? Until version 3 it was automatically created here, after version 4 disappeared
[Magisk] elreydenj:
Should v5 now work with supersu if we install supersu as systemless? in theory android pay should work then even if not using phh method? I know you kept recommending PHH method previously.
[Magisk] mobileman88:
[MENTION=4470081]topjohnwu[/MENTION]

Thanks for the fast and furious releases.

Is it necessary to upgrade from v4 to v5? I am on stock 6P firmware. Just upgraded to V4 and noticed you have V5 now.