yashsingh1/xdaforums huggingface dataset:
[Magisk] reference2myself:
I don't have logs, but it did happen many times. But I edited my post earlier to say it only happens when upgrading from 5.6.2 to 5.6.3, uninstalling first and then installing 5.6.3 works just fine.
[Magisk] Snehajit:
Cannot install magisk manager properly

Root checker: Green, ES file explorer can access/edit root files. In settings Magisk Manager is present and I have allowed root access to it.

Magisk v16.0 through TWRP: in TWRP it shows error 1: Boot image not found.

Logs: - Device platform: x86

- Extracting files

- Unpacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

PXA_BOOT_HDR

KERNEL [1464750080]

RAMDISK [1702126437]

SECOND [1679840844]

EXTRA [174351732]

PAGESIZE [1702126437]

NAME [d

]

CMDLINE [b Version: 1.4 ...

]

CHECKSUM [6f756e640a00426f6f74737475623a206d617020534649204d4d415020746f20]

Segmentation fault

- Checking ramdisk status

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

- Stock boot image detected

- Backing up stock boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Compressing to [stock_boot_7fb73434a8b68321bb48de0746c69596fe2ab651.img.gz]

cp: can't stat 'ramdisk.cpio': No such file or directory

- Patching ramdisk

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Add entry [init] (0750)

Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]

Save SHA1: [7fb73434a8b68321bb48de0746c69596fe2ab651] -> [.backup/.sha1]

Record new entry: [init] -> [.backup/.rmlist]

Dump cpio: [ramdisk.cpio]

- Repacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

PXA_BOOT_HDR

KERNEL [1464750080]

RAMDISK [1702126437]

SECOND [1679840844]

EXTRA [174351732]

PAGESIZE [1702126437]

NAME [d

]

CMDLINE [b Version: 1.4 ...

]

CHECKSUM [6f756e640a00426f6f74737475623a206d617020534649204d4d415020746f20]

Segmentation fault

! Unable to repack boot image!

Failed!

! Installation failed

Installed Magisk manager from .apk and tried installing through it:

Logs: - Device platform: x86

- Extracting files

- Unpacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]

! Sony ELF32 format detected

! Please use BootBridge from [MENTION=2233641]AdrianDC[/MENTION] to flash Magisk

Failed!

! Installation failed

Please help me. Thanks in advance.
[Magisk] -Duir-:
I just discovered this same issue on my ZTE Axon 7.

15.3 works fine and 16.x won't pass SafetyNet at all (never tried 15.4). I noticed upon upgrading from 15.3 that Magisk Hide was disabled and if I enabled it the slider would stay in "on" position until I rebooted.

When trying "magiskhide --enable" I would get the message "Logd is not running, cannot run logcat".

I'm not sure why Magisk Hide suddenly needs logd to function as it has worked fine in 15.3 and previous versions but the inclusion of the line you mention does seem to be killing new versions of Magisk for some devices.

Hopefully someone can shed some light onto why this is now a thing. Also, since Magisk now seems to need this and it already patches the boot.img, why doesn't it patch it to enable logd if not already enabled? Seems like a rather obvious thing to do.

-EDIT-

I checked my init.rc and the lines for logd aren't commented out on mine...so not sure what's keeping it from running.

Anything else I can check/do to make it work?
[Magisk] xdataibai:
In axon 7 a2017u, rooted with magisk, twrp installed. In the root request pop-up, I selected forever and grant. It works OK. But after reboot, when I run the app, it still pop-up the root request prompt, then I go to magisk manager, in the superuser screen, the app is not granted. It looks like after reboot, magisk doesn't remember it. How to fix that? It v16 and magisk manager is 5.6.2
[Magisk] Didgeridoohan:
1 - It sounds like you have a ROM with Magisk preinstalled.

2 - There's this in your installation log:

! Sony ELF32 format detected
! Please use BootBridge from @AdrianDC to flash Magisk

Have you tried following the instructions given?

Either way I would check with the developer of your ROM.

Magisk uses logging for MagiskHide, to monitor apps and processes. This is normally done with logd. Before v15.4, if logd was disabled, the Magisk daemon would seriously hog the CPU trying to start up. That's why MagiskHide was disabled if logd isn't running.

It seems like some manufacturers don't do normal though (surprise!), and don't rely on logd, or at least don't have it running (or something like that, this is not my area). This is something [MENTION=4470081]topjohnwu[/MENTION] is going to have to look into when he has an opportunity. Might be a while...

A Magisk log or magisk_debug.log would be good to see...

One thing to test would be a complete uninstall and reinstall of Magisk.
[Magisk] MrElectrifyer:
Awesome! Thanks very much for shearing. That seems to have worked on my Note 8. Never figured out how to use the Java Function code, keep getting "function invalid".
[Magisk] buran666:
I would gladly do so, but I found no direct mails, do you have idea where I should send the boot. img? I also managed to decompile it, will send them the source. Hope they can help in rooting this (reeeally) cheap device :)
[Magisk] Didgeridoohan:
Upload it somewhere, post the link together with an installation log (so everything's gathered in one place).

Then you hope for the best (but don't hold your breath)... :laugh:
[Magisk] buran666:
Well, I had put it here, maybe someone will read, ok, anyways I should stop posting empty answers, or I will get banned 3 posts after I finally registered, so pls. PM me if you have any dev's mail for sending such things.
[Magisk] martyfender:
Upload it and your logs to a file sharing site, then post the link here.
[Magisk] jaka45:
Theres so many module in xposed framework but not in magisk why?
[Magisk] Didgeridoohan:
My apologies. I had not seen your first post. That should be enough... :good:

---------- Post added at 15:32 ---------- Previous post was at 15:30 ----------

He already has...
[Magisk] jcmm11:
You can also do it in Tasker using SecureTask plugin.

Plugin/Secure Task/Secure Settings/write global adb_enabled value 1

Also, under Oreo, if you're getting (from the command line) 'Failure calling service settings: Failed transaction' set selinux to permissive temporarily and it'll work

setenforce 0
settings <whatever options>
setenforce 1
[Magisk] BigMatza:
I'm having the same issue on my A2017U. It appears 15.3 is the latest working version for us. You can page back through last week for the progress on that troubleshooting, or you can see my final conclusion here.
[Magisk] Didgeridoohan:
Did you ever get around to posting those logs?
[Magisk] Shararti1:
Hey guys, i wanna ask if there is any PiP Magisk Module available for Nougat Roms ? and i hope this is the right thread for asking this Question...

Thanks
[Magisk] Snehajit:
I am looking out for the BootBridge way mentioned. Will update here.

My ROM is RR 5.8.5 final for Asus Zenfone 5 T00F/J by tank. I dont think Magisk was preinstalled in this as I did not see any magisk folder. First attempt to clean flash Magisk v16.1 zip file failed with message boot image not found, later I installed magisk manager app separately and shared log got generated.
[Magisk] Jaymin.0.1910:
This is not possible with Magisk
[Magisk] Shararti1:
Then no other way ?

btw thanks for the reply...
[Magisk] Jaymin.0.1910:
Maybe Xposed, but definitely it's not Magisk
[Magisk] GammelBS:
File init.environ.rc looks the same on taimen and mako. Only difference is addition of /system/framework/com.google.vr.platform.jar in BOOTCLASSPATH...
[Magisk] demonoidmaster:
If it's empty then your magisk install is broken, reinstall magisk via twrp

---------- Post added at 07:21 PM ---------- Previous post was at 07:15 PM ----------

Use the twrp app from google play store

Open it and find your device, download the twrp img and flash it

---------- Post added at 07:26 PM ---------- Previous post was at 07:21 PM ----------

Your phone is old buy a new phone that's at least popular

---------- Post added at 07:34 PM ---------- Previous post was at 07:26 PM ----------

*sigh* he meant go into magisk settings and hit the hide magisk button

---------- Post added at 07:35 PM ---------- Previous post was at 07:34 PM ----------

PiP is an Oreo only feature, so no, i wouldn't think it's possible to backport such a thing to previous Android versions
[Magisk] cebs:
Don't know if anyone already asked but any support to Samsung S9 Plus?
[Magisk] IBNobody:
It was already solved. The issue is that v15.4 and on require that logd be enabled, but magisk and magiskhide work fine without it. I'm sitting pat on v15.3 until it gets resolved (or until I choose to build a v16 without the check).
[Magisk] Telperion:
Is there a way to force Magisk to launch in core-only mode through Recovery? I think a module is causing my device to freeze on boot, but I can't get to the module because TWRP is failing to decrypt /data/ on the P DP1 on my device.
[Magisk] YoshiFan501:
Many times. It still gives me the error
[Magisk] a0007:
I have problem

When copy file in system/app , success

After reboot I can't find the file!

Huawei mate 10 pro oreo
[Magisk] Didgeridoohan:
Put a file named ".disable_magisk" (mind the dot, it's necessary) in /cache.

That's an install log, not a Magisk log...

That's because you're mucking with the Magisk mask rather than the actual /system partition. Use the terminal app systemizer instead.
[Magisk] demonoidmaster:
You're doing it wrong
[Magisk] tomo92s:
Device not boot after installing "Magisk uninstaller". I have to root again so that the phone will start up...

My device: Redmi Note 4X (Snapdragon)
[Magisk] Telperion:
That didn't work, still hung up on the splash screen. I was however able to get a root shell while it was hung up, as soon as I 'rm -rf'd Greenify4Magisk the phone booted. From the logcat, it looks like P doesn't like that it's being made privileged. Passing on to the module dev.

03-19 16:05:26.734 1201 1201 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
03-19 16:05:26.734 1201 1201 E AndroidRuntime: java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.oasisfeng.greenify: android.permission.UPDATE_CONFIG, com.oasisfeng.greenify: android.permission.PACKAGE_USAGE_STATS, com.oasisfeng.greenify: android.permission.GET_APP_OPS_STATS, com.oasisfeng.greenify: android.permission.DUMP, com.oasisfeng.greenify: android.permission.WRITE_SECURE_SETTINGS, com.oasisfeng.greenify: android.permission.FORCE_STOP_PACKAGES, com.oasisfeng.greenify: android.permission.INTERACT_ACROSS_USERS, com.oasisfeng.greenify: android.permission.READ_LOGS}
[Magisk] Didgeridoohan:
I'm surprised that didn't work... Because that's exactly what the Manager does when you activate the Core Only Mode, places a .disable_magisk file in /cache.

Glad it worked out though.
[Magisk] YoshiFan501:
My mistake! Here's the magisk log
[Magisk] @ Ayush Garg:
Safetynet is not working after v15.3..

Please fix this... ?
[Magisk] demonoidmaster:
post logs and give device details, cuz safetynet works so
[Magisk] Didgeridoohan:
Now I'm really curious... Saw that you mentioned that it works if you enable Core Only Mode in the Manager. Could you test something? Create the file in TWRP, boot up, verify if Core Only Mode is enabled or not, and then check the permissions for the file. Should be at least 644...

Is that your entire Magisk log? Wow that's broken...

How about providing a magisk_debug.log? That might show more.

Edit: and a full and complete, detailed list of your device's information, modifications, etc.
[Magisk] Jaymin.0.1910:
As a workaround, you can fake the property init.svc.logd with the resetprop tool, just set init.svc.logd to anything but NULL

You are copying files to tmpfs, not the system partition. Disable any Magic Mounts and copy again if you want to modify /system

Otherwise, create a dummy module in /sbin/.core/img with that file to have it Magic Mounted, also see Terminal App Systemizer

The dev missed to declare the apps privileges
[Magisk] Sagar Sharma01:
I didn't get it .Are you saying that i have to upload v15.3 zip somwhere (like drive) and then go to update channel in magisk settings and insert the link by tapping on custom option.

I tried by pasting the v15.3 download link that i copied from OP in custom update channel. But it didn't work saying that Invalid update channel.
[Magisk] Paresh18shah:
Is their any way to backup magisk.img and modules... Because after flashing new rom i always prefers to do clean flash so every time need to flash all modules again...

If any other solution is there please help..

Thank you.

(Sorry for english)?
[Magisk] Jaymin.0.1910:
Copy /data/adb/magisk.img to /data/media, and after flashing

copy /data/media/magisk.img back to /data/adb
[Magisk] innocentus:
samsung tablet t320 user here . had magisk and old variant of netflix working for months with safetynet universal module . i installed xposed with module for spotify .still netflix working . yesterday when i turn on magisk error on both profiles and netflix won`t login anymore ,,need help thanks
[Magisk] Jaymin.0.1910:
You installed Xposed, right ?? There is no chance for SafetyNet then
[Magisk] Didgeridoohan:
No, I mean a json file that points to the file you've uploaded, like the one [MENTION=3306843]kantjer[/MENTION] uses for his snapshots. Here:

https://github.com/kantjer/MagiskFiles/blob/master/updates/kantjer.json
[Magisk] Telperion:
Will give that a try when I get a few minutes today.

That doesn't explain though why the module worked on 8.0/8.1 but not P, since O has the same privileged permission declaration requirement -- at least as far as I could tell from the Android Developer reference.

I created a permissions XML and added it to the module, but it still didn't boot. So either that's not the problem, or Magisk mounted the permissions file later in the boot process than Android System was expecting it.

I'll gladly test anything to pin down what's going on.
[Magisk] Sagar Sharma01:
Am a newbie to github I don't know much about how to use it.

And i created a jason file But i am not able to pull v15.3 zip with it ,MM still says invalid channel what i am doing wrong in my repository jason file, Can you explain

https://github.com/Sharma97sagar/MagiskFiles/blob/master/updates/sagar.json
[Magisk] Jaymin.0.1910:
I don't know, might be that the Oreo ROM was built with privapp privileges in log mode

BTW, I don't have Oreo, so can't test, but I created an XML for you reading Google's documentation

1) Boot with the module disabled

2) Copy the file to /sbin/.core/img/MODID/system/etc/permissions directory, create needed dirs

3) Rename the file to privapp-permissions-greenify.xml

4) Set mode for all dirs in MODDIR to 0755 and all files to 0644

5) Enable the module from MM

6) Reboot and report back the result
[Magisk] innocentus:
yeap uninstalled works fine now . maybe in the future this will be fixed beccause i use a module for spotify . thank you

this is on my tablet on my phone works both magisk for netflix and xposed for spotify strange and magisk still shows me false profile didn`t touch anything ..
[Magisk] Telperion:
Derp, I went back and looked at my XML and I forgot to put the package name in the tree. I updated my zip, re-flashed the module, and the device works.

It appears that O may simply have been logging errors whereas P is now halting boot.
[Magisk] Sagar Sharma01:
https://github.com/Sharma97sagar/MagiskFiles/raw/master/Magisk-v15.3.zip"[/URL] please delete this post i mistakenly submit it
[Magisk] Telperion:
Turns out that the file path is different in TWRP on the Pixels, or at least the Pixel 2. The file goes in /data/cache/instead of /cache, once I put it in the right directory, Core Only worked.
[Magisk] IBNobody:
This did not appear to work. I wrote a magisk boot script to send the following command...

resetprop init.svc.logd running

Here is me verifying that the prop was set and that magiskhide v16 still kills itself.

2|shell@trltespr:/ # resetprop init.svc.logd
running
shell@trltespr:/ # /sbin/magiskhide --enable
Logd is not running, cannot run logcat

EDIT: Here is the bootscript located at magisk/.core/post-fs-data.d/fix_logd.sh (with permissions -rwxr--r-- and tested to be executable)...

#!/bin/bash
resetprop init.svc.logd running

Maybe this doesn't get launched soon enough and the logd variable in the daemon is already set to 0?
[Magisk] djcrash1981:
Magisk Hide not showing apps.

Hi all,

I just recently discovered that magisk Hide is not showing any applications at all.

I'm using magisk version 16 and magisk manager 5.6.3 on a oneplus 3t with oxygen 5.0.1

It was working fine and all of the sudden it's not showing the apps anymore.

I've tried to uninstall and reinstall the manager.
[Magisk] YoshiFan501:
Pixel 2 XL

8.1 OPM1.171019.021

Magisk 16.2

Screenshots show what magisk mods I have installed.

Droid info is my system information
[Magisk] kkuehl:
I have successfully used magiskpolicy, for example:

magiskpolicy --live "allow untrusted_app proc_stat file {read open getattr}"

works correctly.

When I attempt to perform the following, it fails.

The logcat audit avc denied message is like this:

03-20 11:35:22.773: I/handlerThread(28242): type=1400 audit(0.0:563): avc: denied { read } for scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:r:untrusted_app_25:s0:c512,c768 tclass=netlink_kobject_uevent_socket permissive=1

magiskpolicy --live "allow untrustedd_app netlink_kobject_uevent_socket {read}"

Any insight would be appreciated.

Currently, I have the device in permissive mode for troubleshooting purposes.
[Magisk] shark.sh:
Maybe very noob question, but: since in Magisk v16.0 mate 10 pro became officially supported, does that mean I can install Magisk via Magisk manager without unlocked bootloader/twrp/anything else that might invalid warranty?

Inviato dal mio BLA-L09 utilizzando Tapatalk
[Magisk] Ja_som:
Nope
[Magisk] Jaymin.0.1910:
How about faking a logd process ??

Yes, with A / B devices, /cache is just a symlink to /data/cache

Thanks for the info

It is untrusted and not untrustedd, right ??
[Magisk] jam97:
Hello,

Just noticed that Magisk above v15.3 doesn't pass Safetycheck on my Sprint Note 4 (N910P) with latest Android 6.0.1 QI5 build.

Thanks,
[Magisk] ultradj83:
Dears,

just got a dual sim S9+ (SM-G965F/DS).

Magisk v16 correctly completes setup via TWRP, but it's then impossible to boot system, it goes bootloop on Galaxy logo.

Any suggestions?

Tks a lot.
[Magisk] lvbaal:
Yeah, I'd like that, but unfortunately TWRP development is not releasing a version that supports it yet ;.(

In this regard, can you confirm the following maybe:

when I decide to format internal storage in TWRP with ¨Format Data¨and thus getting rid of encryption(link), will it still be (re-)encrypted if I use the unmodified stock kernel (I'm using stock Emui8)? If so, do you know of a modified kernel without encryption?
[Magisk] Didgeridoohan:
S9 not booting with Magisk is a known issue. Wait until [MENTION=4470081]topjohnwu[/MENTION] has time to fix. Don't hold your breath...
[Magisk] ultradj83:
I'm quite confused, I'm not sure it's just a Magisk problem.

Magisk install needs TWRP.

To install TWRP any guides reports to install N965F_Root_for_OEM_issue_devices.zip and no-verity-opt-encrypt-6.0-star.zip, but this causes bootloop, too.

Instead, installing TWRP with only no-verity-opt-encrypt-6.0-star.zip makes TWRP and system work: installing Magisk from this scenario causes bootloop.

Any ideas?

Tks a lot.
[Magisk] Didgeridoohan:
Yes: wait for a fix...
[Magisk] Jaymin.0.1910:
If it was not originally encrypted, then no worries. BUT, be sure to set keepforceencrypt to false and re-flash Magisk
[Magisk] a0007:
Thank you

It's work After deleted module youtube vanced, now I can modify system app and priv-app
[Magisk] lvbaal:
Hi and thanks

So, in light of my current plan to flash stock firmware completely with new build 138 on pro-teammt.ru, the procedure for permanent decrypted /data would be:

1. Uninstall Magisk from Magisk Manager

2. TWRP>Wipe>Format Data

3. TWRP>Wipe (to ¨factory reset¨)

4. Flash stock firmware according to this guide

5 Boot TWRP and from ADB shell on PC send <echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk>

6. TWRP>Install Magisk.zip

Can you confirm these steps? Also, Magisk installation will have patched the kernel to have /data permanently decrypted. Am I correct?
[Magisk] Didgeridoohan:
Nope. Magisk will patch the kernel to remove forced encryption, yes, but you've got the order of things mixed up.

It should be something like this (YMMV):

Install the new firmware.

Run the encryption command in TWRP (you don't need to go it through ADB, the TWRP terminal works fine).

echo "KEEPFORCEENCRYPT=false" >> /cache/.magisk

Flash the Magisk zip.

Format /data.

Reflash the Magisk zip (the boot image will still be patched, but all Magisk files in /data need to be reinstalled).

The key is that you wipe /data

after

patching the boot image (flashing the Magisk zip).
[Magisk] Jaymin.0.1910:
DELETED, I just mixed up some concepts, [MENTION=4667597]Didgeridoohan[/MENTION] is right
[Magisk] kkuehl:
Yes, that was just a typo.

This error might help:

magiskpolicy --live "allow untrusted_app netlink_kobject_uevent_socket * *"

target type netlink_kobject_uevent_socket does not exist
[Magisk] deboopi2:
KBC Sign apk

I'm using magisk in combination with the KBC sign app for the KBC bank in Belgium.

Up to now everything worked perfectly.

The KBC bank has upgraded its app from rel 17.10.1 to 18.2.0. Starting with this version the KBC app sees my phone again as rooted and refuses to work.

For now downgrading to rel 17.10.1 solved the problem but I do not know how long this version will still be supported.

regards, Piet
[Magisk] Didgeridoohan:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] Sagar Sharma01:
[MENTION=4667597]Didgeridoohan[/MENTION] Am a newbie to github I don't know much about how to use it.

And i created a jason file But i am not able to pull v15.3 zip with it ,MM still says invalid channel what i am doing wrong in my repository jason file, Can you explain

https://github.com/Sharma97sagar/MagiskFiles/blob/master/updates/sagar.json
[Magisk] Didgeridoohan:
You're almost there! You've just removed a little to much from the file (versionCode for "magisk"). Try it like this:

{
"app": {
"version": "5.6.3 (180318)",
"versionCode": "180318",
"link": "https://github.com/Sharma97sagar/MagiskFiles/raw/master/MagiskManager-v5.6.3-180318.apk"
},
"magisk": {
"version": "15.3",
"versionCode": "180318",
"link": "https://github.com/Sharma97sagar/MagiskFiles/raw/master/Magisk-v15.3.zip"
}
}

Edit: Also make sure you use the raw address for the file.

https://raw.githubusercontent.com/Sharma97sagar/MagiskFiles/master/updates/sagar.json
[Magisk] lvbaal:
I can imagine :D

---------- Post added at 06:41 PM ---------- Previous post was at 06:24 PM ----------

Okay, I grasp the key point of wiping /data

after

patching the boot image, because only then the kernel is notified of a decrypted data partition. Thanks for the clarification and putting me on the right track.

But, reading this post, I also understand that Magisk installation will not alter fstab

in /vendor/etc (to be specific: removal of flag ",fileencryption=aes-256-xts:aes-256-cts"), Magisk being systemless. So how will the setup then deal with this - in my view -discrepancy (/data being decrypted but the flag still in /vendor/etc/fstab.kirin970?
[Magisk] Didgeridoohan:
Now you've moved beyond my area of knowledge. If your device isn't doing things the normal way, you might need to use a separate zip to disable forced encryption.

If you're up to it, it'd be interesting to know if Magisk will remove forced encryption on your device. If you're going to wipe it anyway, doing a bit of experimenting meanwhile would be useful.