Skip to content

安装/更新模块重启会导致解锁时重启 #2537

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

Open
2 of 3 tasks
kooritea opened this issue Apr 8, 2025 · 10 comments
Open
2 of 3 tasks

安装/更新模块重启会导致解锁时重启 #2537

kooritea opened this issue Apr 8, 2025 · 10 comments

Comments

@kooritea
Copy link

kooritea commented Apr 8, 2025

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

安装模块->点击重启->在锁屏界面等待不会重启->解锁立即黑->循环,只要解锁就重启

解锁后重启前adb logcat日志

04-08 09:25:40.067  1168  1168 I vold    : [sensitive file debug]fscrypt_export_sensitive_file_key start, user_id=0,sensitiveType=0,use_default=0
04-08 09:25:40.067  1168  1168 D vold    : Cannot find key for 0
04-08 09:25:40.067  1168  1168 I vold    : [sensitive file debug]lookup_sensitive_file_key,failed sensitiveType: 0,try to create!
04-08 09:25:40.067  1168  1168 D vold    : fscrypt_unlock_ce_storage 0
04-08 09:25:40.067  1168  1168 D vold    : Trying user CE key /data/misc/vold/user_keys/ce/0/current
04-08 09:25:40.069  1168  1168 D vold    : Successfully retrieved key
04-08 09:25:40.116  1168  1168 D vold    : Installed fscrypt key with ref 9d429fb725173afdc1f97bcdd803548b to /data
04-08 09:25:40.116  1168  1168 D vold    : Installed CE key for user 0
04-08 09:25:40.129  1168  1168 D vold    : fscrypt_prepare_user_storage for volume null, user 0, flags 2
04-08 09:25:40.130  1168  1168 D vold    : Preparing: /data/system_ce/0
04-08 09:25:40.130  1168  1168 I vold    : Verified that /data/system_ce/0 has the encryption policy 9d429fb725173afdc1f97bcdd803548b v2 modes 1/4 flags 0xa
04-08 09:25:40.130  1168  1168 I vold    : oplus_EnsurePolicy end!, user=0,path=/data/system_ce/0
04-08 09:25:40.130  1168  1168 D vold    : Preparing: /data/vendor_ce/0
04-08 09:25:40.131  1168  1168 I vold    : Verified that /data/vendor_ce/0 has the encryption policy 9d429fb725173afdc1f97bcdd803548b v2 modes 1/4 flags 0xa
04-08 09:25:40.131  1168  1168 I vold    : oplus_EnsurePolicy end!, user=0,path=/data/vendor_ce/0
04-08 09:25:40.131  1168  1168 D vold    : Preparing: /data/media/0
04-08 09:25:40.131  1168  1168 I vold    : Verified that /data/media/0 has the encryption policy 9d429fb725173afdc1f97bcdd803548b v2 modes 1/4 flags 0xa
04-08 09:25:40.131  1168  1168 I vold    : oplus_EnsurePolicy end!, user=0,path=/data/media/0
04-08 09:25:40.131  1168  1168 D vold    : Preparing: /data/.recycle
04-08 09:25:40.131  1168  1168 I vold    : Verified that /data/.recycle has the encryption policy 9d429fb725173afdc1f97bcdd803548b v2 modes 1/4 flags 0xa
04-08 09:25:40.131  1168  1168 I vold    : oplus_EnsurePolicy end!, user=0,path=/data/.recycle
04-08 09:25:40.131  1168  1168 D vold    : Preparing: /data/misc_ce/0
04-08 09:25:40.131  1168  1168 I vold    : Verified that /data/misc_ce/0 has the encryption policy 9d429fb725173afdc1f97bcdd803548b v2 modes 1/4 flags 0xa
04-08 09:25:40.131  1168  1168 I vold    : oplus_EnsurePolicy end!, user=0,path=/data/misc_ce/0
04-08 09:25:40.131  1168  1168 D vold    : Preparing: /data/user/0
04-08 09:25:40.131  1168  1168 I vold    : Verified that /data/user/0 has the encryption policy 9d429fb725173afdc1f97bcdd803548b v2 modes 1/4 flags 0xa
04-08 09:25:40.131  1168  1168 I vold    : oplus_EnsurePolicy end!, user=0,path=/data/user/0
04-08 09:25:40.131  1168  1168 D vold    : Starting restorecon of /data/system_ce/0
04-08 09:25:40.141  1168  1168 D vold    : Finished restorecon of /data/system_ce/0
04-08 09:25:40.141  1168  1168 D vold    : Starting restorecon of /data/vendor_ce/0
04-08 09:25:40.150  1168  1168 D vold    : Finished restorecon of /data/vendor_ce/0
04-08 09:25:40.150  1168  1168 D vold    : Starting restorecon of /data/misc_ce/0
04-08 09:25:40.154  1168  1168 D vold    : Finished restorecon of /data/misc_ce/0
04-08 09:25:40.155  1168  1168 D vold    : /system/bin/vold_prepare_subdirs
04-08 09:25:40.155  1168  1168 D vold    :     prepare
04-08 09:25:40.155  1168  1168 D vold    :     
04-08 09:25:40.155  1168  1168 D vold    :     0
04-08 09:25:40.155  1168  1168 D vold    :     2
04-08 09:25:40.226  1168  1176 I vold    : [sensitive file debug]fscrypt_export_sensitive_file_key start, user_id=0,sensitiveType=0,use_default=1
04-08 09:25:40.226  1168  1176 D vold    : Cannot find key for 0
04-08 09:25:40.226  1168  1176 I vold    : [sensitive file debug]lookup_sensitive_file_key,failed sensitiveType: 0,try to create!
04-08 09:25:40.228  1168  1176 I vold    : onUserStarted: 0
04-08 09:25:40.230  1168  1176 I vold    : Mounting emulated fuse volume
04-08 09:25:40.256  1168  1176 I vold    : Bind mounting /data/media to /mnt/pass_through/0/emulated
04-08 09:25:41.156  1168  1176 I vold    : fuse-bpf is enabled because /sys/fs/fuse/features/fuse_bpf reads 'supported'
04-08 09:25:41.156  1168  1176 I vold    : Setting ro.fuse.bpf.is_running to true
04-08 09:25:41.157  1168  1176 I vold    : Configuring read_ahead of /mnt/user/0/emulated fuse filesystem to 256kb
04-08 09:25:41.157  1168  1176 I vold    : Writing 256 to /sys/class/bdi/0:296/read_ahead_kb
04-08 09:25:41.157  1168  1176 I vold    : Configuring max_ratio of /mnt/user/0/emulated fuse filesystem to 40
04-08 09:25:41.157  1168  1176 I vold    : Writing 40 to /sys/class/bdi/0:296/max_ratio
04-08 09:25:41.157  1168  1176 I vold    : mount cost time= 927ms
04-08 09:25:41.157  1168  1176 E vold    : [cherry]not OTG device connect: Invalid argument
04-08 09:25:41.157  1168  1176 I vold    : sd_shutdown =false
04-08 09:25:44.496  1168  1168 D vold    : Aborting fuse connection entry /sys/fs/fuse/connections/296/abort
04-08 09:25:44.496  1168  1168 W vold    : Skip fsync /sys/fs/fuse/connections/296/abort on a file system does not support synchronization: Invalid argument
04-08 09:25:44.509  1168  1168 I vold    : shutdown()++
04-08 09:25:44.509  1168  1168 I vold    : emulated;0 destroy++
04-08 09:25:44.510  1168  1168 E IPCThreadState: Binder transaction failure. id: 124570, BR_*: 29189, error: -22 (Invalid argument)
04-08 09:25:44.510  1168  1168 I vold    : EmulatedVolume:doUnmount start:0
04-08 09:25:44.510  1168  1168 I vold    : Killing all processes referencing /storage/emulated/0
04-08 09:25:44.510  1168  1168 W vold    : KillProcessesWithOpenFiles start, signal=2: Success
04-08 09:25:44.543  1168  1168 W vold    : KillProcessesWithOpenFiles end: Success
04-08 09:25:44.543  1168  1168 I vold    : fuse-bpf is enabled because of property ro.fuse.bpf.is_running
04-08 09:25:44.543  1168  1168 I vold    : Unmounting fuse path /mnt/user/0/emulated
04-08 09:25:44.545  1168  1168 I vold    : Unmounting pass_through_path /mnt/pass_through/0/emulated
04-08 09:25:44.545  1168  1168 I vold    : EmulatedVolume:unmountSdcardFs skip, UserId=0,mUseSdcardFs=0
04-08 09:25:44.545  1168  1168 I vold    : emulated;0 destroy--
04-08 09:25:44.545  1168  1168 I vold    : shutdown()--, rtn: 0

log.txt

在重启时按三下音量-尝试进入安全模式,此时候可以成功解锁进入系统,但是kernelsu并没有进入安全模式,模块也正常更新了,一切正常。

To Reproduce

No response

Expected behavior

No response

Screenshots

No response

Logs

No response

Device info

  • Device: oplus ace5
  • OS Version:oxygenos15.0.0.701
  • KernelSU Version:1.0.3(12018)
  • Kernel Version:6.1.75-android14-11-o-g85dd43e6f808

Additional context

No response

@aviraxp
Copy link
Collaborator

aviraxp commented Apr 8, 2025

04-08 09:18:15.966 8743 8743 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 8743 (apexd), pid 8743 (apexd)

怀疑是对loop设备的处理影响到了apexd。建议在post-fs-data阶段setenforce 0然后抓日志。

@kooritea
Copy link
Author

kooritea commented Apr 8, 2025

我在post-fs-data修补过/apex(但是变更的模块并不包含修补/apex也会触发这个问题),我去掉看看

@kooritea
Copy link
Author

kooritea commented Apr 8, 2025

log.zip
这是Log Catcher抓到的正常和异常的两个日志,不知道有没有需要的信息。
我尝试在post-fs-data.sh里setenforce 0但是似乎没有效果。。开机之后还是显示强制执行

@aviraxp
Copy link
Collaborator

aviraxp commented Apr 8, 2025

所以去掉可以吗

@aviraxp
Copy link
Collaborator

aviraxp commented Apr 8, 2025

没什么用,得先想办法把apexd的tombstone记录下来

@kooritea
Copy link
Author

kooritea commented Apr 8, 2025

所以去掉可以吗

是的,去掉之后确实不会在出现解锁重启了。

@kooritea
Copy link
Author

kooritea commented Apr 8, 2025

好奇怪,我又重新把修改/apex的模块放上去但是又没有触发这个问题,懵逼了,我再看看

@kooritea
Copy link
Author

kooritea commented Apr 8, 2025

tombstone.zip

是这个么,这两个文件的最后修改时间就是这条日志的09:18

我改动过的是/apex/com.android.permission和/apex/com.android.wifi

@aviraxp
Copy link
Collaborator

aviraxp commented Apr 8, 2025

不是这个

@kooritea
Copy link
Author

kooritea commented Apr 17, 2025

tombstone.zip

是这个么,在/data/tombstones目录下面的Process name is /system/bin/apexd, uid is 0, not key_process
分别是关闭/打开shamiko模块时触发这个解锁重启的时间生成的

@kooritea kooritea reopened this Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants