Beta 4e and 4f are up. If 4e doesn't boot or boot loops, then 4f will most likely do the same http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4e.zip http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4f.zip
Saxydroid has a lucid, his testing has been good. I am just keeping overwatch. my lucid should be back any day from LG
Did you try building stock kernel and flashing it onto the firmware it's supposed to be flashed on??? Oh wait :banghead: LG locked the bootloader it was made for.
sammy your very confusing. this is the VS840 LG lucid forum....i believe everything we are doing only relates to the vs840. I think building ics from source breaks due to faulty or missing code from LG. If we can get ICS to boot coming from GB's unlocked boot using cwm....then unlocking the ICS boot loader is a few steps away.....
Just a quick update. I haven't forgotten about this project, but I'm at an absolute lose for finding kernel code that will boot and provide the correct video drivers. The hunt will continue.
this may not be what your looking for, but what about the display drivers qualcomm has for the adreno 220 for jelly bean here. would this be usefull?
It's not the drivers I'm looking for, it's the kernel source. I need to find something that runs the msm8x60 chipset and runs at your 480x800 resolution.
They have a github, so this is encouraging. I'll download the source for the kernel and see how much of the hardware requirements match up.
http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4g.zip This should have perma ADB at boot. Still working on getting the 4g slide kernel to compile correctly. As always, looking for responses on if this works or not.
Correct. I'm not sure why ADB is not starting as it's hard coded to start at boot now and with no instructions to turn off. I'll post another version tonight with some of the previous settings put back in.
Hey Neph or anyone here... don't suppose you have the files needed to reprogram flash using qualcom too to get past a qhusb_dload brick? I have read about large support for this for HTC devices on the XDA forums... how much different can it be?
We have access to dload with buttons (download mode), so I don't know why you would need some program to get into it. If you mess up your aboot (which controls download mode), you'd be at full brick status anyways and you're phone wouldn't turn on.
http://androidfiles.massivefilehost.com/lucid/lucid_kernel_beta4h.zip If this doesn't keep adb, I'm at a loss as far as the init scripts are concerned.
adb doesn't connect, but after letting the phone sit plugged in for a few minutes it started to install drivers for the phone, it took to long for the drivers to install before it disconnected again. it did this about 3 times and that was it. on a side note, what if the adb problems can be solved by modifying parts of CM rom.
Does anyone know the partition table setup for the Lucid? Linux can't seem to find them in a ls /dev/. This is the only information I am missing for fixing the hard-brick caused by the fake rom upload.
I don't have the partition sizes, but here is what each partition is suppose to hold. http://androidforums.com/lucid-all-things-root/667013-need-your-help-few-files.html#post5357181 Hopefully someone with a working Lucid can provide the actual partition sizes. Also, does re-flashing the OS with the .cab file fix anything for what you had happen, or is the nand that messed up?
P.S. , the actual command you want to run in ADB is "cat /proc/partitions" . That will list all the partitions and their sizes.
