PRS-T1 How to edit EbookReader.apk and make it work on non-rooted device?

[ever2047]

1: I use Apktool to unpack EbookReader.apk and made some changes.
but some errors occured when I bulid it to apk.

D:\apk>java -jar apktool.jar b EbookReader
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
Exception in thread "main" brut.androlib.AndrolibException: brut.common.
ption: could not exec command: [aapt, p, -F, C:\DOCUME~1\ADMINI~1\LOCALS
APKTOOL4651201101303012885.tmp, -I, C:\Documents and Settings\Administra
ool\framework\1.apk, -S, D:\mo\apk\EbookReader\res, -M, D:\mo\apk\EbookR
droidManifest.xml]
        at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResou
a:193)

....

2: Need edited apk files to be re-signed? How?

3: How to install edited apk files to non-rooted device?

[jr17oo]

I am not an expert, but a forum search could have brought you to this thread. It might contain some useful information.

If I remember correctly, there is a version of Morkl's EbookHome.apk which can be installed on non-rooted devices. You could try to take apart the installation package to find out how it is done.

[ever2047]

Originally Posted by jr17oo

I am not an expert, but a forum search could have brought you to this thread. It might contain some useful information.

If I remember correctly, there is a version of Morkl's EbookHome.apk which can be installed on non-rooted devices. You could try to take apart the installation package to find out how it is done.

Thank jr17oo a lot! I will try.

Problem 1 solved: I found my aapt(part of apktool) is for linux and I ran it on windows.

[flyingdog]

it was not a problem for me.. you can reverse it either way via pure smali or jartool but you have always to use the correct liblevel and provide the bootclasspath since all your stuff is odexed don't forget

[flyingdog]

there is no way to reinstall it on a non rooted device .. you must use adb and sign your apk properly.. on top remember that the full rom is odexed

[ever2047]

Originally Posted by flyingdog

it was not a problem for me.. you can reverse it either way via pure smali or jartool but you have always to use the correct liblevel and provide the bootclasspath since all your stuff is odexed don't forget

Thanks very much.
Apktool 1.43 does not work, but 1.4.2 works well on my windows.

[ever2047]

Originally Posted by flyingdog

there is no way to reinstall it on a non rooted device .. you must use adb and sign your apk properly.. on top remember that the full rom is odexed

I see that some mods installed (or overwrote?) by flash_reader.bat work on non-rooted device.
Whats the signature of those mods? Any other signature works?

I'm doing some localizations.

[Mark Nord]

There was the word that sony is using a set of cyanomod keys to sign its apps.
Think read it from rupor over at the-ebook.org, or in one of his replys to Morkl.

[jr17oo]

Originally Posted by Mark Nord

There was the word that sony is using a set of cyanomod keys to sign its apps.
Think read it from rupor over at the-ebook.org, or in one of his replys to Morkl.

I just looked it up, it was in a thread here at MobileRead. I tried to find the keys.txt he mentions, but had no luck.

Originally Posted by ever2047

I'm doing some localizations.

If you are only interested in localizations, you could as well ask Morkl or rupor to integrate them in their packages, so other people can benefit from your work.

[j0534ng31]

Originally Posted by jr17oo

I just looked it up, it was in a thread here at MobileRead. I tried to find the keys.txt he mentions, but had no luck.

Keys (not txt) are here: CyanogenMOD Gingerbread keys (it must be the 'test*' one)

[rupor]

Since my first reply on the subject we discovered that those are exactly the same keys Google included in every Android SDK released, so I removed keys.txt. In SVN however build_all.cmd lists key names Sony used to build each of the APK files I know about...

[j0534ng31]

rupor,

Thank you!