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

[Q] debuggerd.exynosabuse

Hello,
today as i was accessing my email on Opera Mobile, the SuperSU window popped up by itself and asked me for root acces for a program called "debuggerd.exynosabuse". I dont know what this debuggerd.exynosabuse is and i didnt open any apk before the SU window suddenly popped up..so naturally i denied it root access...then I went into the SuperSU log file and I saw that it kept trying to get root access for two minutes continuously and about 15 tries... also it doesnt have any icon in the apps section of SuperSU. Any ideas what this is about?
Thanks

Look for the app in app drawer named exynos abuse.
Sent from my GT-N7100 using xda app-developers app

Ok. So I m looking for what exactly? I have already mentioned that it is called debuggerd.exynosabuse. it is not the exynos abuse apk, which I used to root my phone and patch the exploit. It is a different app that has no icon in the SU logfile. This debuggerd is always trying to get root access to modify some root files but I have it denied in SU. It tries to get root access 50 times a day or more. What is this program and where did it come from and what should I do with it. Thanks.

Maybe clear data...
Sent from my GT-N7100 using xda app-developers app

You are not alone
http://www.chainfire.eu/articles/126/ExynosAbuse_APK_released_/
may be malware

Try a full wipe including system cache and dalvik and data.
Then flash latest stock rom and root via cfautoroot.
Also backing up anything using any software is not recommended as malware might have infected it.
Sent from my GT-N7100 using xda app-developers app

I just had the same experience for the first time, unfortunately seeing it was a part of ExynosAbuse, I authorized it...
I then saw a lot going on, and in between SuperSU notifications, I saw Adblock Plus notifications too... Maybe related?

As I said try full wipe and flash latest stock rom.
Sent from my GT-N7100 using xda app-developers app

Well, I'd like to know before I wipe, it's not an easy thing to do for me right now, plus if it's something in the app and I reinstall the app after wiping, I'll have the same problem...

Than you for your input Dr Ketan. I see that this is a relatively new problem and its got people wondering/worried, I appreciate that this issue has come to your attention.
Dear UtkarshGupta, Sure anyone can nuke their phone and wipe all and flash new, but thats not what the xda community is about. We are here to share, communicate, support, enhance, develop, and learn.
Understanding the problem would be the first step in to solving it. When we know what is the size of the problem, we would then know how to deal with it appropriately. It might be something simple that can be cleaned easily, no nuke needed.
As for me, I am happy with my 4.1.1 jb. I dont want to flash any new firmware.
By now I have taken several screen shots of it trying to get root access to many files and even it was trying to change values and commands but all were denied ofcourse because I have it blocked in SU. If it would help the devs or anyone else, I can attach the screenshots if need be.

Well, I have some news.
I removed debuggerd from SuperSU authorizations. Later on, I used Chrome and I got all these requests again. This time, I refused (and took screenshots). At the end, Chrome didn't load the webpage. But mostly, I had no internet connection at all!
Then, I remembered that the first time I had the request, it was when using the web browser. And then, I realized it happened the day after I installed Android Adblock Plus.
I uninstalled it, rebooted, and then my connection worked. I'll try to remove debuggerd from the SuperSU blacklist to see if it still happens.
Anyone can correlate?

Hi,
I had the same problems :
- debuggerd.exynosabuse requested SU privileges
- enter in an infinite loop, use a lot of battery power, automatic reboot of the device more than twice a day
So I tried to remove these files. In order to do that you need :
- a rooted device (su installed and working)
- Android Terminal Emulator installed from Googleplay in the device
Launch Android Terminal Emulator
Enter the commands below :
su (accept su privileges, prompt disappears)
mount -o remount,rw /system
cd /system/bin
rm debuggerd
rm debuggerd.exynosabuse
reboot
It works for me. I hope it will work for you.

debuggerd.exynosabuse
From what I can see, the /system/bin/debugger has been replaced with a script that reads:
#!/system/bin/sh
chmod 0400 /dev/exynos-mem
/system/bin/debuggerd.exynosabuse
Then, debuggerd.exynosabuse seems to launch instead of the normal debuggerd. I suppose some applications may call debuggerd by design, which explains why there are some random popups. Here are the "strings" for debuggerd.exynosabuse which appears to be the renamed original (need to verify). This thread then shows that it appears to do the reported actions.. by design? Would be interesting to trace it down a bit more to determine if the carrier/app developer is sending process dumps back to home for analysis which could contain sensitive data.
ELF
p\4
/system/bin/linker
__aeabi_unwind_cpp_pr0
__dso_handle
__INIT_ARRAY__
__FINI_ARRAY__
memset
property_get
atoi
__stack_chk_fail
__stack_chk_guard
__android_log_vprint
open
close
__errno
strcmp
strlen
vsnprintf
__aeabi_unwind_cpp_pr1
snprintf
strcpy
fprintf
__sF
calloc
free
strdup
fputs
strftime
write
strerror
strtoul
_edata
__bss_start
_end
realloc
memmove
read
socket_local_client
socket_local_server
getsockopt
fopen
fgets
fclose
fcntl
poll
accept
usleep
ioctl
dump_tombstone
dump_backtrace_to_file
getpid
__isthreaded
memcmp
sprintf
__libc_init
fchown
chown
stat
mkdir
sigaction
inotify_init
inotify_add_watch
kill
ptrace
opendir
readdir
readdir_r
closedir
fileno
waitpid
bsd_signal
time
system
fflush
localtime_r
unwind_backtrace_ptrace
demangle_symbol_name
get_backtrace_symbols_ptrace
find_symbol_ptrace
free_backtrace_symbols
format_backtrace_line
try_get_word_ptrace
load_ptrace_context
free_ptrace_context
liblog.so
libcutils.so
libc.so
libcorkscrew.so
/proc/%d/cmdline
%F %T
----- pid %d at %s -----
Cmd line: %s
<unknown>
/proc/%d/comm
"%s" sysTid=%d
Could not attach to thread: %s
Could not obtain stack trace for thread.
%s
ptrace detach from %d failed: %s
/proc/%d/task
----- end %d -----
Sending request to dump task %d.
Error dumping backtrace.
Error dumping tombstone.
Tombstone written to: %s
cannot get credentials
timed out reading tid
read failure? %s
invalid crash request of size %d
/proc/%d/task/%d
tid %d does not exist in pid %d. ignoring debug request
/proc/%d/status
Tgid:
Uid:
Gid:
tid %d does not exist. ignoring explicit dump request
ptrace attach failed: %s
debug.db.uid
failed responding to client: %s
ptrace continue failed: %s
dumpstate -k -t -z -d -o /data/log/dumpstate_app_native -m %d
[email protected]%s
process stopped due to unexpected signal %d
********************************************************
* Process %d has been suspended while crashing. To
* attach gdbserver for a gdb connection on port 5039
* and start gdbclient:
* gdbclient app_process :5039 %d
* Wait for gdb to start, then press HOME or VOLUME DOWN key
* to let the process continue crashing.
********************************************************
/sys/class/leds/red/brightness
/sys/class/leds/green/brightness
/sys/class/leds/blue/brightness
/sys/class/leds/red/device/blink
/sys/class/leds/left/cadence
0,0
255
1,0
debuggerd resuming process %d
debuggerd committing suicide to free the zombie!
logd
android:debuggerd
debuggerd: Oct 4 2012 16:24:21
Usage: -b [<tid>]
-b dump backtrace to console, otherwise dump full tombstone file
If tid specified, sends a request to debuggerd to dump that task.
Otherwise, starts the debuggerd server.
out of memory
/dev/input
could not get event, %s
could not get event
SIGILL
SIGABRT
SIGBUS
SIGFPE
SIGSEGV
SIGPIPE
SIGSTKFLT
SIGSTOP
ILL_ILLOPC
ILL_ILLOPN
ILL_ILLADR
ILL_ILLTRP
ILL_PRVOPC
ILL_PRVREG
ILL_COPROC
ILL_BADSTK
BUS_ADRALN
BUS_ADRERR
BUS_OBJERR
FPE_INTDIV
FPE_INTOVF
FPE_FLTDIV
FPE_FLTOVF
FPE_FLTUND
FPE_FLTRES
FPE_FLTINV
FPE_FLTSUB
SEGV_MAPERR
SEGV_ACCERR
UNKNOWN
pid: %d, tid: %d, name: %s >>> %s <<<
pid: %d, tid: %d, name: %s
#%02d %08x %08x %s (%s+%u)
#%02d %08x %08x %s (%s)
%08x %08x %s (%s+%u)
%08x %08x %s (%s)
#%02d %08x %08x %s
%08x %08x %s
backtrace:
%s
stack:
........ ........
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
ro.build.fingerprint
unknown
Build fingerprint: '%s'
cannot get siginfo: %s
signal %d (%s), code %d (%s), fault addr %08x
cannot get siginfo for %d: %s
memory map around fault addr %08x:
%08x-%08x %s
(no map below)
(no map for address)
(no map above)
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
signal %d (%s), code %d (%s), fault addr --------
/data/tombstones
/data/tombstones/tombstone_%02d
failed to open tombstone file '%s': %s
DEBUG
waitpid failed: %s
unexpected waitpid response: n=%d, status=%08x
timed out waiting for tid=%d to die
timed out waiting for tid=%d to stop
%08x
%08lx
%s %s
memory near %.2s:
code around pc:
code around lr:
cannot get registers: %s
r0 %08x r1 %08x r2 %08x r3 %08x
r4 %08x r5 %08x r6 %08x r7 %08x
r8 %08x r9 %08x sl %08x fp %08x
ip %08x sp %08x lr %08x pc %08x cpsr %08x
d%-2d %016llx d%-2d %016llx
scr %08lx
r0r1r2r3r4r5r6r7r8r9slfpipsp
GCC: (GNU) 4.6.x-google 20120106 (prerelease)
GNU
gold 1.10
aeabi
ARM v7
.shstrtab
.interp
.dynsym
.dynstr
.hash
.rel.dyn
.rel.plt
.text
.ARM.extab
.ARM.exidx
.rodata
.preinit_array
.init_array
.fini_array
.ctors
.dynamic
.got
.bss
.comment
.note.gnu.gold-version
.ARM.attributes

be careful 'RM'ing everything
tcharlier said:
Hi,
I had the same problems :
- debuggerd.exynosabuse requested SU privileges
- enter in an infinite loop, use a lot of battery power, automatic reboot of the device more than twice a day
So I tried to remove these files. In order to do that you need :
- a rooted device (su installed and working)
- Android Terminal Emulator installed from Googleplay in the device
Launch Android Terminal Emulator
Enter the commands below :
su (accept su privileges, prompt disappears)
mount -o remount,rw /system
cd /system/bin
rm debuggerd
rm debuggerd.exynosabuse
reboot
It works for me. I hope it will work for you.
Click to expand...
Click to collapse
should you remove 'debuggerd' & 'debuggerd.exynosabuse' they would simply return from the dead.
i believe they are trying to catch and identify a neardeath experience, in this case relating to exynosabuse. this could be the 4.1.2 upgrade and exynosabuse not sitting comfortably together or it may have been intended to work this way - chainfire is the best source for this answer.
debuggerd is called to examine the problem occurrence point on the source code from a crash dump before the main function is carried out. any prog's with dynamic links can automatically connect to debuggerd and generate crash dumps.
i do find it a bit unsettling when root privileges are asked for something that was never installed as an apk and then devours cpu and battery until nothing is left.
more research needs to be done as to what is really going on...
refer to Koba's blog - 'debuggerd of Android'

No more bugging
Got sick and tired of it requesting su privileges all the time. Copied debuggerd and debuggerd.exy to sd card just in case and then deleted the ones in system/bin, that are doing all the damage, via es file explorer with root access coz couldnt be deleted any other way and its been 3 days since and it didnt come back and all is clean on su logs no more requests from it.
By the way its got nothing to do with 4.1.2 sitting with exynosabuse.apk as im still running 4.1.1.
Problem solved...uptill now.

Noob.Saibot said:
Got sick and tired of it requesting su privileges all the time. Copied debuggerd and debuggerd.exy to sd card just in case and then deleted the ones in system/bin, that are doing all the damage, via es file explorer with root access coz couldnt be deleted any other way and its been 3 days since and it didnt come back and all is clean on su logs no more requests from it.
By the way its got nothing to do with 4.1.2 sitting with exynosabuse.apk as im still running 4.1.1.
Problem solved...uptill now.
Click to expand...
Click to collapse
apologies, i should have been clearer, as i too had root privy requests whilst on 4.1.1 - however the frequency of this increased noticeably once upgraded to 4.1.2. also i have no other apk's title being added to the debuggerd name in system/bin. i had only 2 files in system/bin - the 1st was "debuggerd" and the second "debuggerd.exynosabuse". this seems to be saying that something is specific enough about exynosabuse for the separately titled file to appear.
if anyone finds any other files identified in this way please comment.
so in all, i should have said, for me, that the debuggerd bugged me more, via the massive increase in root requests, when sitting with 4.1.2 than it did when i had 4.1.1 installed.
again, anyone with ideas as to what and why this debuggerd saga is taking place would be greatly appreciated.

I'm having the same issue, denying debuggerd.exynosabuse in SuperSU just causes my phone to reboot when the requests come through. This happens multiple times a day.

It is probably a malware.
Update to 4.1.2 asap.
Sent from my GT-N7100 using xda app-developers app

Noob.Saibot said:
Got sick and tired of it requesting su privileges all the time. Copied debuggerd and debuggerd.exy to sd card just in case and then deleted the ones in system/bin, that are doing all the damage, via es file explorer with root access coz couldnt be deleted any other way and its been 3 days since and it didnt come back and all is clean on su logs no more requests from it.
By the way its got nothing to do with 4.1.2 sitting with exynosabuse.apk as im still running 4.1.1.
Problem solved...uptill now.
Click to expand...
Click to collapse
I am getting "debuggered.exynosabuse cannot be deleted" when I try this method
EDIT: didn't have it set to write, got it to work. Will report back in a few days on whether or not it shows up again.
---------- Post added at 02:39 PM ---------- Previous post was at 02:23 PM ----------
UtkarshGupta said:
It is probably a malware.
Update to 4.1.2 asap.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Others in this thread have said that updating doesn't fix the problem, and that it's actually more persistent on 4.1.2
I appreciate offering your assistance, but does anyone know for certain what's going on or are we all just speculating?

[Q] Xperia S. WiFi error. MAC address WiFi unavilable. Help me please

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.

ERROR: HRESULT = 0x8024a110

Can't send update to my Lumia build 10.10.10586.29 i have always
Code:
(IUTool Version: 11:52:10/Feb 7 2014)
Log file: C:\Users\Thierry\AppData\Local\Temp\IUTool-{299338D7-E9AD-4D02-BD74-B341894FDEEF}.etl
[1] Started device 6ea0f2436b51fa6d88d745b2c8dde3d3
[1] Transferring files started
[1] Transferring files complete: 2 files
[1] Update started
[1] Installation failed (HRESULT = 0x8024a110)
[1] Failed (0x8024a110)
ERROR: 0x8024a110
Command failed. (HRESULT = 0x8024a110)

Im trying to deploy old nokia.service_ndtksvc.generic.spkg.cab
0x80188306
E_FILE_COLLISION
More than one package targeted for the same partition contained the same file.

titi66200 said:
Can't send update to my Lumia build 10.10.10586.29 i have always
Code:
(IUTool Version: 11:52:10/Feb 7 2014)
Log file: C:\Users\Thierry\AppData\Local\Temp\IUTool-{299338D7-E9AD-4D02-BD74-B341894FDEEF}.etl
[1] Started device 6ea0f2436b51fa6d88d745b2c8dde3d3
[1] Transferring files started
[1] Transferring files complete: 2 files
[1] Update started
[1] Installation failed (HRESULT = 0x8024a110)
[1] Failed (0x8024a110)
ERROR: 0x8024a110
Command failed. (HRESULT = 0x8024a110)
Click to expand...
Click to collapse
Astoria's dead. Get over 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.