R2D2 after OTA 4.5.602 bootanimation.zip?
Long long ago, in a -- oh nevermind that for now... and now for something completely different... or not... but I still haven't found what I'm looking for.
In Froyo I was able to access bootanimation.zip, mount/open it with File Expert app, and rename the screaming R2D2 audio file per desc.txt so it wouldn't be found by the boot script. Result: I kept the R2D2 stock boot animation sans audio.
Couple nights ago, allowed the OTA upgrade since I was already up for no good reason and chose "remind me later" twice to the VZW prompt, "why not?" From what I gleam but don't truly understand, my R2D2 supposedly would neglect/disallow/block the OTA upgrade directly from VZW because I had rooted it previously to gain superuser access to mod the bootanimation.zip (among other useful root features), so I was surprised to even get the upgrade notification OTA. Perhaps, "it's a traaaaap!" ???
I skimmed various forum posts suggesting that I would need to unroot my device to successfully upgrade via OTA, and I decided to dive right in, guessing the upgrade would at worst drop back to Froyo as-is, without further tampering or attempting to unroot. So now, running for more than a day in Gingerbread R2D2 is screaming (like a rooster?) quite proudly at each boot. The OTA reloaded/replaced my modded bootanimation.zip with the original audio file.
We're kinda back to stock? Curiouser...
I thought it would be no problem using File Expert to mod bootanimation.zip as I had previously, but I can't seem to find it on any path starting from root folders (/system/media...), so now I come to the question:
Is my R2D2 root/superuser wiped by the OTA? My other root-dependent apps are still functioning. Follow-up questions: Is it possible my device was never completely rooted so that maybe certain access was granted to superuser but not full root, as in semirooted? How could I confidently test whether my root access is still in effect? And lastly, "Where's the beeP?"
The goal: to find my system/media path so I can access that boot audio file and silence it again. If I need to root GB since finishing OTA upgrade, I would dare to reroot, just to seek and destroy that noise. I really don't want shrieking R2D2 on boot or reboot, returning to my solution of burying the speaker under pillows to muffle the audio at startup.
I'll be patient, if it's just a matter of time waiting for more competent users than I, to release a how-to for defeating this R2D2 *feature* for post-upgraded devices. My main concern is that I can't find the path. (Stops rambling ...nnnow)
Suggestions? Thanks in advance!
Sent from my R2D2 Droid using DroidForums App