Just got a security patch update today (11/2/15) from Verizon. About 24 MB. Froze the update as I'm stock rooted on 5.0.2 I may pull the trigger to see if I lose root. But before I do I wanted to see if anyone else received this update and can confirm if it may be the stagefright patch?
Doh! This should be in the VERIZON LG G2 forum. Apologies.
P.S. Thanks mods for moving this to the correct forum.
I'm also stock rooted and tried to get the OTA yesterday but failed (saw an error message "0x1111004" during install and nothing was modified.) Please let me know how it works with you. I'm not sure if this one is a stagefright patch but I found some discussions -- google "verizon lg g2 3aa".
Got the same error message. Can't seem to get the Software Upgrade Assistant to work either. Not in any rush. I may try a factory reset, try a clean update, and see if I can re-root this weekend if I have time.
tedyun said:
I'm also stock rooted and tried to get the OTA yesterday but failed (saw an error message "0x1111004" during install and nothing was modified.) Please let me know how it works with you. I'm not sure if this one is a stagefright patch but I found some discussions -- google "verizon lg g2 3aa".
Click to expand...
Click to collapse
It is the stagefright patch, I was able to install it with no issues. But they didn't patch CVE-2015-6602, all else is patched and I can't wait to get another phone soon.
Got error message as my G2 is rooted.
Yes it's the 3AA update. I went back to stock to get it, now I have all those apps I don't use. I'll have to root again so I can use Titanium to freeze apps.
Got 3AA OTA update working - kept root
striker59 said:
Got error message as my G2 is rooted.
Click to expand...
Click to collapse
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Jonstrong I will print this out for next time, thanks. Long involved process the way I did it, now in the process of freezing apps I don't use with Titanium after I rooted again.
Any idea how to get the Verizon security update when the Verizon phone uses a secondary carrier? (Net10/tracphone).
Alternately, is the security fix build into any of the LG G2 custom ROMs (like Xdabbeb's?)
My gf is using my old phone and complaining about the nagging update. I am not sure it is rooted but I think it is. Regardless, does the update block the root process?
Is it possible to manually install this update?
Help
i keep recieving this error when rooting using aviochs one click method is there any solution
ERROR: The system was unable to find the specified registry key or value.
I know LG has been plugging the root method. My G4 and x8.3 tab require root injection to the system.img.
jonstrong said:
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Click to expand...
Click to collapse
Jon, your instructions worked like a charm. The backup install-recovery_original.sh is located in the same directory as the one put there by SuperSU, /system/bin/. Thanks for doing the legwork!
jonstrong said:
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Click to expand...
Click to collapse
Thank you JonStrong!! Worked like a charm and no more nag! Much appreciated.
Do I need to go back to the "install-recovery.sh" I originally renamed?
superchaos said:
Thank you JonStrong!! Worked like a charm and no more nag! Much appreciated.
Do I need to go back to the "install-recovery.sh" I originally renamed?
Click to expand...
Click to collapse
In my case SuperSU notified me (after update was successful and rebooted) to update its binary, and it automatically replaced install-recovery.sh during the process.
jonstrong said:
Being rooted doesn't block the update. The update script checks a large number of files already installed on the phone, and if they don't match what is expected to be there prior to the update, the script exits and throws the error message.
Since you're rooted, if you don't have one already you can download an install file explore than is root capable and can also mount your file system read/write (several out there).
Browse to the System folder (with Root access)
Open the cache folder
Open the fota folder within the cache folder
Open the log folder within the fota folder
Assuming you had the upgrade error, you'll find a log file there - I don't recall the exact name, and now that I had a successful update the file appears to have been deleted, but it was something to do with "fota" with a file extension of "log". Open the file (it's a readable text file) and scroll to the bottom. You'll see a number of lines that trace the script's examination of each of multiple files, verifying that the right version is in place. In my case, "install-recovery.sh" was the wrong size, causing the script to abort with an error code -- with the update failing.
I did a bit of research, and learned that installing SuperSU (which is excellent) also caused the original install-recovery script to be backed up and replaced by a modified version. If you started by installing a current version of SuperSU, I believe the backed up version of the install-recovery script is still there and an uninstall of SuperSU (via it's own internal menu) will cause the original copy of install-recovery.sh to be replaced.
In my case, I didn't want to give up root - so instead of uninstalling SuperSU, I dug around a bit (don't remember if it was in system\etc or system\bin) and found "install-recovery_original.sh" -- which is the backup that SuperSU had created for me on installation. I backed up "install-recovery.sh" from the system\bin (just renamed it, actually) and dropped in a copy of the "install-recovery_original.sh" file and renamed it to "install-recovery.sh". BTW - I noted the the OEM file was something like 649 bytes, while the SuperSU version was 629 bytes (I think -- all from memory now).
Once I had the original file back in place, the OTA update worked just fine. I also checked: it's now running:
Software version: VS9803AA (Android 5.0.2)
Build number: LRX22G
Baseband version: VS9803AA-MPSS.DI.2.0.c2-00081-M8974AAAAANAZM-1
Kernel version: 3.4.0-perf-ga038154
Using Root Checker Pro after all this, I verified that I still have root, and busybox is still happily installed. No need to re-root the phone doing it this way. The OTA apparently does NOT unroot the phone.
If you're getting an error running the OTA (I think it was 11110004), that suggests that the install script ran into a non-OEM file (size or CRC didn't match). If you have the patience to find the log file and look at the bottom 10 or 15 lines, you can likely figure out which file it's choking on, and possibly figure out how to get the original / OEM file back in its place, after which the OTA will work.
- Jon
Click to expand...
Click to collapse
Thanks, that worked, but I screwed up. I did the rename, but I forgot to save a copy of the 649 byte version of the file. So when SuperSU updated its binary, it wiped out the file and I can't find where it backed it up (if it did.) Is there some way to get a copy of that for next time?
Hi,
Has anyone been using the hotspot provision fix/back with the new VS9803AA update? I successfully upgraded (brand new phone) then successfully rooted (using the LG One-click method). However, I think I messed up the hotspot mod. Now when I try to turn on Mobile Hotspot, it slides to "on" but nothing really happens (I don't get the antenna icon in the upper left status bar like usual) and I can slide the switch to "off." Hotspot Settings and everything can be accessed though.
Any ideas? Did I just screw up the file replacement?
Never mind.... It somehow started working oddly.
Hi My friends
Can anybody suggest any update file for CRR-UL00C433B114 version.. When we get the marshmallow upadate...:crying:
..
deleted
abishrajan said:
Hi My friends
Can anybody suggest any update file for CRR-UL00C433B114 version.. When we get the marshmallow upadate...:crying:
Click to expand...
Click to collapse
First of all thanks ,
Finally I got the update for CRR-UL00C433B114
Do the following steps
1) Download this file from the link below :
http://consumer.huawei.com/ae/support/downloads/detail/index.htm?id=71483
(May be just wait few seconds for the file need to display on site )
2) Extract that file and you get UPDATE.APP
3) Put UPDATE.APP file inside the dload folder of your SD card (If there is no dload folder create one folder and rename that to dload)
4) Go to settings - update and select local update. It will restart your mobile and install the updates
5) Now you are on CRR-UL00, Android5.1, EMUI 3.1, C433B146,
6) Now Go to your setting > updater > check for updates > you will be able to see the Android 6.0 OTA file and you can download and update to marshmallow.... Good luck :laugh::laugh::laugh:
abishrajan said:
First of all thanks ,
Finally I got the update for CRR-UL00C433B114
Do the following steps
1) Download this file from the link below :
http://consumer.huawei.com/ae/support/downloads/detail/index.htm?id=71483
(May be just wait few seconds for the file need to display on site )
2) Extract that file and you get UPDATE.APP
3) Put UPDATE.APP file inside the dload folder of your SD card (If there is no dload folder create one folder and rename that to dload)
4) Go to settings - update and select local update. It will restart your mobile and install the updates
5) Now you are on CRR-UL00, Android5.1, EMUI 3.1, C433B146,
6) Now Go to your setting > updater > check for updates > you will be able to see the Android 6.0 OTA file and you can download and update to marshmallow.... Good luck :laugh::laugh::laugh:
Click to expand...
Click to collapse
Thanks for Your Advice .
One question though does updating from B114 to B146 Wipe The data as in downloaded updates ??
andromodgod said:
Thanks for Your Advice .
One question though does updating from B114 to B146 Wipe The data as in downloaded updates ??
Click to expand...
Click to collapse
no it does not.
but this method not working for me (no Android 6.0 OTA)
jafarsalih said:
no it does not.
but this method not working for me (no Android 6.0 OTA)
Click to expand...
Click to collapse
if you have changed your localization, you won´t get the OTA Update.
Your IMEI is connected to one localization. This way every phone will receive the suitable update. If you have changed your localization (e.g. if you swapped from UL00C00BXXX to UL00C433BXXX) you won´t receive any OTA because the servers can´t find a suitable update for your IMEI/Build combination.
abishrajan said:
First of all thanks ,
Finally I got the update for CRR-UL00C433B114
5) Now you are on CRR-UL00, Android5.1, EMUI 3.1, C433B146,
6) Now Go to your setting > updater > check for updates > you will be able to see the Android 6.0 OTA file and you can download and update to marshmallow.... Good luck :laugh::laugh::laugh:
Click to expand...
Click to collapse
Can you share the OTA File ...
andromodgod said:
Can you share the OTA File ...
Click to expand...
Click to collapse
CRR-UL00 C433B146
http://consumer.huawei.com/ae/support/downloads/detail/index.htm?id=71483
i think he asked for the 6.0 ota file. not the B146
File step 1
Hi, please can you upload the file descriped in step 1. it is no longer available.
Hi guys, I have a quick question.
I want the newest Magisk version, to install every time I update my system, using CyanDelta. This however, requires that I manually move each update to the CyanDelta folder and edit the app setting to install the newest version with each update.
I would like to have a dummy zip, with an installer-script, that will use wild cards, to flash the newest magisk-**.zip
Something like
install("/sdcard/MagiskManager/Magisk-v****.zip")
Essentially, CyanDelta will "flash" this dummy zip. This dummy zip will then call the newest Magisk zip, to install.
Is this possible? Has anyone already done this? If so, mind linking me to the zip file already made (or the code already typed out)?
Alternatively, any tasker task to easily rename and move the latest update, automatically, once the new update is downloaded?
mkhcb said:
Hi guys, I have a quick question.
I want the newest Magisk version, to install every time I update my system, using CyanDelta. This however, requires that I manually move each update to the CyanDelta folder and edit the app setting to install the newest version with each update.
I would like to have a dummy zip, with an installer-script, that will use wild cards, to flash the newest magisk-**.zip
Something like
install("/sdcard/MagiskManager/Magisk-v****.zip")
Essentially, CyanDelta will "flash" this dummy zip. This dummy zip will then call the newest Magisk zip, to install.
Is this possible? Has anyone already done this? If so, mind linking me to the zip file already made (or the code already typed out)?
Alternatively, any tasker task to easily rename and move the latest update, automatically, once the new update is downloaded?
Click to expand...
Click to collapse
I dunno if a zip can call another zip...
However with Tasker... You can use RUN SHELL with a 'su -c' in front of the command to rename and move your magisk zip to your flashaftetupdate directory...
Then just call on it with your recovery
Sent from my Nexus 6 using Tapatalk