At the first,
I am not sure the point of this post - is it a question?
If it is supposed to be a guide, it is incorrect and unnecessary as this info is in the release thread.
There is no need for addonsu, as MagiskSU is included, and it will try to remove any existing root method other than an existing systemless SuperSU root.
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!
Hey guys, quick question. I saw that there was a specific command to type to make newer SuperSU install in system mode, how and where do you actually type this command? I think someone said you type that command in TWRP, but I need details, never used a command in TWRP before. Thanks guys! Much appreciated!
Also, I hope I posted this in the right place, wasn't sure if I should have posted this in the Nexus 6 forum because it's what I'm working with, or in SuperSU because it's kind of a general question. Thanks again!
Have a look at this - http://forum.xda-developers.com/showpost.php?p=66321818&postcount=5659
BUT...
If you've never done it before, you're asking for trouble. There are others in the thread reporting that after playing with this their device didn't boot. It hardly seems worth the aggravation, does it...?
If you want system root just install SuperSu 2.65 in recovery. It is the *stable* release, not beta or alpha and installs in system mode with no further modifications necessary.
http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
---------- Post added at 20:31 ---------- Previous post was at 20:29 ----------
Dopamin3 said:
If you want system root just install SuperSu 2.65 in recovery. It is the *stable* release, not beta or alpha and installs in system mode with no further modifications necessary.
Click to expand...
Click to collapse
AFAIK this is not completely correct. If you flash 2.65 it will check first if system root is possible. If not it will root systemless.
dahawthorne said:
Have a look at this - http://forum.xda-developers.com/showpost.php?p=66321818&postcount=5659
BUT...
If you've never done it before, you're asking for trouble. There are others in the thread reporting that after playing with this their device didn't boot. It hardly seems worth the aggravation, does it...?
Click to expand...
Click to collapse
Do you have to navigate to where your SuperSU zip is located?
Droidphilev said:
http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
---------- Post added at 20:31 ---------- Previous post was at 20:29 ----------
AFAIK this is not completely correct. If you flash 2.65 it will check first if system root is possible. If not it will root systemless.
Click to expand...
Click to collapse
I don't think so. It clearly says in the thread you linked "This is SuperSU that always installs in System-Mode." Literally the first sentence in that thread you linked to. From my understanding SuperSu 2.65 is system root stable and 2.68 is system root beta. Other versions may be systemless, but these are definitely not.
Further what would make it fail system root on the Nexus 6? A kernel I guess? Not sure on that.
@H4X0R46 "Do you have to navigate to where your SuperSU zip is located?"
Sorry, I have no idea, since I'm not brave enough to risk bricking my $700 phone. Chainfire's programming is of a standard that I trust to make the best choice for rooting my device, and he hasn't let me down yet.
dahawthorne said:
@H4X0R46 "Do you have to navigate to where your SuperSU zip is located?"
Sorry, I have no idea, since I'm not brave enough to risk bricking my $700 phone. Chainfire's programming is of a standard that I trust to make the best choice for rooting my device, and he hasn't let me down yet.
Click to expand...
Click to collapse
I'd imagine worst case scenario you would have to flash a stock image, but you make a good point! Regardless of the type of install, it has always worked! Thanks for the reply!
Sent from my Nexus 6 using Tapatalk
Dopamin3 said:
I don't think so. It clearly says in the thread you linked "This is SuperSU that always installs in System-Mode." Literally the first sentence in that thread you linked to. From my understanding SuperSu 2.65 is system root stable and 2.68 is system root beta. Other versions may be systemless, but these are definitely not.
Further what would make it fail system root on the Nexus 6? A kernel I guess? Not sure on that.
Click to expand...
Click to collapse
In your post you didn't mention that you were talking about the same thread as me that's why i answered. The official supersu 2.65 works as i wrote (systemless only when system root is not possible). Check Chainfire's changelog. The thread i have mentioned is unofficial and made by someone else. Last official version that has no systemless root is 2.52
EDIT: about your question how Supersu decides to use systemroot/systemless: this is what Chianfire writes about it:
"ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")"
and
"Notes on 2.64+
There have been a lot of changes to the ZIP installer. Hopefully they won't break a lot of installs. If 2.64 works well, it is likely to be promoted to the "main beta" in place of 2.52, and the How-To SU document will be updated with the relevant information.
A major change in setup is that the ZIP installer will try to detect 6.0 firmwares that can be rooted without doing a systemless install. In other words, a root that modifies only /system, but not the boot image. If this is possible, the installer will install into /system (unless you override via "echo SYSTEMLESS=true>>/data/.supersu"). This may catch (a) firmwares that allow sepolicy reloading from /data but have a locked bootloader and (b) custom firmwares setup to handle this. Regarding the latter, while it is not as clean as systemless, those running custom firmwares are more likely to want to modify /system anyway, it is less likely to mess with updates to those firmwares, and it prevents the necessity of reflashing the ZIP after each kernel switch. Of course, the kernel's SELinux policies must support this!"
I'm new to all these things about systemless root and mods. I checked the thread for dummies, I don't see a proper installation procedure in the first posts. Is there something I can follow to ensure the best result? Are the methods different when I want to use SuperSU and not phh's Superuser or MagiskSU? Thanks.
"Installation Instructions" are in "[2017.2.6] Magisk v11.0 - Root & Universal Systemless Interface [Android 5.0+]"
I am looking for a ELI5 installation guide for Magisk. I have very little experience with rooting phones and the guides I have found confuse me. thank you in advanced for the help
Install TWRP.
Flash Magisk zip in TWRP.
Boot up your device.
Install Magisk Manager (for Magisk v12, from v13 it'll be installed automatically).
It's that easy. Of course, there might be compatibility issues, but let's assume there won't be for now and cross that bridge if we get to it.
Looking at the Unlock/Root/etc thread in the X Style forum, you almost had it with the TWRP install. You were doing the correct commands, but using the wrong file. You were trying to install an apk (an app), where you needed to us an image file (*.img). Go back to the thread and you'll see they gave you the link for the proper download.
Links for the Magisk zip and the Magisk Manager are in the release thread.
Also, here's a link to another thread started today on a similar subject. I put a bunch of links and tips in there that may also be useful for you.
Edit:
An important, basic tip when doing things to your device is to always have a backup of important files. Don't leave anything on there that you can't afford to lose.
I have a successfully installed magisk 14.0 from twrp still safety net was showing false so i tried to update through magisk manager but installation keeps on failing for magisk v14.2 now same error with 14.3 it says unable to unpack boot image, any help would be greatly appreciated
Hi,
I need a simple module that only replace a file on /system with Magisk 24.3 and Zigisk.
I'm not a dev and I tried myself with no success by following the instructions: https://topjohnwu.github.io/Magisk/guides.html.
Is someone can do it please !!
nabsboss said:
Hi,
I need a simple module that only replace a file on /system with Magisk 24.3 and Zigisk.
I'm not a dev and I tried myself with no success by following the instructions: https://topjohnwu.github.io/Magisk/guides.html.
Is someone can do it please !!
Click to expand...
Click to collapse
I would recommend using MMT-Extended (Magisk Module Extended), for one thing its a complete template....
GitHub - Zackptg5/MMT-Extended: Magisk Module Template Extended
Magisk Module Template Extended. Contribute to Zackptg5/MMT-Extended development by creating an account on GitHub.
github.com
1) Download the zip by clicking on the Code button, then download zip and extract the MMT-Extended-master folde inside the zip, and then rename it as you wish for your module
2) Read this guide, prolly easier to understand than the official TJW info for a beginner
For a simple /system file replacement module, steps 1,2,3,4,8, should be all you need to do, and then zip (must be zip, not RAR or 7z) up the folder and test
When you have at least tried following the guide, and if you fail, then come back with what you have tried (with a LOT more detail on what youre trying to achieve) and someone will help you.
There is no "create a module for me" service on XDA, you must be willing to at least try first....