I understand you can't use dual sim features on third party roms but does using dual sim apps on Play enable you to access those capabilities?
Kabayan, Topet! You just did a great job there buddy! You really are a big of a help
I just wanted to asked before doing this steps. I actually, followed you're video tutorial for downgrading to 10D and rooted it but unfortunately I am not receiving any OTA update to 10F unless I update thru LG PC. Can I still do this steps without updating to 10F? Thank you again kabayan!:good:
I just wanted to asked before doing this steps. I actually, followed you're video tutorial for downgrading to 10D and rooted it but unfortunately I am not receiving any OTA update to 10F unless I update thru LG PC. Can I still do this steps without updating to 10F? Thank you again kabayan!:good:
Responses 03.09.2015
Hi Friends,
Here's what I'll do: I'll do my best to check this thread at least once a day, browse through the posts, and then multi-quote them and provide responses whenever I can. So let's start.
Hi @ch4dwick,
I was supposed to edit my initial response to you to provide an update, but I'll just put it here.
So I flashed Euphoria OS 1.0 for the D855 (since the D855 is an international variant). Not sure but I think Euphoria is CM12-based (correct me if I'm wrong). Result: brick! Hahaha! As in full brick and can't even be flashed via the LG Flash Tool. Good thing I made a full system backup via TWRP (so this is a reminder to everyone - back up your system via TWRP first before doing anything adventurous!) and I was able to restore.
I did ask the OP of Euphoria OS 1.0 to add the D858HK as a supported variant. Unfortunately the answer is "no" because (as per the OP) the D858HK variant does not support CM12. Having said that, I did not explore/dwell into looking further as far as dual-SIM apps from the Play Store.
Maybe it will be possible by building/compiling CM from source for our D858HK. That's actually what I'm reading/learning about (as I mentioned in the first post that I am not a developer by profession). If someone with skills can do it, then that would be awesome.
Hi @tmjm28,
Thank you as well. You don't have to do the "bumping" of TWRP; I already did it for D858HK users. Just go back to the tutorial under the "Requirements" section. I have provided a link to download the "bump'd" TWRP. Although for your situation I would suggest starting all over because at this point, I can't trace what you did in the week prior.
Hi @ReeeN,
Allegedly, the LG G3 is "too sharp" so it creates a "ghosting" effect on text. So a developer created a script to fix that and put it up as a flashable zip (hence, we have the Sharpening Mod Script). Some users can't tell the difference though, so if it doesn't affect you then it doesn't matter.
The reason why I advise everyone to flash the Sharpening Mod Script is because it also contains another script that will "unlock" ("bump") the boot.img. This is a very important step for keeping root on Android Lollipop, as well as keeping TWRP.
For the selection: higher value = sharper display. I usually select zero (0) for "no sharpening".
Hi @zurny,
Thanks for confirming your LG G3 variant. I will update the First Post.
Yup, as far as download speed, I haven't investigated it because I did not experience the problem. Try to isolate the easiest causes first (i.e. your Internet quality/speed). One typical way that I would do it is to switch to another wifi, or disable wifi and use 3G/4G/LTE and see if it makes a difference. Only then will I move further in troubleshooting such as clearing cache, etc.
Hi @gelroyliao,
Yes, you can update to Lollipop directly from Kitkat version 10F. I tried that too and it worked (which reminds me, I have to update the tutorial). You're welcome, kabayan.
Hi Friends,
Here's what I'll do: I'll do my best to check this thread at least once a day, browse through the posts, and then multi-quote them and provide responses whenever I can. So let's start.
I'm expecting someone to have actually done it in the future. I'd do it myself but I'm still busy at the moment to be actually redoing stuff from scratch if I fail to succeed in flashing CM12 on the D858HK. Oh, well, maybe later this year.
Hi @ch4dwick,
I was supposed to edit my initial response to you to provide an update, but I'll just put it here.
So I flashed Euphoria OS 1.0 for the D855 (since the D855 is an international variant). Not sure but I think Euphoria is CM12-based (correct me if I'm wrong). Result: brick! Hahaha! As in full brick and can't even be flashed via the LG Flash Tool. Good thing I made a full system backup via TWRP (so this is a reminder to everyone - back up your system via TWRP first before doing anything adventurous!) and I was able to restore.
I did ask the OP of Euphoria OS 1.0 to add the D858HK as a supported variant. Unfortunately the answer is "no" because (as per the OP) the D858HK variant does not support CM12. Having said that, I did not explore/dwell into looking further as far as dual-SIM apps from the Play Store.
Maybe it will be possible by building/compiling CM from source for our D858HK. That's actually what I'm reading/learning about (as I mentioned in the first post that I am not a developer by profession). If someone with skills can do it, then that would be awesome.
Hi @tmjm28,
Thank you as well.
You don't have to do the "bumping" of TWRP; I already did it for D858HK users. Just go back to the tutorial under the "Requirements" section. I have provided a link to download the "bump'd" TWRP. Although for your situation I would suggest starting all over because at this point, I can't trace what you did in the week prior.Hi @ReeeN,
Allegedly, the LG G3 is "too sharp" so it creates a "ghosting" effect on text. So a developer created a script to fix that and put it up as a flashable zip (hence, we have the Sharpening Mod Script). Some users can't tell the difference though, so if it doesn't affect you then it doesn't matter.
The reason why I advise everyone to flash the Sharpening Mod Script is because it also contains another script that will "unlock" ("bump") the boot.img. This is a very important step for keeping root on Android Lollipop, as well as keeping TWRP.
For the selection: higher value = sharper display. I usually select zero (0) for "no sharpening".
Hi @zurny,
Thanks for confirming your LG G3 variant.
I will update the First Post.Yup, as far as download speed, I haven't investigated it because I did not experience the problem. Try to isolate the easiest causes first (i.e. your Internet quality/speed). One typical way that I would do it is to switch to another wifi, or disable wifi and use 3G/4G/LTE and see if it makes a difference. Only then will I move further in troubleshooting such as clearing cache, etc.
Hi @gelroyliao,
Yes, you can update to Lollipop directly from Kitkat version 10F. I tried that too and it worked (which reminds me, I have to update the tutorial). You're welcome, kabayan.
Last edited:
Hi @ReeeN,
Allegedly, the LG G3 is "too sharp" so it creates a "ghosting" effect on text. So a developer created a script to fix that and put it up as a flashable zip (hence, we have the Sharpening Mod Script). Some users can't tell the difference though, so if it doesn't affect you then it doesn't matter.
The reason why I advise everyone to flash the Sharpening Mod Script is because it also contains another script that will "unlock" ("bump") the boot.img. This is a very important step for keeping root on Android Lollipop, as well as keeping TWRP.
For the selection: higher value = sharper display. I usually select zero (0) for "no sharpening".
@topet2k12001
thanks dude.... its crystal clear rite now...
Hi @m.swastik,
Sorry but i do not know the answer. You can try if you are adventurous enough, but ,make sure you take calculated risks (i.e. fully backup your system via TWRP, etc.).
Hi @ReeeN,
You're welcome.
Very nice job ! guide is a spectacular,
but I would like mention that there is one Pre_rooted Rom (LOLIPOP) for the D852 Bell/rogers.
http://xdaforums.com/lg-g3/general/canada-lg-g3-canadian-users-t2810696/page110
I've been running it since last weeks.
but I would like mention that there is one Pre_rooted Rom (LOLIPOP) for the D852 Bell/rogers.
http://xdaforums.com/lg-g3/general/canada-lg-g3-canadian-users-t2810696/page110
I've been running it since last weeks.
Yes that's what I did, I was running stock kitkat and flashed the stock lollipop rom from the official kdz file.
Hi Friends,
Here's what I'll do: I'll do my best to check this thread at least once a day, browse through the posts, and then multi-quote them and provide responses whenever I can. So let's start.
Hi @ch4dwick,
Maybe it will be possible by building/compiling CM from source for our D858HK. That's actually what I'm reading/learning about (as I mentioned in the first post that I am not a developer by profession). If someone with skills can do it, then that would be awesome.
I'll try to look into this but it doesn't look very promising. It would be far easier for me to just work with a cm supported phone than go through the trouble of cooking up a custome cm for it.
Tried it with an SM-G900K in the past that lead me nowhere.
Hi Friends,
Here's what I'll do: I'll do my best to check this thread at least once a day, browse through the posts, and then multi-quote them and provide responses whenever I can. So let's start.
Hi @zurny,
Thanks for confirming your LG G3 variant.
Yup, as far as download speed, I haven't investigated it because I did not experience the problem. Try to isolate the easiest causes first (i.e. your Internet quality/speed). One typical way that I would do it is to switch to another wifi, or disable wifi and use 3G/4G/LTE and see if it makes a difference. Only then will I move further in troubleshooting such as clearing cache, etc.
Well I let the updates finish while I was sleeping and everything is fine this morning. The speed problem wasn't caused by my connection cause I ran a speedtest with the speedtest.net app and my wifi was getting 45 mbps. I think the rom needs to stabilize for a while after the initial flash. For my part I flashed the Lollipop stock KDZ to upgrade from stock Kitkat, so a lot of stuff was updating at the same time so the slowdown was probably CPU or disk related.
On a side note, for those of you getting an LG security error at boot after flashing everything, make sure your boot_196608.bin is renamed to boot.img and your modem_32768.bin to modem.img. I made the mistake of only renaming the extension to .img and forgot to rename the file name. I was able to reboot to recovery and re-flash everything and it was fine.
Cheers!
Battery draining fast
hai all....
after upgrading to lollipop, do you all having problem with the battery? because i think the battery is draining to fast on my device, compared to kitkat. or its just me having this prob? or maybe its lollipop bugs? just curious...
hai all....
after upgrading to lollipop, do you all having problem with the battery? because i think the battery is draining to fast on my device, compared to kitkat. or its just me having this prob? or maybe its lollipop bugs? just curious...
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 @cirusnb,
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 @zurny,
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 @autoprime). 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 @ReeeN,
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!
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 @cirusnb,
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 @zurny,
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 @autoprime). 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 @ReeeN,
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!
Last edited:
Hi Friends,
Here's what I'll do: I'll do my best to check this thread at least once a day, browse through the posts, and then multi-quote them and provide responses whenever I can. So let's start.
Hi @zurny,
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 @autoprime). 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.
I didn't flash the full KDZ, I meant to say that I extracted the three .img files from the kdz , I thought that it was insinuated. I'll more clear in the future
Clarification
Oh, I see. Thanks for clarifying that part. Yes, we all need to be very clear; I realized that XDA is an international forum so everyone is required to speak in English but of course, not all of us use English as the first language (that includes myself, of course).
I'll just keep my previous response as-is, so others who happen to flash the full Lollipop KDZ will also have a reference in the future.
I didn't flash the full KDZ, I meant to say that I extracted the three .img files from the kdz , I thought that it was insinuated. I'll more clear in the future
Oh, I see. Thanks for clarifying that part.
Yes, we all need to be very clear; I realized that XDA is an international forum so everyone is required to speak in English but of course, not all of us use English as the first language (that includes myself, of course).I'll just keep my previous response as-is, so others who happen to flash the full Lollipop KDZ will also have a reference in the future.
Q&A Added
Hi Friends,
Thank you so much for your posts and questions. It allowed me to add a few Q&A items (I edited the "Troubleshooting" section to add the Q&A's). This helps ensure that newcomers can easily be directed to Page #1 of this thread and help save them time in reading the entire thread just to find the answer.
In case this thread becomes busy in the future and you notice that something needs to be added/removed/edited in the First Page (and I missed reading it), please don't hesitate to let me know via PM (Private Message).
Keep them coming!
Hi Friends,
Thank you so much for your posts and questions. It allowed me to add a few Q&A items (I edited the "Troubleshooting" section to add the Q&A's). This helps ensure that newcomers can easily be directed to Page #1 of this thread and help save them time in reading the entire thread just to find the answer.
In case this thread becomes busy in the future and you notice that something needs to be added/removed/edited in the First Page (and I missed reading it), please don't hesitate to let me know via PM (Private Message).
Keep them coming!
Hi @ReeeN,
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!
thanks for your suggestion @topet2k12001 i'll try latter to change the governor from interactive to conservative, hope that will help my battery issue...
D852 Rogers working!
Just wanted to report that this worked. For some reason, it seems that open_bump wasn't bumping the image properly. Anyway, the sharpening script did the trick. Will report in autoprime's thread as well as some canadian users had an issue updating if memory serves correctly. Anyway, thanks for doing most of the experimenting for us and writing this detailed guide. I knew my issue was with the boot.img. Just didn't know that the sharpening script provided another way of bumping. Had I known, would've got lollipop working way earlier (2 days after Rogers OTA xD) since the phone wouldn't throw the error anymore.
Just wanted to report that this worked. For some reason, it seems that open_bump wasn't bumping the image properly. Anyway, the sharpening script did the trick. Will report in autoprime's thread as well as some canadian users had an issue updating if memory serves correctly. Anyway, thanks for doing most of the experimenting for us
and writing this detailed guide. I knew my issue was with the boot.img. Just didn't know that the sharpening script provided another way of bumping. Had I known, would've got lollipop working way earlier (2 days after Rogers OTA xD) since the phone wouldn't throw the error anymore.Great to know!
Hi @DE52,
Good to know that! I'll add your LG G3 variant to the list of working devices for the manual method. I saw your post in @autoprime's thread as well.
Yup, this how-to guide is practically sourced from @autoprime. I just added that extra step of "bumping" the boot.img via the Sharpening Script Mod (apparently, it also contains a script to properly "bump" the boot.img). And then I just detailed the steps - I really did not invent anything here, I just basically spelled it out.
Just wanted to report that this worked. For some reason, it seems that open_bump wasn't bumping the image properly. Anyway, the sharpening script did the trick. Will report in autoprime's thread as well as some canadian users had an issue updating if memory serves correctly. Anyway, thanks for doing most of the experimenting for us
Hi @DE52,
Good to know that! I'll add your LG G3 variant to the list of working devices for the manual method. I saw your post in @autoprime's thread as well.
Yup, this how-to guide is practically sourced from @autoprime. I just added that extra step of "bumping" the boot.img via the Sharpening Script Mod (apparently, it also contains a script to properly "bump" the boot.img). And then I just detailed the steps - I really did not invent anything here, I just basically spelled it out.
problem wit OTA update
hi..i have lg g3 d858hk
few days ago i got v20c update in my update center with OTA,but i didnt update...i cancel it...i didnt select upgrade botton...yesterday i decide to update again with OTA but over again i cancel it and did not push upgrade botton...today i want to update with OTA but there is no update in OTA!!!
it say you are updated to lasted os...my os is kitkat 4.4.2......what happeneed?
why i cant update from ota?
but when i connect phone to pc and luanch LG MOBILE SUPPORT TOOL there is a update..
size of ota update is 566 MB...but size of LG MOBILE SUPPORT TOOL is 1126 MB!!!!what diference of this updates?
plz help me....
hi..i have lg g3 d858hk
few days ago i got v20c update in my update center with OTA,but i didnt update...i cancel it...i didnt select upgrade botton...yesterday i decide to update again with OTA but over again i cancel it and did not push upgrade botton...today i want to update with OTA but there is no update in OTA!!!
it say you are updated to lasted os...my os is kitkat 4.4.2......what happeneed?
why i cant update from ota?
but when i connect phone to pc and luanch LG MOBILE SUPPORT TOOL there is a update..
size of ota update is 566 MB...but size of LG MOBILE SUPPORT TOOL is 1126 MB!!!!what diference of this updates?
plz help me....
Hi @smirdex1,
So basically, you want to upgrade to Lollipop, correct?
If so, don't worry. You can upgrade using the guide in this thread. It's not OTA method, but it will get up upgraded to Lollipop just the same. Plus, this guide will give you root and custom recovery (TWRP).
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
84OWNERS OF OTHER LG G3 VARIANTS ARE WELCOME TO TRY!
IMAGEPREPGUI: AUTO-SCRIPT (GUI) FOR LG G3
Tested on: LG G3 D858HK
FEATURES:
1. Rooting of your LG G3
2. Automatic (no-touch) extraction of aboot.img and laf.img from your KDZ or TOT firmware via the KDZ and TOT Extractor Tool by @bullghost
3. Download and installation of "bump'd" TWRP custom recovery for certain LG G3 models/variants
4. Sharpening Mod Script of Skin1980 included (to be manually flashed upon reboot to TWRP Custom Recovery) - this will "bump" your Kernel (boot.img) and will apply your desired sharpening level of the LG G3's display
5. "Bump" your boot.img (as part of the TWRP installation process of ImageprepGUI)
6. (Experimental): optionally "bump" your "un-bump'd" TWRP custom recovery.img
REQUIREMENTS:
1. Installed LG G3 Drivers for your device
2. Enabled Developer Options and USB Debugging on your LG G3
3. Backed up all your important files to your external storage or computer
4. Downloaded a copy of your KITKAT Firmware (in KDZ or TOT format)
5. Your custom recovery (TWRP) for your respective LG G3 model (Imageprep has download feature but only for certain models)
DOWNLOAD LINK:
ImageprepGUI v2.6: "installer" format. Double-click it to run. It will detect any previous installations of ImageprepGUI and delete them (as in ALL files within).
Imageprep Folder in Google Drive: this contains sub-folders of various LG G3 variants/models where you can manually download aboot.img, laf.img, and "Bump'd" TWRP custom recovery (recovery.img). Users can also download previous versions from here as well as corresponding video tutorials.
Downloadable Video Tutorial
Video Tutorial on YouTube
HOW TO USE:
1. Navigate to C:\ImageprepGUI and you will see ImageprepGUIvx.x.exe (where x.x is the version number). Run this app. It is recommended that you create a shortcut to your desktop or Windows taskbar for easy access.
2. Follow the step-by-step instructions.
DETAILED STEP-BY-STEP (HOW TO USE):
At the first screen with selections (radio buttons):
1. Acquire aboot.img and laf.img: you can choose to...
a. download from my Google Drive, or
b. have the full KDZ or TOT firmware handy and let ImageprepGUI extract them for you, or
c. manually run the KDZ and TOT Extractor tool and manually extract them
IMPORTANT: DO NOT SKIP THIS STEP IF YOU'RE GOING TO INSTALL TWRP. YOU MUST MAKE A SELECTION. SKIPPING THIS STEP IS OKAY IF YOU ARE ONLY ROOTING THE DEVICE.
2. Acquire "Bump'd" TWRP (recovery.img): you can choose to...
a. download from my Google Drive, or
b. have your own "bump'd" TWRP (recovery.img) handy
IMPORTANT: DO NOT SKIP THIS STEP IF YOU'RE GOING TO INSTALL TWRP. YOU MUST MAKE A SELECTION. SKIPPING THIS STEP IS OKAY IF YOU ARE ONLY ROOTING THE DEVICE.
At the next page:
1. You can choose to...
a. root ONLY (there are 2 methods available), or
b. skip rooting (if you are already rooted prior) and then proceed to TWRP installation, or
c. root+install TWRP in one go (there are 2 methods available, since there are 2 ways to root)
What's new:
June 24, 2015:
1. Fixed: COM Port not detected completely (reported by @re_di)
2. Fixed: pushing of BusyBox and Sharpening Script Mod happens only if user selects rooting, so those who select to ONLY install TWRP will not get BusyBox and Sharpening Script Mod (and without BusyBox, boot.img will not be "bump'd")
Older versions:
Update Notes:
June 10, 2015 Update: ImageprepGUI v2.5 Released
Thanks to @digital-bug for sharing the new method of rooting the LG G3. This new approach has the same end-result and effect as the existing methods. Where it's different is how it is being executed. Instead of a Linux Shell Script, it makes use of an "indirect" input (like "piping"), as if the user manually entered the command via a keyboard.
AS ALWAYS, BACK UP FIRST BEFORE TRYING!
Update Notes for Previous Versions:
DISCLAIMER:
This product is not an official LG software and is therefore not endorsed by LG Electronics in any way. As such, this is a 'try-at-your-own-risk' approach. Please make sure to back up your important files when trying this for the first time. I take no responsibility for any undue outcomes resulting from the use of this software.
ABOUT IMAGEPREPGUI:
Imageprep is NOT a one-click application, and it is intentionally created to be so. Because its objective is to support multiple models/variants of the LG G3, it is developed in a way that the process will pause or exit if something is "off", so expect that there will be pop-up messages every now and then. Think of them as "security measures" to reduce the mistakes from a user point-of-view. In other words, Imageprep takes a balanced approach to automation, features, and "mistake-proofing" in order to provide a virtually seamless experience.
In order to support multiple LG G3 models/variants, Imageprep involves the ability to download TWRP Custom Recovery (recovery.img) for your specific LG G3 model/variant. If you are not comfortable with what is being downloaded, or if your device is not listed, there is an option to place a copy of your TWRP custom recovery (recovery.img) manually. Other image files (aboot.img and laf.img) will be extracted via the "KDZ and TOT Extractor Tool" which will be done automatically.
Outside of downloading and/or extracting, the rest of the actual rooting process is done automatically, just like how Imageprep was in its early stages.
FINAL WORDS:
Having no prior background in programming, this is my first-ever attempt to create a GUI application. While I have tested this application extensively and to the best of my abilities, nothing is perfect. Hence as a general rule: always back up your important data before embarking on activities such as this!
Imageprep is continuously evolving and is therefore a work-in-progress so I am open to suggestions, requests to add more LG G3 models/variants, and even small talk via chat or forums. I always strive to visit the XDA forums to respond to queries or Private Messages whenever time allows me.
I hope this application helps you in every simple way. Enjoy!
With kind regards from the Philippines,
- topet2k12001 @xda[/URL]
CREDITS:
@Chainfire for SuperSU.
@autoprime for his tutorial on “Manual Firmware Update” to keep root/”bump’d”, and for guiding and giving clarity by explaining what happens in the background when I conducted my experiment.
@Skin1980 for allowing me to use the commands from his Sharpening Script Mod (for sharpening options) as well as the commands for "live bumping" ("bumping" on-the-fly) of the boot.img.
@jcase for putting up the the “Stump” thread. Without “Stump” we would not have enjoyed “root” functionality of the LG G3.
@thecubed for “Bump”. Such a wonderful tool. It opened the doors of customization for the LG G3.
@bullghost for the “KDZ and TOT Extractor” tool. This nifty tool allowed us to extract the important components (partitions) of the LG G3’s firmware.
@mronly1love for “Bump Windows version”. It is through this tool that I was able to “bump” my TWRP 2.8.4.0.
@hoangnova for his post about the partition layout of the LG G3. It helped me confirm how I should flash aboot.img.
@itsbighead for his post that helped me understand what aboot.img, laf.img, and sbl1.img meant, and for the same post that explains what causes the LG G3 to boot into an error screen that says “certificate verify”.
@gzkenny from bbs.gfan.com for “D858HK TWRP 2.8.4.0”. It is a purely Chinese website and I actually spent time understanding everything even with Google Translate. I’m not sure if he/she will able to read/understand this but I thank him/her too.
@6ril1 for sharing to me how to "bump" a boot.img. Also thanking him for sharing a secret/tip, which actually inspired me to start learning how to program (I'm starting with simple scripts for now). This is the reason why I was able to come up with "imageprep".
@Unjustified Dev for sharing a method of rooting the Android Lollipop without downgrading to Kitkat.
@zurny for proof-reading the guide and pointing out clerical errors or any other errors that may cause future problems for the readers.
@DE52 and @ ravi.vydianathan for spreading the word about this thread and helping to explain the logic to fellow XDA members
@avicohh for automating the rooting commands via a script
@jac10000 for modifying the scripted rooting commands to add TWRP
@somboons for One Click ROOT+TWRP Recovery for Lollipop Stock Firmware36[ANNOUNCEMENT][SCRIPT] Imageprep: One-click solution for TWRP and BUMP v 1.5
Hi Friends,
New version 1.5! Please visit Post #1
Old/Previous Method is archived below for reference purposes.
301. EXTRACT
This is a "sub" tutorial or how-to on extracting the necessary image files from an LG G3 firmware (KDZ or TOT)
In this example, we are extracting Lollipop system.img, boot.img, and modem.img based on the "Kitkat Downgrade" method.
For the "No Downgrade" (Manual and/or "Imageprep) method, it's the same procedure...only different files to extract.
23Troubleshooting and Q&A
Q: No radio signal (wifi, 2G/3G/4G/LTE)
A: The Lollipop modem.img was not flashed because you forgot to rename the modem_XXXXX.img as modem.img. Or, you forgot to put modem.img in the "flash2" folder. Remember, the Flash2Modem.zip script is programmed to look for modem.img in the "flash2" folder.
A: You have various versions (Kitkat and Lollipop) of boot.img, modem.img, and system.img and you accidentally mixed them up. Make sure that you organize your files properly (put them in folders) and then try the process again.
Q: I get the “certificate verify” error when booting to Android.
A: The Lollipop boot.img was flashed successfully, but was not “bump’d” because you forgot to flash the Sharpening Script Mod BEFORE booting to Android as per the tutorial. Also, make sure as well that at the end of the Sharpening Mod Script, un-select the box for rebooting. You should reboot from TWRP’s main reboot menu and not from the Sharpening Script Mod.
A: You have various versions (Kitkat and Lollipop) of boot.img, modem.img, and system.img and you accidentally mixed them up. Make sure that you organize your files properly (put them in folders) and then try the process again.
A: You got adventurous and flashed the Lollipop aboot.img to the device.1. Hopefully you had a “bump’d” TWRP before you followed this procedure.Q: After following the procedure, the phone boots to LG "Life's Good" but after that, I don't see the splash screen/boot animation. Instead, I just see a black screen with "security error" written in the middle of the screen.
2. Extract the Kitkat aboot.img from your Kitkat KDZ (the Kitkat version that you were on prior).
3. Power off the device.
4. Boot into TWRP (yes you can boot to TWRP even with that error – as long as you had TWRP installed prior).
5. Plug the device to your computer. The device will open/show in Windows File Explorer. Transfer the Kitkat aboot.img to your Internal Storage.
6. Power off and then boot to TWRP again, and then reflash aboot.img.
7. You may end up booting properly to Android but losing “bump’d” hence, you will lose TWRP. That’s fine.
8. Assuming you are able to boot properly to Android, install Android Terminal Emulator.
9. While in Android, install the “bump’d” TWRP via Terminal Emulator, following the steps from the “Bump” thread.
10. Power off the device and boot into TWRP.
11. Flash the Sharpening Mod Script. It will “bump” your Lollipop boot.img properly.
12. Reboot to Android.
A: The Lollipop boot.img was not flashed because you forgot to rename the boot_XXXXX.img as boot.img. Or, you forgot to put boot.img in the "flash2" folder. Remember, the Flash2Boot.zip script is programmed to look for boot.img in the "flash2" folder.
Q: I seem to go into a “boot loop” to TWRP.
A: Common mistake is that people accidentally flash recovery.img to the “Boot” partition, or flashing boot.img to the “Recovery” partition. Reflash the proper Image file to the appropriate partition. If the problem persists, @autoprime created a flashable zip that will fix this problem.
Q: I get the “certificate verify” error when booting to Download Mode, or I can’t boot to Download Mode.
A: You got adventurous and flashed the Lollipop aboot.img, laf.img, or sbl1.img (or other partitions that were not covered in this tutorial) to the device. See long answer from above.
Q: How do I "bump" my custom recovery (TWRP)?
A: D858HK users: you can download a copy from the "Requirements" section in Post #1. Popular variants: the more popular variants (like the D855 - International variant) are very well supported; please search for TWRP as a keyword under the LG G3 section. Less popular variants: there are two (2) tools that you can use. One is "Bump Windows version" and another is "Open Bump". It's easy; just drag-and-drop your custom recovery image (TWRP) to bump.exe (for Bump Windows) or open_bump.py (for Open Bump).
Q: Okay, now I have "bump'd" my custom recovery. How do I install it? I obviously can't flash it via TWRP because I don't have it installed yet.
A: There are two ways to do it. One is done manually. You need to be rooted (Kitkat) and should have Android Terminal Emulator installed. And then you will have to enter some commands. The other way is to do it via "Flashify" (it's an app). For details and instructions, please visit the official "Bump" thread; Post #1.
Q: Do I need to have a custom recovery (TWRP) installed? There are not a lot of custom ROMs for the D858HK anyway so it doesn't make any sense.
A: Yes, you do. Even if you do not intend to install custom ROMs. Installing custom ROMs is just one of the features of a custom recovery such as TWRP, but remember - its main purpose is to provide you with advanced options of recovering your device in the event of a "brick" situation. I have had many instances when I totally "bricked" my device and was saved because I created a full system backup using TWRP. Oh, and make sure that you have installed TWRP and created a full system backup while you are in Android Kitkat!
Q: Do I need to "bump" my current (Kitkat) boot.img and flash it to the device too, before I follow this tutorial?
A: So I downgraded back to Kitkat and tried upgrading again. One with a Kitkat "bumped" boot.img, and another without (stock). In both scenarios, the device was upgrade properly (with root, "bump'd" boot.img, and "bump'd" TWRP). I therefore conclude that it doesn't matter. When you update to Lollipop as per this tutorial, you will end up overwriting the Kitkat boot.img with the Lollipop boot.img and "bumping" anyway (at the part where you flash the Sharpening Script Mod).
Q: There are new threads for rooting Lollipop without downgrading. Here and here. How is your method different?
A: Yes I have read them as well. Great guides, actually. However, those are strictly for rooting only. No custom recovery, no "bump". If you want to maintain "bump'd" boot.img and "bump'd" recovery.img (custom recovery such as TWRP), you will still end up having to follow the steps in this guide - downgrade to Kitkat first, extract Lollipop KDZ firmware, and flash only system.img, boot.img, and modem.img. If you are not tinkering around and are confident enough that you won't do adventurous things with your device, it's okay not to have a custom recovery. Therefore, merely rooting your device would be sufficient. In my case, I have "bricked" my device multiple times and was saved by custom recovery, so I would say I need it.
I asked the question in one of the threads: http://xdaforums.com/showpost.php?p=59328257&postcount=9
But eventually, I already saw the answer. Fellow XDA member (Recognized Contributor) @6ril1 also confirms this: http://xdaforums.com/showpost.php?p=59325441&postcount=55
So, I created another guide (within this thread - see First Post for the link) on how to achieve that.
Q: After following the how-to guide, I lost my Download Mode! Whenever I try to go to Download Mode, it just hangs and show a "Certificate Verify" error!
A: This happens when you followed the "No Downgrade" approach and did not flash Kitkat versions of the "Boot Stack" (persist.img, dbi.img, laf.img, sbl1.img, rpm.img, and tz.img). The how-to guide for "No Downgrade" approach has been updated accordingly to include this step. Those who followed the "Kitkat Downgrade" approach do not need to flash these image files anymore because they are already on Kitkat version.
There is an easy way to do this. XDA member @6ril1 created a TWRP-flashable zip file to automate it. The zip file was originally created for the D855, but you can replace its contents with ".img" files for your LG G3 variant. Just follow the instructions in the link provided.183. Flashing
March 15, 2015 Update: these are the steps from the original "No Downgrade" Manual Approach. There is now an automated script called "Imageprep" that makes the process more convenient for you by entering only a single command in the Android Terminal Emulator. Head over to Post #153 for the details!
