Hi all,
First-time poster and fairly new to rooting...
I have a Samsung Galaxy SII (GT-I9100, originally LBP firmware on Orange UK) which I successfully managed to flash with Odin/Heimdall to give:
CF-Root
CyanogenMod 9 RC1
Siyah 3.3.2
I then thought I'd give Boot2Gecko a try so I followed gokhanmoral's post and managed to get a page not found screen booting to the second rom.
So I checked out the B2G source code and performed a
make install-gaia
Click to expand...
Click to collapse
ensuring
adb devices
Click to expand...
Click to collapse
found my phone connected over usb - This gave me a lock screen which wouldn't respond to touch events.
After quite a bit of reading I then decided to attempt pusler new 6th July Build performing:
simg2img userdata.img data.img
heimdall detect
heimdall flash --hidden system.img
(cleared 2ndROM data and cache through CWM)
adb push data.img /sdcard/.secondrom/data.img
Click to expand...
Click to collapse
However, when I booted to the 2ndROM I gott a black screen - I tried looking through the
adb shell logcat
Click to expand...
Click to collapse
output and saw several errors similar to:
I/GeckoDump( 9894): Opened socket on 9999
E/GeckoConsole( 9894): [JavaScript Error: "NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" {file: "chrome://browser/content/shell.js" line: 80}]
I/Gecko ( 9894): Logging GL tracing output to /system/b2g/firefox.trace
I/Gecko ( 9894): Attempting load of /data/local/egltrace.so
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000068 (code=1)
I/Gecko ( 9894): Attempting load of libEGL.so
D/libEGL ( 9894): egl.cfg not found, using default config
D/libEGL ( 9894): loaded /system/lib/egl/libGLES_android.so
I/Gecko ( 9894): Failed to create EGL config!
F/libc ( 9894): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
I/DEBUG ( 9891): debuggerd committing suicide to free the zombie!
F/libc ( 9847): Fatal signal 13 (SIGPIPE) at 0x00002677 (code=0)
I/DEBUG ( 9978): debuggerd: Jul 6 2012 04:08:21
I/ ( 9979): ServiceManager: 0xf958
V/yamaha::media::CManager( 9979): constructor
Click to expand...
Click to collapse
Seems like a Gecko Chrome error but I can't be sure. As a last ditch effort I tried to follow gokhanmoral's method of extracting/mounting pusler's images, creating tar files and placing them into a CWM flashable zip but Siyah wouldn't recognise the 2ndROM after installing so now I'm all out of ideas.
Has anyone managed to successfully install the 6th July build as a 2ndROM? Any help/info would be appreciated.
Cheers
Related
Hello!
I have some problem with my Samsung Galaxy S2. In normal system, when some application crash then can see message box to force shutdown application and additional report a problem to the author. Unfortunately I don't have it. When some application crash then first my phone freeze for about 1-2 minutes (but upper toolbar works) and later my phone restart, but it's not a full booting.
I connected my phone to the PC and run logcat so I got this logs. Parsebin: 8db3G1c5 . I thing this part of logs is interesting:
09-30 10:58:51.570 E/android.os.Debug( 1991): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
09-30 10:58:51.595 I/dumpstate(10861): Check if stand-alone
09-30 10:58:51.605 I/dumpstate(10861): begin
09-30 10:58:52.070 W/ActivityManager( 1991): Activity pause timeout for r
(...)
09-30 10:59:36.900 I/Process ( 1991): Sending signal. PID: 1991 SIG: 3
09-30 10:59:36.905 I/dalvikvm( 1991): threadid=3: reacting to signal 3
09-30 10:59:37.005 I/dalvikvm( 1991): Wrote stack traces to '/data/anr/traces.txt'
09-30 10:59:37.005 E/Watchdog( 1991): [email protected] 183
(...)
09-30 11:00:09.125 I/Watchdog_N( 1991): dumpKernelStacks
09-30 11:00:09.145 E/android.os.Debug( 1991): [email protected]umpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_watchdog
09-30 11:00:09.145 E/Watchdog( 1991): WATCHDOG caused by null
(...)
09-30 11:00:21.200 I/Process ( 1991): Sending signal. PID: 1991 SIG: 9
09-30 11:00:21.200 W/Watchdog( 1991): *** WATCHDOG KILLING SYSTEM PROCESS: null
09-30 11:00:21.330 I/binder_sample(10879): [,14,86755,app_process,100]
09-30 11:00:21.330 I/binder_sample(10847): [,2,89808,com.prodtestapp,100]
09-30 11:00:21.330 I/binder_sample( 2219): [com.android.internal.telephony.ITelephonyRegistry, 4,18131,com.android.phone,100]
09-30 11:00:21.330 I/Process (10847): Sending signal. PID: 10847 SIG: 9
09-30 11:00:21.330 E/AndroidRuntime(10847): Error reporting crash
09-30 11:00:21.330 E/AndroidRuntime(10847): android.os.DeadObjectException
09-30 11:00:21.330 E/AndroidRuntime(10847): at android.os.BinderProxy.transact(Native Method)
09-30 11:00:21.330 E/AndroidRuntime(10847): at android.app.ActivityManagerProxy.handleApplication Crash(ActivityManagerNative.java:2950)
09-30 11:00:21.330 E/AndroidRuntime(10847): at com.android.internal.os.RuntimeInit$UncaughtHandle r.uncaughtException(RuntimeInit.java:96)
09-30 11:00:21.330 E/AndroidRuntime(10847): at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:693)
09-30 11:00:21.330 E/AndroidRuntime(10847): at java.lang.ThreadGroup.uncaughtException(ThreadGrou p.java:690)
09-30 11:00:21.330 E/AndroidRuntime(10847): at dalvik.system.NativeStart.main(Native Method)
09-30 11:00:21.335 W/Sensors ( 8861): sensorservice died [0x1523e0]
09-30 11:00:21.335 W/Sensors ( 2219): sensorservice died [0xb9640]
(...)
Click to expand...
Click to collapse
My phone has version I9100BVLPH (Orange 4.0.4), update only by KIES. I think that my phone has some garbage from previous version, because I had 2.3*, 4.0.3 and now 4.0.4, all update by KIES. I remember that someday it works.
How can I fix it? My phone is rooted.
Thank you for help.
Fryderyk
------
Sorry, please move my post to Q&A.
dedykjp said:
Hello!
I have some problem with my Samsung Galaxy S2. In normal system, when some application crash then can see message box to force shutdown application and additional report a problem to the author. Unfortunately I don't have it. When some application crash then first my phone freeze for about 1-2 minutes (but upper toolbar works) and later my phone restart, but it's not a full booting.
I connected my phone to the PC and run logcat so I got this logs. Parsebin: 8db3G1c5 . I thing this part of logs is interesting:
My phone has version I9100BVLPH (Orange 4.0.4), update only by KIES. I think that my phone has some garbage from previous version, because I had 2.3*, 4.0.3 and now 4.0.4, all update by KIES. I remember that someday it works.
How can I fix it? My phone is rooted.
Thank you for help.
Fryderyk
------
Sorry, please move my post to Q&A.
Click to expand...
Click to collapse
First post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Jokesy said:
First post your ROM and kernel details; Goto Settings - About phone, and post everything you see
Click to expand...
Click to collapse
Model: GT-I9100
Android version: 4.0.4
Modem: I9100BVLPE
Kernel: 3.0.15-I9100BVLPH-CL969772 [email protected] #3 SMP PREEMPT Mon Jul 30 15:28:47 KST 2012
Version: IMM76D.BVLPH
dedykjp said:
Model: GT-I9100
Android version: 4.0.4
Modem: I9100BVLPE
Kernel: 3.0.15-I9100BVLPH-CL969772 [email protected] #3 SMP PREEMPT Mon Jul 30 15:28:47 KST 2012
Version: IMM76D.BVLPH
Click to expand...
Click to collapse
Flash a custom kernel first, then perform a factory data reset
Jokesy said:
Flash a custom kernel first, then perform a factory data reset
Click to expand...
Click to collapse
I don't wanna flash a custom kernel or perform a factory data reset. Maybe it's a better way to fix it. Maybe clear some files or directory in /data directory.
dedykjp said:
I don't wanna flash a custom kernel or perform a factory data reset. Maybe it's a better way to fix it. Maybe clear some files or directory in /data directory.
Click to expand...
Click to collapse
5 minutes ago I discovered a reason of my problem. The reason was rooted phone. After unroot my phone works well. It means that when application crash then I get ANR. Again after root my phone I also get this exception.
Why? Is this only my problem or it's global, but not discovered to now.
Hello, currently, one of our Galaxy 4.0 Players is stuck in a boot loop. I have been searching this site and a few others for over a month now for solutions and am stumped.
I have tried flashing several different US YP-G1 stock ROMs using both Heimdall and Odin, Terrasilent kernel, Steve's kernel, Icyfusion ROM, factory reset, wiping cache/dalvik.
Over a month ago, the device started randomly rebooting and showing the first time startup screen each time it rebooted like this. When it would have a random reboot however, it would get stuck in a boot loop and have to be restarted by holding the power button or pulling battery. Then after a couple weeks of that, it has since been stuck in a boot loop.
Interesting "dmesg" information that may or may not have anything to do with this are:
7.347889] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.352046] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
7.362574] init: SEC_DEVENC ***[/dev/block/mmcblk0p2][0]
7.368081] init: failed that mount s:'/dev/block/mmcblk0p2', t:'/data', f
8.585066] mmc0: error -110 whilst initialising MMC card
8.655510] mmc1: new high speed SDHC card at address b368
I believe that the internal sdcard has died and have formatted the external one with the vfat and rfs partitions to act as the internal sdcard. But according to dmesg, it appears that perhaps mmcblk0p2 is trying to be mounted in the boot procedure before MMC1 is detected?
Any help is greatly appreciated and I will provide any more information as needed.
-Tony
"FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread"
update
Between flashing the international verions's bootloader, reflashing recovery rom, Terrasilent kernel and restoring a Nandroid backup from our other YP-G1, the mounting problems seem to be gone now.
However, there is still a bootloop problem which I believe has something to do with these logcat entries:
D/NativeDaemonConnector( 246): NativeDaemonConnector ::
D/NetdConnector( 246): run ::
D/NetdConnector( 246): listenToSocket ::
I/SystemServer( 246): Connectivity Service
W/dalvikvm( 246): threadid=17: thread exiting with uncaught exception (group=0x
40015578)
E/ ( 246): Dumpstate > /data/log/dumpstate_sys_error
V/ConnectivityService( 246): ConnectivityService starting up
E/ActivityThread( 246): Failed to find provider info for settings
E/AndroidRuntime( 246): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThre
ad
E/AndroidRuntime( 246): java.lang.NullPointerException
E/AndroidRuntime( 246): at android.provider.Settings$NameValueCache.getS
tring(Settings.java:664)
E/AndroidRuntime( 246): at android.provider.Settings$Secure.getString(Se
ttings.java:2209)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:264)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService.<init>
(ConnectivityService.java:61)
E/AndroidRuntime( 246): at com.android.server.ConnectivityService$Connec
tivityThread.run(ConnectivityService.java:229)
I/dumpstate( 277): begin
E/dumpstate( 277): Cannot get free space size. So, skip dumpstate.
When the problems first started before all the flashing, logcat also showed this fatal exception in ConnectivityThread
Hi all,
I work in a cell phone chipset company and I was trying to run CM10.1 on our device.
It looks like the kernel is working and adb is working as well.
But it just can't boot into idle screen. Attachment is the logcat.
Looks like dalvik thing or lot more other things...
Hoping someone give us a hand and provide some clues or hints. Thanks in advance!!
========================================================================
After check the permisson, logs look better but still stuck. Thanks to Kangie.
Any further ideas?
I'm not a CM Porting expert, but looking at the log it does seem to be choking when trying to initialise the dalvik cache.
I'd start with checking the perms on /cache/dalvik-cache.
01-04 18:54:05.310 E/dalvikvm( 824): Could not stat dex cache directory '/cache/dalvik-cache': Permission denied
01-04 18:54:05.310 I/dalvikvm( 824): Unable to open or create cache for /system/framework/core.jar (/cache/dalvik-cache/[email protected]@[email protected])
...
01-04 18:54:05.310 E/dalvikvm( 824): VM aborting
01-04 18:54:05.310 F/libc ( 824): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1), thread 824 (dexopt)
Anyway - Looks mostly like a perms issue. Check that, go from there.
Kangie said:
I'm not a CM Porting expert, but looking at the log it does seem to be choking when trying to initialise the dalvik cache.
I'd start with checking the perms on /cache/dalvik-cache.
Anyway - Looks mostly like a perms issue. Check that, go from there.
Click to expand...
Click to collapse
hi Kangie,
Thanks!! The log seems different when I modified the permissions.
And now the log is attached again. this is logcat_v2.
Any help woul;d be much appreciated~~:good:
On second thoughts: It does look like Vold (Volume Daemon) is crashing then..
01-06 17:49:22.140 W/MountService( 713): Thread android.server.ServerThread still waiting for MountService ready...
This happens over and over. My guess is that the android boot is being held up by this - It just keeps waiting for something that never happens. That's a good starting point. I'm not sure where to go from there and don't have a device - Back over to you for observations.
Hello all
I am having some trouble with SDK installing apps to my Android. I've tried to find many forums about my issue, but I've hit a brick wall every time. My rooted device is an LG Optimus C running Android 2.2 (ancient lol). My issue is that I'm getting the error: Failure [INSTALL_FAILED_DEXOPT] for every app I try to install. I've wiped the device twice and then found out that this error happens every time after I've installed a good amount of apps...which I read somewhere that this will happen because of not having enough space in Dalvik..or in the data area and won't allow the install to write anything else..correct me if I'm wrong on this I've also cleared all caches multiple times, including Dalvik.
I've also tried the work around where you try and skip that all together and put the app straight into /system /app. That came up with no resolution, even with the correct properties selected (read/write/execute etc). So now, I really have no other avenues left but to come here and ask.
Here is the Logcat results I get using adb install -r app.apk no matter what app it is. I will use tumblog.apk (compatible with device) for this example:
D/AndroidRuntime( 4201):
D/AndroidRuntime( 4201): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
I/AndroidRuntime( 4201): Heap size: -Xmx32m
D/AndroidRuntime( 4201): CheckJNI is OFF
D/AndroidRuntime( 4201): Calling main entry com.android.commands.pm.Pm
W/ActivityManager( 1356): No content provider found for:
W/ActivityManager( 1356): No content provider found for:
D/PackageParser( 1356): Scanning package: /data/app/vmdl-166230949.tmp
D/PackageManager( 1356): Scanning package com.luckydroid.tumblelog
E/PackageManager( 1356): Package com.luckydroid.tumblelog has mismatched uid: 10
060 on disk, 10061 in settings
I/PackageManager( 1356): Linking native library dir for /data/app/com.luckydroid
.tumblelog-1.apk
D/installd( 1256): DexInv: --- BEGIN '/data/app/com.luckydroid.tumblelog-1.apk'
---
D/dalvikvm( 4211): Zip inflate: partial write (will retry): (24536 of 32768)
E/dalvikvm( 4211): Zip inflate: write failed: No space left on device
W/dalvikvm( 4211): DexOptZ: extraction of classes.dex from /data/app/com.luckydr
oid.tumblelog-1.apk failed
W/installd( 1256): DexInv: --- END '/data/app/com.luckydroid.tumblelog-1.apk' --
- status=0xff00, process failed
E/installd( 1256): dexopt failed on '/data/dalvik-cache/[email protected]@com.luckydroid.
[email protected]' res = 65280
W/PackageManager( 1356): Package couldn't be installed in /data/app/com.luckydro
id.tumblelog-1.apk
D/AndroidRuntime( 4201): Shutting down VM
I/AndroidRuntime( 4201): NOTE: attach of thread 'Binder Thread #3' failed
D/jdwp ( 4201): adbd disconnected
I really have no clue what any of this means lol...pretty new to logcat. I am aware of the file name not matching the original name of the apk..shouldn't matter considering I've installed many apps with shortened names. Any help would be greatly appreciated! Thanks
EDIT: Looks like "E/dalvikvm( 4211): Zip inflate: write failed: No space left on device" is the problem. Not enough space in Dalvik. Still have no idea how to work around.
Bump
Is this not posted in the correct forum? I'm just guessing no one knows of a solution?
Çözüme Yakın
Sizin sorununuz apk~classes.dex~.smali dosyalarının içinde gereksiz kodları siliniz. "Ayrıca Facebook klasörünü bulup siliniz (her clasess.dex'te bulunmaz)" ayrıca kimi classes.dex boyutu 9MB iken yükleniyor bazı clasess.dex dosyaları ise 7,8*MB olunca yüklenmiyor. Tabikide kodlar içinde dexOpt= dex options ayarı vardır ama ben bulamadım sadece bunları biliyorum. Umarım çözüm bulan çıkar. TR
ported many roms but this is my first rom which has not stuck in boot animation screen im happy but this logcat is kind of pain.(
E/logwrapper( 111): executing /system/bin/e2fsck failed: No such file or directory
E/ ( 171): coming in huawei_oem_rapi_streaming_function! event=213.
E/mm-camera( 153): qcamsvr_start: old_mode = 3f
E/mm-camera( 153): qcamsvr_load_gesture_lib Error opening gesture library
E/mm-camera( 153): Cannot init Gesture library
E/cutils ( 143): Failed to read /data/.layout_version: No such file or directory
E/ ( 142): Qint android::get_number_of_cameras(): E
W/InterfaceController( 134): Warning (dlopen failed: library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
after booting the rom it show com.process.phone.android stopped working , systemui stopped woorking
what is the solution ? i cant locate system/lib/libnetcmdiface.so this file neither in base nor port rom..
for which device did you port we need more info....
Thanks for answering
vovaftw said:
for which device did you port we need more info....
Click to expand...
Click to collapse
i have ported for HUawei y201 Pro
USed rom made for Huawei G300
there are so much builds of Cm which are ported from g300 to y201 pro so i tried to port pac rom but faced this thing..
guide
vovaftw said:
for which device did you port we need more info....
Click to expand...
Click to collapse
please guide me .
Thanks
add me on Skype vova50006
ok
vovaftw said:
add me on Skype vova50006
Click to expand...
Click to collapse
thanks for ans im adding you