yashsingh1/xdaforums huggingface dataset:
[Magisk] biribiribiri:
I have a case.... but how would that resort in a boot stuck? I mean, I get out of the boot stuck by long pressing power and forces the phone to restart....

Just so you know, a friend of mine who used pixel as well just told me they ran into the same boot stuck issue. I am starting to wonder whether this is due to incompatibility between elementalX kernel and magisk, since he used that costume kernel as well.
[Magisk] ShevT:
I would like to return to the issue of MagiskManager on Android 5.1.1 (CM12.1)

After installation, the launcher restarts cyclically. The system becomes unstable until soft reboots of the device.

In logcat:

I/DEBUG ( 150): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
I/DEBUG ( 150): Abort message: 'invalid address or address of corrupt block 0x9 passed to dlfree'
I/DEBUG ( 150): r0 00000000 r1 b6e1fdec r2 deadbaad r3 00000000
I/DEBUG ( 150): r4 00000009 r5 b6e210d8 r6 a401e000 r7 00000011
I/DEBUG ( 150): r8 a4bae66c r9 a4bae72c sl b6cf341e fp b6cf3427
I/DEBUG ( 150): ip 00000080 sp a4bae618 lr b6df1373 pc b6df1374 cpsr 600e0030
I/DEBUG ( 150):
I/DEBUG ( 150): backtrace:
I/DEBUG ( 150): #00 pc 00029374 /system/lib/libc.so (dlfree+1239)
I/DEBUG ( 150): #01 pc 0000f3e3 /system/lib/libc.so (free+10)
I/DEBUG ( 150): #02 pc 00012b97 /system/lib/libandroidfw.so (_ZN7android13ResStringPool6uninitEv+38)
I/DEBUG ( 150): #03 pc 000138d3 /system/lib/libandroidfw.so (_ZN7android10ResXMLTree6uninitEv+12)
I/DEBUG ( 150): #04 pc 000138f1 /system/lib/libandroidfw.so (_ZN7android10ResXMLTreeD1Ev+4)
I/DEBUG ( 150): #05 pc 00010597 /system/lib/libandroidfw.so (_ZN7android12AssetManager10getPkgNameEPKc+258)
I/DEBUG ( 150): #06 pc 000105f9 /system/lib/libandroidfw.so (_ZN7android12AssetManager18getBasePackageNameEj+68)
I/DEBUG ( 150): #07 pc 00083f8f /system/lib/libandroid_runtime.so
I/DEBUG ( 150): #08 pc 0028458b /system/framework/arm/boot.oat
I/DEBUG ( 150):
I/DEBUG ( 150): Tombstone written to: /data/tombstones/tombstone_01

As far as I can find out, this problem is related to AAPT2. Some projects have the same problem.

Slide project issue. Solution...

Twidere-Android issue

Issuetracker Google - Android Studio 3 with Gradle plugin 3.0.0.....

I hope that this information will help you solve the problem.
[Magisk] DodoGTA:
Try to use Magisk from here: https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
[Magisk] Bcl2:
I started the log, opened the camera app twice (it showed the expected error) and then I stopped the log. I attach the log (I had to change it to an .xml file because the .txt size limit for upload is too small)
[Magisk] sebx_g1:
Hi, I have moto z play with xperience Oreo rom latest build - I have all latest bulids of Magisk , Magisk Manager , Adaway systemless -- and I can't pass safetynet check while on Magisk I pass out of the box . I attached my logs , other peopele with Moto Z Play had pass 14.3 Magisk safetynet easily . Need some help .

added logs
[Magisk] RaW D Coy:
is it just me or is this update still having problem with root just disappearing and i have to keep reflashing magisk?
[Magisk] zelendel:
I get the same thing.
[Magisk] Didgeridoohan:
This seems to be the one of the holy freakin' grails when it comes to Magisk bugs at the moment. The new invincible mode in v14.3 keeps the daemon alive, but it doesn't seem to be enough.

Logs would be nice...
[Magisk] zelendel:
I'll see if I can grab one. A simple reboot fixes it so I don't worry too much as I reboot every day anyway.
[Magisk] crypticc:
Hi

Been out of rooting a bit - primarily because my banking apps weren't being root friendly.

I had similar boot-loop (straight back to twrp) with google pixel on the October 8.0 stock monthly.

The instructions were generally speaking boot twrp, flash elementalx > magisk > twrp and then verifiedbootsigner. Reboot system goes straight back into twrp instead of system.

Instead, to get this working, after restoring factory boot.img:

1) fastboot boot twrp, flash elementalx (okay) > twrp (okay) > verifiedbootsigner.

2) Reboot system and the phone boots correctly.

3) Then reboot to recovery. twrp flash magisk > verifiedbootsigner.

4) Reboot system. And the phone also boots correctly.

Note, if it helps I found if twrp flashing multiple zips elemental, magisk and verifiedbootsigner gave error "ioexception unknown tag 18 in the twrp logs.".

I'm now booted with elementalx, magisk and twrp and all the usual drm cts safetynet tests etc pass.

Still can't get netflix to work though. error 1001. lol.

update: that 1001 error is nothing to do with magisk, happens in complete stock if using 3g/4g.

Update ii : Sorry to get hopes up the resulting kernel isn't stable and reboots / boot-loop via twrp

Update ii : without elementalx I get boot-loop back into twrp with version 14.3. Are there any debugs or kernel msg that I might pull to help resolve?

Regards

Chris
[Magisk] biribiribiri:
You are rebooting into twrp because you shouldn't flash twrp in oreo i think. I made a similar mistake before. Just flash boot.img to both slots and restart. I think that should get you into the system. After that boot into twrp and flash elementalx and magisk. Don't flash twrp. verifiedsign is no longer needed either. I think this should at least let you boot into the system
[Magisk] crypticc:
thanks - that gets it booting. .....

Update: actually still getting bootloops after first successful boot. Looking at recovery logs it seems that boot partition is maxing out space-wise when the flashable zips patch boot.img.

update ii : patching stock boot.img within the magisk manager app results in patched_boot.img that is flashable and small enough to flash in fastboot without issues.

But then of course flashing elementalx in twrp then overwrites. So we get to choose either magisk via .apk patched boot.img or custom kernel. not both.

When I have time I'll flash elementalx and then dump boot.img and then patch that in magisk manager. I'll wait until the November security update and let you know the resulting filesizes at each step of the way.

Cheers
[Magisk] :
Hey guys,

I have an issue on my Honor 6X (BLL-L22) using AOSP based roms (AOSPA, RR, AOKP). Whenever Magisk v14.3 (1437) is flashed on my phone, lock screen security stops working. When flashed alongside the rom and gapps, you can add a pin in device setup, but once you do so, you are given an error message saying "settings has stopped" and are sent back to the setup screen. If you try proceeding, you are greeted once again with "settings has stopped". If you setup lock screen security (fingerprint + pin), and then flash magisk, the rom black screens everytime your pin is input, and you cannot proceed. When you flash magisk with no lock screen security, you can enter your device, but adding a fingerprint is no longer an option, and every time you add a pin, it says "settings has stopped" and it returns you to the lock screen security setup menu. I have attached a log of this erratic behavior: it's compressed cause the .txt file exceeded the size limit for upload on XDA :silly: .
[Magisk] citytrader:
Hello!, with my Samsung Galaxy A7 2017 (A720F) I'm getting a lag of 5 sec. aprox after pattern unlock, if I uninstall Magisk the lag is gone, this is happens with any version of Supersu too. (seems is a problem with root)

Log here
[Magisk] jenslody:
So using /system/lib64 to detect whether we are on 64- or 32-bit is not working (at least not on my phone).

It might work, if the 32-bit paths get added to ENV, even if 64-bit is detected. That should not harm (hopefully).

I will test later the day, no time now (at work).

The not working root is a more serious issue (for me).
[Magisk] Ubimo:
Latest beta (1e87780) seems to work on Samsung Galaxy S7 edge with SuperMan ROM 2.5.0. I flashed the latest beta upon 170415 with latest TWRP.

Although the magisk error log is verly long and there are repeating events. Is this normal? See attachment.
[Magisk] Deic:
Is the logging of su process, is normal.
[Magisk] Rom:
Last Magisk BETA zip (1e87780) work good on LG G3 D855, Titanium Backup, Greenify and XPosed works :good:
[Magisk] Ubimo:
But, but the log will grow very fast very big at this speed because there are so many repeating entries. You sure about that?

For comparison, this is the log of version 170415, much smaller and clearer.
[Magisk] Deic:
Again the log is normal, but there is a process spamming "su -c pm enable com.google.android.gsf/.update.SystemUpdateService"...
[Magisk] digital0:
Is it possible to install Magisk without recovery? How do I manually inject it to the boot image?
[Magisk] DodoGTA:
Maybe and it's not possible to do that right now
[Magisk] Artim_96:
Not really. If you are already rooted with SuperSU you can use FlashFire, otherwise it's difficult and you would at least need an unlocked bootloader.

And then you would basically need to read the source code on GitHub to find out how the boot image had to be changed and finally you would need to get your boot.img and manually disassemble it, make the changes and finally flash it to your device. But if you can unlock your devices bootloader there should be a way that you don't need to flash a custom recovery but instead just boot it so it would be only temporary and you wouldn't change your devices recovery partition
[Magisk] digital0:
I am not asking how to unlock bootloader, extract bootimage, flash it, etc. I am asking how to patch bootimage if i have it, but i don't have recovery. It is my problem how I will write patched image, I am not asking help about it.
[Magisk] Didgeridoohan:
[MENTION=3072588]digital0[/MENTION] [MENTION=5125527]Artim_96[/MENTION] [MENTION=6429309]DodoGTA[/MENTION]

According to the latest release notes, it is possible to manually inject Magisk with the current v13 beta. We're just waiting for [MENTION=4470081]topjohnwu[/MENTION] to tell us how.
[Magisk] juan.r.l:
For those who can not install magisk 13 by mistake in recovery use flashfire apk with that app I could install beta 13 and it works great That if if they have a previous version of magisk does not need that the desistale is automatically updated
[Magisk] onliner:
?

English please.
[Magisk] Allstargaurav:
Guys I Got This Error While Flashing Magisk v13.0 (v12 Works Just Fine)

See ScreenShot I have attachment Log Pulled Form Tmp Folder

[MENTION=4470081]topjohnwu[/MENTION]

Edit-Forgot To Add Details

Device-Falcon(Moto G)

Rom-Aosp Extended (7.1.2)(June security patch)
[Magisk] Telperion:
- I'm able to flash 1e87780 on my Honor 8 after enabling the Vendor partition in TWRP

- I have root but MagiskHide doesn't pass SafetyNet in this version, it did in 12

- This beta doesn't break the fingerprint sensor when MagiskHide is enabled and the device rebooted

So the first post says don't post that SafetyNet isn't passing without suggestions for what to hide. My conundrum is that I don't know why it's not passing -- 12 passed, 13 doesn't, same device same configuration same day. So before I go and pull logs, is this something that can/should be looked at? My thought is that if 12 works but 13 doesn't, then it's a 'bug' as opposed to if neither 12 nor 13 worked that's more tough luck. Thoughts?

---------- Post added at 12:00 PM ---------- Previous post was at 11:48 AM ----------

If anyone's device fails to flash the zip in TWRP and fails at "Magisk image mount failed", mount your vendor partition in TWRP then try to flash the zip again. That is, if you have a vendor partition.

I had a similar issue with SuperSU, Chainfire had to modify the installation zip to mount /vendor/ before flashing -- it'll be in SR1 or SR2. The issue is that a lot of devices have drivers in /vendor/ and if it's not mounted, the installation will fail.
[Magisk] jenslody:
You might stumble over the same issue, as I did.

I have a /system/lib64 on my J5 and therefore the script thinks we are on 64-bit, and sets the LD_LIBRARY_PATH accordingly.

If you can do that, you can try to change the update-binary in /META-INF/com/google/android/ inside the zip and also common/boot_patch.sh and comment out the 64-bit detection (and setting of ENV) or add the 32-bit paths at the end of the 64-bit LD_LIBRARY_PATH and try it again.

That works for me, but rooting only works on clean boot.img .
[Magisk] Kapiljhajhria:
Go to magisk settings and change mountspace mode. It should fix the safety net. Disable and enable magiskhdie again before checking safetynet. 99% sure that it will fix your issue. If it doesn't then switch back to v12 or give logs for v13.

Nothing much u could do... Also don't enable busybox or systemless host file.
[Magisk] Telperion:
Turning off systemless hosts did the trick. I left namespace on inherit.
[Magisk] Alucard:
I tried to flash viper4android and my device and stuck on bootloop,plus i have no option for inbuilt busybox.
[Magisk] fusk:
With 14.0 and 14.3 i had problems that installed modules didn't do anything. Adblocker doesn't block any ads, youtube background playing doesn't make youtube play in the background.

The modules install and activate fine, but they don't work.

Suggestions ?

Edit:

magisk_debug.log:

Upload of file failed.

Seems there's some problems with the uploader or it's because it's a 0 byte file containing no data.
[Magisk] Paschfire:
Rename magisk_debug.log file extension, change .log to .txt .

This should allow uploading.
[Magisk] fusk:
Considering it's a 0 byte file, does it make any sense to upload it?

Should be noted this is a new copy i just made and i can't upload that either, gives error 413. Too large. This log is 21mb.

https://paste.ubuntu.com/25924104/
[Magisk] Didgeridoohan:
Completely aware of the irony of this post, I'm just gonna drop this link right here. It's a post by [MENTION=1205214]SacredDeviL666[/MENTION], from earlier in the thread, and it's a great read...

https://xdaforums.com/showpost.php?p=74301875&postcount=4355
[Magisk] ilovemeow:
error loading as soon as startup

module issuing after reboot

does it crash coz of xposed installer?

thanks
[Magisk] gorilla p:
Im using the Beelink GT1 TV box running Android 7.1

Flashing Magisk 14.0 vis TWRP works perfectly fine, however v14.3 fails. I believe it is having trouble locating the boot image. Boot image is located at

dev/block/boot.img

Is there a way to instruct the installer to check a specific folder or file or add that the the list of places it checks?
[Magisk] Chrisy8s:
I don't know how to pull logs but I have this. Excuse the newbie, I know now what I do. ?
[Magisk] Aldideos:
Install Magisk manager and manually select the boot partition before press install...

Why do you want to install the beta on gt1?
[Magisk] jakson7474:
error modules

I ask for help because I can not install modules

View attachment magisk_debug.log[/ATTACH]
[Magisk] Didgeridoohan:
E Magisk : mount /dev/block/loop0->/dev/source failed with 13: Permission denied

You don't happen to have a Moto device, by any chance? Known issue with their faulty f2fs implementation. Use a kernel that has it fixed (Elemental usually works is it's available for your device). Or, it's possible that Magisk will work if you change to ext4 instead...
[Magisk] gudenau:
I have a Pixel XL on version 8.0.0 with the October 5, 2017 security patch. I tried to update it like I did before.

I uninstalled magisk in the app

Got my phone to install the update

During step 2 I installed Magisk for OTA

Let it finish

Reboot

This caused a bootloop which was fixed by using fastboot to flash the latest boot image.

Now it says the update failed and when I try to update again it says "Installation Problem".

When I use Magisk to patch the boot image and flaah that, it boot loops.

Magisk Manager 5.4.0(57)

Magisk v14.3
[Magisk] Didgeridoohan:
It seems like a link to [MENTION=1205214]SacredDeviL666's[/MENTION] wonderful post is needed about once a week...

The following should be considered required reading before posting in this thread:

https://xdaforums.com/showpost.php?p=74301875&postcount=4355
[Magisk] SacredDeviL666:
OT/Safety Net/New Magisk Version

Definitely not happy at all to do another post here for the same thing!!!

There are two ways of going about it, i will lock down the thread or else you all just stop with this never ending OT of v15, safety net and thank you posts.

The challenge would be the actual users who is doing a fabulous job by reporting with logs and the excellent support given by [MENTION=4667597]Didgeridoohan[/MENTION] across all magisk threads will be a utter waste.

so let me post once again how/what this thread should be about :good:

Meanwhile you all can decide whether you want this thread to be kept open or not ( no need to reply to this post ) if you are adhering i will understand you want this amazing thread to be on topic, cluster free :highfive:

Now you all can get back to doing whatever you were, me with my best friend Heineken. :eek:

Thanks

XDA Staff.
[Magisk] vuP22:
Hey guys I have problem but I'm not sure if it is a rom or a Magisk bug:

I cannot activate any Magisk module (tried 3 different) in manager is says flashing, then success but after reboot it's not activated

My setup:

Oneplus 3T

Latest cardinal xtended (Oreo) build

Open gapps nano

Magisk v14.0 (stable, not beta)

Only mod: different system font
[Magisk] Maxr1998:
Thanks for the setup information, but could you also upload your Magisk logs, please?

That way, we can help you fix the problem or see if it has to be fixed by the dev.
[Magisk] Maxr1998:
You need to open Magisk, select log, swipe to the Magisk tab, hit the disk icon to save, and upload the file named in the Toast/popup notification.
[Magisk] AndroidDeveloperLB:
Magisk crashes for me when I try to reach the list of rules (pressing "superSU").

Attached bug report file , crash log file, and video to show what I mean.

Some information:

magisk version is 5.4.0 build 57 . inside the app is says it's v14.3 , which is indeed latest according to this forum thread.

Android version is 8.1 DP1 , build OPP5.170921.005

Device is Nexus 5x.

Clearing the app's data fixed this issue. Now I don't have it, till the next time ... :)

I'd like to also suggest some things about it:

1. allow to go directly to the rules list, for both developers and users.

2. set the version name the same as here. Current situation is really confusing: version name is "5.4.0", yet here on the forum and inside the app it's "14.3" .

3. When a rule gets updated/added, and yet you are in the rules list screen, it doesn't get updated. This is a bug.
[Magisk] AndroidDeveloperLB:
I see.

Magisk is the "engine", and "Magisk Manager" app is just the UI for it, right?

However, this is confusing, because both get flashed together, and I don't think it makes sense to have one without the other.

I recommend to have same version for both.

Have you understood the crash bug though? Can you please fix it?
[Magisk] Didgeridoohan:
The Manager and Magisk can be updated individually. Better to keep the versioning separate...

Your superuser crash is most likely caused by a corrupted su database. It should already be fixed for the next release.
[Magisk] SuperSandro2000:
Latest magisk Manager 1.4.2 with clean install:

11-22 19:33:44.703 E/SQLiteLog(23141): (14) os_unix.c:36116: (13) open(/data/user_de/0/com.topjohnwu.magisk/databases/su.db) -

11-22 19:33:44.703 E/SQLiteLog(23141): (1) Process opjohnwu.magisk : Pid (23141) Uid (10170) Euid (10170) Gid (10170) Egid (10170)

11-22 19:33:44.703 E/SQLiteLog(23141): (1) Stat of /data/user_de/0/com.topjohnwu.magisk/databases/su.db : st_mode (100660) st_uid (10059) st_gid (10059) st_ino(3186752)

11-22 19:33:44.703 E/SQLiteLog(23141): (1) Stat of /data/user_de/0/com.topjohnwu.magisk/databases : st_mode(40700) st_uid(10170) st_gid(10170) st_ino(3244128)

11-22 19:33:44.703 E/SQLiteLog(23141): (1) Stat of /data/user_de/0/com.topjohnwu.magisk : st_mode(40700) st_uid(10170) st_gid(10170) st_ino(3227651)

11-22 19:33:44.705 E/SQLiteDatabase(23141): Failed to open database '/data/user_de/0/com.topjohnwu.magisk/databases/su.db'.

11-22 19:33:44.705 E/SQLiteDatabase(23141):	at com.topjohnwu.magisk.database.SuDatabaseHelper.<init>(Unknown Source:15)

11-22 19:33:44.705 E/SQLiteDatabase(23141):	at com.topjohnwu.magisk.database.SuDatabaseHelper.<init>(Unknown Source:4)

11-22 19:33:44.705 E/SQLiteDatabase(23141):	at com.topjohnwu.magisk.MagiskManager.onCreate(Unknown Source:101)

11-22 19:33:44.706 E/AndroidRuntime(23141): Process: com.topjohnwu.magisk, PID: 23141

11-22 19:33:44.706 E/AndroidRuntime(23141): java.lang.RuntimeException: Unable to create application com.topjohnwu.magisk.MagiskManager: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 1806): Could not open database

11-22 19:33:44.706 E/AndroidRuntime(23141):	at com.topjohnwu.magisk.database.SuDatabaseHelper.<init>(Unknown Source:15)

11-22 19:33:44.706 E/AndroidRuntime(23141):	at com.topjohnwu.magisk.database.SuDatabaseHelper.<init>(Unknown Source:4)

11-22 19:33:44.706 E/AndroidRuntime(23141):	at com.topjohnwu.magisk.MagiskManager.onCreate(Unknown Source:101)

11-22 19:33:45.537 E/BufferQueueProducer(3473): [Application Error: com.topjohnwu.magisk#0] disconnect: not connected (req=1)
[Magisk] fonfox:
App FC by Update magisk mananager

Oreo Oneplus2
[Magisk] Ja_som:
I can't boot to system on my Nexus 7 2013 with LOS14.1.

boot image was patched w/o error, but after reboot I see only Google screen, then black for a second and then again Google screen, and so on. So I can't catch the log.

Here is my boot.img if some one can help me with it.
[Magisk] anvitiousky:
i have a blackview bv8000pro chinaphone with mediatek SOC. I have tried magisk 14.0, 14.3 and now 14.5, and i have the issue that it fails to mount /data/magisk.img, in the previous two releases it tried to mount it into /magisk, but it seems with 14.5 it tries to mount it into /sbin/.core/img, where it fails with this:

mount /dev/block/loop0->/sbin/core/.img failed with 13: permission denied

umount /sbin/.core/img failed with 22: invalid argument

mount /dev/block/loop0->/sbin/core/.img failed with 13: permission denied

* running post-fs-data.d scripts......

inspecting the state with adb shell, it looks like in 14.0 and 14.3, the loopback was removed by the time the system was booted, and simply running "mount /data/magisk.img /magisk" didnt work, neither did attempting to setup the loopback with losetup, giving the "failed with 22: invalid argument". I did however then try to set it up with the busybox losetup applet, and then afterwards i could mount it to /magisk. the image file was empty though, only had the lost+found dir.

on 14.5, it left the loopback loop0 setup for magisk.img, and i was able to both mount that loop0 device into /sbin/.core/img with system "mount", and i could also mount /data/magisk.img directly into /sbin/.core/img with system mount.

Dont know why there would be permission denied, I dont have much experience with android at all, there doesnt appear to be anything in the logs that indicate where the permissions might fail. I have attached the magisk log. It was a completely stock firmware freshly flashed when i installed magisk, so there shouldnt be any other interference.

if anyone is interested in debugging this with me and want more direct communication, private message me and i'll provide irc/im/whatever info
[Magisk] DenyDarko:
It'll probably won't fix it.

You need to flash an unpatched boot.img
[Magisk] Link_of_Hyrule:
Just delete the addon.d file and really your rom without Magisk no need to wipe.

I'm having the same bootloop. I'm going to try uninstall and reinstall Magisk but if that doesn't work has anyone found a solution to the issue?
[Magisk] de.er:
I wasn't able to uninstall magisk using the uninstall zip, but I managed to dirty flash my ROM and that took me back to magisk 14.3 I was running before.
[Magisk] Link_of_Hyrule:
Well my plan to fully uninstall and update didn't work guess I'm just referring as well.