[Motorola Atrix 2] PRichardson:
Deconstructing Class Warfare, one Flub at a Time

I'm still trying to decipher the prose of some of our fellows, however, this stumped me a bit..

What I shall therefor do, is make some guesses here (sorry, I really wish I could just read a book about all this, but time time time, is so very precious, and I've got 5 kids!). Maybe a generous old sage will correct my flubs, wherever they may be, in what follows..:confused:

I'd presume that permissions of files change, once they are moved about. So, the above would be what one should see after the files are in their final resting place, on the phone, correct? And all 3 files should have this permission? hmm... well, I went to the Chinese forum mentioned above, and I have the files now.

=====================================================================

FILE STRUCTURE OF THE PACKAGE: "PhoneRecording-ByZadarboy.zip" is at the bottom/below.

(excepting, the initial portion of the filepath, which is of course, merely where the files are

at on my PC, aka, "D:\")

SIZE: 2.69 MB (2,828,218 bytes) (typically ~2.69 MB (2,830,336 bytes) on NTFS Disk)

HASHES: CRC32: 2428CBAD

MD5: 6A5E3965DAB8A126B35A618162694F6E

SHA-1: 2494CEDBC5D6F54CDA71E23F6927F6D1DBEF920B

=====================================================================

-D:\PhoneRecording-ByZadarboy\ << (FOLDER)

|

|-D:\PhoneRecording-ByZadarboy\META-INF << (SUB-FOLDER 1)

|	|-CERT.RSA

|	|-CERT.SF

|	|-MANIFEST.MF

|	-D:\PhoneRecording-ByZadarboy\META-INF\com << (SUB-FOLDER 1.1)

|	-D:\PhoneRecording-ByZadarboy\META-INF\com\google << (SUB-FOLDER 1.1.1)

|	-D:\PhoneRecording-ByZadarboy\META-INF\com\google\android

|	|-update-binary

|	|-updater-script

-D:\PhoneRecording-ByZadarboy\system << (SUB-FOLDER 2)

|-D:\PhoneRecording-ByZadarboy\system\app << (SUB-FOLDER 2.1)

|	|-BlurPhone.apk << (FILE 2.1.a)

|	|-SoundRecorderMot.apk << (FILE 2.1.b)

-D:\PhoneRecording-ByZadarboy\system\lib << (SUB-FOLDER 2.2)

|-libaudio.so << (FILE 2.2.a)

===============================================================

NOTE: Please notice that I have devised a syntactical notation to refer to specific files by location in the folder/file/path structure. I'm not sure if this is ever used anywhere else, but it will keep us on the same page, if further discussion of these files (or their functions) arises later.

===============================================================

Without knowing anything at all about how CWM words, I will assume that the cryptographic certs and manifest stuff has to do with just allowing this to install. And that still leaves 2 files in the com\google\android path, but again, I think those have to do with update, as they both have update in the name (update-binary, and updater-script). So the real payload here, I would think it perhaps safe to assume, consists of 3 remaining files, namely, the 2 apks, and the \system\lib\libaudio.so

I will guess that so stands for 'shared object', and it's some kind of a C or C++ compiled class or something, that has some useful functionality built into it, and that much the same as an Android NDK, that the flashing process builds these apps back into our phone's operating system in a way that uses this functionality to circumvent the idiotic 'above the law' blocks placed on the slave-class by the proletariat.