yashsingh1/xdaforums huggingface dataset:
[Verizon LG G3] b00ster23:
I had actually tried to use the 35B DLL in the above posted link. My experience was that even with the right .dll and 10 and 12 TOT files, I still wasn't able to downgrade. I had multiple installs and files so who knows if my PC was "janked" up. I would have used the TOT method if it would have worked, and was willing to try. I just didn't feel like hashing thru the ts'ing of the apps and .dll's, and tried the above method. My suggestion would be if you're on 35B or 46A try the TOT method first and research all of the errors (which I've worked through previously) This was my last resort to the LAF error I couldn't get through.

[MENTION=2560614]roirraW "edor" ehT[/MENTION] if a person had the LAF error only, would they necessarily have to upgrade all of the partition previously mentioned, or only the LAF partition and run the TOT downgrade method? This is only morbid curiosity... ;)
[Verizon LG G3] roirraW "edor" ehT:
You're very welcome! Good luck!

LOL. My first post already has that information:

Since I haven't been able to reproduce the issue of getting a black screen / not being able to get into TWRP, etc, I really don't have anything to say about that, at least until someone who has the problem says that their Terminal Emulator output matches my screenshot(s) exactly.
[Verizon LG G3] roirraW "edor" ehT:
I believe you, of course.

I absolutely agree with you: everyone should use the TOT method first. I considered for months whether I should test this method but decided to mainly for those who just couldn't get the TOT method working.

I'm not sure what you mean about upgrading the partitions, unless you meant downgrading. I don't know, but I won't be surprised that only changing the laf partition would help downgrading. If you're going to use TOT, anyway, there's no reason to change what version of the laf partition you have.

Many months ago after 35B came out, someone (don't remember who), who was desperate to downgrade so they could root experimented with a couple partitions including laf and they didn't have any luck, but I can't speak as to whether they were following my direction as completely - because at some point I mentioned downgrading several partitions using the ones from the 35B bootstack and they either didn't have any luck or didn't try it. Too long ago to remember. :)

Downgrading sbl1 is necessary because the 46A sbl1 in combination with the 12B aboot causes the QHSUSB_BULK 9008 brick. *some* of the other partitions might not be necessary, but I didn't feel like potentially testing a bunch of scenarios so I tested downgrading partitions that in my opinion could remotely affect the likelihood of this working. Since the first combination of partition downgrades I chose worked, I didn't feel like making any unnecessary hassle in further testing.
[Verizon LG G3] undeadking:
[MENTION=2560614]roirraW "edor" ehT[/MENTION] when I copy the txt file into terminal there is a couple blank lines at the bottom- should I just delete them or did you add them for a reason? I know its a stupid question but being my phone is literally my only means of communication- id rather not have a bricked device and no way to recover right now. Thanks
[Verizon LG G3] roirraW "edor" ehT:
Blank lines are like pressing enter on your keyboard. Pressing enter any amount of times in terminal won't do anything. If you don't paste at least one blank line at the end, you'll have to manually press enter after pasting.

If you don't have a way of recovering from this, then I don't recommend you do this right now.
[Verizon LG G3] undeadking:
Ok cool thanks bud! I'm just itching to flash some roms. Lol

Sent From MY PIMP CLASS G3!!! ;)
[Verizon LG G3] roirraW "edor" ehT:
You're welcome! I just hope you don't regret it, mate.
[Verizon LG G3] bender_007:
Hey m8, may I use the files provided by you and xdabbeb ( I´ll ask xdabbeb also now) and package into autorec fo v35?

Cheers and good job:good:
[Verizon LG G3] roirraW "edor" ehT:
Thanks and you're welcome! The files are all stock, [MENTION=2941286]xdabbeb[/MENTION] 's 35B bootstack just makes a very easy one stop shop. His permission is all that's required. You can credit me for testing if you want to.

Take note that I don't include the necessary bump'd kernel, so with only these partitions, you *have* to flash another ROM from TWRP. I didn't feel like specifying to people, "...If on 35B, flash this...if on 46A, flash this...etc".
[Verizon LG G3] bender_007:
Can someone supply the 35b and 46a bumped kernels ? :)

If xdabbeb gives the permission I´ll create it automatic (it would automatically flash the right one)

Of course you will be in credits (I´ll post it here and include the thread next to the dload link)

Thanks :)
[Verizon LG G3] roirraW "edor" ehT:
You could ask [MENTION=2941286]xdabbeb[/MENTION] about the kernels - he might already have made them. In the case of 46A Marshmallow, his kernel in his stock 46A firmware ROM is only customized as far as having systemless root.

Cool re: automatic. People get so confused about the different versions for different stock releases. LOL.

Well thank you! No sweat!
[Verizon LG G3] roirraW "edor" ehT:
Added information that this works from 47A. You can additionally still use the TOT method to downgrade to 10B by using the .DLL from the 35B KDZ (you don't need to do the steps in the OP in order to use the TOT method).
[Verizon LG G3] mopartonyg:
[MENTION=3279781]bender_007[/MENTION] I do not have the kernels but on stock 47A when you need a tester. Thanks for helping out here
[Verizon LG G3] bender_007:
Hey, xdabbeb has sent me the kernels. I'll send you a small apk to test the detection first

Poslano sa mog LG-H815 koristeći Tapatalk
[Verizon LG G3] roirraW "edor" ehT:
Cool, thanks!
[Verizon LG G3] mopartonyg:
Here if you need another tester
[Verizon LG G3] bender_007:
Thx guys:)

Poslano sa mog LG-H815 koristeći Tapatalk
[Verizon LG G3] bcsizemo:
Soft borked.

For some reason I'm always "that guy"... I ended up being one of the lucky "KS error" people, so I decided to take the plunge and try this route. Needless to say now it appears I'm soft bricked but I keep running into issues trying to tot back to 10B.

The phone has no picture, which I understand has something to do with a partition mis-match (I was on 47A when I started this). Doing the normal methods of tot-ing back to 10B I run into an error of version mismatch. The flash tool shows my version as either [] or [unknown] to [vs985] and stops. I came across a modified dll that is suppose to bypass this (and it appears it does), but when getting to about 6% I get the can't enter download mode issue. Of course I've tried on a couple of different machines, drivers, ect.. With the screen not showing me anything I don't even know if it is going into download mode.

I'm just throwing this out there if anyone has a suggestion.

-The USB Serial Port is set to 41. This is a Verizon and I'm use the 2.20 unified VZM drivers.

-Tried booting "normally" and ADB doesn't detect anything.

-When trying to place it in download mode the vibration is longer than when just pressing the power button.
[Verizon LG G3] roirraW "edor" ehT:
Hi! At least in this case there's enough other people who've had a similar experience with this method, although I haven't in my tests.

Even without seeing the screen, if you're going through the motions to put the phone in Download mode, and you're seeing the phone in Windows' Device Manager - either in the Modem section or Ports section (Modem section for flashing KDZs, Ports section for TOTs, from what I recall off the top of my head, but both should show up regardless).

I'm not familiar with the can't enter download mode issue.

You can flash KDZs if you had successfully downgraded the partitions, too - you don't have to do TOT, although personally once I got a KDZ to flash, I would flash the TOT after in this case just to be sure everything's 100%.

If the phone is listed as QHSUSB_BULK 9008 mode in Device Manager, you'll have to Google that to find the recovery instructions, which will also use the TOT, but a different program to flash specific partitions one by one, after which you'd follow the normal TOT directions. I've recovered from QHSUSB_BULK 9008 mode twice, although I haven't had that or any problem when downgrading the partitions as specified.

Good luck!
[Verizon LG G3] bcsizemo:
It's not listed or showing as bulk mode, which I suppose is a positive. I did try the KDZ first but kept getting an error there as well, TYPE_WPARAM_UPGRADE_ERROR, wParam : 100, lParam = 51. Which I haven't found much on. I tried with the 24B and the 10B KDZ files.

Looking into the BULK 9008 issue, the board diag tool keeps saying not in DL mode either...

Hmph. Might have to go the hardware route and see if I can force it into the 9008 mode.

Alright so here's an update a week later. I've poured 10+ hours into this and still haven't made progress with the phone. However I have learned a lot about the G3 and variants. I appear to be in some pseudo boot mode, not fastboot or a real download mode or anything to do with secureboot.

If you notice in this thread:

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

a lot of people talk about no picture, no boot, no recovery, no fastboot, no adb, zip. Most programs talk about not being in download or DLOAD mode, ect.. That's me. Now if anyone is reading this please let it be known I hold no bad feelings to roirraW "edor" ehT or anyone else, and it's likely I played a large part in how this happened by futzing around with the terminal commands.... From everything I've found the procedure he has laid out is sound and if followed to the letter should work.

So I've exhausted the software options I've found and have moved on to doing the hardware jumper of forcing the phone in the 9008 mode, which literally it might be easier to find a needle in a haystack cause damn this stuff is tiny. I'll report back just because I hate when people leave threads/posts unresolved.
[Verizon LG G3] marwan20030:
Thank you for the wonderful work.

I updated my device to version 47A and i lost the root and after long search i found your guide, and I've finally succeeded restore my backup to 23C.

Now excuse me for my stupid question, if i flash the updates from 23C to 24B and then to 35B, 46A, 47A. i will lose the root and recovery again?

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

No. You cannot successfully take OTAs starting with 23C->24B one you root. Meaning I don't know if you'll lose root - probably not, but the update won't take, either.

Not only that but noone (that I recall) has reported successfully finding a way to manually apply the updates - again, starting with 23C->24B. So if anyone has had success, they're not reporting it unless I'm key not remembering.

Also - no phone that I'm aware of had been able to take OTAs while having a custom recovery installed.

If you want to root, have TWRP and have 47A, you want to downgrade to 10B (since you're on 23C, it doesn't matter if you want to use the 10B TOT or KDZ), root with the Stump app, use TWRP Manager from the Play Store to install TWRP, then flash [MENTION=2941286]xdabbeb[/MENTION] 's 35B bootstack followed by his stock 47A firmware.

Of course if you're rooted and have the latest TWRP already, just go straight to the 35B bootstack and 47A firmware by flashing them from TWRP.
[Verizon LG G3] bcsizemo:
Update a week later.

I did the pin shorting to get it to go into 9008 mode but it doesn't really help. The boarddiag tool, adb, and fastboot all do not see the emmc nor are there partitions showing up in windows/linux. It seems like after a certain period of time the phone times out and reverts to the not in DLOAD mode in boarddiag.

I've scoured a decent amount and haven't found anything solid other than some cryptic posts about the wrong hex files with board diag.

If anyone has suggestions I'm open, but I'm seriously considering sending it in for warranty.
[Verizon LG G3] roirraW "edor" ehT:
That sucks. Sorry to hear that, and thanks for your updates both in your previous post and this one. I think you should go the warranty route if you have that option, too, unfortunately. If you're talking about LG warranty, I had a *really* good experience with warranty repair on my LG G Pad 8.3 VK810 tablet. It had some kind of screen problem that got worse over time until I couldn't deal with it any longer or wouldn't display anything any more.

They gave me a shipping label, I believe for Fedex or UPS, and I didn't even have to package the tablet - LG paid for Fedex or UPS, whichever it was, to package it for me. I dropped it off about 5 PM on a Monday, and it was back in my hands 5 PM Friday the same week and actually repaired in this case (not sent a refurbished replacement).

Much better than my Sprint Samsung Galaxy S2 warranty repair which took weeks - I think at least three weeks.

If you're talking Verizon warranty, I can't speak much to that because I haven't successfully used that since about 5 years ago, at which point I had successfully used Verizon's paid warranty twice, once each for a dumb phone, and for my first Android phone. Incidentally, I was paying for the best Verizon warranty when I needed the tablet repair. They wouldn't touch it since it was still under LG's warranty, so basically I was paying for the first year of Verizon warranty for nothing. I immediately cancelled the Verizon warranty and was happy I had such a good experience with LG. I'll never pay for an extended phone warranty again.
[Verizon LG G3] bcsizemo:
I stopped in the Verizon store and ultimately they are sending me a replacement (probably a refurb, but at this point it needs a new board or at least a hardware level flash) so there's that. Now here's the real question, should I try this again?

And since I've poured through 25+ threads about every error related to any of this I get the feeling there are levels of "danger" involved with various aspects of doing things. Obviously one click rooting is the easiest or some simple exploit. Then you get into harder things venture off into trying to flash back previous versions... But at that point does it matter how you do it? I mean here you rooted and used terminal to dd the partitions, could the same not be done via ADB or board diag? I'm just wondering if it matters how you get the partitions on the phone or not.
[Verizon LG G3] roirraW "edor" ehT:
I *always* recommend the 10B TOT method using the .DLL extracted from the 35B KDZ before resorting to this method, as I note in the OP.

No, as far as I know it shouldn't matter how you get the partitions on there.

It honestly perplexes me how I haven't had trouble the two or three times I've done this but lots of people bricked their phone on the first try - although of course as far as I remember, everyone else had been able to recover from it. But it's not like I've done this a dozen or twenty times so who knows - it's possible I would have the same bad experience if I did it enough times.
[Verizon LG G3] b00ster23:
As an update to the process (actually verification) I just had another VS985 shipped to me for activation. The default ROM setup over 200 apps upon the "Android is starting..." process. So first thing I do is TOT that little guy down to stock 35B rom. Interesting enough upon reboot under 200 apps started during the setup. My guess there are slight differences in the newly shipped 35B image, compared to the 35B TOT file.

Afterwards, followed the OP instructions and viola' my favorite ROM is up and running on another VS985. How many other LG phones can do that?!!
[Verizon LG G3] roirraW "edor" ehT:
What 35B TOT? Where did you find that? Do you mean KDZ? The 10B TOT is the only TOT we have.

Also I don't understand what you mean about a difference between the number of apps optimizing. If you were already on 35B, why would you flash 35B?

You were either likely on 46A or 47A when the phone arrived, or you flashed the 10B TOT, but there is more bloat nearly every single OTA versus the previous one.

Also, if you flashed the 10B TOT, you wouldn't have to follow these steps. So I'm confused, LOL, are you sure you flashed a TOT? After flashing the 10B TOT, all you'd have to do is root with the Stump app and flash TWRP with TWRP Manager.

Thanks for the update and glad it worked out easily enough for you, though.
[Verizon LG G3] b00ster23:
OK....for some clarification. KDZ not TOT.... Sorry for the miscommunication. So I didn't look at which version I was on to start. I did TRY to downgrade using the correct .dll files from XDA. Once again got the LAF partition error message and KS error. So yes, probably whatever version I was on before while it was optimizing apps was different from the 35B KDZ. Makes sense.... :)
[Verizon LG G3] roirraW "edor" ehT:
Okay, thanks for the clarification! Cheers mate.
[Verizon LG G3] JustAnotherUser69245:
"You will HAVE to flash another ROM from TWRP, or use LG Flash Tool 2014 to flash any KDZ once you reboot from this process, since this doesn't include a bump'd kernel for whichever stock ROM you're currently running."

hello sir its me again

does this mean i wont be able to restart my phone without like flashing a rom or kdz

sorry for loads of questions
[Verizon LG G3] roirraW "edor" ehT:
Hello!

Yes, if you use this method. Kingroot isn't a permanant root anyway, plus the app is very untrustworthy. If you're, for instance, running 47A stock before doing this method, you could probably get away with flashing the 35B bootstack and then dirty flashing [MENTION=2941286]xdabbeb[/MENTION] 's stock 47A firmware (and optional debloat zips) if you don't want to go through the effort of having to restore your apps and settings right now.
[Verizon LG G3] JustAnotherUser69245:
so i would have to do this and then flash 35b and then flash [MENTION=2941286]xdabbeb[/MENTION] 's stock 47A firmware ?

im sorry im not really getting this ):
[Verizon LG G3] roirraW "edor" ehT:
The 35B bootstack, yes, and yes to his firmware. You do have it. :)

As I noted in the OP, I always recommend the different method of flashing the 10B TOT, then rooting with the Stump app and using TWRP Manager from the Play Store to install TWRP. This method is more of a last ditch effort for those who just couldn't get the TOT method to work no matter what they tried.

If you've read through the thread some you'll have noticed that this has gone wrong for many people, although it's worked perfectly the 2-3 times I've tested it myself. If anything goes wrong, flashing the 10B TOT would be the best way out of it, anyway, so it's good to be familiar with it.
[Verizon LG G3] JustAnotherUser69245:
well thank you very much for the help

but i used [MENTION=4482613]someguyatx[/MENTION] guide and i got 46a root thank you very much once again
[Verizon LG G3] roirraW "edor" ehT:
You're welcome.
[Verizon LG G3] :
[MENTION=2560614]roirraW "edor" ehT[/MENTION] YOU SIR...are awesome. Thanks for posting this. I saved a lot of time because of this. The instructions are clear and everything worked flawlessly - including the debloat scripts too.

Great work bro & thanks again ;)
[Verizon LG G3] roirraW "edor" ehT:
*blush* THANKS! YOU'RE WELCOME! I'm very happy to hear that, especially since some people had trouble where they got bricked trying to follow these instructions.

I needed that. :D

Edit: I've wondered if some people aren't scrolling all the way down in the code box when they copy/paste (if they're not using the text file I attached). Just speculation, though.
[Verizon LG G3] :
Yeah, I wondered that too. I don't think you can make the instructions much clearer, really. Maybe some users get a little nervous for fear of the unfortunate brick - so nervous that they skip/repeat/mess up a step? Tough to say when you're not there with them to watch what they are doing. I know you feel bad for them(me too), but I wouldn't put it on your own shoulders....just user error, unfortunately.

Thanks again! :highfive:
[Verizon LG G3] gregory97:
do you know any rom that works on this phone to install after this method?
[Verizon LG G3] roirraW "edor" ehT:
Any ROM that's made for the VS985 works. As normal with any ROM flash on this phone, flash the appropriate Bootstack after flashing the ROM. I highly recommend either [MENTION=2941286]xdabbeb[/MENTION] 's VS985 v2.0 ROM or his stock 47A firmware.

All the ROMs in the Development and Original Development, for example. Also any ROMs that are in the non-variant-specific G3 sections as long as they mention they work with the VS985.
[Verizon LG G3] roirraW "edor" ehT:
I was told by someone that I should post this somewhere and since anyone using TapaTalk all the time won't see this in my signature, here's goes:
[Verizon LG G3] vipulkarkar:
Need help.

Read all steps, all posts and replies.

Followed all the steps and pasted commands from text file.

Was successful and while I was comparing the output of terminal with screenshot in OP.

Phone suddenly went blank.

Now no led, not booting, no download mode working.

Can someone help me how to recover from the brick. :eek::crying:
[Verizon LG G3] roirraW "edor" ehT:
Thanks for the detailed information about what steps you had taken to get to the point you're at now.

Even though it doesn't help figure out why it happened, it's still good to know to compare notes when others have trouble.

I have no clue why that happened.

Does your phone show up as QHSUSB_BULK 9008 I think in the Ports or Modem section of Windows' Device Manager? If so, Google QHSUSB and you'll find the way to recover, which will involve the 10B TOT.

Edit: I forgot, even if your screen stays blank, if you go through the motions it may actually be in Download mode. If it shows up as LGE in the Modem section of Device Manager, then it's in Download mode and I would flash the 10B TOT.
[Verizon LG G3] vipulkarkar:
Thank you [MENTION=2560614]roirraW "edor" ehT[/MENTION] for your patience and help.

I searched YouTube and Google for QHSUSB and found several methods and files.

Downloaded nearly 8 GB of files and collected 6 different tutorials to unbrick my LG G3, spent 9 hrs. (it's very hard to use this much data in India with limited speed but I needed my phone to start):(

Finally able to go through process and voila..:D:victory:

It's been alive and working with Kitkat now. :)

If you don't mind can you please share the method/link to update this kitkat to MM (Resurrection remix). Brief steps would also do.

I'm asking for help as I don't want my phone to be dead. :rolleyes:

Once again, Thanks a lot.:good::angel:
[Verizon LG G3] roirraW "edor" ehT:
You're welcome!

I'm curious since you didn't specifically mention. Was your phone showing up as QHSUSB_BULK in Device Manager? Glad you got it solved.

You say KitKat but I want to make sure you're specifically still on 10B KitKat (not 11C or 12B). If so, use the Stump app to root 10B, use TWRP Manager from the Play Store to put TWRP on, wipe Cache, Dalvik/ART and Data, flash the ROM you want, then the appropriate Bootstack. I don't use non-stock ROMs but I assume the right Bootstack for a non-stock Marshmallow ROM is the same as the Bootstack necessary for a stock Marshmallow ROM, which is 35B.

Rooting becomes more complicated at least on 12B and above (not sure about 11C), and putting TWRP on anything higher than 12B gets harder too.

If you ever flash another ROM, always flash the right Bootstack after flashing the ROM. And I do mean after, for a reason (I've told so many people so many times and so many places I don't recall if you're one of the ones who I've told). There's a reason I say to flash it after. If you restore a TWRP Backup of any ROM, always flash the appropriate Bootstack then too.

12B Bootstack for KitKat

24B Bootstack for Lollipop 5.0.x

35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0