yashsingh1/xdaforums huggingface dataset:
[Magisk] Vakman:
Edit: Logs have been deleted. The issue seems to be resolved with 15.0. Thanks!

On the Essential Phone (Open Beta 2) with Magisk installed, random reboots occur frequently.

These stop when Magisk is removed.

14.3 is the closest to OK. 14.6 disappears after a few of these reboots.

There are no additional modules installed. This occurs even in the core only mode.

I've attached a logcat, dmesg and event logs that should be around the time of some of the reboots.
[Magisk] PRADEEPHONDA:
Hi on my Samsung note 5, not able flash greenify v3.9.0 module. Running on magisk v14.6. Not able to manually flash on twrp too. Debug log is 4.8mb & not able to upload here.
[Magisk] kiwigi:
Would someone be able to confirm if Magisk 14.6 is compatible with sm g930 f(d) with nougat stock rooted(supersu v2.82-sr5)? If not this version, which one would work?

Thanks
[Magisk] VincentJoshuaET:
Does /system/su.d work on Magisk?
[Magisk] guest4711:
Magisk is a standalone root solution and does not work with supersu or LOS-suaddon anymore. It needs a stock boot image...
[Magisk] kiwigi:
Does that mean I would have to unroot supersu first?
[Magisk] guest4711:
Yes, highly recommended.
[Magisk] Iradj:
There is no inbuilt Busybox anymore in Magisk v13
[Magisk] KaMyKaSii:
If bootloop is caused by the lack of busybox, you can install osm0sis Busybox. In your case it will be installed as a Magisk module, but flash on TWRP
[Magisk] lepicane1:
Appreciate any help and hope I have provided the relevant info below and attached. I'm not too bothered about Magisk Hide not working or passing SafetyNet, as long as I can hide the root with a third party app, which is something I cannot do with Magisk 13. Any suggestions for which third party apps can hide Magisk 13 root would be appreciated.

Device: Xiaomi Redmi Note 4 (mido), unlocked bootloader, latest MIUI developer ROM, latest TWRP, LazyFlasher, xiaomi safetynet fix 1.91

Unrooted: 'Root Checker' app confirms unrooted and SafetyNet passes basic integrity check but has CTC profile missmatch (this is in 'Root Checker'). This is a known Xiaomi MIUI issue.

Magisk 12: Magisk Hide never worked, SafetyNet never passes, 'Root Checker' app shows rooted and SafetyNet fail (Response payload validation failed). 'Hide Rooting Lite' app successfully hides the root when needed for banking apps.

Magisk 13: Magisk Hide never worked, SafetyNet never passes, 'Root Checker' app shows rooted and SafetyNet fail (Response payload validation failed). 'Hide Rooting Lite' app cannot hide the root when needed for banking apps (always showing as rooted).

Have tried many of the suggestions in this thread (without success) relating to Magisk Hide and SafetyNet passing. Please let me know if any further info is needed.

Many thanks.
[Magisk] Alucard:
Thats too bad.

---------- Post added at 08:25 PM ---------- Previous post was at 08:23 PM ----------

No bootloop happened because of viper4android flashing module,is osmosis busybox a module on magisk managers download page or do i have to download from xda?Im currently on v12 magisk.
[Magisk] biggdevon:
Just a general question I haven't found info the thread (quick search), since we're now installing busybox separately does Magisk still hide it's existence?
[Magisk] topjohnwu:
Magisk v13.0 (b3da28e)

Another beta!! ;)

Fixed a small issue in magic mount, causing modules fail to load if installed multiple modules. This shall be a rather stable release.

For those who still cannot flash through custom recovery due to CANNOT LINK EXECUTABLE, may you do me a favor? I want to check whether the libsqlite.so is completely incompatible, or the issue is caused by the custom recovery environment. Extract the magisk binary of your device's architecture, and connect your device to a PC with adb access, and do following commands when the device is properly booted up (not in recovery)

adb push <path to the magisk binary> /data/local/tmp
adb shell
(you should now be in the device's shell)
cd /data/local/tmp
chmod +x ./magisk
./magisk

And check whether if any errors occurs, or show the help message for Magisk.

If the help message shows up properly, this means your device is actually capable of running the binary without issues! I might be able to fix things by tweaking the flash script again.

Thanks!
[Magisk] Didgeridoohan:
If it's a Magisk module it might.

[MENTION=4470081]topjohnwu[/MENTION] have said he'll make a busybox module, but meanwhile [MENTION=4544860]osm0sis[/MENTION] have one here that works just fine with Magisk (yes, I've tested it with the v13.0(1e87780) beta and Magisk can hide it).

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

Running on the same setup mentioned in this post, with CANNOT LINK EXECUTABLE issues, the help message shows perfectly fine.
[Magisk] Allstargaurav:
Tried it and help message shows up properly

Here is the terminal Log

home@Home-Pc:~$ adb push magisk /data/local/tmp
home@Home-Pc:~$ adb shell
falcon_umtsds:/ $ cd /data/local/tmp
falcon_umtsds:/data/local/tmp $ chmod +x ./magisk
falcon_umtsds:/data/local/tmp $ ./magisk
Magisk v13.0(b3da28e) multi-call binary

Usage: ./magisk [applet [arguments]...]
or: ./magisk --install [SOURCE] <DIR>
or: ./magisk --list
or: ./magisk --createimg <PATH> <SIZE>
create ext4 image, SIZE is interpreted in MB
or: ./magisk --imgsize <PATH>
or: ./magisk --resizeimg <PATH> <SIZE>
SIZE is interpreted in MB
or: ./magisk --[boot stage]
start boot stage service
or: ./magisk [options]
or: applet [arguments]...

Supported boot stages:
post-fs, post-fs-data, service

Options:
-c print client version
-v print daemon version
-V print daemon version code

Supported applets:
su, resetprop, magiskpolicy, supolicy, sepolicy-inject, magiskhide
1|falcon_umtsds:/data/local/tmp $
[Magisk] will5:
Im getting safetynet CTS error on magisk 12. Was working fine for 15 days (even played mario run a few hours ago and now shows the safetynet check error when I want to play). Didnt installed nothing. Tried "Go to magisk settings and change mountspace mode. It should fix the safety net. Disable and enable magiskhide again before checking safetynet.", Still no luck.

Should I update to v13?

Thanks
[Magisk] lahceneamine:
Every module get loaded perfectly now ;)

Thank You

=============================

Edit :

SafetyNet fails in this last beta

Galaxy S8

TWRP 3.1.0-1

Custom ROM and Kernel
[Magisk] uncle_gonny:
SafetyNet's checks ctsProfile e basicIntegrity are failing on my end since update to Magisk v13.0 (b3da28e) from 1e87780.

I flashed from recovery with no errors and cleared cache/dalvik. Am i doing something wrong?
[Magisk] Didgeridoohan:
If you are prepared to help with testing and providing the proper details and logs, sure.
[Magisk] JEANRIVERA:
same thing here...
[Magisk] de.er:
I'm suddenly failing Safety Net as well, both on v12 and v13...

D802, RR 5.8.3
[Magisk] DenyDarko:
Same here. LG G5 H850
[Magisk] Nomelas:
I guess Google found out how to detect magisk
[Magisk] dt0807:
I'm going to make an educated guess here...I think Google just changed something on their side regarding SafetyNet. Both of my devices (OnePlus 3T and Nexus 7, on different ROMs/setups) were passing earlier today just some hours ago with v12, and I just noticed that they now both fail :eek:

EDIT: basically what the post above mine says
[Magisk] Midomad:
I can confirm.
[Magisk] will5:
Good to hear is a know issue. New google protection or detection should gone up just a few hours ago. I was using safetynet required apps until 3 hours ago.

Ill try to help with testing.
[Magisk] Iradj:
Yep also on my side Magisk v12 and v13 Safetynet fails, both worked few hours ago fine.

Samsung Galaxy S7 Edge

Stock Rom Nougat 7.0
[Magisk] xHardes:
When I update to the new version from 14.5 to 14.6 the MagiskManager says that Magisk is not installed. I have a Asus Zenfone 2 Laser ZE500kl.

I hope you guys can help me.
[Magisk] Nevermindthelabel:
Perhaps someone can. However you need to read the first post and do accordingly. Pay close attention to something in red.
[Magisk] PRADEEPHONDA:
Uninstalled previous version & flashed through twrp so it works fine.

Definitely Root works & Safety net pass. No issues whatsoever on Samsung Note 5 - SM-N920G. Xposed v89 also works without any issues so far.

Thank you for all the contributors of #Magisk & #Xposed.
[Magisk] mikevb:
On Nexus 6 Nitrogen OS 8.1, 14.6 passes basicIntegrity but not ctsProfile.

When I upgraded from 14.5 using an uninstaller from September, it failed so I used the latest uninstaller. Maybe that failing broke it a bit somehow? Will be trying clean flash soon.
[Magisk] ShadySquirrel:
14.6 broke AFWall for me, completely. Magisk isn't even reporting when app is requesting root access, and after I enable it manually, Manager just disables root for AFWall, for fun and games, I guess.

Log from AFWall after root request is sent:

12-23 19:44:42.318 30789 32222 I AFWall : State of rootShellBUSY
12-23 19:44:42.318 30789 32222 I AFWall : Forcefully changing the state BUSY
12-23 19:44:42.318 30789 32222 I AFWall : Start processing next state
12-23 19:44:42.318 30789 32222 I AFWall : Total commamds: #1
12-23 19:44:42.434 30789 30789 E AFWall : libsuperuser error -2 on command 'true'
12-23 19:44:42.434 30789 30789 I AFWall : Start processing next state

And Magisk's su says just denies su request, even if AFWall has access enabled:

12-23 19:45:45.467 260 32328 D Magisk : su: request from client: 17
12-23 19:45:45.467 260 32328 D Magisk : su: request from uid=[10177] (#1)
12-23 19:45:45.473 260 32328 D Magisk : su_db: query policy=[1]
12-23 19:45:45.474 260 32328 D Magisk : su: waiting child: [32329]
12-23 19:45:45.476 32329 32329 D Magisk : su: child process started
12-23 19:45:45.478 32329 32329 D Magisk : su: argc=[1]
12-23 19:45:45.479 32329 32329 D Magisk : su: argv[0]=[su]
12-23 19:45:45.481 32329 32329 D Magisk : su: pts_slave=[]
12-23 19:45:45.483 32329 32329 D Magisk : su: use namespace of pid=[32325]
12-23 19:45:45.485 32329 32329 W Magisk : su: request rejected (10177->0)
12-23 19:45:45.488 260 32328 D Magisk : su: return code: [1]

Next time I open Superuser tab inside manager, it says I've denied AFWall's root access.

What the hell is happening? Reinstalling, clearing data, rebooting, nothing helps.

To make it worse, it works normally for AdAway, Nova Launcher (used for screen locking) and FX File manager.
[Magisk] chudy_85:
For person who have honor or huawei. You must use this configuration using update from magisk 14.5 to 14.6 !!!! Use install using magisk manager 5.5.0 look on my screenshot

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] kiwigi:
Ok. So once the phone is un-rooted do I install TWRP, then Magisc Manager then root with Magisc Manager? Any tools like MagiskHide after that?

Is that correct?

Thanks
[Magisk] Razor10707:
Yes you need twrp then you need to flash thr magisk zip in twrp because if you don't have a older version of magisk it will just download the file then make you reboot to twrp where it gets flashed
[Magisk] michaelnothing:
Attention nanomod users. Magisk 14.6 breaks nanomod. After flashing magisk my nexus 6 sat on the google screen. I went back and uninstalled both and then reinstalled them and got my phone to boot. I had nanomod and microg working until this morning when I updated to magisk 14.6. Before I was on 14.5. I am running 8.0 ColtOS. The nanomod patcher throws error 1 at settings.apk. Microg has signature spoofing unchecked like nanomod is not installed. I didn't have an option in developer options for signature spoofing before, but, everything was checked in microg. I will try to find a copy of magisk 14.5 to remedy the situation, but, I wanted to report the problem as 14.6 unrolls a lot of bugfixes and updates. I have also duplicated this post in the nanomod thread.
[Magisk] michaelnothing:
And in case anyone wants a look here's a log. I searched and found how to make one like a big boy for the first time in five years of flashing ROMs and mods.?
[Magisk] nightraving:
Any advice from anyone? Although not that it matters now, since I accidentally booted to system after reflashing stock OS and therefore had twrp overwritten. I'm currently without a PC and rooted from my grandparents desktop the other day. Looks like I'm stuck without root till I get a new PC in January, right? Or is there a way around this?
[Magisk] pWEN:
Thanks for the new instructions. Here's what I did:

Flashed stock boot.img

Copied stock boot.img to device

Opened Magisk Manager app

Checked to preserve verity

Clicked Install, chose boot.img on device, it patched successfully

Copied patched_boot.img to computer

Used fastboot to flash patched_boot.img to phone

Rebooted to OS

No "internal problem" error!

Opened Magisk - asks me to install, fails SafetyNet

I found these instructions on the official Magisk thread as well (dunno how I missed them before), and made sure that I followed the process correctly. I don't know why it didn't work. Maybe because it used a Magisk 14.0 version when it patched the boot.img? It didn't give me an option to use any other version. (Maybe I can just put 14.6 zip in the MagiskManager folder and rename it to 14.0?) I've attached a log from the patching process.

Also, I'd still like to use ElementalX with this. The instructions say you can use a custom kernel instead of the stock boot.img, but ElementalX doesn't provide one until after it's installed, and you can make a backup... but that requires root. So that puts me in a Catch-22 of "can't back up EX kernel without Magisk, can't patch Magisk without EX". Do you have any suggestions on how to do this with EX instead of stock?

Thank you for the help, I really do appreciate it! I keep tabs on this thread and the official Magisk, but if there's another thread that's more specific to what I'm dealing with, please let me know.

Edit: just tried copying the 14.6 zip into the MagiskManager folder and patching again, but it just downloaded 14.0 and overwrote it.
[Magisk] killerBRs:
Magisk 14.6 is causing bootloop in Android load/boot, After kernel boot,

I have to return to 14.5 to back working.

Samsung Galaxy S6 Edge SM-G925i Android 7.0 stock
[Magisk] Didgeridoohan:
[MENTION=4791226]pWEN[/MENTION]

Change the update channel in the Manager settings to "Beta"...
[Magisk] Amos91:
Had a quick search but couldn't see anything...

Just updated to 14.6 and all my modules have disappeared. Now no modules will install, says unable to extract zip file, installation error.
[Magisk] pWEN:
Ah, thank you!! I've never had to do that before, so forgot it was a thing. Sorry for the n00b moment.

That downloaded the 14.6 zip and patched it, and flashing the patched image got me Magisk root without the "internal problem" error. Hooray! But I was a bit too bold; I then booted into TWRP and flashed ElementalX and the error came back. I'm going to comb through the EX thread again to see if I can find out how to get that modified boot.img so I can patch that through Magisk instead of stock. I have a much better understanding of the process now, though. :D
[Magisk] masri1987:
Why would I need to flash stock boot?

Having same issue
[Magisk] Ja_som:
Because that one in device is already patched with Magisk, stock is not.
[Magisk] Ryan.Feezel:
Will this work with verizon s7e or nahhh
[Magisk] efilty:
Not able to answer incomming calls

Running Magisk v14.6 on OP3T, OOS 5.0, Oreo. I am not able to answer incoming calls. Screen wakes up, but there is no slide to answer button. I tried to disable module 'OOS call Recording enabler' but then it got worse and screen did not even wake up when reciving phone calls. Any suggestions? Only way to answer a call is pull down the notification meny and then answer the call.
[Magisk] shae23:
Did that, bootloop still
[Magisk] masri1987:
So I did what you said, flash boot or kernel flash magisk 14.6. Allowed superuser . Rebooted. Superuser permissions lost.
[Magisk] Ja_som:
Then I don't know how to help you, for me this process was helpful.
[Magisk] jenslody:
Did you try to completely remove afwall from superuser-menu ?

Tap on the afwall entry, so it gets enlarged, tap on the trashcan and remove it completely and let ist ask for root-rights again.

It works fine here on my system, after update from internal beta and after a fresh install of Magisk.

There might be problems if Magisk is updated from earlier versions on some systems, that does not occur on a clean flash.
[Magisk] ShadySquirrel:
I did that, too, first few times, but after I remove it from the list, it simply returns it back as soon as I leave Manager and reopen it :D So went to the safe route and cleared manager's data, reauthed all other apps and got same behaviour - Magisk simply silently denies AFWall, doesn't even prompt for permission, and forces me to manually allow it, just to disable root permission next time I start the app. Peculiar and very annoying bug, I say.

Had no issues with previous betas - all worked fine until now. Could this be something with encryption? I've encrypted my phone a little bit before 14.6 was published (had some mess with 14.5 there which was solved by a simple clean/reinstall), and that's when all fun started (battery gauge started acting up after encrypting my phone, too).
[Magisk] guest4711:
fr

While on 2 devices the update from 14.5 to 14.6 went without problems I had similar problems on a 3rd device: Even deleting all entries and setting the default to "allow" did not help. I solved it by flashing uninstaller and magisk afterwards.
[Magisk] VincentJoshuaET:
I guess OP should advise that a semi-clean install is recommended to update to Magisk 14.6 (restore stock boot image, then flash Magisk).
[Magisk] flar2:
Boot into TWRP, install EX, then backup the boot.img in TWRP. Select the backed up boot.img to patch with magisk.
[Magisk] pWEN:
I did try that, but it gave me an *.emmc.win file instead of an *.img file. I Googled what TWRP gave me and what I read was that it can't just be renamed to have an img extension, and I couldn't find another option to make it export as an img instead.
[Magisk] KaMyKaSii:
In fact it is exactly what should be done. Just rename with ".img" at the end
[Magisk] ajh16:
Any chance you might have the 14.37 zip anywhere? It seems that the selinux repo that the tag was tied to isn't working so I can't build it from source and my phone is generating about 30gb of log files a day running 14.5 (and 14.6 just outright doesn't work.)
[Magisk] vickybonick:
Hey [MENTION=4470081]topjohnwu[/MENTION],

Few Apps2SD users have reported issue related to unmounting a directory. The mount gets unmounted for root user but other users/processes can see the mount (Even with -mm flag and Global namespace). Can you please check it out. If you want any logs I can ask the users
[Magisk] socali:
You bet! I'm hanging on to that for dear life.. it's the only version that works on Essential right now.

magisk-14.3.zip
[Magisk] ajh16:
Fantastic, I'm no longer being firebombed with dozens of gigabytes a day in error logs. Will be nice to see how much my battery life goes up too since the system was taking a full 26% of the battery consumption.

Update: Perhaps I spoke too soon. It is not as much anymore, but I'm still getting a few log entries a minute (instead of many a second) about a bind failure due to address already being bound. I'll have to dig in a bit and see if I can figure out what binds could be failing since it is remarkably sparse on details.
[Magisk] ShadySquirrel:
I'll have to try that in the end. I got kind of more important bug with battery gauge right now I have to fix.
[Magisk] Razor10707:
Thanks will try on my p9 lite and should I direct install right?
[Magisk] chudy_85:
First magisk v14.5 normal if it work for you.

Next you download new magisk menager and open

Secend lock on my screen and then update magisk to 14.6 internal update.

Reboot device and you must see your magisk it's update

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] Razor10707:
Ok thanks
[Magisk] firozpatel:
Can anybody help?

I don't have xposed installed to trip safety net

Is 14.6 not compatible with my device

I have Samsung galaxy S6 edge
[Magisk] shanar585:
Anybody have a copy of 14.5 zip?
[Magisk] wackygoose:
I don't get it, can you reproduce the steps please?

---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------

Sad. Does flashing stable version helps?
[Magisk] SHãdøw:
Here you go
[Magisk] SHãdøw:
File attached
[Magisk] shanar585:
much appreciated, thanks
[Magisk] Didgeridoohan:
Try uninstalling the Manager, from within the Manager (Uninstall -> Uninstall App) and then reinstall v5.5.0 again.
[Magisk] wackygoose:
**** i ****ed it up, I tought it was ok to just flash 14.0 because I have backups, I was wrong, now I get bootlops and cant access recovery to restore it :(.

What can I do now?
[Magisk] Badger50:
I don't know what device you have, but can you fastboot twrp recovery??
[Magisk] leo.riv:
[MENTION=4470081]topjohnwu[/MENTION]

I am having issues with 14.6 on my Lenovo VIBE X3 (X3a40) 64bit android 6.0.1

I was able to flash Magisk 14.3 via TWRP with no issues.

after fash 14.5 or 14.6 have stuck on bootloop

I am uploading the recovery logs

Please help me

View attachment recovery.log
[Magisk] guest4711:
On all devices I know you can enter recovery even if you cannot boot system. Try powering down your device by holding the power key or removing the battery. Reinsert the battery if necessary. Press volume down+volume up simultaneously and hold them. Press power until device logo appears. Release the other keys. You should now see your TWRP. If not, you'll find the correct way in the support forum of your device.

In recovery flash magisk uninstaller (or your ROM). Reboot and see how it works (you loosed root this way). If all ok reboot to recovery and install your preferred magisk...
[Magisk] wackygoose:
oh damn what a rush, I managed to get into flashmode and use flashtool to get back to old stock rom, its all good now.

I could not access recovery at all XD

Thank you all
[Magisk] dev_freak:
It doesn't work. Can't pass safety net
[Magisk] brqndon:
Does anyone with an Essential Phone pass SafetyNet on v14.3? Was rooted and passing SN fine up until last night where I can't get SN to pass.

Magisk v14.0 flat out doesn't flash, 14.6 flashes fine but doesn't acquire root, and now v14.3 doesn't pass SN despite it having root just fine.
[Magisk] Badger50:
That's like saying...my car is broke!

More info is required to get proper help.

What device?

What OS?

Method of installation? :eek::rolleyes:
[Magisk] dev_freak:
OnePlus One with TugaPower 8.0. Recovery Zip install
[Magisk] ITLfx:
It works with honor 8 frd-l09b432b398 emui 5.0.1
[Magisk] G.M.L:
For LG L90 D405(w7) users information 14.6 works normal without problems.
[Magisk] topjohnwu:
Do you have a boot image for me to test?
[Magisk] xHardes:
I've send you a pn, because I can't post links at the moment. And Merry Christmas [MENTION=1007992]everyone[/MENTION] :)
[Magisk] chazarss:
Hi all, my phone just got Android O update, then rooted via magisk but I am not able to install any modules that I used previously and even modules in magisk manager app, installation process just failing. Is there any known issue?
[Magisk] xHardes:
Have you tried to restart your device or reinstalling the MagiskManager?
[Magisk] chazarss:
Of course i have tried many times
[Magisk] masri1987:
Thanks. I went back too v14.0 even battery life seems better too
[Magisk] kush1131:
here is the logs
[Magisk] korom42:
Magisk 14.6 is breaking DRM keys patch for my Sony Xperia XZ
[Magisk] korom42:
[MENTION=7576304]brqndon[/MENTION] I just took 10 minutes scrolling the page down couldn't you compress and upload your log file in zip format or at least make the text hidden in your comment !!

You're just making it harder for developers and any one who tries to help so please fix that .
[Magisk] CecoM:
Confirmed as the only way to update from 14.5 to 14.6.

Huawei MediaPad M3 (BTV-DL09 C100B303) Android 7.0

Clean install (Stock Boot + TWRP) with 14.6 went to wait, restart, wait, erecovery.

Same with update from 14.5 to 14.6 with default advanced settings:

[x] encryption

[ ] AVB2.0/DM-Verity