Database Develop

Wi-fi and BT Failing to Start after Rooting Issues - No solutions worked till date!

Hi All,
Need some help in getting my wifi and bluetooth back to normal. It's over a month now and all my attempts have failed! I would really appreciate some ideas here. Thank you, and sorry for long thread.
Phone info:
Samsung galaxy S6 SM-G920T (T-Mobile), firmware version: NRD90M.G920TUVS6FRC1, stock OS with root and TWRP recovery
Situation:
Bluetooth does not turn ON at all
Wifi takes a long time to turn ON, and only way to turn it ON is from settings (quick access tile does not work)
Wifi does not remember any password
All other functions work correctly, and the phone is now lightning fast after factory reset
Details and Steps Taken:
Rooted my phone a month ago, and started changing config. Took OS and app backup only, but no EFS/other partition backup.
Turned OFF "Allow OEM Unlock" - don't ask why
This (I believe) resulted in WIFI not remembering passwords, so after reviewing potential solutions, I changed "Secure.Storage" value in build.prop to "0"
Took backup of WPA_supplicant.conf and deleted the file
Problem was not resolved, and I had to restart the phone
Restart resulted in FRP lock - to resolve this I re-installed the OS from stock firmware from Sammobile; Yet - no luck on wifi and bluetooth, error still persisted
I reviewed the system log and found tons of errors (listed below). Based on errors, I tried:
Copying libbluetooth_jni.so library file to '/system/lib' and '/system/vendor/lib' folders
Changing 'semGetAllowBluetoothMode' value to "True" - this reduced some errors (refer below)
Validating file / folder permissions for the /efs partition - they seem to be appropriate, but I cannot confirm since there is no reference
I have also tried using SmartSwitch - but it doesn't recognize phone in download mode. It backups the apps, etc. though
Also wiped the system partition once using TWRP, and re-imaged. Yet no luck.
My hunch currently for these errors is:
The /efs permissions became incorrect or partition became corrupt due to some configuration I performed
The system lost its encryption key when the "OEM unlock" was disabled, and thus cannot read any files from the /system and /efs partition (the device was NOT encrypted, but I am thinking /efs is always encrypted by system - correct me if I am wrong)
System log snippets:
Bluetooth Related Log:
Bluetooth GATT service:
Code:
BtGatt.GattService: [GSIM LOG]: gsimLogHandler: null, msg: MESSAGE_LOAD_PREF
Bluetooth Adapter Service:
Code:
BluetoothAdapterService: onProfileServiceStateChanged() serviceName=com.android.bluetooth.gatt.GattService, state=12, Message sending
semGetAllowBluetoothMode:
Resolved this error by updating the value to "True" in build.prop. Was this the right fix, or is it supposed to get value = 2.
Code:
DevicePolicyManagerService: semGetAllowBluetoothMode - value retunrs : 2
Wifi error log:
Code:
WifiHW : ##################### set firmware type 0 #####################
WifiHW : ==========[WIFI] SEMCO MODULE ===========
WifiHW : TEMP_FAILURE_RETRY complete
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 208 Softap operation succeeded
WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
WifiHW : supplicant_name : p2p_supplicant
WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
WifiWatchdogStateMachine: Unhandled message { when=0 what=135173 arg1=2 target=com.android.internal.util.StateMachine$SmHandler } in state NotConnectedState
WifiMonitor: startMonitoring(wlan0) failed!
WifiStateMachine: Failed to setup control channel, restart supplicant
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0
WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 2
WifiHAL : Event processing terminated
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 219 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 229 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 240 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 248 Softap operation succeeded
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 11
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 256 Softap operation succeeded
WifiStateMachine: Failed 6 times to start supplicant, unload driver
WifiStateMachine: sendErrorBroadcast code:10
WifiController: WifiControllerWifi turn on failed

Titanium Backup crashing on start

Hi
I am using Lineageos 15.1 on my good old nexus 6. Working well but Titanium Backup is crashing on start .... I tried uninstall, then reinstall but nothing.
I tried one
Code:
adb logcat
in order to get some clue , here is one extract of the file :
08-04 18:38:37.718 2562 2574 I ActivityManager: Start proc 6602:com.keramidas.TitaniumBackup/u0a233 for activity com.keramidas.TitaniumBackup/.MainActivity
08-04 18:38:37.802 14937 5573 I DeviceStateChecker: DeviceStateChecker cancelled
08-04 18:38:37.802 14937 14937 I MicroDetector: Keeping mic open: false
08-04 18:38:37.811 14937 5898 I AudioController: internalShutdown
08-04 18:38:37.813 14937 6308 I MicroRecognitionRunner: Stopping hotword detection.
08-04 18:38:37.818 6602 6602 I o.კ : onCreate()
08-04 18:38:37.842 6602 6602 I o.კ : Detected CPU architecture: ARM
08-04 18:38:37.845 6602 6602 W Settings: Setting android_id has moved from android.provider.Settings.System to android.provider.Settings.Secure, returning read-only value.
08-04 18:38:37.851 6602 6602 D o.dJ : Debug features are disabled.
08-04 18:38:37.855 6602 6602 I o.dx : restoreMySettings_ifNeeded()
08-04 18:38:37.863 6602 6602 I o.dx : Internal settings found => No need to restore.
08-04 18:38:37.865 2235 6523 D audio_hw_primary: disable_audio_route: usecase(9) reset and update mixer path: audio-record
08-04 18:38:37.866 2235 6523 D audio_hw_primary: disable_snd_device: snd_device(75: voice-rec-mic)
08-04 18:38:37.879 14937 5898 I MicrophoneInputStream: mic_close SR : 16000 CC : 16 SO : 1999
08-04 18:38:37.879 14937 5417 I MicroRecognitionRunner: Detection finished
08-04 18:38:37.949 6602 6602 I com.keramidas.TitaniumBackup.MainActivity: Main Activity is being created for the first time => scheduling next wake-up ...
08-04 18:38:37.950 6602 6602 I o.dg : scheduleNextWakeup(): Invoked with idToExcludeForToday=null
08-04 18:38:37.974 6602 6602 I o.dg : scheduleNextWakeup(): No next wakeup scheduled.
08-04 18:38:37.975 6602 6621 I o.ỵ : Thread started.
08-04 18:38:37.989 6602 6602 I ToolbarWidgetWrapper: Progress display unsupported
08-04 18:38:38.024 6602 6623 D OpenGLRenderer: HWUI GL Pipeline
08-04 18:38:38.031 6602 6622 I o.ep : Detected 0 mount point(s) in addition to Android "external" storage.
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] No cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] Cache valid? = false
08-04 18:38:38.034 6602 6622 I o.ch : [Licensing] Deleting non-valid cache file: /storage/emulated/0/data/com.keramidas.TitaniumBackup/licensing-cache.xml
08-04 18:38:38.035 6602 6622 I o.cj : [Licensing] Performing query: attempt 1/4
08-04 18:38:38.040 11256 11256 I com.keramidas.TitaniumBackupPro.LicenseQueryService: onCreate()
08-04 18:38:38.078 6602 6623 I Adreno : QUALCOMM build : a5b4970, If5818605d9
08-04 18:38:38.078 6602 6623 I Adreno : Build Date : 10/12/16
08-04 18:38:38.078 6602 6623 I Adreno : OpenGL ES Shader Compiler Version: XE031.09.00.04
08-04 18:38:38.078 6602 6623 I Adreno : Local Branch : N24D
08-04 18:38:38.078 6602 6623 I Adreno : Remote Branch :
08-04 18:38:38.078 6602 6623 I Adreno : Remote Branch :
08-04 18:38:38.078 6602 6623 I Adreno : Reconstruct Branch :
08-04 18:38:38.087 6602 6623 I zygote : android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
08-04 18:38:38.106 6602 6623 I OpenGLRenderer: Initialized EGL, version 1.4
08-04 18:38:38.106 6602 6623 D OpenGLRenderer: Swap behavior 1
08-04 18:38:38.138 2562 3863 W ActivityManager: Permission Denial: Accessing service ComponentInfo{com.android.vending/com.google.android.finsky.services.LicensingService} from pid=11256, uid=10143 requires com.android.vending.CHECK_LICENSE
08-04 18:38:38.140 6602 6624 E AndroidRuntime: FATAL EXCEPTION: Thread-4
08-04 18:38:38.140 6602 6624 E AndroidRuntime: Process: com.keramidas.TitaniumBackup, PID: 6602
08-04 18:38:38.140 6602 6624 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.vending.licensing.ILicensingService pkg=com.android.vending }
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:2005)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at android.os.Parcel.readException(Parcel.java:1951)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at com.keramidas.TitaniumBackupPro.LicenseQueryServiceRemoteInterface$if$if.ˊ(Source:133)
08-04 18:38:38.140 6602 6624 E AndroidRuntime: at o.cl.run(Source:75)
08-04 18:38:38.148 2562 3275 W ActivityManager: Force finishing activity com.keramidas.TitaniumBackup/.MainActivity
08-04 18:38:38.165 6602 6624 I Process : Sending signal. PID: 6602 SIG: 9
08-04 18:38:38.201 2562 3290 I ActivityManager: Process com.keramidas.TitaniumBackup (pid 6602) has died: vis +99TOP
Click to expand...
Click to collapse
It seems to be a permission issue but any help will be welcome ... How to solve ?
Thanks
mahashakti89

I think this has to do with the play store. Have you tried clearing cache and data for the play store then reinstalling TiBu?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
I think this has to do with the play store. Have you tried clearing cache and data for the play store then reinstalling TiBu?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
Yes, I already tried clearing cache, uninstall, reinstall but it won't work.
Thanks

I want to double check, you cleared the play store app's data and cache. I'm not talking about TiBu cache/data.
If that's what you meant, then I would do a nandroid and clean flash the ROM again (wiping system, data, dalvik and cache - NOT user data). Use a small Gapps package like nano, then install just TiBu after setup and see if the problem persists.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
I want to double check, you cleared the play store app's data and cache. I'm not talking about TiBu cache/data.
If that's what you meant, then I would do a nandroid and clean flash the ROM again (wiping system, data, dalvik and cache - NOT user data). Use a small Gapps package like nano, then install just TiBu after setup and see if the problem persists.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Hi,
I did a clean install this morning. Wiped system , cache, dalvik but I did'nt format data. I used TWRP. How do you format data and NOT user data ?
What do you mean by clearing play store app's data and cache ?
Thanks

No need to format data. That is usually only done in internal storage (user data) to permanently dycrypt the device.
Wiping data (the partition mounted at /data), is done as a part of a factory reset, or the default wipe in TWRP. Wiping system requires going into the advanced menu in the TWRP wipe screen, and selecting it. Data, cache and dalvik are selected there as well. Internal storage (user data) can also be wiped from that screen, but typically you don't want to do that as all personal files get deleted.
To clear the play store data and cache, you go to settings -> apps -> google play store -> storage
If your problem with TiBu began as part of a clean install, it may be due to a bad flash, wrong gapps, bad download (always use checksums like MD5) or a hiccup during setup.
In this case then, I would remove TiBu, clear the play store data and cache then reinstall TiBu if it doesn't improve, them double check the quality of the downloaded files you installed, make site you've got the correct gapps and wipe, then flash again.
Sent from my Nexus 6 using XDA-Developers Legacy app

ktmom said:
No need to format data. That is usually only done in internal storage (user data) to permanently dycrypt the device.
Wiping data (the partition mounted at /data), is done as a part of a factory reset, or the default wipe in TWRP. Wiping system requires going into the advanced menu in the TWRP wipe screen, and selecting it. Data, cache and dalvik are selected there as well. Internal storage (user data) can also be wiped from that screen, but typically you don't want to do that as all personal files get deleted.
That's exactly what I did. Formatted all partitions except /data and Internal storage.
To clear the play store data and cache, you go to settings -> apps -> google play store -> storage
Already done. I asked because I was not sure if I mean the same as you mean
I will perhaps a full wipe tomorrow or wit till a new version of LineageOS.
Regards
Click to expand...
Click to collapse

I hope you mean "wipe" when you're saying format [emoji6]. A format is a different process.
The fact that you did not wipe data is in all probability, the cause of your problem.
Sent from my Nexus 6 using XDA-Developers Legacy app

ktmom said:
I hope you mean "wipe" when you're saying format [emoji6]. A format is a different process.
The fact that you did not wipe data is in all probability, the cause of your problem.
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, I mean wipe when I say format .... I wait till Wednesday, new LineageOS version, if it doesn't work I shall wipe data .
Thanks

mahashakti89 said:
Yes, I mean wipe when I say format .... I wait till Wednesday, new LineageOS version, if it doesn't work I shall wipe data .
Thanks
Click to expand...
Click to collapse
I did'nt wait .... Wiped data. It works now ....
Thanks for helping

Hitting the "thanks" button on posts is always appreciated.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

Need Belutooth partition backup of Moto one power device having January 1st Patch

Hi all,
Can anybody please share the twrp backup of bluetooth partition of Moto One Power device having the Pie January 1st Patch? My bluetooth partition got formatted while restoring the twrp backup and restore got failed. Now I'm not able to use the bluetooth. I have got the OTA with face unlock, But thile installing the OTA I started getting bluetooth partition block verification failed saying partition got mounted rw. And while restoring the earlier backup it got formatted :crying:

Got it fixed after a hell lot of research
Hi all,
Finally after searching a lot in net, flashed the bluetooth partition with the img file available in the following site ( Phenotypically ) -> mirrors[dot]lolinet[dot]com[slash]firmware[slash]moto[slash]chef[slash]official[slash]RETIN
The root cause for getting the partition formatted is gettiing the following error, to solve it I tried to restore bluetooth partition and it resulted currupt. Hope it may help somebody who will be get the same issue and stumble upon this page.
I was getting "Update Failed" error in Moto updator. While checking for the logs via adb observed the following error :
Code:
update_engine: [0306/081413.872062:INFO:delta_performer.cc(397)] Applying 8 operations to partition "bluetooth"
update_engine: [0306/081413.885946:ERROR:fec_file_descriptor.cc(30)] No ECC data in the passed file
update_engine: [0306/081413.886903:ERROR:delta_performer.cc(432)] Unable to open ECC source partition bluetooth on slot A, file /dev/block/bootdevice/by-name/bluetooth_a: Success
update_engine: [0306/081413.887044:ERROR:delta_performer.cc(1042)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
update_engine: [0306/081413.887251:ERROR:delta_performer.cc(1047)] Expected: sha256|hex = 9F69430D4BED82B26E49AAA81E0F1E823687605099AD61F45A361A96E7BE6FEE
update_engine: [0306/081413.887321:ERROR:delta_performer.cc(1050)] Calculated: sha256|hex = 734059C0A03A2B2E61CBF3302F2982F3811FD243064D434A6CFC0FAEBDBC0E85
update_engine: [0306/081413.887393:ERROR:delta_performer.cc(1061)] Operation source (offset:size) in blocks: 0:1,6:2,34:1,101:30
update_engine: [0306/081413.887487:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2019-03-05 03:36:34.000 UTC.
update_engine: [0306/081413.887573:ERROR:delta_performer.cc(1340)] source_fd != nullptr failed.
update_engine: [0306/081413.887652:ERROR:delta_performer.cc(301)] Failed to perform BROTLI_BSDIFF operation 4604, which is the operation 0 in partition "bluetooth"
update_engine: [0306/081413.887721:ERROR:download_action.cc(337)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
update_engine: [0306/081413.888372:INFO:delta_performer.cc(317)] Discarding 301 unused downloaded bytes
update_engine: [0306/081413.894845:INFO:multi_range_http_fetcher.cc(172)] Received transfer terminated.
update_engine: [0306/081413.895113:INFO:multi_range_http_fetcher.cc(124)] TransferEnded w/ code 206
update_engine: [0306/081413.895166:INFO:multi_range_http_fetcher.cc(126)] Terminating.
update_engine: [0306/081413.895224:INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
update_engine: [0306/081413.895278:INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
Since Moto One Power is having A/B Partition and seemless update support, It looks like the incremental security update was checking for the checksum of the corresponding partition before applying the incremental update. To fix this I flashed the bluetooth and other failing partitions with the apropriate images available in the above shared link.

Hi there, i'm facing the same issue. Can u please tell me which img to flash from stock firmware?

TWRP backup failed Error 255: Error adding file '/data/system_ce/0'

I found some threads with this problem but all this threads have been with "more users" like 999, so I checked this but I have only this one user 0
latest TWRP + latest Existenz Pie + latest Magix, if this information is important?
I don´t know if you need the full log or even more of the part with the error, but this the only part where I can see an error?
Code:
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/0' - 'c078db7cd57ae4ef'
I:Error adding file '/data/system_ce/0' to '/external_sd/TWRP/BACKUPS/BH901GHLCU/2019-10-14--05-40-56_520A8131/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/BH901GHLCU/2019-10-14--05-40-56_520A8131/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
btw. a question to twrp backup: if I want to do a backup because I want to tryout another rom and switching back, is it better/faster to do a system.img?

TWRP commandline backup problems

Hi.
I'm trying to backup data partition with cmdline due to a broken display (currently, LOS 17.1 is installed). However it doesn't work. It seems to having issues with /data/system_ce/0. Can anyone help? The backup worked with via display in the past. Here is some logfile output:
Code:
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37
Invalid encryption mode 'ice:aes-256-cts'
Backing up Data...
Backups of Data do not include any files in internal storage such as pictures or downloads.
Invalid encryption mode 'ice:aes-256-cts'
Breaking backup file into multiple archives...
I:Creating backup...
I:Creating tar file '/data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/data.ext4.win000'
I:addFile '/data/server_configurable_flags' including root: 1
==> set selinux context: u:object_r:server_configurable_flags_data_file:s0
found policy '/data/server_configurable_flags' - '1DK' - 'c0cd60c87b2b4dfc'
I:addFile '/data/system_ce' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
I:addFile '/data/system_ce/0' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/system_ce/0' - '1435bb0a12e56a60'
I:Error adding file '/data/system_ce/0' to '/data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/data.ext4.win000'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
I:InfoManager saving '/data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/data.info'
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I:Copied file /tmp/recovery.log to /data/media/0/TWRP/BACKUPS/84a0237/2021-05-22--19-20-37/recovery.log
Backup Failed
The device uses FBE, but users are decrypted successfully:
Code:
User 0 Decrypted Successfully
I:All found users are decrypted.
Data successfully decrypted
I can pull data from every folder. Maybe it is an idea to pull the data manually? But which data/folders should be pulled?
Thanks everybody in advance for some responses and help.