yashsingh1/xdaforums huggingface dataset:
[Magisk] martyfender:
https://github.com/ianmacd/MagiskBuilds/tree/master

To install, you must first uninstall your current version of Magisk Manager only, first, since it is signed with a different key and will not install over your current version.

Once the new Magisk Manager is installed, in settings, set the channel to ianmacd to install that version of Magisk.
[Magisk] zgfg:
Ok, I will try, but for now I wanted only to test this MM - may I keep Canary Magisk?

Also, Modules as installed, Superuser and Hide apps - will they remain as already setI for official/Canary MM (is this build sharing the same DB)?

And this latest MM muat be this

https://github.com/ianmacd/MagiskBuilds/raw/master/MagiskManager-v7.3.3-2019062101-ianmacd.apk
[Magisk] zgfg:
Actually, testing now with the official v7.3.2, 224, and there is no more crash when opening Superuser :)

Thx for the fix
[Magisk] guest4711:
Yes, they use the same database and modules. So you need to exchange MM only.
[Magisk] martyfender:
The stable 7.3.2 is currently at the same commit level as the unofficial version, so you can stick with it, also.
[Magisk] guest4711:
I use 7.3.3 by IanMacD.
[Magisk] armando_rod:
Has anyone had trouble using the stable version on Android Q beta 4? Everytime I flash it doesn't boot, it boots after 4 or 5 hard resets and with errors, it takes 1 minutos to open apps and everything is slow
[Magisk] Tornado15550:
Latest nightly seems to be bootlooping me to the bootloader on the latest Q beta. Fix is to simply flash the factory boot.img and the system will boot as expected. Will perform a clean flash and report back. The issue persists on a clean flash too. Rolling back to 2019062101.

Device: Pixel 2 XL

Platform: arm64

OS: Q Beta 4
[Magisk] joluke:
Give [MENTION=7187684]ianmacd[/MENTION] build a try. His repo is this: https://github.com/ianmacd/MagiskBuilds
[Magisk] gorilla p:
I initially noticed the download repo wasn't loading when checked today. I closed, cleared cache and reopened and it looked like magisk manager auto updated and it showed up. I thought that was weird.

Applied today's update on my OP6 running latest stock OOS. Rebooted, went through boot animation, entered pin, looked like UI was gonna load, then black screen . Had to power down. Reverted to previous version and it's working OK again.
[Magisk] bggold:
Pixel 3 xl running AquariOS rom. With todays build (19.4-2019062601-ianmacd) swift installer no longer works to update, remove or add themes. If I go back to the previous build it all works fine. I even tried the switch magisk module and that did not help. Anyone else having this issue?

Thanks
[Magisk] martyfender:
[MENTION=7187684]ianmacd[/MENTION] I want to thank you for all of your recent builds. They have been working great, so far.

I see you reverted your most recent commit:

Update to support updated FrankeNDK

Did you have issues building with that commit or with the updated FrankeNDK?
[Magisk] ianmacd:
Yes, John made a change to his BusyBox build in light of some finding he made yesterday. He said this discovery will allow him to update the FrankeNDK to mostly newer files.

However, I couldn't build with this change, even after updating my FrankeNDK to the latest in GitHub (because John hasn't packaged a new release of it yet).

It'll get figured out. For the user, however, the difference is invisible.
[Magisk] martyfender:
As can be expected from time to time, I am having issues with this latest build: 2019071501.

Upon random rebooting, sometimes it shows Magisk is not installed. On other reboots it shows as installed. Some apps are forgetting that root was previously granted for them. Core only mode is sometimes enabled and service.d scripts in /data/adb are not always being run.

Reverting to the previous build from the 8th solves it.

Has anyone else had issues with this build: 2019071501? I haven't yet tried the Magisk uninstaller to see if that solves it.

2019071502 solved the issues.
[Magisk] guest4711:
Did not test it because I was out of office. Now 2019071502 is available. Flashed it and did not see such issues on my ARM devices.
[Magisk] guest4711:
Thanks for new version 2019071601.

Edit: Please ignore the following. My fault. Restored magisk.db and forgot to restart...

Magiskhide does not work for me, even after toggling it off and on. Tried with clean install, nope.

Testing on a spare device. Will not update my daily device.

(Logs will follow, but wanted to inform those who love the bleeding edge.)
[Magisk] mkdante381:
Hi, I'm using ianmacd build, maybe this bug is on other builds. Magisk repackaging not work properly. This Install Manager and after open "Magisk is not installed". Pls fix this. In old builds repackaging work, but app on adopted storage detect root and all settings for Magisk Manager reverted to default.
[Magisk] guest4711:
What did happen to todays changelog?
[Magisk] Golf c:
He can't fix anything. Only one person can fix it.
[Magisk] martyfender:
Yes, I wondered myself, what was changed in this build, since I didn't see any new commits by tjw on his master channel.

Thanks
[Magisk] jenslody:
Most likely a more recent busybox, so just internal changes.
[Magisk] ianmacd:
Yes, sorry about the lack of a changelog, but no actual code changed in the superproject on that day. The changelog is auto-generated, but I should add to my build script the ability to override the changelog in special situations.

The two releases that day were to update BusyBox (the submodule had got stuck at 1.29.x) and to move to a newer version of John's FrankeNDK, the upshot of which is that Magisk is now compiled with clang, not gcc.

Since that day, you will have noted a lot of new changes, as a lot of Victor's new MM code has been merged, allowing, for example, the user to define his own download location.
[Magisk] bggold:
[MENTION=7187684]ianmacd[/MENTION] I just tried updating mm from within mm from today's build 02 to 03 and it says it installed successfully but when I open it 03 stills shows as an update. Tried a few times and same thing. Tried to get logs but when I go into logs for mm it freezes and wants to fc. Haven't been in the logs for a few builds so don't know if it has been like that or is new in 02.

Thanks
[Magisk] guest4711:
Logs are showing on 02 but a had to wait a long time (on first try I got a timeout warning but after selecting 'wait' I got a list displayed.

Will try again with 03.

Edit: When updating a repacked MM from 02 to 03 a normal MM is installed (it's not prepacked before installing). So you'll have to Managers.

Edit2: Restoring (unpackaging) MM does not work, too.
[Magisk] hshah:
[MENTION=7187684]ianmacd[/MENTION], as per the above, the latest update tries to install a non hidden MM so if you aren't paying attention you end up with two MMs installed.

One of the changes is how MM is downloaded so may be linked to that...
[Magisk] bggold:
[MENTION=7187684]ianmacd[/MENTION] I do not hide mm.
[Magisk] hshah:
Apologies for assuming. Definitely something wrong with installing a new MM though :silly:
[Magisk] bggold:
I agree. No apologies needed.
[Magisk] hshah:
Also both update links on the initial MM screen are for MM... top one is usually the zip.
[Magisk] ianmacd:
John fixed a bug and the fix went into 03, but 02 has the bug, and that's what you're seeing. Just pull the 03 MM apk by hand and install it.
[Magisk] bggold:
That did it.

Thanks
[Magisk] martyfender:
Before I read all of this, I had the same problem, so I downloaded MM 03, uninstalled MM 02, then installed mm 03 and hid it and all worked fine, except I had to redo most of my settings. that was on 3 devices. No problem, this is why we like to test cutting edge build. It is nice to have a challenge once in a while. Those that disagree should stick to a non rooted device or the Magisk stable version.
[Magisk] hshah:
Whenever I uninstall MM to switch between normal and hidden, I always lose all the su grants, selected items on the hide list etc.

Any way to update the current hidden MM I have to restore the normal version without losing settings?
[Magisk] ianmacd:
Could you not have simply installed 03 without uninstalling 02? Did you do it that way for a particular reason?
[Magisk] guest4711:
No, 03 does not replace 02 if 02 was hidden... But you don't lose much this way because magisk.db keeps untouchedwhen uninstalling Manager...
[Magisk] martyfender:
I did it because mm would not update to 03 even though it showed it had installed successfully, it had not. The only way was to uninstall 02 then install 03, then hide it. That was on 3 devices. I've never seen this kind of behavior before. Maybe this was because mm was hidden?
[Magisk] hshah:
Strangely enough I just uninstalled the hidden 02 MM and then reinstalled 03 MM.

The only configuration missing were changes under MM Settings (ie update channel, toast notifications etc).

I was convinced that the times I've done that previously, I've lost su and hide items.
[Magisk] ianmacd:
That would have been some time in the past. More recently, all of your important settings are stored in a database that persists, even when MM is removed. It would now take the full removal of Magisk itself to destroy these settings.
[Magisk] martyfender:
On three devices, MM crashes when checking safety net, with today's build, 2019080802. The solution on each device was to delete MM's data and cache in Android settings, apps. I am also getting frequent, Magisk Manager isn't responding. do you want to close it? messages after startup. Has anyone else experienced this?

Thanks
[Magisk] hshah:
Everything has been unusually quiet lately... guessing people are busy and there have been no updates, but just checking in lol :)
[Magisk] martyfender:
2019082201 has been released.
[Magisk] hshah:
When trying to update to the latest MM via MM, it says the installation package cannot be parsed.
[Magisk] martyfender:
[MENTION=7187684]ianmacd[/MENTION] I just tried to install today's release and I get the parse error, also. My MM is hidden. I have not yet tried to flash the new version of Magisk because of this error in installing MM.

I just unhid Manager and MM did eventually install. I had to change back the update channel to ianmacd, hide MM and then I was able to download the new magisk.zip and flash that in TWRP. So far, everything seems ok. By the way, I had to change the update channel back again to ianmacd, after hiding MM.

The same method works on my other 2 devices with your build. The parsing error is only happening on a hidden MM.
[Magisk] guest4711:
No problem upgrading from 2019081202 even with MM repackaged (Android N).

But error (on O) upgrading from 2019082201. Had to unrepackage MM as [MENTION=8126387]martyfender[/MENTION] described to get it working. No problem repackaging MM again.

So probably an issue of 2019082201.
[Magisk] hshah:
As suggested, I just unhid MM which updated it to the latest version and then rehid it :)
[Magisk] martyfender:
2019083101 has the same issue
[Magisk] hshah:
Yep, and the same "workaround" works :)
[Magisk] sdeft:
I noticed that in latest Magisk 19.4 2 directories are created in /data/app as per below

1. com.topjohnwu.magisk-7jUFCuZUkTyxd_4DKQVUlw==

2. vmdl713955882.tmp

Both directories contain the same base.apk which is Magisk Manager. However only one app is shown in Launcher.

What is the purpose of the tmp directory ?
[Magisk] guest4711:
2019090101 too... (and the same workaround).
[Magisk] martyfender:
When I download apps from the playstore, the installer is downloaded to a temp directory in: /data/app, before it is installed. The temp dir is usually deleted after a successful install, I believe.
[Magisk] guest4711:
I cannot install modules anymore - extracting failes. Apparently /system/bin/unzip does not support -j switch but it is called instead of /data/adb/magisk/busybox unzip -j

Anyone else seeing that issue?

- Copying zip to temp directory
- Installing MagiskHide_Props_Config-v4.0.3-v63(47).zip
unzip: invalid option -- j
usage: unzip [-d DIR] [-lnopqv] ZIP [FILE...] [-x FILE...]
! Unable to extract zip file!
! Installation failed
[Magisk] Didgeridoohan:
That's currently being investigated internally. For some reason the Magisk Busybox applets aren't populating and it's then reverting to using the toybox unzip that doesn't have the -j option.

Are you by any chance seeing this on Android Q with Karisakura kernel? That's what has been found to cause it so far.
[Magisk] sdeft:
Doesn't look like it is deleted. It is permanent.
[Magisk] Freak07:
I doubt he’s on my kernel, because I didn’t share it.

Could you maybe tell us your setup as detailed as possible?
[Magisk] guest4711:
No, I'm on android P, arm, running Havoc 2.8 on klte, clean install without g-apps.

https://xdaforums.com/galaxy-s5/unified-development/rom-havoc-os-t3894305/post78775672

I"ll try to flash magisk again from TWRP and see whether busybox applets are populated...
[Magisk] Didgeridoohan:
They're populated at each boot, so a reflash might not have any kind of effect (and if it does it might be just temporary).

Seeing your Magisk log would of course be interesting...
[Magisk] guest4711:
Neither uploading as zip, txt or including it into the post worked. So I'll try to pm it to you...

Edit: This should be the relevant part of log:

05-20 11:33:18.365 377 378 I Magisk : * Setting up internal busybox
05-20 11:33:18.381 383 383 E Magisk : execve /sbin/.magisk/busybox/busybox failed with 26: Text file busy
05-20 11:33:18.382 377 378 I Magisk : * Running post-fs-data.d scripts
[Magisk] Didgeridoohan:
That is indeed the relevant part and the same thing seen in other logs from users with the same issue.
[Magisk] jcmm11:
Just for the heck of it what happens with official Canary rather than this version? And if it does work correctly reboot 2 or 3 times and see if it continues to work.
[Magisk] guest4711:
Just tried. Same problem with canary-debug, even if not repackaged. Error 26: text file busy.
[Magisk] jcmm11:
Doesn't surprise me. Just FYI cause is unknown as of now. Problem appears non-consistent. At least one person doesn't display the problem. 2 other people do have the problem. Sometimes. Occasionally the problem goes away after a reboot, just to return a reboot or 2 later. All 3 have basically the same configuration.

This is not on Oreo or 32 bit though. It's on Q, 64 bit. For the moment it's a mystery. I can tell you how to work around the problem, but it's not a solution. Create a script in post-fs-data that, if they don't exist, properly populates the busybox applets.

Or just install modules using FKM or EXKM. Or wait for TWRP to support Q for your device.
[Magisk] guest4711:
Not a big problem, I use mixplorer to copy the modules in place. But I don't understand why Magisk needs the applets. Why not calling "busybox unzip" instead of "unzip"? The first one will work in all cases while the second one does not if applets are not created...
[Magisk] hshah:
Same issue again whilst trying to update MM when it is hidden...
[Magisk] guest4711:
And the same solution - unhide, install update, hide...
[Magisk] hshah:
Yep, just exactly that. Apologies for not mentioning that... assumed that it was a given and I was focusing on stating that the problem was still present.
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION], [MENTION=7187684]ianmacd[/MENTION]

I just upated MM and for me the problem is partially solved with today's build. MM installed, but it was not hidden and I had to change the update channel back to ianmacd after I hid it manually.

On a second, same, device, older rom build number, I had the same parse error as before, so I must use the same method as mentioned by me and others to fix it: restore MM, change the update channel back to ianmacd, hide it and change the update channel back to ianmacd, again. And, of course, restore my Android desktop shortcut for Manager.
[Magisk] guest4711:
Not to forget: Adding Magisk Manager and Manager to AfWall rules and allowing storage access... ;)
[Magisk] carlos974:
Hi,

This link does not work :

https://github.com/ianmacd/MagiskBuilds/raw/master/MagiskManager-v7.3.3-2019090501-ianmacd.apk
[Magisk] guest4711:
What does not work? Just tried it: MM has been downloaded ( https://github.com/ianmacd/MagiskBuilds/raw/master/MagiskManager-v7.3.3-2019090501-ianmacd.apk ).
[Magisk] carlos974:
I have this message:

"Unable to connect to the server at raw.githubusercontent.com"

No way to update on my pc and my phone :confused:
[Magisk] martyfender:
Do you have an ad blocker that could be blocking it on your end? If so, you may have to whitelist that address.
[Magisk] carlos974:
This is my operator, I tried with another operator it works

Thanks
[Magisk] martyfender:
What do you mean by operator? There may be a translation problem.
[Magisk] carlos974:
Internet provider !

Sorry
[Magisk] martyfender:
John made a commit to fix the issue with the hidden manager, however, the issue is still there, so I reopened the issue:

https://github.com/topjohnwu/Magisk/issues/1834

Are others still having this issue also with [MENTION=7187684]ianmacd[/MENTION] build 2019091001?

Thanks
[Magisk] carlos974:
No for me !
[Magisk] guest4711:
For me it's working on arm (klte) after granting the right to install from unknown sources. MM still hidden.
[Magisk] martyfender:
My mistake, it is fixed in the new update. However, you will still have the error going from the old version to the new version. If you update mm again, you will see that it is fixed.
[Magisk] martyfender:
Everything is working great on today's version, but the text is too tiny and hard to read on my 8" tablet
[Magisk] ianmacd:
Distribution of ianmacd builds ceased at John's request

[MENTION=4470081]topjohnwu[/MENTION] has very politely asked me to cease the distribution of my unofficial Magisk builds. 2019092201 is the final release.

John explains:

I've witnessed first-hand that some users will report bugs in the ianmacd builds against John's official GitHub tree, or in the official XDA threads, and one doesn't need much imagination to understand how this would get on his nerves. Not only are bugs reported in the wrong place, sometimes even omitting the fact that an unofficial build is being used, but often the bugs themselves are ghost bugs, present only in my builds of bleeding edge, work-in-progress code that John never intended anyone to run in its interim state, and which are fixed before the next Canary release.

Once upon a time, my builds would include a small feature or two not found in the official builds, but in recent months, my Magisk repo has all but converged with John's, and the only difference between my builds and Canary now is that I am sometimes a few commits ahead with my releases; often leading to the ghost bug scenario outlined above.

So, although I know a few people will be saddened by this announcement, you shouldn't feel too down about it. Not much will actually change for you. Just reconfigure your Magisk Manager for the Canary channel and move on. John is committed to regular Canary releases.

Do bear in mind that you will have to uninstall my build of Magisk Manager in order to move to builds signed by John's key. This is a one-time inconvenience.

I thank everyone here for using and supporting my builds. Most of all, though, I would like to thank John for giving Magisk to the Android community; and, equally importantly, for having the benevolence to protect the code under the GPL, ensuring that Magisk's future can never be inextricably tied to any one party, even its creator.

Long live Magisk.

P.S.

I forgot one thing: Please be respectful of John's wishes in this matter and don't bother him about it.
[Magisk] mirfatif:
[MENTION=7187684]ianmacd[/MENTION] thanks for your contribution, and hopefully you won't cease it, one way or the other.
[Magisk] topjohnwu:
As said by [MENTION=7187684]ianmacd[/MENTION], please migrate and report issues in the official canary thread.

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

Thread closed as this is no longer relevant.
[Magisk] flipside101:
Hi, Im having reboot issues when I enable Magisk Hide. Its the same across 11,1 and the newest build of 12, any suggestions and what logs would help?

Im running a Sony Z3 Compact

Unlocked Bootloader

Custom ROM based on Stock Sony MM Rom
[Magisk] Deic:
Is the same for all, if you flash version 170304 and 1710316 after all is fine, seems the new boot img tool of topjohnwu is not completed..? report it in https://github.com/topjohnwu/Magisk , this thread is about unofficial snapshot builds compiled from official repo, so here nobody can help to solve that issue
[Magisk] Mozziliac:
Alright, thank's so much.

Thanks for linking me over :)

For who's interested in following
[Magisk] ahrion:
The 3/16 version causes bootloop in OP3 Lineage OS 7.1.1
[Magisk] Mozziliac:
This is on OOS ~ so it must be something with the zip
[Magisk] Captain_Throwback:
There was a problem with MagiskBoot that [MENTION=4470081]topjohnwu[/MENTION] recently fixed, as I was having a similar error on one of my devices. I'm not sure if he pushed the fix yet.
[Magisk] _Nexus8_:
Hello ! Snapchat won't work on my Galaxy S6 with Griffin ROM installed (Android 7.0)

I think Magisk Hide doesn't work at all

I'm using Magisk v170316 and Magisk Manager v5.0.170312

I already tried to flash Magisk Manager Updater Snapshot v3.2.2 but it didn't work either

Does someone knows how to fix Snapchat/Magisk Hide ?
[Magisk] Artim_96:
For Snapchat: it can only detect something if you log in. So just make a backup with titanium and restore it on every new Snapchat installation. And of course never log out.

For Magis, does it pass SafetyNet or RootBeer sample?

Otherwise we will definitely need some logs
[Magisk] Deic:
What you mean Magisk Hide or Snapshot updater not work?

Provide logs of both /cache/magisk.log and /data/magisk/magisk-manager-snapshot-updater/updater.log
[Magisk] android_htc:
Finally got it working again, did a clean install, but initially missed the prompt to install the app. Manually installing it seems to remove the installed app upon reboot?

Received prompt this morning and installed app and now it is working, see screenshot (still old icon on notification). But is seems to be not checking for the latest Magisk v12 updates?

Edit: I guess everything is okay correctly, as I have also installed the latest Magisk module! Thanks
[Magisk] stangri:
Today's (3/18) build is a forced build from the same source files as 3/16 build, no upstream changes.
[Magisk] LazerL0rd:
PLEASE, PLEASE don't do that. It does work for Snapchat. I'm using it right now. It works for some apps and it'll be a shame to remove it...
[Magisk] A$h!$h:
is there any app like Sensor disabled apk.. for magisk.. now its only work on xposed
[Magisk] Artim_96:
No. You would need to find out I it's controlled by a special file and replace it with an empty one.

But if there is something for XPosed, the chances are very low that it can be done with Magisk, they are just way too different
[Magisk] Johnmy212i:
Can someone help me to solve the cts mismatch error?

I'm using the latest version on nemesis v3.1 rom.
[Magisk] Didgeridoohan:
Gonna be hard with the small amount of information you've given... I'm gonna make an assumption though and guess you're using a Samsung device. In that case, you might need to also change permissions on a couple of files related to SELinux. Go to this thread, scroll down to the Hiding root post and look for the "Samsung..." heading:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] Johnmy212i:
Oh sorry about that. Yeah you guessed it right, I'm using s6 flat.

Problem solved, thanks for your help. :D
[Magisk] KatariaMax:
Guys how to bypass safety net I am able to pass basic integrity just not safety net I mean cts profile

This is log I was not able to upload properly so did it as a zip

http://cloud.tapatalk.com/s/58cff81f71c10/magisk_error_20170320_210948.log.zip

Here screenshot

http://cloud.tapatalk.com/s/58cff870912db/Screenshot_20170320-210938.png?
[Magisk] Johnmy212i:
Have you tried to change the enforce and policy permission?

How? Look at my post above you
[Magisk] KatariaMax:
Um sir I am Samsung can I change enforcing and I will see policy changes