yashsingh1/xdaforums huggingface dataset:
[Magisk] jandroidian:
I've downloaded Magisk from the Magisk Manager. On a phone that isn't rooted, How do I use Magisk?
[Magisk] DodoGTA:
Install the Magisk ZIP from custom recovery
[Magisk] MusicHeat:
Same here, and it trips SN i think, i even tried with mod uninstaller
[Magisk] darkeyes22:
Unable to install Magisk over systemless SuperSU. Is it a bug or did systemless SuperSU support got dropped?

Log and screenshots are attached below.
[Magisk] ericotena:
Have you found a fix yet?
[Magisk] beardymarrow:
Supersu support was dropped (possibly temporarily). Check the v13 Changelog.
[Magisk] darkeyes22:
I thought it's just for beta release. Guess I'll have to wait for support on SuperSU
[Magisk] jandroidian:
Doesn't installing a custom recovery require root?
[Magisk] beardymarrow:
Afraid not. What's wrong with magisksu? Works perfectly for me.

---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------

No.
[Magisk] dahawthorne:
You're probably thinking of an unlocked bootloader.
[Magisk] MusicHeat:
I think i did : enable core mode and disable the mod, reboot, disable core mode, reboot.
[Magisk] beardymarrow:
That wouldn't require root either :silly:
[Magisk] DodoGTA:
Except grey and black hats, of course
[Magisk] MusicHeat:
SN suddenly fail, worked fine today and yesterday

Log : https://drive.google.com/file/d/0BzLDQt0yJvJ7end1VXAzQU1DTWM/view?usp=drivesdk
[Magisk] jandroidian:
Oooh, interesting!

Thanks!

Now just need to find a custom recovery for my device.
[Magisk] zelendel:
Very true but they are not posting in threads on xda. That stuff is saying Ed for private areas.
[Magisk] ericotena:
Nice thanks for the tip :good:
[Magisk] dahawthorne:
Yes, I just meant that the poster was thinking of root as a requirement when all he needs is the unlocked bootloader. But thanks for the follow-up. :)
[Magisk] beardymarrow:
Yeah, I know. I was trying to be funny. :)
[Magisk] dahawthorne:
Ha... Sorry, I'm old and a bit slow... :D
[Magisk] MPeti1:
I've tried it again, now the module seems to be installed successfully by the manager (5.1.1), but when the system boots and xposed tries to load, it looks like if it has permission problems. Maybe only needed to update the module to use the new Magiskpolicy correctly?

I found these lines speaking about the problem, after these the system always crashes:

08-08 18:52:58.422: I/Zygote(22246): System server process 22534 has been created
08-08 18:52:58.423: W/Zygote(22534): system_server maxThreads=31, vmSize = 2088960
08-08 18:52:58.426: I/Zygote(22246): Accepting command socket connections
08-08 18:52:58.417: W/main(22538): type=1400 audit(0.0:1108): avc: denied { read } for path=2F6465762F6173686D656D2F64616C76696B2D6D61696E207370616365202864656C6574656429 dev="tmpfs" ino=149245 scontext=u:r:system_server:s0 tcontext=u:object_r:init_tmpfs:s0 tclass=file permissive=0
08-08 18:52:58.417: W/main(22538): type=1400 audit(0.0:1109): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.417: W/main(22538): type=1400 audit(0.0:1110): avc: denied { write } for path="socket:[141666]" dev="sockfs" ino=141666 scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.457: W/main(22538): type=1400 audit(0.0:1111): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.471: A/libc(22534): Fatal signal 6 (SIGABRT), code -6 in tid 22538 (main)
08-08 18:52:58.457: W/main(22538): type=1400 audit(0.0:1112): avc: denied { write } for path="socket:[141666]" dev="sockfs" ino=141666 scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.457: W/main(22538): type=1400 audit(0.0:1113): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.457: W/main(22538): type=1400 audit(0.0:1114): avc: denied { write } for path="socket:[141666]" dev="sockfs" ino=141666 scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.457: W/main(22538): type=1400 audit(0.0:1115): avc: denied { getopt } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0
08-08 18:52:58.457: W/main(22538): type=1400 audit(0.0:1116): avc: denied { write } for path="socket:[141666]" dev="sockfs" ino=141666 scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=unix_dgram_socket permissive=0

But here is the full log I used Android Device Monitor to see what's happening, and i set the logcat buffer to 50k lines (i thought this will be enough), so the very beginning is not here. The first file will be the longer log, the spoiler is copied from this, and in the second will be an other log of the boot, but with the beginning. Here you can find the files.

Also this is the module i try to load, i post it because it's not in the Magisk repository.
[Magisk] nozz90:
when installing Magisk 13.0 I get and error like "failed to repack boot image"

any ideas?
[Magisk] Artim_96:
Upload logs?
[Magisk] nozz90:
here they are

I flash my stock boot image then I flash magisk
[Magisk] pkgnex:
/System Changes in August Security Patch?

Not sure where to post this - maybe [MENTION=4544860]osm0sis[/MENTION] can help since he's written the busybox module I'm using ;).

Nexus 6 users (myself included) are reporting a significant increase in available storage space after flashing the August 7.1.1 build (either one) - it was just under 26 GB available and now it's over 29 GB as reported in the settings/storage menu.

I also noticed by chance that I can no longer run fstrim on /system - it still works fine on /data and /cache, but it now throws an error when entering "fstrim /system" in a terminal emulator. This did not happen on July builds and prior, and I am running the exact same set-up otherwise (same Magisk version and all modules).

It appears something changed significantly in the architecture or mounting of the /system directory, but other than the available size an inability to trim /system everything else seems to be working fine (still have root, pass safetynet, etc.).

I'm not inclined to worry much about this, but am curious if the experts in this thread, or others with different devices, have seen anything similar and have any insight on what may have changed in the August builds.
[Magisk] MusicHeat:
Does SN work for you guys? For me it fails suddenly and it used to work fine.
[Magisk] JRJ442:
Passes fine for me.
[Magisk] MusicHeat:
Yes is a problem on my side, i dont have a file named magiskhide(or something like that) in /.core

What can i do to restore it? I didnt delete it.

Edit : flashed the uninstaller, flashed stock boot img, reflashed magisk v13.3 and now SN works again but i dont see any difference in /magisk/.core

Only thing is that i see more logs and something about magisk hide in /sbin
[Magisk] divineBliss:
Found this post interesting where someone installed Magisk v13.3 and was able to root with SuperSU:

https://xdaforums.com/showpost.php?p=73288353&postcount=1822
[Magisk] shrgerrits:
Tried both ways and it won't work :(

I don't understand any of the technical stuff so laugh at me if I'm wrong, but I read that asus phones need to sign their boot images. Could that have something to do with my problem? I mean I needed a code from Huawei to unlock my bootloader with and given that the bootloop error says boot image I thought they maybe could be related. What do you think?

And if this would be the case, how would I go about fixing that?

Already many thanks for trying to help me earlier.
[Magisk] Didgeridoohan:
I'm afraid I'm no help there.

According to the logs that's not a stock boot image. It's already patched by Magisk. Try again with another copy of the boot image (an untouched one).

Trying to figure out how this is related to Magisk... :confused:

Worth a shot I guess... Here:

https://xdaforums.com/android/software-hacking/signing-boot-images-android-verified-t3600606
[Magisk] pkgnex:
Sorry - probably too verbose in my post; only part of it MAY be applicable to Magisk:

Since Magisk "alters the /system partition systemlessly" and the latest security patch seemed to have changed something with how I can access /system when running Magisk, I figured there may be something in the 8-5 security patch that was affecting the functionality of Magisk, or possibly just the busybox module from osm0sis.

Like I said, it's not the end of the world as far as issues go. My post was meant to be more informational for others to look out for issues, and out of curiosity if anyone else was seeing similar affects from the August patch.
[Magisk] MarcelDnB:
Working on s4 w/lineage os and xenonhd too
[Magisk] tech_head:
I'm bold and daring. Everything working fine on the Aug security updates on a Nexus 6P.
[Magisk] azamet90:
hello im using samsung galaxy s8+ 955fd renovate ice 150 rom installed and pekaka kernel installed busybox

too of course how can i fix this problem with my root checker

installed magisk 13.3

[IMG="root checker binary error"]https://image.ibb.co/dG7JHF/Screenshot_20170809_043820.png[/IMG]
[Magisk] lebaud07:
Hi all,

I've just tried to flash the new august-patched system (nexus 6, Android 7.1.1 N6F27I) with flashfire, and it doesn't seem to work anymore with magisk 13.3.

As far as I remember, I flashed the "may" version (N6F27E) without any problem, but I think it was with magisk v12...

Today, when trying to flash, I get the normal black screen but the phone never reboots for flashing, and get stuck here (hard reboot needed).

In my memories, the same problem happened a long time ago with magisk/phh's-superuser when forcing "permissive mode" : flashfire application worked and detected root, but flash stucked during the first black screen.

Thanks in advance !
[Magisk] Didgeridoohan:
If your root checker isn't working, you should probably change it.

If MagiskSU isn't working, you should provide details and logs.

That sounds more like an issue with Flashfire. You should probably go here: https://xdaforums.com/general/paid-software/flashfire-t3075433
[Magisk] Regys:
Hi,

I have a problem for install Magisk.
[Magisk] Didgeridoohan:
Logs, or it didn't happen. Recovery log in your case...
[Magisk] Viggen66:
How to enable init.d on magisk?
[Magisk] Didgeridoohan:
With a kernel/ROM that has init.d support.

Or you could try the Kernel init.d Support Injector by [MENTION=4544860]osm0sis[/MENTION].

Or you could symlink /magisk/.core/post-fs-data.d to /system/etc/init.d. You'd have to change /system to rw though. :crying: But, a workaround is to make a module that mounts a dummy file to /system/etc. That way it won't touch your system... Then you could also put the symlink command in the service.sh file of the module and the symlink will be recreated on each reboot.

Edit: just to clarify... Point 1 & 2 has nothing to do with Magisk.
[Magisk] Viggen66:
Thanks for your reply. Easiest way would be probably be using "Kernel init.d Support Injector", I have already my scripts on init.d folder on etc.

Also as alternative, I can copy my scripts to "/magisk/.core/post-fs-data.d" it says Magisk will run on boot.
[Magisk] ericotena:
Do you also sometimes lose root after reboot?
[Magisk] MPeti1:
Then i'll go back to Magisk 12. Is there a way to bypass RootBeer's root check solution on this version? I need that for a local bank's app (OTP Smartbank).
[Magisk] MusicHeat:
No, I don't.
[Magisk] Didgeridoohan:
Magisk v12 should be able to circumvent all the things Rootbeer checks for. Only thing is that you'll have to change ro.build.tags, ro.build.type and ro.build.selinux to "safe" values yourself. Look in the troubleshooting guide for details.

Only thing v12 can't circumvent is SafetyNet.
[Magisk] nozz90:
okay, so it turns out that my boot image was actually compressed in an img.gz file

all I had to do was extract it in 7zip,

flash that and then magisk installed successfully!

so to anybody trying to flash supersU backup boot images, remember to extract them in 7zip first!
[Magisk] Didgeridoohan:
[MENTION=4840110]Regys[/MENTION]

You already have something installed that has altered the boot image (I'm guessing SuperSU). You should have seen a text during the flash stating: "Boot image patched by other programs" with an instruction following it. Follow that instruction.

You'll find more details in the troubleshooting guide.
[Magisk] Viggen66:
Relating init.d scripts to Magisk terminology "late_start service mode", do the scripts need to have special permission, or it will run regardless of that?
[Magisk] Kurajmo:
Why this app always give me device bootloop When i flash magisk in TWRP?

Today i tried flash newst magisk on Samsung S3 mini nfc version. On Lineageos 13

Bootloop, the same is on Old HTC desire 310 with cm13

I tried flash magisk unistall package. But Twrp in S3 mini give me error.
[Magisk] pkgnex:
Do you really NEED init.d?

The reason I ask is that I have found that simply placing scripts you would otherwise have put in init.d (or su.d) into the late-start services folder Magisk provides for this purpose (/magisk/.core/service.d) works perfectly, without needing apps, injectors, sym-linking, or any modifications to /system.

If your situation allows it, just copy the files you currently have (or would have had) in your init.d folder over to the /magisk/.core/service.d folder and they will automagically be run by Magisk at startup.
[Magisk] jandroidian:
It would appear that installing TWRP via the TWRP App requires root. The app helps you download the right img file but doesn't seem to let you flash it. Instead, you see "Root access required" at the bottom of the screen.

I've rooted a couple of phones in my time. Just recently a GS4 using Odin IIRC. However the xda forum suggestion for my current phone is TWRP.

How do I install TWRP if not via the Official TWRP App? Something to do with something called fastboot? That's related to adb which requires that I either pollute my Windows machine with a JRE or use a Linux live scenario, doesn't it?
[Magisk] Paschfire:
This is not the thread to be asking TWRP related questions, pls refer to your device specific thread to search out how to install Twrp recovery.

Though the answer to your last question is yes, you would need to install the recovery.img via fastboot.
[Magisk] jandroidian:
In my defence, I'm trying to figure out how to get Magisk! It's not my fault the xda app / forums don't allow proper threading and/or quoting but if this post went back to my previous posts, that would be clear.

Anyway, thanks for the fastboot confirmation.
[Magisk] osm0sis:
Bingo. I'd recommend anything BUT using my init.d injector, it's a proof of concept experiment to see if I could make it work without busybox.

su.d or postfsdata.d/service.d are the way to go. I found there's a bug in postfsdata.d that will break things if you try to go subshell to get around the blocking nature of it, but [MENTION=4470081]topjohnwu[/MENTION] is working on it for v13.4.

(Easily replicated with a script containing only { sleep 1; }& )
[Magisk] dratsablive:
SafetyNet quit working for some people almost two weeks ago. Had latest Magisk and Manager installed on Android O Beta OPP4.
[Magisk] pkgnex:
I concur. I tried postfsdata.d first for my custom scripts, but the blocking nature kept subsequent scripts and services from running, often hanging up the boot process.

No such issues with service.d.
[Magisk] Regys:
Yes, I remove SuperSU by putting the original boot, but when restart I have a bootloop.

My phone Mi5 Miui 8.1.2.0 (6.0.1). Why others succeed in installing ?

*Should I use unSU, then reinstall via TWRP the boot.img that is in ROM 8.1.2.0 ?
[Magisk] mr.naicee:
Hello I have a Note 4 with latest Dr ketan rom, I can't pass safetynet check I tried with latest magisk and manager on h vit and ramkernel but it won't pass. Once it worked but I had to format my system and now it won't work please help me out
[Magisk] soder:
Strangest thing just happened to me. This morning I updated my Magisk module for some emoji replacer.

But I didn't reboot the phone until now, and now there's no more then two apps in my Pixel Launcher.

The apps still installed, but not in the "app drawer".

Someone knows about this?

Edit: it was the appsystemizer module that ****ed things up..

/Söder
[Magisk] lebaud07:
As it worked with a previous version of magisk, I wondered if the problem was more magisk-related or flashfire-related.

I'll ask for help in the flashfire thread and keep you in touch.

Thanks.
[Magisk] soder:
Strange, strange.

If I try to uninstall the appsystemizer, and reboots, all the apps are gone..

/Söder
[Magisk] Alex311360:
can't seem to get any form of magisk except magiskSU working after an update. on a sprint galaxy note 5 (n920p) running MOAR nougatized 1.1/android 7.0.

log attached.
[Magisk] azamet90:
what a bull**** answer is this man :D also u mean so or so i do something wrong the magisk can not have an error or rootchecker the root checker is a paid app not nulled and supersu developper is creating this rootchecker also rootchecker can not have any problem if the supersu is working good too right?

im a beginner it is true but i know how to root device also there is one problem and it is magisk i think if u have a solution than tell pls to me if not pls dont doing trash talking pls
[Magisk] Didgeridoohan:
You simply stated there was a problem with your root checker... Nothing else. So I replied to that.

I also said that if you're having problems with MagiskSU you should provide details and logs. I see neither...
[Magisk] azamet90:
why u understand that i have problems with rootchecker? and i did readed all the things about magisk nothing found about that
[Magisk] zelendel:
Providing logs is troubleshooting 101. The very basic of posting about issues. Without them no one can tell you anything.

Remember this is a developers site. So you will have to put in some work on your own. Like pulling logs.
[Magisk] Didgeridoohan:
From your first post:

If you want help you need to provide details about your issue and relevant logs. There are no mind readers here...
[Magisk] CHEF-KOCH:
LG 3 D855 Magisk Tutorial (thanks to Bene)

* Backup current ROM via TWRP

* Reset defaults via TWRP

* Re-install same ROM (e.g. LineageOS)

* Backup your current boot.img (just in case)

* Restore the ROM backup

* Restore Boot.img

* Suuninstaller (Lineage OS one)

* Unofficial unSU

* Magisk

* Clear Dalvik

* Reboot

I hope this helps others with the same device, everything is working perfectly. Thanks for this awesome solution!
[Magisk] azamet90:
if u read my post i did writed renovate rom with version 150 and magisk 13.3 and put the picture of my problem what do u need more?
[Magisk] cascabel:
It's me again. :(

Finally fixed the mount error by switching kernels. Did a clean flash after to be safe. Unfortunately, I'm getting this in the logs now (every time i reboot) :

01-01 08:26:21.117 305 333 I Magisk : * Running module post-fs-data scripts

01-01 08:26:21.117 305 333 I Magisk : xposed: exec [post-fs-data.sh]

01-01 08:26:21.355 305 333 I Magisk : ukm: exec [post-fs-data.sh]

01-01 08:26:21.391 305 423 I Magisk : * Starting MagiskHide

01-01 08:26:21.391 305 423 I Magisk : hide_utils: Hiding sensitive props

01-01 08:26:21.391 305 423 I Magisk : hide_list: [com.google.android.gms.unstable]

01-01 08:26:21.405 305 423 I Magisk : proc_monitor: init ns=mnt:[4026531840]

08-10 10:20:44.249 305 423 I Magisk : proc_monitor: zygote ns=mnt:[4026536055]

--------- beginning of crash

08-10 10:21:34.166 305 423 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7672 ns=mnt:[4026536175])

08-10 10:21:34.181 7686 7686 I Magisk : hide_daemon: Permissive detected, hide the state

08-10 10:21:34.181 7686 7686 I Magisk : hide_utils: Re-linking /sbin

I'm using the doze for play services module. Thanks for any help.

---------- Post added at 03:25 AM ---------- Previous post was at 03:24 AM ----------

I don't have much knowledge on other g3 variants (I'm using the f460 one), but doesn't that activate the secure boot error? I have to flash the cbump zip every time i do anything to boot.img.
[Magisk] arindam4u:
Everything was working fine on my Redmi note 4 latest Miui global beta. Then Magisk keeps auto deleted after a while. I hv to flash the zip from recovery again. Why is this happening? please help.
[Magisk] Didgeridoohan:
In every single reply to you, I've written what is needed. A detailed description of your issue and relevant logs.

Your screenshot seems to indicate that you're having issues rooting your device with Magisk, which is why I brought up the subject of providing status and logs for a MagiskSU issue in the first place.

But, we can't tell what the problem is, because the only thing you've written is that there is a problem with the root checker. So, for all we know, everything else is working fine on your device and you are simply trying to make that single root checker detect Magisk.

Details, details, details! When dealing with other people through the written medium it is so important to be detailed and clear in your intentions and wants. Our communication is so much more than just words and all the little nuances gets lost when we can't hear or see the other person. Probably also the reason why you though my first reply was "trash talking"...

To conclude, until you've done some work yourself (like [MENTION=1140856]zelendel[/MENTION] already pointed out) you're most likely not going to get much help.

Look around the Magisk forum some more. There are guides around that might point you in the right direction and also give tips on what kind of logs you might provide when asking for help.

Are there any issues with Magisk, or are you just worried about the "beginning of crash" line? If everything is working I'd say ignore it...
[Magisk] ante0:
Magisk was working fine until I installed a new update for my Mate 9 (B190 and B193 in this case), after this CTS Profile keeps failing. AND Hide won't work at all when usb debugging is OFF.

To top it off I can't even enable Usb debugging normally.

I had to use 'settings put global adb_enabled 1' and set /data/property/persist.sys.usb.config to include adb, else it would turn usb debugging off as soon as I left the dev options.

Could Huawei have done something to prevent people from using MagiskHide?

This is really just a question. I don't even use apps that need to pass SafetyNet :)
[Magisk] nozz90:
hey I think I can help

this is the same thing that was happening to me

can I just ask, where were you getting a stock boot image ?

was it from the supers backup in the data partition?
[Magisk] cascabel:
[MENTION=4667597]Didgeridoohan[/MENTION] no problems as far as i cant tell. Play services SEEMS to be included in doze (I'm thinking that may be the issue - I'll try the module thread if i find any issues). Will monitor to be sure. Other than that everything's working fine. Thanks.