Guest G300 Posted June 5, 2012 Report Posted June 5, 2012 tilal6991 this must be like pulling out your own teeth but you keep going well done and good luck.
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 D:\android-sdk\platform-tools>adb push boot.img /sdcard/ 4923 KB/s (4018176 bytes in 0.797s) D:\android-sdk\platform-tools>adb shell flash_image boot /sdcard/boot.img failed with error: -1 error scanning partitions What??? I think the recovery itself is at fault then. The boot partition is not being detected. This isn't a problem with other ROMs since the boot partition has been the same but now it is a problem. Try: /sbin/busybox dd if=/dev/zero of=/dev/block/mmcblk0p15 /sbin/busybox dd if=/sdcard/boot.img of=/dev/block/mmcblk0p15
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 (edited) What??? I think the recovery itself is at fault then. The boot partition is not being detected. This isn't a problem with other ROMs since the boot partition has been the same but now it is a problem. Try: /sbin/busybox dd if=/dev/zero of=/dev/block/mmcblk0p15 /sbin/busybox dd if=/sdcard/boot.img of=/dev/block/mmcblk0p15 could that issue be down the phone sort of having 2 SD cards? An internal and actual SD? I've run those commands and now just seeing if it will boot... D:\android-sdk\platform-tools>adb shell /sbin/busybox dd if=/dev/zero of=/dev/bl ock/mmcblk0p15 dd: writing '/dev/block/mmcblk0p15': No space left on device 16385+0 records in 16384+0 records out 8388608 bytes (8.0MB) copied, 4.175599 seconds, 1.9MB/s D:\android-sdk\platform-tools>adb shell /sbin/busybox dd if=/sdcard/boot.img of= /dev/block/mmcblk0p15 7848+0 records in 7848+0 records out 4018176 bytes (3.8MB) copied, 3.043388 seconds, 1.3MB/s oh I didn't notice that no space left error (the phone did reboot itself after that first command) Edited June 5, 2012 by Hans Gruber
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 It doesn't appear to be booting but logcat is working. It just seems to be looping this http://pastebin.com/jbvi5wZ2
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 Hahaha!! Yes. Excellent. Could you get another logcat of what happens immediately before the long stack trace?
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 Hahaha!! Yes. Excellent. Could you get another logcat of what happens immediately before the long stack trace? Is this any better? http://pastebin.com/gPzNFNPn Sorry if it's not. I might as well be pasting Chinese :D
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 Exactly correct! Right. While it's bootlooping try: adb shell mkdir /cache mkdir /cache/dalvik-cache chmod 7777 /cache/dalvik-cache chown system.system /cache/dalvik-cache.
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 Exactly correct! Right. While it's bootlooping try: adb shell mkdir /cache mkdir /cache/dalvik-cache chmod 7777 /cache/dalvik-cache chown system.system /cache/dalvik-cache. ok new error now... http://pastebin.com/R2mJjL6e
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 ok new error now... http://pastebin.com/R2mJjL6e We're almost there!! Download http://goo.im/devs/tilal6991/u8815/libgenlock.so Put it into the adb folder adb push libgenlock.so /system/lib/ adb reboot adb logcat again
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 D:\android-sdk\platform-tools>adb push libgenlock.so /system/lib/ failed to copy 'libgenlock.so' to '/system/lib//libgenlock.so': Read-only file s ystem this would be going a lot quicker if I wasn't so terrible with linux!
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 Just do adb remount before the adb push. And the fact that we've got this far is amazing in itself.
Guest Posted June 5, 2012 Report Posted June 5, 2012 Doing well here tilal :D And hans gruber,you doing a good job of the testing :D
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 I'm amazed how you do it without the phone in front of you D:\android-sdk\platform-tools>adb push libgenlock.so /system/lib/ 889 KB/s (5464 bytes in 0.006s) http://pastebin.com/Rq0bzkM8
Guest Nesli Posted June 5, 2012 Report Posted June 5, 2012 (edited) Great work guys :D Only few things i understand from logcat, for ex. we havn´t set DPI destiny, so it will boot up (if it will :D ) with dpi 160 (so small), let´s set to 220, or 240 by default.. Edited June 5, 2012 by Nesli
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 adb shell ls /dev please? D:\android-sdk\platform-tools>adb shel accel adsp akm8975_dev alarm android_adb android_adb_enable apr_apps_user ashmem binder block compass_aot console cpu_dma_latency cpuctl device-mapper diag full fuse genlock graphics hw_extern_sdcard hw_extern_sdcardMounted hw_led i2c-0 i2c-1 i2c-debug-0 i2c-debug-1 input key_test keychord kgsl-3d0 kmem kmsg light log mem msm_aac msm_amrnb msm_amrnb_in msm_amrwb msm_camera msm_evrc msm_evrc_in msm_fm msm_mp3 msm_mvs msm_pcm_ctl msm_pcm_dec msm_pcm_in msm_pcm_out msm_preproc_ctl msm_qcelp msm_qcelp_in msm_snd msm_voicememo msm_wma msm_wmapro msmdma mtd network_latency network_throughput null oncrpc pmem pmem_adsp pmem_audio ppp proximity ptmx pts random rfkill rmt_oeminfo rmt_storage rtc0 rtc1 share_mem smd0 smd1 smd17 smd2 smd21 smd22 smd27 smd3 smd36 smd4 smd7 smd_pkt_loopback smd_sns_dsps smdcntl0 smdcntl1 smdcntl2 smdcntl3 smdcntl4 smdcntl5 smdcntl6 smdcntl7 smem_log smem_sleep_log snd socket tgt tty ttyGS0 ttyGS1 ttyHS0 uinput urandom zero
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 Great work guys :D Only few things i understand from logcat, for ex. we havn´t set DPI destiny, so it will boot up (if it will :D ) with dpi 160 (so small), let´s set to 220, or 240 by default.. All these stuff are minor and can be figured out later. First if the launcher appears then the battle is essentially over!
Guest Nesli Posted June 5, 2012 Report Posted June 5, 2012 Yeah, I know, sorry :D Im so excited to see CM9 on our G300 :D
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 The next command is tricky. You need to be very fast. As soon as it starts up type: chmod 7777 /dev/kgsl-3d0 chown graphics.graphics /dev/kgsl-3d0 That needs to be done before it starts boot looping.
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 The next command is tricky. You need to be very fast. As soon as it starts up type: chmod 7777 /dev/kgsl-3d0 chown graphics.graphics /dev/kgsl-3d0 That needs to be done before it starts boot looping. I *think* I got it? http://pastebin.com/Gg47Tamn I put them both in a .bat file
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 I *think* I got it? http://pastebin.com/Gg47Tamn I put them both in a .bat file Very strange. The error causing the loop is I/Adreno ( 150): open(/dev/kgsl-3d0) failed: errno 2. No such file or directory Which suggests that the socket doesn't exist. But from the ls you gave earlier it quite clearly does?? Try the bat file again and see if you go even quicker. If it doesn't work I have a solution but it will mean no HW acceleration ie. slow UI.
Guest Hans Gruber Posted June 5, 2012 Report Posted June 5, 2012 :( I've tried a few more times and I'm not sure it could be done any quicker. It's still saying I/Adreno ( 152): open(/dev/kgsl-3d0) failed: errno 2. No such file or directory
Guest Nesli Posted June 5, 2012 Report Posted June 5, 2012 Could´n be problem with the fact, that G300 doesn´t have Adreno 200, but Adreno 200 Enhanced..?(different drivers, etc.)
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 Right. It's more important to get the system up than HW acceleration. Do rm /system/lib/egl/egl.cfg and reboot.
Guest tilal6991 Posted June 5, 2012 Report Posted June 5, 2012 Could´n be problem with the fact, that G300 doesn´t have Adreno 200, but Adreno 200 Enhanced..?(different drivers, etc.) Shouldn't matter. The socket itself should be the same.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now