yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] CyrilLD:
Héhé !! I found how to change the 2 variables LINUX_COMPILE_BY and LINUX_COMPILE_HOST :D

--> change values in kernel/scripts/mkcompile_h instead of kernel/include/linux/compile.h (replaced each time you compile)

This is absolutely useless but looks great in the kernel revision info :p
[Upgrading, Modifying and Unlocking] gpmoo7:
Thanks but I don't have the phone. I'm just watching this thread because some non-XDA friends of mine have this phone.

I see that you're trying to get Android 2.0 to work on this device but why don't you start by creating a port for the CyanogenMod which is a really good Android ROM and bring Android 1.6 + some of Android 2.0 ... and I beleive it should be easier.

The CM Wiki contains a page for that and it looks "easier" than create a full ROM: http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
[Upgrading, Modifying and Unlocking] DJ_Spray:
not too bad of an idea.....
[Upgrading, Modifying and Unlocking] harnish:
App2SD & LG's libril

As for the hidden menu, it was only on the first boot of the newly flashed apps2sd image and only if I had wiped the userdata as well first. I think the hiddenmenu does an initialization and needs a reboot to actually launch (I believe it runs in the bg all the time ...)

As for the other issue, the problem is with the permissions on su. After accessing my eve with my root adb shell, I ran these commands and su now works from the Terminal Emulator (and I assume a non-rooted adb shell)

chown root /system/bin/su
chmod 4755 /system/bin/su
chown root /system/xbin/su
chmod 4755 /system/xbin/su

On the Apps2SD image, su is owned by uid 501, not uid 0. And I think changing the owner wipes out the setuid bit so I reset it. I'm guessing uid 501 is system.

And with regards to 2.0, if I understand the issue, the version of the libril and rild we have on the Eve is not compatible with the ril for 2.0 (someone has tried just copying them over IIRC) and LG compiled the radio drivers into the ril? I can understand LG being reluctant to release that code, it's probably someone else's IP. With that said though, I can't see them having trouble giving us _binary_ files. Has anyone asked opensource @ LG if the would just recompile their ril library for 2.0.1 or 2.1 and give us the binary? I mean, it should probably only take less than an hour for someone with the source. I mean, if they say no, we are no further back than we currently are.
[Upgrading, Modifying and Unlocking] enkoopa:
Hmm, we could make a request on the CPC site to see if they would do that...
[Upgrading, Modifying and Unlocking] Zacpod:
I think the Eve board may be a little too different from the 32a/32b boards that CM targets. (e.g. no wlan.ko for wireless - the eve uses wireless.ko) We'd still have to roll the LG kernel mods in to CMs kernel - it wouldn't be a simple matter of pulling the config.gz off the running kernel like the wiki suggests. Still, it's worth a try. I'll give it a go later today and let you know what I end up with.
[Upgrading, Modifying and Unlocking] litui:
CyanogenMod

Patching a kernel over CyanogenMod isn't a big deal as it's what we do to run CyanogenMod on the 32A/EBI1 devices already. The bigger issue is keeping the kernel versions similar enough to support the correct functionality I think. I've been wanting to attempt this but do not have my own LG Eve to test on. Come to #cyanogenmod on freenode and I'm sure some people there would be willing to give you pointers on where to start.
[Upgrading, Modifying and Unlocking] CyrilLD:
Well done Zacpod, I am in this way too and yersterday night, I completed the step 1 of your list : looking for diffs between stock and LG trees, boths in version 2.6.27.

I also looked at diffs between the 2 .config files (LG get from my .gz an stock from msm_defconfig) to find all LG's drivers and specific declarations. It was just for looking ...I saved nothing but found all the EVE_ defines, SHARP proximity detector, etc...

Regarding CyanogenMod, I don't think it's the best way for us, and the difficulty of merging the 2 kernels will not be easyer than what we are trying to do there...and just in my case, I don't look for a mod but for an upgrade to the last version of the entire operating system !

Perheaps I coul'dnt work a lot on the merge this weekend, but I'll look for news ;)
[Upgrading, Modifying and Unlocking] Zacpod:
I'm changing tacks again. I don't think the method I outlined is going to work. There are too many changes that LG made, and too many changes between 2.6.27 and 2.6.29. Even if we did get all the patch rejects merged in to place I don't think the results would actually run - or even compile.

I'm now thinking about basically starting from scratch - taking the hardware specs and folding just the minimum required drivers in to the kernel. I've started with just taking the arch/arm/mach-msm/board-eve.c and it's dependencies from the old kernel. If I can get that compiling and booting we can start pulling in the other hardware drivers. That way we can keep the kernel as stock as possible. LG made soooo many changes!

Been a frustrating day. Off to sleep now.
[Upgrading, Modifying and Unlocking] enkoopa:
Do you want me to put a request in to see if LG will provide us with some modules compiled against 2.6.3x? If so, what modules? wireless.ko and ril?
[Upgrading, Modifying and Unlocking] Zacpod:
Worth a try - it's just rild that we need.

2.6.29 is the current, and 2.6.32 is the soon-to-be current...
[Upgrading, Modifying and Unlocking] Zacpod:
Ok, this is working better. I couldn't get the board-eve.c stuff folded in directly, but 2.6.29 does have a QCM7201aSurf eval board config - I'm hoping that'll work for the base hardware. I'm currently bringing in the graphic subsystem, and am making good headway. Still lots of errors to fix buy they're the small manageable kind that don't make me swear and pull out my hair.

Right now the kernels I'm building with this don't appear to boot - but appear is the operative word. Until I get the display going I don't really know what it's doing, lol. And of course, LG is using it's own Innotech 'Moldless" lcd screen, so there aren't drivers for it in the main msm tree.

I'll let you all know as I progress. I have high hopes that this approach will work. It's a lot more work, I think, but a lot less guesswork, so I think it'll work out in the end. :)
[Upgrading, Modifying and Unlocking] Zacpod:
Coming along nice - I hope to have the display driver working by the end of today. I've also switched over to integrating with Kernel 2.6.32 instead of 2.6.29. If I'm going to do all this work I don't want to have to do it again in a month or two when 2.6.32 is the new standard. :)

Edit: Skip that. I can't figure out how to even get the display driver to show up in 2.6.32. It only wants to show me the built in drivers - edited the Kconfig and Makefiles, but they still don't show up. I think it has something to do with what appears to be a new way of handling platforms, so the Framebuffer doesn't realize that it's allowed to display. That's just a stab in the dark though. Either way, I'm going back to trying to make 2.6.29 work.
[Upgrading, Modifying and Unlocking] Zacpod:
Blarg. Good news, and bad.

The good news is that I got the display driver compiling and linking! Yaaay!

The bad news is that the the kernel still won't boot. fastboot boot boot.img just shows "booting linux..." and the device hangs. That's with the kernel set up for the Halibut7201surf development board. *sigh*

Looks like I'll have to try to get board-eve.c folded in to the kernel. I'm getting a headache just thinking about it. Ugh.
[Upgrading, Modifying and Unlocking] Zacpod:
Display driver changes

Here's a diff of the changes I made to the stock msm 2.6.29 tree to get the Eve's video driver folded in to the kernel in case anyone's interested.
[Upgrading, Modifying and Unlocking] Zacpod:
Down to 1 page of errors during compile. It's getting tricky though.. Some of these errors are related to devices that I haven't folded in yet - like the camera. I'm hesitant to start bringing all the devices in that I need as I'm trying to keep things as simple as possible until I can get a bootable kernel. I may just comment out the errors with a note to revisit..

Edit: Done with the compile errors, and on to the linker errors. The board definition file (board-eve.c) is folded in to the tree and compiling. It's still not linking, but there's only a few errors to go!

[sarcasm]Can't wait to get it built so I can see my device hang at "booting linux" again.[/sarcasm] ;)

Seriously though. Finger's crossed - hope it boots!

No wifi, probably no camera, definitely no radio... But hopefully a 2.6.29 kernel. :)
[Upgrading, Modifying and Unlocking] Zacpod:
Linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to bringing in more code from LG, leads to compile errors, leads to linker errors lead to....

Sleep. I'll continue tomorrow. :)
[Upgrading, Modifying and Unlocking] enkoopa:
Damn. Looks llike you had a productive weekend :) nice work! Ill see if they'll compile the module for us against .29
[Upgrading, Modifying and Unlocking] Dennijr:
thats a lotta boots :p
[Upgrading, Modifying and Unlocking] Zacpod:
Lol, ya, especially for something that won't actually...boot!

Well, I'm making headway. Hard to tell how close I am to being done, since I fix one error and 2 more pop up. I fix those and then I get a link error. I fix the link error, and I get a compile error. Etc, etc, ad nauseum.

But I am making headway. I think I'm getting close. The **** I'm debugging now is at a pretty low level, so I'm hoping that means I'm close. :)

However, in hindsight I think I should have started with the source tree that these guys maintain instead of the stock Android tree. I think the CodeAura tree is what LG started with. Hell, maybe if I'd used it first the original diff approach might have worked!
[Upgrading, Modifying and Unlocking] Dennijr:
dont beat yourself with that last fact, atleast you have continued to progress, and even if it was possible that the harder route was taken, you have learned more than a bunch from it, no?
[Upgrading, Modifying and Unlocking] Zacpod:
Oh, I'm not beating myself up, and I've learned a PILE about how the kernel build system works. Can't say I understand the code I'm working with overall, but I understand the bits I'm messing with enough - I hope. Regardless, I'm having a blast. :)

If, after rolling all this stuff in to the kernel it *still* doesn't boot then I'll have a look at the CodeAura tree. Maybe my lgchanges.diff file will apply cleanly to it. But we'll cross that bridge when it comes. For now, I'm off to fix more linking bugs.
[Upgrading, Modifying and Unlocking] Zacpod:
Woot! Ok, minor victory for tonight - the board code is all compiled in and linking fine! I'm still getting a pile of unresolved references, but they're coming when the linker is trying to build zImage - until tonight it was never getting that far. I think it's mostly for auxilary drivers, like the kb etc. We'll see how far I get tomorrow. :)
[Upgrading, Modifying and Unlocking] Dukeraoul911:
nice! seems like you're in the right way. keep us updated
[Upgrading, Modifying and Unlocking] DJ_Spray:
dude!!!!!! your the man!!!
[Upgrading, Modifying and Unlocking] CyrilLD:
Great work !! congrats ! :D
[Upgrading, Modifying and Unlocking] enkoopa:
I've put in a request from the Linux distributor at LGE for the rild sources, and/or an rild module compiled against 2.6.29...
[Upgrading, Modifying and Unlocking] Zacpod:
Excellent! Hope they at least give us the compiled version, though the source would be amazing. I'll be very surprised if they give us the source - it's not required under the licence, and as RouteHero said, LG would probably be breaking a NDA with the radio manufacturer if they gave us the source. Still, it's worth a try. :D

I feel like that cartoon where someone is eating a plate of spaghetti. They start sucking up one noodle and that noodle just keeps coming and coming and coming until the whole plate is empty.

I've now got the keyboard, the home/back/menu keys, the fbconsole, the error handler, the backlight, the keyboard backlight, and part of the camera brough it. I'm about half way thru the link errors, so hopefully in a few hours I'll have something that will fully link - and hopefully boot. :)
[Upgrading, Modifying and Unlocking] Zacpod:
Fail.

Link errors are all resolved and the kernel builds ok.

It still won't boot.

Just hangs at "booting linux..."

Grrrr.

Edit: Here's both my patches. Unzip and apply them in order to a stock 2.6.29 tree ("patch -p1 <patch>" or similar) and you should end up with the same headache I have. ;)

I'm walking away from this for a bit. I'll be back tomorrow - maybe I'll try to take a diff between the CodeAura 2.6.27 tree and the LG tree, and then apply it to the CodeAura 2.6.29 tree. Or maybe I see if I can figure out how to at least get an error message out of the device when it's trying to boot this 2.6.29 kernel. I dunno yet.
[Upgrading, Modifying and Unlocking] CyrilLD:
Hello,

I just finished the same things, but with the CodeAurora kernel 2.6.29b used as a working base.

All LGE code have been merged, a ton of compile and/or linking errors cleaned, all specific drivers activated...and a beautiful "booting linux..." :(

I think I 'll make a break with it... tomorrow I'll go back in compilation !
[Upgrading, Modifying and Unlocking] Zacpod:
Crap.

I don't know what we're missing. Maybe it's a bad default that's being brought in to our .config when we do the first "make menuconfig" on the new kernel? I have a busy day at work today and can't look at this till later tonight, but I'll compare the two .configs to see what the differences are when I get home. Maybe we just need to disable the "HANG_AT_BOOTUP_TO_FRUSTRATE_HACKERS" flag, lol!
[Upgrading, Modifying and Unlocking] Dukeraoul911:
lol I agree :)
[Upgrading, Modifying and Unlocking] Zacpod:
Crap-spackle. I just went thru the whole config line by line and didn't see anything new in the 2.6.29 config that would cause the kernel to not boot. :(

Sooooo... Anyone have a multimeter and know how to use it? I'm wondering if the two contacts behind the battery cover are debug leads to tty3 - That would help us immensely, as we could see the kernel messages before it loads the display driver, and hopefully see why it's failing to start.

I suspect that they're just charging leads for the battery though.
[Upgrading, Modifying and Unlocking] CyrilLD:
I can't see the 2 contacts you're talking about but... under the sim-card holder, there are 5 little pins. It could be a serial port...finger-crossing. :rolleyes:

I make some electronic and robotics for years ago and I'm equipped with multimeter and all tools needed in debugging microcontrollers. (a serial port adapter in this case).

I hope I could determine the function of these 5 pins this weekend, and connect them properly to a serial port on my computer.

Regarding the kernels merge, an other way we didn't try yet :

- Take a diff between LG's 2.6.27 and stock 2.6.27

- Patch it into a stock 2.6.27, compile with no errors and immediate boot must occurs...(optional)

- Patch it to the 2.6.27 Aurora branch --> Perhaps a little more work, because Aurora have done a lot of optimizations for the Qualcomm processors, and more... If this patched kernel can compile and boot fine, I think it's a first good step.

After this, the idea to get a full 2.6.29 Aurora kernel working (the version I patched who compile but no boot) could be to patch by hand Aurora's evolutions from 27 to 29...:rolleyes: hard and long work I agree... but with some steps, testing, booting, merging again others files, re-compiling, re-testing...etc.. we could achieve this goal.

What do you think about this ?

Zacpod: If we want to try this, we should use a common repository to merge our work and so divided the work by 2. I have some SVN servers available to do this...

Good weekend to everybody ;)
[Upgrading, Modifying and Unlocking] Dukeraoul911:
Just remove the back, you don't have to remove the battery, there are 2 connectors at the bottom.

EDIT: I checked at pinouts.ru but found no info on those pins

There are also 8 pins above the sim card, I don't know what they are for..

ZacPod, you talked earlier about a guy that disassembled his LG. Could'nt we find any info about where the pins are leading? I also wonder if the JTAG is accessible and if it could be used to debug the phone in this case.
[Upgrading, Modifying and Unlocking] enkoopa:
LGE said they can't release the source as it's proprietary license for Qualcomm, as expected.

I hit them back asking if we can get a compiled binary.. we'll see what they say!
[Upgrading, Modifying and Unlocking] CyrilLD:
I was thinking on it too yesterday... the link is on the wiki page and you must register on the android overdrive forum to view the images. There is nothing interesting there because pictures are low-res, and I can't view any usable connector...

It's the MicroSD card slot... no serial port here but perhaps an SPi (1-wire bus)
[Upgrading, Modifying and Unlocking] CyrilLD:
OK, I got a serial output !!

This is when I try to boot my last 2.6.2ç kernel with the command "fastboot boot boot_29_4.img"

This looks the fastboot output, who receive the img when boot it, but no the kernel itself.

I will try with a know-working 2.6.27 this afternoon to compare the 2 booting CmdLines and look if the kernel init sequence is outgoing to the same serial port.

Oh... and the serial port is located under your sim-card as I expected, the TX line is the middle-one of the 5.
[Upgrading, Modifying and Unlocking] Zacpod:
Amazing!!!!

You should be able to change the "console=/dev/null" part of the kernel command to shunt the output to that serial port. e.g console=/dev/ttys3

From what I saw in the kernel source, I think ttys3 is the 'debug' serial port. You should be able to test by booting up the phone and echoing text to each /dev/ttys to see which one gives you output.

I assume you used a 3.3v converter? I may have to figure out a way to clip my usb-3.3v serial converter on there...
[Upgrading, Modifying and Unlocking] Dukeraoul911:
Wow this is great!

Yes I also d like to know if you used any level converter on the tx pin
[Upgrading, Modifying and Unlocking] CyrilLD:
sorry guys ...I have a lot of work this week and I can't work too much on debuggins our phone.

Here are some infos :

- I did'nt use any level converter but a device already working on 3.3V : an Arduino: This small board (version with removable Atmega 328 chip) have an FT232 chip (usb<->serial) on-board, and removing the micro-controller from its socket makes the board a simple serial port converter !

- Computer-Side, I used the Arduino Serial Monitor (included in the IDE) but any serial monitor will work. Baud-rate is set to 115200 bauds.

Reading the output :

While both devices are powered by USB (on a little hub in my case), the ground is the same. There is only need to make contact between the TX pins.

Some test I made with no success :

- Setting UART DEGUC (not the full config name sorry)to 1, 2 or 3 in the kernel menuconfig (instead of NONE) --> nothing about the kernel boot in the console

- Set the kernel cmdline to console=/dev/ttys3 or others possible ports ( /dev/ttys2, /dev/ttys1, ttyMSM2, etc...)
[Upgrading, Modifying and Unlocking] Dukeraoul911:
Hey!

I'm going to use this arduino board too for a motorbike alarm.

I just started learning this electronic stuff 2 weeks ago .. that's a good coincidence ^^

I should order it soon, as well as a beagle board to have embedded linux on it. Just for the info this board (has ARM Cortex-A8 uC) and can embedd android eclair, they ported it :)

That should be good, I'll be able to play with it and maybe try to debug the phone :D
[Upgrading, Modifying and Unlocking] Zacpod:
Thanks for the info CyrilLD. I think I have a USB-3.3v serial around here somewhere. I'll see if I can get some kernel messages out later this week. It's been a busy weekend, and looks to be a busy week, but I'll hopefully have some time on Tues and Thurs.
[Upgrading, Modifying and Unlocking] Grank:
That's brilliant! I have an Atmega328 arduino sitting on my desk right now that I'm not doing anything at all with... nice to know that I can easily pin in a usb <-> serial any time I need one ;)
[Upgrading, Modifying and Unlocking] mbee47:
I just looked through the kernel src and noticed there are no config file. Has anyone dumped this via /proc/config.gz or similiar if they are active?
[Upgrading, Modifying and Unlocking] CyrilLD:
The only way getting the .config for the LG kernel is to get it from /proc/config.gz

I'm not on my computer where I worked on it and I can't upload it for you now but it's easy tu get it from your phone (with adb pull for example)

I don't know if "make msm_defconfig" would set correctly all the defaults config flags , but perhaps it will work too.
[Upgrading, Modifying and Unlocking] mbee47:
Ok thanks for the information, I dont have this phone yet but im interested to test if its possible to get a newer kernel running. If anyone got a kernel config I would be really glad.

Regards,
[Upgrading, Modifying and Unlocking] Zacpod:
Here's the one I've been using. It's not the stock config - I've added ipchains and some other small stuff, but it works. :)
[Upgrading, Modifying and Unlocking] Trent1026:
Line 10 of lg eve root

Hey zac im tryin to root my lg eve and i got everything but i cant get past line 10 on the commands of ur root earlier on in this thread i see buddy said ur missing a > in line 10 but i dont know exactly where it goes if u could help me out id be forever in ur debt its such a headache hahaha im running windows vista please help
[Upgrading, Modifying and Unlocking] Zacpod:
adb shell cat /system/xbin/su > /system/xbin/su.original

In the future please try to keep this thread clear for discussions of the ongoing effort to get the 2.6.29 kernel + Android 2.0 working on this device. For all general questions please use the dedicated forums at AndroidNetwork.org

Thanks :)
[Upgrading, Modifying and Unlocking] mbee47:
Thank you!
[Upgrading, Modifying and Unlocking] enkoopa:
Man, I've been having a lot of issues lately with my phone. Freezing and what not.

Anyways, tonight something very new. The wifi module segfaulted. So I got a console screen that came up, right from linux, showing registers and what not. It said push Volume up to view memory, volume down to log the core and reboot. So I did that.

If the serial logging turns up fruitless, might be a different angle.. force the phone to crash somehow and get logs dumped so we can see what's going on.
[Upgrading, Modifying and Unlocking] ouinouin:
usb tether

please consider adding usb tether facility in the kernel, by adding usbnet driver,

so we can do gw620>usb_cable>computer>internet.

all the bluetooth file transfer software are not working, maybe things to add.

the device doenst seems to support ad-hoc mode, is someone interrested by looking it ?
[Upgrading, Modifying and Unlocking] Danteyoon:
Hello, I am a noob tweaker and I bricked my Eve. It seems to cycle through "ANDROID" over and over. ANd I followed this instruction.

After inputing everything in part 1, it says in broken code, @#%%^ URL #^$$ File and prompts me to input a URL or something. So I put the file URL of the provided KDZ file.

It seemed to work then it gave me page error...

and

STEP_TYPE-ENV_ERROR...

Could you please HELP?? :'(