yashsingh1/xdaforums huggingface dataset:
[Magisk] Haunt3r:
Latest version patches dtbo.img and causes errors upon reboot. Any way to prevent it from patching that particular .img? Using a pixel 2 xl, July security patch. Stock rom.
[Magisk] jenslody:
Logcat (if possible) or recovery.log from TWRP ?
[Magisk] Kywrosaki:
I use the last beta magisk 16.6, does not pass the test, more precisely on any version of the magisk did not pass the verification on my smartphone, carefully waited from the update to update that when and yes the problem will be solved but no. However, a strange situation develops, I previously tested in the rootbear application, it informed me that the phone was not rooted, but in the application itself magisk still did not pass the test, but at the moment we have that rootbear complains about the presence in the smartphone of the application to control the root access (magisk manager), but if I re-compile the magisk with a different package name, then the rootbear application is tested, only after that magisk begins to fool, writes that magisk is not installed and ask to install the latest version, end I, the phone starts to reboot every 2-3 minutes, it came to that I had to flash the phone with the formatting of all the data, it was too lazy to clean everything manually, it was easier to flash. Also in the magisk is not active point with a fingerprint scanner for my smartphone, although I have a fingerprint scanner in my smartphone, the item is grayed out and neither turn it on nor turn it off. In general, I attach to the post log magisk, as well as screenshots for clarity, I hope to solve these problems, I'm already really tired of waiting, it's easier to write everything myself and show if it's necessary to test something, then I just have to debug it magisk, for normal operation on my smartphone. Smartphone xiaomi redmi 3 pro, miui 8.4.26, android 5.1.1, I hope for understanding. Thank you.
[Magisk] Kywrosaki:
Hi, updated to the latest version, no changes, no checks, I'm logging on. Earlier I already wrote about this, but my post was ignored. The original of the post here https://xdaforums.com/showpost.php?p=76906480&postcount=5756
[Magisk] topjohnwu:
[MENTION=4544860]osm0sis[/MENTION] has suggested that he thinks the PATH should point to the mirror because some modules messes with the binaries which leads to inconsistent behavior.

It was quite some while ago, and I've done the changes without to much thinking and even forgot it.

However, seeing your report, I'm considering changing the behavior. Since post-fs-data scripts happens before magic mount, scripts executed at that time would already use the unmodified system. I think it would be nice if service.d would actually use the modified system. By doing so it gives these 2 stages an additional difference.

Thanks for your report though!
[Magisk] eivissa:
This is were it stops / loops...Any help is much appreciated

05-04 21:56:09.767 709 709 E TPD : [TPD] ERR: tamper detect flag = 0x8000, detect symptom = 0x8000

05-04 21:56:10.418 872 890 I ServiceManager: Waiting for service media.audio_policy...

05-04 21:56:11.419 872 890 I chatty : uid=1003(graphics) BootAnimation identical 1 line

05-04 21:56:12.419 872 890 I ServiceManager: Waiting for service media.audio_policy...

05-04 21:56:13.420 872 890 W AudioSystem: AudioPolicyService not published, waiting...

05-04 21:56:13.920 872 890 I ServiceManager: Waiting for service media.audio_policy...

05-04 21:56:15.921 872 890 I chatty : uid=1003(graphics) BootAnimation identical 2 lines

05-04 21:56:16.922 872 890 I ServiceManager: Waiting for service media.audio_policy...

05-04 21:56:17.922 872 890 W AudioSystem: AudioPolicyService not published, waiting...

05-04 21:56:18.423 872 890 I ServiceManager: Waiting for service media.audio_policy...

05-04 21:56:19.423 872 890 I ServiceManager: Waiting for service media.audio_policy...

05-04 21:56:19.771 709 709 E TPD : [TPD] ERR: tamper detect flag = 0x8000, detect symptom = 0x8000
[Magisk] guest4711:
Reflash the stock boot image ... (magisk makes a backup of it as /data/stock_boot_*.img)
[Magisk] BORETS24:
I'm again get this bug https://xdaforums.com/showpost.php?p=76735878&postcount=5722

Any solution without wipe data partition?
[Magisk] schack:
Which kernels? Or could I fix the issue by downgrading to Magick 16.4?
[Magisk] osm0sis:
Yep, command not found for something like `date` when the mirrors were in the middle of getting constructed was very similarly a problem.

I think my suggestion was actually have both locations be on the PATH, just with the mirrors first so that there isn't as much of an interruption with basic commands during post-fs-data. This isn't a problem for service.d at all so it could have the 16.4 path still, only post-fs-data.d needs the mirrors added to the 16.4 path. That's how I worked around it on my script here: https://github.com/osm0sis/gappsintegrator/commit/1bc2789d283d113398493dfc0222052958365fa4

[MENTION=4470081]topjohnwu[/MENTION] [MENTION=4487388]jcmm11[/MENTION]
[Magisk] Seagold:
Goto settings > apps > Magisk Manager and clear cache and data.

---------- Post added at 10:55 AM ---------- Previous post was at 10:49 AM ----------

Working on my phone ?.

Samsung Galaxy J200H 3G DUAL SIM

Running Stock ? OS 5.1.1 Lollipop
[Magisk] kunaldas65:
for me no module working....
[Magisk] muff99:
After updating to 16.6 I noticed a problem with AdAway:

After applying a new hosts file and magisks granting root, I get a dozen magisk toasts saying root has been granted.

Can be viewed in MAgisk manager (screenshot attached) as well as logcat:

07-08 12:12:05.593 I/Toast ( 6759): Show toast from OpPackageName:com.topjohnwu.magisk, PackageName:com.topjohnwu.magisk

...

07-08 12:12:07.616 I/Toast ( 6759): Show toast from OpPackageName:com.topjohnwu.magisk, PackageName:com.topjohnwu.magisk

...

07-08 12:12:09.613 I/Toast ( 6759): Show toast from OpPackageName:com.topjohnwu.magisk, PackageName:com.topjohnwu.magisk

...

07-08 12:12:11.629 I/Toast ( 6759): Show toast from OpPackageName:com.topjohnwu.magisk, PackageName:com.topjohnwu.magisk

...

07-08 12:12:13.650 I/Toast ( 6759): Show toast from OpPackageName:com.topjohnwu.magisk, PackageName:com.topjohnwu.magisk

Xiaomi MI6, xiaomi.eu MIUI 10 8.7.5 ROM
[Magisk] S.R.Linguite:
Hi

First of all, thanks for the greatest work!

I've experienced an issue after install the 16.6 version.

My camera stopped working and my recordings (for WhatsApp, for instance) has echoes.

I'm using a Lenovo Z2 Plus, Jaguar 8.1.0 rom (16/06)
[Magisk] kernelguy:
Can magisk still be flashed on a SuperSU rooted device?

The initial description suggests that magisk can handle SuperSU rooted devices and install over them. I have an OnePlus X running OTA OxygenOS. magisk install (via TWRP) fails with the message that the partition has been changed. I have attached the log. Since the deice is practically stock - except for unlocked bootloader and supersu - I thought that magisk flash would just work. I went through the changelog and could not notice a change that dropped support for supersu rooted devices.

(I have even left the original recovery untouched and simply load TWRP via fastboot when I need to use it.)
[Magisk] guest4711:
Afaik it is not supported this way anymore. Deinstall DuperSu or flash your stock bootimage and install Magisk.

You may also use MagiskManager to patch your unmodified bootimage and sideload the patched one later...

There is also a generic un-su script here on XDA...

---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------

Perhaps your modules are outdated? Update them via MagiskManager. If that fails, post the logs...
[Magisk] Oswald Boelcke:
Problem solved!

This morning, installed Magisk Manager v5.8.0 through v5.7.0. Magisk Manager GUI doesn't open respectively forced-clossing.

Logcat attached recorded during the process of trying to open v5.8.0. Reverted back to v5.7.0, all running fine again.

Samsung GT-i9305, RR-N-v5.8.5, Magisk v16.0, Xposed, XPrivacyLua. Same XPrivacyLua settings for v5.8.0 as for v5.7.0

EDIT: Problem solved. The issue was the theming of Magisk Manager. Refer to post #5894.
[Magisk] VampireSH:
I can't patch android p beta 3 boot.img

- Copying image locally

- Target image: /data/user_de/0/com.topjohnwu.magisk/install/boot.img

- Device platform: arm64-v8a

- Extracting files

Bad system call

Failed!

! Installation failed

that's the log, I don't know how to do to patch boot.img

by the way, I put the boot.img in /sdcard/MagiskManger and /sdcard, it patched failed, too.

phone is pixel 2 xl, running android p beta 3
[Magisk] otonieru:
RN5Ai & P20Pro

16.6

Everything is fine.

Only, downloading and upgrading is painfully alow, i think github server might overloaded, lol

---------- Post added at 02:34 PM ---------- Previous post was at 02:32 PM ----------

How about try to patch it from another phone ?
[Magisk] Vincent_b:
Hello :)

Installed also Magisk Manager v5.8.0 on my LG G3 Fulmics 8.0.

Cpu upped to 100%. Thought it was part of the update process, but it was not finishing, and phone was less and less accessible.

Rebooted a bunch of times and used a process viewer to see what was happening.

It starts with a single "sed -E s/ +/\n/g /proc/cmdline" taking all cpu, taking to up 120mb of ram.

Then other "sed -E 's/ +/\n/g' /proc/cmdline" are starting, up to 5 before I could not refresh the process viewer, each one taking 120mb of ram.

I let it run some time thinking if it was an upgrade, it would end after some time...but not.

So I reverted back to v5.7.0
[Magisk] Syoenth:
i did that and still won't open Magisk Manager 5.8

I'm on Samsung Galaxy J7 2015 stock ROM 6.0.1
[Magisk] psychoela:
I get this error after installing latest beta, log here, tq
[Magisk] AnkitGourav:
[MENTION=4470081]topjohnwu[/MENTION] Hi, I got a wired issue on my Redmi Note 5 Pro after installation of magisk v16.6 it's automatically loosing SafetyNet after some time I didn't noticed the exact time but maybe after an hour or two. On every reboot it passes SafetyNet then after some time SafetyNet check is failed.
[Magisk] Brakiss:
Pixel 2 XL updated to 16.6 on DP4. Play store will not open. Cleared data on both apps. Log attached

Reverted to 16.4 and all is good.
[Magisk] davidzam:
No my friend, It´s not that I followed the procedure exactly as you did. So you are using Oreo, well I am using Samsung stock 6.0.1, big difference.

I did a clean update, nothing. I loose root and well everything gets crazy and laggy on the phone. Back on 16.4, the only thing that seems to be working is the manager itself (5.8), but after patching and flashing the boot.img using ODIN, everything stops, This are the logs I got after a clean installation as recommended on the post of topjohnwu himself. Device SM-G550T1. Back using manager 5.7 as well
[Magisk] SacredDeviL666:
Thread Cleaned from the usual working/not working/posts without any logs or any info other than not working!
[Magisk] lesiot:
Huawei Mate 10 Pro - Oreo (8.0.0)

After installing Magisk 16.8 (without modules):

1. Friendly for Facebook - app start but loading icons "working" all the time, and app can't load properly -> magisk_log_20180708_224653_Friendly_for_Facebook.log

2. Electroneum - same as Friendly for Facebook -> magisk_log_20180708_224740_Electroneum.log

3. Connecting to PC by USB - can't access to files (there is no notiification to choose charging only, or file transfer), USB debug mode doesn't work (can't do anything by adb) -> magisk_log_20180708_225139_USB_connect.log

When back to Magisk 16.4 (with Magisk Manager 5.8) don't have this issues.
[Magisk] Tecalote:
[MENTION=4470081]topjohnwu[/MENTION] and [MENTION=4667597]Didgeridoohan[/MENTION]

Magisk 16.6 does not patch ramdisk.img on Huawei Mate 10 Lite, it tries to patch kernel.img - and therefore the phone has no root after the restart.

On Mate 10 Lite /dev/block/mmcblk0p31 = ramdisk.img and /dev/block/mmcblk0p30 = kernel.img

Magisk 16.6 uses mmcblk0p30 (kernel.img) for patching (Target image)....

I saw it in the install_log_20180709_021105.log and Recovery.log (Line 1025) from Magisk 16.6: Parsing boot image: [/dev/block/mmcblk0p30] (wrong)

- because I searched, what could be the reason. And I think it has something to do with the newest Magisk Manager.

You can compare Recovery.log (Line 1013) from installing Magisk 16.42 - here it is correct: Parsing boot image: [/dev/block/mmcblk0p31]

What I did:

I had already 16.42 installed - with the problem, that Magisk Manager mostly FC (if I open Manager) and I had to delete data and cache and sometimes I deleted also Repo-Cache, then I was able to open the Manager again (but after the next reboot, if I open the Manager, then FC)

I updated to the newest Magisk Manager today. There was no problem with FC. I tested also newest Manager with stable Magisk v16.

Then I tried to update Magisk to 16.6 with several methods. Direct install. Flashing with TWRP. It was always the same: no Root.

I uninstalled Magisk completely, restored ramdisk.img and kernel.img, rebooted phone.

After I flashed Magisk v16.6 again, but no Manager was installed. I installed newest Manager manually, opened it - no Root. Checked with Root Checker - no Root. Then I found out, newest Magisk does not recognice the right path to ramdisk.img and uses insted the kernel.img

I tried to grab some logs. Recovery Log = Line 1025.

Soon I flash Magisk v16 or Magisk 16.4 everything is okay.

Edit: Same with Magisk-uninstaller-20180708.

I tested it after with Magisk-uninstaller-20180328 - and it worked correctly. See additional log.
[Magisk] trimax84:
I went back to 16.4 and it fixed the issues 16.6 was causing.
[Magisk] jashan987:
Fatal error 4

Seems to be working fine as i didn't notice any crashes or what not on my redmi note 4 running Advanced LOS custom ROM but the log keeps popping up fatal error 4 log attached
[Magisk] binglejellsx2:
I had the same scare. Update from 16.4 to 16.6 and entering a PIN on reboot results in failed attempts. I just got back from a trip and had I not waited until I got home, I would've been without a phone the rest of the trip. A reboot did not fix the issue.

Reloaded the stock boot in the bootloader and then reloaded 16.4 through TWRP. All is good again. For anyone with a Pixel 2 XL and a PIN for security, best advice is to wait until the next Magisk update.

Attached the only 2 logs I found in /cache. I'm assuming the backup log is the one where I installed 16.6 and the regular log is from reinstalling 16.4, so I flip-flopped the extension on the backup so it can be attached. (Note: I noticed my original post was deleted because it did not have the requisite logs, but I felt my post and lssong99's would've been helpful to "normal" users who need a path to a working device).
[Magisk] dewie68:
Hey guys. On Pixel 2 XL, DP4. Fresh install of DP4. I tried flashing Magisk Zip in TWRP, and when it boots after, it goes to this screen: https://imgur.com/99vQUmk

After flashing the Uninstaller, phone boots up again. Using Magisk Manager to patch the boot.img doesn't work either. When I try that, I get the following log:

- Copying image locally

- Target image: /data/user_de/0/com.topjohnwu.magisk/install/boot.img

- Device platform: arm64-v8a

- Extracting files

Bad system call

Failed!

! Installation failed

Also, after flashing the Zip in TWRP, there's no log in /Cache/. Nothing. Any help would be appreciated.
[Magisk] neekless:
Hey anyone know's what's the command to check the used/total img size in this version? In the previous version the command was (for example)

magisk --imgsize magisk.img

but with the new imgtool applet idk how to check it anymore
[Magisk] zulu99:
This happen only on Shield TV and few other devices because on Shield TV the default sqlite journal mode is set to WAL ( Write-Ahead Logging ) and Magisk not take in consideration this. When journal mode is set to WAL there is a selinux problem on autogenerated sqlite files /data/adb/magisk.db-WAL and /data/adb/magisk.db-SHM and therefore the /data/adb/magisk.db database can't be read or write.

# Root required #

Open the file /system/build.prop with a text editor

Add this line:

debug.sqlite.journalmode=DISABLE

Delete the files:

/data/adb/magisk.db
/data/adb/magisk.db-wal

Reboot
[Magisk] NegativeOne:
I'm using a Google Pixel on Android 8.1.0 and version 16.6 causes Magiskhide to stop working. Apps that are targeted by it simply crash.

Magisk log:
[Magisk] SacredDeviL666:
And again :eek:

Please hit report button wherever you find a user has gone offtopic or against the requirement of OP.
[Magisk] ilal2ielli:
How do I get a log of Magisk after root loss?

I installed 16.6 yesterday on July Nitrogen OS build for my Pixel 2 XL.

I went to the Magisk Manager but couldn't access anything in the Magisk menus since Magisk was no longer installed.

Rebooted to recovery and reinstalled Magisk, but the log was cleared.

Any tips for getting the log for next time this happens?
[Magisk] iPusak Gaoq™:
Hmmm...this is not exactly a real problem/issues but Magisk Logs can't be delete/clears in logs...using latest beta on AEX oreo....

Also i notice there a bit of delay before Magisk start running on every reboot so is there a way to changes those delay time or would it be nice to have an option to changes those delay time on next update?
[Magisk] tbst1337:
hi all,

i have a really strange problem since yesterday: i cant view any websites on any browser (also not ingame browsers). however, whatsapp, telegram and pubg work fine.

the only thing i installed yesterday was the magisk update to 16.6. could that be the issue?

Here is the log:
[Magisk] jcmm11:
For the logs - after you hit the delete button hit the refresh button and you'll see that the log actually is deleted. It's just a visual glitch.
[Magisk] f30R:
Thank you very much, this fixed it! :good:
[Magisk] abdoh01:
hi all i have problem with magisk manager 5.8.0

i install it Successfully and it open but don't get to the main page

and got magisk manager isn't responding do you want to close it ok or wait like screenshot

my phone is lg k10 android marshmello
[Magisk] Bakica:
Try to clear cache and data of MM
[Magisk] jenslody:
It's (in most/all cases) an issue with broken tools on some systems, should be fixed in next update.
[Magisk] stylz3:
I was able to install Magisk 16.6 with no problem. I uninstalled magisk 16.4 flashing the magisk uninstaller recovery and then flashing the magisk 16.6 zip file. The only thing issue I can see that I'm experiencing is the lack of notifications. I'm not sure if magisk 16.6 is putting apps into a deep sleep/deep hibernation, but I'm unable to get push notifications from apps like whatsapp, bleacher report and weather timeline. Attached is a copy of my logs from magisk.

edit: Shoud have included the device and ROM I'm running. OnePlus5t Oreo 8.1 Beta11. BluSpark Kernel r123.
[Magisk] DrSeussFreak:
Running on a Pixel 2 XL (stock with July patches) and it seems that this is patching the dtbo.img again, which had been absent for a number of releases. Any reason on why this was reintroduced?

Thanks to [MENTION=507255]lodufkah[/MENTION] - resolution below
[Magisk] yochananmarqos:
You shouldn't be modifying system files while using Magisk. To modify the build.prop systemlessly, create a Magisk module and add that line to /common/system.prop.
[Magisk] Denkai:
If you can't read or write the database, how would you get the module to work?
[Magisk] yochananmarqos:
You got me there. :silly:
[Magisk] achfighter:
Magisk installer can't open boot.img
[Magisk] martyfender:
Your log does not app3ar to be valid all I get is html code, when opened on my android tablet in mixplorer's text editor.
[Magisk] abdoh01:
I tried but it is the same there is some thing wrong in magisk manager apk v 5.8.0 cause i already using magisk v16.6 but with magisk manager 5.7.0

i don't have problem with that i can use the stable version of magisk manager when it ready but i have problem to get the same wrong in all the further versions that what i fear
[Magisk] youyim:
Android 8.1.0 device:NUBIA Z17 and Red Magic and Z18mini

Soory，my english is poor. I try to flash almost all version, but only Magisk version less than v14 work. I try to flash v16.6, it's bootloop.

version<=14 ---work version>14----don't work

View attachment Screenshot_2018-07-11-19-07-51.png

This magisk.log and logcat. View attachment debug-v16.4.rar

View attachment recovery-v16.4.log
[Magisk] Logix:
thread cleaning

I expect users reporting to at least have basic debug skills, this thread is heavily moderated so refrain from spamming with "useless" reports! (from the op and dev)

Please reconsider writing reports in here unless they are accompanied by a logcat!!!!

Just stating that something does not work does not help the developers fix anything.
[Magisk] Drizzt321:
Installed Magisk 16.6 onto my S9 with LineageOS (Jul 03). Installed fine, booted fine, the MagiskManager 16.0 app says SafetyNet Check was successful, but the SafetyNet Test (https://play.google.com/store/apps/details?id=org.freeandroidtools.safetynettest) fails. See https://imgur.com/a/s3lYC5i for screenshot of the error, something about a Response signature error from a verify URL. My bank's app (USAA) detected I was running on a rooted phone, and so won't work. Google Pay seems to not detect it, as it starts up just fine and tries to swap over to my bank's app to confirm my CC in Google Pay.

EDIT: Added my /cache/magisk.log

EDIT2: Ah, didn't know about Hide for an app. Added USAA app to the Hide list, and it's all working 100% now.
[Magisk] Eamo5:
Hi,

Galaxy S9 appears to be encountering a few errors. Log attached below. Also there have been reports of Android system battery drain throughout the S9 community on 16.6 over Soldier's modified 16.5.5 zip.
[Magisk] Eamo5:
Systemless hosts also seems to return errors in the logs on the S9, unsure if this is a known issue. Logs attached again

EDIT: I can't seem to reproduce this issue. I believe it occurs with systemless hosts enabled.

Magisk hide seems broken for me as stated in my other post.

Here's the link to another time I caused it to occur (no Magisk hide and systemless hosts enabled.)

https://drive.google.com/file/d/1v7TRslKi6fwdW8IZGP3O1FAAhh3GzZ1i/view?usp=drivesdk

Here's the link to the gms Magisk hide error

https://drive.google.com/file/d/1CRl4hpvBQb-pMtYZd-4ZjngRRq05MB-2/view?usp=drivesdk
[Magisk] Dapeebb:
Segmentation Fault when attempting to patch s9+ boot image

Attempted to patch boot image for S9+ (G965F) with Magisk Manager 5.8.0 targeting beta release 16.6 with S9+ support. Logs report segmentation fault when attempting to repack boot image.

Steps to reproduce

Go here: https://xdaforums.com/galaxy-s9-plus/how-to/official-stock-firmware-thread-samsung-t3764479

Download firmware G965FXXU1BRF8.zip (https://androidfilehost.com/?fid=11050483647474828805)

Extract AP_G965FXXU1BRF8_CL13792060_QB18608589_REV01_user_low_ship_meta.tar.md5 from G965FXXU1BRF8.zip

Extract boot.img.lz4 from AP_G965FXXU1BRF8_CL13792060_QB18608589_REV01_user_low_ship_meta.tar.md5

Copy to device with Magisk Manager 5.8.0 and attempt boot image patch with output format .img.tar.

LOGS. Relevant lines in RED
[Magisk] martyfender:
John Wu

‏ [MENTION=4470081]topjohnwu[/MENTION]

12m12 minutes ago

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Or here on github:

https://github.com/topjohnwu/MagiskManager/releases/tag/v5.8.1