Unlocked bootload and CM10

[saxydroid]

Man, that makes this very frustrating. It sounds like CM10 is fully booting up then, but we can't see the screen. . I'm going to keep looking for a better copy of the drivers to see if I can integrate them.

On Linux, do you get any device listed when you run "lsusb"?

lusb shows the device.

I found to get the computer to recognize the lucid, you have to wipe data/ factory reset from recovery every time you want to use adb, because after a few minutes of booting, usb debugging gets disabled by the OS.

here is a logcat and dmesg (from right before the device disappears from adb)

 

[Neph81]

lusb shows the device.

I found to get the computer to recognize the lucid, you have to wipe data/ factory reset from recovery every time you want to use adb, because after a few minutes of booting, usb debugging gets disabled by the OS.

here is a logcat and dmesg (from right before the device disappears from adb)

Ok, this is going to be a strange question, but does anyone have a MHL (micro-usb to hdmi) adapter that they can try out? The dmesg is showing that HDMI is booting up normal and I'm wondering if we can get video output through it to see how far the phone is getting.

 

[sammyz]

Ok, this is going to be a strange question, but does anyone have a MHL (micro-usb to hdmi) adapter that they can try out? The dmesg is showing that HDMI is booting up normal and I'm wondering if we can get video output through it to see how far the phone is getting.

Try this instead:
http://code.google.com/p/androidscreencast/

 

[Neph81]

Try this instead:
androidscreencast - Desktop app to control an android device remotely - Google Project Hosting

Very interesting. I can see my phone screen, so this should in theory work for the lucid. Anyone want to give this a try? And the touch screen drivers do initialize, so you should be able to use touch commands with this.

 

[sammyz]

Very interesting. I can see my phone screen, so this should in theory work for the lucid. Anyone want to give this a try? And the touch screen drivers do initialize, so you should be able to use touch commands with this.

I can get keyboard controls to work after doing this on my optimus M:


adb shell
su
chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
chmod 777 ./

Edit: not sure how you will be able to grant SU permissions if you have to touch the screen...so you will have to mount /data and /system while in recovery and run those commands

 

[Neph81]

Kernel 4c is done. I've added in a few lines so that ADB "should" be persistent through boot and into the system. I've also compiled another kernel image in an attempt to get the video drivers working.

http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4c.zip

 

[saxydroid]

Kernel 4c is done. I've added in a few lines so that ADB "should" be persistent through boot and into the system. I've also compiled another kernel image in an attempt to get the video drivers working.

http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4c.zip

4c doesn't boot :/

screencast works until adb disconnects but all i see is the bootanimation before it disconects.

random question. in the logcat it shows as booting cm10, but the bootanimation is from a stock rom, should it be that way?

 

[Neph81]

4c doesn't boot :/

screencast works until adb disconnects but all i see is the bootanimation before it disconects.

random question. in the logcat it shows as booting cm10, but the bootanimation is from a stock rom, should it be that way?

I'm trying to rule out image resolution sizes. The boot images were all sized at 720X1280, so I replaced them with the stock ones to rule out that possibility of being an issue. I'll rebuild 4a with the persistent adb and post that one in a moment.

 

[sammyz]

I'm trying to rule out image resolution sizes. The boot images were all sized at 720X1280, so I replaced them with the stock ones to rule out that possibility of being an issue. I'll rebuild 4a with the persistent adb and post that one in a moment.

It doesn't really matter what bootanimation you use, it will still boot even if there is none. Unless a locked bootloader thinks otherwise, which I kind of doubt.

 

[Neph81]

http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4d.zip

Added in persistent adb to the 4a kernel. This should allow adb thru all of boot, unless CM decides to override it some how.

 

[Neph81]

It doesn't really matter what bootanimation you use, it will still boot even if there is none. Unless a locked bootloader thinks otherwise, which I kind of doubt.

Ok, I'll replace that with the CM boot animation when we hit beta5 then. I won't be putting out a beta5 until we can at least see then screen though.

 

[saxydroid]

http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4d.zip

Added in persistent adb to the 4a kernel. This should allow adb thru all of boot, unless CM decides to override it some how.

4d bootloops

 

[Neph81]

4d bootloops

It boot loops early or it boot loops right about where the old kernel was cutting off ADB?

 

[Connorh333]

Im trying to test this but i cant get it to flash. I dont have an sd card and CWM wont recognize the internal storage where the rom is located. I is there any way I can CWM to recognize it? Thanks in advance.

 

[Neph81]

Im trying to test this but i cant get it to flash. I dont have an sd card and CWM wont recognize the internal storage where the rom is located. I is there any way I can CWM to recognize it? Thanks in advance.

That would be a question for Koush. I haven't taken apart the lucid CWM, but in most cases, you have to specify the partitions in the fstab file. On my Atrix, which also has internal memory, I could not get it to find backups, even thou it would save to the internal memory if I chose backup from inside Rom Manger.

 

[Connorh333]

Sorry for all of the questions but How would I edit the fstab file? Like where is it located?

 

[Neph81]

Sorry for all of the questions but How would I edit the fstab file? Like where is it located?

Inside the CWM images ramdisk. This probably isn't something that a beginner should edit as a wrong edit could lead to a bricked phone. I would honestly try and get ahold of Koush (the author of CWM and CWM recovery) and ask if he can fix it or possibly tell you how to use it with a menu you haven't seen.

 

[saxydroid]

It boot loops early or it boot loops right about where the old kernel was cutting off ADB?

Early, not able to even get ADB to recognize the device before it reboots

 

[Neph81]

Early, not able to even get ADB to recognize the device before it reboots

Ok, i'll edit the ram disk again and see if I can get it to persist ADB through boot. It may break some stuff in CM, but that is a small price to pay right now.

 

[Neph81]

I don't know why I didn't think about this earlier. Can someone on stock ICS please provide me the file you get when you do "adb pull /proc/config.gz" . This should be the correct config needed to get ICS to boot and should tell me if I'm even trying to use the correct LG display drivers.

 

[saxydroid]

I don't know why I didn't think about this earlier. Can someone on stock ICS please provide me the file you get when you do "adb pull /proc/config.gz" . This should be the correct config needed to get ICS to boot and should tell me if I'm even trying to use the correct LG display drivers.

here is the config

 

[wiisixtyfour]

I don't know why I didn't think about this earlier. Can someone on stock ICS please provide me the file you get when you do "adb pull /proc/config.gz" . This should be the correct config needed to get ICS to boot and should tell me if I'm even trying to use the correct LG display drivers.

Here: config.gz - MediaFire

Edit: saxydroid beat me to it!

 

[Neph81]

Thanks guys. It matches what I've been building off of, but what I'm getting won't boot. Either they fudged the code, or I'm missing something obvious in the settings. The search goes on.

 

[sammyz]

Thanks guys. It matches what I've been building off of, but what I'm getting won't boot. Either they fudged the code, or I'm missing something obvious in the settings. The search goes on.

Which kernel did you build and which bootloader is being used on the test phones??

 

[Neph81]

Which kernel did you build and which bootloader is being used on the test phones??

cayman_vzw_us_defconfig and the testers are all on the GB bootloader as ICS is a locked bootloader.