yashsingh1/xdaforums huggingface dataset:
[Magisk] dr.ketan:
[MENTION=4470081]topjohnwu[/MENTION]

Here logs for two (only) critical bugs found with magisk 16.6 on Samsung Note8 (running on oreo 8.0 SELinux enforcing stock kernel)

1.Couldn't create .core directory if clean install (log attached below). I know you are recommending to update via manager but you can understand issue with ROM developer.

EDIT : Probable this happened because I have manually installed Magisk when doesn't get appeared after clean install ROM

1.Magisk get installed after clean install but doesnt appear in drawer before reboot or taking too long to appear in drawer, if reboot once before it appear, it launches bit faster on second reboot. Once appear, no issue in subsequent reboot. (log attached)

2.Random freeze and reboot with some apps asking root access in serial. Mostly experienced like script to copy files/directory and subsequently giving permission etc (log attached)

- freezing and reboot issue get fixed if flashing 16.3 but that 16.3 have only one bug is mysteriously losing root access

- On 16.3 there is no clean install bug nor required to delete/comment out bootsigner

Thanks for amazing work.
[Magisk] Didgeridoohan:
You say that the issues are fixed by flashing v16.3, but that clean install log is from v16.3(1630)... The issue looks to be present in the log, so I just want to clarify.

Is it that the issue is present on v16.3 as well, but you can fix it by reflashing v16.3?
[Magisk] dr.ketan:
Sorry for not being clear

- I mean no such issue with 16.3 with clean install

- Freeze and random reboot gets fixed if we reflash 16.3

PS : Edited reported post now.
[Magisk] Didgeridoohan:
Thanks, but I'm still a little confused... And more than a little nitpicky. :silly:

In the Magisk log you provided, the first few lines look like this:

07-16 08:34:59.475 3227 3227 I Magisk : link: /sbin/.core/mirror/vendor <- /sbin/.core/mirror/system/vendor
07-16 08:34:59.475 3227 3227 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
07-16 08:34:59.475 3227 3227 I Magisk : bind_mount: /sbin/.core/mirror/bin <- /data/adb/magisk
07-16 08:34:59.475 3227 3227 I Magisk : * Setting up internal busybox
07-16 08:34:59.475 3231 3231 E Magisk : execvpe /sbin/.core/mirror/bin/busybox failed with 2: No such file or directory
07-16 08:34:59.475 3231 3231 I Magisk : Magisk v16.3(1630) daemon started

Plenty of errors about "No such file or directory", but I also noted the last line from the part I extracted above.

Magisk v16.3(1630) daemon started

How does that compute with your statement that there's no clean install bug on v16.3?
[Magisk] dr.ketan:
Oops my bad, recalled it now, Actually I was playing with kernel init, and that's because of that but it's same. Don't worry i will reproduce with clean 16.6 to remove any confusion. wait let me clean install rom and will provide log again but that surely remain same except version name.
[Magisk] dr.ketan:
Sorry for confusion

I have updated post now with correct log
[Magisk] dr.ketan:
[MENTION=3306843]kantjer[/MENTION] [MENTION=4470081]topjohnwu[/MENTION]

here log for freeze UI (as described in post #5922 above) on 17July built unofficial magisk by kantjer
[Magisk] salimskiy:
Hello. Can you help? I can not find a solution to this problem anywhere. After installation, Magisk flies imei, delete magisk, imei restores. On 7.1.1 everything was fine. At 8.0 such a problem. Samsung Galaxy A8 + 2018 (8.0) security patch July 1.
[Magisk] fex42:
In the Mi6 / LOS15.1 thread are various links to treble aware TWRP and Magisk to download.
[Magisk] djsolidsnake86:
hi to all, i have a redmi note 4x with latest twrp, i can install magisk from twrp?
[Magisk] Artim_96:
The first installation has to be through TWRP
[Magisk] ultradj83:
S9+ - Bootloop with 1662 upon SD card reinsert

Dear [MENTION=4470081]topjohnwu[/MENTION] [MENTION=8369284]topjohnwu Magisk Queries[/MENTION] ,

this is just to inform that Galaxy S9+ with Magisk Beta 1662, removing and reinserting SD card goes bootloop.

It's a Galaxy S9+ SM-G965F with firmware G965FXXU1BRF8_CL13792060_QB18608589_REV01.

Steps to reproduce:

Shutdown

Eject SD card

Boot system

Insert password to unlock storage

Wait for application optimization upon boot

Work normally

Shutdown

Insert SD card

Boot system

Insert password to unlock storage

Application optimization endelessly completes and restarts

No way to fix other then to flash stock firmware and reinstall Magisk.

It doesn't boot also without SD card.

Magisk Uninstaller fails (maybe because of encryption).

I'm so sorry but having storage encrypted and disabled USB debug I'm unable to provide and logs or further information.

Thanks and best regards
[Magisk] xLuciferSx:
Hi everyone. I was trying to hide root from banking app called - Vanqiuis. But it still detects root. I checked Magisk log and it says - com.ie.vanquis.interact.shell - Permissive detected. Hide the state. Is it hiding root or not? Sorry for strange question.
[Magisk] chudy_85:
Do Google update safety net?? Yesterday I pass but now I can't. Can you check on your phones
[Magisk] casouzaj:
In general terms, you could launch either a terminal emulator application, or through an adb shell command in your PC (with your phone connected to it), and enter:

su

logcat | grep vanquis

By analyzing the results, identify the offending sub process(es), then, for each one of them, enter:

magiskhide --add enter_sub_process_name

Hope it works for you!
[Magisk] chudy_85:
I have problem it's hide I have gp certificate but problem with basic and cts. Now it's red.
[Magisk] casouzaj:
Try to Install module MagiskHide Props Config and reboot your phone.
[Magisk] akxak:
With Magisk 16.6 on Oneplus 6 with 5.1.8, 5.1.9 installed via local update in inactive slot, Magisk Manager does NOT offer to install Magisk into the second (inactive) slot.
[Magisk] DanGLES3:
Its been temporarely removed due to issues
[Magisk] akxak:
Wow... I did not notice that. Guess that caused problems for a number of people.
[Magisk] DanGLES3:
Its been removed less for issues itself but as the dev states magisk manager didn't properly support it
[Magisk] MiePx3:
I do not pass safteyNet with the latest Magisk as of today. Can someone confirm?
[Magisk] akxak:
Well, for me it did work flawlessly and made updates really easy and convinient. Luckily, I was at home with access to my PC when updating to 5.1.9 relying on that feature. Magisk did not earn trust with that move.
[Magisk] woozie.2007:
after the last update, the modules disappear, i installed again via recovery, but after each restart all of them disappear, i didnt have this issuea with previous magisk manager
[Magisk] jenslody:
Logs (see OP) or it didn't happen.
[Magisk] chudy_85:
Google change something in safety net. When I don't install magisk I have green basic integrity but when I install it's red. We must wait for next update to magisk
[Magisk] jcmm11:
What device? What ROM? And, most importantly, where are the logs? No logs = no fix. It's working just fine for most people.

Also see https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] martyfender:
I am not having any problems with safety net, so it must be something else going on with your specific device.
[Magisk] chudy_85:
I don't know how and why it's fail. I back to v15.4 update to 16.0 and now work correctly.
[Magisk] adwaitatre:
Magisk is uninstall automatically on my oneplus 6 how to fix it?
[Magisk] koxalk:
I had the same problem in my Nexus 5x and I uninstall the app and magisk and after reinstall it again and I don't have problem now

Just uninstall magisk(zip+app) and install again
[Magisk] adwaitatre:
Tried not working
[Magisk] Paschfire:
Maybe try elaborating, what do you mean "Magisk is uninstall automatically"?

Have you tried simply rebooting the device?

On a side note;

Without providing the proper Magisk logs, logcats, or detailed information regarding your setup, steps you took during installation, there's not much anyone can do in helping you.

Read the OP section and follow the rules, guidelines, on reporting issue.
[Magisk] Genetik57:
[MENTION=4470081]topjohnwu[/MENTION] Magiskhide does not work with Pokemon Go (Magisk v16.6 + Magisk Manager v5.8.1) but work with Magisk v16.4 + Magisk Manager v5.7.0
[Magisk] woozie.2007:
the issue was fixed by flashing magisk 16.4, all modules are there even after reboot, so i think 16.6 is the problem, i have stock rom 7.0 moto g5
[Magisk] Costa02:
Works here though
[Magisk] Didgeridoohan:
You're using a beta release and posting in a beta thread. The purpose of which is to test things and post details and logs about any issues that arise, so that the developer can get a chance to fix said issues.

Without details and logs, no fix...
[Magisk] DanGLES3:
Anyone unable to install the 16.7 beta? It crashes magisk manager while extracting files
[Magisk] mitchdickson:
See the post immediately before yours.
[Magisk] DanGLES3:
Already solved,it was a OOM (out of memory error) i increased my phone's heap size and now it installed sucessfully
[Magisk] srt10coupe:
16.7 after installing Magisk boot automatically in fastboot, only fastboot or recovery can i use. my choice is back to 16.6.
[Magisk] mitchdickson:
Why can nobody provide details and logs?

These posts are absolutely worthless without them.
[Magisk] radz_:
Thanks for the update![emoji6]

FYI [MENTION=4470081]topjohnwu[/MENTION]

WiFi is broken with the latest Magisk in 5T treble device,.

Though I'm using custom kernel, not sure with stock kernel.

16.6 works fine.

Will pull out the logs after work..[emoji23]
[Magisk] BadAtDevelopment:
I'm using a OnePlus 5T. After updating from Magisk 16.6 to 16.7 through magisk manager my device reboots into fastboot. I am able to get into TWRP from fastboot without issue but I am unable to boot up my phone normally, it will just go straight back into fastboot.

For some reason I was unable to flash the magisk uninstaller successfully but I was able to flash the Magisk 16.6.zip without issue. This at least allowed me to get my phone back to the same state it was prior to the update. I have attached the update log from when I tried updating from 16.6 to 16.7.

EDIT:

In regards to the magisk uninstaller, I tried using the one that was on my phone already (Magisk-Uninstaller-20180429.zip). I checked just now and realized that there is a more current uninstaller zip available. I included this just in case that had something to do with why I wasn't able to successfully use the uninstaller.
[Magisk] Zackptg5:
Same here on my op5t. It's treble enabled but I'm currently on a non treble rom
[Magisk] Yanghbr:
16.7 BROKEN!

Do not download this version, bootloop to fastboot.
[Magisk] DanGLES3:
Its working fine for me
[Magisk] mitchdickson:
Great logs!!

Works great for me.
[Magisk] xwizard:
I'm on OnePlus 6, MagiskManager 5.8.0 -> 5.8.2 and Magisk 16.6 -> 16.7. Works fine for me.
[Magisk] Loercase:
I have the same problem as everyone else. Boots only to fastboot. Back to 16.6 for me.

Oneplus 5 OOS stable.
[Magisk] yung40oz84:
Don't post dumb stuff like this! Your not the Dev to be telling people not to flash it, and just because you have an error or bug doesn't mean the next person does. Furthermore, post logs if it boots to the bootloader
[Magisk] tikizondo94:
One plus 5t. Latest openbeta12 "treble". Latest 16.7 magisk, no wifi currently.
[Magisk] RowBan:
Just flash 16.6 to downgrade?
[Magisk] smartfaune:
Nexus 5X

Oreo 8.1

Latest 16.7 Magisk works great here
[Magisk] dandemonic:
Yes
[Magisk] Soooperstar:
Works for me
[Magisk] oriveradel:
It works on Huawei P20 pro, reminder every one, before you install new version use magisk uninstaller APK to remove old version.
[Magisk] mitchdickson:
Everyone else?
[Magisk] kjames2001:
Samsung galaxy S8+ sm g9550, installed Magisk 16.7,boots into system but automatically reboots after 2 minutes.
[Magisk] galaxys:
So far, 16.7 running good on my Pixel 2 XL!
[Magisk] mystifiyer:
#metoo
[Magisk] casouzaj:
Magisk v16.7, just like all previous releases, is running flawlessly in my Sony Xperia Z3 Compact phone, loaded with CarbonROM 6.1 (Android 8.1.0).
[Magisk] youyim:
ZTE Nubia Z17. Android 8.1.0. Latest 16.7 magisk, bootloop

View attachment magisk.log

View attachment recovery.log.txt
[Magisk] astracd:
I have same issue with OP5, went back to 16.6

will try to post log later...
[Magisk] Timmmmaaahh!:
As some others, I also had to flash v12.0 prior to installing v13.0b. I had flashed the uninstaller first, which caused an error in the v13.0b install. TWRP log attached! In the log: failed 13 attempt, successful 12 & successful 13.

OnePlus One | Resurrection Remix | 7.1.2
[Magisk] kantjer:
this issue is fixed in the source, I just tested it.
[Magisk] Fentadroid:
Good! I guess someone will build it soon :laugh:
[Magisk] aLexzkter:
I mean...when I had busybox installed I would loose root after a short while, making me have to flash magisk back again
[Magisk] Didgeridoohan:
And you have this problem on the beta release? On v12 and earlier version that's a known issue... But, as have been pointed out, busybox issues shouldn't happen anymore from v13.

If you're willing and able to help with testing, flash the beta and provide the necessary debugging information if there are issues (see instructions in the OP).
[Magisk] DawoodSahi:
So I uninstalled v12 on my xperia z2 running on lineage, flashed v13 beta, flashed some modules that I use and phone's on boot animation for a while now (around 8/10 minutes). Is it normal, should I wait more or revert?
[Magisk] m0_onriver:
hi, is there a way to uninstall topjohn's superuser in magisk and just use your installed supersu app?
[Magisk] immi803:
Same status with op3 oxygen
[Magisk] Ubimo:
Is this beta newer than snapshot v170415.zip?

Edit:

Flashed this beta, my phone takes a veeery long time at the boot screen "Samsung Galaxy S7 edge" powered by android. I had the same problems with snapshots after v170415.

And I have no root access with this beta. I'm on SuperMan Rom 2.5

Magisk error log attached. I can't find /data/magisk_debug.log

Edit1:

Latest uninstaller link does not work main magisk thread. Please provide uninstaller.
[Magisk] DodoGTA:
Magisk v13.0 is the first version of Magisk with Android O support
[Magisk] Ja_som:
Yes, know, I used unnoficial v13 and it was fine, but this official beta does not work, so I flashed the unofficial for now.
[Magisk] vkass:
Flashed on redmi note 3 pro aosp rom, everything works perfectly including the sound modules I use.
[Magisk] OttomanTR:
Report : Note 5 Khongloi Rom 7.0 Dont boot magisk v13
[Magisk] Fenvarien:
V13.0 beta works just fine on my OnePlus One with the latest Lineage OS build.

Uninstalled Magisk manager 4 and flashed V13 beta over V12 in recovery. :good:
[Magisk] abacate123:
Yeah, beta works fine as well here on my Moto X 1st gen, running LineageOS 13. Su works, safetynet passes, and all the other stuff.
[Magisk] koekoek91:
V13 beta also working fine on my Xperia XZ.

At first it gave an error in TWRP when flashing v13 beta, this was happening when first flashing the uninstaller zip to remove v12.

When flashing v13 beta on top of v12 without flashing the uninstaller first, the install went fine without issues.
[Magisk] topjohnwu:
Magisk v13.0 (0b4baad)

Hello, I added the excessive logging in the last minute yesterday, and it turned out crashing the whole daemon if users are using encrypted data :p

The new build fixed the issue, and added a new "namespace" options to MagiskSU. The changelog and release notes are updated, please check!
[Magisk] DodoGTA:
https://github.com/topjohnwu/Magisk/issues/225
[Magisk] topjohnwu:
I will remove the high RAM requirement, it was needed before when using the crappy Jack compiler, but not required now.

For the CMake part, I do not want to complicate the APK building process, so I'll stick with the official solution.

You don't need to always run the "build all" command, in fact, my beta zips uploaded here has binary compiled in debug mode, Magisk Manager compiled in release mode (in order to preserve signature so flashing the zip can upgrade the app). I had to do:

./build.py binary "13.0(XXXXX)" 13XX
./build.py --release apk
./build.py --release zip "13.0(XXXXX)"

If you want to skip the APK building part, you just need to place a pre-built APK into the folder "MagiskManager/app/build/outputs/apk", name the APK to either "app-debug.apk" or "app-release.apk", and call build zip with the corresponding flag.
[Magisk] Zenzfum000:
Moto G 2014 DU 11.5

Error 1 in recovery with latest beta
[Magisk] smartdetodos:
I do agree It.

It's a unavoidable breakpoint. We know It about the securities breach that a inadequate elevation in permissions can do It.

Everyone here choose "Google's standard certified security" versus "break on through"...

In my particular case, elevation of privileged is important to do a "real disaster recovery policy"... It's not enough the backup/recovery method available by Google Account backup.

imho in a future (soon) It will be propagate to others apps that works with DRM (Deezer, Spotify, Netflix, Apple Music, etc) or financial apps. I do understand their concerns (remember KNox?).

No more elevated privileges, no customizations, no personal choices. "1984 It's a reality"... George Orwell was a visionary...
[Magisk] Floydfire:
We are in 1984 since a bit of time now... I personally love magisk for the modules and because I like to root my device and tweak kernels settings. God, I've even bought Mario run. I don't use android pay and I feel pretty ashamed that in order to use a game that I've paid I need a mod that conceal root and that I've modded MY phone. I really hope that android doesn't become like the iPhone. Never liked the feel that they give you a "borrowed" phone.
[Magisk] carlylemiii:
Clear data for Google Play Store and then check the app's settings. Is your device showing as Certified?
[Magisk] bayran321:
Yes my device is showing as certified with safety net in green and I cleared data but netflix and mario does not appear
[Magisk] edzamber:
It won't be showed until you downgrade Magisk Manager to 4.33-31
[Magisk] ForgottenDude:
Try enabling hide for Play Store. That worked for one person that I helped.
[Magisk] Allstargaurav:
Yes and yes
[Magisk] bayran321:
I flashed the new beta and everything is ok. S5 mini SM-G800F, stock
[Magisk] jenslody:
[MENTION=4470081]topjohnwu[/MENTION]

Installing v13.0(b3da28e) fails with:

That happens because /system/lib64 exists on my J5, even if the OS is 32-bit, but has a 64-bit cpu.

Running magisk directly from shell works (help is shown correctly).

Installation works fine after changing 64-bit system detection to:

[ -d /system/lib64 ] && ENV='LD_LIBRARY_PATH=/system/lib64:/vendor/lib64:/system/lib:/vendor/lib:/sbin PATH=/system/bin:/system/xbin:/sbin'

I don't think it breaks anything, but I only tested it on my J5.

The only module I use is systemless xposed, but the module provided inside MagiskManager (87.1) fails.

After reboot the phone hangs in a boot-loop.

Flashing through twrp does not work either (boot-loop).

87.0 from material xposed-installer works.

By the way safety-net still passes (if xposed is not active) with playstore update from yesterday.
[Magisk] vdbhb59:
I agree with you mate, and am finding it real great to see your writeup. Such a command and real pickle! Nice.

Update for you mate: Renaming magisk does not work. So, yes that is not a workaround, nor does the Xiaomi module work.

Hope your injection will work, and awaiting next version.

Advice: Await for 39-41 hours from the time SN was upgraded, and then you will be higher on the chances of breaking it. In 51 hours, it should be completely old focused(SN).
[Magisk] Alcor1us:
Just for clarification: the "b3da28e" is not yet the fix for safetypass is it? And no that is not a wierd way of asking about an ETA. It is just confusing as there was a release today (14.06).
[Magisk] Toutatis_:
No, it's not.
[Magisk] smartdetodos:
dude .. lookup the changelog link at OP... will see it... :)
[Magisk] bednim:
Hi, I'm on galaxy s8+ exynos, stock rooted with Magisk. Uninstalling latest Beta results in constant boot to recovery.

Installing beta back on device sorts the issue.

Play store won't see apps/updates.

Thank you
[Magisk] AnkitGourav:
How to enable systemless busybox in Magisk v13.0 ?
[Magisk] RogerF81:
You need a busybox module for this.
[Magisk] Didgeridoohan:
Take a look in [MENTION=4544860]osm0sis[/MENTION] odds and ends thread (I posted a link earlier in the thread). He's got a flashable zip for a busybox that installs as a Magisk module.
[Magisk] dahawthorne:
I may have missed the answer - apologies if this has already been explained.

I uninstalled Magisk 12 by flashing the zip, installed ElementalX again, installed the newest Magisk beta, uninstalled Manager 4.3.3, installed Magisk from the apk in the v13 zip.

Now Manager shows version 5.0.1, shows Magisk 13 installed, but shows Magisk 12 as the latest version available.

What am I missing...?

Edit: apart from this everything, including Safetynet, works fine. :)
[Magisk] DodoGTA:
Don't worry about it (It's normal)
[Magisk] howtomen:
Flashed Magisk 16.7 on my OnePlus 5 running Android 8.1.1 and now it's bootlooping into Fastboot. I see alot of other people have the same issue so I'm going back to 16.6
[Magisk] Jay0r:
Getting Bootloop after flashing 16.7. Full swipe, clean install of the Rom and flashing 16.7 afterwards - same problem Bootloop.

Details:

OnePlus5, Rom=crDroid, microG, latest Open Beta (14) Firmware, Modem and Vendor.

Used latest Blu spark twrp to flash magisk 16.7.
[Magisk] MajinkenSword:
Also on Huawei P20 Pro using RomAur v1.3...

I didn't need to uninstall APK to upgrade. Also, I had a post earlier that was deleted since I didn't include logs, I was reporting about some apps not connecting to the net or some apps not function correctly on 16.6 under 5.8.0

This is to confirm that the issues I reported before are now working on 16.7 using 5.8.2

Hope this helps others using the same device and/or rom.

I am attaching logs in case it's needed.
[Magisk] huangjqiu:
Flash 16.7. bootloop to fast boot.

Op5t liquid remix.

Flash back to 16.6
[Magisk] kunaldas65:
using 16.7 now.... everything working just one problem no module working....in log...error coming no package for execution....
[Magisk] sunil1304:
Magiak 16.7 flashed, booted perfectly on mido running x9 xtended rom.. kudos
[Magisk] Djizox:
16.7 fastboot loop OP5T.

Flashed back to 16.6
[Magisk] martyfender:
I just flashed v16.7 beta through the direct install method after installing MM v5.8.2 and it is working great so far.

Attached is both the install log and the magisk.log.

Nextbook Ares 8A Intel x86, Android 6.0.1.

For all of you that can't seem to follow the instructions in the OP, this is what you need to included and if you flashed it in TWRP, you need to provide the recovery log, saved in TWRP, before reboot.

Thanks, [MENTION=4470081]topjohnwu[/MENTION], for another great update. I usually test the unofficial builds on another thread, but I could not resist testing this version on 1 of my 4 devices, that is leading to the next stable release.

EDIT: I just updated my Greenify4Magisk Module through downloads and it installed with no problems and is working great, as usual.
[Magisk] AlexX-DE:
OP5T, OB12 "treble", with RenderZenith Kernel, i update directly from 16.6 to 16.7, everthing works perfekt, no bootloop, .. Big Thanks to [MENTION=4470081]topjohnwu[/MENTION] :good:

Edit: WiFi not work with RenderZenith Kernel and Magisk 16.7, It currently breaks the sepolicy patching and bind mounts from RenderZenith Kernel, so WiFi will not work as a result!!
[Magisk] kingnok:
"MagiskManager-v5.8.2(128).apk" and "Magisk-v16.7(1670).zip" working fine on my phone (custom ROM RR-N).

Note2 [RR-N-v5.8.5] using Tapatalk
[Magisk] Zacharee1:
Guys, it's great that it works for you, but this thread is for reporting problems with the service. Stating that it works fine doesn't really help anyone, and really only serves to bury the actual issues, making it harder for them to be found.
[Magisk] debby_:
16.7 (1670) (direkt install) works fine here

OP5 + shield tableet + nexus7

Latest Lineage (non treble) installed everywhere