[G3 General] topet2k12001:
Responses 03.09.2015

Let's be careful; he said his phone is the LG L90 and not an LG G3. That's why i said to him in my response that he may try but make sure that he takes a calculated risk. Although if this procedure works for him then that's great. :)

Hi [MENTION=2863754]cirusnb[/MENTION],

Thanks for sharing! I do see a lot of other LG G3 variants already having repacked, "pre-rooted" Lollipop firmware. I actually wanted to do the same so that it will be more convenient for the D858HK users. On the other hand, it's also a good thing to learn how to do it manually, as it aims to provide a "universal" approach - for example there are variants which are not widely supported so this is the only option for them. Also, knowing how to manually flash is a good thing to know because in case of emergencies people have an alternative way (I had a lot of "brick" status scenarios while experimenting and having knowledge of more than one method of flashing helped me avoid a "full brick" situation).

Hi [MENTION=4646677]zurny[/MENTION],

Thanks for your feedback. :)

I'm not sure, but this may have played a role to your issue:

Flashing the full firmware (KDZ) means that effectively, you are flashing also some of the key components (partitions) that we don't want to be flashed, which goes against the purpose of this guide (whereby this guide is sourced from that of [MENTION=2684188]autoprime[/MENTION]). That's why we are only extracting specific parts of the KDZ (system.img, modem.img, and boot.img) and flashing only these components (partitions) accordingly. Then we "bump" the boot.img via the Sharpening Script Mod to ensure that we can still use TWRP while in Lollipop.

1. Some examples of those components (partitions) that we don't want flashed (which are flashed when doing a KDZ full flash) are: tz.img, rpm.img, sbl1.img, and aboot.img.

2. Flashing the full KDZ means you will be overwriting those existing components (partitions) to Lollipop versions (which we don't want to happen) - which in this guide, we want to remain as "Kitkat versions".

3. Basically, in this guide we are going to Lollipop from Kitkat, and not doing the guide when we are already in Lollipop.

But if everything stabilizes as per your intended course of action, then all good. :)

Yes...effectively speaking, if the boot_xxxxx.img and modem_xxxxxx.img files are not renamed, the Flash2Modem.zip and Flash2Boot.zip will end up flashing nothing. This is because those zips are "programmed" in a way that they will look for a file named exactly as boot.img and modem.img.

It is for this reason why I recommend everyone to read the guide first in its entirety before actually doing it. And to read slowly/carefully, no need to rush it. :)

Hi [MENTION=4294399]ReeeN[/MENTION],

Haven't observed it yet as I was busy responding to posts. :)

On my end, here's what I'll do to test:

1. I'll start from full charge.

2. No installed user apps yet (especially social media and chat/messaging apps). Probably I'll set up my work email but will do manual sync only.

3. I will use only 3G or 4G, no Wifi

4. No auto-syncing for me (I never do that)

5. I don't play games on mobile phones. I'm more of a PC and console gamer.

This is so I can compare with the same method I used when I was with Kitkat. Based on my actual experience, battery lasts for an average of 24 hours when I was on Kitkat.

Basically, I would downgrade to Kitkat, observe/record my battery drain based on my usage pattern. Then upgrade back to Lollipop and do the same (should be pretty much the same usage pattern). This way I can compare the results with some degree of confidence.

I just saw a thread and it's all about changing the "governor" from "Interactive" to "Conservative". It's off-topic from this thread but I just thought of mentioning this. You may want to try it. Here is the thread: click me!