Related
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?
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.
I need some help,
I am trying to install CM11 on my Galaxy Tab Pro. I have a macbook pro running yosemite and I cannot get heimdall to work. I followed the guide on the CM's wiki page and I get this error message: (See bold at bottom of screenshot)
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send data!Releasing device interface...
after sending the command through to push a new recovery. On CM's wiki page it says that if you encounter the error message you have to enter in these commands to disable the default usb drivers:
"On Mac OS X you may see this message: "ERROR: Claiming interface failed!". If so, you need to disable the default USB drivers with the following commands:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;-"
But when I enter these commands into Terminal it just comes up with this error message for all three of them:
(kernel) Kext com.apple.driver.AppleUSBCDCACMData not found for unload request.
Failed to unload com.apple.driver.AppleUSBCDCACMData - (libkern/kext) not found.
Does anyone have any insight as to why this isn't working for me. Would really like to get CM up and running on tabpro but with option currently not working and there being no other solution that works on mac's, Im kind of SOL right now. Any help would be greatly appreciated
-Thanks
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.
Locked me out of STDin on adb and and tty and changed my libfs64.so to another destination. So I'm running out of options.
adb pair 192.168.0.1:5037
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /data/user/0/com.github.standardadb/cache/adb.10600.log
Server had pid: 24563
--- adb starting (pid 24563) ---
adb I 04-07 11:00:57 24563 24563 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 04-07 11:00:57 24563 24563 main.cpp:63] Version 31.0.3p1-android-tools
adb I 04-07 11:00:57 24563 24563 main.cpp:63] Installed as /data/app/~~x9Yjf_NXboB57BGltSn3LQ==/com.github.standardadb-5k6iLgDWIncOskTOBYobtQ==/lib/arm64/libfs64.so
adb I 04-07 11:00:57 24563 24563 main.cpp:63]
adb F 04-07 11:00:57 24549 24549 main.cpp:155] could not install *smartsocket* listener: Address already in use
adb F 04-07 11:00:57 24561 24561 main.cpp:155] could not install *smartsocket* listener: Address already in use
adb F 04-07 11:00:57 24563 24563 main.cpp:155] could not install *smartsocket* listener: Address already in use
* failed to start daemon
error: cannot connect to daemon
Enter pairing code:
adb
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /data/user/0/com.github.standardadb/cache/adb.10600.log
Server had pid: 24734
--- adb starting (pid 24734) ---
adb I 04-07 11:01:00 24734 24734 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 04-07 11:01:00 24734 24734 main.cpp:63] Version 31.0.3p1-android-tools
adb I 04-07 11:01:00 24734 24734 main.cpp:63] Installed as /data/app/~~x9Yjf_NXboB57BGltSn3LQ==/com.github.standardadb-5k6iLgDWIncOskTOBYobtQ==/lib/arm64/libfs64.so
adb I 04-07 11:01:00 24734 24734 main.cpp:63]
adb F 04-07 11:01:00 24734 24734 main.cpp:155] could not install *smartsocket* listener: Address already in use
* failed to start daemon
error: cannot connect to daemon
adb
Android Debug Bridge version 1.0.41
Version 31.0.3p1-android-tools
Installed as /data/app/~~x9Yjf_NXboB57BGltSn3LQ==/com.github.standardadb-5k6iLgDWIncOskTOBYobtQ==/lib/arm64/libfs64.so
global options:
-a listen on all network interfaces, not just localhost
-d use USB device (error if multiple devices connected)
-e use TCP/IP device (error if multiple TCP/IP devices available)
-s SERIAL use device with given serial (overrides $ANDROID_SERIAL)
-t ID use device with given transport id
-H name of adb server host [default=localhost]
-P port of adb server [default=5037]
-L SOCKET listen on given socket for adb server [default=tcp:localhost:5037]
general commands:
devices [-l] list connected devices (-l for long output)
help show this help message
version show version num
networking:
connect HOST[ORT] connect to a device via TCP/IP [default port=5555]
disconnect [HOST[ORT]]
disconnect from given TCP/IP device [default port=5555], or all
pair HOST[ORT] [PAIRING CODE]
pair with a device for secure TCP/IP communication
forward --list list all forward socket connections
forward [--no-rebind] LOCAL REMOTE
forward socket connection using:
tcp:<port> (<local> may be "tcp:0" to pick any open port)
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
vsock:<CID>:<port> (remote only)
acceptfd:<fd> (listen only)
forward --remove LOCAL remove specific forward socket connection
forward --remove-all remove all forward socket connections
ppp TTY [PARAMETER...] run PPP over USB
reverse --list list all reverse socket connections from device
reverse [--no-rebind] REMOTE LOCAL
reverse socket connection using:
tcp:<port> (<remote> may be "tcp:0" to pick any open port)
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
reverse --remove REMOTE remove specific reverse socket connection
reverse --remove-all remove all reverse socket connections from device
mdns check check if mdns discovery is available
mdns services list all discovered services
file transfer:
push [--sync] [-z ALGORITHM] [-Z] LOCAL... REMOTE
copy local files/directories to device
--sync: only push files that are newer on the host than the device
-n: dry run: push files to device without storing to the filesystem
-z: enable compression with a specified algorithm (any, none, brotli)
-Z: disable compression
pull [-a] [-z ALGORITHM] [-Z] REMOTE... LOCAL
copy files/dirs from device
-a: preserve file timestamp and mode
-z: enable compression with a specified algorithm (any, none, brotli)
-Z: disable compression
sync [-l] [-z ALGORITHM] [-Z] [all|data|odm|oem|product|system|system_ext|vendor]
sync a local build from $ANDROID_PRODUCT_OUT to the device (default all)
-n: dry run: push files to device without storing to the filesystem
-l: list files that would be copied, but don't copy them
-z: enable compression with a specified algorithm (any, none, brotli)
-Z: disable compression
shell:
shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...]
run remote shell command (interactive shell if no command given)
-e: choose escape character, or "none"; default '~'
-n: don't read from stdin
-T: disable pty allocation
-t: allocate a pty if on a tty (-tt: force pty allocation)
-x: disable remote exit codes and stdout/stderr separation
emu COMMAND run emulator console command
app installation (see also `adb shell cmd package help`):
install [-lrtsdg] [--instant] PACKAGE
push a single package to the device and install it
install-multiple [-lrtsdpg] [--instant] PACKAGE...
push multiple APKs to the device for a single package and install them
install-multi-package [-lrtsdpg] [--instant] PACKAGE...
push one or more packages to the device and install them atomically
-r: replace existing application
-t: allow test packages
-d: allow version code downgrade (debuggable packages only)
-p: partial application install (install-multiple only)
-g: grant all runtime permissions
--abi ABI: override platform's default ABI
--instant: cause the app to be installed as an ephemeral install app
--no-streaming: always push APK to device and invoke Package Manager as separate steps
--streaming: force streaming APK directly into Package Manager
--fastdeploy: use fast deploy
--no-fastdeploy: prevent use of fast deploy
--force-agent: force update of deployment agent when using fast deploy
--date-check-agent: update deployment agent when local version is newer and using fast deploy
--version-check-agent: update deployment agent when local version has different version code and using fast deploy
--local-agent: locate agent files from local source build (instead of SDK location)
(See also `adb shell pm help` for more options.)
uninstall [-k] PACKAGE
remove this app package from the device
'-k': keep the data and cache directories
debugging:
bugreport [PATH]
write bugreport to given PATH [default=bugreport.zip];
if PATH is a directory, the bug report is saved in that directory.
devices that don't support zipped bug reports output to stdout.
jdwp list pids of processes hosting a JDWP transport
logcat show device log (logcat --help for more)
security:
disable-verity disable dm-verity checking on userdebug builds
enable-verity re-enable dm-verity checking on userdebug builds
keygen FILE
generate adb public/private key; private key stored in FILE,
scripting:
wait-for[-TRANSPORT]-STATE...
wait for device to be in a given state
STATE: device, recovery, rescue, sideload, bootloader, or disconnect
TRANSPORT: usb, local, or any [default=any]
get-state print offline | bootloader | device
get-serialno print <serial-number>
get-devpath print <device-path>
remount [-R]
remount partitions read-write. if a reboot is required, -R will
will automatically reboot the device.
reboot [bootloader|recovery|sideload|sideload-auto-reboot]
reboot the device; defaults to booting system image but
supports bootloader and recovery too. sideload reboots
into recovery and automatically starts sideload mode,
sideload-auto-reboot is the same but reboots after sideloading.
sideload OTAPACKAGE sideload the given full OTA package
root restart adbd with root permissions
unroot restart adbd without root permissions
usb restart adbd listening on USB
tcpip PORT restart adbd listening on TCP on PORT
internal debugging:
start-server ensure that there is a server running
kill-server kill the server if it is running
reconnect kick connection from host side to force reconnect
reconnect device kick connection from device side to force reconnect
reconnect offline reset offline/unauthorized devices to force reconnect
usb:
attach attach a detached USB device
detach detach from a USB device to allow use by other processes
environment variables:
$ADB_TRACE
comma-separated list of debug info to log:
all,adb,sockets,packets,rwx,usb,sync,sysdeps,transport,jdwp
$ADB_VENDOR_KEYS colon-separated list of keys (files or directories)
$ANDROID_SERIAL serial number to connect to (see -s)
$ANDROID_LOG_TAGS tags to be used by logcat (see logcat --help)
$ADB_LOCAL_TRANSPORT_MAX_PORT max emulator scan port (default 5585, 16 emus)
$ADB_MDNS_AUTO_CONNECT comma-separated list of mdns services to allow auto-connect (default adb-tls-conne
t0inK said:
Locked me out of STDin on adb and and tty and changed my libfs64.so to another destination. So I'm running out of options.
Click to expand...
Click to collapse
@t0inK Thread closed as duplicate of
Adb wont work. Lib64 moved. Wont read from stdin. Manifest overwrite, rewrite hack.
Here are the most important parts. Literally every command has been changed to lock me out from making ANY move possible to break free of this hacker . He's checked every back door. "reboot the device; defaults to booting system image but...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator