[FIRMWARE] Sprint LG G3 LS990 ZV6 TOT, OTA and .IMG's - Sprint LG G3

ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Thanks to an anonymous donor we now have the ZV6 TOT. I have broken down the TOT and also uploaded the individual partitions which can be flashed if rooted. Speaking of root... ZV6 blocks Stump Root. If you wish to use ZV6 and have root you must install Bump'd TWRP while on ZV4 then manually flash the ZV6 boot/modem/system partitions... OR you may be able to root on ZV4 then take the official ZV6 OTA update and keep root -- the OTA has NOT been pushed yet so it is too early to say for sure. Remember to NEVER take an OTA if you have modified your SYSTEM partition at all (xposed/tethermod/etc) OR if you have TWRP installed.
Changelog:
Google Security Patches
Qualcomm Security Patch
International Voice over WI-FI
Improve unlock algorithm when phone is in the pocket
Enhancements to the LG Home (Sluggish UI fix)
Enhancement to the compass application
Enhancement to the Auxiliary cable recognition.
Mobilize Device Content Caching - An application caches HTTP web and app data on the device (not the Network), making the retrieval of data faster and saving bandwidth on the network
--TOT (*.zip) can be downloaded *HERE*
Flash this TOT using the same method as ZV4. You will need to select "Board DL" in LG Flash, otherwise you will get stuck. After the TOT flashes it will reboot your phone into the "MiniOS".. unplug the USB cable and press and hold the power button on the phone then press on the "Normal Boot" option on your phones screen. You are now on stock ZV6. Remember... there is no root for ZV6 so do not flash ZV6 TOT unless you don't mind being without root.
--Individual ZV6 partitions to flash manually can be downloaded *HERE*
I am removing the system.img from Codefire but thanks to @budeone system.img has been mirrored HERE. Feel free to make more mirrors of system...
The bootloader does NOT need to be updated in order to use the ZV6 boot/modem/system images. It's completely optional to flash the bootloader files (aboot, sbl1, dbi, laf, factory, tz, rpm). To flash the boot, modem and system partitions manually someone can make some new flashable *.zips containing the partitions... OR you can use my "flash2" *.zips which can be found under the How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img section in my *[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually* thread. You simply stick any loose system.img and/or boot.img and/or modem.img on your internal sdcard and flash my premade flashable zips in TWRP to install them.
--ZV4-to-ZV6 OTA Update Zip can be downloaded *HERE*
You must have a stock recovery and stock system partition for this to work. Being rooted may be OK but if you've edited or removed apks or other files or edited the build.prop then OTA zip may fail the integrity check. Root may not stick thru OTA.. until someone confirms one way or the othe the risk is yours.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename zip file into update.zip
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Alternate Directions to skip using ADB (must have root):
1. Stick OTA zip file in the /cache directory
2. Power off and boot into stock recovery (vol down + power)
3. Select the Update from cache option... then select the update zip you placed in /cache
As mentioned above.. ZV6 blocks Stump Root. Bump is not blocked.. so as long as you have root with ZV4 you can manually update to ZV6 and keep Bump'd TWRP or flash any Bump'd kernel or rom. No anti-rollback has been added to this update either.. so downgrading to ZV4 works!
Click to expand...
Click to collapse

---

Autoprime. Thank you for your work. +1

---

I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.

---

Well, took me a bit to get back up and running... but yeah, not seeing much of a difference in this versus ZV4. (Well, except losing root since I'm impatient and flashed the TOT.)

---

Interesting any major changes or is it a security update

---

autoprime said:
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
​
Click to expand...
Click to collapse
I'll mirror when I get home from work today. Thanks man!

---

@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.

---

Warboy said:
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Click to expand...
Click to collapse
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
engine95 said:
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Click to expand...
Click to collapse
No issues downgrading. There'd be giant red letters everywhere otherwise. But I have now added a mention in the OP that specifies downgrading is still an option. :good:

---

ZV6 upgrade went just fine, as you stated. No problems using flash2 stuff and let TWRP save the root. It seems to upgrade the Home launcher as well as the contacts database. It also upgrades the Sprint data-sharing activity. In other words, ZVF6 works fine, but is not a big update.

---

Flashable zip should be up tonight. Tomorrow at latest.
http://forum.xda-developers.com/showthread.php?p=56937777

---

I have a working compass!
I flashed the modem.img first with no apparent change, then the system.img... Shazammm! After calibration, the compass seems to be accurate. This was the big flaw for me on an otherwise lovely device and now it seems to be working. Now I can look forward to a Lollipop update.

---

I pray it fixes the bluetooth. I have a Chrysler U Connect system and my G3 or a G3 Vigor for my girlfriend will not stay paired to the unit.

---

After unzipping the system.img zip, it's named "14-system.img".
I plan on using the "flash2" process of upgrading.
Do I need to rename "14-system.img" to just "system.img" for the flash2 procedure to work?
Thank you
EDIT: I went back and re-read Auto's manual update procedure and can confirm, yes, I do need to rename "14-system.img" to "system.img"

---

autoprime said:
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
Click to expand...
Click to collapse
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH

---

Warboy said:
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Click to expand...
Click to collapse
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls

---

autoprime said:
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
Click to expand...
Click to collapse
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ

---

Warboy said:
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Click to expand...
Click to collapse
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.

---

autoprime said:
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
Click to expand...
Click to collapse
Should it be Flash2 not flash2

---

thznutz87 said:
Should it be Flash2 not flash2
Click to expand...
Click to collapse
I tried having a capital F and that didn't change anything.

---

system.7z
https://mega.co.nz/#!G0onwR5T!QV-NZ2hpAIllAX9tKCNBDkGLyE7AWD241Stws-c6y18