yashsingh1/xdaforums huggingface dataset:
[Magisk] anandverma458:
Yes, I have tried that too. But my main problem is the bootloop after magisk install. And it is not an ordinary bootloop, its a kernel panic. Thank you by the way for replying so quickly!
[Magisk] TheKnux:
Would [MENTION=1162986]Captain_Throwback[/MENTION] or someone be willing to make either an official or unofficial TWRP for the Moto z2 force (nash_tmo) I would if I had the knowledge.
[Magisk] pjbeee:
G5 Plus XT1687 (USA)?

Being that it's (at least one of) the best and least-expensive "full-featured" Android phones at the moment, do you have anything for the latest stock ROM on the Moto G5 Plus USA (Non-Amazon) XT1687?

What would it take to get you to help root this with Magisk? If it's not too costly, I would like to make a donation and provide this information for free to the community (and hopefully you would gain some additional donations as a result).

Apparently because of encryption or some-such, it's not so simple on the G5 Plus.

BTW I have successfully rooted two Nexus 6P devices with v14.0, made a donation, and thanks for that!
[Magisk] Didgeridoohan:
Sounds like it's incompatible then... Did a quick web search and that seems like a seriously locked down device.

If you can upload the recovery log [MENTION=2807229]Strephon Alkhalikoi[/MENTION] asked about above and a copy of the boot image, someone who actually knows what they're doing might be able to look at it...

Wrong place to ask... And isn't it enough with the work already in progress?
[Magisk] mamutal91:
Hello friends. I really need your help. Thank you
[Magisk] nisavid:
/data/magisk_merge.img mount failed...

I've been running into that a lot too. I found that I can work around it reliably by installing a module that is already installed, then installing any modules that hit this issue.
[Magisk] mamutal91:
Sorry I do not understand. Could you explain more to me what I should do?
[Magisk] Weegee1:
Magisk did its thing and after rebooting i got screen saying something about shutting the device off and taking it to Verizon Samsung sm-j100vpp
[Magisk] k0m3n9:
LOL. My mistake. I didnt noticed abt that.

Is there a way to manually set the Boot Image Location.. coz whenever i try to use patched boot image installation method, Magisk manager keep shows cannot auto detect it. Maybe this just issue on SM-J111F running stock lolli 5.1.1. Tried to find any other post regarding same issue but not found any.

---------- Post added at 08:09 AM ---------- Previous post was at 07:58 AM ----------

Your issue same as mine.. manager unable to detect boot img location.. only on different model..
[Magisk] fOmey:
Post your magisk log.
[Magisk] mamutal91:
Tks
[Magisk] nogaff:
Sony Xperia Z3 Compact

I finally got this working by using ta_poc to create a boot.img with Sony RIC disabled and then running the Magisk installer on that and flashing the patched boot.img.

However, according to this, disabling Sony RIC shouldn't be necessary as of Magisk v13?
[Magisk] Zwitterion:
While on 14.1, I randomly lost root Magisk's bypass functionality.
[Magisk] Strephon Alkhalikoi:
Not a Magisk issue. This could be resolved with a custom bootloader or kernel, but Verizon locks bootloaders. You'll have to see if there is a Magisk module that can help.
[Magisk] ryaniskira:
Magisk 14.2 blocking NSG?

I am thinking something Magisk 14.2 is doing when it patches the boot image is interfering with Network Signal Guru. My Pixel XL was working just fine up until I updated to Magisk 14.2, it claims there is a driver error which means a kernel/boot image modification. I am using my ROM's stock kernel.
[Magisk] prasetya27:
Can confirm Magisk v14.2 work perfectly on my ZE601KL and include Viper4fx modules no bug at all.. Thanks dev for your good work [MENTION=658468]topjohn[/MENTION]
[Magisk] fOmey:
Same issue I'm having with some of my devices

This is your problem:

E( 444: 457) mount /dev/block/loop0->/magisk failed with 13: Permission denied

E(11409:11409) mount /dev/block/loop1->/dev/magisk_merge failed with 13: Permission denied

--------- beginning of main
I( 444: 444) Magisk v14.2(1420) daemon started
I( 444: 446) ** post-fs mode running
--------- beginning of system
I( 444: 457) ** post-fs-data mode running
I( 444: 457) * Mounting mirrors
I( 444: 457) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system
I( 444: 457) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I( 444: 457) bind_mount: /data/magisk -> /dev/magisk/mirror/bin
I( 444: 457) * Mounting /data/magisk.img
E( 444: 457) mount /dev/block/loop0->/magisk failed with 13: Permission denied
I( 444: 663) ** late_start service mode running
I( 444: 663) * Running service.d scripts
I( 444: 663) * Running module service scripts
I(11407:11407) Create /data/magisk_merge.img with size 64M
E(11409:11409) mount /dev/block/loop1->/dev/magisk_merge failed with 13: Permission denied
[Magisk] anandverma458:
Here's the link for stock boot.img:

https://mega.nz/#!W49yiaQI!_-ueJKvRTMiF6QxUiTWTBThpYhKl2ArHQI4oUHe7Mms

And the recovery log is attached with this post.
[Magisk] demonoidmaster:
Please use an online service like pastebin to link your massive wall of text.
[Magisk] Zehlek:
What's wrong with Magisk? I have it installed and I can even use root apps but after a few hours it says Magisk is not installed and I have to reflash it. This happens at least 4 times a day. Please fix
[Magisk] Didgeridoohan:
Please provide logs or details on how to reproduce.

There's currently very little info on this issue. [MENTION=6429309]DodoGTA[/MENTION] have found that it might be related to MagiskHide, but without more info it's impossible to know...

You could try disabling MagiskHide and see if that changes anything.
[Magisk] Zwitterion:
I have had the same issue. Magisk seems to work well and then it loses its functionality for no apparent reason. There are no magic steps to reproduce - simply flash Magisk and it works for awhile until it doesn't.
[Magisk] Didgeridoohan:
Ok... Let me rephrase that: disable MagiskHide and report back if it changes anything.

Some kind of info is needed to troubleshoot. Many, many users aren't experiencing this, so the ones that do need to step up and help solve it.
[Magisk] Zehlek:
I had to reflash. When it says it isn't installed there want an option for logs :(
[Magisk] sumitarora2:
I am facing same problem but after restarting device problem fix untill it happen again, i don't have to reflash magisk
[Magisk] karatekid430:
Hello. I like Magisk - it is modern, and SuperSU is a complete joke now, how you have to jump through hoops to pass SafetyNet.

However, may I suggest an option to hide Magisk from all apps *except* those specified? Or else a toggle all switch, so I don't have to spend five minutes every time manually checking everything. Thank you and great work!

I really need to learn how systemless rooting *actually* works - I am a bit vague. My idea was to patch the kernel to "mount" the su binary where it needs to be, and deny the existence to any UID not allowed - and redirect those who are allowed to execute the binary, presumably in the initrd. Presumably this is similar to systemless root, except afaik you don't tamper with the kernel directly.
[Magisk] kd0g:
Calling SuperSU a joke is like calling Linux a joke in comparison to Android
[Magisk] BokeB:
Try flashing unSU Script before installing Magisk.

Seems to solve this issue, for me.

https://xdaforums.com/showpost.php?p=63615067
[Magisk] Ubimo:
Can you please provide a log (magisk_error_2017......log)

I have lots of entries and repeating events in it. See attachment.
[Magisk] shadavis08:
Thanks for that info.

Magisk manager itself is what caused my bootloop. When it asked me to update to v12 from v11.6. I updated which sent my phone into the loop
[Magisk] slipk487:
Doesn't detect boot on galaxy j7 (j700t1)
[Magisk] aamadorj:
dumpsys battery stats error

I know the error when running "dumpsys batterystats --reset" command is been mentioned at the unofficial Magisk snapshots thread, but it seems the issue is still present at current v13 beta (1777d9f_v2 and all previous v13 betas) on my N6P with latest PureNexus (7.1.2_r8) and latest ElementalX kernel (4.09).

Using an elevated terminal, the command "dumpsys batterystats --reset" will return "Error dumping service info: (Unknown error -2147483646) batterystats". What kind of log can I provide to help pinpoint the reason of this error?

This is the only issue I've found with the v13 betas.
[Magisk] dreinulldrei:
From what I experienced, it did work in beta 0b4baad, but stopped working on 1777d9f. It simply does not correctly map the apk included to /system/priv-app.
[Magisk] shadavis08:
Where is the Uninstaller?
[Magisk] Ja_som:
In the main thread
[Magisk] dimm0k:
is uninstalling previous versions of Magisk always required or just this test build?
[Magisk] DenyDarko:
I was talking about this test build as it has been published to test the patch errors
[Magisk] otaconremo:
Magisk manager app always crashes upon opening.

The only time I can open it is when it's newly installed or when I clear data from app settings. Also, the app doesn't give root permissions although it says in the app that magisk and magisksu is installed.

The only version that works for me is the unofficial version 170528.

What logs do I need to post here for this problem? I'll try to flash again the latest version and get the logs for it.
[Magisk] Deic:
From terminal (be sure you have all debugging options enabled from Android Developer settings)

su
logcat | grep $(busybox pgrep com.topjohnwu.magisk) > /data/magiskmanager_crash.log

Run Magisk Manager.

When crash, close the terminal and the log is on /data/magiskmanager_crash.log.
[Magisk] JERW28:
[MENTION=4470081]topjohnwu[/MENTION] the not all mods mount still happens with 1777d9f v2. The logs can be found here: https://github.com/topjohnwu/Magisk/issues/235
[Magisk] topjohnwu:
Magisk v13.0 (1e87780)

Think I cleared out all weird issues for flashing Magisk now. The only change is in the flashing script.

New beta is up in the OP, finally we can test the real thing rather than the trivial bugs in the scripts:rolleyes:

Thanks for those who are willing to help!
[Magisk] otaconremo:
app crashing

Thanks. Here's my log from version 1777d9f with the app crashing.

Please note that I still haven't opened the app while perfoming the commands so the app still gave me root. After I issued the command and went to open the app, it then crashes.

Haven't tested the latest version yet. Will also upload tomorrow after I tested it and if it still crashes. Most probably it will since the app isn't updated. :D

Also included recovery and app's log if it helps.
[Magisk] Zehlek:
Which Magisk 13 in op do we flash?
[Magisk] 5m4r7ph0n36uru:
If you klick the Download link at the top of the OP it'll download the latest one. Thus you don't have to search which one is the latest.

Easier: read some posts back and you'll find the answer given by the OP...
[Magisk] JERW28:
[MENTION=4470081]topjohnwu[/MENTION] Not all mods mount issue is still happening on Magisk v13.0 (1e87780). New logs here: https://github.com/topjohnwu/Magisk/issues/235
[Magisk] lahceneamine:
MAN I LOVE YOU !

This BETA version rocks !

Everything is working perfectly.

AND I haven't that long (boring) boot time anymore :D

It boots up in 20 seconds only (7 sec on the splash/first screen + 13 on boot logo/second screen)

Now I'm gonna try a module (ART Optimization) which was causing a terrible long boot time (3 minutes ^^) and report back ;)

My Device Specs :

- Samsung Galaxy S8 (G950FD)

- CustomROM (BatmanROM)

- Custom Kernel

- 5 Modules

- TWRP v3.1.0-1

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

Edit :

I've installed the ART module, it always boots up very quickly, but I can't call the module from Terminal using the needed command (it tells me script not found in terminal).

This module used to put a script in the post-fs-data.d folder, but it doesn't seem to be the case with this beta.

Sorry if I went out of the subject, I've attached a log anyway.
[Magisk] :
Much easier: read the title of the thread and compare the numbers / letters ?
[Magisk] mamutal91:
I do not know how to solve it. No one can help.
[Magisk] flocke000:
I got the same problems for the last few weeks.

Let me see if I can get a log the next time it happens.

And I'm gonna try the unSU script next time I flash an update of my ROM, although it is not pre-rooted from what I know.

Edit: Also I don't have to re-flash, a simple reboot and Magisk is back and working. Seems like something gets unmounted that shouldn't. Maybe it also is a problem of the Universal SafetyNet Fix module, since Oreo (Nitrogen OS) I have to use it to pass SafetyNet.
[Magisk] guest4711:
But Linux is a kernel (and nothing more). Android is a complete OS like OpenBSD or GNU with Linux kernel. ;-}
[Magisk] kishd:
Linux is the best-known and most-used open source operating system.

Android is based on Linux.
[Magisk] cmjester6421:
Correct me if I'm wrong he but I noticed apps not working as they did I have look at this for a whole day busybox is not being picked up by a few apps. What could be causing this?
[Magisk] Strephon Alkhalikoi:
[MENTION=4313092]kishd[/MENTION] and anyone else trying to defend SuperSU in the Magisk forum: SuperSU's ownership (i.e. CCMT) has proven itself untrustworthy by trying to sneak analytics software into the code. This wouldn't be an issue if SuperSU was open source software, which it isn't. That said, we're not having a contest between SuperSU and Magisk here, and all the SuperSU discussion is off topic and needs to end.
[Magisk] andrewk36:
Linux is actually just a kernel, it's a common misconception that it is a complete operating system. Most distributions you use like Ubuntu are based on GNU/Linux, not just "Linux".
[Magisk] kishd:
Hate to go so far off topic so this will be my last reply. Linux refers to the whole loosely based alliance that gives us the full operating system and when referring to the kernel only it is called the "Linux kernel"
[Magisk] cmjester6421:
Ummm ya this is pointless who's bigger conversation. So back to magisk and my post above this bs, anyone care to have some input as this phone is my daily driver?
[Magisk] guest4711:
Sorry, I don't get your point. What is your problem? In your screenshot you meant "ls", not "is", right?
[Magisk] cmjester6421:
Lmfao that was a nice one on my part. Yes I sent the command again correctly and received no such file or directory found still at a lose here. It's sad I've all but fully installed a flashable port of kali after porting the kernel I have just a few bugs. But simply installing a magisk module won't work I want to have options open to ppl when I post my work. At this point like I said I'm doing a nuke and pave and hoping for better luck.
[Magisk] fOmey:
That's because there is no solution at the moment, We just need to be patient and wait for a magisk update. :)
[Magisk] digiNZM:
Could the issue be caused by Mediatek's implementation of loopback-support? Just curious.
[Magisk] Sgace:
On a Pixel here with 14.2 beta. Taking an ota update went flawlessly. Thnx!

Cheers
[Magisk] WarningHPB:
Just on a Pixel XL (Marlin) just thought I'd share my experience:

I think i finally got it to work, I applied the full October security patch (minus the -w on update to keep data) so I would be back to stock without SuperSU.

I then booted the newest version of TWRP (3.1.1-0) downloaded from https://eu.dl.twrp.me/marlin/

Then when booted into TWRP (fastboot boot twrp-3.1.1-0-fastboot-marlin.img) I queued the "twrp-pixel-installer-marlin-3.1.1-0.zip" and then " Magisk-v14.2(1420).zip" to be installed which i moved onto the Pixel XL while in TWRP.

Then rebooted into recovery just to check that TWRP had installed properly which it had. Rebooted again but into system everything seems to be up and running with out any issues.

Will report back if there are any issues.
[Magisk] fOmey:
I'm not familiar with Mediatek devices, I only recently received mine..

It's been a nightmare from the get go tho.. I have a semi-working TWRP recovery, with no touch support... no kernel sources... magisk doesnt work.. it's just one thing after another !
[Magisk] steveo17:
echoing this comment. the ota on the Pixel XL went flawlessly. it would be really cool to see in a future update a way for Magisk to intercept the OTA and auto reinstall once it hits step 2.

nevertheless, very happy with the new Magisk!
[Magisk] joderme:
Not sure what the heck is going on with my device. The OTA fails during step one.

Edit: I'm an idiot and noticed during a logcat that the boot.img files for old and new didn't match. Forgot to restore boot.img...

10-02 19:31:19.080 748 748 E update_engine: [1002/193119:ERROR:delta_performer.cc(1057)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
[Magisk] karatekid430:
Okay, maybe a bit harsh, but with SafetyNet, hiding root is mandatory. It needs to be included in the package. I like Magisk how it only came about with Systemless rooting, and started with a clean slate. SuperSU was obviously excellent, up until the systemless era where it had to be hidden.

I believe Chainfire does not think hiding is a good idea, but understands people will want to do it. I don't know why it is a bad idea. Google will tell you that rooting is a security risk and a bad idea, itself. If we are rooting, we are already breaking from convention.
[Magisk] sanryone:
XT-1605-05 moto Z not support install ok

install module failed

Mounting /data/magisk_merge.img /dev/magisk_merge

! /data/magisk_merge.img mount failed..

failed!

recovey install success. but magisk module

Android version 7.1.1

NCC26.118-31
[Magisk] CapnShiner:
Is anyone else losing root after restoring apps or data from Titanium Backup?

I did not have battery optimization disabled for Magisk Manager, so that could be part of it, but I did change that now. I haven't needed to restore anything since doing that.

I am running Oreo on my Pixel XL with the October security update. Kind of a long story, but I ran into problems trying to upgrade to Magisk 14.2 from the unofficial Magisk 13 build for Pixel devices and I ended up having to factory restore my phone. I figured I may as well let it install both OTAs before I reinstall Magisk. I also updated TWRP to the latest version. This is why I miss having MicroSD support in my phone. My backups from TWRP and TiBu were not uploaded to cloud storage, so I lost them. I had to use older backups I had copied to my PC. Some things restored from TiBu just fine but then it got stuck on one of them. I force-closed TiBu and when I opened it again it couldn't get root privileges. I reinstalled Magisk from TWRP and everything is good for now. Just wondering if anyone else has experienced something similar with TiBu.
[Magisk] Zwitterion:
Any reason why I can't seem to get the October OTA? I hit Check Update in the settings section, but it says I'm up-to-date with September.
[Magisk] digiNZM:
Exactly the same here - first Mediatek device (just had to try) - been a hard start. Got a non-flashable TWRP now that is fastboot-able and working fine. Kernel sources as requested on multiple places are not available. I am assuming that we don't have proper loopback support now. Investigating different kernels now.
[Magisk] guest4711:
Because the unofficial build uses it's own keys for signing you have to uninstall it (rsp. MagiskManager) before installing the official build. Directly updating from official to unofficial or vice versa is not possible.
[Magisk] CapnShiner:
I did try to uninstall, but not until after I tried to just install 14.2 over the unofficial 13. I'm assuming the damage was already done.
[Magisk] jenslody:
It should work if you uninstall the (old unofficial) MagiskManager the "normal" way (launcher) and reboot into recovery, dirty flash Magisk (again) and boot into system and wait until the Manager appears.

Or unpack the MagiskManager from the zip-file (it's in the common-folder) and install it manually.

If nothing works you need to reflash your stock (or custom) boot.img.
[Magisk] patroll:
After giving root rights to Adaway and booting I get ramdump and my rom does not boot again.

Before that everything is working. I'm on Pixel xl and Lineage 14.1.
[Magisk] Th3be4st:
Is anyone able to play fate/grand order with magisk? I tried everything, disable magisk, hide root with magisk hide, i also tried unistalling magisk manager but it always give me error. On the other hand if i restore stock boot image it works. What does it detect? How can it know that i have magisk installed?
[Magisk] nisavid:
None of that helped me when coming from an unofficial build of Magisk 14 (14.0 + some part of 14.1). I couldn't get Magisk Manager 5.3.5 installed—neither from the APK with Package Installer, nor from the Magisk 14.1 ZIP via TWRP. Reflashing factory boot & system images did not fix it. Somewhere in the data partition, something was storing the signature from the unofficial build, which caused the new official build to be rejected due to a signature conflict. This was after uninstalling the unofficial build of Magisk Manager (after clearing its data) and verifying that there were no remaining directory names in my file system that contained its package name, com.topjohnwu.magisk. It seemed that no matter what I installed/uninstalled/cleared/reflashed (short of wiping the data partition), I couldn't get the official Magisk Manager to install.

Package Installer kept failing with this message:

Flashing the official Magisk also failed to fully install Magisk Manager. adb logcat showed this:

Unfortunately, I had neglected to properly uninstall the unofficial build of Magisk (via the Magisk uninstall ZIP) prior to flashing the new official build. Perhaps this would have avoided the issue.

What got me unstuck was uninstalling the lingering reference to the unofficial build via ADB:

adb uninstall com.topjohnwu.magisk

For good measure, I then reflashed my factory boot & system images, TWRP, a custom kernel, (official) Magisk, and Busybox (via the installer by osm0sis). Everything was back to normal after that.
[Magisk] zeugme:
Magisk 14.2 also not installing on Pixel C (latest Oreo of October 2017) from TWRP. It is already the case for all versions since 13.3 (which is still working).

How can I fix the problem?

Do others Pixel C owners also have the same problem?

Thanks!
[Magisk] gothicVI:
Twrp log...

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[Magisk] steve51184:
Getting fails on v14 and v14.2 was working last night... I'm new to magisk... This just a sit and wait for an update type thing or what as on suhide 0.55 device it's still working after almost a year? Back on topic the m device in question is a Samsung and needs the 'universal safetynet fix' but again I can't pass at all now... Looked a few pages back sound nothing :(
[Magisk] Ja_som:
About safetynet, please read the OP
[Magisk] pairedprototype:
Just installed on my Pixel XL v8 (October build). Working well so far and passes Safty Net.
[Magisk] steve51184:
I did/have there's nothing there about it?
[Magisk] Ja_som:
It is:
[Magisk] Pkt_Lnt:
You missed this - ;)

SafetyNet / CTS / XXX app won't work after enabling MagiskHide:

Unless you can specify how to improve MagiskHide, for example: what additional boot props to patch? What does the app detect? Or else

Please do NOT report ANYTHING related to these kind of issues!
[Magisk] steve51184:
I'm lost I haven't just enabled magiskhide it's been working since v13 when I started using it and now it doesn't.. Want does that quote have to do with anything?
[Magisk] Ja_som:
That last red sentence.
[Magisk] steve51184:
So a thread about a beta software doesn't allow people talking about the beta software?
[Magisk] Ja_som:
But this thread is about Magisk beta, not about safetynet...
[Magisk] steve51184:
It's a part of the app? Where do I ask about this then?
[Magisk] zeugme:
Sorry! The TWRP Log:

https://pastebin.com/2JVULcF3

Thanks a lot!