Cannot install Magisk v18.1 after installed SuperSU HTC Desire 10 Pro Dugl [Taiwan] - HTC Desire 10 Questions & Answers

Hi
First of all, I am NOT a developer - just an advanced user that once every year flashes a ROM!
I have read somewhere this is due to SupeSU that inserts/write in boot.img
I have no idea how to fix this.
Is there an app that can edit boot.img [save original first!] and I can try and manually modify file myself, with a Developer's help.
i.e. instructions for idiots please.
I do have Magisk Manager v7.1.1 (203) installed and running fine.
Thank you in advance.

Related

[SOLVED] Can I really switch from SuperSU ?

Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.

need help!! how to use magisk in xperia M5 E5603

Hello i'm new in the forum :fingers-crossed: i have an xperia m5 E5603 and i try to install magisk so i can use apps that i can't use with a custom ROM my device is already rooted with super su and twrp recovery is installed any help please
Hello and welcome to XDA.
There's a lot of information about how to install Magisk (and how to replace SuperSU with MagiskSU) in this forum already. If you look around you'll find it. Number one rule on XDA is to search before posting (I'm not kidding, look at the rules).
To start you off I can tell you that you need to first uninstall SuperSU. You can do that through the SuperSU app (full unroot, select to restore boot image if you have systemless root), or with the unSU script and then manually flash a stock boot image (you can do this in TWRP). After that you should be able to install Magisk by flashing the zip in TWRP. Since you're new, I'd recommend to stick to the stable v12 release for now.
If you encounter issues, here's a troubleshooting guide for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Hello and welcome to XDA.
There's a lot of information about how to install Magisk (and how to replace SuperSU with MagiskSU) in this forum already. If you look around you'll find it. Number one rule on XDA is to search before posting (I'm not kidding, look at the rules).
To start you off I can tell you that you need to first uninstall SuperSU. You can do that through the SuperSU app (full unroot, select to restore boot image if you have systemless root), or with the unSU script and then manually flash a stock boot image (you can do this in TWRP). After that you should be able to install Magisk by flashing the zip in TWRP. Since you're new, I'd recommend to stick to the stable v12 release for now.
If you encounter issues, here's a troubleshooting guide for you:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
thank you fo reply after removing super su and install magisk do i need to install super su again for my device to be rooted again ? and is there any recommended version of magisc for my xperia?
Limoneytoo said:
thank you fo reply after removing super su and install magisk do i need to install super su again for my device to be rooted again ? and is there any recommended version of magisc for my xperia?
Click to expand...
Click to collapse
Magisk comes with it's own root, MagiskSU, no need for SuperSU (and for what you seem to want it for, SuperSU isn't compatible). You should probably start by reading through the release thread (the whole thing, it's not that long).
Some Sony devices have issues installing Magisk. This is known... If Magisk v12 doesn't work, you could give the v13.0 beta a go and pay close attention to the info in the TWRP output when flashing. If you do decide to go for the beta, please read through the first post carefully and follow any directions to gather logs to troubleshoot issues.
If you've read through all the info available (I've given you a few good links) and are still having issues, search the support thread for your issue (pretty much everything has already been covered). If you still can't get it going, make sure you post all possible details about your issue and lots of logs (there's also a section about "Asking for help" in the troubleshooting guide I posted earlier).
Didgeridoohan said:
Magisk comes with it's own root, MagiskSU, no need for SuperSU (and for what you seem to want it for, SuperSU isn't compatible). You should probably start by reading through the release thread (the whole thing, it's not that long).
Some Sony devices have issues installing Magisk. This is known... If Magisk v12 doesn't work, you could give the v13.0 beta a go and pay close attention to the info in the TWRP output when flashing. If you do decide to go for the beta, please read through the first post carefully and follow any directions to gather logs to troubleshoot issues.
If you've read through all the info available (I've given you a few good links) and are still having issues, search the support thread for your issue (pretty much everything has already been covered). If you still can't get it going, make sure you post all possible details about your issue and lots of logs (there's also a section about "Asking for help" in the troubleshooting guide I posted earlier).
Click to expand...
Click to collapse
After lot of attemps i always got the same result a bootloop :/ thats happened before when i was trying to install the latest version of super then i release that i can only install an old version of super su but i dont know what version of magisk is recommended for my sony m5

[Question] Correct way to switch from SuperSU to Magisk

Hi everyone!
I flashed a ROM on my S7 EDGE and i selected SuperSU on the process instead of Magisk.
Now as i just subscribed to Netflix i want to be aple to use the app on my phone, but in the play store it says that's is not compatible cause they dont allow rooted uses to use it.
I saw some threads about this subject but i want to be very sure about what to do cause i really don't want to install a rom from the start.
The steps i could get from the threads are:
1) UnSu script to lost root
2) restore the unpatched boot image of the rom again (where exactly do i find it on the rom.zip?).
3) Flash magisk files .zip and the manager
Is there something i'm missing ?
Thanks in advance...

Edxposed installation error

Hi all,
FIrst of all, thanks a taking out time and responding to my questions, highly appreciate it. I have a new Rog phone 3 (Android 10) that I have successfully unlocked and rooted, with Magisk 21.1 installed (manager 8.0.3). I am trying to get edxposed framework up and running.
1. I tried installing Riru v 22.0. I rebooted twice as suggested in some forums.
2. I then tried installing edxposed (Both yahfa and ) 4563 when I install it says the following
! Requirement module 'Riru - Core' is not installed
! Installation failed.
This is driving my crazy because I have installed Riru. Can anyone help me out as to what I am doing wrong. I even tried downloading the files from GIthub tried to install from storage. Same error
adithyavr said:
Hi all,
FIrst of all, thanks a taking out time and responding to my questions, highly appreciate it. I have a new Rog phone 3 (Android 10) that I have successfully unlocked and rooted, with Magisk 21.1 installed (manager 8.0.3). I am trying to get edxposed framework up and running.
1. I tried installing Riru v 22.0. I rebooted twice as suggested in some forums.
2. I then tried installing edxposed (Both yahfa and ) 4563 when I install it says the following
! Requirement module 'Riru - Core' is not installed
! Installation failed.
This is driving my crazy because I have installed Riru. Can anyone help me out as to what I am doing wrong. I even tried downloading the files from GIthub tried to install from storage. Same error
Click to expand...
Click to collapse
Try using Riru v21.3 instead of v22.0. Modules using Riru (including EdXposed) need to be updated to support the new changes in v22.0
Thanks a lot! That worked. I missed this point in the release notes! Much appreciated
Exactly suffering the same problem in ed exposed but the solution posted by the respected moderated works ! Just downgrade riru core to version 21.3
Sent from my hero2lte using XDA Labs

Bank app Error Magisk 26.1

Hello, I hope you can help me with this.
Yesterday I updated to the latest version of the custom rom I'm using (EvolutionX) and I had to flash the zip file manually through recovery since it didn't install automatically.
After that, magisk stopped working correctly, the root of my banking applications is not hidden, as you can see in the images, I have everything hidden and activated correctly (I think), I would appreciate it if you help me with this since the same thing happened to me a long time ago , and not finding a solution I had to do a hard reset and install a new rom.
The bank app says: "this device does not meet the minimum security requirements for this application"
(Sorry for my english, helpe pls)
alesky0903 said:
Hello, I hope you can help me with this.
Yesterday I updated to the latest version of the custom rom I'm using (EvolutionX) and I had to flash the zip file manually through recovery since it didn't install automatically.
After that, magisk stopped working correctly, the root of my banking applications is not hidden, as you can see in the images, I have everything hidden and activated correctly (I think), I would appreciate it if you help me with this since the same thing happened to me a long time ago , and not finding a solution I had to do a hard reset and install a new rom.
The bank app says: "this device does not meet the minimum security requirements for this application"
(Sorry for my english, helpe pls)
Click to expand...
Click to collapse
Hi, try updating the safety net fix module and also try this
Try Universal SafetyNet Fix 2.4.0 Mod by Displex
remove that old module and install te new one 2.4.0 mod

Categories

Resources