• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root OTA update coming back weeks later after already installing?

K

koolsk8ter111

Android Enthusiast
I get a notification to update my L9, I download and install it, the phone reboots after the installation, and then weeks later the notification comes back telling me to update the phone, like a strange loop. It's almost as if the phone pretends to truly update, and after the installation, I go into the settings to make sure I have the latest version of the software, and it tells me my software is up to date, that is until weeks later the OTA notification comes back again.

It has something to do with rooting the phone I am sure since that is usually when I have that problem, but I don't want to have to factory restore the phone, because I believe that un-rooting will not help by itself. It seems to be tied with Clockworkmod. The Clockworkmod is not compatible with my phone and when I attempt to get into recovery mode to factory restore my phone. When I tried installing a recovery through rom manager, or backed up my rom, it shows a picture of an android robot thingy under maintenance lying down like this: http://farm9.staticflickr.com/8298/7885263992_1b0cd197d3_n.jpg, also updating via OTA when the phone rebooted shows the little android thingy like that too. I had installed rom manager to see if I could flash my phone that way since I am having issues flashing via computer and LG software. I changed my mind on installing/flashing roms, and just gave up on it all together, but just attempted to update stock OTA firmware to see if it fixes some of my phone issues, and I can't since the update keeps coming back and won't truly update my phone. I no longer have rom manager btw.

I need to know how to be able to update my phone via stock OTA without the update notification coming back again. I just found out I had a clockworkmod folder on my SD and deleted it. Would that fix it or is there something else I should do, uninstall/remove, or something so that I could make sure my phone can update?
 
Hey koolsk8ter111,

Just wanted to chime-in with my thoughts (disclaimer though: I don't own an LG Optimus L9, but am responding generically to your OTA issues).

I'm guessing by the information you provided that your OTA installations are actually not succeeding because you have a custom recovery installed.

You're seeing it come back because the installation actually never succeeded.

One common and very important feature of an OTA installation is a self verification / validation check that various files and partitions, including the all-important recovery partition, matches the ones expected and needed by the OTA itself so that it doesn't try to patch files that do not match versions.

Also, I've moved your thread over to the all-things-root sub-forum for you.

Cheers and best of luck!
 
koolsk8ter111 said:
I get a notification to update my L9, I download and install it, the phone reboots after the installation, and then weeks later the notification comes back telling me to update the phone, like a strange loop. It's almost as if the phone pretends to truly update, and after the installation, I go into the settings to make sure I have the latest version of the software, and it tells me my software is up to date, that is until weeks later the OTA notification comes back again.

It has something to do with rooting the phone I am sure since that is usually when I have that problem, but I don't want to have to factory restore the phone, because I believe that un-rooting will not help by itself. It seems to be tied with Clockworkmod. The Clockworkmod is not compatible with my phone and when I attempt to get into recovery mode to factory restore my phone. When I tried installing a recovery through rom manager, or backed up my rom, it shows a picture of an android robot thingy under maintenance lying down like this: http://farm9.staticflickr.com/8298/7885263992_1b0cd197d3_n.jpg, also updating via OTA when the phone rebooted shows the little android thingy like that too. I had installed rom manager to see if I could flash my phone that way since I am having issues flashing via computer and LG software. I changed my mind on installing/flashing roms, and just gave up on it all together, but just attempted to update stock OTA firmware to see if it fixes some of my phone issues, and I can't since the update keeps coming back and won't truly update my phone. I no longer have rom manager btw.

I need to know how to be able to update my phone via stock OTA without the update notification coming back again. I just found out I had a clockworkmod folder on my SD and deleted it. Would that fix it or is there something else I should do, uninstall/remove, or something so that I could make sure my phone can update?
Click to expand...

This is a very common problem... It you do have a custom recovery installed and it's rooted then the ota update will fail and you will see the same image that you posted. You would need to return completely to stock for the ota update to work. When you try to install the ota update and it fails... It will then take a few days or a week or so to recognize the ota update is available again. If you want to install the update then like I said you need to return to the stock version for your device and remove the custom recovery and root.
If you have a P769 or MS769 variant and want to disable the ota update notification then you can flash the kuma82 v10F.zip update removal patch. Download it and then flash it through your custom recovey, scroll down to the update 3 section in the OP here- Themed ROM (*769) for locked bootloaders' - xda-developers

Edit: you could also download the ota and then use scary alien's "OTA Verifier App" (which is awesome!) to scan and check to see if the ota is actually able to install the ota on your current devices setup. Just look in scary alien's signature for the apps link.
 
xdrc45 said:
This is a very common problem... It you do have a custom recovery installed and it's rooted then the ota update will fail and you will see the same image that you posted. You would need to return completely to stock for the ota update to work. When you try to install the ota update and it fails... It will then take a few days or a week or so to recognize the ota update is available again. If you want to install the update then like I said you need to return to the stock version for your device and remove the custom recovery and root.
If you have a P769 or MS769 variant and want to disable the ota update notification then you can flash the kuma82 v10F.zip update removal patch. Download it and then flash it through your custom recovey, scroll down to the update 3 section in the OP here- Themed ROM (*769) for locked bootloaders' - xda-developers

Edit: you could also download the ota and then use scary alien's "OTA Verifier App" (which is awesome!) to scan and check to see if the ota is actually able to install the ota on your current devices setup. Just look in scary alien's signature for the apps link.
Click to expand...
I do not have any custom rom on my phone, I installed recoveries, but I believe I removed them from the rom manager, un-rooted and factory restored my phone, then I updated, and now it's still giving me the notification over and over. Is there a simple way to get rid of this issue?

Keep in mind my phone (MS769) isn't compatible with the custom roms, and when I installed the recoveries, like i said I believe I managed to remove them since they don't really work with my phone's software, so I am on still on stock. I just gave up on rom manager, even though I just installed it to double check if it detected I had some sort of recovery installed. The rooting app I have is SuperSU.
 
koolsk8ter111 said:
I do not have any custom rom on my phone, I installed recoveries, but I believe I removed them from the rom manager, un-rooted and factory restored my phone, then I updated, and now it's still giving me the notification over and over. Is there a simple way to get rid of this issue?

Keep in mind my phone (MS769) isn't compatible with the custom roms, and when I installed the recoveries, like i said I believe I managed to remove them since they don't really work with my phone's software, so I am on still on stock. I just gave up on rom manager, even though I just installed it to double check if it detected I had some sort of recovery installed. The rooting app I have is SuperSU.
Click to expand...

The custom recoveries do work with you phone.. They just can't install custom ROMs. If when you boot your phone and the keys light up and flash continuously for a few seconds then you still have a custom recovery installed. The proper method for removing the customer recovery from your phone, if you installed it with the "L9 recovery installer" -

Is to use a root browser and go in and

1.Delete /system/bootstrap directory
2.Delete /system/bin/e2fck
3.Rename /system/bin/e2fck.bin to e2fck

I'm not 100% sure if ROM manager does this properly.
You may still be on a stock rom., but with a custom recovery, root and BusyBox installed on the device then you have modified system files on the device and the ota update will fail.

Edit:
If you still find out that you have a custom recovery installed then you can still flash the kuma82 v10F.zip ota update removal patch even though you don't have a custom ROM installed. Technically kuma82's ROM is just a stock modified ROM for locked bootloaders.

Alternatively you can also use Titanium backup to freeze the "com.lge.lgfota.permission" and or you can also use a root browser and then go into and change the "lgfota.apk" (LG firmware Over the Air) by going into the \system\app folder and renaming it to "lgfota.bak" and setting the permissions to 775, save your changes and then reboot the device. Then you won't be troubled with the OTA update notification any more. You can always rename it back to the original "lgfota.apk" with a root browser and it will now be back to normal and you will continue to receive your OTA notifications again.

Edit:
I really don't think the update was actually applied to your phone. You can always check this though by going into - System Settings/About Phone/Software Information/ and then look at the "Software Version" and it will tell you what version you have installed. eg,
LGMS76910e or it was updated to the most current version it will say LGMS76910f
 
xdrc45 said:
The custom recoveries do work with you phone.. They just can't install custom ROMs. If when you boot your phone and the keys light up and flash continuously for a few seconds then you still have a custom recovery installed. The proper method for removing the customer recovery from your phone, if you installed it with the "L9 recovery installer" -

Is to use a root browser and go in and

1.Delete /system/bootstrap directory
2.Delete /system/bin/e2fck
3.Rename /system/bin/e2fck.bin to e2fck

I'm not 100% sure if ROM manager does this properly.
You may still be on a stock rom., but with a custom recovery, root and BusyBox installed on the device then you have modified system files on the device and the ota update will fail.

Edit:
If you still find out that you have a custom recovery installed then you can still flash the kuma82 v10F.zip ota update removal patch even though you don't have a custom ROM installed. Technically kuma82's ROM is just a stock modified ROM for locked bootloaders.

Alternatively you can also use Titanium backup to freeze the "com.lge.lgfota.permission" and or you can also use a root browser and then go into and change the "lgfota.apk" (LG firmware Over the Air) by going into the \system\app folder and renaming it to "lgfota.bak" and setting the permissions to 775, save your changes and then reboot the device. Then you won't be troubled with the OTA update notification any more. You can always rename it back to the original "lgfota.apk" with a root browser and it will now be back to normal and you will continue to receive your OTA notifications again.

Edit:
I really don't think the update was actually applied to your phone. You can always check this though by going into - System Settings/About Phone/Software Information/ and then look at the "Software Version" and it will tell you what version you have installed. eg,
LGMS76910e or it was updated to the most current version it will say LGMS76910f
Click to expand...
My version currently is LGMS76910e, it stays that way after the update installation. The key lights do not flash continuously when booting the phone, it boots up normally. Also, there's a folder that you told me to delete in the root browser that doesn't exist I don't think "/system/bootstrap directory".


Oh! And I just realized, I swapped the external SD storage with my internal memory using a program called External 2 internal, so I could use my my SD card for storing apps and such and increase space, since the L9 gets only just over a gb for storage. I am wiping out my whole phone right now, and I should probably undo the memory swap, then update the phone. Things probably got confused, and the phone was probably updating from the sd card or vise versa.
 
If you are still rooted, take a peek at your /cache/recovery/last_log and other *log* files in the /cache/recovery folder.

Those files will tell you exactly why your OTA installation is failing.

Post 'em up here if you can and we'll take a look at them with you.
 
scary alien said:
If you are still rooted, take a peek at your /cache/recovery/last_log and other *log* files in the /cache/recovery folder.

Those files will tell you exactly why your OTA installation is failing.

Post 'em up here if you can and we'll take a look at them with you.
Click to expand...
I usually un-root before I factory restore, and I once factory restored before I un-rooted on accident and that caused a load of problems for me. Problems like not getting stock apps back (bloatware), and some bugs I think may have been caused by previously rooting/apps installed that messed with my device. It successfully factory restores, but at the cost of not getting everything back such as the bloatware, and why that bothers me a bit, is because that's a sign that the phone isn't starting out fresh like how you should get it at the store.

I'll try to get the logs, but do I find them in any generic file manager or do I need the root browsers?
 
koolsk8ter111 said:
I'll try to get the logs, but do I find them in any generic file manager or do I need the root browsers?
Click to expand...

You typically need root access to see things in the /cache/recovery directory, but I've seen some devices that do not.

Here's what things look like on my N5:

Code: 
shell@hammerhead:/ $ [B][COLOR="Blue"]ll /cache/recovery[/COLOR][/B]
ll /cache/recovery
/cache/recovery: Permission denied
1|shell@hammerhead:/ $ [COLOR="blue"][B]su[/B][/COLOR]
su
root@hammerhead:/ # [COLOR="blue"][B]ll /cache/recovery[/B][/COLOR]
ll /cache/recovery
-rw-r--r-- root     root            0 1970-01-28 16:55 last_install
-rw------- root     root            5 1970-01-25 23:37 last_locale
-rw-r----- root     root       164699 1970-01-28 16:55 last_log
-rw-r----- root     root       165998 1970-01-28 13:07 last_log.1
-rw-r----- root     root       573643 1970-01-27 13:55 last_log.2
-rw-r----- root     root         6578 1970-01-25 22:41 last_log.3
root@hammerhead:/ #

The "last_log" file should contain the goodies, but I'm guessing they roll-over after every reboot, so grabbing them all would be a good idea.

edit: oh, you'd want to grab these files soon (preferably immediately) after one of your OTA installation sessions so we can be sure that one of them will contain the information about what's going on.
 
Just another thought... But usually when you flash a custom recovery on a device it will actually overwrite the stock or any existing recovery that was already installed on the recovery partition. If this is the case then that maybe one of the issues with the OTA failing.
The only way I know how to restore the stock recovery on the L9 would be to either flash the device back to 100% stock using the offline kdz flash method or the official LG mobile tool.
Anther possible way would be to download your device specific kdz and use a tool - LG firmware bin extractor, which extracts the L9 kdz into images and then extract the stock recovery.img and then flash it to your L9 using fastboot.
 
scary alien said:
You typically need root access to see things in the /cache/recovery directory, but I've seen some devices that do not.

Here's what things look like on my N5:

Code: 
shell@hammerhead:/ $ [B][COLOR="Blue"]ll /cache/recovery[/COLOR][/B]
ll /cache/recovery
/cache/recovery: Permission denied
1|shell@hammerhead:/ $ [COLOR="blue"][B]su[/B][/COLOR]
su
root@hammerhead:/ # [COLOR="blue"][B]ll /cache/recovery[/B][/COLOR]
ll /cache/recovery
-rw-r--r-- root     root            0 1970-01-28 16:55 last_install
-rw------- root     root            5 1970-01-25 23:37 last_locale
-rw-r----- root     root       164699 1970-01-28 16:55 last_log
-rw-r----- root     root       165998 1970-01-28 13:07 last_log.1
-rw-r----- root     root       573643 1970-01-27 13:55 last_log.2
-rw-r----- root     root         6578 1970-01-25 22:41 last_log.3
root@hammerhead:/ #

The "last_log" file should contain the goodies, but I'm guessing they roll-over after every reboot, so grabbing them all would be a good idea.

edit: oh, you'd want to grab these files soon (preferably immediately) after one of your OTA installation sessions so we can be sure that one of them will contain the information about what's going on.
Click to expand...
It's been hours since I updated the phone, but I could give you my logs in a text form. Here it is:

...................................................................................................



Starting recovery on Mon May 5 12:43:12 2014
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache (null) 0
3 /system ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/system (null) 0
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/misc (null) 0
5 /persist ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/persist (null) 0
6 /mlt ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/mlt (null) 0
7 /dvp ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/divxkey (null) 0
8 /ve ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/ve (null) 0
9 /boot emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/boot (null) 0
10 /recovery emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery (null) 0

I:Boot command: boot-recovery
I:Got arguments from /cache/recovery/command
framebuffer: fd 4 (540 x 960)
[RAINEDAY]Display_Width = 540
[RAINEDAY]bnr_recovery = 0, bnr_recovery_s = 0
backup_img = /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip
E:missing bitmap /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip
(Code -1)
END OF while ~~~
Command: "/sbin/recovery" "--update_package=/cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip"

ro.boot.serialno=016073271601501A
ro.serialno=016073271601501A
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=lgep769board
ro.revision=6
ro.factorytest=0
ro.lge.hidden_resetmode=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
EXTERNAL_STORAGE_MOUNT=/storage/sdcard0
EXTERNAL_ADD_STORAGE_MOUNT=/storage/external_SD
persist.sys.usb.config=mtp_only
ro.build.id=JZO54K
ro.build.display.id=JZO54K
ro.build.version.incremental=LGMS76910e.4E255E4D
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=2013. 11. 07. (목) 18:21:37 KST
ro.build.date.utc=1383816097
ro.build.type=user
ro.build.user=sunhong2.kim
ro.build.host=Orange
ro.build.tags=release-keys
ro.product.model=LGMS769
ro.product.brand=MetroPCS
ro.product.name=u2_mpcs_us
ro.product.device=u2
ro.product.board=u2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=LGE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=u2
ro.build.description=u2_mpcs_us-user 4.1.2 JZO54K LGMS76910e.4E255E4D release-keys
ro.build.fingerprint=MetroPCS/u2_mpcs_us/u2:4.1.2/JZO54K/LGMS76910e.4E255E4D:user/release-keys
ro.build.characteristics=default
wifi.interface=wlan0
dalvik.vm.heapsize=256m
com.ti.omap_enhancement=true
ro.lge.audio_soundexception=true
ro.lge.audio_soundprofile=true
dolby.audio.hdmi.channels=0
persist.sys.account=0
ro.lk.version=LK MAY-2012
af.resampler.quality=3
persist.sys.system_volume_index=7
persist.sys.system_volume_value=0.5957
persist.sys.sound_enable=2
persist.gsm.sms.forcegsm7=0
ro.build.target_country=US
ro.build.target_operator=TMO
ro.build.target_operator_ext=MPCS_TMO
ro.config.ringtone=Lifes_Good.ogg
ro.config.notification_sound=Olive.ogg
ro.config.alarm_alert=Alarm_1.ogg
ro.metropcs.ui=1
wlan.chip.vendor=brcm
wlan.chip.version=bcm4330x
wifi.supplicant_scan_interval=20
wifi.lge.patch=true
wifi.lge.hanglessid=true
wifi.lge.offdelay=false
dhcp.dlna.using=false
wifi.lge.supportp2p5g=no
wifi.lge.cc.table=true
persist.sys.CIQ.enable=0
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.ms=android-metropcs-us
ro.com.google.gmsversion=4.1_r6
ro.setupwizard.mode=DISABLED
ro.livewallpaper.map=DISABLED
ro.com.google.apphider=off
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.opengles.version=131072
ro.sf.lcd_density=240
ime_split_keyboard=false
hwui.render_dirty_regions=false
ime_trace_apply=true
ime_vibration_pattern=0:50
ro.device.hapticfeedback=1
ime_onehand_keyboard=no
ro.lge.overlay=true
ro.build.target_ril_platform=ifx
ro.ril.wake_lock_timeout=300000
rild.libpath=/system/lib/lge-ril.so
persist.radio.rr.enable=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
ro.lge.swversion=LGMS76910e
ro.lge.basebandversion=L6260_MODEM_SIC_01.1305.00
ro.lge.capp_optimusui=true
ro.lge.capp_core=true
ro.lge.lcd_default_brightness=153
ro.lge.lcd_auto_brightness_mode=false
ro.lge.capp_themeicon=true
ro.lge.capp_drm=true
ro.lge.capp_smartcard=true
ro.lge.capp_smartcard_oma=true
ro.lge.capp_divx_drm=true
ro.lge.capp_almond=true
ro.lge.capp_resource=true
ro.lge.capp_wapservice=true
ro.lge.capp_quickclip_key=true
ro.lge.capp_ghost_finger=true
ro.lge.capp_touch_scroller=true
ro.lge.capp_touch_ldi=true
ro.lge.capp_touch_flcik_noti=true
ro.lge.capp_key_light_off=true
ro.lge.capp_key_exception=true
ro.lge.capp_keyled_timeout=true
ro.lge.capp_valid_batteryid=false
ro.lge.capp_menu_long=true
ro.lge.capp_mdm=true
ro.lge.capp_lockscreen=true
ro.lge.capp_compat=true
ro.lge.capp_bubble_popup=true
ro.lge.capp_smf=true
ro.lge.capp_art=true
lge.signed_image=true
ro.lge.capp_qwindow=true
ro.lge.fonts=true
net.tethering.noprovisioning=false
net.change=net.bt.name
persist.lg.data.fd=
drm.service.enabled=true
ro.lge.capp_smartcard_ac_gp=false
ro.lge.capp_smartcard_ac_gto=true
ro.lge.capp_smartcard_lgril=true
ro.lge.capp_smartcard_uicc=true
ro.lge.capp_smartcard_smartmx=false
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
sys.factory.qem=0
init.svc.brd=running
init.svc.recovery=running
init.svc.adbd=running

Finding update package...
I:Update location: /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1666 bytes; signature 1648 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
failed to stat "/system/app/MetroAppStore.1.8.1.odex": No such file or directory
file "/system/app/MetroAppStore.1.8.1.odex" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a")
assert failed: apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a")
E:Error in /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip
(Status 7)
Installation aborted.
I:timed out waiting for key input; rebooting.
 
Wonderful and thanks!

That clearly shows the issue:

failed to stat "/system/app/MetroAppStore.1.8.1.odex": No such file or directory
file "/system/app/MetroAppStore.1.8.1.odex" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a")
assert failed: apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a")
E:Error in /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_updat e.zip
(Status 7)
Installation aborted.
Click to expand...

You have a system app (or it's .odex file, anyways) "MetroAppStore.1.8.1.odex" that does not match what the OTA expects.

Did you change anything related to this app?

You might have other issues, too, but I'm guessing that the updater-script stops processing after it hits the first issue.

If you are able to save off and keep or if the /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.otaupdate.zip file is still there on your system, you could run my OTA Verifier app against it and it should show you all of your issues.

I'm about to publish a newer (v2.0) version of the app that's more robust and will parse the edify commands better, but it'll take a few hours to show up on the Play Store. Let me know if you're able to still see the above *.otaupdate.zip file in your /cache partition and if you want a copy of my v2.0 app before it his the Store.
 
scary alien said:
Wonderful and thanks!

That clearly shows the issue:



You have a system app (or it's .odex file, anyways) "MetroAppStore.1.8.1.odex" that does not match what the OTA expects.

Did you change anything related to this app?

You might have other issues, too, but I'm guessing that the updater-script stops processing after it hits the first issue.

If you are able to save off and keep or if the /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.otaupdate.zip file is still there on your system, you could run my OTA Verifier app against it and it should show you all of your issues.

I'm about to publish a newer (v2.0) version of the app that's more robust and will parse the edify commands better, but it'll take a few hours to show up on the Play Store. Let me know if you're able to still see the above *.otaupdate.zip file in your /cache partition and if you want a copy of my v2.0 app before it his the Store.
Click to expand...
Wait!!! I think it's because I deleted or disabled the appstore from metropcs built onto the phone while I was rooted once with an app called Link2sd, then I factory restored my phone while it was still rooted, and maybe it saved everything I've done, since I didn't un-root the phone before factory resetting. I know I deleted and disabled stock apps, and whenever I factory restore the phone the apps aren't there. This is why I been trying to flash my phone for a while now. I need to download the apps again maybe.
 
koolsk8ter111 said:
Wait!!! I think it's because I deleted or disabled the appstore from metropcs built onto the phone while I was rooted once with an app called Link2sd, then I factory restored my phone while it was still rooted, and maybe it saved everything I've done, since I didn't un-root the phone before factory resetting. I know I deleted and disabled stock apps, and whenever I factory restore the phone the apps aren't there.
Click to expand...

Sounds like a likely culprit and scenario to me...

If you can re-install the original version, that might get you through the update.

You can verify that you've got the correct file by verifying it against the SHA1 checksums listed in the above apply_patch_check command (OTA's usually test the current version and the one prior, so either version should work).

The new version (v2.0) of my app has been uploaded to the Play Store, but might take a little longer to show up (it used to just take a few minutes...now its a few hours :().
 
scary alien said:
Sounds like a likely culprit and scenario to me...

If you can re-install the original version, that might get you through the update.

You can verify that you've got the correct file by verifying it against the SHA1 checksums listed in the above apply_patch_check command (OTA's usually test the current version and the one prior, so either version should work).

The new version (v2.0) of my app has been uploaded to the Play Store, but might take a little longer to show up (it used to just take a few minutes...now its a few hours :().
Click to expand...
I can't even find the appstore app on the internet. the only way to resolve my issues is to flash my phone, something I cannot do via computer, since whenever I try, no matter what, it says my phone isn't detected by the port (PHONE NOT FOUND), even though I made sure the drivers were installed and everything, put it in update mode, etc... No matter what I do, this phone stops me from doing what I want it to do, which is getting on my nerves.


This problem when trying to flash:


14:32:22 : Launching SW update
14:32:22 : Unpacking KDZ
14:32:57 : KDZ file extraced
14:33:08 : Files were extracted.
14:33:08 : LGMobileDL Load.
14:33:08 : Port = -1
14:33:08 : Connecting to phone
14:33:08 : PHONE WAS NOT FOUND!
14:33:10 : ===FINISHED===

(it's not mine, i copied it)
 
xdrc45 said:
That's the same one I found on the web. Let me know if it works for you. If not I know I have it stored in one of my backups on my PC.
Click to expand...
If it successfully updates the phone, will the appstore from the official OTA rom replace the one I downloaded off the web? Usually the phone goes through app optimization when it updates, or would I have to factory restore the phone to get the appstore built onto the phone like it should be instead of the downloaded version?


Also, instead of waiting weeks for the update to come back, how do I make it come now, so I could just see if it actually updates, instead of waiting almost a month for a new OTA notification?
 
koolsk8ter111 said:
If it successfully updates the phone, will the appstore from the official OTA rom replace the one I downloaded off the web? Usually the phone goes through app optimization when it updates, or would I have to factory restore the phone to get the appstore built onto the phone like it should be instead of the downloaded version?


Also, instead of waiting weeks for the update to come back, how do I make it come now, so I could just see if it actually updates, instead of waiting almost a month for a new OTA notification?
Click to expand...

See if you still have the /cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip file on your device (I'm betting you don't though because I believe it gets deleted after an OTA installation attempt by your recovery).

If you do, you can run my OTA Verifier app against it to check for other issues.

Or, when you do see it come in next time, don't do the reboot right away and/or make a copy of this file so you can view it and/or run my app against it.

The updater-script file inside that ota_update.zip file will tell you what will happen to your app store files (I'm guessing it wants to update it, since it's explicitly checking to make sure it the right version).

Also, there are known ways to trigger OTA checks updates, but they might vary by device...
 
alright i got it. I followed these steps


1: Go into Settings --> Apps --> All
2: Scroll down to and select "Google Services Framework"
3: Click on Force Stop (let it stop) and then click on Clear Data
4: Hit your back arrow and go to About Tablet --> System Updates (should say it last checked in 1969) and hit Check for Updates
5: Let it download and install


That was pretty easy lol
 
I updated the phone and it failed again, but at least I can bring up the update whenever I want now. I am going to try something different:

(script aborted: assert failed: apply_patch_check("/system/app/MetroAppStore.1.8.1.odex",)

That script is an indication that the update couldn't find the appstore onto the system folder. So I am going to try to get the appstore onto the phone as a stock/system app.
 
K, so none of this actually worked unforturnately.

What is the easiest way I could flash my phone's stock rom?

Is there another program to use other than LG's software, since that always fails for me?
 
You must log in or register to reply here.
Back
Top Bottom