Module Deactivating & Showing No Info

[ThePieMonster]

See the attached screenshot.

Magisk 27005

Pixel 6 Pro
Android 13

https://i.postimg.cc/MG9WXftv/Screenshot-20241016-093220.png

[5ec1cff]

please provide boot log ( https://t.me/hwrtools/12 )

[ThePieMonster]

The issue seems to be adding the Pixelify v3.0 by kingsman44 on Magisk 27000 / 27005 / 27008 which causes a boot loop.

I need to fastboot my boot image and then get into safe mode and then just restart the device normally to get back into it.

Not sure how I can get a log dump for you in this case.

If I disable ZygiskNext and enable built in Zygisk in Magisk then I can run any version of Pixelify just fine.

[ThePieMonster]

@5ec1cff are there any logs we can view to see what the issue is? Why is your module not playing nice with Pixelify?

[aviraxp]

Why are you ignoring the method 5ec1cff provided to catch logs?

[5ec1cff]

please provide boot log ( https://t.me/hwrtools/12 )

[ThePieMonster]

Why are you ignoring the method 5ec1cff provided to catch logs?

Why are you ignoring the post I made above yours that shows I am not able too.

The log catcher returns nothing. Its not able to capture any logs. I tried running it many times at different intervals during the boot process (before, during, and after). The log folder is empty. Yes I did make sure that root was granted to shell before I started any of this.

Is there some other method for capturing the log files during boot?

[5ec1cff]

try https://t.me/hwrtools/10

[ThePieMonster]

The below setup keeps the device running (you can see the image below).

After adding the following module and the rebooting the device the device boots to recovery/fastboot screen. https://github.com/Kingsman44/Pixelify

You can not get the device to boot again. Any ideas? There are no log files that gets placed in the downloads folders after the Pixelify module is added since the device will no longer boot.

I need a way to capture the boot process as the device is booting from the PC somehow. @5ec1cff

[5ec1cff]

There are no log files that gets placed in the downloads folders after the Pixelify module is added ...

[ThePieMonster]

I do not have a cahce folder and the /data/local folder has a "access denied" error. @5ec1cff

[5ec1cff]

Please use a root file explorer

[ThePieMonster]

This is the local folder. Nothing of use is in here however. @5ec1cff

local.zip

[5ec1cff]

what about /cache ?

[ThePieMonster]

So I just briefly looked at the bootlogs. And you will notice that the first (10-19) is showing Magisk 27007 which is the boot before adding the in the Pixelify module.

The second bootlog file (10-20) shows Magisk 27000. This is because after the Pixelify module is installed and the device keeps boot looping to recovery, I can not flashboot magisk_patched-27007 as that does not solve the issue. But what does get me back into the device is if I flash magisk_patched-27000. When I get into the device after the fastboot flash, all the Magisk modules are disabled. So that's probably why there is no other "helpful" boot log.

Let me know if you want me to try anything else. @5ec1cff

cache.zip

[ThePieMonster]

Hello @5ec1cff

I tried the new module version (see screenshot) however I am still having the same issue.

The dump does't seem to have anything after hour mark ~23:30. Device was rebooted around ~23:45 which is 5 minutes after the Pixelify module was added.

dump.zip

Screenshot

I used the following for the Pixelify setup
/sdcard/Pixelify/config.prop - config.prop.txt

[5ec1cff]

Please provide /data/tombstones and /data/system/dropbox

[ThePieMonster]

Please provide /data/tombstones and /data/system/dropbox

https://drive.google.com/drive/folders/1RDppBaTG42OYRsrgcQbrePccSPmlRf9i?usp=sharing

[5ec1cff]

Zygisk-Next-1.2.1.1-434-3d817b6-release.zip

try this

[ThePieMonster]

@5ec1cff Same issue. Crashing 1 to 2 seconds after the "Google" logo appears. Does not make it to the spinning part of the logo.

Needed to flash back to 27000 and then after the Google logo appears hold down power and volume down to force safe boot and then normal reboot back into the device. All Magisk modules are disabled at that point.

Debug Files

Modules That I Enabled At The Time Of Crash

[5ec1cff]

mylogcat.zip
Install this module, reproduce the issue and send /cache

[ThePieMonster]

mylogcat.zip Install this module, reproduce the issue and send /cache

I am getting a installation failed error on log line 3 in Magisk.

[5ec1cff]

?

[ThePieMonster]

Error

[5ec1cff]

extract service,sh and module.prop to /data/adb/modules/mylogcat

[5ec1cff]

mylogcat.zip

[ThePieMonster]

I am testing out Magisk 27005 this time instead of 27007/27008 also.

In this instance, the device rebooted a few times and then booted up. Did not boot to fastboot mode. (This is just how 27005 seems to be). So when the device turned on I looked at Magisk and all the modules were disabled so I booted into fastboot (since the device lost its root) and flashed 27005. Then booted the device and copied the cache folder.

To reproduce the issue all I do here is enable the two Pixelify modules

cache.zip

[5ec1cff]

please also enable hwr_logcat

[ThePieMonster]

cache.zip

To reproduce the issue all I do here is enable the two Pixelify modules

[5ec1cff]

These log files are corrupted. Please clear /cache dir, install the latest ZN (1.2.2) and retry

[5ec1cff]

Please also provide /sys/fs/pstore/* when you send logs

[ThePieMonster]

Installed 1.2.2.
cache.zip
pstore.zip

[aviraxp]

@ThePieMonster Can you access adb during device boot and capture logs?

[ThePieMonster]

I ran the following: adb logcat

Logcat stops recording after the first crash. The device reboots about 3 times before it boots up with no root and all modules disabled. @5ec1cff @aviraxp

logcat-before.txt
logcat-after.txt

[5ec1cff]

Zygisk-Next-1.2.2-437-3a6aabe-release.zip
try this

[ThePieMonster]

Hey, that one looks like it did the trick! Everything seems to be working as intended.
What ended up being the fix? @5ec1cff
logcat.txt

[aviraxp]

Great! This will be fixed in ZygiskNext 1.2.3.

[ThePieMonster]

Was this needed because of how the Pixelify module is setup? Just wondering if any other module that used the same setup as Pixelfiy would have also caused the same issue. (I do not know of any modules that are setup in a manor such however). @5ec1cff @aviraxp

This is a temporary module generated by ZN, which is used to complete tasks such as mounting files included in the zygisk module, loading system.prop, and mounting znctl. This module will not copy files to occupy actual storage space, and will be removed when ZN is disabled/uninstalled. Please feel free to use it.

[5ec1cff]

？