Root [ROM] Jiilik's custom Shine Plus ROM's

zhuanyi said:

Thanks a lot jiilik, however my experience with the flashed ROM has not been that great so far. Basically every time the screen goes dark if I lock the phone without turning off wifi and wait a few seconds first, and after I took out the battery and put it back in and restart the phone, most of the process did not respond at the start (including the qualcomm ones) and I have to flash the ROM again every time to get my phone working, only to happen again next time the phone is rebooted.

I have tried v1,v7 and v8.

I have deleted everything on my SD card and formatted it, I have also tried to wipe out all user settings/factory reset the phone in the recovery menu and set this phone up like a new phone, however none seems to work. At the moment I am trying to flash my phone back to the stock ROM first (but not sure how I can do it, so it would be great if you could help me here: http://androidforums.com/shine-all-things-root/454782-flash-stock-rom-dz-file.html) and then tried to flash to your ROM to see if I can get better results.

Click to expand...

I've seen nothing like this, and it appears to be working normally on most phones. Did you try karendar's original roms too? they are using the stock kernel.

I suspect there is some other problem with your phone, either due to hardware, some residual software/settings that wipe isn't catching, or maybe a bad firmware image. There was a thread here: http://androidforums.com/lg-shine-plus/436866-lgnpst-dll-tot-shine-plus.html#post3409213 that showed how to flash the original update. This might fix your issues if it's a glitchy firmware or somesuch.

Hope this helps.

zhuanyi said:

Thanks a lot, at the moment I am just trying to get a hold on a USB cable so that I can try to flash back to the original ROM, do you know if the firmware KDZ file in that thread is the original firmware from LG?

My phone was using karendar's firmware before I flashed it to yours and other than the wifi + screen issue, I did not have any other problem

Click to expand...

Try flashing back to karendar's rom to see if things settle down. If they do, please let me know. It could be there's something weird going on. If nothing else, if his works fine, then you can rule out some other glitch.

Lastly, I saw that you tried to download the kdz file from LG. If they pulled the update then that will fail. At least one other person has had success flashing with the kdz file I originally posted.

Good luck.

Android Bob said:

I have updated my LG Shine Plus to Android 2.3.3 and have rooted the phone with Gingerbreak. Next I would like to install the custom recovery menu version 3.06 and be able to do a Nandroid Backup. Could you please post the files that I would have to download and a step by step procedure for Android 2.3.3. Any help would be greatly appreciated by me and I'm sure other noobs who follow the forum.

Click to expand...

Hi Android Bob:

There's another thread in the All Things Root forum for this phone that includes links to all the relevant information. It's not in this thread since it's generic information for all ROMs. See here: http://androidforums.com/shine-all-...l-things-root-guide-updated-11-24-2011-a.html

Specifically, for installing the custom recovery partition, see here: http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html

The step by step details are there. All other functions, like making nandroid backups, system wiping, and flashing new roms, can be performed from the recovery program.

Hope this helps.

jparasite said:

jiilik, I think it may be a problem on my end, but I'm having issues getting Superuser to work with anything. There's no permissions pop-ups when attempting to run both SetCPU and Terminal and thus they FC.

Do you have any insight into this?

Click to expand...

I had a problem a few editions of my rom ago where the Terminal was force-closing on me. I uninstalled and reinstalled from the market and it fixed it. But that issue wasn't related to Superuser.

Normally, I'd just say go to the market and update Superuser.apk to the newest version, but this is sort of a chicken-and-egg problem as it would need root to install.

First thing to try is going to wipe your dalvik caches and such, which you can do from the recovery partition. You can do this without wiping the rest of the system. It'll take a while to reboot afterwards as it needs to rebuild the cache, but it might solve the issue. If that fails, do a nandroid backup, then try a full wipe and maybe a reflashing.

That's pretty much all I can recommend for troubleshooting as, like you, I'm still learning too!

Cheers, and good luck

jparasite said:

Well, I determined that yes, apps such as Terminal/SetCPU need to be installed/placed into /data/app, and will FC if placed into /system/app. I'll continue to do research into this, as I know of several custom ROMs for other phones that have Terminal running in /system/app.

Other than that, I gave up attempting to download/build the source in Windows and am now doing it in a Linux VM.

Click to expand...

Yeah - had a similar problem. Don't know the cause. Hope you find out too, since I'd like to include Term.apk and such in the main ROM and haven't figured out how to do that stably yet.

My background is that of a Linux developer... I was a KDE developer for about 10 years - mostly C++ and python. Things like the linux kernel are an old playground of mine, but I don't really know java and am certainly new to the arm architecture and the whole android ecosystem.

This means I don't know much about apk's, signing, dalvik, etc. But I'm perfectly comfortable if you dump me into a terminal Maybe I just need someone to come along that has a complementary skill set

Cheers, and have fun!

jparasite said:

Hey jiilik, I was able to get the kernel to compile (into a zImage) and now I'm figuring out how to put this into a flashable image.

Aside from that, the only other issue I'm having is errors with building the Android source. Specifically:

Step 2 where it says: And, merge the source into the android source code(gingerbread)

Step 3 where it says: You have to add google original prebuilt source(toolchain) before running build scripts.

Any insight into what exactly I should do/enter?

For what it's worth, I've done alot of C++ development but only in a Windows environment mainly with MFC (shudder). So Linux is still fairly new to me. I did tend to use Java alot before my current job so I have much more experience with that.

EDIT

So I can build AOSP Gingerbread checkout just fine, but the moment I try to "merge" the downloaded zip in, I get errors when attempting to compile webkit/WebCore and so on.

Click to expand...

1) Android kernel 101:

When you have a rom, there's two main parts: system.img and boot.img. The former is the contents of /system that will be flashed - it's pretty straightforward in that's it's just a filesystem to be flashed to a partition. The boot.img file is more interesting.

Inside boot.img is two things: the first, a zImage (the kernel) and secondly a mini-filesystem called initrd or 'initial ram disk'. On a normal linux system, an initrd would contain just enough supporting programs to get the main filesystem mounted. Boot scripts are in here.

Unfortunately, the structure of boot.img is a bit complicated (as is system.img, actually).

What I do to make my roms is use a tool called dsi's xda kitchen. It's ever so slightly out of date now, since he stopped developing it a few months ago, but it does a nice job.

It's basically a bunch of command line scripts and ready to use programs put together in a nice menu interface. It allows a set of custom modifications to be easily performed on roms (like adding root, apps2sd, etc.). karendar and I have both been using it to modify and package up our roms as it looks after things like signing the zip file.

In this program, you load an existing rom. It unpacks system.img and lets your much around inside the file system. It also gives you access to boot.img (if you use option '20', then unpack the boot.img). When boot.img is unpacked, you can replace the zImage with the one you built yourself. You can also modify the boot scripts and other files in the initrd.

Lastly, if the kernel built any modules (wireless.ko is the most important), you need to ensure that they get copied into the appropriate place in system.img, replacing the existing .ko files.

Then, you use the kitchen to repack boot.img, and finally, create the flashable zip file. At least, that's how I've been doing it.

I'm pretty sure there's a more official way to build the sources which just creates system.img, boot.img, etc. ready for flashing. I might still use the kitchen scripts to package the final zip file, since it'll look after zipaligning, signing, etc. Plus, I have a workflow now Why change

The good news is that your build environment is working as well as mine, and your kernel is probably perfectly sound. We should start sharing patches and config files and such. I'll see what I can put together from what I've got.

2) Okay, I got the same issue building the sources that LG provides. Here's what I'm thinking: their instructions suck and their sources suck more.

I know it says to get 2.3.3, but I think LG is actually using 2.3.3 from a different source than google. I believe it is the gingerbread branch from the Code Aurora Forum.

Tangent: The Code Aurora Forum, although representing itself as a community driven website, is really just Qualcomm's official dumping ground for their open source projects. It's proof that open projects do not automatically develop a vibrant developer community. Nevertheless, it looks like any phones using Qualcomm chips will use their version of android since it includes all the relevant drivers and such. If you start poking around in the kernel source code for our phone, you'll see that it's actually certainly the case here where LG has taken the kernel that is provided by the Code Aurora Forum and used that as their basis. Hell, half the drivers for our phone are Copyright Code Aurora Forum, All rights reserved. End Tangent.

Okay, so the good news is that we have the same build results - we can both build the generic android sources from google, and we both fail to build LG's sources when merging them (failing on webkit).

I've just checked out the gingerbread branch from codeaurora and it weighs in at a whopping 10GB - it's also version 2.3.6 - whatever. They have pretty good instructions on building at their wiki page.

Anyway, I haven't got that one building yet. Sleepy time.

jparasite said:

Ah that's some good information. It would make sense that LG fails at sources LOL. I'm looking at the Gingerbread releases right now: https://www.codeaurora.org/xwiki/bin/QAEP/gingerbread

I do know that the C710h uses the MSM7227 so I'm gonna guess that the MSM7627 is the closest equivalent on these releases?

EDIT:
Looks like that is the case. Now I'm attempting to see if there's a difference between msm7627a and the regular msm7627 chipsets.

EDIT:
It looks like the msm7x27a versions are upgraded/refreshed versions of the original chips. So in this case, should we check out the latest-non-a version: March 28, 2011, M76XXTSNCJNLYA7120

Click to expand...

I just checked out the gingerbread branch (using -b gingerbread as the repo command option), rather than a specific version. Then if there's patches/fixes/new drivers/etc., I can follow along. But it's good if we're taking multiple angles, so one of us might find a proper solution.

EDIT: oh, and yes: 7227 is simply the 7627 but with GSM instead of CDMA. Pretty much everything else is identical. We can use an android build for the 7627 and it'll almost certainly work happily.

EDIT: I'm building the msm7627_surf target of gingerbread branch from codeaurora to see how that goes. It looks like it won't be that hard to add a new target for the build from this. I'm also trying to checkout CyanogenMod's gingerbread tree, which could take a while. My bloody connection gets interrupted so often. Last time I ever get internet from Bell.

What it looks like is lacking from the LG sources are the files defining the build target for the machine. We may have to recreate those manually. I've already started on this for CyanogenMod, so if that works, we can probably get a 'virgin' build of the code-aurora-forum sources, and one of cyanogenmod. Both for gingerbread, of course.

EDIT: msm7627_surf sources from code aurora build fine for me. If you choose 'eng' as the release, it even creates the OTA update packages, recovery partition, and more. Will keep playing.

jparasite said:

So I finally finished downloading the gingerbread_house branch: https://www.codeaurora.org/xwiki/bin/QAEP/gingerbread_house

And am attempting to compile it using the msm7627_ffa option within choosecombo. Like previously I encountered two compile errors solved here:

building Android from source (Page 2) / Developer Centre / Oxygen Forum

Issue 20795 - android - AOSP build fails in HOST_linux-x86 with _FORTIFY_SOURCE redefined. - Android - An Open Handset Alliance Project - Google Project Hosting

The first thing I'll try to do is just build a ROM with it, flash it, and see if my phone actually boots (I highly doubt it). The next will be an attempt to merge the LG source and fix compile issues from there.

EDIT:
Well putting the compiled boot.img and system.img together with the kernel we built from LG sources resulted in a boot loop. I also had to remove two lines referring to /system/etc/bluez during the update script as those did not exist.

Click to expand...

Congratulations, you're now ahead of me on this one I haven't tried to load any of this on my phone yet. I doubt it'd boot anyway, since boot.img contains the wrong kernel. Try switching the kernel for the one you built from LG's sources.

Cheers

alfi said:

hi jiiilik
i install your rom version 8 and everything work fine at 672 mhz
just one thing, i thing you remove laucher2.apk from system folder ,i don't know why but if you remove that apk i lost the wallpaper gallery,i explain, before i can change my wallpaper with the fixe one not the animated, and after the update i cannot choose the fixe one because he don't appear on the menu.

before i used your rom 2 week ago i remove facebook,map,laucher2,lg advisor etc and after that i lost the menu for changing the wallpaper, i reinstall one by one all the apk i remove and i see that laucher2.apk cause my problem.

can someone can test this bug or i don't understand something?

Click to expand...

Bug doesn't happen for me, but I'm using a wiped system to test things on - all of my old settings got punted before I flashed the new rom.

That said, I think in a future version, I'll put launcher2.apk back in. This was originally removed by karendar to make room in the rom because it grew when deodexed. I think I'll remove the LG App Advisor and Youtube - the former because it's not that useful, and the latter because there's an updated version in the market anyway for people that need it. I might remove a few others too if I can find similar logic. That would make room for putting launcher2.apk back in. It's on my TODO list for v009.

Cheers, and thanks for the feedback!

Android Bob said:

Thanks Jiiilik. I was able to install RECOVERY Ver 3.06 and Ver. 008 of your custom ROM. I'm now testing it at 672 MHz. Could you tell me if you were able to adapt Nuance Voice Control with your ROM or does the app just close when you try to say the Mellisa Jordan sentence? I would really like to get Nuance working properly. Thanks again for all your help.

Click to expand...

I don't use Nuance - have never used it, not even in version 2.1. In fact, I kept trying and failing to remove it from 2.1 (I knew a lot less then - still learning). I don't know what the normal behaviour is supposed to be, so it's difficult for me to troubleshoot.

That said, if you or anyone else comes up with a fix, I'll gladly include it in any updates to this rom.

Sorry I can't be of more help on this one.

Cheers, and thanks for the feedback!

cjmaniac said:

I now have an issue. Not sure if it is related to this rom or not. My speaker has stopped working for calls. Speakerphone still works fine. Tried reflashing it and turned clockspeeds down to normal but no change. Any ideas or is it just failed hardware?

Click to expand...

Sorry, I have no real idea on this one, but I have a few ideas you can try. You could try wiping before reflashing to see if it's a setting. You could try flashing an older version of the rom that doesn't have overclocking turned on (like v001 or karendar's alpha1.2).

It could be a software problem but related to your phone's radio software or similar. You can try running through the phone unbricking/radio updating instructions again as that should reflash your radio.

If none of that works, that leaves hardware. Could be as simple as a loose connection which your neighbourhood cell shop might be able to fix. The radio reflashing/unbricking instructions should return your phone to a near virgin state - if you're still under warranty, you can probably return it. Or you can find a 12 lb sledge hammer and smash it to pieces. Choice is yours

(If you smash it with a hammer, post a video on youtube for our amusement.)

Okay, in all seriousness, I hope something works for you.

Cheers

jparasite said:

Nice work! I'll be sure to checkout that source tonight and try building it myself. I'm assuming that's without merging the LG source because of the lack of build targets.

That's currently a little over my head. I'm guessing a build target files indicate how a particular file should be compiled (for example I was getting errors for DNS.cpp because the file did not exist, etc etc).

Click to expand...

You know, I've been looking through the bits of sources that LG provided for their userspace. It doesn't actually look that useful. I'm wondering if we need it at all.

Assuming we have a working kernel (which we do) and drivers (which we do), we might get away with simply building and installing pretty much untouched sources from CAF. Well, we can try anyway.