When I installed Cyanogen's latest, one of several times, I decided to run a logcat of what was going on (actually just the debug monitor). I noticed the following line of output:
I am particularly interested in the first and last errors
Code:
08-09 09:21:28.684: INFO//system/bin/dosfsck(1352): 63 sectors/track, 255 heads
08-09 09:21:28.684: INFO//system/bin/dosfsck(1352): 64260 hidden sectors
08-09 09:21:28.684: INFO//system/bin/dosfsck(1352): 867510 sectors total
[B][COLOR=Red]08-09 09:21:28.704: ERROR/flash_image(1361): error opening /data/recovery.img: No such file or directory[/COLOR][/B]
08-09 09:21:28.964: DEBUG/AKMD(1363): akmd 1.6.4 START
08-09 09:21:28.964: DEBUG/AKMD(1363): library version: 1.2.1.1129
[COLOR=Red]08-09 09:21:29.144: ERROR/vold(1352): Unable to read framework command (Bad file number)
08-09 09:21:29.144: ERROR/vold(1352): Error processing framework command (Bad file number)
08-09 09:21:29.144: ERROR/vold(1352): Unable to read framework command (Bad file number)[/COLOR]
[COLOR=Red]08-09 09:21:29.144: ERROR/vold(1352): Error processing framework command (Bad file number)
08-09 09:21:29.154: ERROR/vold(1352): Unable to read framework command (Bad file number)
08-09 09:21:29.154: ERROR/vold(1352): Error processing framework command (Bad file number)
08-09 09:21:29.756: ERROR/vold(1352): Unable to read framework command (Bad file number)
08-09 09:21:29.756: ERROR/vold(1352): Error processing framework command (Bad file number)[/COLOR]
[I][COLOR=Red][B]08-09 09:21:30.174: ERROR/RIL Acoustic(1354): Fail to open /system/etc/AudioPara_ALL.csv -1.[/B][/COLOR][/I]
08-09 09:21:30.184: INFO/RIL Acoustic(1354): open /system/etc/AudioPara4.csv success.
08-09 09:21:30.224: INFO/RIL Acoustic(1354): acoustic table version: Dream_TMU_20090305
08-09 09:21:30.304: INFO/RIL Acoustic(1354): read_audio_para_from_file success.
Why am I getting all these errors at boot. Is this normal?
Or is this a problem. Phone runs well enough
try sending a pm to cyanogen
Thanks..but I don't want Cyanogen to think I'm using him for a personal tech support. This appears to be a problem of my making...The last error has to do with the Meltus Louder hack.....I think (those are the names of the files that the audio hack pushes).
Anyway, I was just hoping a member who is knowledgeable about this could pipe in....
Related
passing strings to a sbl i got some interesting text:
Code:
-----------------------------------------------------------
Samsung Secondary Bootloader (SBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Board Name: %s %s
ARIES
REV 03
Build On: %s %s
Jul 30 2010
09:53:23
boot_kernel
loadkernel
boot
command_loop
SBL>
%s: parse command error! (%s)
Autoboot (%d seconds) in progress, press any key to stop
Autoboot aborted..
__Re_partition
%s: undefined code for format.
%s: write virtual pit image.
%s: write bootloader images to NAND!
%s: format failed..
Re_partition
%s: magic code(0x%x)
loke_init
%s: file system init failed..
%s: j4fs_open success..
%s: j4fs_open failed..
%s: bye~ bye!
main
%s: booting stop.
%s: booting stop and power off..
I9000XXIL
console=ttySAC2,115200
/mnt/rsv
setting param.serialnr=0x%08x 0x%08x
setting param.board_rev=0x%x
bootmode=2
bootmode=3
setting param.cmdline=%s
argv[%d] : %s
value : %d
Invalide Parameter Name
setenv
valid magic and version 2 ...
invalid magic and version 2 ...
saveenv
save %s, size: %d
param.blk
save %s successfully.
PARAM Rev %d.%d
%s : %d
%s : %s
printenv
load_lfs_parameters
%s valid magic code and version.
load_lfs_parameters invalid magic code and version
boot parameter file does not exist ..
make new boot paremeter file ..
/mnt/rsv
load_debug_level
debug_level.inf
%s reading debug level from file successfully(0x%x).
debug level file does not exist ..
debug level value is incorrect!! Set default level (LOW)..
get_debug_level
%s current debug level is 0x%x.
There're no available commands.
* Help : %s
* Usage : %s
There's no command
Following commands are supported:
* %s
To get commands help, Type "help <command>"
help
Rebooting...
reset
Code:
open
close
erasepart
eraseall
loadkernel
showpart
bbm add partition start
addpart
delpart
savepart
fsr_bml open error
error return value %x
bbm_erase_all
some of them even look like commands, anyone knows if there is some use for this?
in boot.bin:
Code:
-----------------------------------------------------------
Samsung Primitive Bootloader (PBL) v3.0
Copyright (C) Samsung Electronics Co., Ltd. 2006-2010
Error Occurs During Boot. Please ReBoot.
FSR_BML_Init Error
BML_Open Error
BML_GetVolInfo Error
BML_LoadPIEntry Error! Part_ID: %d
+n1stVPN %d
+nPgsPerBlk %d
BML_Read Error
ERROR.. Bootable SBL doesn't exist ..
PBL found bootable SBL: Partition(%d).
The input address don't need a virtual-to-physical translation : %08lx
""DD
UPCH
LPCH
LPCH
UPCH
[B]e-fused[/B]
i wonder what e-fused is for, and if its related to e-fuse: http://en.wikipedia.org/wiki/EFUSE
How did you got this? UART, jtag?
that's a dump of the PBL and SBL from memory into a file, then the Linux "strings" command was run on the file.
I've used search for UPCH and found this thread.
1.
Any idea what UPCH means?
2.
I can't see Thanx button for luismanson...
Maybe my Browser...
Thanx in advance.
Best Regards
Please.
Any news about UPCH?
I need this for JTAG... maybe.
But I don't know what it is...
http://www.ort-jtag.com/blog/?e=10
For instance it is visible in this Video...
But I have an RIFF Box... not ORT... or Medusa seems also to "repair" UPCH...
It seems Bootloader related...
Thanx in advance.
Best Regards
Hi all !
Here's my guide to read logcat. The post will be updated regularly when needed.
1.) How to logcat
Assuming you already have adb :
Code:
adb logcat
To logcat and save logcat to a file :
Code:
adb logcat>file_name.txt
2.) How to read it ?
Reading logcat is easy, easier than creating a flashable stock ROM. On logcat, you'll encounter following messages :
I/ : Information about what process is doing.
W/ : Warning, mostly displays something wrong, but not as fatal as E/ .
D/ : Debugging, same as I/ but can be crucial or fatal.
E/ : Error, crucial system error. Can be a cause of a problem.
V/ : Verbose-able / output. Mostly common message like I/ or D/ .
Example of the messages :
Code:
I/dalvikvm : Means dalvik-vm is showing an information
W/vold : Means on vold process, something is wrong.
D/dalvikvm : Means dalvik-vm is doing a debug-able actions.
E/dalvikvm : Means a fatal dalvik-vm or dalvik-vm crashed.
V/java : Java is doing something
While reading logcat, you must use your common sense. I/ sometimes can be a fatal error, so you must read it carefully.
3.) Fatal system errors
Another advantages of logcat if you're a ROM themer / porter is you can read where's system error is located.
The most common system errors are :
Code:
E/dalvikvm : The common cause of a bootloop
E/JNIHelp : Another common cause of bootloop
F/libc : Mostly SIGSEGV error, cause bootloop
Examples of errors :
Code:
E/dalvikvm( 908): ERROR: couldn't find native method : Means dalvikvm couldn't find correct method for following actions.
E/JNIHelp ( 908): RegisterNatives failed for 'android/net/wifi/WifiNative', aborting : Means JNIHelp can't register native method
F/libc ( 908): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 908 (zygote) : Caused by E/JNIHelp
Guide will be updated soon when I find something interesting.
Great thread bro,here so many peeps they need to understand it,thumps up.
GREEEETZ FROM TEAM-OPTIMA!!!
This is the message I get when running tpdebrick.. The process works with my other tablets so i think the process and cabling are good? Is there anything that can be done?
[email protected]:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
Connect Touchpad then hold Power+Home+VolumeDown for 30 seconds ...
QDL mode not found
Aborting.
another one with different issues/fixable either?
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
MSG: Open multi failed, unknown error
ERROR: Open multi failed, unknown error
Invalid openMulti response.
Cannot write file tz.mbn
Aborted.
Hello,
I could not find an answer on how to preload the expected libaries so I hope anyone can help me here.
I am a complete noob In devloping with Android Studio.
I tried to write a small app and ran it with the following errors while loading th e AVD (Android 5.1 , WVGA):
Code:
Cannot launch AVD in emulator.
Output:
libGL error: unable to load driver: i915_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i915
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request: GLXBadContext
Major opcode of failed request: 155 (GLX)
Minor opcode of failed request: 6 (X_GLXIsDirect)
Serial number of failed request: 49
Current serial number in output stream: 48
emulator: ERROR: virtual device name contains invalid characters
emulator: could not find virtual device named '3.2_QVGA_(ADP2)_API_22'
I think to get this solved will not be quiet diffcult for advanced users.
Thank you verry much for your help! :good:
Some infos that might help you:
OS: Kubuntu 16.04
Android Studio 2.2.3
used coding language: Java
Hello,
I'm currently trying to run apktool using dalvikvm in the customize.sh script:
Bash:
apktool_d() {
#ANDROID_DATA=$TMPDIR_JCD ANDROID_ROOT=/system LD_LIBRARY_PATH=/system/lib dalvikvm -Xbootclasspath:/system/framework/core.jar:/system/framework/conscrypt.jar:/system/framework/apache-xml.jar -classpath $BIN/apktool_*-dexed.jar brut.apktool.Main d --frame-path $TMPDIR_JCD/framework --no-src -o $TMPDIR_JCD/resout $1
dalvikvm -classpath $BIN/apktool_*-dexed.jar brut.apktool.Main d --no-src -o $TMPDIR_JCD/resout $1
test $? != 0 && abort "Decoding APK resources failed. Aborting..."
}
I've tried to port that code from an outdated template: https://github.com/djb77/magisk-module-template-apkpatcher
When using the commented out method the command aborts with "Decoding APK resources failed" and logcat *:E is telling me the following:
Code:
04-17 21:11:53.649 11641 11641 E dalvikvm: Could not create image space with image file '/system/framework/boot.art'. Attempting to fall back to imageless running. Error was: Unexpected component count in /system/framework/arm/boot.art, received 11, expected non-zero and <= 3
04-17 21:11:53.677 11641 11641 E dalvikvm: Could not initialize without image: Boot classpath is empty.
When trying the second approach without -Xbootclasspath and so on I'm getting a NullPointerException directly in the magisk log (saved file):
Code:
I: Using Apktool 2.3.4 on Bluetooth.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
Exception in thread "main" java.lang.ExceptionInInitializerError
at brut.util.OSDetection.isMacOSX(OSDetection.java:28)
at brut.androlib.res.AndrolibResources.getFrameworkDir(AndrolibResources.java:913)
at brut.androlib.res.AndrolibResources.getFrameworkApk(AndrolibResources.java:754)
at brut.androlib.res.AndrolibResources.loadFrameworkPkg(AndrolibResources.java:116)
at brut.androlib.res.data.ResTable.getPackage(ResTable.java:84)
at brut.androlib.res.data.ResTable.getResSpec(ResTable.java:67)
at brut.androlib.res.data.ResTable.getResSpec(ResTable.java:63)
at brut.androlib.res.decoder.ResAttrDecoder.decode(ResAttrDecoder.java:39)
at brut.androlib.res.decoder.AXmlResourceParser.getAttributeValue(AXmlResourceParser.java:385)
at org.xmlpull.v1.wrapper.classic.XmlPullParserDelegate.getAttributeValue(XmlPullParserDelegate.java:69)
at brut.androlib.res.decoder.XmlPullStreamDecoder$1.parseManifest(XmlPullStreamDecoder.java:97)
at brut.androlib.res.decoder.XmlPullStreamDecoder$1.event(XmlPullStreamDecoder.java:65)
at brut.androlib.res.decoder.XmlPullStreamDecoder.decode(XmlPullStreamDecoder.java:141)
at brut.androlib.res.decoder.XmlPullStreamDecoder.decodeManifest(XmlPullStreamDecoder.java:153)
at brut.androlib.res.decoder.ResFileDecoder.decodeManifest(ResFileDecoder.java:155)
at brut.androlib.res.AndrolibResources.decodeManifestWithResources(AndrolibResources.java:204)
at brut.androlib.Androlib.decodeManifestWithResources(Androlib.java:136)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:122)
at brut.apktool.Main.cmdDecode(Main.java:164)
at brut.apktool.Main.main(Main.java:73)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.String.toLowerCase()' on a null object reference
at brut.util.OSDetection.<clinit>(OSDetection.java:21)
... 20 more
Decoding APK resources failed. Aborting...
! Installation failed
After some research I tried to find out if the customize.sh is running as root because some posts telling that setting LD_LIBRARY_PATH setting as root fixed those "Could not create image space" dalvikvm errors but can't find any info about that. see https://github.com/termux/termux-packages/issues/900#issuecomment-322207233
I'm out of ideas and happy for any help.
Thanks in advance
Danny.