Develop Bugs

Unrevoked problems with Linux x86_64 (SOLVED)

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

Encryption fails with LOS13

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.

Wifi & Bluetooth wont turn on

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.

[BQ Aquaris X2 PRO] WiFi not working after OTA update

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?

Broken boot process/file system?

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.