Database Develop

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).

[ROM/Kernel] Stock 7.1.1 B02 based for A2017G. The "We can do it better than zte" ed.

[ROM/Kernel] Stock 7.1.1 B02 based for A2017G. The "We can do it better than zte" ed.
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootstack. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.

This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk

davidroid1 said:
This rom can flash from twrp? What version of twrp?
Thank you, I was expecting something like this.
I use google translate
Enviado desde mi ZTE A2017U mediante Tapatalk
Click to expand...
Click to collapse
For me TWRP 3.1 did its job.

tron1 said:
No fancy super nice pictures and no other great blabla here.
Thx @wineds for providing a TWRP backup from the system. It's the base of this.
Thx @SuperR. for his great kitchen.
Little mods:
init.d enabled
dm-verity disabled
SuperSU included
Spyware stuff:
tencentNLP removed
Email_ZTE removed
no further actions done on this.
For me it's working with the Universal Bootloader. You will find it in the LOS thread.
Flash it with TWRP.
Download:
The ROM --> https://www.androidfilehost.com/?fid=673368273298948672
The Stock Kernel if you played to much with the others -->https://www.androidfilehost.com/?fid=817550096634763383
p.s.: I've read about problem with big sdcards in conjunction with the original B02 rom. I've never been on this crap version, so I can't tell if there's a difference in the behaviour. But up to now I have no problem with my 128GB sandisk card. And yes, it's formated with extfs.
Click to expand...
Click to collapse
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?

sToRm1nG said:
How did you disable dm-verity? Patch the boot image with the no-verity zip from nethunter?
With the removal of TNL does the Google Location Provider now provide the location information?
Click to expand...
Click to collapse
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.

tron1 said:
Google maps showed me my correct location while beeing inside my house. So i guess it is working right. If not we still have the option to flash/install opengapps to make it run as designed.
Click to expand...
Click to collapse
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.

sToRm1nG said:
Thanks, I will probably try it myself since I am not completely satisfied with LOS.
What about dm-verity? Did you patch the boot image with the zip file I was talking about? I'm asking because I'd probably do it myself.
Click to expand...
Click to collapse
It's just a "click" in the SuperRs kitchen boot image config menu.

Anyone who has U model tried?

WesTD said:
Anyone who has U model tried?
Click to expand...
Click to collapse
I'm not sure if the U model contains the Tencent Network Location app (AFAIK it is not).

Pin Input necessary after installation ....
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?

Snoopy2006 said:
I´m have a A2017G with Stockrom B08 on MM and TWRP 3.1.0.0
Installed the first the Kernel and then the Nougat_7_1_1_B02_we_can_do_it_better_than_zte.zip.
Wipe Cache and Reboot to recovery , than into to the system.
Result:
Need a Pin for the first start, but no ok. I could input all numbers and delete it. But nothing go on.
Any Idea for my failure ?
Click to expand...
Click to collapse
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.

From MM B08 to Nougat 7.1.1 B02
tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with
Click to expand...
Click to collapse
At the Moment I`m back to MM B08 on the Axon 7 2017 G !
What should I flash ?

tron1 said:
Yes, I have an idea. You didn't read and/or under-stand what you have to flash and what not. You don't have to flash the kernel (it's just in case you played with other kernels, so you don't need to flash the whole system). The thing you have to flash before is the universal Bootstack from the LOS thread. For removing the pin do the following in TWRP:
head to Advanced > File Manager, and go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the “Delete” button). Then, delete all the files containing the word locksettings.
Click to expand...
Click to collapse
In my Systemfolder I find gatekeeper.password.key and gatekeeper.pattern.key. Should I remove these 2 Files ?

hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.

can we select the apps which we want and which we do not want while installing ?

sendem said:
hi
thx for the build, but seems I missed something, because the gps is not working without wifi(gps cant lock on).
I tried google and here. coming from NucleaRom flashed only the rom and the universal bootstack.
Click to expand...
Click to collapse
Tried it with Sigic and GPS test tool, no problem here

I flashed the kernel now the gps its ok(so no problems for me) .dont use the latest twrp 3.1 it has some bugs.
best regards.

I understand you kept this close to stock, but I have 3 questions.
Does it support Live Wallpaper? (stock B02 doesn't)
Can you turn off the lock screen 'None'?
Does it run Daydream smoothly?
You need to put it in the viewer to really tell. I tried on other ROMS, but it was super choppy and jittery to the point of nausea.

Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).

HuKu52 said:
Very good battery life, but no MTP connection possible. It's the same fault as with all LOS based roms (based on 7.1.2).
Click to expand...
Click to collapse
No problem here. Check bootstack/modem

Questions regarding xiaoumi.eu ROM

I made the update from stable global to beta global last week, because I needed to unlock bootloader. Now my plan was to wait for the first stable release of Lineage, but I didn't know about Xiaoumi.eu rom and that headphone volume was so bad on this stock (beta) rom...
Now my questions are:
Which partitions have to be wiped before flashing the ".eu" rom?
(Already googled this one on my own, see "EDIT")Are the weekly versions like Beta versions? If yes then would this one be the latest stable rom:
xiaomi.eu_multi_MIMAX2_V8.5.15.0.NDDCNED_v8-7.1.zip
Other than that there shouldn't be any other Things to worry about, right?
Thanks in advance!
EDIT: So I googled a bit about the meaning of weekly and I guess it will work well enough for me, downloading this one right now:
xiaomi.eu_multi_MIMAX2_7.10.12_v9-7.1.zip
I couldn't find much about my other questions though..
EDIT 2: I just went the "factory reset" way and wiped data, cache and dalvik and it worked.
No further questions from me.

Were you able to install Xposed on this ROM?

haven't tried yet, I don't have the time eight now to fix it if it starts acting weird or bootloops...
maybe I have some time in the weekend, I really need xposed fir pbmc...

dnbdel said:
Were you able to install Xposed on this ROM?
Click to expand...
Click to collapse
Good news, look at my reply in this thread: https://forum.xda-developers.com/mi-max-2/how-to/xposed-mi-max-2-t3686416
Tazmaniiac said:
I finally managed to flash xposed-v88.2-sdk25-arm64-test4.zip from the official MIUI 9 Github thread.
I'm on latest weekly MIUI 9 xiaomi.eu rom (7.10.19), which is Android 7.1 with Magisk 14.0. Flashed via iscle's TWRP.
Download for test4 (Android 7.1), Android 7.0 would be this one
Got the downloadlink from here: http://en.miui.com/forum.php?mod=viewthread&tid=946636&highlight=xposed
I suggest you to read the description in the MI Forum thread. I haven't tested any modules yet, I only know that the framework is active for me and that it disabled SafetyNet.
Click to expand...
Click to collapse

Tazmaniiac said:
Good news, look at my reply in this thread: https://forum.xda-developers.com/mi-max-2/how-to/xposed-mi-max-2-t3686416
Click to expand...
Click to collapse
Thanks man, sadly I the phone still won't boot after installing this updated Xposed version. Here are the steps I did:
Install newest Xiaomi ROM (7.10.19)
Flash TWRP
Install Magisk 14 zip via TWRP
Boot up again to check if Magisk was installed (it was)
Flash V88.2_Sdk25_Arm64 Xposed zip
-> Phone doesn't boot
Did I do a dumb mistake here or sth?

dnbdel said:
Thanks man, sadly I the phone still won't boot after installing this updated Xposed version. Here are the steps I did:
Install newest Xiaomi ROM (7.10.19)
Flash TWRP
Install Magisk 14 zip via TWRP
Boot up again to check if Magisk was installed (it was)
Flash V88.2_Sdk25_Arm64 Xposed zip
-> Phone doesn't boot
Did I do a dumb mistake here or sth?
Click to expand...
Click to collapse
Nope, that's more or less how I did it. But before I flashed this version of Xposed I installed the Xposed Installer. Maybe that's necessary, but I think not.
Can you try out flashing the no-verity-opt-encrypt.zip? I did it for something else earlier and also after every attempt of flashing Xposed.
If I understand it right some Xiaomi phones bootloop after you write to /system, then you have to flash that file to fix it. Xposed writes to /system, so that could be a solution.
Before you flash that research it a little bit more, because I don't know much about this topic and don't want to give you false advice.
EDIT:Did you flash the xposed version from my downloadlink? It is different from the regular 88.2 SDK25, it's a testversion made by the xposed creator specifically for MIUI 9 devices.

What really happen to magisk

Why make everything complex now.
I cant find the link for magisk.zip magisk uninstaller etc.
The magisk apk also no help either.

You might want to take a look in the v22 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Things are actually simpler now since everything is included in the apk.

Didgeridoohan said:
You might want to take a look in the v22 release notes:
https://topjohnwu.github.io/Magisk/releases/22000.html
Things are actually simpler now since everything is included in the apk.
Click to expand...
Click to collapse
I'd tried the app said to change the magisk22.apk to zip and i change it to zip and click lets go but nothing happen. Also cant install magisk.
Everything used to be very fast and easy to install magisk and now they hide the .zip link, make it complicated with the app apk. Need to download boot.img and change the apk to zip file.
Man this is so complex.
i use asus zenfone max pro m1 btw

I don't know that you're talking about... The only difference from previous releases of Magisk is that if you now want to install from TWRP you need to first rename the .apk to .zip, and if you want to uninstall from TWRP you rename it to uninstall.zip.
That's it. Everything else is exactly as it has been for a very long time...

Didgeridoohan said:
I don't know that you're talking about... The only difference from previous releases of Magisk is that if you now want to install from TWRP you need to first rename the .apk to .zip, and if you want to uninstall from TWRP you rename it to uninstall.zip.
That's it. Everything else is exactly as it has been for a very long time...
Click to expand...
Click to collapse
I'd the twrp method and it worked. Tq. I thought i need to flash it at magisk app.

i'm sorry it's a long time since i rooted my phone, but i remember that it was possile to install moduels right from the magisk app, is it changed now or it's just that i'm blind xD ?
Thx

Gianluk99 said:
i'm sorry it's a long time since i rooted my phone, but i remember that it was possile to install moduels right from the magisk app, is it changed now or it's just that i'm blind xD ?
Thx
Click to expand...
Click to collapse
If you can't enter in modules tab, probably your device is not properly rooted.

VD171 said:
If you can't enter in modules tab, probably your device is not properly rooted.
Click to expand...
Click to collapse
Yeah you're right. i had something wrong going on with my root XD i tried again and it all works fine now.

Gianluk99 said:
Yeah you're right. i had something wrong going on with my root XD i tried again and it all works fine now.
Click to expand...
Click to collapse
Good work, my friend

Didgeridoohan said:
I don't know that you're talking about... The only difference from previous releases of Magisk is that if you now want to install from TWRP you need to first rename the .apk to .zip, and if you want to uninstall from TWRP you rename it to uninstall.zip.
That's it. Everything else is exactly as it has been for a very long time...
Click to expand...
Click to collapse
Holy hell! That actually works?! The installation guide doesn't convey this at all! Going by that it's super complicated compared to before. Extracting boot.img is quite an endeavour already and then there's extra steps for ramdisk and whatnot. Custom recovery boot vuide with long pressing and short pressing until splash screen.
That guide needs to be adjusted.

Immortal68 said:
Holy hell! That actually works?! The installation guide doesn't convey this at all! Going by that it's super complicated compared to before. Extracting boot.img is quite an endeavour already and then there's extra steps for ramdisk and whatnot. Custom recovery boot vuide with long pressing and short pressing until splash screen.
That guide needs to be adjusted.
Click to expand...
Click to collapse
The installation process is the same of before.

Immortal68 said:
The installation guide doesn't convey this at all!
Click to expand...
Click to collapse
Uhm...
https://topjohnwu.github.io/Magisk/install.html#custom-recovery
And is a simple change of the file extension such a hassle? Everything else is exactly as it has been before...

Didgeridoohan said:
Uhm...
https://topjohnwu.github.io/Magisk/install.html#custom-recovery
And is a simple change of the file extension such a hassle? Everything else is exactly as it has been before...
Click to expand...
Click to collapse
No, not at all! I actually understand now why it says that it's gotten easier! Only renaming the file ending and having everything in one file is super convenient.
The thing is: The installation guide starts with installing Magisk.apk and checking RAMdisk and continues to guide you through steps that are very different from the procedure before. The option you mentioned you be in Bold at the top, with an addition: "Try this first - if it doesn't work, try the rest of the stuff in this guide".

Immortal68 said:
No, not at all! I actually understand now why it says that it's gotten easier! Only renaming the file ending and having everything in one file is super convenient.
The thing is: The installation guide starts with installing Magisk.apk and checking RAMdisk and continues to guide you through steps that are very different from the procedure before. The option you mentioned you be in Bold at the top, with an addition: "Try this first - if it doesn't work, try the rest of the stuff in this guide".
Click to expand...
Click to collapse
Installing Magisk from a custom recovery is actually only kept as a legacy option. More and more devices do not have a custom recovery available and there are many devices where the custom recovery that is available actually is broken and can't properly install Magisk.
Therefore, John considers the boot/recovery image patching the only properly supported installation method. That's the only way he can know for sure that everything needed for installing Magisk is in place.
That's why the instructions are written as they are.