yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] rmcooperjr:
You're probably right. I appreciate the confirmation.

Good luck with the rest of the development!
[Android Q&A, Help & Troubleshooting] LupusGallus:
For those that go back to KitKat might notice that Verizon will force update on your device and constantly eat at your bandwidth. Here's a fix:

Make a copy of your build.prop! Save it on your external SD.

Then edit the build.prop text file and change anything that says VS880(10B/11B/12A) to VS88024A. This SHOULD stop the system upstate from happening since it tricks it in to thinking it is the current build. You shouldn't get any more hastle from it again. Be sure to replace it with the old build.prop before downgrading/full unroot to upgrade to Lollipop if you so choose.
[Android Q&A, Help & Troubleshooting] Kraigkent:
I believe I got mine from here: devtester.ro/projects/lg-firmwares/download.php?page=3

You'll want to search the page for vs88012a. Otherwise it could take awhile to find it.
[Android Q&A, Help & Troubleshooting] straitjacket525:
Help Please

I'm in the same boat as this guy, but cant buy a replacement. LG G Vista AT&T had kitkat before its brick status. no recovry or dl mode.

it was showing up as QHSUSB_BULK buut i have since installed my lg drivers and now it appears as LGE AndroidNet USB Serial Port (COM41)

I looked through that thread but i don't see anything pertaining to my device. any help greatly appreciated
[Android Q&A, Help & Troubleshooting] bkman08:
Have you tried getting into download mode since drivers installed?
[Android Q&A, Help & Troubleshooting] bobdamnit:
You wouldn't see anything in that thread. Like I said, use it as a guideline to know what you did to your device and how we MIGHT be able to fix it. You are now in uncharted territory for this device and now get to be the lucky one to try and fix it without permanently bricking it.

First, if you have installed a custom recovery, this makes it harder. Basically all we really need is to flash aboot, boot, laf, and recovery and then we can use Flash Tool 2014 to fix it, but having a custom recovery means you don't have download mode. And as of now, I'm unsure how to restore it to a device that basically has no partitions and need them made before they can be flashed. (This is the state of the device before it ever received partitions by the manufacturer.)

That you see it on COM41 is good news. That means there's a diag COM port open also. I'll bet download mode (or possibly fastboot) works on your device and it can be fixed relatively quickly.
[Android Q&A, Help & Troubleshooting] bobdamnit:
Verizon hasn't forced any update on me. I've checked with a root browser where the download goes and it hasn't even attempted to download any update.

I haven't noticed any abnormal data usage either. I have 10Gb/month, and my data usage has stayed pretty consistent with my previous months data usage. (It's my only internet source, so I use around 8-9Gb/month.) Besides, once it downloaded the update (around 800Mb for OTA update) you would see bandwidth usage drop to normal usage.

While that may indeed stop updates, from what I've seen, updates don't happen until you first check for an update and accept to download the update. After which it will nag you every time you unlock your device to access the home screen. As long as you never check update status or actually check for updates, it will not and should not ever download or notify you of an update.

Your mileage may vary, I guess. I downgraded from 23A to 10B so if you downgraded to anything else, your experience may be different.
[Android Q&A, Help & Troubleshooting] straitjacket525:
I have tried to enter download mode but no dice. It used to have a custom recovery, before the brick. It does show up (COM41) though and the flash tool can see it and communicate with it. Any advice?

Thanks for helping me out here.
[Android Q&A, Help & Troubleshooting] bobdamnit:
Do you have ADB/Fastboot installed and paths set properly? If you have a custom recovery we might be able to get fastboot mode to work and flash the required partitions to get you back up and going.

Basically remove the battery, reinsert the battery, hold volume up, and plug it into a computer. It should boot, maybe to a blank screen. At that point, issue the command

in a Command Prompt/Terminal and verify your device registers and is displayed. If it is, you got damn lucky.
[Android Q&A, Help & Troubleshooting] straitjacket525:
Of course that would be too simple! lol It does stay as a black screen though, no sign of booting other than that the COM port shows up in my device manager, and a Removable disk containing two directories image and verinfo. Windows says the size of said drive is 63.9mb.

Unfortunately no fastboot doesn't see the phone
[Android Q&A, Help & Troubleshooting] bobdamnit:
Damn. Can't catch a break, can we?

I'm going to bed. I have a vehicle I need to get pictures of and get online for sale and a yard to mow. (If the rain holds off) Afterwords, I have all day to dedicate to this until around 6pm EST. So say from 1pm to 6pm EST.

I need some info. What version were you on when this happened, and exactly what did you do to cause it? What version were you trying to downgrade to? VS880? Do you know how to disable driver verification in Windows XP/Vista/7/8/8.1/10? Are you willing to install the Qualcomm drivers after disabling verification? Are you aware that I take no responsibility for the advise I give, whether it is good or bad advise, and the result of said advise? Exactly what did you do in Flash Tool 2014? Emergency CSE flash?

Please be patient. I'm very scatterbrained and will have multiple projects going at the same time. Most pertain now towards unbricking the VS880 from trying to downgrade, as this is the second report of a bricked device while trying to downgrade.

Also, be aware that I have never seen a device in this state. I'm almost positive that until last night, a G Vista has NEVER been in this state. So we need to figure out a partition map and exactly how we are supposed to flash said partitions. (This is where that thread I linked earlier comes in play! It's a guideline to flashing LG partitions while in a bulk state.) I'm hoping that between you and the previous user we can figure out exactly what happened and prevent it from happening to others, and fix your devices.

Until then, and I cannot stress this enough: DO NOT ATTEMPT TO DOWNGRADE YOUR VS880 TO ANY VERSION OF 4.4.2! There is now a serious potential to brick your device with no known workaround! You have now been warned, and I cannot guarantee that I can unbrick it. I will sure try my hardest, but anything I try may make things worse. It would sure help if I had a device in this state. :(
[Android Q&A, Help & Troubleshooting] straitjacket525:
It was KitKat, it was quite a while ago (like right when the lollipop update rolled out) I believe i was trying to get back to stock without root or custom recovery so i could update to lollipop, and somehow i ended up with a brick. Like I said it was a while ago so I'm a bit fuzzy.

I was just trying to get to stock. d631 AT&T variant

Yes I can do that, and no worries man, it's not like the phone is gonna be any less useful if things go awry lol

I tried to follow this guide

http://xdaforums.com/showpost.php?p=63433138&postcount=806

but it failed to install, but it did let me know that flash tool can communicate with it in some way

I'm in no rush, I just appreciate the help, and all the work you are doing.

but I think we may be mixed up I have a d631 not vs880

Uncharted Territory! Woo! Well my device is up for any testing purposes.
[Android Q&A, Help & Troubleshooting] bkman08:
Your issue is that you tried to go to stock with custom recovery. Never ever ever ever flash anything but a zip in custom recovery. Always use fastboot for partitions. Your problem is probably because you didn't flash back laf partition and stock recovery before taking the update. HOWEVER the fact that your phone responds is a good sign that it's not an unrepairable brick

Edit: I see you used my guide to try and flash. Now we know you need complete stock partitions (as I thought you would) updating now.

Edit 2: derp me I just realised... Theres no way my guide could have worked because in order to have custom recovery you need to get rid of laf... Didn't that get rid of download mode and assure fastboot?
[Android Q&A, Help & Troubleshooting] bobdamnit:
Yes, it does get rid of download mode and default to fastboot. I'm in the process of stripping the D631 TOT for the laf image now, so we can prevent that from happening. I'll provide the link, would you please update your guide with info on how to reinstall the laf image and obtain download mode back? I can provide info on how to do that if necessary.

Any time your going to use an official method to return to stock, all stock partitions are required. Until now, we've not had a TOT file to get your laf partition and obtain download mode again to return to anywhere near stock. It hasn't been needed until now because we never had the TOT. Its a roundy-round. But now that we have it, we can unbrick a D631 almost exactly like we can a VS880.

[MENTION=6859580]straitjacket525[/MENTION] are you comfortable in Linux? Mainly Ubuntu? I need you to plug your phone into a Ubuntu machine (live or installed, not a virtual machine!) and run a few commands. Once we figure out where your phone mounts, lets see if the partitions are actually still there but blank. If thats the case, its a few simple "dd" write commands to get you back up and running now that I have your partitions.
[Android Q&A, Help & Troubleshooting] bkman08:
I can if I'm provided information on how to do so. I have yet to do that with an LG device seeing as this is my first one and after what happened after rooting and toying around with different apps, I don't know if I will take the chance again lol. All phones I have had before had fastboot already available.

Edit: [MENTION=4427107]bobdamnit[/MENTION] are you talking to me or strait about ubuntu?
[Android Q&A, Help & Troubleshooting] bobdamnit:
Info will definitely be provided then. We need as many people comfortable with this as possible. I'll try and make it as Windows friendly as possible, however we may be required to install extra 3rd party software to make it possible. We're going to require Linux of any kind, simply because its easier. I suggest VirtualBox because its free, and DamnSmallLinux or Puppy Linux because they're tiny. Or just download either and run it from a flash drive.

But its a fairly simple process. Copy a command into your terminal after placing the laf.img file in the proper place.

Edit: Talking to strait about Ubuntu. I'm going to need to know whether his partitions are still there and blank, or if they're totally gone. I can fix one, not so sure on the other.
[Android Q&A, Help & Troubleshooting] bkman08:
Right got it. Hopefully partitions are still there.
[Android Q&A, Help & Troubleshooting] straitjacket525:
yes I'm no stranger to Ubuntu

just tell me what commands I need to run.

again thank you man!
[Android Q&A, Help & Troubleshooting] straitjacket525:
Will 14.04 LTS suffice? I'm running it from a flash drive on a 32bit PC. In addition to my Phone I also have a keyboard and the flash drive this is running from plugged in.

This Is what I get from that command.

with that command should I input it exactly as you have it written? or do I need to tack on something to the end of sdb? anyway here is what I get from This command
[Android Q&A, Help & Troubleshooting] bobdamnit:
For now you only care about the aboot partition, which for you is sdb6.

Here is the aboot.img file that we will push to the aboot partition: https://mega.nz/#!qAtzzKqY!T1fM59llB-KrQLv91czCXYaWTgwuum9EvvNGTAbH5OQ

Save this file on the desktop. Open a terminal and cd to the desktop.

Obtain root privledges in terminal:

sudo -i

Type the password.

The next command depends on how your machine is setup. So what I suggest is doing the following: Type the first part of the command, then drag the aboot.img file into the terminal to inpiut the proper path and then finish typing the rest of the command.

So it will look like this when done:

dd if=/path/to/file/aboot.img of=/dev/sdb6

Alternatively, if you know the path to where the file is located, you can modify the above command and copy and paste it in.

Reboot your phone. It should at least attempt to boot and it might even possibly boot fully. After this, use the above post by me directed at bkman08 to reinstall the laf partition and then follow his guide to use the TOT file to go back to stock. Then, update if you would like.
[Android Q&A, Help & Troubleshooting] straitjacket525:
I pushed the file to the aboot partition but it doesn't try to boot at all, it also has switched mounts from sdb to sdc but it still says that it successfully pushes it to the device. I was thinking maybe the battery is to dead to try t boot so it's on the charger now.

Here is my screenshot

I also pushed laf.img to the laf partition (sdc15) but it still doesn't boot. I don't meet any resistance in pushing these .img to the device as they all say successful.

How would I go about getting all these .img files from the ToT? I have the ToT on my hdd
[Android Q&A, Help & Troubleshooting] bobdamnit:
I'll be honest with you. I don't wanna leave you hanging all night, but I have been drinking and my rule is not to work with technology while buzzed. People tend to get "liquid courage" and FUBAR their devices, and as its not mine, I'd rather not give you retarded advise.

I really did expect you to be able unbrick it from this. Are you sure you don't have download mode after flashing the laf partition? Have you unplugged the device, rebooted to Windows and while holding volume up, plugged it back in? That would force a download boot.

I can give you the tools and a fairly straightforward guide to decompiling a TOT/KDZ. It isn't difficult, but be aware that all partitions are in "bin" format and must be renamed with the "img" format. A simple Windows file explorer rename usually does it.

I usually like to type out my thoughts very much like a diary because its how I was taught to remember things (ADHD) so let me thump this out overnight and get back to you tomorrow. 21 beer bravery might just prevail tonight. ;) (This is also why my posts are overly detailed and long winded...)

Edit for beer!:

Let's just flash all the partitions. We will basically be manually flashing a TOT with DD commands. Only the necessary partitions require flashing, and this should be the same instructions for users in a worse state. Having your partition map helps, because I now know which are prudent and where they are located on the device. IDGAF how we get to a bootable/download state, let's just friggin get there. It can't get much more bricked eh?
[Android Q&A, Help & Troubleshooting] straitjacket525:
I haven't tried to enter download mode while connecting it to windows since we have pushed the aboot and laf partitions but I'll give it a shot and report back

edit:

I did try but alas no download mode, in fact the only time I can get anything on the screen is if i plug the phone in without the battery, then it shows the no battery indicator on the screen. otherwise pitch blackness

That would be awesome! Thank you!

Absolutely! It can only get better from here! So the plan is to use dd commands to flash the whole shebang? sounds great! We can get started tomorrow, enjoy your night bud.

Hooray Beer!!
[Android Q&A, Help & Troubleshooting] bobdamnit:
Not the whole shebang, but only whats necessary. I'm not sure what a lot of those partitions are for or what they do so I'm leaving out those. I'm only doing the ones that *should* get you back to a fixable state.

Bear with me. My heads pounding pretty hard. Beer was great last night but it sure sucks this morning. :(

Ok, first, here is the utility I use to strip down a TOT/KDZ. I'll run through the TOT process with pictures for you. KDZ users, the process is almost identical so feel free to use this if you need to. Go get the KDZ/TOT extractor from here: http://xdaforums.com/showthread.php?t=2600575 and save it in a folder on your desktop named "TOT Extractor".

Open that folder and make a new folder called "Extracted TOT". Run "WindowsLGFirmwareExtract.exe" as administrator.

In the firmware extractor, point it to your KDZ/TOT file and your working folder.

You will see it load the TOT/KDZ in the middle window. When ready, push the button!

Once completed, all those bin files will be extracted to your working folder. Open that folder and start renaming EVERYTHING from "bin" to "img". In other words, "aboot.bin" will become "aboot.img". Do that for every file in there.

Now, go back to my previous post where I showed you how to find your phone in Ubuntu and flash the partition. Basically, use that as a guide to flash the following partitions:

-sbl1

-aboot

-laf

-recovery

-tz

-rpm

-boot

From everything I've read, those are the required partitions needed to boot to download mode. If this doesn't work, we're going to at least try and get you custom recovery and fastboot because then we can fastboot flash images MUCH easier.
[Android Q&A, Help & Troubleshooting] rueta1:
Anybody tried flashing the rooted vs88023a.zip yet? Still can't seem to get it to work.
[Android Q&A, Help & Troubleshooting] bobdamnit:
No. I've been busy trying to get strait unbricked. Also, I still haven't figured out a way to nandroid as the only recovery we have will only nandroid to the internal SD card and there just isnt enough space. So I might just give it a go and if it fails, reinstall the laf partition and KDZ back to 10b.

In fact, thats just what I'm going to do. Wish me luck.
[Android Q&A, Help & Troubleshooting] straitjacket525:
I successfully pushed all of the aforementioned img files to the phones correct partioins but i still get no response, but now i think its actually charging so I'll report back after its had a charge. (it wouldnt charge the battery yesterday.)

edit: no sooner than i posted this it quit trying to charge and is still recognized by ubuntu as all those multiple drives
[Android Q&A, Help & Troubleshooting] bobdamnit:
I didn't really expect a response. I really didn't expect it to get past the LG logo/blank screen. But it *should* have download mode enabled now, which means you *should* be able use the TOT. Try removing the battery, putting it back in, holding volume up, and plugging it into a Windows machine just for the hell of it.

[MENTION=5343021]bkman08[/MENTION] I am populating Android Forums G Vista All Things Root section with guides/threads dedicated for the G Vista, as they have an actual sub-forum for the device. It will be MUCH easier to keep guides from getting buried in multiple useless posts/pages. Can you please update your TOT guide and post a guide over on the Android Forums website? Or, can I post it and give credits to you?
[Android Q&A, Help & Troubleshooting] bkman08:
You can post and give credit. I just have too much school stuff going on for tonight and tomorrow and I think the sooner the guides the better. I can do it tomorrow sometime but that would be the earliest
[Android Q&A, Help & Troubleshooting] straitjacket525:
No go, regardless of how i try to connect this phone to a windows pc it comes up as the COM41 port and a removable disk.

I tried exactly as you stated for download mode, I even left the battery out for a minute, but same result.

In this state the LG flash tool sees it and tries to install the ToT but it fails with

PID:NULL

IMEI:NULL

Model:

DLL:D631

BIN:LGD631AT-01-V10B-310-410-JUL-13-2014+0

SWV:

SWOV:

Model Information Check Fail

00000000

Factory Model Check ERROR!!

Download FAIL!! (0sec)
[Android Q&A, Help & Troubleshooting] bobdamnit:
Ok, open a command prompt and see if Fastboot sees it:

fastboot devices
[Android Q&A, Help & Troubleshooting] straitjacket525:
fastboot does not see it
[Android Q&A, Help & Troubleshooting] bobdamnit:
Alright then, lets try with a custom recovery. This is my last idea. If this doesn't work, I'm sorry. Its past the point of me being able to fix it.

Do the same thing in Ubuntu, however only flash these partitions:

1- sbl1.img

2- aboot.img

3- rpm.img

4- tz.img

5- recovery

However, instead of flashing the recovery image file from the TOT, flash the following custom recovery to the recovery partition: https://www.dropbox.com/s/ytka69n3997hr43/vs880_cwm_recovery.img?dl=0

Now, zero the laf partition:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf

Once you get that done, pull the battery and reinsert it. Then hold volume down and power at the same time. It should boot to a menu with the following options:

"Continue Power up"

"Safe mode"

"Factory data reset"

"Wipe cache"

"Power down"

Select "Factory data reset", then select yes when it asks if your sure. It will go to a black screen that says "Factory Reset Processing", then it should boot to PhilZ Touch 6. It wont actually factory reset anything. (Not that we're worried about that.)

If for some reason you can't get this far, there's nothing else I can do. But if you do manage to boot into PhilZ Touch recovery, you can now use fastboot commands to flash images. So within PhilZ recovery, select "Reboot system now". AS SOON AS YOU TOUCH IT, START HOLDING VOLUME UP! It should boot to a version of Download mode that says "Fastboot processing commands" somewhere near the bottom of the text.

Fire up a command prompt in Windows and issue the following to unlock the bootloader:

fastboot oem unlock

Now since fastboot commands now work, perform the following:

fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase dbi
fastboot flash dbi dbi.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase misc
fastboot flash misc misc.img
fastboot erase modem
fastboot flash modem modem.img
fastboot erase persist
fastboot flash persist persist.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase rpm
fastboot flash rpm rpm.img
fastboot erase sbl1
fastboot flash sbl1 sbl1.img
fastboot erase tz
fastboot flash tz tz.img

fastboot shtudown

but substitute all the img files for the ones from your TOT file.

Your phone will shut down. Hold power up and plug your phone back into your Windows machine. It will boot to normal Download mode at this point. You can now use the TOT/DLL file to go back to stock and a normal booting state.

If this fails, I am out of ideas and no longer am able to help you. :(

[MENTION=6918437]rueta1[/MENTION]

The 23A zip doesn't boot for me. It stays at the boot logo. I'm looking into it now.

The nandroid backup doesn't boot for me either.
[Android Q&A, Help & Troubleshooting] straitjacket525:
Well I suppose she's dead, after following that guide I get no recovery, it doesn't appear to linux and on windows it now comes up as qhsusb_bulk. no signs of life other than that. Oh well, Thanks for your time man!