I have a phone Sony Xperia S LT26i (Android version 4.1.2, Build number 6.2.B.0.211). I do not know the history of this phone. It has problems with WiFi. When I want to connect WiFi (Setting-> Wireless & networks -> Turn on WiFi), I get a message Wi-Fi Error. It can not turn on WiFi. When I check the MAC-address WiFi (Setting-> About phone -> Status -> WiFi MAC-address) I always see it Unavailable. I check the file /data/ets/wifi/fw and I can see that there is written MAC-address 30:39:26:0B:C8:73. When I check MAC-address Bluetooth, I can see 90:C1:15:FC:6E:18. I know that usually MAC-address Bluetooth is slightly less, than the MAC-address WiFi, but numbers are relatives and similar. But I see that in my phone, they differ greatly!
Probably the problem with WiFi is what the hardware MAC-address Wi-fi and MAC-address WiFi in the file /data/ets/wifi/fw differ?
Help me please restore operability of WiFi.
Help me please...:crying:
porcelana said:
Help me please...:crying:
Click to expand...
Click to collapse
Try reset to factory settings.
AlinTheron said:
Try reset to factory settings.
Click to expand...
Click to collapse
I've done it already several times. It doesn't solve a problem.
There are still ideas?
porcelana said:
I've done it already several times. It doesn't solve a problem.
There are still ideas?
Click to expand...
Click to collapse
Click Here -> TRY THIS
Error log of Dalvik Debug Monitor
AlinTheron said:
Click Here -> TRY THIS
Click to expand...
Click to collapse
When I start Dalvik Debug Monitor in Android SDK, I see the error log (at phone start), with reports about WiFi. This is shown below, but it is not complete logs, and only a few selected lines:
Code:
Log Startup (error)
01-12 15:03:54.409: E/EventHub(369): could not get driver version for /dev/input/mice, Not a typewriter
01-12 15:03:54.759: E/CommandListener(150): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
01-12 15:03:54.759: E/WifiStateMachine(369): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
01-12 15:03:54.779: E/MobileDataStateTracker(369): default: Ignoring feature request because could not acquire PhoneService
01-12 15:03:54.779: E/MobileDataStateTracker(369): default: Could not enable APN type "default"
01-12 15:03:54.789: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:03:54.789: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:03:54.789: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '2 softap fwreload wlan0 STA' failed with '400 2 Softap operation failed (No such file or directory)'
01-12 15:03:54.799: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '4 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 4 Failed to set address (No such device)'
01-12 15:03:54.839: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:54.889: E/AudioHardwareMSM8660(156): unknown stream
01-12 15:03:54.939: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.419: E/SQLiteLog(369): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]
01-12 15:03:55.449: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.549: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.559: E/Trace(610): error opening trace file: No such file or directory (2)
01-12 15:03:55.649: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.859: E/wpa_supplicant(585): nl80211: Could not set interface 'wlan0' UP
01-12 15:03:55.859: E/wpa_supplicant(585): wlan0: Failed to initialize driver interface
01-12 15:03:56.189: E/Trace(664): error opening trace file: No such file or directory (2)
01-12 15:03:57.629: E/SocketMonitor(735): The socket server maybe not started.
01-12 15:03:57.629: E/SocketMonitor(735): Error in SocketMonitor.
01-12 15:04:05.919: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:05.959: E/(156): [ACDB RTC]->rtc init done!->result [0]
01-12 15:04:05.959: E/Diag_Lib(156): actp_diag_init: call diag init function with 418A0959
01-12 15:04:05.959: E/(156): [ACDB ACPH]->actp diag init done!
01-12 15:04:05.959: E/ACDB-LOADER(156): Error reading MBHC general config returned = fffffff3
01-12 15:04:06.929: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:09.929: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
01-12 15:04:12.629: E/SocketMonitor(735): The socket server maybe not started.
01-12 15:04:12.629: E/SocketMonitor(735): Error in SocketMonitor.
01-12 15:04:12.839: E/Trace(2073): error opening trace file: No such file or directory (2)
01-12 15:04:13.189: E/MM_OSAL(156): ValidateAACFile failed
01-12 15:04:13.249: E/Trace(2131): error opening trace file: No such file or directory (2)
01-12 15:04:14.779: E/MM_OSAL(156): ValidateAACFile failed
01-12 15:04:14.799: E/Trace(2250): error opening trace file: No such file or directory (2)
01-12 15:04:14.939: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:04:14.939: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:04:14.939: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '8 softap fwreload wlan0 STA' failed with '400 8 Softap operation failed (No such file or directory)'
01-12 15:04:14.949: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '10 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 10 Failed to set address (No such device)'
01-12 15:04:14.959: E/WifiHW(369): Unable to open connection to supplicant on "wlan0": No such file or directory
01-12 15:04:14.979: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.019: E/Trace(2299): error opening trace file: No such file or directory (2)
01-12 15:04:15.079: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.159: E/Trace(2319): error opening trace file: No such file or directory (2)
01-12 15:04:15.189: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.189: E/(2262): vnd.android.cursor.dir/event
01-12 15:04:15.289: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.309: E/ThermalDaemon(1152): Fusion modem thermal mitigation not available.
01-12 15:04:15.309: E/ThermalDaemon(1152): Sensor setup:[tsens_tz_sensor0]
01-12 15:04:15.389: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.399: E/Trace(2348): error opening trace file: No such file or directory (2)
01-12 15:04:15.499: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.569: E/Trace(2379): error opening trace file: No such file or directory (2)
01-12 15:04:15.609: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.849: E/Trace(2400): error opening trace file: No such file or directory (2)
01-12 15:04:15.919: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.989: E/Trace(2421): error opening trace file: No such file or directory (2)
01-12 15:04:16.019: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:16.019: E/wpa_supplicant(2295): nl80211: Could not set interface 'wlan0' UP
01-12 15:04:16.019: E/wpa_supplicant(2295): wlan0: Failed to initialize driver interface
01-12 15:04:16.069: E/Trace(2438): error opening trace file: No such file or directory (2)
01-12 15:04:17.239: E/MM_OSAL(156): ValidateAACFile failed
01-12 15:04:17.319: E/Trace(2509): error opening trace file: No such file or directory (2)
01-12 15:04:17.509: E/Trace(2523): error opening trace file: No such file or directory (2)
01-12 15:04:17.629: E/ThermalDaemon(1152): Thermald Server: accept[fd=31]
01-12 15:04:17.629: E/ThermalDaemon(1152): Thermald Server: write success [data=600][0x58 0x02]
01-12 15:04:17.639: E/Trace(2543): error opening trace file: No such file or directory (2)
01-12 15:04:17.819: E/SQLiteLog(2523): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]
01-12 15:04:18.119: E/Trace(2606): error opening trace file: No such file or directory (2)
01-12 15:04:26.969: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:29.779: E/Trace(2847): error opening trace file: No such file or directory (2)
01-12 15:04:29.969: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:29.969: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
01-12 15:04:34.979: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:04:34.979: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:04:34.989: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '11 softap fwreload wlan0 STA' failed with '400 11 Softap operation failed (No such file or directory)'
01-12 15:04:35.089: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '13 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 13 Failed to set address (No such device)'
01-12 15:04:35.159: E/wpa_supplicant(2894): Could not read interface wlan0 flags: No such device
01-12 15:04:36.169: E/wpa_supplicant(2894): nl80211: Could not set interface 'wlan0' UP
01-12 15:04:36.169: E/wpa_supplicant(2894): wlan0: Failed to initialize driver interface
01-12 15:04:46.109: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:50.110: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
01-12 15:04:55.120: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:04:55.120: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:04:55.130: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '14 softap fwreload wlan0 STA' failed with '400 14 Softap operation failed (No such file or directory)'
01-12 15:04:55.150: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '16 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 16 Failed to set address (No such device)'
01-12 15:04:55.160: E/WifiHW(369): Unable to open connection to supplicant on "wlan0": No such file or directory
01-12 15:04:55.189: E/wpa_supplicant(2948): Could not read interface wlan0 flags: No such device
01-12 15:04:56.189: E/wpa_supplicant(2948): nl80211: Could not set interface 'wlan0' UP
01-12 15:04:56.189: E/wpa_supplicant(2948): wlan0: Failed to initialize driver interface
01-12 15:05:07.179: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:05:10.180: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
Run logcat:
E/WifiHW ( 369): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 3043): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 3043): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 3043): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 3043): wlan0: Failed to initialize driver interface
E/WifiHW ( 369): Supplicant not running, cannot connect
D/StateMachine( 369): handleMessage: E msg.what=147458
D/StateMachine( 369): processMsg: SupplicantStartingState
D/WifiStateMachine( 369): SupplicantStartingState{ what=147458 when=-3ms }
E/WifiStateMachine( 369): Failed 6 times to start supplicant, unload driver
..
porcelana said:
[/CODE]
Click to expand...
Click to collapse
Read THIS TUTORIAL Maybe you can fix it.
AlinTheron said:
Read THIS TUTORIAL Maybe you can fix it.
Click to expand...
Click to collapse
Thank you, but is not work for my case
This works fine on my other phone SAMSUNG S2. But my main phone is other. This is the Sony Xperia S model number is LT26i. Code * # * # 526 # * # * does not work for him. I think that for Sony Xperia S other code is necessary. Somebody knows the correct code for Sony Xperia S? My WiFi is not turning on. When i dial *#*#526#*#* there is no message. I stopped on a Step 1. Please help me.
porcelana said:
Thank you, but is not work for my case
My phone name is Sony Xperia S, model number is LT26i. My WiFi is not turning on. When i dial *#*#526#*#* there is no message. I stopped on a Step 1. Please help me.
Click to expand...
Click to collapse
Do you have JellyBean .211 ? WIFI is one of the many bugs in this ROM, you'll have to wait for an update.
---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------
Try this, leave it on Airplane mode for 5 minutes, if that doesn't work, remove the sim card for 10 minutes and then insert it back in. Try you're WIFI after those tweaks.
---------- Post added at 08:53 PM ---------- Previous post was at 08:42 PM ----------
Or, repair your phone with Pc Companion. Back up first, because it will erase everything.
AlinTheron said:
Do you have JellyBean .211 ? WIFI is one of the many bugs in this ROM, you'll have to wait for an update.
---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------
Try this, leave it on Airplane mode for 5 minutes, if that doesn't work, remove the sim card for 10 minutes and then insert it back in. Try you're WIFI after those tweaks.
---------- Post added at 08:53 PM ---------- Previous post was at 08:42 PM ----------
Or, repair your phone with Pc Companion. Back up first, because it will erase everything.
Click to expand...
Click to collapse
Yes i have now JellyBean .211. But before I had version 2.73 and WIFI is not working on it. Then I updated to JB .211 by PC Companion . So this is an old problem. Now I'm waiting for help to solve it.
porcelana said:
Yes i have now JellyBean .211. But before I had version 2.73 and WIFI is not working on it. Then I updated to JB .211 by PC Companion . So this is an old problem. Now I'm waiting for help to solve it.
Click to expand...
Click to collapse
Do a repair with Pc Companion or SUS
AlinTheron said:
Do a repair with Pc Companion or SUS
Click to expand...
Click to collapse
I have PC Companion version 2.10.165 and I do not see her features Repair.
I do not have the SUS. I will search and install it and do the repair, then come back here again.
Thank you for your help.
porcelana said:
I have PC Companion version 2.10.165 and I do not see her features Repair.
I do not have the SUS. I will search and install it and do the repair, then come back here again.
Thank you for your help.
Click to expand...
Click to collapse
Ok, try to press UPDATE on Pc Companion and even if it says that you have the latest software installed it will give you the option to repair your phone. Or press Support Zone.
AlinTheron said:
Ok, try to press UPDATE on Pc Companion and even if it says that you have the latest software installed it will give you the option to repair your phone. Or press Support Zone.
Click to expand...
Click to collapse
I did this and PC Companion tells me that I have the last Update, and no others. Repair function is not available.
porcelana said:
I did this and PC Companion tells me that I have the last Update, and no others. Repair function is not available.
Click to expand...
Click to collapse
READ THIS
Worst case scenario : Hardware problem.
AlinTheron said:
READ THIS
Click to expand...
Click to collapse
I took all steps from this manual, but WiFi wasn't restored. Any ideas? .
AlinTheron said:
Worst case scenario : Hardware problem.
Click to expand...
Click to collapse
In the error log (in the message #6) reports that there is a problem with the driver and with wlan0. I want to check that all configuration files for WiFi and MAC are available in phone. Somebody can tell me what configuration files for WiFi and MAC have SXS? It is possible that in my SXS missing necessary files.
Definitely a hardware problem.
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.
Hey,
i got the same issue as mention here --> https://forum.xda-developers.com/galaxy-tab-s/help/wifi-bluetooth-t3725452
i checked /efs/wifi/.mac.info which contains the right MAC. Anyway i was not able to activate WiFi or BT. There are a lot file inside the efs folder so i dont think the partition is corrupted.
I got lineage-microg flashed, but i also tried lineage build 07.09.2019 with same result.
Any suggestions how to fix this issue?
I reflashed original Firmware, which shows the correct MAC under Systemstatus, but i cannot enable WiFi or BT anyways ...
Could someone be nice and check which file are in your /efs folder? Maybe i'm missing some ...
mine is:
/efs/
/efs/lost+found
/efs/drm
/efs/drm/sdrm
/efs/drm/sdrm/data_agent
/efs/drm/playready
/efs/drm/playready/00003.PRV
/efs/.files
/efs/.files/.dx1
/efs/.files/.dm33
/efs/.files/.mp301
/efs/wifi
/efs/wifi/.mac.info
/efs/wifi/.mac.cob
/efs/bluetooth
/efs/bluetooth/bt_addr
/efs/prov
/efs/prov/ffffffff00000000000000000000000c.tlbin
/efs/prov/libdevkm.lock
/efs/imei
/efs/imei/mps_code.dat
/efs/FactoryApp
/efs/FactoryApp/hist_nv
/efs/FactoryApp/fdata
/efs/FactoryApp/test_nv
/efs/FactoryApp/earjack_count
/efs/FactoryApp/factorymode
/efs/FactoryApp/keystr
/efs/FactoryApp/serial_no
/efs/FactoryApp/hw_ver
/efs/FactoryApp/prepay
/efs/FactoryApp/baro_delta
/efs/FactoryApp/asoc
/efs/FactoryApp/batt_cable_count
/efs/FactoryApp/max_temp
/efs/FactoryApp/batt_discharge_level
/efs/FactoryApp/max_current
/efs/FactoryApp/control_no
/efs/ss_data
/efs/nv.log
/efs/nv_data.bin
/efs/.nv_state
/efs/.nv_core.bak
/efs/.nv_core.bak.md5
/efs/.nv_data.bak
/efs/.nv_data.bak.md5
/efs/gyro_calibration_data
/efs/nv_data.bin.md5
/efs/00000000.authtokcont
/efs/grip_cal_data
/efs/prov_data
/efs/prov_data/dev_root
/efs/prov_data/dev_root/dev_root.dat
/efs/prov_data/dev_root/sym_key.dat
/efs/prov_data/knox
/efs/prov_data/knox/knox.dat
/efs/prov_data/ccm
/efs/prov_data/ccm/ccm.dat
/efs/sec_efs
/efs/sec_efs/ucm_ca_cert
/efs/wv.keys
/efs/h2k.dat
/efs/mc
/efs/cpk
/efs/TEE
/efs/SMS
/efs/pfw_data
/efs/Battery
/efs/Battery/batt_capacity_max
/efs/recovery
/efs/recovery/postrecovery
/efs/umc
/efs/umc/BulkEnrollmentProfile
/efs/edk_p_sd
logact gives me:
09-13 13:29:27.920 2795 7794 E WifiMonitor: startMonitoring(wlan0) failed!
09-13 13:29:32.935 2315 2956 W CommandListener: Failed to retrieve HW addr for wlan0 (No such device)
09-13 13:29:32.935 2795 7794 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '54 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 54 Failed to set address (No such device)'
09-13 13:29:32.940 2795 7794 E wifi : Could not read interface wlan0 flags: 19
09-13 13:29:32.945 2795 7794 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
09-13 13:29:33.310 15395 15395 I wpa_supplicant: set_csc_config : ifname(wlan0), certi_flags(0x0), autoconnect_flags(0x0), opbranding_flags(0x0), boolean_flags(0x20008), vendorssid_list()
09-13 13:29:33.495 15395 15395 E wpa_supplicant: Could not read interface wlan0 flags: No such device
09-13 13:29:33.495 15395 15395 I wpa_supplicant: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
09-13 13:29:33.495 15395 15395 E wpa_supplicant: Could not read interface wlan0 flags: No such device
09-13 13:29:33.495 15395 15395 E wpa_supplicant: wlan0: Failed to initialize driver interface
and yes, thats true. There is no WiFi device unde /dev. Where is it gone?
You need to post more info on what caused this?
ashyx said:
You need to post more info on what caused this?
Click to expand...
Click to collapse
What info do you need?
I got the device from a friend because it refuses to charge. Because of this fault he put it inside a locker in his Bathroom for about a year.
I got it charging by holding down power and volume down for 30 seconds, plug in charger while holding down these buttons and hold it for again 30 seconds. After that it started to charge.
After first boot WiFi turned on but toogled of randomly. By toogling on BT it got better but not much. After i flashed lineage MAC was shown as 02:00:00:00:00 and WiFi wont turn on. So i reverted to Stock ROM. Here MAC was shown correctly but WiFi wont turn on. Same for BT. This is the current state.
Because my friend stored the device in his Bathroom (why people do sh*t like this???) i think maybe some steam found its way inside the device and maybe under/inside the Chip. But i want to be sure before i'll try to replace it.
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?