• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Unlocked bootload and CM10

Not really. There second e-mail was asking for my error log. I responded yet again that there is no error in the compile. The zImage will not boot. I've asked again for info on what GCC they are using, but I doubt I'll get an answer from them.

the readme included with the src should say. I think it was 4.3.3 I used, may have been 4.6 included with CM10, dont recall atm, I got something to compile with 4.6 tho. lol
 
Upvote 0
Latest response I received from them. The readme says 4.4.3.

[FONT=&quot][/FONT][FONT=&quot]We will deliver your request to our dev. team to check it.[/FONT]
[FONT=&quot]As we know, we use GCC 4.3 or 4.4 not 4.7.[/FONT]
[FONT=&quot]We will check GCC version again.[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Please wait for some times to receive result from dev. team.[/FONT]

I linked them to the Iproj kernel and told them point blank that the source I have boots the lucid, but is missing the display drivers. I guess it's back to playing the waiting game and seeing what else I can find out there for possible kernels to steal a display driver from.
 
Upvote 0
Latest response I received from them. The readme says 4.4.3.

[FONT=&quot][/FONT][FONT=&quot]We will deliver your request to our dev. team to check it.[/FONT]
[FONT=&quot]As we know, we use GCC 4.3 or 4.4 not 4.7.[/FONT]
[FONT=&quot]We will check GCC version again.[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Please wait for some times to receive result from dev. team.[/FONT]

I linked them to the Iproj kernel and told them point blank that the source I have boots the lucid, but is missing the display drivers. I guess it's back to playing the waiting game and seeing what else I can find out there for possible kernels to steal a display driver from.

the kernel src for the lucid should have em if not for all 3 840's. They are also prolly in the lge dir in the root of the src dir just copy of the cayman shyt and and look at the make & kconfig files for what lines might be need to be added to the same file in the iproj src. Might be some defines in the board file needed too along with other places too.

I am working on adding em for the connect but not got it to compile yet.
 
Upvote 0
the kernel src for the lucid should have em if not for all 3 840's. They are also prolly in the lge dir in the root of the src dir just copy of the cayman shyt and and look at the make & kconfig files for what lines might be need to be added to the same file in the iproj src. Might be some defines in the board file needed too along with other places too.

I am working on adding em for the connect but not got it to compile yet.
I was able to compile it with that method after about 20 builds, but you end up changing files in the LGE board setup, display drivers, backlight drivers, and a few other areas. I still could not get it to boot either. On a weirder note, LG is still chatting with me and now wants to know the exact steps I'm doing to compile the code and how I'm installing it once I have the boot.img. I'll keep everyone updated in case I do get something positive out of it.
 
Upvote 0
I was able to compile it with that method after about 20 builds, but you end up changing files in the LGE board setup, display drivers, backlight drivers, and a few other areas. I still could not get it to boot either. On a weirder note, LG is still chatting with me and now wants to know the exact steps I'm doing to compile the code and how I'm installing it once I have the boot.img. I'll keep everyone updated in case I do get something positive out of it.

they are prolly taking notes with the intentions of figuring out how to make it even harder lol
 
Upvote 0
And with this, I will never be buying another LG phone. This is now considered dead in the water. I may pick up a lucid this summer to play around with if I find a cheap one on ebay or swappa just because I'm stubborn like that.

"[FONT=굴림][FONT=맑은 고딕]Thank you for your interest about our mobile phone. [/FONT][/FONT]

[FONT=굴림][FONT=맑은 고딕]“[/FONT][FONT=맑은 고딕]We received your request on LG Open Source Code Distribution site([/FONT][FONT=맑은 고딕]http://opensource.lge.com[/FONT][FONT=맑은 고딕]). [/FONT][/FONT]
[FONT=굴림][FONT=맑은 고딕]This site is just for providing source codes of FOSS(Free and Open Source Software) we have used in our product.[/FONT][FONT=맑은 고딕]”[/FONT][/FONT]

[FONT=굴림][FONT=맑은 고딕]We received response from Open Source department.[/FONT][/FONT]
[FONT=굴림][FONT=맑은 고딕]They said that GPL doesn’t have terms which are guaranting boot with different bootloader.[/FONT][/FONT]

[FONT=굴림][FONT=맑은 고딕]It is very hard to support multiple bootloader with the same kernel source code.[/FONT][/FONT]
[FONT=굴림][FONT=맑은 고딕]And we don’t miss any source codes while we upload the newest kernel we used.[/FONT][/FONT]
[FONT=굴림][FONT=맑은 고딕]Please consider this situation.[/FONT][/FONT]

[FONT=굴림][FONT=맑은 고딕]We hope this information will help you. [/FONT][/FONT]

[FONT=굴림][FONT=맑은 고딕]Thank you.[/FONT][/FONT]
[FONT=굴림][FONT=맑은 고딕]Sincerely yours,[/FONT][/FONT]

[FONT=굴림][FONT=맑은 고딕]LGE MC Company Open Source Code Distribution Center"[/FONT][/FONT]
 
Upvote 0
How could this Bootloader be unlocked? If it does get unlocked there would be a possibility of CM9 or other vanilla 4.0.4 based roms. Does anyone know how the spectrum, Optimus G or any other LG ICS bootloader?


The boot loader wasn't the problem (because the gingerbread boot loader was unlocked), the device would boot cm10 but the video drivers were for the spectrum, which has a larger HD display. The video drivers supplied by lg for the lucid won't work with the source for the cm kernel either, so someone is going to have to create or modify the driver to support the lucid s display.
 
Upvote 0
Hello all, I have been lurking this thread for a few weeks, and have made an account in the hopes of contributing. I have a lucid for testing and have enough C experience (but no kernel experience at this time) to give this kernel a shot.

I was able to download and build the LG ZV7 kernel, but how can one turn the zImage into a flashable ZIP file for recovery? Also, which kernel source is the code that builds but produces no video, and which exact ROM boots the lucid? Sorry if I'm asking stupid questions, but I want to be doubly sure, as this lucid is a replacement for the one that died last week during an OTA and I will have a tough time getting it fixed if it breaks.
 
Upvote 0
Hello all, I have been lurking this thread for a few weeks, and have made an account in the hopes of contributing. I have a lucid for testing and have enough C experience (but no kernel experience at this time) to give this kernel a shot.

I was able to download and build the LG ZV7 kernel, but how can one turn the zImage into a flashable ZIP file for recovery? Also, which kernel source is the code that builds but produces no video, and which exact ROM boots the lucid? Sorry if I'm asking stupid questions, but I want to be doubly sure, as this lucid is a replacement for the one that died last week during an OTA and I will have a tough time getting it fixed if it breaks.

https://github.com/spectrumhackers/lge-kernel-iproj

spectrum-defconfig

It boots, but no video on any Rom I've injected the zImage into. This includes a stock ICS rip and a CM10 rom we have on the Spectrum. Inserting the video drivers, and needed dependencies, from the v7 source into this causes it to no longer boot, which means either the video drivers are bad, or I'm missing something that needs to be merged.
 
Upvote 0
https://github.com/spectrumhackers/lge-kernel-iproj

spectrum-defconfig

It boots, but no video on any Rom I've injected the zImage into. This includes a stock ICS rip and a CM10 rom we have on the Spectrum. Inserting the video drivers, and needed dependencies, from the v7 source into this causes it to no longer boot, which means either the video drivers are bad, or I'm missing something that needs to be merged.

So, to confirm, I should compile the "lge-kernel-iproj" kernel with

[HIGH]make spectrum-defconfig ARCH=arm ...[/HIGH]

and put the zImage thus generated into the Quattrimus kernel link you posted (the CM10 version?).

Does this involve using "split_bootimg" and "mkbootimg" to simply swap out the zImage inside the "boot.img" in that ROM, or is there more work (signing? "--base 0x..."?) to be done? I'll give it a try by the weekend if all goes well.
 
Upvote 0
So, to confirm, I should compile the "lge-kernel-iproj" kernel with

[HIGH]make spectrum-defconfig ARCH=arm ...[/HIGH]and put the zImage thus generated into the Quattrimus kernel link you posted (the CM10 version?).

Does this involve using "split_bootimg" and "mkbootimg" to simply swap out the zImage inside the "boot.img" in that ROM, or is there more work (signing? "--base 0x..."?) to be done? I'll give it a try by the weekend if all goes well.

Correct, your build setup should provide you with a functional zImage and .ko files.

This source is what is currently in the CM10 (aka beta 4) posted in this thread. The easiest way to insert the zImage is with abootimg . The replace kernel option works just fine. This alone will not fix what we need as the video drivers do not work. If you manage to merge some different source codes together and get this working, I would love to hear about it.
 
Upvote 0
Correct, your build setup should provide you with a functional zImage and .ko files.

This source is what is currently in the CM10 (aka beta 4) posted in this thread. The easiest way to insert the zImage is with abootimg . The replace kernel option works just fine. This alone will not fix what we need as the video drivers do not work. If you manage to merge some different source codes together and get this working, I would love to hear about it.

I was able to compile and link a test kernel using gcc 4.4.3, but the kernel no longer fits with the Quattrimus boot.img configuration in the "i_vzw" (is this the right one?) folder:

[HIGH]/opt/android/image$ abootimg -u boot.img -k zImage
reading kernel from zImage
boot.img: updated is too big for the Boot Image (8368128 vs 8237056 bytes)
[/HIGH]

Can I go into the config and safely increase

[HIGH]bootsize = 0x800000[/HIGH]

or will this cause a brick when it is flashed? Likewise, if the ramdisk gets bigger when the new modules are inserted, will this cause issues?
 
Upvote 0
After flashing the Quattrimus ROM, both with the kernel it ships with and the kernel I tried to build, the phone is responding to power button, keys, etc. but the screen is black as before. What did you do to get access with android screen cast to find out how far the phone got into the boot? The phone is not currently being detected by either a Linux or Windows computer.
 
Upvote 0
After flashing the Quattrimus ROM, both with the kernel it ships with and the kernel I tried to build, the phone is responding to power button, keys, etc. but the screen is black as before. What did you do to get access with android screen cast to find out how far the phone got into the boot? The phone is not currently being detected by either a Linux or Windows computer.
Follow the instructions in this post and it should enable ADB for you.
http://androidforums.com/spectrum-a...quattrimus-jb-cm10-aokp41-27.html#post5468360
 
Upvote 0
While I still have no screen, I have found out the following:

  • Stock kernel rips from the phone with ICS running do not boot.
  • Using the open source Lucid kernel and modules does not bring up the screen.
  • The iproj kernel and the Quattrimus CM10 kernel bring up the phone with no screen, but the screen cast works, and data is connecting with 4G indicated. WiFi is operational, have not tested Bluetooth or GPS yet.
  • The digitizer driver needs to be adjusted, as the bottom-most 1/2" or so of the screen is unaddressable, along with about 1/8" on the right. I cannot get past the CM10 intro screen as the OK button on the bottom is not touchable.
 
Upvote 0
After hours of merging, I got a combination to compile with a screen! (Took parts of the LG ics kernel and merged into thebigq's android-msm-3.0-jb kernel)

cayman_first_screen.jpg

(link if image does not show)

Backlight is working (can adjust brightness, auto-dims). Bluetooth enumerated other devices, so that looks good. Haven't had a chance to try GPS. Sound and vibrator are good to go. Wireless charging cover (which I do not own) will not work as I have not yet merged the rt9524 drivers.

The following issues are still noted:
  • Touch coordinates are still not right
  • Icons/text are too big (the ROM seems to be still wanting the higher resolution). Is this a theming issue? Or is there something in the kernel I need to set?
  • Charger might not be displaying the right power level (no way to verify for sure at this point)
  • Neither front nor rear camera driver is working (merged, but cannot connect)
 
Upvote 0
As of now, I have fixed the touch screen problem, so the phone is halfway usable. I have now found out that the "search" button does not work and the backlight does not turn off properly, so those are the next two things to fix, followed by the cameras. The phone also charges very very slowly, so I need to look into that.

Is there anyone else who might be an expert on these particular issues (especially power) so that they can be resolved quicker?
 
  • Like
Reactions: jhcii
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones