[HELP][KATE] Switching SuperSu to Magisk - Xiaomi Redmi Note 3 Questions & Answers

Just as the title said. I want to switch from supersu to magisk. Do i need to full unroot my device without flashing the stock boot.img?

AFAIK, magisk doesnt change the boot.img so i guess you have to full unroot via SuperSu then boot to twrp and flash Magisk
that is how i do it :good:

Related

Help with ashyx's TWRP + magisk

Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
You have to install the Magisk zip with TWRP then the Magisk manager apk.
@sp4r3h did you manage to get it working?
@ashyx can you give me some more details?
This is what I tried.
1. Restore stock firmware
2. Flash TWRP
3. Choose Read Only
4. Install zip - Magisk
5. Reboot
Then I get the verification failed error. But from my understanding.. if I use your dm-verify patch then I can't pass SafetyNet?
Which kind of negates the point of magisk?
Thanks for your time.
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
The manager was removed from the appstore. I'll try manually installing an APK.
napx said:
Follow instructions in first post and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
Click to expand...
Click to collapse
If I try patching the Magisk then I get the verification failed. If I patch the dm-verify then I can't pass SafetyNet.
Any ideas?
Magisk 12 can't pass SafetyNet anymore.
I also tried the beta Magisk 13.0 but I ran into the same error, so I can't even check if it can pass ...
Follow instructions in first post (in TWRP thread) and flash magisk.zip instead of supersu.
Install magisk manager after system reboot.
That works for me.
napx said:
Magisk 12 can't pass SafetyNet anymore.
Click to expand...
Click to collapse
Google Tweaked Some S**ta again
So What you Gotta do is -
1. Goto Magsisk Manager Settings
2. Enable Core Only and Magisk Hide and select the app (Also Disable the other two adblocker and BusyBox)
3. Reboot
Worked for me (Verified Snapchat and Then Undo all got root back)
But I did one my S4mini
I was just surfing and saw the post and Share it with you guys
Magisk
sp4r3h said:
Can anyone help me install ashyx's TWRP with magisk instead of super su? I've seen that it's been done on the TWRP thread.
I've installed TWRP, then flashed magisk but its not working, seems like I need to patch the boot.img but from my basic understanding that negates the point of magisk right?
Thanks in advance.
Click to expand...
Click to collapse
Well, I also like to try magisk because SU does not work proper. Is there a way to uninstall SU
without a wipe in TWRP ??
Hi. This might be interesting for ALL.. After me Tab hangs, I downloaded the latest OFFICIAL ROM from Samsung,
in my case "DBT-T825XXU1AQF3-20170713092645.zip"...
Extract and place AP, BL, CP and CSC. I decided not to use CSC-home.
Now, reboot.
Activate the developer-option and activate USB Debug.
Restart phone in download-mode (you will need 3 hands Menu, vol-down, power keys at the same time..
Again use odin. This time flash TWRP "twrp_3.1.0-1_sm-t825_AQD6.tar" as AP.
In ODIN, you might select the auto-reboot option because after flashing, you will only need to press
menu + vol-up keys.. Easier with two hands
Now proceed as already described in this thread (format data, wipe etc...) for rooting your tab, BUT (!!!!) do not use supersu. Use magisk "Magisk-v14.0.zip".
After flashing magisk, flash "no-verity-no-encrypt_ashyx.zip".
Now reboot and enjoy a rooted tab. This does not modify the knox counter, warranty is not void. I still use the original samsung firmware..
Lets see if a suitable custom ROM will show up soon. Would be nice if Lineage was available, for tab S3 and phone S8..
ashyx said:
raymondbernard
Need some help with magisk I downloaded the magisk v14.0 and it still says that it's not install just magisk manager is installed I'm trying to root a samsung sm-j320w8
---------- Post added at 03:06 PM ---------- Previous post was at 03:04 PM ----------
ashyx said:
You have to install the Magisk zip with TWRP then the Magisk manager apk.
Click to expand...
Click to collapse
Hey it's raymondbernard trying to get help from you about magisk manager app to root a Samsung sm-j320w8
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Installing Magisk

I am on latest los 14.1 with Lineage root. can i use Magisk module directly or unroot and then flash Magisk
Unroot, boot to system, reboot to recovery, flash Magisk.

Magisk Hide not works for SuperSU, need to change to MagiskSU?

Hi,
I am using autoroot Chainfire SuperSU and I have flashed Magisk v12 through Flashfire (from Chainfire). I want to use Magisk Hide, but I fail to pass SafetyNet check. I have tried many things and I think the problem is that I am using SuperSU instead of MagiskSU.
Is there any way to switch from SuperSU to MagiskSU without wipe/factory reset the phone? I have read myself you need to Uninstall SuperSU and flash Magisk again, but will it be a problem if I flash it again, because in my first attempt I allready flashed it.
25 USD donating for the solution!
You have to flash the SuperSU uninstaller zip. Then flash Magisk again with TWRP to patch your boot image so you can start using MagiskSU

How to install OTAs on rooted poco F1 ?

There will(hopefully) be a lot of otas coming to Poco F1 for bug fixing. So if we are rooted with Magisk we cannot install Otas directly as magisk modifies our stock boot image. And since poco doesn't have A/B partitions we cannot install OTA's and still keep Magisk. That brings us to Flashfire which can preserve root. Flashfire doesn't work on MIUI 9.6.14.0 (it doesn't work on mine) .So how do we install OTAs while preserving Magisk ? Is it possible or do we have to flash stock recovery and stock boot image and lose magisk ?
OTA update method according to topjohnwu:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Would be helpful if somebody can post a diy in the guide section on how to apply OTAs on Magisk rooted devices.
I would be very interested as well!!
Go to recovery.
Flash Magisk zip to restore old kernel backup.
Boot to system, you will not have root.
Update.
You still have TWRP, install Magisk again.
Profit.
I did flash my ota via stock recovery . You need flash stock recovery then go to system update after done go back to twrp and your magisk
abdohop said:
I did flash my ota via stock recovery . You need flash stock recovery then go to system update after done go back to twrp and your magisk
Click to expand...
Click to collapse
Could you please be more specific?
1. Flash stock recovery (so you loose Twrp)
2. Boot to System and make update
3. Flash twrp again and root again with Magisk?
Thanks
---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------
trax7 said:
Go to recovery.
Flash Magisk zip to restore old kernel backup.
Boot to system, you will not have root.
Update.
You still have TWRP, install Magisk again.
Profit.
Click to expand...
Click to collapse
You mean that flashing Magisk again will "undo" root?
DoudouJack said:
You mean that flashing Magisk again will "undo" root?
Click to expand...
Click to collapse
Yes.
trax7 said:
Yes.
Click to expand...
Click to collapse
Hi, just booted into TWRP and flashed Magisk zip file, I'm still rooted.
Do you mean then the uninstaller Magisk file? If so, it will remove packages as well and root will still be there... Could you please be more explicit? Thanks!
DoudouJack said:
Hi, just booted into TWRP and flashed Magisk zip file, I'm still rooted.
Do you mean then the uninstaller Magisk file? If so, it will remove packages as well and root will still be there... Could you please be more explicit? Thanks!
Click to expand...
Click to collapse
Magisk makes a backup of ur boot.img, which you need to use OTAs, to restore it, you can flash Magisk again to restore it. (that's how it should work)
trax7 said:
Magisk makes a backup of ur boot.img, which you need to use OTAs, to restore it, you can flash Magisk again to restore it. (that's how it should work)
Click to expand...
Click to collapse
In my case flashing Magisk again did not work. From Magisk Manager -> Uninstall either since it was "unable to download".
For those who would be in the same case, I did following steps to update:
- Download latest Magisk uninstaller (currently 17.3, I tested with 17.1 & 17.2)
- Boot into TWRP (I use an app for convenience), go to Install > flash the Magisk uninstaller zip and (optional) boot to system to make sure root is gone (with Root Checker e.g.)
- Power off device and boot into Fastboot, flash stock boot.img (you can find it in the ROM folder you used to install your ROM), boot to System and install OTA update via the update manager, then reboot
- At this point I was stuck in fastboot screen, I simply booted with TWRP (with decryption working) and it took care of installing the update, I then flashed Magisk from there.
DoudouJack said:
Could you please be more specific?
1. Flash stock recovery (so you loose Twrp)
2. Boot to System and make update
3. Flash twrp again and root again with Magisk?
Thanks
---------- Post added at 07:59 AM ---------- Previous post was at 07:57 AM ----------
You mean that flashing Magisk again will "undo" root?
Click to expand...
Click to collapse
Correct
Sandepp said:
There will(hopefully) be a lot of otas coming to Poco F1 for bug fixing. So if we are rooted with Magisk we cannot install Otas directly as magisk modifies our stock boot image. And since poco doesn't have A/B partitions we cannot install OTA's and still keep Magisk. That brings us to Flashfire which can preserve root. Flashfire doesn't work on MIUI 9.6.14.0 (it doesn't work on mine) .So how do we install OTAs while preserving Magisk ? Is it possible or do we have to flash stock recovery and stock boot image and lose magisk ?
OTA update method according to topjohnwu:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Would be helpful if somebody can post a diy in the guide section on how to apply OTAs on Magisk rooted devices.
Click to expand...
Click to collapse
Try this guide, https://forum.xda-developers.com/poco-f1/how-to/step-step-guide-flashing-ota-beta-t3878730
Darklouis said:
Try this guide, https://forum.xda-developers.com/poco-f1/how-to/step-step-guide-flashing-ota-beta-t3878730
Click to expand...
Click to collapse
Its ok I have already flashed several OTAs, custom roms and kernels on my pocophone.
Sandepp said:
Its ok I have already flashed several OTAs, custom roms and kernels on my pocophone.
Click to expand...
Click to collapse
Is that so? What custom recovery you used?
Darklouis said:
Is that so? What custom recovery you used?
Click to expand...
Click to collapse
Twrp with working decryption
Sandepp said:
Twrp with working decryption
Click to expand...
Click to collapse
About that recovery, data partition will not get encrypted when you flash OTA update?
Darklouis said:
About that recovery, data partition will not get encrypted when you flash OTA update?
Click to expand...
Click to collapse
It will but I am ok with encryption. If you don't want then flash disable force encryption from twrp after flahsing the ota or flash magisk which will disable force encryption.
Sandepp said:
It will but I am ok with encryption. If you don't want then flash disable force encryption from twrp after flahsing the ota or flash magisk which will disable force encryption.
Click to expand...
Click to collapse
Nice nice.. Thanks for the tip
Darklouis said:
Nice nice.. Thanks for the tip
Click to expand...
Click to collapse
You're welcome

Root 11.0.1 on BE2028

I was rooted using Magisk, but did the 11.0.1 update. The update caused the phone to reboot, and I lost root. I don't have the option to install to inactive slot in Magisk.
I figure I need to repatch the boot image, right? Where can I find the stock image?
LDL707 said:
I was rooted using Magisk, but did the 11.0.1 update. The update caused the phone to reboot, and I lost root. I don't have the option to install to inactive slot in Magisk.
I figure I need to repatch the boot image, right? Where can I find the stock image?
Click to expand...
Click to collapse
If you can use twrp or a custom recovery with adb support you can rename magisk.apk to magisk.zip and either install in twrp or through adb in recovery adb sideliad magisk.zip it will auto install to right slot and patch the boot img for you

Categories

Resources