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

Root New OTA issues

palmtree5

palmtree5

Sunny Vacation Supporter!
Moderator
Received a notification about a new OTA and attempted to update (which failed, of course) So I used this app and am posting the output here.

[HIGH]================== Detailed Analysis ==================
- you have 6 frozen system apps; this may (but not necessarily) impact the ability of
the OTA's updater-script to update these apps and cause the OTA install to fail
- there were 3 failed expressions; see below
for the details about these tests that will cause your OTA install to fail
- there were no bypassed expressions (good!)
-------------------------------
Frozen system apps analysis:
1. ASUS Keyboard
2. Device Policy
3. Google Hindi Input
4. Google Korean keyboard
5. Who Am I?
6. iWnn IME
-------------------------------
statistics:
frozen system apps: 6
success count: 211
fail count: 3
ignore count: 651
partition count: 0
protected count: 0
bypassed count: 0
Device information:
Device: grouper
Maker: asus
Model: Nexus 7
Carrier:
Board: grouper
Name: nakasi
Bootloader: 4.23
Android OS: 4.3
-------------------------------
updater-script analysis details:
FAILED: line #138:
assert(apply_patch_check("/system/app/Keep.odex",
"3af602f90589be934a937dc78a5ac0dfdb3031ad",
"a2e89c93ff50754e7abb82bffd26bfb58cd50aae"));
----------------------
FAILED: line #144:
assert(apply_patch_check("/system/app/LatinImeGoogle.apk", "f9f2d31431a1ab8e8bb6a59d1140392271970038",
"50a127cea592446b11be96a166bc8d6a72d8dcd3"));
----------------------
FAILED: line #410:
assert(apply_patch_check("/system/lib/libwebcore.so",
"0fc28968fe51732eec8659cbce2c59693437fa6c",
"776f151ca6eb6c2438d1dd2b06f55c2c7a375440"));
[/HIGH]
 
Hey palmtree! :wavey:

Lemme find the thread where I posted a special version of the OTA Verifier app that will display the actual SHA1 digests that the app sees so that I can compare my files against yours.

I've not yet installed the 4.3 OTA on my device, so I should be able to compare and see what is up.

I think the issues that I've seen and read about where various rooted apps that were monkeying with system files that you're not necessarily made aware of until it's too late (i.e., when you are ready to install an OTA :p).

(you're rooted, right?)

Thanks!
 
Yes, I'm rooted

Here's the output:

[HIGH]==================
Detailed Analysis
==================

- you have 6 frozen system apps; this may (but not necessarily) impact the ability of the OTA's updater-script to update these apps and cause the OTA install to fail

- there were 3 failed expressions; see below for the details about these tests that will cause your OTA install to fail

- there were no bypassed expressions (good!)

-------------------------------
Frozen system apps analysis:

1. ASUS Keyboard
2. Device Policy
3. Google Hindi Input
4. Google Korean keyboard
5. Who Am I?
6. iWnn IME

-------------------------------
statistics:

frozen system apps: 6
success count: 211
fail count: 3
ignore count: 651
partition count: 0
protected count: 0
bypassed count: 0

Device information:

Device: grouper
Maker: asus
Model: Nexus 7
Carrier:
Board: grouper
Name: nakasi
Bootloader: 4.23
Android OS: 4.3

-------------------------------
updater-script analysis details:

FAILED: line #138:

assert(apply_patch_check("/system/app/Keep.odex", "3af602f90589be934a937dc78a5ac0dfdb3031ad", "a2e89c93ff50754e7abb82bffd26bfb58cd50aae"));

[the SHA1 checksum for file /system/app/Keep.odex (adae4df9fc2334e417296f41cf048f471116fa45) does not match any SHA1 in the above expression]

----------------------
FAILED: line #144:

assert(apply_patch_check("/system/app/LatinImeGoogle.apk", "f9f2d31431a1ab8e8bb6a59d1140392271970038", "50a127cea592446b11be96a166bc8d6a72d8dcd3"));

[the SHA1 checksum for file /system/app/LatinImeGoogle.apk (01afb9b584289f61e3ed81790b17a2e08a77dc71) does not match any SHA1 in the above expression]

----------------------
FAILED: line #410:

assert(apply_patch_check("/system/lib/libwebcore.so", "0fc28968fe51732eec8659cbce2c59693437fa6c", "776f151ca6eb6c2438d1dd2b06f55c2c7a375440"));

[the SHA1 checksum for file /system/lib/libwebcore.so (285d200e9a68ad0f0d572f474ed40a88f058c959) does not match any SHA1 in the above expression]

(the above text has been copied to the clipboard)[/HIGH]
 
Oh, palmtree!

I just noticed / realized you are already on 4.3--so, this is yet another OTA? :eek:

I don't even have the Keep.odex file on my 4.2.2 N7, so I'm not sure how much help I can be with comparing my files to yours.

I take it you installed the 4.2.2 -> first 4.3 OTA with no issues?

Also, what root-related apps have you installed since then? They might have tweaked some of the files that are showing as not matching...:dontknow:
 
scary alien said:
Oh, palmtree!

I just noticed / realized you are already on 4.3--so, this is yet another OTA? :eek:
Yes, the build number on it is JWR66Y
I don't even have the Keep.odex file on my 4.2.2 N7, so I'm not sure how much help I can be with comparing my files to yours.

I take it you installed the 4.2.2 -> first 4.3 OTA with no issues?
Yes, if I remember correctly, I had no issues with that at all
Also, what root-related apps have you installed since then? They might have tweaked some of the files that are showing as not matching...:dontknow:
Not really sure, other than replacing SuperSU with CWM Superuser when it was updated to support 4.3
Click to expand...

:dontknow:
 
Got it to work

I happen to have a copy of the factory image for 4.3 (build JWR66V) for grouper on my computer. From there, it was a simple matter of mounting the system image to a folder on my computer, checking the SHA1 sums of the files in question, pushing them to the device via ADB, and manually copying them to their appropriate locations using ES File Explorer

Conveniently, the OTA breaks root

Reflashed Superuser via a zip file and it works
 
:thumbup: Awesome!

I was just gonna suggest grabbing the factory image and unpacking it to grab the files that are needed (I do it on my Linux system--do you use Cygwin or Linux?).

I still wonder if one of your apps is the one responsible for replacing those files in question? :dontknow:
 
Linux

As for the apps, wouldn't updates to the app have a different SHA1 sum than what the script is looking for?

I'm lucky I had that factory image on my computer already as the one for the version I was coming from was replaced by the new one in the list of factory images
 
palmtree5 said:
Linux

As for the apps, wouldn't updates to the app have a different SHA1 sum than what the script is looking for?

I'm lucky I had that factory image on my computer already as the one for the version I was coming from was replaced by the new one in the list of factory images
Click to expand...

Yeah, I'm thinking that the (root) app might update/replace one of those systems files which their own version (which is why you'd see three different SHA1 values (the new, unknown file from the app and the two values specified in the updater-script file (those values are typically the digest of the previous and current Android version of that file)).

I think we saw that the new SuperSU updated a file or two, but I'm not recalling that perfectly at this time :p.
 
scary alien said:
Yeah, I'm thinking that the (root) app might update/replace one of those systems files which their own version (which is why you'd see three different SHA1 values (the new, unknown file from the app and the two values specified in the updater-script file (those values are typically the digest of the previous and current Android version of that file)).

I think we saw that the new SuperSU updated a file or two, but I'm not recalling that perfectly at this time :p.
Click to expand...
If I'm not mistaken, the new SuperSU mods the install_recovery.sh file to run root at daemon, due to the way 4.3 looks at admin file directories.
 
You must log in or register to reply here.
Back
Top Bottom