yashsingh1/xdaforums huggingface dataset:
[Magisk] teddy0209:
Maybe, maybe not, who knows, but currently no one's working on it... Yes, that is the way to do it if you need to pass safetynet with xposed installed...
[Magisk] kozyy:
Is there instructions on using magisk 13s manual injection yet? Only thing I could really find was in the release notes.
[Magisk] dantemustdie312:
How do I install Magisk with my phone?

Zenfone 2 ze500CL(z00d).

I am running Resurrection Remix Nougat with pre-installed Magisk Manager 4.3.3 but doesn't have Magisk 12 Installed. Everytime I try to flash MagiskV12.zip in TWRP 3.xx it say's "Unable to detect boot image". Ideas??

----------

currently reading Magisk and Magisk Hide installation and troubleshooting tips and tricks (v12)

.

--------

hmmm, seems that I need to flash a stock boot.img to make it work. Which stock boot.img do I need to flash? nougat 7.1.2 or my phone's stock ROM 5.1?
[Magisk] Didgeridoohan:
Like [MENTION=3615867]teddy0209[/MENTION] says, that's the way to pass SafetyNet with Xposed installed and using Magisk.

In the Pokemon thread there was recently talk about another method, but that requires a security patch earlier than November 2016 (or an otherwise patched device).

Cool that it worked, but phh's superuser was removed in favour of MagiskSU with the release of Magisk v11.0.

And so far that's all that's been written about it. Instructions will come soon and it will later be implemented into the Manager (like it says in the release notes).

Why does the ROM come with the Manager, but not Magisk? Weird, but anyway...

Asus devices have been finicky with Magisk in the past. I believe some Asus devices need the boot image to be signed or something like that. Take a look in your device's forums for any info on that.

And since the ROM looks like it's supposed to work with Magisk (the bundled Manager), you might have better luck asking in the ROM thread.
[Magisk] nathanchance:
Most ROMs that include Magisk include the manager as a prebuilt and flash the zip after the ROM automatically so it's possible that the flash afterwards is failing as well. Only way to tell is a recovery.log.
[Magisk] dantemustdie312:
Thanks for the feedback. Thread has not been touched for a few days but I left a comment there just to be sure the OP or other user can guide me.

Yes, the Magisk manager is built-in in the settings menu. I will do a clean install then flash the magiskV12 zip and pull out the log and post it here.

-------------------

End of log

*****************************
Magisk v12.0 Boot Image Patcher
*****************************
- Mounting /system(ro), /cache, /data
- Device platform: x86
! Unable to detect boot image
run_program: child exited with status 1

script succeeded: result was [1.000000]I:Updater process ended with RC=0
I:Legacy property environment disabled.
I:Install took 100 second(s).
Updating partition details...
I:Data backup size is 0MB, free: 10853MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=0
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Installing zip file '/external_sd/Magisk-v12.0.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/Magisk-v12.0.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/busybox
inflating: arm/magiskboot
inflating: arm/magiskhide
inflating: arm/magiskpolicy
inflating: arm/resetprop
inflating: arm/su
inflating: arm64/busybox
inflating: arm64/magiskboot
inflating: arm64/magiskhide
inflating: arm64/magiskpolicy
inflating: arm64/resetprop
inflating: arm64/su
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/custom_ramdisk_patch.sh
inflating: common/file_contexts_image
inflating: common/init.magisk.rc
inflating: common/magic_mask.sh
inflating: common/magisk.apk
inflating: common/magiskhide/add
inflating: common/magiskhide/disable
inflating: common/magiskhide/enable
inflating: common/magiskhide/list
inflating: common/magiskhide/rm
inflating: x64/busybox
inflating: x64/magiskboot
inflating: x64/magiskhide
inflating: x64/magiskpolicy
inflating: x64/resetprop
inflating: x64/su
inflating: x86/busybox
inflating: x86/magiskboot
inflating: x86/magiskhide
inflating: x86/magiskpolicy
inflating: x86/resetprop
inflating: x86/su
*****************************
Magisk v12.0 Boot Image Patcher
*****************************
- Mounting /system(ro), /cache, /data
- Device platform: x86
! Unable to detect boot image
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 1 second(s).
Error installing zip file '/external_sd/Magisk-v12.0.zip'
Updating partition details...
I:Data backup size is 0MB, free: 10853MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1

Full log attached.
[Magisk] nathanchance:
If you haven't already, I'd try the 13.0 beta to see if it is detected then drop a recovery.log in that thread to get topjohnwu's attention.
[Magisk] Didgeridoohan:
Yes, like already suggested, the Magisk flash from the ROM fails in the same way as when you try to flash the zip yourself. If the v13.0 beta doesn't work (remember to remove the built-in Magisk Manager first) I'd say your best bet is to ask in the ROM thread, like you've already done. Hopefully, the person maintaining the ROM knows what's going on.
[Magisk] hachiroku:
I'm now using Magisk v13 beta and so far works flawlessly where v12 wouldn't. Thanks for all the help and hard work guys!
[Magisk] ThatAndroidGuy91:
In OnePlus 3 TWRP thread there is mention that "dm-verity and forced encryption disabler" needs to be flashed if using some other root method thant SuperSu. Magisk thread mentions this as feature: "Remove dm-verity, forceencrypt, unlock partitions blocks to support remount to rw". Does this mean that disabler is not necessary if using Magisk? I just updated my OnePlus 3 and flashed disabled first and then Magisk but am I doing one extra unnecessary step?
[Magisk] Didgeridoohan:
I've never used the disabler and have no issues on my OP3T... Magisk takes care of that.
[Magisk] ThatAndroidGuy91:
Good to know. I think I can then leave it out.
[Magisk] netcitizen:
Hi, I use Oneplus 3 running OOS 4.1.5 rooted with supersu and TWRP recovery with blu kernel. I read about magisk and the touchscreen latency improvement module and wanted to try it out.

So i uninstalled the supersu app , booted to recovery, flashed magisk 12 zip. Now when I check Magisk Manager the first 2 boxes are green (2nd says supersu though) but the safety net has failed.

what is the right way to get this installed and rooted properly with magisk.

The touchscreen magisk module shows as installed though.

I also tried to uninstall magisk and try . I flashed the uninstaller zip i found in the forum .but it failed. the link in the OP of magisk 12 thread for uninstaller zip does not work.
[Magisk] Didgeridoohan:
You can still use systemless SuperSU with Magisk v12. That support will be temporarily dropped from v13 though (more hassle than it's worth at the moment).

If you care about SafetyNet you'll need MagiskSU though, so you'll need to remove SuperSU completely. This can be done by using the full unroot option in the SuperSU app and letting it restore the stock boot image. It might be worth flashing the stock boot image anyway, just in case (you'll find it inside the OOS OTA zip and can flash it in TWRP). If you can't get this to work you'll need to use [MENTION=4544860]osm0sis[/MENTION] unSU script and manually flash the stock boot image. The Magisk uninstaller can be found attached to the OP of the release thread.
[Magisk] Cm4nXD:
I'm trying to get live boot to work on a device without int.d support and using magisk, cuz I need magisk hide for saftynet. I installed the magisk module, as well as ran the live boot app, doesn't seem to work. What do I need to do to get it to work? Thanks in advance.
[Magisk] Didgeridoohan:
You don't have to bother with that module... Open a terminal emulator and run the following:

su
ln -s /magisk/.core/post-fs-data.d /system/etc/init.d

After that you can open up LiveBoot and it'll install the script. The symlink created by the command will disappear on a reboot, but you'll only need it if you want to open up the app again.
[Magisk] danilo_scala:
good morning friends, please , i want use magisk, i have xperia z5 premium root with supersu , android 7.. i only need flash magisk and install manager? thanks
[Magisk] DodoGTA:
Yes (if you encounter SuperSU-related issues when flashing Magisk, fully remove SuperSU and try to flash Magisk again)

Note: Magisk Hide doesn't work with SuperSU (even if it is systemless SuperSU)
[Magisk] XxJuggernautxX:
Team, I just recently tried to root my Note 5 (TMobile) using the Magisk/ PHH Super User method. Upon completion of installing both zip files via TWRP, I had went to update Magisk, but as we all know Magisk was removed from the play store a couple days ago. Additionally, I downloaded the latest version of magisk from the XDA website and installed via TWRP. Still no luck. Therefore, I was unable to gain full root. I checked with Root Checker, and I had downloaded Titanium Backup. Both apps confirmed that I did NOT have root access. Is there a workaround for magisk or is there another way to gain full root access for my Note 5 (running 7.0)??
[Magisk] danilo_scala:
thanks i will try, i will unroot supersu (delete supersu), i click full unroot in app, continue, later in full unroot i click yes or no? (ota, stock), i have recovery. and later i install (flash)magisk?
[Magisk] DodoGTA:
Say yes to restoring boot image backup and no to restoring stock recovery
[Magisk] Didgeridoohan:
You do not flash phh's (not since Magisk v11.0). Just flash the Magisk zip and you'll find a link to download the Manager apk in the release thread.
[Magisk] :
Not sure if this will help..

On my galaxy s5 i recently wiped and installed a new rom.

Little did i know about magisk being removed from playstore. I found out after i installed my rom and could not install magisk.

Well I have v12 and manager version v.3.3 i believe.

Initially my rom was rooted with supersu. So i went into the supersu app and chose full unroot allowing it to restore the original boot image.

Then i booted normal and made sure safetynet passed. (It should pass at this point)

Then i googled the latest magisk manager apk for magisk v12 and downloaded the apk for the manager only.

I then rebooted into twrp and flashed magisk and rebooted. And installed the manager apk and opened it to check magiskhide and rebooted.

All is well.

Main thing was finding the magisk manager apk and instaling it manually did the trick.
[Magisk] XxJuggernautxX:
Thanks

[MENTION=2218242]gothen[/MENTION]burg ...thanks. That did the trick. I just had to download the manager and run it. I appreciate the help.

---------- Post added at 12:42 PM ---------- Previous post was at 12:42 PM ----------

@ moncton ...thanks brother. That helped out. I was able to get full root.
[Magisk] Einheit-101:
How is it possible that Magisk hide successfully hides root from SafetyNet, but a simple app like Sparkasse Push Tan still detects root? :D

Sparkasse > Google?
[Magisk] Didgeridoohan:
Yup... :good: Kind of...

I like how [MENTION=631273]Chainfire[/MENTION] put it forward a few days ago: https://xdaforums.com/showpost.php?p=72573825&postcount=10305
[Magisk] nek46:
Hello , :) Downloads any module and {dolby atmos } I see this, try clear and cache the same

magisk version 4.3.3

htc m9 rom nougat leedroid .
[Magisk] DodoGTA:
No logcat = No solution
[Magisk] :
While Magisk-v13.0 is being sorted out, here's a handy flashable *.zip for v12.0 that I just customized:

https://mega.nz/#!fMUxWRoK!vsTtx9HpN7R2VLYUo3wm4Gh_S7qzgM6cPscvyS0pUvM

The only difference is that the Manager-v4.3.3 is in the *.zip now, not just the stub apk, like before. This file could be added to the official pinned thread too, if the developers wish.

Thanks for bringing multi-user support in v13.0, [MENTION=4470081]topjohnwu[/MENTION], it hasn't been long ago that I came here to request it too, and although I know it probably wasn't because of my request that you're bringing this feature to Magisk now, I appreciate the quickness you're putting into it, thank you. Multi-user's the only reason why I'm with SuperSU still, and I'll switch for good when v13.0 is flashable on Samsung, which it isn't yet.

Thanks also to [MENTION=4667597]Didgeridoohan[/MENTION] and [MENTION=6429309]DodoGTA[/MENTION] for contributing to Magisk and for helping out/replying, whenever I needed. Thanks to [MENTION=4899305]ashyx[/MENTION] for making the TWRP for SM-A720F for I and others.

I might flash the beta soon, just to send the error log to you guys, thus making a small contribution into furthering the development of v13.0.

UPDATE: [MENTION=4470081]topjohnwu[/MENTION] unfortunately, I can't copy any logs from flashing the beta. Flashing turns off the device at "patching ramdisk". Device: Samsung Galaxy A7 2017 (SM-A720F).
[Magisk] khaled147:
hi

can we used xposed installer modules in magisk manager to install xposed on samsung galaxy s8 ?
[Magisk] Watanabe_You:
S8 runs on Nougat. Xposed does not support Nougat.
[Magisk] ForgottenDude:
Guys, is it possible to use Magisk if a ROM comes pre-rooted with Lineage root? I'm talking about crDroid if anyone is wondering.
[Magisk] Watanabe_You:
Get UnSU zip to unroot first then magisk
[Magisk] Nimueh:
That simple? Wow, I wish someone in the crDroid G+ group had told me that when I asked there weeks ago ... I have moved on to another rom since then and mostly because of that built-in superuser :rolleyes:

Thanks, I'll remember that for next time :) :good:
[Magisk] Artim_96:
Yes, it's that simple, I do it myself that way. Just flash Osmosis' unsu zip, best afterwards your ROMs boot.img and then Magisk.

Problems can only occur if you have a ROM that has a prerooted boot.img, then this would not work
[Magisk] whosucks:
I currently dont have magisk on my phone but am considering switching to it. Currently, I have a modified build.prop, modified keylayout file, and I use APPS2SD for folder mounting(symlinking folders from Micro SD I think).

From what I've read, I can replace files by simply adding the file in /post-fs-data.d/ (ex. a file currently in /system/usr/keylayout/ is put into /post-fs-data.d/system/usr/keylayout/).

I can add lines to the build.prop by having a file in /post-fs-data.d/ containing the lines:

However, I'm not sure how to change values already in build.prop or if I can use APPS2SD anymore since it places files in /system/etc/ for its mount script. Can anyone give any insight or comfirm what I read was the correct method?
[Magisk] veez21:
You've got it wrong. You can reread in here to understand things better: https://xdaforums.com/apps/magisk/magisk-details-dummies-to-developers-t3473486
[Magisk] Artim_96:
Will

Well, the first part is the easiest, but for simplicity you should build a module for that. Get the template, everything necessary is explained inside.

And for App2SD there should be s Module in the module collection v2 to mount internal storage folders to SD card, do take a look at it if it can do what you want.
[Magisk] Umbardacil:
Vanishing Magisk

Hi

I've recently flashed stock rom for my Galaxy Note 4 (MM 6.0.1) and Magisk, since I was looking for possiblity to have Android Pay and Viper4Android working together ;)

After clean install I've flashed Magisk 12.0.3 - everything went smooth.

Recently, after phone reboot I've been notified, that there's new Magisk version v.12 and sudddenly I've got no root, and no Magisk :confused:

Can anybody tell me what to do now?

Lucas
[Magisk] e1072502:
Hi, I got a Samsung Galaxy S5 SM-G900F on 6.0.1, rooted on system level, supersu, busybox, toybox, toolbox and boot menu without recovery option.

I'd like to install Magisk, but I can't afford ending up with a bootloop or brick because that's where I get my Internet from. I've seen there's an unninstall file, but I have no idea how to use sh files.

Should I just use supersu to do a full unroot, and then proceed with the Magisk guide like normal?
[Magisk] abbas78861:
I have run into a wierd issue, tried searching but couldn't find a solution, so I installed magisk v12 on dirty unicorns rom I had on my OnePlus 3T, I checked safetynet with magisk hide on and no Android debugging and safetynet passed, so I proceeded to install Android pay, as I tried setting it up it have an error saying custom rom installed, so I went back to magisk and checked safetynet and it said it failed, I checked it again and it passed, it kept passing and failing so I thought maybe it's the rom, I installed freedomos and it does the same exact problem, it fails and passes, so sometimes Android pay will work and it won't, same thing with snapchat, help would be greatly appreciated
[Magisk] Daman5202:
Hello everyone, I've got a problem with magisk:

I wanted to use Snapchat so I selected "hide root" option from magisk manager app settings, after this, I rebooted my phone and here is the result in screenshot below, I lost root! Any solution will be appreciated! :)
[Magisk] Gerard15799:
Flash magisk again... I've experienced it once too...I just flash magisk zip again
[Magisk] vemacs:
Anybody managed to resolve the issue of Magisk occasionally bricking the data partition, even when uninstalled on OnePlus devices? It's incredibly frustrating and makes every module flash a hope-and-pray event: https://xdaforums.com/oneplus-3t/help/blackscreen-magisk-update-t3576571?nocache=1

I think this is the issue, note that it's recoverable on non-encrypted devices but not on encrypted ones: https://github.com/topjohnwu/Magisk/issues/185
[Magisk] Daman5202:
So I flashed the zip again and safetynet passed too! :3
[Magisk] JCLB:
It seems the manager got deleted form playstore, need to download it from third party sites.
[Magisk] nathanchance:
Don't download it from another site, it's still available in the main thread: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post68966662
[Magisk] Didgeridoohan:
Easier to download it here from XDA. In the Magisk release thread you'll find both the link and an explanation.

Edit: Ninja'd! :p
[Magisk] yochananmarqos:
There is no need. It's available in the main thread and XDA Labs.
[Magisk] Ibuprophen:
This type of pertinent information is typically posted on the Announcement thread by [MENTION=4470081]topjohnwu[/MENTION] personally.

You'll locate the answer to your specific question within the following announcement post:

Why is Magisk Manager not available on Play Store? Is development abandoned? - Announcement by by topjohnwu [06-01-2017]

Good Luck!

***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise...
[Magisk] RandomPooka:
It cannot be stressed enough that you should NOT be downloading this from some third party site. Get it from here only.
[Magisk] :
I don't think magiskhide works on the stock rom for the s5. So if you need to pass safetynet you'll need a custom rom. If you don't care about safetynet then no worries.

Then yes like you mentioned, if that rom is prerooted then full unroot and install magisk.

I would even extract your boot.img from a downloaded official firmware to keep in case you run into a bootloop.

I usually do a safetynet check after unrooting to be sure nothing is left behind.
[Magisk] Iceman248:
So I had this module for Tasker already. Thanks by the way.

So when I realized it works for Secure Settings, I enabled the System+ feature. Gained root, but then for the first time I had a CTS profile mismatch with the SafetyNet. Crap! But after disabling System+, it passed again, which I didn't think was supposed to happen, but not complaining. Is there a way to not trigger the SafetyNet to fail with this System+ feature?

Edit: SafetyNet has failed again after reboot. What the heck!

Edit 2: SafetyNet passed second time, perhaps after giving some processes a chance to run after the boot process.

Edit 3: SafetyNet failed again. Failed again. Then passed. Makes no sense to me how that can happen.
[Magisk] CryonicCore:
Yea you need to flash the magisk zip again. This time don't hide root. Instead, use magisk hide.

Your settings should look like this.
[Magisk] e1072502:
It's stock rom. Guess I'll stay like this, then. It's a shame it doesn't work, because usually S Health doesn't work in other roms, last time I checked, and I use it daily.

I wanted it mainly for magiskhide.
[Magisk] Yooshaw:
I can't advise on how to unroot, but I have Magisk functioning fully on my S5 (T-Mo Variant) on stock TW.
[Magisk] Didgeridoohan:
No worries. I'm glad some people found the module useful.

I haven't used Secure Settings in 2-3 years, so I'm a bit rusty. :D But, I did install it right now to test and no matter what I did SafetyNet passed. Did you have any special actions you're using?
[Magisk] Iceman248:
I just use it to toggle NFC. I've been looking at alternatives, none so far have made me that excited about switching to them. I didn't do anything but enable the System+ feature. I just figured I'd check SafetyNet, not expecting it to fail, then was surprised when it did. Let me try it again and see if it passes and fails back and forth, as perhaps that was already happening in background for awhile and I never knew, as Android Pay never complained.
[Magisk] :
Ok thanks for the info. I'll have to try it on stock rom again. Last time i tried stock was magisk v10 i think. I have the canadian g900w8 model.

Edit: I Did switch to stock 6.0.1 and works thx
[Magisk] Iceman248:
So I tested it with it on again and still passing and failing, usually passing it seems, maybe 60/40. So it was either already doing that or once (if) it touched anything on the system, it was messed up from there. It doesn't seem like it is supposed to though, so I'd lean towards it was already like that, but it passing and failing back and forth, does that happen for anyone else? It seems rather bizarre to do such a thing. As long as Android Pay doesn't complain and works, then it doesn't really matter.
[Magisk] shadavis08:
Well magisk asked me to update to v12 and I updated and it sent phone into a slow boot loop ! About every 30 to 40 sec it would reboot. So I had to reinstall my NATF rom with SuperSU instead of magisk. Kind of scared me away from magisk. What is the benefits of magisk anyway I only saw like a few mods in there and o don't think any would really work with my lgv20 ?
[Magisk] yochananmarqos:
If you don't know what the benefits of Magisk are, why are you using it? Sounds like you have some searching and reading to do.
[Magisk] shadavis08:
Actually I am researching right here and right now . I bought this phone already rooted. I really didn't realize it was rooted when I purchased it . Anyway I used to root way back in the GS3 days and kind of just fell out of it for a while, until now . So yes magisk is new to me. And I don't really get what all the benefits are with it. Also I don't understand what saftynet is. And if magisk is for modding similar to Xposed , where are all the mods ? I only saw a few in the magisk manager.
[Magisk] Reilitas:
I can never pass the SafetyNet no matter what I do, the only time it ever did is when I tried an S8 port but that is the only ROM EVER that let me pass it, I'm going as far as buying a whole new phone. Wish me luck!
[Magisk] DodoGTA:
What device are you using and what ROM are you running?
[Magisk] e1072502:
I might try it sometime, then. One of the main reasons is to use Google Pay, since I want to walk around without a wallet.
[Magisk] Reilitas:
SM-G930W8

Samsung Galaxy S7 Canadian

King ROM S7 Edge