yashsingh1/xdaforums huggingface dataset:
[G3 General] topet2k12001:
Very Observant!

Hi [MENTION=5867010]mlazim14[/MENTION],

Sorry for the delay.

Ha!!! Very observant. You noticed that too. :) I have been working on a version 1.3 because I also took notice. I am doing a final test and will upload after responding and testing. Give me maybe 20 minutes after I submit this post.

Finding:

I had a minor error with the script.

I programmed the script in a way that:

It will extract and back up your existing (Lollipop) BOOT partition

Then, the script will save it as lollipop-boot.img in a system folder, and NOT the Internal Storage (a.k.a. /sdcard). The reason is because "bump" and "oversharpening adjustment" will not work

Apparently, I left an old command in my script that copies the "bump'd" Lollipop boot.img (with the user's selected sharpening level) to /sdcard, and then flashes the /sdcard copy to the BOOT partition

As an effect, the "sharpening level" that the user selected will not take effect.

So I have found out that old command and deleted it. I will do one final test and then release it as version 1.3.

Please stay tuned. :)
[G3 General] hlucky:
Hi topet2k12001,

This is really the last one!...

I've seen you rewrite the procedure at page 16, #153 of this tread.

Under "where do I get it", on... "or click me" if you click you go to MEGA and download the first version, not the last one! I've checked, first script..

Luc
[G3 General] topet2k12001:
Version 1.3 is out!

Hi @hlucky,

Yes I was still editing. I just finished it. :D I removed the "Mega" link and instead, I chose to just update the attachment of Post #153 as it is faster that way. Very observant too!

ANNOUNCEMENT:

Version 1.3 is out! Please read Post #153 to know what has changed. Issue of "sharpening adjustment" not taking effect has been fixed. However, please (again) read the instructions!

Thank you for testing and please do not hesitate to let me know of any issues with the script! Also, please don't forget mention your LG G3 model/variant! :)
[G3 General] mlazim14:
Thanks for the dedicated work topet2k12001! I ran 1.3, and it looks like the bump worked properly and everything however I still appear to be having the oversharpening issue. This must be driving you slightly mad, I apologise! Hopefully its something on my end...

EDIT: Just thought I'd note that I used the 'reboot' command at the end of the script as advised, turned the screen off after reboot - and performed another reboot using the power button just in case, but the white halo is still present.
[G3 General] topet2k12001:
Hm...I tested it and it worked properly for me.

Oh by the way: upon reboot, did you turn off the screen, waited for a few seconds, and turned it on again? You need to do this upon first boot as per instructions from the original author of this fix/mod.

Just like you, I like sharpness disabled (set to zero). That's why I noticed that version 1.2 was not working properly. I tested version 1.3 and that fixed the issue for me. Since I just edited the script, I could really see the difference (it's 5am right now and I'm in a dark room so I can really see it). Maybe try going to a darker room too?

EDIT: I saw your edit. :D

Try this:

My script backs up the original Lollipop boot.img. It's saved in /sdcard/imageprep/limagefiles. Look for a file named lollipop-boot.img.

Put a copy to your Internal Storage (/sdcard).

Flash it manually via Android Terminal Emulator:

su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/lollipop-boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot

REMEMBER: YOU CANNOT REBOOT TO ANDROID AT THIS POINT! THIS IS BECAUSE CURRENTLY, YOU JUST FLASHED THE ORIGINAL, UN-"BUMP'D" LOLLIPOP BOOT.IMG. IF YOU TRY TO REBOOT TO ANDROID, YOU WILL GET A "CERTIFICATE VERIFY" ERROR. HOWEVER, YOU CAN STILL REBOOT TO TWRP CUSTOM RECOVERY, SO THAT'S A SAFETY FEATURE THAT I CONFIGURED IN MY SCRIPT (THE SCRIPT FLASHES CUSTOM RECOVERY FIRST AND FOREMOST).

Still in Android Terminal Emulator, re-run the "imageprep1.3.sh" script.

Go through the entire process like you did (there aren't any options that will screw it up anyway).

Reboot the device.

Upon reboot, open your Messaging App (SMS) and observe it. Within a few seconds, turn off the display (double-knock), wait for a few seconds again and then turn it back on.
[G3 General] mlazim14:
Thanks for the quick reply, and I did indeed. Went into a dark room and it does certainly seem to have improved - its only when I put a dimming screen filter when the halo appears. Perhaps there still is some sharpening that can't be fully removed and I'm just being too pedantic! It looks good, thanks for the great work.

EDIT: Hahah woops! Sorry for not giving you time - we've managed to create two parallel conversations through edits ;) Yeah it certainly looks like a success, it's probably just that I had the dimming app making it more prominent. I'll leave it there, thanks again!
[G3 General] topet2k12001:
Hahaha, you're too quick to respond. I just finished my response to your previous post. :)

Good to know! Yeah, I did read in the related threads that it will be more noticeable in a dark environment. In my case I love to put my display brightness to the lowest so maybe it's an eyesight thing (I got used to it), and therefore I can notice it better even in a brighter environment.

They also have some websites that you can use to compare; I forgot the exact post #, but check out this original thread. Please do let me know of the Post # in case you find it...I was reading it earlier (too bad I forgot to bookmark it).

EDIT: yes, I remember. I already have my sharpening to zero (disabled)...but when I installed some "dimming filter" apps, I still noticed it. I think it's normal. If you used the default brightness (minimum) and not use "ultra-dimmer" apps, I'd say it worked well. :)
[G3 General] Jaaaaay:
Hi, im wondering if you could help me out.

Last night I used your old method to get from Kitkat to Lollipop v20h on my D855.

The first time i attempted it I messed up and got a security error or something, turns out i forgot to bump TWRP (oops), i thought i had a bumped version from before, turns out I didnt.

Anyway, i bumped my TWRP, then followed the extraction and transfer steps correctly, and now its working great, apart from the signal is a bit poor, and under Software Info in settings, it says Baseband Version: unknown, could this be the reason why? And how can I fix it?

Thanks in advance
[G3 General] topet2k12001:
Hi @Jaaaaay,

Baseband....hm. Have you flashed the Lollipop-version "modem.img" already (as written in the old version of the guide)? I'm assuming you followed the "Kitkat Downgrade" approach, since you mentioned you are coming from Android Kitkat.

EDIT: I'm about to go to sleep (I have work in the early afternoon). Your problem is "fixable". That's what I can tell. I can check my Private Message Inbox later. Best of luck!
[G3 General] Jaaaaay:
Oh thats good news, I hope you can help me fix it.

Yes i flashed the boot.img, system.img and modem.img as per the instructions, so yes, i have flashed the lollipop version of the modem, is this where the problem lies?

EDIT: I came across a v20i modem over in this thread, i flashed it using TWRP, and its seemed to have worked, i've now got a baseband version, and the signal has improved slightly, but its still not excellent, I shall test it tomorrow when im outside.
[G3 General] jfedorchuk:
Hey so i followed all your steps and it gave me some errors about not being able to find certain things then after the sharpness settings it stopped. I typed in reboot and the screen shut off and now I can't turn my phone on. It's completely unresponsive - won't even boot into download mode.

Any help please?
[G3 General] lethoncbon:
wrong rom version

Hi,

first thanks for the super detailled tutorial, that's an impressive work :)

My problem : I followed every steps until I realized that I used the wrong Rom for my phone (flashed with d852G instead of d852).

My phone now gives me the security error, and flashing the correct boot.img doesn't seem to solve anything. I also tried to reflash system.img with the good one, but it doesn't seem to do anything either.

Any idea how to flash back to the correct version?

note: I also tried to go back to KK with LG flashtool, but I get an error saying I'm trying to flash the wrong model (my phone is recognised as a d852G...)

Many thansk!
[G3 General] hlucky:
Hi topet2k12001,

Just wanted to thank you again for your work on that script.

Just run version 1.3 of imageprep.

I'm on Bell D852. It went clean, great. I opted for Laf partition only(select no), and use default 40 for display sharpness.

Tested download mode, working OK with only laf.

All good, thanks in the name of all users,

Luc
[G3 General] aitanoddl:
Help meeee

HELLO HOW I DID EVERYTHING IN THE GUIDE BUT WHEN THE RESTART PHONE REMAINS WITH BLACK SCREEN AS IF does not come on, I HAVE TRIED TO GO BUT NOT download mode Go ... HOW CAN I HELP
[G3 General] topet2k12001:
HI [MENTION=225078]lethoncbon[/MENTION],

Indeed you can't flash your device in Download mode due to mixed versions of partitions. You can fix that in custom recovery (TWRP). Can you still try to boot to TWRP? The script flashes a custom recovery (if you put your bump'd custom recovery in the correct folder before running the script).

Download and extract the correct firmware versions on your PC.

Boot the phone to custom recovery and plug it to your PC.

Transfer the correct IMG FILES to your Internal Storage.

In TWRP, you can actually run "Terminal" commands.

From here, you can manually flash the correct partitions. Go to First Page and look for the link to the instructions for "No Downgrade" approach...basically it's the manual version of the script. :)

You need to flash the correct Lollipop images: BOOT.IMG and LAF.IMG. Also SYSTEM.IMG because you mentioned that you flashed it (we don't know what version you flashed). At this point, your BOOT.IMG and LAF.IMG are now consistent with the same version. :)

Then, download the "Sharpening Script Mod" of [MENTION=2174433]Skin1980[/MENTION]. Run (flash) it in TWRP. Aside from the sharpening adjustment feature, it will "bump" your BOOT.IMG.

Try to reboot to normal Android.

Hi Friends,

Try to pull out the battery and then put it back on, then turn on the device.
[G3 General] aitanoddl:
NO GO WRONG NE NE IN NORMAL MODE DOWNLOAD , ACCORDING TO ME IN HARD BRICK is , I FOLLOW THIS GUIDE BUT THEN ALSO NEEDED MONEY http://xdaforums.com/lg-g3/general/fix-unbrick-lg- g3 - stuck- qualcomm - hs - usb - t2933853
[G3 General] samorgs:
Your english is not making a lot of sense, presuming your saying you have hard bricked your phone.

You will need to give more info on exactly what you have done not just saying you followed the guide. You need to let them know exactly what you did and the order you did it.

Also no need to shout in your posts, that is just being rude and will not get you any help as people will just ignore you.
[G3 General] aitanoddl:
excuse my English, then the procedure I did was download the KDZ for my terminal and I extracted as trained all the files in order to create the .img I took the super and I turned on the extension .zip .img I installed busybox and I launched the terminal, I gave the commands I came out recovery aborted and ended the procedure ... I wrote in the terminal and restart from there my terminal is not lit anymore. it does not go into download mode in recovery and it is not recognized by pc me qualcomm hs-usb qdloader 9008 ... sorry I had not realized yelling are a bit rough
[G3 General] shaajrocks:
hi, first off thanks a ton for creating a method to be able to install a custom recovery !

I loved kitkat with xposed, I didnt use a custom rom, xposed could do most for me !

But when lollipop came, I blindly removed root and OTAed lollipop, biggest mistake of my life, waited 3 months and when on the edge of downgrading and and re-rooting, I was finally able to root without downgrading using the Unjustified Dev's method, and when finally xposed is made possible for lollipop with a limitation that a custom recovery is needed, I was redirected to your post !

So i have the international version of the LG G3, 32 GB, stock lollipop rooted, and i have installed busy box and installed it from within the app and also installed terminal emulator !

I have downloaded the same firmware that my phone has and extracted it using the KDZ extractor and followed your " 1.EXTRACT " method and was able to do all the steps correctly !

but I have only the "" boot.img , modem.img and system.img "" (img1) and you have requested to have these files "" Extracted Kitkat Boot Stack (aboot.img, dbi.img, rpm.img, persist.img, sbl1.img, laf.img, tz.img) "" where to obtain the rest of the .img files ? do I just rename the .bin of the extracted .dz file (img2) like what I did in the merge_output folder !

can you/anyone please babysit me through the steps !! any help would be appreciated !
[G3 General] topet2k12001:
Hi [MENTION=4444139]shaajrocks[/MENTION],

For the "Imageprep" Method (auto-script), you need to download the latest Kitkat Firmware for your model. And then extract the said files from that one.

Yes, rename the files to "kitkat-***.img" (for example: kitkat-aboot.img, kitkat-laf.img, etc. etc.) and then place them in the "kkimagefiles" sub-folder of the "imageprep" folder.

IMPORTANT: Make sure that you are changing the actual file from ".bin" to ".img" - not just the file name!

The instructions are at post #153 of this thread (Imageprep).
[G3 General] shaajrocks:
Thanks for the reply [MENTION=5231281]topet2k12001[/MENTION]!

so its like I have to extract the "" boot.img , modem.img and system.img "" using KDZ of the latest lollipop firmware.., and extract the "" aboot.img, dbi.img, rpm.img, persist.img, sbl1.img, laf.img, tz.img "" using KDZ of the latest KitKat firmware for my phone right ? or extract All Off The Above using KDZ of the latest KitKat firmware alone ...... ?
[G3 General] jfedorchuk:
Phone is unresponsive, removing battery does nothing and it shows up in my device manager as qualcomm hs-usb qdloader 9008. No combination of buttons will do anything with the phone. After reading your last post - the kitkat boot images that i have are all .bin. I did not change them to .img files so i assume this is what bricked it?
[G3 General] aitanoddl:
guys I have the phone locked in it does it in revovery and downloadmode You come revive Solutions ?
[G3 General] badchip:
[MENTION=5231281]topet2k12001[/MENTION], I have one question and I'd be very happy if you can answer, Is it possible to download a rom for d855 on d858hk (even if dual sim not work, i don't use it). I tried to flash 2 roms but all I had is a soft-brick (device stuck in fastboot) and I had to flash 10D kdz to make device working again. Is there any method? Can I edit custom rom and put boot images (boot.bin) of d858hk inside custom rom? or something like this?

Thank you for your work, all your posts are useful to me

edit: oh by the way all the images in post #2 are gone :(
[G3 General] topet2k12001:
Responses 03.17.2015

Hi Friends,

Just got home from work. Really sorry but I have been very busy lately. But I promise I will try my best to check this thread at least once a day.

Hi @shaajrocks,

So it's like this:

"Kitkat Downgrade" method: you need Lollipop boot.img, modem.img, and system.img

"No Downgrade" method: you need Kitkat aboot.img, dbi.img, laf.img, rpm.img, persist.img, sbl1.img, and tz.img

"Imageprep" method: same as "No Downgrade" method since "Imageprep" is merely an automated version of the "No Downgrade" method

Hope this clarifies for everyone as well. Maybe I should add this to the first page. Also, I purposely kept/maintained the old methods because they do work still, and they are good as "backup" methods in case you run into trouble with "Imageprep".

ANNOUNCEMENT: IMPORTANT POST AND ANSWER!!!! READ BELOW, EVERYONE!!!

Hi @aitanoddl and @jfedorchuk,

It seems both of you did the same thing which resulted to both of you having the same result.

Yes, @jfedorchuk is correct. That is the cause of the problem, resulting to "bricking" the phone. It is very important that you not only rename the file NAME itself, but you need to effectively change the file TYPE (meaning, you need to be sure that the image files will change from ".bin" to ".img"). The steps to do it are in my old tutorial (check First Page, and then click "Show Content" or "Unhide Content").

This is the reason why I need everyone to really read carefully first and not blindly follow steps - this goes for ANY tutorial/how-to/guide out there. Don't go rushing things. There is a reason why my posts are "too wordy and long". I even put a reminder in the script itself, which users have to confirm by typing "yes".

Please try following the instructions from this thread: http://xdaforums.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853

Friends,

I'll put more security features in the script to make sure that future instances of this mishap can be avoided. Please wait for version 1.4 (although please expect my progress to be slow this week as I am busy with work).

Hi @badchip,

Thanks for informing me of missing images. I'll try to use another free image-hosting site and fix all my tutorials.

I remember I have asked the same question elsewhere (I can't remember), and unfortunately the answer is "no". The difference between D855 and D858HK are not a simple case of being single-SIM versus dual-SIM. This means that someone has to create a custom ROM specific only for the D858HK.

Also, most custom ROMs for the D855 are built from CM (Cyanogenmod) as the "base", where the D858HK is not supported.
[G3 General] badchip:
I was thinking if I put the boot.img from stock KDZ inside custom rom (for example: cloudy 1.2) then repack the rom and flash it, maybe it'll work? It's something that I have to try, maybe I'll get lucky (or I'll probably end up with a brick that I can hopefully recover)! Because I'm sure the hardware is 100% the same between the two devices.

Thanks for the response man and all the good resources you give us :)
[G3 General] topet2k12001:
Hi @badchip,

The issue is not about hardware being the same or different. It's the software. Here's a hint: why do you think there is a separate KDZ or TOT download for each model/variant of the LG G3? ;)

Trust me, I have thought of it the same way previously and I remember now: I asked the developer of Euphoria OS and the response I gave you is the same thing he told me. I already tried what you have tried and about to try, if that helps. :D

What you're about to try (put stock boot.img into a custom ROM)...I wish it were that easy. I may be mistaken but based on my stuff I read, the "boot.img" is actually the "kernel" of the Operating System (or it houses the kernel). The kernel of an OS is like the "base" or the "heart" of it all. It's the one that "communicates" (or facilitates "communication") between the hardware and the software.

EDIT: please don't get me wrong; I'm not trying to discourage you. I have the same hopes up to now, and as I mentioned to other members, the original reason why I came up with this how-to is because I wanted to give a temporary fix/solution to get TWRP custom recovery to the D858HK, which will hopefully attract developers to create a custom ROM for this specific LG G3 variant/model. Another reason is that I am trying to learn all of the "developer stuff" because I don't intend to sell my LG G3 for a long time (I wanted a dual-SIM phone that has relatively high specs).

EDIT #2: In case you are adventurous enough and didn't heed my "warnings", just a heads up: you won't be able to recover via Download Mode. You can boot to Download Mode, yes, but if you try to reflash the D858HK firmware to your (already) chop-chop LG G3, the LG Flash Tool will give you an error saying something like "Mismatch".

You can recover via custom recovery (TWRP), either by:

1. restoring a full system backup that was created via TWRP (make sure you make one before doing all of this!) - this is what they call a "NANDROID" backup. Basically, a "clone" of your entire system in its last working state (like System Recovery in MS Windows)

2. Manual flashing via the built-in Terminal Commands of TWRP (make sure you have placed a copy of all your Lollipop image files to your /sdcard or Internal Storage!)

How did I know all of this? I tried (as I have told you). :)
[G3 General] topet2k12001:
See you tomorrow!

Hi Friends,

Gotta sleep now.

For important messages ONLY, please send me a PM. For help when you soft-bricked your device or when you are confused with the instructions, please post in the thread. Don't wait for me to wake up, get to work, and go back home before you receive advice/help. :D There are other members who are as knowledgeable and have already tried the procedure with success.
[G3 General] aitanoddl:
I also tried this guide but does not go into the smartphone downloadmode then it is useless, also the discussion was closed xke demanded money to fix ... I have sent my g3 in assistance. a question. it would be better a script already compiled for each variant of the g3? definitely not mistaken.
[G3 General] igoticecream:
Yay!

Got it working following the kitkat downgrade approach (the other method seems to risky for me).

Anyways thanks for teaching us how to get TWRP with Lollipop.
[G3 General] davedwelling:
awesome stuff man

Just what I was looking for man confirmed working on Verzion LG G3 Vs985 you are a life savior
[G3 General] danzel:
D858HK v20D firmware is out... hope my root will stick
[G3 General] danmak89:
Well, this is a total bummer.

Device is bricked after typing reboot. I tried to pull the battery and reboot but nothing. However when I plug the device in to my PC it's showing up. Would I have to run the LG flash tool to restore my device? I can't even boot in to download mode.

EDIT: Please note, unlike other people who have reported this issue, I DID rename the .bin files to .img
[G3 General] danzel:
Looks like I can't do OTA when I'm rooted. This is sad....
[G3 General] topet2k12001:
Hi [MENTION=4046368]aitanoddl[/MENTION],

I don't think it will be practical for me to create a script for each and every LG G3 variant. This website shows you just how many variants of LG G3 are existing: http://lg-phone-firmware.com/firmware-Lg+G3-Tutti-41.html

Also, the cause of your problem (bricking the phone) is not related to the fact that LG G3 has different variants. Assuming you and the other member did the same thing, the reason for the bricking of the phone is due to not properly changing the ".bin" files to ".img" files.

Hi [MENTION=5159277]danmak89[/MENTION],

1. What is your LG G3 model/variant?

2. When renaming the files, it is not enough to rename the file name itself. You need to tick "Enable file extensions" in Windows File Explorer so that you can properly change the file type (from ".bin" to ".img"). You will know you were able to do this properly if the icon of the files changed to a "CD"-like icon. As of this writing, this is the only reason the phone will "fully brick".

3. Any error messages that you saw when you ran the script?

4. You mentioned that the PC still recognizes the device. What does it show on the PC?

Hi [MENTION=224742]danzel[/MENTION],

Yes, this is true and was already mentioned in older threads.
[G3 General] danmak89:
Hi Topek,

1. It's a D855

2. All the icons were CD-icons, I was prompted as well if I wanted to change the file type when I changed the extension (to which of course I said yes)

3. Nope, no error messages at all

4. I see LG USB device in device manager

Might have to wait and take it home to use my PC there perhaps to workaround some admin issues.