yashsingh1/xdaforums huggingface dataset:
[LG Optimus G Pro] hkfriends:
Yes, It sounds strange... anyway, I will extract the LG source code again and try just compile it and Loki-patching and flash it to see...

the test before is clone the source from thecubed and just compiled successfully without modification

anyway, it is midnight in here, I will do that tormorrow again, thanks for your help
[LG Optimus G Pro] djrbliss:
You are patching a full boot.img (with ramdisk), not just a compiled kernel, right?
[LG Optimus G Pro] madmack:
I posted a little about the segfault in loki_flash here: http://xdaforums.com/showpost.php?p=43481635&postcount=15

it's one of those memcmp operations that's doing it.
[LG Optimus G Pro] djrbliss:
Could you post the Loki image that's causing the crash and the aboot and recovery/boot that you used to generate it?
[LG Optimus G Pro] madmack:
its that cwm recovery that the thecubed posted in the OP of my referenced post. I'm sure he used the same aboot.img as the one I sent to you earlier yesterday. The CWM image when flashed by dd works just fine.
[LG Optimus G Pro] djrbliss:
Fixed, thanks. Let me know if you run into any more problems.

Now I'll add support for those Korean variants...
[LG Optimus G Pro] thecubed:
Awesome, you're the man.

I'll make sure my CWM instructions are linking to the most recent loki_flash binary in your github. I believe I have it just looking in MASTER, so it should be the most recent you uploaded.

After I get some more testing done I'll release my python LGNPST replacement, so we can just flash these images as a TOT file to the phone without bothering with root/etc (and yep, to satisfy LOKI's requirements, I can also check the build ID/etc before allowing the flash)

Thanks!
[LG Optimus G Pro] djrbliss:
Support has been added for both of these Korean variants.
[LG Optimus G Pro] hkfriends:
yes.... am I doing wrong?

It could be related the ramdisk modified with init.d supported and repacked

I need to do a test again..

---------- Post added at 07:15 AM ---------- Previous post was at 07:12 AM ----------

great ^^...

it seems that F240 L / K ==> the same signature for Korea model

ATT & HK ==> the same signature for "outside Korea" model
[LG Optimus G Pro] kevinwzh:
Dan i got this error,pls help

I compile cwm.lok under the device shell, but got error like below. My device is F240L. pls help.thnks

1|root@android:/data/local/tmp # /data/local/tmp/loki_patch-linux-arm recovery aboot.img cwm.img cwm.lok

tch-linux-arm recovery aboot.img cwm.img cwm.lok <

[+] loki_patch v1.6

[-] Unsupported aboot image.

1|root@android:/data/local/tmp #

I remembered i have flashed a customerization rom before do loki patch.

Could you help check my builde.prop file and update your loki patch file, thnks.

ro.product.model=LG-F240

ro.product.brand=lge

ro.product.name=geefhd_kt_kr

ro.product.device=geefhd

ro.product.board=GKKT

ro.build.description=geefhd_kt_kr-user 4.1.2 JZO54K F240K10l.1364193783 release-keys
[LG Optimus G Pro] hkfriends:
First of all... why you are using F240L machine and the build.prop is F240K ?

anyway, you should dump your current aboot.img from your phone here and let Dan to have a look...

As the source code is shown supported for F240K and F240L

and the aboot.img for K and L are provided by post #13, #14 (I trusted they give the correct aboot.img)

so If your current aboot.img either K or L should be shared the same signature, there is no reason saying "Unsupported aboot image."
[LG Optimus G Pro] kevinwzh:
===================

The rom i flashed was made based the F240K version, and the owner said that it can also be flashed in the L version.

After i flashed this rom, the build,prop file changed to this.

so i attached my boot.img file, pls help about my special case:( thsnk all .
[LG Optimus G Pro] hkfriends:
I compiled Dan's source with echo the pointer address... it is strange that your Aboot is different from F240K and F240L

I think we need Dan to fix this or investigate further... very easy to fix

$ ./loki_patch recovery f240l_aboot.img gkatt-cwm-e98010g.img gkatt-cwm-e98010g.lok

[+] loki_patch v1.6

aboot_base = 0x88efffd8

aboot= 0x7ff20000

ptr= 0x7ff310e0

target= 0x88f110b8

[+] Detected target KT or LGU LG Optimus G Pro build F240K10o or F240L10v

[-] Input file is already a Loki image.

[+] Copied Loki image to gkatt-cwm-e98010g.lok.

$ ./loki_patch recovery f240k_aboot.img gkatt-cwm-e98010g.img gkatt-cwm-e98010g.lok

[+] loki_patch v1.6

aboot_base = 0x88efffd8

aboot= 0x7ff20000

ptr= 0x7ff310e0

target= 0x88f110b8

[+] Detected target KT or LGU LG Optimus G Pro build F240K10o or F240L10v

[-] Input file is already a Loki image.

[+] Copied Loki image to gkatt-cwm-e98010g.lok.

$ ./loki_patch recovery aboot_error.img gkatt-cwm-e98010g.img gkatt-cwm-e98010g.lok

[+] loki_patch v1.6

aboot_base = 0x88efffd8

aboot= 0x7ff20000

ptr= 0x7ff31098

target= 0x88f11070

[-] Unsupported aboot image.
[LG Optimus G Pro] djrbliss:
It's going to be difficult for me to support these kinds of "customizations". Why can't you flash a stock ROM instead?
[LG Optimus G Pro] reider123:
Hi. can you update this device:LG-F240S ?

I tried to flash loki, but it says aboot version does not match, so I attach my aboot and device info.

ro.product.model=LG-F240S

ro.product.brand=lge

ro.product.name=geefhd_skt_kr

ro.product.device=geefhd

ro.product.board=GKSK

ro.build.description=geefhd_skt_kr-user 4.1.2 JZO54K F240S10w.1370567904 release-keys
[LG Optimus G Pro] hkfriends:
Hi Dan

something really went wrong, here is my testing: it is really strange... it seems not related to your LOKI patch

root@ubuntu:/usr/android# abootimg -x boot.img

writing boot image config in bootimg.cfg

extracting kernel in zImage

extracting ramdisk in initrd.img

e.g. Just using the LG E988 clean source to compile a clean Zimage

root@ubuntu:/usr/android# abootimg --create myboot.img -f bootimg.cfg -k ./kernel/obj/KERNEL_OBJ/arch/arm/boot/zImage -r initrd.img

reading config file bootimg.cfg

reading kernel from ./kernel/obj/KERNEL_OBJ/arch/arm/boot/zImage

reading ramdisk from initrd.img

Writing Boot Image myboot.img

root@ubuntu:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok

[+] loki_patch v1.6

[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b

[+] Output file written to myboot.lok

root@ubuntu:/usr/android#

==> then I flash this myboot.lok (with only re-compile zImage from LG source E988)

==> It will keep boot loop (of course I can see the security msg saying unlocked and boot msg)

==> then I re-using the orginal zImage and patched again by LOKI

==> then I flash this myboot.lok again (this boot.img only with patched LOKI signature)

==> Now it works again (of course I can see the security msg saying unlocked and boot msg)

e.g. Just re-pack the original files and perform LOKI patch

root@ubuntu:/usr/android# abootimg --create myboot.img -f bootimg.cfg -k zImage -r initrd.img

reading config file bootimg.cfg

reading kernel from zImage

reading ramdisk from initrd.img

Writing Boot Image myboot.img

root@ubuntu:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok

[+] loki_patch v1.6

[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b

[+] Output file written to myboot.lok

root@ubuntu:/usr/android#
[LG Optimus G Pro] Timisone:
If I port a rom from lg optimus. How do I go about loki flash the rom? Or is this even possible?
[LG Optimus G Pro] kevinwzh:
thnks,Dan.

OK, i will follow u and try to update my device to original system --> V10L, but where can i get the seconde parameter [in.img]

in the below command:

./loki_patch [boot|recovery] [aboot.img] [in.img] [out.lok]

??
[LG Optimus G Pro] djrbliss:
That's the original boot or recovery image that you're trying to patch.
[LG Optimus G Pro] djrbliss:
Next time please make sure you're using the latest version of Loki. This device is already supported because its aboot is identical to the other two Korean models.
[LG Optimus G Pro] reider123:
I use the latest version of loki. I downloaded it. Hmmm......

Edit: Aha! the problem was in TWRP recovery. hahaha maybe I just have to wait til Korean version is out :)
[LG Optimus G Pro] kevinwzh:
ohhhh, can i get the recovery image by using below :

dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/data/local/tmp/mycwm.img
[LG Optimus G Pro] hkfriends:
NO, if u using the original recovery... no need to LOKI

we used LOKI, because we want to use 3rd party recovery program, and LOKI help us to bypass LG security check.
[LG Optimus G Pro] hkfriends:
Edit: Sorry guy, finally I managed to sort this problem........

I can boot a custom kernel (this problem is from LG given me the wrong instruction on config file)

now the LOKI is really working :good:
[LG Optimus G Pro] kevinwzh:
Sure, Dan, I have already rooted and installed the 3rd cwm but i dont know where is it and how to dump it to IMG file for LOKI. thnks for help.
[LG Optimus G Pro] twpsangha:
thank you

thank you!!!
[LG Optimus G Pro] @gbaxh:
Thank you

Dan, THANK YOU for taking the time to make this happen
[LG Optimus G Pro] inyourface09:
Needing device help

my aboot image is unsupported which isn't a shock because the phone isn't. I was hoping to kindly ask if you could add support for my device.

LG Optimus F3 (LS720)

ro.product.model=LG-LS720
ro.product.brand=lge
ro.product.name=fx3s_spr_us
ro.product.device=fx3
ro.product.board=fx3s
ro.build.description=fx3s_spr_us-user 4.1.2 JZO54K LS720ZV5.1368193247 release-keys

I posted on the SGS2 Loki thread i believe it was, I apologize for that seeing as how both these threads haven't been active for a month or so.

Dan can't thank you enough for all the hard work and time you have put into this!
[LG Optimus G Pro] god_md5:
hello djrbliss

Please help to support LG F7 F260S for KOREA version ... Thanks you

here is aboot.img and build.prop

ro.product.model=LG-F260S

ro.product.brand=lge

ro.product.name=fx1sk_skt_kr

ro.product.device=fx1sk

ro.product.board=FX1

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=LGE

ro.product.locale.language=ko

ro.product.locale.region=KR

ro.wifi.channels=11

ro.board.platform=msm8960

# ro.build.product is obsolete; use ro.product.device

ro.build.product=fx1sk

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=fx1sk_skt_kr-user 4.1.2 JZO54K F260S10j.1370308633 release-keys

ro.build.fingerprint=lge/fx1sk_skt_kr/fx1sk:4.1.2/JZO54K/F260S10j.1370308633:user/release-keys
[LG Optimus G Pro] WACOMalt:
Any support for the LG-VS980 yet? (Verizon LG G2)
[LG Optimus G Pro] bb12489:
Second this! I don't get my upgrade until October 5th, but definitely will post files for you then!
[LG Optimus G Pro] bads3ctor:
LG Mach LS860

I am a fan of your work. Thank you for your Loki bootloader bypass.

ro.product.model=LG-LS860
ro.product.brand=lge
ro.product.name=l2s_SPR_US
ro.product.device=l2s
ro.product.board=L2S
ro.build.description=l2s_SPR_US-user 4.0.4 IMM76I LS860ZV7.c755138 release-keys
[LG Optimus G Pro] Heatshiver:
Hi, I have an LG G2 version D802B. I was recommended by Dees_Troy to get a hold of you and ask if you could update Loki for this version? I have the aboot.img in my Google Drive here.

This would be greatly appreciated not only by me, but by numerous others. We are trying to get TWRP to work and could truly use your help.

Thank you!
[LG Optimus G Pro] Chenglu:
Hi djrbliss

Please help to support LG G2 China version ... Thanks so much !

ro.product.model=LG-D802
ro.product.brand=lge
ro.product.name=g2_open_cn
ro.product.device=g2
ro.product.board=MSM8974
ro.build.description=g2_open_cn-user 4.2.2 JDQ39B D80210d.1379696461 release-keys
[LG Optimus G Pro] esimon311:
What about a touch CWM ?

___________________

/Beavers & Ducks!!!!!!\
[LG Optimus G Pro] speedyg0nz:
Appreciate your help in supporting the LG F5 as well. The aboot.img has been attached as instructed.

ro.product.model=LG-P875
ro.product.brand=lge
ro.product.name=l1e_OPEN_ESA
ro.product.device=l1e
ro.product.board=L1E
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.build.description=l1e_OPEN_ESA-user 4.1.2 JZO54K P87510e.1373987755 release-keys
ro.build.fingerprint=lge/l1e_OPEN_ESA/l1e:4.1.2/JZO54K/P87510e.1373987755:user/release-keys
[LG Optimus G Pro] romup:
THX

ro.product.model=SM-N900V

ro.product.brand=Verizon

ro.product.name=hltevzw

ro.product.device=hltevzw

ro.product.board=MSM8974

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=samsung

ro.board.platform=msm8974

# ro.build.product is obsolete; use ro.product.device

ro.build.product=hltevzw

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=hltevzw-user 4.3 JSS15J N900VVRUBMI9 release-keys

ro.build.fingerprint=Verizon/hltevzw/hltevzw:4.3/JSS15J/N900VVRUBMI9:user/release-keys

ro.build.characteristics=verizon
[LG Optimus G Pro] bads3ctor:
Is the aboot image I posted not loki compatible?

./loki_patch boot aboot.img new_boot.img boot.img

[+] loki_patch v2.1

[-] Unsupported aboot image.

Edit: I used 2nd Init Recovery by 985hPaKicK to get CWM on my LS860 Mach which seems to have altered the aboot image I posted previously. I have pulled the aboot image from LG's V8 firmware and it is different from the one I pulled from my device so I'm posting it here to see if it can be loki-fied.
[LG Optimus G Pro] mustbepbs:
Any chance of support for the G Pad (LGV500)? I'd be willing to test.
[LG Optimus G Pro] aatish:
Hi i have one stupid question.

If reflash my 240L with panama 980A rom ... now I want to flash my baseband but I use the recovery lte2jbrecovery.rar. but i flashed my baseband my phone doesn't boot up.

Some user have done it but it doesn't work for me.

Now here is my question if i relflash to stock 240L rom and then install recovery. Will this stay there if I reflash my rom to panama 980H using kdz?

regards,
[LG Optimus G Pro] concaopp:
need support for Optimus GK F220K, please give it a shot!

Name: Optimus GK

build: F220K
[LG Optimus G Pro] the_crevis:
+1 my G Pad is on the way. I will root and then provide info and aboot, I have some experience with compiling from source so I could maybe get a recovery.img sorted.
[LG Optimus G Pro] mustbepbs:
Awesome. I'll be glad to help out once I get back from vacation.
[LG Optimus G Pro] concaopp:
Please help us!!!
[LG Optimus G Pro] bahuy2003:
I have smartphone LG GK f220K. I want to unlock it to flash Cm10.2 of optimus pro E988! But i don't know how unlock it. Help me please!
[LG Optimus G Pro] mustbepbs:
Hello all! I've got an issue (I think?)

Relatively new to all this, no official CWM for my LG G Pad so I decided to tackle the project. I successfully built CWM for my device, patched the recovery.img with loki_patch and flashed it with loki_flash like normal. All of it went swimmingly, but when I went to reboot into recovery, I get this:

https://www.dropbox.com/s/591cd1a349nqfq0/bootingimage.jpg

After that, the tablet boots fine. Any ideas? Did I muck up somewhere? Any help would be appreciated! Thanks :)
[LG Optimus G Pro] youdug:
Hello Dan,

Just wondering if you could update the Sprint LG G2 variant for us.

Everyone in our community would appreciate it very much.

ro.product.model=LG-LS980
ro.product.brand=lge
ro.product.name=g2_spr_us
ro.product.device=g2
ro.product.board=MSM8974
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=g2
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=g2_spr_us-user 4.2.2 JDQ39B LS980ZV8.1385430553 release-keys
ro.build.fingerprint=lge/g2_spr_us/g2:4.2.2/JDQ39B/LS980ZV8.1385430553:user/release-keys

Thank you very much.
[LG Optimus G Pro] youdug:
Hello again Dan,

Sorry, I just reread my post and I meant to say update.

We just recieved an update about two weeks ago to ZV8.

If you could update the Sprint variant to that we would very much appreciate it.

Thank you again.

Sent from my LG-LS980
[LG Optimus G Pro] warduke:
Hi I have a LG Optimus F3 LG MS659 How can I use LOKI to unlock bootloader I also want to install CWM.
[LG Optimus G Pro] PhantomThiefX:
Hello djrbliss,

It looks like you have done incredible work on this and i wanted to pick your brain. I have a LG G Flex d950, I am a developer myself and am no stranger to LAMP development. Here is the thing, I don't want to give you the info on the phone, I would like you to help me learn how to do it myself. I have downloaded the loki zip from github and have all my info and am about to dive in, what pitfalls should I be looking bout for initially? Should I start on a VM spec'ed to device or just start hacking away on the device itself?
[LG Optimus G Pro] AndroidAddict||AA:
I have the LG MS659 (Optimus F3). I just tried to loki a custom recovery.img and I got the aboot error. I pulled the files straight from my device.

Here are the results:

./loki_patch recovery aboot.img recovery.img recovery.lok
[+] loki_patch v2.1
[-] Unsupported aboot image.

I would appreciate any and all help, thanks!

Edit: I am also on firmware C if that helps
[LG Optimus G Pro] hm-s:
I tried loki_patch-linux-x86_64 fromSavoca gihub.

mmommer@ubuntu1:~/Entwicklung/loki-sav/loki-master/bin$ ./loki_patch-linux-x86_64 boot aboot.img recovery.img test.lok

[+] loki_patch v2.1

[-] Unsupported aboot image.

It is the new D802 Vodafone Rom with Knock Code where I pulles the aboot.img.

Can somebody help me with an working loki_patch for Ubuntu 64bit?
[LG Optimus G Pro] shabbypenguin:
why wouldnt you grab the latest from bliss' github?
[LG Optimus G Pro] hm-s:
This did not work for me with Ubuntu 12.04 64bit

Do you have an working Version? Maybe you can help me
[LG Optimus G Pro] shabbypenguin:
the newest version is loki_tool, an all in one tool that patches, flashes, unloki's and more. how did you compile it?
[LG Optimus G Pro] hm-s:
I took that one in bin directory, not compiled by myself.

I have tried compiling but got errors. Can you tell me how I should try compiling and what I need.
[LG Optimus G Pro] shabbypenguin:
well if you looked at the makefile you would see that loki_tool is by default designed to run on arm, not your computer. you need to compile it yourself.
[LG Optimus G Pro] hm-s:
can you tell me which pakets I Need and the correct Syntax to compile
[LG Optimus G Pro] shabbypenguin:
pakets? you just need to edit the makefile to switch it from arm to x86. why are you trying so hard to compile it to make loki images on your computer? the loki tool works on arm and its already compiled so you can just push it to your device and run it that way. or just make a flashable zip of whatever kernel it is you compiled and flash that in an autoloki recovery.
[LG Optimus G Pro] peat_psuwit:
make CC=gcc
[LG Optimus G Pro] peat_psuwit:
Hi djrbliss,

Please help to support LG L90 Dual.

ro.product.model=LG-D410

ro.product.brand=lge

ro.product.name=w7ds_global_com

ro.product.device=w7ds

ro.product.board=w7ds

ro.build.description=w7ds_global_com-user 4.4.2 KOT49I.A1393455031 1393455031 release-keys

.vendor = "LGE",

.device = "LG L90 Dual",

.build = "KOT49I.A1393455031",

This is aboot.img:

https://mega.co.nz/#!UMUzTChZ!vpimrtT_yiyaoToXhqeMQ5YVY2yOK8y369DBE9VUyKk

Thank you.
[LG Optimus G Pro] shabbypenguin:
He doesnt monitor this thread, you ask for device requests on his github, aside from that loki was patched in 4.4 so you are probably going to be told it wont work.
[LG Optimus G Pro] czun:
Aboot image was not supported after i updated my device from 4.1.2 to 4.4.2,it will be better if you update the loki source to support 4.4.2 aboot image.
[LG Optimus G Pro] hoquangthaiholy:
Help!

I can't make loki work on LG Isai 4.4.2. I get error message:

Loki tool v2.1
[-] Unsupported aboot image.

This is my aboot.img

Thanks.
[LG Optimus G Pro] LaDY Vengeance:
The build for our LG Optimus L90 is KOT49I.D41510c. Here is the complete stock boot which has the aboot included.

http://d-h.st/jo2
[LG Optimus G Pro] AndroidAddict||AA:
Loki was patched in 4.4
[LG Optimus G Pro] invaderjohn:
someone out there with some skills want to help out making this work for lg g2 mini? i dont have alot of experience but i can do alot and try things out if i get some help. :)
[LG Optimus G Pro] tangbakhanh:
Pls support for lg lg3. Thanks you
[LG Optimus G Pro] LNRawz:
P875h

OK, this msg is right for the situation with a lokified img.

My problem seems that the P875h won't run the full recovery code. Looking into it.

(leaving the below post as documentation)

Hello.

I compiled a CWM for the P875h.

Then used LOKI and got the recovery.lok. Flashed.

Now, trying to boot into recovery, I get boot loop, right after the LG logo I get this msg:

[860] -------------------------------------------------------------------

[860] Secure booting error!

[860] Cause : Device UnLock!, so Boot Success!

[860]--------------------------------------------------------------------

And I can only leave the loop with a hard reset.

I did patch the boot.lok and the recovery.lok.

This is the P875h not the P875 or VS870 (both know as Optimus F5 as well), so, maybe LOKI isn't fully compatible?

If thats the case, djrbliss, please patch for this device?

__________________________________________________________________

ro.build.id=JZO54K

ro.build.version.incremental=P875h10b.1378974332

ro.build.version.codename=REL

ro.build.version.release=4.1.2

ro.product.model=LG-P875h

ro.product.brand=lge

ro.product.name=l1e_OPEN_BR

ro.product.device=l1e

ro.product.board=L1E

ro.product.manufacturer=lge

ro.build.description=l1e_OPEN_BR-user 4.1.2 JZO54K P875h10b.1378974332 release-keys

___________________________________________________________________

--aboot.img

Thank for any help.
[LG Optimus G Pro] shabbypenguin:
that's an lg issue. You need to zero our the flag in misc.
[LG Optimus G Pro] LNRawz:
I see. That is for the boot loop into recovery, right?

Just compiling the CWM, patching with LOKI and flashing is not enough?

To boot into recovery there is another step for LG, so CWM takes control?

I am trying to find out how to debug this boot process.

Thankx.
[LG Optimus G Pro] LNRawz:
boot.lok

Disregard the question. (I will leave it here as documentation.

The authors for unpackbootimg found out that a lokified img wont unpack right.

So you need to unlokify then unpack.

I did flash boot.img on the device:

127|root@android:/data/local/tmp # ./loki_tool patch boot aboot.img boot.img boo
t.lok
aboot.img boot.img boot.lok <
Loki tool v2.1
[+] Detected target International LG Optimus F5 build P87510e
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to boot.lok

Then I did setup CM for compiling. Preparing the device tree.

Did anyone have this?

android@builduntu:~/android/system$ ./build/tools/device/mkvendor.sh lge l1e_OPEN_BR ~/tmp/boot.lok
Arguments: lge l1e_OPEN_BR /home/android/tmp/boot.lok
Output will be in /home/android/android/system/device/lge/l1e_OPEN_BR

gzip: ../boot.lok-ramdisk.gz: not in gzip format
cpio: premature end of archive
Done!

Using boot.img dd(ed) from the device the output is "normal":

android@builduntu:~/android/system$ ./build/tools/device/mkvendor.sh lge l1e_OPEN_BR ~/tmp/boot.img
Arguments: lge l1e_OPEN_BR /home/android/tmp/boot.img
Output will be in /home/android/android/system/device/lge/l1e_OPEN_BR
6954 blocks
Done!

Looks like LOKI isn't writing the file right.
[LG Optimus G Pro] scandiun:
Loki exploit for LG G2 and such was patched on android kitkat 4.4 and won't work again. You should try instead

AutoRec - KitKat Recovery Installer

Anyway it's weird that the developer didn't mention it on first page or some. He just left things like this and let people guess whether it's working or not.

More information here:

[ROM][D802][D80220H]Original open eur 80220H kdz to recovery flashable zip
[LG Optimus G Pro] jpcdeux:
Ummm. Try FreeGee in play store. It installs Loki twrp or cwm.

I'm on an unofficial 2.8 twrp that's Bumped so no Loki needed and it supports external sd