Root Froyo Development

[flick159]

Disable signature verification. Won't matter though that rom will not boot.

 

[thelostsoul]

All attempts I tried had same result. Init is broken. Also, prelinked map is diff from aosp as lg doent use aosp they use code aurora sources. Code Aurora Eclair coffee branch was used by LG for eclair.

Hmm, okay I'm trying to build from Code Aurora now. I tried the almond branch, but I'm having trouble getting the Wifi module to build. Do you use gtalk? Would you be willing to help me get it built properly?

PM me your gtalk name and we can try to get this going.

Thanks!

 

[flick159]

*delete please*

 

[chase8333]

Sounds like were making headway... fast.

 

[darkxsun]

Dunno if it means much, but I unpacked that froyo test and pulled the kernel from it, then repacked that kernel into velocity .3 rom. I got the kernel to boot.

$ su
su
# cat /proc/version
cat /proc/version
Linux version 2.6.29 (grid@grid-laptop) (gcc version 4.4.0 (GCC) ) #3 PREEMPT Fr
i Sep 3 04:55:29 EDT 2010

Isn't the Froyo kernel 2.6.32?

 

[flick159]

IIRC, yes it is. I wanted to know if the kernel was the problem, and the version that was included in lostsoul's zip.

 

[darkxsun]

What I mean is, are you sure that's the kernel from the froyo test image?

 

[flick159]

What I mean is, are you sure that's the kernel from the froyo test image?

Scratch that, must have made a mistake when repacking the boot image. Doing it a second time using the kernel from the froyo zip, putting it into velocity, resulted in a hang at the lg logo.

 

[darkxsun]

Scratch that, must have made a mistake when repacking the boot image. Doing it a second time using the kernel from the froyo zip, putting it into velocity, resulted in a hang at the lg logo.

Thanks for double-checking -- that's the result I got too.

 

[thelostsoul]

The one I posted here was using CWM's kernel. I did not expect that to work at all, I just wanted to get some advice from other people who knew more.

The one I sent over IRC before was a pretty bare AOSP build. That's the one that hung on the "ANDROID_" screen.

I've since given up with those two builds and am now trying to work with code aurora, but will need some help. If you know a thing or two about building and want to help me out, send me a PM with your gtalk username. I'd like to get another build going tonight if possible, but I'm pretty stuck in getting it to either skip the wifi module completely or actually build it properly.


Thanks!

 

[flick159]

Wish I could help you out man, I'm not familiar with building anything from source. I'll be glad to test out anything when you get it finished up though.

 

[death2all110]

Will help test once you get a build.

 

[chase8333]

Will help test to. (BTW i changed some things in the file and it got to the verizon splash and hung)

 

[thelostsoul]

Guys please, this is NOT a beta-testing signup thread. I'll ask for testers when or IF it gets to a working state. Far from it right now.

Will help test to. (BTW i changed some things in the file and it got to the verizon splash and hung)

Could you be specific as to what you changed? If you got it to boot further it could really help a lot!

 

[chase8333]

I replaced the boot.img with velocity V0.3 and flashed it with the turbo 4 kernel I will continue to fiddle with file and tell you if i make anymore progress.

 

[thelostsoul]

I replaced the boot.img with velocity V0.3 and flashed it with the turbo 4 kernel I will continue to fiddle with file and tell you if i make anymore progress.

Replacing the boot.img replaces the kernel. Replacing the kernel with a 2.1 kernel won't help getting froyo.

Good try, thanks for the effort!

 

[chase8333]

any time

 

[thelostsoul]

The problem I encountered building the wifi driver was bypassed by removing these lines from the "BoardConfig.mk" file:

# Wifi related definesBOARD_WPA_SUPPLICANT_DRIVER := WEXT
WPA_SUPPLICANT_VERSION      := VER_0_6_X
BOARD_WLAN_DEVICE           := bcm4325
WIFI_DRIVER_MODULE_PATH     := "/system/lib/modules/wireless.ko"
WIFI_DRIVER_FW_STA_PATH     := "/system/etc/wl/rtecdc.bin"
WIFI_DRIVER_MODULE_ARG      := "firmware_path=/system/etc/wl/rtecdc.bin nvram_path=/system/etc/wl/nvram.txt"
WIFI_DRIVER_MODULE_NAME     := "wireless"

From what I can tell, removing these is most likely not building the wifi drivers, but I'd be willing to go without wifi for a bit. Unfortunately, I ran out of hard drive space while building late last night. I'm going to try again tonight, but if anyone has any advice, please contact me asap! I'd really like to get this working.

 

[myfishbear]

The problem I encountered building the wifi driver was bypassed by removing these lines from the "BoardConfig.mk" file:

# Wifi related definesBOARD_WPA_SUPPLICANT_DRIVER := WEXT
WPA_SUPPLICANT_VERSION      := VER_0_6_X
BOARD_WLAN_DEVICE           := bcm4325
WIFI_DRIVER_MODULE_PATH     := "/system/lib/modules/wireless.ko"
WIFI_DRIVER_FW_STA_PATH     := "/system/etc/wl/rtecdc.bin"
WIFI_DRIVER_MODULE_ARG      := "firmware_path=/system/etc/wl/rtecdc.bin nvram_path=/system/etc/wl/nvram.txt"
WIFI_DRIVER_MODULE_NAME     := "wireless"

From what I can tell, removing these is most likely not building the wifi drivers, but I'd be willing to go without wifi for a bit. Unfortunately, I ran out of hard drive space while building late last night. I'm going to try again tonight, but if anyone has any advice, please contact me asap! I'd really like to get this working.

excuse me if i sound a bit noobish here but going on my knowledge of linux and windows makes me think. i can run android apks on linux. so maybe you can port a linux driver to the android or the existing one from the current 2.1 and name it the after the froyo name scheme. anyway i see the word nvram in there... i think thats for a nvidia device... or broadcom (bcm)... maybe even realtec(rtecdc.bin)... idk... anyway i never use my wifi cuz 3g makes it pointless (and my email dose not sync + kills my battery)
bty what are you building it on... maybe ill dl it and start tinkering around.(i know c++ and html and can guess at other languages well)+ i got like 2 2tb hds lol

 

[thelostsoul]

I'm not too sure I follow what you're implying about running apks on linux. The most prominent issue is getting the kernel to work. As someone mentioned earlier, init is not functioning. I am building from codeaurora.org at the moment.

As for copying the Wifi module, from what I can tell, some of the building variables and commands have changed for Froyo, and that is why it won't build. I will post the exact error when I get home and try it again.

But I am building it on my laptop under Ubuntu 10.10. It takes a bit to get all the proper packages setup and the build environment working, but I could use your help if you PM me your gtalk name. We might be able to discuss things and get something going.

 

[myfishbear]

well i figure if you copy and tweek the old code then place it on top of the new module piece by piece so we dont mess up the command list. basicly filling in the module of the new kernal (i would start where it defines the hardware and would work my way out)

 

[thelostsoul]

Except the new module needs to be built from scratch. This is the key issue that comes from not having a Froyo build from LG to start. Most custom builds from source are not ports unless there exists a similar hardware device with that code. For example, if one HTC device got the update before the other and the specs are similar, a port would likely be considerably easy. But when there exists no similar devices, its a lot more difficult because nothing can be copied.

 

[myfishbear]

lets see if the lg shine plus, the lg optimus one, or the lg vortex(a verizon phone with a 600mhz arm cpu and froyo. it is being released on oct 29) has one maybe. if not skip the wifi for now and wait to see if any files pop up after the vortex is released.

 

[thelostsoul]

Nope, I checked. It's just about the same as the Ally, but it's GSM so would also be difficult to port even if it did exist.

 

[myfishbear]

Nope, I checked. It's just about the same as the Ally, but it's GSM so would also be difficult to port even if it did exist.

the vortex is a vzw phone that looks so much like the ally. i know that one is cdma but it hasnt been released yet

http://www.androidmsg.com/2010/09/23/lg-vortex-for-verizon-spied-again-bing-no-fm-radio/

again i don't think we can do anything with the module until this phone comes out so bypass it for now