Magisk General Support / Discussion

[ineedroot69]

I'm using lineagOS 17.1 on the xperia xz2 compact

Is it necessary to re-flash the patched boot.img everytime lineage releases an update? Can i use to the same patched boot.img or do i need to extract boot.img from the new release, patch it, and then flash it?

they might do some changes on boot partition so if that happen and you used patched boot.img from previous OS version it might trigger bootloop so its better to extract and re-flash patched boot.img everytime lineage releases an update its not that time consuming anyway ...

 

[pndwal]

Hi everyone
After a lot of researches I'm closed to giving up installing Magisk. But before that, I'm here to see if someone can take some time to help me get what I'm missing.
So here is my situation and my understanding. Any help would be appreciated.

I bought a K20 pro (MI9T Pro) with unlocked bootloader (global ROM installed in place of the original chinese one) unrooted. So I can't pay with Gpay.
I found a way to make if work from :
https://xiaomi.eu/community/threads/tutorial-working-fix-for-safetynet-cts-profile-failed.59384/

From there I realised I need to install Magisk.
I then installed magisk.app but my Ramdisk is at NO

So plz tell me if all that's bellow, if no plz correct it :

• I need to install twrp
• I must find the recovery.img (I downloaded my official rom.zip but couldn't find the recovery.img, only the boot.img) ==> where can if find this recovery.img ? Plus, is that necessary ? I read on this thread that Magisk can work with the boot.img for Xiaomi phone
• I proceed like discribed on https://topjohnwu.github.io/Magisk/install.html
• I dl the module on xiaomi.eu's link above

I'm good.
My two problems are :
Do I need to install twrp and where to find this recovery.img (and any other mistakes that would have been pointed out^^)

Thx for you help

NEVER give up!

Can you confirm its actually Chinese variant (eg box info, not phone settings)... Appears some Indian K20 Pro variants physically lack NFC hardware, and have been sold unlocked w/ global ROMs etc.

NFC cannot apparently be made to work on these Indian models, but Chinese variant has NFC and reportedly also works with later (10.3.12.0 MIUI onward) global or custom XiaomiEU ROMs.
https://forum.xda-developers.com/t/solved-no-nfc-on-redmi-k20-pro.3945229/

You should NOT need the mods you found on XiaomiEU site.

You DON'T need TWRP.

You likely DON'T need recovery.img DESPITE (factory) ramdisk (in boot) = no (because it's Xiaomi):
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84603817

Once you have 10.3.12.0 MIUI global or later installed, and ADB Fastboot PC drivers working, also extract boot.img from ROM package, then simply install Magisk APK, open app, click install Magisk, then NEXT (in Options with Recovery Mode UNCHECKED), click Select and Patch a File, select your boot.img, click Let's Go, wait for All Done!, boot to fastboot and flash patchedboot.img (as for ramdisk= yes). Boot to system. If it bootloops (system is corrupted message), simply flash UNPATCHED boot.img. You will likely need Magisk in recovery in this case.

If system boots, check you have root in Magisk app. If not, you will also likely need to flash UNPATCHED boot.img and Install Magisk in recovery.

If you have root (most likely), turn on Magisk hide in settings, reboot and run Check SafetyNet in Magisk app. If you get basicIntegrity pass but ctsProfile fail, install Universal SafetyNet Fix (and Busybox for Android NDK) Magisk module, reboot and check SafetyNet again. If you have pass, open PlayStore settings and check PlayProtect says Device is Certified. If not, clear Google PlayStore data and Google Play Services cache, reboot and check again.

If you have PlayProtect certified device, Install Gpay (if necessary), open Magisk app and toggle on Google Pay in MagiskHide list, then reboot. Next, clear Data for Google Pay, then open it and try setting up card(s) / NFC payment.

Nb. It seems that there is no longer a need to install SQLite fix for Gpay.

All best! PW

 

[toot-217]

When I open Magisk on my LG G5 h850 (running Lineage 10) I get the prompt to "upgrade to the complete Magisk manager to complete the setup."

And when I choose to "download and install" and hit Ok I receive the toast message "please manually re-launch the app".

I wanted to open Magisk to update to v.22, what have i to do now?

 

[Philnicolls89]

Hi all, sorry for the OT question but I haven't been able to find the answer elsewhere. I am curious to know how i can find out if a phone has its /system as RW or RO? my current S10+ is RW and I like being able to just delete or edit things using mixplorer, especially when it comes to debloating system apps.
If I have access to the device in question (fully stock unrooted) is there a way to find out this information?

 

[Homeboy76]

But, you're installing the recovery to the boot partition.

Does it just work out because you install something else to the boot partition later?

Opps, I left out the word temporarily.
This is why I said temporarily install lineage 17.1...recovery...img to the boot partition on my Pixel XL (marlin): Install LineageOS on marlin
I do understand your point, because it makes sense to temporarily boot the recovery using fastboot boot lineage17.1...recovery...img.

 

[pndwal]

I'm using lineagOS 17.1 on the xperia xz2 compact

Is it necessary to re-flash the patched boot.img everytime lineage releases an update? Can i use to the same patched boot.img or do i need to extract boot.img from the new release, patch it, and then flash it?

Aside from above advice:

FWIW, if you simply want to avoid large download each time, this should work (if you have TWRP):

Unroot, flash OTA update, do TWRP backup of boot image, rename resulting boot.emmc.win file to boot.img and patch that. Flash to re-root.

Have a properly extracted boot.img on hand the first time you try this to recover device in case it doesn't work for you. PW

 

[pndwal]

Opps, I left out the word temporarily.
This is why I temporarily install lineage 17.1...img to the boot partition on my Pixel XL (marlin): Install LineageOS on marlin - Temporarily booting a custom recovery using fastboot

Mmm. And more seriously "fastboot flash boot lineage-17.1-20210303-recovery-marlin.img will install (flash) the recovery image to the boot partition on the device" (causing boot failure) as pointed out!
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84612929

PW

 

[Homeboy76]

Mmm. And more seriously "fastboot flash boot lineage-17.1-20210303-recovery-marlin.img will install (flash) the recovery image to the boot partition on the device" (causing boot failure) as pointed out!
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84612929

PW

Never had a boot failure following the instructions: Install LineageOS on marlin . I do understand your point and I <edited> my post.

 

[ineedroot69]

unless if you got fetish having bootloop then go on

Hi all, sorry for the OT question but I haven't been able to find the answer elsewhere. I am curious to know how i can find out if a phone has its /system as RW or RO? my current S10+ is RW and I like being able to just delete or edit things using mixplorer, especially when it comes to debloating system apps.
If I have access to the device in question (fully stock unrooted) is there a way to find out this information?

adb shell > cat /proc/mounts

or this android app https://play.google.com/store/apps/details?id=me.kuder.diskinfo

 

[pndwal]

Never had a boot failure following the instructions: Install LineageOS on marlin . I do understand your point and I <edited> my post.

Well, you're right... That guide prescribes 'fastboot flash boot <recovery_filename>. img' for temporary boot to recovery!

This makes no sense to me... are you sure you used that?

Official instructions properly prescribe 'fastboot boot path/to/twrp.img'
https://twrp.me/google/googlepixelxl.html

PW

 

[pndwal]

Latest Canary Magisk Changelog:

Magisk (45e0df9c) (22002)

• [App] Prevent multiple installation sessions running in parallel
• [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
• [General] Proper cgroup migration implementation
• [General] Prevent possible deadlock in logging code
• [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images

PW

 

[pndwal]

John Wu, 57m

Just published a new canary build with support for preserving and patching vbmeta structures in boot images. For those running into vbmeta bootloader issues, please go and try it out!

PW

 

[pndwal]

Just had an 'Oh No' moment after flashing this!

Re-booted fine, but not fully; clock widget wouldn't appear, apps wouldn't open, or open and hang... Thought I'd be reflashing last patched boot.img...

Decided to try second reboot:

Fully booted this time, and all seems fine now...

Root is intact, settings preserved, SafetyNet passing fully.

So be aware, you may have issues till second reboot. (Some are also getting 'unable to repack boot Image!' error.)

- Redmi Note 8T, Magisk in boot.img (despite ramdisk = no). PW

 

[pndwal]

Latest Canary Magisk Changelog and Release Notes:

Magisk (bf80b08b) (22003)

• Rebuild executables (fix boot image repacking issues)

Diffs to v22.0

• [App] Prevent multiple installation sessions running in parallel
• [App] Prevent OutOfMemory crashes when checking boot signature on PXA boot images
• [General] Proper cgroup migration implementation
• [General] Prevent possible deadlock in logging code
• [MagiskBoot] Preserve and patch AVB 2.0 structures/headers in boot images

PW

 

[pndwal]

John Wu, 14m

Clean rebuild the binaries and republished a new build. Non clean rebuilds causing corrupted binaries

Well, that was a quick fix John! PW

 

[pndwal]

Much better too!

Seamless flash, only one reboot needed.

Root intact, settings preserved, SafetyNet passing fully.

- Redmi Note 8T, Magisk in boot.img (despite ramdisk = no). PW

 

[Homeboy76]

Well, you're right... That guide prescribes 'fastboot flash boot <recovery_filename>. img' for temporary boot to recovery!

This makes no sense to me... are you sure you used that?

Official instructions properly prescribe 'fastboot boot path/to/twrp.img'
https://twrp.me/google/googlepixelxl.html

PW

Yes, decided to give fastboot boot ... a try the next time I update. Also posted a question to Dev about it.

 

[capitarider]

Hey there,

I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).

What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".

What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful

At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.

What I also tried next:
3) Tried to delete magisk modules via twrp --> not successful
4) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format

What can I do next?
Please help me

 

[boxemall]

Device: Xiaomi Mi9t /Redmi K20

Updated to "https://xiaomifirmwareupdater.com/firmware/davinci/weekly/21.1.28/"
&
Flashed "https://build.aospa.co/prerelease/davinci/pa-ruby-beta-1-davinci-20210202.zip"

After reboot all worked fine without any errors. I then went on and rebooted into TWRP (twrp-3.5.0_9-0-davinci.img)

I followed instructions and patched the above twrp-3.5.0_9-0-davinci.img which got successfully patched & renamed into the process.

following that, i flashed the patched recovery. system rebooted fine but without root, which was expected due to not pressing any key combos during boot.

also worth mentioning: once rebooted after flashing the patched recovery magisk app won't show magisk as installed. is that due to the "normal" boot? it will probably only show in the app when the key combo is executed properly during boot, right?

the issue here is that no matter what key combo is pressed the device ends up in fastboot mode. using fastboot commands, it won't reboot normally (fastboot reboot) and neither into recovery (fastboot reboot recovery).
reoobting without key combos won't reboot into system either.

the only thing that helps is re-flashing the unpatched twrp image over fastboot.

if there is anything i can help with, plz do tell and i'll do anything possible to me!

regards

 

[zelitrex36]

NEVER give up!

Can you confirm its actually Chinese variant (eg box info, not phone settings)... Appears some Indian K20 Pro variants physically lack NFC hardware, and have been sold unlocked w/ global ROMs etc.

NFC cannot apparently be made to work on these Indian models, but Chinese variant has NFC and reportedly also works with later (10.3.12.0 MIUI onward) global or custom XiaomiEU ROMs.
https://forum.xda-developers.com/t/solved-no-nfc-on-redmi-k20-pro.3945229/

You should NOT need the mods you found on XiaomiEU site.

You DON'T need TWRP.

You likely DON'T need recovery.img DESPITE (factory) ramdisk (in boot) = no (because it's Xiaomi):
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84603817

Once you have 10.3.12.0 MIUI global or later installed, and ADB Fastboot PC drivers working, also extract boot.img from ROM package, then simply install Magisk APK, open app, click install Magisk, then NEXT (in Options with Recovery Mode UNCHECKED), click Select and Patch a File, select your boot.img, click Let's Go, wait for All Done!, boot to fastboot and flash patchedboot.img (as for ramdisk= yes). Boot to system. If it bootloops (system is corrupted message), simply flash UNPATCHED boot.img. You will likely need Magisk in recovery in this case.

If system boots, check you have root in Magisk app. If not, you will also likely need to flash UNPATCHED boot.img and Install Magisk in recovery.

If you have root (most likely), turn on Magisk hide in settings, reboot and run Check SafetyNet in Magisk app. If you get basicIntegrity pass but ctsProfile fail, install Universal SafetyNet Fix (and Busybox for Android NDK) Magisk module, reboot and check SafetyNet again. If you have pass, open PlayStore settings and check PlayProtect says Device is Certified. If not, clear Google PlayStore data and Google Play Services cache, reboot and check again.

If you have PlayProtect certified device, Install Gpay (if necessary), open Magisk app and toggle on Google Pay in MagiskHide list, then reboot. Next, clear Data for Google Pay, then open it and try setting up card(s) / NFC payment.

Nb. It seems that there is no longer a need to install SQLite fix for Gpay.

All best! PW

just waw
Thank you so much for the spent to help me. It worked like a charm.
I had a hard time finding if my NFC was working but a phone tester app made its tests with a credit card to test the NFC. From there I could run everything you said.
Unfortunately, I have one last problem and I found it as already been described here :

[Discussion] Google Pay Magisk Discussion Thread

This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...

forum.xda-developers.com

The OP could solve it by wiping datas... That doesn't work for me. Any idea of what I could do ?
Anyway thanks again that was veeeeeery kind to help me like that and taking the time to describe step by step what to do

Edit : I realized that I did that not correctly :
If you have PlayProtect certified device, Install Gpay (if necessary), open Magisk app and toggle on Google Pay in MagiskHide list, then reboot. Next, clear Data for Google Pay, then open it and try setting up card(s) / NFC payment.
I did :
Got PlayProtect certified device, opened Gpay, clear Data for Google Pay (and play service and Playstore again). Only then I got what "open Magisk app and toggle on Google Pay in MagiskHide list, then reboot" means and actually did it.