yashsingh1/xdaforums huggingface dataset:
[Magisk] Team DevDigitel:
Running LG V20 7.0 May Sec Patch.

Updated From 0606 to 0611.

0606 was causing viper4arise module to not be able to mount/driver abnormal status. This is fixed if selinux is turned off. This usualy is from the module not having rw access.

The 0611 build now can not pass safetynet as well the viper4arise bug atill2 exists.
[Magisk] Didgeridoohan:
Try the beta v13.0 (1777d9f). There was a bunch of fixes for Magisk Mount a few hours ago that are not in the 0611 build.
[Magisk] Sartharon:
You seem to have lots of errors

E( 5135: 5135) dup2 failed with 9: Bad file descriptor

E( 471: 7291) sqlite3_exec: disk I/O error

Dup2 is repeating over and over
[Magisk] Team DevDigitel:
Yeah constantly. I managed to go in and add a few things to hide list and it stopped and passed safetynet / calmed down. But modules not working specifically viper. Its a issue with how it see device in enforcing i believe

0606 didnt have this issue with magisk hide. But it also wasnt able to work with viper module.

0611 changes caused the repeat failues when enabling magisk.
[Magisk] mrtruckincowboy:
if you have install errors i would try downgrading twrp t o 3021 the Latest has been known to have instsll errors on some devices.

also if the boot is patched with su you need to use a stock boot. img that is not patched first then flash your kernel then magisk.
[Magisk] Team DevDigitel:
Unfortunately it was the same issues as before.
[Magisk] zerenco1:
Working smoothly

I am running Magisk V13 (Magisk-v13-170612.zip) and it works lovely.

My Phone: Samsung galaxy S7 "SM-G930F" Nougat.

Thanks for this lovely work!

A proof that is works. But Safetynet still sees i have root, but i don't mind, still beta. Still manages to use snapchat :)

[IMG="A proof that is works. But Safetynet still sees i have root. Still manages to use snapchat"]https://lh3.googleusercontent.com/MQ-_acqsSsYXOdQRuXgSW_sFsjTAc4Co5aulfGH_b5Zs4yG5cE3uaI4tYUpYOVVcw-VDqO92HTrEVXzYWOcbkdwngcA=s341[/IMG]
[Magisk] DenyDarko:
Can we please stop the posts about Safetynet and return to the beta testing thing?

It's a known issue, Google changed the method and topjohnwu knows it and will be probably fixed in the next beta.

I'm getting tired of notifications about new useless posts.

Please people.
[Magisk] ImjustSaiyan92:
Nonsense! We must keep blowing up the OP, asking and demanding for an update! How else will we get it?! This is Xda after all!!
[Magisk] lollyjay:
Hahahaha
[Magisk] JEANRIVERA:
This is just a merged newest magisk v13 beta with a working magisk manager apk while we wait for an official update from developer

https://xdaforums.com/attachment.php?attachmentid=4183222&stc=1&d=1497573624

If I was helpful please use the thanks button!!!
[Magisk] _litz:
I finally got around to updating my build setup, but now magisk fails to build. Stops with this error :

make: *** No rule to make target `jni/ndk-compression/bzip2/Android.mk'. Stop.

Can't find anything about this ... obviously it's trying to build support for bzip2 .. but there's nothing online anywhere about how to provide it that. anyone know how to fix this?

---------- Post added at 11:43 PM ---------- Previous post was at 11:12 PM ----------

Appears the github download was corrupted. Had to wipe the whole directory and start over, after a new git clone, it appears all files are present.
[Magisk] Akhilesh S V:
I tried flashing Magisk 13 zip in recovery but I'm getting some error

Tried flashing stock boot.img but still the problem persists

Device- Nexus 6

ROM- Nitrogen OS
[Magisk] JEANRIVERA:
Try this one
[Magisk] candiesdoodle:
Works fine. Dirty flashed over v12. Nothing else to be done. Modules continued to stay on
[Magisk] computercarl:
Can someone smarter than me, make a build of the latest beta of 13 (the one w/ the SN bypasses and such) for the Pixel / Pixel XL (The whole A/B partition stuff)?

Thanks!
[Magisk] stangri:
Small update: my home router has crashed and I've lost access to the machine the build script runs on (yeah, I run it on my home computer, was too lazy to set up a cloud VM for builds) and I won't be able to fix it until early July. Given that [MENTION=4470081]topjohnwu[/MENTION] has started posting beta-builds himself, maybe it's for the best -- I'd encourage people to switch to the builds posted by [MENTION=4470081]topjohnwu[/MENTION], but if you insist on living on the edge -- the build script (working on macOS and Linux) is on the github, please share your builds either in the thread or by requesting access to the github repo.

PS. And again, thanks to all the people keeping this alive by reporting back, helping others or posting new builds -- it's the XDA community at its best!
[Magisk] leosnake347:
im using magisk on zuk z2, and some apps are not with root. i cant acess my files on flud or airdroid.
[Magisk] kantjer:
I would be interested to hear from other builder if they are still able to build using the build.py script.

My last successful build was 0614 but since today I'm no longer able to build MagiskManager.

build log
[Magisk] _litz:
I built it last night at midnight without issue, fresh code pull, too.

Sadly, it does not fix the persistent magiskmanager-loses-root issue.
[Magisk] ridobe:
I tried to build last weekend but I have been struggling to get my environment set up.
[Magisk] jenslody:
Exactly the same errors here (since yesterday, didn't try for some days).
[Magisk] dahawthorne:
[MENTION=4317549]_litz[/MENTION]

A senior member posts 20 screens of previously posted text. Really?
[Magisk] _litz:
Yeah, oops ... was in the middle of 5 different things at work.

Someone evidently edited it, to fix, so thanks.
[Magisk] Bloodgod:
I've had updater error 0 happen with different builds of magisk not exactly sure what went wrong. But it did delete the system partition luckily I backed everything up before flashing. For the record I have never used magisk before but I did follow all the instructions making sure to read them again a few times before hand in order to not make any errors. Is it possible that it just doesn't work for the Pixel XL/Marlin yet?
[Magisk] Lockheed95:
Hello, i'm sorry but i've a problem when i want flash magisk v13, i've Error : 1.

I've uninstall v12 with uninstaller and unroot my Note 4.

I've Also flash clean boot image but always the same issue

An idea ?
[Magisk] kantjer:
I fixed it by adding the following to the top of my build script

export LC_NUMERIC="en_US.UTF-8"
[Magisk] jenslody:
That works, thank you.

Default is "de_DE.UTF-8" on my system.
[Magisk] kantjer:
By adding it to the build script you can keep your system settings as is
[Magisk] kantjer:
For those who want to live on the edge, you can find my builds here

I use my own key to sign the MagiskManager.apk so you will need to uninstall your current MM version (use Titanium Backup to restore MM data afterwards if you want to keep the app and SU settings.

My build has fully working update notification also downloading and installing via MagiskManager is working for the snapshot builds.
[Magisk] ridobe:
Outstanding. The 17th build works great. Thanks for this.
[Magisk] _litz:
I'm becoming increasingly convinced there is some kind of fatal flaw in MagiskManager.

I can no longer keep the app running literally past an app switch. Switching to another app, screen off (sleep), anything ...

The INSTANT the manager app loses focus, it gets killed by the OS, and all SU functions then fail.

Basically, to do anything, you have to swipe-right the app to kill it off, and re-run it from the desktop icon. Then it loads fine ... until it's no longer in the foreground, then the whole process repeats.

This has consistently gotten worse and worse as the v13 devleopment process has moved along, to the point where now, MagiskSU/hide is almost no longer usable.

It's a monster hassle if you want to open Pogo, pay with A-pay, etc ... anything ... you have to kill and restart the manager app FIRST, then try your operation ... and pray you can get it started before the OS kills the manager app and you lose SU/hide capabilities again.
[Magisk] _litz:
Also, build.py is busted on Windows :

* Building Magisk Manager

'.\gradlew' is not recognized as an internal or external command,

operable program or batch file.

Build Magisk Manager failed!

Someone patched this (or somesuch) so it no longer works on Windows, since it's explicitly looking for .\gradlew, which doesn't exist. In windows, it's gradlew.bat, found via path inside the SDK

Edit: git is not correctly updating the SUB-project for MagiskManager. You can't properly freshen it ... I had to wipe the entire directory and re-clone.

Edit #2 : Magisk is no longer installable on a Moto X Pure.

Fails with Magisk Image Mount Failed, error 1
[Magisk] _litz:
Also fails on Nexus 9.

Installs without error, but all systemless functionality is not working.

Cannot run adaway, cannot install busybox, etc etc.

(yes, tried on a factory fresh to ensure no contamination; still fails)
[Magisk] _litz:
The MagiskManager "loses root" issue is seemingly (at least partially) solved with the Memory Locker app, using it to (at least help) prevent the system from killing the manager app ...
[Magisk] d3nni:
This seems like exactly the same problem I have.

I alao have a Note 4, running 6.0.1 TW Stock and I just flashed Magisk v13 without any errors. But the MagiskManager saying that Magisk is not installed even if it is. If I install Xposed Systemless then he recognised Magisk is installed.
[Magisk] Wesley_NL:
Guys i have a problem

On my sm-g928 f with khongloi v11 it dont want to install i waited 15 min but it wont contineu, seems screenshots failed because i forced shut down and reflash v12 magisk again
[Magisk] jenslody:
There is a tracker for known workarounds to some of the v13 beta issues: https://xdaforums.com/apps/magisk/beta-workarounds-to-issues-magisk-beta-t3624176

Your issue will most likely be fixed with the updated zip by @Nodens .
[Magisk] john270:
Hi,

Any fix to getting (any) module to work and keep SafetyNet? In v12 I passed SafetyNet with Viper and Audio Buffer modules installed. I then upgraded to 0612 v13 and immediately failed SafetyNet. I've reverted back to v12 but can now not pass SafetyNet no matter what I do with that version. Only time I can pass SafetyNet seems to be v13 but with no modules.

I've tried installing modules via Magisk Manager and also TWRP but both have same result.

Samsung Note 3 - RRN 7.1.2 - Synergy Kernel

Thanks!
[Magisk] guest4711:
Google has changed something so safety will fail on magisk12 or on some configurations of 13.

See https://www.xda-developers.com/new-...is-now-available-and-it-can-bypass-safetynet/
[Magisk] Wesley_NL:
I use that one
[Magisk] Ragarianok:
There's a module for that!

https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431

I believe it only works with v12, however.
[Magisk] john270:
Thanks but I tried that last night. I am at least able to flash that module and keep safety net (in v13, no other modules) but still have same issue as soon as add any other module. Tried installing it before and after other modules but always ends up with safety net fail

---------- Post added at 12:05 PM ---------- Previous post was at 12:02 PM ----------

Anybody able to describe how to use magisk_mount flashable? Mentioned as possible fix to issue with modules but it has instructions inside the update.binary that I can't follow
[Magisk] maximesharp:
I just install LineageOS 14.1 on my Galaxy S5 (sm-901f) and try to install Magisk Manager.

I flash the lastest Magisk v13 (zip and apk), the phone reboot correctly, but if I reboot my phone another time, he get stuck with bootloop.

update : So, after a clean and fresh install (wipe data/system/cache), Magisk don't cause me anymore bootloop, until I switch on MagiskHide.
[Magisk] djelectron:
Love Magisk! On beta 13 using ViperU on my HTC U11. So far so good now, but having an issue with lastpass. It only works in core module only mode. I've tried Magisk Hide on it with no luck. I am successfully passing safety net. Ideas?
[Magisk] djelectron:
Sorry. Posted here since I'm using the beta. Searched before posting. Should this go in the Magisk General Support / Discussion thread?
[Magisk] Captain_Throwback:
This isn't the Beta thread...
[Magisk] DodoGTA:
This is the beta thread: https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Magisk] FreeTheWeb:
Can't install it on SM-G925F stoock firmware BTU wit 7.0 and it was the same on nemesis room

It stuck in ''-Constructing enviroment''

Sorry i noticed that is not the beta thread later
[Magisk] Nye-uhls:
Check out the appropriate thread here https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/page135

The comment by [MENTION=571197]Nodens[/MENTION] says exactly what to do, worked perfectly for me.
[Magisk] Deep-Knight:
Xiaomi Redmi4x MagsikHide wont work

Magisk Hide wont work. Crash Message.

Redmi4x 7.22

SETPROP seems to be right. Any ideas ?

--------- beginning of main
D( 423: 423) client: connect fail, try launching new daemon process
I( 424: 424) Magisk v13.0(54e6a79) daemon started
D( 424: 425) sepol: Starting large patch thread
I( 424: 426) ** post-fs mode running
--------- beginning of system
D( 424: 425) sepol: Large patch done
I( 424: 675) ** post-fs-data mode running
I( 424: 675) * Mounting /data/magisk.img
I( 424: 675) * Running post-fs-data.d scripts
I( 424: 812) ** late_start service mode running
I( 424: 812) * Running service.d scripts
D( 424: 812) resetprop: New prop [ro.magisk.disable]
D( 424: 812) resetprop: setprop [ro.magisk.disable]: [1] by property_service
--------- beginning of crash
D( 424: 5551) su: request from client: 9
D( 424: 5551) su: request from uid=[10258] (#1)
D( 424: 5552) su: collector started
D( 424: 5551) su_db: query root_access=[1]
D( 424: 5551) su: wait_result waiting for 5554
D( 5554: 5554) su: child process started
D( 5554: 5554) su: use namespace of pid=[5543]
D( 5554: 5554) su: argc=[2]
D( 5554: 5554) su: argv[0]=[su]
D( 5554: 5554) su: argv[1]=[-v]
D( 5554: 5554) su: cwd=[/]
D( 5554: 5554) su: pts_slave=[]
D( 424: 5551) su: return code to client: 0
D( 424: 5578) su: request from client: 7
D( 424: 5578) su: request from uid=[10258] (#1)
D( 424: 5578) su: wait_result waiting for 5580
D( 5580: 5580) su: child process started
D( 5580: 5580) su: use namespace of pid=[5555]
D( 5580: 5580) su: argc=[1]
D( 5580: 5580) su: argv[0]=[su]
D( 5580: 5580) su: cwd=[/]
D( 5580: 5580) su: pts_slave=[]
D( 424: 6544) su: request from client: 9
D( 424: 6544) su: request from uid=[10258] (#1)
D( 424: 6544) su_db: query root_access=[1]
D( 424: 6544) su: wait_result waiting for 6546
D( 6546: 6546) su: child process started
D( 6546: 6546) su: use namespace of pid=[6529]
D( 6546: 6546) su: argc=[2]
D( 6546: 6546) su: argv[0]=[su]
D( 6546: 6546) su: argv[1]=[-v]
D( 6546: 6546) su: cwd=[/]
D( 6546: 6546) su: pts_slave=[]
D( 424: 6544) su: return code to client: 0
[Magisk] gil80:
Can anyone get Viper4Android working on latest beta build?
[Magisk] Captain_Throwback:
Seems like everyone is confusing this thread with the Beta thread...

[MENTION=2226076]stangri[/MENTION]

Maybe you can add a disclaimer at the top of the OP to alleviate some of the confusion?
[Magisk] LPW00:
Isn't the [UNOFFICIAL] in the title obvious?
[Magisk] Captain_Throwback:
Clearly it isn't, because people are posting in this thread thinking it's for the Beta. Maybe people think "unofficial" and "beta" are synonymous. Just because it's obvious to you and me doesn't mean it is for everyone else.
[Magisk] stangri:
Done! In the future, you or any other mod should feel free to modify the OP content to reflect up-to-date information.
[Magisk] AndroidON:
Don't know why, but Magisk v13 is conflicting with Moon reader app.

Moon reader app works well with v12, but it just freezes when I install v13.

Was on Galaxy note 3, 6.0.1 Marshmellow touchwiz.

Would you please fix it? Thanks :D
[Magisk] loocool2:
Are there any big differences between this unofficial and the beta as of now? The GitHub doesn't really say anything.

Edit. Seems like, as of now, this and the beta are exactly the same, with the latest commit (54e6a79) being the latest beta release and the latest unofficial release.
[Magisk] dahawthorne:
Moonreader Pro works perfectly on my latest Magisk v13.

Nexus 6, Pure Nexus June.
[Magisk] kantjer:
Functionally the official beta and my builds are identical

The only difference is that in my builds the update check is working for both Magisk and MagiskManager. Also MagiskManager will always show you the last available beta version.

If either Magisk or MagiskManger is older than the version on my git you will be offered to download and install the update via MagiskManager.
[Magisk] dannycellestio:
the irony
[Magisk] w20grippy:
build Magisk-v13.0-170624 is not passing safety net with rr on Mi5.
[Magisk] kastik4:
in magisk 12 there was an option within the app to keep force encryption and dm verity how enable them in magisk 13?
[Magisk] Didgeridoohan:
They're still there, right on the status page.
[Magisk] kastik4:
yea but when i click it it say download magisk 12 not the 13 :p:p
[Magisk] TaifAljaloo:
Yes it can in my case with galaxy note 4 you have to enable system less hosts and core thingy and re check for safetynet
[Magisk] eried1:
Would it be easy to rectify? Annoying that you can't reset battery stats. I only want to charge to 80%, but have to charge to 90% to restart the battery monitoring.
[Magisk] Gazzasore:
I have Traders ROM on my Note 3 n9005

Jairus980 (Xenial latest kernel

And Magisk v13

Everything is running perfect
[Magisk] Judson1975:
I just updated magisk 13, same time I upgraded my aicp rom. Now I can't get safety net to pass...
[Magisk] Benny100:
Lol install magisk 13 all ok safetyNet

Restart Phone magisk safetyNet Not OK
[Magisk] swa100:
So you have the same problem? The command still works on adb, so I'm doing that every once in a while..
[Magisk] HamsterHam:
Yeah, same here. I am using [MENTION=3306843]kantjer[/MENTION] build and it seems the latest version doesn't seem to pass for me on a reboot. Temperamental when it passes.
[Magisk] Trilletralle:
Flashed magisk om ny oneplus 2 running ASOP extended ROM. Everything seemed to be working fine. Root access, magisk hide and everything.

However, the Facebook messenger app would just freeze. Tried uninstalling the app, clearing data and everything, but noting worked. So I flashed the magisk uninstaller, and everything went back to normal. Does anyone have a fix for this?
[Magisk] JEANRIVERA:
there are new commits on magisk github that hasn't been posted to the official beta could it be possible to make a new unofficial build? [MENTION=3306843]kantjer[/MENTION]
[Magisk] DodoGTA:
https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post72944486
[Magisk] alvinputrabjn:
Thank
[Magisk] unknown:
I try this magisk build on cm 12.1 and face bootloop

Any help ? :D:D
[Magisk] Didgeridoohan:
Flash uninstaller/Restore your stock boot image.
[Magisk] unknown:
I know . I like to use this build :o:o

Any way to install it on cm 12.1 ? :D:D
[Magisk] kantjer:
Done
[Magisk] Judson1975:
Just finally got 13 to pass. It worked fine b4 it updated, but when it did I couldn't get it to pass regardless what I did. I just went into settings and cleared the repo cache and it works now

---------- Post added at 06:26 PM ---------- Previous post was at 06:08 PM ----------

And my tablet just rebooted and doesn't pass anymore, even clearing that cache
[Magisk] DEVILOPS 007:
Is this version more updated than the one DodoGTA did? I mean with more of the recent commits and changes on github? Thanks.
[Magisk] ridobe:
Yes. This one is run daily, but only if there has been a commit.
[Magisk] Hyflex:
Mine isn't showing the latest one as built? Last build was 30 days ago
[Magisk] ridobe:
Do you have this one installed and do you have the check daily toggled on?
[Magisk] MultiKoopa:
Anybody here use FlashFire, and try it with Magisk 13? I had Magisk 13 from a few builds ago installed, rooted with MagiskSU. No modules installed.

I just tried this out, but with magisk 13 and the July security patch OTA: http://i.imgur.com/dRWj5nc.png

it completely failed in every way. still on the June security patch, not rooted, and magisk isn't installed.

Anybody got any ideas why it failed so spectacularly?
[Magisk] Didgeridoohan:
Try putting your stock boot image at the top of the queue. A normal OTA won't work with a modified boot image. If that doesn't work, try adding the stock recovery as well.
[Magisk] MultiKoopa:
Hmm. I know FlashFire finds a backup of the boot image each time. I'm not sure how to find it myself...
[Magisk] Didgeridoohan:
The Magisk installer puts a backup of the boot image in /data (stock_boot***.img.gz). If you haven't flashed anything else (custom kernel) prior to Magisk, that one should work.
[Magisk] MultiKoopa:
found it! thank you! but how long does this work? I mean, would the upgrade from 7.1.1 to 7.1.2 have stopped this boot image backup from being usable?
[Magisk] Didgeridoohan:
As long as you flash Magisk after the update it'll make a new backup. So, no worries...

Edit: but yes, don't flash an old boot image to your new OS. That's asking for trouble.
[Magisk] MultiKoopa:
man I'm slow tonight lol

magisk was flashed after the July security patch, so it made a backup then. I'll use that next time, then flash magisk after the next OTA, and it'll make a new backup

thanks for being patient :P
[Magisk] HamsterHam:
[MENTION=3306843]kantjer[/MENTION], safetynet passes on your latest build on a reboot! ? Cheers dude.
[Magisk] aamadorj:
I confirm unofficial Magisk-v13.0-170709 is free of the magiskhide issue: it starts properly at boot. Thanks to [MENTION=4470081]topjohnwu[/MENTION], [MENTION=3306843]kantjer[/MENTION] and all the team supporting Magisk.
[Magisk] Kyuubi10:
Hey guys, before reporting a bug in the official thread... Just want to know if anybody is aware whether the following 2 bugs have been solved, or work around has been found:

1) All installs through Magisk manager are failing.

2) MagiskHide is unable to unmount soundfx folder.

(issue appears with Atmos module from [MENTION=5357345]ahrion[/MENTION]).

This being said, for issue (1) I am unsure which log I'm meant to post, I'd be grateful if anybody could help me.
[Magisk] pavan3999:
i'm getting magisk not installed on my redmi 3s
[Magisk] paed808:
Not for me, still have to manually toggle it. Not sure which log to provide.

Edit: See post below for logcat.
[Magisk] paed808:
Edit: Attached is logcat.
[Magisk] kantjer:
Funny, I never had the issue myself but it started on this build.

A simple MagiskHide toggle fixes it.
[Magisk] HamsterHam:
Odd - both your 9th and 10th builds pass SafetyNet on a reboot.
[Magisk] inffy:
9th and the 10th build also work here after reboot and safetynet reports pass [emoji848]
[Magisk] abacate123:
I also report back that both 09 and 10 builds are working as it should when it comes to safetynet and hide.
[Magisk] PeterImmel:
Where can I download latest snapshot? Can't build myself
[Magisk] inffy:
Well there is a clear link in the first post...
[Magisk] PeterImmel:
Sorry, didn't see the zips in mobile web view
[Magisk] kantjer:
a simple Tasker hack fixed it for now
[Magisk] Kyuubi10:
BUMP
[Magisk] espionage724:
With July 9 and 10th unofficial Magisk builds, if I install them, I lose Developer Options. If I use the latest and previous builds of Magisk V13 beta, no such problem occurs. In both cases, Magisk installs and works fine (with the caveat of the latest official beta needing the Hide toggle).

Anyone know why this is and how I can fix it?
[Magisk] Didgeridoohan:
It's probably because [MENTION=4470081]topjohnwu[/MENTION] have added a bunch of ro.build props back to Magisk Hide. Your issue would be with ro.build.type. Some ROMs don't show Developer options if it's set to user (needs to be userdebug). I'm not sure if there's anything you can do about it at the moment, except disable Magisk Hide or go back to an earlier build. I've asked on GitHub why he brought these props back to Hide, considering it can bring issues like this...