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,
I followed the instructions to convert L09 to Middle Eastern & North and South Africa version and it all worked well for me, but I'm wondering how do I convert to Chinese version? Can anyone help with some information?
Like do i just need to edit the build.prop and have the correct regions update.app file? or is something else necessary.
Thanks in advance
Gavin
brumgav said:
Hi,
I followed the instructions to convert L09 to Middle Eastern & North and South Africa version and it all worked well for me, but I'm wondering how do I convert to Chinese version? Can anyone help with some information?
Like do i just need to edit the build.prop and have the correct regions update.app file? or is something else necessary.
Thanks in advance
Gavin
Click to expand...
Click to collapse
So I managed to convert to Chinese version. This is how I did it.
While fresh in the memory, instructions on how to change the region+ firmware to UL00
What do you need (links in 004's original post earlier in the thread or here:
1. Firmware UL00-C433B114 (Middle East, North and South Africa)
2. The oeminfo.img program to change the locale (45.69 KB) Anti-Virus may or complain, so disable it)
3. Mounted on the phone ES Explorer (Solid or Root Explorer will not work !!!)
4. You need a copy of your existing ROM versions recovery.img. You can get this using the Huawei ROM extractor tool.
What to do:
1. Flash TWRP Recovery through Fastboot (Bootloader must be unlocked)
2..Get Root (install SuperSU.zip through TWRP), reboot.
3. Install and enable root in settings of ES Explorer and go to the folder /dev/block/platform/hi_mci.0/by-name/
4. Copy oeminfo file and transfer it to your computer
5. On your computer, unpack the oeminfo.exe program from the RAR. Put your oeminfo file in the same folder.
6. Rename oeminfo in oeminfo.img
7. Run oeminfo.img.exe and type hw / meafnaf replacing dualcu / cn - click apply
8. Rename oeminfo.img back to oeminfo and copy to your mobile phone
9. Replace the original file in the phone to change (overwrite)
10. Go to the phone / system / and open the file build.prop
11. Find the line ro.build.displey.id = change your version to "=" CRR-UL00C433B000 and save changes
EDIT ?: These steps (10/11) MUST be completed or it will not allow you to update later with new regions ROM
12. Extract the new ROM file on your computer with the firmware.
13. Copy dload folder with the Update.app file and copy it to the phone's internal memory or MicroSD card
14. Flash back stock recovery from your existing ROM (use the extractor tool if needed). You can do this now or at the end before flashing but you must remove TWRP and ROOT before attempting to flash new rom.
15. On the phone go Settings - Update.
16. Select Menu - Local update
I then ensured Google Play was installed.
After doing this, flashed TWRP again and Rooted the phone, I then edited the oeminfo file using the above method, changing the attribute back to "dualcu/cn". After this I edited the build.prop to using the above method but this time I changed "ro.build.display.id=CRR-UL00C00B131".
I then removed root and flashed the original Huawei recovery, and then rebooted and went to update settings. I searched for update and a new file was found however a modified system was detected so it offered to download a full version which was the B160 build. This downloaded and then updated and now I have CRR-UL00C00B160 version
Whats the advantage of this Version?
There are more updates to the Chinese version..they are on build B160 whereas UK still on build B144.
Some other features like dual SIM should work however I haven't tested this.
Other things like build in virus scanner, permissions manager and also the ability to set the date of your mobile data plan to help keep track of data usage and allowance.
Pressure sensitive screen is also featured although not yet used in any apps but maybe it will be enabled soon by Huawei
brumgav said:
So I managed to convert to Chinese version. This is how I did it.
While fresh in the memory, instructions on how to change the region+ firmware to UL00
What do you need (links in 004's original post earlier in the thread or here:
1. Firmware UL00-C433B114 (Middle East, North and South Africa)
2. The oeminfo.img program to change the locale (45.69 KB) Anti-Virus may or complain, so disable it)
3. Mounted on the phone ES Explorer (Solid or Root Explorer will not work !!!)
4. You need a copy of your existing ROM versions recovery.img. You can get this using the Huawei ROM extractor tool.
What to do:
1. Flash TWRP Recovery through Fastboot (Bootloader must be unlocked)
2..Get Root (install SuperSU.zip through TWRP), reboot.
3. Install and enable root in settings of ES Explorer and go to the folder /dev/block/platform/hi_mci.0/by-name/
4. Copy oeminfo file and transfer it to your computer
5. On your computer, unpack the oeminfo.exe program from the RAR. Put your oeminfo file in the same folder.
6. Rename oeminfo in oeminfo.img
7. Run oeminfo.img.exe and type hw / meafnaf replacing dualcu / cn - click apply
8. Rename oeminfo.img back to oeminfo and copy to your mobile phone
9. Replace the original file in the phone to change (overwrite)
10. Go to the phone / system / and open the file build.prop
11. Find the line ro.build.displey.id = change your version to "=" CRR-UL00C433B000 and save changes
EDIT ?: These steps (10/11) MUST be completed or it will not allow you to update later with new regions ROM
12. Extract the new ROM file on your computer with the firmware.
13. Copy dload folder with the Update.app file and copy it to the phone's internal memory or MicroSD card
14. Flash back stock recovery from your existing ROM (use the extractor tool if needed). You can do this now or at the end before flashing but you must remove TWRP and ROOT before attempting to flash new rom.
15. On the phone go Settings - Update.
16. Select Menu - Local update
I then ensured Google Play was installed.
After doing this, flashed TWRP again and Rooted the phone, I then edited the oeminfo file using the above method, changing the attribute back to "dualcu/cn". After this I edited the build.prop to using the above method but this time I changed "ro.build.display.id=CRR-UL00C00B131".
I then removed root and flashed the original Huawei recovery, and then rebooted and went to update settings. I searched for update and a new file was found however a modified system was detected so it offered to download a full version which was the B160 build. This downloaded and then updated and now I have CRR-UL00C00B160 version
Click to expand...
Click to collapse
Hello, could you please tell me why do you write (type) in step 11. CRR-UL00C433B000 instead of CRR-UL00C433B114? Thanks for your answer.
MoritzSu said:
Hello, could you please tell me why do you write (type) in step 11. CRR-UL00C433B000 instead of CRR-UL00C433B114? Thanks for your answer.
Click to expand...
Click to collapse
you need to set your build.id to B000 so you can update to B114 with an full update package in the EMUI Update app
Tuerkay said:
you need to set your build.id to B000 so you can update to B114 with an full update package in the EMUI Update app
Click to expand...
Click to collapse
Thanks for your soon answer. To say the truth, i have just completed the process. Unfortunately, i wrote (in my case) CRR-L09C432B114 instead of CRR-L09C432B000; my device ist just running with this B114 Rom. I was running the B119 Rom before, what should i do now in order to receive the updates?
MoritzSu said:
Thanks for your soon answer. To say the truth, i have just completed the process. Unfortunately, i wrote (in my case) CRR-L09C432B114 instead of CRR-L09C432B000; my device ist just running with this B114 Rom. I was running the B119 Rom before, what should i do now in order to receive the updates?
Click to expand...
Click to collapse
if you have changed your localization ( the "Cxxx" part) then you won´t receive any updates. You have to manualy update via Update.APP files.
Your IMEI is linked to you Build/Localization. This way, Huawei makes sure that every phone receives the right update file. If you change one of both, you won´t receive OTA updates anymore, since the update system can´t assign the "right" update file.
Anyone can confirm the dual sim function work after this procedure?? This I want a dual sim active dfsa
it does not, EU Mate S does not have dual-dim hardware
brumgav said:
7. Run oeminfo.img.exe and type hw / meafnaf replacing dualcu / cn - click apply
Click to expand...
Click to collapse
Anybody know, where to get this information from?
if I want to change to any other region where can I find the correct information for the OEMINFO.IMG?
Sventastic said:
Anybody know, where to get this information from?
if I want to change to any other region where can I find the correct information for the OEMINFO.IMG?
Click to expand...
Click to collapse
Sorry I don't know
Please share file oeminfo Dual Sim CRR-UL00 any region (hw/meafnaf or dualcu/cn)
Hi Everyone!
I followed the instructions to upgrade to Nougat from MM, this includes a file named update_data_full_hw_la.zip
http://ministryofsolutions.com/2017/01/huawei-p9-plus-vie-l29-nougat-b354-latin-america.html
The step that I cant seem to install this file, I tried:
Renaming file to update.zip and try to apply it through forced update (DIDNT WORK)
Extract all the content into dload folder (DIDNT WORK)
The content has an UPDATE.APP file and multiple folders. The forced update goes really fast and does not seem to install anything.
The ROM itself does not have many apps so I guess this zip should have everything else that is missing from the ROM but I cant seem to install it properly.
Any help on this? How am I supposed to install it?
jeinnerabdel said:
Hi Everyone!
I followed the instructions to upgrade to Nougat from MM, this includes a file named update_data_full_hw_la.zip
http://ministryofsolutions.com/2017/01/huawei-p9-plus-vie-l29-nougat-b354-latin-america.html
The step that I cant seem to install this file, I tried:
Renaming file to update.zip and try to apply it through forced update (DIDNT WORK)
Extract all the content into dload folder (DIDNT WORK)
The content has an UPDATE.APP file and multiple folders. The forced update goes really fast and does not seem to install anything.
The ROM itself does not have many apps so I guess this zip should have everything else that is missing from the ROM but I cant seem to install it properly.
Any help on this? How am I supposed to install it?
Click to expand...
Click to collapse
try the alternative method:
Alternative Method
Remove update files from your phone, if you have copied before
Download Huawei updater from This Link
Download latest Hisuite from official huawei website
Open huawei update, tick in custom rom, in custom rom version type VIE-L29C605B354
In Custom rom URL copy this link http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1257/g104/v71996/f1/
Then tick custome port, don’t change it.
now connect your phone with pc and make sure Hisuite recognize and connected properly. then just open Hisuite menu and change network settings as shown in image below.
Easy-Nougat-Update-2.png
Then in hisuite click check for update
it should start downloading and installing firmware
Thanks, but that method won't work as the ROM itself was already applied, therefore, HiSuite returns a message saying that I'm on the most updated version.
The file m trying to apply should contain apps like the calculator, Bluetooth, compass, etc. These apps are not part of the ROM but they come on a separate zip file.
The issue seems to be that apps are not compatible with the Nougat ROM already installed.
Any other thoughts?
If any of you has an update zip containing all remaining apps, please share!
The problem u are facing could be 2. Cust and oeminfo but fitting the package and /of rom. And the two packages need to be installed immediately with starting with the hw update, after that the normal one. Tell me which version and cust we are talking about?