yashsingh1/xdaforums huggingface dataset:
[Magisk] siealex:
Nexus 5x, stock 8.1, Magisk 19.0. Can't replace the stock bootanimation using Magisk modules (any available in repo, e. g. Pixel 2 bootanimation). If I soft-reboot, I see the custom bootanimation, but if I perform an ordinary reboot, I see the stock Nexus circles. WTF?
[Magisk] Hemuli:
I can confirm that Magisk 19.0 from beta channel booted to download mode on Samsung GT-I9506. After enough retries it booted properly.
[Magisk] siealex:
No such problems on Nexus 5x. Did you clean flash or update from 18.1?
[Magisk] Wolfcity:
After installing Magisk Manager 7.1 flashing magisk 19.0 via direct install takes me right to the TWRP recovery after the reboot, also after several attempts. Roll back to 18.1 boots to system again.

I don't think the log will help too much but here they are.
[Magisk] guest4711:
On a friends device I had the same problem. So I flashed magisk.zip in TWRP again, rebooted and all was fine.

(Because MagiskManager was hidden I had to uninstall the second (new installed) MagiskManager leaving the Manager intact.)
[Magisk] pyksy:
Just updated my OnePlus 6 to Magisk 19, now it won't boot (stays in boot anim forever). I'll investigate more tomorrow. What should I do to get it booting up again? Flash older Magisk from TWRP?
[Magisk] guest4711:
Try to power off and on again. It may start now. If this does not help try to flash actual magisk again from TWRP.
[Magisk] SalvH:
Updated my Oneplus 6T on Beta 6, everything seems to work fine so far.
[Magisk] jcmm11:
On the 5x the only way to replace the boot animation is to physically change the file in /system/media/ (if memory serves me correctly)

It's a timing issue - the system grabs the file before Magisk has a chance to mount it.
[Magisk] drezz2:
Is it possible to update the manager if it is "hidden" or is it "unhide" to update and then hide again?
[Magisk] pkgnex:
Working on Pixel 2XL Stock

Upgraded to 19.0 on my stock-ROM (March 2019 security) Pixel 2-XL with no issues using direct install option. I have TWRP and a custom kernel installed, and none of that was adversely affected.

I first downloaded and installed the new Magisk Manager.

Then I rebooted (manually).

Then I downloaded and installed Magisk 19.0.

Rebooted (automatically from install process).

Device came back up on first shot, no issues, loaded my scripts and everything.

Just wanted to report some good news... because I lot of people only post if they have a problem.
[Magisk] iankelly2001:
Thanks for the suggestion. Yes, managed to force the phone into recovery by holding down Vol Up + Home + Power buttons together for about 10 seconds. However, reflashing the kernel and then Magisk 19 ended up with the same result - the phone booted into Download mode again.
[Magisk] Artnig:
Did you do a direct install through magisk manager or did you flash through twrp? Thanks for your report
[Magisk] guest4711:
Normaly it works even if it is hidden.
[Magisk] SalvH:
Direct update install through Magisk Manager. I updated the manager first, rebooted and then updated magisk.
[Magisk] Pho3nX:
Bootloop with 19 on OP5 lastest OB. Each time i reboot, when Android starting > Power Off > Recovery Mode
[Magisk] scaldaferri:
What´s the procedure to install the old version? I´m on redmi 5 plus AEX 6.4 and lot´s of problems on this new version.
[Magisk] Wolfcity:
Flash magisk 18.1.zip with TWRP.
[Magisk] tovarichtch:
This did the trick. I was having bootloop / recovery mode on Lineage OS 14.1. When it did happen, I did the following :

Flash "boot.img" from zipped rom Lineage OS 14.1 via TWRP (I have 3.2.0.0)

Flash my custom kernel (I have ElementalX 8.14)

Flash Magisk 19.0

Reboot

Now everything is fine and working.
[Magisk] appman1234:
Just want to report that my Bank app is working properly in Magisk v19.0 now! (It can no longer detect my phone rooted)

Big thanks to Topjohnwu!!
[Magisk] noobhero:
quick question .. is there a way to backup the list of MagiskHide apps when flashing updates to system OS? uninstall and reflashing masgisk is always necessary during official updates. but each time the list of apps is lost. is there a way to back them all up and restoring them after the reflash ?
[Magisk] raptorskate:
I'm getting force close when opening my bank's app (Citibanamex). This has happened before and I just installed v19 and it's still closing.. already hide Magisk and uses Hide for the app.

Any solution?
[Magisk] simonpunk2013:
latest google play version and service will detect the su, so simply magiskhide them it should pass the safetynet again.
[Magisk] Mickyman:
Have you tried repackaging Magisk? This solved some of my "hiding" issues.
[Magisk] raptorskate:
What should I hide exactly?

---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------

Yep, I already did that before but same issue

---------- Post added at 08:13 AM ---------- Previous post was at 08:11 AM ----------

I forgot to mention that Safetypass is working, it has always worked
[Magisk] AndrzejDwo:
Hi guys! I had some problems with updating Magisk to the latest version. My phone is SM-G950F, HadesRom 5.0, updating from Magisk Stable 18.1. Usually I'm using direct install, but this time it didn't work because after updating MM to 7.1 it started to FC (but I still had my superuser rights). So I downladed all the latest stuff from Magisk github and boot to recovery. Flashed at first latest uninstaller (successfully) and after that I wasn't able to install v19 and v18.1 either. After reboot I have ended in download mode. So I forced the phone to boot to recovery and reflashed NX 23.5 kernel and that let me install Magisk v19. It's all good now.

All I have is recovery logs if someone consider it useful.
[Magisk] DragonFire1024:
Hello. I have a Galaxy Tab 3 Lite and an Amazon Fire 7 rooted with Magisk. I started to notice some things on the Tab 3: I can't delete or replace certain files or folders. I can't flash zips and when I do flash or add files to system and reboot, all of my changes or additions are gone. It's like they never existed. The same started to happen on my Amazon fire yesterday. BusyBox is installed, selinux is in permenant permissive and all my root apps have root access. TWRP Oon both devices. Anyone ever see this before?
[Magisk] AndrzejDwo:
Yes, I had the same problem using the canary built. Flashing v18.1 fixed it.
[Magisk] kari kimber:
safenet issue

N950f with alexndr 8.0 s5crk5.

Canary 18812 safenet true, beta 19000 safenet false.
[Magisk] iankelly2001:
Followed this method, but once again, on reboot, the phone goes into download mode. Samsung Galaxy S5/KLTE/SM-G900F, running Resurrection Remix v7.0.1 [klte] (Android Pie).
[Magisk] kotuamoalt:
@

Reboot into TWRP.

Reflash OS. (DO NOT WIPE)

Reboot.

Install 19.0 using TWRP.

Reboot.

Install MM 7.1.

I did this 10 minutes ago after encountering the download bootloop issue.

All good.:svetius:

---------- Post added at 10:00 AM ---------- Previous post was at 09:52 AM ----------

[/COLOR]

---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------

[/COLOR]

Try wiping the cache and data on the banking app.
[Magisk] iankelly2001:
Just tried this method as well. Returned to the download bootloop after the "Install 19.0 via TWRP" step, and rebooting.
[Magisk] Johnn78:
Why with new version of Magisk v19, it breaks my safety while with previous I passed it ?
[Magisk] DragonFire1024:
I rooted with 18.1 so can't be that.
[Magisk] kotuamoalt:
Did you reboot after flashing the OS? I did, and I had a magisk-less phone without losing any data or settings. I then rebooted into TWRP and installed ver. 19. I also have a Galaxy S5, so I don't know if that makes any difference.
[Magisk] AndrzejDwo:
Hmmm, that's interesting. I had exactly same problem and it was a solution for me on s8 SM-G950F. I couldn't even change hosts files because they were replaced with previous ones over and over again. Typing commands in termux gave me "system file read only" answer, even that host file was 0755. Only changes I made in /system in recovery file manager were saved, everything else was restored after reboot.

Try to enable "core only" mode in Magisk, and then check if changes were saved.
[Magisk] Yippee-ki-yay:
I can not find the debloat module in the application and the energized module seems not to work.
[Magisk] iankelly2001:
Yes, I rebooted after flashing the OS (Resurrection Remix v7.0.1 [klte]) and I too had a Magisk-less phone, all data and settings intact. But after rebooting to TWRP recovery (version 3.2.3.0) and attempting to install the Magisk v19.1 zip (which the dialogues whilst flashing claimed was successful), on rebooting, back to the download bootloop!
[Magisk] kotuamoalt:
Hmmmm... unfortunately, this is where my "help" ends, as I have a pretty minimal understanding of troubleshooting magisk.
[Magisk] insta.zedd:
Why does the manager says Magisk is up to date, eventhough there are new versions available. (The manager updated yesterday to the newest version).

If manual flash is required, do I need to uninstall v18.1 to install v19? Or is it okay to just durty flash?
[Magisk] AndrzejDwo:
What if you change the update channel to BETA?
[Magisk] iankelly2001:
Samsung Galaxy S5 SM-G900F (KLTE) only booting to Odin/download mode after Magisk v19.0 installation attempt

Here is the TWRP Recovery log, if it helps anyone work out what is going on.

https://paste.tinyw.in/index.php/view/72947184

And the Magisk installation log, from an attempt to install it from Magisk Manager 7.1.0:

https://paste.tinyw.in/index.php/view/12611650
[Magisk] siealex:
Does it use also /data/local? I used this path on older Android versions, but on 8.1 it doesn't seem to work.
[Magisk] kotuamoalt:
Weird. I have a G900V, and it's working. Did you previously have any version of magisk running? The only step that I did differently, was I ran the newest uninstaller, FIRST, then ended up with the boot loop. I then went into TWRP, and reflashed my OS, Rebooted, went back to TWRP and installed 19. Rebooted, then installed the manager. I really can't make much sense of your logs, but they look completely different than mine. I am also running TWRP ver. 3.2.1-0. If I recall correctly, the newer version doesn't work properly on an S5.
[Magisk] Didgeridoohan:
Not really. And since the Hide list only should be kept to the absolute minimum of apps that actually detect root, reapplying them to the list shouldn't take long.

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Have you tried turning it off and on again?

Seriously... Toggling MagiskHide off and on again if it stops working after an update almost always works.
[Magisk] plusminus_:
I had similar problems with Xposed and Manager 7.0.0, which led me to stick to 6.1.0.

But with the notification for Magisk 19.0/Manager 7.1.0 I decided to do a clean install of Magisk - reinstalling all my Magisk modules was a little annoying. I also gradually re-enabled my Xposed modules to see if there was one particular one causing problems.

For a while it looked like one old Xposed module that I was using was the culprit, so I uninstalled it - and Manager 7.1.0 was working fairly well (it closed a few times, but no "keeps stopping/has stopped" dialog) but my phone died overnight and after turning it back on Manager was unusable again! :( So I'm using 19.0 with Manager 6.1.0 now

I have attached a logcat filtered by ".magisk" produced when I tried to open Manager a few times. I noticed that there are no ClassLoader complaints when I use 6.1.0.

I wonder if there's a way to block Xposed for a particular app. This module perhaps?

Ah, my device: Sony Z5C, stock 7.1.1

edit: With the linked Xposed module Manager 7.1.0 is working perfectly fine. Thanks everyone :P
[Magisk] jcmm11:
Pretty sure that /data/local/ hasn't worked for a long time. 6? but I'm guessing, I don't remember what version it stopped working at.
[Magisk] hkjo:
How does KEEPVERITY work?

I thought dm-verity means that a boot partition modified by Magisk will be detected.
[Magisk] DragonFire1024:
That seems to have worked, but after I reboot a few times, magisk re-enables that option on its own.
[Magisk] AndrzejDwo:
Yes, but the changes you made remains, right? So I would use the "core only" mode only when you want to make changes on / partition.
[Magisk] iankelly2001:
Thanks for sharing your experiences.

Yes, I had Magisk v18.1 running. I didn't attempt to use the uninstaller, I was hoping to upgrade to v19.0 from Magisk Manager.

I tried all the above steps, to see if they would work.

(1) I downgraded TWRP from 3.2.3.0 to 3.2.1.0 successfully.

(2) I ran the newest uninstaller 20190228 and indeed, the phone went into the download bootloop.

(3) I forced the phone into TWRP recovery and installed my OS zip. The phone booted into system properly and Magisk Manager was gone.

(4) Rebooted into TWRP and installed Magisk v19.0 zip. TWRP dialogue confirmed it was successful.

(5) Rebooted, but back into the download bootloop, so no chance of getting back into the system to install the new Magisk Manager.

So, downgrading TWRP made no difference and following the above steps just got me back into download mode again.

Just for a laugh, I also tried installing the OS and Magisk v19.0 WITHOUt rebooting in between but that made no difference either. A real mystery.
[Magisk] kotuamoalt:
Yeah, that is super weird. This one is a real stumper...

Last idea. I'm sure you did not, but I need to ask. You didn't encrypt anything, right? And are you running any version of SuperSU?
[Magisk] AndrzejDwo:
That's a statement from over a year, but I think it's an answer for your question. But since Magisk V19 doesn't use magisk.img anymore maybe the problem is already solved. Didn't check yet.
[Magisk] kotuamoalt:
Last last thing. When you get to the installing 19 part, try installing it using "flashfire". Make sure you turn off the "everroot" feature.
[Magisk] etillxd:
i know that's a bit offtopic, but how I'm supposed to post my logs if i'm not able to post links to pastebin because i didn't made ten posts?
[Magisk] Oswald Boelcke:
Just omit the "https://".
[Magisk] martyfender:
A new version of Magisk Manager v7.1.1 has been released.
[Magisk] iankelly2001:
I've not used Flashfire before. Just installed the apk, it acquired Superuser rights in Magisk v18.1, then it promptly closes!
[Magisk] kotuamoalt:
The only thing I can suggest now is to check out the troubleshooting guide. Good luck!

If you ever get it figured out, I would be curious to know what you did.
[Magisk] OldFeller:
Magisk Not Installing Properly with TWRP on Fire HD 10 (5.3.6.4)

I've decided the best way to deal with all the issues I've encountered is to take my Fire HD 10 back to total stock and start the whole process over with a clean slate.
[Magisk] aharisi:
Seems like I get a bootloop after updating a module. Is there a way with the current version of Magisk v19 to remove /disable it from a TWRP terminal?
[Magisk] jcmm11:
Use the file manager in TWRP and go to /data/adb/modules/

To remove a module find the relevant folder and delete it

Edit: to disable rather than remove create a 0 byte file named "disable" in the root of the relevant module directory.
[Magisk] guest4711:
Use filemanager in TWRP and navigate to /data/adb/modules Then delete the folder of the module in question (or move it out if the way)...

Or use the old method to force magisk into "core-only" mode by touching /cache/.disable_magisk (note the trailing dot before disable)
[Magisk] spicediablo:
Hi, anybody knows why the latest magisk according to magisk manager is 18.1 and not 19?

Sent from sagit
[Magisk] kotuamoalt:
Change to beta update channel in settings.
[Magisk] Didgeridoohan:
From the release thread:
[Magisk] tech_head:
Toggle Magisk Hide off then on.

It worked for me.
[Magisk] curiousrom:
Re: Posting Logs w/ Less Than 10 posts - V19.0 Rebooting in Download Mode

You can post anything here until you reach 10 posts: https://xdaforums.com/general/off-topic

You can upload your logs to pastebin and instead of the direct link post: pastebin (dot) com / bV1Vxxxx for example.

BTW two other S5 LineageOS 16.0 have the Magisk v19.0 rebooting in Download mode issue & I quoted you here: S5 LineageOS 16.0 - Magisk V19.0 Beta - Reboots in Download Mode.

Maybe you coud post in that thread too?

***
[Magisk] insta.zedd:
Thank you my friend, switching to beta channel allowed me to have the OTA update. I somehow missed the option when i went through the settings. Thanks again.
[Magisk] L.F.B.:
So the latest manager broke some modules?

How to tell this? Now Im afraid to update and get bootloop like Ive got on my other device...

Edit.

Maybe, this is a maybe... yt vanced module got broke after last MM update.

So for precaussion Ive disabled and it seems no bootloop anymore.
[Magisk] DragonFire1024:
Yes they remain. For now. But I can't wipe or clean cache or it starts over again.
[Magisk] AndrzejDwo:
Did you try v19? I have just tested, and it looks like everything is fine. I have deleted one of my apps in /system/app and it's gone after reboot.
[Magisk] DragonFire1024:
I'll give it a shot in the next few hours and let you know.
[Magisk] Windowlicker001:
Hi, finally got round to friend with Windows machine and followed the instructions for Spflashtools to flash stock ROM back onto bricked Neocore E1. All seemed well but with positive feedback when flashing, but after that the tablet won't boot at all!

Q: do the Mediatek drivers allow SPFT to see the tablet? After downloading the drivers we couldn't find them but the SPFT ui saw the tablet and ran through flashing the stock ROM folder resulting in a green tick at the end....any ideas?
[Magisk] AndrzejDwo:
Make a nandroid backup before you update, just in case ;)

---------- Post added at 11:18 PM ---------- Previous post was at 10:51 PM ----------

I don't think it's right place to discuss about that. There are many ways to flash firmware with spft and a lot of potential issues and a lot of questions to answer to make it possible to help you. I suggest to Google as much as you can.

The main rule with SPFT is "If it's not working, try again! If it still doesn't work - try again... etc etc etc..."

I made my way through hell with reanimation of death mtk tablet...

Good luck!
[Magisk] Alan-B:
Hi,

Hello, Compile of HTC U12 rom with Super-R! Magisk 18.0 .zip installs well at the boot of the rom.

But Magisk 18.1 .zip does not install at all! :(

What can be the problem ?
[Magisk] XtraWater:
I'll wait till the update shows up in the stable version channel.

When I do a backup with twrp before the update I can go easily back if I end up in a boot loop. Right?
[Magisk] DragonFire1024:
A backup for these devices isn't important. I made the update and so far so good on my Galaxy Tab 3. For now, because of other things I'm doing, I decided to go back to SuperSU for now on my Fire 7. I'll keep an eye out for anymore anomalies.
[Magisk] kepetmania:
I'm using Lenovo a6000+ with Lineage OS 14.1. using magisk 18.1 it works fine, but after i install magisk 19.0 it suddenly doesn't want to boot into system, it just directly boot into recovery.
[Magisk] martyfender:
I am seeing many reports of users on Lineage OS having this issue, most of which are Samsung users.
[Magisk] 0ddj0b7:
Using the newest version of magisk on LOS 16 no bootloop but I'm on Motorola.

One problem I'm having which is a big one is magisk hide is not playing well with EDXposed.

With magisk hide on and Xposed framework active I'm failing safety net. I toggle magisk hide in settings on/off I can then pass safety net but it disables my Xposed framework. No Xposed modules installed.

Any one have a suggestion?
[Magisk] Jos_Hdez22:
As far as I know it's impossible to pass safety net with active Xposed
[Magisk] ZDeuce2:
Working fine here...
[Magisk] 0ddj0b7:
I just came here to post that I somehow managed to get everything working as I playing with logs. So weird how it happened.

https://imgur.com/a/h0vYERG
[Magisk] Oswald Boelcke:
@Jos_Hdez22 refered to Xposed. With Xposed you will never ever be able to pass the SafetyNet check.

Copied, I recognised that you are successfully using EdXposed but at no point in your video I could see if you pass the SafetyNet check.
[Magisk] Chris17funk:
can someone here help me please? I wanna root my phone and I don't know how to do it but Magisk seems like the best option right now.. I have the magisk manager apk installed and I have the zip file too. how do I go from there? my phone is a Samsung Galaxy J5 btw SM-J500H
[Magisk] Shariq3422:
Search it on Youtube Mate u will understand :)

Inorder to root ur phone u will need to Install TWRP nd then install zip via TWRP
[Magisk] 0ddj0b7:
Beginning of the video, front and center is magisk where it shows safety net pass, CT true and integrity true. Somehow I'm on the beta which was the problem.

I've always been and to pass safety net with Xposed for pie it comes that way by default
[Magisk] roles75:
Hello

Magisk19.0 works great on my SAMSUNG N960F with Android9! Thank you!

The problem I have with SAMSUNG-G900F with LineagOS16.0 Android9 (Build: lineag_klte-userdebug 9 PQ2A.190305.002 1966eb3313)

After installing Magisk19.0, the device boots only in download mode!

When I install Magisk18.1 the operating system is loaded. Please solve the problem!
[Magisk] kotuamoalt:
Right.

---------- Post added at 11:49 AM ---------- Previous post was at 11:45 AM ----------

Boot into TWRP after boot loop, and re-flash your OS, (No wiping) Then install 19, reboot, and install MM 7.1.
[Magisk] dhorihyka:
I cannot install xposed to my phone

cannot install xposed i do all procedure as u say

Here are logs of Magisk

Someone pls help my phone is J5 (2017) with Prometheus 9.0 PIE custom ROM

Sorry for horrible English

***LOGS***

- Copying zip to temp directory

- Installing magisk-riru-core-v17.1.zip

- Mounting /system, /vendor

Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip

creating: common/

inflating: common/post-fs-data.sh

inflating: config.sh

inflating: module.prop

- Device platform: arm

***********

Riru - Core

***********

******************************

Powered by Magisk (@topjohnwu)

******************************

- Creating /data/adb/magisk_merge.img with size 64M

CANNOT LINK EXECUTABLE "/system/bin/make_ext4fs": cannot locate symbol "using_default_flexbg" referenced by "/system/bin/make_ext4fs"...

Create /data/adb/magisk_merge.img with size 64M

Cannot mount image!

! /data/adb/magisk_merge.img mount failed...

! Installation failed
[Magisk] col94:
Hello! Does Magisk 19 work good on Xiaomi mi 5?
[Magisk] iankelly2001:
That didn't work for me. Reflashing the OS is fine, but rebooting after installing Magisk v19.0 Beta results in the download bootloop once again. The only way out to get a working system again is to restore the TWRP backup with the working Magisk v18.1 setup.
[Magisk] kotuamoalt:
Strange. That was the fix for my SM-G900V.

ps. I flashed the latest uninstall zip FIRST, which caused the bootloop, which was fixed with my prior description.
[Magisk] iankelly2001:
I tried that as well, but the Download bootloop was the end result. My phone is the Samsung Galaxy S5 SM-G900F, if that makes any difference.
[Magisk] chooks06:
I flashed latest uninstall, rebooted to TWRP, installed Magisk 19 zip. Got an ERROR 1 at the end.

I assumed it did not install and proceeded to install 18.1 zip. Got the same ERROR 1 at the end.

For the fun of it, reboot to system and it went straight to download mode. Forgot what the message in red was..

Returned to TWRP, restored backup.

Will make another try later when I have time.

Galaxy Note 3 N9005 on Pixel Experience (AOSP) 8.1.

---------- Post added at 12:35 PM ---------- Previous post was at 12:34 PM ----------

There's no Xposed for Pie... Up to Oreo 8.1 only.
[Magisk] kotuamoalt:
The only other suggestion I could make would be to try to updated through the manager.
[Magisk] kotuamoalt:
You are not describing the procedure that I used. After the uninstaller, I reflashed the OS, rebooted, THEN flashed v.19.