Database Develop

Flashing system.img to upgrade from mra58k to N

so heres the situation
running stock mra58k rooted with elementalX
encrypted
rooted with su2.46
can i just flash system.img from mra58n to upgrade then reroot?

darthchilli said:
can i just flash system.img from mra58n to upgrade then reroot?
Click to expand...
Click to collapse
Yes, that will work just fine. You may need a newer version of SuperSU to get proper root on marshmallow. The latest version is 2.52 (there is also a v2.56, but that's only for the "systemless" root method).

Face_Plant said:
Yes, that will work just fine. You may need a newer version of SuperSU to get proper root on marshmallow. The latest version is 2.52 (there is also a v2.56, but that's only for the "systemless" root method).
Click to expand...
Click to collapse
So if we are running a Kernel and rooted, this will work. I guess I am nervous to try flashing the new OTA because I don't want to have to setup programs again, but that isn't a huge deal.

haibane said:
So if we are running a Kernel and rooted, this will work. I guess I am nervous to try flashing the new OTA because I don't want to have to setup programs again, but that isn't a huge deal.
Click to expand...
Click to collapse
I've been using the same non-encrypted/no boot warning kernel on MRA58K, MRA58N, and MRA58R with no issues. I was rooted with the experimental "systemless" root method. I have flashed the system.img from both MRA58N and MRA58R without losing root or having to flash anything extra (like my kernel or SuperSU) or set up my phone again.
The only things you will have to redo (if you ever did any of these in the first place) are build.prop edits, redelete any system apps you removed, reinstall Busy box, and reinstall hosts files from ad blockers. All of your other data should remain unchanged.

Face_Plant said:
I've been using the same non-encrypted/no boot warning kernel on MRA58K, MRA58N, and MRA58R with no issues. I was rooted with the experimental "systemless" root method. I have flashed the system.img from both MRA58N and MRA58R without losing root or having to flash anything extra (like my kernel or SuperSU) or set up my phone again.
The only things you will have to redo (if you ever did any of these in the first place) are build.prop edits, redelete any system apps you removed, reinstall Busy box, and reinstall hosts files from ad blockers. All of your other data should remain unchanged.
Click to expand...
Click to collapse
So my follow up question. I am runing SuperSU 2.52. Would I have to do a clean install to update to the "systemless" after a OTA flash?

haibane said:
So my follow up question. I am runing SuperSU 2.52. Would I have to do a clean install to update to the "systemless" after a OTA flash?
Click to expand...
Click to collapse
You cannot flash an OTA if you are rooted.

danarama said:
You cannot flash an OTA if you are rooted.
Click to expand...
Click to collapse
Sorry I meant do a system.img flash. I assume it has the same result as doing a full OTA and then re-rooting/adding custom kernel.
Basically, I am just trying to get from mra58k with supersu 2.52 and franco kernel to mra58r with supersu 2.52 or 2.56 and franco kernel.
Obviouslly, I could probably just do a nandroid backup and go crazy on the phone to try and do whatever, but I wanted to see what the preferred method would be first.

haibane said:
Sorry I meant do a system.img flash. I assume it has the same result as doing a full OTA and then re-rooting/adding custom kernel.
Basically, I am just trying to get from mra58k with supersu 2.52 and franco kernel to mra58r with supersu 2.52 or 2.56 and franco kernel.
Obviouslly, I could probably just do a nandroid backup and go crazy on the phone to try and do whatever, but I wanted to see what the preferred method would be first.
Click to expand...
Click to collapse
I don't know what a full OTA is but no, an OTA is not the same as flashoing a system.img.
Process should be flash system.img and boot.img, boot to recovery, flash kernel and supersu. All good. Do not boot up to android before flashing kernel if you want to be unencrypted.
The reason for flashing the boot.img is that some kernels do not provide their own ramdisk, so it is always worth flashing the boot.img that comes in the factory image for the sake of wasting 3 seconds.

danarama said:
I don't know what a full OTA is but no, an OTA is not the same as flashoing a system.img.
Process should be flash system.img and boot.img, boot to recovery, flash kernel and supersu. All good. Do not boot up to android before flashing kernel if you want to be unencrypted.
The reason for flashing the boot.img is that some kernels do not provide their own ramdisk, so it is always worth flashing the boot.img that comes in the factory image for the sake of wasting 3 seconds.
Click to expand...
Click to collapse
Ah. That makes sense. I have been avoiding going unencrypted because well encryption brings security so why not lose a little processing to gain security. Anyhow, Thanks I'll try this method after my backup finishes.
Also not sure if you know the answer to this, but could I move to the systemless root variant after doing the system.img and boot.img flash? I would assume this would become possible because the system.img would clean anything done by the standard root.

haibane said:
Ah. That makes sense. I have been avoiding going unencrypted because well encryption brings security so why not lose a little processing to gain security. Anyhow, Thanks I'll try this method after my backup finishes.
Click to expand...
Click to collapse
No probs.

This is probably going to sound insane, but I am almost annoyed that the update appears to have worked flawlessly. I kind of wanted some sort of catastrophic failure. I've yet to have any bootloop etc...

haibane said:
This is probably going to sound insane...
Click to expand...
Click to collapse
yeah....

haibane said:
This is probably going to sound insane, but I am almost annoyed that the update appears to have worked flawlessly. I kind of wanted some sort of catastrophic failure. I've yet to have any bootloop etc...
Click to expand...
Click to collapse
Be careful what you wish for, you just might get it.

How to install ElementalX Kernel

I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.

The kernel is the boot.img. Just flash it via TWRP and it will automatically be present.

And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Better flash superSU2.65.zip (latest atm).

Not necessarily better. Versions after 2.62 have a number of comments across various threads saying that root doesn't work for them. 2.62 uses a different method from the later versions. 2.62 works fine for me and (from the silence in the forums) for most people, so upgrading to 2.64/2.65 is probably taking an unnecessary risk.
And again, why try to install a different kernel on a working rooted device? It makes no sense to me unless there's an amazing function that will make a discernable difference, and personally I don't believe that any kernel makes that much of a difference in real-life normal usage.

dahawthorne said:
personally I don't believe that any kernel makes that much of a difference in real-life normal usage.
Click to expand...
Click to collapse
Not something i'd agree with since CPU governors and I/O schedulers can make allot of difference to "real life normal usage", obviously this depends on what the developer impliments and user choice.

there are times that I'll run elementalx kernel, but I ALWAYS change the governor and scheduler. always. as I can't stand the way that its set up. personally, I always use ondemand with deadline :angel:

daddylok said:
I'm a newbie and my phone is at Marshmallow 6.0.1, rooted with Nexus Root Toolkit su (with SuperSU 2.62)
later flashed twrp, now want to install ElementalX Kernel.
Do I need to unroot the system, and then flash the kernel with twrp?
thanks in advance.
Click to expand...
Click to collapse
Wondering how you achieved root.I am unable using the stock kernel.TWRP installed just fine.Do you mind sharing your procedure?

Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.

To install elementalx, just flash in recovery.
dahawthorne said:
And why do you specifically want to install Elementalx? If you've got a working rooted phone, why continue to mess with it? Continual unnecessary tweaking is the sure way to end up with a glass-and-metal paperweight...
Click to expand...
Click to collapse
Silliness. Why are you even on xda with that attitude? He probably wants to install it so he can use some of the added features and enhancements.

"Why are you even on xda with that attitude?" Ditto. We're all entitled to our opinions, and my opinion is that a lot of noobs do stuff just to see what happens, and the result is that they're in forums asking after the event "How do I fix this?" rather than "How do I do this?", and in both cases without any particular need or reason or understanding of what they want. And this is a typical thread - an admitted noob wants to install a specific kernel, and still hasn't said why (though he/she has thanked me, which I appreciate ). I think that to warn noobs about unnecessary tinkering is doing them a service - isn't that why we all respond to questions?

dahawthorne said:
Download SuperSU v2.62-3 (you can try later versions, but some people have reported that they don't work for them - v2.62 works fine for me and many others). http://forum.xda-developers.com/showpost.php?p=64161125
Copy the zip file to a folder in your Nexus 6 - say, Downloads, it doesn't really matter which one.
Boot into TWRP. Press Install. Navigate to the folder where the SuperSU zip file is and select it. Swipe in TWRP to install it. DO NOT accept any offer from TWRP to root your device (again) - you'll break it. Once installed, just reboot system. Done.
Click to expand...
Click to collapse
Thanks very much -so to be clear that was with the Stock kernel?
I am running 3.10.40-g557ba38
Trying to avoid a brick situation,sorry to be a bother..

Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.

Awesome thanks again.

dahawthorne said:
Yes, stock kernel. As I understand it, the SuperSU backs up and replaces the stock kernel (as part of the boot image) and will restore it if you unroot. You just need to follow the instructions as written - it's exactly what I did on my stock 6.0.1 ROM.
Click to expand...
Click to collapse
Thanks again-this worked out perfectly and I am running Cyanide which has made me very happy so far.REALLY fast and smooth.Everything working great so far.Loving my N6- who needs Samsung! I just had to edit the .xml file for the Music volume other than that the ROM seems about perfect.

[SuperSU][System-Mode][2.82 SR5]

This is SuperSU that installs always in System-Mode.
Instructions
1 - Download zip
2 - Go in recovery & make a backup (optional, but recommended)
3 - Flash zip
Changelogs here & here
Special thanks to @aufarxda (the original creator of this thread) @Chainfire @CCMT

binaries failed to update
Just installed the lastest security update (6.01) from google on my nexus 6. Flashed v2.66 and binaries will not update. Any suggestions?

Thanks My Brother ?

Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.

aufarxda said:
Reflash the kernel.
Unroot.
Reroot.
Should work.
Hope that helps.
Click to expand...
Click to collapse
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.

fpqc said:
I am on CM13 1/6/2016 nightly on angler, and this is causing a bootloop now. Before this newest nightly, I was able to install with no problem. Systemless also still works.
Click to expand...
Click to collapse
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.

aufarxda said:
Nightly comes with problems.Look Angler's XDA thread and ask others which nightly is the most stable build.
Hope that helps.
Click to expand...
Click to collapse
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.

fpqc said:
The reason I think is that this is the first update with the newest vendor.img. That's the only thing that seems out of the ordinary.
Click to expand...
Click to collapse
Well, just reflash last update before this one.
Or, just wait another update with the fix.

I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0

FernBch said:
I have the Verizon SCH-I545, MDK bootloader, and am running JDC Team's AOSP 6.0.
I am unable to install any version of SU above 2.52. TWRP 2.8.7.0 and 2.8.7.2 by Antaresone and the official 2.8.7.0 all fail with the same message.
Recovery.log
https://www.dropbox.com/s/kmc3bafuvlfq20v/recovery.log?dl=0
Click to expand...
Click to collapse
Solution 1(Tricky, and may not work) :
Try to mount data and system using mount option and remove mounting script on the updater-binary.
Then, use TWRP file manager to remove /supersu manually.
At last, install the zip again.
Solution 2 (not really a solution) :
If you really cant mount data or system, ask the rom dev or someone on your phone's forum for solution.
Solution 3 (1% chance of working) :
Dont bother about the bootloader.
Check your boot image instead.
Solution 4 :
Check if you have chcon on system/bin.
If not download this file and move it into system/bin.
Link :Drive

Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!

Droidphilev said:
Hi,
Thanks! This version finally works for secondary roms in Multrirom!!!
Click to expand...
Click to collapse
Nice to know.

Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk

I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?

slick97477 said:
I installed 2.64 beta via TWRP. It installed successfully however upon reboot it shows i still have 2.52. Is that normal?
Click to expand...
Click to collapse
Don't know. Maybe install the app on the zip manually. Update the binary and if updating fails, full unroot and re-root with the new zip.

krazyace35 said:
Can this be flashed over systemless root to convert to system root or will I have to flash my system.img backup then this. I'm running systemless root on Htc M9 Marshmallow dev edition
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.

aufarxda said:
No, full unroot first.
Then, remove /su
Replace the kernel with new custom one.
And then, flash the system mode zip.
Click to expand...
Click to collapse
Cool thanks for the info
Sent from my HTC One M9 using Tapatalk
---------- Post added at 06:00 PM ---------- Previous post was at 05:30 PM ----------
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk

krazyace35 said:
@aufarxda I'm guessing there are no custom kernels yet for Marshmallow? I can't find one I also noticed flar2 said the kernel source hasn't been released yet
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe not avaiable for your phone.
But most Marshmallow phone devs already made custom kernels for their phones.

Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?

KreAch3R said:
Thanks for this, @aufarxda. Can you tell us what you did and made it always install in System mode?
Click to expand...
Click to collapse
I moved v2.52 script with little modifications (aside from the ui_print).

Anyone know what's in the Verizon Update pushed on 4/12? OTA XT1096

I'm wondering if it's worth it. Version 23.201.2.en.us

I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.

I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?

dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
To take the ota you have to reflash the full 5.1 firmware for verizon.
You can't have root nor a modified sytem for OTAs to work. So you need back all those apps you removed and get rid of root.
Sent from my XT1095 using Tapatalk

jonnythan said:
I'm not sure, but here it is:
https://dl.dropboxusercontent.com/u/12873062/Blur_Version.23.201.2.victara_verizon.verizon.en.US.zip
Is there a way to flash this onto a rooted phone? I unlocked my XT1096 a couple of months ago and installed Teamwin then flashed SuperSU.
Click to expand...
Click to collapse
dunderball said:
I need some help on this too. I heard it's just a security update but it fails for me because I'm rooted and deleted a bunch of apps. Is there any way to take the OTA update?
Click to expand...
Click to collapse
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Please review the first post in that thread as the ROM is partially debloated and has SuperSU and Xposed pre-installed. GApps have been removed and you need to install your own. It is possible with the files posted to have a full stock install but you'll need the instructions from that thread to accomplish that.

mikeoswego said:
I've put together a debloated TWRP flashable version. It's here: http://forum.xda-developers.com/showpost.php?p=66354183&postcount=1057
Click to expand...
Click to collapse
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.

jonnythan said:
Which of these files would I want to flash, if I'm running stock firmware (rooted with SuperSU flashed)? The update from Verizon is ~20 MB, but you have a 30MB modem firmware and 398K bootloader.
Click to expand...
Click to collapse
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.

mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
Click to expand...
Click to collapse
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?

mikeoswego said:
Ok, those files are for the stock based rom that I maintain. You need to read the first post in that thread to understand what it is. SuperSU and Xposed are preinstalled, GApps are removed and you have to install your own. If you want a full stock install, that is also possible with the files posted, it's all explained there.
The file sizes are different because the Verizon patch has some full files like gpt.bin and fsg.mbm but the rest is just small patches to apply to the exisiting files. The first thing the Verizon patch does is check that you have the correct original files and if not, it aborts; you can't apply the patch if you've modified system by installing SuperSU, etc. My patches have the gpt.bin update seperate for ease of putting the files together, the firmware has the fsg.mbm file from the Verizon patch and then the full modem partition from my phone after applying the patch instead of just the patch files. That way the patches can be applied no matter what is on your phone now but they are much larger files.
Click to expand...
Click to collapse
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?

dunderball said:
Thanks mikeoswego. I flashed the two smaller files you provided using TWRP. Are those the only 2 zip files I need? I didn't see anything specific to a kernel or anything.
I am on rooted stock rom where I deleted a bunch of apps I didn't want.
---------- Post added at 04:09 PM ---------- Previous post was at 03:58 PM ----------
It turns out that when I flash the two .zip files, my Moto X still thinks there is a system update available. Is there something else I'm supposed to flash?
Click to expand...
Click to collapse
jonnythan said:
Thanks.. it doesn't seem like I can install just the update. I'd need to flash the whole ROM. Correct?
Click to expand...
Click to collapse
The two smaller zips are the bootloader and modem firmware, the rom and kernel are in the xt1096-5.1-23.32-25-5-2_1.zip file. You could extract the boot.img file from the zip and flash it with fastboot. If you want the full ROM and want to flash SuperSU yourself and remove whatever bloat yourself, then use xt1096-full-stock-23.32-25-5-2.img.7z file; you can flash the image file within that archive with current versions of fastboot. (Or, using 7zip, you could delete the system.img file from xt1096-5.1-23.32-25-5-2_1.zip then rename the .img file in xt1096-full-stock-23.32-25-5-2.img.7z to system.img and place it in xt1096-5.1-23.32-25-5-2_1.zip. Then you would TWRP flash that, it would update your kernel (boot.img) and install the system partition just as if you took the OTA on the stock system.) Like AGISCI said above, the only way to use the OTA directly is on an unmodified stock system.

Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?

jonnythan said:
Forgive me, I'm not really following you. I don't know what's in the OTA exactly. Is there anything in your post that I can flash that will update my system to the latest version without wiping everything and starting from scratch?
Click to expand...
Click to collapse
You must flash the full firmware like was mentioned earlier. It is impossible to do the update with a modified system.
Sent from my XT1095 using Tapatalk

I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.

I flashed the system .img file and it just updated my system without wiping anything. Seems to be working fine, but I had to reflash SuperSU.

desertcat said:
I'm wondering if there is a way to not take the update. I keep getting a nag message about installing the update and I keep pushing reminder out to a new time.
A little background. I have a XT1096 (Verizon version) and unlocked the bootloader and rooted. I also nuked a bunch of bloatware so there is no way that a OTA update will install. I'm not sure that I really want to go back to stock and start over.
Click to expand...
Click to collapse
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.

desertcat said:
I found a way to not take the update. Use your favorite applications manager for root to freeze MotorolaOTA and the update won't be downloaded and you won't get messages about installing the update.
Click to expand...
Click to collapse
THANK YOU!!! After being stuck on vacation for a week with this !#@[email protected]#$ update bugging me to install it every couple of minutes this fix stopped the problem.

Magisk General Support / Discussion

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread

Oh wowww. Thanks!!
Error in the thread title: 2015.8.4

Yay it's finally here!
I'm already using it and I must say it works fine

Man, this "universal MultiROM support" left me full of hope. I hope it works out. And it was time for a mods manager on Android, thanks topjohnwu

Working great on my N6!
topjohnwu has my vote for President!
(and a well deserved donation)

AMAZING!, now to be sure, if i have a rom and want to integrate Magisk, the correct order of flashing is:
1-rom
2-magisk
3-modded su (magisk compatible)
it's that the way?

topjohnwu said:
....Magisk Is A Magic Mask to Alter System Systemless-ly.
If you are running custom roms, dirty flash the rom again to remove all possible issues. If the rom includes SuperSU, unzip the boot image from the rom zip, and flash it through TWRP, flashify, fastboot etc. to restore to stock ramdisk......
....... you can now download Magisk and flash to your device.
To remove Magisk, restore your boot image back (Magisk will backup your boot image automatically in /data/stock_boot(md5).img.gz), then delete /data/magisk.img.
Click to expand...
Click to collapse
is the following still applicable in the case of custom roms?
smohanv said:
1. Boot in to TWRP
2. go to Advanced / File Manager and delete folder named supersu
3. go to Advanced / Terminal and enter these two commandsecho SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu​The first one forces systemless, the second prevents /su/xbin_bind from existing.​4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.
5. Reboot device and enjoy systemless
6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".
7. I rebooted in to TWRP and flashed xposed 85.1 (also updated with 85.2 later) and installed the apk (Material design apk from this thread)
8. All done and my xposed works.....
Click to expand...
Click to collapse

Awesome....
Sent from my AO5510 using Tapatalk

Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?

So wait, before i get excited this means things like viper4android can be installed without messing with system?

swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
Click to expand...
Click to collapse
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app

grep_i said:
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock marshmallow, flashed via twrp, and yes i followed the op correctly. No custom kernel.

swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ��
Click to expand...
Click to collapse
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.

Nezorflame said:
[/COLOR]
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Click to expand...
Click to collapse
The threads download section. Should i have downloaded from phhs thread?

swipp3r said:
The threads download section. Should i have downloaded from phhs thread?
Click to expand...
Click to collapse
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.

Nezorflame said:
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Click to expand...
Click to collapse
Thanks for trying bro.....

@topjohnwu this new "magisk" method. It doesn't allow Android Pay to work on custom roms like CyanogenMod does it? If I remove SU from CyanogenMod and use your root.

Magisk on (Yu Yureka) ARM64 device
i did a full clean wipe and then flashed rom, magisk and 'Magisk Compatible phh's SuperUser' - in that order. magisk manager app does not open.

Holy crap.. everything universal with support for extensions. This platform could be the beginning of a new era in mods. @topjohnwu amazing work. Don't want to be rude, but personally I think the name of the project is not as awesome as the project itself. "Magisk" sounds a bit cheesy.. :silly:

great work, will try it out soon! one little thing i noticed in the thread title...i guess it should be 2016