Magisk General Support / Discussion

[CapnShitzhu]

So through the process of hiding magisk through inapp settings, magisk crashed. And now I only see the Home screen of magisk app only. All the other tabs are gone. So I boot to recovery and reflash the magisk zip but still its the same. So I tried the Uninstaller and it fails too. I think the hiding process crashed before finishing so some stuff are messed and could not be Uninstaller. Anyway to fix this

Magisk. 21.4, Twrp 3.4.0, oneplus 5.

 

[Homeboy76]

Latest Canary Magisk Changelog and Release Notes:

Magisk (bf80b08b) (22003)...
PW

Disregard, human error.

 

[pndwal]

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

I'd forget using Magisk in recovery, at least till you've tried patching boot.img.

Try method I gave @zelitrex36 (after restoring unpatched recovery):
https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84614357

It worked for him; see post after yours. PW

 

[pndwal]

So through the process of hiding magisk through inapp settings, magisk crashed. And now I only see the Home screen of magisk app only. All the other tabs are gone. So I boot to recovery and reflash the magisk zip but still its the same. So I tried the Uninstaller and it fails too. I think the hiding process crashed before finishing so some stuff are messed and could not be Uninstaller. Anyway to fix this

Magisk. 21.4, Twrp 3.4.0, oneplus 5.

Yes, uninstalling Magisk won't fix this as uninstall can't see hidden app.

Just locate and uninstall BOTH hidden manager/app(s), and current manager/app (which are conflicting), then reinstall app for current Magisk root Installation. PW

 

[pndwal]

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

Restore a previously patched, or unpatched boot image for your ROM. PW

 

[pndwal]

just waw
Thank you so much for the spent to help me. It worked like a charm.
...
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.

Yeah; If you have any further problems, ensure you toggled on Google Pay in MagiskHide list and rebooted BEFORE clearing GPay's data. PW

 

[J.Michael]

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?

I think even if unrooted, you can install a terminal emulator and run "mount" from the command prompt. The line for "/system" will tell how it is mounted ("ro" vs. "rw").

 

[J.Michael]

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://xdaforums.com/t/magisk-general-support-discussion.3432382/post-84612929

PW

I haven't tried it, but I would have thought flashing recovery.img to the boot partition would just give you two recoveries installed. Not a great way to have the device, but I wouldn't expect boot failure.

 

[pndwal]

I haven't tried it, but I would have thought flashing recovery.img to the boot partition would just give you two recoveries installed. Not a great way to have the device, but I wouldn't expect boot failure.

Yeah, that crossed my mind too...but I don't know, and have never heard of this done in practice.

It could actually be useful, but I don't have an A/B device... PW

 

[zelitrex36]

Yeah; If you have any further problems, ensure you toggled on Google Pay in MagiskHide list and rebooted BEFORE clearing GPay's data. PW

Hi there, I still have some issues
But someone told me to never give up so I won't^^

My Gpay problem is still not resolved but I'll post that specific subject in the proper thread to avoid confusion and stick to magisk here.

I have one question and one issue :
Question : when I read "hide magisk" does that refer to :
1)

OR

2)

My issue is : My phone is now rooted and and can't connect to Teams anymore because it detects my phone as rooted. I don't know if it's Teams apk or "portail d'entreprise" which I also tried to hide as you can see on picture one.

Am I missing a module or did I make a mistake ?
Thx for you help. This is actually a bigger problem than my previous one lol (Gpay)

 

[ineedroot69]

Hi there, I still have some issues
But someone told me to never give up so I won't^^

My Gpay problem is still not resolved but I'll post that specific subject in the proper thread to avoid confusion and stick to magisk here.

I have one question and one issue :
Question : when I read "hide magisk" does that refer to :
1)
View attachment 5243611

OR

2)
View attachment 5243615

My issue is : My phone is now rooted and and can't connect to Teams anymore because it detects my phone as rooted. I don't know if it's Teams apk or "portail d'entreprise" which I also tried to hide as you can see on picture one.

Am I missing a module or did I make a mistake ?
Thx for you help. This is actually a bigger problem than my previous one lol (Gpay)

you can try using xprivacy lua

 

[bacardischmal]

.

 

[Marwan112004]

I want to get the boot.img file necessary for the magisk patching for the Xiaomi redmi note 6 pro

 

[pndwal]

Hi there, I still have some issues
But someone told me to never give up so I won't^^

My Gpay problem is still not resolved but I'll post that specific subject in the proper thread to avoid confusion and stick to magisk here.

I have one question and one issue :
Question : when I read "hide magisk" does that refer to :
1)
View attachment 5243611

OR

2)
View attachment 5243615

My issue is : My phone is now rooted and and can't connect to Teams anymore because it detects my phone as rooted. I don't know if it's Teams apk or "portail d'entreprise" which I also tried to hide as you can see on picture one.

Am I missing a module or did I make a mistake ?
Thx for you help. This is actually a bigger problem than my previous one lol (Gpay)

Good you don't have TWRP then!

Answer to 1st question: Without knowing where you were reading, I'm guessing neither. It's probably option Hide the Magisk app, --> Settings / App, last option.

Best tips on apps detecting root / custom mods:
https://www.didgeridoohan.com/magisk/MagiskHide#
-scroll down to Hiding Root from Apps. PW

 

[pndwal]

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

I haven't tried it, but I would have thought flashing recovery.img to the boot partition would just give you two recoveries installed. Not a great way to have the device, but I wouldn't expect boot failure.

Yeah, that crossed my mind too...but I don't know, and have never heard of this done in practice.

It could actually be useful, but I don't have an A/B device... PW

Actually, it now seems that this method may be reasonable practice for Legacy A/B devices as 'fastboot flash recovery twrp.img' will fail ('fastboot boot twrp.img' works however) as there is no recovery partition for these (although later A/B devices w/ 2SI & boot type ramdisk may include recovery _a / _b partitions), whereas flashing to boot_a / _b works! (until boot image is reflashed with a new OTA etc it seems).
https://android.stackexchange.com/q...rite-to-recovery-using-fastboot-on-a-b-device

Not sure if flashing this way will replace both ramdisk and kernel (don't know how new TWRP builds implement 'Install Recovery Ramdisk' option (which now utilizes Magiskboot to allow repacking boot images)) or the consequences, but only ramdisk (not kernel) should be replaced on these devices it seems. (Ramdisk in boot image is only used for recovery in these devices anyway; kernel is used for both system and recovery.)
https://topjohnwu.github.io/Magisk/boot.html

PW

 

[CSX321]

My issue is : My phone is now rooted and and can't connect to Teams anymore because it detects my phone as rooted. I don't know if it's Teams apk or "portail d'entreprise" which I also tried to hide as you can see on picture one.

FWIW, I've never had a problem running Teams on my rooted Pixel 3, even without ticking it in Magisk Hide. It's running right now, and working fine.

 

[HippoMan]

DELETED - I found a more appropriate and "on topic" thread in which to discuss my issue.

 

[Homeboy76]

Actually, it now seems that this method may be reasonable practice for Legacy A/B devices as 'fastboot flash recovery twrp.img' will fail ('fastboot boot twrp.img' works however) as there is no recovery partition for these (although later A/B devices w/ 2SI & boot type ramdisk may include recovery _a / _b partitions), whereas flashing to boot_a / _b works! (until boot image is reflashed with a new OTA etc it seems)...
PW

Thanks for the information, I am going to edit my post (fastboot flash boot lineage17.1...) based on this information.
If the dev replies to my post with a change to the instruction I will modify the instructions and post his reply.

 

[HippoMan]

Actually, it now seems that this method may be reasonable practice for Legacy A/B devices as 'fastboot flash recovery twrp.img' will fail ('fastboot boot twrp.img' works however) as there is no recovery partition for these (although later A/B devices w/ 2SI & boot type ramdisk may include recovery _a / _b partitions), whereas flashing to boot_a / _b works! (until boot image is reflashed with a new OTA etc it seems).
https://android.stackexchange.com/q...rite-to-recovery-using-fastboot-on-a-b-device
[ ... etc. ... ]
PW

On my legacy A/B device (OnePlus 7 Pro - GM-1917), I always do this to initially install TWRP:

1. boot phone into bootloader
2. connect phone to desktop via USB
3. (on the desktop machine) fastboot boot twrp-recovery.img
4. (in TWRP) Advanced->ADB Sideload
5. (in TWRP) swipe the "Swipe to Start Sideload" slider to the right
6. (on the desktop machine) adb sideload twrp-installer.zip
7. (in TWRP) reboot to recovery

I never had any problems with this TWRP installation method.

 

[djsolidsnake86]

hello, mi 9 lite and latest miui
i installed magisk 22 from zip (by renaming apk) and now my phone boot only in twrp
also installing 21.4 by zip file it boot to recovery
what do now?
also installing the uninstaller it boot to recovery