yashsingh1/xdaforums huggingface dataset:
[Magisk] josephcsible:
On a Nexus 5X, 100% stock ROM with no changes other than Magisk itself, I can't refresh the Downloads tab in Magisk Manager or it crashes. Here's what adb logcat says when it crashes:

04-14 15:35:35.137 7063 10951 E AndroidRuntime: FATAL EXCEPTION: AsyncTask #5
04-14 15:35:35.137 7063 10951 E AndroidRuntime: Process: com.topjohnwu.magisk, PID: 7063
04-14 15:35:35.137 7063 10951 E AndroidRuntime: java.lang.RuntimeException: An error occurred while executing doInBackground()
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at android.os.AsyncTask$3.done(AsyncTask.java:353)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:271)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: Caused by: java.util.concurrent.RejectedExecutionException: Task com.topjohnwu.magisk.asyncs.UpdateRepos$$Lambda$1@6e24ec8 rejected from java.util.concurrent.ThreadPoolExecutor@90cab61[Running, pool size = 13, active threads = 13, queued tasks = 128, completed tasks = 4]
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2078)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:843)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1389)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at com.topjohnwu.magisk.asyncs.UpdateRepos.doInBackground(Unknown Source:79)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at com.topjohnwu.magisk.asyncs.UpdateRepos.doInBackground(Unknown Source:2)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at android.os.AsyncTask$2.call(AsyncTask.java:333)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
04-14 15:35:35.137 7063 10951 E AndroidRuntime: ... 3 more

I'm on the April 2018 stock ROM from Google, Magisk 16.3, and Magisk Manager 5.6.4.
[Magisk] teddybear3k:
Hi,

I'm a beta tester a new rom CAF KeyLemon for 5T.

The developer does not find out why the ROM does not want to become Root.

Can you help?

Log

https://file.io/mTbOJ5

Thx

Ted
[Magisk] Artim_96:
Link only shows error 404
[Magisk] teddybear3k:
Sorry,

New link : https://wetransfer.com/downloads/c5...bd439e8eb330430fb35e479e20180414230452/53da39
[Magisk] daddylonglegs:
Nobody replied to my post here but I thought I could help someone else in case they have this issue. Also maybe the developers can make a change so that it does not happen to anyone else.

After literally 15 hours of trying to figure this out, it seems as though the XPosed Magisk Module (SDK 27) was causing this issue (could have been because of GravityBox). This was weird because last month's OTA had zero issue with Magisk and XPosed/Gravitybox but that's neither here nor there.

The thing that finally worked for me was booting into recovery and launching Magisk Manager for Recovery (by going into TWRP, installing the Magisk Manager for Recovery zip, and then going to terminal and typing "mm"). In there I told Magisk Manager for Recovery to "resize" the Magisk image so that it used the full size instead of only 60% of it.

I am not sure why this fixes the issue for me, or why Magisk does not use the full 100% by default (it's only 91 MB) but I figured I would be helpful to anyone else who has this issues, or the developers who might like to know about this issue. Cheers!
[Magisk] :
I am unable to install Magisk, even on stable or beta version.

Error: ! Unable to unpack boot image

My phone:

- Gionee P4, CrDroid 7.1.2 ROM.

- Recovery: TWRP 3.2.1

Log, boot img and screenshot below.

By somehow the unofficial Magisk ZIP below works, but buggy:(
[Magisk] daddylonglegs:
I just tried this. Unfortunately it does not mount the extra storage in such a way that all my file explorer programs can see it.

I need my external USB storage to show up in /storage/emulated because a lot of my apps will not let you browse anywhere else. Is there any way with Magisk to do this?
[Magisk] demonoidmaster:
that's beta magisk, not stable, report your issue in the proper thread
[Magisk] Jaymin.0.1910:
Hi,

Thanks for your precious feedback.

Yes, I planned all of this, just the disable feature is rather a hard to implement thing, but still not impossible.

Please let me know if there was another feature you'd want.

MCMotherEffin'
[Magisk] zeduck:
Up

Can anyone help me, please?
[Magisk] Sir Backe:
Tks very much!

Disabling does not help. I have to uninstall, clearing all caches of all involved apps and then reboot. Very fortunately I could avoid a factory reset.

Building an own exposed installer is not an option, due to a lack of knowledge.

So I arrive at option 3. Either xposed or access app.

Tks very much anyhow for your help!
[Magisk] Didgeridoohan:
It's known and already fixed, but not yet released.

You might be able to get the download list to load fresh if you first clear the repo cache.

That's a Manager issue, and v5.6.4 is the latest stable Manager. No need to take it to the beta thread.

I don't see any logs posted...
[Magisk] gundal:
^ this!!

Has been happening to me with every version of magisk that I can remember on all my Samsung devices.

I have a strong suspicion it has to do with the low battery power saving mode triggered at 15% and Sammy kernel killing magisk daemon.

Will do some testing and grab a logcat.
[Magisk] valkyrjur:
Hello everyone.

One question. How can I backup first and then restore all my installed modules?
[Magisk] ulli5:
I flashed Magisk v16 on my MHA-L29 (german), which has all OTA Updates (8.0.0.366). Then I installed xposed framework via Magisk Manager. This caused a bootloop.

I tried all tips on https://www.didgeridoohan.com/magisk/MagiskModuleIssues, but in vain.

- I wasn't able to create a .disable_magisk file

- when I startet to flash the "Mount-Magisk.zip" I got "Magisk is not installed". So I flashed Magisk again, rebooted to recovery and flashed Mount Magisk again. Same result.

- when I'm flashing the Magisk Module Uninstaller I get "ERROR:1" (tried all three)

- flashing the "Magisk Manager for Recovery Mode" is successfull, but when I start it, I get "Magisk is not installed"

Already the TWRP installation was problematic (see https://xdaforums.com/mate-9/development/recovery-twrp-3-2-1-0-oreo-t3734967/post76232553.)

Can someone help me? I didn't make a backup.
[Magisk] Mohitjolly:
Hi MAGISK TEAM

I need your help

I want to ROOT my device to MAGISK.

M using MICROMAX HS3 (MICROMAX CANVAS INFINITY PRO)

Please suggest me how I can root my device.

On XDA page no information for Micromax HS3 device.

When I search for MICROMAX HS3,, details coming for MICROMAX CANVAS INFINITY (HS2)

Bt my device is HS3 (MICROMAX CANVAS INFINITY PRO)

I have flash with ""RECOVERY MICROMAX HS2.IMG"" flashing successfully done bt unable to ON reovery mode.

Please help if possible.

My Email id - iammohitjolly@gmail.com
[Magisk] adaa1262:
There's an abd install mode
[Magisk] Mohitjolly:
I have tried with ADB tool to Micromax hs2 IMG file.

Bt I don't have ""TWRP RECOVERY.IMG"" file for my device (Micromax HS3).
[Magisk] Didgeridoohan:
I have a slight suspicion that it might have to do with MagiskHide not being able to mount all the files again after hiding (for whatever reason). If you're not on the beta release, could you install the beta, and when it happens save the magisk_debug.log (in /data/adb, you might have to pull it from recovery) and post that here.

Everything is in the Magisk image, located in /data/adb. Make a backup of that and put it back after reinstalling Magisk, after any wipe or whatever you're planning on doing.

Any logs from all of these attempts? And how come you couldn't create the .disable_magisk file? You could try just deleting the Magisk image (/data/adb/magisk.img).

If your device is compatible (there's no list of compatible devices), the easiest way is to use the install instructions from the release thread. If you don't have a custom recovery, follow the instructions for letting the Manager patch the boot image.

If you can't get things to work, check out the Magisk guide for any tips and pointers. If you can't get it to work anyway, make sure to read this part of the guide.
[Magisk] gundal:
Yes absolutely, would love to help get this problem fixed, installing beta now. Will report back when possible.

Ok IT just happened, again, in Magisk Manager I get "Magisk is not installed."

Any requests made by apps get /system/bin/su not found

This include terminal app (Rom Toolbox pro)

`whoami` returns

u0_a229

Interestingly enough, when I use adb...

I can get root privileges,

everything is running still,

> adb shell

greatqltecs:/ $ whoami

shell

greatqltecs:/ $ su

greatqltecs:/ $ whoami

root

greatqltecs:/ # ps | grep magi

root 2185 1 17444 4 unix_strea 000045d28c S magiskinit

root 3284 1 26424 2612 __skb_recv 74226a7c0c S magisk_daemon

u0_a448 22032 4137 2286540 168416 SyS_epoll_ 7a9c9fdc6c S com.topjohnwu.magisk

Attached is magisk_debug.log and logcat.

The logcat was far too big to upload so I just did a `logcat | grep -e magisk -e johnwu -e gms`

As you mentioned, /sbin appears to not have any of the extra commands except resetpop
[Magisk] LoV432:
So i been having safety net problem so i decided to reinstall magisk but when i uninstalled magisk i noticed some of my modules still worked....like iytbp and ios emoji...is that how its supposed to be?......i m confused as hell.....:/
[Magisk] Artim_96:
No, they shouldn't. Sure that you at least reflashed your boot.img? Maybe you need to clear cache to revert changes fully,I don't know how these modules work
[Magisk] LoV432:
I flashed the whole rom again and it did nothing :|
[Magisk] Artim_96:
Very strange. That YouTube app should be removed with the next YouTube update, but I have no idea how you could get rid of the emojis.

Flashing back the ROM won't change a thing other than restoring the boot.img... But I have no clue what that survival script does. So maybe use the uninstaller zip and then clean cache and dalvik
[Magisk] LoV432:
I did that and then flashed rom cuz all that didn't work
[Magisk] euleralves:
After two days I got a Google Pay update. I kept all my Magisk modules actived and headed to a POS. It simply worked.

After all, it was a Google Pay bug, probably because an old app been blocked, nothing to do with Magisk.
[Magisk] Eyji:
Hello guys,

does Magisk work on KitKat ROM?

Can it work alongside SuperSU (or even replace it)?

Thanks
[Magisk] Wolfcity:
No,as far as I know the "modern" magisk works from 5.x upwards (Someone correct me if I'm wrong).

And as a rooting solution/method it can for sure replace SuperSU.
[Magisk] :
Anyone can help me?

I attached all log things there... :(
[Magisk] StarScream_X:
I just found a fix for Tez app.. at least this works for me than everything else suggested..

1. Download n install the Magisk Hide Props config from the download section of Magisk. (Also download a terminal emulator from playstore)

2. Enter "su" and then "props" in the terminal manager.

3. Select first option by entering "1"

4. Select from the list of available props according to your device..

5. Once installed, reboot system.. Then go to app manager and clear all data from Tezz app..

6. Go to magisk manager and verify safety net again, this time cts profile and basic integrity both should pass..

7. Open Tez, and setup your account.. this should work now.. (at least it did for me)

Good luck.
[Magisk] francwalter:
I have Magisk v16.3 on a Cubot Note Plus. Magisk crashes when I pull down (update) in the Downloads menu.

EDIT: Oh-oh, I read now in a previous page here, that this is already known and fixed. Its just not yet published. As a meanwhile help the repo cache can be deleted (in settings) and then the pull-down to update will work the first time.

So nothing for ungood :)
[Magisk] guest4711:
If you don't like to wait you may give the unofficial up2date builds a try: https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901/post70157494

(but because of different keys you have to uninstall your magiskManager first).
[Magisk] Didgeridoohan:
It's quite tricky to find a link to current downloads in that thread, since the one in the OP hasn't been updated in months.

Current snapshots by [MENTION=3306843]kantjer[/MENTION] can be found here:

https://github.com/kantjer/MagiskFiles

---------- Post added at 13:18 ---------- Previous post was at 13:09 ----------

You've provided good info, so there might be a fix in a later release. But, [MENTION=4470081]topjohnwu[/MENTION] is very short on time so it might be a while before anything could be done about it...

Have you tried any of the other official releases? You can find the stable ones attached to the OP in the release thread and the beta ones in the beta thread.
[Magisk] :
I use all releases, include stable and beta, but no one fixed. Still the same problem.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] 's unofficial builds have been working great for me as well as the official beta, with one exception, Magisk Manager sometimes crashes. On a second launch, it usually works fine.

Attached is a logcat filtered for that app in logcat extreme.

Could someone please take a look. My device info is in my signiture.

Thanks
[Magisk] UMU24013:
resetprop

I need a simple thing to do:

Make a "permanent" change to build.prop using the Magisk resetprop command that would survive device reboot.

I can enter resetprop someprop somevalue in terminal and it works: getprop returns the saved value. But after rebooting the device it is reset to the original value.

Searched a lot but found nothing how to do this easy thing step by step.

Is there a boot script or something in Magisk that would allow me to add the required resetprop line, so that it would apply the property change each time on system startup?
[Magisk] Didgeridoohan:
The latest update to my module MagiskHide Props Config can do that. Just enter the prop and the value, reboot and you're done.
[Magisk] fiverings:
I had that happen recently. I changed the Gapps package and it install perfectly.

---------- Post added at 09:27 PM ---------- Previous post was at 09:11 PM ----------

It does replace supersu, if you install Magisk, you don't use supersu. But if your phone is older, then you might be able to just use supersu and not Magisk. There has been no response work on supersu since September or October.
[Magisk] UMU24013:
Thanks. What option should I use for this? Edit prop files, MagiskHide props, maybe Custom props?

I did not find any usage examples in the docs.

Here's the menu

←[01;33m=====================================←[00;37;40m

Select an option below.

←[01;33m=====================================←[00;37;40m

←[01;32m1←[00;37;40m - Device fingerprint

←[01;32m2←[00;37;40m - Edit prop files←[01;32m (active)←[00;37;40m

←[01;32m3←[00;37;40m - MagiskHide props

←[01;32m4←[00;37;40m - Custom props

←[01;32m5←[00;37;40m - Options

←[01;32mr←[00;37;40m - Reset all settings

←[01;32mb←[00;37;40m - Reboot device
[Magisk] demonoidmaster:
no i wasn't talking about the manager, he was using magisk 16.3 which is beta and not 16.0

---------- Post added at 03:23 AM ---------- Previous post was at 03:18 AM ----------

who even wants to use supersu anymore lol? Magisk is superior
[Magisk] mattman1978:
I need some help. I have rooted samsung devices before by flashing TWRP image for the device. Trouble is, the new phone doesn't have a TWRP built for it yet. So I found the stock firmware and even used odin to confirm it's good. The file looks like BL_____.tar.md5. I'm assuming that's the boot-loader. I am now stuck at trying to get Magisk manager to convert the file so I can flash it. I have placed the .tar.md5 on the phone and tried to select it, but it doesn't show up. I've tried removing the .md5 extension leaving only the .tar and still nothing. Can someone explain or point me to a good explanation of what I need to do to the BL file in order for Magisk manager to patch it?

As far as I know, there is no known root method for the S727VL, so I'm giving Magisk a try.

Thanks in advance.
[Magisk] Pkt_Lnt:
Well, first thing is you want the BOOT **IMAGE**, not the boot loader.

In this post.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Scroll down to the

* Instructions for installing the first time are presented below:

Then click the box that says "CLICK TO SHOW CONTENT"

I copied here, but please see the original post with the RED warnings!
[Magisk] famewolf:
Is there still a version of Magisk suitable for an older device running android 4.4.2 (kitkat)? I'm not thrilled with supersu especially now that a chinese company owns it instead of chainfire and would really like an alternative for a phone being used as a "server" to run several apps...the primary being related to home automation.
[Magisk] Pkt_Lnt:
No. the main / release thread states:

[2018.3.28] Magisk v16.0 - Root & Universal Systemless Interface [Android 5.0+]

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] jenslody:
But the issue he posted about is not a Magisk beta, but a MagiskManager issue and it is already known (and fixed in github) and therefore there is no need to post it in beta-thread also (and clutter it more).
[Magisk] famewolf:
Let me rephrase my question since it apparently wasn't clear. What OLD version will still work on kitkat 4.4.2? I don't care if none of the modules work. All it has to do is provide root.
[Magisk] Didgeridoohan:
Magisk has always been for Android 5+.
[Magisk] NYLimited:
Your tab doesn't require an su which is maintained. Why not grab an old Chainfire or phh or koush version?
[Magisk] :
Still not work, I am using MicroG :(

---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------

Can you upload your magisk ZIP file? I want to test it...
[Magisk] guest4711:
Current snapshots by [MENTION=3306843]kantjer[/MENTION] can be found here:

https://github.com/kantjer/MagiskFiles
[Magisk] Cogor:
Hi everyone I'm new on this and I don't have a recovery. How can I install Magisk?
[Magisk] Didgeridoohan:
Installation instructions in the release thread (patch via Manager). Always a good idea to take a look at the stickies in a forum... Usually a lot of good info there.
[Magisk] Pkt_Lnt:
This post just a few posts back. Has links to do install without custom recovery. Go to the links and read them all carefully, based on the hints and cautions in this post.

https://xdaforums.com/showpost.php?p=76254201&postcount=24312
[Magisk] Cogor:
Thank you

---------- Post added at 07:55 PM ---------- Previous post was at 07:55 PM ----------

Thank you
[Magisk] ArdW:
I have a problem with my Xperia XZ1 compact. I installed magisk v16 thru TWRP, then the magic manager app latest release, but it seems it does not working please see my attachemets. I have 47.1.A.12.119 firmware with wrp-3.2.1-0-lilac-10-patchlevel-2018-04-05 twrp. I am also running xperifix DRM hack.
[Magisk] ekscelsior:
Hey guys. I'm using v16.3 with Magisk Hide turned on, safetynet passes wonderfully. Unfortunately Samsung Health can still detect root and won't start. :( Of course it has been enabled in the Magisk Hide tab along with a bunch of other google and samsung apps (so is the Health Framework). Idk whats wrong? :confused:

Its on a Galaxy S7, Nougat.
[Magisk] Artim_96:
Maybe hide the manger too? What does Rootbeer sample say when you use Magisk hide on it?
[Magisk] Didgeridoohan:
Looks normal... That's what the Manager looks like when you don't have an internet connection.

The basics of hiding root from an app can be found here:

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

But, are you sure it's root that's triggering it and not your tripped Knox? Quick search shows you might have success if you change the prop ro.config.tima to 0 (unconfirmed, I literally spent 30 seconds searching for a possible correlation). You can use my MagiskHide Props Config module for that (use the "Custom props" option).
[Magisk] ArdW:
LOL it really changed after internet connection. However, it seems still bad? If I click install it wants to install magisk v16, even I especially did that thru TWRP. Thanks
[Magisk] Didgeridoohan:
Still looks perfectly normal. And when you press install, it's supposed to install the latest version (no matter what you have installed currently). And since you're on the stable update channel, that would be Magisk v16.0. If you want some other version you'll have to change the update channel in the app settings.

What is the result you're expecting? What are you trying to do?

Reading through the release thread and the Magisk guide might be a good idea... Also, if you search through this thread you'll likely find some answers as well.
[Magisk] Marvino.:
Why there's no online repo for magisk modules like the one xposed used to have? Where are these magisk modules basically stored? Because my magisk manager has sort of issues with downloading/updating my magisk modules every time. I have a stable internet connection but not fast and when I try to download the latest Xposed framework unity 1.2.5 update for my note 3 (over 100mb) it gives that error "Process Error". Back in xposed repo time, when I was having issues downloading the modules from the in-app repo, I was visiting the online web repo from my computer and download those apks flawlessly. But not with Magisk, as for me the source of all these Zip modules files is unknown.
[Magisk] Didgeridoohan:
https://duckduckgo.com/?q=magisk+repo

And the process error usually means the Manager doesn't have storage permission or that the MagiskManager folder is missing from the internal storage. Those are bugs that shouldn't be an issue no more though, so either you're likely using an old release or you've got a new bug. Logs would be good in the latter case...
[Magisk] Marvino.:
After giving up on that latest xposed update, I tried downloading it for one last time after reading your post to provide logs but VOILA it worked and the download process was successful (It probably heard us). Old versions? Not my case. I'm sure my entire apps are updated all the time and the version installed on my device for Magisk manager is 5.6.4 (v16.0) and the related folder is created in the internal memory. For the permissions expectation, I checked the app perms and no problem, it's granted. I'll attach logs soon when this problem happens again. Thanks for ur support.
[Magisk] symbianvn:
Hi! I can't restore image from Magisk. It shows "stock image does not exist", how to solve this? don't want to flash boot via fastboot method with each OTA update.

Thanks!
[Magisk] Artim_96:
If it can't find it you obviously deleted the backup. Then of course you'll have to flash it manually
[Magisk] andrew2432:
Still need mount namespace and a kernel above 3.x.x for hide? I used to keep up with multiple methods but none of my devices used to have a kernel version that was supported. Lurking and messing around as always still.

Edit: 3.8 I maybe saw? Doesn't matter, I only have 3.0.101 available for the device I'm working on
[Magisk] UMU24013:
With Magisk 16 Samsung Music does not work. It quits with the error message: "Samsung Music is not supported to rooted device." Why?
[Magisk] guest4711:
Please see [MENTION=4667597]Didgeridoohan[/MENTION]'s famous guide at https://www.didgeridoohan.com/magisk/MagiskHide