The 48A_03 KDZ is in the usual place - my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in this section.
It is downgradeable, but neither KingRoot v4.82 that worked with 47A, nor the latest v4.96 will root it yet. See post # 7 http://forum.xda-developers.com/showpost.php?p=68055444&postcount=7 below for details and caveat for newer VS985 variants with "K" in model or revision 2 PCB but the summary is the normal 10B TOT method still using the .DLL extracted from the 35B KDZ. Thanks to @swcunn via this post http://forum.xda-developers.com/showpost.php?p=68047533&postcount=1441 to make me aware and I downloaded the OTA files just to capture them even though they don't do us any good anymore to try to manually apply them (at least I haven't had any luck and it was the same for a bunch of others).
Still says Android 6.0 in the About screen. June 2016 security patch level.
Its 229.5 MB, has one less bloat app than 47A (Thanks to @DeanGibson who noticed that Amazon Music isn't on the VS985 any longer here http://forum.xda-developers.com/showpost.php?p=68064661&postcount=10), and is larger than all OTAs other than 12Bto23C, 24Bto35B and 35Bto46A.
I repeat again for anyone wondering: there's nothing we can do with the OTA files manually, I'll test rooting directly via KingRoot like 46A and 47A could. If it's possible to make a rooted ROM out of the new update, you'll have to give it some time as likely those more knowledgeable than myself would have to do the real work, and that's if they're willing, have time, and if they volunteer.
And also, for those who don't know, don't expect a KDZ to come out for at least a week if at all.
Thanks to @maximusmullivan for the hint that the update information was available on Verizon's site. LG's site still is at 46A. http://www.lg.com/us/support/product-help/CT10000027-1414534794596-software-updates
https://www.verizonwireless.com/support/lg-g3-update/
Software Version: VS98548A
Verizon Wireless is pleased to announce a new software update for your LG G3.
This update provides new options to recover your Lock PIN code, plus the latest Android™ security updates and bug fixes.
New backup PIN
A backup PIN is an additional method to access locked content, like Gallery pictures. Once you set-up a backup PIN, it can be used to access locked content.
You can still unlock device content with a pattern lock, but the option to reset the pattern using your Google account has been removed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Haven't tested yet. Thanks to @swcunn via this post http://forum.xda-developers.com/showpost.php?p=68047533&postcount=1441 to make me aware and I downloaded the OTA files just to capture them even though they don't do us any good any more to try to manually apply them (at least I haven't had any luck and it was the same for a bunch of others).
I have no idea what the new build # is, nor what version of Android for fact, although since N isn't final I'm sure it's just 6.0.1 at the most.
It's about 259 MB.
I repeat again for anyone wondering: there's nothing we can do with the OTA files manually, I haven't returned to 100% stock via TOT and KDZ yet to take the official OTA and see what it's made of, if it's downgradeable, rootable directly via KingRoot like 46A and 47A could, or anything. If it's possible to make a rooted ROM out of the new update, you'll have to give it some time as likely those more knowledgeable than myself would have to do the real work.
And also, for those who don't know, don't expect a KDZ to come out for at least a week if at all.
Click to expand...
Click to collapse
48A http://www.verizonwireless.com/support
maximusmullivan said:
48A [/QUOTE]
Thanks mate. Once I sear...www.verizonwireless.com/support/lg-g3-update/
Software Version: VS98548A
Verizon Wireless is pleased to announce a new software update for your LG G3.
This update provides new options to recover your Lock PIN code, plus the latest Android™ security updates and bug fixes.
New backup PIN
A backup PIN is an additional method to access locked content, like Gallery pictures. Once you set-up a backup PIN, it can be used to access locked content.
You can still unlock device content with a pattern lock, but the option to reset the pattern using your Google account has been removed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Wha!?
Warning/encouragement when trouble flashing TOT/KDZ
Let this be a warning and encouragement for whenever anyone has trouble flashing a TOT or KDZ on any LG device.
Last night I attempted to flash the 22B TOT for my VK810 LG G Pad 8.3 and then the 10B TOT for the VS985 LG G3. The VK810 was successful, the VS985, not so much and was indeed a huge amount of frustration. At this point I will admit I did something extremely stupid while the TOT was (as far as I know successfully) beginning to flash to the VS985, but I can't know for certain if it affected it since I was successful later as described below. I was even going so far as to try to force it into QHSUSB_BULK 9008 mode - I was unsuccessful doing so - either I was shorting the wrong pin since it's so tiny and all the light I could muster at 1 AM wasn't enough at least close by the PC where I had to connect the USB cable to, or the paper clip I was using wasn't making a good enough or any connection, or I just had dumb "luck" in hindsight and the Android dieties were looking after me.
Flashing the TOT on the VS985 was showing all sorts of communications errors even though for the VK810 it went off without a hitch. This is on a VERY new and VERY high end PC I just built a month ago, with Windows 10 x64. I've previously flashed TOTs on a different Windows 10 installation on an older PC I had built before. I was using the latest driver.
I suspected last night but I didn't feel like messing around anymore and didn't swap cables with another original LG OEM one. This morning I tried everything but with the other USB cable on a completely different PC I never flashed from before, using the latest drivers again and it succeeded the very first time. What a relief! I'll have to put the aluminum metal shield and all the screws back in later, but it's booted up and working 100% on 10B right now. The case I have holds it all together just fine. Now my plan is to flash the 47A KDZ and take the 48A OTA, try downgrading and if successful, do it all again and try Kingroot - probably the same version I had tried four months ago on 46A and 47A since I think I still have it. I'll probably try my manual partition downgrade method as well since I'll be in the ideal position to test it yet again.
Update: I was still able to flash the TOT on my VK810 successfully without effort on the first PC - the one that I had trouble flashing the TOT on my VS985, although I'm using a different cable - the one that I successfully flashed my VS985 with at work.
What the heck is going on with these duplicate posts when I try editing one of my existing posts!??? Weird.
The phone is done flashing the 10B TOT using the 35B .DLL coming from 100% stock 48A. It's booting now so at least with those with non-model "K" and/or non-revision 2 PCBs (Printed Circuit Boards) are in the clear for re-downgrading.
When I re-upgrade to 48A and try Kingroot, if it's successful the first thing I'll do is pull the partition images just in case a KDZ never comes (hopefully it will).
Neither KingRoot v4.82 that worked with 47A, nor the latest v4.96 will root it yet.
I'm back on my TWRP backed-up 47A and 35B Bootstack! WOOHOO!
Bye-bye app
roirraW "edor" ehT said:
... Its 229.5 MB, has one less bloat app than 47A (haven't checked which app...)
Click to expand...
Click to collapse
I think there were four Amazon apps that I had disabled, and now there are only three. "Amazon Music" is still on my VK815 tablets, but not on the VS985, so perhaps that was it???
DeanGibson said:
I think there were four Amazon apps that I had disabled, and now there are only three. "Amazon Music" is still on my VK815 tablets, but not on the VS985, so perhaps that was it???
Click to expand...
Click to collapse
Ah, thank you! By the way, I noticed in the OEM source code zip for the VK810 (I believe the 35A source), there was code for LG Backup. Huh!
Updated my fifth post. http://forum.xda-developers.com/showpost.php?p=68054128&postcount=5:
I was still able to flash the TOT on my VK810 successfully without effort on the first PC - the one that I had trouble flashing the TOT on my VS985, although I'm using a different cable - the one that I successfully flashed my VS985 with at work.
Is 48A 6.0.1 or still 6.0?
Sent from my LG-VS985 using Tapatalk
minhas729 said:
Is 48A 6.0.1 or still 6.0?
Click to expand...
Click to collapse
Still says Android 6.0 in the About screen. June 2016 security patch level. Added this info to the OP.
I'm not the best guy for info, but when I was on stock 6.0 Verizon to me there was update of which your talking about which was to be small changes to problems with battery life, the update was to be 6.0.1 as you know I'm no longer stock Mm, but that's what they told me when I hold a bootloop problem when going from 5.1 to 6.0,at that time they had to give me a new phone as I bootloop ed on upgrade.
Sent from my VS985 4G using Tapatalk
gweeto85 said:
Thanks for posting, I got the notification this morning for the ota update. I came to XDA first
I am running 47a with twrp and don't mind being a guinee pig. Just sayin'
Click to expand...
Click to collapse
You're welcome!
There's nothing to test, but thanks anyway. Until we either have a method to root 100% stock 48A, or the KDZ arrives, there's nothing to do. And then if we get either it would have to be modified to be nasty KingRoot free and have Bump'd kernel and systemless root. I haven't ever experienced extricating KingRoot from the system.img or bumping and implementing systemless root - it's not too likely I'll find the time to learn this anytime soon.
Edit: Downloaded the 48A_03 KDZ using the official phone Windows tool, uploading to Android File Host now - same place I have all the other KDZs and TOT available to download. Slow upload speed so might take a couple of hours.
Can't dd if system?
vs985 China user
andy_zhang said:
Can't dd if system?
Click to expand...
Click to collapse
If you're asking if we can use just the system partition alone (without upgrading the kernel, etc), I don't know. If you try before anyone else, let us know.
roirraW "edor" ehT said:
You're welcome!
There's nothing to test, but thanks anyway. Until we either have a method to root 100% stock 48A, or the KDZ arrives, there's nothing to do. And then if we get either it would have to be modified to be nasty KingRoot free and have Bump'd kernel and systemless root. I haven't ever experienced extricating KingRoot from the system.img or bumping and implementing systemless root - it's not too likely I'll find the time to learn this anytime soon.
Edit: Downloaded the 48A_03 KDZ using the official phone Windows tool, uploading to Android File Host now - same place I have all the other KDZs and TOT available to download. Slow upload speed so might take a couple of hours.
Click to expand...
Click to collapse
Don't forget to share link here when kdz is up.. Planing to go with that..
Right now i m on 47A xdabbeb with 35B BS
Which steps should i use..
And what if want to go to 10B for root again... Is it by using special.dll file via tot
Sent from my VS985 4G using Tapatalk
minhas729 said:
Don't forget to share link here when kdz is up.. Planing to go with that..
Right now i m on 47A xdabbeb with 35B BS
Which steps should i use..
And what if want to go to 10B for root again... Is it by using special.dll file via tot
Click to expand...
Click to collapse
The link is at the bottom of the first post of @annoyingduck's stickied return to stock thread in this section, I also have a link to that thread in my signature below. That's the thread for flashing KDZs so the instructions are there.
The second sentence of the first post of this thread confirms the downgrade method.
roirraW "edor" ehT said:
The link is at the bottom of the first post of @annoyingduck's stickied return to stock thread in this section, I also have a link to that thread in my signature below. That's the thread for flashing KDZs so the instructions are there.
The second sentence of the first post of this thread confirms the downgrade method.
Click to expand...
Click to collapse
I am very sorry, my screen of vs985 damage, I can't try.
vs985 China user
Related
*WARNING* - There have been at least two known hard bricks using this method. It has worked successfully for many people, including myself three times. However, with two hard bricks, this isn't something to go into without at least considering the possibility. The standard warning has always been in this thread (second paragraph), but consider yourself doubly warned. Now that we have root and TWRP on 5.0 stock, this method is all but obsolete. We're just waiting on the good devs to bring us superb Lollipop stock ROMs like SkyDragon by @HolyAngel and Jasmine by @hsbadr. Once those are out, this method should really only be used if you need "official" software on your phone. Or you can just wait for Verizon to push the actual OTA, which is probably technically safer than any custom flashing methods there are.
--------------------------------------------------------------------
**NOTE** - There are two stellar custom-stock ROMs here in the form of Jasmine v.5.0 and SkyDragon 3.0.0. There is no longer any need to use this method to upgrade to stock LP unless you just really need the software status to say "official". Download link & instructions at the following links:
SkyDragon G3 VS985 Edition Version 3.0.0
JasmineROM v5.0 Release [LP] [Stock] [Rooted] [Unmodified]
--------------------------------------------------------------------
Are you still here after reading that warning and looking at the great custom options? Read post # 148, then, if you really insist on being so daring as to try an obsolete method, I guess proceed on. Best of luck to you.
--------------------------------------------------------------------
For starters, this thread may be deemed unnecessary and/or redundant. If so, please accept my apologies and mods feel free to close the thread. This is an extension of this thread started by @annoyingduck. It's a start-to-finish way to flash 23A and keep all your apps. Rather than linking threads here, there and everywhere, I've compiled everything and put it all in one place, to try and keep down the number of questions in that thread (which is really supposed to be for devs to assist them in getting the info they need to make the wonderful stock ROMs we've all come to know and love). NONE of this information is original to me. I'm not that smart. All credit goes to the respective posters listed below.
Now, the usual disclaimer - I am not responsible if you brick your device by using any or all methods outlined below. They worked for me. They may or may not work for you. If you go down this path, you do so at your own risk and/or peril. Don't come crying to me in the unlikely event you can't figure it out or kill your phone!
Also, please take note right here right now, as this question will never be answered again by me in this thread. There is currently NO ROOT on 23A. Root will NOT be retained when you upgrade (in fact, it will be lost at the 12B KDZ step). Further, we do NOT know how to root stock Lollipop on Verizon at this point. So to answer your questions: NO, you will not have root on 23A at all, period, no matter what, until some smart dev is able to come up with a way to root it.
The good news is that you can downgrade back to 10B (the only root-able version) at any time and get back to rooted goodness and flashing rooted stock-KK or AOSP-Lollipop. I'm hopeful we'll get root eventually for stock Lollipop, but it's too soon for that.
First, you need to download several files. The first several have to do with KDZ'ing back to 10B, followed by 12B (you WILL LOSE DATA going back to 10B...back up everything!).
Things you will need:
Drivers from LG for the G3.
Two files from this download page - the 10B KDZ file (VS98510B_01.kdz) and the 23A update file (LG_VS985_12B-23A.dlpkgfile).
NEW 3/6/15 - The 23B (should be an OFFICIAL LP build) update is available here. Same as before, rename to .up and put it in the Software Update folder. Update from 12B stock.
The 12B KDZ file. (Alternate mirror.)
The LG Flash Tool 2014 (originally from this thread).
Now that you have those, we can move on to the directions. To KDZ back to 10B (followed by 12B after a few interim steps), you need to follow the procedure outlined here by annoyingduck. I'm quoting everything so it's all in one post, but linking back so those who made it get all the credit.
When flashing the 10B KDZ, you must use the "CSE Flash" option, because you're downgrading and getting rid of everything on your phone. You will lose ALL data, so copy your TiBu folder, your photos, files, etc. elsewhere first.
annoyingduck said:
-First remove any of the .tot flashing tools/programs that you may have already installed as they will conflict with the KDZ flashing tool.
-Download and install the latest LG drivers for your phone here (FYI I am linking the LG site directly instead of the file to ensure that you download the current up-to-date drivers): http://www.lg.com/us/support-mobile/lg-VS985-Metallic-Black
-Download the VS985 10b KDZ file from here: http://downloads.codefi.re/autoprime/LG/LG_G3/VS985 and thank @autoprime in whatever manner you deem fit.
-*New* Mirror for 10b.01 KDZ: https://mega.co.nz/#!7ERgXJbI!2KxATJt7q-HWvAPbTfVrT3wGuwPjWCw70N65MVlgfWg md5: d228ba692ef0c4704cba0b00fad8b8ce
-Download the LG Flash Tool 2014 from this thread here: http://forum.xda-developers.com/showthread.php?t=2797190 and be sure to thank @quangnhut123 for his efforts. Also read that thread a bit so you understand how to fully use the tool exactly, but I will outline the process below.
-Extract the .zip folder to wherever you wish to keep it (desktop, downloads, etc).
-Copy the 10b KDZ file (or whatever KDZ your flashing) into the LG Flash Tool folder
-Power off your phone completely, hold volume up, plug in the usb cable, wait for any drivers to load, and you should then be in Download Mode
-Run LGFlashTool2014.exe (you may need to run as administer as its not an installed program, rather an executed one from wherever you saved the folder).
-You may need to install Visual C++ Runtime Library. If so, refer to the LG Flash Tool thread for more info on obtaining that.
-Select CDMA as your type
-Select Diag as your phone mode
-Select your KDZ file that you copied or pasted into the folder
-Choose the option of CSE Flash (this is a full wipe, you will lose your data). Do not choose Normal Flash when performing a downgrade, nothing good will come from doing that!! Another screen will open, just leave everything the way it is.
-Click the Start button and yet another window will appear showing a language selection screen. Just leave everything the way it is as Korean and hit OK. Don't worry, the tool is already set to flash in English.
-Wait until the Flash is done 100% and unplug/reboot... and that's it
Click to expand...
Click to collapse
Ok, now that you're back to 10B, it's time to do some work there. You need to root your phone, install Titanium Backup and restore your backed up apps & their data. I prefer to use the IOroot method. So root, then install all your apps. After that, it's time to update to 12B. You're doing the same thing you did with 10B, except this time you are choosing "Normal Flash", not CSE flash, because you're upgrading. Once you've done that, you will be upgraded to 12B and will have lost root. Here is more from annoyingduck:
annoyingduck said:
-Restore apps, and select system data items you want restored (aka: call log, sms/mms messages, wifi access points, bluetooth pairings) via Titanium
-KDZ to 12b, but this time choose NORMAL flash. No bootloops because it's an upgrade
-Root is now lost, but atleast all your apps and data are already there
Click to expand...
Click to collapse
Now we're going to update to 23A using a method described here by justiz33.
justiz33 said:
Do not attempt unless you are sure of yourself and have a high percentage of battery left.
if you are on 12B and NONROOT, you can put the update on /storage/external_SD/SoftwareUpdate/23A.up (**hokie note - FYI, I had to put mine on the internal SD in a SoftwareUpdate folder for this to work; it wouldn't flash when on the external SD card. Don't forget to rename your update downloaded above to "23A.up")
then download and install Activity Launcher (**hokie note - Here's a play store link.)
then in Activity Launcher use the drop down to switch between ALL ACTIVITY.
scroll down to the bottom area and look for either 'Software Update' or com.lge.permission (**hokie note - Mine was titled a little differently, something like com.lge.fotaupdate.permission.)
click the dropdown and expand the list.
look for DmcEzUpdateStart and click it.
You should be on a black screen with FOTA UPDATE written, just sit on that screen and wait 3 min and it will then say 'Shutting Down'
It should reboot and start the update.
Click to expand...
Click to collapse
Now we'll let annoyingduck take us home.
annoyingduck said:
-Be prepared to wait a while while all that bloat and user apps optimize in ART!!
-Put your internal sd card data you pulled earlier back on your phone
-Cry now, because its a nice build and your stuck without root. No more saving your app data with Titanium or removing the load of ****e Verizon has put into it...... unless a root method is found.
-You can KDZ or TOT back to stock, re-root, bump recovery, flash 12b radio, and restore your backup if you can't live without root....which I will be doing again shortly because my OCD won't allow me to function with apps like NFL mobile embedded in my phone!! Just wanted to outline a method for you guys.
Click to expand...
Click to collapse
So there you have it, you're on Verizon official stock Lollipop (23A) for the G3! Now, there's a lot of bloat on there, which you can disable at will. This is a list of apps that are safe to disable, courtesy roirraW "edor" ehT and typed up by yours truly.
Can Be Uninstalled said:
Farmville
iHeartRadio
Click to expand...
Click to collapse
Can Be Disabled said:
Amazon
Amazon app suite
Amazon Kindle
Amazon MP3
Appstore
Audible
Cloud
DT Ignite
FamilyBase Companion
Favorite Contacts Widget
FIle Manager
Google Play Books
Google Play Games
Google Play Movies & TV
Google Play Music
Google Play Newsstand
Google+
LG TTS+
Message+
Music
Music
My InfoZone
My Verizon Mobile
NFL Mobile
SLacker
Support & Protection
Verizion Location Agent
VZ Navigator
Click to expand...
Click to collapse
After disabling most of that (I think I left one or two I use on, like G+, Google Books, etc), my G3 is happily up & running without issue. Some have discovered issues with their installs.
The only issue I've had is gmail not syncing on WiFi. I've tried everything I (and the community) can think of and am unable to fix the no-notifications-on-WiFi bug. Unfortunately I'm not alone, but it doesn't affect everyone. So, be forewarned, this is a semi-widespread bug. Everything else I experienced about this build is absolutely wonderful, save for that one bug.
Once you're done, you should be greeted by some notifications similar to these...and a software info screen that looks like this. With the bloat disabled, Antutu treated me well with a score over 41K. That's without any tweaking at all obviously since there is no root yet. I only miss two things about root - Titanium Backup and the ability to change DPI (to my preferred 600). Aside from that and the bloat (which is disabled), I'm quite happy as it is.
There you have it folks...if you want to be an early stock Lollipop adopter on the Verizon G3, this is how to do it! To answer the other inevitable question, yes you can downgrade back to 10B, root and install bumped TWRP without issue.
Special thanks to @annoyingduck for most everything how-to above, @justiz33 for the easy 12B-to-23A path, @roirraW "edor" ehT for the safe-to-disable list, Team Codefire for the files, @autoprime for IOroot & @quangnhut123 for the LG Flash Tool. If any one of you takes issue with how your posts are represented, please don't hesitate to PM me and I'll do what it takes to fix it.
Last, but not least, please do not quote this entire ginormous post in responses. It's unnecessary and insane. Thanks in advance. :fingers-crossed:
Do you have the MD5 for LG_VS985_12B-23A.dlpkgfile? (The update 12B to 23A MD5sum) i cant seem to find it but mine is
478a14b37b34e353722022e547fb2894
KShion619 said:
Do you have the MD5 for LG_VS985_12B-23A.dlpkgfile? (The update 12B to 23A MD5sum) i cant seem to find it but mine is
478a14b37b34e353722022e547fb2894
Click to expand...
Click to collapse
I just downloaded it again on my PC and checked the one on my phone. Both match: 85f01bfdefb4615328a29300a3625b64
Well this is new, and nifty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, fyi, disabling and re-enabling account sync did NOT fix my Wi-Fi gmail sync problem. Deleting and re-adding my Google account didn't either. Hate it, but I might have to try a factory reset. Perish the thought.
EDIT - Battery life is looking pretty darn good to me too.
I have the world's worst Windows machine and I'm having problems with the LG flash tool working. It just freezes every time I try and use it. I'm currently on the 11c build and with root and TWRP. Could I just restore the stock recovery, take the OTA to 12b, unroot within superuser, and then use the above method to get to lollipop?
jlvlawrence said:
I have the world's worst Windows machine and I'm having problems with the LG flash tool working. It just freezes every time I try and use it. I'm currently on the 11c build and with root and TWRP. Could I just restore the stock recovery, take the OTA to 12b, unroot within superuser, and then use the above method to get to lollipop?
Click to expand...
Click to collapse
If you're able to do that, I don't see why it wouldn't work; but I don't think it has been tried, at least that I've seen, so you'd be the guinea pig.
As far as flash tool, do you have any TOT flashing tools/programs installed? Are you sure the driver is properly installed? Try seeing if you can see your device with adb. It comes with the ioroot package linked in the OP. Enable USB debugging, plug it in and set it to internet/ethernet mode. Then launch a command prompt in the adb folder and see if you can see your device by typing "adb devices".
hokiealumnus said:
If you're able to do that, I don't see why it wouldn't work; but I don't think it has been tried, at least that I've seen, so you'd be the guinea pig.
As far as flash tool, do you have any TOT flashing tools/programs installed? Are you sure the driver is properly installed? Try seeing if you can see your device with adb. It comes with the ioroot package linked in the OP. Enable USB debugging, plug it in and set it to internet/ethernet mode. Then launch a command prompt in the adb folder and see if you can see your device by typing "adb devices".
Click to expand...
Click to collapse
Well, I wasn't able to OTA from 11c to 12b. I keep getting an error. My issue with the flash tool is it freezes before the flash process. It freezes at around 7 percent after plugging the phone in. Im pretty sure the drivers are correctly installed.
jlvlawrence said:
Well, I wasn't able to OTA from 11c to 12b. I keep getting an error. My issue with the flash tool is it freezes before the flash process. It freezes at around 7 percent after plugging the phone in. Im pretty sure the drivers are correctly installed.
Click to expand...
Click to collapse
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
hokiealumnus said:
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
Click to expand...
Click to collapse
I'll check when I get home and see if adb is working. Thanks for your help.
hokiealumnus said:
The only issue I've had is gmail not syncing on WiFi. I turned off, then re-enabled account syncing. I'll report back if that doesn't fix it when I'm back on WiFi.
Click to expand...
Click to collapse
A resolution has been had! Deleting my google account didn't work, nor did toggling sync. What worked was a kind suggestion by @Crsdr37 from the bug thread.
Crsdr37 said:
Use the built in LG backup app. Do a factory reset through settings and your sync issues should be resolved was for me anyways.
Click to expand...
Click to collapse
hokiealumnus said:
I'll give that a try, thanks! I honestly just ignored the built-in backup and didn't realize it would do downloaded apps. That's quite handy. Thanks for the tip, I'll report back whether it works. :fingers-crossed:
Click to expand...
Click to collapse
hokiealumnus said:
Wow, that worked incredibly well; pretty much equally as good as TiBu. Seems it fixed my gmail-on-wifi issue too. Thanks for the tip!
Click to expand...
Click to collapse
Like I said there, that thing is just as good as TiBu. Now the only real reason I miss root is the inability to change DPI. Sure, I'd rather have it de-bloated than have to disable a bunch of stuff, but disabled is nearly as good. I'm very pleased with this build.
Now @hsbadr & @HolyAngel are working diligently to try and get a custom stock ROM going for us, but in the mean time I'm happy to stick it out on unrooted stock. For now.
Thanks - this worked great. Software status says modified, is there a way to change that back since we're stock again?
hokiealumnus said:
Hmm. Sorry; without being at your computer to play with it, there isn't a whole lot I can think of other than the drivers. Did you check whether you can access the phone via adb?
Click to expand...
Click to collapse
So this is where I get stuck within the flash tool.
Ignite023 said:
Thanks - this worked great. Software status says modified, is there a way to change that back since we're stock again?
Click to expand...
Click to collapse
Huh...good question. Following the path above, mine says Official. Screenshot is here. You're not the first to report that though, so I'm not really sure what makes the difference, sorry.
hokiealumnus said:
Huh...good question. Following the path above, mine says Official. Screenshot is here. You're not the first to report that though, so I'm not really sure what makes the difference, sorry.
Click to expand...
Click to collapse
I don't know if this is the case here, but I think I've noticed even someone's rooted and they successfully unroot and restore stock everything, something is left behind and the status is modified, whereas if going straight from completely stock to 23A results in Official.
Sent from my VK810 4G
roirraW "edor" ehT said:
I don't know if this is the case here, but I think I've noticed even someone's rooted and they successfully unroot and restore stock everything, something is left behind and the status is modified, whereas if going straight from completely stock to 23A results in Official.
Sent from my VK810 4G
Click to expand...
Click to collapse
Very interesting. Using the method in the OP I was indeed rooted on 10B to install my apps with TiBu, then the upgrade to 12B took root away (leaving the apps). I wonder if it has to do with the method for root? Could stump root be different than ioroot maybe?
@jlvlawrence, what method did you use to root on 10B?
hokiealumnus said:
Very interesting. Using the method in the OP I was indeed rooted on 10B to install my apps with TiBu, then the upgrade to 12B took root away (leaving the apps). I wonder if it has to do with the method for root? Could stump root be different than ioroot maybe?
@jlvlawrence, what method did you use to root on 10B?
Click to expand...
Click to collapse
Mine's on official. I wasn't sure until I checked. I had my apps installed with Titanium Backup under 12B before I flashed the OTA. After trying it out I found my WIFI was constantly trying to turn on, so I did a factory reset and it was good after that.
I used Stump under 10B, for the record.
My phone overall seems snappier from the factory reset. It's probably a good idea for folks to so, period.
KDZ to 10B, root & restore apps, KDZ to 12B, initiate OTA to 23A, backup with LG utility, factory reset, login and restore from LG backup.
Sounds like a lot, but it is worth it, at least IMHO.
hokiealumnus said:
My phone overall seems snappier from the factory reset. It's probably a good idea for folks to so, period.
KDZ to 10B, root & restore apps, KDZ to 12B, initiate OTA to 23A, backup with LG utility, factory reset, login and restore from LG backup.
Sounds like a lot, but it is worth it, at least IMHO.
Click to expand...
Click to collapse
Doesn't 12B have the LG Backup too? Save restoring with TB if so. Might have to play with this.
Huh, not sure.
...and darnit, not getting notifications again. There must be something in the backup. I'll try it again and only back up my apps with nothing else and see if that fixes it.
I know it successfully got an email before restoring the backup. Hmm. Might have to just download the apps fresh the lollipop way. Hate to lose that data though.
hokiealumnus said:
Huh, not sure.
...and darnit, not getting notifications again. There must be something in the backup. I'll try it again and only back up my apps with nothing else and see if that fixes it.
I know it successfully got an email before restoring the backup. Hmm. Might have to just download the apps fresh the lollipop way. Hate to lose that data though.
Click to expand...
Click to collapse
Keep us posted if you make any progress on eliminating the quirks.
I really need some help. Please please help. I have my LG G3 VS985 and it was on stock verizon firmware. I had lollipop and android 5.1.1. I rooted it using Kingroot and it was working fine. I used an app called Autorec and i tried flashing twrp using it and all it did was make my phone not turn on. It keeps vibrating and i really need your help or anyone. I'm very worried.
I have this same exact problem... anyone have a solution?
I haven't looked in @bender_007 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.
Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.
Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.
Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. @xdabbeb experienced just how much Kingroot modifies the ROM under the hood.
roirraW "edor" ehT said:
I haven't looked in @bender_007 's autorec thread in a while but last I looked he didn't provide a version for 35B, only 23C and 24B.
Even if the screen stays black, go through the motions of putting the phone in Download mode. Does your phone show up in Windows' Device Manager in the modem section? If so, flash the 10B TOT using the .DLL that's extracted from the 35B KDZ to start fresh. Re-root with the Stump app and use TWRP Manager from the Play Store to put TWRP back on.
Rooting gets more complicated after 10B and putting TWRP on gets more complicated after 12B. For what it's worth, I stick to stock but modified/heavily debloated Verizon/LG ROMs.
Always flash the 10B TOT to root and to put TWRP on, it just saves a lot of headache. Kingroot installs a bunch of stuff behind the scenes (not just apps), so it's very shady. @xdabbeb experienced just how much Kingroot modifies the ROM under the hood.
Click to expand...
Click to collapse
I was completely stupid and have soft bricked my phone tonight.
I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.
I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.
Can you please walk me through the steps?
I feel so stupid and this couldn't have happened at a worse time.
Specter597 said:
I was completely stupid and have soft bricked my phone tonight.
I had a small issue with xdabbeb's 47A and went to restore a prior nandroid. Now the phone turns on, (I can hear it) but the screen is black. I'm sure it's a bootstack 35B issue.
I'm in a panic and am having trouble finding all the correct files to TOT or KDZ back and fix my phone.
Can you please walk me through the steps?
I feel so stupid and this couldn't have happened at a worse time.
Click to expand...
Click to collapse
For KDZ, @annoyingduck 's stickied return to stock thread in the General section.
For TOT, just Google for:
Code:
TOT method
and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.
As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
roirraW "edor" ehT said:
For KDZ, @annoyingduck 's stickied return to stock thread in the General section.
For TOT, just Google for:
Code:
TOT method
and just use the VS985 TOT and .DLL. The method is the same on all LG devices, just use the VS985 files instead of whatever the directions you find specify. You can still get the 10B TOT and the .DLL that's necessary at my Android File Host section which is linked to from the bottom of the first post of the return to stock thread I referenced. There's also a link to his thread in my signature below.
As you found out, when restoring TWRP back ups or flashing a new ROM, always flash the corresponding appropriate Bootstack after the restore or flash. 12B Bootstack for KitKat, 24B Bootstack for Lollipop 5.0.x and 35B Bootstack for Lollipop 5.1.x and Marshmallow 6.0.
Click to expand...
Click to collapse
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
Specter597 said:
Yes, I see the link in your sig now. Thanks for responding. The 10b download is not working from that link but 12b KDZ is downloading. Should that be a problem? I can still bump and stump 12b right? Also I think 12b was what shipped with my phone.
Click to expand...
Click to collapse
You're welcome!
You're looking at the direct links to those KDZs, right, like the following?
-VS98510b_01.kdz: -Thanks to @autoprime
-Mirror for VS98510b_01.kdz (10b): md5: d228ba692ef0c4704cba0b00fad8b8c
-VS98512b_00.kdz: -Thanks to @hokiealumnus for the AFH hosting
-Mirror for VS98512b_00.kdz (12b): md5: e8280b279d327b96689579a9eca22a3e
Click to expand...
Click to collapse
I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place. 10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.
What your phone came with doesn't affect things.
Even though your screen may stay blank, if you go through the motions of putting it in Download mode, then it will be in Download mode. Pull the battery first then put it in Download mode using the original USB cable that came with the phone, connected preferably to a USB 2.0 port that comes directly off of your PC motherboard - not through a USB hub. You can check it by looking in Windows' Device Manager to see if the "LGE..." device is listed under the Modem section.
The symptom you're having is common and isn't actually caused by a Bootstack, but by a lack of one, or probably more accurately, a catastrophic mix of conflicting partitions caused by, in this case, having one Bootstack on the device - probably 35B, and then restoring a backup that might've included only some of the partitions necessary for the Bootstack. TWRP backups don't back up the entire Bootstack, so you end up with some partitions from one, and other partitions from another, and they don't play well together.
JasmineROM and SkyDragon in particular play havok, so even if you dirty flashed either ROM after restoring a TWRP backup of either, if you had the 35B Bootstack flashed previously and didn't flash any Bootstack after dirty flashing either ROM, you'd have a mix of 24B and 35B partitions because even though the latest versions of both of those ROMs are based on 35B, they include part of the 24B Bootstack, but not even the whole thing at that. The reason they did that is because they couldn't figure out how to get the 35B modem working, and it wasn't until @xdabbeb packaged the proper Bootstacks we needed that it was realized that the 35B sbl1 - which those two ROMs don't include any kind of sbl1 partition - is necessary for the modem to work with it, so they included some 24B partitions because that modem worked fine with the older sbl1 which was still on the device from the last time the phone was flashed to stock unrooted.
We have a similar situation with 47A except in this case, besides needing the 47A sbl1 for the 47A modem to work, the 47A sbl1, in combination with the 12B aboot (bootloader) causes a QHSUSB_BULK 9008 mode type of brick, which requires different instructions for recovering than the normal KDZ or TOT methods, although it does use the TOT as part of the recovery, and then you flash the entire TOT method afterwards.
Sorry if this is TL;DR.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
roirraW "edor" ehT said:
You're welcome!
You're looking at the direct links to those KDZs, right, like the following?
I have an Android File Host link below those that points to a folder that has all the KDZs and TOTs in one place.
Click to expand...
Click to collapse
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b
10B, whether TOT or KDZ, is recommended because you can root 10B the easiest - by using the Stump app found on XDA. You can't use Stump after 10B, or at least definitely not on 12B (not 100% positive about 11C that came between). Put TWRP on after rooting with TWRP Manager from the Play Store. Installing TWRP is possible that easily on 12B if you root it using a different method. Putting TWRP on becomes more complicated after 12B, FYI.
Click to expand...
Click to collapse
I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.
Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?
About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"
... and here we are.:crying:
Specter597 said:
I followed to your Android Host link and was getting errors on primary DL and mirrors for 10b KDZ and 10b TOT. That is why I started DLing the 12b
I think the most recent version of Stump could brute force 12b. I never TOT'd back to 10b when I bought my phone so it may have worked a year or so ago. But I will try downloading 10b KDZ and 10b TOT/.DLL in a few minutes and see if the Android Host File DL's are working again.
Is there any problem with KDZ'ing now and TOT'ing later? I understand the limitation on KDZ and Updates. But KDZ doesn't prevent a future TOT does it?
About the TL;DR - I read it. You describe EXACTLY what I did. I was on Jasmine 9.1; I successfully installed 47A but TWRP borked my MMS/SMS backups so I thought, "I'll restore my TWRP nandroid AND (because I thought I was clever) I'll dirty flash the ROM and Update over the Nandroid so that the partitions are correct!"
... and here we are.:crying:
Click to expand...
Click to collapse
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.
No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.
I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.
No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.
Whether TOTing or KDZing, if you're rooted and have flashed any of @xdabbeb 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
roirraW "edor" ehT said:
Weird, I just checked and all the servers aren't working for me either. I might have to put all the files up somewhere else as a backup. AFH is so convenient though since developers can upload via FTP.
No, Stump won't work on 12B. You have to brute force on 10B, but it just won't work on 12B. A new root method had to be found, and they're available, some scripts in some threads in the non-Verizon G3 General section, but it requires a connection to the computer and USB Debugging mode and is less reliable than Stump.
I'll upload the 10B stuff and the .DLL elsewhere and I'll let you know if/when it's up - might take a while to upload though.
No, you can always TOT - just TOTing from stock unrooted 35B and higher requires the .DLL I have a copy of (it's extracted from the 35B KDZ). There was an older .DLL that worked fine coming from 24B and lower, but the new .DLL should work for coming from both new and old builds. And as I think you're saying you already know, if you're on stock unrooted 35B or higher you can only flash the 35B or higher KDZs, which is one of the reasons it's always suggested nowadays to flash the 10B TOT in order to root and put TWRP on.
Whether TOTing or KDZing, if you're rooted and have flashed any of @xdabbeb 's Bootstacks, then you should be able to flash the TOT with either the old or new .DLL, and you can flash any KDZ.
Click to expand...
Click to collapse
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
Specter597 said:
Thank you, thank you. I DID manage to download the special 10b .DLL from your Android Host File location. I think I've found the 10b_3 TOT on a different site and I'll try using it with your DLL - but if I doesn't work I'll try getting yours as well when you tell me its working.
Click to expand...
Click to collapse
You're welcome. That's good. I'm uploading the TOT and KDZ elsewhere but looks like it'll take three or more hours to finish.
Good luck!
---------- Post added at 10:03 AM ---------- Previous post was at 09:27 AM ----------
@Specter597 I had put in a ticket to Android File Host and it appears the problem was caused by me. They told me there were illegal characters in the filename and said he'd contact the uploader, not realizing the uploader was me, so he didn't mention which characters are illegal - I asked so hopefully he'll reply soon and I don't have to experiment to find the right combination.
For what it's worth, thanks for helping me to find out there was a problem with some of my filenames on AFH. Doh me!
Edit 2: Turns out it was the comma I had put in the filename. I removed the comma from that one and the 10B KDZ and now they download fine. Sigh!
This time I was successfully able to start the 10b TOT download from your AHF.
Thank you so much.
I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
Specter597 said:
This time I was successfully able to start the 10b TOT download from your AHF.
Thank you so much.
I'm going to take the time and download YOUR file out of sheer paranoia, even though the other file has finished.
Click to expand...
Click to collapse
If the MD5 hash of the TOT you had downloaded is F22CD79F6C4924A0FE4429A8C4BABE9A, then it's the same as the TOT I have inside the 7-Zip archive you're currently downloading. That's the easiest and quickest way of checking to see if you have the right thing.
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.
Do you think I should just try different Phone drivers?
Edit: Maybe I have the drivers right now.
Edit 2: The Drivers' installation seem to be spotty.
Sometimes The LGE Android MTP Device install Fails
Sometimes the LGE Mobile for VZW USB Modem fails.
But I'm having a hell of a time figuring out if I'm in Download Mode or not.
How long, @roirraW "edor" ehT after I plug in the USB cable should I continue to hold "Up"?
Specter597 said:
I've gotten everything installed and setup, but for whatever reason Windows 7 is not showing the LGE Modem at all in COM Ports.
Do you think I should just try different Phone drivers?
Edit: Maybe I have the drivers right now.
But I'm having a hell of a time figuring out if I'm in Download Mode or not.
How long, @roirraW "edor" ehT after I plug in the USB cable should I continue to hold "Up"?
Click to expand...
Click to collapse
You would only have to hold the Up volume button for at the very most 10 seconds, and that's probably extreme. If the Modem and Port sections list the LGE device now, you can be reasonably sure it's in Download mode. For TOT, change the port of the LGE device that's in the Port section (not Modem section) to 41.
I always use the latest drivers either from LG's or Verizon's website. 4.0.4 was the latest last I looked. I always reboot the PC (with the phone disconnected) after installing drivers. I don't bother updating the drivers to the latest if I already have working ones installed. With new drivers, it can take Windows up to 10 minutes to actually finish loading the drivers the first time you plug a new device into a new/different USB port. That's the way all USB devices work. In other words, if you plug the phone into port "A" in Download mode and you wait anywhere from seconds to minutes until it loads the drivers, and then unplug it and replug it into port "B", then it'll load the driver again. If you switch back to "A" it won't have to load the driver again, though.
They'll all load them from the same driver installation you did once.
Are you using the original USB cable that came with the phone? Letting the phone sit while plugged in, and not moving it around? Sometimes just rebooting the PC or trying different USB 2.0 ports help. In the end, sometimes trying a different PC helps.
Update: Success.
Successfully TOT'd back to 10b.
I decided (after installing/reinstalling the drivers 6 times) that even though it had said that some of the drivers failed to install, I would just say "F* it." Try it anyway. Despite the Windows installer saying that two elements of the DL Mode Driver package didn't install - it worked anyway. The other part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in. What a way to spend 12 hours of my life.
Thanks for all your support @roirraW "edor" ehT
Now I just have to decide if I want to bother rooting again, install xdabbeb's 47A or just play it safe ...
Specter597 said:
Update: Success.
Successfully TOT'd back to 10b.
I decided after installing/reinstalling the drivers 6 times, that even though it had said that some of the drivers failed to install, I would just F* it. Try it anyway. The part that got me was that after clicking the Yellow arrow you have to unplug/plug the phone back in.
Thanks for all your support @roirraW "edor" ehT
Now I just have to decide if I want to bother rooting again or just play it safe ...
Click to expand...
Click to collapse
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting!
Hope you didn't lose anything you don't mind losing.
roirraW "edor" ehT said:
Great! You're welcome! Glad things didn't get worse from installing drivers so many times. F* it. Root it, it's so easy. Just always remember to flash the right Bootstack after flashing any ROM, even if you think you're already on the right Bootstack - doesn't matter, just flash it, there's no reason not to. You know you can't stand it without the features you get from rooting!
Hope you didn't lose anything you don't mind losing.
Click to expand...
Click to collapse
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
Specter597 said:
No. I don't think there was anything that I don't have backed up. (I'm a nut about cloud/sdcard/etc.) Just some SMS/MMS. Maybe a save'd game. Who cares! I still have a phone!! :laugh:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
And after I Root and TWRP is there any reason I can't go straight from 10b to xdabbeb's 47A?
Click to expand...
Click to collapse
Yes you can go straight to 47A from 10B, I've done it a few times before with no problems. Also you can try out xdabbeb's 2.0 which is lollipop not marshmallow. Very slimmed down, not a whole lot of grill to it, but very smooth and reliable. I keep going back and forth between the two myself.
Sent from my g3 using XDA Labs
Specter597 said:
But I'm definitely deleting those Jasmine 9.1 backups. I don't even want to risk that again. Aside from Skydragon/JasmineROM are there any of the other ROM's floating in the DEV forum that will Bork my phone this badly?
Click to expand...
Click to collapse
Not that I'm aware of. And either ROM is just fine as long as you flash the Bootstack after, and you should do that no matter what TWRP backup or ROM you flash.
Is this at all possible? When attempting to downgrade with LGUP, it interrupts the flashing process (usually) around 9% with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a way to force-flash it regardless of this error? Or am I stuck without root forever?
Any answers are greatly appreciated.
At this moment in time the answer is NO. This is why you want to not do an upgrade until root is confirmed for the newer OS. Once recovery is available maybe you might be able to get root back.
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
LBJM said:
I should correct myself you can't use the kdz files and go back to lolipop
details here :
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I was thinking about the TWRP method before, my bad.
Click to expand...
Click to collapse
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
jingTongy said:
Thank you for the snappy reply! I have been very closely watching these forums on updates to either downgrade to lollipop, or root marshmallow. I sure hope we can get this resolved for people who's phone came with marshmallow
Click to expand...
Click to collapse
I had to downgrade using that same software when I purchased my Lg G3 and that alone sold me on the V10. With Samsung phones you are stuck if you have a newer OS.
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
mcbeat257 said:
The main reason you cannot downgrade is that the software won't flash an old version (as it checks your version stub), at all, on Verizon.
Click to expand...
Click to collapse
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
jingTongy said:
So, with the way you termed it, it sounds like it's a software problem with LGUP?? If so, do you think it can be patched to ignore the version?
Click to expand...
Click to collapse
The software itself makes it do this, and it is irrevocable and not able to do so in the builds, it reminds me of when I had my galaxy s4 and this happened as well.
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
zatanas33 said:
Could you quote the part on that post where it talks about downgrading the firmware? As far as I can tell from the link you provided, that post only talks about returning the phone back to stock. And just to be clear, once you install the OTA update to the MM build, your stock is now the MM firmware. Please correct me if I am wrong.
Click to expand...
Click to collapse
You may be correct, and hopefully somebody more knowledgeable than myself will chime in, but this text is part of the instructions from that thread:
TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a FULL wipe, tick BIN file. Press Start. Make cup of tea and be patient
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
mikekoz said:
According to this thread , you can:
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I normally do not root my phones, but I am having battery drain problems and I see no advantage to Marshmallow. I may downgrade if I cannot resolve my current problem.
Click to expand...
Click to collapse
I was having the same battery drain problem after the Marshmallow update on my V10. I let it go for a couple days to see if things would improve. Unfortunately, things weren't getting any better. While I've rooted a lot of Android phones in the past, I didn't really want to void the warranty on this phone yet.
I went ahead and did a factory reset and the battery is working better than ever. I usually use Titanium Root to backup, but had to rely on LG Backup this time. It worked well enough even though it took a long time to copy everything to the SD Card (about 3 hours for 4 GB). Only things that didn't come through after restoring were my home screen settings and the history for one game. No big deal, about an hour to get everything configured back to original (grab screenshots of your homescreen first).
Pretty thrilled to see the battery performing better than ever. Just got 16 hours out of it yesterday and had 35% left on somewhat light use.
burnsky05 said:
This does not work on the Verizon variant
Sent from my VS990 using XDA-Developers mobile app
Click to expand...
Click to collapse
The instructions say otherwise. There is even links to Verizon drivers. Where do you see that this method does not work for Verizon V10's?
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
burnsky05 said:
http://forum.xda-developers.com/showthread.php?t=3344828
Sent from my VS990 using XDA-Developers mobile app
The thread also states its for certain models of LG V10 but the LGUP has a anti rollback built into it that will not allow you to go from marshmallow to lollipop on certain models...
Click to expand...
Click to collapse
Thanks. :good:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
hann1balk1ng said:
So, maybe someone could come up with a anti rollback work around? Hopefully, or some other alternative.
Click to expand...
Click to collapse
Possible if someone could reverse-engineer LGUP to allow downgrading. I have the lollipop KDZ file, now all I need is a way to flash it to my vs990.
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
AMCJUNGLE said:
In an attempt to downgrade an error was not seen in LGUP. As far as anyone could tell the phone and LGUP were in sync up until 85% or so and the reboot was initiated. The phone never came back on. LGUP made it to 100% but the phone stayed black. Maybe not,enough time was allowed to pass but the battery was then removed. The phone became a brick and wouldnt start in any mode. When plugged into a computer the computer sees something tries to install a driver then fails. Do not try and downgrade from Marshmallow with LGUP. It will not work.
Click to expand...
Click to collapse
Oh man that sucks.
Sent from my Nexus 7 using XDA-Developers mobile app
I've used the KDZ method successfully to return to stock several times but now I have to do a warranty exchange and Verizon won't send the replacement phone because they claim they can see I didn't take any updates. So now I have to go back to stock but I can't use KDZ because the charging port is the flaky part so I can't connect to the PC. What if any alternate methods can I use?
On a related note, I am guessing the replacement will have most if not all of the latest updates and from what I've read I can no longer use Stump Root to root the phone. Alternatives?
gospodinwizard said:
I've used the KDZ method successfully to return to stock several times but now I have to do a warranty exchange and Verizon won't send the replacement phone because they claim they can see I didn't take any updates. So now I have to go back to stock but I can't use KDZ because the charging port is the flaky part so I can't connect to the PC. What if any alternate methods can I use?
On a related note, I am guessing the replacement will have most if not all of the latest updates and from what I've read I can no longer use Stump Root to root the phone. Alternatives?
Click to expand...
Click to collapse
Unfortunately, KDZ or TOT require the USB port. And those are the only way to return to full stock.
If you have root and TWRP now, I can make you a flashable zip that contains all the stock 47A partitions, including recovery, so once you'd boot out of custom recovery you'd be back to stock. I can't guarantee that it would say "Official" instead of "Modified" in the About menu, though. I also can't guarantee that the phone won't be bricked somehow, either. All the risk is on you.
Stump is still the way to go, you just have to downgrade to 10B using the TOT method and the .DLL that's extracted from the 35B KDZ. Both the TOT and correct .DLL are up in my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
roirraW "edor" ehT said:
If you have root and TWRP now, I can make you a flashable zip that contains all the stock 47A partitions, including recovery, so once you'd boot out of custom recovery you'd be back to stock. I can't guarantee that it would say "Official" instead of "Modified" in the About menu, though. I also can't guarantee that the phone won't be bricked somehow, either. All the risk is on you.
Stump is still the way to go, you just have to downgrade to 10B using the TOT method and the .DLL that's extracted from the 35B KDZ. Both the TOT and correct .DLL are up in my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
Click to expand...
Click to collapse
The good news is I fiddled with USB enough to be able to successfully flash the 10B KDZ again. The weird news is that when I went to check for system updates, I was politely told my phone was up-to-date at 10B. Makes no sense to me and I'm not sure what to do about it. Any thoughts? The only reason I care about the updates is Verizon swore they wouldn't send out a replacement until I took updates. I.e. their complaint was that I hadn't taken any updates.
gospodinwizard said:
The good news is I fiddled with USB enough to be able to successfully flash the 10B KDZ again. The weird news is that when I went to check for system updates, I was politely told my phone was up-to-date at 10B. Makes no sense to me and I'm not sure what to do about it. Any thoughts? The only reason I care about the updates is Verizon swore they wouldn't send out a replacement until I took updates. I.e. their complaint was that I hadn't taken any updates.
Click to expand...
Click to collapse
It's normal and common that after flashing a TOT or KDZ that it says no updates for hours or even a day or so. Eventually, as long as you have an activated Verizon SIM inserted, it'll get updates. It won't without the SIM so if you already are using the SIM in a backup phone, that's another reason why.
If your USB were reliable, I'd suggest flashing the 47A KDZ, but I would recommend against it at this point.
roirraW "edor" ehT said:
It's normal and common that after flashing a TOT or KDZ that it says no updates for hours or even a day or so. Eventually, as long as you have an activated Verizon SIM inserted, it'll get updates. It won't without the SIM so if you already are using the SIM in a backup phone, that's another reason why.
If your USB were reliable, I'd suggest flashing the 47A KDZ, but I would recommend against it at this point.
Click to expand...
Click to collapse
Good point about 47A. Especially since their complaint was I hadn't taken any updates I want to be to say I actually took an OTA so I've got 24B on it now and I'll give it a day and see what shows up.
Glad to see you got it flashed back to stock.
Also, I should have asked this before, but are you using the original cable that came with the phone or a different one? It could be the cable itself is bad. Have you tried several different cables? Also, make sure you are not hooking up to USB 3.0 ports. I believe those won't work or don't work well with this phone. I could be wrong.
Or it could be the USB port is loose on your phone causing the issue. In that case, that's a hard one to get to work other than what you tried, which is jiggling and fiddling with it.
In any case, it appears you are good to go. Just because you haven't taken the latest OTAs shouldn't prevent them from taking the phone back IMHO but who knows.
Or, as @roirraW "edor" ehT stated, you can wait a few days and it should get the OTA eventually. I've usually found that after flashing TOT or KDZ, I get the notice right away.
iBolski said:
Glad to see you got it flashed back to stock.
Also, I should have asked this before, but are you using the original cable that came with the phone or a different one? It could be the cable itself is bad. Have you tried several different cables? Also, make sure you are not hooking up to USB 3.0 ports. I believe those won't work or don't work well with this phone. I could be wrong.
Or it could be the USB port is loose on your phone causing the issue. In that case, that's a hard one to get to work other than what you tried, which is jiggling and fiddling with it.
In any case, it appears you are good to go. Just because you haven't taken the latest OTAs shouldn't prevent them from taking the phone back IMHO but who knows.
Or, as @roirraW "edor" ehT stated, you can wait a few days and it should get the OTA eventually. I've usually found that after flashing TOT or KDZ, I get the notice right away.
Click to expand...
Click to collapse
Want to make sure I clearly understand. Now that I have the replacement phone up and running, I use the flash tool and flash 7b._VS985_LGUP8974.dll_-_From_stock_35B-47A_TOT_back_to_10B_using_this_DLL.7z to get back to back to 10B and then use Stump to reroot?
gospodinwizard said:
Want to make sure I clearly understand. Now that I have the replacement phone up and running, I use the flash tool and flash 7b._VS985_LGUP8974.dll_-_From_stock_35B-47A_TOT_back_to_10B_using_this_DLL.7z to get back to back to 10B and then use Stump to reroot?
Click to expand...
Click to collapse
No. That's only the .DLL. You also need the .TOT file, which I have the same place as that .DLL, and you need to extract them from the .7Z (7-Zip) archive with the free www.7-zip.org. See the last two posts of this thread http://forum.xda-developers.com/verizon-lg-g3/help/lg-g3-vs98547a-downgrade-t3354241/page3#post67731364.
Yes, Stump's brute force option, then TWRP Manager to put TWRP on, then wipe Cache, Dalvik/ART, Data, flash the ROM you want and then the appropriate Bootstack for the ROM you're flashing.
roirraW "edor" ehT said:
No. That's only the .DLL. You also need the .TOT file, which I have the same place as that .DLL, and you need to extract them from the .7Z (7-Zip) archive with the free www.7-zip.org. See the last two posts of this thread http://forum.xda-developers.com/verizon-lg-g3/help/lg-g3-vs98547a-downgrade-t3354241/page3#post67731364.
Yes, Stump's brute force option, then TWRP Manager to put TWRP on, then wipe Cache, Dalvik/ART, Data, flash the ROM you want and then the appropriate Bootstack for the ROM you're flashing.
Click to expand...
Click to collapse
OK finally got back to this. I have the flash tool and LGUP8974.dll and VS98510B_01.kdz. In the flash tool I see nowhere to specify a dll to use so that makes me a little nervous. The directory with the flash tool executable has other dll's in it already but none have the same name as the dll I downloaded. Do I just drop the downloaded dll in that directory and flash the 10B KDZ or is there something I'm missing? Clearly I'm erring on the side of caution here. Sorry for all the questions but I rather ask alot and get it right than damage anything.
My bad not the KDZ but this: 7a._VS98510B_03.TOT-4.4.2-KitKat-MD5_hash_inside-(official-will_get_OTAs_-_file_inside_is_mistakenly_named_Jellybean).7z
gospodinwizard said:
OK finally got back to this. I have the flash tool and LGUP8974.dll and VS98510B_01.kdz. In the flash tool I see nowhere to specify a dll to use so that makes me a little nervous. The directory with the flash tool executable has other dll's in it already but none have the same name as the dll I downloaded. Do I just drop the downloaded dll in that directory and flash the 10B KDZ or is there something I'm missing? Clearly I'm erring on the side of caution here. Sorry for all the questions but I rather ask alot and get it right than damage anything.
My bad not the KDZ but this: 7a._VS98510B_03.TOT-4.4.2-KitKat-MD5_hash_inside-(official-will_get_OTAs_-_file_inside_is_mistakenly_named_Jellybean).7z
Click to expand...
Click to collapse
It doesn't matter where the separate .DLL is, or the TOT. When you launch the tool you browse to the locations of them. If you already got the different megalock.dll and replaced the one in the installation directory then you're good to go. I don't think there's any danger, if something's not right it won't flash anything so there's no chance of damage from that anyway. There's directions for the TOT method all over including in the non-Verizon G3 General section. The instructions are the same no matter what device, just use that TOT and .DLL, and the driver's for the VS985 instead of whatever ones the guide you use specify. In all cases it's the same flash program and replacement megalock.dll as far as I've been able to tell.
roirraW "edor" ehT said:
It doesn't matter where the separate .DLL is, or the TOT. When you launch the tool you browse to the locations of them. If you already got the different megalock.dll and replaced the one in the installation directory then you're good to go. I don't think there's any danger, if something's not right it won't flash anything so there's no chance of damage from that anyway. There's directions for the TOT method all over including in the non-Verizon G3 General section. The instructions are the same no matter what device, just use that TOT and .DLL, and the driver's for the VS985 instead of whatever ones the guide you use specify. In all cases it's the same flash program and replacement megalock.dll as far as I've been able to tell.
Click to expand...
Click to collapse
Well see here's what is confusing me. I have the flash tool and have used it many times for KDZ's. However, there is no spot in there that lets me specify a particular dll AND it only browses for
.kdz and .cab files. .... .tot doesn't appear to even be an option. The only two files I downloaded were the TOT and dll for going back to 10 B that you pointed. It leaves me wondering if something is amiss with the flash tool I have. I am operating under the assumption that my objective is to flash the TOT file as I would previously flashed a KDZ but the flash tool I have wont even select a TOT file or a dll for that matter.
gospodinwizard said:
Well see here's what is confusing me. I have the flash tool and have used it many times for KDZ's. However, there is no spot in there that lets me specify a particular dll AND it only browses for
.kdz and .cab files. .... .tot doesn't appear to even be an option. The only two files I downloaded were the TOT and dll for going back to 10 B that you pointed. It leaves me wondering if something is amiss with the flash tool I have. I am operating under the assumption that my objective is to flash the TOT file as I would previously flashed a KDZ but the flash tool I have wont even select a TOT file or a dll for that matter.
Click to expand...
Click to collapse
The Flash Tool 2014 is for KDZs only. If you Google for "TOT method", you'll find instructions and links to a different flash program, and also to the megalock.dll that you need to replace the one that the program comes with when you install it. Find a TOT method thread and you'll get all the information and screenshots you need of what you need.
I'm getting a new g3 this week. I know the first thing the phone will do when I activate it is to do the OTAs. I want to root my phone. I want to know at which point do I stop the OTAs so I don't get stuck with unroot able version. I know the latest version, 6.0 is not root able. I do want to accidentally go to far.
Thanks
Don't take any OTAs at all if you can help it. It could come with 47A already, some other user's have recently.
Usually you can downgrade to 10B via the TOT method using the .DLL that's extracted from the 35B KDZ (both available from my Android File Host link at the bottom of the first post of @annoyingduck 's stickied return to stock thread in the General section, or in my signature below.
Root is easiest with the Stump app on XDA with its brute force option and that only works on 10B, then use TWRP Manager to install TWRP, and that part is only that easy on 12B and below
@R-T-B has found evidence that if under your battery the model number has a K at the end like VS985WK, then you might not be able to downgrade at all, so no permanent root.
Kingroot works even on 47A but it's highly suspicious and deeply ingrains itself into your system even more than is necessary for root, and with it you have to reroot after every reboot, rooting requires Internet every time, and it might be sharing your private information in the background.
If you do try to downgrade and brick, especially if you have the "K" model number, @R-T-B has a new debrick thread in the General section with modifications to previously available methods to at least get the phone working back on 47A.
This my first lg phone so I'm not a noob when it comes to rooting, I'm unfamiliar with some of lg terms. I've had moto and Samsung in the past.
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
And yes, I have two threads on here. I have a thread to try and figure out out to unbrick a somewhat bricked g3 and this thread to make sure I don't do the same thing to the new phone.
Thanks
simpson1190 said:
So when the phone arrives I am going to post the current versions of everything and see if someone can guide me through the bes way to root, get twrp and flash a rom if I had to.
Click to expand...
Click to collapse
The best way is the same (what I replied previous) no matter what version.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
So the only hard thing is if I'm past 10b and/or the device is already on MM.
simpson1190 said:
So if I am on 10b, I can root with stump, flash twrp with twrp manager and I'm good to go? I can flash rooms even if they are based on new versions like MM?
Click to expand...
Click to collapse
Yes to both. Highly unlikely it'll come with 10B, and very likely it'll come with 47A or at least 35B.
roirraW "edor" ehT said:
The best way is the same (what I replied previous) no matter what version.
Click to expand...
Click to collapse
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
simpson1190 said:
so my new g3 had 35b on it.
i've followed the guide to flash down to 10 b, i get an error in the lg tool that says upgrade stopped due to an error. then it gives instructions on trying again..
Click to expand...
Click to collapse
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
roirraW "edor" ehT said:
You're using the new .DLL I directed you to? If you downloaded the TOT and .DLL from my Android File Host link, did you use 7-Zip to extract the files out of .7z archives you downloaded? Are you using the original USB cable (hopefully it came with the OEM one)? Installed the latest drivers from LG's website for the VS985 and then rebooted with the phone disconnected from the PC? Connected the phone in Download mode to a USB 2.0 port that comes directly off the motherboard on the PC (not USB 3.x and not through a USB hub)?
You changed the port # of the correct device - the one in the Port section, not the one in the Modem section, right?
Once the TOT flashing software gets to certain point where you think it's just going to "continue" on it's own but it doesn't, did you try unplugging the cable from the phone, wait five seconds, and then plug it back in, and wait up to a minute or more while the software should then start the flash in earnest?
Lastly, sometimes trying a different PC does the trick.
Click to expand...
Click to collapse
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878
simpson1190 said:
the post you pointed me to has the KDZ file not the TOT file. It does reference a thread to downgrade via TOT file but that thread doesn't have the download links on it anymore. [/QUOTE]
My Android File Host link...d has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
roirraW "edor" ehT said:
My Android File Host link at the bottom of the first post of that thread has all the KDZs, and the TOT and the .DLL.
Click to expand...
Click to collapse
ok i found your files and I"m downloading them now. I have downloaded the flash tool and it wants a username and password. found a work around that involves turning off the internet and resetting the date on the computer. Is this the best way to flash a tot or did i not download the correct tool?
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
simpson1190 said:
i give up....i get an error when using the tot that it didn't load. i even looked into the LGup tool and it says i have an unknown model. maybe this tool is not for the g3
Click to expand...
Click to collapse
simpson1190 said:
f it. i'm doing the ota to MM, i like the phone with stock unrooted. so it's not worth this headache. Maybe the problem is I am on windows 10. But it is the only computer I have. If I every have a chance to use a win 7 computer, maybe I will try. With what I read, I should be able to downgrade to 10b from MM using the same methods.
Click to expand...
Click to collapse
LGUp doesn't work with the VS985. The second post of the LGUp thread details what to use for Verizon G3s.
Windows 10 works fine. As long as your PCB (printed circuit board) in your particular phone isn't v2 (you'd have to look in @R-T-B 's thread in the General section as far as where to look on the board to find the "2" or "1", etc), then yes the downgrade method is the same from 47A. If you happen to have a newer revision of the VS985 then putting Marshmallow on will keep it from being downgraded any longer. This is a fairly recent development (last week or two) that this has been noticed in such detail.
If it is revision 2 of the PCB, then you won't be able to downgrade from 47A at all.
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Dethfull said:
What you mean with "unrooteable" ?
If we like rooteable devices, why still people stay paying these "unrooteable" devices?
Its time to IMPOSE for CHITTY GOGLE INC to create REAL LINUX ADM ROOTED devices or STOP BUYING THESE DAMN CHITS!
Sent from my XT687 using xda premium
Click to expand...
Click to collapse
Personally, I love my G3, but I'm with you. I won't buy another LG product until they lose their root/custom firmware unfriendly stance.
The Google in says "Google is your friend"
so, A friendly acceptable device, is being distributable by them?
We have years Forcing, imposing, root on all SIMPLY ALL these "friendly" devices.
How we believe on their phrase?
I only believe, the UNIX AND LINUX GPL ARE BEING PAID FOR THEIR "FRIENDISM".
Sent from my XT687 using xda premium