yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
If you could use the Canary debug build the Magisk log would be much more informative.

The log you did post suggests that there's a boot script in post-fs-daya.d named "Boot" that might be causing issues. And I'd suggest trying with a different module than Riru/EdXposed, since the sepolicy patches it uses can cause issues (there's an updated option in Magisk v20.2 they need to start using instead).

Try going to /data/adb/modules and delete anything you find there, then remove the boot script in /data/adb/post-fs-data.d as well and see if things start working. Try with a simple module from the Magisk Downloads.

You can check if things are working when installing by first going to /data/adb after installing a module, before rebooting. If there's a directory called modules_update that contains the new module, things are working as they should. After rebooting the module should have moved to /data/adb/modules and show up in the Manager Modules section.
[Magisk] Didgeridoohan:
[MENTION=7168712]lilian_ncy[/MENTION] [MENTION=4818370]Minshter[/MENTION] [MENTION=7133952]Zachster96[/MENTION]

Logs will be necessary... Install and boot logs (Magisk log and logcat).

https://didgeridoohan.com/magisk/MagiskHelp

Make sure to install the Canary Debug build when testing so that any logs produced are nice and verbose.
[Magisk] Wolfcity:
I'm using myVodafone for a long time and never had any issues with it. It's not hidden in MM and doesn't detect root on my device.

My MM is hidden but I remember the app working with unhidden MM too. Maybe your problem isn't magisk related or you got a new update of myVodafone. My version is 10.1.1.0.
[Magisk] feretio:
How did you manually get into TWRP? I can't seem to get into it and am starting to think my recovery was wiped or corrupted. Holding the power button won't power off so I've been trying to pull the battery and do the power button/volume down dance with no luck. It just keeps returning to the fastboot screen. With the SDK, "fastboot reboot recovery" doesn't seem to work though I'm not sure "recover" is a valid parameter.
[Magisk] ktmom:
On a rooted device you can use an "adb reboot recovery" command when fully booted.
[Magisk] feretio:
Thanks, but unfortunately, I can't get the phone to boot into anything but the bootloader. My V20 US996 has (or had) TWRP installed and was previously running Magisk 20.1. So far, I only can execute fastboot commands from the SDK.
[Magisk] martyfender:
I have the same issue on my older Android 6 Nextbook tablets, which started with the previous Canary release and continues. I reported to [MENTION=4470081]topjohnwu[/MENTION] in his github issue area and provided the logs that I could. You should install the latest Canary debug and save logs and post under this issue also. [MENTION=4470081]topjohnwu[/MENTION] asks that users be on Canary debug to report issues there.

https://github.com/topjohnwu/Magisk/issues/2182
[Magisk] kurtextrem:
That's probably the reason then, 20.1 works fine.
[Magisk] darkknight200:
Same with my stock Oreo rooted v20 us996 firmware.

Went straight to fastboot after updating magisk from 20.1 to 20.2.
[Magisk] Shantanu:
How to make older magisk detectable? 20.2 is just not making my ASUS ZenFone Max Pro M2 boot, gets stuck on ASUS logo (which comes before ROM logo animation) Everything was working fine on Magisk Manager 7.4.0 with the combination of Magisk 20.1. Want to go back to magisk 20.1 but the app says "Magisk is not installed"

Edit: Figured it out. Use Magisk Uninstaller, reboot, flash magisk 20.1, reboot, install magisk 7.4.0, done!
[Magisk] LATINORAMON:
20.2 not work. 20.1 Works perfect. Android 9 S8.

I dont know why is it stable. 20.2 brings Always Not installed Error
[Magisk] Furax31:
20.2 work perfectly

A5 2017 - Pie
[Magisk] Minshter:
For me—after the battery pull & putting it back in—I had to hold the power button and volume down button first, then once the LG logo appears I quickly release the power button and press it again (never releasing the volume down button).

Then the factory reset screen pops up. As long as you have TWRP installed, you answer yes to the next 2 questions, and then it takes you to TWRP.

As for fixing the fastboot, I restored the boot only from an image I had taken before the new Magisk, then installed the previous Magisk that I knew worked, cleaned cache and rebooted back to the now working phone.

Hope this helps.
[Magisk] Zeuszoos:
I can confirm that's how it's done to get into TWRP with the LG V20Z, except I just restored my whole backup. I wasn't sure if that "Yes" that says it would "Wipe User Data" would actually do it or not and since I had just backed up last night, I just restored everything. :)

Magisk v20.2 caused my phone to boot into FastBoot Mode as well. I guess it's not just me. :)

Does the developer monitor this thread? Or do I need to report it elsewhere?

First I did update Magisk Manager to v7.5.0 though. Does anyone know if it's okay to do just that?

Thanks!

Dave

Posted from my way cool LG V20 (H910) Nougat 7.0
[Magisk] feretio:
That's what I was trying though I might have been releasing and repressing the power button too slowly. I was finally able to get into TWRP by reflashing it though I had to use the newer 3.31 version as the original 3.0.2 version I had wouldn't unlock the internal storage. Unfortunately, I don't have a backup of the previous image anymore (old SD card failed and forgot to take a new one) so I'm probably going to have to reapply the last flash zip file I installed.

For reference, that can be found here:

https://xdaforums.com/v20/development/rom-us99610k-stock-rom-twrp-flashable-t3691784
[Magisk] rmedure:
BUG REPORT: ver 20.2 causes LG-G6 to be stuck in fastboot. Fortunately, I had an boot partition backup from October I was able to re-flash.

This is a pretty big fail. Any idea if this issue will be fixed in the next release??

Cheers!
[Magisk] TvBIFI:
at 20.2 the Radio/Sim is not working Magiskmanager 7.5 says Magisk not installed.

then flashed to be sure several times thru TWRP but no Luck

reverted back to 20.1 everything is fine.

Using a Samsung Galaxy S7

must be a New Years Bug
[Magisk] eKFreak:
I also have an s7 (flat) bootleggers rom. everything works for me.
[Magisk] :
I have the same issue with my LGV20, I'm just glad I had a backup or I would have been in a huge dilemma.
[Magisk] guest4711:
Without proper logs ir the device in quesrion on the hand it is hard to analyze and fix. Chances are better if people submit the required information...

So please try canary-debug and submit the logs if it fails to work as it should.
[Magisk] TheMattMercy:
My magisk installation was successful, and root works. However, modules seem broken. They install and enable but do not work.

I have tried:

FDE.ai

GravityBox (via EdXposed & Riru)

Pie Controls (via EdXposed & Riru)

Running latest Magisk (20.0.2) on my factory unlocked OnePlus 7 Pro running stable Android Q.

Please help, I'm beyond frustrated. I'll provide whatever logs are needed as long as someone tells me what to provide/how to get it ?
[Magisk] thor7777:
My V20 (US996 unlocked) also went into fastboot mode after upgrading to 20.2. Followed lilian_ncy steps to restore boot.img and reinstalled 20.1 via TWRP and now is booting fine.
[Magisk] Didgeridoohan:
Why is it that practically no-one that is posting about issues is posting logs? No logs usually means that there's no way of knowing if there's anything that needs fixing. It makes it really, really hard for [MENTION=4470081]topjohnwu[/MENTION] and those of us that try to help...

If you don't know how, take a look here:

https://didgeridoohan.com/magisk/MagiskHelp
[Magisk] feretio:
I was able to finally recover but now I have another issue with TWRP.

I know this is a bit off topic but for anyone with a US996, what version of TWRP are you using?

I ended up with TWRP v3.0.2 installed but it prompts me for a password to unlock the internal storage. I can flash the latest 3.3.1 which works fine except the phone will only boot to TWRP, even if I tell TWRP to boot system or if I boot from power off. There's 2 other versions in between on twrp.me for the US996, 3.3.0 & 3.2.3 which I'll try to see if either of those work.

Thanks!
[Magisk] martyfender:
For all of you above having this issue, I had this same issue on older versions of Magisk using the direct install method, on my Nextbook Ares 8A's, Android 6 tablets. To recover from it I had to reflash a stock boot.img then patch it from twrp with Magisk. From then on, flashing Magisk updates through twrp worked all of the time. Subsequent releases of Magisk using the direct install now work on both my 4 Android 6 devices and my Android 9 device.

I believe patching a stock boot.img in Magisk Manager and flashing it through fastboot should work for those of you who don't have twrp for your device, although I only did it a few times in the past when I had this issue on older builds.

However, this issue seems to have emerged now for some devices with newer builds.

I would install the Canary debug build and save logs and report it in the github issue area for [MENTION=4470081]topjohnwu[/MENTION]. The Canary debug build is a requirement to report it there, or topjohnwu will close the issue.

https://www.didgeridoohan.com/magisk/MagiskHelp
[Magisk] Crowbro:
In India, I'm using version 8.0.3.0 of Vodafone app which is the latest one available on playstore. It detects root and doesn't open. After using magisk hide it opens but shows an error when I enter my phone number, "We are facing some technical issues". I think it has something to do with root or custom rom. So I wanted to check by unrooting my phone completely.
[Magisk] Detonatte:
Magisk 20.2 crash my phone Samsung Galaxy Note 9 with Ambasadii Rom.
[Magisk] LATINORAMON:
Same Error with S8 Android 9
[Magisk] golf12:
Please see attached log HTC u11 running LeeDroid v3.5.3 r17 Android 8 attempting to update to latest Magisk 20.2, had to revert to 20.1 which works fine. Let me know of there any further information require.

PS downloaded zip a few times used app to get these and link in the original magisk thread, also attempted to install through TWRP vet 3.3.3.1 which stated it was installed but app still suggests to install.

- Device platform: arm64-v8a

- Copying image to cache

1566+0 records in

1566+0 records out

1603584 bytes transferred in 0.018 secs (89088000 bytes/sec)

1045+1 records in

1045+1 records out

1070668 bytes transferred in 0.014 secs (76476285 bytes/sec)

- Unpacking boot image

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

! Unsupported/Unknown image format

! Installation failed
[Magisk] rmedure:
ver 20.2 LG stuck Fastboot

Is there going to be anything in the logs? Install/patch boot partition is "successful" with no errors, reboot, then stuck at fastboot.
[Magisk] jcmm11:
To EVERYONE with a problem. If you don't supply these your chances of getting a fix are miniscule. See https://www.didgeridoohan.com/magisk/MagiskHelp

It's extensive and if you follow everything there you'll stand the best chance of getting a problem resolved.

No logs = (in most cases) the problem doesn't exist.
[Magisk] patuxco:
Latest Magisk Manager 7.5.0 installed succesfully this morning, now it's stuck at the logo screen.

I've got an S9, used the magisk for almost an year in this phone.

Anyone having the same issue? Thanks.
[Magisk] Wolfcity:
Read the post right above yours:

No-one here is a mind reader so please everyone having problems follow the tutorial [MENTION=4487388]jcmm11[/MENTION] has posted and provide logs. Dozens of " new version doesn't work for me" posts won't help.

This is not addressed to you only but to everyone having problems.

---------- Post added at 01:50 AM ---------- Previous post was at 01:47 AM ----------

The full uninstall process is also found here:

https://www.didgeridoohan.com/magisk/HomePage

https://www.didgeridoohan.com/magisk/MagiskUninstall

I'm from Germany so Vodafone may handle things different here.
[Magisk] Umgak:
I'm having the same problem everyone else is, I'm afraid.

I'm running a OnePlus 5T (A-only, non-system-as-root) on OxygenOS 9.0.9, installing via TWRP v3.3.1 (blu_spark version by eng.stk).

Phone worked fine on 20.1, but on 20.2, the device powers on and instantly reboots into RescueParty. I can tell that magisk is loading because my custom boot animation is present.

Attached logs:

recovery.log (TWRP installation log - should have no errors, but included for completeness)

magisk.log (Magisk log - appears to be old, included for completeness)

kmsg.log (included for completeness but I'm pretty sure this is kmsg for the recovery, not for the failed boot, and my device doesn't appear to keep last_kmsg. I was unable to get kmsg to run during the failed boot.)

In addition, I have a logcat file, but it is MUCH too large for XDA or even pastebin, so you will have to get it from mega.

EDIT: May have been a module issue - managed to get 20.2 installed & booted on 9.0.9 by dirty flashing ROM, flashing Magisk Uninstaller to get rid of modules, and reinstalling.

EDIT 2: I can confirm that my device IS working after flashing Magisk Uninstaller.
[Magisk] pannerch:
+1
[Magisk] J.Michael:
still: SECURE CHECK FAIL: vbmeta

Magisk Manager 7.5 used to patch AP.tar.md5

Patched Odin used to download to tablet

Still fails with "SECURE CHECK FAIL: vbmeta" on tablet, a few seconds later Odin declares "Fail", tablet reboots in spite of having unchecked Odin's "auto reboot" option.

When I enter download mode on the tablet, it says:

CURRENT BINARY: Samsung Official

OEM LOCK: OFF (U)

KG STATUS : CHECKING

QUALCOMM SECUREBOOT: ENABLE (CSB)

RP SWREV: S1, T1, R1, A1, P1

RP SWREV: K 1, S 1

SECURE DOWNLOAD : ENABLE

DID : 00001ff15c2a

download mode !!

Could someone comment on that? After unlocking the bootloader, should it still say "QUALCOMM SECUREBOOT: ENABLE" and "SECURE DOWNLOAD : ENABLE"?
[Magisk] Phoenix007:
I've got another issue with my S9+ ...

I installed the latest update and manager and it removed ROOT and also TWRP!

Regards,

Phoenix007
[Magisk] TheMattMercy:
Thank you for the helpful link. I have attached the appropriate log, I believe.
[Magisk] fatappel:
LG V20 - h918 stock rooted Oreo. 20.2 direct install (recommended) seemed to successfully install but upon reboot stuck in fastboot mode. All previous versions worked seamlessly. I have ADB. How do I get the logs you need?
[Magisk] Soutrik01:
Build : PixelExperience_z2_plus 20191224-2158-OFFICIAL (Android 10)

Magisk : 20.2(20200)

Flash type : Clean - (from Arrow-9.0)

Banking apps like GooglePay is not working.

Please (anyone) suggest how to fix it.

Already did :

(1) Magisk hide : Checked- GooglePay , Play services, Android services library + uninstalled all active modules + reboot

**SafetyNet check : success.

(2) Unchecked : Permissions - sms, contacts, telephone, location in Play services

(3) NOT Allowed : Display over other apps for play services

(4) Force stop & Clear storage for Banking apps + reboot. But failed :(

** While reverting to previous build (20.1) it's showing - "magisk NOT installed"

Pls suggest how to fix it.

Thnx [MENTION=4487388]jcmm11[/MENTION] [MENTION=5237901]Wolfcity[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] AggelosGR:
Same thing at my htc 10.root removed and magisk appeared as non installed.twrp wasnt removed.

restored boot and recovery through twrp and everything is back to normal.

i will update when this issue is fixed.
[Magisk] mattWhisky:
Same problem here, but with LG G6 - H870 FulmicsROM Nougat, direct install, cant get into system, everytime fastboot, what can i do? Cant use phone right now.. ADB works, some logs too?

Theres more people with this issue.. https://xdaforums.com/lg-g6/help/fastboot-problem-updating-magisk-stock-t3888528
[Magisk] stathis95194:
Faced this with latest canary version. If I hide MM it shows that it needs update but version is the same. If I unhide everything is fine.
[Magisk] phelite2015:
same here...
[Magisk] andreacos92:
With latest Magisk Manager - 7.5.1 (266) - I have a strange issue: even if I keep the application in background in the recent apps, after a while Magisk Manager is closed.

I already disabled battery optimization for the app (even after the update yesterday), but it's the same. With previous versions I never had this issue :confused:
[Magisk] pannerch:
Same here too.I reflash the rom and install version 20.0.No issue.
[Magisk] heslo.rb26:
Flashed successfully on my HTC U12+

No errors, still have root and passes SafetyNet!
[Magisk] tremalnaik:
Same on LG G5 with stock Oreo ROM: to quickly solve the problem I had to reflash TWRP to the boot partition (no way to directly boot it or flash it to recovery partition), and from there flash the backup made by Magisk of the previous boot partition, found in /data/ folder.
[Magisk] HippoMan:
Installing to inactive OTA slot without updating Magisk?

I am using Magisk v20.1 on my OnePlus 7 Pro running 10.3.0.

It turns out that v20.2 is causing me problems which I haven't figured out yet, and so I want to stay at v20.1 for the moment.

I had to reflash my ROM, and normally, I would do so followed by an installation of the "TWRP A/B Retention Script" via Magisk, which I subsequently would follow with INSTALL->INSTALL->Install to inactive slot(After OTA). However, the "Install to inactive slot(After OTA)" procedure only appears under "UPDATE" now due to the fact that v20.2 is available, and there is no "INSTALL". Invoking this would also update Magisk to v20.2, which I don't want to do.

Is there any way for me to perform the "Install to inactive slot (After OTA)" procedure while still keeping my Magisk version at v20.1?

Thank you very much.

.​
[Magisk] mkdante381:
Magisk 20.2 stable have bug. After hiding magisk manager (repackaging Magisk manager) is installed Magisk Manager Canary version. Stable channel is ticked...Pls fix this.
[Magisk] da_reeseboy:
Same issue here - LG G6 H872 on stock 20G Oreo rom. Magisk 20.2 caused bootloops to fastboot.
[Magisk] Chicken 14:
Hello everybody, Happy New Year,

I think evertybody had problem's with the Magisk update. Like you, yesterday, I did the Magisk APK update. After that, my phone works with no problem. But this morning, I wake up with the proposition of Magisk ZIP update. I did it and at the restart, I was stucked in FASTBOOT MODE.

By chance, my recovery TWRP mode works. So, I tried to wipe cache/dalvik cache in a first time but no way to unlock the phone.

So, I know I keep always on my phone, the ZIP I flashed when I root my phone. I found a 19.1 Magisk ZIP version (original version when I rooted my phone).

I tried to install the 19.1 ZIP on the 20.2 version but I was always stuck in FASTBOOT MODE.

So, I go on internet to search more information and I see everybody have the same problems. To continue to solve the problems, I download the MAGISK UNINSTALLER 20.2 ZIP and I download the old 20.1 MAGISK ZIP.

In recovery mode, I have access to my memory. Thus, I copy the files on my phone and I flash the UNINSTALLER two times with a cache/dalvik clean each time.

And, I reflash the 19.1 MAGISK ZIP two time with the dalvik/cache clean (like the uninstaller) and I reboot system.

Actually my phone works (I loose anything and my root work, just open your root application for reactivate the right).

I hope this method work for you.

My Phone : LG V20 H990DS with a OREO STOCK ROOT system (kernel: mk2000, root : magisk, method : dirty santa)
[Magisk] guest4711:
Happy new year, too. I have no problem with this update on all (sammy) devices I've tried: S4 I9505 (jfltexx), S5 (klte), Tab 2, Maguro.
[Magisk] basant toppo:
asus zenfone 2 z00a stock firmware 6.0.1

method .. patch boot image(direct method not works)

seccussfully rooted...

but reboot problem within 30sec.

previous ver. was working fine..

now i am unable to revert pre version..

no solution found

so my phone is unrooted now..
[Magisk] pendgy:
Here is the ultimate solution for the problems of Magisk update from 20.1 to 20.2 (at least for LG phones I do believe). https://xdaforums.com/showpost.php?p=81378123&postcount=13 Don't panic! :)
[Magisk] LayneLucero801:
Same here!

Any help???
[Magisk] LayneLucero801:
​

Just re-installed ROM and kernel, rebooted without losing data or root
[Magisk] erOzeOz:
Hello,

I have a bank app that used to work with MagiskHide. Since the latest update of the app some days ago, it detects I'm rooted and FC when I try to open it, before redirecting me to a website notifying me that my phone is rooted. The app is Keytrade Bank.

This detection occurs on Magisk 20.2 using magisk manager 7.5.0 even if I successfully pass SafetyNet Check (both ctsProfile and basicIntegrity are true). I have a OnePlus 3, running android 9 (ROM is Lineage 16.0), and of course the app is selected in MagiskHide.

I have tried both Magisk Core Only Mode and uninstalling Magisk Manager, without success either.

I am attaching a logcat if that could be of any help.

Anyone could let me know what I can do to try to identify how the app detect rooting or if there is a "hide request" channel to the developer?

Thanks.
[Magisk] Tyakrish:
Randomize the package name
[Magisk] jcmm11:
Start here

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] fatappel:
Yes! Phone's back with no data loss. Follow these posts:

https://xdaforums.com/showpost.php?p=81378123&postcount=13

https://xdaforums.com/showpost.php?p=81379913&postcount=15
[Magisk] jcmm11:
I just installed the app and opened it successfully. Obviously I don't have an account, but I accepted conditions and went to the market link.

If it's flagging you as soon as you try to open the app make sure that:

You're on the latest version of Magisk

You've added the app to Magisk hide

You've hidden Magisk Manager itself.

You've cleared data/cache from the app before restarting it.

If it's not flagging you until you try to login with an account, I can't check that.
[Magisk] Edwardbleachy:
Pls, magisk is not working o

Installation error
[Magisk] erOzeOz:
Thanks, clearing data/cache was the issue and fixed it. It must have flagged the root somehow.
[Magisk] KRisXD:
Hi.

I have noticed that after clean install ROM (Android 10) then (if no Gapps included) gapps and magisk 20.2 Gcam (PMGC_7.0.009_Astrophotography_Version_V7.apk and GCamWhyRed_7.2_Q[IW].apk) front cam doesn't work night mode and also normal mode.

Then I figured out it may be Magisk problem because I have this Gcam working on same ROM but with 20.1 installled and then updated to 20.2

So what I tried:

Clean flash ROM + Magisk 20.2 + front cam Patch, Gcam doesn't work.

Then

Clean flash ROM + Magisk 20.1 + front cam Patch, Gcam is working.

And what is interresting:

Clean flash ROM + Magisk 20.1 + front cam Patch, Gcam is working. then update Magisk to 20.2 Gcam is still working.

Tried with ROM's Blaze, CleanDroid, DerpFest, DureX, EvolutionX, Havoc, Ion2.2b, PixelExperience, Potato, Rebelion, Superior.
[Magisk] warrencoakley:
Has anyone had issues with loosing Root when flashing kernals? Haven't had this issue since the new update.

Rooted with Magisk Canary 20.3, stock, Android 10

Flash custom Kernal.

Reboot,

Rooted lost (attached pictured)

Flash patched stock boot image from Magisk Canary 20.3

Reboot,

Stock Kernal back installed.

Reboot, custom Kernal back installed.

Root lost again.

So frustrating.
[Magisk] RedNas74:
Just installed android 10 on my xiaomi mi 9t. Now when I try to hide magisk manager under a new name, I get the following message: Upgrade to full Magisk Manager to finish the setup. Download and install?

Pressing ok does nothing and the app doesn't open. Reinstalling the masigk manager without hiding works. Unfortunalely I need this function to hide magisk from my banking app. Any Idea what to do next?
[Magisk] Badger50:
After you flash the custom kernel, then flash the magisk zip, then reboot. I just thought of it :cool:
[Magisk] warrencoakley:
Yes but should I be flashing the patched Magisk img or flash the zip module itself? I thought you cant flash the zip as TWRP hadn't been updated to do so. When I flash the the patched img it contains the stock boot img which will revert back to stock.