Hi,
I lately did an OTA update from 2.0.2 to 2.3.5 - it says "with success" after that I flashed the corresponding patched boot.img with fastboot (to get back my magisk based root access).
After that I noticed that my WiFi is no longer working.
When I switch it on it immediately switches off again - no matter what I do...
When I look at the logs (with CatLog) I get some errors from several processes:
Code:
02-01 11:36:19.245 W/QCNEJ (2307): |CORE| CNE received unexpected action: android.net.wifi.WIFI_STATE_CHANGED
02-01 11:36:20.247 E/[email protected](692): Failed to access driver state control param No such file or directory, 2: No such file or directory
02-01 11:36:20.247 E/[email protected](692): Failed to load WiFi driver
02-01 11:36:20.247 E/[email protected](692): Failed to initialize firmware mode controller
02-01 11:36:20.247 E/[email protected](692): Wifi HAL start failed
02-01 11:36:20.248 E/HalDevMgr(1823): IWifiEventCallback.onFailure: 9 ()
02-01 11:36:20.248 E/HalDevMgr(1823): Cannot start IWifi: 9 ()
02-01 11:36:20.249 E/WifiVendorHal(1823): Failed to start vendor HAL
02-01 11:36:20.249 E/WifiNative(1823): Failed to start vendor HAL
02-01 11:36:20.249 E/WifiNative(1823): Failed to start Hal
02-01 11:36:20.249 E/WifiClientModeManager(1823): Failed to create ClientInterface. Sit in Idle
Any ideas what causes that problems and how I can solve it?
Related
Hi all,
I was trying to root with unrEVOked 3.1 on a 64bit Ubuntu installation and hit this problem and found a solution so I thought I'd post it up here to help any other newbies like me
Problem (running from terminal)
Code:
unrEVOked recovery reflash tool
git 7bb95e5
/usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so
/usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgiogconf.so
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
I assume the problem is that reflash is 32 bit and my libs are 64, so install
frozenfox.freehostia.com/cappy/getlibs-all.deb
then
Code:
getlibs libgioremote-volume-monitor.so
This will install the 32 libs / gvfs and reflash is happy.
not solved for me
Unfortunately, this doesn't solve the problem for me:
Code:
[email protected]:~/Downloads$ sudo ./reflash
unrEVOked recovery reflash tool
git version: 4f78f67
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
This was my first attempt. unrevoked reported "done" in the end, but it didn't work. Now I followed your suggestion:
Code:
[email protected]:~/Downloads$ getlibs libgioremote-volume-monitor.so
libgioremote-volume-monitor.so: gvfs
The following i386 packages will be installed:
gvfs
Continue [Y/n]? y
Downloading ...
Installing libraries ...
[email protected]:~/Downloads$ sudo ./reflash
unrEVOked recovery reflash tool
git version: 4f78f67
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
Same error messages. And again it didn't work although unrevoked reported "done".
This is on Ubuntu 10.04 64bit. Any help appreciated.
Sorry, apparently it DID work. Titanium Backup was reporting a failure with root access, but that was down to a not-working BusyBox. Titanium downloaded an alternative, crashed with force close on restart but after a second restart it worked.
So potentially the first rooting without the 32bit libraries might have worked as well?
need to:
Code:
sudo apt-get install lib32ncurses5 libgtk2.0-0 ia32-libs-gtk
After flashing an M9 with LOS 13, the device does not encrypt and fails to start. I get the following error in logs:
------------------------------------------------------------------------------------------------------------------------------------
E/QSEECOMAPI:: Error::ioctl call to wipe the encryption key for usage 1 failed with ret = -1, errno = 14
[ I/ ]
Keymaster version is not 1.0
[ D/ ]
HW based disk encryption is enabled
[ E/ ]
get_tmp_passwd: Passed argument is NULL
E/QSEECOMAPI:: Error::ioctl call to create encryption key for usage 1 failed with ret = -1, errno = 22
E/Cryptfs: Error enabling encryption after framework is shutdown, no data changed, restarting system
------------------------------------------------------------------------------------------------------------------------------------
If anyone could help with a workaround or had the same issue, it would be very helpful.
Not so sure about that if this question should be posted on magisk's board or here. Anyway, if this is inappropriate, please remind me, thanks everybody.
My Zenfone is a 5z ZS620kl, on 20190723 version's Android P. The Magisk is 19.3 (also tried 19.4 canary, tried manager 7.2.0, 7.3.2, 7.3.3. All of these combination are same results:
1. Can't save any superuser settings. It just gave me totally blank.
2. Magisk Hide is same. Every checkbox I've checked would be unchecked after exit from the manager.
3. Repack to hide manager isn't work. It just cause two manager icon in launcher. (One is the one you'll get after boot.img being flashed, and another is a repacked but useless one, keeps telling that "Magisk is not installed".)
The log seems telling that it can't found su from the first time boot. But I've tried reinstalling or reflashing boot.img, but won't work. Trying to fix permission or just simply edit the data/adb/magisk.db are nothing but useless.
Is Magisk have some compatibility problems with P or something else? Should I downgrade back to Oreo or try the Q beta or try roms on xda? I really need to fix this situation 'cause many apps like Line pay or something likewise are broken because of they detected Magisk.
Thanks for reading and responding, hope that there would be solutions soon.
There is the log:
--------- beginning of system
--------- beginning of main
08-20 12:43:44.872 644 2092 I Magisk : ** boot_complete triggered
08-20 12:43:44.874 644 2092 E Magisk : su: cannot find manager
08-20 12:43:44.915 2109 2109 I Magisk : apk_install: /data/magisk.apk
08-20 12:43:45.510 2264 2264 I Magisk : apk_install: Success
08-20 12:43:53.162 644 2397 I Magisk : ** post-fs-data mode running
08-20 12:43:53.168 644 2397 I Magisk : * Initializing Magisk environment
08-20 12:43:53.173 644 2397 I Magisk : * Mounting mirrors
08-20 12:43:53.174 644 2397 I Magisk : mount: /sbin/.magisk/mirror/system_root
08-20 12:43:53.174 644 2397 I Magisk : link: /sbin/.magisk/mirror/system
08-20 12:43:53.200 644 2397 I Magisk : mount: /sbin/.magisk/mirror/vendor
08-20 12:43:53.202 644 2397 I Magisk : mount: /sbin/.magisk/mirror/data
08-20 12:43:53.204 644 2397 I Magisk : * Setting up internal busybox
08-20 12:43:53.227 644 2397 I Magisk : * Running post-fs-data.d scripts
08-20 12:43:53.232 644 2404 E Magisk : sqlite3_exec: attempt to write a readonly database
08-20 12:43:53.232 644 2404 I Magisk : * Starting MagiskHide
08-20 12:43:53.232 644 2404 I Magisk : hide_policy: Hiding sensitive props
08-20 12:43:53.232 644 2404 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
08-20 12:43:53.252 644 2404 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
08-20 13:01:20.088 644 2518 I Magisk : ** late_start service mode running
08-20 13:01:20.088 644 2518 I Magisk : * Running service.d scripts
08-21 02:16:05.816 644 4206 I Magisk : ** boot_complete triggered
08-21 02:16:30.961 644 2404 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[7199] UID=[10007]
08-21 02:16:43.143 644 7675 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:16:51.173 644 8560 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:16:51.268 644 8564 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:16:51.359 644 8568 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:16:51.452 644 8570 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:18:04.336 644 9394 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:18:04.581 644 9431 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:19:00.306 644 10031 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:19:00.558 644 10049 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:19:31.415 644 10165 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:19:31.428 10166 10166 W Magisk : su: request rejected (10138->0)
08-21 02:19:31.776 644 10180 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:10.016 644 10335 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:10.287 644 10370 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.676 644 10437 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.718 644 10439 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.761 644 10441 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.795 644 10443 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.839 644 10445 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.883 644 10447 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.928 644 10449 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:22.971 644 10451 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:23.035 644 10454 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.445 644 10487 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.492 644 10489 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.551 644 10491 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.607 644 10493 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.648 644 10495 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.694 644 10497 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.755 644 10499 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.817 644 10501 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:31.866 644 10503 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:42.653 644 10795 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:43.082 644 10799 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:43.464 644 10802 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:43.746 644 10805 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:44.603 644 10813 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:45.084 644 10817 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:45.757 644 10820 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:46.163 644 10823 E Magisk : sqlite3_exec: attempt to write a readonly database
08-21 02:20:46.579 644 10826 E Magisk : sqlite3_exec: attempt to write a readonly database
Click to expand...
Click to collapse
I experience the same problem and resolved by removing the boot PIN code when startup, then reboot the phone. After that, magisk will be able to use MagiskHide and repackage with hide magisk manager.
efraim14 said:
I experience the same problem and resolved by removing the boot PIN code when startup, then reboot the phone. After that, magisk will be able to use MagiskHide and repackage with hide magisk manager.
Click to expand...
Click to collapse
thanks man! i've facing this problem quite a while. and after removing the boot PIN when startup, magisk work properly.
I just updated to the latest Nightley of LinageOS for the Fairphone 4.
In order to get root access, I did the usual Magisk flow of patching the boot.img
However, after patching, even though I got root access, my wifi and audio (meaning no phone, no ringing...) was gone
Looking at the logcat I saw a huge amount of these logs:
00:15:09.595 sscrpcd I vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:159: rpcmem_init_internal: opened ION device fd 4, configured heap IDs: system (0x2000000), contig (0x400000), secure (0x200), secure flags (0x80080000)
00:15:09.595 sscrpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2961: fastrpc_apps_user_init done with default domain:0 and &fastrpc_trace:0x7b161faf20
00:15:09.596 sscrpcd E vendor/qcom/proprietary/sensors-see/sscrpcd/src/sscrpcd.cpp:82:adsp_default_listener_start called for [sensorspd]
00:15:09.596 sscrpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_pm.c:85: fastrpc_wake_lock_init done for sscrpcd:653
00:15:09.596 sscrpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1663: wakelock_control: enabled wakelock control for domain 0
00:15:09.596 sscrpcd E vendor/qcom/proprietary/sensors-see/sscrpcd/src/sscrpcd.cpp:60:fastrpc wakelock control is enabled
00:15:09.596 sscrpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1305: remote_handle_open: Successfully opened handle 0x0 for '":;./\createstaticpd:sensorspd on domain 0
00:15:09.596 sscrpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2752: Error 0x200: apps_dev_init failed for domain 0, errno Transport endpoint is not connected
00:15:09.596 sscrpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2850: Error 0x200: open_dev (-1) failed for domain 0 (errno Transport endpoint is not connected)
00:15:09.596 sscrpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1308: Error 0x200: remote_handle_open failed for adsp_default_listener (errno Success)
00:15:09.596 sscrpcd E vendor/qcom/proprietary/sensors-see/sscrpcd/src/sscrpcd.cpp:86:listener exits
00:15:09.596 sscrpcd I vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:192: rpcmem_deinit_internal: closed ION fd 4
00:15:09.596 sscrpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_pm.c:116: fastrpc_wake_lock_deinit done
00:15:09.596 sscrpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2897: fastrpc_apps_user_deinit done
00:15:09.598 sscrpcd E vendor/qcom/proprietary/sensors-see/sscrpcd/src/sscrpcd.cpp:97:sscrpcd daemon will restart after 25ms...
00:15:09.624 adsprpcd I vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:159: rpcmem_init_internal: opened ION device fd 4, configured heap IDs: system (0x2000000), contig (0x400000), secure (0x200), secure flags (0x80080000)
00:15:09.624 adsprpcd I vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:159: rpcmem_init_internal: opened ION device fd 4, configured heap IDs: system (0x2000000), contig (0x400000), secure (0x200), secure flags (0x80080000)
00:15:09.624 adsprpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2961: fastrpc_apps_user_init done with default domain:0 and &fastrpc_trace:0x77b42b9f20
00:15:09.624 adsprpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2961: fastrpc_apps_user_init done with default domain:0 and &fastrpc_trace:0x7ab5352f20
00:15:09.625 adsprpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1305: remote_handle_open: Successfully opened handle 0x0 for '":;./\attachguestos on domain 0
00:15:09.625 adsprpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1305: remote_handle_open: Successfully opened handle 0x0 for '":;./\createstaticpd:audiopd on domain 0
00:15:09.625 adsprpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2752: Error 0x200: apps_dev_init failed for domain 0, errno Transport endpoint is not connected
00:15:09.625 adsprpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2850: Error 0x200: open_dev (-1) failed for domain 0 (errno Transport endpoint is not connected)
00:15:09.625 adsprpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1308: Error 0x200: remote_handle_open failed for adsp_default_listener (errno Success)
00:15:09.625 adsprpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2752: Error 0x72: apps_dev_init failed for domain 0, errno Transport endpoint is not connected
00:15:09.625 adsprpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2850: Error 0x72: open_dev (-1) failed for domain 0 (errno Transport endpoint is not connected)
00:15:09.625 adsprpcd I vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:192: rpcmem_deinit_internal: closed ION fd 4
00:15:09.625 adsprpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2897: fastrpc_apps_user_deinit done
00:15:09.625 adsprpcd E vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1308: Error 0x72: remote_handle_open failed for adsp_default_listener (errno Success)
00:15:09.626 adsprpcd I vendor/qcom/proprietary/adsprpc/src/rpcmem_android.c:192: rpcmem_deinit_internal: closed ION fd 4
00:15:09.626 adsprpcd I vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2897: fastrpc_apps_user_deinit done
00:15:09.628 adsprpcd E vendor/qcom/proprietary/adsprpc/src/adsprpcd.c:47:adsp daemon will restart after 25ms...
00:15:09.629 adsprpcd E vendor/qcom/proprietary/adsprpc/src/adsprpcd.c:45:fastRPC device driver is disabled, retrying...
00:15:09.629 adsprpcd E vendor/qcom/proprietary/adsprpc/src/adsprpcd.c:47:adsp daemon will restart after 25ms...
Click to expand...
Click to collapse
Not sure what went wrong but perhaps anyone else noticed this bug.
TobiasR. said:
I just updated to the latest Nightley of LinageOS for the Fairphone 4.
In order to get root access, I did the usual Magisk flow of patching the boot.img
However, after patching, even though I got root access, my wifi and audio (meaning no phone, no ringing...) was gone
Looking at the logcat I saw a huge amount of these logs:
Not sure what went wrong but perhaps anyone else noticed this bug.
Click to expand...
Click to collapse
Did you flashed boot.img? If yes, this is your problem. Our device can only handle to boot the boot.img
Sony make.believe said:
Did you flashed boot.img? If yes, this is your problem. Our device can only handle to boot the boot.img
Click to expand...
Click to collapse
Hi. Could you explain what this means and what must be done instead? Or how can it be reverted?
I might be having the same issue. I had a clean install of the "lineage-20.0-20230521-nightly-FP4-signed" build but only USB-C audio wasn't working. Everything else was fine.
Now I updated to "lineage-20.0-20230611-nightly-FP4-signed" via OTA and lost full audio and wifi.
---
Fixed the OTA update blunder:
- Fully uninstalled Magisk
- Exported the OTA update and moved it to the SD card
- Rebooted into Recovery and reinstalled the OTA update
- Sideloaded Gapps over adb
- Rebooted
All seems back to normal except the issue that I had before the update: USB-C wasn't doing any sound either via a USB-C to 3.5mm adapter or a USB-C to HDMI adapter even before having installed Magisk the first time. Both of these adapters work fine with other devices.
---
Now installing Magisk with boot.img breaks with "lineage-20.0-20230611-nightly-FP4-signed" (boot b).
It worked just fine when I installed it the same way on "lineage-20.0-20230521-nightly-FP4-signed" (boot a).
What's the correct method of installing Magisk on a Fairphone 4?
After rebooting my A5 2017 a few days ago, it seems to have some problems. It does "boot" fine, asks for my (encryption) password, and goes to the "starting phone..." screen.
After this the screen goes blank. Pressing the power button once doesn't do anything. Holding the power button shows a screen with the options: lockdown (doesn't work), power off and restart.
It does not show my launcher nor anything else, just those lockdown, poweroff and restart button.
Code:
-------- beginning of system
E vold : Failed to chmod /data/system_ce/0: No such file or directory
E vold : Failed to chmod /data/misc_ce/0: No such file or directory
E vold : Failed to chmod /data/media/0: No such file or directory
E StorageManagerService: No valid MediaStore provider found
<>
TaskPersister: restoreTasksForUserLocked: Unable to list files from /data/system_ce/0/recent_tasks
BackupPasswordManager: Unable to read backup pw version
BackupPasswordManager: Unable to read saved backup pw hash
--------- beginning of kernel
After which this stands out to me (removed a whole lot of "yunk"):
Code:
<>
W vold : Trim failed on /data: Inappropriate ioctl for device
W vold : Failed to open none: No such file or directory
<>
--------- beginning of crash
F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4119 (main), pid 4119 (main)
F libc : crash_dump helper failed to exec
E [3: kworker/3:2: 2713] cnss_wlan_unregister_oob_irq_handler: no OOB task is running
E [3: kworker/3:2: 2713] wlan_platform_sdio_enumerate: notify_func=ffffffc000818658, mmc_host_dev=ffffffc0b94ca818, device_present=0
E : [3: kworker/3:2: 2713] card removed
E [0: kworker/u16:3: 1448] mmc1: card remove detected
E [0:iptables-restor: 3899] audit: rate limit exceeded
--------- beginning of main
<>
E CarrierIdProvider: read carrier list from ota pb failure: java.io.FileNotFoundException: /data/misc/carrierid/carrier_list.pb: open failed: ENOENT (No such file or directory)
<>
E rkstack.proces: failed to connect to jdwp control socket: Connection refused
E com.android.se: failed to connect to jdwp control socket: Connection refused
E m.android.phon: failed to connect to jdwp control socket: Connection refused
E ndroid.setting: failed to connect to jdwp control socket: Connection refused
< above multiple times >
E StorageSessionController: Failed to exit session: emulated;0. Killing MediaProvider...
E StorageSessionController: com.android.server.storage.StorageSessionController$ExternalStorageServiceException: Failed to end session: [SessionId: emulated;0. UpperPath: /storage/emulated. LowerPath: /data/media
<>
E StorageManagerService: Failed to mount volume VolumeInfo{emulated;0}:
E StorageManagerService: type=EMULATED diskId=null partGuid= mountFlags=PRIMARY|VISIBLE
E StorageManagerService: mountUserId=0 state=CHECKING
E StorageManagerService: fsType=null fsUuid=null fsLabel=null
E StorageManagerService: path=/storage/emulated internalPath=/data/media
E StorageManagerService:
E StorageManagerService: com.android.server.storage.StorageSessionController$ExternalStorageServiceException: Failed to start session: [SessionId: emulated;0. UpperPath: /storage/emulated. LowerPath: /data/media]
<>
E StorageUserConnection: Service: [ComponentInfo{com.android.providers.media.module/com.android.providers.media.fuse.ExternalStorageServiceImpl}] is null. User [0]
<>
E StorageManagerService: Failed to notify volume state changed to the Storage Service
E StorageManagerService: com.android.server.storage.StorageSessionController$ExternalStorageServiceException: Failed to notify volume state changed for vol : StorageVolume: Internal shared storage
< All StorageManagerService/StorageUserConnection error's above multiple times>
F zygote64: jni_internal.cc:729] JNI FatalError called: (com.android.providers.media.module) frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:786: Failed to mount /data_mirror/data_de/null/0/com.google.android.gms to /data/user_de/0/com.google.android.gms: No such file or directory
F zygote64: runtime.cc:655] Runtime aborting...
F zygote64: runtime.cc:655] Dumping all threads without mutator lock held
<>
E libc : failed to raise ambient capability 0: Operation not permitted
E libc : failed to raise ambient capability 1: Operation not permitted
< Above repeated but then number increases >
E DEBUG : failed to readlink /proc/6117/fd/0: Permission denied
E DEBUG : failed to readlink /proc/6117/fd/1: Permission denied
< Above repeated but then number increases >
F crash_dump64: crash_dump.cpp:474] failed to attach to thread 6117, already traced by 0 ()
E libprocessgroup: Error encountered killing process cgroup uid 10187 pid 6108: Permission denied
< A lot repeated errors of the Permission/denied and operation not permitted above + the StorageManagerService/StorageUserConnection errors >
Based on those errors, I think my /data partition is broken. However, when booting into TWRP recovery, the partition looks fine and I can browse all the files?
ROM: official lineageOS
Please let me know if you know how to fix this, or how to troubleshoot further. It's luckily not my main phone, but I'd like it to be usable again.