-
Notifications
You must be signed in to change notification settings - Fork 11.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Zygisk / Modules icon grayed out on FireTV 2nd gen Cube (Amlogic S922x) #6042
Comments
Can you capture a log via |
Sure, here you go |
Looks you started grabbing too late... You may need to set log buffer size to max in developer options, and connect your device to PC before it boots. Use |
I did use I don't know if there is another way to get earlier logs? |
That's ok, just send the thing you've got |
Do you want me to redo the logcat from above?
This log starts at Looking at the uart output there is about 15sec of kernel loading before ADB connects. The USB needs to be configured before an ADB connection can be made.
I may be wrong but it looks like logcat is logging in memory before I even make an ADB connection. And |
Yes, please redo it |
Ok, here you go EDIT: btw i did increase the logcat buffer just to make sure I wasn't missing anything but even then the log always starts with:
|
A Magisk module that can help you save the log When the system boot normally and /data/local/logcatcher/boot.lcs is not detected, the logs will be packaged and copied to the Download folder Recent Updates:
|
Thank you, but I'm not sure how i would install a Magisk module to catch logs, because the issue I'm having is that Magisk zygisk and modules features are not working? Also as I mentioned above, it appears that logging starts before I have even started logcat. I can wait until the OS has almost loaded, and logcat will provide me with any logs generated since system startup.
|
If you dont want to follow the instruction from us, I would close this issue. |
|
Ok, I ran the module install
No error, no confirmation of success either. I still do not have a Just in case, I rebooted the device and checked /cache, but there is no EDIT: sorry let me correct that, the magisk --install-module command returns error 127 I'm not sure if modules and applets are the same? |
place the module zip in |
ok I ran
but i'm still getting error 127. I checked EDIT
is the missing magisk in cache a problem? |
Try the following in root shell: OUTFD=1 ZIPFILE='/data/local/tmp/Log.Catcher.zip' ASH_STANDALONE=1 /sbin/.magisk/busybox/busybox sh -c '
. /data/adb/magisk/util_functions.sh
install_module
exit 0' |
Ok, I got an error that busybox is missing
This is what's in
|
So the problem is that your installation missed |
yea this is all that comes up:
Is there anything I can do on my end to try to resolve this? |
|
|
Try to run |
Ok, ran that command without any error and rebooted. After reboot, modules is still grayed out. And busybox is still missing from the path
|
try: OUTFD=1 ZIPFILE='/data/local/tmp/Log.Catcher.zip' ASH_STANDALONE=1 /data/adb/magisk/busybox/busybox sh -c '
. /data/adb/magisk/util_functions.sh
install_module
exit 0' |
That installed, and then I rebooted the device. But I'm not seeing any log in
|
Pull out |
|
Magisk/native/jni/core/bootstages.cpp Lines 189 to 198 in 0b26882
|
app-debug.zip |
Fix topjohnwu#6042 Co-authored-by: vvb2060 <vvb2060@gmail.com>
Thank you @yujincheng08 @canyie @vvb2060 👍 👍 👍 Yes, this appears to have solved the issue. Zygisk is a 'yes' status, and modules are appearing. LogCatcher is generating log files in |
This comment was marked as off-topic.
This comment was marked as off-topic.
Fix #6042 Co-authored-by: vvb2060 <vvb2060@gmail.com>
Device: FireTV 2nd gen Cube
Android version: Android 9 (FireOS 7)
Magisk version name: Canary 9183a0a
Magisk version code: (25101) (D)
Amlogic s922x SOC, slot-A only, SAR, no super partition device
I have tried a few canary builds after v24300, as well as v25000, v25100, and today's canary build. I have flashed the Magisk patched boot.img to the boot paritition in fastboot. Magisk superuser rights work properly, but I can't get Zygisk to work, and the modules icon remains grayed out. I've checked and unchecked Zygisk under settings a couple times.
I'm don't think it's related, but the Cube native boot.img does not have a ramdisk. However like some Xiaomi devices, the Cube does accept and use a ramdisk placed in the boot.img. After patching the boot.img with Magisk, ramdisk switched to a yes status.
Also a patch was added in 24.300+ to ignore illegal androidboot.slot_suffix=normal. I don't know if simply ignoring the suffix rather than classify the device as an '_a' device complicates anything?
#5806
I'm including my boot image, boot-up log, and magisk log.
The text was updated successfully, but these errors were encountered: