yashsingh1/xdaforums huggingface dataset:
[Magisk] jenslody:
The recovery log shows a segfault, when magiskpolicy tries to modify sepolicy.

Because of the segfault sepolicy stays unmodified and magisk-daemon will not be started on boot.

I have the same issue and posted about it.

As workaround, I extracted a modified sepolicy from boot-image created by latest beta and added it to the common-folder in the Magisk zip.

I changed the boot_patch.sh by commenting out the following two lines:

cpio_extract sepolicy sepolicy
./magisk magiskpolicy --load sepolicy --save sepolicy --minimal

So the old (but working) sepolicy gets added to the new boot image.

And everything works fine.

I think it does not make sense to add a modified zip here, because sepolicy is most likely device-specific.

To get the working sepolicy you can either extract it from a backed up working boot image (if you have one) or just flash the last beta that installed for you and get it from your devices root with adb or whatever tool you have.

To gather more information why this happens:

if this happens to more users (look for segfaults in the recovery log)

which cpu do you have (we both have armeabi-v7a),

which Android do you have?

We both seem to have MM, because the new Android M policy compatibility mode is used (maybe that's the cause for the issue).

I know the place where it segfaults;

it's in jni/selinux/libsepol/src/expand.c inside type_set_expand, when the variable type gets it's value from the last allowed member of type_val_to_struct.

type is a pointer to whatever, but gets the value 13 here, which is obviously not in the memory-range allowed for pointer operations. That leads to the segfault.

But the question is, why is this value invalid, and why does this happen on some Rom's, but not on others.
[Magisk] Spikestrip:
I just wanted to let people know that Magisk 13.1 is successfully allowing the brand spanking new Android Pay 4.0 to work on my OnePlus 5 running FreedomOS.
[Magisk] jamy015:
The explanatory text says that MagiskHide will stay enabled, so if the behaviour is intended, the text should be changed.
[Magisk] iLoveMuffinz:
Is Magisk (Latest ver.) compatible with Samsung Galaxy G920T? I’m guessing it is but i’m not sure, but i have been wanting to obtain root for a while but i have not been successful, so I’d also like to know if MagiskSU works on Android N (My version is G920TUES5EQF1).
[Magisk] Lazdaa:
Anyone else having issues installing modules that are not within magisk itself?

I tried installing iYTBP but while installing Magisk crashed and after that no modules shows up under installed (even the ones installed prior).

Now i can't install any modules and none of the ones i had before works.

Is there a fix for this?

---------- Post added at 12:28 AM ---------- Previous post was at 12:23 AM ----------

Anyone else having issues with installing modules from outside of the Magisk Manager?

I just tried to install iYTBP and while installing the manager crashed and after that my previously installed modules as well as iYTBP does not show up as installed.

Now i can't install any and the ones i had prior doesn't work.

Is there a fix for this? The log doesn't show anything out of the ordinary.
[Magisk] yakie996:
I still have no safetynet pass on Xiaomi mi 6 even with universal safetynet fix beta v4, I posted this in the magisk v13 beta thread and did not get any response now the stable version is released still got the same https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post72693322
[Magisk] harsh_hk:
Issue with flashing the zip

My twrp shows that i have successfully flashed the 13.1 zip but after reboot the magisk manager 5.0.4 shows i am not rooted. I can't understand what's the issue here. I also tried flashing using adb sideload command but after reboot it shows i am not rooted. My phone is LeEco Le2. Twrp version 3.1.1-1.
[Magisk] Pkt_Lnt:
Read the red writing under this section

from here.

https://xdaforums.com/showpost.php?p=72979751&postcount=23

I'd highly suggest you read the complete post, save yourself some grief. :good:
[Magisk] SynaTech:
after trying to fix the broken 13.1, I reverted back to 12.0 - now 12.0 doesn't even work, 13.1 f****d up my root and magisk.
[Magisk] Lazdaa:
Thanks but actually it didn't work through Magisk for some reason. However I just reinstalled Magisk and flashed the module in twrp and that working completely fine. So all good now.
[Magisk] PhaseBurn:
Hi, [MENTION=2461994]goodwin_c[/MENTION] and thank you so much for your heroic effort in getting Magisk working with the Pixel and Pixel XL. Alas, I'm getting errors trying to install it on my Pixel XL.

Installing zip file '/sdcard/Magisk/Magisk-v13-Pixel_new10.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /sdcard/Magisk/Magisk-v13-Pixel_new10.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: arm/magisk
inflating: arm/magiskboot
inflating: arm64/magisk
inflating: arm64/magiskboot
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/custom_ramdisk_patch.sh
inflating: common/file_contexts_image
inflating: common/init.magisk.rc
inflating: common/magisk.apk
inflating: x64/magisk
inflating: x64/magiskboot
inflating: x86/magisk
inflating: x86/magiskboot
inflating: arm64/magiskpolicy
************************
* Magisk v13 Installer
************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
cp: can't stat '/dev/tmp/magisk/common/magiskhide/.': No such file or directory
chmod: /magisk/.core/bin: No such file or directory
chown: /magisk/.core/bin: No such file or directory
- Found Boot Image: /dev/block/bootdevice/by-name/boot
- Unpacking boot image
/tmp/updater[336]: /dev/tmp/magisk/arm64/magiskboot: No such file or directory
! Unable to unpack boot image
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
I:Install took 2 second(s).
Error installing zip file '/sdcard/Magisk/Magisk-v13-Pixel_new10.zip'
Updating partition details...
I:Data backup size is 12574MB, free: 3391MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Set page: 'flash_done'
I:operation_end - status=1

Any suggestions? This is on stock on 7.1.2 July Sec patches (also tried on June, just to be safe).
[Magisk] EXV:
Works but only until the next reboot. But disabling MagiskHide completely works fine.
[Magisk] murphyjasonc:
I'm having issues with a few apps force closing unless I'm using core only mode. It was there in all the beta versions also. The log doesn't show much. Mainly the apps I'm having issues with are Google, Gmail and Amazon.
[Magisk] bobonit:
Thanks for responding, I know its been a crazy day.

Magisk.img is in /data

"Magisk patched images detected!" when flashing the zip the second time.

Attached recovery.log in case it helps.
[Magisk] npjohnson:
You don't have a cache partition. You need to use a different path. Becuase we don't have a cache partition, we have to either use an alternative magisk_mount folder or change the path to /data/ in source.
[Magisk] dynospectrum:
Ditto
[Magisk] bobonit:
I'll take a nandroid just in case I fudge it up real good, but I'll give this a try. Thanks.
[Magisk] Robot76:
Success with SafetyNet!!!

Magisk 13.1

Xperia Z3C

Lineage 14.1

5th July security

Thank you...

[emoji7]

LOS A.R.I.S.E. Z3C MAGISK SUBSTRATUM
[Magisk] JpegXguy:
Only on stock for me. On RROS it worked fine. ?
[Magisk] Shtiff1:
Has anyone been able to get ADT pulse app working with v13.1?
[Magisk] aacprime:
Everything worked perfectly when I had magisk 12 installed on my smartphone (wileyfox swift COS13). No problems at all, working root and safetynet passed.

Then magisk prompted to upgrade to 13.1, which I did. After rebooting I lost root access. Magisk manager (which was still of version 4) was showing me that magisk isn't installed. Then I've installed magisk manager 5.0.4 and it just crashed every time I've tried to launch it.

After that I did full wipe via twrp and flashed fresh new firmware (COS13 once again) + magisk 13.1 afterwards. Magisk manager wasn't in apps list, so I had to download it from here and install it by myself. And then it crashed after launching again.

Is there any hope of fixing this (besides installing magisk 12 again)? Is there any possible solution? Or should I report this somewhere else?
[Magisk] Xaviertool:
Hello. I'm having a problem installing Magisk on my old but still good S4 (i9500). I follow all the recommended steps, but the words always appear in red, followed by the message: failure :crying:.

Thank you very much if anyone can help me.

Note: I use a Rom and Kernel customized, as you can see in the image of the settings of my attached device.
[Magisk] jwrezz:
I'm having the same issue on PN latest on a Nexus6. It says I have root via magisksu but that "installed magisk version: (none) and I try to do the install from the magisk manager and it promts to reboot but still nothing. I try to manually install by flashing magisk.zip from twrp and still get the same thing.
[Magisk] JaylanPHNX:
Can anyone see in this log why safety net fails?
[Magisk] secw:
Tried updating to 13.1 within the latest and old manager, status not installed & rooted. Used uninstaller and tried again still no luck. 12.0 is working fine.

Device is redmi note 3/kenzo with Lineage 13
[Magisk] japodude:
Same here. Had version 13.0 working fine. I stalled latest version now saying not I stalled and no root

HTC one max stock 5.0.2
[Magisk] :
I had Magisk 12 installed. Then Magisk manager prompted me to update to 13.1 so I did, but I updated my Magisk Manager first. After reboot, all modules worked, except for Xposed 87.1 SDK22. I tried flashing the Xposed 87.1 zip on TWRP but it can't. It shows error 1. Although this is nothing new. I installed all my modules in Magisk Manager due to this problem even before 13.1 anyway. So I removed Xposed first using Magisk Manager, rebooted, and tried to install it again using Magisk Manager. Installation error. Again, all other modules are still working, and when I was on Magisk 12, there is no error when installing the Xposed zip. I reverted back to Magisk 12 and it worked again.
[Magisk] galaxy s4 nutjob:
I keep getting this error when trying to install the 1.31 update I'm on on 6/12 7.2 with supersu 2.81 and magisk 1.20 installed
[Magisk] ForSquirel:
You should be able to uninstall 13. and reinstall 12. I'd recommend and under 5 version of MagiskManager. Quite a few people have had to revert.
[Magisk] Hyperbomb64:
Tried to update to Magisk 13.1 and now it shows I don't have any Magisk installed. Had to revert to 12.0 to get it working again. Running Droid Turbo on 6.0.1 with systemless xposed installed.
[Magisk] BlackDragonz:
I'm using a Redmi Note 3 with MIUI here. Latest 13.0 beta worked like a charm for me but when I updated to 13..1 , the Manager - I use the latest version of it, v5.0.4 - said that magisk is not installed & no root. Can anyone help me with this? No module installed.

P/s: and i experienced a longer boot issues, approx. 30 sec with 13.1. The boot was like <10 sec with 13.0 beta.
[Magisk] secw:
A few more feedback, the 5.0.4 manager with v12 seems to break some stuff. My nav and volume button freezes up everytime I open the manager, made me stuck inside. Can't go anywhere except notifications and settings, force stop the manager on app manager didn't fix the freezes, had to force reboot to escape this. Also some force closing apps. Revert back to 4.3.3 and everything sail smooth.
[Magisk] BlackDragonz:
Of course man, Magisk v13 is compatible ONLY with Manager >v5. topjohnwu said this in his magisk 13 beta thread.
[Magisk] SynaTech:
where can I grad the sub-v5 of magisk manager?
[Magisk] divineBliss:
Magisk Manager v5.0.4 is working fine with Magisk v12 for me so far. Just updated Magisk Manager today though.

Where can the old official pre-v5.0.4 Magisk Manager be downloaded from now that v5.0.4 is the latest official version?

---------- Post added at 11:55 PM ---------- Previous post was at 11:53 PM ----------

Link in https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] cozarnavarro:
Magisk 13.1 doesn't work on my samsung galaxy j320m (2016)

Everything works fine in the magisk version 12, when I try to update nothing works, I re flash my stock rom then the twrp but when I tried to install magisk 13.1 the twrp give me Error:

:Set page: 'flash_zip'
I:operation_start: 'Flashing'
Instalando archivo zip '/external_sd/Magisk-v13.1.zip'
Buscando archivo MD5...
Saltando verificación de MD5: no se ha encontrado archivo MD5
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Archive: /external_sd/Magisk-v13.1.zip
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: addon.d/99-magisk.sh
inflating: arm/magisk
inflating: arm/magiskboot
inflating: arm64/magisk
inflating: arm64/magiskboot
inflating: chromeos/futility
inflating: chromeos/kernel.keyblock
inflating: chromeos/kernel_data_key.vbprivk
inflating: common/boot_patch.sh
inflating: common/init.magisk.rc
inflating: common/magisk.apk
inflating: common/util_functions.sh
inflating: x64/magisk
inflating: x64/magiskboot
inflating: x86/magisk
inflating: x86/magiskboot
************************
* Magisk v13.1 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
- Creating /data/magisk.img
WARNING: linker: /data/magisk/magisk: unused DT entry: type 0x6ffffffe arg 0x1ad0
WARNING: linker: /data/magisk/magisk: unused DT entry: type 0x6fffffff arg 0x2
- Mounting /data/magisk.img to /magisk
WARNING: linker: /data/magisk/magisk: unused DT entry: type 0x6ffffffe arg 0x1ad0
WARNING: linker: /data/magisk/magisk: unused DT entry: type 0x6fffffff arg 0x2
Cannot mount image!
! Magisk image mount failed...
Proceso Updater terminó con ERROR: 1
I:Legacy property environment disabled.
Error instalando archivo zip \'/external_sd/Magisk-v13.1.zip\'
Actualizando detalles de la partición…
I:Data backup size is 2958MB, free: 513MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
…hecho

When I install first magisk 12 and then update to magisk 13.1 the twrp doesn’t give me error but magisk doesn’t work in the safetynet test, and I tried everything, put magisk in core mode, turn off usb debugging, reset magisk hide and still not working at all, I went back to magisk 12.
[Magisk] secw:
I didn't use v13. Or did you mean manager v5 only works with v13? If you write it right, I tried v13.1 already with both latest manager and old manager.

And the manager issue I added above is magisk v12 with v5 manager.
[Magisk] Didgeridoohan:
Your Linux kernel version is too old. It needs to be at least 3.8 (or the kernel developer need to backport mount namespace support). Not much you can do except try to find a kernel that matches the requirements.

From a quick glance everything actually looks alright. Do you fail both CTS profile matching and basic integrity?

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post72987751#post72987751

Magisk v12 goes with Manager v4.x. Magisk v13+ goes with Manager v5.x. Anything else is unsupported and is just asking for issues...

The old Magisk Manager can now be found bundled in the v12 zip attached to the release thread. Don't mind me... When I checked, I accidentally opened up an old v12 zip where I had bundled the proper apk myself. :silly:

Get the old manager here: https://github.com/topjohnwu/MagiskManager/releases
[Magisk] amageek:
yes, reverted back to v12... and now SafetyNet fails again... have to manage it again
[Magisk] Lord_Kany:
Alright, I updated to 13.1 and I noticed I can't use android pay anymore. When I try to run the safetynet check I get an invalid response and google services crash.

Not sure why it doesn't work anymore, it worked fine before updating. I read that turning hide off, rebooting and turning it on fixes the problem. It fixes the crashes but now I don't pass the safetynet.

S7 Edge with latest LineageOS nightly.

Logs:

i.imgur.com/KQpWrSj.png

i.imgur.com/5P8h7yz.png
[Magisk] Varun.Shanbhag:
Hi,

I Installed this version,

Phone bootlooped,

Booted back twrp,

Browsed to /data/,

/data/magisk/,

But there was no file called magisk_debug.log

In /data/ there was only one magisk related file which was magisk.img

What should I do?
[Magisk] divineBliss:
Go back to Magisk v12 and the associated Magisk Manager if they worked for you previously.
[Magisk] Magpye:
Good job morons! Stuck with a nice recovery loop on Moto E 2015 with cm 13. Restoring boot.img/Magisk-made backup and flashing uninstall as per instructions does nothing.
[Magisk] BlackL0dge:
Why would someone want to help you with that attitude..? :rolleyes:
[Magisk] divineBliss:
The zip just contains the Magisk Manager installer stub apk which directs you to the Play Store which of course does not have the Magisk Manager app any longer :( . [MENTION=4470081]topjohnwu[/MENTION] needs to make the older official Magisk Manager version available for those having to revert to Magisk v12. Should be in the release thread with the other files.

Does the latest uninstaller work for Magisk v12 or does the old uninstaller need to also be made available?
[Magisk] Didgeridoohan:
You are perfectly correct... I downloaded and checked, but accidentally opened up an old v12 zip where I had bundled the Manager apk myself. :silly:

Get the old manager here: https://github.com/topjohnwu/MagiskManager/releases

Edit: I believe the uninstaller should be backwards compatible... But I haven't tried it myself.
[Magisk] Magpye:
I'm sorry, I'm very frustrated with this considering I'm been at this for several hours with no hope in sight.
[Magisk] Didgeridoohan:
Ok then... That's a little better, let's see if we can get this going for you.

Have you tried restoring the boot image from your ROM zip, rather than the Magisk backup? That usually works wonders when something gets messed up while flashing Magisk (personal experience). If that doesn't work, try dirty flashing your ROM.

---------- Post added at 07:58 ---------- Previous post was at 07:52 ----------

Dude... Great find. I did not see that line in the log. If you haven't already, open up a GitHub issue on that one. It really needs to come to the attention of [MENTION=4470081]topjohnwu[/MENTION] (if he doesn't know about it already).
[Magisk] Magpye:
In my original post I said I already tried that. What do you mean by dirty flashing? I have tried re-flashing my ROM in its entirety and instead of a recovery loop it's stuck in a perpetual CM Android boot logo loop.

Thanks for your help.
[Magisk] Didgeridoohan:
Ah, I understood your original post as if you had only used the Magisk backup of the boot image, not the one directly from your ROM zip. Noted... Dirty flashing is just reflashing your ROM without wiping /data, so I guess you've tried that as well. Did you try a complete wipe (clean flash)?

I'm not quite sure as to how flashing Magisk got you to this point... Could you, in as much detail as possible (don't leave anything out), go through what you've done and what you've flashed up until now?
[Magisk] vldesco:
HTC One M8 here, stock Marshmallow Unlocked European model TWRP 3.1.1

V13.1: the installation messages says stock boot found, applied patching and installing new boot image, but after reboot, MagiskManager says Not Installed

V12: During installation (after flash MagiskUninstall and reboot), same messages as V13.1. after reboot, MagiskManager says it is installed, but I can't get root access. Root Checker shows Magisk as SU Binary, but "Not Rooted"

Any advice?
[Magisk] Didgeridoohan:
Right after flashing v13.1, save the recovery log (in TWRP it's under Advanced - Copy log) and post it (as an attachment, not in the post).
[Magisk] Lord_Kany:
Okay so I apparently magiskHide was crashing the webview. I went back to 13.0 and it works flawlessly so I'll stick to that for now.
[Magisk] Magpye:
Trying to avoid wiping my phone in its entirety because I don't have a recent backup because magisk usually doesn't screw up this badly.

Here's what's happened so far:

Magisk app says there's a new version. Try to update and then after reboot Magisk manager says Magisk is not installed at all. It does this 3 different times.

So I attempt to manually update as-per main page instructions via TWRP=recovery loop.

Restoring backup made by Magisk=causes an error after reboot stating the boot loader can't be loaded.

Installing boot.img=Recovery loop

Flash Uninstall Magisk=Says Magisk isn't installed

No change to recovery loop during this.

Re-flashing ROM=Boot loop (Over two hours of this now)
[Magisk] ayamgoreng:
why do I still need no-verity-opt-encrypt after flashing Magisk for samsung tab s2 ? (clean stock M roms, nothing installed except twrp)

if I flashed just Magisk, I'll get bootloop.

I always thought Magisk patch verify and no encrypt by default. Am I wrong ?
[Magisk] Didgeridoohan:
Apart from a full wipe I have nothing else to offer... Pull any important files of your device in TWRP and go for it, I'd say.

Always, always make a TWRP backup before flashing. There's always the risk of something going wrong and instead of spending hours trying to fix whatever has gone wrong and restoring your device you spend 10 minutes doing the backup and another 10 minutes restoring it if things went wrong.

You're not wrong, but we're talking Samsung here. Nothing's normal when Samsung is involved...
[Magisk] xmixmaster:
Superuse via magisk manager crushing the app I have to go to root tab via setting that not happened on previous version maybe its a bug?(it doesn't worrying me cuz its work on that way too I just say)

Also for those who got problems with installation on v13.1 use magisk uninstaller then use an unroot zip then install the v13.1
[Magisk] Didgeridoohan:
The app crashes when entering the Superuser tab? Clear data for the Manager.
[Magisk] D1stRU3T0R:
Change to latest 13 and flash safetynet fix...
[Magisk] DzikrRully:
HELP Please, my phone can't Install a new Magisk 13.1. I tried many times and still stuck on boot logo.

My phone is XiaoMi 4 Prime (unlocked) with MiUI Global Stable 8.2.4.0.
[Magisk] xmixmaster:
How dumb I'm forgotten to try it thanks xddd
[Magisk] moquiwa:
Nothing on the webview crash that the app is causing??

Several people already said here that they are having this problem

Enviado de meu Moto G usando Tapatalk
[Magisk] Matts_:
Hey, installation of 13.1 also fails for me.

I'm on a OnePlus 3T with FreedomOS 2.9 Android 7.1.1.

I also tried flashing through TWRP which says everything went fine but Magisk manager says Magisk isn't installed. Root seems to be working fine.

Thank you! (Sorry for pasting the log, Tapatalk won't let me attach text files.)

--------- beginning of main
I( 454: 454) Magisk v13.1(1310) daemon started
I( 454: 456) ** post-fs mode running
--------- beginning of system
I( 454: 740) ** post-fs-data mode running
I( 454: 740) * Mounting /data/magisk.img
I( 454: 740) * Running post-fs-data.d scripts
I( 454: 900) ** late_start service mode running
I( 454: 900) * Running service.d scripts
E( 454: 4340) sqlite3_exec: no such table: settings
E( 454: 5732) sqlite3_exec: no such table: settings
E( 454: 6063) sqlite3_exec: no such table: settings
E( 454: 7263) sqlite3_exec: no such table: settings
E( 454: 7291) sqlite3_exec: no such table: settings
E( 454: 7350) sqlite3_exec: no such table: settings

posted mobile with oneplus3 freedomos 2.8