Database Users

[ROOT][Magisk 14][09/11/2017] SUPER Easy systemless root for B580+

Since OTA updates NXT-L09CxxxB580+ for our devices is out and because of the fixes in the kernel, we are now able to root our device using Magisk.
This is a step-by-step guide leading you throughout the process and also stating the pros of using Magisk over using SuperSU.
News:
09/11/2017
- Magisk was updated to v14 which adds more root hiding mechanisms and also more devices compatibility.
07/18/2017
- Magisk was updated to version 13.3 and will once again pass SafetyNet without any issues
- To update, just open MagiskManager and press Download and Install (if you are new to Magisk, just follow guide below)
07/14/2017
- Google updated SafetyNet and Magisk devices will not pass it
Pros of using Magisk over SuperSU:
Automatic updates
Does not break OTA updates
Does not break SafetyNet (you will be able to use AndroidPay, play Pokemon Go, install Netflix from Google Play and use apps requiring SafetyNet pass)
Ability to install modules from the repository (much like xposed modules)
Before installation:
Unlock your bootloader
Make sure you have stock boot.img
Make sure you are on B580+ as Magisk cannot be installed on older versions
Installation:
Flash this recovery in fastboot: https://forum.xda-developers.com/mate-8/orig-development/twrp-t3576364
Flash latest Magisk in TWRP recovery: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Boot into system
Check your apps for Magisk Manager
[OPTIONAL] In the magisk manager, you can check if you pass SafetyNet
Troubleshooting:
Magisk Manager was not installed
- Open the Magisk.zip, inside open common folder and install magisk.apk
SafetyNet does not pass
- First try disabling and enabling Magisk Hide in the Magisk Manager
- If above does not help open stock Huawei dialer, dial *#*#2846579#*#*, tap Background settings, tap LOG settings, check all checkboxes, open Magisk Manager and disable and enable Magisk Hide
Supported devices:
All NXT-L29 B580+ devices
All NXT-L09 B580+ devices
All other Mate 8 versions with B580+
Basically any other device as Magisk is not device dependent (works with like 95% of all devices, as long as the device's kernel supports loop mount and few other things)
My Magisk Modules for Mate 8:
[Magisk] Official Huawei Automatic Call Recorder
Hope this will help you guys!

car nikolaj
. I recommend this app to anyone who want for the root acces. :good::good::good::good::good::good::good:

Does this method and the TWRP attached work on B585?
Thanks.

Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?

xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
Same here. CTS profile mismatch
Fresh B581

Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?

necc0 said:
Does this method and the TWRP attached work on B585?
Thanks.
Click to expand...
Click to collapse
Yes
xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
sZx1 said:
Same here. CTS profile mismatch
Fresh B581
Click to expand...
Click to collapse
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
shestolemyusrname said:
Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?
Click to expand...
Click to collapse
You just press uninstall button in Magisk manager

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?

Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk

woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?

Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk

Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
xxlap1xx said:
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Open Magisk Settings and enable Systemless hosts data.
Systemless root means you can't directly edit /system partition, because editing it voids SafetyNet. Magisk uses Magic Mount to systemlessly replace /system files and folders on-the-fly without actually modifying the original ones. All you need is appropriate modules from magisk manager "Downloads" tab.

woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
Try installing it as user app and use App Systemizer module in magisk manager to convert it to system app.

xxlap1xx said:
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Yea you are right, I have it working, but the process is a bit tedious. We better wait for new Magisk version, where it should be fixed.

shestolemyusrname said:
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?
Click to expand...
Click to collapse
Keep it Read Only.

Boosik said:
Open Magisk Settings and enable Systemless hosts data.
Click to expand...
Click to collapse
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.

Hilton.Swart said:
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.
Click to expand...
Click to collapse
sZx1 said:
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.
Click to expand...
Click to collapse
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.

Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Boosik said:
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.
Click to expand...
Click to collapse
Can you, please, share. I'm pretty handy with terminal and willing to experiment. Worst - have to return to stock.
Thanks

how to get SafetyNet working on latest 7.1.1 update (Stock Rom) Magisk 14 (version is

Just safety fix module gonna work, every other module gonna bugged.
To install modules you have to wait the f2f2 fixed kernel.
Guys after some testing on magisk i discover that have some modules that work with this method, but carefully because some modules like app systemizer gives a bootloop. So do a backup.
Click to expand...
Click to collapse
For your security make a backup of boot partition first
Click to expand...
Click to collapse
Hi everyone, I decided to do a tutorial, to explain how to get safetynet working while the kernel with f2f2 fixed is not released
{Unlocked bootloader is needed}
{stock rom is needed too}
{TWRP is needed too}
1. you have to reboot in TWRP and install Magisk 14 and reboot (is needed to reboot to create all files) and reboot again into TWRP
2. to work the correct function of magisk you need to do the trick maked by jbblancoperez
3.you have open terminal on TWRP and move the file
mv /data/magisk.img /cache/magisk2.img
Click to expand...
Click to collapse
4.after you have to symlink the files
ln -s /cache/magisk2.img /data/magisk.img
Click to expand...
Click to collapse
5.boot system and check on magisk manager if SafetyNet works if it not works ( install the safety net universal fix) (link above)
6. If you had to install the SafetyNet Fix after works you can unistall the module because its gonna work without it
If anybody have a problem with magisk hide on 14 version just install the 13.3 version and use root explorer to copy the .core folder to sdcard and then install 14 version and put .core folder in appropriate place]
The directory of . core folder is /magisk/.core
Click to expand...
Click to collapse
Links
SafetyNet Fix (for the 14 magisk version you need to install the zip with hotfix, which is in same post of last beta but is in the end of the post) https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
Magisk : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse

Worked like a charm, thank you!

It worked perfectly. Just one thing, you had a syntax error in step 6:
Its '/cache/...' not '/cacve/..."
Anyway, thank you very much. I needed it :good::fingers-crossed:

flapcon said:
It worked perfectly. Just one thing, you had a syntax error in step 6:
Its '/cache/...' not '/cacve/..."
Anyway, thank you very much. I needed it :good::fingers-crossed:
Click to expand...
Click to collapse
I have not seen it ! thanks

Guys after some testing on magisk i discover that have some modules that work with this method, but carefully because some modules like app systemizer gives a bootloop. So do a backup.

Safetynet still fail. Could you explain how to get Safetynet pass? THanks

Magsik dont work with Xposed. Install Magisk 14.3 it will work perfect without doing anything, i am on Security Patch August.

Nchls said:
Safetynet still fail. Could you explain how to get Safetynet pass? THanks
Click to expand...
Click to collapse
Did you move the image to cache and symlink with the correct comands? Check if you don't have sure, try the process again. And if you don't get the safety net working try the module.

I just applied the hotfix plus the "mv and ln" to my moto z play, I passed the entire safetynet check for the first time ever and Google Pay just works.
Thanks a million!!
p.s. I am running magisk 14.3 beta IIRC.

The trick with symlink worked. I can pass SafetyNet and HideRoot on my Moto Z play (7.1.1 Nougat - august security patch).
PS: there is an extra space before symlink parameter. it should be like this:
ln -s /cache/magisk2.img /data/magisk.img
Click to expand...
Click to collapse

razorsbk said:
The trick with symlink worked. I can pass SafetyNet and HideRoot on my Moto Z play (7.1.1 Nougat - august security patch).
PS: there is an extra space before symlink parameter. it should be like this:
Click to expand...
Click to collapse
Thanks! I gonna correct!!

Can I use the latest version of magisk (15.3)? It doesn't seem to work when i try to use Superuser functions in Automate

GiantPlaidSquirrel said:
Can I use the latest version of magisk (15.3)? It doesn't seem to work when i try to use Superuser functions in Automate
Click to expand...
Click to collapse
I relock my bootloader so i can't test or try another way. Sorry about that, but i don't know if something can be done to work

Magisk 25.1 for Fire TV

As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"

Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?

Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?

Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI

mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.

Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho

Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...

Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.

tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?

hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.

mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release

tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks

What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.

yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp

I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)

I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.

Magisk Module to replace the FakeStore in the OmniROM with a patched PlayStore from NanoDroid

Hi
fyi:
I created a Magisk Module to replace the FakeStore in OmniROM with the patched PlayStore from NanoDroid
The Module will replace the apk for the FakeStore with an empty file and add the directory
/system/priv-apps/Phonesky
with the patched PlayStore from NanoDroid.
The patched Playstore works with MicroG so that apps using the license functionality from the Playstore can also be used in ROMs using MicroG .
The ZIP file with the Magisk Module can be downloaded from here:
http://bnsmb.de/files/public/Android/PlayStore_for_MicroG.zip
(I am not sure if I can attach the file in this forum ..)
regards
Bernd

How can i update this patched Playstore Module?

Does your module do the same as the fakestore2playstore module ? If not, what are the differences ?
SERGE4NT said:
How can i update this patched Playstore Module?
Click to expand...
Click to collapse
I don't think it needs updating...
edit : so, I wanted to install your module next to this version of microG. It is a microG installer that works as a Magisk module, and the only way I got microG to work on unofficial CrDroid Android 13 for the Samsung A20e.
Anyway, didn't managed to install your module through Magisk. If I tried to install it after having installed the microG module, it says error: system/priv-app/Phonesky already exists.
If I try to install it before the microG module, it says error: no version of microG detected.
I had to boot to TWRP, try to install it from there, where it would hang on detecting TWRP, force restart my phone, then it appears as installed for some reason.
But it works ! Don't know how or why, or what's up with the installation, but it works, whereas other versions of this module didn't, so... thanks x)

Hi
fiy:
see How to install a more recent version of the Playstore in OmniROM for how to install a more recent version of the playstore
regards
Bernd

How to edit hosts file for Android 11 OnePlus 8 Pro

Hi, I have rooted my OnePlus 8 Pro device, and I want to edit my hosts file,
I tried to follow this guide here: https://forum.xda-developers.com/t/editing-host-file.4345167/
But it seems the post is old and not maintained anymore. I tried to search other thread but no luck so far.
I'm on Android 11 (11.0.11.11) and I got failure while remounting. It seems I cannot remount because I need to disable dm-verity first.
But when I run adb disable-verity, I got following error:
Code:
verity cannot be disabled/enabled - USER build
Any idea how to make it work?
Thank you in advance

Why dont you use the build in magisk systemless host module?

xtcislove said:
Why dont you use the build in magisk systemless host module?
Click to expand...
Click to collapse
What is a magisk systemless host module?

tealtadpole said:
What is a magisk systemless host module?
Click to expand...
Click to collapse
Systemless Adaway With Magisk
Systemless Adaway With Magisk Can anyone help me with this i already have a working magisk safetynet and everything.... but i need the adaway this is the reason i root my phone but i dont want to loose ota thanks
forum.xda-developers.com