[ICS] CyanogenMod 9 for the Ascend G300 [LINK UP]

[Guest Hans Gruber]

Right. It's more important to get the system up than HW acceleration. Do rm /system/lib/egl/egl.cfg and reboot.

http://pastebin.com/bTZsQT2W

[Guest tilal6991]

adb shell app_process -Xzygote /system/bin --zygote --start-system-server

please?

[Guest Hans Gruber]

adb shell app_process -Xzygote /system/bin --zygote --start-system-server

please?

I'm getting java errors now

D:\android-sdk\platform-tools>adb shell app_process -Xzygote /system/bin --zygot

e --start-system-server

java.lang.RuntimeException: ANDROID_SOCKET_zygote unset or invalid

at com.android.internal.os.ZygoteInit.registerZygoteSocket(ZygoteInit.ja

va:165)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:522)

at dalvik.system.NativeStart.main(Native Method)

Caused by: java.lang.NumberFormatException: Invalid int: "null"

at java.lang.Integer.invalidInt(Integer.java:138)

at java.lang.Integer.parseInt(Integer.java:355)

at java.lang.Integer.parseInt(Integer.java:332)

at com.android.internal.os.ZygoteInit.registerZygoteSocket(ZygoteInit.ja

va:163)

... 2 more

is that an error on my PC or the phone?

[Guest]

I dont think that error is with your pc,looks like phone to me.

From reading that it looks like android socket has a number format problem,just a guess really because I dont have a clue what I am seeing,may as well be in code.

Edited June 5, 2012 by Guest

[Guest tilal6991]

I think I know what's gone wrong now. All the sockets are throwing exceptions. Including zygote. So it must the boot image at fault. I'll put up a new one to flash.

[Guest tilal6991]

http://goo.im/devs/tilal6991/u8815/ROMs/boot.img

Flash in the same way as the previous boot image.

[Guest neoMJ]

The problem is with the BOARD_KERNEL_CMDLINE in the boot image. Probably the init.u8815.rc and ueventd.u8815.rc scripts are never run, because the androidboot.hardware parameter is wrong. I booted to full CM9 launcher with my own build at home by changing this parameter (but couldn't get touch screen to work yet, so did not share).

Change BoardConfig.mk to include the following and it should boot:

BOARD_KERNEL_CMDLINE := console=ttyDDC0 androidboot.hardware=u8815

Edited June 5, 2012 by neoMJ

[Guest Hans Gruber]

http://goo.im/devs/t...5/ROMs/boot.img

Flash in the same way as the previous boot image.

back to

- exec '/system/bin/sh' failed: No such file or directory (2) -

[Guest tilal6991]

The problem is with the BOARD_KERNEL_CMDLINE in the boot image. Probably the init.u8815.rc and ueventd.u8815.rc scripts are never run, because the androidboot.hardware parameter is wrong. I booted to full CM9 launcher with my own build at home by changing this parameter (but couldn't get touch screen to work yet, so did not share).

Change BoardConfig.mk to include the following and it should boot:

BOARD_KERNEL_CMDLINE := console=ttyDDC0 androidboot.hardware=u8815

[/CODE]



Wow. Thanks man. That should help.

[Guest tilal6991]

back to

- exec '/system/bin/sh' failed: No such file or directory (2) -

The above guy is correct. I never even realised that error. I'll put up a new full build soon.

[Guest Hans Gruber]

Awesome great job both of you

[Guest Davidoff59]

What a first post neoMJ. Thank you.

[Guest]

Can I light up that cigar yet :lol:

[Guest tilal6991]

Can I light up that cigar yet :lol:

Not far off I think :P

[Guest FrankieADZ]

The problem is with the BOARD_KERNEL_CMDLINE in the boot image. Probably the init.u8815.rc and ueventd.u8815.rc scripts are never run, because the androidboot.hardware parameter is wrong. I booted to full CM9 launcher with my own build at home by changing this parameter (but couldn't get touch screen to work yet, so did not share).

Change BoardConfig.mk to include the following and it should boot:

BOARD_KERNEL_CMDLINE := console=ttyDDC0 androidboot.hardware=u8815

Nice :)

Great post

[Guest neoMJ]

The problem is with the BOARD_KERNEL_CMDLINE in the boot image. Probably the init.u8815.rc and ueventd.u8815.rc scripts are never run, because the androidboot.hardware parameter is wrong. I booted to full CM9 launcher with my own build at home by changing this parameter (but couldn't get touch screen to work yet, so did not share).

Change BoardConfig.mk to include the following and it should boot:

BOARD_KERNEL_CMDLINE := console=ttyDDC0 androidboot.hardware=u8815

One more thing. Be sure to mount boot, system and userdata partitions in init.u8815.rc with ext4 partition type. Because the default init.rc of CM9 tries to mount them with yaffs2.

[Guest tilal6991]

http://goo.im/devs/tilal6991/u8815/ROMs/CFX/update-cm-9-20120605-SNAPSHOT-u8815-ColdFusionX-tilal6991-signed.zip

Here we go. Thanks to neoMJ for the tips on boot image.

[Guest Hans Gruber]

http://goo.im/devs/t...6991-signed.zip

Here we go. Thanks to neoMJ for the tips on boot image.

D:\android-sdk\platform-tools>adb logcat

- exec '/system/bin/sh' failed: No such file or directory (2) -

[Guest tilal6991]

D:\android-sdk\platform-tools>adb logcat

- exec '/system/bin/sh' failed: No such file or directory (2) -

Still... Annoying...

Try flashing the old boot image like last time.

[Guest neoMJ]

D:\android-sdk\platform-tools>adb logcat

- exec '/system/bin/sh' failed: No such file or directory (2) -

That's because the system partition cannot be mounted. init.u8815.rc should be changed to add ext4 mount commands.

I'll try to post my images when I go home.

[Guest tilal6991]

I added the commands to mount system.

[Guest tilal6991]

I'm an idiot. I know where it went wrong. I didn't git pull. I'll put up a boot.img which should fix booting.

[Guest tilal6991]

http://goo.im/devs/tilal6991/u8815/boot.img - that should fix it. Same command as last time (the dd one)

[Guest Hans Gruber]

http://goo.im/devs/t.../u8815/boot.img - that should fix it. Same command as last time (the dd one)

ooh new error! :D

looping this now... http://pastebin.com/iZr1TtBa

[Guest tilal6991]

That one is simple to fix.

adb shell

chmod 777 /dev/genlock

chown graphics.graphics /dev/genlock