Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Boot Loop With Cm9 Rc1


This topic has been archived. This means that you cannot reply to this topic.
2 replies to this topic

#1 Androidarian

Androidarian
  • Members
  • 100 posts

Posted 17 July 2012 - 02:43 AM

Hi everyone,

I have a Sony Ericsson Active which I installed CM 9 rc1 on .

It's stuck in a boot loop:


D/CALCFPS ( 632): ignorethresh_us: 500000
D/FramebufferNativeWindow( 632): mNumBuffers = 2
E/libgenlock( 632): genlock_create_lock: open genlock device failed (err=No such file or directory)
E/msm7x30.gralloc( 632): alloc_impl: genlock_create_lock failed
E/memalloc( 632): /dev/pmem: Failed to unmap memory at 0x21 :Invalid argument
E/msm7x30.gralloc( 632): Could not unmap memory at address 0x21
E/memalloc( 632): PMEM_UNMAP failed (Bad file number), fd=1236880, sub.offset=0, sub.size=2008
D/libgenlock( 632): Invalid gralloc handle (at 0x12c874): ver(1389920/12) ints(946239248/12) fds(946239424/2) magic(\@--/gmsm)
E/libgenlock( 632): genlock_release_lock: handle is invalid
E/msm7x30.gralloc( 632): free_impl: genlock_release_lock failed
F/libc ( 632): @@@ ABORTING: INVALID HEAP ADDRESS IN dlfree
F/libc ( 632): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 119): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 119): Build fingerprint: 'SEMC/ST17i_1254-6360/ST17i:4.0.4/4.1.B.0.431/UL5_3w:user/release-keys'
I/DEBUG ( 119): pid: 632, tid: 645 >>> system_server <<<
I/DEBUG ( 119): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 119): r0 deadbaad r1 00000001 r2 40000000 r3 00000000
I/DEBUG ( 119): r4 00000000 r5 00000027 r6 2aae92ca r7 2aaf74d4

Any ideas on this?  I can easily try anything if someone has suggestions.  I think this is the same as this bug:

http://code.google.c.../detail?id=5586

Actually that is merged to bug: http://code.google.c.../detail?id=5522 which is going to be fixed probably in the next RC.

Thanks

Edited by Androidarian, 17 July 2012 - 02:47 AM.


#2 Androidarian

Androidarian
  • Members
  • 100 posts

Posted 21 July 2012 - 01:25 AM

I just installed RC2 and it had the same bootloop.

#3 Androidarian

Androidarian
  • Members
  • 100 posts

Posted 13 September 2012 - 04:10 PM

View PostAndroidarian, on 21 July 2012 - 01:25 AM, said:

I just installed RC2 and it had the same bootloop.

This bug was my fault.  I need to reflash the boot.img using fastboot.  It works great!  CM 9.1 on a water-resistant compact phone!

Edited by Androidarian, 13 September 2012 - 05:00 PM.