yashsingh1/xdaforums huggingface dataset:
[Magisk] MPeti1:
Also it will always be compatible with Magisk

---------- Post added at 02:25 PM ---------- Previous post was at 02:17 PM ----------

Yesterday i flashed everything because something went really bad, long story short otp smartbank started to work in rooted phone (at this time i had supersu and magisk 12), and at the end of the day it got some more weird things, and then fastboot mode not worked properly for a time.

Anyways, it not matter anymore, i fully reinstalled my phone. Now i will make a full backup with flashfire, then update magisk and manager to 13.3 and 5.1.1, then i will upload the logs :D thanks for help

---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------

Will try, thanks :D
[Magisk] Lyveth:
Tried to flash magisk v13.3 but i got Updater process ended with error 1

and also above that Unable to repack boot image

already full unroot superSU, but should i flash stock ROM? Because I'm running on Resurrection remix

Can't upload recovery log because I'm a new member :(
[Magisk] bluegizmo83:
No need to reflash your entire ROM. You just need to remove SuperSU (which it looks like you already did) and flash an unmodified boot image, and then install Magisk. Just flash the boot image for your device (which you should be able to extract from the resurrection remix zip) by: fastboot flash boot boot.img, and then flash Magisk in recovery (TWRP or CWM).

I just had to do exactly this (on a different ROM though) when I changed from SuperSU to Magisk yesterday.
[Magisk] Lyveth:
Yes, i've tried to flash the boot image but via twrp. But, still giving me the same error tho. Do i need to do it by fastboot?
[Magisk] Dc0de:
Regarding my post #17802, the first logs I posted were for the Magisk 13.3 and Magisk Manager 5.11 on the op. On that version, Magisk manager crashed on opening app if the flight mode is On or Off. The 2nd lot of logs are from the Magisk & Magisk Manager Daily build from 5th August. With that version I can get into Magisk Manager 5.11 (build 5th August 2017) ONLY if the flight mode is on. Once in the app I can turn flight mode off (to enable internet access) but modules list never downloads from the repo (is the download tab is empty and just shows the busy indicator).

Hopefully someone with more expertise reading my logs can see the issue and provide a fix (or comment back and say what more info the need from me).

For the time being I'm going back to Magisk v12 and Magisk Manager 4.x

Can anyone in the know have a look at my logs and comment if I need to provide more info. Or am I the only person with this issue. Thanks
[Magisk] bluegizmo83:
I'm not sure on that one. Did it seem to flash ok through TWRP? I did mine via fastboot and it worked fine. Also, don't let your os boot up between flashing the boot image and flashing magisk. Go straight from flashing boot image to flashing magisk. Some ROMs modified the boot partition and/or reinstall root at boot if it's missing.
[Magisk] Legendary Cryptid:
When flashing stock, that rightfully removes any custom recovery previously flashed right? Dirty or clean flash?
[Magisk] methoddon1:
anyone aware of why banking app would start detecting root?

it was always detecting root but not with magisk... Android Pay is fine.

all of a sudden without updating the app..

latest magisk, app obviously included in Hide list.
[Magisk] trawel:
I have a problem since Magisk 13.3. After some time of using, root like disappears - when I open the app it says that phone is rooted but the app needs to have it allowed (I didn't change anything). Weird thing happens also with kernel - when I reboot my phone, the CPU governor changes itself and I have to flash kernel and Magisk again to make it work. Weird is that it happens after couple days of using (without rebooting). Phone is OP3 with OOS 4.1.6, kernel blu_spark r.164 and I'm using ex kernel manager to tweak kernel.

Maybe someone know what might be causing that? I don't remember having such problems on earlier versions of magisk.
[Magisk] Iradj:
All latest Banking-Apps detect some magisk root files and the manager itself so you have to wait till magisk hide gets updated.
[Magisk] Zackptg5:
[MENTION=4470081]topjohnwu[/MENTION]

Any reason why the latest magisk module template is missing support for magisk installs located in /cache? Support for those is still present in magisk 13.3

I opened an issue on the template github here: https://github.com/topjohnwu/magisk-module-template/issues/25

and a pull request that fixes it here: https://github.com/topjohnwu/magisk-module-template/pull/27
[Magisk] dantexaiver:
What's that mean
[Magisk] fornol:
Some apps just shut down

I found it to be a fine alternative to SuperSU. But just spent several hours to find out why some of my apps do not work. Unfortunatelly it all leads to Magisk.

I am on Samsung Note 3 with Ressurection Remix. Carcassone does not open. The same for Dancing Line. Found just those two. May be more. I tried all options in settings for Magisk. No help. No matter what I do both apps just quick.

I am writing this with a hope that this will help to improve the app.
[Magisk] Lyveth:
I tried to re-do it in order, Flash RR > Unroot > Flash unSU > Flash RR boot.img via fastboot > Flash Magisk

Still giving me the same error with unable to repack boot img.

I think the problem is the custom rom, so i'll try to use another like CM12

btw, thanks for your help :D
[Magisk] Joe199799:
Running Magisk 13.3/Manger 5.11, failing safetynet don't know if something is wrong or if I messed something up, no modules installed and I was passing a week ago
[Magisk] blackknightavalon:
Magisk 13.3 was giving me a bootloop when I flashed it on top of the latest Open Beta build for the OnePlus 3T. :(
[Magisk] rosboy:
Latest magisk manager 5.1.1 is force closing, and apps cannot access root.
[Magisk] Pkt_Lnt:
Without logcats of crashes, the best we can offer is "cool story bro".

I've never heard of those apps and it is unlikely I use the same phone and rom you do, so.....

[Tutorial] How To Logcat

Please get logs of crashes, post them on pastebin and link here so we can help.

---------- Post added at 06:14 PM ---------- Previous post was at 06:14 PM ----------

clear manager cache and data
[Magisk] Paschfire:
Magisk Log?

logcat?

... Any pertaining information regarding your device/ROMs setup?

If you don't provide proper information regarding the issue attached within your post, then there's no point in reporting anything.
[Magisk] bluegizmo83:
Your welcome! I'm also thinking it may be an issue with the ROM being pre-rooted as you said. This info here was located in a Magisk troubleshooting thread: "If your ROM comes pre-rooted this can be tricky, depending on how the ROM roots your device. Usually the ROM just flashes root at the end of the ROM flash and you can simply open up the zip, unroot and flash the clean boot image from the ROM zip. If the ROM comes pre-patched from the start, ask for advice in your ROM thread or you could try a custom kernel that modifies the ramdisk"
[Magisk] Lyveth:
No luck either with CM12, and i also tried to clean flash stock rom of my device. Still giving me the same error even tho it's still very fresh :(
[Magisk] bluegizmo83:
Damn sorry man. I'm all out of ideas. Maybe as a last ditch effort try redownloading the Magisk files if you haven't done so already?

Edit: this post here my be helpful for you if you haven't already read it, see if you can post a TWRP log here of the flashing error too, might help nail down the exact issue. http://blox2.com/fixmagisk-install-error-1-twrp-recovery/
[Magisk] thatOneWeeaboo:
Hi, I tried to install a module once and it somehow messed with my Magisk. I used Magisk 13.3 and 5.1.1 Manager and it's all fine until that attempt. Now, any Manager version 5.0.4+ always crashed as soon as I open it, within exception with the 5.1.1 version, which just pops for a few moments for an update check and then it crashed (logs attached. despite it says sagit it's actually rolex (redmi 4a) since I used the safetynet fix module). Manager ver. 4.x.x is fine only for root requests and as expected, it doesn't detect my Magisk installation (it immediately notifies me that an update ver. 13.1 is available) . I tried to re-install everything (including the rom), still no idea. But it appears that it occurs at somewhat random times, at one time it just going great and at other times it just refuses to run, although root requests is somehow still being managed i.e. root requests was just fine

in case it's not clear enough:

Device's Redmi 4a with LineageOS 13 (Marshmallow 6.0.1). Only module enabled for now is the SafetyNet fix.
[Magisk] Lyveth:
Forgot to mention that i once used kingroot to root my device before trying to use magisk, which is i regret it so much, and also i couldn't flash Magisk Uninstaller with the same error. Do you think that kingroot still leave it's trace even though i've done all the process i mentioned before?
[Magisk] bluegizmo83:
Sounds like a module issue. With the recent Magisk update all modules are required to use template v4, and any modules that aren't updated to v4 will cause the issue your having. I had the same issue with the Dolby Atmos r-6.5c module (which still hasn't been v4 updated). If you can disable your modules do so, if not then flash Magisk uninstaller and then flash Magisk again for a fresh Magisk with no module. If the future, make sure the modules you try specifically state they're v4 compatible.
[Magisk] thatOneWeeaboo:
Nep, no luck. The Manager crashed despite having the Magisk itself not installed. As soon as it finished checking for a new Magisk update it immediately crash.
[Magisk] bluegizmo83:
Ah ok, sorry. I had a very similar issue that was module related so I thought I'd throw it out there.

---------- Post added at 05:31 AM ---------- Previous post was at 05:25 AM ----------

Looking through your log it appears to maybe be an issue with your app Poweramp (and/or possibly a low memory/ram issue). Try uninstalling Poweramp and test again
[Magisk] thatOneWeeaboo:
Nope. Uninstalled Poweramp and crashes' still there. All was fine before I tried the module. The module in question is actually this. Funny thing is, if I had the Manager apk stored in my Downloads folder, Solid Explorer crashed while trying to load the folder. Just the Solid Explore, stock LineageOS fileman has no crashes.
[Magisk] Didgeridoohan:
If that was a general issue with OB12 and Magisk it'd be all over the Open Beta thread. All I've seen is about Magisk and the latest beta is one user reporting it works fine. There's likely something wrong on your end...

You're working on the presumption that the installation is failing because if previous root. Does the output of TWRP state "bootloader patched by other programs"? Sounds to me like you're simply experiencing a device incompatibility...

But, to know for sure we'd have to see a recovery log. Use Pastebin and just post the id for the paste.

I recognise that one. There have been other users with crashing issues that reported that their file explorer would crash when viewing the folder where the apk was (corrupt thumbnail?).

Where did you download the apk?

Try re-downloading Magisk, uninstall (including the Manager) and re-install. You shouldn't need to install the Manager separately.
[Magisk] thatOneWeeaboo:
I download it off from apkmirror. Been done that, still the same. I even tried to install the Manager from the downloaded Magisk zip.
[Magisk] Didgeridoohan:
Hm... I think that pretty much all users that have had this issue downloaded the apk from apkmirror.

Did you uninstall before installing the apk from the zip?

If you haven't already, do a completely clean install with the Magisk zip from the release thread (re-downloaded). Don't install any apk separately (it should get done automatically when you flash the zip in recovery).
[Magisk] Lyveth:
no, i didn't see "bootloader patched by other program" message, it's only stating that twrp unable to repack boot image and yes i also started to think that it's because my device isn't compatible with current version of Magisk yet.

I'm using Lenovo a5000, not popular i know so maybe I'll just wait for the next release.

Thanks for your response!
[Magisk] thatOneWeeaboo:
Yes, there's an attempt with existing Manager uninstalled before installing the zip, still results the same.
[Magisk] rogconnect:
For some reason, Nexus 6 on Pure Nexus keep losing root after a few hours and have to reflash Magisk 13.3. Anyone have a fix? I have tried reflashed ROM.
[Magisk] bluegizmo83:
I take partial credit for leading you down the "assuming it's a pre-rooted problem instead of a device compatibility issue"... I was trying to help but I probably did more harm than good cause I thought this whole time it was a "patched by other program" issue like I had when I did mine. I didn't read your initial messages closely enough, I apologise.
[Magisk] cascabel:
Hi. I'm very new to Magisk - been using it for only about a day. I just checked logs (because greenify4magisk doesn't work for me), and i found this:

--------- beginning of main

I( 330: 330) Magisk v13.3(1330) daemon started

I( 330: 332) ** post-fs mode running

--------- beginning of system

I( 330: 362) ** post-fs-data mode running

I( 330: 362) * Mounting /data/magisk.img

I( 330: 362) * Running post-fs-data.d scripts

I( 330: 362) * Loading modules

I( 330: 362) systemless-substratum-legacy: constructing magic mount structure

I( 330: 362) Greenify4Magisk: constructing magic mount structure

I( 330: 362) single-user: loading [system.prop]

I( 330: 362) Resize /data/magisk.img to 64M

I( 330: 362) * Mounting system/vendor mirrors

E( 330: 362) mount /dev/block/bootdevice/by-name/system->/dev/magisk/mirror/system failed with 16: Device or resource busy

I( 330: 860) ** late_start service mode running

I( 330: 860) * Running service.d scripts

I( 330: 860) * Running module service scripts

W( 5580: 5580) su: request rejected (1000->0)

Looks like there's an error since /dev/block won't mount. I'm guessing this is why greenify4magisk won't work? And does this mean systemless substratum isn't working either (its weird because the theme I'm using gets errors from dialer before i used that module. Now the dialer got themed no problem)? Other modules (like single user) work fine though...

Edit:

Im on lg f460 running RR 8.5.0. Development is dead and this is the most stable N rom we have right now.

Edit 2:

I've encounter the mount error before, but i can't remember where. The solution was to use busybox mount. Is that possible here?
[Magisk] shrgerrits:
Hi,

I'm new here and new to the whole custom phone **** so please forgive me if I made a mistake without knowing.

I have an old Huawei p8 I just want to use for spoofing my gps. So I factory reset that badboy so it was clean of all the old **** still on the phone, rolled back the security patch from march 2017 to january 2017 and I unlocked bootloader. Flashed TWRP on it and made a backup. Now when I try to install Magisk v13.3 on it and reboot the phone gets stuck in bootloop(I think it's called that) and the only way I know how to get out of it is by pressing both volume buttons + power button at the same time to make it "upgrade" to the old security patch and then it works fine again. I've tried it a couple of times now and the results stay the same. I looked around but I couldn't find any solution to the problem on this forum or anywhere else. Some help would be greatly appreciated :).

Below are my phone details, install log from TWRP and bootloop screen with errors.

Thank you in advance for taking the time to help out.

TWRP log:

Full SELinux support is present.
MTP Enabled
Installing zip file '/sdcard/Download/Magisk-v13.3.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
*******************************************
*Magisk v13.3 Installer
*******************************************
-Mounting /system, /vendor, /cache, /data
-Device platform: arm64
-Constructing environment
-Creating /data/magisk.img
-Mounting /data/magisk.img to /magisk
-Found Boot Image: /dev/block/mmcblk0p27
-Unpacking boot image
-Checking ramdisk status
-Stock boot image detected!
-Backing up stock boot image
-Patching ramdisk
-Repacking boot image
-Flashing new boot image
-Unmounting partitions
-Done

The bootloop screen says:

RESCUE MODE
Attention!
Please update system again
Error!
Func NO: 10(boot image)
Error NO: 2(load failed!)

Phone Details:

Model number: Huawei GRA-L09
Build number: GRA-L09C432B391
EMUI version: EMUI 4.0.1
Android version: 6.0
CPU: Hisilicon Kirin 930
RAM: 3.0GB
Android security patch level: 1 January 2017
Baseband version: 21.600.89.00.010
Kernel version: 3.10.86-g5eda55f android@localhost #2 Wed Dec 21 20:47:44 CST 2016

I hope my information provided is clear enough, I couldn't post any links so I can't show any pictures.
[Magisk] Didgeridoohan:
[MENTION=8466269]shrgerrits[/MENTION]

Take a look here: https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417

Try the two echo commands in the second half of the "Bootloop" section of post #2.
[Magisk] inuyasha555:
I've been trying to install Magisk on my galaxy s4 i337m and can't get it to work.

I flashed stock and cleared everything on the device in preparation. Installed the MagiskManager-v5.1.1 APK and safetynet passes as expected.

I then flash TWRP through Odin and boot into recovery. From there I flash the Magisk-v13.3.zip and reboot.

Upon opening the manager Magisk is NOT installed and safetynet now fails both checks.

What would cause it to successfully install and then say it's not installed like this?
[Magisk] DeadlyByNite:
I'm a little concerned... Why would magisk log be saying the device is in permissive mode? I never set it to permissive, and shouldn't have done anything to make it permissive. Since setting this requires root access, it has to be an app that already has root access, but there's no way to tell what app it was.

I( 516: 841) * Starting MagiskHide
I( 516: 841) hide_utils: Hiding sensitive props
I( 516: 841) hide_list: [com.google.android.gms.unstable]
I( 516: 841) proc_monitor: init ns=mnt:[4026531840]
I( 516: 979) ** late_start service mode running
I( 516: 979) * Running service.d scripts
I( 516: 979) * Running module service scripts
I( 516: 979) ARISE_Magisk_Compatibility_Module: exec [service.sh]
I( 516: 841) proc_monitor: zygote ns=mnt:[4026535795] zygote64 ns=mnt:[4026535797]
I( 516: 841) proc_monitor: com.google.android.gms.unstable (PID=7773 ns=mnt:[4026535920])
I( 7787: 7787) hide_utils: Re-linking /sbin
I( 516: 841) proc_monitor: com.google.android.gms.unstable (PID=10408 ns=mnt:[4026535991])
I( 516: 841) proc_monitor: com.google.android.gms.unstable (PID=13293 ns=mnt:[4026535939])
I( 516: 841) proc_monitor: com.keramidas.TitaniumBackup (PID=13543 ns=mnt:[4026535847])
I( 516: 841) proc_monitor: com.keramidas.TitaniumBackup (PID=13584 ns=mnt:[4026535983])
I( 516: 841) proc_monitor: com.keramidas.TitaniumBackup (PID=14043 ns=mnt:[4026535919])
I( 516: 841) proc_monitor: com.keramidas.TitaniumBackup (PID=15310 ns=mnt:[4026535874])
I( 516: 841) proc_monitor: com.keramidas.TitaniumBackup (PID=4211 ns=mnt:[4026536020])
I( 516: 841) proc_monitor: com.google.android.gms.unstable (PID=5241 ns=mnt:[4026536088])
I( 5248: 5248) hide_daemon: Permissive detected, hide the state
I( 516: 841) proc_monitor: com.google.android.gms.unstable (PID=12088 ns=mnt:[4026536122])
I(12093:12093) hide_daemon: Permissive detected, hide the state

This is why I liked superSU, because it logged all the apps commands. (with the pro version of course)

This would be a great feature to add to magisk, and with shady things like this going on with my device, I'm going to have to figure out a way to find what app is doing this. Does anyone have any ideas?

I'm using an HTC One A9, with stock rom. The command "getenforce" inside a terminal emulator confirms it is in permissive mode, but only when I catch the line in magisk log. A reboot fixes it, but sometimes overnight I have seen the line in the logs, and for now I am disabling root.
[Magisk] shrgerrits:
I tried it, but alas it didn't work:(

Same thing happened as the other times
[Magisk] Didgeridoohan:
It's likely it wasn't a successful install... Only way to know for sure is to see the recovery log from the installation.

I haven't taken a look at the actual module, but Iwouldn't be surprised if it's the Arise Compatibility module messing with the SELinux policy.

Too bad... Just to make sure, you did uninstall Magisk and made sure you had a working, booting system before running the commands and flashing Magisk again?
[Magisk] DeadlyByNite:
It actually says in the description of the ARISE module: "Sets selinux policy and makes scripts compatibile for magisk"

I'll take the issue over to that thread if needed. Thanks for the quick response! ?
[Magisk] shrgerrits:
Yeah I even restored back to before putting magisk on the phone using TWRP, just to be sure. You think trying magisk v12 is worth the effort?
[Magisk] inuyasha555:
nvm got it working

Gave up and installed a custom ROM
[Magisk] Ashley david:
Yes you should flash v12 because when I flash 13.1 zip on my stock marshmallow ROM it bootloop.but v12 installs fine and you can update magisk to 13.1 through the magisk manager app so no issue for me.note: I am not using p8:D
[Magisk] alexbelgium:
when listening to music on google play music, it stops mid-track every 10 minutes or so.

I'm on magisk 13.3. The issue is not present with magisk 12.

Does someone have a fix? Thanks
[Magisk] Didgeridoohan:
Sure, you could give it a shot. Like already mentioned, it might work updating from an older version... Try both with and without the keep dm-verity and force encrypt options.

Weird. Sounds like Magisk gets installed but MagiskSU doesn't. Your log shows one error right at the start of the installation script, might be related...

Details? About your device (ROM, kernel, etc), your Magisk installation (what modules, Magisk log, etc), any other mods you're using (batter savers might be an issue), etc...
[Magisk] Ashley david:
I have one doubt does installing xposed make the safety net check fail?because mine is saying it's failed.earlier it was passed
[Magisk] DodoGTA:
Xposed = SafetyNet failure
[Magisk] ericotena:
Why can't i uninstall modules especially appsystemizer? Everytime i reboot the module is still there. How to fix this?
[Magisk] zoolly:
Can someone help?

Galaxy 6 g920i android 6

(screenshot added)
[Magisk] DodoGTA:
Can you post the Magisk log from Magisk Manager?
[Magisk] Didgeridoohan:
You mean you can uninstall other modules but not App Systemizer?

Magisk log, logcat, etc?

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417
[Magisk] zoolly:
--------- beginning of system

--------- beginning of main

08-08 08:29:20.760 3018 3018 I Magisk : Magisk v13.3(1330) daemon started

08-08 08:29:20.770 3018 3038 I Magisk : ** post-fs mode running

08-08 11:29:21.160 3018 3045 I Magisk : ** post-fs-data mode running

08-08 11:29:21.220 3018 3045 I Magisk : Resize /data/magisk.img to 128M

08-08 11:29:21.310 3018 3045 I Magisk : Upgrade module: systemless-unicode9-ios10-Emoji

08-08 11:29:21.410 3018 3045 E Magisk : sendfile failed with 2: No such file or directory

08-08 11:29:22.380 3018 3223 I Magisk : ** late_start service mode running

08-08 11:29:23.290 3018 3223 I Magisk : * Running service.d scripts

08-08 11:29:23.290 3018 3223 I Magisk : * Running module service scripts
[Magisk] zoolly:
And if I'm trying to install model I get failed: /
[Magisk] Mateus109:
Hi, I'm struggling to get 13.3 installed on a LeEco Pro 3 running EUI 23S. I had v12 installed which I've removed and flashed the stock boot image back, but upon flashing Magisk 13.3 I get:

! Magisk image mount failed...

I've looked online for guidance but not found anything at works yet.

Thanks :good:
[Magisk] Gazzasore:
I get the exact same thing

Note 3 N9005 on Traders Lineage 7.1.2

The SU side is working perfectly
[Magisk] Sascha1976:
Hello my problem is...Iam loosing root after a while... A reboot fixed it, but it happend again. Then Magisk is force closing. Nexus 6P on Pure Nexus 7.1.2 with Franco Kernel