[G3 General] topet2k12001:
Hi Friends,

Thanks for all the feedback. I've read through them and working on some improvements.

Hi @ravi.vydianathan,

I see. Could it be that your version is non-rootable? Or maybe others have found a solution.

As far as the COM port, please delete it manually first before trying again. Depending on how you exited ImageprepGUI, it may not have been deleted (although I configured ImageprepGUI to automatically delete it after usage). Or better yet, please wait for the update that I will send out.

Favor: can you run the "reg query" command I gave you from the other page? It's supposed to "copy-paste" the result into a text file. And then, please attach the actual text file (don't copy-paste the content of the text file in a message here). It's very important to me. Thanks in advance.

Hi @Daptonic and @moonlightinwhite,

It's possible that, during the "firmware extract" phase where the mouse moves automatically by itself, you might have had a window suddenty pop up which interrupted the automation (hence the mouse movements and clicks pointed to some other app). As a result, the laf.img was not extracted.

The laf.img is the one responsible for "Download Mode".

But to be sure, I'm inspecting it again. I will keep you posted. As an alternative, you may manually download a copy of an extracted laf.img from my Google Drive (where you downloaded ImageprepGUI). Just make sure you are downloading the correct one for your LG G3 model/variant.

If you are already rooted prior, you may also want to inspect via a File Manager (such as ES File Explorer) on your device. Navigate to /data/local/tmp/ and check if aboot.img and laf.img are there.

If the LED is flashing red and blue at startup, there may be something wrong with the TWRP that you flashed. It may not have been "bump'd" at all. Try to download from another source and test it again. Or, download an "un-bump'd" version and try your luck in "bump'ing" it via the utility in ImageprepGUI.

Hi @Big0013,

I made this to be sure that it will work with a 32-bit Windows OS. Unfortunately I don't have Windows XP anymore. You are very much welcome to try (just back up everything first!)

Hi @boi_echos,

Your username sounds like you are a Filipino. Only Filipinos use the slang/colloquial word "echos".

It's good to hear from someone with a Korean model/variant. I have been waiting for someone with this model/variant to test. :)

Secure Boot Error happens either when your TWRP is not "bump'd" (patched), or when you did not change/flash/replace your Android Bootloader (aboot.img) with a Kitkat version (after you have flashed a "bump'd" custom recovery.img such as TWRP). ImageprepGUI has a built-in utility to try and "bump" your TWRP. It also has a utility to download a "bump'd" TWRP for the F400K.

TIP: when you encounter an error like this, no need for a full reflash (as long as you can still boot to normal Android). Tools available here in XDA like one-click scripts, Autorec, and Imageprep are merely here to automate the process, but those who understand the logic behind it can actually accomplish this manually (by being rooted first, then installing Android Terminal Emulator, then entering some manual flashing commands).

Here's a "flowchart" of manual approaches:

1. Can boot to TWRP but not to normal Android: save a Kitkat version "aboot.img" and flash it via TWRP. Recent versions of TWRP have the ability to flash image files (back then, TWRP can only flash zip files)

2. Can boot to normal Android but not to TWRP: boot to normal Android, make sure you are rooted, install Android Terminal Emulator, and manually flash your "bump'd" TWRP (custom recovery.img) via "dd" command (I believe I have still kept the manual steps in the First Page of this thread)

3. Can boot to normal Android and TWRP, but not Download mode: same process as number 2. Only difference is that you will need to flash Kitkat "laf.img". Or, you can also do it via TWRP custom recovery

Hi @dancrow,

I don't know your LG G3 model/variant as you haven't mentioned it, but I looked at the thread and it seems like it is also based off the One-click script, so I assume it will work.