yashsingh1/xdaforums huggingface dataset:
[Magisk] Romaan:
I am having some issues. I flashed the latest version "Magisk-v16.5-20180627-ianmacd.zip". Everything was working fine for many days. However, I installed Xposed Systemless and as expected saftey net failed and after testing some of the new modules I wanted to test I uninstalled Xposed. Once my device rebooted saftey net still failed. I then went and uninstalled Magisk completely and failing still occurred. I wiped all my data and re flashed a clean rom and saftey net still failed. I then wiped and formatted everything again and flashed stock rom and saftey net still fails. I have even run the unbrick tool and saftey net still fails. What has happened to my device to make it fail no matter what I do?
[Magisk] Tecalote:
This has nothing to do with Magisk, but with Xposed Framework.

Try to make a factory reset from settings with wipe of internal storage (not factory reset from TWRP - TWRP should not be installed to clean up your Firmware)
[Magisk] Romaan:
Thanks for your help. I have managed to get safteynet to pass.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] Is invincible mode back in todays build? I don't see mention of it in the changelog.

Thanks
[Magisk] kantjer:
AFAIK it's part of Magisk.

Don't see any Magisk commits pushed yet. I check later and push a new build.
[Magisk] Ferbee:
[MENTION=7187684]ianmacd[/MENTION] I'm quite certain that the loss of root bug is fixed

As per the screenshot
[Magisk] ianmacd:
Sorry, but I don't understand how the attached screenshot demonstrates this.
[Magisk] Ferbee:
Oh sorry, I've had the device in for they many hours and haven't lost, is what I was trying to get at
[Magisk] martyfender:
My thoughts, exactly.
[Magisk] jenslody:
Device uptime in screenshot.
[Magisk] martyfender:
Topjohnwu posted this on Twitter a few hour ago:
[Magisk] martyfender:
Sorry, it was hard to read, even on my desktop computer. I just don't understand why dark modes are so popular. They make it an utter nightmare to read for my 60 year old eyes, even with bifocals!
[Magisk] kantjer:
The issue wasn't fixed, you were just lucky.

I had root loss a few days ago.

Weird thing I had 4-5 days without root loss and then twice in one day

Hopefully it will be fixed in the upcoming release.
[Magisk] Ferbee:
Ah that's fair, I'm 17 so I don't have those problems...

And the black just looks better for me
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION], I was just wondering if [MENTION=4470081]topjohnwu[/MENTION] provided you with any information concerning the root loss issue based on the logcat you provided him? There have been very few commits recently but supposedly he is getting close to a release.

His most recent post on twitter:
[Magisk] kantjer:
A few things are rewritten and I'm running an internal test build and it's stable as rock for me.

There are a few last things to fix (not root loss related) but as far as I can tell a release is close.
[Magisk] aer0zer0:
Was just going to chime in: I'm running your 7/4 build on essential ph1 with P beta 2 (=pixel dp4). It has been great for me. No issues to note.
[Magisk] topjohnwu:
I didn't push the latest code to Github, as I want some "surprise" factor to releases LOL.

There are some sweet stuffs up in my sleeves, you will see them very soon........ :D:D:D:D
[Magisk] armando_rod:
The beta is up now https://xdaforums.com/showpost.php?p=77014053&postcount=43

https://github.com/topjohnwu/Magisk/releases

Flashed the beta on top of Kantjer 180614 build and it was giving errors with the Pixel Imprint setup, crashing Settings.

Flashed the uninstaller, reboot, flashed beta again and is all fine now
[Magisk] 587.saboor:
Ok does anyone know what the update channel url is?
[Magisk] radz_:
If you are using the unofficial version even you change Beta Channel in Magisk Manager, you wont get a notifications. I suggest download the latest beta magisk thread.

I also recommend flash the latest uninstall zip from topjohnwu to prevent issues.
[Magisk] 587.saboor:
I still want unofficial updates though without the hassle of finding them and flashing from twrp so i can flash directly from magisk
[Magisk] neekless:
https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json

it's on kantjer's github
[Magisk] kantjer:
https://github.com/kantjer/MagiskFiles/blob/master/README.md
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] I just downloaded 180708. Am I correct that there are new commits in it since v16.6 beta was released?

Thanks
[Magisk] ianmacd:
Nothing has yet been committed to the official repo since the release of 16.6.

My own 180708 build just bumps the version number, provides a custom change log (culled from the GitGub commits), and continues to include the 64 bit binaries.

Much the same is probably true for [MENTION=3306843]kantjer[/MENTION]'s new build. He's probably just providing continuity for his users.

---------- Post added at 16:36 ---------- Previous post was at 16:34 ----------

Not so. If you use a custom update channel with an unofficial build, you will be notified when a custom update becomes available.
[Magisk] martyfender:
Sorry, I was confused, because [MENTION=3306843]kantjer[/MENTION] 's changelog for 180708 has a much more thorough listing of all of the changes [MENTION=4470081]topjohnwu[/MENTION] made vs. the ones he posted for the changelog in the op of the beta thread. My mistake.

---------- Post added at 01:49 PM ---------- Previous post was at 01:08 PM ----------

I have updated all four of my Nextbook Ares 8A's to the [MENTION=3306843]kantjer[/MENTION] 180708 build and all of them seem to be performing very well. One thing I notice is that when I launch a root app, the toast granting access appears a little faster.

The only minor problem I encountered, was when I installed the MagiskManager-180708.apk, on the 4th device and launched it the first time, it froze on the splash screen. I have encountered this quite a few times, randomly, in testing new, beta and stable builds.

What almost always solves this for me is to run the manager.apk installer a second time, without uninstalling it. I think it is just a peculiarity of my particular device. This minor problem, as I stated only occurs randomly, not all of the time.

I always uninstall the current manager first. I was on 16.6 beta and Magisk Manager 5.8.0.

I then launch the newly installed Manager, set up the custom channel, then use the direct or module install method to update Magisk, itself to the latest snapshot, then reboot.

Great job [MENTION=4470081]topjohnwu[/MENTION] on another superb release and thanks to all of you that release these community builds to help further in the testing of bug fixes and feature enhancements to make Magisk great.
[Magisk] kantjer:
Two reasons for that, the official (beta) changelog gives a readable overview of changes.

My changelog lists all new commits since my last build, one change can consist of more than one commit.

Also I pull, what in the original source are external submodules, direct from the source so it can be for those external tools I pull have new commits not in the official build (yet).

Most of the time those commits from external source have little or no consequences for the working off Magisk or Magisk Manager.

In my manifest you can see all source I use.

As you might have seen, I also added the used NDK version to the changelog when you check it in MM.
[Magisk] nguyentankiet:
Have not uninstall file of your build?
[Magisk] abacate123:
Latest uninstaller for kantjer's magisk build here. If that's what you want.
[Magisk] nguyentankiet:
ianmacd included arm64, but official and kantjer uninstall is not. You think they working?
[Magisk] ianmacd:
The uninstaller indiscriminately removes all of Magisk's directories, so it will remove whatever's in them, including any extra binaries that may happen to be present.
[Magisk] nguyentankiet:
Thank for info
[Magisk] radz_:
[MENTION=3306843]kantjer[/MENTION]

I just received an update notif for 0711 build, is this an updated version of the official beta 16.6? What is the base of this update?
[Magisk] kantjer:
it a derp, I'm testing new changelog format.

Sorry for that, just ignore.

This is what I'm thinking off, don't mind the contend, that's fake

https://github.com/kantjer/MagiskFiles/blob/master/updates/changelog.md
[Magisk] martyfender:
The latest I see is 180710.
[Magisk] kantjer:
I reverted the derp commit
[Magisk] MiltonJames:
#SaveDerp

:)
[Magisk] deepu458:
Hi [MENTION=3306843]kantjer[/MENTION],

I just wanted to let u know one thing that was missing from last 2 versions of MM app. That is the option of long press on the manager app is now not showing all options as it used to show in the padt. It's now showing me the superuser option only now, before it used to show all 5 like downloads, modules, superuser, hide, etc. Is this something u know of this change or missed while making the update
[Magisk] nguyentankiet:
Delete
[Magisk] neekless:
Works here on 180710 version.
[Magisk] deepu458:
As the earlier user mentioned after clearing the data of Magisk Manager and reboot now it shows fine to me.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] As usual your recent builds have been working great for me.

One thing I noticed though, is that the magisk_debug.log is not being updated any longer. It shows a date of 6/27. On one of my 4 devices I deleted it and rebooted and it was not recreated. Is this expected behavior with recent builds?

Thanks
[Magisk] kantjer:
debug.log is replaced by magisk.log, you can find that in the cache folder.
[Magisk] SpectraFun:
After booting i get a Android-System popup with 16.6 and newer builds from here. With 16.4 all fine.
[Magisk] hshah:
I'm an even happier bunny than before... RootBeer says no root, Sky Go and Barclays Banking apps work, not losing root... loving my Note 8 at the moment :)
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] I want to report an issue with 20180715. On one of my Nextbook Ares 8A's Android 6.0.1, after installing it through either the direct install method or through TWRP, upon reboot it stuck on the boot animation for about 4 minutes. eventually it does boot up. When I try to open any root app there is no denial of root message, the apps are usually just stuck, checking for root access. When I open System Monitor the cpu is at about 85- 95% all of the time and only the max of 1.9GHz. in addition, apparently there is rapid battey drain. Restoring to 2018713 solves the issue. I will try to provide logs when I can, later.

Edit: Upon restoring 20180713, I realized that on Greenify 4.1, I had to enter to grant root in it's settings and re-enter all of the previous settings I had. It had lost them all, including my icons for it and the sleep and hibernation shortcuts on the desktop. It is installed with the Greenify4Magisk module v4.1.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] [MENTION=4470081]topjohnwu[/MENTION]

180715 logs attached.

WOW! I did not realize until I uploaded that the magisk.log is ~596 megabytes uncompressed!
[Magisk] 587.saboor:
cuz it is looonnnggg af
[Magisk] kantjer:
How is the situation on today's build. Your entire log is flooded by one error message. No idea what's causing it.
[Magisk] martyfender:
I just installed 20180716 and it has the exact same issues as 20180715. Last night I installed 20180715 on one of my other Nextbook Ares 8A's and I have the same issues.

I once again reverted to 20180713 and all is well again. I could try the Magisk uninstaller.zip and a fresh stock boot.img, if you think that might make a difference.

Edit: I tried the magisk uninstaller.zip and a fresh, stock boot.img and still have the same result. Also I forgot to mention, previously that MM freezes at the splash screen even though that new version works when Magisk 20180713 is installed.

One or more of the new commits in the 20180715 apparently is causing this issue on my devices.

I attached the install log before I removed Magisk and flashed the stock boot.img. Magisk and recovery logs were attached in a previous post. Also, magisk log with 20180713. Note an error at the end of it that I don't see on 2 out of 4, other Nextbook Ares 8A tablets with 20180713 installed. Magisk. Log renamed.
[Magisk] mkdante381:
Unofficial build 180704 work with Sysconfig Patcher module, but from 15, 13 July and maybe from older, problem with install in magisk manager. When is installing in twrp this module doesn't work. This is possible to fix this? I need ZIP installer from 10 July and older ZIP to testing
[Magisk] Didgeridoohan:
[MENTION=5228676]VR25[/MENTION] looks at the loopback devices to find the Magisk mount point. That part of Magisk has changed as of 170706:

https://github.com/topjohnwu/Magisk/commit/1283167595270b848df5d954fb41fa8daf46de23

Those modules need to be updated for future compatibility, but unfortunately it seems like [MENTION=5228676]VR25[/MENTION] has been preoccupied with life outside xda for some time now...
[Magisk] ianmacd:
A fix for this was just committed:
[Magisk] martyfender:
Thanks, Ian. I read the commit but do you know what wrap accept4 means? A command?
[Magisk] ianmacd:
accept() is a system call, i.e. a function provided by UNIX kernels, to accept a network connection on a socket. accept4() is a non-standard system call on Linux that extends the functionality of accept().

Although Android is basically Linux, it seems that some devices come with kernels that don't provide an accept4() system call, so Magisk's developer has had to fall back to accept() instead, and wrap the invocation of that function in code that mimics the extra functionality of accept4().
[Magisk] martyfender:
Thanks, again, Ian for clarifying that for a non-progammer. That is the kind of comments I would like to see with code, but considering the time, and extra work, I understand why many don't do this. It is, of course better to devote ones valuable time to the actual coding and bug fixes, which topjohnwu seems to be doing very well. Thanks, [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] ianmacd:
You're welcome. I appreciate the desire to learn the things one does not understand. Every healthy human mind possesses this quality.

Did the change fix your problem?

I haven't built with today's code — I don't necessarily release a new build every day there is a change — but I can compile one if you need it.
[Magisk] kantjer:
Can you please test todays build and check if the issues is fixed.

You are the only users reporting this issue so we need you to test the fix :)
[Magisk] radz_:
Hi man, your release is the updated version of 16.6 right? I'm confused..[emoji23]
[Magisk] kantjer:
It's a snapshot build with all the latest commits.

These builds can add new functionality or fix bug buts also introduce new bugs.

Keep backups when using snapshot builds (I think you should always keep backups)
[Magisk] SpectraFun:
Is Android-System warning popup after booting fixed with latest build?
[Magisk] guest4711:
Always running kantjer's latest build. Never had this issue. But try it yourself and report..
[Magisk] SpectraFun:
I have this message with latest 3 Builds on my Oneplus 6. With 16.4 all fine.
[Magisk] radz_:
Anyone having issues with the latest build from kanjer?

Whenever I update it, after boot, It says Magisk is not installed?

16.6 works fine
[Magisk] kantjer:
Did you remove MagiskManager before flashing my build? The signature is different so you need to remove MagiskManager first when coming from a different build.
[Magisk] Didgeridoohan:
From your post history I'm going to guess you have a Oneplus 5T, maybe even with the Treble Open Beta. If so, it's a known issue and will be fixed.
[Magisk] martyfender:
Yes that fixed my problem. I am now installing kantjers build on a third device.

Thanks
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] [MENTION=4470081]topjohnwu[/MENTION]

I installed it on all 4 of my Nextbook Ares 8A's and it is working great so far.

I have attached both the magisk.log and magisk.log.bak, so you can see the error in even 20180713, versus no error in the build 20180717.

As you my recall, the major errors were from the 20180715 and 20180716 builds, fixed in todays build.

Thanks, again.
[Magisk] radz_:
Yeah I removed Magisk Manager first, but I guess my issue is related to this post below..

Yeah 5T. Latest OB with treble. So latest gmhas issus with treble?

16.6 works fine though..
[Magisk] Didgeridoohan:
If you're going to be flashing snapshot builds of current unreleased code you're going to have to expect issues. Much more so than with the official beta...

The issue you're experiencing will be fixed. Stay on previous builds or the official releases until then. Keep an eye on [MENTION=4470081]topjohnwu[/MENTION]'s GitHub to see what's going on.
[Magisk] joluke:
What's your link for the magisk manager apk?
[Magisk] guest4711:
You will find the link in the custom update channel https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json

The url of today's build is https://github.com/kantjer/MagiskFiles/raw/master/MagiskManager-20180717.apk
[Magisk] xXCoolGuYXx:
Is this the link I put in the update channel - custom - link - ?
[Magisk] guest4711:
Yes, for sure (the url of the json-file).
[Magisk] bggold:
[MENTION=3306843]kantjer[/MENTION]

Any thoughts on how to fix the issue that devices bootloop randomly after a reboot? Usually a two finger salut once resolves it.

Thanks
[Magisk] kantjer:
If you think the reboots are Magisk related we need much more info including logs.

Without that these kinds of posts are useless.
[Magisk] kantjer:
You will find all the links and info here
[Magisk] bggold:
You got it I will grab them next time it happens.

Thanks
[Magisk] martyfender:
https://twitter.com/topjohnwu
[Magisk] kantjer:
And I think I know why :D
[Magisk] martyfender:
I'll bite, why?
[Magisk] ianmacd:
It's in the Twitter thread that [MENTION=3306843]kantjer[/MENTION] linked to. Basically, the submodules are an inconvenience requiring extra work, so they're best left for linking in external projects, rather than for managing sections of one's own code.

Some people are already reporting problems with OnePlus devices on 16.7, so watch out for that.
[Magisk] kantjer:
Uploaded todays build again, this new build should fix the issues on OnePlus and Huawei devices.

If you already updated to today's build, download and flash the zip again.
[Magisk] radz_:
deleted.
[Magisk] ianmacd:
I've somewhat reluctantly updated my own build system today to allow for multiple builds per day, although I shall try to avoid making use of this facility whenever I can. ;)
[Magisk] kantjer:
I also promised myself not to make multiple builds per day. Broke that promise today :)
[Magisk] martyfender:
You get that in MM when you are not connected to the internet.
[Magisk] neekless:
[MENTION=3306843]kantjer[/MENTION] [MENTION=7187684]ianmacd[/MENTION] since both your builds are updated to latest source would you guys say your builds are identical? is there any reason to choose one over the other?
[Magisk] martyfender:
[MENTION=7187684]ianmacd[/MENTION] 's builds also contain 64 bit binaries that [MENTION=4470081]topjohnwu[/MENTION] removed a while back. This is from Ian's github repository readme:

I believe topjohnwu made a commit to avoid that misidentification, recently, if I am not mistaken, though.

Furthermore, I believe that both builds should function properly on both 32 bit and 64 bit devices, again, if I am not mistaken. I am sure if I have any of this wrong, [MENTION=3306843]kantjer[/MENTION] or [MENTION=7187684]ianmacd[/MENTION] will set it straight.
[Magisk] ianmacd:
If the 64 bit binaries are no longer needed, I will remove them. At that point, the only notable difference between my builds and [MENTION=3306843]kantjer[/MENTION]'s would be in the cut-off point at which the build was executed. In other words, one build on any given day might contain commits that the other didn't, and the next day the other build might be slightly ahead.
[Magisk] SpectraFun:
Test latest 16.7 and 19. build and on both i get Android-System popup after booting. With 16.4 all ok. Can you fix this please?
[Magisk] kantjer:
No we can't.

We could pass on the issue if we had more info

Check this great Magisk and MagiskHide Installation and Troubleshooting guide by [MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] Didgeridoohan:
Do you mean this (from the OP of the release thread):
[Magisk] SpectraFun:
My english is not so good. I mean this: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"

---------- Post added at 11:23 ---------- Previous post was at 11:22 ----------

Yes thanks. My english ist not so good.
[Magisk] Didgeridoohan:
Just follow the instructions and restore the image and then reinstall Magisk straight away, with the option enabled.
[Magisk] martyfender:
[MENTION=3306843]kantjer[/MENTION] [MENTION=4470081]topjohnwu[/MENTION] I just installed 20180721 on my 4 Nextbook Ares 8A's and upon reboot and subsequent reboots, I get a: Magisk Manager has stopped message dialog on startup.

Attached is a logcat filtered for Magisk Manager, in Logcat Extreme and the magisk.Log, for one of the 4 tablets.

On one of the reboots of the one tablet, I had it freeze on the boot logo, where I had to force a shutdown, then it started normally to boot to the Magisk Manager has stopped error, once again.

EDIT: it turns out that 3 out of the 4 tablets had the: Unfortunately, Magisk Manager has stopped error, on reboot.

On subsequent launches of Magisk Manager, after reboot the app works normally.

They are all Nextbook Ares 8A's with, I think the same hardware, the same Android 6.0.1 and kernel version, 3.14.64-x86_64, different date revisions of the rom and a different IFWI (Intel Firmware Interface) version.

This is strange, but I like it: on one of the newer tablets, the Magisk Manager icon was installed on the desktop, like other apps that are installed?

EDIT: On one device, I deleted the app cache and data re-entered settings and the error may be gone. Further tests are needed, though. EDIT: Error on boot is still there. I have Kernel Aduitor and lspeed apply on boot settings. The error seems to pop up when lspeed is executing it's apply on boot script. may just be a coincidence?

I tested again, first booting to TWRP and deleting cache and dalvik cache and got the error again when lspeed was showing it's apply on boot notification, which show a progress bar and takes a few seconds. I saw something related to this in the beta thread, when scripts were being applied.

The above info is provided as a bug report in the interest of furthering Magisk development.

In the future, if I can do anything different to make my reports better, please let me know. Sorry, I do most of this from a Linux desktop and it may not be mobile friendly. I only use mobile when I have to, like when I am working, on breaks and testing Magisk.

Thanks
[Magisk] kantjer:
Are you running any wake lock blokkers?

AndroidRuntime: java.lang.RuntimeException: Unable to start service com.topjohnwu.magisk.services.OnBootService@c0712b1 with Intent { cmp=com.topjohnwu.magisk/.services.OnBootService }: java.lang.SecurityException: Neither user 10105 nor current process has android.permission.WAKE_LOCK.
[Galaxy Grand Prime Q&A, Help & Troubleshooting] dougr33:
Hi all I just bought a galaxy grand SM-G530AZ phone, and when I try to set it up it gives me the Samsung error that a abnormal update had been used

every time I try to load a rom on it with Odin it gives me a R/L error best I can tell G530AZTUS4BOJ7 is the full model of my phone, I really need the 4.4.4

original rom for G530AZTUS4BOJ7, thanks in advance
[Xperia Z5 Compact Q&A, Help & Troubleshooting] madshark2009:
Guys is it me or do all xperia phones take too long optimizing apps every time casche and dalvic are cleared... I owned plenty of htc phones. Usually 1.5 ghz -1.9ghz are so fast!! I mean usualy in the htc , it took like litteraly 20 seconds to 1 minute to optimize 300+ apps , our xperia phone ,also the z2 and i tried , take forever! Even when overclocked , and they over heat so much so quickly!! Can any one explain to me whats up

Thanks