yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] hokiealumnus:
ROFL...I was reading that on my phone, hastily, and missed that. I feel shame. Much shame.

/me crawls back in my hole....
[Verizon LG G3] hokiealumnus:
Consider this confirmed! I'm KDZ'ed back to 12B and working to root/twrp shortly. Thanks so much for sharing [MENTION=884560]agh1701[/MENTION] !
[Verizon LG G3] pahlerc1:
Would you mind sharing your guide on what you did? I tried, followed instructions to the T, it finished and rebooted to a factory reset screen blue with a red 2.. But rebooted and it doesn't boot. Not sure what i missed, it should flash the 10B stock rom correct? I also used the dll provided

Am I supposed to just switch KDZ programs and try to pop into download mode and KDZ to 12B? Because the tot method took a different flash tool program.
[Verizon LG G3] agh1701:
You must keep the windows device manager open during the flash. after the phone reboots the phone will be re-detected only at a different com port. You must change the com port back to 41, the flash program will wait and continue after this is done. At the point you are now if you re-flash the tot after setting it to com 41 of coarse it may not require you to reset the com port because you are flashing the same version on top of the same version. You will know you are finished when you see a code 3 on the phone and you may need DownVol-Power to reboot.

This happens because the LAF partition is flashed before the reboot. Each version 10b, 12c etc. has a slightly different com port revision that it sends to windows for detection. Even though the driver is the same it is re-detected as a different device.

Note: the only reason I flashed 12b was because I could not get android debugger ie. ADB to work with 10b(bug maybe?) after flashing 12b I could.

OP: you may want to link to this as well. It is perhaps the toughest part of TOT flashing.
[Verizon LG G3] pahlerc1:
Thanks for your response. i figured it out. I selected Board DL isntead of Upgrade DL and it took me to an Atlas screen. Selected normal boot and all is well. LG setup wizard now. Thanks again
[Verizon LG G3] hokiealumnus:
Interesting...I didn't need to re-change com port. Mine is actually still on 41; I had to use that to re-root.
[Verizon LG G3] agh1701:
May be I am not flashing TOT's correctly but ever since my G2 getting stuck at Code 2 means you need to reset the com port to 41.
[Verizon LG G3] christheconfused:
Just wanted to give my two cents. I don't really mind the new update. My phone was rooted prior to updating to 5.1.1 and the mod that let me use all apps for dual window still works. Checking on the software about page in settings, it is indeed "modified".

My only annoyance is that my emoji on the entire phones system changed back to the ugly LG emoji nobody likes. Out of all the different OEMs, LG has the ugliest emoji. Is there any way to change it without rooting an unrootable stock ROM? I've read that it's possible on Samsung and HTC phones.
[Verizon LG G3] Kingofallskies:
TOT question

Do I use the LGUP8974.dll in place of the LGVS985_20140620_LGFLASHv160.dll or in addition to it?

I'm assuming in place of, correct?

Thank you.
[Verizon LG G3] hokiealumnus:
You can only select one DLL when initiating the TOT process, so in place of.
[Verizon LG G3] Kingofallskies:
Yeah, I realized this once I tried. But it worked! And easy.

Thank you.
[Verizon LG G3] agh1701:
In place of.
[Verizon LG G3] jdgesmlls:
I am not sure if this has been mentioned already but once you successfully TOT back to 10B, you can root with Stump 1.2.0

http://xdaforums.com/lg-g3/orig-development/root-stump-root-lg-g3-sprint-verizon-t2850906

I did this before 35B was available to get a clean start on my G3. Once I was back on 10B, I rooted with Stump, installed TWRP 2.8.7.0 and installed AICP 10.0. I was also able to restore a backup from SkyDragon 5.0. I figured I would just suggest this as there has been talk of needing to KDZ to 12B once you were at 10B and I wanted to know if I was missing something?
[Verizon LG G3] hokiealumnus:
Nope; as long as you're successful rooting & installing TWRP, there's definitely no need to go up to 12B. :)
[Verizon LG G3] bama17:
Worked like a charm first time with no issues. SD 9.0 is running smooth and sweet now!
[Verizon LG G3] hokiealumnus:
Welcome back to the land of the living!

Added a note in the OP to straight-up NOT take the OTA and linked to SkyDragon & Jasmine. Hopefully that'll keep anyone from needing to TOT back again. It won't of course, but maybe it'll help that one person that happens upon the thread before taking the OTA. :D
[Verizon LG G3] roirraW "edor" ehT:
Not picking on you so no offense, but SkyDragon is v6. JasmineROM is v9. :)

There are (amazingly) some people who frequent XDA who don't root. I'm always surprised.

Thanks for maintaining the latest info. :)
[Verizon LG G3] bama17:
Wow..none taken..wasn't that stupid, LoL. Yeah I guess I've been going back n forth so much I wasn't even paying attention.
[Verizon LG G3] roirraW "edor" ehT:
LOL, that's cool. I do things like that. I just did myself here at work in an email with two names that are similar.
[Verizon LG G3] moswald1978:
I tried switching the dll and I got an error in flash tool saying cross dll. Can anyone help please
[Verizon LG G3] hokiealumnus:
Sorry, no idea here; I selected the DLL and the TOT file and it flashed right away. Did you correctly set the phone to COM port 41?
[Verizon LG G3] moswald1978:
Yes
[Verizon LG G3] bweN diorD:
i have been looking into this for a bit, and most of what i have seen points to the dll not matching the phone.

are you sure you have a VS985? if you are not sure, pull out the battery and look at the sticker under the battery.
[Verizon LG G3] moswald1978:
I think I got it figured out. I need to download the 35b kdz and use the dll from that.
[Verizon LG G3] bweN diorD:
thats for sure lol

the dll was posted a while back, and i would think its in the op, but i havent looked really.
[Verizon LG G3] moswald1978:
Thank you for your help
[Verizon LG G3] hokiealumnus:
Not physically, but it links to the post and says to download the file. :)
[Verizon LG G3] KiloTheGiant:
I'm not sure if this is a semantics issue, but when you say "switching" the .dll, what do you mean? There should only be one .dll involved in restoring (the 35B .dll agh1701 provided earlier in the thread) and it should work in only one flash (potentially two, if your first flash yields a "2" instead of a "3").

So, unless I just misunderstand your question, there's no "switching" of .dll's involved. That actually sounds like risky business and you should make sure you're following the .TOT flashing instructions to a 't'. Loading multiple .dll's is something that sounds like it could lead to a hard brick, although I don't even know how you'd load multiple .dll's as Flashtool only allows for one.

---------- Post added at 10:14 PM ---------- Previous post was at 10:08 PM ----------

Sorry for the double post, but wanted to thank both [MENTION=884560]agh1701[/MENTION] and [MENTION=4936949]hokiealumnus[/MENTION] for their help with this thread. I've been without root for acouple months after resetting just so I could take a 5.0 OTA (definitely a mistake) and so-called "current" root methods failed, but I didn't feel as though reverting to stock was worth it until I took the new OTA and realized I'd be locked in otherwise. Thanks for the charitable work and helpful information.

In addition, as I said in my previous post, if any people new to Flashtool are having issues with a "2" instead of a "3" appearing on the final check screen, you either have to wait (it should update to a 3 in a few seconds) or simply redo the flash (Flashtool is much quicker overwriting than it is copying, so it shouldn't take as long). The second time has ALWAYS yielded a "3" for me. I think the "2" most commonly appears if coming from a non-stock ROM or if you're one of the VS985 users that ever received a "secure boot error" whenever booting up your phone that had a custom recovery installed. I'm not sure exactly why, but it doesn't appear to be too much of an issue.
[Verizon LG G3] roirraW "edor" ehT:
There's actually two .DLLs involved, both of which replace two other DLLs. The megalock.dll, which you replace in the program installation folder with the provided one in the linked "Restore to Stock TOT method" post after you install the flash program on your Windows PC. Then, following the directions for flashing via TOT method, the .DLL you point the flashing program to isn't the one the directions give, but the new one which came with the 35B KDZ. That second DLL is the only new thing in this method. In other words, if you use the DLL the instructions tell you to use, it won't flash, but if you use the new one, the 10B_03 TOT file will flash.

Hope that makes things clearer. I'm sure you already knew all this, but I'm positive the second instance of using the new .DLL in place of the one specified in the instructions is what anyone is referring to when talking about replacing .DLLs.

Also I want to note that when I did this (albeit was the first time I've TOT'd so no idea if this is usual, for a second or two the phone said "2", then switched to "3". I was coming from completely 100% stock non-rooted 35B, but certainly had secure boot errors at various times in the past, and of course have run non-stock ROMs at various times too, all the time if you count rooted debloated stock, and have previously had a custom recovery. Just additional data for anyone to absorb.
[Verizon LG G3] agh1701:
Information about 2 and 3 please see this post.

http://xdaforums.com/showpost.php?p=63272955&postcount=94
[Verizon LG G3] KiloTheGiant:
This is mildly off-topic, but I think your debugging didn't work on 10B because us Verizon users had ethernet mode which is required to use adb on that firmware. 12B did away with the ethernet mode, if I remember correctly. Just in case you ever restore again, you don't have to wait for OTA. ;)
[Verizon LG G3] timgman:
I ran into the ethernet mode when I did the tot... It took me a bit to remember..

100% success with tot and now on Jasmine 9.1 35b.

Nice to know that these phones are still flexible / rommable..
[Verizon LG G3] newobrain:
I'm having the same issue as another poster I saw a few pages back. I've tried both dlls (LGUP8974 and LGVS985_20140620_LGFLASHv160) neither of them work. The latter gives me the model id error, and the former gives me "crossDL (blank) to (VS985). SW version (blank). I noticed the model number for the lgup dll is 8974, which is the model number for the qualcomm snapdragon processor, which the lg g3 has. So i'm assuming it's the correct dll, I guess? I'm also 110% sure that I have a vs985. running the current ota update. Device was previously rooted, a few OTAs ago. When i'm on the firmware update screen it says 'modified' maybe that has something to do with it? Any feedback is appreciated. I just want root back
[Verizon LG G3] hokiealumnus:
First you need to put the DLL that comes with the TOT program into the program directory, if you haven't already. Then you simply select the TOT file and the DLL from post #84 (which you seem to have - LGUP8974) and it should move forward. Unfortunately from your post it looks like all of those things are in place.

My instinct says you're having driver issues. Make sure you're using the Verizon LG G3 drivers and not the generic G3 driver from LG. There is a difference, and it will cause issues.

As far as your software saying modified, that's because you were rooted or have attempted root and I'm truly surprised you were able to take any OTAs to get up to 35B with that flag tripped.
[Verizon LG G3] newobrain:
I double checked, and all that is in place. I even downloaded updated drivers directly from lg, still nothing. I've also tried using different usb ports. I'm running windows 10 if that makes any difference.

As for updating with 'sw modified' status. I wasn't even aware being rooted had any effect on taking OTAs, lol. I was rooted, with the stock rom, and took an OTA to unroot. I've taken one or two more OTAs, not including 35b, with no problems. Do you think that may have had something to do with it?
[Verizon LG G3] hokiealumnus:
Are you using the drivers from LG's support page for the VS985 specifically? If so, I'm kinda stumped, unless Windows 10 has something to do with it. I'm still on Win 7 (giving Win 10 a few more months to work out the kinks), so I can't help with Win 10 issues.

Having a modified software status shouldn't have anything to do with being able to TOT back, as mine was modified from attempting to root 35B (and failing). TOT worked just fine.
[Verizon LG G3] newobrain:
If anyone else has used this process and you're running windows 10 can you confirm whether or not you were able to TOT?

Since i'm a new user it wouldn't let me hyperlink, but, I just confirmed I'm using the same link you posted for the drivers.
[Verizon LG G3] roirraW "edor" ehT:
Have you checked in Device Manager with the phone plugged in while it's in Download mode to see if you're getting the phone's entry under the "Modem" section? If you're not, you'll have to solve that first. The first time you plug the phone (in Download mode) into the PC, it can take up to 10 minutes to actually load the driver that you had installed, depending on the PC. After you install the LG-Verizon drivers, try rebooting the PC while the phone's disconnected. Then try a different USB 2.0 port than you've tried before, if you have any that fit that criteria. :) ...And put the phone in Download mode. Are you using the original charging cable that came with the phone?

If I get bored enough, I'll check TOT under Windows 10 to see if it "can" work fine, but who knows when/if that'll be.

Regarding OTAs and "Modified" status: pre-Lollipop, OTAs often worked whether rooted or not as long as you have the stock recovery - the OTAs merely looked for the original files that were going to change, to make sure they hadn't been already changed any other way. With Lollipop, it checks to see if the system partition has been modified in any way. I don't know what the "Modified" status in the About menu all takes into account, but if you have been on the Modified status through the past three OTAs (12B->23C, 23C->24B, 24B->35B), then I would guess there's some other partition that's been modified, but one that doesn't keep OTAs from being successfully taken. Weird, though, and there's some other people who have reported the same or similar mystery.
[Verizon LG G3] newobrain:
Here's a picture of what shows up in device manager when I plug in my phone. puu sh/kTDBv/3237fcb32e.png

I clicked 'query modem' to see what would happen and I got this error message. Does this happen to you? Or is this abnormal? I'll try restarting my pc, and see if that has any changes. Lastly, I do not think this is the cable that came with the phone. That cable is probably loooong gone :crying:

I can't even create an image because of this no links thing.

---------- Post added at 06:22 PM ---------- Previous post was at 06:14 PM ----------

I FEEL LIKE SUCH A FOOL.

Restarting my pc seems to have done the trick. How could I have forgotten the first rule of basic trouble shooting. Currently at 40%. Thank you guys so much.
[Verizon LG G3] roirraW "edor" ehT:
It happens to the best of us. Glad you appear to have it solved! It's not always necessary but it's definitely made a difference sometimes for myself and some others I've advised. You're welcome! I haven't TOT'd or KDZ'd without the original cable yet. Glad it seems to function on some third party ones. :)
[Verizon LG G3] newobrain:
At least now we know what the problem is for any future people who have my issues. The TOT just finished, and I successfully booted up. Thank you warrior, and thank you OP.
[Verizon LG G3] hokiealumnus:
Yay! Glad you got it figured out. :good:
[Verizon LG G3] roirraW "edor" ehT:
Confirmed that [MENTION=2941286]xdabbeb[/MENTION] 's 35B firmware at http://xdaforums.com/verizon-lg-g3/development/xdabbeb-s-vs980-2-0-0-t3231279 still allows getting into TWRP (I reboot Recovery from within TWRP, rebooted from running Android using Quick Reboot, and used the hardware keys), and it's definitely using the 35B modem and still has a signal as well. Mobile Data's working fine - at work Verizon signal is on the low side, so just barely have 3G here which was the same on the 24B firmware at least recently. Haven't explicitly tested Advanced / HD Calling yet and won't get a chance until after work, if I remember.
[Verizon LG G3] Aleroniponi:
OMG

Confirmed working 5.1.1 35B

Seriously, thank you so much!
[Verizon LG G3] dcooterfrog:
i will further confirm that using the bootstack allows encryption to work. I have advanced calling enabled and when dialing my office phone i can hear the outgoing message and leave a message.

clearly this is not an hd call because my office phone is some other IP phone but it didn't break anything enabling hd calling. i had already enable dhd on my line
[Verizon LG G3] RackBee:
Report TOT method not work on 5.1

Sorry my english poor

Plzzz Help! My G3 was up to 5.1 and now i cant use TOT to downgrade 4.4(10B).

When i into Download Mode the driver not receive (Portable Devices(!VS985 4G)) diver to appear exclamation mark, but when boot into OS driver receive all.

who can help me fix it? I was try all driver LG.
[Verizon LG G3] roirraW "edor" ehT:
You have to use the new .DLL that's near the bottom of the first post of this thread in order to downgrade from 35B 5.1.1 to 10B_03 TOT.
[Verizon LG G3] RackBee:
Thanks i'll try.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! Worked great.
[Verizon LG G3] RackBee:
Ok it's worked.

First i run new DLL, but it only run to 89%, then i use old DLL and it worked 100%.

Thanks very much.
[Verizon LG G3] roirraW "edor" ehT:
Great! You're welcome! I'm confused, but whatever works! :)
[Verizon LG G3] RackBee:
Plzz help i flash rom Cloudy 2.5 and now my phone lost imei ( Imei 000000000000)?

Do you know how to fixx it?
[Verizon LG G3] bweN diorD:
what i know is, this thread isnt the place you should be asking!!

look in the q&a forum, there are threads there on how to fix it, and where you should have asked this question.
[Verizon LG G3] MrC1122:
Yes, as of 11/10/15 KingRoot does work for stock VS985 35B. However, DO NOT use LG G3 AutoRec-Lollipop on Google Play to flash TWRP. It WILL brick your phone when you try to boot into recovery! Hopefully I can recover using KDZ or .tot. Props to the KingRoot team!
[Verizon LG G3] BillFZhu:
Did you try the AutoRec-Lollipop for Verizon 24B on xda?

https://www.androidfilehost.com/?fid=24052804347813325

From http://xdaforums.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396
[Verizon LG G3] roirraW "edor" ehT:
It had to be updated for 24B so it probably has to be updated again for 35B.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] MrC1122:
No, just the update for 24B on Google Play...huge mistake!
[Verizon LG G3] eagle8762:
About Factory Reset

Hello all,

probably not the right place to ask, and I am sure it has been and answered several times over. I, however, cannot find an answer to this question.

If I have taken an OTA and then just factory wipe and reset does it start at the latest OTA taken or go back to the original 10b that was on the phone when I unboxed it?

Thanks and if it does not then I'll go the #84 route and TOT the phone.

Again, thanks for the answer or a link to it.
[Verizon LG G3] roirraW "edor" ehT:
You have to take the TOT to downgrade, along with the new .DLL that came with the 35B KDZ, linked to at the bottom of the first post.

When you take an OTA it permanently upgrades all the partitions on your phone. Factory reset wipes cache, Dalvik and user data including internal storage.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] thehuypt:
I saw an error :( Can u help me?
[Verizon LG G3] jdgesmlls:
If you unplug/plug back in the USB cable, it should start.
[Verizon LG G3] Liegepk:
So I'm about to use KingRoot from my stock 35B.

What should I be using to flash TWRP?

Just the old manual way?
[Verizon LG G3] owlmatt:
Think I bricked my phone using this. Can't get anything on startup. Anyone else have issue?
[Verizon LG G3] Liegepk:
Kingroot does not work.... Just tried it and changed it to that stupid modified version.......

DO NOT TRY TO ROOT VIA KINGROOT!

now I gotta go back again.... That's really annoying..

UPDATE: So I Uninstalled kingroot after falling and after being suggested to retry, I installed or again, and now it says that I'm rooted before even getting to root. I checked with root checker and it says I'm rooted! Yes!
[Verizon LG G3] thehuypt:
It's not start.

But I tried with old DLL, this is worked :D
[Verizon LG G3] punkore:
Did anyone find a working root method for the 35b ?
[Verizon LG G3] fast69mopar:
I rooted my VS985 with Kingroot the day before yesterday and it worked flawlessly.
[Verizon LG G3] punkore:
it works ! but i can't replace it with SuperSU :crying:
[Verizon LG G3] Liegepk:
I'm really curious how you guys are getting it to work..

It did not work for me at all. Kingroot says it failed to root. And now my version is "modified"...

---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------

Btw, they have instruction on kingroot page telling you how. But they don't recommend it
[Verizon LG G3] punkore:
Did you retry ?

it didn't work, the phone reboots in the middle of the operation
[Verizon LG G3] Liegepk:
Okay I reinstalled it and somehow it works!
[Verizon LG G3] roirraW "edor" ehT:
If you can find a way to install TWRP (I have no idea what that takes to do under 35B, until the autorec app is updated to 35B) then you can flash a stock 35B based ROM that uses SuperSU.

Personally I find it easier to downgrade to 10B, root worth Stump, use TWRP Manager from the Play Store to flash TWRP, then flash the stock based ROM.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] punkore:
I Told You !!!! :D

I don't know why. but i want to keep stock recovery
[Verizon LG G3] roirraW "edor" ehT:
I don't know why either. ? You can back it up and restore it anytime.

[VK810.4G] [altev] [ViKtory810ROM] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

[VK810.4G] [altev] official LG G Pad 8.3 Lollipop 36B_00 5.0.2

DEBLOAT SCRIPTS

and copies of all the files they remove

[VK810.4G] [altev] OTAs, .IMGs and KDZs, oh my
[Verizon LG G3] punkore:
[MENTION=6994519]Liegepk[/MENTION] [MENTION=2560614]roirraW "edor" ehT[/MENTION] :

Finally...:victory:

I replaced kingroot with SuperSU using "Super SU-ME Pro"
[Verizon LG G3] Liegepk:
Thanks for letting me know!

Although right now I like Kingroot. Freezing apps are built in and free. Noticed a good speed boost after purify as well
[Verizon LG G3] roirraW "edor" ehT:
Great! Thanks for reporting the success and how. I forgot - I had heard of Super SU-Me but never had to use it myself.
[Verizon LG G3] Liegepk:
So I swapped out to SuperSU because kingroot seemed to have several issues with some of the apps I had. But now my smart lock isn't working. When I'm at home, it doesn't disable lockscreen pin as it used to.

I'm using the built in smart screen function.

Anybody having the same issue?

Update: is little finicky right now. It works kinda. I'll observe for few more days.