[G3 General] topet2k12001:
Responses 03.21.2015

HI @zuixian,

(a) No. You only need to follow the steps in my video tutorial (and written how-to). You do not have to use the same exact files. Please use the corresponding files for your LG G3 model/variant.

(b) You need Kitkat Boot Stack: aboot.img (Android Bootloader), laf.img (LG Download Mode), sbl1.img, dbi.img, rpm.img, persist.img, tz.img. Rename them to "kitkat-xxxx.img" where "xxx" is the name of the file. Save them to /sdcard/imageprep/kkimagefiles.

Hi @cre4per and @lr89stang,

Which method did you follow:

1. "Kitkat Downgrade" method

2. "No Downgrade" method

3. "Imageprep" method (this is basically an automated version of the "No Downgrade" method)

If you followed "Imageprep", can you remember if you flashed only the Kitkat LAF.img AND ABOOT.img, or the entire Kitkat Boot Stack as well (dbi.img, persist.img, tz.img, rpm.img, sbl1.img)?

While most users say that flashing only Kitkat ABOOT.img and LAF.img are enough, other users say that they needed to also flash the entire Kitkat Boot Stack, which is why I provided that option in "Imageprep" version 1.4. This option comes in after the "Congratulations!" message.

Hi @Tornisyourdaddy,

Please clarify what you meant by "restore to stock". Did you mean you reflashed the device via KDZ/TOT method? And when you meant "restore to stock", did you mean you reflashed to the latest Kitkat firmware or the latest Lollipop firmware (please mention the version as well, e.g. 20C/D, etc.)?

Reason I asked is because you mentioned you restored to stock "with the same files you used before". What was the Android version of the "files you used before"? Kitkat or Lollipop? Depending on your answer, you might have introduced an extra "variable" to the process which may have led to the problem.

To which, my recommendation in my how-to is to always "start fresh" and to not use files that were used in a prior attempt. This is because in any of the three (3) methods, we are effectively extracting files with the same file name (both from a Kitkat firmware and a Lollipop firmware), and it can get confusing sometimes (believe me there are times I get confused and inadvertently flashed the wrong file - even if I have renamed them).

My tip is to always delete the files after using them (on the device). If I wanted to have a backup of the extracted files, I always put them in properly-labeled folders in my PC.

The fact that you can go to "download mode" and "recovery mode" means either:

1. You were able to "bump" your Lollipop boot.img and flash it to the device, so it already bears a Kitkat signature. However, the aboot.img is still on Lollipop (you can simply boot to TWRP, go to the built-in Terminal Emulator of TWRP, and manually flash the correct files via the "dd if=/blah/blah/blah commands).

2. You flashed a Kitkat boot.img ("bump'd" or un-"bump'd") to the device.

...etc. You get the picture. :) I have re-worked version 1.4 to be as "fool-proof" as possible, where the only failure point of the process is when a user will save the wrong image files to the /sdcard/imageprep/kkimagefiles folder. This is so that it will be easier for me to troubleshoot.

The fact that you are getting "Certification Verify" or "Security Boot" error is a certain indicator that you have the incorrect boot.img or aboot.img. It's just one or the other. I had it all documented in the "Troubleshooting and Q&A" portion of this thread, in Page 1.

And it's not wrong to insist that you had the right version of the files in the correct locations. Many times I thought I did...but trust me, I make mistakes too. I have re-flashed my LG G3 multiple times already because I make it a point to test "Imageprep" before I release a certain version. :)

Outside of that, if you are 120% sure you had the right files at the correct location, then the only variable left is the LG G3 model/variant in itself (I heard that there are more "unique" variants like the Verizon and T-Mobile ones).

Friends,

Remember that "Imageprep" is nothing more than an automated version of the "No Downgrade" method. Inside my script is the exact same commands that are in my "No Downgrade - Manual" method, just chained together so that users will only have to type in a single command. The only "extras" that are in the script is the "Sharpening Mod" and "Live Bump" that I asked permission from @Skin1980 to use. Plus, I have re-worked "Imageprep" version 1.4 to "fool-proof" it a bit. The only failure point is when a user saves the wrong Android version of their image files to /sdcard/imageprep/kkimagefiles, and/or an un-"bump'd" or wrong version of TWRP to /sdcard/imageprep/twrp.

So more often than not, it is a case of wrong version of image files saved rather than the script itself. Everyone is free to inspect the contents of the script anyway (part of forum rules or "open-source" rules), and you will see that it is nothing more than the actual commands in the "No Downgrade" manual approach, put together in a single script file so that all of these commands will execute in an almost automatic fashion.