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!
XDA:DevDB Information
Magisk Guide for Zenfone 2 (x86 Devices), App for all devices (see above for details)
Contributors
[email protected]
Version Information
Status: Stable
Created 2019-02-05
Last Updated 2019-02-05
Duplicate threads closed with links to this thread, as it was the original.
mattgyver said:
Duplicate threads closed with links to this thread, as it was the original.
Click to expand...
Click to collapse
Wouldn't this be placed in magisk..? Its technically not a app. Nor a port.
Also looks like spam post due to the 20times it was posted
Has anyone tried 19 on the ze551ml?
I couldnt get mine to boot.
Please, advise on magisk 19 - it's not working with this procedure
Candoris said:
Please, advise on magisk 19 - it's not working with this procedure
Click to expand...
Click to collapse
So any news? Did you successfully install it?
yannahzinha said:
So any news? Did you successfully install it?
Click to expand...
Click to collapse
Candoris said:
Please, advise on magisk 19 - it's not working with this procedure
Click to expand...
Click to collapse
jamesoh said:
Has anyone tried 19 on the ze551ml?
I couldnt get mine to boot.
Click to expand...
Click to collapse
Any update guys?
Did you follow the procedure?
Magisk -> Signature Verification zip ?
Does the boot.img get patched in twrp?
What error do you get?
Remember guys. If it boot loops, just flash the signature verification zip again. It will work.
And please report the success with a screenshot guys. It helps everyone.
19.1 patched works well now, all credit to Tensai™ on Telegram.
Candoris said:
19.1 patched works well now, all credit to Tensai™ on Telegram.
Click to expand...
Click to collapse
Thanks for sharing here! Gonna test right now <3
Candoris said:
19.1 patched works well now, all credit to Tensai™ on Telegram.
Click to expand...
Click to collapse
So, The method in this thread doesn't work? You tried this method? (Magisk Zip + Sig Verification Zip).
Please clarify here. If this method does not work, i'll get this thread locked.
yannahzinha said:
Thanks for sharing here! Gonna test right now <3
Click to expand...
Click to collapse
Hey,
You tried the method in the OP? Please revert.
[email protected] said:
So, The method in this thread doesn't work? You tried this method? (Magisk Zip + Sig Verification Zip).
Please clarify here. If this method does not work, i'll get this thread locked.
Hey,
You tried the method in the OP? Please revert.
Click to expand...
Click to collapse
I have tried the method indicated in this thread, it works for 18* versions of magisk, but didn't work for 19 (bootloops, unstable). I haven't tried it with 19.1, since I got a working patched 19.1, which I shared here. If you wish to lock the thread, you should indicate it is valid for up to ver 18. I am not sure how they got 19.1 to work with some kind of patch.
Candoris said:
I have tried the method indicated in this thread, it works for 18* versions of magisk, but didn't work for 19 (bootloops, unstable). I haven't tried it with 19.1, since I got a working patched 19.1, which I shared here. If you wish to lock the thread, you should indicate it is valid for up to ver 18. I am not sure how they got 19.1 to work with some kind of patch.
Click to expand...
Click to collapse
A person in the Zenfone 2 forums claimed that this method works. He flashed the verification zip and said it works. (And it should work)
Our bootloader needs a signed boot image to run. The Magisk zip does not sign the boot.img after patching on our devices.
The VerifiedBootSigner.zip basically signs the boot.img, so that the bootloader accepts it and does not bootloop. The Magisk post by the dev has this in his FAQ.
I wrote this up, so that users do not have to wait for someone to issue a patched zip (which does this exact same thing).
I tried flashing 19.1 on a device that my friend owns, and it worked. However i do not understand why some people here claim that this fails. Hence i came here to ask.
I still own this device, but i forgot to carry it on my trip. I'll be home next month and cant post screenshots till then. I wish somebody would step up and post screenshots using this method.
[email protected] said:
A person in the Zenfone 2 forums claimed that this method works. He flashed the verification zip and said it works. (And it should work)
Our bootloader needs a signed boot image to run. The Magisk zip does not sign the boot.img after patching on our devices.
The VerifiedBootSigner.zip basically signs the boot.img, so that the bootloader accepts it and does not bootloop. The Magisk post by the dev has this in his FAQ.
I wrote this up, so that users do not have to wait for someone to issue a patched zip (which does this exact same thing).
I tried flashing 19.1 on a device that my friend owns, and it worked. However i do not understand why some people here claim that this fails. Hence i came here to ask.
I still own this device, but i forgot to carry it on my trip. I'll be home next month and cant post screenshots till then. I wish somebody would step up and post screenshots using this method.
Click to expand...
Click to collapse
Look, it is exactly like I said: with your method 19.00 didn't work stably, basically you flash it, it works until your next reboot at which point it bootloops or some such, you try to install a module, it loops on you. This is for 19. 19.10 I got already patched and it works no probs at all. It's possible that the issue only affects 19 and not 19.10 which might work just fine with your method. I'm not trying to discredit your method in any way just saying exactly when and in which way I couldn't get magisk to work following your boot sign procedure. I am not qualified enough to look at the code an tell if the issue is with your method or with the magisk itself so I provided people with what worked for me from the moment it started working. No hard feelings.
Candoris said:
Look, it is exactly like I said: with your method 19.00 didn't work stably, basically you flash it, it works until your next reboot at which point it bootloops or some such, you try to install a module, it loops on you. This is for 19. 19.10 I got already patched and it works no probs at all. It's possible that the issue only affects 19 and not 19.10 which might work just fine with your method. I'm not trying to discredit your method in any way just saying exactly when and in which way I couldn't get magisk to work following your boot sign procedure. I am not qualified enough to look at the code an tell if the issue is with your method or with the magisk itself so I provided people with what worked for me from the moment it started working. No hard feelings.
Click to expand...
Click to collapse
Hey,
No hard feelings here too mate.
Thanks for the Heads-up!
magisk 20.1 stable + verified boot signer v8 works
Goodmorning everyone,
I own a zenfone 2 ZE551ML (android 6.0). After installing magisk manager 7.5.1, I downloaded the magisk 20.3 zip file as indicated by the app. I went to TWRP and launched the installation which ended successfully. Restarted the smartphone, it always returned to the TWRP screen, I have not found any way to start the operating system. Then I proceeded to install the VerifiedBootsigner v8 zip always from TRWP.
The initial configuration of the phone is restarted, only that it restarts after about 1 minute. After many reboots I managed to finish the initial configuration and I see that magisk manager is installed (I managed to start it and I see that the installation of magisk was also successful).
Now, how can I end these annoying reboots that don't actually allow me to use the phone?
Thanks to those who will be able to help me
-------------------------------------------------------------------
Buongiorno a tutti,
possiedo uno zenfone 2 ZE551ML. Dopo aver installato magisk manager 7.5.1, ho scaricato il file zip di magisk 20.3 come indicato dall'app. Sono andato in TWRP e ho lanciato l'installazione che si è conclusa con successo. Riavviato lo smartphone, ritornava sempre nella schermata TWRP, non ho trovato alcun modo per far partire il sistema operativo. Allora ho provveduto ad installare lo zip di VerifiedBootsigner v8 sempre da TRWP.
E' ripartita la configurazione iniziale del telefono, solo che si riavvia dopo circa un 1 minuto. Dopo molti riavvii sono riuscito a finire la configurazione iniziale e vedo che magisk manager è installato ( sono riuscito ad avviarla e vedo che anche l'installazione di magisk è andata a buon fine).
Ora, come posso far terminare questi riavvii fastidiosi che di fatto non mi permettono si utilizzare il telefono?
Grazie a chi saprà aiutarmi
jef_83 said:
Goodmorning everyone,
I own a zenfone 2 ZE551ML (android 6.0). After installing magisk manager 7.5.1, I downloaded the magisk 20.3 zip file as indicated by the app. I went to TWRP and launched the installation which ended successfully. Restarted the smartphone, it always returned to the TWRP screen, I have not found any way to start the operating system. Then I proceeded to install the VerifiedBootsigner v8 zip always from TRWP.
The initial configuration of the phone is restarted, only that it restarts after about 1 minute. After many reboots I managed to finish the initial configuration and I see that magisk manager is installed (I managed to start it and I see that the installation of magisk was also successful).
Now, how can I end these annoying reboots that don't actually allow me to use the phone?
Thanks to those who will be able to help me
Click to expand...
Click to collapse
You'd have to post logs for anyone to have any kind of chance of helping... The console-ramoops and/or lasg_kmsg would probably do the trick. Take a look here for details: https://didgeridoohan.com/magisk/MagiskHelp
I hope they are correct. i file sono sul drive . google . com
logcat.log
/file/d/1eWMrOgBy1oiE6Gvk8FYsOUJuOgiRyA7V/view?usp=sharing
pstore_console
/file/d/1nmrLyTzyb6_Auon-_OZgSAjtfV6zI4eP/view?usp=sharing
event.log
/file/d/1npdyrqH2UAysNhsjcLvQHuhrb6BKmWdj/view?usp=sharing
dmesg.log
/file/d/1GaulviR53dtfCMskiT6jmGklO8R9h9S4/view?usp=sharing
thanks
----
Spero siano corretti.
grazie
Update 4.04.:
I flashed the Stock ROM Version 4.21.40.352 to my phone.
Then unlocked my bootloader installed twrp recovery and did the procedure again:
Installed in twrp my magisk 20.4 and twice the VerifiedBootsigner v8 to be save and delete cache/davlik and restart.
Now no bootloops and i have now root from magisk!!!
Hello,
i have the same Problem with rebooting to twrp screen.
I have Resurection Remix with Android 7.1.2 and it was rooted.
Some Finace App would not work with rooted phones . I installed hideroot app and now i am not anymore rooted, bad because i didn't made a backup before.
I wanted to install Magisk.zip with the twrp recovery mode. I think it will not install because i am no root anymore? but it give no error out.
After installing and rebooting my phone it always return into twrp screen also install "signing boot image" but same result.
If i recover my backup from twrp (only boot) it will boot but no Magisk is installed (see in Magisk Manager).
So two question how i get root again and why i will not install?
edited:
i copied logfiles from twrp recovery to my sd card but i cannot read them, sorry
Best
Felix
I was able to get Magisk 20.3 working on a custom rom. I am using the Groovy Android thats running Android 7.1.2.
Here are my steps.
1. Download rom, and extract the 'boot.img'.
2. Download latest Magisk, then extract the Magisk APK file from the 'common' folder in the zip.
3. Download Gapps of your choice.
4. Download also the VerifiedBootsigner v8
5. Boot into TWRP recovery. I'm doing a clean install here, so go to Wipe--> Advanced wipe --> Select (Dalvik/ART Cache, System, Cache, Data,) and 'swipe to wipe'
6. The go to install, flash your rom, then flash Gapps.
7. Reboot, complete initial setup and go to file manager and find your extracted Magisk APK. Install it.
8. Make sure you're connected to internet, open the Magisk app, select install. Pop up will appear, select install.
9. Pop up with " Select Method" will appear, select "Select and Patch a File", then navigate to the boot.img file the you extracted in Step 1.
10. It will download Magisk files and patch your boot.img, when it finishes it will create a new file in the Download folder called magisk_patched.img
11. Boot into TWRP again, select 'Install', navigate to Download folder. Then press "install Image" button. Your magisk_patched.img will appear. Select it, then make sure you tick the "Boot" bullet in the "Select Partition to Flash Image" option. Swipe to confirm flash.
12. Then flash the VerifiedBootsigner v8.
13. Reboot system, Magisk works. Safetynet passed.
Related
Hi all ...
Today i show you how Root And TWRP Recovery for SM-J530F without any Problem
Part 1 : Root
ENABLE OEM UNLOCK and usb development
Note : all you data we will delete all Make sure take Backup !!
a) Download CF-Auto-Root from this link : https://download.chainfire.eu/1135/...y17lte-j5y17ltexx-smj530f.zip?retrieve_file=1
b) Flash with ODIN 3.10.7 in the AP slot.
c) Put your device in DOWNLOAD mode.
d) Load the CF-Auto-Root-j5y17lte-j5y17ltexx-smj530f.tar.md5 file below into the AP slot and hit start.
e) waiting finish, after finish you will see message ( you device is problem press Erase to fix ) press Erase and wait for Erase all data
F) after reboot,, again start in option " C "
g) Now after again Load the CF-Auto-Root file below into the AP slot and hit start. ,,, waiting finish and device is working again ,, you will see SuperUser
Congratulations !!
Now you can flash TWRP recovery form here :
https://forum.xda-developers.com/ga...twrp-samsung-j5-pro-twrp-3-1-10-v2-0-t3728233
Jest only do this :
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
this is all ,, Sory for bad English
Hi, can anyone confirm that this instructions works
SM-J530F/DS
Confirmed working! Thanks @Abdullah_a86 :good:
Twrp install errors
So, i flashed the twrp with odin after enabling 2 things in developer options .
Good, i entered the TWRP menu from phone and formated data , after that when i was trying to install the Magisk Root it always show errors like:
E: TOUCH_DRAG (or HOLD or REPEAT or RELEASE): and 2 numbers here like 575,1000 (example)
Please help me.
The phone is working but i think twrp is broken idk please help.
Thanks
Thanks!
who can, adapt to SM-J530FM recovery ???
(FM - version)
Does it work on the dual sim model?
Does it work on J530F/DS? The dual sim model, thanx in advance
Not working -- UNSTABLE !!!
Yesterday I've followed this root guide to root my J530F (NOT Pro-edition, NOT dual sim) and it worked great but for short time. The first root app I've installed is "Root Checker" to confirm that root is installed correctly - and it was. Then I was installing "Lucky Patcher" app and there was no prompt for root access from SuperSU. I went back to "RootChecker" it was telling me that my root is not available.
Then I rebooted my phone and I got famous Samsung "Black screen of death" - J5 logo appears and then blank, nothing on the screen. I got in Download mode without a problem, re-flashed my firmware (AP) and works fine.
Now it feels stupid, while I triggered KNOX to 0x1 and I don't have a root. I haven't tried this TWRP recovery because I'm afraid that it won't work and that I'll have to format my phone again and start from the beggining.
It is very important that you guys share your experience, so the other knows if this is working or not.
Anyone tried this custom TWRP Recovery???
in my Experience the best way to root j530f is trwrp+ refined kernel
wetito said:
in my Experience the best way to root j530f is trwrp+ refined kernel
Click to expand...
Click to collapse
Can you confirm that TWRP recovery from the first post is working?
Thanks!
Yes it works
wetito said:
Yes it works
Click to expand...
Click to collapse
I've just tried to install TWRP over stock firmware (not rooted) and I got bootloop. I can enter TWRP, but Android can't start. I guess I will wait for some time while stable custom recovery is released. I use this phone everyday, so I can't deal with all of these problems...
In my case root and recovery from this post is not working.
Hope there will be official solution soon.
Thanks!
Guys, someone please help, i have J5 PRO 2017 SM-J530G, i did a search on all XDA and did not found twrp for my model "G", found only for models Y and F, so i must ask if that version exists, and where i can find it ! Second question would be, if i can't find one especifically for G model, if i can use Y or F model of twrp ! thanks in advance for someone that can help !
NeleRS said:
I've just tried to install TWRP over stock firmware (not rooted) and I got bootloop. I can enter TWRP, but Android can't start. I guess I will wait for some time while stable custom recovery is released. I use this phone everyday, so I can't deal with all of these problems...
In my case root and recovery from this post is not working.
Hope there will be official solution soon.
Thanks!
Click to expand...
Click to collapse
Same problem in my case.
Hi. I have problems with the Google Assistant after rooting it. It stucks after telling it a command and suddenly crashes. Why does anything to do this with the root? Google Assistant and root haven't any relationship!!! I also have problems with an app called HelloTalk because it stucks in the chat screen too.
I had to flash my phone back to Stock ROM, because it gets stable again.
Thank you!
Enviado desde mi SM-J530F mediante Tapatalk
JaviLukiOficial said:
Hi. I have problems with the Google Assistant after rooting it. It stucks after telling it a command and suddenly crashes. Why does anything to do this with the root? Google Assistant and root haven't any relationship!!! I also have problems with an app called HelloTalk because it stucks in the chat screen too.
I had to flash my phone back to Stock ROM, because it gets stable again.
Thank you!
Enviado desde mi SM-J530F mediante Tapatalk
Click to expand...
Click to collapse
try root with magisk 14.0 and choose hide magisk
Abdullah_a86 said:
try root with magisk 14.0 and choose hide magisk
Click to expand...
Click to collapse
Where can I find the Magisk 14.0 patch for this phone model? I've never used this Root Manager.
Enviado desde mi SM-J530F mediante Tapatalk
JaviLukiOficial said:
Where can I find the Magisk 14.0 patch for this phone model? I've never used this Root Manager.
Enviado desde mi SM-J530F mediante Tapatalk
Click to expand...
Click to collapse
How to Install Magisk Latest Version 15.0 on Android [Non-Rooted Phones]
Download and install the Magisk v15 zip file from here:
http://magiskmanager.com/Magisk/Magisk-v15.0.zip
Place the zip file in your internal storage. Make sure that you remember the proper location of the zip file.
Reboot your phone into recovery ensure that you have a custom recovery such as TWRP is installed on your phone.
Now, click on the Install button in the TWRP recovery.
Download Magisk Manager
Navigate the Magisk-v15.zip on your internal storage or SD card.
Download Magisk Manager
Now, install the zip file on your device and wait till it is getting installed on your device.
Download Magisk Manager
You have successfully flashed the Magisk-v15.zip on your device.
Reboot your phone and see if it works on your device.
Download Magisk Manager
Download the magisk manager application from here: https://magiskmanager.com/Magisk/MagiskManager-v5.5.1.apk
Install the application by following the above procedure.
Open it and then you will see magisk is installed on your Android device.
Source :
https://magiskmanager.com/
Abdullah_a86 said:
How to Install Magisk Latest Version 15.0 on Android [Non-Rooted Phones]
Download and install the Magisk v15 zip file from here:
http://magiskmanager.com/Magisk/Magisk-v15.0.zip
Place the zip file in your internal storage. Make sure that you remember the proper location of the zip file.
Reboot your phone into recovery ensure that you have a custom recovery such as TWRP is installed on your phone.
Now, click on the Install button in the TWRP recovery.
Download Magisk Manager
Navigate the Magisk-v15.zip on your internal storage or SD card.
Download Magisk Manager
Now, install the zip file on your device and wait till it is getting installed on your device.
Download Magisk Manager
You have successfully flashed the Magisk-v15.zip on your device.
Reboot your phone and see if it works on your device.
Download Magisk Manager
Download the magisk manager application from here: https://magiskmanager.com/Magisk/MagiskManager-v5.5.1.apk
Install the application by following the above procedure.
Open it and then you will see magisk is installed on your Android device.
Source :
https://magiskmanager.com/
Click to expand...
Click to collapse
That web page is false. The same creator of the application has confirmed it in his thread
I think you should reference and post the links to the author's thread and not to a third-party page.
Sent from my Samsung Galaxy S8+ using XDA Labs
ASPViTo said:
Guys, someone please help, i have J5 PRO 2017 SM-J530G, i did a search on all XDA and did not found twrp for my model "G", found only for models Y and F, so i must ask if that version exists, and where i can find it ! Second question would be, if i can't find one especifically for G model, if i can use Y or F model of twrp ! thanks in advance for someone that can help !
Click to expand...
Click to collapse
Anyone can help?
--------------------------------> DISCLAIMER <------------------------------------
Premise: The root is a relatively risky operation.
Premise 2: It will not be possible to apply the updates OT(he)A(ir) that the phone manufacturer could release in the future
Premise 3: You MUST have installed TWRP. You can find the tutorial HOW TO INSTALL TWRP here
--------------------------------> HOW TO ROOT <------------------------------------
Open the browser from the phone and go here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Tap and download the stable version of Magisk Manager:
https://github.com/topjohnwu/Magisk/releases/download/manager-v6.1.0/MagiskManager-v6.1.0.apk or from the View attachment MagiskManager-v6.1.0.apk
Probably, on the phone screen, will appear a screen that tell you that the application is not secure and you'll have to tell him to enable the installation from that source (you'll have to do a couple of extra tap)
Now, on the phone you will have installed the Magisk Manager application, start it!
1) From the main screen of Magisk Manager, Tap on 'Install'
You will see 'Installation of Magisk, do you want to install Magisk-V...zip?
2) Tap on 'Install'
3) You will be asked to select the method you want to install it with, Tap on: Direct Install (Recommended)
4) It will appear a screen with a series of writings, at last you'll read: All Done!
5) Tap on REBOOT.
Congratulations you have performed correctly the root!
Now that you have root, maybe you are interested to have Google Camera Mod for do better shots! You can find the tutorial HERE
Does this apply for the Lenovo z5 as well?
447981117949 said:
Does this apply for the Lenovo z5 as well?
Click to expand...
Click to collapse
yes, but you need the twrp for z5
can I use these steps to unlock the Lenovo Z5s too?
Please help I lost all my personal data because of Unlock Bootloader and now i can't go to TWRP to install Root files So sad
GorranKurd said:
Please help I lost all my personal data because of Unlock Bootloader and now i can't go to TWRP to install Root files So sad
Click to expand...
Click to collapse
it is very well-known that rooting and/or unlocking the bootloader will wipe your phone. never do something without making a backup and please do not cry if you don't and lose data... that's part of the experience and your own stupidity .
try to reinstall the drivers in safe mode, or use adb manager to install the proper drivers. most of the times it does not work due to driver issues. maybe try it on a different computer (this one saved me lots of work)!
Broh ! I need to unlock my bootloader can you help me @Myheartisjoker.gmail.com
Esqueci minha senha de bloqueio z5 pro gt como desbloquear sem pc no ajude já fiz todos os tutorial mas não conseguo
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.
vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?
Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.
Hi there!
Sorry if this post is duplicated, I searched a lot but other people's solutions didn't work for me so I'm writing here.
I am using Samsung s8+ (sm-g955f) Exynos and wanted to install a different rom. Flashed to stock image-everything ok, installed TWRP from here:
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
=everything ok-booted to twrp and phone working perfectly.
I tried to install Magisk using the twrp method-latest installs in the mega thread. All seemed ok until i rebooted and my touchscreen stopped working.
I tried a lot of things to fix that, including but not limited to:
-reflashing magisk
-flashing stock rom again
-installing twrp without magisk
-tried to uninstall magisk but after stock flash it didnt find any modules to uninstall
-flashed stock boot.img.tar via odin
Nothing worked..As of now my phone is working-boots and loads OS and i can use otg mouse to click around but touch still isn't working. At this point I dont care about rooting the phone or the custom ROM, just want my touch screen working again..
Can anyone help?
nundu said:
I tried to install Magisk using the twrp method-latest installs in the mega thread.
Click to expand...
Click to collapse
What does this mean? What is "twrp method-latest installs in the mega thread"?
Didgeridoohan said:
What does this mean? What is "twrp method-latest installs in the mega thread"?
Click to expand...
Click to collapse
Sorry for the unclear explanation, i mean this: https://www.xda-developers.com/how-to-install-magisk/ , i downloaded a zip magisk file and flashed it via twrp.
Edit:after flashing magisk this way and reeboting the touch issue appeared.
I don't understand enough to be able to explain to you why, but with some ROMs you shouldn't flash Magisk right after flashing the ROM, you should reboot after installing the ROM, then go into twrp and flash Magisk. It has solved many issues for me before, I don't know if it applies to your case because I didn't see your method step by step, but is something to try.
Enviado de meu POCO F1 usando o Tapatalk
[email protected] said:
I don't understand enough to be able to explain to you why, but with some ROMs you shouldn't flash Magisk right after flashing the ROM, you should reboot after installing the ROM, then go into twrp and flash Magisk. It has solved many issues for me before, I don't know if it applies to your case because I didn't see your method step by step, but is something to try.
Enviado de meu POCO F1 usando o Tapatalk
Click to expand...
Click to collapse
Thank you for the response! I will try that but I installed Magisk before the custom rom. In the link I uploaded for TWRP instructions after successful TWRP instalation (part 2 completed with no problems) it gives the options for root-magisk or spersu (part 3) before rom installation so I did that.
I installed twrp on a fresh stock image,because I first wanted to do a clean factory reset on the device, before doing anyting else.
UPDATE
-installed stock rom
-installed TWRP
-installed magisk-Version 20.4, Magisk Manager-v 8.0.2-both green ticks, Root check=ROOT DETECTED
-installed Alexis ROM ( https://forum.xda-developers.com/ga...ce-development/alexis-rom-1-1-stable-t3753975 )
-Every function is working, phone is without bloatware, root is active, twrp is working. Everything BUT the stupid touchscreen... Is it possible something fried during the first install? Can I flash some touchscreen driver?
There are kernels with diferent touch drivers like D8G for instance, you'll find it on github.
Enviado de meu POCO F1 usando o Tapatalk
So i was minding my own business then i notice "Magisk Manager" have red dot notification on it's icon upon opening there's update for "Magisk Manager" app and "Magisk" itself... so i decided to first Install the "Magisk Manager" update and it went real smooth
but when i try to update Magisk itsaid "Magisk Manager is Dead. Love live the Magisk app" then it ask me for Method
"Select and Patch file" or "Direct Install" now at this point idk what to do. I have at least done 3x Magisk update installation already it never ask me this option also when i try download root checker on playstore itsaid im rooted i just want to update Magisk should i patch my stock boot.img again or what??
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
scarmage said:
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
Click to expand...
Click to collapse
clicking Direct Install doesn't do anything
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
dl200010 said:
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
Click to expand...
Click to collapse
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
ineedroot69 said:
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
Click to expand...
Click to collapse
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
dl200010 said:
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
Click to expand...
Click to collapse
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
Can you tell more? How did you extract the boot.img? Did you get it from the newest Android full OTA? DId it just straight up work after flashing the new boot.img? I'm asumming it was an unpatched one, right?
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.
ineedroot69 said:
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
Click to expand...
Click to collapse
Exactly the same experience as OP here.
I am at exactly this stage as well..oneplus 6T; rooted; stock image.
Not sure what to do next?
Thanks in anticipation.
~S.O
where is the "Download zip only" option ?
VangelisGi said:
where is the "Download zip only" option ?
Click to expand...
Click to collapse
There isn't one, because there is no separate zip anymore:
https://topjohnwu.github.io/Magisk/releases/22000.html
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Cygnust said:
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Click to expand...
Click to collapse
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Didgeridoohan said:
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Click to expand...
Click to collapse
Sorry, I skipped that part and when directly to the one saying you had to patch BOOT.IMG..
Many thanks
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
sprocketoctopus said:
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
Click to expand...
Click to collapse
Magisk still consists of two parts, Magisk app and Magisk internals, they're now just distributed together.
What your screenshot shows is that you've now updated the app, but not yet the internals...
Do not update simply as the update is Device bricking.
Magisk 22.0 update killed phone will only boot into fastboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the...
forum.xda-developers.com
I updated my magisk to version 22, and it looks ok, except for the bottom menu that disappeared, does anyone know where it went or is it a bug?