yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] MuffinsFTW:
This might be a stupid suggestion but have any of you guys tried running 2.1 instead of 2.0 on it.

Im sure i remember reading somewhere there were less problems with 2.1 than 2.0 could be wrong though. I cant test it out as i still don't have my GW620 yet.
[Upgrading, Modifying and Unlocking] pinashstri:
i aacept with information:

* Routehero is making steady progress getting 2.0 to boot on the stock

kernel.

* A few folks are communicating with LG with the hopes of getting LG to

release their kernel changes for this device to Android Trunk

* I'm working on getting a functional backup process in place so we don't

have to keep reflashing to factory

* enkoopa got a process sorted to install all the various drivers for windows

* The wiki page is growing, though it doesn't yet contain all the juicy

goodness from this thread.
[Upgrading, Modifying and Unlocking] Zacpod:
If you've tried to install the LG drivers while debug mode was on you MUST turn debug mode on and use Device Manager to uninstall any detected devices. There should be 2 devices to uninstall. Once you've uninstalled them, scan for hardware changes and they should show up as unknown devices. You can then right click on each of them and select update driver - let me choose the driver to install - select from list - all drivers - have disk - then browse to the Android SDK USB Drivers folder.

That's a bit of work. You'll have to partition your SD card in to at least 2 partitions - format the 2nd partition as Ext2. Move /data/app/* to the ext2 partition, and ensure /data/app/ is empty. You'll then have to modify the boot.img's ramdisk (and the system.img's /etc/fstab) to mount the ext2 partition to your /data/app folder after /data has been mounted. That should do the trick, but I've not tested the process. To do this you will need a dump of boot.img as you need to modify the ramdisk and can't do that on the phone. All the other mods can be done on the phone, afaik. You'll also need the ROM-Cooker scripts (unpack.pl and repack.pl) mkyaffs2image from the Android source tools, and unyaffs. I know those tools work in Linux and MacOS, but I don't know if they're available for Windows... mkyaffs2image will be problematic, as it's generated during the build of AOSP, and building Android on Windows isn't supported.

Phwew! Glad that didn't cause anyone a headache. :)

Afaik, if you turn off debugging and turn off mass storage mode the phone will present itself as a modem. You can then tether via usb. You'll have to get the number to dial from your isp though - e.g. on Bell Blackberries it's #777

We're using AOSP (Android Open Source Project.) I'm not sure if it's 2.0 or 2.1 - it's the most current Open Source available at the time. The problem, however, isn't that A2.0 is unstable - it's that we're trying to use a 1.5 kernel to run 2.x. At least until we can hold of LGs kernel changes.
[Upgrading, Modifying and Unlocking] Core_5:
Thanks. I will wair patiently for further developments before continuing.
[Upgrading, Modifying and Unlocking] Zacpod:
If you're still having problems with the USB driver you may want to consider setting up a virtual machine and installing Ubuntu. That way you'll at least be able to use ADB.

I'll poke around a little and see if I can build a boot.img/system.img that stores apps on the sd card. It's something I've been interested in checking out, and now that I've outlined the process I may give it a shot. :)
[Upgrading, Modifying and Unlocking] Zacpod:
I have managed to move my apps to my SD card. I need to clean up the process a little, as it currently involves manually setting some permissions every reboot, but once I have that sorted I'll make a boot.img/system.img and make them available. :)
[Upgrading, Modifying and Unlocking] DJ_Spray:
Thanks for this. If i do your mod, will i lose my programs, my settings (french keaboard, background and musics etc)?
[Upgrading, Modifying and Unlocking] sheptard:
I just did this, I might not have done it properly, but I seem to have kept all of my existing settings.
[Upgrading, Modifying and Unlocking] DJ_Spray:
mmm, might give it a go then this weekend....
[Upgrading, Modifying and Unlocking] Zacpod:
You should keep all your settings and programs. However, this boot image is based off the Rogers image, so you may gain some (and loose some) carrier specific apps if you're with another provider. It won't affect which carrier your phone is sim-locked too - you'll just get some of the Rogers cruft. There's info on cleaning it out in the Wiki. Some of it is useful, so I left it all in there.
[Upgrading, Modifying and Unlocking] fraps:
Just AWESOME! Great work!!
[Upgrading, Modifying and Unlocking] lgeveuser:
safe

nice work all going for the lg eve! i cant wait for 2.0!
[Upgrading, Modifying and Unlocking] sheptard:
So I flashed Zacpod's rom, and I don't have the ability to open up settings -> Wireless.

Also if I turn on Wifi via the top menu, the phone will go into a loop where it reboots just after the android screen.
[Upgrading, Modifying and Unlocking] Zacpod:
Odd, It sounds like either userdata or cache is corrupt.

Cache is easier, so try reformatting it. Easiest way to do that is to do a "fastboot flash cache lgdrm.img" to throw and almost empty yaffs img on to it.

If that doesn't work, do a nandroid backup, then "adb shell cat /dev/zero > /dev/mtd4" then reboot to fastboot and "fastboot flash userdata userdata.img"

Let me know if that doesn't work and we'll try some other stuff.
[Upgrading, Modifying and Unlocking] gmarcoux:
I apologise in advance if I am in the wrong forum. If I am please direct me to the proper one. I’ve recently purchased an unlocked Rogers LG Eve and am able to make calls but am unable to connect the Bell Mobility HSPA network. I’ve copied my friend’s Samsung Galaxy settings so I know those are correct. Can you help?

Thank you in advance
[Upgrading, Modifying and Unlocking] Zacpod:
Sorry GMarcoux - I don't know what the issue might be. You may have to register the imei with Bell. Call them. If you have a contract with Bell they should be able to help you get your phone online.
[Upgrading, Modifying and Unlocking] tony378:
Hi, I follow the Configuring Apple iPhone for the Bell Mobility HSPA networking, it works on my LG Eve.

Link:

http://www.bell.ca/support/PrsCSrvWls_Configure_iPhone.page
[Upgrading, Modifying and Unlocking] Core_5:
Is it possible to edit the list of images in Android's Wallpaper Gallery? And where are those images stored in the phone?

I ask because it appears that these wide format images from this locked set can be applied with no cropping and no stretching and divide into perfect thirds for each home page. I think the way the phone makes you crop images is god awful :(

PS. Excellent work Zacpod for working out Apps to SD. Thanks.
[Upgrading, Modifying and Unlocking] Nick14:
Anyone can tell me what CPU it has ? :)
[Upgrading, Modifying and Unlocking] sheptard:
The CPU is a Qualcomm MSM7200A
[Upgrading, Modifying and Unlocking] Zacpod:
There's now an LG GW620 Eve specific forum over at Android Network. Any general android/Eve questions can be asked there. Please leave this thread free for discussing getting AOSP running on the Eve.

Thanks, and cheers :)
[Upgrading, Modifying and Unlocking] semaan123:
1. Connect to your phone using "adb shell", make sure your file system is read/write (remount)

2. If you want to make a backup copy of the non-functional terminal emulator to your sdcard

# cd /system/app

# dd if=Term.apk of=/sdcard/Term.apk

28+1 records in

28+1 records out

14630 bytes transferred in 0.005 secs (2926000 bytes/sec)

# dd if=Term.odex of=/sdcard/Term.odex

97+1 records in

97+1 records out

49960 bytes transferred in 0.017 secs (2938823 bytes/sec)3. Delete terminal emulator

# rm Term.apk

# rm Term.odex4. Using Android

Everytime I try this step, it tells me Read-Only file system. I am running windows 7 and I followed all the steps to root the phone and it seems to be working. How can I ensure the rooting is done and how can i make my file system read-write.

Thanks in advance
[Upgrading, Modifying and Unlocking] Zacpod:
adb remount

or from an adb # shell:

mount -o remount rw /system
[Upgrading, Modifying and Unlocking] semaan123:
After doing "adb remount", it tells me remount succeeded but it still did not solve the issue. I tried the "mount -o remount rw /system" aswell. It still tells me Read-only file system
[Upgrading, Modifying and Unlocking] Zacpod:
Is your phone rooted?

If you get a $ prompt when you do an "adb shell" then "adb remount" won't work - you have use su to get to a # prompt then "mount -o remount rw /system"

This will not work at all if you haven't rooted your phone is some way - the system partition is read-only, and can't be set to read-write without root permission. If you don't want to root your phone but do want a proper terminal, then just find Better Terminal Emulator and install it.

If may be easier for you to simply download my apps2sd image and fastboot it on to your phone.
[Upgrading, Modifying and Unlocking] kingrz:
In the .mbn files, there are some .form files. someone know how to open this .form files?
[Upgrading, Modifying and Unlocking] routehero:
I'm back from some R&R over the holidays.

Just got a notice of a post (Zac did too) that they distributed the GW620 open source.

I'm downloading it now. It weighs in at 135 MB, which is considerably higher than the Linux kernel (plus any reasonable modifications) alone.

Will post an update after I have a look at the contents.
[Upgrading, Modifying and Unlocking] semaan123:
When I do abd shell, I see #. I followed Routehero's rooting procedure. Does that automatically mean my phone is rooted?. And also what is the apps2sd image, what does it change over the regular image?

Thanks for your quick response I appreciate it
[Upgrading, Modifying and Unlocking] Zacpod:
W00t!!!

I didn't get that notice yet - going to download now! Wohooo! Downloading now. Aw yaaaa, I can almost taste 2.0!
[Upgrading, Modifying and Unlocking] Zacpod:
The Apps2SD image does a pile of things. You can read about it on my website, or on the forum post a page or two back. It's a rooted image, with the broken terminal.apk already deleted for you, plus a bunch of other stuff that make working on the command line a lot easier.
[Upgrading, Modifying and Unlocking] routehero:
Here's the list of directories. It's the full kernel plus what you see below.

Edit: Don't find any mention of libril in there. The radio search reveals wlan stuff.

find . -type f -exec grep -H radio {} \;
find . -type f -exec grep -H libril {} \;

./kernel/
./external/dbus
./external/elfutils
./external/yaffs2
./external/bison
./external/emma
./external/genext2fs
./external/expat
./external/webkit
./external/qemu
./external/wpa_supplicant
./external/clearsilver
./external/elfcopy
./external/ppp
./external/libpng
./external/esd
./external/e2fsprogs
./external/iptables
./external/grub
./external/dosfstools
./external/tcpdump
./external/aes
./external/jdiff
./external/bluez
./external/libpcap
./external
./cts/tools
./cts
./dalvik/libcore
./dalvik
./vendor/qcom
./vendor/brcm
./vendor/lge
./vendor
./system/extras
./system/wlan
./system
./prebuilt/common
./prebuilt/linux-x86
./prebuilt/darwin-x86
./prebuilt/windows
./prebuilt/android-arm
./prebuilt
./packages/apps
./packages
./frameworks/base
./frameworks
[Upgrading, Modifying and Unlocking] semaan123:
When I run adb shell and I get # does that mean the phone is rooted? Or is there any other method to ensure it is rooted.
[Upgrading, Modifying and Unlocking] Zacpod:
Hrm. Is it somewhere in the prebuilt section maybe? 5 mins left on my download and then I'll be poking around with it too. :)

I think first thing I'll do is just a straight make to see if it actually builds a valid/bootable image.
[Upgrading, Modifying and Unlocking] Zacpod:
Ya, that's the first step. You have root access from ADB, but you'll still be a user from terminal or any other app. You need to install a modified su and the superuser.apk. There are instructions further back in this thread - maybe around page 15-20... Not sure where. You can also just go to my site - rooting instructions are the third post down right now.
[Upgrading, Modifying and Unlocking] Zacpod:
Or perhaps it's something that Rogers put in place?

Poking around in the source now... May try merging it with the aosp tree to see what frankenstein emerges, lol.
[Upgrading, Modifying and Unlocking] Zacpod:
Lol!

./GW620/packages/apps/Quake/quake/src/QW/client

Quakeworld client included! That doesn't seem to be on my phone anywhere tho... odd. ;)

Anyhoo... I've moved everything from the GW620 folder in to the aosp tree and have started a build. Finger's crossed!

fyi, you'll need to do a "LGE_MODEL=eve make" or you'll get some weird-ass errors.

I'm having some issues with headers, but that's a normal part of building on OSX. Wading thru them now - hopefully I'll have something bootable before I sleep tonight. It may not be any better than our previous efforts at getting 2.0 going, but we'll see. :D
[Upgrading, Modifying and Unlocking] enkoopa:
Just got my account too! Where did you guys find it?

Cmon, you're killin me! :) I got this CPC site open and it is confusing as hell, did you get it through there or some other place?
[Upgrading, Modifying and Unlocking] Zacpod:
Ya, it's a waaay confusing site. It just showed up for me in one of the sections. It may have been manually added to our profiles by someone.

Here's the link. :)

GW620 Source Code
[Upgrading, Modifying and Unlocking] CyrilLD:
Great !!

I wish an happy new year 2010 for everybody, and a lot of success for updradiging this great phone to 2.0 !

@Zapcod, I have found your board "Zac’s Pad" before reaching the end of this post... The LG's Firmware is downloading now :D
[Upgrading, Modifying and Unlocking] Zacpod:
Well, it was worth a try, but simply copying the GW620 source in to the existing AOSP tree just resulted in a lot of link errors. I think we'll have to be a little more selective about which bits of the source we bring in to the AOSP. Too tired to do anything else tonight though. Maybe tomorrow I can try taking a diff of the kernel against a stock 2.6.27 and then applying that againt 2.6.29. Hopefully that will result in a current kernel that will run properly against a stock AOSP.

Also, Routehero, I had a look at the AOSP's default rild, and it will only work right in the emulator by the looks of things. And it seems to be under the Apache license, which iirc means that LG doesn't have to give us the source. :(

We may be back to trying to get the existing rild to work, or maybe finding another rild that will run against our radio. :s

I'm no expert though, so hopefully I'm mistaken.
[Upgrading, Modifying and Unlocking] routehero:
In my mind, here's the current state of the union:

- we have their kernel source now

- we have the ability to create a working 2.0 image (sans radio and wifi at the moment)

- the radio process (rild) works to a point, and then fails.

- wifi module loads from stock firmware in to 2.0 image, just need to get userland wpa_supplicant working properly

For wpa_supplicant, you have to make a few small changes to compile it in Android:

1) ensure /usr/src/mydroid/external/wpa_supplicant/.config has CONFIG_DRIVER_WEXT=y

2) ensure /usr/src/mydroid/external/wpa_supplicant/Android.mk has WPA_BUILD_SUPPLICANT := true

3) ensure /usr/src/mydroid/build/target/board/generic/BoardConfig.mk has HAVE_CUSTOM_WIFI_DRIVER_2 := true

4) rebuild source and you should now have a 2.0 wpa_supplicant.

For the radio, I'll have to get back to debugging. I was hoping that LG would be somewhat more lax in what they released, but hope is obviously not a strategy.

The way I see it, is we'll need to make some changes in the framework that allow the 1.5 radio functions to work in the 2.0 base. I might be missing something obvious here, so someone with greater debug-fu might have greater success here. I can debug in win32 fairly easily, but I've got to start from scratch with gdb if we need to get to that level.

Edit: In the worst case, since we have their kernel source, we can at least buff up the stock 1.5 image with some new enhancements to the kernel, not the least of which is iptables.
[Upgrading, Modifying and Unlocking] Adam620:
Very nice to see that you guys finally managed to get a hand on LG's sources.

Crossing fingers about how sufficient they'll be in getting a working AOSP build...
[Upgrading, Modifying and Unlocking] enkoopa:
Got the source.. they sent it to me after a bit!
[Upgrading, Modifying and Unlocking] Zacpod:
Ya, I think that's going to be the first thing I do as well. I've brought the kernel sources in to the aosp tree and pulled the config.gz off the phone. Make menuconfig showed all the proper flags in place - sweet! Building it now to ensure it's good before I start messing around. :)

Odd - I can get in to the hidden menu no problem. I did have some issues getting superuser.apk to work properly when I was first making the image (it turned out that replacing toolbox with busybox wasn't such a great idea. Toolbox has some stuff in it that busybox doesn't provide, and that was causing superuser.apk to be unable to communicate with su.)

But if you didn't replace toolbox then the problem may be simpler - try deleting /data/davlik-cache/*Superuser* and /data/app/superuser.apk and then rebooting. If you had Superuser.apk installed in /data/app before you installed the apps2sd image then you probably have 2 odexes in /data/davlik-cache for superuser.apk, since I put it in /system/app on the apps2sd image.
[Upgrading, Modifying and Unlocking] Zacpod:
Bah, been trying off and on all day to get it to compile in OSX but it just doesn't wanna go. I'm going to have some dinner and then reboot in to Linux and try from there.

Maybe we can patch the kernel up to 2.6.32.3, or whatever the latest stable is that works for msm.
[Upgrading, Modifying and Unlocking] Zacpod:
Yep. Building in Linux worked flawlessly! I'm now booted up in a kernel that I compiled. Time to add in some ipchains goodness!

I had to jump thru a few small hoops.. Mostly just making links to the precompiled arm toolchain to somewhere in the path.

e.g.

cd ~/bin
ln -s ~/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.3.1/bin/* .

I also had to modify one of the source files slightly. It was throwing a __ARM_CC undefined error. There was a small typo in the file. Changed it to "defined(__ARM_CC)" and all was well. :)

Oh, also should be noted that it will NOT build properly with arm-eabi-4.4.0 - just save the headaches and use 4.3.1. :)
[Upgrading, Modifying and Unlocking] DJ_Spray:
Dude that is some great news!
[Upgrading, Modifying and Unlocking] Zacpod:
Woot! Managed to get netfilter enabled. The wifi tether app now starts without complaining, and claims to have started the WAP, but I can't see it from my laptop. Ah well - I think a self-compiled kernel is enough victory for the day. I'm off to bed. :)
[Upgrading, Modifying and Unlocking] AlkaYoda:
Nice job !

Thanks a lot for your work !
[Upgrading, Modifying and Unlocking] enkoopa:
I don't think there's anything in the Wiki about removing rogers contacts...
[Upgrading, Modifying and Unlocking] Zacpod:
There were some links to the forum posts about it. I just removed them.
[Upgrading, Modifying and Unlocking] gpmoo7:
The link is not valid

[url]http://www.4shared.com/get/149810989..._eve_dump.html[/url]

(same in the wiki page)
[Upgrading, Modifying and Unlocking] Zacpod:
Hrm. Looks like it's a corrupt link - it's missing some stuff in the middle.

Regardless, you can dump your own phone now - just reboot in to fastboot mode and use nandroid to back up all the data. Voila - full set of img files for your enjoyment. :)
[Upgrading, Modifying and Unlocking] Zacpod:
Got the kernel patched up to 2.6.27.43, and it's compiling OK.

Took a while to get the patch applied - lots of rejected diffs and mispatches that had to be manually applied or modified. All I can say is Thank Gnu for the meld tool!

The kernel booted up fine on my phone - even included all the generated modules in the boot.img. Used to just have wireless.ko. I did have to copy the new wireless.ko module to /system/lib/modules and reboot before wifi worked, but everything else is flawless. :)

The bonus is that it's now a bog-standard 2.6.27.43 kernel with the LG changes. Hopefully it'll be fairly straightforward to get the 2.6.3x.xx patches applied to this now. :)

Sadly, wifi tethering still doesn't work. Not too worried about that till we're running a 2.6.3x tho.
[Upgrading, Modifying and Unlocking] jelani101:
My lg eve serious problem

just got an lg eve too many invalid pattern locks and i cant unlock it with the google account for some reason . how can i fix this issue or reset the phone or something
[Upgrading, Modifying and Unlocking] Zacpod:
Download the Android SDK, Google for Fastboot and download it from HTC. Remove the battery. Unplug from USB. Plug in to USB. Wait 2-3 seconds till the screen brightens slightly and then hold spacebar. Screen should say "Fastboot 0.5 blahblahblah." Type \path\to\fastboot\fastboot -w

That will wipe all userdata off the phone and should restore it to factory defaults.

In the future please leave this thread free for the discussions about getting Android 2.0 running on this beasty. There is a new forum dedicated to the GW620 over at AndroidNetwork.org that is better suited to helping with general questions. Thanks in advance. :)
[Upgrading, Modifying and Unlocking] Zacpod:
Bloody chunder. I've been trying to get the LG changes merged in to a 2.6.32.3 source tree and it is just not working at all. :(

I'm not a kernel expert, so I'm sort of flailing around in the dark here. I know enough to config a kernel for specific hardware and get it running, but actually messing with the source is new to me. Soooo - sorry if any of these seems daft or naive... Like I said, I don't really know what I'm doing. :)

Things I've tried:

Downloaded the 2.6.30.xx patch and tried applying it to the working 2.6.27.43 tree. Total fail.

Downloaded the full vanilla source for 2.6.27.43, took a diff between vanilla and the working 2.6.27.43 with lg mods, and then tried to apply that diff to a 2.6.30 and a 2.6.32. Better, but still an utter fail. Waaay too many compile errors for me to work thru.

So then I thought, Hrmmm... Maybe I can just manually copy the arch/arm/mach-msm bits in to a current kernel. I did so, and... Fail. Tonnes of compile errors. Fixed a few, but I think I'm barking up the wrong tree.

So now I'm thinking that maybe I don't want to be working off a vanilla source - I should try using the msm branch of aosp. (Duuuh!) It's downloading now. Once it's down I'll see if copying the arch/arm/mach-msm section over does the trick.

I'll keep y'all posted. :)
[Upgrading, Modifying and Unlocking] DJ_Spray:
I keep a chrome tab opened on this page... following the news very close!