Develop Bugs

[G4/G4 Plus] How to Install Magisk and pass safetynet?

Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.

Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.

mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.

guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do

mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.

I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu

aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.

mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?

aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?

guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error

If I do a ROM update do I need to unSU and flash Magisk again?

Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.

aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?

guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?

aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).

guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.

Would using the wrong unSU version affect safetynet detection?

Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?

guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.

Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?

magisk module installation issue

Is anyone else getting an error when trying to install magisk modules? I tried to install the Xposed one and it throws this error after trying to mount and on others it says it's not a magisk module, even though I downloaded it right off the magisk manager

Have you tried flashing it through twrp?

bednim said:
Have you tried flashing it through twrp?
Click to expand...
Click to collapse
Yeah I get this error

Veid71 said:
Yeah I get this error
Click to expand...
Click to collapse
Same thing happens to me when flashing terminal app systemizer. The application based module doesn't work either on the pixel XL.

[email protected] said:
Same thing happens to me when flashing terminal app systemizer. The application based module doesn't work either on the pixel XL.
Click to expand...
Click to collapse
I found out it wouldn't flash any app from magisk, turns out my phone just hated 14.0 and 14.3 version, I don't know why but when I flash 14.2 everything works

[MAGISK] [8.0] ARCore with modded Google Camera

Hey,
I've created a small magisk module, with that you can use the Argument Reality function inside the Google Camera.
It works on AOSP 8.0 Beta and Stable, maybe it also works on nougat.
When you want to test it on other devices than the Mi A1, please don't forget to make a backup even if bootloop and such things are very unlikely.
Wehen you have a device where it also works you are allowed to create a thread, only condition link me and very important Arnova8G2 because without his work it would not be possible.
Installation instructions:
The modules can easily flashed inside the Magisk Manager or with TWRP.
To get it fully working you have to flash both modules
Downloads:
All in one version:
https://forum.xda-developers.com/mi...re-modded-google-camera-t3720269/post75090632
ARcore Basic files:
https://drive.google.com/folderview?id=1C3pylJpeK9bc93L56v1JWrjJNXnNbU06
ARcore Basic files V2:
https://drive.google.com/file/d/16YyJN1PTDMZ5WPQ_F2VFZuyTJlAOmAyi/view?usp=sharing
Apps Module:
https://drive.google.com/file/d/12t5jRzlEM0tz1mkyKqjwu0RS8yZ37IeY/view?usp=sharing
Apps Module V2:
https://drive.google.com/file/d/19rtu2nUAcH2WKCBbGbm2F75uXsfwKXt4/view?usp=sharing
Do not thank me, just thank him @Arnova8G2

Thanks for your contribution! Will try as soon as I get the oreo beta working on my phone.

Unable to flash via magisk

Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted

fosco_ said:
Unable to flash via TWRP nor Magisk, maybe cause data partition is encripted
Click to expand...
Click to collapse
My storage is also encrypted and it works.

AnnePunk said:
My storage is also encrypted and it works.
Click to expand...
Click to collapse
What version of Magisk and Magisk Manager?

fosco_ said:
What version of Magisk and Magisk Manager?
Click to expand...
Click to collapse
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3

AnnePunk said:
Latest Magisk Beta: v14.5 (code: 1456)
Magisk Manager: v5.4.3
Click to expand...
Click to collapse
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....

Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
Had the same bug, reinstall magisk with the Magisk Manager, reboot and try again.

I can flash other zip.. But these two can't be flashed on magisk

Rakibboss said:
I can flash other zip.. But these two can't be flashed on magisk
Click to expand...
Click to collapse
Hmm for me it works

Whatever, i managed to do it via this method
https://forum.xda-developers.com/redmi-note-3/themes/mod-updated-6-11-17-google-camera-hdr-t3701190

Yash98 said:
I can't get Magisk Manager to install any module, it says something like /data/magisk not setup....
Click to expand...
Click to collapse
"I can flash other zip.. But these two can't be flashed on magisk"
You must create an folder "magiskmanager" on internal sd card...then it works

I will try for Android Nougat. Thank you

It doesn't work on nougat .i tried

Hello, install without problems, but I would like to know which Gcam application exactly should I I must use, Thanks.

anyone got it working ?

jeneb11 said:
anyone got it working ?
Click to expand...
Click to collapse
Not working on Redmi Note 4 stock global miui9 with camera2 api enabled. Tried with both magisk, and TWRP, AR Stickers stoped.

how can you install magisk on oreo? when i booted to the twrp, it asks for my pattern and when i draw the pattern, it says pattern failed. so please tell me how can you install magisk on oreo

jigs4wkiller said:
Hmm for me it works
Click to expand...
Click to collapse
Which magisk version??

Why safetynet do not pass on any custom rom?

I tired all arm64 custom roms for moto z play, some arm, tried mixing with all kernels and magisk/without magisk.
And i can't pass safetynet on all these configurations

That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work

But I have passed with magisk

Artim_96 said:
That's the point of SN. Those ROMs aren't certified by Google so they don't want you to pass. That's not a problem of any ROM, that's how it's intended to work
Click to expand...
Click to collapse
But on my old phone, i was using custom roms (not certificed), and SN was passing.

mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
With ROM you using?

dawidrejowski said:
With ROM you using?
Click to expand...
Click to collapse
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.

dawidrejowski said:
But on my old phone, i was using custom roms (not certificed), and SN was passing.
Click to expand...
Click to collapse
How old of a phone? My last phone (HTC One M8) passed on custom ROMs because it didn't seem to report the bootloader was unlocked. But I have safety net passing on custom ROMs on my Z play thanks to magisk and universal safteynet fix beta 5.

mijing said:
Im using official Validus ..you can try universal safety net fix to pass safety net.I'm using this.
Click to expand...
Click to collapse
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!

KrisM22 said:
What do you mean by "universal..." - magisk? if so, which release are you using? Thanks!
Click to expand...
Click to collapse
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk

mijing said:
Universal safetyNet Fix(v2 Beta 5) is the module of Magisk
Click to expand...
Click to collapse
That is a very old one - could you please attach it to your post for a few minutes? TIA!

KrisM22 said:
That is a very old one - could you please attach it to your post for a few minutes? TIA!
Click to expand...
Click to collapse
Yes it is too old but till now it is usefull as you can see

mijing said:
Yes it is too old but till now it is usefull as you can see
Click to expand...
Click to collapse
I found it up on
https://androidfilehost.com/?fid=673368273298984533
is that it?
I'll go try it on AOSP 8.1 Alberto97

Yes,It Is. but I dont Know about AOSP Is it will work or not

mijing said:
Yes,It Is. but I dont Know about AOSP Is it will work or not
Click to expand...
Click to collapse
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?

KrisM22 said:
lots of red messages so far - what version of magisk MANAGER are you using? (magisk/settings/about) - I tried 4.3.1 but no go.
EDIT I see you're running 16 of magisk, but have added module 14 2-5. How did you manage to add that?
Click to expand...
Click to collapse
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English? )

mijing said:
But I have passed with magisk
Click to expand...
Click to collapse
Edit: Never mind I saw what Rom you were running.

mijing said:
Yes I'm using v16 of magisk with module
Go to magisk manager - module - + bottom (for add Module) install it
If installation fail you can flash with recovery that's it.
(My English )
Click to expand...
Click to collapse
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!

KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Im glad you have fix your problem

KrisM22 said:
Your English is excellent!!!
I now have a very tiny understanding of Magisk Modules...
I started with 1600 this time (it later updated the mgr).
I thought this failed before so it may be necessary to try to add module with magisk, let it fail, then boot to recovery, flash that old 2 beta 5 zip (flash goes fine) , and reboot and I find that old 2 beta 5 zip is now in magisk modules. YOU THE PERSON!!! (gender non-specific version of you da man!)
I went on to do my usual of install TBPro, restore my stuff(obviously root works), reboot to recovery to backup at this point. and test. SafetyNet passes fully, Pogo plays, Netflix shows in gpstore. And I now have a working 8.1 on my MZP.
HUGE THANKS for your patience!!!!!!!
Click to expand...
Click to collapse
Check for Bluetooth and wifi if they are working correctly. I flashed the fix on AOSP and my Bluetooth crashed, needed to restore backup.

Flashfire Alternative

Hey everyone, i got a new j6+ (sm-j610f) running 8.1 oreo. I rooted it via magisk patched boot.img method , also removed all the bloatware. I want ro install xposed framework but this device doesn't have a compatible twrp/cwm recovery yet, i tried using flashfire but it's not working. I'm not sure if the app isn't compatible with oreo or magisk, i granted it superuser permission but it's stuck on acquiring root access. Is there a fix for this problem, if not is there an alternative for flashfire?!

dope77 said:
Hey everyone, i got a new j6+ (sm-j610f) running 8.1 oreo. I rooted it via magisk patched boot.img method , also removed all the bloatware. I want ro install xposed framework but this device doesn't have a compatible twrp/cwm recovery yet, i tried using flashfire but it's not working. I'm not sure if the app isn't compatible with oreo or magisk, i granted it superuser permission but it's stuck on acquiring root access. Is there a fix for this problem, if not is there an alternative for flashfire?!
Click to expand...
Click to collapse
Magisk already has Xposed support. No need to install the framework separately.
Just type Xposed in the download section and install the SDK 27 version.

ashyx said:
Magisk already has Xposed support. No need to install the framework separately.
Just type Xposed in the download section and install the SDK 27 version.
Click to expand...
Click to collapse
I tried this, no success

dope77 said:
I tried this, no success
Click to expand...
Click to collapse
Are you sure you have the latest version of Magisk installed?
Also save and post the log after install.

ashyx said:
Are you sure you have the latest version of Magisk installed?
Also save and post the log after install.
Click to expand...
Click to collapse
Magisk manager says that i have the latest version

dope77 said:
Magisk manager says that i have the latest version
Click to expand...
Click to collapse
update-binary[102]: /sbin/.core/mirror/bin/magisk: not found
Have you got stuff hidden?

ashyx said:
update-binary[102]: /sbin/.core/mirror/bin/magisk: not found
Have you got stuff hidden?
Click to expand...
Click to collapse
Look, here's how i got this phone rooted, downloaded magisk manager, patched the boot.img and flashed through odin, restored phone to factory settings bcz i was stuck with integrity verification failed and there was no way to flash dm verify disabler since there is no custom recoveries for j6+ yet. After that phone booted and magisk was installed. Haven't touched any settings nor hidden any things, and there's this message i keep getting whenever i open magisk. Each time i open magisk it popups, even if i press yes it will appear the next time open magisk.

This is the log i get after installing the additional setup
- Detecting target image
- Target image: /dev/block/mmcblk0p23
- Device platform: armeabi-v7a
- Existing zip found
- Extracting files
Killed
Killed
Killed
- Unpacking boot image
Killed
Killed
Killed
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
Killed
! Unable to repack boot image!
! Installation failed

This commonly happens whe u don't have the latest MAGISK installed NOT MAGISK MANAGER.