As I don't seem to have permissions to post in the developers' forum.. here goes:
When installing the OTA patch for MIUI 1.9.23 to 1.9.30 on my Desire, a reboot ended being stuck in the Recovery.
logcat showed me the following:
D/AndroidRuntime( 1503):
D/AndroidRuntime( 1503): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime( 1503): CheckJNI is OFF
D/dalvikvm( 1503): creating instr width table
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/core.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/core.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/bouncycastle.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/bouncycastle.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/ext.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/ext.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/framework.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/framework.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/android.policy.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/android.policy.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/services.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/services.jar'
E/dalvikvm( 1503): Can't open dex cache '/data/dalvik-cache/[email protected]@[email protected]': No such file or directory
I/dalvikvm( 1503): Unable to open or create cache for /system/framework/core-junit.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1503): Unable to process classpath element '/system/framework/core-junit.jar'
E/dalvikvm( 1503): No valid entries found in bootclasspath '/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/core-junit.jar'
W/dalvikvm( 1503): JNI_CreateJavaVM failed
E/AndroidRuntime( 1503): JNI_CreateJavaVM failed
These errors returned in a loop.
Looking on the system itself, /data/dalvik-cache seemed to be missing.
After creating this directory, the phone continued booting.
So this would be a quick-fix.
Yet I didn't take into account the necessary symbol links for the a2sd to work properly yet.
Can someone point me to some docs which symbol links I should apply?
Thx for your help.
According to the logcat, your dalvik-cache is missing. Wipe dalvik cache from recovery.
If that won't help, create the following directory and then wipe:
/data/dalvik-cache
If still does not work, check THIS thread.
Hi davebugyi
Thanks for your answer.
That's what I did, and it fixed the problem.
I wanted to write that in the original thread, but I didn't have enough interaction on this forum (10 posts) to allow me to write there directly.
Cheers!
Guys, please, help me to find a solution. Very big bug, software or hardware, I don't know!
My HOX after a some time of normal working starts force closing almost all apps.
It happens independently of which apps i run or use.
As I can observe it doesn't depend on a state of radio module or wi-fi or data connection or usb plugging. It can happen at any time and in any case.
Apps that getting crashed are as system as custom but mostly are system apps. The full list of crashing apps you can see below in a logcat with filter "crash".
I tried to solve it myself by doing all possible steps: factory reset, manually formatting all partitions in recovery, formatting SD-card via PC and a device, re-locking bootloader and flashing different custom and stock ROMs, using a phone clean without any custom apps, or disabling radio and data connection. No result.
Now I recorded two logcats, one is when a phone was still normally working, and a second when a phone became force stopping apps.
I am not an advanced user of android OS so hardly i can read a log correctly.
So I need someone who knows how to analyze an information in the logs and find a reason of troubles. I will be very thankful.
One thought when reading logs:
When its OK there is no error messages like "Read-only file system", when it gets bad there are a lot of such warnings. Apps and services cannot operate with /data/ partition because of read-only. What can be a reason that the /data partition gets read-only?
May be this is a clue?
I don't want to believe that this is a hardware problem.
Do you have a custom recovery? If yes, try doing a "Fix Permissions" from the Recovery. I am a noob too, so cant really interpret your logcat. But have read somewhere, that "Fix Permissions" in Clockworkmod Touch Recovery can help solve such FC issues.
If nothing else works, I personally would install RUU (be careful and follow proper instructions) and see if that resolves the issue. If that doesn't send the phone back to HTC.
a.james said:
Do you have a custom recovery? If yes, try doing a "Fix Permissions" from the Recovery. I am a noob too, so cant really interpret your logcat. But have read somewhere, that "Fix Permissions" in Clockworkmod Touch Recovery can help solve such FC issues.
If nothing else works, I personally would install RUU (be careful and follow proper instructions) and see if that resolves the issue. If that doesn't send the phone back to HTC.
Click to expand...
Click to collapse
Fixing permissions doesn't help.
I did install RUU twice on a fully clean device but no trouble had gone away.
Sending back to HTC may be difficult - the phone was unlocked and now is re-locked.
ninelo said:
Fixing permissions doesn't help.
I did install RUU twice on a fully clean device but no trouble had gone away.
Sending back to HTC may be difficult - the phone was unlocked and now is re-locked.
Click to expand...
Click to collapse
That should not be an issue. Relocked with RUU, is basically is same as Stock. As if you unlocked ur phone, and re-locked it without actually doing anything. So, warranty should cover it, if its a Manufacturing Defect. Unfortunately thats all I can think of, unless some senior devs have a look at the logcat and identify the exact issue.
Sorry couldnt be of much help...
a.james said:
unless some senior devs have a look at the logcat and identify the exact issue.
Click to expand...
Click to collapse
Thanks thats what I hope on.
ninelo said:
Thanks thats what I hope on.
Click to expand...
Click to collapse
Try "fastboot erase cache" from your Pc. You will need fastboot files. Look under development section
Sent from my HTC One X using xda premium
eyosen said:
Try "fastboot erase cache" from your Pc. You will need fastboot files. Look under development section
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Did it. It only helps to solve booting into recovery issues. Its not my case.
After some time of testing I came to conclusion that the reason was the error "EROFS (Read-only file system)".
A few examples:
Code:
Line 69: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 87: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 171: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop272.tmp: open failed: EROFS (Read-only file system)
Line 187: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 279: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 297: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 311: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 329: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 347: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop270.tmp: open failed: EROFS (Read-only file system)
Line 361: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 395: W/BatteryStats( 358): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp: open failed: EROFS (Read-only file system)
Line 407: W/BatteryStats( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 443: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 461: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 485: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop278.tmp: open failed: EROFS (Read-only file system)
Line 499: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2201: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2219: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2233: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2251: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2413: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop285.tmp: open failed: EROFS (Read-only file system)
Line 2429: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2527: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2545: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 2559: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 2577: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 3039: E/libEGL ( 9262): error creating cache file /data/data/com.htc.Weather/cache/com.android.opengl.shaders_cache: Read-only file system (30)
Line 3195: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 3213: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 3231: W/SqliteDatabaseCpp( 9327): getJournalMode: errno = 30, error message = Read-only file system
Line 3235: E/SqliteDatabaseCpp( 9327): native_setLocale: errno = 30, error message = Read-only file system
Line 3545: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 3563: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 3595: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 3613: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 4039: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 4057: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 4087: W/ActivityManager( 358): java.io.FileNotFoundException: /data/anr/traces.txt: open failed: EROFS (Read-only file system)
Line 4105: W/ActivityManager( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 5189: E/DropBoxManagerService( 358): java.io.FileNotFoundException: /data/system/dropbox/drop179.tmp: open failed: EROFS (Read-only file system)
Line 5205: E/DropBoxManagerService( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 5729: W/BatteryStats( 358): java.io.FileNotFoundException: /data/system/batterystats.bin.tmp: open failed: EROFS (Read-only file system)
Line 5741: W/BatteryStats( 358): Caused by: libcore.io.ErrnoException: open failed: EROFS (Read-only file system)
Line 7275: W/SqliteDatabaseCpp( 9677): getJournalMode: errno = 30, error message = Read-only file system
Line 7279: E/SqliteDatabaseCpp( 9677): native_setLocale: errno = 30, error message = Read-only file system
It remains to find a solution...
have same problem
in recovery dmesg
dmesg
0
<6>[ 3.891118] mmc0: clock 52000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 3 timing 1 ddr 0
<6>[ 3.892378] mmc0: clock 52000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 3 timing 5 ddr 0
<6>[ 3.892488] mmc0: clock 52000000Hz busmode 2 powermode 2 cs 0 Vdd 7 width 3 timing 5 ddr 0
<6>[ 3.892691] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.893476] mmcblk0: mmc0:0001 K2U00M 29.1 GiB
<4>[ 3.895943] Primary GPT is invalid, using alternate GPT.
I seem to be having the same problem, as outlined in a previous post i made.
I'd love to help and provide more logs but i don't know where to get the logs from.
Also at the moment my phone is stuck on bootloop so i'll need to get that taken care of before anything else. Bootloop happens if my battery is low (<14%) and i reboot the phone or shut it off and back on...
I am also in the process of restoring to stock to see if that helps.
Thank you
smiro2000 said:
I'd love to help and provide more logs but i don't know where to get the logs from.
Click to expand...
Click to collapse
Boot your phone normally, connect to PC, check ADB debugging, run "cmd" on your PC, go to the folder where you have ADB drivers and run:
Code:
adb logcat *:W > C:\logcat.txt
Then look into the logcat.txt and search errors like "EROFS (Read-only file system)"
Had the same errors ... weird fix
Hi,
I had the same errors and found your post.
I tried everything too, installed stock RUU, reflashed, remounted and the errors kept rolling in. All kinds of apps crashed because of the read only filesystem.
But usually when having an error that is illogical, I tend to try **** that is illogical too ... I remembered that my phone fell a couple of weeks ago, cracking the glass (yeah that sucked bigtime!) and the errors started a couple of weeks after that ...
so first I thought it was a hardware thing like memory that was damaged, but since it took a couple of weeks for the errors came I discarded that idea and finally I got the 'dumb' idea to pop out my simcard and re-inserting it ....
and I haven't had a similar error since !!!!
I know it seems weird but maybe Android locks the partitions in case of a sim error or a security risk concerning the sim-card
hope it helps
Hey guys take a look at this post, maybe can help with pur problem http://forum.xda-developers.com/showthread.php?t=895628
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?
Right, so I've been an absolute idiot and I uninstalled mediatek-res.apk. I was probably very tired and I was stupid enough to forget to make a backup in recovery. The phone is a Chinese clone (Jiake JK3) and I can't find any stock firmware on the internet. It's now stuck in bootloop, so somehow I need to restore mediatek-res.apk so I can boot it up. I can get adb access with root when I'm in recovery. I've tried pushing it to /system/framework with the correct permissions, but that hasn't worked. The log (when I boot up) says:
Code:
D/PackageManager( 1699): scan package: /system/framework/mediatek-res.apk , start at: 66650ms.
D/asset ( 1699): AssetManager-->addDefaultAssets CIP path not exsit!
and
Code:
I/PackageManager( 1699): /system/framework/mediatek-res.apk changed; collecting certs
D/dalvikvm( 1699): GC_CONCURRENT freed 1976K (15855), 34% free 4069K/6124K, paused 1ms+2ms, total 19ms
and
Code:
E/PackageManager( 1699): Package com.mediatek has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 1699): Signature mismatch for shared user : SharedUserSetting{41de1470 android.uid.system/1000}
I have no idea what any of this means but I'm a fairly capable user so if someone could let me know what it means that'd be great.
mediatek-res.apk problem [FIXED]
rowan.allen.rules said:
Dude this is the easiest problm to fix
The path you have entered is incorrect
you enter:::: /system/framework/mediatek-res.apk
Should enter::::
PHP:
/system/framework/mediatek-res/mediatek-res.apk
This is because there is a folder mediatek-res and inside it there should be mediatek-res.apk:good:
Try this and if you could fix this error then leave a THANkS:victory:
Click to expand...
Click to collapse
I'm running stock 6.0 on a UsU'd LG G4 vs986 that is rooted with Magisk. In trying to install the onX Hunt app and it claims to have been installed but when opening, it immediatly force closes. I ran adb bugreport while installing the app and the bug report shows
Code:
01-01 20:47:55.592 13367 13367 W System : ClassLoader referenced unknown path: /system/priv-app/GooglePackageInstaller/lib/arm64
01-01 20:47:55.594 13367 13367 D FingerprintProtector: This is not product version.
01-01 20:47:55.623 13367 13367 W : Unable to open '/data/app/onxmaps.hunt-1/split_config.armeabi_v7a.apk': Permission denied
01-01 20:47:55.623 13367 13367 W zipro : Error opening archive /data/app/onxmaps.hunt-1/split_config.armeabi_v7a.apk: I/O Error
01-01 20:47:55.623 13367 13367 D asset : failed to open Zip archive '/data/app/onxmaps.hunt-1/split_config.armeabi_v7a.apk'
01-01 20:47:55.623 13367 13367 W PackageManager: Failure retrieving resources for onxmaps.hunt
01-01 20:47:55.671 13086 13097 I DefContainer-JNI: error opening: /data/media/0/Android/data/onxmaps.hunt/cache: Permission denied
Looking at a backup from the same device from before having done a wipe of data, cache, system, dalvik and internal storage and doing a fastboot flash of 6.0 stock, I find that there are files missing from /data/app/onmaps.hunt-1/ which is the cause of the app force closing. I tried copying the files over from the backup but it still fails to make the app work. I also tried changing ownership of those files but not sure if they should be system.install or system.system or something else.
I've also tried installing the apk using adb install onxhunt.apk and get the same results.
I found the problem. It turns out that the onxhut apk was incomplete as it was just the base.apk which was only 13 MB and when I installed gplaycli to download the app, I found it was 84 MB. I had initially used Ad Apk Extractor to get the onXhunt apk from another phone that had installed it directly from the Play store.
Does anyone know of an app that would properly back up apks for apps such as onXhunt?