yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] vipulkarkar:
I was using xolo q3000 since last 2yrs.

I bought lg g4 and my younger bro bought lg g3.

I flashed Resurrection remix on my g4 and was doing the same to g3. I have been involved in porting Roms and developement even after belonging to medical profession. This is my hobby. I was new to flashing roms and methods on lg devices.

And yes my device manager showed QHSUSB.

I downloaded 10b tot.

Updated firmware.

Flashed tot using lg flash tool.

It was kitkat 10b.

Rooted using kingroot.

Installed flashify.

Flashed twrp 3.0.0.

Rebooted into recovery.

Flashed Resurrection remix (Marshmallow)

Flashed gapps. mM nano.

Wiped cache.

Flashed bootstrap 35b provided by [MENTION=2941286]xdabbeb[/MENTION]

Rebooted successfully. But network was not showing up inspite having valid imei.

Then changed network mode in settings and now everything is working great.

My bro is more than happy and the credit goes to you.

Thanks a ton.

Shared all steps so if someone faces same issue this can help them.
[Verizon LG G3] johnny567:
Alternative?

So I've tried this method twice and have had to send my g3 in both times due to it being bricked so hard. LG put bad PMIC on both receipts when I sent it in. The first time I tried with 12b aboot, the second the 35b like posted here. My question is, would it be possible to use the test point to restore to 10b? I would prefer to try the less risky of the two. Current firmware is 47a rooted with king root.
[Verizon LG G3] roirraW "edor" ehT:
Hi!

From the OP:

To clarify, I *always* recommend the above (TOT method) first. Even when having problems with the TOT method, you should do everything you can possibly do to try to get it working before using this method. That said, I haven't been able to replicate bricking my phone with this downgrade partitions manually method, although some seem to have something closer to your experience (although not necessarily having to send their phone in, in order to recover) and others have had my experience, which has been no bricks with this method.

I had made this thread after I tested the method, only since there were a select handful of users who despite all reasonable efforts just couldn't get the TOT method working for them. In total I've tested this method 2-3 times.

Also, I'm not sure what you mean by "first time I tried with 12b aboot, the second the 35b like posted here". The aboot (boodloader) that's in the 35B Bootstack is the 12B aboot. Using the 12B (or earlier 11C or 10B) aboot is the only way we can get into TWRP. Any aboot newer than 12B, you can't get into TWRP. Maybe you were confusing the aboot and Bootstack terms? All the Bootstacks (12B, 24B and 35B) contain the 12B aboot.

I believe most people who bricked their phones on this method were able to recover either using the regular TOT method or the QHSUSB_BULK 9008 mode method. At least one person was able to use the KDZ method, which was part of the aim of these instructions as well since before these steps, if you're on 35B or higher, you can only use LG Flash Tool to flash any KDZ 35B and higher.

You'd have to Google QHSUSB to get the directions for recovering from that mode - it'll involve the 10B TOT as well, but using a different Windows tool. I have had my phone in QHSUSB mode twice before, caused by other experimentation not related to this thread, and was able to recover it myself using the recovery methods I found via Google.

I know there are methods to put the phone into QHSUSB_BULK 9008 mode using the test point so that they could use the QHSUSB recovery method after, but I don't believe the test point will specifically help getting the phone onto 10B other than enabling using the QHSUSB method. If your phone is currently unbricked, I definitely don't recommend fooling with the test point - that's only to be done if your phone is hard bricked but not showing up as QHSUSB_BULK 9008 mode in Windows' Device Manager in the Ports section.

Edit: I finally changed the OP to make obvious note just how dangerous this method appears to be for some people. I had considered doing that before but since I never had the issue myself, I really didn't want to.
[Verizon LG G3] johnny567:
Okay. Thank you. The tot restore hasn't worked for me. Every time I get the ks error. I don't know if I want to risk it again but thank you for this method.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! I wish there was some easier alternative. Is there any possibility to try to use someone else's Windows PC to try the 10B TOT method (using the .DLL extracted from the 35B KDZ)?
[Verizon LG G3] rohitece06:
worked flawlessly for me!!!
[Verizon LG G3] roirraW "edor" ehT:
Awesome! Thanks for the report.
[Verizon LG G3] undeadking:
Hey there man- I've got good news, After nearly a month without a working phone(since I soft bricked mine like an idiot) Last night I was finally able to get my G3 booted, But not after a hundred attempts and tons of hours-trying different friends computers, usb cables, about a hundred gigs of kdz, tot, LGUP, flastools, and drivers downloads... I was 100% unable to 10b tot but finally I got LGUP to flash the 35b kdz and have a working phone again but still no TWRP due to the "no ks version and ks version error" when trying the 10b tot with proper .dll. When I'm back at my friends computer tonight I am going to give your dd method a shot since I have a way to recover if I run into any problems. My bad for the mildly OT post- I'm just super stoked to finally have a working phone :)
[Verizon LG G3] roirraW "edor" ehT:
That's cool, really glad to hear it and thanks for the update. Let us know if you find anything out further.
[Verizon LG G3] undeadking:
So i tried the dd method and the second i pasted the commands in terminal emulator my G3 screen went black and there is zero response as far as it turning back on... When plugged into a computer running windows 10 i get an error message saying that an unrecognized or malfunctioning usb device has been connected. I havent had a chance to try and fix it further- just wanted to report what happened when using this method since i have been unable to tot back to 10b and go that route...
[Verizon LG G3] b00ster23:
Have you tried to hold the vol down>power button together? there are certain times when I couldn't get the lg splash screen up I would have to use this method to get thru. I'm sure you've tried but wanted to put it out there...
[Verizon LG G3] jlb1959.01:
I have a question for roadwarrior,ur very good at figuring things out,why is it that after getting a temp root with KR., a person couldn't eliminate KR, replace it with SU,then reboot?just asking,i know ur way of downgrade to 10b works fantastic,and I thank everyone involved for those files and instructions..this probably is the wrong way to ask this question so please excuse for my ignorants..
[Verizon LG G3] roirraW "edor" ehT:
You may or may not be able to do completely eliminate KingRoot and replace it with SuperSU somehow. Some people have on various devices. There's even an app for that "SuperSUMe", but it's a crapshoot sometimes it works and others it's unsuccessful, leaving people with a brick. Recoverable, but brick which requires just using the 10B TOT as could've been done in the first place. It's tricky since you can't completely eliminate KingRoot before you put SuperSU in place, since you need something there to give (or deny) apps permission to use root, and you need root to put SuperSU on. Also, having two competing root permissions apps running at the same time - SuperSU and KingRoot will often lead to a crash or brick.

[MENTION=2941286]xdabbeb[/MENTION] got to dive deep into just how entrenched KingRoot is into someone's phone once you use it to root. It puts things on the phone that are completely unnecessary and are not noticeable to the unwary user. KingRoot is always changing so what needs to be done to get rid of it and replace it with SuperSU might change on a regular basis, which could partly explain why SuperSUMe is sometimes unsuccessful.

IMHO, the easiest and cleanest way of rooting is to use Stump on 10B, anything else is just banging my head against the wall. :D A lot of effort for possibly some gain, or possibly a brick.

And no way to downgrade to 10B is better than just using the TOT with the appropriate .DLL. As you probably know, the steps I give in the OP are meant for last ditch effort only for those who get "KS ERROR" when trying to TOT. I'd try everything in my power including using a different PC before this method, since - unknown to me what the reason is - a decent quantity of people have the experience of bricking their device with my instructions, too.
[Verizon LG G3] jlb1959.01:
As I said,your instructions worked FANTASTIC on my wife's phone as I did in fact brick her phone on 5.1 when using supersume,i asked you what to do,you posted the way and I unbridled,downgraded and rooted,however I left it alone when rooting at 10b,now my phone has its Upgrade to 6.0 and as you probably remember I complained of crappy battery life compared to 5.1 and using greenery.so at some point I too will downgrade to 10b,i used KR for temp root to eliminate some of Verizon's bloat,didn't make that much difference in battery Mike,i also noticed even after a factory reset it shows as my phone was modified,which in guessing but something from KR is still in my phone? I will say your VERY talented with 985 and your GREAT with our files and guidance.I was and still am convinced that downgrading and rooting is the best way to get performance on the 985.thanks again,can't thank you enough,not many people take the time to truly advise people,most just opinionate bad criticise.in sure when I try to dwngrade to 10b from 6.0 I will be bugging you,lol..
[Verizon LG G3] roirraW "edor" ehT:
Yep, once KingRoot is installed and you've used it to root, unless you flash a TOT or KDZ, it's going to say Modified. Factory Reset doesn't wipe all the stuff KingRoot leaves in the system partition. Even if you removed all the KingRoot stuff manually it would say Modified. [MENTION=2941286]xdabbeb[/MENTION] 's ROMs (both the 47A firmware and his VS985 v2.0 ROM based on 35B) put Official as the status manually.

Well thank you very much! You're welcome! I couldn't know what I know now without having learned from those who know more than I.

To downgrade, use the 10B TOT and the .DLL that's extracted from the 35B KDZ. Both are available at my Android File Host section, which is linked to at the very bottom of the first post of [MENTION=4795150]annoyingduck[/MENTION] 's stickied return to stock thread in the General section. That thread is also in my signature below.
[Verizon LG G3] jlb1959.01:
Ok,so if I downgrade to 10b via ur files,will that wipe the mess that KR left behind in my phone.because the phone is still covered for problems but I want to clear the KR remain,then follow your files for 10b and stump root.at least that's SAFE!!.
[Verizon LG G3] roirraW "edor" ehT:
Yes, it would be restored to 100% stock unrooted just like from the factory. Move anything that you want to keep from the internal storage. You can use the built-in LG Backup to backup your user apps, user data and limited system data. It's very fast and easier than Titanium Backup although you might still want to use TB for things like backing up Bluetooth pairings, etc.
[Verizon LG G3] jlb1959.01:
Thank you,your fantastic my friend..
[Verizon LG G3] thvoicwethin:
After 2 hours of messing with KDZ and TOT, this method did the trick. I cannot thank you enough for this process, I can finally be at peace with my phone now that I have 47A and a custom ROM. For those on 35B, I posted in /r/LGG3 on Reddit about my full method of getting from stock 35B to a rooted 47A using The Road Warrior's guide Replacement G3 on 35B, here's how to get to 47A. You, sir, are a godsend.
[Verizon LG G3] roirraW "edor" ehT:
*Blush* Thank you and you're welcome! We all owe [MENTION=2941286]xdabbeb[/MENTION] too! Glad this helped and that you didn't end up bricking like some people.
[Verizon LG G3] thvoicwethin:
Agreed. I haven't run into an issue like this since I bricked my Droid 1. But when you mean "last ditch effort", it really means, "Come all ye who had no more faith that you could TOT to 10b, I will show you the way". Currently running Ressurection Remix and re-downloading all my apps. You'll have a beer in your paypal soon, or a drink of choice.
[Verizon LG G3] roirraW "edor" ehT:
LOL! Well thank you very much!
[Verizon LG G3] appzstarxda:
I have successfully used this method without any problem. Thank you so much for this wonderful share
[Verizon LG G3] R-T-B:
Just to caution others who have February 2016 forward made/ordered LG G3's, it seems at least I can no longer downgrade the bootstack. It immediately bricks the phone requiring testpoint recovery.

Please see this thread for more info:

http://xdaforums.com/verizon-lg-g3/help/vs985k-purchased-verizon-ships-47a-t3420071

If you have an older phone you are probably ok.

A potential way to identify this would be to look at your PCB. Mine has "HW Revision 1.0 (2)" printed on it. That "(2)" probably means they revised the PCB to obey the qfuses, and block downgrades.
[Verizon LG G3] roirraW "edor" ehT:
You're welcome!!! Thanks for the report.
[Verizon LG G3] ST Dog:
Just got a CPO G3 for my wife. It came with 35B installed.

She's been using xdabbeb's VS982.5 on her G2 for a year or so.

I knew there had to be a way to root and get TWRP on the G3.

This worked great and I'm flashing xdabbeb's VS985 V2 now.

I made it through the thread and was wondering if anyone ever hear more from [MENTION=3279781]bender_007[/MENTION] regarding autorec for LP or MM on the VS985.

If he's got it working I didn't see it earlier when searching.

It might be good to link it in the first post as an automated system is less error prone.
[Verizon LG G3] roirraW "edor" ehT:
Great, glad to hear! Out of curiosity, had you tried the 10B TOT method before this and had trouble?

[MENTION=3279781]bender_007[/MENTION] 's thread for autorec TWRP is in the non-Verizon G3 General section. I just checked again and no, at least in the OP of the thread there's no mention of a version of the app beyond 24B.
[Verizon LG G3] ST Dog:
No, I just got the phone yesterday AM.

Knew I wanted xdabbeb's ROM.

I was a slacker and didn't find everything I needed before that, and had to wait for the phone to see what SW it had.

As I was looking for root options I kept seeing that TWRP would work, but I had read xdabbeb's post in the 35b ROM and bootstack threads so knew it would and suspected I just needed to get the old aboot to get TWRP working (and a bumped kernel)

Then I found this which confirmed my suspicions.

(Suspect just need aboot and recovery then flash the bootstack from TWRP)

Maybe time with the G2 made me more open to it?

Oh, and afh was acting up last night when I tried to download the DLL and TOT (that was the backup route). But it worked fine earlier to get xdabbeb's stuff.

Wonder what happened. Maybe trouble with detection to get the right kernel?
[Verizon LG G3] bender_007:
:) just lack of time. I promised new builds and they will come for sure

Poslano sa mog SM-G930F koristeći Tapatalk
[Verizon LG G3] rooster1973:
Bricked my phone too. Just black screen, no lights. Pasted commands everything looked good, then after reboot recovery, just black. Wont respond to any flash tool. Just wrong ks, missing ks, missing IMEI or wrong model version.
[Verizon LG G3] roirraW "edor" ehT:
By "any flash tool" does that include BoardDiag? Are you going through the motions of trying to put into Download mode? Meaning pull the battery, put it back in, then the usual to put it into Download mode while connecting it to the PC - just ignoring that the screen doesn't show anything.

When you do that, what shows up in Windows' Device Manager in the Modem and Port sections. Does it show up as "LGE..." device, or does QHSUSB_BULK 9008 mode show up in I think the Port section? If the latter, then you need different drivers and a different recovery method, just Google for the QHSUSB_BULK recovery method. Uses the BoardDiag program and the 10B TOT. The preferred, faster method only has you use BoardDiag to flash some key partitions, and then has you continue recovery using the normal TOT method, which is faster than continuing with BoardDiag, which flashes things much more slowly plus you have to flash one partition at a time.

If you really did get your IMEI wiped (if the regular TOT flashing program still refuses to flash the TOT after switching from BoardDiag), you can continue flashing partitions with BoardDiag. There's a thread or two in this section or maybe the non-Verizon G3 General section for putting the IMEI back in manually using another WIndows program, but I've never had to so I don't know if the phone has to be running or at least minimally recovered with BoardDiag first.

Or if you use BoardDiag to flash the rest of the partitions and get 10B fully running, then re-root with the Stump app with it's brute force option, reinstall TWRP with TWRP Manager from the Play Store, then if you made a backup of your EFS with TWRP you can restore that and that'll restore your IMEI. I keep a password-encrypted copy of the EFS from all of my devices on Google Drive as a backup just in case. I've never lost my IMEI through all my flashes, so I've been very lucky.

Out of curiosity: had you actually had the "KS Error" or another problem when trying to use the TOT method before this one?
[Verizon LG G3] rooster1973:
Thank you for the replay. I have tried the flash tool, the 2014 flash tool and boarddiag. I either get 4% lockups in 2014 flash tool or failed previous load in the other flash tool. Boarddiag says can't access flash program mode or something like that and says ap bad. I do think it is going to dload mode but can't see for sure. I do get a vibration and LG device drivers (LGE ANDROIDNET USB SERIAL PORT41) Was getting ks error or missing ks which is how I got to the replacing of the aboot etc in the last ditch effort method.
[Verizon LG G3] roirraW "edor" ehT:
Sure!

BoardDiag would be useless for you unless Device Manager was showing your phone as "QHSUSB_BULK 9008". If it's showing "LGE..." then you don't need BoardDiag. Again, BoardDiag requires special drivers, too (and also on 64-bit Windows, disabling driver verification certification in order to install the special drivers properly).

Maybe you should try [MENTION=2250889]R-T-B[/MENTION] 's thread in this section with a very large unbrick zip of files/programs to try. He created the zip as part of solving his constant bricking trying to downgrade his phone. He was never able to get the phone to downgrade but he was at least able to get it back to 100% working stock 47A. The reason his bricked might've been different than yours but it's possible the same methods to unbrick might help. It probably won't hurt, at least, and is worth a shot.

About the only other thing that I can think to try is another PC but I don't know if that'll help in this situation.

Good luck!
[Verizon LG G3] rooster1973:
Do you know where I can find a dll file for the 35B firmware. I keep seeing downgrade to 10b using the 35b dll but can't find one.
[Verizon LG G3] roirraW "edor" ehT:
Yep, my Android File Host link at the bottom of the first post of [MENTION=4795150]annoyingduck[/MENTION] 's stickied return to stock thread in this section, also in my signature below. I believe the file numbered 7b. Extract the .7z archive with the free 7-Zip from www.7-Zip.org on Windows to get the .DLL.

And that's definitely a reason the TOT method wouldn't work for you previously.
[Verizon LG G3] ST Dog:
Weird that people have problems with a seemingly straight forward thing.

Temp root, write a few partitions, and boot to recovery.

What could be the cause? dd not working? Shouldn't there be an error?

Wonder if adding a verification (read partitions back and compare) might catch some problem?

I wonder if there's some common bit to the faults. Like the current version on the phone, or how they got there (OTA v/s TOT v/s KDZ)

Mine was in a CPO box, assuming it was a CPO device. So 35B may have flashed (KDZ or TOT) instead of OTAs.
[Verizon LG G3] roirraW "edor" ehT:
I might've only asked one or three users who bricked if they had compared the Terminal output to what I have in my screenshots, but if I remember correctly, either no one had compared or only one had, so I stopped asking pretty quickly.

I took a lot of time to make, mark up, and splice the screenshots together - I had previously already tested the method I believe two times without a hitch - perhaps once on 46A and another on 47A, and I then had to make backups, move everything off of my internal storage again to flash the 47A KDZ and create the screenshot. I realize I could've made the screenshots while on the rooted 47A ROM but I like to keep things as real as possible, so only actually doing it on the real 100% stock 47A would do as far as I was concerned.

It's such a long series of screenshots I had to [ S P O I L E R ] them to keep the OP as reasonable as possible, but perhaps users ignore the screenshots more with them spoilered?

It's similar to MD5 hashes - even when OPs instruct people to check the MD5 hash of a flashable ROM zip before flashing, it always seemed most people don't even after they have a problem flashing, so that's why I don't bother pushing people harder to compare the screenshots with their output.

That all said, I'm 99% convinced that at least in the majority of cases, no one is doing anything wrong, or not following the directions completely - OTHER than the potential difference in output. I don't think anyone ever volunteers the information that they compared their output with the screenshots either.

I have ideas for making a more complicated/intelligent script or process, but as with everything else it would take time I don't have, and I'm not convinced it would help diagnose this problem, and it's hard to get motivated to do a lot of work that might merely answer the question in the affirmative "were all the partitions flashed correctly". I could be wrong, of course. If users would instead just compare the screenshots to the Terminal output before rebooting to recovery, we might have some ideas, although it's possible that there were one or two users who said their phone went to black screen after flashing the partitions but before trying to reboot to recovery.

I doubt it, but it's as good a possibility as any other and definitely would be worth asking about in the future if I can remember whenever anyone bricks. Thanks for the suggestion. Any piece of information, especially one gotten as easily as this, would at least help confirm or eliminate the likelihood.
[Verizon LG G3] ST Dog:
Didn't mean they did anything wrong ;)

But something certainly went wrong.

The black screen w/o rebooting really makes no sense unless the wrong partition was written to.

Maybe the modem?

But aboot, sbl, and recovery aren't used once booted.

Perhaps better luck with a more minimal set of partitions. Would require the full bootstack being flashed in recovery after, but that's already true. Well I did anyway just to be safe ;)