Related
**** The posted systemless kernel is only compatible with SuperSU 2.56!!! ****
*** Starting with SuperSU 2.60+ kernel can now be auto-patched for systemless root. ***
**As of 06 December 2015 flar2 has released ElementalX 6.02 for Sense Marshmallow **
* If you still desire a stock kernel with systemless root but want to use newer SuperSU see below *
Messed around with the boot.img from today's Marshmallow update and have made it compatible with systemless root.
Systemless root in general is experimental and so is the kernel. I've literally just made it and tested it enough to that it boots and apps are able to be granted root access, so flash at your own risk.
Kernel has been running without issue.
Other than systemless root compatibility, this kernel is completely stock and no other modifications made.
Intructions - Systemless:
Download kernel from here.
Download SuperSU 2.56 beta from this post (only one that works with this method of root).
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash SuperSU-v2.56-20151030013730.zip afterwards.
Reboot
TWRP will notify of no SU when you reboot, click DO NOT INSTALL as TWRP needs to be updated to detect this root method (it only looks in /system)
Instructions - Traditional:
Download kernel from here.
Download SuperSU 2.52 beta from this thread (it's the M compatible version)
Copy both to phone
Flash the image directly using TWRP (toggle from ZIP to IMG under install)
Immediately flash BETA-SuperSU-v2.52.zip afterwards.
Reboot
Keeping stock kernel with updated SuperSU:
If you prefer running the stock kernel with systemless root and want to stay current on SuperSU versions you need a stock kernel when you update SuperSU. When SuperSU installs it tries to restore a backup it made of your boot.img from the last time SuperSU was installed. Since this was made before auto patching there won't be a backup. Also, in newer versions it detects if your device needs systemless or if it can modify /system. If TWRP hasn't been told to keep system read-only it will likely default to a /system install. So, if you want to keep stock kernel and systemless root there are two things you are going to need:
Stock Kernel: You can actually use the kernel provided for traditional root as a stock kernel for the purpose of these instructions.
Systemless Override: To guarantee that SuperSU gives you the systemless install over /system you need to create a file called ".supersu" with the line "SYSTEMLESS=true" and place it in /data in TWRP before you install (eg. /data/.supersu). Alternatively, you can download this one (extract from the ZIP and place in /data).
When the file is placed in /data flash the boot.img in TWRP and then flash SuperSU. It will make a backup when it installs so don't remove it as it will look for this backup again when you install an updated version.
Note: These are only to tide us over until HTC releases source allowing awesome devs like flar2 to work their kernel magic.
Not checked yet, but is systemless the only way to do it on 6.0 ?
Electronic Punk said:
Not checked yet, but is systemless the only way to do it on 6.0 ?
Click to expand...
Click to collapse
No, you can still do it by modifying /system, but Marshmallow made it so kernels had to be modified as well to allow root. @Chainfire took it a step further, since we already have to modify the boot.img we can modify it a little more and remove the need to alter /system and make it easier to accept OTA updates. The link I put in the OP explains it a little more, but here it is again.
Added root modified kernel for using "traditional" (modifies /system) root to the OP along with link to current Marshmallow compatible SuperSU.
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
If you still have stock kernel and no root you can just flash the latest SuperSU (v2.65).
If you're systemless already but don't have a backup you need to flash a boot.img that isn't already systemless modified as SuperSU will abort the install.
You can't flash the one in the OP for traditional (modifies /system) root and it will patch that one, but unless your set your /system partition to read-only, it will install using traditional root (this is the case with any unmodified boot.img not just this one because it's modified for traditional root). To make sure SuperSU installs using systemlesss you need to place the mentioned .supersu file in /data/ o make sure system is read-only in twrp. You also want to use latest SuperSU.
Just make sure you don't let TWRP install it's own SuperSU package that it includes. TWRP by default can't detect systemless root installs, so each time you reboot from TWRP it will warn that there is no root access on the device. It is important you make sure to click DO NOT INSTALL.
If you don't want to be bugged with the no root message in TWRP you can download this version which has the incompatible SuperSU package removed disabling the root check.
HAHAHAHAHA!!!!! Silly me...... it was written up there......
mcta said:
I'm trying to do a systemless root. Just to confirm, I should flash the latest TWRP. Then from there flash the kernel then SuperSU both through TWRP?
Click to expand...
Click to collapse
Okay, hopefully this is a stupid question, but I want to be sure before I flash something to boot.
I followed the instructions before the later versions of SuperSU betas came out, so I have the above linked custom boot image, but would like to be able to update to later versions. Can I safely assume that the boot_signed.img file I pulled out of ROM.ZIP in the Developer Edition Marshmallow RUU is the correct "stock" bootloader? Note that I ran the RUU, let it pause on accepting the license, then pulled the ROM.ZIP out of the temp folder to extract the binary.
Hi! Im pretty much new to rooting and I was wondering does the phone have to be S-OFF or S-ON. If it has to be S-OFF, how do you do it?
Thank you for help!
-This methode is old but working with emui 4 Android MM (6). Not work with Android N (7).
-Xposed not work in systemless mode if your Android security patch is >= november 2016
-Try to search the last version of zip files and apk on google, the version on this tutorial is old.
Hi!
This tutorial will install Magisk, phh's superuser, xposed and busybox on your Huawei P9 lite device!
Tested on a VNS-L31C432B151 version but normally work on all VNS-L31 and VNS-L21.
Magisk will allow you to "hide" the root... not realy just hide because Magisk and phh's superuser systemless edition create the root outside the system folder!
Magisk feature for common user:
-"hide" root (PokémonGo, Androidpay, banking app, ... all work!) work with
-Magisk not only allow you to replace existing file and directories, but also support adding new files and directories into system!
-Update OTA work! (not tested by me)
For more detail visite this post: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Phh's superuser work at 100% on this device
After a lot of Xposed version tested I can say that Xposed systemless edition is by far the best for P9 lite!
DONT install busybox on system folder!
Ok let's go:
1 Update your system on last emui version and swipe data/factory reset to get a clean and untouched device!
2 Unlock your bootloader (see multiple method on this forum)
3 Install TWRP 3.0.2.0 (see multiple method on this forum)
4 Download this files: Magisk V6.zip / phh's superuser 17.zip / xposed-v86.5-sdk23-topjohnwu.zip / Magisk Manager.apk / XposedInstaller_by_dvdandroid.apk. Put all this files on your externalSD.
5 Go to TWRP recovery and flash in order [Magiskv6.zip > phh's_superuser.zip > Xposed-v.86.5.zip] also reboot your device.
6 When you are on the homescreen go reboot again.
7 Install Magisk Manager.apk and XposedInstaller.apk, then go to the playstore download and install Phh's SuperUser app AND Busybox meefik. Reboot after this step.
8 Open your setting app and allow permission SD card to Busybox.
9 Open Busybox >> settings. Remplace the path file /system/xbin/ with /data/busybox/ and check "Remplace Applets". Also go Menu Zip Archive and download this zip.
10 Go on TWRP recovery and flash the busybox zip file.
10 please perform 3 or 4 reboot
DONE!
So, please try to open yours setting app. if it appears you have done! If not, please try again this method
Now, go Magisk Manager (app) and switch root togle off, launch your protected against root app and normally work!
(Dont need reboot between switch root off/on!)(Selinux switch work, but not persist a boot)
Have fun!
Well done. Works perfect.
The are no files any more
Links are dead
deleted
Evas0r said:
Battery draining after the process...
Is this xposed fault?
Click to expand...
Click to collapse
yes u have to flash another version
Did anyone try this on Nougat/Android 7?
Alexander33 said:
Did anyone try this on Nougat/Android 7?
Click to expand...
Click to collapse
TWRP with this [RECOVERY]Revolution Recovery Android Nougat {15-12-16} Beta .9 in Nougat but anything I tried to flash failed.
Is there anything one can do to get Pokémon Go working while having all of these installed?
Alexander33 said:
Did anyone try this on Nougat/Android 7?
Click to expand...
Click to collapse
Hey, man I've tested it on my Huawei P9-LITE B370 and it all works perfectly. To flash Magisk, you need this custom recovery (https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356)
this really helped me thanks
Helped me alot. Still, post is a bit old, so what I did on b380 version:
FLASH RECOVERY twrp-3.1.1-0-venus.img
FLASH KERNEL Elite+Kernel+for+P9+Lite+CxxB3xx+v10.1.zip
ROOT with Magisk-v13.0(96f8efc).zip
INSTALL busybox archive via recovery to /sbin (for me it installed on /system/xbin, still ok.)
REBOOT after each step
Finally works ! :good:
is this Magisk work on Huawei P9?
I have Emui 5.0 and Android 7.0. I flashed everything except xposed but I still can't use Pokémon Go or Snapchat. Is it beacause i can't flash xposed? And when yes, how can I fix it?
Lg ThePrinoob
ThePrinoob said:
I have Emui 5.0 and Android 7.0. I flashed everything except xposed but I still can't use Pokémon Go or Snapchat. Is it beacause i can't flash xposed? And when yes, how can I fix it?
Lg ThePrinoob
Click to expand...
Click to collapse
flash magisk v13
simo255 said:
flash magisk v13
Click to expand...
Click to collapse
Ok, I will test it!
I installed magisk v13 and got the app but it when it check safety net it doesnt work. What should I do?
ThePrinoob said:
I installed magisk v13 and got the app but it when it check safety net it doesnt work. What should I do?
Click to expand...
Click to collapse
enable magisk hide and see if usb debugging is enabled
simo255 said:
enable magisk hide and see if usb debugging is enabled
Click to expand...
Click to collapse
Okey thank you it worked.
Hey,
If I open the camera app or snpachat I cant make any picture so I have a blackscreen. What should I do? And in youtube or Instagram I cant see videos, they dont load and I also cant hear any sound.
Sorry for my bad english.
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Code:
Installation Instructions
(NOTE: I don't feel comfortable to redistribute SuperSU unless I have explicit permission, so for now, if you want to use SuperSU with Magisk, you are required to have systemless SuperSU installed before flashing Magisk. Magisk will detect SuperSU installation and automatically convert systemless SuperSU into a Magisk Module, using the files that are already installed to your boot image. System installed SuperSU is obviously not supported, since it is not systemless. Actually, it is a trivial task to add official Magisk support to a SuperSU zip package, however the decision is not in my hands.)
If you're rooted with Official Systemless SuperSU, or using Magisk v3+ with Magisk version of phh's superuser
Install the latest Magisk Manager
Install/upgrade Magisk as prompted in the application
Reboot and you're done!!
If you're not rooted, rooted with the depreciated Magisk Version of SuperSU, using Magisk version older than v3, or you got issues when flashing in Magisk Manager (some devices requires Magisk to be flashed in recovery to find boot image location)
(If you have Magisk installed) Flash Magisk Uninstaller to get a clean start
Download the latest Magisk zip file
Download the latest Magisk Version phh superuser from this thread:
[Magisk] [2016.10.4] phh's SuperUser
Flash both zips in custom recovery
Install the latest Magisk Manager for a complete Magisk experience
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
NotExist said:
I am a HTC M9 user and due to some sepolicy issue(perhaps) in latest stable SuperSU (2.78), I can only use 2.65 to prevent a bootloop problem currently.
According to the information in Magisk v6 known issue, issue in sepolicy-injection tool is known and will be fixed in v7. In v7 sticky, it does use own sepolicy-injection tool, I assume it does fix something now.
But, according to the information in v7 sticky:
Since I've donated on SuperSU Pro, I'd prefer to make it work in higher priority, therefore 2nd method is not in my consideration now. If I start from a brand new phone (RUUed device with fresh TWRP recovery only), there's 3 ways I tried to apply Magisk v7, here's the process and result:
1. Flash SuperSU 2.65, and the system should count as "If you're rooted with Official Systemless SuperSU" state.
=> Update SuperSU 2.65 to 2.78 with SuperSU own update process in apk, reboot required, SUCCESS.
=> Install latest MagiskManager, SUCCESS
=> MagiskManager got SuperSU authorized, SUCCESS (root still working at moment)
=> MagiskManager found latest version (v7) and suggest to install it, accept and reboot, SUCCESS(boot successfully)
=> Open SuperSU apk, FAILED (root lost, not able to find su binary)
2. Flash SuperSU 2.65 and then follow by Magisk v7 zip
=> Root does't work, cannot find su binary, FAILED
3. Flash SuperSU 2.78 and then follow by Magisk v7 zip (assuming Magisk V7 will repatch the kernel with fixed tools and the boot loop can be fixed)
=> Bootloop, FAILED
Is there anyone success in any configuration on HTC M9?
Click to expand...
Click to collapse
Am using an honor 7 PLK-L01 with MM build B370.
Also tried the first method you described with SuperSU 2.62, difference being that magisk manager could not install v7 zip so flashed it manually. It said something about
Insufficient storage for boot image
and kind of aborted.
Since then flashing SuperSU says seplocy failed and aborts.
Tried flashing a new boot and rooting, still the same.
Flashed boot and Cust, the same error both with magisk and SuperSU.
Cleared dalvik and cache, still the same.
Tried the magisk uninstaller, no success...
Would appreciate a solution.
Sent from my PLK-L01 using XDA Labs
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
ibrokemypie said:
bump, says installing su helper, then there is no root upon boot. supersu cant find binary and magisk manager crashes due to no root
Click to expand...
Click to collapse
Had to flash system, boot and Cust to root again using SuperSU.
Otherwise it was failing and flashing only boot did not cut the deal.
Sent from my PLK-L01 using XDA Labs
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
HyperCriSiS said:
I have the same issue. Could not get SuperSU 2.65 running with Magisk.
Click to expand...
Click to collapse
Magisk ver 6 works well but have to have that zip and it's corresponding apk I guess 1.2 that is.
Used it a couple of days ways back just to make sure it works.
An update that it works after Magisk v8, although there's no information about it.
(Flash SuperSu v2.65 -> Update to SuperSU v2.78 with Google Play -> update su binary to v2.78 with SuperSU -> install Magisk Manager v2.1 -> Install Magisk v8 with Manager -> done!)
Hello everyone,
So I wanted to root my Honor 5c (NEM-L51) under android 7.0, so I have unlocked the bootloader, I have installed a custom recovery compatible with android 7.0 which is twrp-3.1.0-2-hi6250 I think ...
Then I tried to flash the supersu.zip, I had to try several versions because many did not work and indicate "image boot patcher" failure aborting "then I flash a supersu that works but I have the impression that the root has badly installed ...
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Maybe the best method would be to flash the emui stock rom 5.0 but it is not found, and it seems to me that you must also remove the root to avoid any "brick"..
if you have solutions to my questions it would be fine !!!!!
Thank you in advance !!!
Curiosity2000 said:
I explain, first I test with root checker which tells me that everything is fine, but I can not update the binaries su as the supersu app asks me ... I reboot remove , Reinstall the app supersu NOTHING does !! So I wanted to remove the root to reinstall it properly but it does not want to be deleted (root checker still shows the presence of the root) more so I wanted to delete it manually but the file "system / bin / su " and "xbin / su "are not found there is only one su "su" file at the root directory...
Click to expand...
Click to collapse
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
sclarckone said:
I have the same problem with the latest stable SuperSU (2.82) that asks me to update the su binary and fails.
As for the su binary not found in /system/bin and /system/xbin it's probably because SuperSU made a systemless root (check this).
And be advised there might be some problem with restoring in the TWRP version you found (see here).
[EDIT]: I was able to update my SuperSU installation by flashing the latest stable version from the official thread with TWRP.
Click to expand...
Click to collapse
Okay , thanks you for yours answers, I have effectively a supersu systemless I will test yo flash the latest supersu, if it don't work I will remove the su and flash an other twrp or flash the rom stock I think ...
[EDIT] I success to remove the Root systemless with flash the boot.img , but the latest supersu doesnt work for me . I try to install Magisk
[REEDIT] Okay, I success to flash Magisk 13.3 I am root
Stay with magisk, it is better than SuperSU
PalakMi said:
Stay with magisk, it is better than SuperSU
Click to expand...
Click to collapse
Okay thanks you !
Curiosity2000 said:
Okay thanks you !
Click to expand...
Click to collapse
No prob
Hi!
I have rooted Samsung S7 Edge with android 7. I currently have SuperSU v2.79 installed. I want to install Magisk because I want to hide root from certain apps. Should I remove SuperSu before I install Magisk?
Other question is that here https://topjohnwu.github.io/Magisk/faq.html I read that Magisk no longer hides root because now the new way is to use Magisk modules. Do I even need Magisk at all or if I have TWRP 3.1.0.0 can this also be used to install those Magisk modules? Or would it be best to grab some older Magisk that has root hider there already?
sysctl said:
Hi!
I have rooted Samsung S7 Edge with android 7. I currently have SuperSU v2.79 installed. I want to install Magisk because I want to hide root from certain apps. Should I remove SuperSu before I install Magisk?
Other question is that here https://topjohnwu.github.io/Magisk/faq.html I read that Magisk no longer hides root because now the new way is to use Magisk modules. Do I even need Magisk at all or if I have TWRP 3.1.0.0 can this also be used to install those Magisk modules? Or would it be best to grab some older Magisk that has root hider there already?
Click to expand...
Click to collapse
yes u should, always use the latest one
Is it good enough to uninstall SuperSU app when android is running or should I reboot to TWRP and do some magic there?