NOTE: This patch is only for upgrading from 12B to 23A. If you're currently on 10B or 11C, you'll need to upgrade to 12B before applying this patch. If wanted, I can upload those two patches as well.
Though there's already a thread about update 23A on the VS985, I figured an actual release of the OTA would warrant its own thread.
This is a release of the Verizon LG G3 5.0 OTA (VS98523A). The OTA package is unmodified (and probably couldn't be modified, at least easily, due to signing in the OTA package format). It was downloaded directly from Verizon's OTA servers. The OTA patch is only for version 12B; if you want to apply this upgrade and are running a version prior to 12B, you'll have to get to version 12B before applying the 23A patch.
You can download the package at http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/LG_VS985_12B-23A.dlpkgfile.
UPDATE: I've uploaded all three OTA update packages (10B to 11C, 11C to 12B, and 12B to 23A) to http://downloads.codefi.re/illegalargument/LG_VS985/.
The package is in an odd format and it is rather difficult to extract files from it, as many of the updates are provided in diff patches. However, there is a relatively simple way to apply this OTA using VerizonHiddenMenu. Root access is required to run the VerizonHiddenMenu activity.
Download the OTA package from the link above.
Copy the package to your device as either /storage/sdcard0/SoftwareUpdate/23A.up or /storage/external_SD/SoftwareUpdate/23A.up (technically, the filename can vary as long as it ends in the .up extension and is one of those two locations).
Run the following command:
Code:
adb shell su -c "am start -n com.lge.VerizonHiddenMenu/.fota.DmcTestFotaMenu"
This will start the diagnostic FOTA menu from the Verizon Hidden Menu.
From here, click on the "Select Package" option, and then choose "23A.up" from the list.
Once you've selected the update package, choose the "Do update" option from the menu. This should apply the update and if all goes well, you'll wake up with 23A when it's all done.
That's all there is to it. Have fun!
Annnnnd here we go! Lol
Nice work!
We need a Guinea pig that is willing to stay on stock/unrooted/locked 5.0 in order to test downgrade ability via kdz/tot.... Not it!
So if anyone is up for initiating this ota via terminal, can you please do some additional work by testing out downgrading? I have a 12b kdz file link in my thread that you can flash back to in order to push the lp update again (if downgrading works).
*edit*, command requires root, so full roll back to 10b will be required. Stock unrooted 12b is SOL unless you roll back for this method.
Thanks .....
Thank you!
I was going to mention I might become a guinea pig, but I'm not quite that brave yet. Maybe I will be in the morning when I've had proper sleep, and depending on what I've got got on at work.
I just planned on testing keeping root with SuperSU's keep root option, but otherwise completely stock besides the hidden menu requirement.
Sent from my VK810 4G
Thank you! Finally!
Do you have to be on stock KitKat for this to work?
I, too, am very anxious to see what the "guinea pig's" result of a potential downgrade is....that ominous "security software version" seen in that screenshot that has been circulating has me a tad worried though tbh. Thankfully I've gotten all the g3's I need for right now and have rooted/unlocked then all....but there's one more I'd like to get in about ~10 months (don't ask, long story) and would like to be able to root/unlock it, so really hoping for the best here!
---------- Post added at 05:04 AM ---------- Previous post was at 05:03 AM ----------
luke24 said:
Thank you! Finally!
Do you have to be on stock KitKat for this to work?
Click to expand...
Click to collapse
You would need to be on stock KitKat w/ stock recovery, yes.
luke24 said:
Thank you! Finally!
Do you have to be on stock KitKat for this to work?
Click to expand...
Click to collapse
Yes completely stock. No modifications. A reminder that this will break any exploits we have so far for rooting, you've been warned. Please tread cautiously. [emoji106]
Sent from my VS985 4G using Tapatalk
skiman10 said:
Yes completely stock. No modifications. A reminder that this will break any exploits we have so far for rooting, you've been warned. Please tread cautiously. [emoji106]
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Yea I kinda thought so..
This is exciting, but I think I'm gonna wait too...
Someone correct me if I'm wrong - but as far as anyone knows, literally anything could happen if one upgraded to his 23A update and then attempted to kdz back to 12B (or 10B_01, for that matter) - up to an including anything ranging from the downgrade simply erroring in flash tool and not working and you being OK but totally "stuck" on stock LP for the foreseeable future.....to a potential hard brick of your device, right?? It's the latter possibility that definitely would scare the ****ahky mushrooms out of me LOL
IllegalArgument said:
Though there's already a thread about update 23A on the VS985, I figured an actual release of the OTA would warrant its own thread.
This is a release of the Verizon LG G3 5.0 OTA (VS98523A). The OTA package is unmodified (and probably couldn't be modified, at least easily, due to signing in the OTA package format). It was downloaded directly from Verizon's OTA servers.
You can download the package at http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/LG_VS985_12B-23A.dlpkgfile.
The package is in an odd format and it is rather difficult to extract files from it, as many of the updates are provided in diff patches. However, there is a relatively simple way to apply this OTA using VerizonHiddenMenu. Root access is required to run the VerizonHiddenMenu activity.
Download the OTA package from the link above.
Copy the package to your device as either /storage/sdcard0/SoftwareUpdate/23A.up or /storage/external_SD/SoftwareUpdate/23A.up (technically, the filename can vary as long as it ends in the .up extension and is one of those two locations).
Run the following command:
Code:
adb shell su -c "am start -n com.lge.VerizonHiddenMenu/.fota.DmcTestFotaMenu"
This will start the diagnostic FOTA menu from the Verizon Hidden Menu.
From here, click on the "Select Package" option, and then choose "23A.up" from the list.
Once you've selected the update package, choose the "Do update" option from the menu. This should apply the update and if all goes well, you'll wake up with 23A when it's all done.
That's all there is to it. Have fun!
Click to expand...
Click to collapse
@IllegalArgument, thank you for the dlpkgfile patch. I'll use it to build a rooted 23A ROM.
hsbadr said:
@IllegalArgument, thank you for the dlpkgfile patch. I'll use it to build a rooted 23A ROM.
Click to expand...
Click to collapse
That would be awesome!!! Thanks!
ohlin5 said:
I, too, am very anxious to see what the "guinea pig's" result of a potential downgrade is....that ominous "security software version" seen in that screenshot that has been circulating has me a tad worried though tbh.
You would need to be on stock KitKat w/ stock recovery, yes.
Click to expand...
Click to collapse
Some info on that security software message
commoncriteriaportal.org/files/epfiles/st_vid10593-vr.pdf
niap-ccevs.org/st/Compliant.cfm?pid=10593
gsmarena.com/at_ts_lg_g3_is_receiving_the_android_50_lollipop_update_too-news-11143.php
TLDR: Basically, just its just a certification that all US varients have passed. Shows up in ATT version too, and ATT has confirmed rollback
mattd7591 said:
Some info on that security software message
commoncriteriaportal.org/files/epfiles/st_vid10593-vr.pdf
niap-ccevs.org/st/Compliant.cfm?pid=10593
gsmarena.com/at_ts_lg_g3_is_receiving_the_android_50_lollipop_update_too-news-11143.php
TLDR: Basically, just its just a certification that all US varients have passed. Shows up in ATT version too, and ATT has confirmed rollback
Click to expand...
Click to collapse
Interesting....well I still won't hold my breath given the things I've seen VZW do in the past, but thanks for the info, good find!
hot wings and beer explanation of wht this means...?????????????
great work
annoyingduck said:
Nice work!
We need a Guinea pig that is willing to stay on stock/unrooted/locked 5.0 in order to test downgrade ability via kdz/tot.... Not it!
So if anyone is up for initiating this ota via terminal, can you please do some additional work by testing out downgrading? I have a 12b kdz file link in my thread that you can flash back to in order to push the lp update again (if downgrading works).
Click to expand...
Click to collapse
I'd be willing to try it out and test the ability to downgrade but I won't be near a pc until 10 hours from now.
Error
IllegalArgument said:
Though there's already a thread about update 23A on the VS985, I figured an actual release of the OTA would warrant its own thread.
This is a release of the Verizon LG G3 5.0 OTA (VS98523A). The OTA package is unmodified (and probably couldn't be modified, at least easily, due to signing in the OTA package format). It was downloaded directly from Verizon's OTA servers.
You can download the package at http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/LG_VS985_12B-23A.dlpkgfile.
The package is in an odd format and it is rather difficult to extract files from it, as many of the updates are provided in diff patches. However, there is a relatively simple way to apply this OTA using VerizonHiddenMenu. Root access is required to run the VerizonHiddenMenu activity.
Download the OTA package from the link above.
Copy the package to your device as either /storage/sdcard0/SoftwareUpdate/23A.up or /storage/external_SD/SoftwareUpdate/23A.up (technically, the filename can vary as long as it ends in the .up extension and is one of those two locations).
Run the following command:
Code:
adb shell su -c "am start -n com.lge.VerizonHiddenMenu/.fota.DmcTestFotaMenu"
This will start the diagnostic FOTA menu from the Verizon Hidden Menu.
From here, click on the "Select Package" option, and then choose "23A.up" from the list.
Once you've selected the update package, choose the "Do update" option from the menu. This should apply the update and if all goes well, you'll wake up with 23A when it's all done.
That's all there is to it. Have fun!
Click to expand...
Click to collapse
Quick question on this...
I did all of the above, am on software 10B rooted with StumpRoot, put the file in /storage/sdcard0/SoftwareUpdate/23A.up, but after selecting the file at "Select Package" it hangs for a few seconds, gives me a toast notification that reads "Download = 23A.up", but when I press Do Update it reads, "RESULT_NOT_EXECUTED". Screenshots of the progress included. Any reason I'm getting this message? I tried renaming the file to 23A.up on the device first, then on the PC, and both times moved the file to the directory in sdcard0 (which didn't exist, I created the "SoftwareUpdate" folder). I'd be very grateful if someone could help me out.
First pic is selecting the file, second is it hanging and then returning to the FOTA Test Menu, and the last is obviously the error. I really would appreciate some help on this. Thanks in advance.
KlausWillSeeYouNow said:
Quick question on this...
I did all of the above, am on software 10B rooted with StumpRoot, put the file in /storage/sdcard0/SoftwareUpdate/23A.up, but after selecting the file at "Select Package" it hangs for a few seconds, gives me a toast notification that reads "Download = 23A.up", but when I press Do Update it reads, "RESULT_NOT_EXECUTED". Screenshots of the progress included. Any reason I'm getting this message? I tried renaming the file to 23A.up on the device first, then on the PC, and both times moved the file to the directory in sdcard0 (which didn't exist, I created the "SoftwareUpdate" folder). I'd be very grateful if someone could help me out.
First pic is selecting the file, second is it hanging and then returning to the FOTA Test Menu, and the last is obviously the error. I really would appreciate some help on this. Thanks in advance.
Click to expand...
Click to collapse
Additional info: each time the device restarts after trying all of that (manual restart of me turning it off and on), it goes to the blue Software Update screen and gives "err: 0x1111004". Once again, help is greatly appreciated. Thanks in advance.
KlausWillSeeYouNow said:
Additional info: each time the device restarts after trying all of that (manual restart of me turning it off and on), it goes to the blue Software Update screen and gives "err: 0x1111004". Once again, help is greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
If I remember right, "err: 0x1111004" means that something in the system filesystem has been modified, so when the FOTA program goes to verify the status of all of the files it wants to update, it finds a mismatch between what it expects and what is actually there. Since many of the files are updated with diffs, it can't patch the file if it has been changed from what it was expecting to find. I had trouble with this when I modified my HotspotProvision.apk to enable tethering.
And now reading what you said again, I'm pretty sure the problem is simpler than that. The patch provided is only from 12B to 23A. If you're currently on 10B, you'll have to upgrade up to 12B first before applying the 23A patch. I'll edit the main post to clarify that, sorry for not doing so earlier. I did just check and didn't see any direct patches from 10B available, unfortunately. If you need the OTA patches for 10B to 11C and then 11C to 12B, I can get those for you as files that you can then just apply manually.
Related
Updated 2/3/16 Master Download Link Added at Bottom of This Post For All Old and Current KDZ's
This method is confirmed working 100% for devices running 10b/11c/12b/23abc regardless of root/unlock state. While the .tot method is also working on Windows 7, users with Windows 8.1 are having difficulty using that method. Myself and @autoprime obtained a 10b KDZ file that has solved the issue for +10b updaters that couldn't flash back to 10b, so please send him some love for his help and for hosting the file on Team Codefire's servers for all to download. A big shout out to @quangnhut123 for creating the super sweet modified LG KDZ Flash Tool 2014 that makes KDZ flashing an absolute breeze!! He deserves some love as the previous KDZ flashing methods were anything but fun - especially on Windows 8. And another shout out to @deathsquad737 for initially testing the method for our device.
-Please this post and second post FULLY before asking questions!
-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: Downloads Located Below
-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 - now enjoy your corrected mistake and stop taking OTA's!!!
KDZ files rock, and are nice and easy to flash. No separate DLL files or changing ports either with the tool linked. If any other KDZ files become available in the future I will add them to this post along with any tool or flashing method changes. This thread will be solely kept for KDZ flashing for the VS985. I will also help as much as I can if you run into trouble, though I am not a Windows expert and actually only boot into it when I have to run programs like this....Linux MInt FTW!!
~KDZ Downloads~
-VS98510b_01.kdz: http://downloads.codefi.re/autoprime/LG/LG_G3/VS985 -Thanks to @autoprime
-Mirror for VS98510b_01.kdz (10b): https://mega.co.nz/#!7ERgXJbI!2KxATJt7q-HWvAPbTfVrT3wGuwPjWCw70N65MVlgfWg md5: d228ba692ef0c4704cba0b00fad8b8c
-VS98512b_00.kdz: https://www.androidfilehost.com/?fid=95916177934537134 -Thanks to @hokiealumnus for the AFH hosting
-Mirror for VS98512b_00.kdz (12b): https://mega.co.nz/#!7AwylQiZ!vK6rumjP0r1eP7lN37oeJ_cWLwal1DnriGDPUZGW1-0 md5: e8280b279d327b96689579a9eca22a3e
New download link to all KDZ files thanks to @roirraW "edor" ehT https://www.androidfilehost.com/?w=files&flid=35484
-For reference, here's @ins5736 thread for restoring using the .tot method: http://forum.xda-developers.com/verizon-lg-g3/general/restore-verizon-to-stock-t2827878 .
-Also there are reports of the tool deleting the KDZ you copied to the Flash Tool folder after the flash. I cannot confirm this, as it did not happen to me, but to be safe make sure you copy the file to the folder instead of pasting it so that you don't have to re-download the file for future use.
-Please note that the KDZ file we have is build # 10B.01, while the .tot file available is build # 10b.03. The only difference between the 2 files is that the .03 build is the actual released build that shipped with the phone, while the .01 kdz build was obviously a pre-released build. Its most likely some minor last minute changes/bloat added. We can't find any noticeable differences between the 2 builds.
-OTA's WILL FAIL USING THE 10b KDZ FILE WE HAVE due to a signing error with it being a pre-release. The purpose here is to downgrade, unlock, and flash whatever you want. This is NOT to return to an official stock state. You'll need to use the .tot file or the official LG Flash Tool that downloads the current build automatically in order to be in an official "stock" state. The 12b kdz is official and will allow OTA's
*Error Update* So with this leaked LP image, I've been playing with kdz'ing quite a bit and with a new Windows install I got to experience a few of the issues being reported by others that I have never seen, along with trying to troubleshoot some others. Did I manage to fix them easily you ask?? Hell yeah!
USB Disconnected Issue: This is a driver issue. Very easy fix, just download the latest Verizon drivers from the link I posted above and install them without phone plugged in. Power off phone, hold up, plug into usb and WAIT for download mode drivers to install (as stated several times in this thread). Click the balloon to watch the progress, this took about 10min on an i5/ssd machine - be patient. This is the predominant issue I think people are having. The drivers while in download mode are:
-USB Composite Device
-LGE Android phone or LGE AndroidNet for VZW USB Serial Port COM5 (this is the important one)
-CDC Serial or LGE AndroidNet for VZW USB Modem (this will fail if you are on a rom with certain VZW items removed - not a problem, its not needed)
-CDC ECM LGE AndroidNet for VZW NDIS Ethernet Adapter
If driver install fails, manually update them by pointing windows to the driver file you downloaded. I am not going any further here, use Google.
??????'s In The Field: easy, don't change region or language from Korean as stated in the OP. Leave it alone, it will flash in English I promise you. Result = all fields readable in English while running
Connection To Server Failed: Simple, ignore the window. Just drag it away, but don't close it. This is an offline hack originally indented to run online, deal with the window!
Progress Bar: The tool will initially analyze the phone, then when flashing starts, pay attention to the phone screen which will now say COM5. The blue progress bar on the phone is the important one. At around 80% on the tool screen, the phone will reboot. The flash is over and the bar will continue to progress into the 99% while rebooting - then the program will crash. You can disconnect now, you've been successful.
Thanks for the help and the new guide
WHATSAMATTA U ALUMNI
I'm getting a message saying "Path is too long or file problem" when adding the kdz. Any ideas?
droidiac13 said:
I'm getting a message saying "Path is too long or file problem" when adding the kdz. Any ideas?
Click to expand...
Click to collapse
Sounds like your linking the file path instead of directly copying the file right into the folder. Also try checking the file md5 with this one for the 10b kdz file: d228ba692ef0c4704cba0b00fad8b8ce
Don't Forget To Remove Previous LG FlashTool
When I first tried the method I was receiving a message "Path is too long or file problem". So I read through the instructions again. I failed to remove the previous LG FlashTool I was using. Once I uninstalled that program, everything went through without a problem. Thanks annoyingduck!!
I keep getting this and I installed all drivers. Any ideas? Thanks
Sent from my VS985 4G using XDA Free mobile app
kreep22 said:
I keep getting this and I installed all drivers. Any ideas? Thanks
Sent from my VS985 4G using XDA Free mobile app
Click to expand...
Click to collapse
Some basics to check first:
-Were you in download mode before executing the program?
-When you initialized download mode, did you wait to allow the download mode drivers to load before hitting start?
-Were all steps followed?
-Check cable, and try another one (this is very often the cause)
-Change usb port
-Don't use a 3.0 port, use a 2.0
Thanks for this excellent guide, Duck. Very simple to follow, well laid out, etc. I haven't actually done it yet, but I've got everything in place to do so (the flash tool, the KDZ file in the folder, etc.)
I assume once the downgrade is successful, just reroot with Stump, etc and wait for updates via the community?
Will future updates be available via this flash tool, or will they have to be flashed via TWRP? Sorry, I'm just now getting used to the LG G3 dev community, coming from an old GNEX.
Thanks!
continued error when trying ota
I have a problem. I was originally rooted without a custom recovery. I decided to try the ota and got the error message when trying to install. I then flashed this method (kdz) and got back to stock. I rerooted via stump and tried the ota again, failure. I then rewiped and kdz again, this time I did not root. Tried the ota again, no dice.
Any thought? I can flash the kdz fine and get phone to factory 10b but once I try to install the ota I still get the error.
killian1212 said:
I have a problem. I was originally rooted without a custom recovery. I decided to try the ota and got the error message when trying to install. I then flashed this method (kdz) and got back to stock. I rerooted via stump and tried the ota again, failure. I then rewiped and kdz again, this time I did not root. Tried the ota again, no dice.
Any thought? I can flash the kdz fine and get phone to factory 10b but once I try to install the ota I still get the error.
Click to expand...
Click to collapse
That's odd... You chose cse flash, not normal correct? Normal would not wipe your device and could definitely be the culprit for the ota failing. While cse mode is a complete wipe prior to flashing.
Correct. I did cse, full wipe. I dont know what's going on. I tried atleast 10 times from scratch. I still cant get the ota to install.
killian1212 said:
I have a problem. I was originally rooted without a custom recovery. I decided to try the ota and got the error message when trying to install. I then flashed this method (kdz) and got back to stock. I rerooted via stump and tried the ota again, failure. I then rewiped and kdz again, this time I did not root. Tried the ota again, no dice.
Any thought? I can flash the kdz fine and get phone to factory 10b but once I try to install the ota I still get the error.
Click to expand...
Click to collapse
annoyingduck said:
That's odd... You chose cse flash, not normal correct? Normal would not wipe your device and could definitely be the culprit for the ota failing. While cse mode is a complete wipe prior to flashing.
Click to expand...
Click to collapse
After using the method here to downgrade back to 10b and root. I too wasn't able to then S/W update to 11c using survival mode in SuperSU. I perform the OP procedures again and this time didn't root and still wasn't able to S/W update, kept getting error. So I used ---> [GUIDE][HOW TO][VS985] Restore Verizon to Stock to go all the way back. I'm now able to S/W update to 11c and keep root with survival mode set in SuperSU. I most humbly say that there may be a very slight issue with maybe the files here. I truly do appreciate the ability to return to 10b using this method after updating in the first place!
Thanks, ill try the other method and report back. wish me luck. Either way, a huge thanks to duck for the easy way to rerturn. I just wish kdz worked for future ota. It may be a file issue allowing us to revert to 10b but not then allowing future updates.
Use the kdz method then factory reset the device and see if that works.
I tried that. No dice.
annoyingduck said:
Use the kdz method then factory reset the device and see if that works.
Click to expand...
Click to collapse
I tried that as well.
gatorstew said:
Thanks for this excellent guide, Duck. Very simple to follow, well laid out, etc. I haven't actually done it yet, but I've got everything in place to do so (the flash tool, the KDZ file in the folder, etc.)
I assume once the downgrade is successful, just reroot with Stump, etc and wait for updates via the community?
Will future updates be available via this flash tool, or will they have to be flashed via TWRP? Sorry, I'm just now getting used to the LG G3 dev community, coming from an old GNEX.
Thanks!
Click to expand...
Click to collapse
Sorry, I missed this question. Yes, any future kdz's that become available will be updated here, along with any changes in flashing methods. Though it's pretty hard to beat the current tool that's available.
And yes, the idea here is to downgrade to 10b and be able to root, unlock, and flash anything you want. Still unclear as to why some want to take the 11c ota, but that's for another thread. The kdz method here is working where the tot was failing for some, and I personally think it's faster and easier to do than the tot method.
The third step might be clarified. Do you mean something like, "Power off your phone completely, then turn power on while also holding the volume up button..."?
markfm said:
The third step might be clarified. Do you mean something like, "Power off your phone completely, then turn power on while also holding the volume up button..."?
Click to expand...
Click to collapse
You should probably try it before trying to correct it.....
Nope, power off phone completely, hold volume up ONLY, plug in usb cable...it will auto power on into download mode
I have the Verizon LG G3 with build 12b installed (Was updated by the store when I purchased phone). Is there anyway to unlock the boot loader and root the device as is, or roll the device back to a previous build that is easily unlockable/rootable?
You should have posted in the q&a forum area.
Anyhow - if you want to root, and install a custom recovery (twrp), use the kdz method to get back to 10b:
http://forum.xda-developers.com/showthread.php?p=56484240
Then from this forum area install the bump/twrp from autoprime, and make sure to either freeze system updates or rename the two LGDMSClient files in /system/app. The freeze or rename is so new ota don't get pushed onto your phone after you get the custom recovery (twrp). Otherwise you'll needed the solution in the "stuck in custom recovery" thread:
http://forum.xda-developers.com/showthread.php?p=56061720
(It is handy to download the "stuck" zip onto your phone as a just-in-case. If you do get an ota, and your phone keeps booting to recovery, tell twrp to Install the zip to clear the ota files )
HTH!
I am trying that method now (actually before you replied) but the kdz file is taking for ever to download. Been running for 30 minutes and still showing 7 hours remaining. I have a really fast internet connection but that one file doesn't wanna download!
markfm said:
You should have posted in the q&a forum area.
Anyhow - if you want to root, and install a custom recovery (twrp), use the kdz method to get back to 10b:
http://forum.xda-developers.com/showthread.php?p=56484240
Then from this forum area install the bump/twrp from autoprime, and make sure to either freeze system updates or rename the two LGDMSClient files in /system/app. The freeze or rename is so new ota don't get pushed onto your phone after you get the custom recovery (twrp). Otherwise you'll needed the solution in the "stuck in custom recovery" thread:
http://forum.xda-developers.com/showthread.php?p=56061720
(It is handy to download the "stuck" zip onto your phone as a just-in-case. If you do get an ota, and your phone keeps booting to recovery, tell twrp to Install the zip to clear the ota files )
HTH!
Click to expand...
Click to collapse
Check post 150 in that thread. annoyingduck posted a second link
markfm said:
Check post 150 in that thread. annoyingduck posted a second link
Click to expand...
Click to collapse
I think I am in love with you, JK.....seriously though thanks a bunch....downloading the Mega link now and it seems to be going MUCH faster.
Did it work for you? I tried to downgrade, when phone said 100% it rebooted. I had a dark screen.... Went to the Verizon store, was told it was hard bricked. Haven't tried rooting my replacement yet.
Early adopter, got my phone in July, used the original ioroot, never had to revert.
The kdz method has had quite a few people who succeeded, based on what I read, no idea why it went bad for you. If you are gun shy, understandable, post 2 of annoying duck's thread has a link for the tot approach, supposed to be a slightly more pita way but not too exotic. Key is to flash any existing g3 drivers on your PC, install the proper things used by the tot method.
martinez5241 said:
Did it work for you? I tried to downgrade, when phone said 100% it rebooted. I had a dark screen.... Went to the Verizon store, was told it was hard bricked. Haven't tried rooting my replacement yet.
Click to expand...
Click to collapse
Anyway to downgrade without this happening? I want to run stock lollipop on my G3 but so far am stuck at the VS98512b update too
_AI_ said:
Anyway to downgrade without this happening? I want to run stock lollipop on my G3 but so far am stuck at the VS98512b update too
Click to expand...
Click to collapse
I did the kdz method. Omg you run the program and it starts don't click on any notifications, just let it run. Sorry about the late response.
Thanks to everyone over the past almost six years who helped me get to the point where I am so far. Glad to help others in what ways I can.
Thanks to @bweN diorD for his Verizon LG G3 VS985 repository. Inspired me to do this for the VK810.4G, although it took me six months of considering doing it before I was motivated enough to.
Thanks to @Papay346 for purchasing and testing the 22B_00 TOT file from a Chinese website, and for sharing it with us! His original post here http://forum.xda-developers.com/showpost.php?p=66089535&postcount=6.
I intend this as a repository for all OTA, .img, KDZ and TOT files relating to each official (and leaks if we ever find any, which will be indicated as unofficial/leak/whatever) LG release. If not noted otherwise, all files are official (unaltered from the official stock release).
The latest files will always be at the top with the oldest always at the bottom.
All downloads are available in my VK810.4G section on Android File Host in the OTA, IMG or KDZ and TOT subfolder. Below is merely a list of what's available there. If you don't know what to do with these, you don't need them.
36B_00 - Lollipop v5.0.2
KDZ: VK81036B_00-Lollipop_5.0.2_KDZ.7z
IMGs:VK81036B_00_5.0.2_system.img.7z
VK81036B_00_5.0.2_all_but_system.img.7zOTA: VK810.4G_altev_35A_08to36B_00_5.0.2_OTA.7z
35A_08 - Lollipop v5.0.2
KDZ: VK81035A_08 - Lollipop 5.0.2.KDZ - MD5 hash inside.7z
IMGs:VK81035A_08 5.0.2 system.img.7z
VK81035A_08 5.0.2 all but system.img.7zOTA: VK810.4G_altev_24A_00to35A_08_5.0.2_OTA.7z
24A_00 - KitKat 4.4.2
KDZ: VK81024A_00.KDZ - KitKat 4.4.2.7z
IMGs:Verizon LG G Pad 8.3 VK810.4G 24A system.img.7z
boot.img
modem.imgOTA: Not captured yet.
23A_04 - KitKat 4.4.2
KDZ: VK81023A_04.KDZ file with MD5 hash inside - NON-FLASHABLE - KitKat 4.4.2.zip
IMGs:VK810.4G Verizon LG G Pad 8.3 23A_04 system.img partition file.7z
VK810.4G Verizon LG G Pad 8.3 23A_04 other partition img files.7z
VK810.4G Verizon LG G Pad 8.3 23A_04 extracted from KDZ Web8064.dll - don't know if it's useful.7zOTA: Not captured yet.
22B_00 - KitKat 4.4.2 (TOT available)
TOT: VK81022B_00.TOT file with MD5 hash inside - KitKat 4.4.2.7z
DLL for TOT method: VK81022B_00-KitKat_4.4.2-Web8064.DLL_for_TOT_method.7z
KDZ: VK81022B_00.KDZ file with MD5 hash inside - KitKat 4.4.2.7z
IMGs:VK81022B_00_4.4.2_all_but_system.img_and_userdata.img.7z
VK81022B_00_4.4.2_system.img_only.7z
VK81022B_00_4.4.2_userdata.img_only-extracts_to_10.7GB.7zOTA: Not captured yet.
11A_01 - Jellybean 4.2.2
KDZ: VK81011A_01 - Jellybean 4.2.2.KDZ - MD5 hash inside.7z
IMGs:VK81011A_01_4.2.2_all_but_system.img.7z
VK81011A_01_4.2.2_system.img_only.7z
I confirm that this works.
How is this tool used to flash VK81023A_04.kdz?
D0M1N!X said:
I confirm that this works.
Click to expand...
Click to collapse
Every time I go to thank your post I happen to not be on TapaTalk and over my 8 Thanks limit. Thanks for confirming.
gehx said:
How is this tool used to flash VK81023A_04.kdz?
Click to expand...
Click to collapse
Hi! The page I linked to for [URL=" Flash Tool 2014 - Tools Offline KDZ Flash Rom for LG[/URL] has the directions and screenshots. I know the language is in Vietnamese. Google Chrome (at least on the PC, but I believe on Android too) will translate the word directions closely enough, and for what doesn't get translated because it's text in a picture won't matter because the screenshots make it pretty clear what to do. It's pretty easy, I've done it a couple of times.
I'm not seeing the link for the KDZ file on the page. I used the translate option but maybe I'm blind. I looked around and found this:
https://www.androidfilehost.com/?fid=95864024717073362
Is this the right file?
sefirosu0522 said:
I'm not seeing the link for the KDZ file on the page. I used the translate option but maybe I'm blind. I looked around and found this:
Is this the right file?
Click to expand...
Click to collapse
Yep, that's my file as you can tell by the MD5 hashes matching those in my post. My link is at the end of the line:
Any current and future files for this and other devices will be available in my section on Android File Host.
Click to expand...
Click to collapse
I'll try to make it stand out more. Thanks!
roirraW "edor" ehT said:
Yep, that's my file as you can tell by the MD5 hashes matching those in my post. My link is at the end of the line:
I'll try to make it stand out more. Thanks!
Click to expand...
Click to collapse
Thanks. So basically just to dumb it out. What I should be doing is:
Install the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe file.
Download and install the LG Flash Tool 2014.zip file.
Which files get copied into the KDZ 2014 LG Flash Tool folder?
Connect the phone to the computer. (Are we supposed to use ethernet mode ?)
LGFlashTool2014.exe
Does that sound right? Sorry for the dumb questions. I've set my G2 back a ton of times using the Verizon only method. I've never done it with the tablet and it seems like it's done differently.
Any help would be very appreciated.
sefirosu0522 said:
Thanks. So basically just to dumb it out. What I should be doing is:
Install the LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe file.
Download and install the LG Flash Tool 2014.zip file.
Which files get copied into the KDZ 2014 LG Flash Tool folder?
Connect the phone to the computer. (Are we supposed to use ethernet mode ?)
LGFlashTool2014.exe
Does that sound right? Sorry for the dumb questions. I've set my G2 back a ton of times using the Verizon only method. I've never done it with the tablet and it seems like it's done differently.
Any help would be very appreciated.
Click to expand...
Click to collapse
Just going by memory at the moment - I'm at work so I have to hurry. Yes, it all sounds right except the driver. If I remember correctly, the Verizon variant of the G3 uses a different set of drivers, I think it's mentioned on that LGFlashTool2014 page, right after it mentions the one you said. They're probably saying to copy the KDZ to the flash tool folder, but I think you can just browse to wherever you have it on the same PC from the tool anyway.
Yes, ethernet mode.
sefirosu0522 said:
Thanks. So basically just to dumb it out. What I should be doing is:
Click to expand...
Click to collapse
How'd it go?
Sent from my LG-VS985
roirraW "edor" ehT said:
How'd it go?
Sent from my LG-VS985
Click to expand...
Click to collapse
It was flawless. The only thing is that I did the CSE flash and I was able to root but I'm not sure how to get TWRP back. I tried following the thread but ran into issues. I can't remember what it was. So basically I did it twice and now I am fully stock unrooted.
sefirosu0522 said:
It was flawless. The only thing is that I did the CSE flash and I was able to root but I'm not sure how to get TWRP back. I tried following the thread but ran into issues. I can't remember what it was. So basically I did it twice and now I am fully stock unrooted.
Click to expand...
Click to collapse
That's good to hear!
To confirm that your steps of trying to root and put TWRP back on are the same as what I think:
1. Turn BOTH USB Debugging and (install from) Unknown Sources on.
2. Install and run Stump.apk (turn volume all the way down) and choose to brute force. Might take 10-20 minutes.
3. When Stump reports success, reboot when prompted, install SuperSU from the Play store, run SuperSU, install binaries and reboot again.
4. If it is or ever will be your intention for USB Debugging to stay on (for use with Titanium Backup, etc) between reboots, Stump creates a quirk where it doesn't stay selected between reboots. A known fix is to (if I remember correctly) plug the tablet into your PC, select Camera (PTP) mode, then re-select Media sync (MTP) mode. You might or might not have to already have USB Debugging re-checked during this - *shrug*.
5. While on the subject of Titanium Backup, I find that on recent versions of SuperSU (since it's been made Lollipop compatible and includes the "Mount namespace separation" option and it's checked by default), that I have to de-select "Mount namespace separation" in SuperSU's settings in order for Titanium Backup to work for restoring - perhaps backing up or other things as well. Reboot after changing that option in SuperSU.
6. Follow the directions at http://forum.xda-developers.com/showthread.php?t=2726707 to the letter, using the extracted zip of TWRP v2.7.0.1, then flashing 2.7.0.2 from 2.7.0.1 once booted into it.
Note that by "terminal", if I remember right, they mean the Terminal app on the rooted tablet - not Terminal under Linux or Command/PowerShell under Windows. Or it's the other way around, I really haven't done it quite enough times but I think I recall that it wasn't as convenient since I couldn't as easily copy and paste the necessary commands. Sorry for vagueness! Make sure USB Debugging is turned on for this, too.
roirraW "edor" ehT said:
That's good to hear!
To confirm that your steps of trying to root and put TWRP back on are the same as what I think:
6. Follow the directions at http://forum.xda-developers.com/showthread.php?t=2726707 to the letter, using the extracted zip of TWRP v2.7.0.1, then flashing 2.7.0.2 from 2.7.0.1 once booted into it.
Note that by "terminal", if I remember right, they mean the Terminal app on the rooted tablet - not Terminal under Linux or Command/PowerShell under Windows. Or it's the other way around, I really haven't done it quite enough times but I think I recall that it wasn't as convenient since I couldn't as easily copy and paste the necessary commands. Sorry for vagueness! Make sure USB Debugging is turned on for this, too.
Click to expand...
Click to collapse
Thank you. You've been extremely helpful with this. For step 6, are you talking about the instructions over at this thread?
http://forum.xda-developers.com/showthread.php?t=2726707
I thought that was only for 4.2.2.
sefirosu0522 said:
Thank you. You've been extremely helpful with this. For step 6, are you talking about the instructions over at this thread?
I thought that was only for 4.2.2.
Click to expand...
Click to collapse
You're welcome and thank you!
It's what I've used to put TWRP on, with 4.4.2 loaded, and make backups and restores.
roirraW "edor" ehT said:
You're welcome and thank you!
It's what I've used to put TWRP on, with 4.4.2 loaded, and make backups and restores.
Click to expand...
Click to collapse
Thanks again. I haven't tried this yet but I will soon.
I can confirm that the trick worked as noted in the VIET website. Thanks again.
joeminati said:
I can confirm that the trick worked as noted in the VIET website. Thanks again.
Click to expand...
Click to collapse
You're welcome!
I must be the only person who cannot understand the Vietnamese website....even when translated. I've attached images of what I get from Google, once translated. Yes, it's English, but it makes no sense. Any help would be appreciated.
ddodge68 said:
I must be the only person who cannot understand the Vietnamese website....even when translated. I've attached images of what I get from Google, once translated. Yes, it's English, but it makes no sense. Any help would be appreciated.
Click to expand...
Click to collapse
You can have the phone already in Download mode and attached when you start the LG Mobile 2014 tool. Personally (if the Android system is working), I leave the phone fully on and plug it into the PC. After all drivers load, I make sure the USB connection is set to MTP, or on 10B set it to Internet.
When you start the flash process in the tool, it'll reboot the phone into Download mode itself. Saves me some finger-wrangling plus coming from the Samsung Galaxy S2 & S3, I like to keep my presses of the power button to a minimum (because they would go bad on the Galaxy S2 & S3).
Leave all the settings exactly as pictured. CSE flash is what you want almost all the time. It's a complete wipe. Normal is like a dirty flash. If you're ever downgrading from a newer version to older version, you DEFINITELY want CSE, but you almost always want CSE anyway. Make a copy of the KDZ file and put it in the folder you extracted LG Mobile 2014 into. Use the button to the right on the first dialog to direct it to the KDZ file you just put in there.
On the screen with the language. Don't believe any instructions that say to leave it to Korean and that it'll still come out English. It doesn't. That doesn't affect actually flashing the phone but it's nice to understand the status messages, so change them appropriately. The rest is just as pictured.
If you have any specific questions beyond that, please ask.
VK810.4G altev Verizon LG G Pad 8.3 Stock 4.4.2 24A (4/5/2015) KDZ file
Added news that the build 24A KDZ file is available at my AFH link for posterity or at one of the two sources I downloaded it from, listed in the OP.
Thanks for always posting about the VK810. I feel like it gets no love!
Can this brick your phone/void your warranty? Of course it could! I wouldn't be posting it on XDA if it couldn't!
TeutonJon78 said:
Just be aware that once you unlock, you won't get anymore OTA updates at the current moment, and there's not full factory images to fall back on. They will still try to push OTAs if anyone does this bootloader unlock method, but they will always fail due to version checking.
Click to expand...
Click to collapse
So as it stands right now, if you do this, you're not going to get further updates from ZTE, unless they change their stance.
Here's a method that should work for any brave souls. It's the method I used so far.
My understanding is this update only makes the required patches to allow the command fastboot oem unlock to actually unlock the bootloader. That being said, I do not know for sure that this is not specific to my phone's IMEI. If someone would supply me with the file/link they get from using adb shell logcat > ota.txt while checking for updates, then grep ota.txt | ZDMLog (if you use linux) or do a find for https:// in ota.txt it would be useful for this verification.
For microSD card method:
Take this (Thanks DrakenFX) or this file and put it in /sdcard/, making sure extension is .zip
Enable OEM unlock from the settings->development menu.
Reboot phone (or boot phone) while pressing volume up. This will get you into stock recovery. From here, apply update from SD card, P996A01B20Fastboot_ssl.zip
No microSD card method:
This may also be possible without an SD card using the adb sideload option in stock recovery and "adb sideload P996A01B20Fastboot_ssl.zip" on your desktop. If you are successful using this method, send me a PM so I can update this post.
Now if you reboot into bootloader (which you can do right from recovery), you will hopefully find that "fastboot oem unlock" actually brings up the bootloader unlock prompt on your phone.
You should be able to verify to this point as per below.
Without using the fastboot oem unlock command I have not lost any user data (but it's still a good idea to back it up!) If you do unlock, you will lose your data!
This method requires 20B to already be installed, correct? If so, is there a way to sideload the 20B update (so one can go from launch firmware -> sideloaded 20B -> sideloaded 20B_boot)? Juuuust in case ZTE puts out a 20C or something that blocks sideloading and renders "unofficial" bootloader unlock attempts like this invalid.
xtermmin said:
This method requires 20B to already be installed, correct? If so, is there a way to sideload the 20B update (so one can go from launch firmware -> sideloaded 20B -> sideloaded 20B_boot)? Juuuust in case ZTE puts out a 20C or something that blocks sideloading and renders "unofficial" bootloader unlock attempts like this invalid.
Click to expand...
Click to collapse
It does require 20B to be installed. It appears 20B can sideloaded as well. The only error message I received was 20B expects 20160624 or 20160707 (and I'm now at 20160805). Maybe someone can try to sideload 20B on 20B?
So looking through the update script, it seems to check for SHA1 matches for certain parts of the boot, system and recovery partitions. I'm not sure if the patch itself has content specific to an IMEI or if this is just a simple check to make sure the phone has the correct build installed.
Looking at this, it seems the purpose of the part of the script before # ---- start making changes here ---- is used to verify a correctly configured system, with no apparent relation to the IMEI. It looks like the script itself is completely generic, and the checks could probably be removed so this will work on any build. Now we just need another update package to compare the other content (fastboot.img, patch\boot.img.p, patch\recovery.img.p) with to see if they're generic as well. This makes me wonder if flashing fastboot.img alone is enough, as that's what is used to interface with the bootloader unlock.
Helpful references:
Built-in functions in update binary
range_sha1
dennis96411 said:
So looking through the update script, it seems to check for SHA1 matches for certain parts of the boot, system and recovery partitions. I'm not sure if the patch itself has content specific to an IMEI or if this is just a simple check to make sure the phone has the correct build installed.
Looking at this, it seems the purpose of the part of the script before # ---- start making changes here ---- is used to verify a correctly configured system, with no apparent relation to the IMEI. It looks like the script itself is completely generic, and the checks could probably be removed so this will work on any build. Now we just need another update package to compare the other content (fastboot.img, patch\boot.img.p, patch\recovery.img.p) with to see if they're generic as well. This makes me wonder if flashing fastboot.img alone is enough, as that's what is used to interface with the bootloader unlock.
Helpful references:
Built-in functions in update binary
range_sha1
Click to expand...
Click to collapse
Man I hope so, then the rest of the world can get a bootloader unlock even if ZTE won't unlock the bootloader for us.....
Has anyone captured 20B and has it for others to try?
My phone won't come until next week (first wave of grays), but I'll try capturing it if it's not already installed. We just have to wait 5 days
rczrider said:
Has anyone captured 20B and has it for others to try?
My phone won't come until next week (first wave of grays), but I'll try capturing it if it's not already installed. We just have to wait 5 days
Click to expand...
Click to collapse
I think this is it: http://forum.xda-developers.com/showpost.php?p=68109239&postcount=5
There are no full system images available for the US model yet, unfortunately.
xtermmin said:
I think this is it: http://forum.xda-developers.com/showpost.php?p=68109239&postcount=5
There are no full system images available for the US model yet, unfortunately.
Click to expand...
Click to collapse
So in theory, the process would be to sideload the 20B update, reboot, then sideload the file in the OP?
Hopefully someone will get around to testing this method (or at least the OP's file) before my phone comes next week, but if not, I'll do it first thing.
rczrider said:
So in theory, the process would be to sideload the 20B update, reboot, then sideload the file in the OP?
Hopefully someone will get around to testing this method (or at least the OP's file) before my phone comes next week, but if not, I'll do it first thing.
Click to expand...
Click to collapse
In theory, yes (You could also update to 20B normally, but good to have it as a backup). Hopefully 20B_Boot is not device-specific.
xtermmin said:
In theory, yes (You could also update to 20B normally, but good to have it as a backup). Hopefully 20B_Boot is not device-specific.
Click to expand...
Click to collapse
I assume the most likely outcome is that it simply wouldn't flash. Even so, I'm willing to be a bit reckless as I can just return the phone for new one (via the retailer, not ZTE)
rczrider said:
I assume the most likely outcome is that it simply wouldn't flash. Even so, I'm willing to be a bit reckless as I can just return the phone for new one (via the retailer, not ZTE)
Click to expand...
Click to collapse
Haha same but never dealt with B&H so we'll see how that goes. Still waiting for the grey one.
---------- Post added at 09:17 AM ---------- Previous post was at 09:16 AM ----------
So everyone should update to B20 as soon as possible and then not update to anything else.
reddrago said:
Haha same but never dealt with B&H so we'll see how that goes. Still waiting for the grey one..
Click to expand...
Click to collapse
They're fantastic. 30-day (from delivery) no-questions-asked return policy on smartphones. If there's an actual problem with the phone, they'll even pay for return shipping. No restocking fee in either case.
If there is a problem with the phone itself, you can exchange it and the 30-day return policy resets from delivery of the replacement unit.
jkuczera said:
Reboot phone (or boot phone) while pressing volume up. This will get you into stock recovery. From here, apply update from SD card, P996A01B20Fastboot_ssl.zip
Click to expand...
Click to collapse
I was trying but Can't use " apply update from SDCard " but the "apply update from ADB " seems to be enable just didn't try cuz i don't have my laptop with me at the moment (till i get home) , check picture.
P.S. just to clear things up when i select "apply Update from SDCard" is when i get that message, so the ADB option is the only way for me to apply this and yes I'm in B20.
DrakenFX said:
I was trying but Can't use " apply update from SDCard " but the "apply update from ADB " seems to be enable just didn't try cuz i don't have my laptop with me at the moment (till i get home) , check picture.
Click to expand...
Click to collapse
Did you have an update file in /sdcard/ ? Since this is the stock recovery, I'm quite certain it's looking for a physical microSD for this usage scenario.
jkuczera said:
Did you have an update file in /sdcard/ ? Since this is the stock recovery, I'm quite certain it's looking for a physical microSD for this usage scenario.
Click to expand...
Click to collapse
Yep, have the P996A01B20Fastboot_ssl.zip in actually both internal and SDCard root directory, looks like apply Update from SDCard is block But apply update from ADB isn't (side loading)
DrakenFX said:
Yep, have the P996A01B20Fastboot_ssl.zip in actually both internal and SDCard root directory, looks like apply Update from SDCard is block But apply update from ADB isn't (side loading)
Click to expand...
Click to collapse
Try changing the filename to P996A01B20Fastboot_ssl.up. The direct-link from ZTE for the 20B update has that extension.
DrakenFX said:
Yep, have the P996A01B20Fastboot_ssl.zip in actually both internal and SDCard root directory, looks like apply Update from SDCard is block But apply update from ADB isn't (side loading)
Click to expand...
Click to collapse
It's got to be another issue altogether because I can pull up the SD card menu even if I don't have files in there.
jkuczera said:
It's got to be another issue altogether because I can pull up the SD card menu even if I don't have files in there.
Click to expand...
Click to collapse
I got this from the recovery log from the Recovery menu.
sd_upgrade_disable = 1
Check image
DrakenFX said:
I got this from the recovery log from the Recovery menu.
sd_upgrade_disable = 1
Check image
Click to expand...
Click to collapse
You're also getting a
Code:
get_oem_unlock_statut oem_unlock_enabled=0
that isn't looking good .
TeutonJon78 said:
See, it's bull**** like this that prevents OEMs from wanting to support third party development in the first place with things like bootloader unlocks. In the ZTE forums aren't you arguing that it's fair to not cover software related problems after unlocking, but here you are wanting them to cover that as well. B&H just charges the defective unit back to ZTE in the end.
Click to expand...
Click to collapse
It's all the same to ZTE in this instance because they will reflash their stock software upon return of the phone since it's not for a warranty repair.
djona12 said:
You're also getting a
Code:
get_oem_unlock_statut oem_unlock_enabled=0
that isn't looking good .
It's all the same to ZTE in this instance because they will reflash their stock software upon return of the phone since it's not for a warranty repair.
Click to expand...
Click to collapse
That's because i haven't been able to flash the file from OP and enable OEM after
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
This also what happened to me.
szophiya said:
I got a notification about a new software update, but no matter how much I try, the installation fails.
Is this normal, since I'm rooted? Or am I missing something?
I've rebooted a bunch of times but I still get a "Couldn't install system update" notification.
If I go to the settings, it says "Couldn't update" with "Installation problem" in red letters.
As the title says, the update version is 11.0.2.BE88CF. I've attached a screenshot for reference.
I'll appreciate any help. Thanks in advance.
Click to expand...
Click to collapse
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
JazzieBoi said:
https://android.googleapis.com/packages/ota-api/package/240680600a156993855db4474abfd98e3a9f89a3.zip
That's the link for the 11.0.2 BE88CF zip. It's for TMO devices though. Try performing a local upgrade by downloading that to your phone and moving the zip file to the root directory. Then go back into settings and system updates, press the gear icon on the top right. Click on the 2406...zip file. Hopefully that works.
Click to expand...
Click to collapse
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
arda99 said:
Incremental OTA expects stock partitions, so for a rooted phone, you need to follow the OTA survival guide, otherwise update will fail.
Unfortunately there is no local update option for metro, and very limited full ROM availability.
Click to expand...
Click to collapse
Wow I had no idea metro did that. I knew metro doesn't like unlocked bootloader's and are strict. I will never buy one in my life .
szophiya said:
Thank you for the link. I downloaded the file, but I can't perform the local upgrade because I can't find the gear symbol inside system updates. When I go to system update I still get the screenshot I added earlier.
Also, I still don't know what the problem with the installation is.
Click to expand...
Click to collapse
You could try flashing the stock boot.img via fastboot to see if it finishes installing. https://forum.xda-developers.com/attachments/boot-11-0-1-be88cf-img-zip.5399231/
You'll need to reboot to fastboot and then run: fastboot flash boot_a boot-11-0-1-be88cf-img and then fastboot boot_b (img filename). Try rebooting and performing the update then.
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Misclicked and did a double post, sorry.
szophiya said:
Well, quick update on this.
I've given up on updating. Either it's not working or, most likely, I'm doing something wrong which causes the process to fail. Thanks for the help to all who replied, though. I really appreciate it.
Click to expand...
Click to collapse
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
JazzieBoi said:
Hey, I'm sorry for the late reply but if you really want to upgrade to 11.0.2 maybe try MSM download tool to restore to OxygenOS 10. This will completely format your device though so backup everything including internal storage. https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/ Then once you're updated to 11.0.2 you could root again... I normally just unroot my phone update then reroot, but in your case that doesn't seem to be working.
Click to expand...
Click to collapse
The MSM you provided is for BE86AA and BE89BA, not for BE88CF which is what they need.
As far as I know, no MSM exists for BE88CF: https://forum.xda-developers.com/t/...8cf-11-0-2-be88cf-rooting-impossible.4367271/