KSU bug in granting root for apps on BlissOS #2113

hmtheboy154 · 2024-10-02T23:07:23Z

Please check before submitting an issue

I have searched the issues and haven't found anything relevant
I will upload bugreport file in KernelSU Manager - Settings - Report log
I know how to reproduce the issue which may not be specific to my device

Describe the bug

(This issue may look like #2095, but I can't verify yet)
Currently with latest KSU on BlissOS, tested on kernel 6.1 & 6.6 & 6.9 & 6.11, there are some bugs that I started to notice: While some apps like Aurora Store, Neo Store & FoxLog can be able to grant root and use normally, some are broken in functions or just straight up not working:

Termux can only be able to go to su if using /system/bin/su, and when in su no $PATH is set other than Termux or KSU own path.
MiXplorer can't be able to use Allow Root even set with rootexplorer.root or system template. I tried another app Amaze File Manager with their Root Explorer & Use legacy listing for root and it can do things like show the whole /data but can't access anything in /data/app.
If using another term app like TermOnePlus, it will not working even if using either su or /system/bin/su

All recent BlissOS builds with KernelSU 1.0.1 have this issue. And currently they are on kernel 6.1. I bumped kernel to 6.6 to test locally and it show the same behaviour. For newer kernel that are on stable branch, the same behaviour can be seen on this PR I made . Recently I do try to build for kernel 6.11 and it also have the same behaviour (here is my fork for 6.11).

To Reproduce

For kernel 6.1 + KSU 1.0.1 testing, download any latest stable build of BlissOS
For kernel 6.1 + KSU 0.9.2 testing, download older builds such as 16.9.6, 15.9.1 or 14.10.2
For kernel 6.9 + KSU 0.9.2 testing, download latest BlissOS Zenith (16.9.6)
For kernel 6.6 + KSU 1.0.1 or kernel 6.11 + KSU 1.0.1 tesing, it's currently WIP and still being worked on. If anyone ask, I'll provide.

Expected behavior

Apps can be able to grant root and work as expected

Screenshots

An example of Termux can't use su can be seen here : #1785 (comment)

Logs

will provide soon

Device info

Device: Generic x86_64-v2 devices
OS Version: Android 11/12.1/13/14
KernelSU Version: 1.0.1 (latest main)
Kernel Version: 6.1.x + 6.6.x + 6.11.x

Additional context

One last thing that I tested is to downgrade to 0.9.2 as some people suggested , it only work with kernel 6.1 & 6.6. If you port it to higher kernel like 6.9, it will have the exact same issue.

The text was updated successfully, but these errors were encountered:

hansalemaos · 2024-10-03T00:24:03Z

Same problem here. It seems like something in the shell is "cloaking" the su call
If I pipe something to toybox, I can call su.

Maybe it is releated to:

# interesting detail of KernelSU - it doesn't actually place a su file in
# /system/bin, but hook execve(2) call in kernel to redirect it to kernel
# impl when executing /system/bin/su.

termux-play-store/termux-tools@9187cfa#diff-3de48b02d1685061aec7aeb7ee702149f1d3b8beee98158b5b35e9c94f88d6f7R9

tiann · 2024-10-03T02:12:06Z

exec strace su and observe the output

Xtr126 · 2024-10-03T04:28:53Z

/system/bin/strace su says faccessat(AT_FDCWD, "/system/bin/su", X_OK) = -1 ENOENT (No such file or directory)

strace.txt

tiann · 2024-10-03T05:44:40Z

It seems that this kprobe failed: https://github.com/tiann/KernelSU/blob/main/kernel/sucompat.c#L265
is there any dmesg log?

Xtr126 · 2024-10-03T06:08:23Z

Looks like it has succeeded
dmesg:

[    0.621438] KernelSU: sucompat: execve_kp: 0
[    0.622879] KernelSU: sucompat: newfstatat_kp: 0
[    0.624354] KernelSU: sucompat: faccessat_kp: 0
[    0.626269] KernelSU: sucompat: devpts_kp: 0
[    0.626359] KernelSU: ksud: execve_kp: 0
[    0.628102] KernelSU: ksud: vfs_read_kp: 0
[    0.630275] KernelSU: ksud: input_event_kp: 0
[   19.383064] KernelSU: on_post_fs_data!
[   19.383068] KernelSU: unregister input kprobe: 1!
[   19.383072] KernelSU: devpts sid: 741
[   19.383073] KernelSU: unregister execve kprobe: 1!

dmesg.txt

hmtheboy154 · 2024-10-03T17:25:25Z

[   19.383068] KernelSU: unregister input kprobe: 1!
[   19.383072] KernelSU: devpts sid: 741
[   19.383073] KernelSU: unregister execve kprobe: 1!

this indicate it failed to unregister ?

hmtheboy154 · 2024-10-04T17:20:43Z

@tiann I just remember something: When I test #2041 , I test it in kernel 6.1.84. And it work perfectly fine from granting apps to using modules. After the PR got merged I upstream the kernel and then I have reports about KSU bugging.
So something in the upstream kernel is causing this. Which explain why stable branch affected the same even if using 0.9.2.

I am currently narrowing down to see up until which version does the bug happen, currently it's around 6.1.84 ~ 6.1.89

hmtheboy154 · 2024-10-05T04:32:06Z

6.1.85 is when it happen

Xtr126 · 2024-10-05T13:00:37Z

I just thought, it could be that ksud init broke because modules also don't work, modules.img does not get mounted.

hmtheboy154 · 2024-10-05T14:10:49Z

I just thought, it could be that ksud init broke because modules also don't work, modules.img does not get mounted.

6.1.84 works perfectly fine with 1.0.1, here's an image for you to test
https://drive.google.com/file/d/1Z9Fc0v25gf19n-6ia3JUm8UBQGM_LuIa/view?usp=sharing

Xtr126 · 2024-10-05T15:28:10Z

I just thought, it could be that ksud init broke because modules also don't work, modules.img does not get mounted.

6.1.84 works perfectly fine with 1.0.1, here's an image for you to test https://drive.google.com/file/d/1Z9Fc0v25gf19n-6ia3JUm8UBQGM_LuIa/view?usp=sharing

I have tested 6.1.84 and can confirm everything works there, but I meant in the builds with newer kernel, modules don't work or even get mounted.

hmtheboy154 · 2024-10-05T15:34:34Z

I just thought, it could be that ksud init broke because modules also don't work, modules.img does not get mounted.

6.1.84 works perfectly fine with 1.0.1, here's an image for you to test https://drive.google.com/file/d/1Z9Fc0v25gf19n-6ia3JUm8UBQGM_LuIa/view?usp=sharing

I have tested 6.1.84 and can confirm everything works there, but I meant in the builds with newer kernel, modules don't work or even get mounted.

try to get log, maybe there are more clue than faccessat() is broken

Xtr126 · 2024-10-05T18:25:32Z

I tried even with loglevel=7 and checked in logcat but no clue yet. The dmesg doesn't differ much from that of the working version (6.1.84). But I saw that KernelSU has CONFIG_KSU_DEBUG, it could possibly help in getting more logs.

I just thought, it could be that ksud init broke because modules also don't work, modules.img does not get mounted.

6.1.84 works perfectly fine with 1.0.1, here's an image for you to test https://drive.google.com/file/d/1Z9Fc0v25gf19n-6ia3JUm8UBQGM_LuIa/view?usp=sharing

I have tested 6.1.84 and can confirm everything works there, but I meant in the builds with newer kernel, modules don't work or even get mounted.

try to get log, maybe there are more clue than faccessat() is broken

hmtheboy154 · 2024-10-06T14:07:54Z

@tiann found the commit:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1e3ad78334a69b36e107232e337f9d693dcc9df2

Revert this and it KSU work as expected now. And I even test this on kernel 6.11.2

hmtheboy154 · 2024-10-06T14:08:31Z

so this seems affected all x86 platform not just Android-x86 based like us

tiann · 2024-10-06T14:24:03Z

please check cat /proc/kallsyms and dump the symbols

hmtheboy154 · 2024-10-06T14:27:06Z

please check cat /proc/kallsyms and dump the symbols

when KSU broke or when it's working ?

tiann · 2024-10-06T14:29:27Z

please check cat /proc/kallsyms and dump the symbols

when KSU broke or when it's working ?

broken, and the kernel image

hmtheboy154 · 2024-10-06T14:40:51Z

kallsyms.txt

and the kernel image

kernel.zip

hmtheboy154 · 2024-10-06T17:50:45Z

So as a workaround, I saw this patch in LKML:
https://lore.kernel.org/lkml/20240417164514.66hgypzxgqxt3ssk@desk/T/

I applied it and test on my kernel 6.11 and it's working so far
android-generic/kernel-zenith@0c2e19c

However, I still think that we should fix KSU itself.

hmtheboy154 · 2024-10-07T18:38:47Z

So as a workaround, I saw this patch in LKML: https://lore.kernel.org/lkml/20240417164514.66hgypzxgqxt3ssk@desk/T/

I applied it and test on my kernel 6.11 and it's working so far android-generic/kernel-zenith@0c2e19c

However, I still think that we should fix KSU itself.

Build this on 6.1 requires disabling BHI mitigations by setting spectre_bhi=off though

hmtheboy154 · 2024-10-08T19:37:25Z

@tiann I found this post : https://blog.hakuya.moe/post/13

hmtheboy154 · 2024-10-10T13:35:54Z

So as a workaround, I saw this patch in LKML: https://lore.kernel.org/lkml/20240417164514.66hgypzxgqxt3ssk@desk/T/

I applied it and test on my kernel 6.11 and it's working so far android-generic/kernel-zenith@0c2e19c

However, I still think that we should fix KSU itself.

Finalize the temp fix: android-generic/kernel-zenith@5648396

Because I don't want to fully revert, I put the option under a cmdline syscall_hardening=off . Until there's a new way to hook into x86_64 syscall, I guess this is what I can do.

hansalemaos · 2024-10-10T15:22:40Z

So as a workaround, I saw this patch in LKML: https://lore.kernel.org/lkml/20240417164514.66hgypzxgqxt3ssk@desk/T/
I applied it and test on my kernel 6.11 and it's working so far android-generic/kernel-zenith@0c2e19c
However, I still think that we should fix KSU itself.

Finalize the temp fix: android-generic/kernel-zenith@5648396

Because I don't want to fully revert, I put the option under a cmdline syscal_hardening=off . Until there's a new way to hook into x86_64 syscall, I guess this is what I can do.

Nice, any idea when the updated BlissOs will be online?

hmtheboy154 · 2024-10-13T09:21:02Z

So as a workaround, I saw this patch in LKML: https://lore.kernel.org/lkml/20240417164514.66hgypzxgqxt3ssk@desk/T/
I applied it and test on my kernel 6.11 and it's working so far android-generic/kernel-zenith@0c2e19c
However, I still think that we should fix KSU itself.

Finalize the temp fix: android-generic/kernel-zenith@5648396
Because I don't want to fully revert, I put the option under a cmdline syscal_hardening=off . Until there's a new way to hook into x86_64 syscall, I guess this is what I can do.

Nice, any idea when the updated BlissOs will be online?

updated, please check

hansalemaos · 2024-10-13T12:15:14Z

Thx, I will check that today!!

hansalemaos · 2024-10-13T12:45:40Z

Did not work :( Only with the Toybox trick I used before. I downloaded Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso

hmtheboy154 · 2024-10-13T12:47:16Z

Did not work :( Only with the Toybox trick I used before. I downloaded Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso

have you boot with syscall_hardening=off cmdline yet ?

hansalemaos · 2024-10-13T12:51:15Z

nope, I should have read your old post, let me try

hansalemaos · 2024-10-13T12:53:52Z

WORKING! THX SO MUCH!

ZewZack · 2024-11-03T20:30:34Z

Did not work :( Only with the Toybox trick I used before. I downloaded Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso

have you boot with syscall_hardening=off cmdline yet ?

bro thank you sooo much u save my day <3 (⁀ ͜ʖ⁀)

harryxmin · 2024-11-07T23:36:27Z

I have to put syscall_hardening=off in the grub terminal or termux?

Xtr126 · 2024-11-08T02:27:06Z

I have to put syscall_hardening=off in the grub terminal or termux?

In grub.

harryxmin · 2024-11-10T17:03:26Z

Thank you. It worked. I can grant root now. Is it possible to use a VPN app that is running in bliss OS on a proxmox host to be accessible by other proxmox containers?

AFFAN129 · 2024-11-22T09:40:57Z

Did not work :( Only with the Toybox trick I used before. I downloaded Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso

have you boot with syscall_hardening=off cmdline yet ?

bro how to fix ksu i don't understand even though i've read it,I want to fix in bliss os version 14.10.3

harryxmin · 2024-11-23T03:26:02Z

yeah i got it to work. when the device boots and you see the OS bootloader or recovery page, press "e". You will see the grub menu. Just add the line after "linux" for eg: starting from /android-boot if your grub does not already have it. *Add syscall_hardening=off:* - Add the parameter to the line starting with linux: linux /android-boot quiet androidboot.selinux=permissive syscall_hardening=off

…

On Fri, Nov 22, 2024 at 4:11 PM AFFAN129 ***@***.***> wrote: [image: 2024-10-13 09_42_33-Window] <https://private-user-images.githubusercontent.com/77182807/376035289-85cbff54-0b75-423b-9df6-98e2c46f1c3f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg4MjM5MDcsIm5iZiI6MTcyODgyMzYwNywicGF0aCI6Ii83NzE4MjgwNy8zNzYwMzUyODktODVjYmZmNTQtMGI3NS00MjNiLTlkZjYtOThlMmM0NmYxYzNmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDEzVDEyNDY0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI2OGU4MDc0ZDZlYjUzNDVjYjI4YmUyZWVmY2ExZWM2ZmJjY2ZkMDBmOTIxM2FiMGM1OWQyYWEzMDEwNzk5ZmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ZyxCr_riCQ6-yyd5NLJgY5f1Ideq7a_68s0IzXKVZnY> Did not work :( Only with the Toybox trick I used before. I downloaded Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso have you boot with syscall_hardening=off cmdline yet ? bro how to fix ksu i don't understand even though i've read it — Reply to this email directly, view it on GitHub <#2113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANJX6UDJECLSEE6VIYGR52L2B334DAVCNFSM6AAAAABPIUQDZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGMZTONJUHA> . You are receiving this because you commented.Message ID: ***@***.***>

AFFAN129 · 2024-11-23T03:48:53Z

Ok I'll try Pada Sab, 23 Nov 2024 10.26, harryxmin ***@***.***> menulis:

…

yeah i got it to work. when the device boots and you see the OS bootloader or recovery page, press "e". You will see the grub menu. Just add the line after "linux" for eg: starting from /android-boot if your grub does not already have it. *Add syscall_hardening=off:* - Add the parameter to the line starting with linux: linux /android-boot quiet androidboot.selinux=permissive syscall_hardening=off On Fri, Nov 22, 2024 at 4:11 PM AFFAN129 ***@***.***> wrote: > [image: 2024-10-13 09_42_33-Window] > < https://private-user-images.githubusercontent.com/77182807/376035289-85cbff54-0b75-423b-9df6-98e2c46f1c3f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg4MjM5MDcsIm5iZiI6MTcyODgyMzYwNywicGF0aCI6Ii83NzE4MjgwNy8zNzYwMzUyODktODVjYmZmNTQtMGI3NS00MjNiLTlkZjYtOThlMmM0NmYxYzNmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDEzVDEyNDY0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI2OGU4MDc0ZDZlYjUzNDVjYjI4YmUyZWVmY2ExZWM2ZmJjY2ZkMDBmOTIxM2FiMGM1OWQyYWEzMDEwNzk5ZmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ZyxCr_riCQ6-yyd5NLJgY5f1Ideq7a_68s0IzXKVZnY> > Did not work :( Only with the Toybox trick I used before. I downloaded > Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso > > have you boot with syscall_hardening=off cmdline yet ? > > bro how to fix ksu i don't understand even though i've read it > > — > Reply to this email directly, view it on GitHub > <#2113 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ANJX6UDJECLSEE6VIYGR52L2B334DAVCNFSM6AAAAABPIUQDZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGMZTONJUHA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#2113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYBN2YR2NBGYA27JEQLTOQ32B7YWBAVCNFSM6AAAAABPIUQDZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGI3TAMZXHE> . You are receiving this because you commented.Message ID: ***@***.***>

AFFAN129 · 2024-11-23T04:48:14Z

I have added the cmd but after that I want to boot it happens like this Pada Sab, 23 Nov 2024 10.26, harryxmin ***@***.***> menulis:

…

yeah i got it to work. when the device boots and you see the OS bootloader or recovery page, press "e". You will see the grub menu. Just add the line after "linux" for eg: starting from /android-boot if your grub does not already have it. *Add syscall_hardening=off:* - Add the parameter to the line starting with linux: linux /android-boot quiet androidboot.selinux=permissive syscall_hardening=off On Fri, Nov 22, 2024 at 4:11 PM AFFAN129 ***@***.***> wrote: > [image: 2024-10-13 09_42_33-Window] > < https://private-user-images.githubusercontent.com/77182807/376035289-85cbff54-0b75-423b-9df6-98e2c46f1c3f.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mjg4MjM5MDcsIm5iZiI6MTcyODgyMzYwNywicGF0aCI6Ii83NzE4MjgwNy8zNzYwMzUyODktODVjYmZmNTQtMGI3NS00MjNiLTlkZjYtOThlMmM0NmYxYzNmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEwMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMDEzVDEyNDY0N1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI2OGU4MDc0ZDZlYjUzNDVjYjI4YmUyZWVmY2ExZWM2ZmJjY2ZkMDBmOTIxM2FiMGM1OWQyYWEzMDEwNzk5ZmQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ZyxCr_riCQ6-yyd5NLJgY5f1Ideq7a_68s0IzXKVZnY> > Did not work :( Only with the Toybox trick I used before. I downloaded > Bliss-v16.9.7-x86_64-OFFICIAL-gapps-20241011.iso > > have you boot with syscall_hardening=off cmdline yet ? > > bro how to fix ksu i don't understand even though i've read it > > — > Reply to this email directly, view it on GitHub > <#2113 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ANJX6UDJECLSEE6VIYGR52L2B334DAVCNFSM6AAAAABPIUQDZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGMZTONJUHA> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#2113 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYBN2YR2NBGYA27JEQLTOQ32B7YWBAVCNFSM6AAAAABPIUQDZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGI3TAMZXHE> . You are receiving this because you commented.Message ID: ***@***.***>

AFFAN129 · 2024-11-23T07:47:09Z

So as a workaround, I saw this patch in LKML:
https://lore.kernel.org/lkml/20240417164514.66hgypzxgqxt3ssk@desk/T/

I applied it and test on my kernel 6.11 and it's working so far
android-generic/kernel-zenith@0c2e19c

However, I still think that we should fix KSU itself.

I have tried cmd but it is like this

olekor · 2024-11-30T12:32:18Z

Yesterday, I added syscall_hardening=off and, using Termux su managed to activate Bluetooth. However, Termux displayed a notification stating: "/system/bin/sh: hciconfig: inaccessible or not found." Despite that, Bluetooth started working. Unfortunately, this activation only lasts until I restart Bliss. After each reboot, I need to re-enter the chain of commands for hciconfig. I experimented with several reboots and was satisfied with the results, though not completely. It was an improvement over before. However, today this method is no longer working; when I enter the hciconfig commands, Bluetooth does not start. Any idea?
Currently, BT appears to be operational, but it is not as stable as it should be.

hmtheboy154 mentioned this issue Oct 2, 2024

KSU report "not installed" on installed system, but "installed" on Live boot when using BlissOS #1783

Closed

3 tasks

hmtheboy154 mentioned this issue Oct 7, 2024

🐛 [BUG] - Bliss OS 16 v16.9.7-gapps-20240911 Kernel SU Superuser Root Access is Broken BlissRoms-x86/support#99

Closed

Xtr126 mentioned this issue Dec 1, 2024

🐛 [BUG] - KSU's Module doesn't work . BlissRoms-x86/support#111

Open

KSU bug in granting root for apps on BlissOS #2113

KSU bug in granting root for apps on BlissOS #2113

Comments

hmtheboy154 commented Oct 2, 2024

Please check before submitting an issue

Describe the bug

To Reproduce

Expected behavior

Screenshots

Logs

Device info

Additional context

hansalemaos commented Oct 3, 2024 • edited Loading

tiann commented Oct 3, 2024

Xtr126 commented Oct 3, 2024

tiann commented Oct 3, 2024

Xtr126 commented Oct 3, 2024 • edited Loading

hmtheboy154 commented Oct 3, 2024

hmtheboy154 commented Oct 4, 2024

hmtheboy154 commented Oct 5, 2024

Xtr126 commented Oct 5, 2024

hmtheboy154 commented Oct 5, 2024

Xtr126 commented Oct 5, 2024

hmtheboy154 commented Oct 5, 2024

Xtr126 commented Oct 5, 2024

hmtheboy154 commented Oct 6, 2024

hmtheboy154 commented Oct 6, 2024

tiann commented Oct 6, 2024

hmtheboy154 commented Oct 6, 2024

tiann commented Oct 6, 2024 • edited Loading

hmtheboy154 commented Oct 6, 2024 • edited Loading

hmtheboy154 commented Oct 6, 2024

hmtheboy154 commented Oct 7, 2024

hmtheboy154 commented Oct 8, 2024

hmtheboy154 commented Oct 10, 2024 • edited Loading

hansalemaos commented Oct 10, 2024

hmtheboy154 commented Oct 13, 2024

hansalemaos commented Oct 13, 2024

hansalemaos commented Oct 13, 2024

hmtheboy154 commented Oct 13, 2024 • edited Loading

hansalemaos commented Oct 13, 2024

hansalemaos commented Oct 13, 2024

ZewZack commented Nov 3, 2024

harryxmin commented Nov 7, 2024

Xtr126 commented Nov 8, 2024

harryxmin commented Nov 10, 2024

AFFAN129 commented Nov 22, 2024 • edited Loading

harryxmin commented Nov 23, 2024 via email

AFFAN129 commented Nov 23, 2024 via email

AFFAN129 commented Nov 23, 2024 via email

AFFAN129 commented Nov 23, 2024

olekor commented Nov 30, 2024 • edited Loading

hansalemaos commented Oct 3, 2024 •

edited

Loading

Xtr126 commented Oct 3, 2024 •

edited

Loading

tiann commented Oct 6, 2024 •

edited

Loading

hmtheboy154 commented Oct 6, 2024 •

edited

Loading

hmtheboy154 commented Oct 10, 2024 •

edited

Loading

hmtheboy154 commented Oct 13, 2024 •

edited

Loading

AFFAN129 commented Nov 22, 2024 •

edited

Loading

olekor commented Nov 30, 2024 •

edited

Loading