{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey Guys,
As we all know, our Zenfone 2 has a slightly different method for installing Magisk. It is often confusing to install Magisk Properly and there is sheer lack of proper guides and support for the same for our device.
I was recently looking to install magisk in order to get banking apps to work on my device and also get the play store device status to "Certified".
My Device is as follows:
Device: Asus Zenfone 2 | ZE551ML | 4GB RAM | 32 GB ROM
ROM: Lineage 14.1 Last Official Build and January 2019 Gapps (from openGapps)
Xposed: NO
Any other root modifications: NO
Now, you might be wondering what is the need of this guide.
Firstly, there are no threads that point to the procedure for installing latest Magisk (i.e. 18 and 18.1) for our devices.
I found it depressing taht we only had threads for Magisk 16 and 17.1 and none after that.
Secondly, the method i am going to show you, will work on all future versions of magisk. All very easily.
Thus this eliminates the need for multiple magisk version threads.
I would like to request you guys to report as and when a newer magisk version is released to report whether the method still works. So that we know this is still useful.
So lets start with the procedure:
1. A clean ROM is recommended without any modifications. Else all the effort would go waste if the CTS Test fails eventually.
So, backup your important stuff, format system, data, cache partitions in TWRP and clean flash your ROM of choice along with Gapps
2. Download Magisk from the Official Thread linked Here.
3. Download VerifiedBootsigner v8 from Here. This is designed by the Legendary Chainfire , the brains behind the legendary SuperSU.
4. I would recommed you to finish the setup of your device. i,e, ROM + Gapps first.
Then Reboot into recovery and flash Magisk zip downloaded from the link above in step 2.
5. After flashing Magisk, flash the VerifiedBootSigner v8 downloaded from the link above in step 3.
6. After successful flashing, reboot your Device and open Magisk Manager from the drawer. and Check your safetynet status.
7. You will get 2 green tics.
SUCCESS!
Special thanks to:
@topjohnwu
@Chainfire
Google and everyone else who did their bit.
Screenshots:
Magisk 18.1
Magisk 18
Reserved - just in case!!
Doesnt work on my ze500cl (z00d)
Thread is duplicate of https://forum.xda-developers.com/apps/magisk/magisk-versions-asus-zenfone-2-x86-t3897181
Related
Hi,
For several days I have been trying to install "Magisk" without success. I have seen plot of tuto but does not one seem to function.
So, is it possible or not please ?
thx !
Nevermind
I want to hide root access for apps. How make ?
Install latest firmware.
https://www.androidfilehost.com/?fid=673368273298969887
Last update of what application ?
Download and install latest firmware as shown in the link.
Then install Magisk.
Ok, but what is it ?
What is what?
the firmware !
Open Google search, type firmware and press enter.
And I should uninstall SuperSU before ?
No
I installed the update, and Magisk did not install.
Now, there is written down "Unlocked" during the boot. And I no longer have the fingerprint to unlock.
Even by doing a complete restore (boot,recovery,data,system) it does not disappear.
How to remove this update.
Did you install firmware 7.7.6 ?
That one did workout fine for me.
No problem at all.
You can always reinstall you're backup.
Yes,
As I said, I installed my backup, but the problem is still there.
My miui verson is 8.1.2.0
How to remove this firmware and back to last before ?
What firmware version did you install?
You could try another version of the FIRMWARE.
last thing to do is an factory reset. Be sure you make a backup first.
Well, it is working for me.
I have an unlocked bootloader as well with TWRP 3.1.0.1. I first installed a xiaomi.eu ROM (multi) with TWRP, then logged in. Then through TWRP installed Magisk 13.3. Logged in on the phone, installed the latest MagiskManager. Download the latest version of Universal SafetyNet Fix (V2, beta 5 test 7). Flash that through TWRP. Start the MagiskManager and choose which programs to hide (Google play services etc). In the settings of MagiskManager, disable Magisk Hide and then test whether it works or not.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MI 5 using Tapatalk
The firmware you gave me, 7.7.6
Even with this firmware Magisk does not install, error 1 boot...
I have v8.1.2.0 (6.0.1) TWRP 3.0.2.0
Try magisk version 13.1
same thing !
Now Magisk root is working for oreo....
Download Working TWRP from
https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/kernel-t3404970
Download Magisk Beta from
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Credits to the developers topjohnwu,eng.stk
Process to acquire Magisk Root....(Simple)
1.Flash TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27225)
2.boot in to TWRP(FastBOOT)
3.Install Magisk 14.3 (https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356)
4.(optional) Clear Cache...
5.Reboot..
Its will take time to boot please wait....
Now you can verify whether root is achieved ot not by searching for an app installed in your phone called Magisk Manager
Click on the Thanks button:good: if you like this thread
ScreenShots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you link me to a Stock Recovery of OnePlus 3 (for Oxygen OS 5.0) as well?
Tried the method on my OnePlus 3T OOS 5.0, but the phone/calling app wont show up when receiving or making a call.
Found out it was because of the magisk module "OOS Call Recording Enabler", works fine now!
You can use TWRP blu spark by eng stk v.8.54.
Yeah, you have to use the Blu Spark TWRP, and SuperSu SR5 2.82 Flash TWRP from Desktop,then flash SuperSu from TWRP and VICTORY!!! I haven't used Majisk but once or twice, IMO they muck up the superuser process. But,hey, if the masses want options,give'em options!!!!
Reflash full rom
abobobilly said:
Can you link me to a Stock Recovery of OnePlus 3 (for Oxygen OS 5.0) as well?
Click to expand...
Click to collapse
Just flash the Full rom and reboot the system without flashing magisk you will get the stock recovery...
seperate recovery images dosent work perfectly
StakMak99 said:
Yeah, you have to use the Blu Spark TWRP, and SuperSu SR5 2.82 Flash TWRP from Desktop,then flash SuperSu from TWRP and VICTORY!!! I haven't used Majisk but once or twice, IMO they muck up the superuser process. But,hey, if the masses want options,give'em options!!!!
Click to expand...
Click to collapse
Magisk works perfectly without a pc...
if you need to bypass safetynet the only option is to use magisk as SUhide dosent work .......
Magisk 14.3 works and performs better than SuperSu.....
Magisk (14.5) installed fine and root works, but I cannot install any modules through magisk manager. It either fails or the install finishes, but the actual module does not work. I flashed one of those modules through TWRP instead and it works that way. Does anyone have an idea what this might be about, or has experienced the same thing?
Hi, I have a problem when running the magisk manager application, it says setup failed after the "require additional setup" does anyone know how I can fix it? Thanks
Install
- TWRP 3.2.1.0 Treble
- Use the "magisk-unistaller-20181208"
- Install the latest version, Magisk v18.0
- Wipe dalvik and cache
My terminal is a moto z play and I am using the rom of android 9.0 xperience-13.0.0-20181126-NIGHTLY-addison.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you got magisk on an internal or external SD card? What worked for me was to move it to internal storage.
SOLUTION
All you need to do is uninstall Magisk Manager and install it again from the following MagiskManager-v7.1.1.apk.
MOD: Edit Links Removed
Lukss203 said:
All you need to do is uninstall Magisk Manager and install it again from the following MagiskManager-v7.1.1.apk.
MOD: Edit Links Removed
Click to expand...
Click to collapse
Or, instead of downloading and installing a possibly dodgy apk, download straight from the source instead:
https://github.com/topjohnwu/Magisk/releases
Didgeridoohan said:
Or, instead of downloading and installing a possibly dodgy apk, download straight from the source instead:
Click to expand...
Click to collapse
I've tried installing straight from the source github and I still get the exact same problem as OP on my Samsung S5 G900W8
In case anyone is reading this 1 month later, I had the same problem and had removed all remnants of old MM installs. The fix for me was to remove MM, then go into recovery and before running the 19.1 installer, run the official latest uninstaller first and then (without rebooting) install 19.1. After that, I could hide without the "setup failed".
Turn On Internet
Just Turn On Internet
Magisk Downloads some kind of data
So just turn on data or wifi
It will work:fingers-crossed::fingers-crossed:
Someone already tried installing kernelSU in OP 10 Pro? And how to do?
GitHub - tiann/KernelSU: A Kernel based root solution for Android
A Kernel based root solution for Android. Contribute to tiann/KernelSU development by creating an account on GitHub.
github.com
I wanted to install it long time ago but I'm not sure what would happen to our devices, on telegram group of kernelsu I read that many devices ended up in bootloop after flashing the provided boot.img many of them because they flashed the wrong img and others for incompatibility, on kernelsu manager shows that our device is compatible and we can just flash the provided boot.img or flash through Franco kernel and ex kernel apps(if rooted) the anykernel zip from kernelsu GitHub but I didn't try it.
works fine
RokCruz said:
I wanted to install it long time ago but I'm not sure what would happen to our devices, on telegram group of kernelsu I read that many devices ended up in bootloop after flashing the provided boot.img many of them because they flashed the wrong img and others for incompatibility, on kernelsu manager shows that our device is compatible and we can just flash the provided boot.img or flash through Franco kernel and ex kernel apps(if rooted) the anykernel zip from kernelsu GitHub but I didn't try it.
Click to expand...
Click to collapse
I have installed sucessfully!
Unninstalled magisk and flashed the right zip version via twrp. Works great!
Magisk Delta still better for me, but its a good alternative for the future.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Machad3x said:
I have installed sucessfully!
Unninstalled magisk and flashed the right zip version via twrp. Works great!
Magisk Delta still better for me, but its a good alternative for the future.
Click to expand...
Click to collapse
Good to know, twrp can be just booted or we need to install it? Wich zip did you install?
RokCruz said:
Good to know, twrp can be just booted or we need to install it? Wich zip did you install?
Click to expand...
Click to collapse
Recovery need to be installed, cant just boot.
I've installed the zip below, but i'm using ColorOS 13.1 beta! Install the same version of your kernel!
AnyKernel3-android12-5.10.136_2022-11.zip
Has anyone built their own Kernel? I’m stuck and confused on the instructions.
Hello,
I currently have Magisk and the Magisk manager app both at versions 26.1 on a Redmi 9T (lime), I have configured denylist and pass the SafetyNet test so all good so far.
I wish to downgrade magisk to version 25.2. To do so I changed update channel to Custom and input this URL: https://raw.githubusercontent.com/t...26c0454a947cb4fa0a3bb1bc7d29e7caa/stable.json
Problem: When I go back to homescreen I can only install the 25.2 version of the magisk manager app, not the actual magisk. When I try to downgrade actual magisk by patching the boot.img file, it patches it with version 26.1.
So, is it safe to downgrade the magisk manager app to 25.2 now? Will it automatically also downgrade magisk? I am afraid of some wonkiness happening if I downgrade the app but magisk itself is still 26.1
Alternatively, would it be better to downgrade magisk but not the app? How would I do that?
I don't think you can downgrade Magisk app. But you can downgrade Magisk boot patch.
To downgrade, Just download the zip file of the version you want (Canary/stable etc..) and install it just like a Magisk module. Then after reboot, goto Magisk app and Install and Direct Install. Then after reboot, your Magisk boot is downgraded.
To be clearer I put pictures. I change update chanel to custom and input the raw json in first post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then I get in homescreen that the latest version is 25.2, with option to install. perfect!
when I click on app install, it even shows me the changelog of version 25.2.
the big problem is, when I click on Magisk install, I get changelog of most recent version 26.1, and when I go through and patch boot.img, it gives me as output the name of a file magisk_patched_26100_[x].img, further implying im getting the patched boot image of version 26.1.
What do I do? do I click on install app version 25.2? will it automatically downgrade magisk as well? I really dont wanna wipe data lol this is why im asking so many questions before clicking anywhere now
Just manually download zip file from GitHub and install as a Magisk module. That's the way I always do without any issues!
I did the installation of the version I want as a module and it worked fine, thanks for your advice.
it didnt downgrade magisk app tho. I used custom update channel as above to downgrade magisk app and now I have both the app manager and the actual magisk at the version I want, no data loss or anything. So the answer to the thread question is: downgrade magisk first then the app.
now I'm curious about figuring out how to encrypt my phone data and still be able to use twrp, because i had to wipe data and make twrp force phone not to encrypt in order to see my files in twrp. but thats a topic for another day