yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] MrGunBest:
Just try, that cost nothing :laugh:
[Android Q&A, Help & Troubleshooting] D33PTHAWTE:
Agreed, but I haven't accepted the OTA because I was under the impression it couldn't be rooted.
[Android Q&A, Help & Troubleshooting] bkman08:
A few pages back I have showed that I have rooted 5.0.2 with kingroot. Verizon users it doesn't work because you have 5.1.1 which hasn't been rootable yet without actually manipulating system access yourself
[Android Q&A, Help & Troubleshooting] classic757:
I have the Verizon VS880 that was on 5.1.1 when I bought it and you are right, Kingroot (at least the 12-30-15 version) does not root it.

There is a new version of Kingroot out (1-5-16) but I have not tried it yet.
[Android Q&A, Help & Troubleshooting] bkman08:
It says it roots 5.1 but doesn't specify 5.1.1 or just 5.1
[Android Q&A, Help & Troubleshooting] classic757:
Yeah, I had an LG Transpyre on 5.1.1 and Kingroot rooted it, but for some reason it won't root the G Vista.

Maybe the new version will but I don't want to try it because if it does not work then my software status will say "modified" and yet with no root applied and I don't want to have to go through the whole LG Flashtool thing again to return my phone software status to official.
[Android Q&A, Help & Troubleshooting] ThumbDriveCorps:
I just rooted my AT&T LG G Vista D631 on firmware 5.0.2 using "One-Click Root"
[Android Q&A, Help & Troubleshooting] A Christian Guy:
Thanks but I'm trying to update to 5.0.2 I'm on kitkat 4.4.2 anyways and how to update
[Android Q&A, Help & Troubleshooting] ThumbDriveCorps:
This is what AT&T Tech Support told me to do... Use the UnRoot option in SuperUser and then reboot your device.

Wait around 2 hours and you should get a push notification for the update.

If you do not get the push notification. Dial 611 and talk to tech support saying you need them to push the update to your device using their service where they remote connect to your device and push the 5.0.2 update to your phone from their end.
[Android Q&A, Help & Troubleshooting] A Christian Guy:
Okay thanks I try to do that
[Android Q&A, Help & Troubleshooting] inmydream316:
really? i tried one click root with mine (5.02) and it doesnt get rooted.

it processed 100% and completed but i dont get any root.

I am going to try kingroot app
[Android Q&A, Help & Troubleshooting] beaverslayer:
If you were rooted on 4.4.2 that ain't going to work. It'll push the update and then fail during the install. I've been there and done that. Just download the ToT found posted a few pages back and follow the instructions posted a while back and you can be updated. When you remove root with superuser there are still traces of root that can't be undone without flashing the ToT and. Dll files. It'll take the over the air after that.
[Android Q&A, Help & Troubleshooting] andreshuerta428:
I have a question about this, i just flased the TOT file using LgFlashTool and i do not get the OTA, is there anything I'm missing here???
[Android Q&A, Help & Troubleshooting] bkman08:
Wait for the update, as its not just going to show up right after you restored.
[Android Q&A, Help & Troubleshooting] andreshuerta428:
It's been like 5 days.

---------- Post added at 01:59 AM ---------- Previous post was at 01:58 AM ----------

........actually 4
[Android Q&A, Help & Troubleshooting] beaverslayer:
I had an LG tablet that wouldn't show it had an update. I finally when to the AT&T webpage and chatted with an AT&T representative and they put in a service ticket and had the update pushed to my phone. Not sure why but for some reason some devices get blocked. It took about 3 days before the update was pushed, but it successfully installed once it did.
[Android Q&A, Help & Troubleshooting] jbird6143:
I think once you try to update it and it fails, it tries again 45 days later. I think there is a way to reset this timer though.
[Android Q&A, Help & Troubleshooting] gatawa:
yes there is a way to reset timer, all you have to do is goto your apps in settings and check for google services framework under all apps, clear the data and change your date to next day that is all check for update again.
[Android Q&A, Help & Troubleshooting] allmylightersareempty:
mine does that exactly too. I'm just trying to downgrade to get around the Google reset protection. anybody know how to do that on this model?

---------- Post added at 03:02 AM ---------- Previous post was at 02:58 AM ----------

mines does exactly the same thing
[Android Q&A, Help & Troubleshooting] LittleHelp12:
...

I have an issue here.

I have the vista verizon vs880 .

I am fine with all the steps except for "apply update from external SD card"

It's not listed in my reboot. I believe I know why but cannot figure out a solution.

The only way I am able to copy and paste the Vista update folder from my desktop to the sd root is if i format with the sd still in my phone using the erase sd disk under storage. If I format using minitool to ext 2 or 4 about half way through the file transfer from my desktop to sd disk it gets stuck and says this device has either stopped responding or some crap and freezes until i unplug the phone. The only time I can transfer the file from my desktop to my sd disk is when I format to FAT or fat32. But then obviously the recovery does not read the sd disk or give an option to update.

Any suggestions?
[Android Q&A, Help & Troubleshooting] TripFX:
To copy from pc to sdcard use either usb cable or via wifi with es file explorer. What you are doing is wrong never take the sdcard out and plug it directly into pc unless your pc is using linux.
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Root just succeeded for me in vs880 24A (Dec update) using kingroot 4.8
[Android Q&A, Help & Troubleshooting] mkfryan:
I would like to see confirmation of this, just tried VS880 on 24a 5.1.1 without any success.
[Android Q&A, Help & Troubleshooting] rmcooperjr:
Seems legit. I used Kingroot 4.8, root reported successful. So far I've installed AdAway and it's working. Also installed Root Checker and it shows root access.

VS880 5.1.1
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Been running it all day, stable and permanent. Even wiped phone to 23A and re upgraded to 24A and got root again
[Android Q&A, Help & Troubleshooting] mkfryan:
Awesome! Took 4 reboots and 7 times running kingroot before it finally went. Thanks for confirming that it worked.
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Now that I had root the next obvious step was to go after the bootloader. Rather then doing the EXTREMELY risky blasting LAF method I tried this one: http://xdaforums.com/android/development/tool-lg-g-vista-philz-recovery-07242015-t3164582

It however did not work. That was the official thread by the creator/compiler of this recovery for our devices. There is another img I have which I have not checked out yet. After I work up my nerves I'll try that one later.

The above method failed giving me a secure boot 1003 error. Download mode still worked and the device still booted thankfully.

Before I proceed further I'd like to request that someone who is on 24A (5.1.1 Dec update) and has attained root please send me a vanilla copy of you're recovery img

command that should do it from console with su:

if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img

That is of course assuming there is one there. I neglected to check it before I flashed it.
[Android Q&A, Help & Troubleshooting] classic757:
Thank you so much for confirming this. I had tried version 4.8 with no success but after reboot and retry it worked.

Also, if you want to replace kinguser with supersu please follow the instructions in this post( I can confirm it works) : http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

VS880 5.1.1 version 24A

---------- Post added at 10:00 AM ---------- Previous post was at 09:53 AM ----------

Thanks for the reboot info. I tried version 4.8 and at first it did not work but after reboot and retry it worked. :good:

VS880 5.1.1 version 24A
[Android Q&A, Help & Troubleshooting] CircusClown:
Recent prepaid Lg G Vista owner checking in. Purchased 2 weeks ago, software version was VS880PP01. Kingroot worked the first time, however I got a little over zealous and deleted a few too many apps. I believe it was a VZ app that I removed that soft bricked my phone. Phone would boot to a screen that said "authentication fail #9 modified". I had to use the LG flash tool to flash 23a. I re rooted the Phone and all is good. Question now is what is the difference between 23a and 24a, and does anyone have a 24a image?
[Android Q&A, Help & Troubleshooting] classic757:
Not sure if there are any major differences between 23A and 24A. My G Vista was on 23A when I bought it and I updated it to 24A and I don't see any difference. Probably some security updates in the 24A version. If you want to update to 24A just go to settings>system updates>check for new system update. If there is an update available it will let you know.

Rooted VS880 5.1.1 version 24A
[Android Q&A, Help & Troubleshooting] DaxxTrias:
24As is security patches. One example is it fixes some of the stagefright vulns
[Android Q&A, Help & Troubleshooting] classic757:
Kinda thought so.

Also, do you know if xposed will work on the VS880 5.1.1 ?
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Latest version of xposed says it needs to be flashed with custom recovery
[Android Q&A, Help & Troubleshooting] classic757:
Oh okay, thanks.

Would love to have a custom recovery image for this device. The G Vista is a solid mid-range device. Too bad we don't have much development going on with it. :(
[Android Q&A, Help & Troubleshooting] DaxxTrias:
I'm eager to begin working on this phone. I havent tried my hand at custom rom development since the froyo timeframe, however blasting my LAF doesnt seem smart to me.

In other news I've discovered I have dust or dirt underneath the screen. I have a screenguard (one of those thin plastic type covers that go on top of it without a bulky case) yet this dust is underneath the actual screen. Between the screen and the digitizer I guess.

I took the phone apart enough to replace the digitizer but I cant seem to disassemble the actual digitizer to clean out the dust grrr.

If it wasn't for the root, I'd probably put this phone up on ebay.
[Android Q&A, Help & Troubleshooting] classic757:
I hear you.

Oh, and is there a recovery for the G Vista on 5.1.1 available?
[Android Q&A, Help & Troubleshooting] DaxxTrias:
The recovery usually doesn't care about rom version. Phil's cwm recovery
[Android Q&A, Help & Troubleshooting] mkfryan:
I installed Philz, same version as I had used with kit kat, I received a secure boot violation when trying to boot to recovery, it would not load past that point. I had to pull the battery to be able to boot the phone.
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Which one did you use? I've been able to locate two different philz cwm .img's of varying size and checksum.

Earlier in this thread (probably 20 pages back) you shared a link for one which you can flash without blasting away your LAF. Is that the one you used? If so you're results mirror the ones I experienced two nights ago when I tried mimicing you're previous post to do the same thing.

I also have an .img that is different that I found that was said to be used for the LAF blast method.

In any event, if you did everything the same as you did back on kitkat and it worked before but wont work now I guess that disproves my previous statement lol.

Also, 23A or 24A?

Edit:

I found a post the other night for a user of the LG G3 or maybe G4, where he got the same error for doing the same thing. (Flashing a recovery image like us, just not the same image) And he was told it was due to the OEM Unlock option in the developer options. Once he ticked it he said his problem went away and the Secure Boot 1003 didn't occur anymore.

For us we don't have that option revealed in our dev options, so perhaps they forced it off and then hid it from the menu.
[Android Q&A, Help & Troubleshooting] classic757:
Do you have the links to the two different philz's recoveries?

And yeah, I found it kind of odd that we don't have the oem unlock in the developer options settings.
[Android Q&A, Help & Troubleshooting] mkfryan:
I used the same method that I posted before.

Would we be able to swap out the .Img to test?

I am on 24A.

Would we be able to get that option from a hidden or service menu?
[Android Q&A, Help & Troubleshooting] DaxxTrias:
The first one you can find by either finding my post a page or two ago where I linked to another thread on this forum, or 20 or so pages back for mfryan's older post.

The second one I found I have uploaded. Blasting your LAF though is EXTREMELY risky but I'm including the steps I received for it just incase any of you are daredevil enough to try it. Whether or not you can simply swap the images to test it I don't know. Consider that your own leap of faith.

https://mega.nz/#!3xs03SJY!Dd-Q8o-IVA2fQKefpQn6F5oLOBNMf2t3BNOWEi2kwNQ

edit:

Whether we can unlock the option or modify it without having it on the menu is something I've been researching. Generally speaking a menu such as the developer one is simply a GUI screen to alter an entry elsewhere. I checked the build.prop file and didn't locate it there so I am searching elsewhere.

My hope is that LG/Verizon forcibly hid the option from us, but they probably did not remove its functionality from the Android OS itself. If a GUI modifies a config file, and they only modified the GUI, perhaps the config is still there.
[Android Q&A, Help & Troubleshooting] mkfryan:
If we swap out the img and it does install the recovery theoretically if it doesn't work shouldn't it behave in the same manner? Just giving the secure boot 1003 error.
[Android Q&A, Help & Troubleshooting] DaxxTrias:
I can't answer that as I don't know. The flashing processes could be different.

The one you linked was built around using root/adb to overwrite a file.

The one I posted before it sounds like its designed to be used from fastboot flash.
[Android Q&A, Help & Troubleshooting] mkfryan:
Thanks for the input! What do you think would be the likelihood of it bricking based on how they each install if you attempt to swap them out? Or would it probably not even install?
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Well the concept is basically the same, even when flashing something its usually done by overwriting files. But until we can get into the image and make sure thats what its for I have no idea.

In other news I've discovered thanks to root we have 650mb free space in the /dev partition, and 850mb free in the /cache partition.

Its a real shame considering our cache doesn't actually goto the /cache directory. Got over a gb and a half of free space we can't normally access, yet with root.....

edit:

/mnt/obb and /mnt/asec also each have about 600mb of free space. The more I look around the more pissed I'm getting seeing all this wasted space. Android 5.1 allocates 5gb of space for itself, yet its only using about 2.5gb. It seems absurd, yet we'll likely need a custom rom to be able to fully utilize it. (Who knows what hacky functions have been written to use those free spaces every once in a blue moon)

edit2:

Well I fixed the secure boot 1003 error I was getting after flashing that recovery rom. I ripped the stock 23A recovery out of the kdz and stuck that in there. Idk if 24A included a newer version but I'll worry about that later. Now to test the second Philz img since I seem to have a working way backwards for this type of thing.

edit3:

I tested the second philz img which I uploaded and linked to here earlier now that I had a confirmed method of repairing a badly flashed recovery img. It also provided the wonderful 1003 boot error. In any event all I've really accomplished is to break my recovery 2x and then repair it 2x. Still remains to be seen if the recovery is different from 23A to 24A also.

It looks to me like we're either going to need a way around this error (whether by someone making us a working recovery, or us finding that oem unlock option) we're just gonna have to wait until some maverick is brave enough to try the LAF blasting method and seeing if fastboot works to flash the image.
[Android Q&A, Help & Troubleshooting] classic757:
Root is working very well and survives reboot.

Would love to have a custom recovery but at this point there really is no need for one. I mean, what can we do with a custom recovery?

There are no roms to flash or anything. Maybe install Xposed, which I guess would be nice.

Anyway, glad to have a working root, especially since there is basically no development for this phone.
[Android Q&A, Help & Troubleshooting] bobdamnit:
Ok, its been a very long time since I've been active here. I still own a VS880, however I quit using it for a while due to some issues the phone was having. I could only talk on the phone on speakerphone otherwise nobody could hear me (odd because they both use the same microphone?!), and it has an issue charging (Namely it didnt charge at all lol). I obtained a VS985 (G3) on Verizon that had the screen replaced and was given to me after an upgrade. Well, whoever replaced the screen did an awful job and broke the proximity sensor, power/volume buttons, and camera. I tore it apart and tried to fix it, but in the end I ended up junking it in a fit of rage. I'll admit, I was taking out some aggression after losing both my house to a fire and my longtime girlfriend from the stress and devastation of losing everything you own in one night. Hammer: 1 VS985: 0

Well, while I was using that junk G3, I sent my VS880 in to Verizon to have it insurance fixed. They literally just gave me a new one. MEID is different, it came in a new box, the whole shebang. So now I'm back to using this lovely device. Problem is, I've been out of the loop for a long time here. Last I knew, 5.1.1 wasn't rootable (or it was, with signal issues) and certain downgrade methods had to be used to get back to 10/11B to root. Is this no longer the case? Is blowing away the LAF partition still required for custom recovery? And, is PhilZ still the only recovery available?

Also, I still have most of the source for this phone. I saved it to MEGA while I was working on building CM 12 for this phone. Unfortunately, I wasn't saving anything to any type of cloud service, so I basically have to start from scratch and memory because literally all was lost in a fire. I'll admit, I'm a heavy pot smoker. I'm also old. My memory just isn't that great. But, I'm willing to give it a go again. No ETA's please. I have a life, and the phone works as it currently sits so this isn't a top priority. I'm still dealing with insurance, the fire department, a realtor, depression, and full time job.

Also, for future CM 12 updates, please move over to Android Forums. They've given us a proper subforum that I've populated with the most useful tutorials and files a while ago. I'll be creating a thread there for updates, Q&A, and support. If possible, please try and post any other guides and help you can there. (Seriously, I'm not plugging AF I promise. Its just so much easier to keep things organized with a

proper subforum

!

HINT HINT, XDA!!!

)

Thanks for the help guys!

Edit: I see Kingroot 4.8 does indeed root 24A. Awesome. I'll get it updated and rooted, then I'll post a tutorial to removing Kingroot in favor of SuperSu. At that point, I'm sure one can just backup the LAF, wipe it, and replace it with PhilZ for Xposed ;)
[Android Q&A, Help & Troubleshooting] DaxxTrias:
Glad to see you're alright bob, lots of problems notwithstanding. Sorry about the house and the gf :( (My brother just wrecked my brand new truck last month so I sort of know a bit of how you feel)

I've got 2 different philz recovery img's but they were from July of last year, and since mkfryan said he was able to simply overwrite 1 of them back on kitkat and have it work, but now it yields a secure boot 1003 error has me thinking lollipop has some sort of security feature blocking us (such as OEM unlock missing from our dev options?)

I've backed up the recovery and the LAF for my 24A but I've honestly been too scared to blast my LAF. If its blasted and then I get another secure boot 1003 hello $200 paper weight.

Also, I'm an experienced programmer in the C language (I specialize in CSharp, but have experience in C/PP) if you want to setup a repo (bitbucket perhaps?) we can collaborate on the rom once we get the recovery situation worked out. I used to live and breathe custom rom work back on my MotoG in the Froyo days and am eagerly looking forward to doing it again.
[Android Q&A, Help & Troubleshooting] bobdamnit:
I've already gotten the 24A KDZ and have it decompressed into a DZ which I then broke down into actual partitions. I have aboot, boot, laf, etc...

I've never had a problem blowing away the laf partition as long as you know the recovery you are going to install is going to work. I have one I know works, however the external SD card will not mount while in PhilZ. Not a deal breaker, but annoying. If you want, check mine against yours and see if one of them matches.

Link to my recovery: http://androidforums.com/threads/g-vista-unlock-bootloader-custom-recovery.961873/

Thats also a guide for the VS880 (made by me) for unlocking and blowing away the laf partition to enable fastboot. I can confirm that the recovery posted there does work if you waste the laf partition. I've done this already on mine and installed it on my VS880. Again, no extSD support, but as long as you do NOT wipe the internal SD you should be OK. I ran mine on this recovery for about a year and am currently running 11B that way with it.

A secure boot error can be fixed with the TOT/DLL file for your device and the legit version of LG Flash Tool. There is a TOT available for the D631 (I paid to acquire it lol) but never one for the VS880 because Verizon releases the KDZ for it. In this instance, if fastboot isnt working you are indeed screwed. You might be able to use Linux to mount the phone and manually "DD" the laf partition but you better know which partition is which before you even attempt it. (I've done exactly this on a Moto X that I bricked)

Also, 23A came with many security features. One was the added protection for downgrading. Another was disabling the "Send_Command.exe" file to pass certain fastboot commands (its how the G3 was rooted) and now apparently signature verification for signed files. We might want to think about "bumping" anything that needs flashed. (Recoveries, ROM's, etc...)

The last time I built a ROM was CM 7/7.1 for an LG Optimus M. Yeah, its been a while. And even then, I had a lot of help from PlayfulGod, BobZhome, and reppard. I did get CM 12 quite a ways along but never in what I consider a bootable state. (It booted, screen came on, did not accept touch input.) However, I don't exactly remember how I did it now.

I'm ok setting up a repo, but I've never actually done it. If you want, go for it. I'll definitely commit to it.
[Android Q&A, Help & Troubleshooting] classic757:
Good to see you back on the xda forum [MENTION=4427107]bobdamnit[/MENTION]

Hope to God everything is coming back together for you.

As for the VS880, it is a lovely phone. Sad there is virtually no development gong on for this phone.

BTW, I used super su me from the play store to remove and replace kingroot with supersu. There is also another method by Wolfdroid. Just google "replace kinguser with supersu" annd you will find it. As for a custom recovery, Philz is the only one available but I'm not sure it will work on 5.1.1 and you have to nuke the laf to install it. I'm not willing to try that.

Kingroot version 4.8 (2-3-16) rooted my g vista. Failed the first time. Rebooted and tried again with success.

Again, welcome back. :)