yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] cali4nia831:
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.

---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------

Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...

EDIT:

Ended up just renaming the LGFOTA.apk file listed in the first reply above. So I should be good to go...
[G3 Android Development] autoprime:
Don't tap Enable.. Tap Disable... and that's it. OTA disabled... off.. all done.
[G3 Android Development] Mennooo:
Someone can provide me with img files? I dont have a PC, just using my phone :) PM if you can help me.
[G3 Android Development] veronesi.n:
Don't stick threads.. stick the man :D :D :D :D :D

He knows too much :p

Thanks for all your work

Edit: Can someone sticks his threads ?
[G3 Android Development] pRo_lama:
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks. :)
[G3 Android Development] GuestK00280:
First of all, thanks for the guide! It will help a lot of users in preserving bump and root :)

I don't think that leaving boot/etc .img out will help. LG engineers aren't stupid. The can, for example, do it like this: after "m" update all our phones will reflash aboot/etc partitions to patched versions on 1 jan 2015. The partition's images will be hidden in some big system file, while the waiting daemon will be hidden in, for example, healthd. We will never discover it until it's too late. GG WP.

That said, I really doubt that they will do it that way, but this is still a possibility. I guess i'll flash AOSP/CM/OMNI/smthing rom ASAP.
[G3 Android Development] teddy0209:
link a, b ,c , d in the O.P. mate.. He provided all you need.... =)
[G3 Android Development] L10nH34Rt:
The Python scripts and Windows GUI App, don't work for my D855 kdz files.

Don't have linux currently setup to test the last one (needs to be compiled).
[G3 Android Development] teddy0209:
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
[G3 Android Development] lossah:
The hidden menu setting ever resets? Not after reboot, factory reset etc?
[G3 Android Development] L10nH34Rt:
I get an unsupported KDZ format error, that's my problem.
[G3 Android Development] teddy0209:
Well, I just extracted mine.... d855, v10i..

Check the command...
[G3 Android Development] L10nH34Rt:
I tried to extract v10l and it failed.
[G3 Android Development] android-incredible:
i deleted system updates with tibu should i delete LGFOTA.apk? under system,etc security there are a file named otacerts.zip should i delete that one to.
[G3 Android Development] zennonace:
I guess this method doesn't work with lollipop....just tried it and it also boots back to my previous ROM.

Worked like a charm on Kitkat

LG G3 D855
[G3 Android Development] autoprime:
if system (rom) didnt change then it's due to some sort of bug in the flash2 system zip... but you should have picked up on that due to it only taking few seconds to flash... vs the normal 2-3 minutes it would take to flash a system.img.

flash system manually thru adb shell while in twrp to get around the issue. adb shell commands are the preferred method for myself..

adb shell
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system

and for those getting a boot error after flashing to L... you didn't read the text in red at the top of the OP or visit the link it directs to. you need to bump the stock boot.img if using Lollipop system/boot while still on KK bootloader.
[G3 Android Development] topet2k12001:
Rooted!!! D858HK

BOOM!!! D858HK - successfully rooted! :)

In honor of my phone variant's thread (D858HK) I will be posting the procedure over there, and I will return to this thread as well. I'm so excited!

TEASER: What was missing? Flash "aboot.img" (this is the Android Bootloader - not to be mistaken to sbl1.img which is the Secure Bootloader, I assume?) and "laf.img" (this is the Download Mode). But!!! Make sure that you have followed [MENTION=2684188]autoprime[/MENTION]'s procedure in the first post!

Also, make sure you have "bumped" TWRP (custom recovery)! This is very important so you would avoid "bricking" the device. Throughout my readings I have seen unfortunate circumstances where users have no more choice other than to send their device for LG Official Service. Some examples of the said threads: click me! and me too!

[MENTION=2684188]autoprime[/MENTION]: thank you for your procedure. Kudos to you, sir! I diligently read through your procedure as well as the red-font message at the top. Particularly your previous post in the said thread:

As I found out (and If it may help), I'd like to confirm that users will need to also flash aboot.img (after your entire procedure). But I can only speak for my variant (D858HK).

[MENTION=3717338]hoangnova[/MENTION]: his post/thread gave me an understanding of the LG G3's partition layout/list. Helped me ensure that I am flashing the correct ".img" to the correct location/partition.

[MENTION=1157052]thecubed[/MENTION]: his post helped me ensure that I am using the proper flashing command for the less known ".img" files (i.e. laf.img, etc.).

[MENTION=5340614]itsbighead[/MENTION]: his post made me understand why we are getting that white-text error message at the top-left corner of the LG G3 booting screen (a.k.a. "certification verify"). In a nutshell, it's because of a signature (?) or version mismatch if we do a manual flash of the "bumped" boot.img, system.img, and modem.img without flashing aboot.img. To my understanding, the boot/system/modem.img files are Lollipop and since the procedure of autoprime did not make mention of also flashing aboot.img, then the system is confused (or don't like each other) because aboot.img (if not flashed with Lollipop) is actually Kitkat. It wasn't really explained that way - I just used my common sense here as I am not a developer.

THERE IS A SIDE-EFFECT, HOWEVER: my "bumped" TWRP was lost. And even if I try to install "bumped" TWRP following the instructions from the "Bump" thread, I always get the "certification verify" error. I will try to figure out how to solve it, but would appreciate inputs from the experts.
[G3 Android Development] autoprime:
Hiya.. congrats on root! If you flashed the D858HK 20c aboot.img then you will lose BUMP.. which means you would not be able to use TWRP or any custom kernel.

For the other G3 variants the trick was to leave the stock KK aboot.img on the phone... then you would take the D858HK 20c boot.img and BUMP it... and then flash the 20c system.img, 20c modem.img and the BUMP'd 20c boot.img. The stock KK aboot should work with a BUMP'd D858HK boot.img... the BUMP "signature" should pass all checks and then boot.

If you keep stock KK aboot.img on but flash a stock un-BUMP'd boot.img then it will get the "certification verify" error due to the signatures changing from KK to L.

If you did try the BUMP'd D858HK 20c boot.img with the original KK aboot.img and got a booting error then it is possible that "open bump" is not patching the file properly. We do not support open bump so it is hard to say for sure.

If you want TWRP back you will HAVE to flash the KK aboot.img back... then the BUMP'd TWRP you had installed should work again. Then you will need to figure out how to properly patch the stock 20c boot.img with BUMP so that it works with the KK aboot.img. :good:
[G3 Android Development] mystery007:
Thank you for you very useful posts.

My english is not very well, but I think I understand mostly of yours.

Would you please be so kind, to write a "step by step" manual incl. all download sources for rooting the D858HK 20c?

If you need space, please let me know.
[G3 Android Development] supralex:
Nice work toPet. Waiting for your video tutorial since i am afraid to do it in case that I miss any steps and brick the phone. Thanks again for your work :)
[G3 Android Development] topet2k12001:
Hi [MENTION=2869940]mystery007[/MENTION]

Definitely I will, and that is really my plan. I am even planning to upload a video tutorial for it. I will post the procedure at the appropriate D858HK Discussions thread as well as the YouTube video link.

Please allow me to do it over the weekend because I have work in the office today.

Hi [MENTION=244832]supralex[/MENTION],

Thanks for recognizing the effort. :)
[G3 Android Development] tamghi:
Kudos topet2k12001 !!! Your brilliant finding allowed me to upgrade to Lollipop while keeping root :)

Many thanks again .
[G3 Android Development] scottspa74:
Fantastic work and documentation, [MENTION=5231281]topet2k12001[/MENTION]
[G3 Android Development] ch4dwick:
Have you tried successfulling installing CyanogenMod?
[G3 Android Development] topet2k12001:
Thank you [MENTION=961707]tamghi[/MENTION] and [MENTION=1681704]scottspa74[/MENTION]! I'm currently busy writing a proper documentation for the procedure; apologies for the delay.

Hi there [MENTION=4803927]ch4dwick[/MENTION],

I haven't tried yet since:

1. I am currently concentrating on the documentation (and preparing for a video tutorial) for Android Lollipop Upgrade of my LG G3 variant (D858HK)

2. I have done initial reading about Cyanogenmod (I do have that in my Nexus devices) but it seems like there is no full support for dual-SIM models (my LG G3 is a dual-SIM variant)
[G3 Android Development] mystery007:
[MENTION=5231281]topet2k12001[/MENTION]:

Also possible to install the TWRP with "Flashify"?

I've installed using flashify. Is it the same?

Best regards
[G3 Android Development] topet2k12001:
Flashing "Bump'd" TWRP with Flashify

Hi [MENTION=2869940]mystery007[/MENTION],

I have read through the "Bump" thread of [MENTION=1157052]thecubed[/MENTION] and if my memory serves me right, the answer is "yes". You can test it anyway; reboot to TWRP and if you see TWRP then it means it worked. But don't trust my memory. :) Please read through the "Bump" thread. I believe it was mentioned there.

I would prefer typing in the commands via Android Terminal Emulator though, as mentioned in the first post of the "Bump" thread.
[G3 Android Development] mystery007:
Yes, I see TWRP and I can backup and restore...

By exctracting the roms I only get .bin-files not .img.

I think I'm something doing wrong or don't understand.

Now, I'm still better waiting for your documentation - it will be the best.

Thank you in advance :good:
[G3 Android Development] topet2k12001:
Tutorial In Progress

Hi [MENTION=2869940]mystery007[/MENTION],

Ah, that's good to hear. :)

Please be patient as I write a proper document/tutorial. I have a scheduled late-night move with my wife (It's 8:40pm my time here), and I will do it when I get back home.
[G3 Android Development] guyd:
Yes. I've used Flashify to install TWRP and it works fine. I extracted the IMG file out of the zip first.
[G3 Android Development] wigginst:
I installed twrp using flashify as well with no problems.
[G3 Android Development] topet2k12001:
D858HK Rooting Guide Android Lollipop

HI Friends,

Here's the rooting guide (Android Lollipop) for the D858HK.

http://xdaforums.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845

Video tutorial is not yet done because I decided to write the steps in MS Word in as much detail as I can.

This is based from the procedure in [MENTION=2684188]autoprime[/MENTION]'s thread of manually flashing the firmware. I just added an extra step from his tutorial to "bump" the boot.img and therefore, keep custom recovery (TWRP) as well.

For those with other LG G3 variants who want to try this, please do share your results, LG G3 variant, and Android version (5.0.1 or 5.0.2).
[G3 Android Development] ragnarokx:
It appears your link is broken.
[G3 Android Development] topet2k12001:
Fixed!

Fixed; thank you for letting me know. :)
[G3 Android Development] DE52:
D852 Rogers working! :)

Just wanted to report that this method worked for my Rogers D852. For some reason, it seems that open_bump wasn't bumping the boot.img properly or something. Anyway, the sharpening script did the trick. So, to anyone getting the boot error, although their boot.img is supposedly "bump'd", you should try the sharpening script. I booted successfully as soon as I flashed that. I also have access to TWRP and root as described by this method. Thanks to autoprime for discovering this in the first place (how to update without losing root and such) and topet2k12001 for posting the details of his experiments :highfive:
[G3 Android Development] Deses:
Hi, so, uhm, I followed these steps to the letter, I downloadet the ota file using my IMEI, dusted off my Linux MInt VM installation to run those python scripts and built the system.img and renamed the modem from .bin to .img.

Then I put those files + the flash2 zips in my phone and flashed them with TWRP and cleared the dalvik cache and the normal cache, reboot and then is where thing go awry.

The LG logo appears and then another, smaller LG logo appears with the message "Security Error", then the phone just shuts down, no bootloop. I'm able to access the recovery and restore my backup, but no luck updating... and I need that to make my phone work with my carrier's 4G network.

I'm coming from a rooted 4.4.2 10L LG stock rom. As I'm writing this I remembered that I flashed some kernel to fix the oversharpening issue... could it be that? How can I know what kernel I flashed? What Kernel should I use then? Any recomendation?

Thank you very much!

Update: probably this one: http://xdaforums.com/lg-g3/orig-development/fix-stock-kernel-oversharpening-fix-t2951620

Update 2: I installed RIN Kernel and after wiping the data partition it boots... Is there any chance of NOT wiping? I'm lazy and I don't want to set all the apps again... ugh...
[G3 Android Development] DE52:
Use this: http://xdaforums.com/lg-g3/orig-development/fix-stock-kernel-oversharpening-fix-t2951620 Select your desired sharpening value, and after it'll bump your boot.img. You get the error because your boot.img wasn't bumped or not appropriately. You'll boot without having to wipe. Just make sure after the script is done, you Untick reboot, click continue and then reboot system through TWRP. All your data will be conserved and you will boot successfully. It'll take a while to boot though since all your apps have to optimized for lollipop
[G3 Android Development] Deses:
Hi, thanks for your answer. I'm still having issues...

I flashed the system image and the modem, then the RIN Kernel and finally the version 3.5 of this fix to bump my boot.img, rebooted and after a while the phone booted and started to optimize all the apps. The data was there and all was fine... or not.

The performance now is awful, really really awful, and eventually everything just freezes and I have to pop the battery out. I noticed that it takes a while to lock and unlock the phone and it's when it freezes...

What could be wrong? Thanks for the help!
[G3 Android Development] DE52:
Your problem may be RIN kernel. You have to make sure it is not the AOSP version of it. You can't install the AOSP version over a stock ROM. That's why you're getting all kinds of horrible performance and long boot times. Also, make sure that you're not installing the KK version either. If indeed it is the correct version for stock lollipop, then go ahead and flash it after the first boot and see (make a backup of lollipop without RIN installed since you have access to TWRP anyway). See if that helps. If not, I'd say use stock kernel for now.
[G3 Android Development] dornz:
Awesome. im on d855 international variant so code for hidden menu ends 855#..Disable OTA..epic stuff autoprime ☺
[G3 Android Development] feverdoingwork:
I tried the flash2 method. Flash2 zips are on the root of internal storage and boot/modem/system.img(all lowercase) are in the flash2 folder(lowercase folder name) located on the root of my internal storage(sdcard folder in twrp). When I flash the zips, they instantly complete. These files must not be flashing, there's no way a huge system.img would finish instantly. Is there any other way of flashing system/modem/boot.img?
[G3 Android Development] DE52:
when you extracted the system files from the kdz, did you make sure to merge all the system bin files? Also,are your files successfully converted to .img files? If you have windows 7, it should show up as CD icons when successfully converting
[G3 Android Development] glyxkecks:
Same problem here (extracted D85520P_00.kdz) . All system files merged sucessfully to system.img...

Any idea what went wrong? Files are internally located on /sdcard/flash2/ (all lowercase)...

-------

edit: more detailed description

If I try to install any of this files, I get the following output:

Installing '/sdcard/Flash2System.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found

Getting things ready..

Flashig system.img

Cleaning up..

Finished. OK
script succeeded: result was [Finished. OK]
Updating partition details...
...done

Everything finishes within 1-2s and nothing has been changed on the phone afterwards...

Files I tried to flash:

/sdcard/flash2/system.img
/sdcard/flash2/boot.img
/sdcard/flash2/modem.img

ZIP-Files I've used:

/sdcard/Flash2System.zip
/sdcard/Flash2Boot.zip
/sdcard/Flash2Modem.zip

Device: LG G3 (D855). All system files merged sucessfully to /sdcard/flash2/system.img (extracted D85520P_00.kdz). Other files have been renamed after extracting (boot.bin --> boot.img; modem.bin --> modem.img). Tool used to extract KDZ-File: KDZ and TOT Extractor: http://xdaforums.com/showpost.php?p=49192452&postcount=1

Any idea what went wrong?
[G3 Android Development] NBreunig3:
So when you say flashing the kernel/boot.img will patch root. Lets say I just have root with stock recovery. Could I just flash the boot.img for the current version I am on, that would block root. Then I could take OTA?
[G3 Android Development] leiko49:
unable to locate update.zip

You stated: If using ES File Explorer you may have to use the "show hidden files" option and grant the app root. You will see the update .zip file in cache if you did everything correctly. If no one has already uploaded the OTA zip.. copy the update to your sdcard and then upload for everyone else. Now delete the zip file from /cache/.

I found the zip file eventually by looking through 5 folders in /cache directory, found a large file called dlpkgfile.zip which I concluded was the update after looking it up on the web.

The notification keeps coming up though. You state:

Deleting the file in /cache/ will get rid of the OTA but will not get rid of the notification. To get rid of notification:

1. Pull the notification shade down on your phone

2. Long press on the OTA notification until you see the App Info option pop up.

3. Click App Info and uncheck the Show Notifications box.

However, the long press does bring up app info, but clicking on it does not do anything, though would like to get rid of it, says "system updates"

When I clicked on "install updates", after deleted the update file as above, it rebooted my phone, which I halted by removing battery. When I rebooted phone after then, the problem was solved.

Thanks
[G3 Android Development] cap1tal1sm:
My cache folder is empty, I'm running Jasminev8.0 and it's completely empty, and have check marked the show hidden files, still empty.

Tried taking a whack at it with App Quarantine but not sure if it worked. For those wondering, it says system_updates file. Search system update....
[G3 Android Development] Ronkan555:
Ok
[G3 Android Development] markfm:
Note, if there is a "void" (small area with an air pocket), give it several days and it might fill in; don't keep removing and reinstalling it. I had about a 4mm oval in the upper left, it cleared by itself after a couple days, is perfect now.
[G3 Android Development] teddy0209:
KDZFileTools.py -f xxxxxx.kdz -x

Just check the command...
[G3 Android Development] L10nH34Rt:
KDZFileTools.py -f D85510L_00.kdz -x
[!] Error: Unsupported KDZ file format.
[ ] Expected: 0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80 ,
but received 0x28 0x5 0x0 0x0 0x24 0x38 0x22 0x25 .
[G3 Android Development] autoprime:
yes, this is technically possible. No, this will never ever happen. LG won't be sneaking anything by us... it'll either come in OTA... or it won't.

Block OTA's properly.. and if one sneaks by don't accept the OTA install and immediately delete it using directions in OP and everything will be fine.

As an example... look at the AT&T or Verizon Galaxy S 4. Loki was patched the very next OTA... but those who never took OTA are still able to use Loki with no issues.

Not even Samsung is sneaky enough to force a "backdoored OTA" to update the bootstack.

No, LG and Samsung are not the same... but Samsung is even more serious when it comes to security and locking things down.

open the .py script up in a proper text editor(notepad++ on windows for example)..

find "\x28\x05\x00\x00\x34\x31\x25\x80" in the script... \x28\x05\x00\x00\x34\x31\x25\x80

replace it with "\x28\x05\x00\x00\x24\x38\x22\x25" then save script. rerun script. profit.
[G3 Android Development] L10nH34Rt:
That did it, thanks.!

Now extracting DZ...
[G3 Android Development] 4ndroid99:
Thanks for this. I will never repeat the same mistake I did with att s4 ever again... No more ota for me, it's all roms now :D
[G3 Android Development] meyerweb:
Just an FYI, I entere the ADB command shown in the first post (to disable OTAs) using a terminal emulator, instead of ADB. Just type SU and press enter first, then enter the command.
[G3 Android Development] stevoswifty:
My phone updated ota on uk vodafone from h to i and never lost root
[G3 Android Development] autoprime:
This thread is to expose all outcomes so yours is certainly welcomed. Yes this is known to happen for sure.. but it is only one of multiple unpredictable outcomes. And we do know for sure that everything up until 10L for D855 is safe to use. Many on XDA are already using 10L. And I'm sure M, N, O and P are right around the corner.

For some users, the OTA fails to install because it detects root.

For others the OTA is successful but root is gone.

For those who take an OTA with custom recovery installed.. they get stuck in TWRP until they flash a zip file to repair their FOTA and Misc partitions.

And although root sticks for some after OTA... the bootloader is updated. If you only want root on a stock LG rom you can gamble each time with root. But if you don't want to gamble.. manually updating is the best bet. And if you're someone who wants to keep Bump.. the ONLY option right now is to update manually. Of course, once future bootloader updates are confirmed to work with Bump by someone in Team Codefire.. you could always update the bootloader then. But in most cases this is never needed... possibly only once after official Lollipop from LG comes out.
[G3 Android Development] bweN diorD:
after you delete/freeze the updaters, just go to settings and try to check for updates. settings will crash if you got it right.
[G3 Android Development] android-incredible:
I don't have that option in system, setting, about phone . I thing I deleted.
[G3 Android Development] bweN diorD:
mine is another option in settings main menu under about phone, not in about phone. if your is gone, i would think you are good.

i only froze "com.lge.lgfota.permission" and "system updates" apps. my update option still shows in settings, but crashes when i click on it.