yashsingh1/xdaforums huggingface dataset:
[Magisk] chudy_85:
I have problem with magisk v16.6

When I connect to pc its not connect to mtp only it's charging phone.

Here it's my log

07-11 16:49:53.388 521 11570 I Magisk : * Stopping MagiskHide 07-11 16:49:54.205 521 11572 I Magisk : * Starting MagiskHide 07-11 16:49:54.206 521 11572 I Magisk : hide_utils: Hiding sensitive props 07-11 16:49:54.206 521 11572 I Magisk : hide_list: [com.google.android.gms.unstable] 07-11 16:49:54.230 521 11572 I Magisk : hide_list: [pl.allegro] 07-11 16:49:54.254 521 11572 I Magisk : hide_list: [com.enelmed.enelmedonline] 07-11 16:49:54.278 521 11572 I Magisk : hide_list: [softax.pekao.powerpay] 07-11 16:49:54.298 521 11572 I Magisk : hide_list: [hr.asseco.android.mtoken.pekao] 07-11 16:49:57.408 11578 11578 F adbd : usb_linux_client.cpp:598] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1) 07-11 16:50:02.418 11580 11580 F adbd : usb_linux_client.cpp:598] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1) 07-11 16:50:07.431 11582 11582 F adbd : usb_linux_client.cpp:598] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1) 07-11 16:50:12.113 11592 11592 F adbd : usb_linux_client.cpp:598] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1) 07-11 16:50:17.154 11640 11640 F adbd : usb_linux_client.cpp:598] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1) 07-11 16:50:22.514 11651 11651 F adbd : usb_linux_client.cpp:598] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1)
[Magisk] topjohnwu:
You have to extract the boot.img from the lz4 format. Google how to extract lz4 files :)
[Magisk] tecknight:
I will repost with correct description of issue
[Magisk] SacredDeviL666:
Thread Cleaned.

Come on guys :crying:

i have posted so many times thread cleaned i might have to start cleaning my own posts for the maximum number of "thread cleaned" posts :eek:

Please stay on topic and stop cluttering this thread with unwanted posts and posts without beta troubleshooting logs. The dev will just skip all the posts including relevant one's because of the rest.
[Magisk] Parzival_UY:
Hi guys,

I've got something odd happening on my phone. Magisk installs correctly, runs correctly, I MagiskHide Play Store, Play Services Framework and Pokemon GO and do the SafetyCheck and it verifies correctly. After that I install App Systemizer module and reboot the phone. At this moment no "hidden" app works and SafetyCheck ends with cts and basicIntegrity failing. This didn't happen to me on previous versions. I've already checked the log but there's nothing there. I'm attaching magisk.log and also a magisk.log.bak I had since it has more entries although I can't see anything helpful.

https://drive.google.com/file/d/1UarBGBtyq_-w7USdCv3FekQWUqSa5e_e/view?usp=sharing

https://drive.google.com/file/d/1hIrXckRGiJQtcgcE7iSJmPmaRuYcADFR/view?usp=sharing

Any help will be appreciated.

Thanks
[Magisk] tecknight:
USB issues under Magisk 16.6

Gentlemen,

I would like to report a strange progressive USB issue I am having with Magisk 16.6.

I was having this issue under 16.4 and 16.0, but only recently did I determine it was a Magisk problem.

I have a seen this problem personally on 2 phones, both LG devices.

Here is the problem I am having:

Starting a variable amount of time (immediately to ~ 2 days) after Magisk is installed, I start losing USB functionality on my phone.

The first problem that occurs is that USB Debugging stops working despite a notification that it is enabled.

Once USB debugging stops working, enabling USB debugging blocks all other USB devices/nodes on the phone.

This includes MTP file sharing, the modem device and com port and the USB gadget.

The issue continues to progress until none of the USB devices show up at all, even with USB debugging disabled.

At that point, I reimage the phone back to stock (the USB still works in download mode, thankfully) and then full USB functionality returns.

I then re-root the phone and re-install Magisk 16.6 and the cycle continues.

I have attached dmesg, logcat, magisk.log, magisk.log.bak and USBDevView logs.

These logs are from an LG Aristo 2 running Android 7.1.2.

BTW, I also have this line in my logcat and magisk.log:

07-12 22:59:27.418 717 717 F adbd : usb_linux_client.cpp:602] Check failed: dummy_fd != -1 (dummy_fd=-1, -1=-1)

Thank you so much for your help.
[Magisk] Old Blacky:
From your description it sounds like a problem, that maybe can be fixed by the following pull request: https://github.com/topjohnwu/Magisk/pull/395
[Magisk] :
I can't install version 16.6. I tried both from magisk manager and TWRP witch both said that the installation was successful but when I rebooted my phone and checked the magisk version it said that magisk is not installed, then I tried to install v16.4 witch worked just fine. I tried to update one more time to v16.6 but it still didn't work, after the reboot it still said version 16.4.

And also here is the log :fingers-crossed:.

https://www.dropbox.com/s/0zwofel4znpwmfo/install_log_20180713_163239.log?dl=0
[Magisk] Dragon_16:
Could you add in manager 16.6 the 5.8.1?
[Magisk] :
I already have the latest magisk manager and I tried to update magisk through it, but the result is the same.
[Magisk] martyfender:
Have you tested this without the large number of modules you have loaded? Also, your issues.txt is a 0 byte file.
[Magisk] smbunn:
USB Debugging functionality stopped

I am having the same issue with a Huawei P20 Pro. I installed Magisk 16.6 and it was all successful. Root checker confirms my phone is rooted OK and it works fine as a phone. But if I plug in the USB cable to my laptop it will only work with HiSuite if USB debugging is off. As soon as I turn debugging on the HiSuite connection is dropped and I can no longer transfer files or see the folder under windows file manager. ADB does not see any devices when in USB Debugging mode or when HiSuite is connected. It all worked fine before I installed Magisk under TRWP.
[Magisk] tecknight:
Yes, it has actually happened with no modules loaded, but I went ahead and removed all but 2 modules and fixed the issues.txt. I have attached the new logs. Thanks.
[Magisk] Eamo5:
Another issue when applying Magisk hide on Galaxy S9. Logs attached below.
[Magisk] ska4fun:
Can you guys confirm that magisk 16x isn't working on the latest Lineage OS 15 nightly?
[Magisk] Loriot:
Magisk v16.6 works perfect on my bacon with latest

LOS 15.1
[Magisk] ska4fun:
Thanks. I can't make it work on my mi6...
[Magisk] karmatose:
Same. V16 stable and 16.6 just bootloops after install. I'm on a Mi Mix 2.
[Magisk] espaciosalter20:
Ok, I'm reporting back again, now with log.

Huawei p10 vtr-l09 with Oreo 8.0 under emui 8.0

Fw 370

Magisk 16.6 breaks webview...
[Magisk] zallaevan:
ADB not working

Hi,

I have found that adb isn't working after installing this beta. I tested it on a Huawei Nova 2s. I uninstalled it from the Magisk Manager, and the adb started to work properly.
[Magisk] tecknight:
Hey, I tracked down and figured out the ADB/USB problem and I have a workaround.

I tracked down the source for adbd to find out what was causing that log message

I found it here:

https://android.googlesource.com/platform/system/core/+/master/adb/daemon/

in module usb.cpp:

lines 531-535

void usb_init() {

dummy_fd = adb_open("/dev/null", O_WRONLY);

CHECK_NE(dummy_fd, -1);

usb_ffs_init();

}​

So the error was resulting from a failure to open /dev/null in write only mode.

So I opened a shell and tried

ls > /dev/null

as a non root user, and I got the error "can't create /dev/null. permission denied."

So I checked out the permissions on /dev/null and it is owned by root and has 644 permissions.

I changed the permissions to 666 so non-root users can write to it and suddenly my USB debugging is working along with my MTP file sharing and the USB com port, modem, everything.

However, when I reboot, Magisk changes the permissions back to 644.

So, until Magisk comes out with a fix for this, just do a:

chmod 666 /dev/null

from a root shell and your adb/USB issues should go away at least until you reboot.

I wouldn't be surprised if this issue might be causing some other problems as well.
[Magisk] Minotaur:
I've got a bit pf a problem that's developed since I reinstalled Magisk and the Manager app. Magiskhide isn't running automatically when the phone starts. It shows as enabled in settings, but in order for it to run I have to disable and re-enable it. Not sure what might have caused this to happen. It's happening on both 16.0 and 16.6. Any ideas?
[Magisk] martyfender:
You are correct, on one of my Nextbook Ares 8A tablets, where USB is working correctly, /dev/null is set to permissions 666 and not 644, as your device is. So on my devices, Magisk is not changing it to 644, as is the case on your device. Maybe your info will give [MENTION=4470081]topjohnwu[/MENTION] some idea how to fix your issue. Could it be a bug in your specific rom?
[Magisk] jenslody:
On my device it has 666 as permissions. As workaround you can place an executable script in "/sbin/.core/img/.core/service.d/" or "/sbin/.core/img/.core/post-fs-data.d/" that runs chmod on boot.
[Magisk] asd13751418:
16.6 wifi issue on lg g3

My phone work with stock lg marshmallow.

When I flash 16.6 magisk,wifi can't catch the IP address.

Once I uninstalled it, it work.It's strange.

It's the magisk log. Hopefully it is useful to find the problem.

Thanks in advance.
[Magisk] erayrafet:
Whenever I install Magisk 16+ on my Huawei P8 on Android 6.0, I can't open Magisk Manager. Just shows a black screen. I've tried with the patched boot method, but I got the same result.

Is this a typo?
[Magisk] watoan:
version 16.6 with manager 5.8.0 works great on my Nexus 6 (LineageOS 15.1 Android 8.1.0)

But after it prompted and upgraded to Manager 5.8.1, Magisk Hide does not work anymore...

Does anyone faced the same?
[Magisk] fex42:
On my Mi6 with LOS15.1 TWRP complains that it can't mount /vendor and stops installation with an error.
[Magisk] ska4fun:
This happens on my Mi6 LOS15.1 two, with the latest nightly.
[Magisk] karmatose:
Updating to latest TWRP solved that problem or me, but... Flashing any version of Magisk leads to bootloops and having to replace the original boot.img file.
[Magisk] callifo:
I've still had an issue with Magisk loosing root randomly, can happen over a few hours or a few days. Havent identified what causes it, but eventually I will get a message from Magisk Manager to update my version, and when I open Magisk Manager, it says Magisk is not installed and offers to install it. Apps with root access no longer detect root. Rebooting the phone fixes it.

Phone: Google Pixel 2 (non-XL)

Android version: 8.1 June 5th, 2018

ROM: Resurrection Remix, RR-O-v6.1.0-20180613-walleye-Unofficial

Kernel: 4.4.136-FlashKernel+

Logcat is attached, the issue occurred towards the bottom. Logcat logging had been running for a few hours.
[Magisk] tecknight:
Yes, there are still a lot of questions. I don't know if you noticed, but there are at least two other people (on other devices) having the same issues that I am having. I have also seen the issue on an LG V30 running Oreo.

Whatever the cause is, I would not call it a bug in the ROMs affected, since adb works fine on the ROMs if Magisk is not installed. Mine was a stock LG ROM, before I installed Magisk.

I am going to restore my device back to stock and take a snapshot of my /dev folder before I install Magisk.

I will then try to get some logs when the permissions change on /dev/null.

I am also going to see if there are any other permission changes on files in the /dev folder.

I will post any logs or other info I am able to acquire.

Thanks.

---------- Post added at 06:34 AM ---------- Previous post was at 06:26 AM ----------

Thanks. I will do that once I am finished testing.
[Magisk] jenslody:
Please also check (or backup) "/ueventd.rc", because it (should) set(s) the access rights for "dev/null" (and others).
[Magisk] fex42:
In the meantime, I learned that LOS 15.1 20180710 is a treble release. TWRP and Magisk need also to be treble enabled versions. After using treble variants of TWRP and Magisk, everything works again.
[Magisk] Encik Panda:
Magisk 16.6 with Manager 5.8.1 seems works pretty impressive on my phone. With 5.8.0 my device get slightly warm/hot but with 5.8.1 the device working normally w/o any issue. Module n Magisk Hide also working fine. Currently using DevBase 5.8 + NK-v102T10.4 together with Magisk 16.6 & Manager 5.8.1. Lots of improvement in battery life for me. 8hr SOT with fulltime LTE + WQHD+
[Magisk] tecknight:
Attached is the current ueventd.rc from my affected system. It has /dev/null set to 0666.

I am still running Magisk and after booting my /dev/null gets set to 644.
[Magisk] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] just made a commit to fix broken adbd here:

https://github.com/topjohnwu/Magisk/commit/2bde8a197590523224492726c19bff75947edb17

Not sure if that applies to your device also since it states EMUI.
[Magisk] tecknight:
That's great. Hopefully it fixes mine as well.

I just got done reimaging to stock and recreating the problem.

I have attached detailed logs from the exact boot where the problem started and also from the stock unrooted image.

FYI, the issue started immediately after installing 16.6 via TWRP.

Update: I just tried installing Magisk 16.6 via Magisk Manager.

Based on the log, it appears that the issue is being caused by MagiskHide.

As soon as MagiskHide launches, I start getting the errors.

Before it launches there are no errors at all.
[Magisk] tecknight:
Thanks.

So any .sh file with executable permissions in that folder will run at boot after permissions have been set on /dev/null ?

Actually, I just tested it and it works perfectly. Thanks
[Magisk] jenslody:
Any executable files regardless of the ending.

I did not try real executables (non-scripts) to be honest.
[Magisk] tecknight:
Thanks, I just tried it and it works great !!
[Magisk] DenyDarko:
https://github.com/topjohnwu/Magisk/commit/2bde8a197590523224492726c19bff75947edb17
[Magisk] tecknight:
Yes, [MENTION=8126387]martyfender[/MENTION] posted that earlier. I'm happy to see it.

Looks like Magisk is using the system's logcat binary as it's logging daemon and some logcat binaries do not play well when redirected to /dev/null.
[Magisk] tosunkaya:
Hi i cant install magisk 16.6

It's successfully flashing on twrp but when i reboot and open magisk manager it says magisk isnt installed.

Last working version is 16.4 (1642)

I attached log. Tried to install 16.6 2 or 3 times then installed 16.4

Device: xiaomi redmi note 4x nougat

Please help
[Magisk] Texan1:
Strange one on my Huawei Mate 10 – installing Magisk 16.6 stopped my email from working – email header would load but the content would not.

I also noticed I couldn’t create a new email account for my work Office 365 email account.

Rolled back to 16.0 and email working all fine again.

Edit - apologies for no log, need email working as a priority so won't be installing 16.6 again, hopefully someone else can provide.
[Magisk] Didgeridoohan:
PSA - Don't forget to post logs

A friendly reminder about posting in this thread...

Don't forget to post logs if you're experiencing issues.

Bug reports without logs are most of the time useless... And useless posts get deleted!

And

, make sure the logs are relevant!

I see many posts that contains logs that have next to nothing to do with the reported issue.

Take a look in the OP for tips if you don't know which logs are useful.

More tips on getting logs can be found here:

https://www.didgeridoohan.com/magisk/MagiskHelp

And, finally... Please don't post:

"Everything works, yay!" - It only clutter up the thread and will be deleted. Only post this if you've been testing an issue that has now been fixed, as a confirmation for that specific issue.

"Something doesn't work, I'm going back to version xxx." Without any relevant logs supplied. - Completely useless post that will be deleted.

Posts that have nothing to do with the current beta. If you're having issues with the stable release, take that to the general support thread!

Etc...

This thread's purpose is to test the beta releases for Magisk. They may have issues, they may break your phone. They're always tested internally on several devices before being released publicly, but there are so many variants of Android and devices that it's impossible to test them all...

Please help by keeping the useless posts somewhere else, preferably nowhere at all...
[Magisk] neeksxda:
The install after OTA option disappeared in manager v5.8.1...[IMG="Magisk Manager Install"]https://image.ibb.co/bSQGZJ/Screenshot_Magisk_Manager_20180716_111727.png[/IMG]
[Magisk] Didgeridoohan:
https://github.com/topjohnwu/MagiskManager/commit/831112abd2d7fd3df0b1680d1c73c458512e7745
[Magisk] neeksxda:
Thanks -- should I patch and build from source? I've been using that option w LineageOS for months. I tried to downgrade manager but it prompts to upgrade.
[Magisk] Didgeridoohan:
It's been disabled because it needs to be reworked. You could always build your own Manager without that commit if you want to, but it'll be reintroduced eventually.
[Magisk] neeksxda:
I wish I would have checked before updating OTA. It was really convenient for us that were able to use it. Maybe bring it back w a disclaimer or warning?

Now I either have to:

- build and install Manager from source w a patch before my phone reboots

- go through the annoying A/B root process again

- change the boot slot to not use the updated slot

Is there an alternative way to trigger an install to the other slot? A shell command to run in Android's terminal?

Edit: Went ahead and built a debug apk of Manager w patches from source. It was quick if you already have an Android dev environment setup
[Magisk] maggotbonez:
Ran into an issue but probably on user side hah.. been awhile since I rooted and tweaked no thanks to Huawei. Tried to flash in TWRP magisk hoping to rid of root from fh root tool so I can use facial recognition but ran into error. Any advice?
[Magisk] Pkt_Lnt:
https://xdaforums.com/showpost.php?p=77084438&postcount=5901
[Magisk] maggotbonez:
Hm didn't realize it said bad request and didn't upload.. would a ss work? Tried a few times but won't upload
[Magisk] Pkt_Lnt:
https://xdaforums.com/showpost.php?p=77084438&postcount=5901

Posts that have nothing to do with the current beta. If you're having issues with the stable release, take that to the general support thread!
[Magisk] ska4fun:
How did you got these treble-friendly versions?
[Magisk] ska4fun:
Even using latest twrp recovery I was unable to install magisk 16.6 in my LOs 15.1 lastest nightly Mi6... '"Unable to mount vendor'' was the error in the flashing process.
[Magisk] tchavei:
Since today's Google update, my magisk 16.6 stopped passing safetynet check (both ctsprofile and basic integrity say "false"). Is this a general problem or just me?

Thx

Tony
[Magisk] andrew2432:
https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/
[Magisk] kutzman:
I cannot confirm. Had this Google update to 8.10.22.21 today and still passing both safetynet checks.
[Magisk] mbc07:
I'm not sure on how to get a log about this but I'm having an issue with MagiskHide since Magisk v16 (at least), where my phone will sporadically stop passing SafetyNET checks. When this occurs, I need to reinstall Magisk to get it working again. Steps to reproduce:

1) Install Magisk through TWRP, on top of the stock boot image.

2) Everything works, SafetyNET passes, root access working fine.

3) After some use, usually a few hours (sometimes a few days), SafetyNET starts failing (both ctsProfile and basicIntegrity checks return false). Root access still works fine. Rebooting the device doesn't fix the SafetyNET checks.

4) Reinstall Magisk through Magisk Manager or through TWRP (on top of the already patched boot image) then reboot.

5) SafetyNET checks passes again, until the problem occurs again.

I'm using Magisk on this phone (from my signature) since v15 at least, but I recall noticing this problem only with v16 and onwards (currently running v16.6, though). In this meantime I received some security patches, so I think it might have something related to this too. I attached the Magisk log files I could find on my phone, but I didn't notice anything in them that might be related to sporadically failing SafetyNET checks...
[Magisk] casouzaj:
I was passing both Safetynet tests without any additional module, but, like you, today both of them failed. Then, after installing module 'MagiskHide Props Config' and rebooting my Z3C phone, both tests are green again.
[Magisk] tchavei:
Thx to all replies. I went into twrp to wipe cache but had a brain freeze and wiped my phone in the process. Surprisingly, after all updates, magisk is still passing safetynet (don't know for how long though)

Tony
[Magisk] iWARR:
Quick feedback (Xiaomi Mi5, RR Darkness OS, Oreo 8.1, Magisk v16.6, MM v5.8.1, Busybox (system, TWRP) by osm0sis v1.28.4)

The next problems are relative to the 2 rescent Magisk versions:

1) "Magisk Manager" can't show/update Repository list or download anything while DNS is encrypted.

Otherwise it can inform you about incoming MM update and even show a changelog of the new version.

To make MM working online I have to temporary disable my already organized and safely working encrypted DNS.

I'm using dnscrypt-proxy for Android.

Probably, MM trying read the system DNS settings directly (127.0.0.XXX that is a must for "dnscrypt-proxy" to work properly) and does not understand the way it working.

There is no network (DNS) problems with other installed apps, they are connecting and functionig without any issues (browser, messanger, etc).

(I'm using the original installation of "dnscrypt-proxy" from GitHub + my own manual launching methods inside OS, not a module from the Magisk Repo.)

2) Manual launching "Magisk Manager" app often stuck at the green splash-screen with Magisk logo. Second launching is successful in the most cases.

3) ROOT access to the sertain app that already has granted SU is too long and not always successful. This may cause sticking the UI.

Closing this and the second attempt is a workaround.

Othewise, I can notice that very first time granting SU to all apps became faster and more stable in v16.6.

4) Manipulating with Magisk on RR is often a dangerous operation (system changes: updating, etc).

For example, manual updating MM (apk) cause 100% stuck after rebooting the OS (boot-animation stage). On the MM v5.8.1 also.

Wiping ART/Dalvik cache is a workaround. (Probably this is a custom RRD OS issue, probably not).

Installing the new (not yet tested) module is always a risk also.

So, I'm using only minimum (a few) well known, tested and very necessary modules.

Note: Almost the same bahavior was noticed on Xiaomi Redme Note 5 + official RR OS.

Summary (IMO): A future developing of the Magisk needs more attention to LOS-based operative systems.

Thank you for attention and your hard work. My best regards.
[Magisk] martyfender:
Do you mean the Google App update in the Playstore? If so, I just installed it and my device still passes safetynet.

---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------

https://xdaforums.com/showpost.php?p=77084438&postcount=5901
[Magisk] MAH3SH:
Unable to mount '/system' (invalid argument)

Error while flashing magisk in pixel experience gsi, zuk z2 plus

cts profile false