yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] ncjones28:
So I ended up trying tot on my roommates desktop and I was able to get it to work. I think there was something that went wrong with drivers when I was initially attempted everything and there were redundant drivers which were messing things up. I also got a dll and tot file from a different thread i found om xda which really did the trick. Every time I used the files from your link i got the 'failed previous load' error. Anyway I toted back to 10b and in now running CM13 again. Thanks for all of the help!
[Verizon LG G3] roirraW "edor" ehT:
Glad you got it working!
[Verizon LG G3] lexluthor:
If I want to get to xdabbeb's 47a here

http://xdaforums.com/showthread.php?t=3304365

with TWRP/rooted/35B bootstack from a refurbished LG G3 (VS985) that I purchased what's the process? I'm not sure what version will be installed on the LG G3 when I get it.
[Verizon LG G3] roirraW "edor" ehT:
Answered in the other thread. :)
[Verizon LG G3] roirraW "edor" ehT:
For anyone who's interested, [MENTION=2684188]autoprime[/MENTION] provides a download for the 47A KDZ at this post http://xdaforums.com/showpost.php?p=66096623&postcount=965. I'll reupload and share at my Android File Host section linked to at the bottom of the first post just as soon as I can.
[Verizon LG G3] DeanGibson:
Oops ...

Unfortunately you copied the abbreviated URL (fixed in my copy above). :laugh:
[Verizon LG G3] roirraW "edor" ehT:
Ah, thank you! Whoops! I'll have to check the other thread I posted that in. :)

Edit: nope, apparently I only did that here.
[Verizon LG G3] sorrowfulveil44:
thank you!!!

I signed up just to tell you thank you sooo much! I have spent months trying to fix this phone. I even went ahead and bought a new one :( I swear I tried this method before, with no luck, but decided to try it again and it worked. Thank you!
[Verizon LG G3] cerealkiller974:
Fails to connect to server

I tried this method both with 10B and 47A files. Both times it says it failed to connect to the server. If I wait a bit and retry the installation, it gets to 10% stays there for a while, and fails again saying "Upgrade stopped due to an error". My internet is great and not the issue. Is there any way to fix this?
[Verizon LG G3] roirraW "edor" ehT:
http://xdaforums.com/showpost.php?p=56484818&postcount=2

Near the bottom where it says:
[Verizon LG G3] ugoPS:
Im on 47a xdabeb and i have a problem to acces to TWRP recovery, i can try flash this 47a kdz directly or i need frist go yo 10b?
[Verizon LG G3] roirraW "edor" ehT:
You can go direct if you really want to, but if you're going to want to be rooted and have TWRP in the end, it'll be harder to do it once you flash the 47A KDZ. If you're going to want to be rooted and have TWRP, you want to flash the 10B KDZ instead, or the 10B TOT if you want to make sure everything's 100% correct on your phone.
[Verizon LG G3] ugoPS:
and you could tell me please the steps I should I take to get back to the root and 47a with TWRP
[Verizon LG G3] roirraW "edor" ehT:
Follow the instructions in the first post to flash the 10B KDZ. Root with the Stump app. Use TWRP Manager from the Play Store to flash TWRP. Boot to TWRP, wipe Cache, Dalvik/ART and Data, flash the 35B Bootstack and the 47A stock firmware.
[Verizon LG G3] ugoPS:
tnks a lot sir, I can try with Windows 10, o is only with win 7?
[Verizon LG G3] roirraW "edor" ehT:
You're welcome. I've used XP, 7, 8, 8.1 and 10.
[Verizon LG G3] ugoPS:
I am already in the 47th, but I have a problem, I can not see the internal card, external if I can see it, but no phone card
[Verizon LG G3] roirraW "edor" ehT:
Try wiping or reformatting it from TWRP?
[Verizon LG G3] ugoPS:
But on recovery i can ser it, and if I wipe internal storage, the phone run normally? o I need flash the new the rom?
[Verizon LG G3] roirraW "edor" ehT:
Just a suggestion - I don't know if it'll make a difference or not.

Yep. If you have anything on internal storage you want to save (doubtful), you can use TWRP's file manager to move the files to the external MicroSD card.

No.
[Verizon LG G3] ugoPS:
I fixed the internal storage problem with format , but I lose the root :,)
[Verizon LG G3] roirraW "edor" ehT:
Just dirty flash the ROM.
[Verizon LG G3] ugoPS:
I mean I have to do it again, from 10b?
[Verizon LG G3] roirraW "edor" ehT:
You still have TWRP, right? Flash the rooted 47A firmware. Formatting the internal (or external) storage shouldn't lose your root, but it definitely shouldn't get rid of TWRP either.
[Verizon LG G3] ugoPS:
I could not enter to recovery, I made all from 10B kdz again, and all work now, tnks a lot friend...
[Verizon LG G3] Naruyasha:
I need help, my phone starts up on download mode but it ALWAYS says "firmware update Do not unplug the USB connection until the process is complete." but the process never completes... it doesn't even start it stays in 0% forever, what am I doing wrong? Thanks in advance!
[Verizon LG G3] roirraW "edor" ehT:
Hi! We'll need more details please.

Did you install the latest drivers in Windows? Are you using the original USB cable that came with the phone? Are you using a USB 2.0 port and not through a USB hub and not a USB 3.0 port? Is your phone listed in Windows' Device Manager in the Modem section?

After installing the Windows drivers, I recommend rebooting the PC (with the phone disconnected). Even if you already installed the drivers previously, try rebooting the PC with the phone disconnected.

The first time you plug the phone into a different USB 2.0 port on the PC, it can take up to 5-10 minutes for the driver to finish loading. It's the nature of USB that every time you connect the same device to a different USB port, it has to re-load the driver. This only happens once for each USB port. Restoring to other stock ROMs/flashing other ROMs may cause the PC to think it's a new device. After you've given it 5-10 minutes to load the driver, does Device Manager list your phone in the Modem section now?

Other key information we need is what stock ROM are you on now, or what official VS985 stock ROM was the most recent one you were on? Are you rooted and have flashed a bootstack? What KDZ are you trying to flash? If you haven't flashed a bootstack and you're on 35B or higher, you can only flash the 35B or higher KDZ. If you want to downgrade to lower than 35B, such as to 10B in order to root and put TWRP on in the easiest way, you have to use the TOT method to flash the 10B TOT, using the .DLL that's extracted from the 35B KDZ, then you can root using the Stump app and use TWRP Manager from the Play Store to put TWRP on.

Rooting gets more difficult after 10B, and putting TWRP on gets more difficult after 12B.
[Verizon LG G3] Naruyasha:
Ok I managed to get it to work (windows 7 compatibility mode) :rolleyes: but now the phone reboots on its own and the recovery symbol (android with the blue icon inside and the blue bar down) show but it immediately reboots and now I'm stuck in an eternal reboot cycle :( I flashed v12B I was rooted with XDABBEB ROM/VS98547A Firmware. I can still enter the fastboot mode but no luck in flashing with success.
[Verizon LG G3] roirraW "edor" ehT:
Try a Factory Reset? Had you flashed the KDZ in "CSE" mode which wipes all data including internal storage or "Normal" mode that doesn't wipe? "CSE" is necessary when you're downgrading from a more recent stock ROM, and some other times too. A Factory Reset in the stock recovery after the fact will effectively do the same thing, wipe everything including internal storage. It's also semi-common on all or a lot of different phones by different manufacturers that even after restoring to stock, sometimes an extra "Factory Reset" or at least "Wipe Cache" is necessary if the phone bootloops.

If a Factory Reset doesn't solve it, maybe you should try flashing the 10B TOT instead of KDZ. Flashing the TOT will will wipe your data and internal storage too. As [MENTION=2941286]xdabbeb[/MENTION] taught me and I've personally witnessed when I checked into it, TOTs flash more partitions than KDZs do. Flashing the 10B TOT can fix things that flashing any KDZ or ROM won't. I had a weird problem several months ago that no matter what ROM or KDZ (including 10B) I flashed, the problem persisted. It wasn't until I flashed the 10B TOT that the problem went and stayed away.
[Verizon LG G3] Naruyasha:
I did the CSE flashing, I tried with 10B and also with 12B both on CSE and got the same results. Everything was flashing ok until it reached like the 80% when it reboots and then the android symbol appears and the reboots keep happening. I will try the factory reset and see if that works, if not I will do the TOT flashing and see. Thanks for answering!! You are very kind! [emoji106]

Update:

ok the factory reset/cache didn't worked, again the recovery android icon appears and the blue bar starts moving but it reboots with no end and also just finished with the TOT flashing but it also failed... the last thing it says is "waiting for reset 25 sec" and that's when the phone starts acting crazy... I have no idea what is going on :(
[Verizon LG G3] roirraW "edor" ehT:
Ah, I see. I wasn't clear if you actually got it to flash. If it's not finishing flashing it's doubtful a Factory Reset will help. Hopefully you have much better luck with the TOT method.

Since you haven't mentioned I want to make sure you know - if LG Flash Tool 2014 puts any error dialogs up (server disconnected, or almost any other error dialog), don't click any buttons in the dialog, just drag it out of your way if you must. 95% of the time if you wait 5-10 minutes you'll find the phone has finished flashing despite LG Flash Tool 2014 showing error dialogs.

At least with the TOT method it doesn't have that issue. Can have different issues, but not that kind.

You're welcome, mate! :D Thanks!
[Verizon LG G3] Naruyasha:
Well I tried TOT flashing but I got the same results with KDZ, it flashes everything up to 80% and reboots after that it's reboot after reboot, maybe there's something wrong with the file? What can you recommend me? [emoji29]
[Verizon LG G3] roirraW "edor" ehT:
Did you try the Factory Reset from stock recovery anyway, just in case?

Personally I doubt if all the files you downloaded were bad - I believe the software checks them before flashing. However, it's easy to find out if what you downloaded is good or not by checking the MD5 hash and comparing it with what's given for the file.

For any KDZ and TOT files I upload in 7-Zip archives, I provide the file's intended MD5 hash in the filename of the KDZ or TOT extracted from the archive.

One of the reasons I put them in 7-Zip archives is when you extract the KDZ or TOT out of one, you can be very sure it's not corrupt as it either won't extract it or the software you're using to extract it will tell you it's corrupt.

If you're downloading anyone else's files, and if the KDZ or TOT aren't in an archive and if the file is on Android File Host, then you would use the MD5 hash Android File Host lists for the file on the download page.

The MD5 hash would be the same for the same files no matter who's file you downloaded.

My only other recommendation is to use a different PC and/or different high quality USB cable. I can't make any recommendations for a cable brand since I always use the original cable that came with the phone without trouble. I think trying on a different PC would have the higher chance of fixing the trouble.

It stopping flashing at 80% no matter which method tells us that the method doesn't matter, so we're left with any other item in common - the PC, cable or the phone itself is likely the problem. What about the USB port you're using on the PC? I recommend a USB 2.0 (not 3.0 or 3.1) port, and only one that's connected directly to the PC's motherboard - not through a USB hub.

If I'm repeating myself from before, ignore it as I'm mobile. Did you try rebooting the PC? Try a different USB port - maybe one located on the back of the PC instead?

Does either the KDZ or TOT flashing software provide any error information?
[Verizon LG G3] stewbuntu:
Does anyone have a working 23C KDZ please? The link here has something wrong with the file. Once downloaded the file won't open/uncompress in winrar or zip, all the other KDZ's work for me. I need 23C so I can use one-click root, rooting 24B is leading to "boot error 1003" after TWRP and CM12
[Verizon LG G3] roirraW "edor" ehT:
By the way, in the future you might want to consider 10B (either KDZ or TOT) instead of anything higher. It's easiest to root and put TWRP on 10B. Root with the Stump app and then put TWRP on with TWRP Manager from the Play Store.

Rooting becomes more complicated after 10B, and putting TWRP on becomes more complicated after 12B.

Then wipe and flash the ROM and appropriate Bootstack for whatever ROM you want.

Also, please don't take this the wrong way but you only have to post about a problem in one thread - not three or more.
[Verizon LG G3] Galaxynote1234:
Is there a video of someone going through this entire process? I want to root my G3 but all this reading has me dizzy now.

And on another note would rooting via kingroot, uninstalling it and then installing twrp and supersu be considered a permanent root?
[Verizon LG G3] roirraW "edor" ehT:
[MENTION=5066255]LASERWOLF452[/MENTION] has a thread in this section with a video.

TWRP requires the 12B or lower aboot (bootloader), not just root. Also, the 12B bootloader combined with the 46A/47A sbl1 partition bricks your phone into QHSUSB_BULK 9008 mode so the sbl1 needs downgrading to 35B. Then without the 46A/47A modem doesn't work with the 35B sbl1 so that needs downgraded too.

That's why it's easiest if you can downgrade to 10B. A small handful haven't been able to using any method but most can.
[Verizon LG G3] Galaxynote1234:
Thanks I'll check out the video. I'm thinking about just going the kingroot route since after reading some more this seems like a tricky method for me if I miss a step. Just not sure if I can re-root after rebooting since I want to install xposed.
[Verizon LG G3] DarkFamiliarity:
Hello, I wish to root my VS985 on 47A. Does this method work to downgrade to 10b? Every other thread says users had to tot back to 10b or use kingroot. Half of these threads have users complaining of bricks. What is the best way to go about this? Also, if I get a brick during a kdz flash while downgrading, is there still hope for the phone? (issues like the user further up this thread who stated that their phone was stuck in a bootloop at 80%)

Sorry for the noob-ish questions and thank you all in advance.
[Verizon LG G3] roirraW "edor" ehT:
Hi!

You have to use the 10B TOT along with the newer .DLL that's extracted from the 35B KDZ. You can get the TOT and .DLL from my Android File Host link at the bottom of the first post of this thread. There's a thread in the non-Verizon G3 General section that gives instructions, links to the other files needed, and screenshots. It's the second post of the LGUp thread. Or [MENTION=5066255]LASERWOLF452[/MENTION] has a thread in this section with a video.

From 100% stock 35B and higher you can only flash the 35B and higher KDZ.
[Verizon LG G3] roirraW "edor" ehT:
Just be aware that Kingroot is untrustworthy at best: it injects all sorts of things into your system partition that aren't necessary for root and it's suspected that it might "phone home" with potentially who knows what personnel information.
[Verizon LG G3] DarkFamiliarity:
Thank you very much for the quick reply. Are files 7a and 7b on your AFH the files I need? And will the General LG G3 tot guide work for the VZW G3 as well or do I need to switch up any steps? Just confirming (I know I'm really paranoid)

If the tot flashing stops midway or crashes, or something goes wrong in the middle, will it be a permanent brick or are there ways to recover?

Also, after I root and install TWRP, to flash fulmics, what modem do I need to flash?

Will this guide http://xdaforums.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878 or http://xdaforums.com/showpost.php?p=64624324&postcount=2 work? Which one is more updated and safer?

Thanks again!
[Verizon LG G3] roirraW "edor" ehT:
You're welcome!

I believe so. If they say 10B TOT and .DLL extracted from the 35B KDZ, then yes. Extract the .7Z archives with the free 7-Zip from www.7-zip.org.

I've never had flashing a TOT stop or crash but there's almost always a way to recover.

As a general rule, after you flash any ROM on this phone, flash the appropriate Bootstack from [MENTION=2941286]xdabbeb[/MENTION] 's VS985 v2.0 ROM thread in the Development (non-original) section.

For KitKat 4.4.2 ROMs, use the 12B Bootstack, for Lollipop 5.0.x, the 24B Bootstack, for Lollipop 5.1.x and Marshmallow 6.0, the 35B Bootstack. I don't use anything but stock VS985 ROM-based. I don't know what Android version Fulmics is. He warned that some people with the VS985 never get their signal or at least mobile data working right on Fulmics or other international stock ports, and on some CM/AOSP too.

The second is better because the links in the first are dead and the screenshots aren't as good.
[Verizon LG G3] DarkFamiliarity:
Thank you again for the quick and detailed response. I think I'll follow laserwolf's video guide, as everything is clearly explained. There is just one conflict between the text guide and video guide. In the video guide, laserwolf says that the phone should not be unplugged until flash tool goes to 100% and says pass. On the text guide, it says this:

If in case the flash tool fails at 85% or above, what are the exact steps I should take (unplug, pull battery, shut down flash tool) ?

Also, how do basebands/modems/bootstacks work? I don't know which is which. If I want to go from 10b to Fulmics (ROM OS Version: 6.0.x Marshmallow), I have to flash the 35B bootstack and what else?

I think I will try Fulmics as my carrier uses band 3, and http://xdaforums.com/lg-g3/general/4g-fix-fulmics-rom-verizon-vs985-t3398361 seems to be a valid solution for the data issues. I'm not on a verizon SIM anyway.

Thank you!
[Verizon LG G3] roirraW "edor" ehT:
My pleasure!

If by text guide you're referring to the instructions in the first post of this thread, this thread is for flashing KDZs. [MENTION=5066255]LASERWOLF452[/MENTION] 's video guide is for the TOT method, which is more universal since it can downgrade from 100% stock 35B and higher to 10B whereas the KDZ method can't.

The "85%" is referring to what the Windows program says - not a reflection of what the phone says. It'll reboot as normal. It's also normal for LG Flash Tool 2014 (the Windows tool for flashing KDZs, referred to by this thread) to crash at the end, and to throw error dialogs during the process (see post # 2). If you ever flash KDZs, just never click any error dialog buttons - move them out of the way if you have to but otherwise ignore them.

Read I believe it's the second post of [MENTION=2941286]xdabbeb[/MENTION] 's VS985 v2.0 thread - it describes what the Bootstack is. The Bootstack includes the appropriate modem. Modems are the same as basebands. 12B Bootstack is for KitKat 4.4.2, 24B Bootstack is for Lollipop 5.0.x, and 35B is for Lollipop 5.1.x and Marshmallow 6.0.

I'm not sure what any particular ROM might have to do with getting certain bands to work, but I'm not that knowledgeable about that sort of thing since I'm on Verizon and haven't fooled with alternate bands or using the VS985 with other than Verizon. As far as I understand, no matter what carrier you're using you can enable bands that are normally disabled, but I don't know the details for the same reason as above. :) I only know there's threads in the General and Q&A section detailing how.

So I guess what I'm saying is that unless there's something I don't know about Fulmics (and if I don't, please feel free to let me know what it is), it's just as easy or effective to just unlock the correct bands on any stock-based VS985 ROM.

You're welcome! Happy flashing.
[Verizon LG G3] DarkFamiliarity:
Thank you again for detailing out the baseband/modem details, really helps with understanding the procedure.

By text guide, I meant this one. End of the post has the 85% warning.

If the program comes to a complete halt or just crashes around 85%, I just leave the phone alone until it reaches the factory reset stage, then pull the battery out?

And as for the Fulmics thing, if it's easy to change to band 3 then there shouldnt be any data issues, and hopefully I can use the ROM like an international variant user. Is flashing the bootstack once more after installing the rom safe?

So that means the procedure is downgrading to 10b via tot > rooting with stump > twrp with twrp manager > nandroid backup > full wipe > flash 35b bootstack > flash fulmics 5 > flash ota updates in order > optionally flash xposed > wipe cache/dalvik > reboot, am I right about the baseband part/missing out any files?

Thank you once again for patiently answering all my questions! I'm just paranoid something like this may happen. Hopefully this is the last set of them.
[Verizon LG G3] roirraW "edor" ehT:
Ah, thanks. It's confusing since we're talking about this in the KDZ thread. :D I really wouldn't worry about it. Although I've flashed the TOT a dozen times I can't recall it ever ending with anything but a "SUCCESS". I know I've at least occasionally either had to pull the battery (but not every time I don't think), and at least once or twice I think I got the big red "3" (or is it "2"), which normally should only appear briefly when it does and then it changes into the other. Sorry I don't recall if it usually ends in "3" or "2" - I know that one of those is normal and the other isn't, and when I got the one it wasn't supposed to be, I believe I had to flash the TOT again right after but everything was good after that. I might've had that happen twice.

I always suggest flashing the Bootstack AFTER flashing the ROM, but only because there's two stock based ROMs, JasmineROM 9.x and SkyDragon 6.x, which contain a partial 24B Bootstack - so that if the 35B Bootstack is flashed before flashing either of those two ROMs, you end up bricking and you have to flash the TOT or use the QHSUSB_BULK 9008 mode method - again, it all kind of runs together since I haven't had that happen to me in a while. So I always tell everyone to flash the appropriate Bootstack after flashing the ROM - BUT to answer your question, as far as I know, there's never any reason that you shouldn't flash a Bootstack after flashing a ROM, or flash it twice, once before and after. There's no reason to flash it twice, either - just flashing it once after flashing any ROM is all you need.

Another reason I tell users to get in the habit of flashing the correct Bootstack after flashing a ROM is they should also get in the habit of flashing the right Bootstack after restoring a TWRP or other kind of backup. And I recommend that even if you think you're on the correct Bootstack already, again, just get in the habit of always flashing the right one after a ROM flash or restoring a backup.

I can't really advise regarding Fulmics flashing - I haven't flashed it in over a year, but of course according to what I said above, flash the Bootstack after flashing the ROM - the only reason to flash it first is if the ROM purposefully overwrites some of the Bootstack and it might - I don't know but I doubt it since some of the Bootstack components are dependent on other components. If the ROM installation instructions say to flash it first, then I suppose follow their instructions. You should probably be asking in the Fulmics thread to get a better answer.

Normally another Cache/Dalvik/ART wipe isn't necessary if you did one before you started flashing, but as a rule on *any* Android device if you have trouble booting a ROM, even after restoring a 100% official stock ROM, wiping Cache and Dalvik/ART should be the first thing to try to get it booting. If you want to wipe them again, it shouldn't hurt anything of course.

Doesn't sound like you're missing anything to me. Of course, you have to install the Xposed app that's downloaded directly from the Xposed Lollipop/Marshmallow thread inside Android once you're booted.

You're welcome!