Device is Mi A1 (tissot).
To install permanently twrp, i need to flash magisk. But i already have it installed.
I'm thinking if i could flash the twrp installer zip, and after this, update magisk (via twrp), that is crucial to keep twrp.
Related
Hi there,
I had Magisk and the Magisk manager on my S8 but after installing the latest firmware for my S8 I can not install the Magisk.zip anymore. SU and TWRP are working fine though. Does anyone knows how get magisk again on my Phone?
I found it here: https://forum.xda-developers.com/apps/magisk/guide-magisk-troubleshooting-t3641417
With SuperSU, most of the times you can simply use the full unroot option in the SuperSU app and let it restore your stock boot image, alternatively use the full unroot option and then flash the stock boot image before installing Magisk.
I am using Redmi 4a . Rooted with magisk and recovery is Twrp. It. I don't want to lose root access after update. tried FlashFire but it crashes when I open it .
Help appreciated !
I'm using miui10 (beta) developper Rom (miui_HM4AGlobal_8.10.25_d36c3e7df5_7.1.zip) and it is true that a big update (mean when it's the entire ROM) replaces twrp and crashes root.
You just have to install again twrp with fastboot method in order to flash SuperSu (the one i use) in order to retrieve root.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Hi, when used to use MIUI i installed pitchblack recovery and after the miui update it didn´t dissapeared so there is no need to always flash the recovery but the magisk fil you have to install again because the update flashs the stock boot img.
Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.
Hello,
Some times ago I was able to install magisk (v20) on my K20 Pro using TWRP. It worked well but an OTA update removed magisk. I didn't required to reinstall it until today.
However, I didn't succeed.
I'm on the stock EEA rom (V12.0.4.0.QFKEUXM), manually applied using mi flash tool.
I was able to install TWRP (twrp-3.5.0_9-0-raphael.img from the TWRP site). I add to fix the vbmeta to avoid TWRP been overwritten, but it worked.
Now I try to apply magisk.zip (latest, V22. Also tried with the older) using TWRP. It flash without error, but hte phone won't boot. It's stuck at the MI splash screen (just before the MIUI logo is expected to display).
What should I do ?
I also tried to patch the boot.img from magisk app. But not better.
What is surprising me, is that magisk is telling me my phone does not have a ramdisk boot partition. Since it worked already, I don't understand.
Thanks in advance for the help.
Hi, I want to install ArrowOS on my OnePlus 3T. Since I am a noob to CustomROMs I saw that when installing TWRP on OnePlus 3T there is an issue with dm-verity which can cause bootloop issue.
All of the install guides mention flashing SuperSU at time of TWRP installation to bypass dm-verity issue.
But since SuperSU project is now replaced with Magisk, should I flash SuperSU with my ROM installation then uninstall it and flash Magisk or should I flash Magisk instead of SuperSU from the get go, and will that cause any issues with dm-verity or bootloop.
Any help would be great. Thank you everyone.