Hi there, I'm having difficulties flashing Magisk 10.2 on my OP3 from TWRP. This is the error that displays:
MTP Enabled
Installing zip file '/sdcard/Download/root things/Magisk-v10.2.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
******************************************
Magisk v10.2 Boot Image Patcher
******************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found boot image: /dev/block/sde18
- Unpacking boot image
- SuperSU patched boot detected!
- Adding auto patch script for SuperSU
! SU image mount failed. . .
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/root thing/Magisk-v10.2.zip'
Updating partition details. . .
. . . done
Click to expand...
Click to collapse
Any help would be much appreciated!
For the record, I just fully unrooted SuperSU and am trying to now flash Magisk 10.2.
SilverCorrosion said:
Hi there, I'm having difficulties flashing Magisk 10.2 on my OP3 from TWRP. This is the error that displays:
Any help would be much appreciated!
For the record, I just fully unrooted SuperSU and am trying to now flash Magisk 10.2.
Click to expand...
Click to collapse
Don't what ROM you are using, but try this script https://forum.xda-developers.com/showpost.php?p=63615067
then dirty-flash your ROM(possibly gapps if it is a custom ROM) (if it is a ROM with in-built root reflash the script) let it boot, reboot to recovery and try to flash newest Magisk 11.1
SilverCorrosion said:
Hi there, I'm having difficulties flashing Magisk 10.2 on my OP3 from TWRP. This is the error that displays:
Any help would be much appreciated!
For the record, I just fully unrooted SuperSU and am trying to now flash Magisk 10.2.
Click to expand...
Click to collapse
This is because you have to restore boot.img file after uninstall SuperSu. So...
1. Extract boot.img from the rom zip you are using and copy this file into internal memory
2. Uninstall SuperSu from settings and say NO when SuperSu ask you about restore Boot (if you say YES, you will have bootloop for sure).
3. Reboot recovery and install the file boot.img you extracted in boot partition (select boot partition)
3. Install Magisk (last version is V11.1 ) Now it will work properly. It will install Superuser Magisk too.
4. Reboot system and install Magisk Manager from Play Store
5. From Magisk settings, select "Magisk Hide"
6. Reboot system and check if you can pass SafetyNet from Magisk. It should work now.
Hi
I can't install Magisk
I tried to install using this thread https://forum.xda-developers.com/t/install-magisk-on-android-11-r-100-functional.4162761/
Tried to install Magisk on OctaviOS 1.3
If i do this
Code:
1-Reboot in twrp and flash MagiskR.zip
2-Reboot system and install MagiskR.APK
3-Open magisk and update MagiskR.APK
And go to Magisk I have only 3 options Magism home page, Magisk Logs, Magisk settings and nothing else. No plugins and ways to give root to applications.
Also it types.
Magisk
Latest: N/A
Installed: N/A
Status:N/A
A/B: Yes
SAR: Yes
Ramdisk: Yes
When I try to do all 5 steps
Code:
Twrp installation:
1-Reboot in twrp and flash MagiskR.zip
2-Reboot system and install MagiskR.APK
3-Open magisk and update MagiskR.APK
4-Reboot in twrp and Flash Magisk-e66b0bf3(20425).zip
5-Reboot system and ready
I get always in fastboot
Then I tried to install Magisk on Syberia Project and after flashing zip I don't have Magisk Manager installed on my phone. I installed apk from this thread and tried lastest apk from Github. Both didn't work
I also tried to update Magisk apk to Beta version and nothing changed.
Is your bootloader unlocked?
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.
The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)
sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
[deleted]
johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working
Hello! As written in the title, i updated my already rooted poco f3 to the latest miui 14.0.7 (european rom) and then proceded to flash magisk. I followed everything to a T (extract boot from payload, patch in magisk, check partitions) and flashed it in fastboot. The terminal said "flashed to boot_a succesfully" so i rebooted. After unlocking the phone though, just a few seconds later it starts reooting on its own and prompts me to the miui recovery. I tried flashing the patched boot image both to boot_a and boot_b after this error, but it keeps happening.
Any help? i just don't want to lose my data.
EDIT: Thankfully i made it. The error was caused by a magisk module, so in the adb shell just run magisk --remove-modules and the error should be solved. Info from https://topjohnwu.github.io/Magisk/...debugging,and automatically reboot the device.
Would it work again if i flashed the stock boot image?
Pillow fan said:
Would it work again if i flashed the stock boot image?
Click to expand...
Click to collapse
Yes, or you can reflash the ROM.zip (without data-format of course)
OrangeFox Recovery has a Magisk Module Manager built-in and lets you disable/remove individual Modules.
Otherwise, you can simply put an empty file called "disable" or "remove", into /data/adb/modules/your_module_here/
On the next boot, Magisk will take action accordingly.
Also, maybe this is easier for you, but you can simply use a TWRP / OrangeFox Backup of the boot-partition, to patch Magisk.
Then you can rename the Magisk-patched Boot.img back into "boot.emmc.win", put it into Backup folder and replace with original Boot backup file, and restore with TWRP/OF.
Doesn't require a PC.
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Rename magisk from apk to zip, and then flash the magisk zip from recovery
Saezrfff said:
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Click to expand...
Click to collapse
Hi,
Boot your F3 into fastboot mode and connect to a PC,
Download "Temporary Recovery" and unzip, run the "RUN ME Temporary TWRP A13-Orange Fox Recovery.bat" file and choose TWRP.
Once rebooted select: Advanced from within TWRP and tap "Flash current TWRP", copy over the included Magisk files into the internal memory (I use a OTG adaptor and USB Stick), install Magisk V26.1.apk, when in recovery you can install Magisk as a .apk format.
Included are the files i use when switching between roms, included are the latest, Magisk V26.1 and Magisk Delta, it also includes the latest versions of TRWP/OrangeFox recovery and other goodies,
I hope it helps
It's possible that the MIUI 14 update may have caused compatibility issues with your previous root method. You could try using a different root method or a different version of Magisk. Additionally, make sure you are following the correct steps for patching the boot.img file and installing it. If the issue persists, you may need to wait for an updated version of Magisk or seek assistance from the Magisk community.
you can try patching Boot.img instead of flashing Magisk.zip
you can do a OrangeFox/TWRP Backup of Boot-partition and patch the resulting "boot.emmc.win" file in Magisk App, because it's actually just a normal partition-image.
then flash the magisk-patched image file.
no pc required. just a custom recovery.
you can try the new Magisk v26.1, or Magisk Alpha (not affiliated with official Magisk).
i use Magisk v26.1 Official but I'm on AOSP