• 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?

koolsk8ter111,

Since you've got a copy of the OTA.zip file (or can easily force it to download), have you run my app against it to see if that is the only file you've got issue with?

If it is the only file, you really shouldn't have too much to do to get that squared-away...
 
scary alien said:
koolsk8ter111,

Since you've got a copy of the OTA.zip file (or can easily force it to download), have you run my app against it to see if that is the only file you've got issue with?

If it is the only file, you really shouldn't have too much to do to get that squared-away...
Click to expand...

How does that OTA app work? I still don't understand where and what zip file to find.
 
koolsk8ter111 said:
How does that OTA app work? I still don't understand where and what zip file to find.
Click to expand...

1. Download and install my app (free from the Play Store):


2. The OTA .zip file is getting downloaded into your /cache directory when you're doing the trick with the Google Services Framework thing.

3. After you do that, do not restart your device, but instead:

launch my OTA Verifier app
grant it root permissions
press the "Select File" button
navigate to the /cache folder
long-press the *.ota_update.zip file
select Verify updater-script option (it's the only one)
copy & paste it's output back here (all it's output is sent to the clipboard)​

4. Optionally, but recommended: use a rooted file explorer like Root Explorer or ES File Manager to copy that *.ota_update.zip file to your /sdcard or somewhere safe--that way, you'll have access to it when you want.

The *.ota_update.zip file will still be in your /cache folder until you try to install the OTA.
 
koolsk8ter111 said:
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.
Click to expand...

The "MetroAppStore.1.8.1.odex" is actually a separate file from the "MetroAppStore.APK". The odex file is basically a file extension of the APK that has pre-boot load information about the APK.
So you'll actually need both the APK. and the .odex file.

Also just an FYI you can easily set almost any app as a system app simply by using a root browser and moving the APK to /system/app/ and setting permissions to 644 or rw-r-r
 
--------------------------------------------
Failed expression at line #596:

assert(apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.1/by-name/boot:7028736:5c64a1ff5b67b8697714f69a91557e22acf7d291:7032832:c953f643d61e9363d62f1e74c49418d06563f04c"));

[actual SHA1 of target file: 940ef31d0d814a149d9a1536421aae45a1c59ccf]



Selected file to process:

/cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip

---------------------------------
Analysis:

statements read: 1243
expressions processed: 307
true statements: 306
false statements: 1
inaccessible count: 0

- there were (1) failed expressions encountered (see details above)

Device information:

Device: u2
Maker: LGE
Model: LGMS769
Carrier: T-Mobile
Board: u2
Name: u2_mpcs_us
Bootloader: unknown
Android OS: 4.1.2

(the above text has been copied to the clipboard)
 
Thanks and that's actually very interesting on two fronts:

1. It looks like you've got a different boot image than what the OTA expects...I wonder if that happened when you tried returning to stock? The recovery and boot image tests are usually done at the end of the list of .apk files to be cross-checked, so I imagine that after you resolve the problem with the missing MetroAppStore.1.8.1.odex file, you'll still have to deal with this.

2. Knowing that your MetroAppStore.1.8.1.odex is missing and that my app didn't catch it tells me my new version of the app has a bug with missing files. I'm looking into that now and will re-upload my app when I've fixed this issue (:banghead: :p).
 
Ok @koolsk8ter111 I ended up finding the metro AppStore 1.8.1 APK and the .odex file for you in one of my L9 backups. I uploaded it to my Dev-Host account here - Dev-Host - L9 - MetroPCS AppStore v1.8.1 APK and .odex file.zip - The Ultimate Free File Hosting / File Sharing Service

Make sure that both are put in /system/app/
Permissions set to 644/ rw-r-r
Or use the system app mover that you found.

Once scary alien fixes the bug in his OTA Verifier App and after you run it, if you find that your missing anymore system apps just let me know... I have all of them easily available now.
 
^^^ Thanks, xdrc45! Much appreciated :thumbup: :).

I've just published the fixed (v2.1) version (had to tweak the code to discriminate between between read/access-protected files and truly non-existent files), so it should be show up as an update in a few hours.

Still a bit concerned that the boot image will be a sticking point...:dontknow:
 
scary alien said:
^^^ Thanks, xdrc45! Much appreciated :thumbup: :).

I've just published the fixed (v2.1) version (had to tweak the code to discriminate between between read/access-protected files and truly non-existent files), so it should be show up as an update in a few hours.

Still a bit concerned that the boot image will be a sticking point...:dontknow:
Click to expand...

Thank you scary alien... Your awesome!!! :thumbup:
Great job on your OTA Verifier App. You got that fixed quick.

Yeah, I'm thinking that boot.img is gonna be a problem too. I'll see about pulling the right one from the my v10E and uploading it.
I'm curious to know what boot.img koolsk8ter111 currently has and how exactly he got it.
 
Ok @koolsk8ter111 if you still need it here's the boot.img. I just pulled it from my stock v10E nandroid backup, so this should be the right one that the OTA is checking against.
Dev-Host - L9 v10E boot.img.zip - The Ultimate Free File Hosting / File Sharing Service


Even thought this came from a nandroid backup, this isn't a flashable zip through recovery.
You would need to extract the file and place just the boot.img in the "platform tools" folder and then flash it using fastboot:

fastboot flash boot boot.img


Make sure that you have and save a copy of your current boot.img just in case something goes wrong.
 
xdrc45 said:
Ok @koolsk8ter111 I ended up finding the metro AppStore 1.8.1 APK and the .odex file for you in one of my L9 backups. I uploaded it to my Dev-Host account here - Dev-Host - L9 - MetroPCS AppStore v1.8.1 APK and .odex file.zip - The Ultimate Free File Hosting / File Sharing Service

Make sure that both are put in /system/app/
Permissions set to 644/ rw-r-r
Or use the system app mover that you found.

Once scary alien fixes the bug in his OTA Verifier App and after you run it, if you find that your missing anymore system apps just let me know... I have all of them easily available now.
Click to expand...
I'll use the system app mover.

but what was the boot.img you were talking about? What should I do with it? Is it necessary to do anything with the boot.img file?

If I am using the system app mover, I don't need to do anything with the permissions?
 
koolsk8ter111 said:
I'll use the system app mover.

but what was the boot.img you were talking about? What should I do with it? Is it necessary to do anything with the boot.img file?

If I am using the system app mover, I don't need to do anything with the permissions?
Click to expand...

If your using the system app mover then you shouldn't have to set the permissions. Just move both the APK and .odex file to the /system/apps/

The boot.img is for, when you ran scary alien's OTA Verifier App it gave a boot.img error.

After moving the APK and .odex file to the system apps, I would download the new version of the OTA Verifier App v2.1 and run it against the OTA update again to see what errors you might get and then post the output log here again.
If you get the boot.img error again then you'll need to try and flash that boot.img I posted to see if it will pass the OTA verification or if your missing anymore system apps/.odex files I can upload them for you.
 
xdrc45 said:
If your using the system app mover then you shouldn't have to set the permissions. Just move both the APK and .odex file to the /system/apps/

The boot.img is for, when you ran scary alien's OTA Verifier App it gave a boot.img error.

After moving the APK and .odex file to the system apps, I would download the new version of the OTA Verifier App v2.1 and run it against the OTA update again to see what errors you might get and then post the output log here again.
If you get the boot.img error again then you'll need to try and flash that boot.img I posted to see if it will pass the OTA verification or if your missing anymore system apps/.odex files I can upload them for you.
Click to expand...
Thank you.

One quick thing. Do you have to install the odex file as an app on the phone like an apk file? Or do I just transfer it over to the /system folder some how? I don't know if I can transfer odex files via app mover, because the app mover I'm sure only moves actual apps/apks to the /system folder after they've been installed, but what about files like the odex ones?
 
koolsk8ter111 said:
Thank you.

One quick thing. Do you have to install the odex file as an app on the phone like an apk file? Or do I just transfer it over to the /system folder some how? I don't know if I can transfer odex files via app mover, because the app mover I'm sure only moves actual apps/apks to the /system folder after they've been installed, but what about files like the odex ones?
Click to expand...

Yeah if the System App Mover won't move the AppStore.odex file then just use an app like Root Browser to do it.
Copy the AppStore.odex file to you sdcard. Open Root Browser and navigate to the sdcard, long press on the AppStore.odex file and and select move, then navigate to /system/app/ and select paste. Once it's pasted, scroll to the AppStore.odex and then long press on it again and select permissions. Set the permissions to 644 or rw-r-r
Save, exit and done.
 
Do I need the odex file to install? because it's not letting me install the appstore app. Every time I try to install the apk, it says "application not installed" when I press the install button. I have unknown sources checked as well.
 
Alright, even though I didn't get the metro app installed. I'll still give you the log from the OTA verify app.



--------------------------------------------
Failed expression at line #230:

assert(apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a"));

[actual SHA1 of target file: 28059261de6c07632f2511c30baae3c421e1822e]

--------------------------------------------
Failed expression at line #232:

assert(apply_patch_check("/system/app/MobilePosse_MetroPCS.odex", "36ee63a8d1559d67839944a8a9e63258bd09cf9d", "5300dd130e3cede91592f4933490869aa692051a"));

Note: could not access: /system/app/MobilePosse_MetroPCS.odex

--------------------------------------------
Failed expression at line #258:

assert(apply_patch_check("/system/app/RhapsodyStub.odex", "f1f53bb74b8e6303c77ce2f87cf3cbf7c4164886", "ecc20ab0e62739ecdc0f043be517be03d05db4ad"));

Note: could not access: /system/app/RhapsodyStub.odex

--------------------------------------------
Failed expression at line #294:

assert(apply_patch_check("/system/app/VVM-release-MPCS.odex", "48b6be298aac2205161b765f95226697c51b8b7b", "735ccac0140936c894c266b1de4e67cd09bc4c84"));

Note: could not access: /system/app/VVM-release-MPCS.odex

--------------------------------------------
Failed expression at line #596:

assert(apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.1/by-name/boot:7028736:5c64a1ff5b67b8697714f69a91557e22acf7d291:7032832:c953f643d61e9363d62f1e74c49418d06563f04c"));

[actual SHA1 of target file: 940ef31d0d814a149d9a1536421aae45a1c59ccf]



Selected file to process:

/cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip

---------------------------------
Analysis:

statements read: 1243
expressions processed: 307
true statements: 302
false statements: 5
inaccessible count: 12

- there were (5) failed expressions encountered (see details above)

- there were (12) files could not be accessed (see details above)

Device information:

Device: u2
Maker: LGE
Model: LGMS769
Carrier: T-Mobile
Board: u2
Name: u2_mpcs_us
Bootloader: unknown
Android OS: 4.1.2

(the above text has been copied to the clipboard)
 
koolsk8ter111 said:
Alright, even though I didn't get the metro app installed. I'll still give you the log from the OTA verify app.



--------------------------------------------
Failed expression at line #230:

assert(apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a"));

[actual SHA1 of target file: 28059261de6c07632f2511c30baae3c421e1822e]

--------------------------------------------
Failed expression at line #232:

assert(apply_patch_check("/system/app/MobilePosse_MetroPCS.odex", "36ee63a8d1559d67839944a8a9e63258bd09cf9d", "5300dd130e3cede91592f4933490869aa692051a"));

Note: could not access: /system/app/MobilePosse_MetroPCS.odex

--------------------------------------------
Failed expression at line #258:

assert(apply_patch_check("/system/app/RhapsodyStub.odex", "f1f53bb74b8e6303c77ce2f87cf3cbf7c4164886", "ecc20ab0e62739ecdc0f043be517be03d05db4ad"));

Note: could not access: /system/app/RhapsodyStub.odex

--------------------------------------------
Failed expression at line #294:

assert(apply_patch_check("/system/app/VVM-release-MPCS.odex", "48b6be298aac2205161b765f95226697c51b8b7b", "735ccac0140936c894c266b1de4e67cd09bc4c84"));

Note: could not access: /system/app/VVM-release-MPCS.odex

--------------------------------------------
Failed expression at line #596:

assert(apply_patch_check("EMMC:/dev/block/platform/omap/omap_hsmmc.1/by-name/boot:7028736:5c64a1ff5b67b8697714f69a91557e22acf7d291:7032832:c953f643d61e9363d62f1e74c49418d06563f04c"));

[actual SHA1 of target file: 940ef31d0d814a149d9a1536421aae45a1c59ccf]



Selected file to process:

/cache/7c3d73ff84aead1a3ab54509d7528a5042144b5f.ota_update.zip

---------------------------------
Analysis:

statements read: 1243
expressions processed: 307
true statements: 302
false statements: 5
inaccessible count: 12

- there were (5) failed expressions encountered (see details above)

- there were (12) files could not be accessed (see details above)

Device information:

Device: u2
Maker: LGE
Model: LGMS769
Carrier: T-Mobile
Board: u2
Name: u2_mpcs_us
Bootloader: unknown
Android OS: 4.1.2

(the above text has been copied to the clipboard)
Click to expand...

Ok it looks like your missing a couple .odex files.
Do you have the mobileposse/rhapsody/vvm visual voicemail APK's in /system/app/ ? Or are you missing both the APK's and .odex files? That way I know if if need to upload the APK's and .odex files for you.
Looks like your gonna have to try and flash that boot.img too.

Now for installing the APK's...
What file/root browser are you using?

Do you have SuperSU installed?

Have you tried rebooting the phone after moving the APK and .odex file to /system/app ?

You were able to set the permissions and did the permissions stick after setting them?

If you already moved the AppStore with the "System App Mover" it might not let you move the version I uploaded for you into /system/app/ you might have to delete it and try it again.

You might also want to try doing it the same way but instead of moving the APK and .odex to /system/app/ try copying it there.
 
@koolsk8ter111
Just another thought... Check the permissions settings on the whole /system/app/ folder.
It should be set as 755 or rwxr-xr-x
I use Root Browser with SuperSU permissions so that when editing folders, files, etc.. It's mounted as RW (read/write) if the file browser that you are using is set as "read only" and doesn't have SuperSU permissions, then any of the changes that you make won't stick.

Also I'll start pulling those missing APK's and .odex files for you and get them uploaded.:thumb:
 
xdrc45 said:
Ok it looks like your missing a couple .odex files.
Do you have the mobileposse/rhapsody/vvm visual voicemail APK's in /system/app/ ? Or are you missing both the APK's and .odex files? That way I know if if need to upload the APK's and .odex files for you.
Looks like your gonna have to try and flash that boot.img too.

Now for installing the APK's...
What file/root browser are you using?

Do you have SuperSU installed?

Have you tried rebooting the phone after moving the APK and .odex file to /system/app ?

You were able to set the permissions and did the permissions stick after setting them?

If you already moved the AppStore with the "System App Mover" it might not let you move the version I uploaded for you into /system/app/ you might have to delete it and try it again.

You might also want to try doing it the same way but instead of moving the APK and .odex to /system/app/ try copying it there.
Click to expand...

I deleted the other appstore and I did do the things you said above, and yes I am using the Root Browser and SuperSU. I think it would be pointless to insert more odex files, since I already put one in the system folder and it still says there's an error with the metroappstore one. It would give off the error with the other ones as well I presume.


Other options? Should I try flashing the rom of my phone? I cannot use the LG software, as it fails to recognize my phone in the usb ports even when I put it in SW upgrade mode.
 
xdrc45 said:
@koolsk8ter111
Just another thought... Check the permissions settings on the whole /system/app/ folder.
It should be set as 755 or rwxr-xr-x
I use Root Browser with SuperSU permissions so that when editing folders, files, etc.. It's mounted as RW (read/write) if the file browser that you are using is set as "read only" and doesn't have SuperSU permissions, then any of the changes that you make won't stick.

Also I'll start pulling those missing APK's and .odex files for you and get them uploaded.:thumb:
Click to expand...
Alright I try changing the permissions again.
 
Guys,

I've calculated the SHA1 digests of each of the files that xdrc45 kindly provided above. The disconcerting thing is that they don't match any of the digest values that it looks like the OTA is looking for (so, installing these files will not help the OTA succeed):

Failed expression at line #230:

assert(apply_patch_check("/system/app/MetroAppStore.1.8.1.odex", "b3895800b5ea86931abbe63a84375a23be57b447", "5a7c62093f69a5fcbb3b313982b370a21818a58a"));

[actual SHA1 of target file: 28059261de6c07632f2511c30baae3c421e1822e]

xdrc45 file: 28059261de6c07632f2511c30baae3c421e1822e *MetroAppStore.1.8.1.odex

(this value actually matches what the OP has on his phone--it just doesn't match the OTA expectation)

--------------------------------------------
Failed expression at line #232:

assert(apply_patch_check("/system/app/MobilePosse_MetroPCS.odex", "36ee63a8d1559d67839944a8a9e63258bd09cf9d", "5300dd130e3cede91592f4933490869aa692051a"));

Note: could not access: /system/app/MobilePosse_MetroPCS.odex

xdrc45 file: 5931e3160f81fdb0abd10e2c229c9185894cc90c *MobilePosse_MetroPCS.odex

--------------------------------------------
Failed expression at line #258:

assert(apply_patch_check("/system/app/RhapsodyStub.odex", "f1f53bb74b8e6303c77ce2f87cf3cbf7c4164886", "ecc20ab0e62739ecdc0f043be517be03d05db4ad"));

Note: could not access: /system/app/RhapsodyStub.odex

xdrc45 file: fd0469ce7dfc923cf316169c5a78c6b32bb35759 *RhapsodyStub.odex

--------------------------------------------
Failed expression at line #294:

assert(apply_patch_check("/system/app/VVM-release-MPCS.odex", "48b6be298aac2205161b765f95226697c51b8b7b", "735ccac0140936c894c266b1de4e67cd09bc4c84"));

Note: could not access: /system/app/VVM-release-MPCS.odex

xdrc45 file: ed624359259f9f870655b4ac63f6cb305accc3be *VVM-release-MPCS.odex
Click to expand...

Also, there's still the boot image to take into account :(.
 
Nice work scary alien! :alberteinstein::thumbup: You know your OTA Verifier App is pretty Bad@$$!! Thank you!


Now onto the sad note...Well that stinks!
Man that will probably be pretty tough to find all of these apps with matching digest values then.
There's probably no way to really edit the digest values either.

You would have to actually download the v10Fkdz and either, copy the metro apps from the system.img and then use those as the apps to reinstall on the L9

Or
You can remove those apps from the OTA update completely. So those apps aren't in the update to be check against.

Plus there's still the boot.img too.

scary alien
Can you check the registry vales on the boot.img and see if they match with the OTA?

You could flash all the way back to stock with the Offline kdz flash method or the LG Mobile update tool.

Kools8ter111
I guess I never really asked.. Do you have a stock nandroid backup?
 
You must log in or register to reply here.
Back
Top Bottom